Bogus or missed normal recording mode events between power up and first parking mode session

[rcg530]

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

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.

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.

 

[StrayCam]

I'd like to make a couple points. Number 1 is that you just have to be one of the best dashcam reviewers out there. Some reviewers seem to just put on their happy-faces and rarely say anything about important malfunctions with the dashcams. Luckily you're out there giving a fair balance with your reviews, never missing a major issue!

Everyone knows there is no such thing as a perfect dashcam; most all of them seem to have one or more important issues that need to be ironed-out.

I believe the important thing becomes can we trust a given dashcam manufacturer to correct the types of malfunctions that you have uncovered?

I know some companies are better than others in dealing with their dashcam problems. Since this thread is dealing with Blackvue/Pittasoft, can you give us some idea on their responsiveness to addressing problems, such as those you have raised through your research?

I appreciate all your hard work!

 

[rcg530]

I'd like to make a couple points. Number 1 is that you just have to be one of the best dashcam reviewers out there. Some reviewers seem to just put on their happy-faces and rarely say anything about important malfunctions with the dashcams. Luckily you're out there giving a fair balance with your reviews, never missing a major issue!

Thanks for the support! There definitely are several dashcam reviewers that put A LOT of effort into their reviews! It's very time consuming to get the dashcams unboxed, setup, installed and then drive around (day and night) to gather footage for the review and then edit the review video(s).

Everyone knows there is no such thing as a perfect dashcam; most all of them seem to have one or more important issues that need to be ironed-out.

I believe the important thing becomes can we trust a given dashcam manufacturer to correct the types of malfunctions that you have uncovered?

I know some companies are better than others in dealing with their dashcam problems. Since this thread is dealing with Blackvue/Pittasoft, can you give us some idea on their responsiveness to addressing problems, such as those you have raised through your research?

Pittasoft has been very supportive of my dashcam reviewing efforts. I first met with representatives of Pittasoft when my daughter and I attended SEMA 2019 in Las Vegas. The Pittasoft marketing team was willing to take a chance on me as a brand new dashcam reviewer (at that time). The Pittasoft marketing team has been extremely helpful in trying to help me get issues figured out by supply the initial equipment, any replacement or additional equipment (if a hardware problem is found).

The Pittasoft customer support team has been quite friendly with my inquiries, but I have to say they are not very fast at responding or initially understanding the issue at hand. You have to understand that my questions are usually more complex than the typical customer asking a question about the product. Every company has been impacted by COVID-19 issues, so I understand that can impact any company's response to issues reported by customers. The issues I've reported to Pittasoft over the past year with regard to the BlackVue X Series dashcams (loss of video frames with rear/interior cameras at file transitions, dark (underexposed) video from X Plus series rear cameras, DR750X-3CH Plus interior camera video/audio out of sync) have yet to result in any firmware or product change to correct any of the issues.

Based on my reviews of the BlackVue dashcams, I now have other dashcam companies wanting me to review their dashcams. I have 40 years of experience being a lead QA engineer and a computer programmer at various levels ending up as a principal software engineer for several companies over the past couple of decades. I love digging into how something works and asking the question does it work correctly. Although, when a problem is found the product review usually is paused for several days/weeks/months while issues are investigated.

I hope that answers your question.

 

[rcg530]

DR750X-3CH Plus / FW 1.002 - Bogus Normal Recording Mode Event

Using the BlackVue SD Card Viewer on Windows to examine the firmware settings for the G-Sensor sensitivity values.

Normal Mode = 2,2,2 / Parking Mode = 9,9,9

Test: Dashcam is powered up and enters normal recording mode


Clicking the "Advanced Settings" button will present this popup panel where you can access/use any of the recordings on the SD card and see how the actual up/down, side-to-side and front/back movement activity actually stacks up against the firmware setting selected. The gray band in each of the motion activity windows is where it displays the allowed motion activity based on the current/selected sensitivity setting for that type of motion. The smaller the setting number the band becomes wider (less sensitive) and the larger the setting number the band becomes narrower (more sensitive). Whenever the motion value breaches the allowed values (outside of the gray band), that reading will qualify as an "Event".

In this particular example, the up/down and side-to-side motion had their largest amount of movement in this section of the video. You can see that the values are well within the gray bands which represent the allowed amount of motion (settings 2,2,2). These values resulted in a cloud event notification and the video to be recorded in an "_ER" (event rear - normal mode) video file. There were no data points for any of the three motion indices that qualified as an event. This is one of many examples on this trip that a bogus event was "detected" when it was not an actual event.



DR750X-2CH Plus / FW 1.007 - Bogus Normal Recording Mode Event

Same day/car but a video from a DR750X-2CH Plus.

Normal Mode = 2,2,2 / Parking Mode = 9,9,9

Test: Dashcam is powered up and enters normal recording mode


The same thing is true with this example as with the previous example. None of the motion values breach the gray bands (settings 2,2,2). This is one of many examples from that trip where the an event was falsely detected during the normal recording mode between the initial power up of the dashcam and the first parking mode session. After the dashcam enters/exits parking mode for the first time, the problem does not occur any longer (no more false/bogus events).

 

[kamkar]

I have only used G - sensor while driving one time, and that was with my first proper 1080p dashcam the Lukas LK-7500
Using that i was very happy it had user changeable value settings cuz even on low it triggered way too often, i did in the end get to a place where it would at worst trigger just once on a drive.
I cant recall what axis it was but it was just the one of them that gave me problems.
But in the end i just said screw it and disabled G - sensor while driving, and i have never used that since then, or i have but then only test samples i have been sent where it was not possible to disable it.

 

[rcg530]

BlackVue customer support requested I test G-Sensor sensitivity settings of 4,4,4 for normal mode and parking mode.

If the dashcam firmware is initializing the G-Sensor with the normal mode settings when the dashcam is powered up and enters normal mode, the number of "events" should be the same or more since the normal mode settings were being made more sensitive.

If the dashcam firmware was incorrectly initializing the G-Sensor with the parking mode settings when the dashcam is powered up, the number of events could be the same or go down because the parking mode setting is being made less sensitive (9 -> 4).

I drive a very specific route on a weekly basis and the initial normal recording mode section of that weekly route is what I'm referencing in this post.

Upping the normal mode G-Sensor values from 2,2,2 to 4,4,4 and reducing the parking mode settings from 9,9,9 to 4,4,4, greatly reduced the number of normal mode events generated between power up and the first parking mode session on that portion of the route. Previous to these value changes, the average number of normal mode events on this route is 13 and after the value changes the number dropped to 3.

The results from this test suggest that the parking mode settings change from 9 to 4 had more of an impact on the dashcam behavior than the normal mode settings change from 2 to 4. The parking mode settings change should have zero impact on the normal mode event detection.

Dashcam = DR750X-3CH Plus – Firmware v1.002 – Powered by 3-Wire Hardwiring Harness / Dashcam Battery Pack – Native Parking Mode – Instant Entry/Exit To/From Parking Mode based on ignition switch status

Example One (Parking Mode = 4,4,4 / Normal Mode = 4,4,4):

To see how this week’s trip is compared to previous weeks with different G-Sensor settings, here are the filenames from this same trip/route with G-Sensor settings of Parking Mode = 9,9,9 / Normal Mode = 2,2,2

11-Mar-2022: Events = 13, Normal = 4
20220311_090335_NF.mp4
20220311_090350_EF.mp4
20220311_090446_EF.mp4
20220311_090544_EF.mp4
20220311_090639_EF.mp4
20220311_090735_EF.mp4
20220311_090831_EF.mp4
20220311_090927_EF.mp4
20220311_091023_EF.mp4
20220311_091119_EF.mp4
20220311_091215_EF.mp4
20220311_091311_EF.mp4
20220311_091407_EF.mp4
20220311_091507_NF.mp4
20220311_091607_NF.mp4
20220311_091707_NF.mp4
20220311_091739_EF.mp4
20220311_091839_PF.mp4

04-Mar-2022: Events = 13, Normal = 6
20220304_094858_NF.mp4
20220304_094922_EF.mp4
20220304_095018_EF.mp4
20220304_095114_EF.mp4
20220304_095217_EF.mp4
20220304_095313_EF.mp4
20220304_095409_EF.mp4
20220304_095509_NF.mp4
20220304_095515_EF.mp4
20220304_095611_EF.mp4
20220304_095707_EF.mp4
20220304_095803_EF.mp4
20220304_095859_EF.mp4
20220304_095956_EF.mp4
20220304_100052_EF.mp4
20220304_100152_NF.mp4
20220304_100252_NF.mp4
20220304_100352_NF.mp4
20220304_100452_NF.mp4
20220304_100535_PF.mp4

Here are the filenames from this week’s trip with G-Sensor sensitivity settings set to Parking Mode = 4,4,4 / Normal Mode = 4,4,4

18-Mar-2022: Events = 3, Normal = 15
20220318_094739_NF.mp4
20220318_094840_NF.mp4
20220318_094940_NF.mp4
20220318_095040_NF.mp4
20220318_095140_NF.mp4
20220318_095240_NF.mp4
20220318_095340_NF.mp4
20220318_095403_EF.mp4 – valid event – up/down motion breached setting of 4
20220318_095503_NF.mp4
20220318_095603_NF.mp4
20220318_095703_NF.mp4
20220318_095803_NF.mp4
20220318_095831_EF.mp4 – valid event – up/down motion breached setting of 4
20220318_095927_EF.mp4 – valid event – front/back motion breached setting of 4
20220318_100027_NF.mp4
20220318_100127_NF.mp4
20220318_100227_NF.mp4
20220318_100327_NF.mp4
20220318_100408_PF.mp4

 

[rcg530]

I ran an additional test on 18-Mar-2022, where I changed the G-Sensor settings for parking mode to 1,1,1 and I left the normal mode settings at 4,4,4 from the previous test.

Why? To see if having the parking mode settings at 1,1,1 would cause the normal mode event detection miss an event. If the dashcam was initializing the G-Sensor values at power up with the 4,4,4 values it should detect motion values that breach that threshold. If it's incorrectly using the parking mode values for normal mode at dashcam power up, motion values that breach the more sensitive "4" setting will be missed because it's using the less sensitive "1" setting.

Example One (Parking Mode = 1,1,1 / Normal Mode = 4,4,4):



Using the “Advanced Settings” feature for the normal mode G-Sensor sensitivity settings - BlackVue SD Card Viewer, I found file 20220318_112610_NF.mp4 which has an up/down movement take place that breaches the up/down G-sensor setting of 4. The files for all three channels were “Normal” files instead of “Event” files. There was also no cloud event nor push notification sent for what should have been an event.

The up/down motion activity should have generated an event.

 

[StrayCam]

Thanks for the support! There definitely are several dashcam reviewers that put A LOT of effort into their reviews! It's very time consuming to get the dashcams unboxed, setup, installed and then drive around (day and night) to gather footage for the review and then edit the review video(s).


Pittasoft has been very supportive of my dashcam reviewing efforts. I first met with representatives of Pittasoft when my daughter and I attended SEMA 2019 in Las Vegas. The Pittasoft marketing team was willing to take a chance on me as a brand new dashcam reviewer (at that time). The Pittasoft marketing team has been extremely helpful in trying to help me get issues figured out by supply the initial equipment, any replacement or additional equipment (if a hardware problem is found).

The Pittasoft customer support team has been quite friendly with my inquiries, but I have to say they are not very fast at responding or initially understanding the issue at hand. You have to understand that my questions are usually more complex than the typical customer asking a question about the product. Every company has been impacted by COVID-19 issues, so I understand that can impact any company's response to issues reported by customers. The issues I've reported to Pittasoft over the past year with regard to the BlackVue X Series dashcams (loss of video frames with rear/interior cameras at file transitions, dark (underexposed) video from X Plus series rear cameras, DR750X-3CH Plus interior camera video/audio out of sync) have yet to result in any firmware or product change to correct any of the issues.

Based on my reviews of the BlackVue dashcams, I now have other dashcam companies wanting me to review their dashcams. I have 40 years of experience being a lead QA engineer and a computer programmer at various levels ending up as a principal software engineer for several companies over the past couple of decades. I love digging into how something works and asking the question does it work correctly. Although, when a problem is found the product review usually is paused for several days/weeks/months while issues are investigated.

I hope that answers your question.

Thanks very much for the information. It's no wonder why your analyses are so thorough based on your background! - - Crossing fingers that Pittasoft/Blackvue makes the necessary changes to correct their dashcam's malfunctions soon!

Clicking the "Advanced Settings" button will present this popup panel where you can access/use any of the recordings on the SD card and see how the actual up/down, side-to-side and front/back movement activity actually stacks up against the firmware setting selected. The gray band in each of the motion activity windows is where it displays the allowed motion activity based on the current/selected sensitivity setting for that type of motion. The smaller the setting number the band becomes wider (less sensitive) and the larger the setting number the band becomes narrower (more sensitive). Whenever the motion value breaches the allowed values (outside of the gray band), that reading will qualify as an "Event".

I had previously seen the gray bar at the bottom of the videos when using the PC Blackvue SD Reader app. What I am able see however is very small and looks nothing like the displays you presented above. I'm trying to figure out how to do what you did with the settings. I cannot find anything that says "Advanced Settings"...Can you steer me in the right direction. Thanks!

Edit: I found the Advanced Setting button. For those who don't know, when in PC SD Card reader app, go to gear (top right corner); click on Firmware, then choose Sensitivity in horizontal tab list. Far right corner has "Advanced Settings". (see pic)

New problem: how to make the g-sensor graphs bigger? On the advanced-settings page they are about 1/2 inch in height and less than 2 inches wide! Very hard to see... Even rcg@530's pic above with settings is considerably larger than what I can see on my 15" laptop...

 

[rcg530]

The BlackVue SD Card Viewer program can be used to view all of the video files from all channels in the main viewer. You can examine and edit the firmware settings as well.

1) Mount the dashcam's microSD card on your computer
2) Start the BlackVue Viewer and click on the SD Card Viewer selection



3) Click on the "Settings" button (top middle/right of the screen)

The "G-Sensor" panel in the lower right section of this screen is a read-only view of the three G-Sensor motion values recorded by the dashcam. You see the full one minute's worth of movement values for all three movement indices at the same time.



4) Click on the "Firmware" tab:



5) Click on the "Sensitivity" tab



6) Click on the "Advanced settings" button for normal mode or parking mode to view or adjust those values.



7) Select a video file from the dashcam's microSD card that you want to playback and see if the dashcam recorded motion values stay within or breach the selected setting.

Off / 0 = No monitoring of this value takes place
1 = Least sensitive value (widest gray band)
10 = Most sensitive value (narrowest gray band)

Any data point on the graph that is within the gray band would be considered an expected/allowed amount of movement for the direction of motion.

Any data point on the graph that is above or below the gray band would be a value that has breached the threshold for that setting and it should generate an event for that motion direction.

To adjust the sensitivity value on this screen, you need to click on the scroll bar on the right side of the display section for each one and scroll up/down to change the value. If you do make a change, don't forget to click on the "Save and close" button to exit this screen.

One thing I noticed in this screenshot is that the up/down graph (lower left side) seems to have a slightly different scaling factor for the 0 to 10 values. All of the settings are 4 in this example, yet the gray band for the value of four for the up/down motion setting is wider than the other two.

 

[StrayCam]

I did not mean to get your important topic "off topic". But your use of the graphs and your explanation of how to get to them are fantastic! Blackvue should be putting this information in the hands of its users. Thanks very much... very helpful!

And btw I found out how to make the tiny graphs legible/bigger... plug 15" laptop into 55" TV with hdmi cable...lol...

 

[rcg530]

With the mountain of evidence I have provided over the past two months, my Pittasoft support representative seems to have "almost" stated that this issue might actually exist.

To temporarily avoid the excessive number of normal mode events between power up and the first parking mode session, Pittasoft support has suggested I set both the normal mode and parking mode G-Sensor sensitivity settings to 4,4,4. Those settings are only a workaround to help minimize the number of erroneous events generated during the first normal mode directly after powering up the dashcam.

Any user of a DR750X Plus series dashcam should be able to set the parking mode G-Sensor sensitivity values to anything that is appropriate for parking mode and not have those values influence the first normal mode after powering up the dashcam.

I hope this gets fixed soon with a firmware update.

 

[rcg530]

This issue continues to languish inside the Pittasoft support group. I've provided numerous emails, video files, pdf documents on how to reproduce this issue. I decided to create a video showing how the DR750X Plus dash cameras appear to have the very first "normal mode" recording session end up using what looks like the "parking mode" G-Sensor setting values instead of the "normal mode" G-Sensor values.

If you don't have your DR750X Plus dash camera connected to the BlackVue Cloud service, this bug will be a silent one unless you actively review the video files on the microSD card.

I hope this gets fixed soon.

 

[rcg530]

I have tested every DR750X Plus firmware available since the start of February 2022 until late April 2022. That's when I paused my testing waiting for Pittasoft to reproduce/fix the issue. Last night, I had another email discussion with Pittasoft. It was decided I would test the absolute latest firmware (DR750X Plus v1.010).

I rearranged the dash cams in my car to provide power to a DR750X-2CH Plus dash cam with firmware v1.010. I ran a test as outlined in the video (normal mode = 2,2,2 / parking mode = 9,9,9).

Very much to my surprise, the results of my test were surprisingly positive. This was the first test in 3.5 months any DR750X Plus dash cam did not misbehave during "Normal Mode #1" (just after power up).

DR750X Plus firmware v1.010 (released 11-May-2022) added some "Reckless Driver" improvements which involve the accelerometer (G-Sensor). I have the "Reckless Driver" detection features turned off.



On Friday, I will go on an extended drive which should show for sure if this is resolved or not starting with v1.010.

 

[rcg530]

Today, I performed a series of tests with a DR750X-2CH Plus dash cam to see if I can get that dash cam to generate invalid “impact detected in normal mode” events with the three most recent firmware versions (excluding 1.008). Over the past couple of days, I had tried a couple of test trips with 1.010 installed and it appeared the problem was not reproducing with that firmware in place.

Last night, I performed a deep dive review of the numerous tests and emails and video files I have in my dash cam video archive from this model dash cam. I reported this problem to Pittasoft back when firmware v1.007 was the latest version of firmware available. I was able to reproduce this problem until my active testing of this problem stopped at the end of March 2022. At that point, no forward progress was being made on this issue so I applied the band-aid solution of setting both the normal mode and parking mode G-Sensor settings to 4,4,4. Both the DR750X-3CH Plus (which looks like it had firmware version v1.002) and the DR750X-2CH Plus were experiencing the bug.

DR750X Plus (1CH/2CH) Firmware versions 1.008 and 1.009 were released at the beginning of April 2022. I did not actively test this issue again because there was absolutely no mention of any G-Sensor fixes present in the Pittasoft firmware change log.

I prepared three microSD cards with the three firmware versions I was testing 1.007, 1.009 and 1.010. Last night, I loaded firmware 1.007 into the DR750X-2CH Plus dash cam and reviewed / configured all firmware settings appropriate to that version of firmware. I set the G-Sensor settings to normal mode = 2,2,2 and parking mode = 9,9,9 (for this test).



Test Setup

• With each firmware version installed and firmware settings configured / confirmed
  • Power up DR750X-2CH Plus dash cam
  • For “Normal Mode #1” drive a specific route
  • Return to start point of trip and park – have DR750X-2CH Plus enter parking mode for about one minute and then have it exit parking mode
  • For “Normal Mode #2” drive the exact same route
  • Return to start point of trip and park
  • Upgrade to the next firmware version to be tested and configure / confirm settings – repeat exact same route / test

I was able to easily reproduce the problem with firmware v1.007 installed. I received an “impact detected in normal mode” push notification from the BlackVue Cloud service before leaving the parking lot where I started the trip.

Here is a listing of video files with firmware 1.007 installed. The first 90 seconds of "Normal Mode #1" video was with me listing my audio notes to the dash cam audio to note the configuration before leaving the parking lot. The entire "Normal Mode #1" was made up of "impact detected in normal mode" events. After entering and then exiting parking mode, "Normal Mode #2" was void of any impact events. This is the exact description of this problem as I reported to Pittasoft when 1.007 was the latest available firmware version. The playback of the first event video file from "Normal Mode #1" showed that it did not qualify as an actual impact event with the normal mode G-Sensor settings set to 2,2,2.




My iPhone received nine (9) push notifications for "impact detected in normal" mode. Reviewing the video files on the microSD card, there were actually ten (10) impact events in "Normal Mode #1".

I did not test 1.008 because 1.009 was released as a minor bug fix to 1.008 for the proximity sensor just two days after 1.008 was released.

Version 1.009 and 1.010 did not produce the problem. It appears that some unnamed / unlisted bug fix was made in 1.008 and/or 1.009 that appears to have resolved this issue with the DR750X-2CH Plus dash cam.

I'm now going to get the DR750X-3CH Plus dash cam reinstalled in my car to test its latest firmware version 1.003. I last tested version 1.002 with the DR750X-3CH Plus dash cam and it had the problem at that time with that version of firmware installed.

I've reported my latest findings to Pittasoft support.

 

[rcg530]

I completed my firmware version testing with the DR750X-3CH Plus dash cam. The same test plan and route was used for the DR750X-3CH Plus testing as it was for the DR750X-2CH Plus testing.

• Version 1.002 (Released 2022-01-18)
  • I first encountered this bug using this firmware version
  • Over the past several months, I reproduced this issue using two different DR750X-3CH Plus dash cams
  • This DR750X-3CH Plus dash cam still had firmware version 1.002 installed
  • I confirmed the G-Sensor settings were set to “normal mode” = 2,2,2 and “parking mode” = 9,9,9
  • Bug was reproduced using firmware 1.002
• Version 1.003 (Released 2022-05-18)
  • During my execution of the test steps, the bug was not reproduced with firmware 1.003 installed​

Here's a file listing from the microSD card when firmware 1.002 was installed. Except for the first 32 seconds when the car was stationary, every one minute segment during "Normal Mode #1" was flagged as an impact event. After the one minute parking mode session, the same exact route resulted in zero impact events during "Normal Mode #2". I've reported these findings to Pittasoft support.

 

[rcg530]

I created a follow-up video showing the firmware versions for the BlackVue DR750X 1CH/2CH/3CH Plus dash cams that resolve the incorrect G-Sensor values being used during the first normal mode just after powering up the dash cam.

Minimum firmware versions with G-Sensor fix:

DR750X (1CH/2CH) Plus: Version 1.009
DR750X 3CH Plus: Version 1.003