[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: Need help with video system problem



So this is an up the coax PTZ control set up? "these cameras support perhaps
6-10 different protocols." Not true for up the coax, generally only one. If
PTZ control is on a data cable then yes many protocols.
If  PTZ #8 ever worked someone must have "set the protocol on the camera to
the match the controller." already. Unless you did something to change the
settings that shouldn't be an issue.
Sounds like #8 may have problems and needs a RMA.
Only 8 cameras? And still using a mux? That system is too small and old to
use anything but a replacement DVR head end when that time comes unless you
have money to burn or are going to add a bunch of cameras soon. No need to
sniff out Verint and such. That doesn't get cost effective until a minimum
of 32 cameras is reached and more are to be added soon.
I guess you have a large facility with a small number of cameras.

"JM" <jm@xxxxxxxxx> wrote in message
news:lLm5h.26865$OE1.19507@xxxxxxxxxxxxxxxxxxxxxxxxx
> Thank you for helping.  I appreciate it.
>
> As for where the tour information is or isn't, here's what I tried:  In
> the server room the video cables are terminated on boxes with BNC
> connectors. They run left to right from 1-9.  From there, patch cables
> connect them to the multiplexer underneath the server.  So I can try
> different ports on different cameras simply by moving the patch cables
> around and watching the result on the server monitor.  When I connect any
> port to the #8 camera, there is no movement.  However, when I connect any
> camera to the #8 port, the camera starts moving.  Therefore, unless I'm
> not thinking properly, the video port is giving the tour info.  It's just
> that the #8 camera isn't listening.
>
> From what I can reason, there are at least three possible places where
> this programming information must be configured:  the camera itself
> (dipswtiches and jumper pins), the programming interface accessed by the
> joystick/keyboard, and the RapidView software.  The only method I haven't
> tried is the joystick/keyboard.
>
> I asked a video professional I know from another region, and he thinks I
> haven't "set the protocol on the camera to the match the controller."  He
> said for interoperability, these cameras support perhaps 6-10 different
> protocols.
>
> One problem is that I can only access the server room about twice a week.
> It's an area of limited access.
>
> thank you again,
>
>
> jm
>
>
>
>
>
>
>
>
>
> "Michael" <sirflannelS@xxxxxxxxxxxx> wrote in message
> news:km6al2d3vlicm4eb4lanul2l1ktu0uv2ot@xxxxxxxxxx
>> Sorry to hear you're thrown to the wolves like that. One of the bggest
>> source of new customers is from other companies that can't (or won't)
>> service their installs. Anyway, let's try to help you. I hope I'm not
>> giving you bum scoop, as I have worked mostly on other brands of
>> cameras and DVR's. But, The others are similar in the relationship
>> between the DVR and the PTZ operation.
>>   I'm not convinced the DVR is sending any signal to start it's tour.
>> If you can, try getting a camera to stay still, then plug it straight
>> into the monitor (if it's not too difficult). After a few minutes, my
>> guess is the camera will start it's tour on it's own. That would lead
>> me to think the other camera might not be programmed with a tour. I
>> noticed another post that said the part number you mentioned was an
>> advanced replacement. Another clue, IMO, that it needs a tour.
>> Yes, using the joystick or keyboard to program the camera sounds just
>> about right. I'm sorry I'm not familiar with the procedure for the
>> Rapid Eye domes. Good luck, and feel free to ask more questions if you
>> need.
>>
>>
>>
>> On Fri, 10 Nov 2006 14:05:41 GMT, "JM" <jm@xxxxxxxxx> wrote:
>>
>>>I think you're right.  My challenge is now figuring out how to tell the
>>>camera what to do.
>>>
>>>The cameras in question, as best I can tell, are "RapidDome" cameras
>>>(VC8E-GC18) on the large pedestal (about 3 feet).  They are mounted to
>>>light
>>>poles through a large facility.
>>>
>>>I was able to find an installation document, which seems to suggest to
>>>enter
>>>programming through the joystick/keyboard controller.  Does that sound
>>>right?  Other than that, I've only got the physical settings on the
>>>camera
>>>to work with and the RapidEye software, which does not address this type
>>>of
>>>programming.  The RapidEye docs simply state that "some camera models can
>>>be
>>>programmed to perform an operation after a View session is ended."
>>>
>>>And you hit on the only troubleshooting method I didn't try - putting a
>>>working camera from another location into location 8.  It was late and I
>>>was
>>>about out of time on my bucket truck.  The only thing I know is that back
>>>at
>>>the head end where the cable runs are terminated, I connected another
>>>camera
>>>to the #8 port on the multiplexer and it started moving.  So I know the
>>>port
>>>is sending the message.  Now, I guess it's possible that there's a
>>>problem
>>>in the wiring or terminations on the #8 camera end.
>>>
>>>If someone could point me to the programmable settings (if there are any)
>>>on
>>>the camera, then I think I could figure this out.
>>>
>>>By the way, we're in this position because the company that installed the
>>>system will not take care of us.  They take 2-3 weeks to get out after
>>>they're called, then they bill us extraordinary amounts, often without
>>>even
>>>fixing the problem.  I'm a contracted computer guy, so I'm trying to take
>>>over the video.  I'm willing to put in the time; I just need some
>>>direction.
>>>
>>>Thank you,
>>>
>>>jm
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>"Michael" <sirflannelS@xxxxxxxxxxxx> wrote in message
>>>news:ogg7l25a6ci5rrbsce7abruodbk36insj7@xxxxxxxxxx
>>>> I'm not sure what cameras you're using, but with the PTZ cams I use,
>>>> the programed tour is stored in the camera, and the head end only sent
>>>> the signal to start it, or it was programmed to start after a few
>>>> minutes of inactivity. Is it the same with the cameras you're using?
>>>> Which brand, model are you using? Perhaps the original camera with the
>>>> tour was replaced, and a new tour not programmed back in? Did you try
>>>> putting a known good camera in the #8 position? That would be my
>>>> guess. Hope it helps
>>>>
>>>> On Thu, 09 Nov 2006 23:08:38 GMT, "JM" <jm@xxxxxxxxx> wrote:
>>>>
>>>>>A client has a Honeywell video surveillance system with RapidEye Admin
>>>>>and
>>>>>View software.  There are 9 cameras, all fully PTZ.  The "preset 1"
>>>>>(local
>>>>>tour) instructs the cameras to be in motion at all times, panning R/L,
>>>>>zooming in, out, then starting over.
>>>>>
>>>>>One camera (camera 8) WILL NOT respond to the preset.  We can move the
>>>>>camera manually via the View software.  All functions appear to be
>>>>>working.
>>>>>I took camera 8 to another location where the installed camera was
>>>>>acting
>>>>>properly, installed it there, and it still would not move.  So the
>>>>>problem
>>>>>definately is in the camera.  I checked all the jumpers and dip
>>>>>switches,
>>>>>and they appear to be set just like those on the working cameras.
>>>>>
>>>>>Any suggestions?  Have I left out critical info?  I'll be glad to fill
>>>>>in
>>>>>the blanks.
>>>>>
>>>>>Thank you,
>>>>>
>>>>>jm
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
>




alt.security.alarms Main Index | alt.security.alarms Thread Index | alt.security.alarms Home | Archives Home