tonydi

One 3TB drive with three shares. But I don't see any way to allocate less than the whole drive to any camera, those settings show the whole 3TB but are grey'd out so I can't change the numbers. I found a great deal on WD 3TB Red drives so I'm going to take the "easy" way out and give each camera it's own drive.

I think I've single-handedly worn out the Google servers looking for this today and I've come up empty. If anyone can point me in the right direction I'd be very appreciative.

Despite the fact that all three of my cameras have the Overwrite set to Yes, they filled up the 3TB drive in my NAS box and then just stopped recording. At around 6pm I went into the Playback section and picked today's recording and the bar graph actually showed that it was still recording even though it had stopped writing to the NAS about 13 hrs before. The NAS is an Acer Aspire H340 running NAS4FREE. Is there something I'm missing, something I didn't set correctly?

All 3 of my 2032's are sending emails with motion attachments just fine, however I'm pointing them at my own domain's SMTP server. Originally I was sending them through a Gmail account, back when I had only one camera. After a couple of days, Gmail locked my account for a period of time. Apparently there's a move afoot to stop anything that's not human from sending email through a Gmail server probably as an anti-spam measure. Subsequently I happened to talk to a Microsoft dev who works on their email servers and he reluctantly gave up the info that they, too, are trying to stop the exact same sort of traffic on their web mail platforms. Could this be what you're butting up against?

The DDNS service is so when you're away from your network, you don't need to know the actual public IP address of your network. If you're like most people, the public IP can change so the DDNS keeps track of that and updates it when it changes. So essentially it's an alias that you can use that always points to the real IP. A note about port 554....if you're on AT&T, be aware that they block 554 on their 3G/4G network. That gave me fits because I could see my cameras at home and even from other people's computers at various places. And my phone worked at home on wifi, but as soon as I left the house and switched to cell data, I couldn't see the cams. Once I discovered the 554 block, I simply changed my equipment to use 555 and everything worked.

No updates, both are using the firmware they came with. But you're right, no telling what sorts of shenanigans have been pulled before these are shipped to the US.

No thats julias personal hack so she can watch/access your cameras Hi Julia! So let's see, we've got Julia watching hundreds of camera feeds and now we know that anyone can grab snapshots if they know your IP... http://www.cctvforum.com/viewtopic.php?f=19&t=41641.

Yes, it records and plays back just fine. The last camera I got, the one with 5.1.6, appears to have come from CCTV Camera China with CBX's fix already in place. There's an actual file on the camera with a log from his process.

I have two DS-2CD2032-I cams, both Chinese versions with Chinese firmware, purchased from CCTV Camera China. One has V5.1.2 build 140116 and the other has V5.1.6 build 140412 firmware that the vendor applied the hack to give English UI (well, multi-language capability). I don't normally use IVMS-4200 so I'm not sure what's supposedly broken, but it seems fine to me...

The vendor has confirmed that they patched the camera for English. Now, the only question is, has anyone patched this version for CIFS compatibility and not bricked it using the 5001D4C09DE50000000007005CE100000000 hex string to replace the stock 5001D4C09DE52C00001A07005CE12A00001A string?

No denials so I'd say you've got a good theory, Ray.

Ok, here's the deal and it does make sense. Hikvision support says the only time they actually save the snapshot in my situation (24x7 recording) is when you specify the email or ftp option. That's because they need the snapshot saved in order to perform those tasks. Since I just wanted the snapshots to narrow down the time frame when an event occurs so that I didn't have to wander through hours of recorded video, they said just enable the motion detection. Then look through the LOG to find the Motion Detection events. So I'll definitely be re-"formatting" my NAS since there's no reason to devote all that space to pictures now.

I've got a second Chinese version Hikvision DS-2CD2032-I and this one has V5.1.6 build 140412. I patched the davinci file on my first camera so it would properly initialize my CFS NAS. The davinci file from this camera has the same string so I modified the file. When I went to load it back onto the camera, I noticed the /dav folder had a file named davinci.tar.gz.patch.txt. Here's what that file has inside.... ======================== Cyclone Bit Xtra Patcher 0.0.7b ------------------------------- #WARNING - DO NOT ATTEMPT CAMERA MODIFICATION BY SIMPLY COPYING PATCHED FILES #YOU MAY BRICK YOUR CAMERA WITHOUT PATCHER EXECUTABLE!!! Detecting version ....done 5.1.6 Reading serial from mtd5 ....done Reading language flag from flash ....done Unprotecting flash memory ....done Patching dav ....done Enable _malloc() in kernel ksyms ....done Sanity check proc table ....done Enable languages in davinci ....done AES Decrypt start ...........................................................................................................................................................................................done Checking camera part table layout ....done (OK 0x00) Writing new checksum to flash ....done Watchdog disable ....done Reprotect flash ....done Deleting patcher from camera mtd ....done FINISHED!!!! Error code is: 0x00 Checksum: 97f9b1ad81ea4a7b8ed026487d569706 debug: 0x71977927a830 ============ I haven't seen this file mentioned previously in all of the discussions on patching davinci. Should I go ahead and upload the patched file to the camera, figuring this is just a CYA move on the part of Hikvision, or am I missing something here?

I still want the other email notifications, like for HD failure or illegal logins, so it seemed like it would just be best to have one account and just block the snapshot emails. I will contact Hikvision about this but I was first trying to be certain it wasn't just me being stupid and not figuring out how to configure something that was staring me in the face. Thanks for the info on alarms, makes perfect sense now.

Well, the NAS is hung on the network as is the camera, but essentially yeah, the Hikvision camera has the ability to address the NAS directly, without any computer/software help. At this point in time, I'm successful in getting everything pushed to the NAS except the ability to save a Snapshot triggered by motion WITHOUT also sending that snapshot attached to an email. If I tell the camera to email me motion-triggered snapshots, it all works. I guess I still don't understand what the "alarm" function is for. When doing the scheduling for capturing snapshots, there's a distinction between "motion" and "alarm". Anyway, if I can't find a way for it to just save the snapshots to the NAS without emailing them, then I'll probably turn that option back on and just nuke the incoming emails at my domain's email server. That way I'll have the snapshots on the NAS and won't have an inbox full of snapshot mail and attachments.