Incorrect amplitudes in output data from measurement computing DAQ, Bonsai crashing and not recording #1239
Unanswered
cameycalzolano
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all -
I am using a measurement computing DAQ (USB-205). My workflow at this point is pretty basic - I am using the AnalogInput sink (included in the MccDaq library that I have installed) to record 3 different channels connected to a MatrixWriter node (the DAQ is used to record TTL pulses generated by a med associates operant chamber). I have also added a timer connected to a WorkflowOutput node to stop the sequence automatically after a fixed amount of time.
I am running into a few problems:
1 - Bonsai often doesn’t record the data. Most of the time, if Bonsai is started before starting the operant chamber, the output .bin file is 0KB. If I start the Bonsai workflow after starting the operant chamber, it almost always records the data (but this is not feasible for the actual experiment).
2 - Bonsai often crashes while running the workflow. Note that we are using Bonsai32 as it is the only version of Bonsai compatible with the driver (CL eye multicam driver) that we will be using for our cameras (PS3Eye Camera).
3 - The amplitude of the output is not what we expect. While they should be between 0 and 5, they are between 2000 and 3000. I am using the following matlab code to extract data from the bin file (also note that the layout for MatrixWriter is set to “ColumnMajor”):
fileID = fopen(‘fileName.bin’)
numChannels = 3
A = fread(fileID, [numChannels, Inf], ‘uint16’)
If it is more helpful, I can open up separate questions, but wanted to have them all together with the setup in case they are all related.
Any input is much appreciated. Thank you!
![MccDaqtest-Workflow](https://user-images.githubusercontent.com/114766484/215906799-219f76b2-3ad1-4c30-b072-436507f70b9a.PNG)
Beta Was this translation helpful? Give feedback.
All reactions