Vantrue n4s pro - parking mode settings

[Migot]

Hi, I bought the N4 Pro S and have a question about the parking mode settings. I've read that the camera takes an unusually long time to wake up after detecting an impact, so long that it may miss the event. Do you have any suggestions on how to best set this up to buffer the recording? I connect the camera via the VP03 (II) to a 70MAI P01 power bank.

 

[Jeff_Vantrue]

Thank you for your question. We recommend tuning on Quick Start Collision Parking Mode. In this mode, the camera will power on roughly 3 seconds after detecting an impact.
If power consumption is not a major concern for you, you can turun on Motion Detection parking mode. With Motion Detection enabled, the camera can record with a 10-second pre-buffer, capturing footage from before the incident occurs.

 

[Migot]

Thanks for the reply. Can using low bitrate mode be combined with collision detection? I mean, if the camera is recording continuously, if it senses an impact, it will save the footage to the event folder, or do I have to manually browse the files?

 

[rcg530]

Thanks for the reply. Can using low bitrate mode be combined with collision detection? I mean, if the camera is recording continuously, if it senses an impact, it will save the footage to the event folder, or do I have to manually browse the files?

I recently completed my power consumption testing for the N4 Pro S. You can only select one parking mode type at a time. I did find that when low bitrate parking mode was enabled, the dash camera firmware would move the currently recording low bitrate video file to the "Event" directory when an impact event was detected.

My full power consumption and parking mode time estimate results can be found in this post: N4 Pro S - Power Consumption Test Results

 

[Migot]

I recently completed my power consumption testing for the N4 Pro S. You can only select one parking mode type at a time. I did find that when low bitrate parking mode was enabled, the dash camera firmware would move the currently recording low bitrate video file to the "Event" directory when an impact event was detected.

View attachment 88553

My full power consumption and parking mode time estimate results can be found in this post: N4 Pro S - Power Consumption Test Results

What's the best way to check this? I have low bitrate mode set, but unfortunately, I don't receive notifications on my phone after 1 minute. It only worked when I changed the parking mode to collision detection. But if I have low bitrate mode and, for example, I slam the door in park mode, I don't get any notifications, and the recording is in the parking directory, not in the collision directory. Is there a way to configure this?

 

[rcg530]

What's the best way to check this? I have low bitrate mode set, but unfortunately, I don't receive notifications on my phone after 1 minute. It only worked when I changed the parking mode to collision detection. But if I have low bitrate mode and, for example, I slam the door in park mode, I don't get any notifications, and the recording is in the parking directory, not in the collision directory. Is there a way to configure this?

I haven't tried the N4 Pro S with the LTE module yet. If the low bitrate file is still present in the "Parking" directory after the impact event took place, the N4 Pro S did not detect the impact.

I reviewed my power consumption test video files created during the low bitrate parking mode test. I confirmed the low bitrate parking videos that were recording when I strongly "tapped" the stand the N4 Pro S front camera was mounted on were moved the "Event" directory [A,B,C files].

Yesterday, I drove my car with the N4 Pro S dash camera. The "Event" files from that date are only from while I was driving, not parked in low bitrate parking mode. The five other dash cameras in the car detected parking mode impact events when I closed my driver side front door, but not the N4 Pro S. There's no sensitivity setting for impacts when you configure the low bitrate parking mode, so I'm not sure how to address the N4 Pro S not detecting impacts in real world impact situations. I just reviewed all of the "Record" settings. There's no specific setting for impact detection in parking mode except when you select "Collision Detection" parking mode. I'll ask my Vantrue contact for more info on this topic.

 

[Migot]

So it's not a settings issue, but a software glitch? I've also noticed that when you're driving and hit a bump, the camera often thinks it's an accident. You can hear a distinctive clicking sound. Do you have any answers regarding incident detection during parking mode? It would be useful if these two functions could be combined. And if you have low bitrate mode and physically hit the camera, does it detect collisions?

 

[rcg530]

So it's not a settings issue, but a software glitch? I've also noticed that when you're driving and hit a bump, the camera often thinks it's an accident. You can hear a distinctive clicking sound. Do you have any answers regarding incident detection during parking mode? It would be useful if these two functions could be combined. And if you have low bitrate mode and physically hit the camera, does it detect collisions?

Vantrue has stated there are two distinct G-sensor algorithms available for use [built-in vs application layer]. The "built-in" algorithm can only be used when the "application" is not in use. That means the "built-in" algorithm is only available to collision detection parking mode. The sensitivity setting available for collision detection parking [1 to 5 with 3 being the default] define how sensitive the G-sensor is to impacts in that one parking mode.

The second algorithm is available to the "application" [for parking modes that means low bitrate, low frame rate, and motion detection parking modes]. Vantrue stated they are already setting the sensitivity values their maximum values for this g-sensor algorithm [no user adjustable setting].

Based on our testing, it would seem those "maximum" settings are not sensitive enough for typical impacts in those three parking modes. It does appear that a very strong impact [see my power consumption parking mode test screenshot above] while in low bitrate parking mode will result in those videos being placed in the "Event" directory. It will detect impacts in that parking mode, but it seems to take a lot more force than one would expect.

I'll review more of my recent drives in the car with the N4 Pro S dash camera. I'll follow up with Vantrue again.

 

[rcg530]

With the N4 Pro S in my car, I found one time that an impact event resulted in the low bitrate parking mode video files to be placed in the "Event" directory. I had closed the front passenger side door which is close to the N4 Pro S installation location [about half way to the right side a-pillar]. I believe there should have been more impacts detected by the N4 Pro S.

Comparing to the VUEROID S1-4K 1-channel dash camera in that same car, there were far more events detected by that dash camera. The S1-4K's parking mode is "Impact & Time-Lapse".

Comparing to the Thinkware U3000 Pro 2-channel configured for "Radar" parking mode:

The radar detected motion event recording files are placed in the "motion_timelapse_rec" directory. Only the impact events are created as "PAK" files in the "parking_rec" directory.

 

[attila24nagy]

I would repeat @Migot's question, a combination of two parking modes.

Thanks for the reply. Can using low bitrate mode be combined with collision detection? I mean, if the camera is recording continuously, if it senses an impact, it will save the footage to the event folder, or do I have to manually browse the files?

 

[attila24nagy]

Greetings. I have an N4Pro S along with an LTE module, when I want to download a file from the camera's SD card via the LTE connection, the camera restarts and I can't download. I mention, the camera is in low bitrate parking mode. Any solutions or suggestions?

 

[rcg530]

Greetings. I have an N4Pro S along with an LTE module, when I want to download a file from the camera's SD card via the LTE connection, the camera restarts and I can't download. I mention, the camera is in low bitrate parking mode. Any solutions or suggestions?

I installed a Vantrue LTE module into my car and paired it with the N4 Pro S dash camera in that car. I had the N4 Pro S already configured for Low Bitrate 1080p 15 fps parking mode. Front camera firmware is EFA301.

I was able to successfully download a low bitrate parking mode file [112 MB] over the LTE connection, but it took a very long time [35 minutes]. The transfer speed was an abysmal 0.053 MB/second. The Vantrue LTE module showed a signal strength of 2 [Green LEDs on LTE module or bars in the Vantrue app]. I'll have to try and find a location where the signal strength is 4 bars to see how much the signal strength impacted the transfer rate [upstream bandwidth from the LTE module to the LTE network]. My phone was connected to the internet via a high speed Wi-Fi connection. My phone had plenty of downstream network bandwidth to download the file quickly.

Downloading the video file results in the N4 Pro S exiting low bitrate parking mode [pausing all recording] to handle the download of the video file. During the 35 minutes the video file was being transferred to my phone, the N4 Pro S was not recording anything. When the download finished, the N4 Pro S resumed normal recording mode for a short time and then it re-entered low bitrate parking mode again.

Download of video file started at 10:44 and finished at 11:19:

Parking mode low bitrate files showing the time gap between recording files while downloading the file over the LTE connection

 

[Jeff_Vantrue]

Greetings. I have an N4Pro S along with an LTE module, when I want to download a file from the camera's SD card via the LTE connection, the camera restarts and I can't download. I mention, the camera is in low bitrate parking mode. Any solutions or suggestions?

Sorry to hear you’re experiencing this issue while downloading videos.
Please try updating your dash cam, LTE module, and the app to the latest versions and see if that resolves the problem.
If the issue persists, could you please send us the app log files? This will help us further analyze the cause.