Hikvision 7608 motion detection not working

[mfred68]

Hi Guys, I'm totally new at this ip stuff, I recently replaced my SDI cctv system (due to its unreliability) to an IP NVR system.
I opted for the Hikvision DS 7608 NVR, but due to budget i bought 5 IP cameras from ebay from China, these are branded as "Onsoo" but are Onvif branded too and include motion detection.
Owsoo 1080P 2MP IP Camera 24IR Network Onvif Security CCTV Dome Night View Y0M7 | eBay
After a lot of trial and error I managed to get all cameras showing on screen through the PoE ports of the NVR.
For the cheap price of the cameras, the picture clarity is superb.
Now my problem is that I can not get motion detection to work on the NVR.
I can select a camera and bring up the red grid, and eliminate any part of the grid, but I cannot get motion to be detected within the red grid, no matter how high or low i adjust the sensitivity.
I recently read that it's the cameras that detect motion, not the NVR, so in that case why does the NVR have the option of the red grid?
Now onto the cameras, I unplugged them from the PoE ports of the NVR and plugged them in turn into my network switch, I took note of their ip addresses which was seen on the NVR camera set up screen, but when typing in any of the 5 camera IP addresses, it just times out and does not find any camera at all. the IP addresses are 192.168.254.163 with the last number changing for each camera.
Are they not found, because their ip addresses are not correct for my LAN? is so, how do you go about changing their IP addresses?
I'm thinking/hoping that if I could get into the camera settings, that there is an option to activate motion detection for the NVR to respond to? or have I wasted my money in buying cheap cameras? Or should my Hikvision NVR detect motion by itself?
The Analog system was much more straight forward.

 

[alastairstevenson]

Now my problem is that I can not get motion detection to work on the NVR.

When connected as an ONVIF model type, the camera must be able to generate ONVIF event notifications to be able to trigger a motion recording event in the NVR.
An ONVIF motion event notification is not the same as the more common motion detection that cameras can do.
It's often the case that cameras do not generate ONVIF event notifications even if they support motion detection.
You can find out if the cameras generate ONVIF event notifications by querying them with ONVIF Device Manager from sourceforge.net
Onvif Device Manager v2.2.250
Any events will show on the 'Events' page.

I recently read that it's the cameras that detect motion, not the NVR, so in that case why does the NVR have the option of the red grid?

That is correct.
But the ONVIF specification does support motion events and the ability to configure it, and the NVR supports the ONVIF specification.
But it sounds like the cameras don't support ONVIF motion event notifications.

To get ONVIF Device Manager to 'see' the cameras on their 192.168.254.x addresses, you will need to set the PC IP address to something in that range (such as 192.168.254.200) and connect the PC to an unused NVR PoE port.
All the cameras on the NVR PoE ports should be automatically found by ONVIF Device Manager, after you supply it with the camera logon details at the top left of the window.
Then you can easily check if they generate ONVIF events when they sense motion.


*edit*

I can select a camera and bring up the red grid, and eliminate any part of the grid, but I cannot get motion to be detected within the red grid, no matter how high or low i adjust the sensitivity.

OK - but after configuring motion detection, did you then configure the recording schedule and the type of recording (ie motion) that you wanted, in the NVR Storage menu?

 

[mfred68]

So would it not have been less troublesum and less head scratching if the designers of the nvr had supported onboard motion detection as they did with the SDI system?
This would have allowed all brands of ip cameras to be simply used as a camera apposed to a smart camera. Why couldn't the nvr be a smart box instead? After all it cost more than a "smart" sdi dvr

 

[alastairstevenson]

So would it not have been less troublesum and less head scratching if the designers of the nvr had supported onboard motion detection as they did with the SDI system?

It takes a lot of processing to do video analytics, this would bump up the cost and complexity of an NVR.
The cameras have an SoC (System on a Chip) that combines a 32-bit CPU that handles the environment and control with a specialised DSP (Digital Signal Processor) doing the complex video processing. So the load is spread round quite effectively.

 

[alastairstevenson]

How did you get on with progressing this problem?
Did you conclude it?

 

[mfred68]

I forked out for a Hikvision branded camera, to see if that works with motion detection. It arrived today, but i'm having a hell of a time trying to get the NVR to detect it, it just wont work even though its supposed to be plug and play.
I started another thread about that.

 

[mfred68]

Hi again, sorry to be a pain, but i'm still hoping you can help with a problem of accessing my cameras inorder to access camera settings within the cameras.
I can view the cameras perfectly on the PoE ports as explained. I have done what @alasterstevenson instructed me to do by detecting the cameras usin onvif manager via a laptop on a spare PoE port.
Onvif manager detects the cameras now, but a browser won't (google chrome in my case) but when i click on a detected camera in the onvif manager i get a message which reads:
There was no end point listening at Http://192.168.254.150/Onvif/Device_Service that could accept the message. This is often caused by an incorrect address or SOAP action, see inner exception if present for more details.

Does anyone know what this means, and how to get round this?

 

[alastairstevenson]

(google chrome in my case)

Unless it's an older version of Chrome, you won't be able to see Live video or make many configuration changes as Chrome hasn't supported NPAPI plugins for quite a while.
IE11 will still run the Hikvision webcomponents plugin OK.

There was no end point listening at Http://192.168.254.150/Onvif/Device_Service that could accept the message.

A likely cause of this is incorrect or missing logon credential given to ODM.
Top left of the window.

Your Hikvision camera at least, should be accessible via 'Virtual Host' under the NVR web GUI 'Camera Management' page.

 

[mfred68]

What are the logon credentials?
is it the same as the camera in question, which is default as admin and password left blank?
its not for my Hikvision camera, but i need to configure my cheap ebay Onvif cameras which have the aforementioned logon credentials.

 

[mfred68]

because i plugged the cheap ebay cameras directly into the PoE ports straight away, without first plugging them into my network, could it have been the NVR that changed their IP address to 192.168.254.2** ? because I read that the cameras come from the factory with a preset IP of 192.168.1.100
At no time did i change the third part to 254 myself, and now theres no way of accessing the camera via my network to configure it, i've exhausted just about every route as i just can't find a way of changing the ip address back to shipping condition.
The instruction page that came with the cameras tell me to download a CMS program from drvipcam.com which i did, and it does detect the cameras ip address of 192.168.254.2** but theres no way i can see to alter it.
Is anyone familier with the CMS program from the mentioned website?

 

[alastairstevenson]

What are the logon credentials?

The userID (often admin) and associated password that you need to provide ONVIF Device Manager with (top left of the window) in order for it to be allowed to access the camera.

could it have been the NVR that changed their IP address to 192.168.254.2** ?

Yes, that's how Plug&Play works with Hikvision cameras connected to NVR PoE ports, and it seems it has also worked that way for your ONVIF cameras.

and now theres no way of accessing the camera via my network to configure it, i've exhausted just about every route as i just can't find a way of changing the ip address back to shipping condition.

That doesn't seem likely, to me.
ODM can find the cameras with no problem, when you have connected the PC to an NVR PoE port and given the PC an IP address in the 192.168.254.x range.
You may be able to change the IP addresses using ODM, if it has admin access.
But the browser (you'll need to use IE11, these cameras will be using an ActiveX control) will also be able to access the cameras and change settings.

Suggestion to try:
With the PC connected to the NVR PoE port, and ODM active and seeing the cameras -
For each camera in the list, in ODM check the 'Network' page for each camera, note down the IP address and the HTTP port if it is different from 80.
In the IE11 address bar, use the IP address, and if the HTTP port was not 80, append a ':' followed by the port number and press Return.
You should get the camera login page, where you should be able to log in and adjust as required.