Camera Analytics for HIKVision OEM
Completed
I am using OEM HIKVisio Camera which report modem number DT385-I, I believe these are the same as the DS-2CD2385FWD-I.
After setting up events in the camera, when I try and do create a camera rule for an Analytics event is tells me that Analytics is not available for my camera. Is this because this particular HIKVision camera does not support Analytics events or is it just the because the model number reported is not the HIKVision model number?
-
Norman, sorry to revive this thread, but do Dahua cameras use a similar API? I contacted support about my Dahua cameras not having analytics when flashed with generic unbranded firmware. (On v4 betas) If I flash the exact same camera with Dahua branded firmware, analytics are picked up. Each firmware has feature parity, just branding differences. This seems like something that could easily be resolved, but I was told you guys ONLY support analytics from AXIS, Hanwha, Hikvision, Digital Watchdog, and Dahua(in v4.0). That doesn't seem to line up with what Paul experienced here with his unbranded firmware Hikvision.
Thanks!
-
Hi Ryan,
My apologies for the delay in the response, but I was on a holiday.
Obviously, Dahua uses their own API and it might vary in their OEM version.
You mentioned correctly that the Dahua analytics will be supported from v4.0 onwards.If the companies that create OEM versions have various version of their API as well, it is likely that they will run into compatibility issues. Also this varies per OEM versions. Some will work and some don't.
Best practice would be to recommend to Dahua or any other OEM manufacturer that they should use only 1 API, this would make life also much easier for themselves.
-
Paul, thanks for the clarification.
Norman, I hear what you're saying, but it's my understanding the firmware/API are functionally identical. I'm guessing the issue is the way in which NX Witness detects or attempts to detect the analytics.
Example, when I go to the following URL, I can see my CrossLineDetection IVS rule. Are you guys using something other than the Dahua HTTP API?
http://<camera_ip>/cgi-bin/configManager.cgi?action=getConfig&name=VideoAnalyseRule -
@Paul,
Based on the information I have today, I expect that 4.0 will be released in the 2nd half of September.
@Ryan,
We use the API of Dahua that was offered to us by Dahua, specifically v2.7120 of 2019-06-03. The syntax you mentioned is one of the many syntaxes that is used for the analytics. I do not know, what the differences are between the Dahua versions and the OEM versions, I think Dahua is the one who could answer that.
-
@Norman
The only differences between the Generic firmware and the Dahua firmware is the branding. So if I use the camera API to poll the Vendor, Model, and Name, they come back as generic values. The API for the cameras still reports all analytics the same as the Dahua branded firmware.
Additionally, if I flash the Dahua firmware, integrate it into NX, it'll detect the analytics, and allow me to utilize them. If I then flash the generic firmware, NX continues to utilize the analytics and everything still functions as expected. So, I found the documentation for the NX api and did some digging.
I *think*, you guys are identifying analytics not based on what the camera API returns for analytics, but instead just based on the Vendor name. I can somewhat understand why you do this, it's a simple way to narrow down what analytics are supported for a specific camera; however, the API will actually tell you what analytics it supports too. I could see that as a future enhancement if you guys want to have wider adoption of analytics in the future.
For the time being, the id, parentId, physicalId, and typeId are all identical between the Generic and Dahua firmwares when I add the camera on a fresh NX install. I found the api/manualCamera/add option, to manually define a camera, however, it doesn't let me over-ride the vendor. Is there a way to do this? I think if I could over-ride the vendor, all the analytics on my camera would function as expected. Thanks again!
-
Okay, Ryan Flagler and Paul Kealley
My apologies for the delay, but in the meantime, we created a workaround.
When the OEM camera (any we natively integrated; Hikvision, Dahua, etc.) has the same firmware and the only difference is the OEM Vendor and Model name, we could provide a *.JSON file which you can add to your system with the instructions we provide with it after t is added and the server application is restarted the analytics should be available.
The only limitation is that the model name and vendor name can't be too generic like IP Camera, General, etc. otherwise it might conflict with other cameras.
-
Hi Norman,
I currently have this exact issue with a Hikvision OEM LPR camera.
I have two of them, one is Hikvision Branded and the other is Hikvision OEM.
The Branded version has analytics working and the OEM version does not. You mentioned in the previous comment above that you can provide a JSON and instructions. I'm wondering if you could do that for me?
The Vendor is listed as ONVIF
The Model Number is listed as NC512-VBA12-LPR
Thank you for any help you could provide!
-
Hi Tuli Dem,
Please follow the steps as described below:
1 - Remove the device from the system
2 - Stop the mediaserver application and paste the resource_data.json file in the LINK at the following location:For Windows: C:\Program Files\Network Optix\Nx Witness\MediaServer
For Linux: /opt/networkoptix/mediaserver/bin/3 - Now start the mediaserver application again
4 - Add the device againTo stop and start the media server, please do it as follows:
For Windows:
1 - Open the task manager
2 - Select tab ‘Services’
3 - Find the mediaserver application, right-click and select; Stop or StartFor Linux:
1 - Open the terminal (Ctrl+Alt+T)
2 - Enter the following command;sudo systemctl restart networkoptix-mediaserver.service
After this, the request should be fulfilled.
Please confirm, and we will add it to a future patch.With kind regards.
-
Thanks for adding this for me Norman. I followed your instructions and did not see any change. The system is still not recognizing the camera as an analytics capable camera.
The server is a DW Spectrum branded version. I'm not sure if this makes any difference as I did not see anything in the JSON file referring to NX or DW, and the top of the json lists is as compatible with all versions. I did drop the file in the corresponding folder for DW
Please advise on what I can try or what I might be doing wrong.
Thank you.
-
Hi Tuli Dem,
You're right, the branding of the software is irrelevant
Can you share a screenshot of the Camera Settings menu, tab General that shows the Vendor, Model and Firmware?
-
Hi Tuli Dem,
Would it be possible to get remote access to the device via port forwarding or to the server and client through TeamViewer?
Post is closed for comments.
Comments
20 comments