rcg530
Well-Known Member
- Joined
- Jan 23, 2021
- Messages
- 853
- Reaction score
- 1,185
- Location
- California
- Country
- United States
- Dash Cam
- BlackVue, Blueskysea, VIOFO, Vantrue, Thinkware
I started my pre-review checks of the two FineVu GX1000 dash cameras that I was sent by Finedigital. I started gathering power consumption data for the GX1000 and noticed a few issues with the four available parking modes. Before that, I noticed that FineVu app (android) did not notify me of an update being available for the GX1000.
My two GX1000 dash cameras came with firmware v1.00.001. The FineVu website has v1.00.002 available for download. I downloaded and installed firmware version v1.00.002.
File System on MicroSD Card
When an empty (not yet initialized by FineVu GX1000) microSD card is used, the boot up process will state it is initializing the microSD card's file system and after that completes the GX1000 reboots. The file system contents after the initialization looks like this:
Normal mode recording files are placed in the "normal" directory. The video files created by the GX1000 are AVI video files which has the front video, rear video and a mono audio track.
Normal mode filename example: 20230305-14h01m29s_FR_N.avi
The "FR" in the filename means that this video file has the "F"ront and "R"ear video contents in the video file. Most video players will only play/access the first video track which is the front video file. My video editing program (Adobe Premiere Pro) cannot access video track two (rear video), so I created a Bash shell script that uses the ffmpeg utility to copy front video track (track 0) and the audio track (track 2) to its own AVI file. I then use ffmpeg again to extract the rear video track (track 1) and audio track (track 2) to its own AVI file so I can access both the front and rear video within my video editing program.
Parking Modes
Within the FineVu app, you can select one of four available parking mode types.
(F) = Front, (R) = Rear
My two GX1000 dash cameras came with firmware v1.00.001. The FineVu website has v1.00.002 available for download. I downloaded and installed firmware version v1.00.002.
File System on MicroSD Card
When an empty (not yet initialized by FineVu GX1000) microSD card is used, the boot up process will state it is initializing the microSD card's file system and after that completes the GX1000 reboots. The file system contents after the initialization looks like this:
Normal mode recording files are placed in the "normal" directory. The video files created by the GX1000 are AVI video files which has the front video, rear video and a mono audio track.
Normal mode filename example: 20230305-14h01m29s_FR_N.avi
The "FR" in the filename means that this video file has the "F"ront and "R"ear video contents in the video file. Most video players will only play/access the first video track which is the front video file. My video editing program (Adobe Premiere Pro) cannot access video track two (rear video), so I created a Bash shell script that uses the ffmpeg utility to copy front video track (track 0) and the audio track (track 2) to its own AVI file. I then use ffmpeg again to extract the rear video track (track 1) and audio track (track 2) to its own AVI file so I can access both the front and rear video within my video editing program.
Bash:
#!/bin/bash
# Extract front camera video with audio
ffmpeg -i $1 -map 0:0 -map 0:2 -vcodec copy -acodec copy ${1%.*}_front.avi
# Extract rear camera video with audio
ffmpeg -i $1 -map 0:1 -map 0:2 -vcodec copy -acodec copy ${1%.*}_rear.aviParking Modes
Within the FineVu app, you can select one of four available parking mode types.
(F) = Front, (R) = Rear
- Motion
- No Motion within the field of view
- No video files are created
- Motion within the field of view
- 2560x1440 30fps combined Front/Rear H.264 AVI
- Stored in "motion" directory - File basename suffix "_M"
- 2560x1440 30fps 15.66 Mbps (F) + 2560x1440 30fps 15.66 Mbps (R)
- Buffered: 20 Seconds Total = 10 seconds before / after triggering motion
- Impact event
- 2560x1440 30fps combined Front/Rear H.264 AVI
- Stored in "parking" directory - File basename suffix "_P"
- 2560x1440 30fps 15.66 Mbps (F) + 2560x1440 30fps 15.66 Mbps (R)
- Buffered: 20 Seconds Total = 10 seconds before / after triggering impact
- Returning to normal recording mode.
- FineVu has stated this parking mode should announce the number of events that took place in this parking mode.
- My testing has found this parking mode does not announce the number of events.
- No Motion within the field of view
- Smart Time Lapse
- Continuously records 20 second videos
- 2560x1440 30 fps combined Front/Rear H.264 time-lapse video files
- Stored in "motion" directory - File basename suffix "_M"
- Front/rear video is recorded at 2 fps - No audio is recorded
- Each 20 second time-lapse video file equals 5 minutes of wall clock time
- The smart time lapse videos are not interrupted by an impact event.
- Both the smart time lapse and impact video files are written to the microSD at the same time.
- Impact event
- 2560x1440 30fps combined front/rear H.264 AVI file
- Stored in "parking" directory - File basename suffix "_P"
- 2560x1440 30fps 15.66 Mbps (F) + 2560x1440 30fps 15.66 Mbps (R)
- Buffered: 20 Seconds Total = 10 seconds before / after triggering impact
- Returning to normal recording mode.
- FineVu has stated this parking mode should announce the number of events that took place in this parking mode.
- My testing has found this parking mode does not announce the number of events.
- 15 FPS
- No Motion
- No video files are created
- With Motion Within The Field Of View
- 2560x1440 15fps combined Front/Rear H.264 AVI
- Stored in the "motion" directory - File basename suffix "_M"
- 2560x1440 15fps 11.76 Mbps (F) + 2560x1440 15fps 11.76 Mbps (R)
- Buffered: 20 Seconds Total = 10 seconds before / after triggering motion
- Impact Event
- 2560x1440 15fps combined Front/Rear H.264 AVI
- Stored in the "parking" directory - File basename suffix "_P"
- 2560x1440 15fps 11.76 Mbps (F) + 2560x1440 15fps 11.76 Mbps (R)
- Buffered: 20 Seconds Total = 10 seconds before / after triggering impact
- Returning to normal recording mode.
- FineVu has stated this parking mode should announce the number of events that took place in this parking mode.
- My testing has found this parking mode does not announce the number of events.
- No Motion
- Power Saving [Parking Mode]
- This is a low power consumption parking mode
- When the accessory power is switched off
- GX1000 enters into a surveillance mode for a 70 to 75 second period.
- This surveillance mode will look for motion within the field of view and if present, a 20 second motion video files are created.
- 2560x1440 30fps combined Front/Rear H.264 AVI
- Stored in "motion" directory - File basename suffix "_M"
- 2560x1440 30fps 15.66 Mbps (F) + 2560x1440 30fps 15.66 Mbps (R)
- Buffered: 20 Seconds Total = 10 seconds before / after triggering motion
- The somewhat odd behavior of this mode is that if the motion is continuous, each motion video file will contain overlapping video/audio
- Second count is the number of seconds since the accessory power was turned off
- Motion file 1 contains – seconds 10 to 30
- Motion file 2 contains – seconds 21 to 41
- Motion file 3 contains – seconds 32 to 52
- Motion file 4 contains – seconds 43 to 63
- Motion file 5 contains – seconds 54 to 74
- This surveillance mode will look for motion within the field of view and if present, a 20 second motion video files are created.
- After the initial surveillance mode finishes, the GX1000 goes into low power consumption mode (4 mA / 0.05 Watts) waiting for an impact event to occur.
- When an impact event occurs
- The GX1000 powers up and starts recording an impact video file.
- The power up steps takes on average 5.6 seconds (not the 1.9 seconds as stated on the FineVu website).
- Video info
- 2560x1440 30fps combined front/rear H.264 AVI file
- Stored in "parking" directory - File basename suffix "_P"
- 2560x1440 30fps 15.66 Mbps (F) + 2560x1440 30fps 15.66 Mbps (R)
- 20 second impact recording is created.
- After 20 seconds, GX1000 enters a post-impact surveillance mode
- The GX1000 powers up and starts recording an impact video file.
- Post-Impact Surveillance Mode
- GX1000 remains in surveillance mode for up to 66 seconds if motion is detected and 61 seconds if no motion is detected
- If motion is present while in post-impact surveillance mode:
- Each “Motion” video file is 20 seconds in length.
- If motion is continuous during this time period, the “Motion” video files will contain overlapping video/audio content.
- My test involved having motion visible to the front and rear video cameras during and after the impact event that created the impact video file.
- Impact video file contains seconds 1 to 20 for this test example:
- Motion file 1 contains – seconds 12 to 32
- Seconds 12 to 20 overlap with the parking mode impact video recording.
- Motion file 2 contains – seconds 22 to 42
- Motion file 3 contains – seconds 33 to 53
- Motion file 4 contains – seconds 44 to 64
- Motion file 5 contains – seconds 55 to 75
- Motion file 6 contains – seconds 66 to 86
- Motion file 1 contains – seconds 12 to 32
- AVI video files are 30 FPS video files.
- Video Info
- Stored in the “motion” directory with file basename suffix “_M"
- Front: 2560x1440 30 fps, H.264, 15.66 Mbps data rate
- Rear: 2560x1440 30 fps, H.264, 15.66 Mbps data rate
- Audio is recorded.
- Video Info
- The FineVu website states the post-impact surveillance mode is 40 seconds in length, but my testing shows otherwise.
- When the post-impact surveillance mode has completed, the GX1000 returns to the low power state waiting for the next impact.
- Exiting “Power Saving” parking and returning to “Normal” recording mode
- When accessory power is restored, the GX1000 will exit power saving mode and return to normal recording mode.
- Announcements made:
- If one or more impacts took place during power saving mode
- Announcement: “Impact detection record, ‘Number’”
- If one impact event took place: “Impact detection record, one”
- Announcement: “Impact detection record, ‘Number’”
- If one or more motion events took place during the power saving surveillance mode(s):
- Announcement: “Motion detection record, ‘Number’”
- My testing had over ten events, so the GX1000 stated “Motion detection record, over 10”
- Announcement: “Motion detection record, ‘Number’”
- If one or more impacts took place during power saving mode
- Announcements made:
- When accessory power is restored, the GX1000 will exit power saving mode and return to normal recording mode.
- GX1000 enters into a surveillance mode for a 70 to 75 second period.
Last edited:
