Hikvision Dvr Restart Problem
Kenneth
Hi, i have bought a switch model GS752TPP to change my old ubiquiti switch 24p 500watt poe.
With ubiquiti i not have a problem with a ipcamera that is distance 70 meters with cable ethernet, from the switch poe. The date signal and the power of camera was ok. Now with the netgear, i can't see the video stream, the switch and other software can't detect the ipcamera but the switch can detect the the current draw.
I have put the full duplex negotiation but the problem remain.
How can i resolve this problem.
This switch i think is not more better than ubiquiti but i didn't found nothing better than netgear for 870 euros.
Thanks a lot for the help.
Hi, in the page of POE configuration i see on the left, what must i do for setting it ?
You speak of negotiation with ipcameera but is on other men, (see on the right) and i already setted on full for negotiation but the problem persist.
Thanks a lot for the help
I told that the ipcamera come detect for aborbing current from switch but i was wrong. The power work fine becouse the led IR of camera stayed power on.
I think to know what is the problem, the cable that is not copper pure, but with ubiquiti this problem not was there.
I don't understand they speak a standard of poe if they are not good standard.
Just in case Have restarted the switch after enabling the longer detection time on all ports? Double checked the config is in place, including the enabled longer config time on the PoE port settings? Can you please provide the screenshot of the PoE config again please?
The couples of cables are correct, if i use same cable for not much meters (2-3 meters) the camera came detect correct. I suppose that the problem is the cable becouse once time i changed with same lenght (70 meters) and was pure copper and with a different switch (tplink) i was have same problem. In this case i was changed only one cable and i bought other switch (ubiquiti) and the rest of camera that have this problem, with ubiquiti have worked whitout problem. Now the ubiquiti is dead (after 6-7 years).
I will check the couples of cables for secure, but i think the problem is material of cable.
Either way, as you own a factory new switch, you can always get in touch with the support via ... Your Registered Products -> (select your switch) -> Get Support (by phone, chat, email) ... and from there you go
In attached you can see that all ports are in full duplex mode, and you can see 100 only where there are ipcamera that work.
Tomorrow i try to contact the support.
I'm very very disappointed from netgear for this problem.
According to the Hikvision DS-2CD2032F-I information (including the datasheet) it's clear these discontinued value cameras have a 1 RJ-45 10 M/100 M Ethernet interface only. Difficult for the switch to negotiate a higher link rate.
Have challenged Hikvision about their camera model? According to the details you posted, the camera does negotiate and establish a Fast Ethernet link. Keep in mind, this series and specs were outdated for several generations since that product release.
I have been fighting this issue for a few days now with no avail. I have Hikvision DS-2CD4112FWD cameras that seem to drift in time over a period of a day. Once i connect the cameras in the exacq VMS and review the video they are perfectly sync'ed up, then after about 12 hours they are off by 2-5 seconds. I have configured the exacq vision to be the time server, i don't have an alternate NTP server configured, the camera shows the NVR as the time server. I have modified the NTP update field in the cameras to update every hour, and they are still off. i found a windows task to sync the time, and set that to hourly with out any success. cameras are on a flat network on my testing bench.
Does any one have any suggestions or had any advice on this one? I have never had issues with cameras drifting this much in the past. Cameras are on the latest firmware, exacq is on the latest release.
I haven't seen any issues with Hikvision cameras drifting during our testing, but we run a dedicated time server on all the Exacq machines. I've actually never tried syncing to an Exacq server without it, now that I think of it.
Did you check the internal time on the cameras? Mine are fine and in sync (so the time being held in the cameras are fine). Its the overlay exacq time that is off and when you review video the searches are way off. I have this issue on a small exacq server and Large site as well. I have been working with Exacq on this with no luck. If i restart the server everything is in sync for 2 days at least! I am beyond frustrated.
If you are referring to the camera OSD. I didn't leave it on. I turned it on... Its purpose is to help identify what the time is on the physical camera to see what portion of the system is loosing time.
that's awesome, as we have been sweeping this issue under the rug and silently working on it with our own system. if possible i would love to toss my name in the hat to have them test out some fixes with it.
Undisclosed #1... Let me know how you make out. I have already spent 6+ hours on this. 1 tech says something completely different than the other and I still have no fix. I have a support case with them already so I will continue with this one.
As far as your questions go, we have Axis cameras, and we have Hikvision cameras on the same system, the axis cameras are not missing a beat and are in sync with each other and the time server (which is local to the network, and we can communicate to it. The cameras are set to use the NVR, the firewalls are off (and have been for testing). The Hikvision cameras are off from eachother and the server by as much as 6 seconds, when you restart the exacq services and reconnect all cameras they are all synced up, but after a few days hikvision cameras are drifting. I have adjusted the time sync interval in the cameras to as low as 1 minute, and 90 minutes just to see if that would help (it didn't).
Thanks for the details. Our engineering team is investigating. I'll let you know when we have the answer. A couple of comments on your screen shots: I definitely see that Data Center and Main Entrance cameras are Hikvision and are off several seconds. On Tech Door, which is also Hikvision, the exacqVision time appears close to correct. If part of your concern is that the camera's timestamp is 4 hours off, that is by design. We always set the camera to UTC (EDT is UTC-4:00) and then use the server's timezone to compensate. Thus, that 4 hour offset is not indicative of an issue.
I responded that we set the hikvision time on the camera like #2 had done to prove the exacq time and camera time were different. And I also responded i knew about the 4 hour offset. Hopefully we will see what they come back with.
I am a liitle curious as to why the time server is set to 127.0.0.1. This should be set to an accurate server, such as time.nist.gov. Check your camera to make sure it shows the actual ip address of the exacq server. Do not change any ntp settings at the camera. It must use GMT. I have seen that if you do not use an external ntp which the server can reach, like the default ntp.pool that exacq had programmed, cameras will be out of sync. I have also seen issues in the past where exacq will push a loopback address, 127.0.0.1, to the camera. This is from the network interface settings in windows, probably. If this is the case, usr the override feature with exacqvision server address. You would not be able to use cameras on a secondary nic. Make sure your dns settings and gateway are correct and working on server or this will not work. Never tried to run a NTP service on a server, and not sure why you would do this, since time will not be accurate on the system (and will drift over time).
If you have modified ntp settings on the camera, reset to default and start over. Leave camera ntp settings untouched. Make sure the server time settings are correct in windows (correct time zone) server and client.
I should clarify, i did catch that 127.0.0.1 as a time server, which actually got pushed to the cameras, and when i saw that address in the camera, I corrected it. The camera can connect to a time server, whether its pool.ntp.gov or the exacq box without issues, the problem is the cameras drift. We have defaulted cameras, the issue is not with a single camera, its with multiple cameras at different customer sites.
if you change ntp settings on the cameras, the exacq connection will, on a regular basis, over write it if ntp is enabled. Of course I am assuming that the camera NTP feature is working from a firmware standpoint. If you say the camera has the correct dns/ip information, and ntp functions, which is drifting, the time of the camera or that of the server? (you would have to deselect the camera in exacq so it does not keep pushing itself as the ntp server, unlesd the override has an alternate fqdn or ip address of another ntp source).
As I stated before, if you manually corrected the ntp on the camera, exacq will reset it on regular intervals (back to 127.0.0.1, or to itself, which will not work to keep accurate time). If you change settings such as frame rate, codec, and quality on the camera (those that I have used), these settings will be pushed back to Exacq. Can not be certain this is the case versions 7.0-8.0.
If the camera is showing 127.0.0.1 as the ntp server, though, I assume this is the problem since Exacq is pushing this out to the camera, which is trying to reference itself for the right time. Try entering the actual ip addresd of the server in the override field in exacq, and enable. Go to the camera to see if this is now listed as the ntp server. If so, turn on the osd time on the camera, and compare to the exacq server time, lower right corner of the client.
So the reason that your time server is set to 127.0.0.1 is that you have anti-virus on the system. What happens is that the Exacq software asks the computer for what its IP address is so it can set the cameras NTP server to that value. The anti-virus software on the PC makes it so that instead of the real IP address it returns the loopback address. This is to prevent malicious viruses and malware from finding out what your IP address is and spreading. If you go to Configure System -> Date/Time there is a field ccalled Ip Camera Time Server: and an override checkbox. Click that box and then enter the NTP server, which I am assuming is your address.
4a15465005