ASIAir + ASIStudio

jpoveda

I might be wrong, but reading around on this forum, other online forums, and through my own experimentation, I'm coming to the conclusion that ASIStudio does not work with ASIAir. They are considered two different platforms. This is unfortunate for ZWO, but maybe not so for me.

As a result of this, I'm now finding myself learning new software to interact with the cameras via my laptop that do not involve ZWO. This is opening me up to new possibilities... and new hardware that is not ZWO.

ZWO has a good thing going with its tightly integrated eco-system. I'd suggest one of two paths forward to help keep your customers committed to a pure ZWO eco-system:

1) fully integrate ASIAir + ASIStudio so that I can simply join the same network as the ASIAir and ASIStudio will then have access to all the cameras, EAF, etc. OR

2) ensure ASIAir's software is so feature rich that customers don't find themselves looking at other alternatives to the ASIAir software. Since I'm on a Mac, I can use ASIAir either on my laptop or on my iPad, so I'm fine with just having a single fully integrated software solution -- but it has to be as feature rich as alternative software.

When I find myself having to plug my cameras, EAF, and EFW into my laptop because I can't just do someting with the ASIAir, I also start looking at a whole new world of alternative hardware since I'm no longer benefitting from the fully integrated eco-system of ZWO. That doesn't mean that I won't still choose ZWO when the price / performance makes sense; but, since I'm no longer locked in with the ASIAir, it does mean that I'm now open to all kinds of other options.

This is not a problem for me, but it seems like ZWO would benefit by keeping me in its ecosystem by not incentivizing me to start looking at alternatives.

Either way, I'm happy with the ZWO products I have -- I just want more from the software. Thanks!

johnpd

The ASIAIR was designed to be a simple to use fairly comprehensive solution to astro-imaging. It succeeds well at that. It can image (live or with preset plans), focus, and guide and is controlled by a phone, tablet, or in some cases emulation software on computers. But it has limitations. It requires ZWO equipment and has limited hardware and software capabilities. ASIStudio is designed to run ZWO cameras and equipment directly. Even if you could get ASIStudio to run the ASIAIR, you are still limited by the ASIAIR box hardware and software capabilities. It is not a mini-PC.

More comprehensive PC software such as SharpCap, NINA, PHD2, etc. do not have the limitations that the ASIAIR has. They do open up the world of astronomy equipment to you. They do require a PC near the telescope, but still can be run remotely using remote connectivity software. There are a number of new mini-PCs now available which are only a little bigger than the ASIAIR and handle the many available astronomy PC software programs.

I find the ASIAIR is a great option for public star parties with its quick setup and ease of use. For more extensive capabilities I have purchased a mini-PC for the home environment.

JohnD

jpoveda

Thanks John, the feedback is appreciated, but I am well aware of the alternatives.

The point of my post was that it is in ZWO's interest to reduce the occasions where I might want to start looking at these alternatives. Why? Because these alternatives, in addition to having features that led me to start looking at them, also do not entail vendor lock-in. Hence my point that this is bad for ZWO but maybe not so much for me.

I think you missed the point of my post, but in the process, you helped to make my point. 😉

While the ASIAir is not an open platform "mini-PC"; it very much is a "mini-PC". It's an ARM based platform running the Linux operating system. In fact, the newer versions of the ASIAir Plus appear to be quite powerful given their limited power requirements.

I'm not confused that the ASIAir is a closed platform. I choose it specifically because of that. So, you'll notice that my original post made no request that ZWO open it up to allowing me to install ad hoc software. I think this would be a terrible mistake and would reduce its reliability as an appliance.

My request was pretty specific. Either:

1) integrate ASIAir + ASIStudio so I get the greater benefits of ASIStudio (assuming they continue to build this platform out) OR

2) continue to enhance ASIAir so I have no reason to look elsewhere.

The implication being that if I look elsewhere, then I'm no longer locked into ZWO.

I don't agree that integrating ASIStudio with ASIAir would limit functionality to ASIAir's features. I'm not sure why that would be the case? As I mentioned above, ASIAir is based on a general purpose ARM chip running a general purpose operating system, Linux. It's not like they designed a custom ASIC for astrophotography... that would probably be awesome, but very limiting.... and the ASIAir would then cost quite a bit more. So, anyways, my point is they have a fairly flexible platform... a mini-pc... that just happens to be setup to run only their software. So, yeah, they could allow tight integration between ASIAir and ASIStudio if they wanted to put in the engineering effort.

But why do that at all? Well, I would actually prefer they just continue to enhance ASIAir and ASIStudio doesn't offer any benefits. But I think there's a practical reason why I might want both. My Apple M1 Pro powered laptop is insanely more powerful than the ARM chip in the ASIAir (though they share a common heritage). So, ASIStudio could do things that require far more horsepower than might be practical on the Air. It would be nice to have a seamless choice. If I'm running light, I have everything setup on my telescope already plugged into my Air. If I need more heavy lifting, I fire up my ASIStudio and it discovers the Air already plugged into everything and allows me to command the cameras (etc) so from my laptop, where I can then use my more powerful CPU to do whatever it is that's beyond the computational capabilities of the ASIAir... assuming there currently are such things.

Anyways, I'm not a product manager for ZWO, so it's up to them to figure out the feature set that will continue to incentivize me to remain a pure ZWO setup... I'm just suggesting that offering a greater feature set in Studio while not also creating a case where I am incentivized to continue to use my Air with it opens me up to using hardware that comes in colors other than red.

johnpd