19 replies to this topic

[DForcier]

Seems that Zwo has responded for the Nyx-101 compatibility issue with the ASIAIR :

 

Walf@ZWO :

Let me explain, because of serial port of pegasus conflict with the mount, we didn't handle it well, this is a bug of ASIAIR, not intentional absolutely, we will fix it after Chinese new year!

Source : https://bbs.astronom...t-aa-firmware/5

[Panotaker]

The ASIAIR doesn’t work with the Software Bisque mounts either from what I have seen from other posters.

[ZWO Astronomy Cameras]

Hi everyone here,

 

This is ZWO. We would like to officially address the issue of poor connectivity with Pegasus Astro's mount.

 

We recently received user reports that he cannot control his mount when using Pegasus Power Box with the ASIAIR. We found that the Pegasus Power Box has one USB to serial port built-in and this caused confusion to the ASIAIR leading to communication failures to the mount.

 

Our initial bug fix solution to quickly resolve this was to filter out the Pegasus Power Box's serial port when there is a Pegasus serial device connected, while we devised a better long term fix. However, the unintended consequence of that quick fix was the disabling of communications with the new Pegasus mount. This was totally not our intention, nor is there any plan by ZWO to prevent Pegagus Astro mount being used with the ASIAIR. We are genuinely sorry for any inconvenience caused to affected users.

 

We are working to resolve this issue quickly and will intend to release a new version to solve this after Chinese New Year. (Our devs are now having their Chinese New Year holiday. Spring Festival is the most important festival of a year for Chinese people and we all need the holiday to stay with our families and friends.)

While some people might think this is a brand war. We'd like to seriously clarify that we have no willingness to do that. We are very aware that the astronomy community is a small and friendly environment, and we can not respect more the fair and impartial business environment where ZWO and other vendors can all get healthily developed.

 

Ever since the ASIAIR is released, ZWO remains fully committed to providing support to the user or vendor who uses various mounts with the ASIAIR. But we have to be honest - the time and energy we have are very limited, thus we more focus on the equipment we have already supported and try to provide a better and better user experience. The goal of ASIAIR is to make astrophotography easy and fun, it would never change.

 

Thank you all for reading this.

 

ZWO Team

[Shiny]

😆

Attached Thumbnails

• 

[Stephanh]

Hi everyone here,

This is ZWO. We would like to officially address the issue of poor connectivity with Pegasus Astro's mount.

We recently received user reports that he cannot control his mount when using Pegasus Power Box with the ASIAIR. We found that the Pegasus Power Box has one USB to serial port built-in and this caused confusion to the ASIAIR leading to communication failures to the mount.

Our initial bug fix solution to quickly resolve this was to filter out the Pegasus Power Box's serial port when there is a Pegasus serial device connected, while we devised a better long term fix. However, the unintended consequence of that quick fix was the disabling of communications with the new Pegasus mount. This was totally not our intention, nor is there any plan by ZWO to prevent Pegagus Astro mount being used with the ASIAIR. We are genuinely sorry for any inconvenience caused to affected users.

We are working to resolve this issue quickly and will intend to release a new version to solve this after Chinese New Year. (Our devs are now having their Chinese New Year holiday. Spring Festival is the most important festival of a year for Chinese people and we all need the holiday to stay with our families and friends.)
While some people might think this is a brand war. We'd like to seriously clarify that we have no willingness to do that. We are very aware that the astronomy community is a small and friendly environment, and we can not respect more the fair and impartial business environment where ZWO and other vendors can all get healthily developed.

Ever since the ASIAIR is released, ZWO remains fully committed to providing support to the user or vendor who uses various mounts with the ASIAIR. But we have to be honest - the time and energy we have are very limited, thus we more focus on the equipment we have already supported and try to provide a better and better user experience. The goal of ASIAIR is to make astrophotography easy and fun, it would never change.

Thank you all for reading this.

ZWO Team

Dear ZWO Team,

You wrote: ""We'd like to seriously clarify that we have no willingness to do that. We are very aware that the astronomy community is a small and friendly environment, and we can not respect more the fair and impartial business environment where ZWO and other vendors can all get healthily developed""

My question is: If that is the case, why are you restricting ASIAIR users to your own brand of focuser?

[wykbbb]

Chinese New Year 2023 falls on Sunday, January 22nd, 2023, and celebrations culminate with the Lantern Festival on February 5th, 2023. 

So, the way I see it …15 days of celebrations and festivities, then 15 days of needed recovery. My guess is No AsiAir usage with this mount until late February 

I thought Pegasus Astro already updated their firmware to fix the connection issue. Did that firmware update fix the issue?

 

There are multiple versions of ASIAir (ASIAir original, ASIAir Pro, ASIAir Plus, ASIAir Plus Rockchip, ASIAir Mini Rockchip). We don't know which version of ASIAir Pegasus Astro used when they tested the mount.  In theory, the mount might work with one version, but not the other versions.

 

If Pegasus Astro can't fix the issue, then you would need to  wait for the ZWO fix.  The ZWO devs go back to work after Chinese New Years. We don't know how long it will take to fix the issue or when the fix will be released.  ZWO could just release a software update  just for that Pegasus Astro fix, or that fix will be included with 2.1 release.  ZWO has not announced a release date for 2.1.

 

Plus the ZWO fix might not work. Even if ZWO  fixes the issue with the serial port for Pegasus Astro powerbox, there might be other problems connecting with the NYX-101 mount.  Some ASIAir users reported problems with Pegasus Astro powerbox and Pegasus Astro eqmod cables, so there is a history of connection issues between ASIAir and Pegasus Astro products.

 

For people who bought NYX-101 because Pegagus Astro claimed it was compatible with ASIAir, things might be buggy for a while until those two companies talk directly to each other.  

Edited by wykbbb, 18 January 2023 - 01:36 PM.

[900SL]

Dear ZWO Team,

You wrote: ""We'd like to seriously clarify that we have no willingness to do that. We are very aware that the astronomy community is a small and friendly environment, and we can not respect more the fair and impartial business environment where ZWO and other vendors can all get healthily developed""

My question is: If that is the case, why are you restricting ASIAIR users to your own brand of focuser?

I assume so they don't have to write code to accommodate every man jack component out there, or spent half their working hours dealing with ensuring compatibility

 

I do expect ASI Air Pro to address the Pegasus mount issue however. I've been a purchaser of ASI cameras and the AAPro for a while now, however I intend to buy the Pegasus at some point once the early mounts have proven their worth and I'll switch to a PC based set up and alternative cameras if they don't 

[MJB87]

Note to the community...

 

There were a series of posts that were off-topic in a post about the Pegasus Mount, but which nonetheless are important. So I have moved them here to a new topic.

 

Marty (moderator)

[ZL4PLM]

Dear ZWO Team,

You wrote: ""We'd like to seriously clarify that we have no willingness to do that. We are very aware that the astronomy community is a small and friendly environment, and we can not respect more the fair and impartial business environment where ZWO and other vendors can all get healthily developed""

My question is: If that is the case, why are you restricting ASIAIR users to your own brand of focuser?

because the platform design intentions by ZWO is to not be an open platform supporting every device on the market, the post mentions mounts.. not every other component. Its been a pretty clear intent from ZWO from day one of the ASIAIR. 

 

"Ever since the ASIAIR is released, ZWO remains fully committed to providing support to the user or vendor who uses various mounts with the ASIAIR. But we have to be honest - the time and energy we have are very limited, thus we more focus on the equipment we have already supported and try to provide a better and better user experience. The goal of ASIAIR is to make astrophotography easy and fun, it would never change"

[ZL4PLM]

I assume so they don't have to write code to accommodate every man jack component out there, or spent half their working hours dealing with ensuring compatibility

 

I do expect ASI Air Pro to address the Pegasus mount issue however. I've been a purchaser of ASI cameras and the AAPro for a while now, however I intend to buy the Pegasus at some point once the early mounts have proven their worth and I'll switch to a PC based set up and alternative cameras if they don't 

it will be resolved after Chinese NY  

[Cinnamon]

While it's easy to look for a deliberate act on ZWO's part, the two mounts are different in significant ways. The Pegasus is heavier and quite a bit more expensive than the AM5. To me, they are slightly different markets and deliberately crippling use of your product is almost always a fail in the end with the hit to your image. Now if it had the same weight capacity, similar price and weight, then it would be a head to head competitor.

[Mike Sandy]

I thought the nature of ASCOM as an interface for various equipment and OEMs was to put the burden of building a functional driver on the OEM.  OEM's should not have to adjust their software for every new product that hits the market - that was the issue that caused Bob Denny to champion ASCOM in the first place.  I can't say that I understand this issue all that well, but it seems like if ZWO's software is doing things outside the ASCOM Spec - they need to fix that.  To attach some nefarious plot to this issue is ridiculous.  The same is true for the Pegasus equipment - if their drivers don't work because they don't comply with the ASCOM standards, they need to fix it.

 

ASCOM has been, and continues to be, one of the most important developments for amateur astrophotography I can think of.  With the amount of automation we all use today, can you imagine the nightmare of mixing the proprietatary software for every piece of hardware (focusers, filterwheels, mounts, cameras) and controll software in your system.  

 

This issue will get worked out - it really is not a unique situation,  It is a normal part of a new product development.  Probably could have been avoided with another six months of interoperability testing - but then everyone would have burned the internet down with folks screaming for their mounts. We tend to be a very demanding and judgemental group as we sit behind our keyboards and cast stones toward those folks trying to build things that we love to own 

[James Peirce]

My question is: If that is the case, why are you restricting ASIAIR users to your own brand of focuser?

Just want to note that there is a *massive* difference between 1) restricting the AAP product to ZWO products in some select product classes (cameras, focusers, electronic filter wheels), and 2) backpedaling in support for mounts now that the AM5 exists. The later would be a bait-and-switch on the product and phenomenally dishonest to existing customers, and this is the issue that was originally implied and to which ZWO has responded above.

 

It doesn’t seem productive or sincere to conflate the two.

[Cinnamon]

I thought the nature of ASCOM as an interface for various equipment and OEMs was to put the burden of building a functional driver on the OEM.  OEM's should not have to adjust their software for every new product that hits the market - that was the issue that caused Bob Denny to champion ASCOM in the first place.  I can't say that I understand this issue all that well, but it seems like if ZWO's software is doing things outside the ASCOM Spec - they need to fix that.  To attach some nefarious plot to this issue is ridiculous.  The same is true for the Pegasus equipment - if their drivers don't work because they don't comply with the ASCOM standards, they need to fix it.

 

ASCOM has been, and continues to be, one of the most important developments for amateur astrophotography I can think of.  With the amount of automation we all use today, can you imagine the nightmare of mixing the proprietatary software for every piece of hardware (focusers, filterwheels, mounts, cameras) and controll software in your system.  

 

This issue will get worked out - it really is not a unique situation,  It is a normal part of a new product development.  Probably could have been avoided with another six months of interoperability testing - but then everyone would have burned the internet down with folks screaming for their mounts. We tend to be a very demanding and judgemental group as we sit behind our keyboards and cast stones toward those folks trying to build things that we love to own 

In my experience, glitches and things not working as they should is par for the course. lol I have a glitch in sequence generator pro and NINA that I am trying to resolve, but one clear night in 8 weeks is not conducive to trouble shooting! lol

[Mike Sandy]

In my experience, glitches and things not working as they should is par for the course. lol I have a glitch in sequence generator pro and NINA that I am trying to resolve

I remember back in the early 2000's timeframe - automation required a hodgepodge of software and hardware.  Seems like every software update broke something, and every piece you used was a pay to play deal.  I'm feeling pretty old today as I repeat what my grandfather always used to tell me: "you don't know how good you have it these days". 

 

 but one clear night in 8 weeks is not conducive to trouble shooting! lol

I feel your pain - although less of an issue than you've had!  The atmospheric river (pineapple express, darn lot of rain, whatever you want to call it) has wiped out at least the past three weeks for me. 

Edited by Mike Sandy, 19 January 2023 - 01:36 PM.

[rloftin]

ASIAIR Plus working with NYX-101 but......

These steps worked for me after spending days pushing buttons and keys, ouch. I use Android so expect iOS to be different but similar.

- Uninstall ASIAIR app, if you have 2.0 or greater, if not skip upgrade and keep version 1.91 (the easy way), otherwise...

- Search the internet for the version 1.91 APK and download it, there are multiple sources

- Go through the hoops of installing the 1.91 APK, again reference the internet for how to do this. It requires you to allow special permissions to install.

- Open ASIAIR app, do not upgrade to 2. anything (skip), and select your equipment. In Mounts select 'Meade LX200 Classic'. Complete initial setup.

- Tap About, the "!" icon and choose Reset Firmware, Reset to 8.33, this is quick.

- restart ASIAIR app and download data, no choice. This took several app restarts and one clear cache but eventually completed, then it unpacks. Wait for it.

- restart ASIAIR app. It will force an upgrade to firmware version 9.97, do it, this is also quick.

- restart ASIAIR app and download data, no choice. This also took several app restarts and one clear cache but eventually completed, then it unpacks. Wait for it. 

- restart ASIAIR app DO NOT upgrade to 2.anything, SKIP if suggested.

- Verify in main settings pop-out your equipment is correct

- Now the fun part, with your NYX-101 turned on and both USB 2 ports connected, hopefully on the telescope icon (mount) page 'Serial' will have 'Connected' displayed,

- If not unplug the USB cable and try again. It took several tries for me but eventually 'Connected' was displayed. Nothing can happen if it is not 'Connected.

- Meade LX200 Classic should already be entered, if not scroll to and select it AND now set Baud to 115200. It didn't work at any other rate for me.

- Now I believe you can use your ASIAIR as expected. It works in my living room, hope it keeps working and with the Lantern Festival (Feb 6) over, ZWO may address this formally. They just released 2.1 yesterday but no mention of NYX-101 issues fixed, Do not know anything about 2.1... maybe. Not going there yet. 

 

It does work. Nowhere as easy as setting my CEM60 is. Looking at the mounts listed it appears ZWO is setting themselves above everyone else. I believe 'Z' is not the first letter of the alphabet, but I am sure that is a silly standard to observe.   Hope this gets worked out, I like both products.

[Nikolas234]

ASIAIR Plus working with NYX-101 but......

These steps worked for me after spending days pushing buttons and keys, ouch. I use Android so expect iOS to be different but similar.

- Uninstall ASIAIR app, if you have 2.0 or greater, if not skip upgrade and keep version 1.91 (the easy way), otherwise...

- Search the internet for the version 1.91 APK and download it, there are multiple sources

- Go through the hoops of installing the 1.91 APK, again reference the internet for how to do this. It requires you to allow special permissions to install.

- Open ASIAIR app, do not upgrade to 2. anything (skip), and select your equipment. In Mounts select 'Meade LX200 Classic'. Complete initial setup.

- Tap About, the "!" icon and choose Reset Firmware, Reset to 8.33, this is quick.

- restart ASIAIR app and download data, no choice. This took several app restarts and one clear cache but eventually completed, then it unpacks. Wait for it.

- restart ASIAIR app. It will force an upgrade to firmware version 9.97, do it, this is also quick.

- restart ASIAIR app and download data, no choice. This also took several app restarts and one clear cache but eventually completed, then it unpacks. Wait for it. 

- restart ASIAIR app DO NOT upgrade to 2.anything, SKIP if suggested.

- Verify in main settings pop-out your equipment is correct

- Now the fun part, with your NYX-101 turned on and both USB 2 ports connected, hopefully on the telescope icon (mount) page 'Serial' will have 'Connected' displayed,

- If not unplug the USB cable and try again. It took several tries for me but eventually 'Connected' was displayed. Nothing can happen if it is not 'Connected.

- Meade LX200 Classic should already be entered, if not scroll to and select it AND now set Baud to 115200. It didn't work at any other rate for me.

- Now I believe you can use your ASIAIR as expected. It works in my living room, hope it keeps working and with the Lantern Festival (Feb 6) over, ZWO may address this formally. They just released 2.1 yesterday but no mention of NYX-101 issues fixed, Do not know anything about 2.1... maybe. Not going there yet. 

 

It does work. Nowhere as easy as setting my CEM60 is. Looking at the mounts listed it appears ZWO is setting themselves above everyone else. I believe 'Z' is not the first letter of the alphabet, but I am sure that is a silly standard to observe.   Hope this gets worked out, I like both products.

They released 2.1 yesterday ? Where did you see that? One of the Beta tester stated that they did fix the NYX101 to work with ASIAIR...

[rloftin]

On the ZWO website, beta version. Happy to make it work without being a beta tester. Will look into it later. Had a hard enough time making it work as above. If it works in the 2.1 beta great!!!

[Pawan]

Can someone confirm if the latest version of ASIAIR now supports NYX?

 

Thanks

[G45]

Can someone confirm if the latest version of ASIAIR now supports NYX?

 

Thanks

For my experience, NYX-101 sadly is not in the list of supported mounts on the latest update.

However, It does works pretty good for me once I managed to actually connect it :-) 
The issue is that it will work perfectly with onStep Electronics on Baud 115200, but, not quite directly at for the initial setup. 

If you try to connect the mount via onStep Electronics, you will get an error saying that the mount cannot be connected, what I found weirdly enough, is that when I first connect to 'HOBYM crux Series' with the same baud value, NYX-101 will be connected immediately, however, the mount will not move on command, then I disconnect the HOBYM crux, and connect to 'onStep Electronic' and everything then will work perfectly. 

I did try other combinations, and what I described above, simply works for me. 

I have not had long sessions with ASIAir, maybe an hour here and 30 min there, but, as I said, it worked without any issues including guiding.