horaceCJ
Active Member
- Joined
- Mar 15, 2013
- Messages
- 197
- Reaction score
- 210
- Country
- Romania
- Dash Cam
- Mobius A/B/C / 808 #16D
I saw somebody else was interested in the subject, so I'm starting a new thread with my tests results and some details of the way this feature works.
My configuration was:
- FW v1.13
- Motion Detect: On
- Motion Sensitivity: High
- Motion Timeout: 60s
- Video Data Rate: Standard
- Video Clip Length: 3 Mins.
- Power Off Disconnect: Immediate
I think these are enough for what I'm writing below.
Recording delay is between 1.33 and 2 seconds. The camera was in stand-by and I started my windscreen whipers (single cycle). Their movement started the recording but it didn't show in the video. Starting another whiping I counted that one cycle is 40 frames long (~1.33 seconds). The upper limit (2 seconds) is a guesstimate.
Sensitivity: I parked the car in a mall and noticed the following (see attachment motion detect sensitivity.jpg):
- motion in green area (10 meters, even pedestrians) started the recording
- motion in smaller (red) areas didn't start the recording
- (from another scene) pedestrian in front of the car (on the edge of the picture) will not start recording if he's just moving his head
Continous driving and recording:
I drove for 45 kilometers in daylight and I got 42:18 minutes of continous recording in 14 files with 1 second overlap (see atachment motion detect 42 minutes.jpg). Two of the files were 3:03 long, I don't know why, but I noticed that from time to time in the last FW too (12*3:01 + 2*3:03 = 42:18). I drove for few minutes on a foggy motorway (the only motion was the road paitings and parapets) and I had only one red traffic light for about 70 seconds, but recording was kept alive by other cars passing by.
Recorded files:
The recording will allways last a specified time (Motion Timeout) from the last detection of a motion. Examples (for 60 seconds timeout and 3 minutes clips):
- single file of 2:20 > last motion was detected at 1:20
- two files 3:01 and 0:30 > last motion was detected at 2:30 and until then other motions were detected at least one per 60 seconds
Power off disconnect - for me it seems like a bug, someone reported it also in the RC forum:
- camera is recording and the power is cut: nothing happens (I suppose the camera will remain in motion detect mode until the battery runs out)
- camera is not recording (waiting for movement) and the power is cut: the camera shuts down (according to Power Off Disconnect parameter)
That's it at the moment, hope it clarifies the way it works. I'll keep the configuration for few days to see how it works in city and night driving.
Edit (03.01.2013): The Power Off Disconnect bug was reported to the developer thanks to Isoprop and Tom Frank.
My configuration was:
- FW v1.13
- Motion Detect: On
- Motion Sensitivity: High
- Motion Timeout: 60s
- Video Data Rate: Standard
- Video Clip Length: 3 Mins.
- Power Off Disconnect: Immediate
I think these are enough for what I'm writing below.
Recording delay is between 1.33 and 2 seconds. The camera was in stand-by and I started my windscreen whipers (single cycle). Their movement started the recording but it didn't show in the video. Starting another whiping I counted that one cycle is 40 frames long (~1.33 seconds). The upper limit (2 seconds) is a guesstimate.
Sensitivity: I parked the car in a mall and noticed the following (see attachment motion detect sensitivity.jpg):
- motion in green area (10 meters, even pedestrians) started the recording
- motion in smaller (red) areas didn't start the recording
- (from another scene) pedestrian in front of the car (on the edge of the picture) will not start recording if he's just moving his head
Continous driving and recording:
I drove for 45 kilometers in daylight and I got 42:18 minutes of continous recording in 14 files with 1 second overlap (see atachment motion detect 42 minutes.jpg). Two of the files were 3:03 long, I don't know why, but I noticed that from time to time in the last FW too (12*3:01 + 2*3:03 = 42:18). I drove for few minutes on a foggy motorway (the only motion was the road paitings and parapets) and I had only one red traffic light for about 70 seconds, but recording was kept alive by other cars passing by.
Recorded files:
The recording will allways last a specified time (Motion Timeout) from the last detection of a motion. Examples (for 60 seconds timeout and 3 minutes clips):
- single file of 2:20 > last motion was detected at 1:20
- two files 3:01 and 0:30 > last motion was detected at 2:30 and until then other motions were detected at least one per 60 seconds
Power off disconnect - for me it seems like a bug, someone reported it also in the RC forum:
- camera is recording and the power is cut: nothing happens (I suppose the camera will remain in motion detect mode until the battery runs out)
- camera is not recording (waiting for movement) and the power is cut: the camera shuts down (according to Power Off Disconnect parameter)
That's it at the moment, hope it clarifies the way it works. I'll keep the configuration for few days to see how it works in city and night driving.
Edit (03.01.2013): The Power Off Disconnect bug was reported to the developer thanks to Isoprop and Tom Frank.
Last edited: