Started the day by analyzing results of 07_14_14_21_47_40_TargetRun which ran overnight

These used the same maps as the previous two tests but with no updating (which was turned on for the previous test 07_14_14_08_25_24_TargetRun). Motor maps were verified the same for all three tests. The performance was different for the test with updates on but not in an obviously meaningful way.

There was some confusion as to why the timestamps on the binary databse files used by MSIM had been changed to more recent ones than matched the xml which was believed to be loaded in there. Talking to Hrand and Charlie it sounds like this was the result of reloading and resaving the same xml during some debug. The MSIM databases were dumped and motor maps spot checked to ensure they were the same and they were.

070914_set3_allmaps_adj4 was loaded into MSIM and saved and then MSIM was restarted.

Motors were connected and the target script 2014_07_09_TargetsEMSetC_no7 was rerun to get a third test with the above map to directly compare with the test 07_11_14_19_29_30_TargetRun. When this finished, the results did not match as expected. Specifically PIDs 5, 6, and 8 did worse in the new run. The rest were very similar to the original test a few days prior.

PID8 Debug

Closed MSIM and Opened up pathway software. Moved several motors to figure out which ones was PID8 theta. Then went to axis properties and recorded the current drive frequency to be 59.524kHz. Opened up the sweep window and did several sweeps only to see flat curves. Realized that this was because the sweep window settings were incorrect, not sure why. Consulted the NST delivery documentation and used their sweep settings for this motor and achieved a similar result to the documentation, 62.81kHz. Not sure why we swept different frequencies to begin with from NST had in their documentation.

Kept PID8 with it's 59.524kHz since that is what all our current calibration has been done with.

PID7 Debug

Reran all of the ontime scripts to get ontime for PID7.