When the profile is overwritten at start to overwrite the CC (Continuous Calibration) file, the default calibration file will also changed. This happens because (1) Some settings appear in both calibration.cal and profile.motive, and when settings are duplicated, they are internally aligned across each file according to the most recently loaded file (thus, if profile is loaded after cal and profile instructs motive to use CC-Continuous, then the calibration file CC setting is set to CC-continuous); and (2) Motive automatically save SystemCalibration.cal (and the profile) on closing the connection to the API (not on re-loading the calibration or profiles).
We don't want technicians to open up a file that has CC ON, since it will screw up the calibration. Possible Solutions include:
(1) Revert the SystemCalibration.cal file in the ProgramData/Optitrack/Motive/ directory back to its value before the RTLSServer was started.
(2) On closing RTLSServer, manually rewrite the SystemCalibration.cal file to change the number below back to its original value.
(3) Instruct technicians to load a different cal file from the Motive GUI on startup. This will still be problematic, because on startup, the default (CC-Cont) will be loaded.
(4) Re-load the old calibration file right before closing RTLSServer.. that way, there are no changes to the cal file.
(5) After the Motive API is disconnected, then overwrite the SystemCalibration.cal file (if it was used to load the calibration, or always?) with the last cal file that was saved --> Requires backing up this file on startup before anything is loaded.
.cal file line 277 shows what Continuous Calibration Setting is used based on the calibration file. The last number is { 30 = Disabled, 31 = Continuous, 32 = Continuous + Bumped }
003c 0076 0061 006c 0075 0065 003e 0030
When the profile is overwritten at start to overwrite the CC (Continuous Calibration) file, the default calibration file will also changed. This happens because (1) Some settings appear in both calibration.cal and profile.motive, and when settings are duplicated, they are internally aligned across each file according to the most recently loaded file (thus, if profile is loaded after cal and profile instructs motive to use CC-Continuous, then the calibration file CC setting is set to CC-continuous); and (2) Motive automatically save SystemCalibration.cal (and the profile) on closing the connection to the API (not on re-loading the calibration or profiles).
We don't want technicians to open up a file that has CC ON, since it will screw up the calibration. Possible Solutions include:
(1) Revert the SystemCalibration.cal file in the ProgramData/Optitrack/Motive/ directory back to its value before the RTLSServer was started.
(2) On closing RTLSServer, manually rewrite the SystemCalibration.cal file to change the number below back to its original value.
(3) Instruct technicians to load a different cal file from the Motive GUI on startup. This will still be problematic, because on startup, the default (CC-Cont) will be loaded.
(4) Re-load the old calibration file right before closing RTLSServer.. that way, there are no changes to the cal file.
(5) After the Motive API is disconnected, then overwrite the SystemCalibration.cal file (if it was used to load the calibration, or always?) with the last cal file that was saved --> Requires backing up this file on startup before anything is loaded.
.cal file line 277 shows what Continuous Calibration Setting is used based on the calibration file. The last number is {
30=Disabled,31=Continuous,32=Continuous + Bumped}