Kevin_A Not sure yet how corrected trigger accuracy applies and is it just a simplified adjustability for minmo?
Yeah, from the description below the box, that's just MinMo. They are probably somehow try to side step modifying PHD2 (open source license).
Just 0.1/0.2 pixel; nothing in between.
Chen
w7ay thanks Chen, that does confirm my thoughts as I had just never heard of the term corrected trigger accuracy. Their description below is the smoking gun. I am glad they reversed their previous change.
It will be nice to have 0.1 back again. Now I just need clear skies to test out my new guide scope… Sharpstar 50EDPH with 0.84 reducer flattener. At 1.2 kg it is very light and should give nice sharp stars.
Kevin_A I had just never heard of the term corrected trigger accuracy.
MinMove is just a limit (e.g., 0.1 pixel) where no correction feedback is sent to the mount if the centroid did not move by no more than that (e.g. 0.1 pixel).
A MinMo of 0.2 pixels would require the measured centroid to move by more than 0.2 pixels before there is anything fed back. I never liked the concept of limits in a feedback loop (derogatorily nicknamed "bang-bang control" by those in the business) and prefer a purely linear loop (MinMo of 0.0) since it more mathematically correct.
With a MinMo of 0.2 pixels, a high PE slope mount would have moved by 0.4 or more pixels before any correction is sent to it (check the sawtooth graphs). More likely 1 or two pixels. ZWO is using 0.2 pixels probably because their mounts are not linear to within 0.1 pixel (you get what you pay for).
Chen
Kevin_A I have been pestering them now for months to put it back.
Completely random "techincal" activities over there.
When ASIAIR first started ueing PHD2 for auto guiding, it was using a 0.2 pixel MinMo.
When I acquired my first RST-135, I wrote and told Sam that a Harmonic drive that has no backlash needs smaller MinMo to work well. It took at least two years of pleading (and only after they had started "designing" the ZWO mounts) that they finally relented, and changed it to 0.1 pixel; presumably, as you found out, 0.2 pixels is a disaster for these gears.
Now some random person with no Control Theory background decided to change it back to 0.2 pixels again in an early TestFlight.
Finally, they appear to now allow 0.1 pixel again.
What a zoo.
Chen
w7ay yes, it took a few logs from myself and others to show them the differences. I think that they may have had oscillating issues with a few 432s mounts that settled down and were kind of fixed using 0.2, but now all their mounts are 288s and may not have issues with oscillating so they are back to 0.1px. I am just glad it is back to 0.1px. Who knows….
I think that they care more right now about the Seestar thingy anyways. I havent seen clear skies in 6 weeks now so nothing matters to me right now. All I am doing is getting prepared for when the skies do clear…. Better guide scope, better ways of elliminating flexture, better guide settings and better mount rigidity etc.
Kevin_A so they are back to 0.1px
Looks like 0.1/0/2 pixel MinMo is still on the latest TestFlight [Firmware 10.98 -- the TestFlight Notes has 10.97 update info]:
This is the actual "what to test" on 10.98:
The 0.1/0/2 switch is apparently there in the Advanced Guiding window, but defaulted to 0.1 pixel (to keep the "Simple 1,2,3" crowd happy).
Chen
@Tech@ZWO Please we need help on this one https://bbs.zwoastro.com/d/17089-asiair-v212-public-beta-released/203 any answer can be appreciable
@Kevin_A there is any way to do a quick escalation i feel like it's not working to ping them 
caradou are you using the testflight version. If not, do so and send feedback through the app regarding the issue. Keep it simple in your request… not overly detailed. I had issues previously with a dslr being recognized but it was the way I was tryin* to access it after starting asiair. Make sure the camera has BOTH data ucable to asiair usb port and snap cable( intervalometer cable ) to snap port attached with the camera turned on prior to booting up asiair. It needed both cables on my Nikon for my camera to work. Make sure your camera is on M in Bulb mode too.
Kevin_A I appreciate a lot your answer.
Yes of course i'm using the testflight (My DSLR is not recognized in other version)
I put the two cable as well. Everything is using the latest firmware, i even tried by having an older firmware on my Sony.
I shared on the testflight as a bug, but no answer for like 2 months now?
i hope someone from the team will be able to address my issue.
Kevin_A you were talking about kind of booting sequence.
You start your DSLR, you connect with the ASIair, and then you start the ASIair, and then you connect to the app, and then it's connected and showing the preview on the screen is that correct?
Trying to find if there is any specific sequence i have to follow.
I agree, it's a beta, but as a beta, i was expecting at least the minimum to work which is showing my camera 
Kevin_A Yes it is showing the camera, i can enable it, then i have the message pop up, and then nothing else, the preview camera tab is not showing anything and when i click to shoot, it's saying exposure failure.
When i click on the exp 1s nothing is happening.
When i go to live, and try to shoot, i have exposure failed, please check if the shutter release cable is connected properly(which is the case)
Of course i connected disconnected multiple time, the shutter cable is working (because i tried with my skywatcher)
in the preview or live, it's always showing the ASIair background (as easy as 1,2,3)
caradou that is strange. It is like it is not recognizing it is in Bulb mode. What type of data cable are you also using? Did it come with the camera? I had issues on my camera once when using a usb3 cable splitter into the usb2 port. It did not like the fact it was a usb3 splitter. Try hooking the data cable into the usb2 port and not the 3 and vise versa. This seems more like a cable issue. I needed one more usb port and got a splitter and it did not work until i downgraded the splitter to a usb2 type.
Two weeks ago, i have tried the Beta release of ASIAir, with my ASIAir Plus. All worked well but then i run into an issue where i thought there was a fault on my 2600MM Pro camera, before it turned out that this camera works perfectly with older firmware & SW (i rolled it back) as well as with ASI Studio. Also, all my other cameras including 2600MC Pro worked fine with the beta, but NOT 2600MM Pro - that was an exception.
What was happening was that as soon as i connected the camera via USB, it's cooling stopped. The cooling was working as default upon turning ASIAir Plus on, but the moment i activated its connection with camera, cooling was off. Again, strangely, this was happening only with the 2600MM Pro camera - all three others (2600MC Pro, 183MC pro and 183MM Pro) worked just fine.
Hope this helps.
Normally I jump on betas like this. The only reason I haven't is that it's been overcast and raining for 2 months. Turns out to be a mixed blessing. By the time I can image again I assume all of the bugs would have been squashed.
I've been working with software for some 35 years and have never seen a company issue a beta version that remains beta for 3 months. Is ZWO abandoning the ASIAIR to focus on their SeeStar? It appears that way. I'll give it another month or so and then consider moving over to NINA or PHD and the Primaluce Eagle.
im using and before testing the new version and everything working perfect
please. could someone tell me what is wrong with asi air pro plus
50% or more problems are bad cables , or bad quality cables. start checking the cables , and dont bends the cables less 90 degree ( data cables like (usb hight** speed )
