GrouchoBoucho

having to drill oversize holes to fit pre-made ends is a pain, but remember, the hole doesn't have to fit *all* of them through at the same time; it only has to fit all but one of the cables, and the last end that said, kawboy is right, somewhere like a soffit is the best idea, as that's usually easiest to repair/replace later, and doesn't piece the envelope of the building. if you do have to go through a wall, look at mounting a suitably-sized weatherproof junction box over the hole, and run the cables out the *bottom* of the box. this will prevent water from running along the cables and through the wall. use a good outdoor silicone caulk to seal the box against the wall. also, if you're drilling through a wall, always angle the hole slightly upward from the outside to the inside, so water can't run *down* into the house.

I thought of that, but did not suggest it. There is no guarantee this camera will be checked regularly. A 64GB card may be recorded over every 14-34 hours, depending on the resolution. It will not help find out who dumped the trash several days (or weeks!) ago. horsehockey. configure proper motion detection, don't run everything at maximum quality, and you should be able to get anywhere from days to months on a 64gb card.

drop a pm to user named 'hiddenmountain', he's done something exactly like this and has plenty of experience with what you're trying to do. check out these posts

with poe, all you need to know about volts/amps/watts is that the maximum wattage rating of the camera doesn't exceed the power available on its switch or injector port. everything except the ptz is well within 802.11af spec, which calls for up to 15.4w/channel. since you're building from scratch, forget the injector - these are useful if there's an existing switch that you want to use, but in your case, a poe switch will be far easier, and probably cheaper. just make sure you use one that supports the full 15.4w on *all* ports, to account for the 10w cameras (cheaper ones will do full power on half the ports, or half-power (7.5w) on all ports). cisco's small business line are some excellent, robust switches for a decent price. the only other concern is the ptz; this can be powered off a 24vac adapter. anything rated 40va or above will suffice.

your poe switch goes at one end of the 1300' pipe, your nvr at the other end... connect the two ends via fiber. no. ip cameras can send video anywhere in the world... but you need to build the network properly. *ethernet* is limited to 100m (approx 328') per segment. fiber is probably your best bet in this case; wireless won't give nearly enough bandwidth and will be highly unreliable unless you have unobstructed line-of-sight. remember that the camera isn't "sending video" as such; it's encoding the video into network data. anywhere you can send the data, you can send the video. it can go over 3g (cellular), over the internet, over fiber, using dsl, etc. but fourteen 2mp cameras will potentially generate a *lot* of data, so the network connecting them to the dvr has to be able to handle that traffic.

the power wires are too small. at that distance, you're getting too much voltage loss once the ir turns on and the current draw increases. best solution is to ditch the crap system completely. workaround solution is to run a separate 18/2 power wire to each camera.

[quote="marvincctv"]Hi DC12V is one very low voltage. With our test result. If the DC12V is powered with net cable, the longest distance only can touch 8 meters. If longer, the camera won't work for the outpu voltage already lower than 6 voltage. 50 meters is also one long distance for RS485 communication. RS485 is voltage signal from 4V to 9V. Marin [/quote] i think you're in the wrong line of work. this information is so wrong, it's beyond laughable.

ummm, just about all of them will do all that.

any dvr that has a 12v power adapter can run directly off a car battery.

your assumption is wrong - every dashcam i've seen cycles storage, continuously overwriting the oldest video. most use sd or micro-sd cards, which you can get in up to 32gb with sdhc spec, and 2tb with sdxc (make sure the specific camera supports these specs). sd cards *are* generally removable - not "self contained".

i don't use or recommend wireless for video. period. your original post said you wanted to run from the dvr to *two* tvs. two does not constitute "many". there's *always* a way. your original request said nothing about sharing with the neighbors - your wanted to run to *two* tvs in your own house. i wouldn't really call that a success... "o hai neighbor, sorry about f***ing up your wifi, but look, you can view my cameras now!"

that is sure a *lot* of screwing around just to save a few bucks. first of all... almost all ip cameras support poe, cheap ones included. you can also put a poe "splitter" at the camera end to break out dc stepped down to 5v, 9v 12v, etc. for devices that don't do poe. second... what is your time worth? how much time have you spent now trying to figure this out, sort out your voltage losses, etc., when you could have just used a poe switch or injector and been done with it? and what is the cost of that vs. simply using poe injectors? poe injectors can be had for under $50: http://dx.com/s/poe+injector - i've seen them as low as $15 elsewhere. this one will do two cameras for under $44 (or $22/camera): http://dx.com/p/48v-500ma-dual-port-48w-power-over-ethernet-poe-adapter-black-115419. this one is barely over $20: http://www.amazon.com/TP-Link-AC-TL-PoE150S-PoE-Injector/dp/B003CFATQU/ref=sr_1_4?ie=UTF8&qid=1361951891&sr=8-4&keywords=poe+switch or for under $60, you can get an 8-port switch with four poe ports: http://www.amazon.com/TRENDnet-8-Port-100Mbps-Switch-TPE-S44/dp/B000QYEN1W/ref=sr_1_1?ie=UTF8&qid=1361951891&sr=8-1&keywords=poe+switch or you can keep wracking your brain trying to figure out why your hack job doesn't work.

that's a lotta money to waste just to avoid pulling a wire.

i still haven't seen anyone address your other point at the very top of the thread, and is, what vms's would even support the sdi-to-ip encoders? it's all well and good that you could drop a couple grand to convert your sdi cameras to ip, but it doesn't do much good if you don't have a vms or nvr that can record that stream.

that's amazing - you can tell from those pictures that that pc "isn't up to the job"??

without knowing more about the dvrs (brand, model, version, etc.) it's impossible for anyone to tell you what their capabilities are.

the card looks like a geovision, although it's hard to say if it's a legit card, as the proper ones will usually have a hologram sticker and a serial number on them. assuming it's a legit gv card, you should be able to contact geovision to request the latest software (drivers included), but you will have to provide the serial number. if there's no serial sticker, there's a good chance it's a 'grey market' geovision knock-off - good luck ever getting it to work properly.

cameras will not *stop* prowlers, and only *may* deter them. a better deterrent is to add some motion lighting so the bright lights coming on makes it hard for them to hide. if there's nothing else around at night to trigger falses, you could even rig an alarm siren to the light as a further deterrent.

you could also use a nas that has built-in nvr application, like synology or qnap.

yeah, that's a great idea - instead of picking the proper camera for any given usage, always use the same brand as your vms. might as well go back to a f**king costco package system with proprietary connectors. you know, there's one major vms i work with (which shall remain nameless) that has their own brand of cameras as well - well, they're actually oem'd from a well-known asian name - and they're horrid in every regard. pita to install, pita to configure... firmware updates not only break integration, they also sometimes break the setup utility. at least twice i've been sent to site with a new model of camera and found the version of the setup tool i had wouldn't work properly with it. 'always use the same brand vms and cameras' - what a cop-out.

you should do a big favor for the avigilon boosters, and avoid it as well. i foresee the first time some third-rate camera manufacturer updates firmware and breaks avigilon support, you'll be in here ranting in big letters that avigilon should have seen it coming and prepared for it months in advance. i just imagine the tear you'll go on when they don't dedicate every resource they have to fixing the problem within minutes. avigilon fanbois, you may mark my words. some people will never be satisfied.

a single 32-channel recorder with sufficient storage is all you need. all cameras record separately, so whatever resolution you tell them to record at, they will continue to record at regardless of how you're viewing them.

try stringing a piece of cat5e across the ground and connect it up, see if that solves your problem... if so, at least you know what it is, even if it's a pain to deal with. if not, then you can rule out that it's the type of cable. doubling up pairs won't help - there should be one pair per balun.

u jelly bro?

sounds like cross-talk between the pairs. i'd suggesting using cat5e instead of this 10-pair; the pairs have different twists so you don't get signals induced into adjacent wires.