Sejjiboy

I am looking at building my own NVR. I have already spec'd and priced out all the hardware except for a case. I would prefer to throw this system in a rack, which I have also not been able to pick. Just a simple build, microATX Mobo, ATX modular PSU, 2x ram, cpu, raid card, 2x WD Black caviar. Anyone have any suggestions for what type of cases to look for or to stay away from? Same for a rack. There isn't a lot of desk / shelf space to put stuff, hence the rack idea.

I have been on this forum a little bit and I have been in this industry for a couple years now, but most of what we do is commercial. It is all the higher end Panasonic and Pelco stuff. I am looking at putting together a small home system and don't want to be spending 300+ for one camera. The type of stuff I am looking for / stuff to look into; DVRs -Brands or Models and Cheaper / Lower end cameras of good quality -Brands or Models. I am interested in throwing a camera in a tree outside my house, any suggestions for that?

We have discovered the issue. Apparently.. By default the Pelco protocols are set to a baud of 9600 when using other Pelco products. When connecting direct to a different product; -Pelco P operates on a baud of 4800. -Pelco D operates on a baud of 2400.

Let's see.. The VEZ does have separate RS-485 input connections. Both devices are set for the Pelco protocol over RS-485. It appears that you can only access the on screen menu if you have a controller connected and working... Currently I have +/+ and -/- connected, that is how RS-485 works correct? Regardless, reversing polarity doesn't change anything. The baud rate is set by DIP switches on the VEZ. Both the camera and the controller are set for 9600. Thanks for the suggestions to check / try. Unfortunately they did not get it working >< Any other ideas?

I am trying to get a Bosch VEZ-400 Mini PTZ Dome camera working direct with a Pelco KBD300A Keyboard. I think I have addressed them properly and the protocols are both set to Pelco D/P. I'm getting nothing, other than a decent image over the Coax =P Anyone have any ideas?

Ok.. Well we seem to have discovered the problem.. Originally they had the cameras hooked up with TXB-AD translator boards. Once we decided they weren't needed they simply removed them. Apparently there is some kind of PCB that has to be inserted into that socket to complete the circuit? Those were discarded during the initial install.. Ugh..

OK so, we couldn't get it working. We picked up a PTZ controller. Now we have a KBD300a going direct D to the Spectra IV. We have the baud rates, the protocols, and the wires all hooked up properly. 3 different techs from tech support confirmed this. Still nothing.. We assumed something wrong with the camera? Tested with a second camera. Still nothing.. I would assume a Pelco controller properly hooked up to a Pelco PTZ would work wouldn't you?

Hmm yeah we seem to be having issues >< From what I've been told, the Pelco PTZ's will not run on sensornet. So a matrix and a rs232 connection, hmm, time to look into that one. Thanks for a reply.

I was approached to help solve an issue regarding the integration between an American Dynamics Intellex DVMS and three Pelco Spectra IV PTZ cameras. They can get video, but cannot get any PTZ control via the software on the DVMS. Currently they have the PTZ set to D Protocol, connected to the DVMS via the UTP Data connection, and D Protocol firmware installed on the DVMS. From my understandings of these types of systems, this would be like trying to drive a car without a steering wheel. Doesn't there have to be some kind of RS422 connection between the devices? The DVMS doesn't have any 422 connections on it. The solution that first popped into my head was to add a USB-422 converter between the DVMS(USB) and the PTZ(422). If we were to throw in three USB-422 converters, could that potentially correct the error or are there more issues that would need to be addressed? Thanks, ~Sejj