Chen - thanks for the quick response. Checked the location services on the iPad - no joy - was set to Always.


Yes, agree, with plate solving, SkySafari is a complement to the setup but not needed. Like the idea of two iPads (have one old and one new, so this is an option). Use the SkySafari to plan my viewing and to record what I've seen - new hobby and want to see or image the 100 Messier objects in my remaining life.


Great catch on the wrap around for the Longitude value - should have been obvious. Wonder why there's a calculation for Long when this value is likely stored in the HC? But alas, will leave those questions to the application programmers.


Still strange that the Mount Info isn't displayed unless I completely close (shutdown) the app, and merely restart it.


I have one question about the ASIair updates - are the firmware and app updates all handled through the application or do I need to go to a web site to download (recall first launching the app there were some updates but didn't watch carefully what was updating).


For any beta testing, how do you get on the list to be a tester - could devote on iPad to this endeavor.


Jim

Hi Jim,


> I have one question about the ASIair updates - are the firmware and app updates all handled through the application or do I need

> to go to a web site to download (recall first launching the app there were some updates but didn't watch carefully what was updating).


The ASIAIR firmware (in the Raspberry Pi SD card) is a payload that is contained in the ASIAIR app.


When you launch a new ASIAIR app, it apparently checks if the ASIAIR firmware is in sync. If not, it will ask you if you would like to push the firmware to the Raspberry Pi.


There is no need to track the firmware versions yourself. The ASIAIR app will do it for you.


Be sure that you have a good WiFi connection before you tell the ASIAIR app to go ahead and update the firmware, and make sure both ASIAIR (if it is on battery) and iPad have good battery levels. If you lose WiFi connection while updating the firmware, you might corrupt the SD card and need to flash a fresh copy.


It usually takes less than 2 minutes for firmware update to complete on 5 GHz WiFi, but don't trust the progress bar in the ASIAIR app; I have never seen that to be accurate between my two iPad pros and an iPod touch :-).


Also, if you are on iOS, you may want to wait a week or two after a new ASIAIR app is released before installing it. Check the ASIAIR Facebook page in the meantime for reports on your specific mount still works. ZWO camera and EAF seem OK, but third party stuff like mounts and DSLR cameras seem to go through very little regression testing.


The problem with iOS is that after you download a new non-working version, you cannot go back to an older working version. With Android, you can revert back to an older APK file (and flashing older firmware), but with iOS, there is no going back. My RainbowAstro mount was rendered useless with ASIAIR between v1.2 and v1.3). I wish ZWO could establish two different apps (one app called ASIAIR Backup or something), so that you can still run the older version of the app.


Since you mentioned that you have two iPads, you can use one iPad as the guinea pig for new software releases. If a new version stops working, go back to an older archived SD card image and the older working app on the "other" iPad.


Chen

>> For any beta testing, how do you get on the list to be a tester - could devote on iPad to this endeavor.


Hi Jim,


The first thing you need to do is download a copy of Apple's TestFlight app on iOS (that is how iOS betas are pushed out).


Then use this web page on Safari to join the beta test (no further invitation needed from ZWO):


https://testflight.apple.com/join/6uEyoSl3


Just remember to remove the copy of the beta app the next time you want to download a released app.


If you have TestFlight notifications turned on, you will be notified when there is a new TestFlight version of ASIAIR.


Chen

2 years later

I have same problem with AVX mount. After I enter the asiair app I see that asiair has acquired the wrong coordinates for the phone. I then enter the correct coordinates again, and connect the mount, at which point the phone corrdinates jump back to the incorrect values (the mount coordinates are correct). I then have to quit the app (actually, force stop it) and then re-enter the correct phone coordinates, at which point I reconnect to the mount, and see the phone coordinates have reverted to the incorrect values again. Unfortunately there's no way to enter the correct phone coordinates once i'm connected to the mount. If I then use the app, most objects are reported to be below the horizon. I have to go through this cycle several times and eventually the phone coordinates remain correct. The app has permission to use the phone coordinates, and they are correct. I've no idea where the app gets the incorrect phone coordinates from. It seems to be crucial to make sure the app is closed, and asiair itself off, then switch on asiair and then after 30 seconds, launch the app.

I have the same issue with my Rainbow Astro RST-135. I end up with a wild longitude number such as 488E while I am 110W. I cannot continue when that happens. And it might initially pick up the correct numbers but somewhere along the line it gets changed. I hope they fix this because I basically have to start over when that happens as GoTos no longer work. Also "Sync to mount" does nothing. I press the button and it says completed, but no change is made.

JohnD

  • w7ay replied to this.

    johnpd I have the same issue with my Rainbow Astro RST-135.

    Turn off the GPS radio in the RainbowAstro hand controller. Even better, don't even plug in the Hubo-i when you use ASIAIR. You don't need the hand controller when using ASIAIR.

    Chen

      OK Chen,

      I first did a {Home} using the hand controller. Then unplugged the HC and restarted the mount. I am still getting Longitude E 488.04.59, Latitude S 00.00.00. "Sync to Mount" has no effect.

      JohnD

      • w7ay replied to this.

        johnpd Then unplugged the HC and restarted the mount. I am still getting Longitude E 488.04.59, Latitude S 00.00.00. "Sync to Mount" has no effect.

        Are you using iOS or iPadOS? And if so, did you give the ASIAIR app permision to access Location Services in the Apple OS?

        Chen

          I am using an iPad Mini 5 with iPadOS v14.7.1. I have the Location option for ASIAIR set to "While Using". I also have "Local Network" set as "On" and "Cellular Data" set as "On".

          JohnD

          • w7ay replied to this.

            I have been using ASIAIR with two different RST-135 (I keep one mount as a spare, and for performing indoor experiments) and have not seen the problem that you are witnessing. I use three different iPad pros and an ancient iPod touch which can only get its location through the home network, and they all work.

            Be sure to only connect the ASIAIR to the mount's USB port, keep the handcontroller completely disconnected when you power up the mount. Don't even take it outdoors until you have the location problem diagnosed.

            If the problem persists, perhaps the ASIAIR app preferences has remembered some old bad coordinates. The only way I know of getting rid of it is to expunge ASIAIR app completely from the iPad; reboot the iPad, and download a fresh copy of the app from the App Store.

            Also, when you first launch ASIAIR, you will see a setup page. See if you can the wrong coordinates are also there, and if so, manually change it.

            ASIAIR first implemented RST-135 protocols in v1.2, but it was incomplete. They added slew and pulse guiding in v1.3, but the app would crash if you try to do anything to the RainbowAstro mount. At that point, they asked for a loaner RST-150h from Korea (which as far as I know, is still in Suzhou). The RST-135 became fully functional from v1.4 onwards, and we are at v1.7 now.

              I have to set up every time. How do I get a proper {Home} position without the hand controller? According to the documentation that is available for the ASIAIR, you need to have the {Home} position of the mount set before you connect it to the ASIAIR. The ASIAIR uses this initial position as the mount's {Home} position when the ASIAIR boots up. I have attached screen captures of the initial ASIAIR screen and the Telescope mount screen. No hand controller was connected when I did this.

              JohnD


              • w7ay replied to this.

                johnpd How do I get a proper {Home} position without the hand controller?

                Have you scrolled down the Telescope Setup window? There is a menu item named "GoTo Home Position." Click Start and then Confirm again. It sends a protocol command that does exactly what the handcontroller long-press-zero does.

                Keep scrolling past the Guiding Rate menu that you showed in the screen capture. Almost every window in ASIAIR taller than the tablet window (and especially a smart phone window). The tracking on/off switch is also below that Guiding Rate menu.

                Chen

                  Using the HC I tried changing the Location in the secondary screen off the main screen. I was able to enter the same numbers as appeared on my iPad. When I checked what the ASIAIR picked up, it was weird. It picked up the Longitude (except the seconds was "20" instead of "22") and Latitude was still "S 00.00.00". If I do a "Sync to mount", the Longitude reverts back to the E 488...
                  I finally got a GPS signal and checked the ASIAIR again. It had the correct Longitude, again except for the last digit, but Latitude remains all zeros. I tried the USB cable that came with the RST-135, no difference. With another attempt, the Longitude shows in the HC Location as "E 489.55.00". There is something royally screwed up here.

                  JohnD

                  • w7ay replied to this.

                    The {Home} in the ASIAIR does work.

                    JohnD

                    • w7ay replied to this.

                      As a sanity check, make sure the mount is receiving clean power between 12V and 15V (preferably near the high end of the range).

                      Be sure to disconnect everything from ASIAIR, including USB hubs, and have only the mount plugged directly into the USB 2 connector of the Raspberry Pi (one of the two USB connectors with the black plastic insert instead of the blue plastic insert, just in case (since RST-135 is a USB 2 device). Do not go through any USB hub. Use the USB cable that came with the mount (in the accessory box).

                      Do not connect any third party apps such as SkySafari to the ASIAIR proxies.

                      If that still fails, check with ASCOM on a Windows computer to see if you can control the mount properly.

                      If ASCOM also has a problem, you could have a defective mount. Contact your distributor and they should be able to get an RMA for you to ship the unit to RainbowRobotics (parent company of RainbowAstro) at their UNLV lab (Las Vegas). They usually promise a three week turnaround.

                      You can also try reloading the firmware:

                      http://www.rainbowastro.com/2020/03/08/how-to-update-the-firmware-for-rst-mounts-2/

                      Chen

                        Yes, in Equatorial mode (when you have the Hubo-i connected, you should see Equatorial Mode in the main display of the hand controller), the mount would first seek the index mark (even if it is already homed) and then home to the West Horizon. Be sure not to home from the communication port if the mount is ever pointed below the horizon; it has a potential of wrapping your cables around due to loss of the pier side.

                        Chen

                          I am using a Jackery 240 Power Station to power things inside. If I power the mount directly from this, it gets 13.3v. Going through the ASIAIR for power it gets 12.8v. Outside I might use a Pyramid Power Supply which usually gives me 13.8v as I recall.
                          Right now I just have the mount attached to the ASIAIR with the supplied USB and power cables. No camera or other device is attached. I am not using any hub. I am able to control the mount with SkySafari and Luminos apps on my iPad Mini through WiFi. The last time I was out and I got the mount and ASIAIR to sync, I was able to take a couple of hours worth of images. The plate solving was fantastic. The ASIAIR is a great product once it is working properly. I will take a look at ASCOM and load the latest firmware. I think Stellarium can now connect via ASCOM without any secondary software.

                          JohnD

                          • w7ay replied to this.

                            johnpd Right now I just have the mount attached to the ASIAIR with the supplied USB and power cables.

                            Just make sure power goes directly from the power supply to the mount and not through the ASIAIR's power ports.

                            Chen

                                w7ay Chen,
                                This would require me to have a splitter on the battery or power supply and two power cables. I had hoped to limit the number of cables coming up from the ground.

                                JohnD

                                  I found the problem. I had the Protocol set at "LX 200". When I changed it to "Rainbow Astro", everything kicked in. I don't recall seeing this on the Rainbow Astro site referring to the ASIAIR, but when I looked under the ASCOM FAQ as I was playing with that to get a connection, I thought I would see if that would work with the ASIAIR, and it did. So I am good to go.

                                  Thanks for your help. You are a godsend to this site.

                                  JohnD