Vixen SkySensor2000 PC

crackout

Hi,

I'm trying to get my ancient Vixen SkySensor2000 PC to work with the ASIAIR Pro.

I finally managed to connect it via the SS2K profile (you have to set the SS2K to LX200 mode in telescope settings....).

Manual slewing works on max speed (only).

However, any GoTo command is not working.
Is there a fix?

crackout

Seems like I‘m not alone:

https://bbs.astronomy-imaging-camera.com/d/11792-vixen-skysensor-2000pc

This seems to be a bug.

i can GoTo using SkySafari6 Plus over the ASIAIR without a problem. Only the direct GoTo command in the ASIAIR App does not work.

Please fix this!

PMTeam@ZWO

It may be a bug of indi, upload the log.

crackout

@asiair@zwo

Hi, thanks for your notice.
I uploaded the logs using the feedback form in the app.

RobinHS

Don’t know if you’ve already resolved this or gotten a reply, but just wanted to let you know ASIAir Plus is compatible with Vixen SkySensor 2000 if you have upgraded the EEPROM to version 2.10. GoTo and other functions to control my GP mount are working fine. Also works with SkySafari GoTo commands.

crackout

RobinHS Yes, I upgraded the EEPROM to 2.10 and it works fine. I use an EQ6-R though in the meantime.
Thanks for your post, should help others as well.

elviejo

I have a SS2K (EPROM v2.10) controlled Atlux mount which in October 2021 worked flawlessly with the ASIAir Pro running iPad app version 1.7 and firmware version 8.43 (I think). The November iPad app update to v1.8 and accompanying firmware update saw this change with the loss off guiding calibration and misreporting of observer latitude and longitude to the SS2K handset. I have spent the last 6 months trying to isolate the problem and can confidently state the following.

Having SS2K eprom version 2.10 does not eliminate problems between the SS2K or the FS2 controller and ASIAir Pro. It does however allow the ASIAIR Pro to be used to its maximum.
Every app update (both iPad and android) since v1.8 causes the same problems for the SS2K and probably the FS2 controller.
The primary problem is that the ASIAir Pro does not issue guiding pulses in a manner recognised by the SS2K. I repeat, the loss of guiding calibration IS NOT due to cables, ports, or any other physical connection problem. It is solely a code-based communication problem related to the INDI driver utilised by the ASIAIR Pro unit.
My final solution was to purchase a Samsung Android tablet and download the android app v1.7 onto it and then disable Google play auto updates in order to prevent any change to the app version. I then reloaded the original ASIAir firmware version supplied with it from the backup version created when I first received the ASIAir Pro unit. This then updates the firmware appropriately on first use of the ASIAir Pro. I now only use the ASIAir with this android tablet and have all of the functions of v1.7 operating correctly, most importantly the guiding calibration which make the ASIAir useable.
Note that, in my experience, the only ASIAir function that has been affected since the introduction of app v1.8 is the guiding calibration. Slewing, go to, centering, etc, remained unaffected.
Note also that if you accidentally activate the ASIAir app using an iPad then you cause an automatic update that will change the app and firmware versions installed on the ASIAir Pro and will have to reload a new version of the original firmware onto it before the android v1.7 can used used again.
Hopefully, our friends at ZWO will examine the ASIAir-SS2K miscommunication problem and institute the necessary changes before the next app update in order to raise it back from the expensive polar alignment tool it is currently,to the valuable Astro imaging tool it was prior to v1.8.
I would venture to suggest that any RS232-connected hand controller using 9600baud and the original LX command set or a subset of this will probably be affected similarly and perhaps even more so depending on the individual commands instituted into it.
I hope this helps those users of SS2K handsets and stops them thinking that they are no longer useable with you ASIAir. I can assure they are but it involves additional cost and a bit of messing around with the app version.