Slight flaw in parking mode impact detection announcment feature

Discussion in 'DR750S-2CH' started by glowstix047, Oct 2, 2017.

  1. glowstix047

    glowstix047 New Member

    Messages:
    17
    Likes Received:
    4
    Country:
    Australia
    So I noticed that there might be a slight flaw in the parking mode impact detection announcement feature today.

    Quick recap, the parking mode impact detection announcement is the announcement your camera makes after exiting parking mode if your camera has detected any impact while you are away from the car and your camera is in parking mode.

    So when you return to your car, enter your car, close the door/boot, it detects this as an impact. When you drive off and the car exits parking mode, it will announce that there was an impact detected.

    This means that every time you enter your car, drive off, it exits parking mode, it will always tell you there's an impact, even though it's just you closing your door. This renders the parking mode impact detection announcement feature a little less useful than i originally thought as it's always detecting "false positives".

    Just thought I would point this out, at the end of the day it's still best to do a quick inspection of your car and not rely too much on this feature.
     
    evad and michael007 like this.
  2. BlackboxMyCar

    BlackboxMyCar Active Member Retailer

    Messages:
    334
    Likes Received:
    153
    Location:
    Vancouver, BC.
    Country:
    Canada
    Dash Cam:
    Thinkware, BlackVue, BlackSys , LG Innotek, VIOFO,
    Definitely agree, the concept is flawed. Can't blame the camera for not knowing the difference between a hit and run and a door slam though.
    Luckily you can turn off this feature in the settings.
    Thinkware does it a bit better by announcing exactly how many events were detected so you can filter out the one you know is just you closing the door/trunk.
     
  3. Benji

    Benji New Member

    Messages:
    2
    Likes Received:
    2
    Country:
    United States
    The simple solution to this is for them to just have it announce the number of parking mode impact events it detected during that particular parking mode session.
     
  4. glowstix047

    glowstix047 New Member

    Messages:
    17
    Likes Received:
    4
    Country:
    Australia
    Agreed, how do we put forward this feedback to blackvue so it can be implemented in a firmware update?

    Sent from my XT1635-02 using Tapatalk
     
  5. glowstix047

    glowstix047 New Member

    Messages:
    17
    Likes Received:
    4
    Country:
    Australia
  6. Shpixx

    Shpixx New Member

    Messages:
    2
    Likes Received:
    0
    Location:
    Canada
    Country:
    Canada
    Dash Cam:
    DR750S-2CH
    Mine has been going off with the impact detected in park mode - every time - and I check the footage and the event stamp is the time in which I close the door. Yup!!
    Hoping a firmware update might fix it! I've turned off the notification for now, unfortunately.
     
  7. Cessna CJ4

    Cessna CJ4 Member

    Messages:
    49
    Likes Received:
    19
    Country:
    United States
    Dash Cam:
    Blackvue DR650S Dual Channel

    It probably won't be a firmware "fix." As BBMC states above, this is more of a conceptual problem.

    From and end user standpoint for this particular product, there are two primary inputs relative to this one logical output: Time and Expectation. The timeline for the expected output begins when the driver enters the vehicle and drives off. That starts the expectancy clock in the mind of the driver. The driver then expects to be notified whether or not there has been an impact in "Parking Mode" prior to the initiation of "Normal Mode." However, that impact would by definition had to have taken place in a previous "Parking Mode," which cannot become "previous" until a new "Normal Mode" becomes state. Thus, the conundrum of issuing a real-time audible alert to a driver having an expectation about a prior event along a different timeline. This explanation also contains the solution (if Blackvue were paying attention).

    As a creative design engineer, you will run into these conceptual contradictions all the time in your work. You have to creatively solve the problem and that could entail everything from a simple logic revision to an entire redesign of the subsystem, function or sub-function depending on how deep the logic tree goes.

    This is not a software or coding issue. This is a creative logic design issue - but I'm sure Blackvue could care less about hearing from me on how to solve this problem - which actually has a very simple solution that does not require a change in underling output design logic. But, like I said - Blackvue keeps ignoring my emails - so I'm positive that would not want to hear from me on how to solve this problem. In fact, based on my experience with Blackvue, I'm fairly confident that they don't even see this as being a "problem" at all.

    This is not coding problem. This is an issue having to do with Engineers being thorough and complete in their input/output algorithms such that end users are allowed to maintain a consistent expectancy model absent logical lurches and speed bumps.

    I solve problems like this all day long in my business. I would love to solve this one - but I'm not going to unless Blackvue calls me on the phone and apologies for ignoring my emails. (y) Big hint by the way, Blackvue.
     
Loading...
Similar Threads - Slight flaw parking
  1. Wargoose
    Replies:
    6
    Views:
    461

Share This Page