Hikvision NVR DS-7716NI-SP issue with generic cameras

Bearlord

n3wb
Feb 1, 2017
7
0
Hello. I am a new poster to these forums, but I have used it plenty of times to troubleshoot my Hikvision NVR DS-7716NI-SP. This time however, I can't seem to find the problem.
Where I live it is hard to find ip cameras and related technology, so usually I am stuck with whatever brand of cameras a semi-local distributor is working with at the moment. I have ordered some cameras online but its also a nightmare to get them here (remote location). Due to this issue, I have 3 different brand of cameras connected to my NVR. One of those brands is Hikvision, so there were no issues at all with those cameras. Then I got some Dahua cameras, and after some tweaking I got them to work with my NVR. The problem comes with my last 2 cameras. They are from a brand named AVTECH, model AVM511.
I have tried a lot of tricks that I learned from these forums to get them to work. I have installed the Onvif Device Manager. So far, I have tried these methods to add them:
- I tried adding them the easiest way first. Plug and Play. It didn't work.
- I tried adding them with manual settings, using onvif protocol (used Onvif Device Manager to get the right port). Didn't work well. The camera shows on the camera management in the NVR but the livestream is black. It doesn't show any errors.
yJHOD4ROzL8us30uxd2EAWX10-CrJizMubHq18HF69l6CgfqMgET4lW6kCTSTEieBbe77VioGIhz_h8U8qy2ufNxDkQvpWAn1r7iSCE5gY7seLE0RU28VlXg0OsWHXK2lmsNrfF1lefV3MFEahU59ymeMOfYYtF_ILcjUXwONHXQ02H6f9CsBpAGOmczQFYYgyjU2IqPPrH8AgK0tWLsNik1bTuM_-SIy7xLxWPOdz-iks-MnOQXivue2FYSEG3_TqHbaC1pVpUPuPNeIdScSKpDGJBTN50r7g3-uXU_Y-kg6-KWzi82NCMQdK_AZamL_2ePAcFdhEg1wbdHknRqivylzM94CFp9ZrBaanCkUdUcNkqq2vnEtl2FlXo7SZ03ctx4ru3zLWWJpVCRhhZTPPokWbhBAvCQmTYBVSAvTOziJqOEFzqlsvwtZDCttCLUcjqFwtuLVAFdlc2waqVwnTIvQ_1gNcFGu0C3UHhSUc0_O_Fe9fTasmhNVaDxwru8ECHz9PGA5KWqM3fnIB-2zj2OYulYCfxLB4_-FmC9a-6eTLd-MbiudvJMi-5FpFfhV20Yr9zCU5jgmVTKQFUZaGB1m0D76I28Guy73r30wPEWXNkhCA=w1152-h648-no


vKumbtjcTnTzJ4LXTsRs0TY6mgYwh1ytqUKrs5lHJXQIjjqyntNoBJMd2-4pxXoMjDKbwjAp8BcKU8CWFP063mauwME8a1crbOuyAVWiUhFD2emz1FokyRS0hT2bxjhD9vo6mWFejLA-N1BMCh_Xtrxhw_9pB9MkKp1JChnA9vO_zXwB-iKraOlwY_3M-phddat8dqnWCeQ7KUqF9gXJs-Q9lWc8-BW9m4nE0WmUMNo_Dn2EGa-Ez9NnCiL0gVFZwxRZoisSPuyZpSBOlywBhO7J4wqCe4JzJRqYP-TBi-fW5c_Ac4QT6PEbZfOdCAEnpAHdtqIufb49gI4qGAzrlybs659RQMLLxpAsuGMD5Idd5Pc2qW_JKoOiStsRYGg3aIQlWK7R_yLykBRa68kom4MKjstJ5-HKIh3fTOfXAxexgG_ZindrlZpYdqtYag3tGKo3kC3t9PUdHp5uiUuAfptwL0xRiLopl8MNvGH0QALi4-nk-hxZUKh42SvKWD6nhk-ldMnYUHrr5_3liUMtoJrIaNVonKg9IOW30a_-JF80WDioxuRW7hvZ69pHSCrFY-O9cmBrHLbNM_i8oAQihS4AJo8c1_mBPsqTB8gxJ7EoUTVPMw=w1152-h648-no


Sp_IDjCK9QPqsoRy5uRi4uTa0ZDUKlBxJ4BFvLWySHO5g5HIpzFo10pq6h158lfS2hcb0UacEiNQ0kU119EFah9IVLLlMfwEiPQ_DSrOp6UiZJ7Dv812kxMcOq3V7TeyIgL7CH1lPukmN5WvPdCL5-fXiBANjDmcxo5nFmZyd7nfCzKgFBICaDhhAhjzy5Ad_AP_NWKn5D82TTIMkwWmpinHcJUbf-cuuM48Gxp7CcOtrSSmuLF7IOX3GSDEL_0PuoOq_jz7a9tcfwTkrjaYk_fGBogoRN7lZ78QRQnUmF7xxJgKdW3PT38Ma14Mas9gSxiFRG2fryulmxs7_dTw8H_4xqsBzhtqVJr3qCOgKAwcz1FlbyYQj2zfvz3-kQSbnNuprcnnJsjoWG4lTTqMmeyKmpcbvJIP-IIQDaY7rTzIy-mOQDvP0YPAbukP4yWpsi4UeH9PxvDwD5YwhRfOFrSGVA0BZfyz83mlCPNjUy73yD2ILqyPvnx_BPF4O3cU-J-Z0ML4O7sjfkYTMnJQxdgKr7dSy5lWvAiPpuOqVyvIM3LtzwkqZZq1Y7rG84YktLupQrt4v_W5SJ2hBSypdYsew05SMEcq09oZiL32JKPTTgOTGg=w1152-h648-no

- Adding them using custom RTSP custom protocol, using the path I got from the ODM didn't work either. It shows an error.
M-BKCF8XMF10Ejluha1etJ8XOjghEV988YgOUBhRf9tppAyqhp9nVhjEdnh9oTDA1-qo6rqfu4tCtqeS0C-3MiziJDtGhM3E64bm6Xqz0-vniIcPEBvrOgzWL20FNi7caYMtId8tRHVEwvvJRf5X3G5hc_1J9oHU6JRBPtmp4AKefHTXA68gNHeIWOI_t1qGtLH_8dts7lV4b6xqcs3EDFg5_ebsTtzIQhhJAmPdkD3FwyYQbey8-PHeeLwAFwu08nZEQ2KhqLOtqRRZ278F9GDv3TtbD_9dX2QIkckh7m_KA2pxyGYugTi52GiEXxpiQ9MkBV8_2c3bxE1urLOY9yOxNo1KOT4dvLbVzQDu0h1VZml9ub05P-9t3L9Va3tyvWltSHAwvsvuNEuzBWPKhlmagZPR1nYN4ZmzMjek20kM3HQa0uzR7B1v0VhYrz6qU5rzgWD3GFt9tZUk7qoSYsJWVNzNhmiqp4MUAbfNpAd8PKFz3f-dSqhityxJ0chPZ-NiqmKxWvSI184qPOTojc1nTJNq3RIG7HQPazDPWLAzAvmvVFYfUg50SU5dQ7rIORackF1Na4HfiL_Ut8uybiQVW_Fyr1aMaNqRwrGVTOL55XNMyQ=w1152-h648-no


Here is the info I got from the Onvif Device Manager:
upload_2017-2-2_10-58-15.png
upload_2017-2-2_10-58-31.png

Notes: The camera image does show up on the Onvif Device Manager. My laptop is connected to the NVR with the same ip segment as the cameras. The ip of the camera was changed to match the ip segment of the NVR's POE network via the web gui of the camera itself.

Thanks in advance for any help!
Sincerely,
Bear.
 
A common cause of ONVIF problems with unknown brand cameras is the ONVIF port being other than 80 - but I see that ODM has it as 80, as seen in the URI under Identification.
I'd have expected your ONVIF setup to work OK.
Does the camera GUI have an ability to change the ONVIF port away from 80?

Moving on - you are trying a Generic RTSP 'Custom' connection.
Unusually - ODM has the RTSP port as 80.
The usual default is 554.
Is this something you have modified in the camera GUI?
Can it be changed to the more usual 554?
In your Custom protocol, the Path should be:
/live/video/profile1
with port=80 as you already have it.
For continuous recording, I think that has a good chance to work.
And you can verify the RTSP URL with VLC Media Player, 'open network stream', with the full
rtsp://camera_IP_address:80/live/video/profile1
URL. I included the port above in case you are able to change it to the more standard 554.

And lastly - does the camera generate any motion events in the 'Events' page of ODM?
And does it list any Analytics Rules?
 
  • Like
Reactions: Bearlord
Hello Alastair. Thanks a lot for your fast reply.

I did not modify the RTSP port on the camera. I will try to change it to 554 on the camera GUI. It does have motion event capabilities, however I do not need these to work. All I need is the continuous recording.

I tested the strem with VLC media player and it works, using the port 80.
upload_2017-2-2_12-6-26.png
 
I went into the camera web GUI. I couldn't find anything related to analytic rules.
This is all that comes under the Onvif category in the web GUI:
upload_2017-2-2_12-24-59.png

It looks like it only supports events but not analytic rules, or maybe I am missing something.

Thanks again!
 
It looks like it only supports events but not analytic rules, or maybe I am missing something.
The Analytics Rules I was wondering about would be in ONVIF Device Manager, if the camera supports them. But as you've said you do get events, there should be the underlying rules showing. Your screenshot above suggests they will be Motion and Alarm.
It's impressive that the camera web GUI has ONVIF event configuration.

In your Custom protocol, the Path should be:
/live/video/profile1
with port=80 as you already have it.
Did you try correcting the Path in your Custom Protocol definition?
It should not include the 'rtsp://camera_IP_address' section.
And you've validated the correct full RTSP URL in VLC, that's good.
 
Did you try correcting the Path in your Custom Protocol definition?
It should not include the 'rtsp://camera_IP_address' section.
And you've validated the correct full RTSP URL in VLC, that's good.

Yes, I tried correcting the path to only <</live/video/profile1>> but it didn't work either. It marks an error "IP CAMERA EXCEPTION".

upload_2017-2-2_14-27-32.png

The Analytics Rules I was wondering about would be in ONVIF Device Manager, if the camera supports them. But as you've said you do get events, there should be the underlying rules showing. Your screenshot above suggests they will be Motion and Alarm.

Oh, I thought you meant Onvif events on the camera itself, not on the ODM. I do not see any events on the Onvif Device Manager, and it doesn't show any analytic rules.



I also wasn't able to find a setting to change the RTSP port. However, I tried to connect through the full url via VLC using port 554 instead of 80 and it worked! So I tried a new custom protocol on the NVR using 554 port, but same result. It gets detected but it marks an error.

upload_2017-2-2_14-32-3.png

I am really puzzled by this. I even tried upgrading the firmware on the cameras.

Thanks again and greetings!
 
Oh yeah, I had that option ticked on one of my tests. I tried with it ticked, unticked, with the full path, with the short path and with port 80 and port 554 and all the possible combinations of said settings. Still nothing. Same error "IP CAMERA EXCEPTION". The only way it works without showing an error is with Onvif protocol, port 80, no substream. But the live view is a black screen. I wonder if it has something to do with the video profiles instead, where I can change resolution and other values. I haven't changed any of those yet.
 
Well, that exhausts my standard suggestions.
What's the resolution of the camera main profile set to, and what does your NVR allow? Looks like a 2MP max camera.
What about the NVR web GUI Live View, does that behave in the same way? And when you select the substream in Live Vew?
 
It is a 2MP camera. I started playing with the profile 1 stream to see if it has something to do with that. I changed the 1920*1080 resolution it had for 1280 x 720 since that is what the cameras that are working on the Onvif protocol have. Still getting black screen. There's a setting I am not sure if I should play with. It says h264 and it lets me change it to JPEG. I don't want to be doing that. I am also out of ideas of what I can do. The cameras took long enough to get here and I really don't want to send them back and wait for new ones.

I really appreciate your help and the time you have taken to answer my questions alastairstevenson :)
 
Apologies if you've already covered this - how does the Live View via the NVR web GUI and the Live View via the NVR VGA/HDMI interface compare in terms of the problem?
Does the Live View in the web GUI show an image if substream is selected for the camera channel (on the Live View screen)?
 
I have issues with the live stream on the web gui, i don't use it because i can't. When i login it prompts me to download and install a plugin, I do, but it won't work. I've tried different browsers and still the same issue. I figured I didn't need it, since I just used the ivms 4200 to view the cameras and the direct hdmi. It doesn't show in the ivms4200 either.