Problem Connecting to Dynap-se

[Andrew Hansen]

Hi all,

I was running tests through pyNCS on Dynap-se yesterday, in the middle of one of the tests, I noticed some odd behavior in SpikeView, so I closed down cAER, unplugged the Dynap-se from it's USB port (from the computer side), and booted everything back up again. Now, everytime I try to connect via cAER, it repeats this error message (and won't connect):

"ERROR: Dynap-se ID-1: USB device address restriction is present (142), this device didn't match it (8).

CRITICAL: Dynap-se ID-1: Failed to open device."

I've tested the USB ports, rebooted the computer, and rebuilt cAER from clean, though this problem persists. I'm running Arch Linux. Does anyone have any experience with this issue, and/or perhaps some advice on the matter?

Best,

Andrew

[carsten.nielsen]

Hi Andrew,

Can you post the output of dmesg and lsusb 5-10 seconds after plugging in the device?

libcAER can be made to match devices based on which USB device ID they are given. This changes every time you plug it into a port. Are you using the device restriction feature of libcAER in any way?

Best,

Carsten

[Andrew Hansen]

Hi Carsten,

Thanks for the reply. I haven't explicitly imposed any restrictions, but will ask the person who installed it on the lab computer. The strange aspect of this error is that dmesg still shows the dynapse when connected to other computers, but not on the lab computer that I've been running it on. I haven't changed anything, and it seems to have happened somehow during an unplug-reset in the middle of running tests with pyNCS. I don't understand why.

Best,

Andrew