Is this an Encoder failing?

[nm17]

I recently started seeing these messages intermittently in the logs - could you please confirm if this indicate the device is failing or if it could be something else as well?

Code: Select all

2026-03-18T14:49:36.968  <Info> phidget22usb[AttachUSBDevice()] : Attaching Phidget | Path: \\?\usb#vid_06c2&pid_0046#751486#{ddc0b225-2263-4835-aa6e-55f8b77788fe} | PDO Name: \Device\USBPDO-18 | Hub Port: 2
2026-03-18T14:49:36.968  <Warn> phidget22usb[AttachUSBDevice()] : GetDescriptor USB_STRING_DESCRIPTOR_TYPE failed with error code: 0x0000001f - A device attached to the system is not functioning.

I also had these which are probably related

Code: Select all

2026-03-18T15:04:45.174 <ERROR> phidget22vint[PhidgetHubDevice_updatePortProperties()] : Couldn't read VINT Port 2 descriptor from: HUB0002 (6-Port USB VINT Hub Phidget) v101 S/N:751486
2026-03-18T15:04:45.179  <Info> phidget22usb[PhidgetUSBGetDeviceDescriptor()] : GetDescriptor failed with STALL or other error.

It is fairly hard to reproduce reliably and/or debug due to the nature of system/software and the intermittent nature of it happening.

Port 2 is an Encoder (ENC1000 with rotary encoder HTK22 attached to it) - it fills a little unusual that Encoder is failing intermittently but I guess there is a probability for everything.

Could you please confirm?

[Patrick]

This can sometimes happen while a device is being plugged in or unplugged. It can also happen if multiple Phidget programs are open at once (control panel and network server and your app for example). In those cases, it's nothing to worry about, the library just tries again. It could also happen at system sleep/wake. In general it's probably nothing to worry about unless you're actually seeing errors in your program, missing data, etc.

-Patrick