E360 Parking Mode with Hardwire Kit

[mikek753dct]

Hello all,

This is my review and installation steps for E360 Hardwire Kit.
Note: the E360 dashcam for Parking Mode to work correctly requires new 3 wires VP05 hardware kit, that 3rd wire is connected to the ACC fuse. Any other 2 wires or old hardwire kit might not work, so be sure to use new 3 wire hardware kit for the E360.

The hardwire kit has all 3 fuse sizes for easy installation.
The install process took me about an hour as I don't do it everyday, while easy for DIYer.
The most time it took me to wire type-c cable through car dashboard due to size of that connector, everything else was straightforward.

The hardwire kit VP05 has worked as expected and cut off camera to avoid complete car battery discharge at selected cut off voltage.
The kit has 3 settings to protect car battery - 11.6V, 12.0V, 12.4V for normal 12V car battery.
Also it works with 24V battery for trucks with the cut off - 23.6V, 24.0V, 24.4V.
It has convenient display for current battery voltage, so you know current car battery state.

 

[mikek753dct]

Collision Detection Parking Mode
This Mode has 2 options:
Power Save - Standby 0.025A, wake up time 10 sec , recording 30 sec at 1A
Quick Start - Standby 0.22A , wake up time 3 sec, recording 30 sec at 1A

This Collision Detection Mode is for the less car battery usage, when a few car driving per week, that isn't enough to recharge car battery daily.
This is where Power Save option will not draw power almost at all and car battery would be good for a week without driving, but the drawback is the long 10 sec wake up time upon an impact, so there is a risk to miss an impact details, like hit and run, or someone will walk away in 10 seconds.
The next Quick Start uses 10x power, while almost 4x less then Motion Detection Mode, also has 3 seconds delay. I think this is Ok compromise between what will be recorded and power usage for infrequent drives, or about each other day car driving to recharge car battery.

 

[mikek753dct]

Motion Detection Parking Mode

This is real Buffering Recording, that records all the time, while upon Motion Detection resulting file will be about 10 seconds before the Motion Event time and the next 30 seconds after.
This is the most useful Parking Mode.
Standby 0.66A , recording 40 sec at 1A
This mode will drain car battery fast, and every day 2 - 3 driving would be needed to recharge car battery.
Another option for this mode to have extra power bank or even power station, while this is outside of this scope topic.

I like how E360 detects any motion from all 3 cameras and also records all 360 view, while in some cases it could be overkill.

 

[mikek753dct]

Low Framerate Parking Mode
This mode at 5FPS uses 0.72A, or about the same as Motion Detection, but records all the time in parking.
The good side that no any detections are required, and the trade off is that will be a lot of files that you will need manually screen to find the one.
I'd recommend this mode for very specific situations when you want to record for a few hours none stop.

 

[TonyM]

Collision Detection Parking Mode
This Mode has 2 options:
Power Save - Standby 0.025A, wake up time 10 sec , recording 1 min at 1A
Quick Start - Standby 0.22A , wake up time 3 sec, recording 1 min at 1A

Which FW version are you using?

On my desk I am currently testing the E360 in 2CH configuration (Front+Cabin) on FW VT-EDK271, with a Vantrue 512GB card and VP01 HW kit.
I see the same standby power consumption, but the wake up and record times are different:
Power Save: Standby 0.1W, Wake up time 17 seconds, Records for 30 seconds in 5.2K30 at 3.7W
Quick Start: Standby 1.2W, Wake up time 5 seconds, Records for 30 seconds in 5.2K30 at 3.7W

 

[mikek753dct]

Which FW version are you using?

On my desk I am currently testing the E360 in 2CH configuration (Front+Cabin) on FW VT-EDK271, with a Vantrue 512GB card and VP01 HW kit.
I see the same standby power consumption, but the wake up and record times are different:
Power Save: Standby 0.1W, Wake up time 17 seconds, Records for 30 seconds in 5.2K30 at 3.7W
Quick Start: Standby 1.2W, Wake up time 5 seconds, Records for 30 seconds in 5.2K30 at 3.7W

I have last current FW that I updated to

I started from using existing VP01 HW Kit and got many issues, till I upgraded to 3 wire VP05 HW Kit
There is something in VP05 with 3 wires (additional ACC wire) that make E360 correctly work for Parking Mode, its different.
yes, I have 5.2K30 + 1440P

Can you test with VP05?
I spent about 2 weeks with old VP01 had tried to make it to work, but after I went with 3 wires VP05 all started working as expected.
The reason I put in red my notice.

 

[TonyM]

I have last current FW that I updated to



I started from using existing VP01 HW Kit and got many issues, till I upgraded to 3 wire VP05 HW Kit
There is something in VP05 with 3 wires (additional ACC wire) that make E360 correctly work for Parking Mode, its different.
yes, I have 5.2K30 + 1440P


Can you test with VP05?
I spent about 2 weeks with old VP01 had tried to make it to work, but after I went with 3 wires VP05 all started working as expected.
The reason I put in red my notice.

I have the VP01(II) which is a 3-wire HW kit and it has been working perfectly on my desk setup. I am running a few indoor tests before installing the HW kit in the car. Perhaps you had an older 2-wire version of the VP01?



The only other difference in your setup is that you are running 3CH whereas I was running 2CH. I am planning to run some 3CH power consumption and bitrate tests tonight so I will see if the collision detection operates differently in 2CH and 3CH modes.

 

[mikek753dct]

yes, I have old hardware kit with 2 wires only, which didn't work well for E360.
Yes, I have all 3CH up and running.
Please, update with your findings.

 

[TonyM]

On my desk I am currently testing the E360 in 2CH configuration (Front+Cabin) on FW VT-EDK271, with a Vantrue 512GB card and VP01 HW kit.
I see the same standby power consumption, but the wake up and record times are different:
Power Save: Standby 0.1W, Wake up time 17 seconds, Records for 30 seconds in 5.2K30 at 3.7W
Quick Start: Standby 1.2W, Wake up time 5 seconds, Records for 30 seconds in 5.2K30 at 3.7W

With a 3CH setup I am getting the same wake up and record times in collision detection mode that I reported in 2CH configuration:

Power Save: Standby 0.2W, Wake up time 17 seconds, Records for 30 seconds in 5.2K30 at 5.3W
Quick Start: Standby 1.2W, Wake up time 5 seconds, Records for 30 seconds in 5.2K30 at 5.3W

When the E360 is in normal recording mode, 5.2K + 1440P, this is what I see on screen. The third symbol from the left indicates a loop duration of 3 minutes.

When I tap the camera to trigger the g-sensor, this is the screen after it wakes up. There is a collision indication symbol in orange in the centre, and the loop duration is shown as 30s.

 

[mikek753dct]

@TonyM

So far I think about we have different HW Kits.
I can't explain power usage difference.
What readings you are using?
I use readings from USB reader for the E360 power usage, I don't know how much is total power usage before HW Kit.
How much power usage difference you see based on your Power Supply and USB meter? How much power HW Kit uses?

 

[TonyM]

I'm also using a USB power meter between the HW kit and the camera. I don't think the power consumption is any different. It's just the duration of the collision video clip which seems to be 30s for me but 60s for you.

I'm not sure it's worth more testing time. I'll report my findings back to @Jeff_Vantrue

 

[mikek753dct]

@TonyM

I retested Parking Mode and
Collision Detection records for 30 sec
Motion Detection records for 40 sec, with 10 sec buffered
All power usage are the same as in my original results

 

[EmailPJC]

Collision Detection Parking Mode
This Mode has 2 options:
Power Save - Standby 0.025A, wake up time 10 sec , recording 30 sec at 1A
Quick Start - Standby 0.22A , wake up time 3 sec, recording 30 sec at 1A
..............
The next Quick Start uses 10x power, while almost 4x less then Motion Detection Mode, also has 3 seconds delay. I think this is Ok compromise between what will be recorded and power usage for infrequent drives, or about each other day car driving to recharge car battery.

Interesting. I was in doubt as to which configuration to use and this clears things up a lot. I had tested with fast start and collision detection and the loss I recorded was 2.5sg.
--------------
Interesante. Tenía dudas de que configuración utilizar y esto aclara mucho las cosas. Yo había realizado pruebas con el inicio rápido y detección de colisiones y la pérdida que registré fue de 2,5sg.

 

[steveo3002]

i posted on my own review but maybe chime in here too

would it be possible to enable more options? like record full time for lets say an hour incase i run into a supermarket etc , then default to motion or impact for when at home , or clock based settings so it can record when at work then back to motion for when at home in the driveway

would also be nice to flag or mark any impacts so that its easier to look through dozens of files for an incident

how about it @Jeff_Vantrue

 

[Jeff_Vantrue]

Thanks for your suggestion! While it would be great to have the ability to set different modes for each situation, there are a few limitations with dash cams in terms of customizing settings for every scenario and will make the dash cam be more complex to use.
As for the parking mode videos, our R&D team is actively working on this feature. Once it's ready, the videos will be stored in a separate folder to make it easier to manage and review them.

i posted on my own review but maybe chime in here too

would it be possible to enable more options? like record full time for lets say an hour incase i run into a supermarket etc , then default to motion or impact for when at home , or clock based settings so it can record when at work then back to motion for when at home in the driveway

would also be nice to flag or mark any impacts so that its easier to look through dozens of files for an incident

how about it @Jeff_Vantrue

 

[carusos]

So the 3ch takes 3 or 5 seconds?

This is very important for me and I'm evaluating between this and the s1 pro max which seems to be around 2 seconds

With a 3CH setup I am getting the same wake up and record times in collision detection mode that I reported in 2CH configuration:

Power Save: Standby 0.2W, Wake up time 17 seconds, Records for 30 seconds in 5.2K30 at 5.3W
Quick Start: Standby 1.2W, Wake up time 5 seconds, Records for 30 seconds in 5.2K30 at 5.3W

When the E360 is in normal recording mode, 5.2K + 1440P, this is what I see on screen. The third symbol from the left indicates a loop duration of 3 minutes.
View attachment 76704

When I tap the camera to trigger the g-sensor, this is the screen after it wakes up. There is a collision indication symbol in orange in the centre, and the loop duration is shown as 30s.
View attachment 76705

 

[Constantinus]

I have not installed my E360 yet, and the consumption in Motion Detection mode (with pre-buffering, the others seem useless for dents or "interested persons") that I planned to use as a parking surveillance camera is somewhat disappointing. Maybe it will not last a whole workday in the parked car.

How about radar-based motion detection? Thinkware, DDPai, AZDome have it, some lesser known brand dashcams have it. Vantrue, 70mai don't have it.
As far as I've read, these radar motion detectors consume very little power in standby (10mW they claim). I have not measured it myself.

I tested such a dash cam with built-in radar. It detected me walking already a few meters in front of the car, at least a meter behind the car, and, surprisingly, approaching the car from the front or rear side windows. True, there was nothing else moving in the vicinity of the car. Still, a few seconds pre-starting recording when the perpetrator is not even touching the car is useful. Even when a car bumps into you, it will be recorded before it actually touches your car. If it comes at 100km/h, then no, it won't, but in a parking lot?

• Vantrue could add an external, paid extra radar module, together with extra functionality in the firmware and in the app.
• There are separate, aftermarket modules for this specific purpose. They have a Type C USB input, radar motion detector, Type C output. The output is powered only if the module senses motion, otherwise the output is cut off. Pretty simple and universal. I'm thinking of putting this inbetween the Vantrue 4G modem and the E360. I can still access the 4G module anytime (850mW standby), but the camera itself will stay powered off, unless the radar motion detector senses something and turns it on, then it films. Maybe the camera even connects to the 4G module and uploads the suspicious footage. I'm not sure how well the E360 or the 4G module handle the frequent disconnects. Of course, Vantrue (and other brands) use the Type C lines in their own proprietary way, so this aftermarket universal radar module might not even power the E360 at all.

The barebones small radar sensor+automatic switch itself, with wires sticking out, is about 3$ retail.
Heck, I ordered one such radar module for dash cameras, cost me 18$. Will test it when it arrives and have some time. I have the E360, its 4G module, will connect this radar module between them. Would be great if @Jeff_Vantrue could let the dev team know about this idea. It does not seem too complicated to implement. Source some reliable radar modules, implement either just the correct wiring, no software changes, or do the wire matching+firmware+app changes. Maybe one could still wake up the LTE-radar-camera remotely and look around, if implemented correctly.
This could work for other Vantrue cameras, too. ~1A just for parking monitoring is impractical.

Universal radar-based motion detection module for dash cameras (one model, there are several); this one is supplied from the OBD port, but it can be three-wire BAT-ACC-GND, that's not the point; the module itself is a small, 4-5cm plastic square:

Edit: Nope, the E360+LTE-01, firmware 2025-10-21 10:23 E360_VT-EEJ101, does not work well with this aftermarket radar based motion detector power supply. Mostly because the E360 takes ~14 seconds to boot and start filming, from when it receives power. The LTE module also takes a few seconds to boot up. I feel that this is too long: even if the radar sensor "feels" the "enemy" meters away from the car, 14 seconds to start filming might miss the beginning of the event.

Worse, this specific radar-based motion detector module does not seem to work properly. It resets after every 25 seconds - bringing the LTE module and the E360 with it - even with motion in front of it, as indicated by its red LED. When it has a very light load - not 5-6W of the E360 filming - it does not reset. Its output is rated at 3A, but it seems it can't handle even an 1A load.

A bit off topic: speedtest.net through the LTE-01's Wi-Fi hotspot gives 35Mbps download from my 4G provider. Not bad.

 

[Constantinus]

i posted on my own review but maybe chime in here too

would it be possible to enable more options? like record full time for lets say an hour incase i run into a supermarket etc , then default to motion or impact for when at home , or clock based settings so it can record when at work then back to motion for when at home in the driveway

would also be nice to flag or mark any impacts so that its easier to look through dozens of files for an incident

how about it @Jeff_Vantrue

Also, location (GPS) based settings profiles would be interesting, although not as reliable as time based ones. When at Home/Work, do the lowest power parking monitoring, or none at all. Warm-start and read GPS (or LTE location) only every couple of minutes, to save battery but still detect theft/towing. If outside these Zones, however, film the living daylight out of everything around the car. Film the living moonlight as well, we have Starvis 2s, after all.
I know, not with today's memory prices.

 

[Jeff_Vantrue]

Also, location (GPS) based settings profiles would be interesting, although not as reliable as time based ones. When at Home/Work, do the lowest power parking monitoring, or none at all. Warm-start and read GPS (or LTE location) only every couple of minutes, to save battery but still detect theft/towing. If outside these Zones, however, film the living daylight out of everything around the car. Film the living moonlight as well, we have Starvis 2s, after all.
I know, not with today's memory prices.

I am sorry that these features aren’t supported at the moment. Thank you for your suggestion and we’ll include it in our future evaluations.