Recent content by darrylb

Thanks, I probably could do that, but don't have the required hardware. I am tempted to send it back for replacement. If this is a Chinese one as well, at least knowing that, I could have handled it differently. On a side note, I am never resetting all my cameras with unplugging the POE adapter...

Thanks! Yeah Ill track that down later this week. Right now just trying to get my last camera (the new one) the 2142 functioning. For the life of me, I cant get it to look at the TFTP server, like the other camera's do.

Yeah, this has me rethinking Hikvision in the future. I may keep these on the front of my house, and then switch to something else, when needing more.

I am starting to figure that out. Is there an official way to find out? The "Downgrader" has just saved my two older ones. I find it interesting though. The 2132F-IS updated to v5.2.5 in English, but my 2032-I updated to v5.2.5 in Chinese. What are next steps to convert the Chinese to English...

-- Downgrader fixed my 2CD2132F-IS, now is at V5.2.5. So if I understand correctly, this would indicate that one was a Chinese one.

Thanks... :| Well, I found the "Min-System" is an incompatible firmware, So I am currently trying the Downgrader solution that some say fix that. The problem is, on the new one, I never applied a new firmware... Not that I can figure. Unless no matter what, the device always tries to install...

Hello All, I have 3 Hikvision Camera's. - 1 Hikvision 2132 - 1 Hikvision 2142 - 1 Hikvision Bullet (Cant recall version). Additionally, they are all wired to a switch and a POE injector. When I got the new 2142 yesterday, I plugged it in, and it worked great. I like the newer firmware, so I...

Yeah, it was very picky about the exact path it was looking in. Also, I had to restart the camera a few times, and it finally grabbed it.

Okay, I was able to figure it out. For some reason, it seems to be very PATH SPECIFIC. I thought I was being smart, and using a different path. But by following directions exactly, I was able to get back in :)

Hello everyone, I am trying to unbrick my 5.2 that went wrong... I run the tftp server, assign it 192.0.0.128 on my desktop (ip), I see the "TEST" statement show, but never get a connection. When I ping 192.0.0.64, I get about 3 ping responses and then it stops. a few minutes later, I get...

Understood!. I will use the other one I have (to unbrick with), which is : 2xx2_Series_IP_Camera_Firmware_v5.2.0_140721 and the file in it is digicap.dav, file size is: 19,786KB. This sound correct? :)

Done!

Interesting... My original davinci.tar.gz: 2,523,136 bytes. My new one was: 5,309,046 bytes

I wouldn't argue that I most likely broke it. Not sure what I did wrong though. I only found the 5.1 Hex, which I updated closely and confirmed valid. And my file did tar.gz successfully... In my defense, I am an IT guy... took my time, and validated everything... How much bigger will the...

Well, that's a bummer. I tried it out, seems I bricked it. :( Yep, definitely bricked. Not pingable. Seems like tonight I get to try a TFTP update back to 5.2 When I did mine, I could not find the hex for 5.0.1, and tried based on 5.1.. Doesn't seem it liked that. I also found that my .tar.gz...