CBX

I believe you have a Chinese factory version camera that the supplier put hacked files on so it would show in English. The CH part in your serial indicates the Chinese factory version.

Yes sir, that it is. Interestingly enough it displays the day of the week in English. I was wondering if you wanted a dump of the firmware to examine. If it's showing English day of the week and English menus on 5.1.6 that you have put on yourself (not that it came with) without my region changer program or manual file hacks then you have an English factory version camera If all of the above not the case then probably not You can always check if you want by putting on original non hacked 5.1.6 yourself or new firmware when released, but be aware your camera might then have Chinese menus and OSD.

Looks Chinese due to label. But look in web interface and you will see full serial number: e.g. DS-2CD2032-I20140619CCCH123456789 CH = Chinese factory version.

No it's been pulled due to an issue with 5.1.6. And it didn't have everything enabled in it anyway due to library/compilation issues. I do make software for these cameras according to people's need these days, feel free to PM me if you want to discuss.

Yes totally correct - the new program thread in my post is evidence of this. The camera is doing more work. That is probably OK and my cameras are doing more still with NFS server functionality, ssh server etc which is not standard. It's hard to know why they pulled it, but in my mind the extra functionality is reserved for the advaned smart series of their new cameras. I'm happy to be told I'm wrong by someone who knows Hikvision though

If you have CH in your serial number it's the Chinese version. If you've put 5.1.6 on yourself and your camera is still in English (replacing any hacked files the supplier put on), then you have a English version camera (unless you used my region change program).

I wonder if this is why it was pulled. I've noticed my cameras now have a higher average CPU load due to the extra work it is doing: # ps fax -T | grep smart 1259 root 4:14 {ipc_smartDetCtr} /home/davinci # uptime 11:39:21 up 13 days, 17:25, 0 users, load average: 4.13, 4.19, 4.22 Average load used to be 3-3.5

No same code base and kernel etc (for now at least anyway). But can now change things that were read only on filesystem and install extra software not manually on each camera but just via firmware upgrade with customised digicap.dav Planning to add some of my developments so far such as language patches, busybox improvement, ssh plus a few network monitoring agents for centralised management. Could change kernel but a lot of work and won't unless needed. Also keep original davinci.tar.gz but just patch in memory which is alot cleaner and better for any future fw updates from Hikvision. Certainly won't be publically publishing customised firmware to the whole world as contains copyrighted code from Hikvision.

HAHAHA!

Built and applied custom firmware: http://www.cctvforum.com/viewtopic.php?t=41103

I'm not sure myself but some people will know

I've tested NVRs in the past (with help from others) and yes - should be resettable.

Use the firmware matching the region of the camera. There is no advantage in forcing a flash of firmware from a different region. It doesn't matter which region the fw it is - it currently makes no difference to the camera (the chinese language issues have nothing to do with which region the firmware is, only the region setting in the cameras flash memory).

Just to let you know you can also enable the ftp server on the camera and pull the files rather than push. Search my posts for info. Also, you'll get massive extent files - not the individual videos/pics on the SD card which is probably not what you want. If you want to extract the videos and pics only you'll need to either: - use the web interface - use the SDK - write your own file extractor to parse the index files (which is actually quite fun if you like such things)

Yes - any Hikvision IPC you can always email Hikvision for it - there's a youtube video of how.

You need to change IP (or create an alias) to that on the camera subnet (e.g. 192.0.0.128), login in to the camera and set it's IP to your network. Then change your computer back to normal. Good luck!

Well there's lot of traffic from your cam on 192.0.0.64 .... I suppose it's possible the cam is running on that IP before it switches to another one, but I'd configure your linux box to be on the 192.0.0.0/24 subnet and try talking to the camera on 192.0.0.64

Depending on your linux box you may have to run this as root, as possbility specify the network interface to listen on. Try man tcpdump And you'll then need to power off and back on your camera whilst tcpdump is listening.

I haven't read the whole thread fully, so I might have posted wrong advice. I am assuming that your camera is on the same subnet as your computer (I don't mean IP - on the same section of network). If it is, then the router functions aren't needed - only the switch/hub part. Since you were using Ubuntu, I assumed good networking knowledge (no offense is intended here). If you have access to Windows, you may be better off with wireshark as is graphical. The idea is that wirehsark/tcpdump listens to the network and reports traffic it sees. The camera when it boots up will be trying to connect to things and you would be able to see what IP address that's from. Here's a tcpdump example where I filter out ssh traffic (otherwise I'll get flooded with results as I'm using ssh to run tcpdump): root@rl70:~# tcpdump -n | grep -v ssh tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 11:46:13.336981 IP 192.168.0.6.22 > 192.168.0.15.2775: Flags [P.], seq 3250769780:3250769976, ack 1301303205, win 43952, length 196 11:46:13.448615 IP 192.168.0.15.2775 > 192.168.0.6.22: Flags [.], ack 196, win 65535, length 0 11:46:13.790055 IP 192.168.0.100.138 > 192.168.0.255.138: NBT UDP PACKET(138) 11:46:19.111707 IP 192.168.0.202.80 > 192.168.0.6.41450: Flags [P.], seq 3497760973:3497763344, ack 638217591, win 8453, options [nop,nop,TS val 454588382 ecr 1165145], length 2371 In the last line uou can see my server (192.168.0.6) get a response from the webserver (port 80) of one of my cameras (192.168.0.202). If this doesn't make sense to you, or I've got your situation wrong, then please ignore me.

Just to be clear, that link and poster have no connection to, or endorsement from me. That's not saying it is or isn't legit - just nothing to do with me.

You can always just use tcpdump on linux or wireshark on Windows to listen for the camera when it's booting - should reveal the IP address (if it's not on 192.0.0.64). Some people also get confused about 192.0.0.64 and think it's 192.168.0.64 (which would have made more sense Hikvision!).

If you are happy in linux then you can also just assign an IP to an alias of your NIC: root@rl70:~# ifconfig eth0:0 192.0.0.128 When done: root@rl70:~# ifconfig eth0:0 down Also, in terms of configuring the cam, you could use WINE but a linux ONVIF program would be much easier.

I had similar thoughts myself, and agree with everything you said. It's because it's technology and most people don't understand the details. If you say the following: My credit card account has been hacked and 1000s stolen! Admittedly I did give my card with the pin number written on the back to a local thief but I can't believe my bank allowed their systems to be hacked! ...then people wouldn't be blaming the bank would they. I'm not saying this analogy is exactly the same as this situation but I think it shows that if it is something more tangeble that people understand it can be looked upon very differently.

Well the Chinese > English patch is mine, and some other stuff I've posted in a different thread - but the NAS fix is who done by someone else so the credit for that goes to them (not sure who that was as I don't use it). I don't actually change the bytes in the davinci file or it's tar container, but rather patch the program in memory just before it runs. But that means changing a script on the (linux) camera which isn't for everyone and runs the risk of having to reflash your camera if you mess it up. And as for the hard way issue - posting the patched binary may be a copyright violation of Hikvision's code - whereas posting the bytes to change isn't. Though in practice they could object to one, neither or both if they wanted to to some degree.

Certainly if the hardware is all there then a patch (or changing values in the flash) would work for wireless. I myself have no ethical issues with this as I consider that if you bought a product which has been crippled by the manufacturer then you have the right to modify your own property. If you were selling them then that would be a different case. I don't have that camera, and like you say wired is preferred for most. But you could likely come up with a patch if so minded. I think I activated wireless on mine when playing with the code (though mine don't have the hardware of course). Changing the flash is not insurmountable, it just comes with risks of bricking your camera and future detection by Hikvision if they decide to check in future firmware updates (though I suppose you could revert your flash values back before flashing or investigate new davinci first). I think I could do it, but I don't want to risk my cameras and given I modify them so much anyway am happy with patching davinci in memory before execution.