rcg530
Well-Known Member
- Joined
- Jan 23, 2021
- Messages
- 1,543
- Reaction score
- 2,582
- Location
- California
- Country
- United States
- Dash Cam
- BlackVue, Thinkware, VIOFO, Vantrue, Blueskysea, FineVu
In my thread for my review of the DR750X-3CH Plus dashcam, I posted about an issue I've been having with the DR750X-3CH Plus and two different DR750X-2CH Plus dashcam.I've been testing the DR750X-3CH Plus along with a DR750X-2CH Plus dashcam in my vehicle for a while now. Recently, I connected my CM100LTE connectivity device to the DR750X-3CH Plus using the USB hub included in the DR750X-3CH Plus box.
While reviewing video, I was seeing a large number of normal mode driving impact events ( _EF, _EI, _ER ) files. After I added the CM100LTE, I noticed my phone was alerting A LOT during the first driving segment of my trips. After I would park the vehicle and the dashcam went into parking mode and then I started driving again, the insane number of impact events went back to normal (small number or none).
I have the G-sensor settings for driving mode set to 2,2,2. The parking mode G-sensor settings are 9,9,9.
View attachment 59817 View attachment 59818
As a test, I decreased the parking mode settings to 5,5,5 and went on a test drive. The number of normal driving mode impact events went way down.
I restored the parking mode G-sensor settings to 9,9,9. On 10-Feb-2022, I went on a short trip into town. Just about every 1-minute segment of the drive was considered a normal mode impact event (see file listing screenshots included below). I parked the car for just over 45 minutes. On the trip back home, I drove over the exact same roads and there were no alerts being generated and all of the video files were "_N" normal driving mode video files.
On 11-Feb-2022, I went on a much longer trip (almost 30 miles round trip). The same pattern was observed. The driving segment when I left my home and drove to the first stop (of four), the number of alerts and normal mode event files was outrageously high. After making the first stop and letting the dashcam go into parking mode, the remaining normal driving segments only generated normal recording files.
I power off my dashcams while parked at home. They are powered by dashcam battery packs and I have no need to drain those battery packs nor do I need to record the inside of my garage for hours and hours. Before I leave my home, I restore power to my dashcams.
It appears when the DR750X-3CH Plus and DR750X-2CH Plus are first powered up, they appear to not get initialized with the proper G-sensor settings for normal driving mode.
I have firmware v1.002 installed in the DR750X-3CH Plus and v1.007 installed in the DR750X-2CH Plus.
I don't recall this behavior before the recent firmware upgrades, but I did not have the CM100LTE connected to the DR750X-3CH Plus until just this past week.
I've reported the issue to BlackVue/Pittasoft and I'm waiting on a response from them.
Here are screenshots of the files from the 10-Feb-2022 trip into town. The first red outlined set of files are the impact event files while driving into town. The second red outlined set of files are the normal mode video files driving back home.
View attachment 59815
View attachment 59816
The "short" description of the issue is that bogus normal mode events are detected (push notifications and normal mode event files) by the DR750X Plus front camera during the normal recording mode that occurs just after powering up the dashcam and ends with the first parking mode session. Once the dashcam enters parking mode and then exits parking mode back to normal recording mode, no more bogus events are detected by the DR750X Plus front camera.
When I first started reviewing the DR750X-3CH Plus, I did not have it connected to my CM100LTE LTE cloud connectivity device. The problem was occurring, but I was not being made immediately aware of the number of normal mode events since I did not get push notifications with it not being connected to the BlackVue Cloud service.
After I connected the CM100LTE cloud connectivity device to the DR750X-3CH Plus, I started noticing a large number of push notifications being generated during the normal recording mode occurring just after power up and ending with the first parking mode session. There were so many notifications that my iPhone/iOS would present a question to me about muting the notifications because so many of them were occurring in a short period of time.
I know the roads around where I live are not the best in the world, but they're not that bad to generate 13 events in 15 minutes of driving. If I allow the dashcam to enter parking mode, exit parking mode and then drive on the very same roads, no events are detected.
I had both the DR750X-3CH Plus and DR750X-2CH Plus configured with normal mode G-Sensor settings of 2,2,2 and parking mode G-Sensor settings of 9,9,9.
After A LOT of testing, it's beginning to look like the DR750X Plus front camera is initializing the G-Sensor with the parking mode G-Sensor setting values for the very first normal recording mode just after the dashcam is powered up. The entering and exiting of parking mode seems to "correct" the issue. No matter how many additional normal mode sessions and parking mode sessions take place while the dashcam is powered up, there are no additional bogus normal mode events detected.
I was requested by Pittasoft support to change the G-Sensor settings to 4,4,4 for both normal and parking mode. I ran that test today. If the normal mode G-Sensor settings were correctly being used to initialize the G-Sensor at power up, the number of events detected in normal recording mode should be the same or go up since the values went from 2,2,2 to 4,4,4. I drive a very specific route on a weekly basis. That first normal recording mode between power up and the first parking mode session with settings of 2,2,2 would generate on average 13 events. Increasing the normal recording mode G-Sensor values to 4,4,4 and decreasing the parking mode G-Sensor values from 9,9,9 to 4,4,4 actually resulted in a huge reduction in the number of events from the pre-change average of 13 events down to 3 events.
A second test I ran today was to leave the normal recording mode G-Sensor settings at 4,4,4, but decrease the parking mode G-Sensor settings even further to 1,1,1. I reviewed the video files with this configuration in place and found that events that should have been detected with the normal recording mode 4,4,4 settings were being incorrectly recorded as normal recording mode video files. After the first parking mode session with this configuration, the events with normal recording G-Sensor settings at 4,4,4 were being detected correctly.
Based on all of the testing I've conducted over the last six weeks, it appears that the DR750X-3CH Plus and DR750X-2CH Plus dashcams are incorrectly initializing the normal recording mode G-Sensor sensitivity settings from the parking mode values as the dashcam is powered up and enters normal recording mode. Entering and then exiting parking mode seems to correct the issue.
I've reported my additional test results from today to Pittasoft support.