Ekos does not recognise ZWO USBST4 adapter

  • Posts: 389
  • Thank you received: 15
Hello,

Fantastic. The rule is fine. That is good. Next use: sudo udevadm trigger -a idVendor=03c3. This is supposed to see if the rule is triggered.


What I do next is: sudo udevadm monitor. I unplug and plug the device back in. I note the IdVendor # and idProduct #. I take the line and use: sudo udevadm test /sys/the string. Test is supposed to take the device and match it to its rules
Last edit: 4 years 2 months ago by John Robison.
4 years 2 months ago #56974

Please Log in or Create an account to join the conversation.

Ekos does not recognise ZWO USBST4 adapter - Page 4 - INDI Forum - Results from #36
  • Posts: 49
  • Thank you received: 0

Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

Hmm... I do not see the expected out from: sudo udevadm monitor. I see the expected output from: sudo udevadm test /lib/udev/rules.d/99-ZWOUSBST4.rules. This was the expected output from the previous message.

Please send the output from this command. sudo udevadm trigger -v. This will be with the device plugged in.
4 years 2 months ago #56982

Please Log in or Create an account to join the conversation.


×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

  • Posts: 49
  • Thank you received: 0

Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

Ok. This is your device.

/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:03C3:CCCC.0002

Notice the .0002. Hmm... Let's try this. At the end of idProduct, let's add "cccc.0002". This might be the issue.
4 years 2 months ago #56985

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello.

The next thing is to confirm.

sudo udevadm test /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:03C3:CCCC.0002

This should present the device. We shall see.
4 years 2 months ago #56986

Please Log in or Create an account to join the conversation.

  • Posts: 49
  • Thank you received: 0

Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

We have it in sight. I also see this. I don't think the rules for ttyACM apply here. Giving this a port is not the answer.

Reading rules file: /lib/udev/rules.d/99-USBST4.rules
Reading rules file: /lib/udev/rules.d/99-ZWOUSBST4.rules

Ok. Here is how we will tackle this.

HID_ID=0003:000003C3:0000CCCC
HID_NAME=ZW0 USBST4
HID_PHYS=usb-0000:01:00.0-1.3/input0
HID_UNIQ=
MODALIAS=hid:b0003g0001v000003C3p0000CCCC
ACTION=add
SUBSYSTEM=hid

This is a HID system. At least this is what the OS thinks and the device thinks it is. I am beginning to think this device isn't ready for Raspbian.

Let's try a different rule approach. I am wondering if INDI isn't ready for HID devices. IP and Serial are what it recognizes.

We can try a different approach. Copy and past over the rule. Unfortuantely, looks like there are two now.

# ZWO USBST4 adapater
ATTRS{idVendor}=="03c3",ATTRS{idProduct}=="cccc",ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="03c3",ATTRS{idProduct}=="cccc",ENV{MTP_NO_PROBE}="1"
KERNEL=="ttyACM*",SUBSYSTEM=="tty",ATTRS{HID_ID}=="0003:000003C3:0000CCCC",ATTRS{HID_NAME}==“ZW0 USBST4”
ACTION=="add",SUBSYSTEM=="hid",ATTRS{HID_ID}=="0003:000003C3:0000CCCC",ATTRS{HID_NAME}==“ZW0 USBST4”,SYMLINK+="ZWOUSBST4",MODE="0666"
Last edit: 4 years 2 months ago by John Robison.
4 years 2 months ago #56988

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

Yesterday, I went to ZWO’s website for the ZWOUSBST4. I specifically looked for Raspberry PI support. I found different architecture support. I found many ASCOM supported tools. HID is for a Windows 10 market.

Most equipment today has direct Raspberry PI support. ZWO specifically states that their hardware doesn’t work well with LINUX. Raspbian is a LINUX variant. We can try, but ZWO says unsupported.
4 years 2 months ago #56995

Please Log in or Create an account to join the conversation.

  • Posts: 1957
  • Thank you received: 420
The support people on the ZWO forum respond to requests usually within a few days. Maybe open a topic in feature requests and ask for a Linux/Mac driver?


Wouter
4 years 2 months ago #56999

Please Log in or Create an account to join the conversation.

  • Posts: 389
  • Thank you received: 15
Hello,

That is a good suggestion. I did post in the hardware. But, I mentioned this discussion and it was moved to AstroBerry. Oh well. The OS recognizes the ZWO as a HID. It would seem that HID would need a dedicated port to operate. Maybe not.
Last edit: 4 years 2 months ago by John Robison.
4 years 2 months ago #57005

Please Log in or Create an account to join the conversation.

  • Posts: 474
  • Thank you received: 168
Are you using the indi_asi_st4 driver? It uses ZWO's SDK which should handle the HID stuff by itself.
4 years 2 months ago #57023

Please Log in or Create an account to join the conversation.

Moderators: Radek Kaczorek
Time to create page: 1.319 seconds