acquisition-board icon indicating copy to clipboard operation
acquisition-board copied to clipboard

Acquisition freezing

Open stef1029 opened this issue 1 year ago • 6 comments

Hi,

When recording and streaming inputs from the ADC, with no headstage attached, it works for a while but then freezes and I get this error in the terminal streaming continuously until I stop the acquisition: [open-ephys] ERROR Error in Rhd2000EvalBoard::readDataBlock: Incorrect header.

Thanks for any help you can give, Stefan

stef1029 avatar Oct 16 '23 13:10 stef1029

Hi Stefan -- did you mean to close this issue? If not, it would be helpful to have a bit more info:

  • Are you using the OE FPGA Acquisition Board plugin (compatible with boards purchased in the past year from the Open Ephys store), or the Acquisition Board plugin (compatible with boards that use an Opal Kelly FPGA)?
  • Do you ever see the same issue when a headstage is connected?
  • Is there anything else hooked up to your computer's USB ports (besides mouse and keyboard) during data acquisition?

jsiegle avatar Oct 16 '23 16:10 jsiegle

Hi,

I closed it as I thought it was more appropriate to write it on the plugin-gui repository. I'm using an older Opal Kelly FPGA, with the rhythm data plugin. I'll do those tests to see if there's still an issue with the headstage plugged in and test whether another USB device is causing an issue though and get back to you.

stef1029 avatar Oct 19 '23 15:10 stef1029

Hi, I've tried again with a headstage plugged in and can't seem to replicate the error with the headstage or without. It may well be an issue from another USB device, although not sure. I'll write here again if the error comes back but for now it seems to have gone.

stef1029 avatar Oct 24 '23 15:10 stef1029

Ok, thanks for the update!

jsiegle avatar Oct 24 '23 16:10 jsiegle

Hi again,

It looks like the issue is still there. With a headstage plugged in and recording from the adc channels I got the same error about half an hour into a recording. I'd previously run lots of recordings with no issue before that, and this seemed random that it popped up again so really got no clue what's causing it, but am cautious to start any major experiments until there's some indication of what might be happening as it results in lost data.

Thanks for any help you can give

stef1029 avatar Dec 11 '23 13:12 stef1029

Do you have another power supply unit available (5V DC)? We've seen problems like this crop up in the past when the power supply was faulty. Switching the USB cable may help as well (and double-check that it's connected to a USB3-compatible port).

jsiegle avatar Dec 11 '23 21:12 jsiegle