khx73

I didn't realize 8 weren't PoE either. I guess I never looked into it, as the 16 port system was overkill for me. The 8 port one I got was all PoE. The idea may be that anyone requiring that many cameras probably isn't going to be doing home-run cabling from each camera to the NVR. More likely some would be far enough away that it would make more sense to power them from their own PoE switch, and uplink one single cable back to the NVR. The extra $200 for the other system may be worth it, if it's practical for you to make use of the 16 actual PoE ports. I don't know the area you have to cable for that many cameras, but consider the cost and trouble of all the possible cabling. Would it make sense maybe to buy a second PoE switch for a distant group of cameras and only have to run one single cable back. May offset your $200 pretty quick. Hopefully someone else will chime in with input on Dahua for you. When you ask "good enough?" , that's hard to answer. Good enough for the average home user? Certainly, in my opinion. For the pro market? No. Huge difference in price though. Different markets.

According to Korgoth Of Barbaria's post http://www.cctvforum.com/viewtopic.php?f=19&t=45515&start=50 , 12-14Mbps. Depending on your bitrate settings of course. Not enough to make a 100Mbps port even break a sweat. A gigabit port PoE switch would add a lot of cost for no benefit.

1 - Go for it. Only hassle would be a return if you needed to. 2 - Can't really answer that... I don't know anything about Qsee. I do own the swann system from there (the 8 cam one). 3 - See above 4 - All the time... Seems like every other month I get the costco ad email and the systems are on sale. I believe they are right now. Got mine on sale. The swann system as you mentioned you know, is re-branded Hikvision gear. I've had no issues, and have even added extra Hikvision cameras to it (not rebranded) since they're the same, works fine. You can also communicate with the cameras directly and access further configuration options than would be available just through the NVR. I also play around with Blue Iris software, using the same cameras at the same time. No interference with the NVR system at all. Once you get to know how things work, it's really quite versatile. It's a good, functional solution that should serve you well, without breaking the bank. The pro stuff and pro installers definitely have their place, but for the average home user, this system is quite capable. I'm pleased with mine.

You can, so do it. Just make sure you choose an unused IP. Keep it simple and don't even use the WAN port on the WiFi router. Just plug one cable from the PoE ports to the LAN section of the wifi router, then connect your iPad over wifi with a static IP. This way you don't have to touch the router settings at all - just use it as a simple switch that happens to have wifi access.

Have you tried getting to the web interface on the 806? http://(ip address) Assuming it's a rebanded Hikvsion like the NHD-820, the full web interface will give you access to everything.

To override this in Chrome (for now), enter: chrome://flags/#enable-npapi in Chrome's address bar. Click Enable on the 'enable-npapi' feature when the list comes up. Restart Chrome. Voila. Good until September 2015 when they'll remove NPAPI plugin support permanently. Wonder if Hikvision and others are working on an updated technology for their plugins?

pjaneiro- I added a Hikvision 2032 to my Swann system with no problems whatsoever. Auto-detected and auto configured just like the Swann branded ones that came with the system. Of course that doesn't really help answer the OP's question... He's trying to get a slightly different model working.. I just added the identical model (without the swann branding & firmware).

255.255.255.0 should be fine. Set the PC or laptop you hooked up to something like 192.0.0.2 . Then you should be able to access the new camera's web interface at 192.0.0.64. That is all assuming that: 1- the cam is working. 2- it's default IP is 192.0.0.64 (and is still currently set to that) Now, that being a Swann branded cam, it may have had it's default Hikvision ip changed. You may need to use the SADP tool to locate it.

I'll toss around some ideas... Not saying I have the fix or anything..but here goes. I'd start by proving out the new cameras. Hook one at a time to the NVR so it's powered up over PoE. Connect a laptop or PC to one of the free ports, with an IP in the 192.0.0.x range, so you can talk to the new camera. The new cam should be accessible at 192.0.0.64 if it hasn't been re-configured. Verify it works fine, and that it's at the factory default settings (or else your NVR might not be able to configure it automatically). I assume they were new and un-opened, so this shouldn't be the issue. Log into each one and try setting it up like the 1080p ones as far as the network config goes. I believe the NVR tries to set them up in the 172.16.1.x range. (I have the NVR8-7250, and this is the case). Then try manually adding it to the NVR's configured cameras list if need be. Start with that.. see what you find out. I'm assuming you aren't a stranger to the network stuff, being a linux guy.

Just wondering.. is that a DVR or actually the NVR8-7200?

No it does not matter that your NVR is PoE. The NVR's poe function won't be used if you use a separate poe switch near the cameras.

Thank khx but that path stopped working for me the last time I updated firmware and broke this same process until I found the /onvif/snapshot path. I'm still digging though. Dave Ok, none of your example URLs ended in /picture . That's why I suggested it. Also, I should have added that this example works on my 2032, after the firmware update broke the onvif one. So of course no guarantees it'll work on your 2132.

http://ip:port/Streaming/channels/1/picture works for me... prompts for user/pass

Yeah it does look huge to be a ferrite choke.. unless it has to be that big due to the possible long cable runs. Just guessing. I didn't know about the Dahua thing.. sounds reasonable.

Looks like a ferrite choke, used to supress high frequency interfering noise on the line. You see them often on video cables, etc. Like the one going to your computer monitor sometimes.

I think I read that the 2032 draws 7W max .. worst case (IR leds on, etc). 584mA by my math (at 12V).

Turn off uPnP (Universal Plug and Play) and NAT in the camera's config. These functions send commands to your uPnP enabled router to open the ports necessary. This is what it is supposed to do, to make it easy for non-technical people to not have to worry about stuff like port forwarding, etc. While you're in there, turn off Platform Access (if it's there). This should stop all that stuff, and leave it up to you to do the forwarding you choose. Same goes in the NVR..it may have uPnP options as well.

Weird... thanks for the post.. might help someone googling for answers someday.

Where do you see that on the US site? I just see the listing "2xx2_Series_IP_Camera_Firmware_v5.2.0_140721 2014-07-21" ..but I've been fooled by Hikvision's web maze before.

Good stuff... It should work with no issues in Internet Explorer.. It might have been that you missed the plugin warning that pops up, or some security settings inhibited it.

It should prompt you to install the add-on (Plugin) called "Web Components". Then everything should work as you expect.

Yes that has everything to do with it. Get the plugin working, and the auto-saving should work as you make changes in the Image menu. I noticed it didn't work one day when I accessed the camera with a non-standard web browser on a linux laptop. If you're using a popular browser you should have no trouble. As telc said, it will automatically save with a "Save Succeeded" message at the bottom right as you make changes.

Managed or not it should have no bearing on IP used. As well, I have to assume he's using the LAN ports on the router to interconnect the PC and camera..which should also work fine.

There must be some fundamental thing missing here.. cause it really should be that simple. Both stations connected to the LAN ports, IPs set properly.. No idea what the problem is.. unless it's software related (like some crazy firewall thing going on). Interesting that the SADP program was able to communicate with it. And it isn't 'how routers work' .. it's really how *switches* work... IP won't make a diff to them. Not sure what you have going on.

The 4-port ethernet switch built into the back of the versalink OR the 8 port switch should have no issue with that. As long as both the PC and the camera are both connected to it. A normal switch doesn't care what IPs are being used on its ports.. it just cares about the lower level (layer 2) stuff. How did you end up getting in?