×

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

Bi-monthly release with minor bug fixes and improvements

RPi3B_ZWOasiEFWmini_again

  • Posts: 10
  • Thank you received: 0
My RasPi(Raspbian 9.4 (stretch)+livimdi 1.7.4) cannot communicate with ZWOASI EFWmini as follows. I have installed dependencies, sudo apt --fix-broken install, and cp udev rule based on ASI website. (Last year, it did worked with jessie+libindi_1.4.1)
My final goal is to do this on PizeroW, but did not work. Then I retried it on Pi3B, but not worked. Thank you for your kind advice.

#My script
export LANG=en_US
sudo indiserver indi_asi_wheel &
sleep 3s
indi_setprop "EFW.CONNECTION.CONNECT=On"
indi_setprop "EFW.CONNECTION.DISCONNECT=Off"
jobs
indi_setprop "EFW.FILTER_SLOT.FILTER_SLOT_VALUE=1"
indi_getprop "EFW.FILTER_SLOT.FILTER_SLOT_VALUE"

#Error message.
2018-11-14T08:39:28: startup: indiserver indi_asi_wheel
2018-11-14T08:39:28: Driver indi_asi_wheel: Searching for HID Device VID: 0x3c3 PID: 0x1f01
2018-11-14T08:39:29: Driver indi_asi_wheel: FW ID: 0 FW Name: EFW enumerate? false
No EFW.CONNECTION.CONNECT from localhost:7624
No EFW.CONNECTION.DISCONNECT from localhost:7624
[1]+ 実行中 sudo indiserver indi_asi_wheel &
No EFW.FILTER_SLOT.FILTER_SLOT_VALUE from localhost:7624
No EFW.FILTER_SLOT.FILTER_SLOT_VALUE from localhost:7624


#USB info. looks OK.
Bus 001 Device 005: ID 03c3:1f01
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
|__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=smsc95xx, 480M
|__ Port 5: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 3: Dev 7, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 4: Dev 9, If 0, Class=Mass Storage, Driver=usb-storage, 480M
Device: ID 03c3:1f01
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 16
idVendor 0x03c3
idProduct 0x1f01
bcdDevice 0.00
iManufacturer 1 ZW0
iProduct 2 ZWO EFW
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 41
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 64mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
Warning: Descriptor too short
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.01
bCountryCode 0 Not supported
bNumDescriptors 2
bDescriptorType 34 Report
wDescriptorLength 68
bDescriptorType 0 (null)
wDescriptorLength 0
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 10
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 10
Device Status: 0x0000
(Bus Powered)
5 years 5 months ago #31672

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

  • Posts: 10
  • Thank you received: 0
Can I have the meaning of this message, and useful URL or something to solve the issue?
>Driver indi_asi_wheel: FW ID: 0 FW Name: EFW enumerate? false
Any small advice should be appreciated.
5 years 5 months ago #31734

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

  • Posts: 1009
  • Thank you received: 133
Likely nothing that really helps you, but I do get that message, too, from my EFWmini. But it's working without issues, so at least it's not a showstopper...
The following user(s) said Thank You: Tatsuji_Tanaka
5 years 5 months ago #31743

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

  • Posts: 10
  • Thank you received: 0
Thank you DerPit.
So you do't get message like;
>No EFW.CONNECTION.CONNECT from localhost:7624

I have installed libindi, and not any third party driver, just rules such as;
>$sudo cp efw.rules /lib/udev/rules.d
>Replug filter wheel
One option is to get the old version, meaning jessie+libindi_1.4.1, because I did not have any issue last year.
5 years 5 months ago #31748

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

  • Posts: 10
  • Thank you received: 0
I have also consulted ASI, and got shown below;
On my script is
indi_setprop "EFW.CONNECTION.CONNECT=On"
Correct property of connection is
indi_setprop "ASI EFW.CONNECTION.CONNECT=On"

All property need "ASI "
I am not sure why my wrong script did worked last year on my same board with jessie+libindi_1.4.1.
Anyway, it does work, and now I will try it on my RPi0W.

Thanks all.
5 years 5 months ago #31750

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

Time to create page: 0.894 seconds