×

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

Bi-monthly release with minor bug fixes and improvements

Ekos does not recognise ZWO USBST4 adapter

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

Thank you for the pointer. Rules are not necessary if a driver exists. The use would be under accessories.
4 years 2 months ago #57025

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

  • Posts: 49
  • Thank you received: 0

I can only find the INDIGO driver. Is it the same as INDI?
How does INDIGO work with Ekos?
4 years 2 months ago #57027

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

  • Posts: 474
  • Thank you received: 168
It's included in the indi-asi package, it can be found as ASI ST4 under Aux when creating profile in Ekos. INDIGO is similar, but not the same as INDI, different implementation, but works with Ekos and can be mixed with INDI with some limitations.
4 years 2 months ago #57031

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

  • Posts: 49
  • Thank you received: 0
It doesn't seem to work either, I get a 'Unable to estabish: +ASI ST4' error, even though its properly connected (I also tried rebooting while connected)
4 years 2 months ago #57034

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

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

Ouch. Then the driver is not recognizing the new ASI product. Back to the Rule game again. The last we were at was writing a new rule based on HID. I posted the new rule. I would like to see if it worked. I do not have the hardware. This the new rule cleaned up to be strictliy HID.

# ZWO USBST4 adapater
ATTRS{HID_ID}=="0003:000003C3:0000CCCC",ATTRS{HID_NAME}==“ZW0 USBST4”,ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{HID_ID}=="0003:000003C3:0000CCCC",ATTRS{HID_NAME}==“ZW0 USBST4”,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 #57041

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

  • Posts: 49
  • Thank you received: 0
I tried the rule (copied the new rule in the old file), but there is still no ttyACM port in /dev
4 years 2 months ago #57058

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

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

Use: lsusb -v -d 03C3:CCCC. I would like to see the output.
4 years 2 months ago #57061

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

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

Depending on the output with LSUSB, I am offering as solution to test. This comes from the output of our previous discussion, 97-hidtohci.rules, and 99-asi.rules.

# this file is for ZWO equipment
ACTION=="remove", GOTO="ZWO_END"
SUBSYSTEM!="usb*", GOTO="ZWO_END"

#ZWO device setup
KERNEL=="hidraw*",ATTRS{idVendor}=="0003|000003C3|0000CCCC", RUN+="kmod load hid:b0003g0001v000003C3p0000CCCC"

ENV{DEVTYPE}!="usb_device", GOTO="ZWO_END"

# ZWO USBST4 adapater
ATTRS{idVendor}=="0003|000003C3|0000CCCC",ATTRS{iProduct}==“ZWO USBST4”,ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="0003|000003C3|0000CCCC",ATTRS{iProduct}==“ZWO USBST4”,ENV{MTP_NO_PROBE}="1"
ACTION=="add",SUBSYSTEM=="hid",ATTR{idVendor}=="0003|000003C3|0000CCCC",ATTR{iProduct}==“ZWO USBST4”,SYMLINK+="ZWOUSBST4",MODE="0666"
KERNEL=="ttyACM*",SUBSYSTEM=="tty",ATTRS{idVendor}=="0003|000003C3|0000CCCC",ATTRS{iProduct}==“ZWO USBST4”

LABEL="ZWO_END"
4 years 2 months ago #57068

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,

Yes. I have changed somethings after further review. Use this version.

# this file is for ZWO equipment
ACTION=="remove", GOTO="ZWO_END"
SUBSYSTEM!="usb*", GOTO="ZWO_END"

#ZWO device setup
KERNEL=="hidraw*",ATTRS{idVendor}=="0003|000003C3|0000CCCC", RUN+="kmod load hid:b0003g0001v000003C3p0000CCCC"

ENV{DEVTYPE}!="usb_device", GOTO="ZWO_END"

# ZWO USBST4 adapater
ATTRS{idVendor}=="0003|000003C3|0000CCCC",ATTRS{iProduct}==“ZWO USBST4”,ENV{ID_MM_DEVICE_IGNORE}="1"
ATTRS{idVendor}=="0003|000003C3|0000CCCC",ATTRS{iProduct}==“ZWO USBST4”,ENV{MTP_NO_PROBE}="1"
ACTION=="add",SUBSYSTEM=="hid",ATTR{idVendor}=="0003|000003C3|0000CCCC",ATTR{iProduct}==“ZWO USBST4”
ACTION=="add",SUBSYSTEM=="tty",KERNEL=="ttyACM0",ATTRS{idVendor}=="0003|000003C3|0000CCCC",ATTRS{iProduct}==“ZWO USBST4”,SYMLINK+="ZWOUSBST4",MODE="0666

LABEL="ZWO_END"
4 years 2 months ago #57219

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

  • Posts: 49
  • Thank you received: 0
I changed the rule, reloaded udevadm and rebooted, but still no ttyACM0 port visible. lsusb just shows the vendor and product id (03c3:cccc)
4 years 2 months ago #57220

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

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

I wished this could be fixed. Ok. I just recently noticed how both of my RS232 devices were not running fully. I could see evidence of partial running.

Open the rule and replace its content with this.

# this file is for ZWO equipment
ACTION=="remove", GOTO="ZWO_END"
SUBSYSTEM!="usb*", GOTO="ZWO_END"

ENV{DEVTYPE}!="usb_device", GOTO="ZWO_END"

# 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"
ACTION=="add",SUBSYSTEM=="tty",KERNEL=="ttyACM0",ATTRS{idVendor}=="03c3",ATTRS{idProduct}=="cccc",SYMLINK+="zwousbst4",MODE="0666

LABEL="ZWO_END"

This setup to what I use now. This works for me and my devices.

Use: sudo udevadm control --reload-rules
Use: sudo udevadm trigger

Next command tests the port.

Use: sudo udevadm test -a add $(udevadm info -q path -n /dev/ttyACM0)
Last edit: 4 years 2 months ago by John Robison. Reason: syntax
4 years 2 months ago #57254

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

Moderators: Radek Kaczorek
Time to create page: 1.108 seconds