×

INDI Library v1.9.3 Released (11 Nov 2021)

Bimonthly Stable INDI Library release introduces new drivers and fixes for existing ones. Some highlights:

CCDceil usb 2-1.2.3.3: reset high-speed USB device number 45 using ehci-pci

  • Posts: 26
  • Thank you received: 4
Last night I set up with my AT6RC and ASI1600mm for the first time in a long time. I have an ASI174mm mini for a guide imager. Things seemed okay at first, and polar alignment went smoothly.

I'm running on an old laptop (Thinkpad T420s) running Ubuntu 20.04.

Then, I started getting various USB errors. I would lose my connection to the scope. I would lose my connection to the main camera. I would have to unplug everything and restart. Eventually I tailed syslog and saw a constant stream of usb reset  messages. Once those started, everything would go downhill rapidly.
roland@astro-02:~$ lsusb
Bus 002 Device 004: ID 17ef:1003 Lenovo Integrated Smart Card Reader
Bus 002 Device 003: ID 8086:0187 Intel Corp. 
Bus 002 Device 046: ID 0403:6015 Future Technology Devices International, Ltd Bridge(I2C/SPI/UART/FIFO)
Bus 002 Device 042: ID 2109:2817 VIA Labs, Inc. 
Bus 002 Device 045: ID 03c3:1749  
Bus 002 Device 044: ID 03c3:1f01  
Bus 002 Device 043: ID 03c3:1604  
Bus 002 Device 041: ID 04b4:6572 Cypress Semiconductor Corp. Unprogrammed CY7C65642 hub
Bus 002 Device 040: ID 2109:2817 VIA Labs, Inc. 
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1)
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

device 45 is unnamed, so I had to dig a bit
Bus 002 Device 045: ID 03c3:1749  
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x03c3 
  idProduct          0x1749 
  bcdDevice            0.00
  iManufacturer           1 ZWO
  iProduct                2 ASI174MM Mini
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
  ...

Unfortunately, I didn't check the other times to verify it was only and always this device. I'll try some daytime connectivity testing to see if I can figure this out, or maybe try again tonight and leave that 174mm unplugged to see if it's only that. The 174m was plugged in at times to a USB hub, and at other times (when I captured the above) to my ASI1600mm. 

The only thing close to this I've found was here: github.com/indilib/indi/issues/950 and that was two years ago and doesn't have a clear resolution (nor is it clear to me it's the same thing except for the general USB reset symptom).

Any suggestions besides trying again? I do have second laptop with the same set of software I can try, and I can swap out cables. I had already tried various USB ports on the laptop and swapped out the main USB cable but that was before I found the link to the 174mm; I'll try to reproduce this and then swap out those cables.
2 months 2 weeks ago #75430

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

  • Posts: 212
  • Thank you received: 14
smeird commented on 13 Jun 2019
I received this from ZWO support , the reset is deliberate

I checked the videos, but not very understand.
For the reset, now I am sure there is a reset, and I checked our program again, find it this time. This reset is used to resolve internal device exceptions. For example, the last time a unknown problem occurred, the device was not released, and the next time you use it again, the device will be busy. With this function reset, the device can be released, ensuring the next normal transmission. I am sure the reset you find in the log is this. For this reset, we just reset our device. It will not affect other devices.

github.com/indilib/indi/issues/950#issuecomment-501602832
2 months 2 weeks ago #75434

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

  • Posts: 34
  • Thank you received: 28
Hi !

I can confirm the asi driver will generate these reset messages in kernel logs, probably for every exposure, and that is totally armless. So it's probably not the cause or a symptom of your problem !
You should try without any hub...
2 months 2 weeks ago #75437

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

  • Posts: 26
  • Thank you received: 4
Well, that's not a happy thing to hear :-( Because the only other references to this slew of failures I can find suggest an issue with the USB controller on the motherboard of my laptop. 

I think I can try without a hub by using the ASI2600mm as a hub for the filter and guider then a different cable direct to my laptop for the scope. I'll give that a try this evening. 

Thanks
roland
 
2 months 2 weeks ago #75441

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

  • Posts: 26
  • Thank you received: 4
Well, that turned out okay after all. I dropped the hub and connected directly to the mount and ASI1600 using that latter as the hub for the filter wheel and guider. I did continue to get USB resets, as you said, on every exposure, but nothing every locked up or failed and I wasn't forced to power cycle or physically reconnect anything.
so I guess I'll need a new hub it I want to move further away from my mount.

I have to say that this still feels. wrong. It sounds like either there's an issue with the ZWO driver or the API isn't being used correctly because I can't see how normal, correct use should result in a device reset on every exposure :-/

roland
​​​​​​​
2 months 2 weeks ago #75480

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

Time to create page: 0.572 seconds