vimes

I have the 2.3.9 USA firmware I got from their FTP site a week or two ago and works well on a 7608 I put it in for a neighbor. PM me for the link if you want it.

You do know that it is still available on their FTP site...?

DS-76xxNI-SE(P) USA Firmware_v2.3.9_140820.zip

mmm that doesn't sound too good..!

I can understand the 5.1.6 camera firmware going AWOL as it seemed to introduce several broken features. Maybe the 3.0.8 NVR firmware went for similar reasons.

I would not have liked to have tried to force the update with the TFTP tool, as that would have been the last resort. Instead I'll just keep to the US 2.3.9 version.

Are there any functional differences with version 2.3.9?

From what I've seen I think that they have removed this firmware from their site..?

When I tried to flash it it failed each time through the browser and when trying directly from the NVR I got "not enough flash memory".

Basicly CBR (Constant Bitrate) will guarantee you better quality at all times, but at a higher bandwidth cost. All the systems we install, we install with CBR.

 

Example to explain it:

You have a camera watching a door. Someone enters and rushes thru the door quickly, you would like to see who it was and get a detailed image of his/her face.

 

Case VBR (Variable bitrate): While there is no motion, bitrate is very low, and when someone enters thru door, camera raises the bitrate to handle all motion. This might cause blurriness/pixelation in the beginning of the motion, if the motion is short enough (rushing thru door, enters and leaves camera view within second for example) image might be very blurry/pixelated and person not recognizable.

 

Case CBR: Even when there is no motion, bitrate stays the same, when someone enters thru door, bitrate is enough to handle the motion and even if the person is visible only for a second, image is as clear as it is without motion.

 

So if you have a very limited bandwidth, you can try to go with VBR, but there is always a chance its wont capture everything as sharp as CBR would.

 

On my ACTi 3MP domes I set:

 

Encoder Type: H.264

H.264 Profile: High Profile

Resolution: N2048X1536

Frame Rate: 15

Video Bit Rate Mode: Constant Bit Rate

Video Max Bit Rate: Unlimited

Video Bit Rate: 6M

 

Question: Is the video bit rate setting @ 6M overkill in your opinion? Should I lower it to 4M?

Two of my six cameras have the same resolution as you and frame rate, I use 4M for their CBR.

I use the above resolution as the aspect ratio suits the intended area of coverage better than 1080p. Also the covered area is fairly constant in what it records, except if there were intruders or family members etc present. Thus a high bit rate, to capture lots of scene changes, is not necessary.

My other four cameras are set to 1080p and use CBR of 4M with the same frame rate. The reduced resolution has the same bit rate due to more movement and traffic etc being recorded.

I have the Hikvision tools noted and both run fine under Windows 8.1. Nothing special was installed prior or since.

It seems that this bit is new....

Added Smart Search in playback full screen. Also Support remote client software

iVMS-4200 smart search.

and

In NVR “File Management” local menu, optimized “Quick Export” function to be able to

export video by specific time section.

As I needed six cameras I knew that the NVR I chose only had four POE connections at the back but allowed a total of eight cameras to be connected. I did not wish to spend the money on the 16 channel Hikvision NVR as it was too costly, even though the increased bandwidth and four extra POE ports might have been useful. Also I wasn't sure how "good" the POE aspect of the NVR was at delivering power and how it could be "managed" compared to the features on my managed 8 port switch. I had read a thread expressing some concerns over the POE module used in the Hikvision NVR's, not sure how valid that was though.

Only once one of my cameras became not accessible with an abnormal network error. Rather than go into the loft etc or outside and up a ladder I just used the web interface for the POE Switch and turned off its power to that cam and thus invoked a reboot, this, thankfully, brought it back to life. Little things like that warm me to the switch.

I could have injected the power to each camera differently to POE but to be frank my analogue system was a mess of wiring and many PSU's etc and one important factor for me was to simplify and tidy it all up.

I bought the managed Netgear 8 port POE switch so that it will supply power to all of my cams (six) and then the last two ports being used for the NVR directly (LAN port) and the final port for my internal network, connected to a different Switch. They seem to draw 32w in total when the IR are on at night so there is still spare capacity there.

Doing it the way I did means that the NVR to the Netgear POE switch is a straight connection and thus has no impact on my LAN, unless I am accessing the cameras etc.

Finally not needing the NVR close to where the wires of the camera enter the building allows me to hide the NVR wherever I wish as they are connected directly via that POE switch and thus only need a single (and not six) Ethernet connection.

I do not consider security to be a concern with my set up.

Still not sure why you would want a different subnet as you have your set up...?

All six of my cameras are connected to a Netgear 8 port POE switch. I have not used any of the POE ports on the NVR. I have manually assigned each of the IP addresses (inc subnet) and gateways etc for each of the devices using the SADP utility.

Why do you not use that tool to assign them with the same subnet as the NVR...?

I also have doubts about the proper functioning of motion detection. I have several examples where specific motion events hae no been detected. Thankfully I had specified the whole system to have enough bandwidth and storage for continuous recording. So now I am operating on continuous recording 24x7 to be safe. The annoying thing is that when the disks get filled up and the overwrite of the oldest recording begins the available free space on the disks is always 0, which is right but obviously meaningless after the first overwrite.

 

I also have two disks for redundancy. I discovered that the video is never lost irrespectively which disks disappeares for whatever reason but the log is only written in the first disk and it is not recorded mirrored in the second disk.

It is annoying when I seem to be able to capture a potted plant swaying a fraction but then miss a person walking by...! Or that some activity is clipped due to anomalies in the consistency with the motion detection. I have only one disk in my NVR, a WD 4TB purple. With the system being quite new it has not yet filled up. But, like you, I have got the ability for 24/7 recording and the bandwidth calculator shows that I'm just at the edge of what is claimed to be support for the NVR. The free space showing as 0 might be "right" but it is less than useful once the disk as filled up for the first time.

The motion detection anomalies do not seem new to me as my analogue systems would also have this issue. The missing motion capture aspect of either my previous systems or this Hikvision set up could not be entirely trusted for reliability in having just motion recordings.

I just like them as they flag the recordings with "markers" which have some use when reviewing recordings.

Hence my reasoning, if you prefer to use the time-line aspect of the web interface, for the motion detection flags to be shown on the otherwise solid blue time-line.

At which software or interface do you see your attached pictures and under which menu?

Hikvision Tools...

SADP for the Live View Image and Bandwidth calculator for the other.

Hikvision Tools(V1.0.0.2) Setup

http://www.hikvision.com/en/download_more.asp?id=1178

When I initially tried the 2.39 beta I had three of my cams updated to the 5.20 firmware and three were still in the post. So it worked fine. Since then I have connected the newly arrived cams (all 5.16) and downgraded the 5.20 cams and all remains well.

So I have all six cams working fine with the 2.39 beta and 5.16 firmware on my cams.

Not a straight forward install, as such, but great that you have got your cams working and some consideration might need to be given to the camera firmware, as you note.

Any reason you have remained with that firmware for your cams...?

I think that Ill hold back a little as the 2.39 beta seems to work fine with all of my six cameras (5.16 firmware) and I don't feel like changing over to the 5.20 just to test out this firmware for the NVR. I have just downgraded three of the cams back to 5.16.

Hope that you get your other three cams working without the need to "upgrade" them. Hopefully if others are feeling brave they will post back their results.

Ok thanks

It does seem that you can still search for a motion detection event within the software iVMS-4200 Client, and download just those, rather than just the continuous recordings. But you don't seem to be able to get a timeline showing those motion detection events as I noted above.

Anyway I have emailed Hikvision to ask their opinion.

Interesting observations on 2.39 event tracking, I have no answers but will be following.

It got me too when I updated to 2.38, it should be on the Maintenance screen on the lower left side (red dot).

If it is missing you may want to reset to default and see if it shows up then.

Thanks for that, at least I know how, if I should ever want to, switch it off in a safe manner, goodness knows how I missed that dot

The following is a fake mock up of what I would have liked.....

the build up of what would be a solid blue bar indicating a continuous record and then segmented when tagged with a motion detection event. To me it seems pretty basic in what I would expect but I can't seem to achieve that. If it can't be tagged all that you would have is a solid blue timeline bar with no event tagging which makes it a little pointless when overviewing any timeline for triggered tagging etc.

Any ideas on the bandwidth part of my question...?

Many thanks

Hi

I have a Hikvision DS-7608NI-SE/P NVR and I have flashed it with the 2.3.9 beta firmware.

I have six Hikvision IP cameras connected to it and all seems well, learning various settings and configurations etc.

At the moment I have each of the six cameras set up for motion recording. In the main it works well but even though the sensitivity is really good, recording the minimum of movements etc, there are times when it will either clip too much before a car or person has entered the frame or not recording enough for the duration of movement. I have set it to record 5 (and then tried 10) seconds prior to the trigger and 30 seconds after but still it can be clipped. This used to be the case with my older analogue D1 type system and thus I moved to continuous recording but kept the motion detection recordings as well.

With this Hikvision though, I am mainly using the web interface to access it, if I have each camera set (just going to show Cam 1 as an example) to still pick up on the previously noted motion trigger (and to trigger an event) this will no longer be shown in the timeline....

....you can see the yellow marked segments as they represented motion detection recordings. But you can now see a solid blue bar which shows a continuous recording, even though there are individual motion events within that solid blue time period. What I am not able to do, or find, is to show or search for just motion detection recordings (or markers) from when the NVR is continuously recording.

With my old analogue system and generic DVR I could use the CMS software to search by Alarm, Motion, period etc etc. Thus it was always possible to ensure that no motion events were missed being recorded and none were ever clipped. The timeline on that could show various markings or colours representing the triggers which caused the tagging.

So is it possible to sho a timeline whilst might be blue and solid to indicate a continuous recrding but also indicate where a motion trigger was tagged.....?

Also my six cams are set as follows....

...so I should be ok as this is the maximum that the NVR can manage, in terms of bandwidth. But if I did, for example, change two of the cams to 20fps it would then push the max to around 45mb/sec but as long as all six channels are not recording at the same time would that be acceptable or could that cause an issue...? It will accept those settings so I assume that they could be ok...?

Last point I must be missing this but when I had an older 2.37 firmware installed on the NVR I found the power down option easy enough in the NVR menu but for the life of me I can't find it again...?!

Thanks for any advice

I upgraded my cameras to 5.2.0 without reading the forums first....shouldn't have done that. Now I've been able to downgrade one to 5.1.6, but the other acted like the firmware took over TFTP just like the previous one did, but now it's not responding. I've rebooted it multiple times, and it doesn't even try to connect to the TFTP and doesn't respond to pings on 192.0.0.64 either. Any ideas, or did this camera brick itself?

 

Downgrading 5.2.0 -> 5.16 works. Checked!

PC LAN CARD IP=192.0.0.64

RUN HIKVISION TFTP with digicap.dav in directory

IPC POWER ON

READ message in window

CLOSE TFTP after success messages.

Reboot IPC

 

Besides, I made ​​a custom firmware that reduces the version from 5.2.0 to 5.1.6, which can be used in the web interface.

Checked!

Are you going to share that one for those who wish to "upgrade" back to 5.16....?

I've noticed an anomaly with the 6mm ds-2cd2032-i that has more blue in the image than say the 4mm or 12mm lenses. Almost like the affect you get from a broken IR filter but nowhere near as strong, so it's not that. Could be a lens design issue or the IR filter color used in the 6mm is different, but I would think they use the same IR filter with the different lenses, or not.

 

Anyone have the same experience with this lens?

I have just had that camera (ds-2cd2032-i) delivered from Aliexpress with a 6mm lens fitted. Two of my DS-2CD2332-I cameras are still in the post but three of them have now been fitted. Comparing both types of camera images for colour hues they are both very similar with no difference noted at all.

I do not have another ds-2cd2032-i to do a direct comparison.

I used the web interface from a networked PC to upgrade the firmware (done twice now) on my NVR.

This might not matter but would linking that firmware be the "right one" for the OP...?

 

The reason I'm asking is that I bought the DS-7608NI-SE/P and it came with the same revision of firmware as the OP first noted ( V2.3.7 build 131112) and I was told by the seller over at Aliexpress to not use the USA firmwares but to use the EU ones and thus I upgraded my NVR to V2.3.7 Build 140609. That is the latest one on the Hikvision EU site for download.

 

The Image settings noted by the OP from his last picture shows the WDR etc functionality and this whole section is missing in the firmware I updated the NVR to.

 

Again I was advised not to use the US firmware as that would not be the right one for my NVR, but I do not know if that applies to the OP or even if it is valid...?

 

 

I have the same experience.

 

I have a HIK DS-7604NI-SEP with serial number that contains the characters BBRR in the middle of the string. I tried to upgrade from firmware 2.3.7 build 131112 to the firmware 2.3.8 build 140513 from the USA HIK ftp site and it failed half way through with the message "Upgrading failed, no enough flash memory". It also failed when I tried the USA firmware 2.3.7 build 140122.

 

Careful these are the 5 versions of 2.3.7 available in total sorted by date.

Version 2.3.7 build 131112 from the European portal most commonly ecountered in many HIK 760X NVRs (file size 13.677.413

Version 2.3.7 build 140122 from the USA HIK ftp site (file size 14.831.804)

Version 2.3.7 build 140327 from the European portal (file size 15.461.588)

Version 2.3.7 build 140411 from the European portal (file size 15.456.928)

Version 2.3.7 build 140609 from the European portal (file size 14.270.397)

Then the following firmware versions followed (file size 14.830.554)

Version 2.3.8 build 140513 from the USA HIK ftp site (file size 14.209.552)

Version 2.3.9 build 140704 beta from the USA HIK ftp site

 

If anyone else has additional information or know anything better, please advise.

 

I only managed to upgrade with the latest European build 140609. I have NOT tried upgrading to 2.3.9 build 140704 beta yet.

What is this flash memory? Why smaller firmwares can not fit in the flash memory and the larger firmwares are acceptable and only from the European portal? Is there a connection with the 4 characters in the serial in the same way as the region in the cameras firmwares?

 

I urge anyone who has upgraded succesfully this NVR to inform us which model they have upgraded, the characters in the serial number and from which version firmware they upgraded to which version taking into account the above information of the firmware history.

I have upgraded without issue to the latest beta firmware noted.

I have a Hikvision DS-7608NI-SE/P bought from Aliexpress. It has BBRR within the serial number.

I had the following firmware prior to the upgrade....

Version 2.3.7 build 140609 from the European portal

I have four Hikvision cameras attached via a POE switch at the time of the upgrade and they were recording.

The upgrade went without issue.

I have used the EU/US versions on my NVR, both the same.

Thanks for that confirmation

I have upgraded to the 2.3.9 beta and posted about a concern about it, in the section from the above link, regarding scheduled recordings. This "issue" has been resolved as it seems that the problem was related to the cache in Firefox. Once cleaned then I got the "new" UI changes without the old ones also being present.

This might not matter but would linking that firmware be the "right one" for the OP...?

The reason I'm asking is that I bought the DS-7608NI-SE/P and it came with the same revision of firmware as the OP first noted ( V2.3.7 build 131112) and I was told by the seller over at Aliexpress to not use the USA firmwares but to use the EU ones and thus I upgraded my NVR to V2.3.7 Build 140609. That is the latest one on the Hikvision EU site for download.

The Image settings noted by the OP from his last picture shows the WDR etc functionality and this whole section is missing in the firmware I updated the NVR to.

Again I was advised not to use the US firmware as that would not be the right one for my NVR, but I do not know if that applies to the OP or even if it is valid...?