Closed stillwer closed 5 years ago
The problem seems to be that the way the programs talk through the MCS Command Queue. MCS Controls can not find the reference to the queue to stack in the starting sequence...and without the starting sequence the MCS will not receiver command input. MCS code version 2 fixes this problem by forcing all MCS program functionality into a single program so no reference to be lost.
When tying to port the MCS code over to windows 10, the link between the MCS and MCSControls seems to be broken. I noticed this when trying to get Catharine setup on labview. Not sure what is wrong but it can be fixed by setting the state of the MCS using Brad's old code then running just the MCS reading program. That is obviously not a long term fix.