Specs for Home Built NVR - All IP

[n2glox 0]

I am in the process of starting up some security cameras. I need to start with indoors and will expand to outdoors as time goes on. I want IP cameras. Some will be wired, some will be Wireless. I am looking for tips on how to spec out a PC that I want to build to handle the recording.

 

First some questions. I currently have part of my house wired with Gigabit Ethernet. Cat5e. I have spots left on my Switch and I have a wireless AP for 802.11 G. Should I allow the wired cameras (through the POE) go straight into my Switch? or Should I route those drops to a separate switch. I could also create a separate Wireless AP to help. I want to make certain that my current Wired Gigabit ethernet is not going to be slowed.

 

I am looking AXIS cameras, I like the 207W and the wired version of that camera Pretty good bang for the buck with an indoor installation with good lighting. I would prefer a low profile camera that had a wider angle. I want to set up 5. I want my NVR to be able to handle 6 to start with and expandable if I decide to later. I want to get a software package that will record and detect motion. I think the software packages do better than motion detecting on the camera,

 

So What Specs do I need. Any guides here on building one? I figure a dual core or quad (probably the later). 2gb to 4gb of memory. 1tb hard drive. Any add on cards? What about graphics cards? Can I go AMD?

 

Thanks

 

jeff

[akelley 0]

Suggestions on the network is to separate camera traffic from regular traffic if possible. You can do this physically (two separate switches) or virtual (VLAN - a single switch creates the VLAN for the specified physical ports on the switch). This will allow you to better manage your camera traffic and provide scaleability as you need. Also, I wouldn't suggest using wireless for MP cameras - you'll saturate the wireless signal quickly and you run the risk of having someone accessing your camera feeds remotely (from outside your network), if you're not careful on how you setup encryption, etc. Also keep in mind that all cameras being recorded to the NVR will be streaming their signal continuously (even if it's not recording - the software has to analyze the image to detect motion, for example, to know to begin recording), so be sure to get switches that are robust enough to handle this continuous data stream - some of your cheaper consumer brands/models are not designed for this level or service. Commercial quality switches with POE can get costly (you can sometimes save money by using switches without POE, and use POE injectors for your cameras, but then you've introduced another point of failure into the system).

 

You should first consider the software NVR you're going to use to determine the specs for your server. Some require a good deal of horse power (CPU) whiles others do not. It will also depend on the cameras you ultimately choose (h.264 requires more CPU to encode/decode), and obviously the number of cameras you intend to record (and you may want to spec a system that will allow you to add one or two more cameras with little or no modifications to the system). Hard drives are also important to consider in both size and duty rating. One, how much space will you need? This can be calculated by number of cameras x storage requirement (see camera spec) x frequency (days per week, 24/7, frames per second, event only, etc.). Two, spec server rated drives - that is drives that are intended to run 24/7. Most consumer model drives are not rated for this and can have high failure rates when pushed to run 24/7x365. Though I've found that you can save a little money over the server drives by looking for hard drives that are designed for DVRs (like Tivo or your cable DVR box) - these are designed to run 24x7x365.

 

I'm sure there are other tips out there, but hope this helps.

[n2glox 0]

Suggestions on the network is to separate camera traffic from regular traffic if possible. You can do this physically (two separate switches) or virtual (VLAN - a single switch creates the VLAN for the specified physical ports on the switch). This will allow you to better manage your camera traffic and provide scaleability as you need.

 

I like this idea. I sort of wondered. I can probably do this for reasonable costs. Most of the wires are run and can be moved to another switch and a wireless router.

 

Also, I wouldn't suggest using wireless for MP cameras - you'll saturate the wireless signal quickly and you run the risk of having someone accessing your camera feeds remotely (from outside your network), if you're not careful on how you setup encryption, etc.

 

There are places I need cameras and I cannot fish cable. Vaulted Ceilings or no Attic Access. I am comfortable with WPA2. My current system is locked down with MAC Addresses and WPA2.

 

 

Also keep in mind that all cameras being recorded to the NVR will be streaming their signal continuously (even if it's not recording - the software has to analyze the image to detect motion, for example, to know to begin recording), so be sure to get switches that are robust enough to handle this continuous data stream - some of your cheaper consumer brands/models are not designed for this level or service. Commercial quality switches with POE can get costly (you can sometimes save money by using switches without POE, and use POE injectors for your cameras, but then you've introduced another point of failure into the system).

 

Good points

 

You should first consider the software NVR you're going to use to determine the specs for your server. Some require a good deal of horse power (CPU) whiles others do not. It will also depend on the cameras you ultimately choose (h.264 requires more CPU to encode/decode), and obviously the number of cameras you intend to record (and you may want to spec a system that will allow you to add one or two more cameras with little or no modifications to the system). Hard drives are also important to consider in both size and duty rating. One, how much space will you need? This can be calculated by number of cameras x storage requirement (see camera spec) x frequency (days per week, 24/7, frames per second, event only, etc.). Two, spec server rated drives - that is drives that are intended to run 24/7. Most consumer model drives are not rated for this and can have high failure rates when pushed to run 24/7x365. Though I've found that you can save a little money over the server drives by looking for hard drives that are designed for DVRs (like Tivo or your cable DVR box) - these are designed to run 24x7x365.

 

I'm sure there are other tips out there, but hope this helps.

 

Any suggestions on software? I don't want to spend too much on software. I want basic recording with motion, and the ability to upload (FTP) MJPEGS or something similar. I am willing to look at SVGA rather than Megapixel.

 

I need low profile indoor cameras that can give reasonable views at up to 30 feet. Preferably wide angle. Filming will be about 12 hours per day, less for some rooms. One room may run 24/7. I do not need to see 12 pt text, but facial view would be nice.

Thanks

[akelley 0]

Milestone (http://www.milestonesys.com) is one of the better commercial software NVRs. They used to be quite expensive but have recently released significantly lower priced versions of their product for the consumer and small business. I believe they even have a free version with limited features which may be just what you need. Check out their website for more info. Also, LuxRiot gets good reviews for a lower priced alternative to the more expensive commercial products like Milestone or exacqVision. And keep in mind that there are many authorized resellers of these products in this form that can give you much better info and provide pricing info as well. Ask around.

 

Search the forum here as there are plenty of recommendations and reviews of both cameras and NVR solutions.

[buellwinkle 0]

For a home setup, I use BlueIris and don't let the $50 price fool you, it's perfect for home use and remote access through it's web server. One thing I like that's cool is that you can turn recording on/off with a traffic light icon. When you turn it on, it gives you a few minutes to get out of the house, that way you don't end up with a bunch of alerts and recordings of you leaving the house.

 

As far as cameras, VGA cameras are cute, but you can do better. I replaced my low end Axis with low end ACTi cube and you get more bang for the buck, 4 times the resolution, better dim light performance, PIR motion detect on the newer models, interchangeable CS mount lenses. Cost is comperable to the low end Axis, maybe a little more. The cube cams start with the ACM-4201 and go up to their higher end TCM line. Just understand that these Axis and ACTi cams are "day" cameras, meaning that you need white light at night to see anything. You can not use IR illuminators. I was thinking of upgrading my indoor ACTi cam to the 3511 because it has day/night capability and built in IR illuminators.