Camera Analytics for HIKVision OEM

Answered

Comments

13 comments

  • Official comment
    Avatar
    Norman Graafsma

    Hikvision analytics are supported via the Hikvision API (ISAPI) so I assume that there is a difference between the firmware of the OEM vs. the original Hikvision camera. I think Hikvision should be able to pinpoint these differences. 

    Comment actions Permalink
  • Avatar
    Paul Kealley

    Hi Norman,  thanks for the quick response. T he camera uses the standard HIKVision firmware, not an OEM firmware, and the functionally is identical to the HIKvision branded camera. 

    0
    Comment actions Permalink
  • Avatar
    Paul Kealley

    Sorted this out, turns out Hikvision-CGI was disabled on the camera.  Enabled this and all good. 

    0
    Comment actions Permalink
  • Avatar
    Norman Graafsma

    Thank you for the feedback, Paul. Much appreciated. 

    0
    Comment actions Permalink
  • Avatar
    Ryan Flagler

    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!

    0
    Comment actions Permalink
  • Avatar
    Norman Graafsma

    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. 

    0
    Comment actions Permalink
  • Avatar
    Paul Kealley

    Hi Ryan, 

    Just to confirm the camera I was using was an OEM but the firmware was the genuine Hikvision firmware, therefore the API for the analytics was working OK once I enabled the correct settings on the camera.  

     

     

     

    0
    Comment actions Permalink
  • Avatar
    Paul Kealley

    Norman,  a little off topic but any word on the release date for version 4?

    0
    Comment actions Permalink
  • Avatar
    Ryan Flagler

    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

     

    0
    Comment actions Permalink
  • Avatar
    Norman Graafsma

    @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 that one that could answer that. 

    0
    Comment actions Permalink
  • Avatar
    Ryan Flagler

    Thanks Norman. I've got a question out to my vendor about the firmware differences. I appreciate your help!

    0
    Comment actions Permalink
  • Avatar
    Ryan Flagler

    @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!

    0
    Comment actions Permalink
  • Avatar
    Norman Graafsma

    @Ryan,

    I will get back at you asap. 

    0
    Comment actions Permalink

Please sign in to leave a comment.