Search results

Use it instead of the Hikvision tftp updater tool when the firmware file size is larger than 32MB.

Presumably using Chrome browser, or maybe Firefox? Blocked as an ERR_UNSAFE_PORT edit as per the screenshot on your first post. Allow per-site insecure content in Site Settings under Privacy & Security. Or click the settings button to the left of the URL when attempting access.

I don't know. Does it unpack ok?

Excellent! That's good to hear, thanks for the update.

Int It's a bit of a mystery why it's behaving differently as opposed to just doing a fairly quick restart as it did to begin with. Does the web GUI work and look normal? How close to actually working does it seem to be?

What does windows task manager show for the offending high CPU processes?

That is correct, the NVR has administrative control of the cameras via the Hikvision command&control protocol and the admin userID/password. When the camera is 'activated', such as when a new Inactive camera is first connected, the camera IP address is assigned by the NVR to match the IP address...

It is quite complicated as it involves disassembling the code of the control program, working out what it's doing (many thousands of lines of code) and finding the part that sets the way of working. Working up a patch to change that. But a hard part is being able to unpack and decrypt the...

Haha! Yes, I've done that, just for fun, on some of the value series cameras. It's the same firmware, that just behaves with different capabilities depending on the model data from the bootpara data that's written in to the camera at manufacture. Same hardware as the more expensive models...

It looks to me like these are 'dumbed down' cameras with no smart event capability. That significantly reduces the ability to fine tune the event generation to avoid getting those that you do not want. Motion detection is the most basic of event types and is quite limited.

Do you mean reading the flash gives consistently the same results? And this didn't fix it? Which is why I said 'not being written correctly' as opposed to faulty flash.

Example :

The newest (and last) firmware is V3.4.106 Build191009 here : https://www.hikvisioneurope.com/eu/portal/?dir=portal/Technical%20Materials/02%20%20NVR/00%20%20Product%20Firmware/07%20E-series/%5B7600NI-E1%28E2%29%207700NI-E4%5D That's the Linux default start date for when the system time has...

It looks like the flash memory is not being written correctly.

What wiring standard did you use when crimping the connectors on? (eg T568B) Do you mean that the link detect light on the switch is absent on the problem cameras? What is the result of pinging the assigned IP addresses of the cameras?

Maybe here : https://www.hikvisioneurope.com/eu/portal/?dir=portal/Technical%20Materials/13%20%20Z%20Phased%20out/01%20Back-ends/NVR/7600NI-SE%207600NI-V%28P%29

On the assumption that they are connected to the NVR using the ONVIF protocol, it depends on whether the cameras issue ONVIF motion event notifications. You can check if motion event notifications are issued using ONVIF Device Manager https://sourceforge.net/projects/onvifdm/ ODM will find...

No, the firmware you linked to is for the I-series NVRs. E-series firmware is here : https://www.hikvisioneurope.com/eu/portal/?dir=portal/Technical%20Materials/02%20%20NVR/00%20%20Product%20Firmware/07%20E-series/%5B7600NI-E1%28E2%29%207700NI-E4%5D

That's quite an old model NVR. What model and firmware version are the cameras you ended up buying? There may be some compatibility issues if there is a big gap in the device ages.

Check your Conversations ...

If the cameras are 'inactive' and the NVR PoE port is set to Plug&Play all that's needed is to connect the camera to the NVR PoE port. The NVR will activate the camera, set the password as configured in the NVR and set the camera IP address automatically.

What version of CN firmware did you apply?

You should be able to play back recordings right up to the minute - there is no 24 hour buffer.

Make / model of NVR and cameras? Do you get the same issue if you access playback via the VGA/HDMI interface?

That's a pity. A bit of a long shot - but there are quite a few newer versions of the NVR firmware here, mostly bugfixes / compatibility problems ...

Is h.265 enabled on the camera? The E-series NVRs don't support that codec.

Are you recording to a Hikvision NVR? In the web GUI, under System, tick the box 'Enable rules' and all triggered events will show on the video.

As it doesn't look like the firmware update has also cleared the configuration, it may be worth checking (this varies from model and manufacture date) is if there is a command still in the bootloader to erase the config. Sometimes something like erasecfg Interrrupt the bootloader, then use 'b'...

Yes, the same error triggering the reboot. My guess is it's a hardware fault, unfortunately.