Camera X2 Driver crashing on latest version of TheSkyX on Arm8 platform: Page 3

Camera X2 Driver crashing on latest version of TheSkyX on Arm8 platform

Software@ZWO

It's really a puzzling thing.

jays_ct

Software@ZWO It is.. I can wipe out everything, but that doesn't tell us much. :-( I really would like to try and figure out what is blocking the connection to TSX (for only ZWO Filter Wheel it seems) while everything else saw it fine. I was able to see other branded EFWs attached to a ZWO camera so it would seem it's not the hardware in any way..

Jay S.

jays_ct

All,

ZWO.. Would be very helpful if new X2 driver for EFW enabled "Calibrate" as an option (unless I'm missing it) in TSX!

Here's an update. Seems that INDI Ekos is at heart of the problem. I've rebuilt and tested a system with TSX, INDI/EKOS and PHD2. Everything works with starting TSX, including cameras and filter wheels. Guide camera, Imaging Camera and Filter Wheel all attached through Imaging Camera to single USB port on RPI. EVERYTHING works.

IF I start an EKOS connection FIRST (there is an EFW Calibrate steps there) the filter wheel responds BUT then the connection errors start despite the fact that I done a complete software driven "disconnect" in INDI/EKOS. A reboot allows TSX to operate fully again (reboot did not clear the error on the old system). Is there a hardware command to try and disconnect EFW at the system level from any operations? I know this is NOT a ZWO issue anymore (other than possibly providing Calibrate in the X2 plugin?) but wondering if smarter minds than mine have an idea? Is there an ASI Studio for RPI?

Thanks!
Jay S.

Software@ZWO

jays_ct
ZWO.. Would be very helpful if new X2 driver for EFW enabled "Calibrate" as an option (unless I'm missing it) in TSX!
Can you describe this in detail? I don't understand. thank you

rpineau

On some Raspberry Pi you can power cycle the usb ports using uhubctl, see if that works on yours (it should as uhubctl supports RPi4B).

jays_ct

Rodolphe.. Well UHUBCTL ran but didn't change the issue BUT on that thought, I unplugged the EFW and plugged it immediately back in, and the EFW will now work after using INDI/EKOS.. Don't know if I lose the effects of calibration then? Seems like an endless loop!! No idea with none of the USB resets seem to make ANY difference.. You would think a power reset like UHUBCTL would be the same effect as unplugging and plugging back in. Here's the result from UHUBCTL (nice utility.. Installed with Synaptic and ran as SUDO)

pi@raspberrypi:~ $ sudo uhubctl
Current status for hub 2 [1d6b:0003 Linux 5.15.76-v8+ xhci-hcd xHCI Host Controller 0000:01:00.0, USB 3.00, 4 ports, ppps]
Port 1: 02a0 power 5gbps Rx.Detect
Port 2: 0203 power 5gbps U0 enable connect [03c3:1604 ZWO ASI1600MM Pro]
Port 3: 02a0 power 5gbps Rx.Detect
Port 4: 02a0 power 5gbps Rx.Detect
Current status for hub 1-1.4 [05ac:1006 Apple, Inc. Keyboard Hub 000000000000, USB 2.00, 3 ports, ppps]
Port 1: 0100 power
Port 2: 0303 power lowspeed enable connect [05ac:0220 Apple, Inc Apple Keyboard]
Port 3: 0303 power lowspeed enable connect [045e:0039 Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)]
Current status for hub 1-1.2 [04b4:6572 USB2.0 Hub, USB 2.00, 4 ports, ppps]
Port 1: 0100 power
Port 2: 0103 power enable connect [03c3:1f01 ZW0 ZWO EFW]
Port 3: 0503 power highspeed enable connect [03c3:224a ZWO ASI224MC]
Port 4: 0100 power
Current status for hub 1-1 [2109:3431 USB2.0 Hub, USB 2.10, 4 ports, ppps]
Port 1: 0100 power
Port 2: 0503 power highspeed enable connect [04b4:6572 USB2.0 Hub, USB 2.00, 4 ports, ppps]
Port 3: 0100 power
Port 4: 0503 power highspeed enable connect [05ac:1006 Apple, Inc. Keyboard Hub 000000000000, USB 2.00, 3 ports, ppps]
Current status for hub 1 [1d6b:0002 Linux 5.15.76-v8+ xhci-hcd xHCI Host Controller 0000:01:00.0, USB 2.00, 1 ports, ppps]
Port 1: 0503 power highspeed enable connect [2109:3431 USB2.0 Hub, USB 2.10, 4 ports, ppps]

rpineau

So I assume you actually ran : uhubctl -l 1-1.2 -p 1 -a 2 (hub 1-1.2 port 2 where the EFW is , 2 = cycle).
Also uhubctl can only control the port of the Raspberry Pi so if hub 1-1.2 is the one on your camera, uhubctl can't control it.
On my Pi4 B if I plug the EFW in one of the usb 2 port it shows on hub 1-1 (this is just part of the output from uhubctl):

Current status for hub 1-1 [2109:3431 USB2.0 Hub, USB 2.10, 4 ports, ppps] Port 1: 0100 power Port 2: 0100 power Port 3: 0103 power enable connect [03c3:1f01 ZW0 ZWO EFW] Port 4: 0100 power

So to power cycle it I use :

uhubctl -l 1-1 -p 3 -a 2 Current status for hub 2 [1d6b:0003 Linux 5.15.76-v8+ xhci-hcd xHCI Host Controller 0000:01:00.0, USB 3.00, 4 ports, ppps] Port 3: 02a0 power 5gbps Rx.Detect Sent power off request New status for hub 2 [1d6b:0003 Linux 5.15.76-v8+ xhci-hcd xHCI Host Controller 0000:01:00.0, USB 3.00, 4 ports, ppps] Port 3: 0080 off Current status for hub 1-1 [2109:3431 USB2.0 Hub, USB 2.10, 4 ports, ppps] Port 3: 0103 power enable connect [03c3:1f01 ZW0 ZWO EFW] Sent power off request New status for hub 1-1 [2109:3431 USB2.0 Hub, USB 2.10, 4 ports, ppps] Port 3: 0000 off Current status for hub 2 [1d6b:0003 Linux 5.15.76-v8+ xhci-hcd xHCI Host Controller 0000:01:00.0, USB 3.00, 4 ports, ppps] Port 3: 0080 off Sent power on request New status for hub 2 [1d6b:0003 Linux 5.15.76-v8+ xhci-hcd xHCI Host Controller 0000:01:00.0, USB 3.00, 4 ports, ppps] Port 3: 02a0 power 5gbps Rx.Detect Current status for hub 1-1 [2109:3431 USB2.0 Hub, USB 2.10, 4 ports, ppps] Port 3: 0000 off Sent power on request New status for hub 1-1 [2109:3431 USB2.0 Hub, USB 2.10, 4 ports, ppps] Port 3: 0101 power connect [03c3:1f01]

jays_ct

rpineau

Rodolphe.. Success with UHUBCTL both on a standalone USB port on RPI and with everything connected to camera. I was able to address the specific locations for both connections and power cycle just those. Effectively the same as unplugging and then plugging back in I'm guessing (except done with software). Still the question of if power cycled does calibration "go away"? Will ask of ZWO in my reply to their question. Still no clue as to what INDI is holding on to, but have an open question on INDI forum.. Maybe Peter can help?

Jay S.

jays_ct

Rodolphe..

Hmm.. thought it did everything but see your point. I was thinking if it reset the camera, it would reset the EFW. Will try to be more direct..

Jay S.

jays_ct

Software@ZWO

Software@ZWO Good day and thanks for replying and staying with this. ASIStudio on RPI would be great.. Hoping it would be an easy port from version on ASIAir since both at Pi based ARM based software?

As for sequence question... Yes, depends on what is started first. See my reply to Rodolphe (rpineau) above. I can manually reset power to the USB ports for the EFW both by unplugging and reattaching EFW, or by specific software control with UHUBCTL as indicated above. The question is one of calibration. IF I do calibrate first, then power cycle that USB port and the EFW, does the effect of calibration on EFW remain or is it lost? Since the EFW does not "move" after I did calibrate, I'm hoping it stays.

For sequence..

Normal startup for RPI and TSX, connect filter wheel and there are no problems.
Terminate TSX
Start INDI/EKOS and connect EFW - Then calibrate (or just move EFW position)
Disconnect all from INDI/EKOS and terminate programs.
Restart TSX and attempt to connect to EFW - will fail with connection error.
Disconnect EFW from USB port (or run UHUBCTL)
Attempt to connect to EFW - will now be successful.

Two solutions I see.. Either ASIStudio for RPI to calibrate, or add a Calibration step to X2 plugin for TSX. If you want to keep ASIStudio as ASIAir only, then requesting Calibration be added to X2 plugin. This is not a reflection on ASIAir, but TSX for Paramount mounts is just much more robust right now.

Thank you all for staying with this!!! It is appreciated!!!

Jay S.

Software@ZWO

jays_ct Hi Jay, what do you mean by calibration? Can you send me a screenshot?
We will try to solve this problem. We will not give up. Thank you.

jays_ct

Software@ZWO

In both ASIStudio and in EKOS/INDI, there is a function to calibrate the filter wheel. When you select that, it appears the filter wheel is going through a process of "checking" each position from 1-5 or 1-7, etc. against a starting point or perhaps each of the other slots or balancing based on filter weight? At least it appears that's what it is doing. In ASIStudio, it is under Settings for the Filter Wheel once attached (where you can change filter names). I "assume" that it's somehow keeping that calibration internal or is it simply a hard "reset" to make sure all the slots are centered?

So having that either in the X2 plugin as a selection under TSX Settings or perhaps an additional "push button" next to where you can update filter wheel names in TSX would be great. Alternative is have ASIStudio on RPI but don't know if that opens up the whole "who is controlling the filter wheel" problem we currently have with INDI/EKOS.

Jay S.

Software@ZWO

jays_ct Hi Jay, thank you. I know what you mean by calibration. I think we can add it to SkyX. I will schedule the development of this feature.

jays_ct

Software@ZWO Happy Holidays and Thank you..

Just wanted to stop back in (for now) and again thank you for all the efforts by you and the team in helping to resolve this sticky issues using SkyX on a Raspberry Pi. When a "calibration" step comes about, please don't hesitate reaching out if you need any testing. :-)

A couple of questions.

Will the "beta" links for EFW, Camera, Focuser become fully available downloads as new versions on the download page?

Also

Since the ASIAir is RPI based, is there any consideration of using something like an Argon M.2 case to be able to have ASIAir run off an SSD? Would be excellent!! :-)

Thanks again..
Jay S.

jays_ct

That is great to hear. I truly appreciate it all! Please feel free to reach out at any point if you want to "try" anything on a Raspberry Pi in the future. I do have a system image with INDI/EKOS, INDIGO AIN Imager, and SkyX and PHD2 all running (not concurrently). I'm still waiting on a focuser to be able to test all aspects. The "trick" to running these is to be able to totally disconnect devices before launching another. The exception seems to be PHD2 which handles things pretty well it seems. Again, please don't hesitate. I am running this all on an SSD based RPI which enhances speed greatly. SkyX will launch in under 3 seconds from start to full screen.

Jay S.

Software@ZWO

jays_ct Thank you, Jay. If there is any progress, I will let you know.

mcgillca

Thank you very much for all the activity! I've downloaded the new versions of the EAF and the camera plugins - both work well for TSX on the Rasp Pi 4 (64 bit). I've also been running a test to look for memory leaks, and so far, no issues.

I'll continue to run for a few hours before testing tonight since the weather forecast is (unusually) clear here in the UK for tonight.

Colin

mcgillca

rpineau

Thanks, Rodolphe! Apologies, I've been on holiday and not had time to check this site. The new versions do work, otherwise I'd definitely have asked for your previous version.

Hope all is well with you,

Colin

Software@ZWO

jays_ct
Hi Jay,
The calibration function is already in the development schedule, and we will complete it as soon as possible.

The new version will be uploaded to the official website soon.

Since the ASIAir is RPI based, is there any consideration of using something like an Argon M.2 case to be able to have ASIAir run off an SSD? Would be excellent!! :-)
I will feed this question back to our ASIAIR development team.

Best Regards

Software@ZWO

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

Thanks for the update.. Happy New Year.

Jay S.

« Previous Page Next Page »