Closed lo-co closed 7 years ago
@JustinLangridge So this was initially intended to maintain the state of the system before the calibration started. It is unclear to me whether the system was storing the state properly, but I assumed it did. So it could have been that the system was always running in sample mode when a calibration kicked off. I have removed the filter state requirement and now the Calibration Actor
sends a Change Filter State MSG
with the packet set to TRUE
.
So, just to be clear, the sequence is
In addition, the CVT value calibration.cal_state = 0
.
Currently it seems that the system goes to sample at the end of a calibration.