A229 Pro Test & Review PP

[Panzer Platform]

If so, can you check if there is a bug in the a229 Pro/Plus that is found in other cameras and is not fixed?

Yo Ogz,
I don’t 100% fully understand what you’re asking me to do.
If you are using Google translate for English I think it’s not working well.

I’m unwilling to actively check for bugs on “unofficial" firmware because if there are bugs found they will most likely be already fixed when the official firmware is released to the public on the Viofo website.

VIOFO A229 Pro Dash Cam Support

viofo.com

I hope you can understand.

The only reason I reported this current bug was I noticed it without going looking for it.
-Chuck

 

[Panzer Platform]

Keep in mind these are just test notes for future reference with “unofficial firmware”.

Q: How long will the A229 Pro 2-CH REAR operate in Low Bitrate Parking Mode with @BlackboxMyCar PowerCell 8 Battery Pack, (actual, not theoretical)?
A:
Test #1 16 Hours 15 Minutes
Test #2 17 Hours 56 Minutes (1Hr 41Min more, what is going on here?)
Test #3 18 Hours 2 Minutes (1Hr 47Min more, what is going on here?)
Test #4 18 Hours 19 Minutes (PT)
Test #5 18 Hours 57 Miniutes (PT) Retail / Production
Firmware & Settings;
Front Firmware 1208
Rear Firmware 1207
HDR On
Wi-Fi & Screen Off
Test Conditions: Indoor Ambient Temp 65℉ (18℃)
512GB Viofo SD Card

Q: What is A229 Pro 2-CH REAR power consumption in Low Bitrate Parking Mode?
A: 5.41 Watts

Q: What is A229 Pro 2-CH REAR power consumption in Normal Recording Mode Mode?
A: 5.97 Watts
Firmware & Settings;
HDR On
Wi-Fi & Screen Off
Bitrate: Maximum
512GB Viofo SD Card

Comparing my test results with @rcg530 on firmware 0925 & 0901 it looks like Low Bitrate parking mode may have changed;
0925 & 0901: 4.98 Watts
1208 & 1207: 5.41 Watts
Yo Robert, if you have time can you confirm & verify with 1208 & 1207 firmware?

Here’s videos of my power consumption tests;

 

[forcefed]

There's aed with no motion? I thought all aed was with motion

 

[Panzer Platform]

There's aed with no motion? I thought all aed was with motion

For testing purposes I only use Low Bitrate Parking Mode.
AED parking mode is condition based.
No Activity = Lower Power Consumption
Activity = Higher Power Consumption
AED = Power Fluctuations
Low Bitrate Parking Mode power consumption is constant / fixed / linear.
Low Bitrate is more accurate for predicting run times, and comparisons.

 

[rcg530]

I moved my power supply and Fluke 117 out to my car to rerun the A229 Pro 2CH (rear) power consumption test for low bitrate parking mode. I had to use a different VIOFO hardwire kit, because the HK4 I was using for that purpose is now installed in my car powering an A119 Mini 2 on the rear window.

There was a small upward change in the power consumption with the later firmware versions installed (front: v1.1_231208, rear: v1.0_231207). I also discovered a 5-minute time period where the power consumption in LBR parking mode was very high, but then it calmed down to the same level I observed in all of my other testing performed today.

• Test 1 - 128 GB VIOFO Memory Card
  • I used the existing 128 GB memory card to run this first test.
  • I have the enter parking mode delay timer set to 90 seconds.
  • I turned off accessory power and waited the 90 seconds to enter LBR parking mode.
  • LBR
    • 00:00 => 05:00: Avg 403 mA / 5.08 W
    • 05:00 => 10:00: Avg 404 mA / 5.09 W
    • 10:00 => 15:00: Avg 405 mA / 5.10 W
• Test 2 - 512 GB VIOFO Memory Card
  • I formatted the 512 GB memory card on my Windows laptop using the VIOFO guiformat program as a FAT32 with a 64K allocation block size.
  • I powered down the A229 Pro using the button on the A229 Pro, inserted the 512 GB card and powered up the A229 Pro.
  • I used the "Format" feature in the firmware menu to reformat the card.
  • I exited the menu and the A229 Pro started recording.
  • I used a voice command to turn off the screen.
  • I turned off accessory power and waited the 90 seconds to enter LBR parking mode.
  • LBR
    • 00:00 => 04:15: 448 mA / 5.64 W
      • At about 4:15 into the parking mode session, the power consumption started to drop.
      • At this time, I don't know what triggered this higher power consumption level.
    • 05:00 => 10:00: 411 mA / 5.18 W
    • 10:00 => 15:00: 412 mA / 5.19 W
• Test 3 - 512 GB VIOFO Memory Card
  • I powered down the A229 Pro after test 2.
  • I removed power by turning off the DC power supply.
  • I turned on the DC power supply to boot the A229 Pro.
  • I turned off accessory power and waited the 90 seconds to enter LBR parking mode.
  • LBR
    • 00:00 => 05:00: 420 mA / 5.29 W
    • 05:00 => 10:00: 414 mA / 5.22 W
    • 10:00 => 15:00: 414 mA / 5.22 W
• Test 4 - 128 GB VIOFO Memory Card
  • I powered down the A229 Pro after test 3 and swapped back in the 128 GB memory card.
  • I powered up the A229 Pro and used the firmware menu format option to format the 128 GB card.
  • I powered down the A229 Pro and turned off the DC power supply.
  • I turned on the DC power supply to boot the A229 Pro.
  • I turned off accessory power and waited the 90 seconds to enter LBR parking mode.
  • LBR
    • 00:00 => 05:00: 413 mA / 5.20 W
    • 05:00 => 10:00: 414 mA / 5.22 W
    • 10:00 => 15:00: 414 mA / 5.22 W

 

[Panzer Platform]

There was a small upward change in the power consumption with the later firmware versions installed (front: v1.1_231208, rear: v1.0_231207). I also discovered a 5-minute time period where the power consumption in LBR parking mode was very high, but then it calmed down to the same level I observed in all of my other testing performed today.

Thank you for the extra work.
I bet it was cold in your garage this morning. lol
So it looks like it’s possible SD Card size / capacity may be a factor in power consumption.
Wow, I remember @Nigel saying something about this.
I will re-test with different size Viofo Brand SD Cards.
I will also let the camera run in parking mode for 5, 10, 15, 20+ minutes to see if it power consumption comes down.
Thanks again Robert.
-Chuck

 

[rcg530]

Thank you for the extra work.
I bet it was cold in your garage this morning. lol
So it looks like it’s possible SD Card size / capacity may be a factor in power consumption.
Wow, I remember @Nigel saying something about this.
I will re-test with different size Viofo Brand SD Cards.
I will also let the camera run in parking mode for 5, 10, 15, 20+ minutes to see if it power consumption comes down.
Thanks again Robert.
-Chuck

The 512 GB card and the 128 GB card tests (3 & 4) have about the same power consumption during 05:00 => 15:00 time period. I'm not sure what the test 2 power spike was due to in the first four minutes.

 

[Nigel]

The 512 GB card and the 128 GB card tests (3 & 4) have about the same power consumption during 05:00 => 15:00 time period. I'm not sure what the test 2 power spike was due to in the first four minutes.

You had formatted the memory card, so had deleted all the files. Maybe, having placed them in the delete pool, it took around 5 minutes to go through the deleted blocks and physically erase the memory. I don't know, but that seems a reasonable explanation, a reasonable time period to do it, and a reasonable additional power consumption to do it. Flash memory needs to be erased to "0" before it can be reused.

 

[Panzer Platform]

@viofo @VIOFO-Support
Dear Viofo,
I’ve been hesitant to report all the little “insignificant” firmware bugs I’ve noticed since I began testing the A229 Pro 9/11/23 (89 days ago) because I don’t want to divert any manpower / time / resources away from fine tuning image quality.
The most important “elephant bug” is image quality & NIGHT TIME HDR performance for me.
Without the world famous, industry leading Viofo image quality I see no point, and everything else takes a back seat for me.
Image quality is the basic fundamental ingredient that make your cameras better than all other brands.
I’m only 90% satisfied with current image quality.

But, now I think I found a bug that is complicating my parking mode run time tests.
If I recall the whole reason for the new 5-Pin GPS mount on the original A229 Duo, & A119 Mini in 2022 was to enable power saving features like disabling power to the GPS module in parking mode to reduce power consumption, and increase parking mode run times.
It appears “Disable GPS in Parking Mode” setting is missing from both the LCD Screen menu settings, and the Viofo Smartphone APP.
See attached photos.

Viofo:
Yes, Chunk we have already fixed.
It will be released in the next A229 Pro & A229 Plus firmware update, and the all new Viofo Smartphone APP.

 

[Nigel]

I’ve been hesitant to report all the little “insignificant” firmware bugs

The person. fixing the little bugs is probably not the same person fixing the IQ issues, so send them all in!
They may just get stuck on the queue, but more likely will get fixed. Unlikely that they are going to slow the IQ progress.

 

[Panzer Platform]

send them all in!

Duly noted.

 

[Panzer Platform]

I moved my power supply and Fluke 117 out to my car to rerun the A229 Pro 2CH (rear) power consumption test for low bitrate parking mode. I had to use a different VIOFO hardwire kit, because the HK4 I was using for that purpose is now installed in my car powering an A119 Mini 2 on the rear window.

There was a small upward change in the power consumption with the later firmware versions installed (front: v1.1_231208, rear: v1.0_231207). I also discovered a 5-minute time period where the power consumption in LBR parking mode was very high, but then it calmed down to the same level I observed in all of my other testing performed today.

• Test 1 - 128 GB VIOFO Memory Card
  • I used the existing 128 GB memory card to run this first test.
  • I have the enter parking mode delay timer set to 90 seconds.
  • I turned off accessory power and waited the 90 seconds to enter LBR parking mode.
  • LBR
    • 00:00 => 05:00: Avg 403 mA / 5.08 W
    • 05:00 => 10:00: Avg 404 mA / 5.09 W
    • 10:00 => 15:00: Avg 405 mA / 5.10 W
• Test 2 - 512 GB VIOFO Memory Card
  • I formatted the 512 GB memory card on my Windows laptop using the VIOFO guiformat program as a FAT32 with a 64K allocation block size.
  • I powered down the A229 Pro using the button on the A229 Pro, inserted the 512 GB card and powered up the A229 Pro.
  • I used the "Format" feature in the firmware menu to reformat the card.
  • I exited the menu and the A229 Pro started recording.
  • I used a voice command to turn off the screen.
  • I turned off accessory power and waited the 90 seconds to enter LBR parking mode.
  • LBR
    • 00:00 => 04:15: 448 mA / 5.64 W
      • At about 4:15 into the parking mode session, the power consumption started to drop.
      • At this time, I don't know what triggered this higher power consumption level.
    • 05:00 => 10:00: 411 mA / 5.18 W
    • 10:00 => 15:00: 412 mA / 5.19 W
• Test 3 - 512 GB VIOFO Memory Card
  • I powered down the A229 Pro after test 2.
  • I removed power by turning off the DC power supply.
  • I turned on the DC power supply to boot the A229 Pro.
  • I turned off accessory power and waited the 90 seconds to enter LBR parking mode.
  • LBR
    • 00:00 => 05:00: 420 mA / 5.29 W
    • 05:00 => 10:00: 414 mA / 5.22 W
    • 10:00 => 15:00: 414 mA / 5.22 W
• Test 4 - 128 GB VIOFO Memory Card
  • I powered down the A229 Pro after test 3 and swapped back in the 128 GB memory card.
  • I powered up the A229 Pro and used the firmware menu format option to format the 128 GB card.
  • I powered down the A229 Pro and turned off the DC power supply.
  • I turned on the DC power supply to boot the A229 Pro.
  • I turned off accessory power and waited the 90 seconds to enter LBR parking mode.
  • LBR
    • 00:00 => 05:00: 413 mA / 5.20 W
    • 05:00 => 10:00: 414 mA / 5.22 W
    • 10:00 => 15:00: 414 mA / 5.22 W

Good news.
I retested with your method, after 15 minutes I'm getting "identical" measurements with my 512GB Viofo SD Card.
I'm so glad we have the "same" power supply, and Fluke.
I also tested a 64GB Viofo SD Card, and umm I got some interesting results that I don't want "open the can of worms" right now. lol

 

[VIOFO-Support]

@viofo @VIOFO-Support
It appears “Disable GPS in Parking Mode” setting is missing from both the LCD Screen menu settings, and the Viofo Smartphone APP.

It will be added later.

 

[Panzer Platform]

It will be added later.

@rcg530
I just completed my 3rd run time test.
Low Bitrate parking mode, A229 Pro 2-CH REAR, BBMC PC8 Battery Pack (96Wh).
Test #1 16 Hours 15 Minutes
Test #2 17 Hours 56 Minutes
Test #3 18 Hours 2 Minutes
This time I monitored the camera during the 18 hour test.
It appears the poor run time / fluctuations are caused by the GPS Module “hunting for signal”.
My test rig is indoors, (surrounded by EMI / RFI signal interference).
The camera’s GPS module intermittently looses, and regains GPS lock.
I discovered this when I witnessed the GPS status LED like blink, and go steady throughout the day, (blue LED light on camera).
Once you add the “Disable GPS in Parking Mode” firmware setting it should increase parking mode run time by approximately 30 minutes, and "more importantly" eliminate power fluctuations.
I will retest when the setting is added.

 

[Panzer Platform]

Vantrue OBD Cable + A229 Pro = No Worky
Old: https://www.vantrue.net/product/obd_cable_for_x4S_n4_n2S_e1
New: https://www.amazon.com/gp/B0CMWX21M4I’ve been putting off testing the Vantrue OBD2 Power Cable because a curtain someone said we would be getting a Viofo OBD2 Power Cable before the “Year Of The Dragon” and I’d like to test the same time. lol

How To Make a VIOFO OBD2 Adaptor

I show you how to make your own VIOFO OBD2 cable

dashcamtalk.com

I quickly tried the Vantrue cable with the A229 Pro to check if parking mode would function “identical” to a Viofo Hardwire Kit, (ignition / ACC triggered).
Unfortunately it does not.
I tried on my;
2004 Ford Crown Victoria (non CANbus)
2010 Mercury Grand Marquis (CANbus compliant)
The Vantrue cable has all 16-Pins.
I need a female OBD2 pigtail for further testing.

@viofo @VIOFO-Support
Dear Viofo, can we get an updated ETA on the OBD2 Power Cable?
Hopefully before “Year Of The Snake”. lol

 

[NAUTY]

Ask me again in 30 days. Lol

Ayo, Its almost been thirty days. What do you think?

 

[Panzer Platform]

@viofo @VIOFO-Support @NAUTY
I received my retail / production A229 Pro 3-CH for test & review, so for the past week I’ve been checking it out to see if it behaves / performs like the pre-production unit I received on September 11, 2023 (104 days ago).
So far I’m glad to say they are “identical”, so I don’t have to go back and redo all my previous testing. Thanks again Viofo for sending that out.

I gathered DRIVING test footage with the newly released firmware for the A229 Pro from the official Viofo website.
Front: V1.1_231208
Rear: V1.0_231207
I also gathered some “useless” indoor / outdoor stationary night time HDR test footage.
I’m glad I have two A229 Pro units because it will enable me to gather side by side simultaneous footage to test things like;
1.) Q: Never use HDR during the DAYTIME (Yes/No)?
2.) Q: How badly is image quality degraded by connecting the IR Interior Camera, (this drops the Bitrate from 60 Mbps to 36 Mbps)?
3.) Q: How badly is image quality degraded by NOT using HDR at NIGHT TIME?

I find it difficult to evaluate overall image quality when looking at footage from only one camera without comparing it to other “known cameras” as a benchmark.
To help me make this comparison I have 4 cameras on the front window, and 2 cameras on the back window.
Front Window:
A229 Pro 2-CH Rear
A139 Pro 1-CH
A119 Mini 2
A229 Pro 1-CH (HDR usage opposite A229 Pro 2-CH Rear)
Back Window:
A229 Pro Rear
A119 Mini 2
Long story short DAYTIME footage is OK / good / acceptable.
I saw some improvements in NIGHT TIME HDR performance, but I think it still needs more fine tuning, and polish, (not 100% tits).
Side note: I did not see any improvement in night time HDR performance of the A229 Plus Front with the new firmware V1.1_231208.
Also, when comparing footage it’s critical all cameras have identical 50/50 road & sky lens alignment.
This has been difficult for me since the Viofo Smartphone APP does not have an alignment line in the Live View.
The good news is I’ve finally been able to figure out how to align all cameras on my front window in my garage with reliable / repeatable results.
I basically transferred a “known good horizon line” on my garage door with painter’s tape.
And align the bottom edge of the “second” camera in Live View to the painter’s tape horizon line.
Shoutout to @rcg530 and another DCT member whose name escapes me right now for helping me figure that out.
Unfortunately this only works with multi-channel cameras.
The single channel A119 Mini 2 lens alignment is still elusive to me, and you can see I mucked it up with too much sky.

About the test footage I gathered.
I filmed daytime & night time footage of my usual highway / city test loops.
It will take a few posts to upload all the footage.
Testing notes;
Now that we have STARVIS 2 sensors I’m seeing less of an impact from using a CPL Filter at night, so from now on all my night time test footage will have the CPL Filter installed, unless otherwise noted.
The A229 Pro Rear camera does NOT have an “officially available” CPL Filter.
All settings are default, except for Bitrate that is always set to Maximum.
All firmware is the most current / up to date available from the official Viofo website.

Daytime Highway:
Front;

Rear;

Night Time Highway:
Front;

Rear:

Stay tuned for day / night CITY driving next.
-Chuck

 

[Karagandinez]

Rear;

On cameras mounted on the rear window there is too much sky in the frame.

 

[Panzer Platform]

On cameras mounted on the rear window there is too much sky in the frame.

Correct, I will fix.
At least they are both the same. lol

 

[Karagandinez]

At least they are both the same. lol

This doesn't affect anything.