You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The detector tells when recordings are started and stopped, both in the log files and in the user interface. But the reason for this is not logged. Reasons may be that the user changed detector mode or that the scheduler activates/deactivates recording. This kind of information is useful when preparing the reports after a survey, as well as for debug purposes.
The main control loop for this is located in the Scheduler section and every 10 seconds it is checked whether recording is to be activated or deactivated.
The text was updated successfully, but these errors were encountered:
The detector tells when recordings are started and stopped, both in the log files and in the user interface. But the reason for this is not logged. Reasons may be that the user changed detector mode or that the scheduler activates/deactivates recording. This kind of information is useful when preparing the reports after a survey, as well as for debug purposes.
The main control loop for this is located in the Scheduler section and every 10 seconds it is checked whether recording is to be activated or deactivated.
The text was updated successfully, but these errors were encountered: