Replies: 6 comments 1 reply
-
part of it might have been a COM port issue (not being closedor something like that). After rebooting the computer, I can have the 3 device connected to the USB at the same time. But the issue remains once I connect the clock cables. The analog input device seems to work as expected (sending messages with a harp clock timestamp that has now a low value) while the behaviour device does not emit any messages anymore. |
Beta Was this translation helpful? Give feedback.
-
A couple of questions to try to identify the issue:
|
Beta Was this translation helpful? Give feedback.
-
Hi,
If I connect only the clock synchronizer, start bonsai and double click on the clock synchroniser device, I never get the connection. The bottom of the window displays "Connecting to device..." forever. |
Beta Was this translation helpful? Give feedback.
-
A screenshot in case it helps: The bonsai console is also empty. |
Beta Was this translation helpful? Give feedback.
-
Taking into account what you've described it seems that somehow the device firmware got corrupted and/or the device got damaged. You can try to update the firmware and see if it works
You should now be able to see after the initial LED burst, the LED toggling after a couple of seconds. If not, or if the firmware update fails I would suggest you to request an RMA to replace the clock synchronizer board. |
Beta Was this translation helpful? Give feedback.
-
It seems that there is another issue. I got this error message: I'll write to eops to see how I can get it fixed. |
Beta Was this translation helpful? Give feedback.
-
I'm not exactly sure what my issue is. I have a analog input device and a behaviour device. Both of them work fine but have different harp clock (as expected). I got a clocksynchronizer to solve that but when I connect the clock synchronizer the behaviour device is not detected anymore.
In bonsai the workflow runs but does not emit anything. In the behaviour GUI, only the analog input appears in the list of connected devices.
I tried to disconnect all the clock jack cables (powering eveything down before doing so) and connect only the usb cables. That already triggered the issue. If I have usb/power cables connected to both the behaviour and analog device everything work. As soon as I connect the clock synchronizer the behaviour device disappears (but the analog device still works).
Is it likely to be a hardware issue? A missing driver? Or is there maybe a bonsai step that I need to run to start the synchroniser which I forgot (and my behaviour device is stuck waiting for a clock signal)?
Beta Was this translation helpful? Give feedback.
All reactions