V2.0 Firmware for Public Testing

Forester25 said:
While the Config Viewer helps, it does not have the answers to all choices that are buried in the menu. But it is a help. A file with all choices would be nice to have. So they could be found easier and a print out that could be used to mark. But maybe it is just because I am new to this sport. Would like the dash came to be for the most part set and forget.
Click to expand...

Ah, I now understand that you are looking for something that also lists all potential selections for each setting, not just the user selected one.
 
At Viofo they must have a complete map, but I could never understand the Chinese. 🙂
 
Forester25 said:
Is there any way to get a complete map of all the choices in the menus?
Click to expand...
Yes. If you export the current settings to microSD then open the viofo_config.ini file in a text editor you can see all the available options, plus the one you have selected.

In the example below from the Viofo blog page, the text in green is the list of options, followed by the text in blue which is your current setting.

1761671478993.webp
 
TonyM said:
Yes. If you export the current settings to microSD then open the viofo_config.ini file in a text editor you can see all the available options, plus the one you have selected.

In the example below from the Viofo blog page, the text in green is the list of options, followed by the text in blue which is your current setting.

View attachment 87128
Click to expand...

Thank you! I thought I remembered seeing that somewhere, but couldn't immediately find it.
 
A bit more on my Geofencing experience with the most recent beta firmware...it takes me ~48 seconds to back out of my garage and drive down a short driveway to an electric sliding gate and then out to park on my street. A good bit of that time is unfortunately waiting for that gate to open 🙄. Anyway, the cam connects to a GPS signal within that time* and with the 15m setting all of the street is outside that zone. PM kicked in as expected when I immediately turned off my car this time after parking. When I returned to my garage, the camera again turned off automatically as desired.

It also seems the newest firmware settings are now showing in the beta iOS app, but that's just a cursory check and not a 1:1 comparison.

*without a helper, I cannot check on the screen to estimate actual time of first GPS fix as my cam is on the passenger side and hidden by my mirror unless I lean waaay over. I realize that first GPS connectivity can vary widely depending on specific conditions, but still would be interesting to know.
 
For the parking mode impact detection notification, I get frequent notifications because it takes me a little time to get the kids in the car before I start the car. Would it be possible to have the dashcam ignore any impacts from maybe 3 min before we start the engine? It'd be similar for when putting groceries in the trunk and closing the trunk also causes an impact.
 
Vortex Radar said:
For the parking mode impact detection notification, I get frequent notifications because it takes me a little time to get the kids in the car before I start the car. Would it be possible to have the dashcam ignore any impacts from maybe 3 min before we start the engine? It'd be similar for when putting groceries in the trunk and closing the trunk also causes an impact.
Click to expand...
@Vortex Radar @VIOFO-Support @viofo
I think it's possible. It needs some work.

For example, this camera processes voltage data thanks to the HK6.
What can be done?
For example, the camera monitors the voltage data while parked. When the vehicle is unlocked with the remote control or keyless entry, there will be a momentary voltage drop, and when the camera detects this, it may reduce sensitivity for a certain period of time.

This requirement could be addressed with specialized or official software.
 
Being over-notified tends to make the notification lose its value. You will ignore the notification because it occurs so often and for what you perceive as your re-entry into the vehicle. I think a large portion of @Vortex Radar's suggestion could be implemented by not changing the video creation/handling process for an impact event in parking mode, but how the firmware is tracking whether to notify about the impact events.

The firmware could track/keep the timestamp for the first impact event during the parking session. When the dash camera resumes normal/driving recording mode, if the impact timestamp is more than 3-minutes in the past, then notify. You might still get files placed in the RO directory for impacts within the 3-minutes prior to returning to normal/driving recording mode, but the dash camera would only notify you to look for impacts that occurred before the last 3-minutes of the parking mode session. Not a perfect solution, but it gets rid of the annoyance factor of being over-notified for impact events unless they were before the last 3-minutes of the parking mode session.
 
rcg530 said:
The firmware could track/keep the timestamp for the first impact event during the parking session. When the dash camera resumes normal/driving recording mode, if the impact timestamp is more than 3-minutes in the past, then notify. You might still get files placed in the RO directory for impacts within the 3-minutes prior to returning to normal/driving recording mode, but the dash camera would only notify you to look for impacts that occurred before the last 3-minutes of the parking mode session. Not a perfect solution, but it gets rid of the annoyance factor of being over-notified for impact events unless they were before the last 3-minutes of the parking mode session.
Click to expand...
The notification logic already ignores impacts in the first and last minute of parking mode. It might be nice to have that increased to 3 minutes. It would certainly reduce the number of false alerts, with a small risk of missing a genuine impact in those 2 extra minutes.
 
TonyM said:
The notification logic already ignores impacts in the first and last minute of parking mode. It might be nice to have that increased to 3 minutes. It would certainly reduce the number of false alerts, with a small risk of missing a genuine impact in those 2 extra minutes.
Click to expand...
I went back and reviewed the Beta blog page and found that this:

Code: 
The reminder excludes files triggered within 1 minute of switching between parking and normal recording modes, reducing false alerts from car doors closing.

It's only documented that the reminder ignores impacts within 1-minute of switching from parking to normal recording modes, but I believe you're correct that it ignores impacts just after entering and just before exiting parking mode.

The latest beta [2.0_251027] firmware still has the annoying behavior of occasionally [80% of the time] self-inflicting an impact event immediately as it enters parking mode with zero movement of the dash camera. I turn off the accessory power and when it switches to low bitrate parking mode I hear the photo sound and the alert symbol is on the screen.

Since the A329S self-triggers an impact event immediately after enter parking mode [80% of the time], I used that impact event as the within the first 1-minute of parking mode impact event to see if it notifies on impacts within the first 1-minute of parking mode. I let it enter parking mode, it self-triggers an impact event, I let the A329S remain in low bitrate parking mode for another 4-minutes, and I then restore accessory power. There's no notification for the self-inflicted impact event within the first 1-minute of parking mode.

One of the rare times it entered parking mode without self-triggering an impact event, I let the A329S operate in low bitrate parking mode for just over 2-minutes when I triggered an impact event. I waited another 3-minutes before restoring ACC power and it did produce a notification for the impact event in parking mode. The notification time period now appears to be reduced as well to about 7 seconds.
 
TonyM said:
Glad to see you recognise that we have daylight savings here too. I had to set my location to GMT+1 to get the correct time until last week.
Click to expand...
I might be in Oz but I’m from Blighty..! 🤣

They daylight save here too – not where I am, but most of the Eastern States do….As do plenty of other countries – a quick Google will tell you approximately 34% of countries do..!

The Daylight Saving setting needs to be universal on top of wherever you have set your GMT time location….
 
Updated my A329T to v2.0_251027.
It factory reset to Initial Setup menu after reboot.
Did a power cycle after setting most settings on the cam itself.
When i went to enable the wifi, the cam froze, hard locked up.
A power cut and reboot later, it worked fine. Have not have it freeze up like that again as of yet.
Used the New app to type in my plate number and check settings. All seems fine and in sync to me (i do not use parking mode/collision detection etc
 
These long awaited impact notifications sound interesting. I need to get me one of these to try.
 
TonyM said:
The notification logic already ignores impacts in the first and last minute of parking mode. It might be nice to have that increased to 3 minutes. It would certainly reduce the number of false alerts, with a small risk of missing a genuine impact in those 2 extra minutes.
Click to expand...
This version increased to 3 minutes. (Link updated, thanks to @Jaqb feedback.)
 
Last edited:
You must log in or register to reply here.
Back
Top