survtech

External drives being standard drives in an external case, the answer should be obvious.

One word: NO. When ONVIF can get its collective head out of its a$$, I might consider changing that answer to "maybe".

thewireguys, It is OEM'd from Dynacolor - DynaTester DT-1. Also available as the Axis T8414 and the Siqura Multifunction Monitor Handheld Camera Setup Monitor, although the Axis T8414's firmware is crippled; limited to just Axis cameras (the Siqura is probably similarly crippled). There might be other brands OEM'd too. Also, we haven't found remote zoom/focus to be necessarily a good thing. Since all remote zoom/focus cameras start out fully wide, it is impossible to get critical aim proper. We found we had to aim, zoom/focus, them aim again at least twice to get the FOV's we want on critical scenes like table games and the faces of slot machines. Our aim tolerance can be as little as +/- 2" to 3" for many of our applications. One caveat on the Dynacolor / razberi: it is apparently not capable of accessing the camera's menus so with remote aim/focus cameras, one would still need a computer hooked up somewhere in the chain, making the tool somewhat useless in that case. In its favor, it can digitally zoom MP images so an installer could use it in conjunction with manual lenses, assuming it can obtain video from the camera. It did show video from the Axis P3364 and P3384 test cameras, just not any other tested brands (Ganz, IndigoVision and Dallmeier).

We just tested the razberi IT-5000 (http://www.razberi.net/products/accessories/it-5000/). It has some nice features but some pretty severe shortcomings: 1. First, the package contains a "razberi Utilities" disk that is unreadable (tried in 3 different computers). 2. The list of supported IP cameras contains some recognizable names, like Axis, Arecont and ACTi, but some real oddballs: autoIP, DIVA Protocol, e-vidence, Level One, OpenEye and Safety Vision while missing some very common cameras like Ganz and Mobotix. 3. The menus are difficult to navigate. Even the selection list of cameras is buried in only one of 3 camera menus and that's hidden if you have the keyboard popped up. 4. I have yet to get it to connect to any camera with ONVIF selected. That theoretically should work with the three camera brands we've tested that are not on razberi's list, since all three manufacturers swear their cameras are ONVIF-compliant. 5. On battery power for POE, it shuts off POE after a maximum of 60 seconds. Almost every camera we have tested won't even boot up in much less than that (and some take much longer). So by the time the camera should be ready to aim/focus, etc., it loses power and the installer has to start from scratch. This is apparently not a problem if you insert the IT-5000 into a POE line but the installer has to get that done first. Supported IP cameras: ACTi Arecont Vision autoIP AXIS D-Link DVTel DynaColor Diva Protocol e-vidence GE IQinVision Level One ONVIF OpenEye Optelecom-NKF Panasonic Planet Safety Vision Sanyo Sony VivoTek We are returning it after talking to a razberi tech rep. Next, we might try the ToteVision MD1001 in conjunction with a Veracity Pointsource pictured above by tomcctv (http://www.totevision.com/catalog/lcd-monitors/mobile-devices). The main issues with laptops and the like are their weight and bulkiness and their fragility. Have fun standing on top of a ladder trying to juggle a laptop or notebook and the camera while holding on with ???

Jomadav, we use other means to test monitors (NTSC color bars and actual camera signals). The LCD-565KIT includes a carry case that folds out to become a hood that blocks ambient light. It resolves most of the glare issues.

USB 3.0 solves the speed problem, as does eSATA.

3.5" is a bit small to obtain good focus. We use the ToteVision LCD-565KIT 5.6" monitor. http://www.totevision.com/catalog/lcd-monitors/4-6-monitors/lcd-565kit-desk-wall-hot-shoe-bracket-field-monitors

That device is 24VDC to 12VDC. Typical camera power supplies are either 12VDC or 24VAC. To convert 24VAC to 12VDC, use any of the Altronix VB/VR products except the VR3T. http://www.altronix.com/products/index.php# - click on "Power Conversion Modules". VR1- Converts 24VAC or 24VDC to a 12VDC @ 1 amp. Modular Connector/Cable Assembly. VR1T- Converts 24VAC or 24VDC to a 12VDC @ 1 amp. Screw Terminals. VR2T- Converts 24VAC or 24VDC to a 12VDC @ .5 amp. Screw Terminals. VR5T- Converts 24VAC or 24VDC to a 12VDC @ 3A.

Most likely the dome drive's power supply. You probably need to replace it - Part Number: DD53KIT, Description: Power Supply Kit, Pelco Spectra III, Price: $169.63. http://www.timelapsesupply.com/pelcospectraiii.html

A proper lens is the best solution. Assuming both lenses are DC auto-iris, the 3 vs. 4 wire construction could be just that one company ties the (Control -) wire to the (Drive -) wire together internally but there's also the possibility that one lens is DC Drive (the most common type), while the other lens is Video Drive. DC Drive lenses typically have 4 wires while Video Drive lenses typically have 3 wires. The two types are not interchangeable.

I agree with ilk. RS422/485 is not designed for star distribution. It is possible to use a code distribution unit, like Pelco's CDU-T or GE Security's Kalatel KTD-83 at the hub but if you just tie multiple control lines to one port, you are likely to run into control problems. Daisy-chaining multiple PTZs is always an option. Common practice is to only terminate the device at the end of the chain while leaving devices in the middle of the chain unterminated but I've found that you can terminate up to at least three devices in a daisy chain with no effect on operation. Although the resulting termination would be 33 ohms (100/3), RS422 drivers have no problem handling the increased load. The problem with only terminating the end of the chain is that if the end device is removed, there would be no termination; which can cause control signals to reflect up and down the line and interfere with proper operation.

Simple enough. One matrix bay = one CC1 port. Try attaching a VGA monitor to the CC1, reboot the matrix bay and the CC1 and watch what happens on the monitor as you switch camera-to-monitor assignments. The blocks should change. You'll also be able to see many types of system errors on the display as the system boots up. If it takes an inordinate amount of time to start running, look at what the display "hangs" on and post your results here.

They are, as I recall, comma-delimited text files but there are so many columns it's hard to translate what's what. You're better off getting the manager program from Pelco, copying the flat files from the CC1 to a floppy and importing them into the manager program. You can then see how things are connected and make any modifications you want, then re-copy them back to the CC1 if you make any changes. You need to know what software version you're running before you contact Pelco. How many matrix bays are in your system and what's the configuration (inputs and outputs)?

Newer versions of the Pelco software are less critical but I believe the matrix bay(s) typically go on the first Sercom port(s) in number, followed by keyboards and then auxilliary products like MDAs, Multiplexers, etc and the highest ports are for PTZs. It all depends on how the flat files were programmed.

What the cameras connect to. Although my best guess is that the control signals are not getting from the CC1 to the matrix bay, either because you have a bad ribbon serial cable or because the wrong port is connected to the bay or there is something wrong with the Sercom port. By the way, did you try rebooting the matrix bay? Turn it off and on.

It should work for 125'. Do you have the polarity (+ to + and - to -) and all other settings, including address and protocol correct?

For relatively short runs, 18/2 should work. In fact, many other cable types can work, including shielded 22/2, CAT3 and even zip cord. However any cable that either has other than 100 ohm impedance or relatively few twists per foot will likely limit the distance control signals can be reliably transmitted. RS422/485 can travel up to 4,000 feet on proper cable but improper cable will substantially shorten that maximum distance.

Are you selecting the monitor first, ie: 1 20 Other than that, it sounds like either the CC1 has lost communication with the matrix bay (double check the serial cables and make certain they are connected to the proper Sercom ports on the CC1) or there is a problem with the cross-point switching (the input cards).

Even so-called voltage regulators, such as the 7812, are basically resistive and would have to dissipate a huge amount of power.

Not if the supply is (a) adequate, and (b) regulated. Note I specified a voltage converter at the camera end; the camera is not being supplied directly by the line voltage. Higher line voltage reduces the current, so reducing voltage drop, and regulating at the camera prevents any fluctuation in line voltage affecting the camera. So, you're suggesting feeding 50 Volts and regulating that to 12 Volts at the camera end? First, that "fix" goes beyond Class 2, which is limited to 24 Volts, so theoretically it requires an electrician to wire (almost as flaky an idea as running an extension cord to the camera). Second, 50 Volt power supplies are not that easy to find, nor are suitable DC-to-DC converters. And forget any other kind than switching. Non-switching voltage regulators dissipate the voltage drop as heat. Even assuming a 20 Volt loss in the cable, you still have to dissipate 28 Volts times 4 Amps (approximate) or over 100 Watts.

I agree with the toss but would also add that the IR LEDs also are probably not "On" during the daylight so now you have two variables that will affect the voltage drop: motor current draw during pan/tilt operations and LED current draw at night. Although Zmodo's specs are unclear on this, I would guess that quiescent power requirements (daytime, no movement) would be under 1 amp while nighttime movement would draw up to 5 amps. Therein lies your problem. If you kick up the supply voltage to account for the voltage drop at 5 amps, you will likely fry the camera during daytime no load conditions and if you keep the supply voltage low enough during daytime no-movement to prevent over-voltage, the voltage at night under movement would be too low to power the camera. One way around the problem would be to use a heavy gauge power wire but even 12 gauge wire would drop 4 volts over 250 feet at 5 amps. 12 gauge wire is 0.1588 ohms per 100 feet and both positive and negative wires of the pair would have an equal drop so .1588 x 2.5 x 2 = .794 ohms x 5 Amps = 3.97 volts drop across the power cable under full load. 10 gauge wire would have a resistance of .25 ohms per 250 feet (.5 ohms total), which would drop the voltage 2 volts at 5A vs. 0.5V at 1A. That might be sufficient, depending on the voltage tolerance of the PTZ, but it's still a 12.5% swing. Wire thicker than 10 gauge would solve the problem but is very difficult to find. You're best to power the camera from a nearby source or consider a 24VAC PTZ or one without IR (which probably takes the majority of the power). A Pelco Spectra IV, for example, only uses ~ 1 Amp max without heater/blower at 24VAC. 250 feet would be a breeze with 18 gauge, or perhaps 14 gauge with heater.

Standard or not, Todd has chased enough manufacturers away from the HDcctv Alliance to make HD-SDI a viable alternative. Yes, interoperability is not guaranteed between HD-SDI manufacturers and their products but since both HD-SDI and HDcctv utilize the same chipsets, I wouldn't be too concerned deploying HD-SDI.

3,500 feet is pushing it for CAT5/CAT6. For that distance, you should use active/active, not baluns. The alternative would be fiber, which is much more difficult (and expensive) to work with.

Not terribly useful for IP.

Analog (baseband) video is not 5 or 6 MHz. It consists of a range of frequencies from around 25/30Hz to 5 or 6 MHz. 25/30Hz is also the frequency of the vertical sync pulse of analog video. With analog video, there are two distinct loss factors: low frequency attenuation and high frequency attenuation. Both are affected by length and cable design. Low frequencies (primarily sync signals) are attenuated by (the essentially DC) cable resistance. In order of highest resistance to lowest: "mini coax", RG59, RG6 and RG11. Put an oscilloscope on a long piece of cable and compare sync pulse shape to the source. You will see that the longer the cable and the higher the resistance (a function of cable diameter and material) the poorer the sync pulse shape becomes. At a certain point, the receiving end will not be able to synchronize the frames. That will happen at a shorter distance with RG59 than with RG6. The low frequency losses will also affect the lower frequency video; causing smearing of the images. Yes, high frequencies can also be attenuated by the cable. In particular, by cable capacitance. The longer the cable, the higher the overall capacitance, thus the larger attenuation of high frequencies. The color burst, at 3.58MHz (4.43MHz PAL) is among the high frequencies that get attenuated by cable capacitance. When the color burst gets sufficiently attenuated, colors become washed out and a monitor may only display black and white images. In short RG6 (assuming all else is equal), with a larger diameter center conductor, will have lower attenuation per foot at low frequencies. Also note that each type (MiniMax, (which equals RG179), RG59, RG6 and RG11) has the same capacitance (16.2pf) per foot, so high frequency attenuation should be the same. Therefor, the only difference between types is the DC resistance. Perhaps you could explain how the progressively larger cable sizes can carry video for longer distances without it depending on the DC resistance? RG179 = 30Ω/k - 500 feet max distance RG59 = 10.1Ω/k - 1,200 feet max distance RG6 = 6.5Ω/k - 1,800 feet max distance RG11 = 2.6Ω/k - 2,200 feet max distance FYI, Here's a link to a nice CCTV cable reference. Note the maximum distances for each cable type.: West Penn Wire - Security - CCTV Product Line