mkkoskin

To what kind of use is this LPR camera coming to? 40-50ft seems a bit long distance for normal LPR usage (LPR for gate control etc.). If possible, installing the camera closer would probably make the system way cheaper than it is with 40-50ft, i wouldnt personally install LPR camera more than ~15ft away from the plate in case of gate control or such.

If the details are accurate, then definitely the first link (Mcab), atleast they promise the 10/100/1000, the other cable only says 10/100. Even though cat5e should always work as 10/100/1000, i've came across cat5e cables that didn't.

Where do you see this green screen? Browser? Some NVR/VMS software? When do you see it, when the camera is moved? When there is movement on the camera? On "still" image? Totally random? What kind of setup do you have? I've seen this kind of problem appear when there is too much traffic and not enough bandwidth in the network to handle the cameras. I've also come across cameras with loose connetors causing this, so Kawboy12R's tricks might work just fine.

Could you tell us the nvr manufacturer, camera manufacturer and model, it is easier to try to figure out how the setup goes with a bit more details. Some manufacturers have a automatic config for their own cameras and nvr, but on many cases you have to either find out the ip that dhcp gave for the camera, or set the ip manually. After you have the ip(s) for the cameras, you might have to set the ip(s) to your nvr manually.

No, PoE stands for Power-over-Ethernet, meaning the PoE Switch also works as a power supply to the units connected to it via ethernet cable. So if you have an IP camera that supports PoE, you only need a PoE switch and one cat5e-6 cable to power it up and transfer the data.

Why is 128 x 2Mbps (= 256Mbps?) too much bandwidth if they support 256Mbps or 128 cameras?

What a lucky fella

A good alternative solution for Axis P8221, or any other ethernet I/O would be Moxa I/Os: http://www.moxa.com/product/Ethernet_Remote_IO.htm For example: http://www.industrialnetworking.com/Category/Ethernet-Daisy-Chain-IO/Moxa-ioLogik-E1214-Remote-Ethernet-IO $225

What a funny thread to read! Doing technical support in surveillance system has taught me that no matter whats the system, there are issues. Granted, less on the analogs than on IP, but thats because all the new installs are IP, and if old analog has problems, nobody bothers spending money on troubleshooting and buys a new IP-system instead. Mostly problems on IP are caused by cheap systems or systems that are built on an existing network that handles other devices aswell, or just someone installing who is inexperienced with IP-system. For me, if i was to install a new system, it would definately be IP system with server-grade hardware and a VMS. I might consider analog for a system that only has PTZ-cameras and does not require as high image quality, because analog RS-485 PTZ still works better than any network PTZ.

Your computer ip-address must be set to same network as the devices you're trying to connect to, either by ip or netmask. Few examples: - Your computer ip is 192.168.1.5, netmask 255.255.255.0, you can connect to any device with ip-address on a range of 192.168.1.1-254. - NVR ip: 10.140.1.150 netmask 255.255.255.0, any ip camera from 10.140.1.1 to 10.140.1.254 is possible to connect to this NVR. - Router ip is 192.168.1.1 netmask 255.255.255.0 and DHCP is enabled. Router will provide ip addresses to all the devices connected if the "automatic ip /ip from dhcp" is enabled, and you can check the addresses assigned to devices from router. PoE switch only works just as normal switch, but supplies power via ethernetcable. Ip-settings are just the same. Just like ssnapier said, there are "camera finders" or "device search" or "ip address utilities" for most of the camera manufacturers. To name few i've used: - Dahua ConfigTool - Dynacolor DeviceSearch - Panasonic EasyIpSetup - Pelco Device Utility - Shany MyFinder - Sony IP Setup or SNC Toolbox - Axis IP Util - Many more.. Default ip addresses for cameras can usually be found out via google. Just google up camera model and "default ip".

The simplest setup would be camera that shows jpeg (for example: http://87.139.76.248:8081/record/current.jpg ), and link that to a img src on website, everytime website is refreshed, it shows the current image. This way there is no need for any ftp-transfers etc.

I made a small calculator with php/ajax, for now it's only in finnish, but should give you some kind of estimate. http://talviuni.com/Temp/tyo/ Explanation of fields: 1. Hours of recording / day 2. % of movement in the recorded time 3. For how long you want your recordings to be available (days) 4. Amount of cameras 5. Camera bitrate

Could you give us more specific details on your current setup and cpu/mem/network usages (Task Manager/Resource Manager on Windows)? With those, it's probably rather easy to calculate what the requirements are. Also what's the software you're using, does it record all the time, does it have motion detection built-in or are you using the motion detection on cameras? You say 3mp cameras, what bitrate you use on those?

You should check how your router actually acts though, i've come across some cases where 2 computer in same router actually connected from Computer -> Router -> Outside router -> Back inside router -> Another computer. So make sure your LAN is actually configured properly. Probably the best choice is to buy a 1Gbps switch for the cameras, since normal cheap routers (ones that usually ship with the connection from isp) are bad at handling lots of LAN connections at high speeds.

Never tested, but another one that could work: rtsp://IPADDRESS:554/Streaming/Channels/1 And ofcourse when set, requires user and pass: rtsp://user:pass@IPADDRESS:554/Streaming/Channels/1 (If this isn't working for some reason, try rtsp://IPADDRESS:554//Streaming/Channels/1 )

Definately looks like the IR is hitting the hood/cover, and causing this reflection. I just had similar problems with my old HLC-1NAG, for now i solved it by taking the hood/cover off, but that wont work for you since it seems that cam is outside.

What first caught my eye was the same port for mobile and secure http, you should try a different port as they're supposed to be different services. The different version "fix" doesn't sound right either, but if it works, who cares right? You could still troubleshoot it a bit: Did you check the port forwarding and firewalling? It's always wiser to use IP-addresses than DNS-names, or if you must use DNS, configure your hosts-file to manage with them. I dont have any experience with Milestone, so i can only try to help on general networking issues though.

How would rtsp + vlc work out? I dont know any software that works like LiveVue does, so vlc + rtsp is my best bet. Maybe you could ask the author of LiveVue to add a generic RTSP-support?

You might also want to check that your ISP doesnt restrict the usage of the ports you're trying to use. For example, might be worth a try to go with a setup where you connect to external_ip:10000 - :10002, than :81 - :83 external_ip:10000 -forwards-to-> cam_ip:80 external_ip:10001 -forwards-to-> cam_ip:554 external_ip:10002 -forwards-to-> cam_ip:8557 Or what ever are the ports you use/need. This ofcourse requires your router to support "from port" "to port" configuration. For easier troubleshooting, you should first forward the ports to your pc, then run canyouseemee.org.

What are you trying to do exactly? Get image to browser to avoid the need for rtsp?

Accessories: PoE Injectors (Turn your normal ethernet-connection to PoE without a switch)(TRENDnet, D-Link, probably many others) Video recording software: Ksenos (www.ksenos.eu) (free trial, prices unknown) Mirasys (www.mirasys.com) (prices unknown) iOS/Android viewing app: Mirasys Spotter Mobile (www.mirasys.com/spotter-mobile)