×

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

Bi-monthly release with minor bug fixes and improvements

[solved] ZWO EAF not connecting under Debian 11 Bullseye 64-bit

  • Posts: 145
  • Thank you received: 15
Hi,

I compiled KStars/Ekos/Indi for 64 bit OS (thanks to Nou's great scripts, see astro-soft-build ). I'm running KStars 3.5.8 stable and Indi 1.9.5 on a Raspi 4B 8GB. Everything works fine except for the ZWO ASI EAF focuser. I get the message
2022-04-06T14:41:41 Unable to establish the following devices:
+ EAF APO
Please ensure each device is connected and powered on.

In the same 32bit environment (Astroberry, exactly the same hardware) it works. Any ideas what I can check?

Thx, Bernd
Last edit: 2 years 1 week ago by Bernd Limburg.
2 years 1 week ago #82064

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

  • Posts: 3
  • Thank you received: 0
Might be something different but I had the same issue. I had not used the EAF for a while and it seems the firmware on the EAF itself had 'gone'.

From the zwo website I downloaded the latest firmware (not driver but firmware), loaded it using the zwo software and it worked straight away!

You could try..
2 years 1 week ago #82076

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

  • Posts: 145
  • Thank you received: 15
Thx for the hint, will give it a try…
2 years 1 week ago #82078

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

  • Posts: 349
  • Thank you received: 107
Another issue can be that udev rules in /etc/udev/rules.d/ was not installed properly?
2 years 1 week ago #82097

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

  • Posts: 145
  • Thank you received: 15
I just checked, udev rules (99-asi.rules) is identical to the working Astroberry image...

But if I look at dmesg, I get

[ 3.857753] usb 1-1.2.2: New USB device found, idVendor=03c3, idProduct=1f10, bcdDevice= 0.00
[ 3.866637] usb 1-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3.874435] usb 1-1.2.2: Product: ZWO EFF
[ 3.878665] usb 1-1.2.2: Manufacturer: ZW0
[ 3.892728] hid-generic 0003:03C3:1F10.0001: hiddev96,hidraw0: USB HID v1.01 Device [ZW0 ZWO EFF] on usb-0000:01:00.0-1.2.2/input0

It says "<strong>ZWO EFF</strong>". Shouldn't it read "<strong>ZWO EAF</strong>"? Is it possible that indi_asi_focuser is looking for any "EAF" device and can't find it because its name is "EFF"?

And the manufacturer name is "ZW0" which ends with a zero and not with the letter "O". Don't know if that matters.

Edit: This is not the problem obviously, as the dmesg output is identical in the working Astroberry environment.
Last edit: 2 years 1 week ago by Bernd Limburg.
2 years 1 week ago #82099

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

  • Posts: 145
  • Thank you received: 15
@dave: The EAF works in the Astroberry image, so no corrupt firmware. But thx anyhow.
2 years 1 week ago #82100

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

  • Posts: 145
  • Thank you received: 15
Still no success.

ASI EAF seems to be recognized as an USB HID device since 'dmesg | grep usb' yields (as posted before)
[  221.072942] usb 1-1.2.4.1: New USB device found, idVendor=03c3, idProduct=1f10, bcdDevice= 0.00
[  221.072970] usb 1-1.2.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  221.072984] usb 1-1.2.4.1: Product: ZWO EFF
[  221.072996] usb 1-1.2.4.1: Manufacturer: ZW0
[  221.085181] hid-generic 0003:03C3:1F10.0002: hiddev96,hidraw0: USB HID v1.01 Device [ZW0 ZWO EFF] on usb-0000:01:00.0-1.2.4.1/input0

Now starting indiserver manually, not from Ekos, gives
pi@raspberrypi:~ $ indiserver -vvv indi_asi_focuser
2022-04-08T16:55:31: startup: indiserver -vvv indi_asi_focuser 
2022-04-08T16:55:31: Driver indi_asi_focuser: pid=3179 rfd=3 wfd=6 efd=7
2022-04-08T16:55:31: listening to port 7624 on fd 4
2022-04-08T16:55:31: Driver indi_asi_focuser: sending msg copy 1 nq 1:
<getProperties version='1.7'/>
 
2022-04-08T16:55:31: Driver indi_asi_focuser: Searching for HID Device VID: 0x3c3 PID: 0x1f10

Is there anything more I can log which narrows down the root cause for the problem? Any further diagnostics?

Thx, Bernd
2 years 1 week ago #82160

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

  • Posts: 145
  • Thank you received: 15
Finally got it working. It was a permission issue with the USB devices. All devices on BUS1 didn't show up in "lsusb", but they did in "sudo lsusb". So I tried a lot of different udev rules but with no success.

Then I came across Kevin Ross' post , and changing the USB device permissions the hard way did the trick.
sudo chmod +rx /sys/bus/usb/devices/usb*
I put it in /etc/rc.local (without sudo) and it is boot-resistent.

ASI EAF is visible as non-root now and Indi/Ekos/Kstars recognizes it. This is maybe not the most elegant way, but it works...

Finally! :silly:
Last edit: 1 year 11 months ago by Bernd Limburg.
1 year 11 months ago #82411

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

  • Posts: 912
  • Thank you received: 86
Hi Bernd,
I installed StellarMate 1.7 64-bit a couple of days ago and having the same problem with EAF.
So, I need to sudo chmod +rx /sys/bus/usb/devices/usb* and then
put _what_ in /etc/rc.local ?
Sorry, I am not good with Linux...
Thanks!
-- Max S
ZWO AM5. RST-135. AZ-GTI. HEQ5. iOptron SkyTracker.
TPO RC6. FRA400. Rokinon 135 and other lenses.
ZWO ASI2600MC. D5500 modified with UVIR clip-in filter.
ZWO ASI120MM Mini x 2. ZWO 30F4 guider. Orion 50mm guider.
ZWO EAF x 3.
1 year 11 months ago #82426

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

  • Posts: 912
  • Thank you received: 86
OK.
I put chmod +rx /sys/bus/usb/devices/usb* to /etc/rc.local and it worked!
Thanks much!
-- Max S
ZWO AM5. RST-135. AZ-GTI. HEQ5. iOptron SkyTracker.
TPO RC6. FRA400. Rokinon 135 and other lenses.
ZWO ASI2600MC. D5500 modified with UVIR clip-in filter.
ZWO ASI120MM Mini x 2. ZWO 30F4 guider. Orion 50mm guider.
ZWO EAF x 3.
1 year 11 months ago #82429

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

Time to create page: 1.025 seconds