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

jays_ct

rpineau Rodolphe...

The # FILTER WHEELS line is present in the rules.d .. Very confused...

Jay S.

rpineau

And you are sure no other software using the filter wheel is running at the same time ? No INDI stuff running AT ALL.
And you did run the install.bin from the tar.gz file above (after extracting it) ?

jays_ct

rpineau Roldolphe.. Don't believe INDI or INDIGO are involved, as they somewhat police themselves, but will double check that. Yes, on the install file after extraction.. The driver info from within TSX reflects the new code (1.7). The thought about some other driver holding it did cross my mind.. Again, don't think so but will eliminate that software from the system.. Thanks

Jay S.

jays_ct

All... Followed the video link step by step. Everything is identical to what is in the video. NO other Astronomical services running other than SkyX. Redid everything on a totally different RPI4 and running on 273 SkyX code. Error code 215 when attempting to get to settings and Error code 200 when trying to connect. Totally at a loss now. :-( I can image the system and make available if it will help. Has to be something unique here, but no clue what.

Jay S.

Software@ZWO

Hi @rpineau Thank you for your professional analysis.
Hi @jays_ct It's exactly what rpineau said. In fact, I haven't thought of any other way to solve this problem. But I will try to solve the issues. I will consult some professionals. I may not be able to solve this problem in a short time. But I will try my best to solve this problem as soon as possible. If @rpineau has some ideas, please post them here. Thank you.

jays_ct

Rodolphe and ZWO..

I am grateful both of.. I will try a few more things, including a total new build from scratch.

Rodolphe.. The 273 version of TSX I have is the one Richard built to give to SB for distro. It already contained ZWO X2 drivers in it. Am thinking of also deleting all references for and clean install X2 just to see.. Did you try the newer version of TSX for ARM64?

Again thank you.. Heading out for a couple of days, but will dive back in when I'm back!

Jay S.

travis

Hi jays_ct
I read this post. EFW plugin can be used on my PI. I suggest you try this. Decompress my compressed package and overwrite the corresponding plugin files according to my screenshot. Because I'm not sure whether your files are the latest. You can check the time of these files before overwriting. The latest version provided by ZWO is 11/11. After the plugin file is updated to the latest level, burn the EFW firmware (both the burning program and the firmware file are in the compressed package, version 3.0.7, which needs to be used on the windows platform). Before burning, you can record your current firmware version. If you have any questions, please contact me.
travis.

files.zip

2MB

rpineau

I'm on build 13273 on a Pi4 8GB for the test above (I have 13479 on another arm64 but 13273 is fine).
If this still doesn't work after you re-install from scratch, I could remote connect to your Pi to see if I can identify what's going on.

jays_ct

Rodolphe,

Many thanks for the offer. VIsiting Grandkids for a couple.. Will be home tomorrow to try.. Again thanks..

Travis,

Thanks.. I'm on Mac (OSX) and Linux, so I'm not sure if the firmware applies?? I will check to see what level mine are before burning.. I appreciate the help!

Jay S.

jays_ct

All,

Built an entirely new Pi OS system with only TSX on it and updated EFW X2 files. All works fine (phew). Still leave an incredibly nagging situation in my mind of WHAT is blocking the connection to the filter wheel on the existing system that both INDIGO and INDI saw fine. I deleted all references to INDIGO, Ain Viewer and Imager but left INDI and Ekos. PHD2 is also installed with a bunch of non-astronomy RPI type of utilities. Would love to nail what's causing the hiccup. I can go about installing one thing at a time on the newly built system but very perplexing. :-(

At least I can add that the new code works!!

Jay S.

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.

« Previous Page Next Page »