Hanwha Wisenet X Analytics and VMD Test

By Rob Kilpatrick, Published May 24, 2018, 10:53am EDT

Continuing our updated testing of camera analytics, we tested Hanwha's Wisenet X analytics for over two weeks in multiple scenes, indoors and out, day and night. To see how these analytics perform in real world scenes, we used three cameras:

Checking performance in indoor and outdoor scenes, including:

  • Intrusion vs. Loitering analytics
  • Configuration recommendations
  • False alert performance
  • Detection range
  • Analytics compared to camera VMD
  • P/Q series differences
  • Hanwha VMS/CMS integration
  • Third party VMD integration
  • Tech support recommendations

Readers should also see our recent series of camera analytic tests, including Axis VMD4, Hikvision Intrusion Analytics, and Dahua Intrusion Analytics.

Summary: ********* ****/********* *****

***** ******'* ********* ********* and *** ****** ******, with ******** ***** ***** issues **** **** ****** sources, ********* ** ********* with * ***** *-* second ***** ****** **** well ** * ********** / ***********, *********** **** of ***** ***** ******.

***** ********* **** ********* settings (* ****** *****, ~70 ***********), ****** *** outdoor ******* **** ** small *******, *******, *******, and ***** ******* **** effectively **********.

*******, *** ****** ****** regular ***** ******, **** using ********* **** ********* settings:

  • ***** ****:******** ** *** ******'* lens/dome ****** ******** ****** during ***** ****, ** they ***** ****** ****** to ** ********** *** trigger *** ****.
  • ***********:*********** ** ********/******* *** other ******** ******** ****** alerts ** ****** ****** (though **** *** ******** these ***** ****** ** some ************). 

*** ******* ****** ******** detected ******** ** ** average ** ~** ***, with **** ********* ********** across ********* *********** *** fields ** ****.

Solid *** ***********

******'* * ****** ******** events ********** **** ******* Wave/NxWitness, ******* ******** ******, and ********* ********, **** bounding ***** *** ****** paths ********** ** *******, as ****, *** ****** in ********* ** **** tested. 

************

****** *********** ***** ********* (IVA) *** ** *** * ****** cameras, ***** ***** *** ********* settings and **** ********* ********* settings ***** *** ******* area ***, ***** *****.

Recommendation: *** ********* ******* ** *********

******'* * ****** ********* analytics ** *** ******* a **** ***** ****** on ***** ****** ********* such ****** ***************. ******* ** ****, sources **** ** *******, light *******, *******, ***., triggered ****** *********** **** entering *** ***** ** view, **** ** **** are ******* *** * fraction ** * ******.

*******, *** ********* **** operates ************ *********** ** Intrusion **** * ************ time *****, ***** ****** eliminated ***** ******* ** false ****** ******* ********* detection ***********. ******* ** this, ** ********* ***** Loitering ******* ** *********. We ****** *** *********** of **** *****.

** ****** ***** ************* options ** **** *****:

Loitering ******* ***********

****** ******* ** *** outdoor *****, ***** ********* almost ********** ********** ***** alarms **** ******* ***** and *******, * ****** trigger ** ****** ***** only *********. **** *** course ** * **** of *******, ********* ******* on ***** ***** **** than **** *** ***.

******* ** *******, ********* nearly ********** ****** ****** by ***** ******* ** the *****, ***** ****** near ******** ****** ** both ********* ********* *** VMD.

*** ***** ****** ** outdoor ***** ****** **** using ********* ********* *** heavy ****, **** ******** on *** ****'* ******* frequently ********, **** *** and *****.

Loitering ****** ***********

******, ********* *** *** affected ** *** **** triggers ** ********* **** as ******* ***** *******.

********* *** ***** ** longer ******* ***** *******, however, **** ** *** closet ***** ***** ****** on *****.

Intrusion ***********

**** **** *********, ***** alerts **** * *********** problem **** ***** *********, ********** alerting ** ****** ******* on/off ** *** **** and ******** *****.

********, ******** **** ** blowing ***** *** ***** animals ****** ******** ******. Increasing ******* **** ****** to ****** ****** **** small *******, *** ******* detection ******** ** ******** in *** ********** **** filtered ***.

*******, ** **** *********, rain ******** **** *** dome ****** ***** **** was ** ****** ******** cause ** ********* ******.

Vs. ****** ***

* ****** ****** ** our ****** ***** ** camera *********, ******'* ********* and ********* **** ********* much ****** **** ***** standard ****** ***.

*** ********* **** ********** than ********* ** ******* *******, such ** *** ***** change *****, *** **** shadows, *******, *** ***** animals.

****** *** ** ******** to ***** ***** ********, but ** *** *****, this *********** ****** ** avoid ***** ******** ******* in ****** **********, ***** below.

Wisenet */* ***********

******'* ******* * ****** also ******** **** *********, but **** *** ******* the ****** ********* ** loitering ******* ***** ** the * ******. *******, object *******/****** *** ********/*********** are ********, ****** ***** rules ******* *********** ********* as ********* ** *** configuration ***** *****. 

*** ******* * ****** includes **** ****** *********, not *********. 

Detection ******

*** ****** ******* ****** ******** detected ** ~**-** ***. This ******** ** *** following ******* ******/*** ****** in ******* ******:

  • ***-**** (*** *:*): ~***' HFOV/~90' ********
  • ***-**** (*****): ~***' ****/~**' Distance
  • ***-***** (*****): ~***' ****/~**' Distance 

Hanwha ****/******* ***** ***********

******'* ********* ********* **** their **** *** *** Network *****, ********* ** event ****** ******* ** the "****** *****" ******. ********* are ************ **********, ** users *** ******* ******** events ** *********, *********, appear/disappear, ***** *********, ***. 

*****, * **** ******** is **** ** ******* an ***** ************ ** Wave:

******* ***********

******* ********** ******'* ********* as ****, **** ****** displayed **** ******* *****. Note **** ***** ***** do *** ******** ***, however, ** ********* ** displayed ** *** **** generic "****** ******* *****" in *******.

** ******** ** ********* events, ******* ******** ******** boxes ****** *******, ** well ** ****** **** from * ****** *********, shown ****:

Milestone ***********

******'* ******** ****** ********* with ********* ******** *** of *** ***. *** example ***** ***** ********* used ** ******* ****** in *** ***** ******.

Avigilon/Exacq ***********

******** *** ***** ** not ***** *********** ** Hanwha's *********, **** ****** side ***. 

Hanwha ***** ****** ***********

******'* ********* ********* ********* with ***** *** ***** ****** software, **** ******** ***** displayed *** ****** ************* displayed ** ** ***** list. ****** *** ** played **** **** ** cards ** ****** ****.

Tech ******* ********

****** ******* **** ******* was ****** *** ***** for *************** ** ********** Intrusion ******** ***********. ***** recommended *** *********:

  • **** *** *********** ** default, *** ****** ** will ***** ** ***** rain/snow (** ******* ** lower)
  • **** *** ********* ******* to * ******* ** ten *******.
  • **** *** ***/*** **** to *******
  • ** *** *** *** ******/********* setting

***** *********** ******** ****** not ** ** ******* during ******* *** *** following *******:

  • *** ******/********* ******* *** no ****** ** *********, it ** * ******** alert *** ***** ****** on ** *** *** no ******. **** **** in ****, ***** *** default ******** ***** ***** misses ** *** ****** and ******* ***** *** the **** ****** ***** triggered ****** ** ** reduced.
  • ********* *** ** * default ** *** ******* would ***** *** ********* alert ** **** * person **** ***** ******* in *** *** ** the *****, **** **** the ********* ******* ** a ******** ***** *** does *** ******** **** the ********* ******** ** loitering ***** ***** ***** in **** ****. *** ********* setting **** *** ** impact ** ************ ** the ********* *******. 
  • ******* *** ***/*** ******** to ******* ****** **** in ****** ******, *** users ****** ** ***** of *** ***** *** between **** ***** ********* and ***** ****** ** smaller ******* ***** ********** the ******* ***** ******** for ** ******* *****.
  • ***** ******* *********** ** default ****** * *** of ****** **** ***** alerts ** ****** **** as ****** *******, ***** animals ** *** ********** and **** ** *** outdoor *****. ** *** indoor ***** ** ****** consistent ****** ** ****** like ***** ******* *** reflections.

Versions ****

*** ********* ******** **** **** in **** ****:

  • ****** ***-*****: *.*********
  • ****** ***-*****: *.*********
  • ****** ***-*****: 
  • ****** ***-*****: 

Comments (27)

Great test and as a result I'm turning off the intrusion setting and testing the loitering at 1 second setting instead.

I'll be interested to hear how it goes for you!

When is Hanwha going to fix this? Using loitering for intrusion detection is a hack, no?

Ethan, I'm not going to have much feedback on the Intrusion to Loitering switch as it was only yesterday that I switched our X-series cams from VMD to Intrusion so I don't have a good baseline.

IPVM Team - In my world I would never use Video Analytics for a 45-90ft scene.  I could just use a cheap PIR or Microwave for that.  I use Video Analytics for long range applications where traditional IDS infrastructure would be too costly to install, i.e. 1,000 - 1,400ft distances.  Because of this I find these tests of minimal value.

Nathan, thanks for your first comment! We have to do these tests (all of them, Axis, Dahua, Hikvision, Hanwha, etc.) to establish a baseline. We can't simply say 'trust us these suck', (1) because we need to have actual measured results, (2) how bad they are differs and (3) because lots of people do use, or at least consider, using these analytics / VMD.

I also don't disagree with your approach but many integrators will not want to take the time and money to add in an external detector, so it's important for them.

If there are other things you want us to test, feel free to share.

 

It’s so easy and not expensive to add an external detector and solve the intrusion issue: We make an inexpensive hardwired LX series of product that can be powered directly from some cameras and communicate the event directly to (through) the camera as well. (And a variety of other options.)  You can even create “double knock” events if you have good lighting.  I can’t begin to tell you how many intrusion analytics jobs we come in behind due to rain drops, spider webs, birds nests, etc  with a very annoyed end user- With correct but simple planning, it’s so much more cost effective, you will have happier customers, and you provide accurate detection that can be verified through video to do it with sensors upfront instead of chasing man hours and service calls after the fact (imho).

inexpensive hardwired LX series of product

What is the price? As a general rule, it's better to cite the specific price than to use a subjective term like 'inexpensive' since people's opinion on what is 'inexpensive' varies.

Makes me wonder why camera manufactures don't build in a PIR detector with or without microwave.     

There are a handful of cameras with PIR detectors built-in typically more residential focus. For example, I recall seeing a Costco kit offering it, like this:

Why is it not more common? I assume cost but if a Costco kit can do it, it can't be that expensive. The other issue is likely how often they would be used in professional deployments, which may be lower if the PIR range is short. Just guessing. Good question.

Yes, PIR's are/were usually on the cheaper cameras, but why not a PIR in enterprise level cameras? Would this not be more reliable than most analytics and certainly more reliable than video motion detection? 

I liked the old Axis M10 series cameras that had a PIR and LED light onboard. Maximum PIR range was 20 feet, but great for dim interior coverage.  

Good Point- That Lexus is so cheap! :)  The 40X50' range (LX402) is around $65US and the 80X7' (LX802) is around $90US. 

Nathan, In our campus environment we mostly record only on motion. Camera Video Analytics usually false less than camera Motion Detection. So for us and many others it's about only recording events, it's not usually used as a substitute for an outdoor intrusion detection system.

I appreciate these tests because they give a performance baseline from various manufactures and ultimately save me hard drive space. 

Nathan, my experience in working with outdoor perimeter is that video analytics allow a much better stability then PIR or Microwave in terms of false alarms. The PIR/Microwave often need adjustments/service calls because of vegetation, a plastic stuck somewhere, signs moving, car lighting close-by or something else but that you can't see. With the video analytics you can actually see what is causing the false alarm and can simply mask the moving area and you're done. Analytics like Avigilon learn to eliminate many of these false alarms over time. If I look at the thousands of triggers (analytics, PIR, Microwave, radar, etc.) for a video alarm at our central, I can say that PIR/Microwave are 1st on top for the volume of false alarms. Securing a smaller perimeter (45-90ft) with PIR is indeed a much cheaper solution compared to analytics but at the end you get what you pay for :) At the end my opinion is solely applicable if the site requires remote monitoring otherwise false alarms don't really matter!

Any plans to test the audio analytics that are built in?

 

That would be great, thanks indeed.

 

I love how bad those outdoor analytics are, i wish i could share it with more of my customers where people keep argue with analytics vs fence intrusion detection system.

Thank you for another great testing! 

Hanwha analytics are integrated in Exacq.
Setup analytics camera by browser, than configure Exacq in Association button.

Can anyone point me to info on forcing Milestone to use the Hanwha driver? 

Can you expand on this question?  Mainly, what camera(s) are you using?  I know that some of the X series cameras are still using the ONVIF driver but most have been changed to use the Hanwha driver.  I don't know if that is what you are referring to or something else.  If you have the specific camera model(s), I can look into it a little more.

XNV-8080R will temporarily work, but quits recording everytime I go back to check it for something. 

Make sure you are using the latest device pack which brings in the camera analytics on the Hanwha cameras.

Thank you for the great review.

I wanted to test the ablities of this myself but you saved me the effort.

It feels like an unfinished solution. Not ready for mass market but rather to get beyond regular VMD.

Some P-series Hanwha cameras also offer Intrusion and Loitering detection, for sure the multi-imager PNM-9080VQ does.

Correct. The P-series cameras which like the multi-directional PNM-9080VQPNM-9081VQ as well as the new PNM-7000VD have the loitering/intrusion analytics on board.

 Will you guys also be testing the new Axis Guard Suite?

Yes, it is on the list for later in the year.

Read this IPVM report for free.

This article is part of IPVM's 6,810 reports, 914 tests and is only available to members. To get a one-time preview of our work, enter your work email to access the full article.

Already a member? Login here | Join now
Loading Related Reports