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

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

Software@ZWO

jays_ct These are the beta releases for Mac, Linux x86, Linux x64 and Linux Armv8(Raspberry Pi4)
Camera: https://drive.google.com/file/d/19-NIfEkTDZVFkFsKNzL7KIUmlhFixlt5/view?usp=share_link
EAF: https://drive.google.com/file/d/1qaR3ZoGUbdslvWJdASQ64qbUP_Itt7eB/view?usp=share_link
EFW: https://drive.google.com/file/d/1vl_1N70QiaUWf4kjnW7ELGCxiFIZq2NL/view?usp=share_link

If there are any issues, please let me know and we will fix them as soon as possible.

Thank you

jays_ct

@Software@ZWO#61043 Thank you!!! I'm building a test system as we speak!

Jay S.

Software@ZWO

jays_ct Thank you

jays_ct

@Software@ZWO#61107 Good morning. Verified new X2 plugin has installed correctly (Driver and SDK EFW 1.7). Unfortunately, the Filter Wheels (7 and 5 position) do not connect. TSX is returning error code 200 (no connection to the device). Have tried separate connections to RPI as well as connections through camera (2600MC and others), ZWO supplied USB 2 cables and others, as well as separate RPI 4s (all 8GB). The filter wheels do show connection to the device when on boot up, as well as through INDI and INDIGO programs (not running at the time TSX is started) both as direct connections and through camera USB ports. TSX is at v10.5.0 Build 13273. Is there more you need (imagine there is). Camera seems fine. Don't have a focuser on hand to try yet.

Jay S.

jays_ct

Just another update. I updated TSX to the latest version on Software Bisque site (Build 13479). The same error exists for the filter wheel. That said, I have no issues connecting or taking test images with the 2600MC on the X2 plugin as it comes by default. Driver version is 3.400, ZWO X2Camera Driver 19.3.6, ASI SDK V1, 20.2

Is there anything else you'd like me to try?

Jay S.

jays_ct

rpineau Rodolphe.. You know X2 far better than most. Anything come to mind on causes for error code 200 Connection error for the EFW X2? Tested a Starlight Xpress EFW connected to and through ZWO camera and it works, so not the cable or USB port, etc.. Just not sure how to help debug any further.

rpineau

Error 200 is ERR_COMMNOLINK, which means the X2 plugin doesn't even see the filter wheel.
Do you see it via lsusb on the PI ?
the EFW is a HID device as far as I know so there is no good way of testing it from the command line.
Does the Filter Wheel work fine on another Operation system ( Linux x86_64, macOS, Windows ? ).
If ZWO uses HIDAPI, is the plugin properly linked .. If not, are they using libusb ? Is it properly linked or is the libusb on the system not the right version ?
Hard to tell without more information. I plan in doing some testing on arm64 (Pi 4 and Odroid) this weekend so may be I'll have more questions or idea later.

jays_ct

rpineau Rodolphe... Didn't do a lsusb, but everything else sees and operates it so I'm guessing yes. INDI and INDIGO see it fine with EKOS and AIN Imager (EKOS lets me run calibration). Also, when the RPI first boots, looks like it's "testing" connection to the EFW, as it moves a little left/right. Works fine on OSX as well (which I would have thought would be somewhat close to Bullseye but maybe not). Let me know if you see something to try with your trial.. Thanks!

jays_ct

rpineau Rodolphe.. The answer to lsusb is "yes" it's there..

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 03c3:1f01 ZW0 ZWO EFW
Bus 001 Device 006: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
Bus 001 Device 005: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI)
Bus 001 Device 003: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Jay S.

Software@ZWO

We will find out the cause of the problem and solve it as soon as possible

jays_ct

@Software@ZWO#61207 The effort is appreciated, especially since all three were provided for Beta.. Please let me know what I might be able to try here to assist. There are lots of other X2 providers and authors out there but hopefully will be an easy fix. Did this ever work on ARM64 (serious question). If so, would seem to be a logical starting point. :-)

Software@ZWO

jays_ct The link below is a video file. It demonstrates how to control EFW on raspberry pie by SkyX. Please refer to it.
https://drive.google.com/file/d/1kSrLnWaTsBs3L6yv65TIR-3HYb0dl4KX/view?usp=share_link

Best Regards

Software@ZWO

@jays_ct#61213 Yes, we tested it on Raspberry PI 4 (ARMv8) and it works. Can you provide your running environment? For example, which version of raspberry PI? What operating system is installed? etc. Thank you.

jays_ct

Software@ZWO Sorry... I didn't see this message. I will get you that information.

Jay S.

jays_ct

Software@ZWO

Let me know if you need more? Are there any updates (firmware) to filter wheels??

System Info:
Model: RPI Pi 4 Model B Rev 1.5

Kernel Info:
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 5.15.76-v8+ #1597 SMP PREEMPT Fri Nov 4 12:16:41 GMT 2022 aarch64 GNU/Linux

OS Info: (using default Debian desktop)
pi@raspberrypi:~ $ hostnamectl
Static hostname: raspberrypi
Icon name: computer
Machine ID: xxxxxxxx
Boot ID: xxxxxxxx
Operating System: Debian GNU/Linux 11 (bullseye)
Kernel: Linux 5.15.76-v8+
Architecture: arm64

Jay S.

jays_ct

Software@ZWO Thank you. I can't read Chinese and the steps were a bit too fast.. Didn't understand what you were doing in many of them, but it appears you've got it working (Thank you). Can you provide the steps in English (slower) or create a new plugin for me to test? Also, have you tried on the newer version of TSX for RPI? If not, I can try that here once I can get through all the steps you did. It's really good to see it working!!

Jay S.

rpineau

I can confirm that the ZWO EFW plugin version 1.7 linked above works on my ARM64 Raspberry Pi OS 64 bit

rpineau

The Camera plugin also works on arm64 same config as above.
My Raspberry Pi image is 2022-01-28-raspios-bullseye-arm64 , it's a base image and then I install XFCE on top of it (but it should work equally well with MATE). Installed current kernel is 5.15.76-v8+

jays_ct

rpineau Rodolphe. Is it working with the Beta code that was supplied, or with the steps in the video. It would seem that they had to take some extra steps in what they have to get the Filter Wheel to be recognized. I don't think the desktop interface should have a part in causing the Error Code 200.. I will check the kernel level, but for whatever reason all the other apps (and the system) see the filter wheel fine. It's only TSX. I even uninstalled and installed the new level. Not sure if there's any residual code left after the uninstall or not.

What version of TSX are you on?

Thanks..
Jay S.

rpineau

i just installed the plugin linked above for the EFW, no need to do anything special. What they show in the video is that before install there was no ZWO files and then after install they were present, showed up in TSX and the filter wheel was working.
So the video show how to install and uninstall the plugin and where the file are installed. They are not doing anything special.

As you can see my PI is similar to yours :
hostnamectl
Static hostname: mobilepi
Icon name: computer
Machine ID: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Boot ID: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Operating System: Debian GNU/Linux 11 (bullseye)
Kernel: Linux 5.15.76-v8+
Architecture: arm64

So if you install the EFW X2 plugin above (version 1.7) it should work as is.
Check that you have the efw.rules in /etc/udev/rules.d and that it contains this :
# FILTER WHEELS ACTION=="add", ATTRS{idVendor}=="03c3", ATTRS{idProduct}=="1f01", GROUP="users", MODE="0666"

jays_ct

rpineau Rodolphe...

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

Jay S.

« Previous Page Next Page »