New Meridian Flip error - fails to solve

Might be an idea to ask your question on the ZWO forum as someone may have reported the issue as well.  Just a thought.

Brian Puhl:
Usually issues like this are related to clock or location settings.    I'd just double check, and make sure the correct settings are also synced to the mount.

Thanks...I was wondering the same thing.  Lat/long looked right and I was running GMT/UTC on my iPad to control (as I've heard DST can cause problems...eventhough that shouldn't be an issue until the Fall).

Will study the mount's specific settings/clock more closely on next outing

Brian Puhl:

Chris:

Brian Puhl:
Usually issues like this are related to clock or location settings.    I'd just double check, and make sure the correct settings are also synced to the mount.

Thanks...I was wondering the same thing.  Lat/long looked right and I was running GMT/UTC on my iPad to control (as I've heard DST can cause problems...eventhough that shouldn't be an issue until the Fall).

Will study the mount's specific settings/clock more closely on next outing

Presuming you're using NINA.... As long as the time is correct for your location, use the sync to mount option. 

If you changed your time on your ipad to GMT and not your own time zone.... and it synced, then I think we found your issue.

Would love that were the truth...but sadly no.

On the previous instance, this occurred when I was controlling the mount via my iPhone, the ASIAIR app on standard EST.

andrea tasselli:
Check NINA log, if you were using NINA.

Just using the ASIAIR.  Its log is attached above.

Chris

Chris:
Just using the ASIAIR.  Its log is attached above.

Chris

I own and use 3 Asiairs, occasionally they do stupid quirky stuff like this because they are a $300 computer and they can act it.
Since yours is doing it continuously, it appears yours may just have gone bad..
I would go reset everything , all the settings back to scratch, do any updates you might have missed and try again.
Zwo makes cool affordable products but when things go bad (I have had to find local repair people to do fixes on 2 cameras I own)
You are out of luck, I don't think they have any kind of repair service.
I hope it is not a Mount issue, that could be a much harder fix.

ill take a punt on a usb cable issue leading to a driver crash or something. 

check non of your usb cables are under any pressure/tension and can work loose while meridian flipping.

Chris:

Brian Boyle:
Hi Chris

I had a similar problem about a month back - using NB filters.  Looking at the logs,  although the ASIAir detected 500 stars in the 2sec exposure, I suspect most were noise.  After increasing the integration time to 10sec, I had no further problems.   

I wish I could use NINA, but it is PC program.  And no, I am too old to use a windows emulator.  [More expense].   If you can't write a Mac version, I ain't buying.

I did post on the AISAir and some helpful folks provided me with a diagnosis - if not the solution.

CS Brian

Thank you Brian very helpful...that very well might be the cause.  Last night was a broadband filter but its worth a shot...so you increased exposure time of which setting exactly?

Hi Chris,

I think it is on the telescope menu, where you can set the exposure time for taking plate solving images 

CS Brian

Chris:
Failure happened again last night.  I set an alarm to wake up and catch it.  This is frustrating however...as last year I executed multiple plans (two targets, two diff meridian flips..no problems).

I increased the flip exposure time to 10s...still no dice.  Something clearly happened since I updated the ASIAIR software.  I think I'm going to try and reset the Air and start from scratch as @Dan Kearl suggested.

Will keep everyone posted.  

How does one use NINA again?  mini PC?  ugh...  Just thinking about the switch away from the Air causes heartburn...

If you try and go the NINA-PC route you will be glad you did.

Tony Gondola:

Chris:
Failure happened again last night.  I set an alarm to wake up and catch it.  This is frustrating however...as last year I executed multiple plans (two targets, two diff meridian flips..no problems).

I increased the flip exposure time to 10s...still no dice.  Something clearly happened since I updated the ASIAIR software.  I think I'm going to try and reset the Air and start from scratch as @Dan Kearl suggested.

Will keep everyone posted.  

How does one use NINA again?  mini PC?  ugh...  Just thinking about the switch away from the Air causes heartburn...

If you try and go the NINA-PC route you will be glad you did.

As far as I know, the Asiair uses NINA

Roy Hagen:

Tony Gondola:

Chris:
Failure happened again last night.  I set an alarm to wake up and catch it.  This is frustrating however...as last year I executed multiple plans (two targets, two diff meridian flips..no problems).

I increased the flip exposure time to 10s...still no dice.  Something clearly happened since I updated the ASIAIR software.  I think I'm going to try and reset the Air and start from scratch as @Dan Kearl suggested.

Will keep everyone posted.  

How does one use NINA again?  mini PC?  ugh...  Just thinking about the switch away from the Air causes heartburn...

If you try and go the NINA-PC route you will be glad you did.

As far as I know, the Asiair uses NINA

I don't believe so, the AIR is an Android application and is INDI based, more like an Astroberry.

I'm beginning to believe this is caused by belt slippage.  I contacted ZWO and performed their recommended belt tightening procedure.  I tested the Meridian flip indoors (obviously didn't plate solve) but it flipped multiple times…multiple different targets w/o issue or grinding.

I'm going to try it again on the next clear night and likely use heavy duty mode and possibly a small counterweight.  While not required…my FRA 500 with associated AP gear isn't necessarily light (still under AM5 limits though)…and a little counterweight can't hurt (in my mind) in trying to relieve stress on the gears etc.  Heck who knows…might improve guiding as well.

So…after trying it last night in Heavy Duty mode and with a counterweight, I had zero errors, a perfect Meridian flip and immediate solve after (used Autorun mode).

I'm getting more convinced this was a belt slippage issue.  I had very few subs lost throughout the whole night as well (usually lose a few to oblong stars etc).

Think the counterweight is key.  I know its not needed etc…but it definitely helped in my situation.