RDeSmet

Has anyone ran into issues with a windows blue screen that says "Hardware Malfunction NMI Memory Parity Error". We are using HP dc7100 Pc's with a p4 3.2ghz, 512mb Ram, it has an integrated video card on the mo-bo. We have gotten this error on almost every gv650 card we've used with this configuration. The error seems random, some will give it in a couple of days after install, and some take a few months. I was just wondering if anyone has come across this before. We have about 15-20 systems doing it.

I think the wansview cameras come with some software that you can install onto a pc to record video with, also, the bigger issue like mentioned before is bandwidth, there are a few things you can do to lower the bandwidth coming out of the cameras that should be a big aid in getting the streams to your computer. I don't know if Wansview uses a fixed bit rate stream or variable bit rate with a cap. I looked at a config page of a Wansview, and you should be able to turn the stream rate down to say 1024k or even 512k which would free up some bandwidth on your wireless network.

Are these cameras being run on 12vdc or 24vac?? It looks to me like they are 12vdc cameras, and are sharing a power supply. Likely what has happened is some moisture has gotten into the conduit and is causing a bit of a ground loop, Try powering the camera that is Ghosting on it's own power supply and see if it clears up, also since it is only 4 cameras, try unplugging the other 3 cameras from power and the dvr and see if it clears up the camera that is ghosting. That will point to a ground issue.

As long as you are not using Gigabit ethernet, which most IP cameras do not do, you are only using 2 pair for network connectivity, so that leaves 2 spare pairs in the cable. Most network cables are wired in the T568B standard. Which means that the orange and green pair are being used for your network connectivity, you could pull out the blue and brown pair on each end of the cable and use that for your power.

The March Networks 3108 will support both IP and analog cameras. I think they will only support 4 Ip cameras in addition to the 8 analog cameras. The Ip support is limited to a number of camera vendors, and also is basically just a stream and store.

I am having trouble getting a dvr to connect to the central monitoring station via center v2, everytime the dvr reboots and tries to run the connect to center v2 it comes up and says run local server failed. If you click ok on the error and then click connect it usually connects up fine then. This is the only dvr we are having this issue on and we have even tried completely reformatting the dvr and reinstalling everything. And still run across this issue. Tech Support looked at the .ini files and said that the ip address was blank, and to put an ip address in, we have an ip address in the box. We are running v7.0

Well Finally after a couple of months I think we are getting down to a solution. It appears to be a conflict between the chipset used in a gv-650 card and the integrated intel video chipset used in the Hp 7100 pc's. We have added an add on video card on a few test systems and so far all of them have been running fine.

I finally got a couple of screen shot from the Merit PIH-0544 IR cameras. Here is a link. http://www.rapidnet.com/~rdesmet/IR.html They were taken at 320x240 resolution, since the dvr is recording at CIF. The 3 pictures were taken with various night lighting conditions.

We use outdoor single gang boxes. It makes it much easier to work on and hook up to with a monitor to adjust.

We've had good luck with these. They don't seem to create all the noise when switching to low light mode like many of the other cheap cameras seem to. I'll get some pics, and post later on. http://www.meritlilin.us/cgi-bin/eCart/Details.asp?id=226

Here is where we get our power adapters. I prefer using the adapter over cutting the power wires on the camera and splicing, it makes it much easier to service, but I do tape the end to keep it from pulling apart. http://www.pimfg.com/local_cat_a.asp?menu_no=0&getsubcat=Y&seq=10&seq_name=Power&main_type=123&sub_type=5&master_desc=SECURITY&secondary_desc=Power&third_desc=RCA%20Power%20Cable

Has anyone used any autotracking ptz's and what kind of luck have they had with them. A lot of our customers want to monitor parking lots and be able to zoom in and track an object without having someone controlling the cameras 24x7. Also, how does the autotracking feature work when there is motion in multiple areas.

Do you still have expansion slots on the back of your case?? If you use a Geovision Net I/O card, you don't need an actual pci slot from your motherboard, you just need a free mounting slot on the back of your case, the Net I/O card hooks into your Geovision Capture card via a ribbon cable. If you don't have any expansion slots on the back of your pc case, then you can control the External GV-Net box with a usb to serial adapter. But then you need to also add a GV I/O since the GV-net is just a rs232 to Rs485 converter.

I've used a bunch of both the I/O's and the I/Onet cards, The biggest thing for me, is that with the I/O net cards, we can have a dry contact on the output, where when we use the I/O's we had to go through a relay. For unlocking Doors, etc... We have only done it tying it together with an access control system, hooking the output from the I/Onet to the egress input. Also, we buy all of our geovision parts from Digital Watchguard. They are really helpful.

There could be an extra conduit to the poles but it's highly unlikely, no one ever seems to plan in advance like that. Look around the pole and you may see a larger grey 12x12 or so NEMA box. When we've done installations like that at remote locations, most of the time all we can do is send the signal wirelessly. Then what we do is have an electrician give us an outlet before the photo sensor on the light pole so we have constant power, then mount the wireless transmitter in a NEMA box and send the video back to the main unit wirelessly.

Thanks for the links. Funny thing with this though, is that I can't seem to find a real fix, some of the systems work if I move the Ram to Different slots, and some work by moving the geovision card to a different slot. Some I have even swapped ram between 2 systems that were giving me this toruble and they seem to work. But there is about 5 or 6 of them out there that I can't seem to get this error resolved. What I can't figure out though is why it only does it on the 650 cards. I haven't had any issues with it at all on the 600 cards. I haven't tried it on anything bigger than a 650 yet.

The nicest dvr I've come across for POS capture is March networks, plus, if you are using a gilbarco, they now have a gilbarco protocol out. Plus a benefit of the March's is that those things are Rock solid.

I've been looking into switching to compression connectors instead of crimp, but price still seems to be a big issue. Does anyone know of a place that sells the compression bnc's for around .75 or less if we buy 5-10,000 at a time??

This is where we've gotten replacement connectors before. http://www.digitalwatchguard.com/securitycameras/pc/viewPrd.asp?idcategory=251&idproduct=1194