Owain

ANPR (automatic number plate recognition) and affordable tend not to go together.

You could try the Neighbours From Hell forum. http://www.nfh.org.uk/ I would strongly advise against publishing your recordings in any way. It could jeopardise a future prosecution and in any neighbour dispute you want to ensure that you appear as the aggrieved innocent party.

Yes. 48V / 50V is only the same voltage as telephone lines, and lower than some PoE implementations. Took me about two minutes to find a nice selection on ebay.com eg http://www.ebay.com/itm/110960049789 http://www.ebay.com/itm/300452160874 DC-DC converters about £10 each if you go to Ebay China. Twenty bucks US. http://www.ebay.com/itm/261147745875 If the cameras are in clusters, one per camera might not be needed. You're right, it would be switched mode converters. I wasn't thinking of dropper resistors.

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.

The baluns make no difference to the power, which is just a straight through connection. Voltage drop is dependent on the current, for the same power to reduce the current you will need to increase the voltage, so you could use a 50V telecom power supply and a DC-DC converter at the camera end to get back to 12V. Or use IP camera with power-over-IP which also uses a higher voltage than 12V. Or use heavier cable for the power. 2 x Cat5 would give you 7 pairs for power and 1 pair video.

Check the DM website downloads page, you may well find an updated version of Netview to install. I find that Netview takes about 10 minutes to start working - it may just be taking its time to get started on your computer, rather than "not working".

if you put a photo up, someone might recognise it.

for basic installation, cctv42.com on youtube

Okay postnatal. Prenatal video of the ickle bairn might be a bit OTT

I'd persevere with the RasPi as you've already got them. If you get a command not found error you probably have to install the relevant package first. RasPi forums should be able to help on that.

2 x IP desk phones set to work back-to-back with auto-answer. Or use one (or 2) Rapsberry Pi http://mattkaar.com/blog/2012/12/01/raspberry-pi-as-a-baby-monitor/

could you handle the audio separately using an IP speakerphone, set to auto-answer when you call it over SIP. They're available quite cheaply if you get an ebay auction bargain.

Vivotek FD7132 has external audio ports for both speak/listen. Not sure if it's Wireless G though. However any decent reseller should be able to put a camera online as a demonstration for you, including audio if you arrange a 'conference' at a certain time.

the problem is almost certainly infra red light from your camera reflecting back into the camera lens. Disable internal IR lighting and fit an external IR illuminator, or get a camera where the IR LEDs and the camera lens don't share the same front piece of glass.

I'm running on 4 fps - more than adequate for general household use as most subjects are fairly slow-moving.

The camera device itself will be an array of pixels. For an analogue camera, processing within the camera assembles these and generates an analogue composite video signal. For a cell phone, it's probable that the camera has no processing and passes the digital image directly to the phone's processing unit. There is thus no analogue signal to extract. Building your own circuit to do so would be synonymous with designing and building a PC graphics card, from scratch, without any documentation, and using discrete logic because the specialised chips are for manufacturers only.

it is quite likely the cellphone camera does not have an analogue signal anywhere but that the pixel image is mapped in memory directly into the phone's CPU.

your camera has to have a lights switch output, or you can use a separate relay controlled by the RS422/485. Something like http://www.bbvcctv.com/products/receivers/rx25x_multiple_protocol_auxiliary_relay_receiver/ A more DIY approach http://www.sigma-shop.com/category/17/rs485-relays.html

Does 192.168.0.106:2000 work any better?

Well, it is now you've said it, but you didn't say it before, so we didn't know exactly what settings you were using. And fault-finding is usually a process of systematic elminiation rather than inspired guesswork. Finally, other people may have a similar problem and read this forum months later, so it's useful to spell things out as they may not have taken all the steps you have. Does your DVR have, and can you connect to, its internal webserver by pointing a browser at the IP address on port 80? If you can't then the router or hub/switch is doing something with the IP.

you need to start with how you are going to magnify the image. Either analogue video with optical zoom, which will need a zoom lens and a controller, or a megapixel camera and do the zoom digitally. Zoom lenses, controller keyboards etc can get expensive and I'd be inclined to use digital. I'd suggest starting with a megapixel webcam as these are quite cheap, and seeing how you get on, or asking the people at networkwebcams as they're expeirenced with megapixel IP cameras. If the aim is magnification of print i.e. a 2-dimensional surface, then video magnifiers are already available, output to either TV, VGA or USB. I don't know how well they'd cope with 3D objects, and as with most things for 'the disabled' the prices are hiked. http://www.eschenbach.com/products-video-magnifiers-desktop.htm

Very likely the IP address of the DVR has changed. The DVR may have a setting for fixed IP address in its network setup. You will have to tell the client software on the PC to connect to the DVR using that new address. You could also check the router settings for client IP addresses (look for DHCP server settings) and if the DVR can only use a 'static IP' address you must exclude the address used by the DVR from the address block offered by the router for DHCP, so that nothing else can use the same IP address that the DVR has.

If a DVR is 4-camera then it should record all 4 cameras. If the DVR has an alarm relay output which is motion activated, OR if you use a PIR detector next to the camera, you can use that to apply a voltage to one of the TV SCART connectors, and the TV may then switch to that input. Not all TVs will autoswitch to SCART inputs. Pin 8: 5–8 V → on/16:9 9.5–12 V → on/4:3 Pin 14: Data Ground

Most modern analogue DVRs have network connections for remote viewing already. 1. There are IP-over-coax solutions, but usually you would install Cat 5/6 ethernet which can often carry the camera power as well. 2. Max length for ethernet will be about 300 ft; IP cameras use various flavours of Power-over-Ethernet and the distance depends on the PoE type and the camera. 3. Most cameras will use DHCP and get an IP address automatically, so just set up a DHCP server with the appropriate network address ranges. 4. IP cameras use IP over ethernet - it's all just packets. You will need to calculate network bandwidth, but many IP cameras can have on-board storage so you can view over the network in low res and store high res on the camera. Cameras will do periodic uploads to FTP server or NAS (which can be cloud based).

most cameras will be standard, 1 V composite video, powered on either 12 V dc or 24 V ac. So there should be no compatibility problems there. More important to get a capture card that will be recognised by your OS and software.