• SDK & Driver

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

Hi - I've just updated to the latest version of TheSkyX on a raspberry Pi 4 running Ubuntu.

I also updated the camera driver (to version 3.25). Unfortunately, this latest version causes a crash. I have an older version (version 3.4) which does work, but this has a memory leak.

Is it possible that you could check and find out the problem?

Thank you,

Colin

you need to go back to 3.24, 3.25 crashes as you saw, they claim to have fixed it in SDK 3.26 but never published a new X2 plugin with the fix (that would also be a 3.26 version of the plugin).
I have a copy of version 3.24 if you need (email. me 😉 ).
Regards,
Rodolphe

    You can also fix the EFW plugin as it's not properly linked on libudev1 ... which makes it crash TheSkyX as it's missing symbols on Linux x86_64.
    I had to have a user patch it on their system using
    patchelf --add-needed libudev.so.1 x2focuserEAF.so

    but you should properly link your library.
    Also if you make a new version, please fix the installer for macOS (I sent an email in a email thread between you guys, software bisque and me over a year ago, your engineer (Yang Zhou) said "we'll fix it in the next release" ... and yet multiple release latter this is still not fixed ... so here is the change to make to your install script :
    if [ -d "$TheSkyX_Path/PlugIns" ]; then
    PLUGINS_DIR="$TheSkyX_Path/PlugIns"
    elif [ -d "$TheSkyX_Path/Resources/Common/PlugIns64" ]; then
    PLUGINS_DIR="$TheSkyX_Path/Resources/Common/PlugIns64"
    elif [ -d "$TheSkyX_Path/Resources/Common/PlugInsARM32" ]; then
    PLUGINS_DIR="$TheSkyX_Path/Resources/Common/PlugInsARM32"
    elif [ -d "$TheSkyX_Path/Resources/Common/PlugInsARM64" ]; then
    PLUGINS_DIR="$TheSkyX_Path/Resources/Common/PlugInsARM64"
    else
    PLUGINS_DIR="$TheSkyX_Path/Resources/Common/PlugIns"
    fi

    This is valid for all your plugin, not just the camera one ... there is NO MORE Resources/Common/PlugIns64 on macOS ! this has been gone for over 2 years

    You might want to improver your dev QA a bit... these are easy to catch if only you were installing the plugins once and actually testing them.

      @Software@ZWO#60921 I have an open discussion on need for X2 plugin for Filter Wheels to support TSX on RPI 4 running Bullseye as well. Been open since September. Truly need this. Thanks!

      rpineau Rodolphe.. Can I do this for the Bullseye issue I'm having for Filter Wheels? If so, might need a little help! ;-)

        Jay, this is only an issue on x86_64 for the EAF, the arm64 library for ZWO devices are properly linked, the EFW issue is a bug inside the plugin.

          rpineau Rodolphe .. Thanks.. Was looking at the statements and the ARM32 and ARM64 plugin references (and hoping it would work). :-(

          Jay S.

            @Software@ZWO#61034 Assume this is for the filter wheel? Very much appreciated.. Will test it thoroughly immediately!

            Jay S.

              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

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

                Jay S.

                  @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.

                  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.

                  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.

                    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.

                      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!

                        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.

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