Astro A50 Gen 3 Firmware Download

[Gerald Weiß]

ZWOplease give us an option to bypass firmware updates. I was at a public star party Wednesday evening. I started the ASIAIR and the first thing that popped up was a firmware which I had no way of bypassing. If that messed up my ASIAIR I would have been SOL. PLEASE GIVE US THE OPTION TO TEMPORARILY BYPASS FIRMWARE UPDATES UNTIL A MORE CONVENIENT TIME.

johnpd Firmware updates are triggered by updates of the app on your mobile device. Make sure that you do not update the app until a more convenient moment OR make sure to update the firmware of the ASIAir as soon as you update the app.

I had not knowingly updated it. I looked at what was recently updated and saw that the ASIAIR app along with several other apps had been updated a few days ago. I was unaware that was happening. I checked the settings for the App Store. Automatic downloads was unchecked. The only thing that was set was to automatically download "new" purchases from other devices. Since I also have another iPad, that statement is apparently being interpreted as "new" purchase also means updates. I have now shut that off and will only update the ASIAIR app when I feel safe to do so.

I would like the ability to bypass as well when loading the app. It's not convenient to go into the android setting and turn the update feature on and off and once updated there does not appear to be a simple path back to the older version.

For me too, the last update of the firmware of the Seestar (1.6.1) stops the application and the firmware's update fails. From now, I can't use my Seestar. I sent a bug report to ZWO and I am waiting for a solving.

My phone is still running Android 13 however, so I decided to connect it to the Seestar and see if the firmware update would succeed. I'm happy to report that it did! When I reconnected to the tablet, everything was normal and the latest firmware - v2.42 - was shown.

If you're having similar issues, check the Android version of your device. If it's Android 14 that's probably the reason. Hopefully ZWO will be able to find and implement a solution before the next update.

Me, in Japan, too.

After update Seestar software , fail to update firmware.

I don't use Station Mode.

Select 5GHz, failed.

uninstall and re-install Seestar software, failed.

Now I cann't use Seestar.

The fact that the firmware update is mandatory is really not satisfactory, at the begining it is not required, once a lot of device are updated without any issue, you can force it, but not on the first day, please.

I tried using the firmware option from the menu as well but it all ends up the same ... the progress screen pops up sits at 0% for a bit then the app reverts to the home screen, after a few seconds the Update Firmware popup shows and the whole things starts again.

It seems to be a specifically Android related issue. I'm too scared to update right now, but I use iPhone. I wonder if any of you guys with this problem would have the option to update the FW on your Seestars with an Apple device? Maybe that would get you over the line and imaging again...

La nouvelle version de l'application SeeSTAR 1.16.1 lance le tlchargement de la nouvelle version du firmware et provoque l'arrt de l'application rendant l'utilisation du tlescope impossible avec les appareils qui ont une application jour.

[unknown] La nouvelle version de l'application SeeSTAR 1.16.1 lance le tlchargement de la nouvelle version du firmware et provoque l'arrt de l'application rendant l'utilisation du tlescope impossible avec les appareils qui ont une application jour.

English translation for those interested: The new version of the SeeSTAR application 1.16.1 starts downloading the new firmware version and causes the application to stop making use of the telescope impossible with devices that have an up-to-date application.

Astro Fi scopes are sold without a hand control requiring the owner to use either the SkyPortal and SkySafari app on their smartphone or tablet to run the scope. But, the Astro Fi mount can work with an optionally purchased NexStar+ or StarSense hand control. Readthis for step by step instructions on upgrading the hand control firmware.

Celestron has posted an official page detailing all firmware versions for the hand control and motor control:

-update-history

Check back periodically for updates or click the link to sign up for notifications.

Date Released: February 15, 2023

Subject: Required Astro Firmware Update

Effectivity: Effective immediately

Required Action: Update all Astro aircraft to firmware v1.1.18 to unground aircraft and resume flight operations

Affected Part Numbers:

SB005 grounded the Astro fleet due to an unknown issue that resulted in a customer crash. The root cause of the customer crash has been determined, fixes implemented in new firmware, and firmware testing completed and passed. The crash root cause was identified to be an electrical hardware failure (onboard SD card system) which exposed software bugs that eventually caused the Astro flight controller to lock up in flight and lose control of the aircraft.

Firmware version v1.1.14 and all previous firmware versions are permanently grounded. It is believed that all previous Astro firmware versions are affected. Astro vehicles can safely resume Astro flight operations only if they have updated their aircraft to v1.1.18 or later.

right out of the box there was some frustration getting the astrolab connect android app to properly sync with the device. probably attempted 3 or 4 times before i was able to successfully sync, even though the keyboard and the app were both clearly connected to my wifi. anyway, finally worked after connecting to the computer and updating the astrolab firmware, so maybe not technically a bug, but the remediation process could have been a bit smoother or maybe i could have updated the firmware directly from the astrolab itself which did have a working wifi connection. either way, a frustrating start to my experience with the keyboard.

at some point during the first day of use, I realized certain presets were no longer producing audio. i initially thought it was a connection problem on my end, but most presets still worked, only a few (certain organs like the Jazz B3) would not make any sound at all. i followed troubleshooting steps and performed a reset of factory prefs which did in fact restore sound on these presets and thankfully did not lose the handful of likes and custom user presets i had already created, but no idea what caused this problem in the first place and whether it may happen again at some inconvenient time.

had some issues getting a sustain pedal working. the korg damper pedal DS-1H would not work properly even after going into settings and updating the polarity. switched out for another brand of pedal and was able to get it working, but not sure why that pedal which works with several other keyboards i own would not work with the astrolab.

adding confusion to my sustain pedal issues, it seems that the arp hold function is tightly bound to the sustain on message from the pedal. stepping on the sustain pedal while playing an arp with hold activated will toggle the hold setting to off. requiring you to go back into the shift menu to reactivate hold. i am contrasting this with the behavior on my novation midi controller where latching the arp is not synonymous with holding down the sustain pedal. (stepping on sustain while a latched arp is playing simply lets each individual note played by the arp ring out until the pedal is released, arp remains latched). it would be nice if the relationship between the sustain pedal and the arp hold were clarified a bit, perhaps with some user options as to how it should behave.

In the end I had to follow instructions from another user which involved editing files in order to get it to update. NI have said it was a problem at Microsoft which has since been fixed with an update.

Sadly I think these things will happen more and more as basically they are a pc in a case with a keyboard attached and something we would think of as simple, like plugging in a pedal, becomes a real pain. Especially for early users.

Adding to the bugs, I am pretty sure that the MIDI implementation on Astrolab is far from perfect. I have posted about this a couple of times on the sound explorer forum but this looks like where I should have posted originally, I am new here, apologies.

The system does not allow very high level debugging (like stepping through code with a debugger). The firmware does have a number of logging output flags to aid you in determining what the mount is doing. But, and it's a big but, this logging is output on the serial port and thus breaks the Meade protocol (since instead of the command response that an app might be expecting, it gets debug spew).

This means that realistically, the only way to debug something is to connect the OAT to a monitor (terminal) and issue Meade commands manually. The Arduino IDE actually has a pretty easy to use and reliable monitor, you just hit CTRL+SHIFT+M and it will open a window that you can use to issue commands and see the logging output. You do have to configure the port and board before opening it, though.

The debugging is controlled in the firmware through a compile-time flag (so that the large number of debug strings and the formatting calls are not in the release/non-debug build) called DEBUG_LEVEL and it is defined in your local configuration file (the config generator puts it at the bottom). By default, it is set to DEBUG_NONE, which means no logging will be created and apps can use the OAT via the Meade protocol.

Now, autonomous Astro missions have more reliable and accurate messaging during system checks. If you experience a blocker on system checks, the Flight app will present a detailed message of the issue at the bottom of the checklist.

This release has been optimized with Freefly's upcoming 1.5.x firmware architecture in mind. While it's always recommended to consult the Matrix of Supported Drones, Cameras, and Lenses before any firmware update decisions, in our testing, the 1.5.x generation of Astro firmware addresses many issues in the 1.4.x generations for Freefly's Astro firmware.

3a8082e126