Longitude bug ruined mount: Page 2

Longitude bug ruined mount

Sam@ZWO

Photon08 we will check, did you upload log? can you tell us your upload email?

Sam@ZWO

@Photon08 this bug should be fixed from 1.8.1, which version did you test?
you need to use sync scan beta instead of syncscan

katzinaz

I am experiencing the same issue. I have a CGEM II mount. Running 1.83 firmware 9.1.2. I set the mount type to Celestron AVX/CGEM. It will come up initially with longitude of W111:28:05, or sometimes, and I don't know why it is different sometimes, it will say E248"31"55. These are what the ASIAIR software reads from the mount. The Longitude from the phone (via the software) is correct at W111:28:05. As soon as I slew to an object, the longitude will change to E and the scope will be pointing as if I was in the E hemisphere. For example, I can do a GoTo, and longitude would be E111:28:05 instead of W. I ran some tests yesterday and uploaded those logs, but of course it seemed to be slewing in the right direction then. As soon as the rain clears, I will test again and upload more logs.

If I set the mount to Sync scan beta, then it will initially read the longitude correctly as W111:28:05. However, once a GoTo command is issued, longitude switches to E111:28:05.

Tech@ZWO

katzinaz Hi Our devs got this problem with CGEM and will fix it in the next version.

Photon08

Sam@ZWO#54334 I uploaded the log when I reported the bug for the first time, but I haven't uploaded the log 11 days ago. I use the iPad version of ASIAIR app and it's 1.8.3 (9.1.2).

katzinaz

@tech@zwo#54551 I look forward to trying it out.

Photon08

@Sam@ZWO#54334 I tried once more yesterday and uploaded the log. Hope your team can find out what's going on and fix.

Tech@ZWO

Photon08 Could you tell us your email address so that we can locate your log, and which options did you choose to connect the mount? please try syscan beta (not synscan)

Photon08

My feedback includes the URL to this thread (https://bbs.astronomy-imaging-camera.com/d/10397-longitude-bug-ruined-mount/20 ) at the very beginning so that it'd be easy to find it. (search for "10397-longitude-bug"). I'll try 'Synscan beta' and let you know what happens.

Photon08

@tech@zwo#54617 Thank you for your suggestion about synscan beta. I tried it last night and Synscan Beta does not have this issue.

katzinaz

@tech@zwo#54551 Do you have an eta on the next version? Or when a beta might be available to test?

wvreeven

katzinaz See https://bbs.astronomy-imaging-camera.com/d/14081-asiair-v19-is-out-for-public-testing/

Dspital

w7ay has this ever been sorted out?
I’m pretty sure that my Celestron CG-5 Meridian flip issues are being caused by Asiair sending faulty goto coordinates.

w7ay

Dspital has this ever been sorted out?

I don't think so. I suspect that ZWO has focused their people to other bigger emergencies that affect their bottom line more.

It is probably time that you move on to something other than an ASIAIR too. There are many other good solutions out there to control your astrophotography instruments, created by people who actually understand what they are doing.

You can probably use a USB Protocol analyzer in between the ASIAIR and your mount to see what data it is trying to pass. I had written one such program many years ago for MacOS X:

https://www.w7ay.net/site/Applications/Serial%20Tools/

Today, you can also use WireShark to sniff the USB ports, and see traffic that is passing between USB devices.

The problem is that even if you spoonfeed the bug fix to ZWO, they will still not fix it. Ask me how I know.

Chen

Tech@ZWO

Dspital We are so sorry for the delay and trouble.I will follow the ASIAIR section of the forum from now on.
And i have replied to you in the other post, i will check it asap once i get the Bug report ID.
Thank you for your patience.

Dspital

I hear you.
Thanks

Dspital

Have you checked this issue yet?

Tech@ZWO

Dspital What is the bug ID of your log? i need that to locate your problem, thanks.

Dspital

Tech@ZWO
Bug I’d: 0003198
Submitted meridian flip issue.
Was advised to install a Remote Desktop program
on my Windows machine so the Tech could try to solve the issue. I responded, installed the remote set up, notified the Tech that my Asiair was available to him. But the Tech never responded after that, disappeared, ghosted me. Support is not happening, it’s hard to imagine a worse support system. Long standing issues ignored.

Dspital

Going around in circles!
Bug I’d: 003191, 003197, 003056
Reported multiple times

« Previous Page