The log file for the position of the scan needs to know where the motor position is. There is no way for the hardware module to know when the scan is done.
When does this occur?
After every scan.
Where on the platform does it happen?
Confocal - During scan.
How do we replicate the issue?
Do a scan with NF_screws.
Expected behavior (i.e. solution)
When the scan finishes it should call a function in the hardware module which logs the final position after a scan.
Other Comments
I can make something in the Hardware Module so that qudi just needs to send a DONE tag to the motorinterfuze which will communicate to the hardware module and activate the log script.
Question
Should I make two log files. One that does software log during scan and one that does hardware log?
What is affected by this bug?
The log file for the position of the scan needs to know where the motor position is. There is no way for the hardware module to know when the scan is done.
When does this occur?
After every scan.
Where on the platform does it happen?
Confocal - During scan.
How do we replicate the issue?
Do a scan with NF_screws.
Expected behavior (i.e. solution)
When the scan finishes it should call a function in the hardware module which logs the final position after a scan.
Other Comments
I can make something in the Hardware Module so that qudi just needs to send a DONE tag to the motorinterfuze which will communicate to the hardware module and activate the log script.
Question
Should I make two log files. One that does software log during scan and one that does hardware log?