...
I had issues setting up the summit keysight electrometer. The This issue was solved by writing a usdev rule.
The instructions for setting up a key sight electrometer were updated on the wiki page.
A failed attempt to implement an asynchronous script to measure the mount position while acquiring the electrometer data.
Mount: script to slew up in elevation, take stop in five measurements positions along the way, then slew to the right in azimuth, slew down in elevation, and take 5 five measurements. Each slew had a fixed amount of secondsperiod, e.g. 5 sec.
Second day:
Mount: The script to start starts at Alt=80deg then do a slew and slews down for four points. Come Then, it comes back to Alt=80 and slew slews down again. Here, I improved the algorithm by measuring what is the expected
Lessons learned
The async code is actually harder than I thought I should make a simple algorithm.
Slewing for a fixed period moving to a given alt and az.
The mount resets the zero point after the second consecutive slew. The function
goto_elevation
estimates the slew time and re-iterates up to the desired position.I could map the room using the first day method of slewing to a given slew time. The slew speed was not constant.
TBD (observation)
Lessons learned about the mount
Slewing for a fixed time is not repeatable. The mount does not always comeback come back to the same position.
The zero-point can be reset when I slew with the goto_elevation function. The reason is still unknown.
There is a delay after stopping the mount that should be quantified.
The async code is actually harder than I thought I should make a simple algorithm.
Lessons learned about the electrometer
TBD