zikronix

Already been there done that. I don't know what version he sent me, this camera has 13402 on it, I expected 13805 when I was done that is not what I got. I was still on 13402. I did attempt a web upgrade after that and I got the language mismatch, which doesnt surprise me. Now Im upgrading to us, 13805...and gonna try the tftp again. When Im done with that im going to play with some hex stuff, and inspect the board for points that maybe could be soldered together to enable write? or version info

Well it hasn't worked yet, im trying some other things and poking around in telnet.

Just curious...why the secrecy? Why not post it in public? Other than people that are trying to resolve the language mismatch, who really cares? Are you going to inflame some Chinese distributor and cause the prices of Chinese cameras to skyrocket? I think the questions to be resolved are that (to my knowledge) nobody has shown that those three bytes are the lone factor causing the language mismatch error and upgrading via the tftp process with a hex-edited firmware may be a viable option. Well I know the EU and the US version are Identical...which is to be expected He just sent me the firmware....standby EDIT: according to the TFTP it took the firmware...but something is weird. Here, when I rebooted the camera I was able to get into it, but It all looks the same. What build number is this firmware you sent me?

yes modify the three bytes is technically useless, its more a proof of concept. I the point Im wondering is if my weekday would turn to Chinese!

Here is idea for you Avigilon camera has I/O Avigilon software has rules if u creative u can have lots of fun Read on their website That idea is nice...but its also like 6 times my budget so....because of how my house is shaped I have no less then 6 cameras out side, and at least 3 inside. With the hikvisons I can pull it off with decent results for a reasonable cost. Currently im running the swann 8 camera from Costco, and it works well for what it is. It was one of those things wife said do something now stop dicking around...so I did. Now that ive had the chance to do some actual research and put numbers together this is what I came up with!

Yes that's what im looking for, I would like more inputs, but now I kinda know what to look for. I guess that brings me to the next question. Do products like milestone, avilgon, exaq support these things? I don't anticipate BI supporting it.

The Hikvison don't have the input outputs....yeah yeah I know use a better camera. If I was using one of their NVR/Encoders I wouldn't have to deal with it. but im not currently

Im might be interested in this product as well. Ill send you a pm in the next few days, to tell you what im looking at.

So if im understanding correctly your saying the plastic housing of the lens if most likely shifting do the heat? Thus causing the loss of focus? So would it be safe to assume the domes could have the same problem? Which in Arizona isn't going to work, not when its 120 out side!

The question is whether the language indicator is embedded within the firmware itself (could be consistent with the microscopic difference between the firmwares), in which case it could be changed if only it was possible to trick the currently running firmware to accept the US/Euro firmware. The size difference you are referring to, is compressed vs uncompressed. The actual firmware binary is around 18 Mb, and if you zip that it shrinks to around 12 MB (thus it is highly compressible). correct the us is 18Mb uncompressed. Here are the facts...all these cameras are the same Chinese, eu, and us from a hardware stand point. Sure I don't know that 100% but im willing to bet large sums of money that I don't have on it. The factory most likely has chips that are preburned with the region data, or they use a header or tft to flash them after prod. So that means either that value is burned into a rom on the board, or its from the firmware. I have a camera here im willing to try to put the Chinese version on, and it should error out if I do it though the web. The tftp process should start before general system boot. So Ill try the tftp method if some one gets me the firmware and what the tftp address is. I am also willing to try a hex edit of the Chinese version changing the three bytes to match the US and see if it flashes to the camera. If I edit the Chinese version and change those three bytes then we know its in the firmware. The real trick would be to this, if I modify those three bytes to match the us version of the firmware and it flashes...will the Day be in Chinese? Subsequently if that works then one should be able to modify the US version and flash it to a Chinese camera, which I cant test because I don't have a Chinese camera. so some one post some firmwares, and the tftp IP so I can get a started!

put the two firmwares in a file compare or in a hex editor and see if there are differences.

NFS share must be public. Setup quota on your nas, as it will fill the drive...I dont recall if it records directly to the nfs or backs it up or what

It was in the online oinly offers booklet that mailes last week some time

Step 1) DVR lockbox. Rough cost 100-150.00 ebay Step 2) Install second harddrive for mirroring Step 3) Off load data from NVR to local NFS share Step 4) Off load from NAS to cloud.

i have to double check, i looked it over and it looked just like the foam i moved around on my 4mm, just bigger, no idea that was a plastic piece. So is the old style dome camera the one with the hard plastic insert? No this is definitly the new style, they have the plastic housing on the light sensor.

Is yours plastic

From Wrightwood 8/2013 2.8mm http://imgur.com/a/bHGdY

Mine were not that bad but also did cover some of the LEDS. What I did with mine was just flip the foam upside down and press and tuck the foam down between the lens and LEDs. Looked fine after than. thats exactly what i did as well! they have been working well for a few weeks now that way. Cant do that with the latest builds. Its a hard piece of plastic with foam on it. It would be a pita to remove and theres not enough space in the in between the leds and the lens to push iit down in there.

No clue...im sure poking around in tech docs might be able to find it though

The swann is a 7708 in a different case and the Lorex is a 7608. More interesting is the swann 16 port has a 16 port Poe switch and hik vision doesn't have an oem of it only an 8 port Poe switch. I'm pretty sure their 16 port is a 7716

PM sent

Starting to think this may be why they have auto-focus versions. In theory if you tighten down the adjustments, tight(er) with a flat screw driver they shouldn't move. I live in AZ, and I picked up a ton of fixed domes from a vendor in a "Panic" sale last night...LOL. I still have my one varifocal dome, and ill tell you right now if it moves in the heat. That will NOT work

Did the upgrade to V5.02_130805 from the usa ftp Camera did not die and now reports V5.0.2 130805 in firmware. I did not see any menu changes or additional options...which is to be expected.

Ill try it on a swann when I get home...but sure it concerns me but im sure its just langauge differences. Put it in an hex editor and look at it.

I feel like they go out of their way to make things obsure. Selling products to people like swann and lorex that you cant buy (dvr with 16 poe ports) their US site doesnt have half the firmware for their NVR. Their us site doesnt list all the NVR available example http://www.hikvision.com/en/us/products.asp?cid=50271#Menu=ChildMenu5 vs http://www.hikvision.com/en/Products_show.asp?id=6528#Menu=ChildMenu5 I know this how this all works because it happens in IT all the time, but its just so odd