Closed lo-co closed 7 years ago
@JustinLangridge and @datid - this is the corresponding server side functionality requested on the client side in msr-consulting/exscalabar#76. This functionality has been put in for the initialization, but I need to note this:
Make sure to calculate the proper number of samples before hand so that you have an integer number (or test the functionality with non-integer numbers). So, what you want to know if samples per shot. This will be calculated as the acquisition rate (AI sample rate in Hz) divided by the laser rep rate and multiplied by the duty cycle.
Anyway, this is ready for some initial shaking out. Please test this with the lasers on and see if you get what you expect. Ask questions.
Matt, this appears to have caused issues - see attached screen shot. Changing the DC control still appears to have no effect
OK - so the problem of continual resets was related to the configuration of the red laser - we set up for taking 1250 samples but were only acquiring 500 per shot (was missing the DC value - 1250*0.4=500
).
The initialization issue appears to be gone and this works as expected if you do not change the laser rates.
Fixed issue associated with the above image. Once again, the changing of the rep rate was not accounting for the duty cycle properly. All appears well now.
This image was taken after changing the laser rep rate several times.
Added new VI to web service for changing the DC. Works. Sort of.
I consider this closed on both the client and the server. Below are images from a run today with resetting the DC.
Still have a problem - web service will not publish but will run. Likely something going on with one of the classes. Changed how I message the CRDS instrument via the Instrument Actor and did not workout.
Leading space in Update red DC - caused all sorts of publishing issues - now rectified.
This was hard coded (as well as the laser frequency).