Soundy

So, your saying all I need to get a camera that will do the job I want it to is only going to set me back 18k. Sure, no problem......... just as soon as I cash in my Lotto ticket... let's see, where did I put that... hmmm its gotta be here somewhere... Avigilon's Pro-series cameras use a full 35mm sensor and Canon EF-mount lenses... 10k would get you into the super-telephoto L-series zooms, for sure, but you can certainly do much more cost-effective lenses

You got it, Pontiac!

Wow. I think I'd be sending that back to CNB and *insisting* on a replacement.

Ah yes, my bad... although I'd term it simply "peak voltage" (or maybe "zero to peak") rather than "peak to ground", since there is no ground reference on the secondary side of a transformer. In any case, the idea is the same: your average multimeter doesn't read "true RMS" and thus will often read higher than the rated RMS voltage.

"Starlight" cameras usually achieve the effect with extremely slow shutters... making them pretty much useless for anything where you have moving subjects.

Your quad balun plan should work nicely. You could also run a Cat5 from each camera to the common point, then connect the video pair from each camera to another pair on the homerun. Or you could use one of these: With one of these at each camera: Then run a single Cat5 from the VPS back to the head end, and connect to the DVR with a quad balun like this:

Keep in mind that if you're using a VBR (variable bitrate) codec, your stream is probably rarely going to actually be at that maximum rate. Depending on scene complexity, contrast, sharpness, movement, and a handful of other factors, it may only be a few kilobits at times, and unless all cameras are seeing movement all at once, your TOTAL bandwidth will be far less than the maximum you're planning for.

What was the resolution? That's a 14.6MP DSLR. Keep in mind with that though, you've got a dedicated 480Mbit connection to the system bus, going through USB... you're also not trying to record that stream... and I've never checked, but I suspect it's not actually sending the full 14.6MP image, but a scaled-down version - a single 14.6MP "fine" JPEG is probably about 5-6MB. Yeah, but you can also share lenses between your Avigilon and your 5DmkII

Gmail's SMTP requires encryption and auth. That DVR appears to support neither. OP: CONGRATS! Glad we could help

my ISP is orange. according to this website the smtp server is smtp.orangehome.co.uk. if i trace that in CMD i get the ip: 193.252.22.189 will this be the ip to use? Correct, that SHOULD work. Port is 25, unless your ISP specifies otherwise. Local address would normally be your address, although it can probably be just about anything. You should probably enter something at least resembling a real email address, as the SMTP server may reject it otherwise. He HAS to use the IP - the DVR setup doesn't give the option to enter a hostname (see screenshot above).

Unfortunately, you'll find almost all NVR/NAS solutions sell licenses on a per-camera basis. Figure they charge $150 per camera (fairly common)... nice as it would be to get a 16-camera setup for $800 (for only $50 per camera), would you want to pay the same $800 if you were just using a single camera? Per-camera licensing is really the most equitable scheme in most cases. Your other option is to build your own NVR and use the free software that many camera manufacturers provide (only for use with their own cameras, of course).

One type of video+power baluns I'm using put the video on wires 1+2 (which with T568B means orange), then one side of power on 3/4/5 (green/white wire, and blue pair) and the other side on 6/7/8 (green wire, and brown pair). I know other people who do the stripes for one side and solids for the other, if they're wiring manually. One pair for video... the others, it really shouldn't matter how you do it.

Are these cameras only dying temporarily, or permanently? Have any of them gone back to CNB to see if they can determine what is actually failing in them? Is it possible power is getting fed into the video output? How are they wired - are you using coax, or UTP+baluns? If the latter, are you terminating in keystones? I've seen a particular keystone design that allowed wire ends to touch and fried a couple cameras when they got full PoE power fed into the NIC.

Electrical braking at its simplest form would be a very low-resistance load across the generator, which would naturally get VERY warm. If they got really hard-core into it, they'd apply a reverse voltage to it (or reverse-phase voltage, if it's an alternator), but I doubt they'd be set up for that in most cases, as you'd need a source of the "braking" power.

Sure it's silly, but you never know... designers do silly things all the time

Maybe they're not variable-pitch design?

I love that feature of the IQs. Haven't come across another brand yet that does it.

Even your 14MP DSLR will only do 1080p video (of those that do video). How fast can you shoot, continuously? My Canon 40D (using JPEG-Fine at full res) will do 6fps for a few seconds, but has to stop to clear the buffer after that. Fact is, getting steady video out requires a very different design philosophy than snapping a series of stills. It has to be optimized for various transport methods, efficiency of storage, constant streaming without buffering... think of how fast you'd fill up your SD card shooting 14MP images at 30fps (IF your camera could handle it).

I would start with learning the foundations of IP addressing - subnets, network masks, DHCP, port routing, etc. That will take care of 99% of your installation concerns. From there you can move to more in-depth topics like QoS, VLAN, etc., as well as more general ethernet topics like layer 2 control, PoE, and so forth. Most of these things, you'll probably almost never need.

That diagram is incorrect for T568A. T568A is the same layout as T568B, except the orange and green pairs are reveresed: That aside, there should be no worry about interference regardless of which pairs you use for video and power.

Pretty much all email systems except Exchange use SMTP to accept email from clients. You'll want to find the SMTP server IP for the ISP you're connected through, and enter that - for example, if the internet connection is through Comcast Cable, you'd want to use Comcast's SMTP server.

Transformer is an Android tablet, not PC; it won't run Windows. Just something to keep in mind...

^That other thread pretty much covers it. Keep in mind that when CCTV camera marketing says "night vision", they're NOT talking about the military technology... they're just talking about a camera with built-in IR LEDs. In that context, there really is no difference between "night vision" vs. "IR sensitive" cameras; it's just different marketing terms for the same thing.

You need an RF modulator for that... and it will have to be one that can modulate the signal to a channel that the cable company doesn't use (many cable companies will have a "blank" channel designated for this purpose). It will also depend on whether you have an analog or all-digital cable system.

Hi Soundy, It seems that Vigil software is just proprietary for 3XLogic hardware, am I right? We need software that work with TRUEN IP camera. Technically, it's proprietary to their capture cards (although I've installed it on a machine using a VideoInsight card that's the same hardware as the Vigil card), but it will work with a wide list of IP cameras. I don't know about TRUEN specifically, but it does have ONVIF support, as well as generic RTSP and HTTP support that will let you enter your own URL strings, so it should work with a number of unlisted cameras.