Can You tell more about disabled ANPR on S3 cams?
With AcuPick enabled I don't see even plate snapshots.. Only in VMD standalone..
But not plate OCR at all on 5xx2-S3...
Review: EmpireTech IPC-T58IR-ZE-S3 / Dahua 5842T-ZE-S3 - 8MP / 4K Turret Camera
- Thread starter Wildcat_1
- Start date
Can You tell more about disabled ANPR on S3 cams?
With AcuPick enabled I don't see even plate snapshots.. Only in VMD standalone..
But not plate OCR at all on 5xx2-S3...
A few weeks ago HIK presented new generation of DeepinMind cams (aka DarkFighter 2.0)..
They allowed to run 2 AI algorithms together in most combinations (like IVS + VMD on cam).
And added AcuSearch 1.0 as part of IVS.
But there are still some limitations (some functions like face mosaic or ShotN disables second AI function)..
And ANPR is not a part of Video Meta Data but separate mode...
Yes these are great cams, always enjoy them BUT I don't like the mounting options they went with on design. Cameras themselves are fantastic BUT if they built them to interface with regular PFA square mounts OR even had mounting kits to allow mounting into those, would be ideal.
Yes there are limits on the SOC's in the 5x S3's BUT they are not being pushed yet. The S3's represent a series of cams where for the first time in recent time (for 5x series) they are not hitting the theoretical or real world limits of the SOC, yet.
Yes the NPU usage in 7x series is different and certainly more methodical in execution. My hope is that with NPU functionality (and price) dropping that an S4 series of cams will truly knock the capabilities and critically, real world performance, out of the park.
Yes I believe we're getting there. The Xi NVR's for example are incredibly good at what they do. The S3 cams are also very capable as I've mentioned and shown here. Some of the limitation are self imposed by Dahua and others (hence what I mentioned above), others are regressions which in any dev work, can exist BUT critically need to be resolved. This is one of the things I try to work on with Dahua in every release and in an ongoing fashion because TBH there are a lot of regressions and a lot of issues. I'm pleased to say that this work (although takes me many hours) has led to some great wins for all of us. The sad part is that for Dah, Hik and others, the lifecycle of the cams / NVR's now is so short. All are very quick to move onto new products and EOL the old. In a lot of cases as we both know, this means new SOC's with new functional code which means that last generation (and certainly 2 or more generations back) fail to ever get the needed fixes (regression, feature or tweak), in place due to dev priority being focused elsewhere. Thats why what we do here in this industry is so important. Raising awareness to manufacturers on critical need, focused issues etc in efforts to get a better (or improved) end product. Similarly though its just as critical in educating end users/business on how to scope, install, configure and deploy correctly and in an optimized fashion for each location, required target capture environment, threat model (where appropriate), as part of an overall solution.
- Yes, they do support it just not implemented / purposefully disabled in current FW. Couple of ways you can see this:
- Throw on AcuPick as an example, go into your NVR of choice (I currently have these hooked into both EI's and XI's) go into AI Settings (on EI) or AI / Parameters on XI.
- Then go down to ANPR, choose the channel you have the SR camera(s) on and you will see that you can enable it for the cam (not to be confused with NVR AI processing), this is strictly reading the supported attributes of the cam itself. You won't get the 'Config is Not Supported' error that you would with a truly unsupported cam (think S1 or S2 versions that do NOT support at all).
- You'll notice (depending on NVR) you can enable Block List Sync etc (XI where you can set database local or remote).
- On the cam you can sanity check as well. Go into Picture (for captured snapshots) in the camera and you'll see the drop-down of capture types.
- Choose ANPR and you'll see it captures 2 (of the usual 3) pictures, wide car, close up but critically even though the camera knows it can capture ANPR, does NOT, currently show Plate due to OCR being disabled in current FW.
- Critically IF you go into the Record menu (for video capture) and then choose ANPR from the selection, you will see NO video is captured at all, even when the Picture / Snapshots ARE recognizing and tagging the vehicle correctly as an ANPR capture.
This is VERY similar to what Dahua did with the early 49xxx that I mentioned as well except it was the reverse. In that implementation of FW for the S1 series cams they DID full ANPR up front (but was not called out as a feature) as part of Video Metadata processing and tagging. They then, under the covers unfortunately released new FW for S1 that disabled it (only showed car wide and close video + pics) and was missing completed in the S2 series of the same cam.
In the case of the S3, this remaining 10% functionality (the actual plate processing) appears to be completed but output and associated tagging is disabled at the moment. Again Video doesn't tag ANPR at all (currently) but Snapshots DO up to the point of the final display/using OCR output. It is 100% currently disabled in current FW. However, it is also 100% possible to deliver it, since the camera a) has the associated attributes, tagged and b) is only limited but the current FW release. My hope is that with what I've shown Dahua and how code is correctly attempting to process, that they do unlock that gate.
OMG... I hate mounting system & junction box on 5xx2H/7xx2..
Usually You can loosen the screw to correct the camera position only 2-3 times..
After that the screw is good for nothing.
Also there is no space for all 10? cables with plugs going outside cam in included junction box..
And those cams are not compatible with any other on the market..
I'm not sure - in first version of internal Dahua presentation about AcuPick 2.0, there were presented more human/car attributes for 5xx2-S3..
they cut the list in second version & final firmware..
Maybe CPU/GPU part of 5xx2-S3 SOC didn't hit limits, but it looks like NPU part had..
HiSilicon is main SOC manufacturer for all Chinese mobiles..
SOC for mobiles are the fastest growing category of integrated circuits, which is pushing the entire SOCs production market forward.
SOCs for CCTV are simply cut / limited / cheaper versions of SOCs for mobiles.
Amen, brother
Every time I deal with Dahua Poland representatives, I literally go on a tirade about the stability and quality of their software. Especially mobile applications (DMSS) and for computers. But also firmwares.
I am a programmer and I can determine what is wrong with their apps. Unfortunately, few people want to hear that..
From what I have noticed, people at Dahua Poland are afraid to report problems in software or firmware to Chinese HQ.
And they are even more afraid to enforce so that the Chinese will fix it.
The only situation where they doing more are when there is huge project (hundreds / thousands of higher models cams) which is at risk (its sale) due to some errors or lack of functionality.
I did software for a large tech company, and could have written the same thing. One of the workers' mottoes was "There's always time to do it over, but never time to do it right".
Thanks, unfortunately its hard to get the customer to spend on the 7xx models. Hoping they may come out with cheaper APNR models in the future.
Definately waiting on Acupick 2.0. Thought we would be able to use AcuPick 1.0 over web service with this XI but guess we have to wait for now.
Also separately on the 5xx EI when you add Face Detect by Recorder you only get 4 channels of SMD by Recorder.
Removing Face Detect you get full 8 channels of SMD by recorder.
I also found SMD by recorder doesnt label the Human/Vehicle events properly alot of the time.
Most new cameras I am using have Human/Vehicle detect now though.
Lots of good info in this thread, will spend some time reading the latest posts.
You can use AcuPick 2.0 features without AcuPick 2.0 interface on 600-xi..
setup AcuPick on camera..
on recorder in AI search -> human / vehicle menus You will have possibility to search human / vehicles by attributes like in AI Search -> AcuPick menu on 5xxx-EI..
in reality Acupick 2.0 = AcuPick 1.0 (3d modeling, searching by image) + simplified Video MetaData (searching human / vehicles by attributes)..
5xxx-EI have 8 AI units.. SMD and Face Recognition (when face detection is done on cam) is using 1 AI unit, IVS 2 AI units, Face detection & Recognition 4 AI units...
Why are You using SMD? it creates a lot of false positives even when run on camera..
In AcuPick 2.0 mode on 5xxx-S3 cams, You have both: mini IVS (tripwire/intrusion) and mini Video MetaData (human/vehicles without face/plate snapshots)..
for perimeter protection use IVS..
If You want faces, better solution is disable AcuPick on camera and use full Video MetaData... it generates human/vehicles/faces/non motor vehicles records with faces and plates snapshots and it works very well.. I run all external / street / gate cams this way on all installations with a new 5442-s3..
if you will contact me by DM, I can send you demo pages from searches on NVR done from 5442 or 7442 with full Video Metadata (no AcuPick mode)..
it can generate thousands records per day depending of street traffic.
Depends on your use case. You can just use full blown Video Metadata by itself in non-Acupick mode + Motion Detection IF you really want it. Personally I would stay clear of MD + SMD and instead as you know, I advocate for Video Metadata or now, AcuPick.
XI's are really good, I have one and love it BUT it is currently trailing behind the EI from an AcuPick 2.0 perspective. I have however addressed this with Dahua and asked that they release a new FW version ASAP for XI that looks to get to feature parity with EI, especially from an AcuPick perspective. This is needed, especially when Dahua themselves call out the XI in the AcuPick 2.0 press. XI is phenomenal WRT on NVR processing, especially from AI by recorder ANPR. EI is surprisingly good for the market its aimed at for sure and certainly a great value for money but it is lacking in certain on NVR AI areas. With that said, AcuPick 2.0 and specifically Map Tracks is very nice to see.
I plan on doing a deep dive for people here on EI vs XI, AcuPick vs VMD etc but at the moment am focused on an LPR challenge that was set (should have that up in the next day or 2) + the bug documentation for Dahua.
I currently only have Tioc cameras with Ivs function and use a 5208-p-ei recorder. I won't get my s3 cameras until next month.
Then use IVS as your main. The S3 cameras will blow your mind BUT as I continue to say (and will do in each video I do on these), you MUST dial in these carefully especially depending on target use case
Okay thank you. I bought the IPC-HFW5442H-ZHE-S3 version. Good choice or ?
Last edited:
You can send them this slide - this is Dahua AcuPick 2.0 presentation from June, where they promised AcuPick 2.0 firmware for 6xx-XI in July...
Again, depends on what you want to use it for target wise (including distance to, type of, lighting etc) but for general surveillance then yes thats a good model. Consider the Z4 version if you want something with extra reach. That is the one I am doing the challenge with currently.
Yep or use their News article they published that clearly shows the same too
If You enable FULL Video MetaData (without AcuPick) then You have only VMD on that camera. there is no SMD or IVS - full AI power is going to FULL version of SMD with all features (faces, car plates snapshots etc).. You can add IVS on recorder (AI by recorder) for that camera...
I use FULL VMD on street cams - so usually don't need IVS.. VMD gives me much more..
No one here is using SMD at all - SMD is a toy..
This is why I strongly advocate for VMD. Also why its frustrating when you see new cams in Mid and High end series that do NOT have VMD as standard