AVC761: 'Auto switch to alarm video' in Video E Server

[todd2 0]

I was trying to use the 'Sequence' mode of the AVC761 in combination with

motion detection trigger to send images to an ftp server and noticed that it

sends OK, except the focus of the sequence doesn't update when the alarm

happens--it just plods along unawares and waits the normal time (2 seconds, default)

to switch to the channel having the alarm.

 

I compared my configuration screen against a manual for AVC760-762 and noticed

that the manual describes an option which is MISSING in my Video E Server:

 

Auto switch to alarm video: Check this option to immediately switch to the channel that an alarm event trigerred and see the live view.

 

This sounds like exactly the problem but it's not there.

 

I tried Video E Server versions 1.0.6.6 and 1.0.6.3. I actually opened the

EXE in a binary editor and see the string 'Alarm auto switch video' so something

must be disabling it internally. Which leads to the question:

 

What is the latest firmware and where can I get it?

[todd2 0]

Assuming I can't hack the configuration software to fire this hidden option,

it looks like the only way to get this to work right is to use some external

logic. A relatively straightforward with a PIC chip could be connected

to the rear RS232 (simulated keyboard) input and the alarm output.

When the NO alarm output closes (indicating one of the cameras is

in motion detection), we rapidly send the sequence 1-2-3-4 to the AVC761

causing it to change screens much faster than 2 seconds. (I've checked

it can be done at least twice per second from the front console.)

 

If we can switch through all the cameras (1-2-3-4) at least once

per second, that would solve the problem because the capture rate

is < 8FPS per camera (30FPS total) no matter which camera is selected,

meaning that during the cycle, no more than 8 images are generated.

If we select 10 images to ftp (the max) per detection event, we're

guaranteed to capture at least one of the important camera.

 

With the 2 second dwell time it ships with, the math tells us we

have to dumb down the total FPS to 3 FPS total (the minimum) to achieve

the same effect, yielding a per camera FPS of 3/4 FPS. At 3/4 FPS,

the 2 second dwell time means that a cycle (1-2-3-4) takes 8 seconds,

generating 8*(3/4) = 6 frames, and again grabbing 10 images will

get at least one of the important camera.

 

The cost of a PIC chip is minimal, but the effort of writing the

code for it, soldering the RS232 connector, etc. is a pane.

 

Oh, and we'd also have to log into the DVR as guest to allow the RS232

commands to go through. One idea to avoid having to manually do this

is that every few minutes, the PIC could send a key sequence logging

us in as guest (blindly) 1, 1111, something like that.

 

What a pain! Why won't that configuration option show up the Video E Server 1.0.6.3/1.0.6.6???

[todd2 0]

An update on this. I just rigged a jumper from the DVR to my PC's serial port to

test out the reaction speed when I send '1','2', etc. commands to switch cameras.

 

It's lightning fast. Project I described above should be doable.

 

I'll post another update when I get the PIC prototype wired up using the 'Alarm Out' from the

DVR as an input. (The PIC will sense the alarm from the DVR and start jumping through the

cameras, manually shortening the dwell time, so that all camera images can be sent to the ftp

server.)

 

I can't get it to jump to the camera in alarm because there's only one alarm output, but this

seems like the next best thing. The PIC power drain is minimal so I should be able to tap

into the 12V fan supply with a Y-adapter.