Soundy

Not exactly. There will be one IP address for the DVR. You cannot connect directly to the cameras; your remote software will be connecting only to the DVR. Incorrect (disclaimer - I'm not familiar with that SPECIFIC DVR, but I'm betting that it works the same as 99% of them out there). Whoever logs in SHOULD have the ability to view any combination of cameras they choose, search recorded video, and if the account gives them permission, access the settings. They will not simply see a copy of your DVR's local display screen; the DVR is taking the digitized video and streaming it back out over the network. Normally you'd be able to create different user accounts with different levels of access - ability to see live video, but not recorded video, and so on. IF the DVR supports the ability to control camera access by account, then you can set up accounts that are only able to display a single camera (or a specific 2 or 3 cameras, if you prefer).

At a guess, I'd say you'd need to create eight separate user account and passwords, and give each account access to only the one desired camera.

If you open it up, there may be a "reset" jumper that will clear all settings, that MIGHT get it back running (wouldn't hold my breath though). Would probably look something like this: You could try looking for an "FCC ID" number silk-screen or stamped on the mainboard - if you can find that, you should be able to look up the manufacturer at the FCC's website (www.fcc.gov). It will probably look something like this (below the sticker): Are there any other labels on the outside of the case at all?

GeoVision cameras are made by someone else and re-branded with the GV name. Couldn't tell you who offhand, but it has been discussed here before. Synology's Surveillance Station package (I have a DS412+) does have some capability to enter custom camera settings, so if you can find the proper URL, you might be able to make it work that way too.

Theoretically, yes. It will depend in large part on the NVR itself, and whether it will let you select generic cameras and define custom URLs.

It normally does... you might want to check your own settings and see if you disabled it inadvertently.

Wow, that was so clever...

kinda defeats the whole point of 940nm doesn`t it .. Physics is a ***.

I think the problem is obvious: if it's not an Avigilon Pro camera with Canon L-series lens, it's a complete waste of money. If you're not spending $15,000+ per camera location, it's just not worth bothering.

You should be able to connect your camera directly to the RS-232 serial port(s).

How would this be worse than spending $500+ on a high-end analog camera that wouldn't let you ID the person either?

Camera sensors are sensitive to IR, which is why it works in the first place... however, the sensitivity drops off sharply not far into the IR range. The longer the wavelength, the less visible the LEDs, the less effective and efficient it is, unless you get into more specialized, and more expensive sensors. The longer-wavelength IR LEDs tend to cost more as well - not a big deal if you're talking about one or two in a remote... adds up fast if you're talking a couple dozen in a camera.

That's a lot of extra cost when it's probably not warranted... I dunno about where you are, but retail on a 1000' box of Cat5e Riser around here is <$100... Plenum-rated is almost $300.

That's an F-connector, common for cable-TV and satellite, not so common for cameras. If it does indeed go to a camera, you'll probably first need an F-to-BNC or F-to-RCA adapter to be able to connect it to a capture device.

Can you post a picture of it? I have a feeling it's still a BNC, maybe just not properly assembled. Either way, you need a capture device or network encoder to do anything with the signal...

Taking a look at the Mobotix S14 - looks pretty nice, may be ideal for a particular job I have in mind, especially with the hemispheric view. Checked the Axis P85xx as well, but the form factor isn't ideal. Wondering what else new is out there?? Doesn't even need to be MP, necessarily.

BCS? Or BNC? Does it look like this? If so, you need either some sort of video capture device to connect it to the computer (USB adapter, DVR card, tuner card, etc.), or an IP encoder to share it directly on the network.

If he has a monitored alarm system, it's likely that they used a relay output on the DVR to trigger an input on the alarm...

Actually, that's the problem: standard color cameras DO have IR cut filters (that's what they do: cut out the IR). TDN cameras have *removable* IR cut filters to allow the IR in when they switch to night/B&W mode, which is why they work with illuminators.

Netbook and a wireless router plugged into the camera network. If it's just one or two cams and they're powered with 12/24V, a crossover cable and plug the netbook in directly. Or if they're PoE powered, something like a Veracity PinPoint or similar device works.

Impossible from that picture - you have at least two different models of PTZs, but they could be almost anything inside those housings. You want to ID them, you'll need to open them up and look for identifying marks - brand, model, serial, etc.

Yeah, too bad you can't tell anyone about it... no good deed goes unpunished, after all.

Pretty much all analog PTZ cameras will inherently have RS-232/422/485 support - be difficult to control them remotely otherwise. RS-485 is just the electrical interface used; where you run into compatibility problems can be in the protocols "spoken" - Pelco D, Pelco P, etc. Fortunately almost all cameras AND DVRs support Pelco D/P in addition to their own - kind of a "universal" language.

Correct. And technically, you don't NEED a default gateway to communicate within the LAN - that's only required if you need the camera to communicate with another network. You'd normally use it if you need the cameras to sync to an NTP server, send email, etc (in which case you normally need a DNS entry as well). Normally, no. The only time you'd need to do this is to allow outside access to each camera... and most routers should also allow you to forward different outside ports to the same port on different internal addresses... for example, the router could forward port 81 from incoming connections, to port 80 on 192.168.1.81. Where it gets tricky is if the cameras use a separate data port (554, 8000, or 37777 are common) - that WOULD have to be set different for each camera, and forwarded individually in the router. That can turn into a hassle to configure and a logistical PITA to maintain, with this many cameras. A better solution would be to use a router that can act as a VPN server (or a third-party firmware like DD-WRT), so you set up a VPN client on your remote system that then connects in and essentially becomes another machine on the same LAN, allowing you direct access to each camera. Port forwarding is not done on the switches; it would be on the router that connects this network to the internet.

First thing to remember is that edited video is useless in court...