70mai 4K Omni - Testing/Review RCG

I put together a hardware installation video along with a setup and configuration video for the 4K Omni and UP05 hardwire kit.


 
I put together a hardware installation video along with a setup and configuration video for the 4K Omni and UP05 hardwire kit.


The placement of adhesive between the defroster lines is misleading, as even placing them on the defroster lines will never lead to it melting. They barely get warm. Never ever had that issue in all my years of mounting dashcams on the rear windscreen.
 
The placement of adhesive between the defroster lines is misleading, as even placing them on the defroster lines will never lead to it melting. They barely get warm. Never ever had that issue in all my years of mounting dashcams on the rear windscreen.
You may not have experienced that behavior, but I have. It’s not a good idea to place a static sticker or the adhesive pad material on a defroster heating element grid line. Even if your vehicle’s defroster grid lines don’t heat up enough to cause damage to the adhesive pad, the grid line can be damaged when the adhesive pad is removed when removing the rear camera depending on the age and type of heater grid material.
 
You may not have experienced that behavior, but I have. It’s not a good idea to place a static sticker or the adhesive pad material on a defroster heating element grid line. Even if your vehicle’s defroster grid lines don’t heat up enough to cause damage to the adhesive pad, the grid line can be damaged when the adhesive pad is removed when removing the rear camera depending on the age and type of heater grid material.
I would wager it was some other external factor and not the defroster line, because they heat up to 29 Celsius and then turn off after ten minutes or so. So I doubt very much it's due to the defroster line and probably something else like high heat from the sun in summer perhaps.

Yes, well that's captain obvious there about the grid lines being damaged when removing adhesive. Electrostatic sticker would be a better idea to mitigate the removal of adhesive.
 
I've now had three different firmware versions installed [1.0.78ww, 1.1.88ww, 1.2.96ww] in two different 4K Omni 2-channel dash cameras. Real world driving [Normal] footage is not CBR [constant bitrate] since the front camera video stream bitrate ranges from the low 30 Mbps range to the upper 70 Mbps range depending on how much motion is present within the field of view. The rear camera footage [1080p] bitrate ranges from upper 10 Mbps range to the low 17 Mbps range. The video files created for uploading to the cloud [if required] for the front camera do appear to be CBR video files in the low 4 Mbps range.

Here are some file listings from today's drive. The column "Data Rate" match up with the video stream bitrate as reported by the ffprobe utility.

Video files with firmware 1.2.96ww installed [Front - stored in the "Normal\Front" directory] - 3840x2160 30fps
[click to see full size image]
1744138829630.webp

Video files with firmware 1.2.96ww installed [Front video files for potential cloud uploading - stored in the "Normal\.s_Front" directory] - 1280x720 30fps
[click to see full size image]
1744138636396.webp

Video files with firmware 1.2.96ww installed [Rear- stored in the "Normal\Rear" directory] - 1920x1080 30fps
[click to see full size image]
1744138300428.webp
 
With the 4K Omni [X800] connected to the 70mai cloud with the UP04 or UP05 4G LTE enabled hardwire kit, your 70mai app will get push notifications for collision and suspicious person [motion detection] events detected by the X800.

There are some "Alarm center > Video upload settings" that govern what video(s) are and are not uploaded to the 70mai cloud. To access the "Video upload settings", you click on the "Alarm center" link under the 4K Omni camera entry on the home page of the app. In the upper right corner of the "Alarm center" screen, click on the three (3) dots. You will then be shown the "Video upload settings" screen.

[click to see full size images]
1744141410447.webp1744141474815.webp1744141524366.webp

There are settings for "Collision detection" and "Motion detection".
  • Collision detection events
    • Supports the uploading of video for the front camera video [Parking\.s_Front 1280x720 15fps].
    • You can decide if you want the extended [rear] camera video uploaded as well for collision detection events.
      • The extended [rear] camera videos uploaded will be the 1920x1080 15fps videos located in the Parking\Rear directory on the memory card.
  • Motion detection events
    • Only the front camera video [Parking\.s_Front 1280x720 15fps] is uploaded to the 70mai cloud.
    • Extended [rear] camera
      • Is not used by the AI motion detection logic to determine if a suspicious person is near your vehicle.
      • Extended [rear] camera video [Parking\Rear 1920x1080 15fps] is captured, but it is not uploaded to the 70mai cloud.
 
Since the 4K Omni dash camera allows multiple sentinel [parking] modes to be enabled at the same time, it's been asked how much power does the 4K Omni consume if multiple sentinel modes are enabled at the same time.

I reconfigured one of my 4K Omni dash cameras to be powered by a UP03 hardwire kit. The 4K Omni has firmware v1.2.96ww installed. I did not retest the other running modes of the 4K Omni, but I did add a test of the 4K Omni 2-channel with all sentinel modes enabled [collision, motion and time-lapse]. It appears the power consumption with all three sentinel modes enabled is the same as it is with only collision detection or motion detection enabled. Sentinel mode [all three] consumed on average 288 mA @ 12.6V or 3.63 Watts.

[click thumbnail to see full size image]
1744241205601.webp
 
In regards to your install video where others recommend wrapping a wire around the fuse leg, as you say it is not ideal. I don't like these mini taps but they get used a lot and do not damage the fuse block.

fuse-tap.webp



Amazon Mini Fuse Tap blades

Wiring Products Fuse Tap Connectors

YMMV, these work great, but not everyone likes them.
 
In regards to your install video where others recommend wrapping a wire around the fuse leg, as you say it is not ideal. I don't like these mini taps but they get used a lot and do not damage the fuse block.

View attachment 79476



Amazon Mini Fuse Tap blades

Wiring Products Fuse Tap Connectors

YMMV, these work great, but not everyone likes them.
While this type of tap does not expand the fuse box fuse socket contacts, it relies on a perfect/tight fit of this item around the leg of the fuse. I've found these in a couple of my previous [used] cars when I purchased the car. One worked okay, but the second one was not grabbing the leg of the fuse tightly enough so there was a random power loss while driving.
 
While this type of tap does not expand the fuse box fuse socket contacts, it relies on a perfect/tight fit of this item around the leg of the fuse. I've found these in a couple of my previous [used] cars when I purchased the car. One worked okay, but the second one was not grabbing the leg of the fuse tightly enough so there was a random power loss while driving.

That is the number one issue with them and is why I tend to avoid them. If these mini taps fit snuggly, they are useful in a auto fuse box that has an empty slot for power and an empty slot for switched. The end will accept a dual / piggyback, or double headed spade connector and enable a person to tap two devices with power from one slot. A big space saving for those tight fuse boxes, trick is have a mini tap that is tight fitting to the leg of the fuse.
 
they are useful in a auto fuse box that has an empty slot for power and an empty slot for switched
To use one of these taps, usually requires the insertion of a [full] fuse into the fuse box fuse socket. If the fuse box fuse socket is "empty", adding a fuse into that fuse box fuse socket can potentially be a problem [not always]. If the fuse box fuse socket only has connectors on one side [power side] then adding a fuse into the fuse box fuse socket should not be a problem. If the fuse box fuse socket has connectors on both sides of the fuse socket, adding a fuse into the fuse box fuse socket can potentially lead to unexpected power drains / issues. Auto manufacturers will often use the same fuse box in multiple models or sub-models of their cars with various accessories/features. If a fuse is added to an "empty fuse socket" which has a connector on the "load" side of the fuse socket, power is now available to what ever the "load" side of the fuse socket is connected to in the fuse box / vehicle. If the "load" side goes nowhere, then it's not a problem. If the "load" side of the fuse socket does provide power to something that didn't have power before, parasitic power drain situations or unusual module/feature operations may occur.

If I were to use one of these in an empty fuse box fuse socket, I might cut the fuse in half and use one of the halves to insert into the side that provides power to the fuse socket. The downside of only using one-half of the fuse is that it might not be as stable as the full fuse in the fuse socket. Again, I don't use this type of tap, but I can see their potential usefulness in certain situations.
 
That is a very nice summary and review. It is quiet interesting the AI uses a 'full facial definition' to determine if someone is looking at the car, and using that full face to trigger the camera to track the person.
 
That is a very nice summary and review. It is quiet interesting the AI uses a 'full facial definition' to determine if someone is looking at the car, and using that full face to trigger the camera to track the person.
There may be a combination triggering data inputs to the AI engine: detecting a human moving in some manner, walking speed, and/or having the person's face faced towards the 4K Omni front camera. I've tried different walking speeds. It doesn't seem to be the determining factor for the way I move/walk, but it could play a role in the AI logic. If I look at the front of my car while walking past the front of the car, that tends to trigger the event at a much higher rate than when I'm not looking at the car.

During yesterday's drive, I did find some AI motion detection events where the person(s) near the front of my car weren't directly looking at my car/4K Omni front camera, but the side and some portion of the front of their face was in view at least for a very small amount of time. So far, I have not found and 70mai has not shared the details [which may never happen] of the logic used by their AI engine to detect a suspicious person.

I'm liking the AI motion detection feature a lot more than I thought I would when I first started testing the 4K Omni. The biggest issue I have with it is that the rear camera is not used to determine when a spuspicious person is near your vehicle. It would be nice to have the rear camera included in the AI logic detection and possibly a setting to enable/disable using the rear camera in the AI logic if it causes the power consumption to increase dramacticly.
 
That is a very nice summary and review. It is quiet interesting the AI uses a 'full facial definition' to determine if someone is looking at the car, and using that full face to trigger the camera to track the person.
It might use face detection but I suspect the explanation is much simpler.

The NT98530 chipset has phase detect autofocus on board already, so knowing how phase detect works (versus contrast detection), I suspect that is how it's determining what to pick up on so quickly.

There may be other factors too that 70mai have added or implemented, who knows
 
It may be like loitering in Dahua/Hikvision IP cameras, where a person is detected and stays in the same area for a few seconds.
 
It might use face detection but I suspect the explanation is much simpler.

The NT98530 chipset has phase detect autofocus on board already, so knowing how phase detect works (versus contrast detection), I suspect that is how it's determining what to pick up on so quickly.

There may be other factors too that 70mai have added or implemented, who knows

Been pondering the PDAF. That is normally a two sensor setup on cell phones and cameras for a quicker focus solution. I can not find anything on the IMX678 where Sony claims PDAF, but, if Novatek added the core/hook/path for PDAF in their board, then I would think that 70Mai would need to put in the sensors or, the sensors are a part of the IMX678. If a part of the IMX678, the attached controller board would handle the PDAF. But...that is only random thoughts as I can't find any good documentation. πŸ™‚
 
.
.
I'm liking the AI motion detection feature a lot more than I thought I would when I first started testing the 4K Omni. The biggest issue I have with it is that the rear camera is not used to determine when a spuspicious person is near your vehicle. It would be nice to have the rear camera included in the AI logic detection and possibly a setting to enable/disable using the rear camera in the AI logic if it causes the power consumption to increase dramacticly.

Yes, that AI motion detection is intriguing me quite a bit and seems to be fairly sophisticated, or enough for the purpose it serves in a dash cam. Good point about the rear camera missing the AI logic, I suppose though power draw would go up a bit?

I look forward to seeing how this model matures in the next couple of releases. Should be interesting, but as it is, this dash cam looks like a winner to me.
 
Last edited:
Here's my final video in my series of videos for the 70mai 4K Omni 2-Channel dash camera.

7:49 Auto Off After Stop
I like this firmware setting, it’s almost like parking mode without hardwiring.
How does the camera know to start recording on the next engine start / drive cycle?
 
Been pondering the PDAF. That is normally a two sensor setup on cell phones and cameras for a quicker focus solution. I can not find anything on the IMX678 where Sony claims PDAF, but, if Novatek added the core/hook/path for PDAF in their board, then I would think that 70Mai would need to put in the sensors or, the sensors are a part of the IMX678. If a part of the IMX678, the attached controller board would handle the PDAF. But...that is only random thoughts as I can't find any good documentation. πŸ™‚
I'd say the support is all there on the Sony sensor too, would be surprised if it wasn't. You're right, PDAF is on cell phones but also mirrorless/DSLR cameras to aid with focus along with contrast detection.
 
Back
Top