Thanks for the update.. Happy New Year.

Jay S.

All,

Well, feel like it's Groundhog Day.. Booted my totally working Raspberry Pi today with no new updates, etc. Same exact system that has been 100% fine.. Now, I'm getting the error code 200 and 215 again in TSX with the Beta code that was working so perfectly .. Again, not the hardware.. Is perfectly happy in INDI/EKOS (and rebooted to make sure those were not running when I tried again). Reloaded the Beta code, still the same errors. About to rebuild a totally new system again and start from scratch.. Would love any suggestions.. I really did not do any updates to that working system. I did copy it to another RPI and was on the other RPI that I first noticed the connection problems again. Then tried the original one thinking I had to have made an error in building the new Pi but had the 200 and 215 errors there as well.

SO tired!!!

Jay S.

Software@ZWO
Hi Jay, about Argon M.2, I consulted our ASIAIR team. Our ASIAIR Pro runs on an SD card. Our ASIAIR Plus and Mini are running on eMMC. SD card and eMMC cannot be replaced, so Argon M.2 cannot be used.

jays_ct
Hi Jay, can you take a video to show this problem(error code 200 and 215)? We can't reproduce this problem. We need some more detailed information to find the cause of the problem. Thank you.

Hello.. I did a complete rebuild from scratch on a new and different SSD (NVME) .. Nothing else except base OS from Imager download, and SkyX (one level back) plus the Beta code. That is working.. Will try to add one step at a time starting with update to Base OS. I think this was a very large update to Bullseye.. Then add PHD2, Pi tools, etc. and see if something breaks it again.. Will post back.. As for the 215, 200 error codes, it happens when I hit the "connect" option. Camera and EFW are at the Beta levels.. Again though, I did not apply the latest OS updates, etc..

Thank you
Jay

I looked up the meaning of error code 200 and 215.
When SkyX connects the camera, if it cannot find the camera from the system, it will report an error code of 200. As shown in the figure below

Error code 215 and 200 are similar. The description of error code 215 is shown in the figure below. When SkyX sets the camera, if it is found that the camera is not connected, it will report an error code 215.

Through the above analysis, I feel that the problem may not be SkyX, but why the camera is not connected. When you encounter problems with error code 200 and 215, can you use other software except SkyX to open the camera? Or can you check whether there are camera devices in the system through the command line.

Thank you.

Hello and thanks for the reply.. Yes, other software sees both the camera and filter wheel fine. SkyX sees the camera fine. I'm familiar with 200 and 215. When the system boots, you can see the filter wheel moving (briefly) left and right, so there is a connection. Again, tried the obvious of new cables, etc..

I have it working again on a totally new system build and will try to see what may be knocking it out.. Bullseye Update, Updates to SkyX, etc.. Will do my best. I'm going to erase the ZWO files on the failing system and reload the beta code again.. I will keep updating.. Just SOO insanely crazy that a working system with the beta code, just stopped working.. At that point in time, I had not done any updates to the application code on the system or the base OS itself..

I do appreciate your working with me on this. For the record, on the failing system, a Starlight Xpress EFW connected to a ZWO camera (1600) works fine..

Jay S.

jays_ct I'm sorry that I haven't helped you solve the problem. I will not give up on solving the problem.

I appreciate the help you have been. As I said, working fine again on a newly built system and still have not been able to determine why it is failing on the older one. :-(

There was mention in an earlier reply from ZWO about adding the "Calibration" function to the X2 plugin. If I had that, I could eliminate the other Astronomical software on the RPI. :-)

Jay S.

jays_ct It's very kind of you

jays_ct We had a happy Chinese Spring Festival holiday. Thank you for your greetings. We will consider adding the calibration function to the plug-in in a later version.

For calibration, according to your practice, the calibration position will be saved. When you calibrate, the calibration data will be written to the firmware. Therefore, even if you restart the device or change the computer, the calibration data is still there.

Best Regards

Thank you.. That will help me. Calibration in X2 Driver is even better. :-). Will the beta code become a new "official" driver soon?

Thanks again!

Jay S.

jays_ct Thank you for your suggestion. We will try to make the software better and better.
We have released the official version on our website.

Best Regards

Thanks again.. Glad I could help in some way.. My thanks also to other who contributed to this entire thread with their ideas and suggestions. Hardware interrupts, cross talk, "ownership", etc. can be some of the more difficult things to resolve, especially across varying platforms and OSes. Personally I would like to see an ASIAir (since it is based on a Raspberry Pi) that has more in the way of fast onboard SSD storage (like the Argon One M2 cases). It's way, in part, I went down this whole route to begin with! :-)

Thanks again.. Let me know if there's anything else I can help in testing if needed..

Jay S.

jays_ct
Astronomy lovers are all people with love. Everyone is willing to share and help others. I am often touched by their willingness to help others.
ASIAIR and ASIAIR Pro, as old products, are no longer produced. ASIAIR Plus and ASIAIR Mini are running on eMMC, which cannot be replaced. The new generation of ASIAIR no longer uses Raspberry Pi, but uses RK.