end of experiment being truncated on ecube

the final event code and between 20-30 clock cycles are consistently being truncated from the end of the experiment in the ecube digital recordings.

my theory: when we command servernode to end the recording, it hasn't yet received those 20-30 cycles, due to a ~150ms delay probably due to latency between the ecube and servernode.

solution: introduce at least that much delay at the end of the experiment before commanding the ecube to stop recording. better solution: have whitematter introduce a feature that triggers recording start/stop on a given digital input