The aq. boards can be daisy-chained with the .1" ribbon cable at the back. Each board has an IN and an OUT pin right now, with a small impedance matching resistor and pull-down.
The simplest way to do this should be to set each board into slave mode or leave it in default.
In default mode, the board sets the OUT pin high as long as data is being acquired.
In slave mode, the user selects a file path, config etc, and starts acquiring data as usual, but the firmware state machine is stopped until the IN pin goes high, and stops again as it goes low.
The main question is whether extra synchronization is needed. If so, then a TTL in/out channel could be used to send periodic sync. signals that we can then use in software to make everything sample perfect.
The aq. boards can be daisy-chained with the .1" ribbon cable at the back. Each board has an IN and an OUT pin right now, with a small impedance matching resistor and pull-down.
The simplest way to do this should be to set each board into slave mode or leave it in default.
In default mode, the board sets the OUT pin high as long as data is being acquired.
In slave mode, the user selects a file path, config etc, and starts acquiring data as usual, but the firmware state machine is stopped until the IN pin goes high, and stops again as it goes low.
The main question is whether extra synchronization is needed. If so, then a TTL in/out channel could be used to send periodic sync. signals that we can then use in software to make everything sample perfect.