Rpi: 4B 4GB
RC HAT
OS: Bullseye 64 bit
DC: 5.0.0dev (tf_2_9 branch)
AUTO_RECORD_ON_THROTTLE = True
When running manage.py drive the data recording starts right at the pull of the throttle trigger on the RC Controller and the "Start Recording" tab in webui switches to "Stop Recording" as expected.
However, when I release the throttle trigger on the RC Controller, the data recording continues on and does not stop until I click the "Stop Recording" tab in the webui which then switches to "Start Recording".
When manage.py drive starts the CLI displays "Recording = False" until I pull the throttle trigger on the RC Controller at which time "Recording = True".
When I release the throttle trigger on the RC Controller, "Recording" should return to "False", but does not do so until I click the "Stop Recording" tab in the webui at which time the CLI displays "Recording = False".
I called the myconfig.py file myconfig.docx so I could upload it so rename it to myconfig.py to view it when you download it.
Rpi: 4B 4GB RC HAT OS: Bullseye 64 bit DC: 5.0.0dev (tf_2_9 branch)
AUTO_RECORD_ON_THROTTLE = TrueWhen running
manage.py drivethe data recording starts right at the pull of the throttle trigger on the RC Controller and the "Start Recording" tab in webui switches to "Stop Recording" as expected. However, when I release the throttle trigger on the RC Controller, the data recording continues on and does not stop until I click the "Stop Recording" tab in the webui which then switches to "Start Recording". Whenmanage.py drivestarts the CLI displays "Recording = False" until I pull the throttle trigger on the RC Controller at which time "Recording = True". When I release the throttle trigger on the RC Controller, "Recording" should return to "False", but does not do so until I click the "Stop Recording" tab in the webui at which time the CLI displays "Recording = False".I called the
myconfig.pyfilemyconfig.docxso I could upload it so rename it tomyconfig.pyto view it when you download it.TCIII myconfig_Slash_N2..docx