From: Rick Romito [mailto:rick.romito@infrasafe.com] 
Sent: Friday, October 03, 2008 10:16 AM
To: Andriy Fomenko
Subject: RE: Advantor Interface with VideoNEXT

Andriy,
 
I sent the commands to you on 9/30 along with a sample log file captured between the switcher and our program.  Basic commands used are listed here.  Replace <camera> with the camera number (position in the switcher), <monitor> with monitor number (as defined by the switcher), and the <term> with a CR (0x0D).
 
Camera to a monitor:  LCM <camera> <monitor><term>        Example:  LCM 12 4<CR>
Move PTZ camera to a preset position:  prepos <camera> <preset><term>        Example: prepos 6 3<CR>
 
These commands can be sent as a single output.  Below is the communications for camera 1 to monitor 1 using preset 1.  The Burle response is to return each command along with "<LF>TC8800> " where <LF> is an 0x0A.  This is excerpted from the cameracomm.txt file (near the bottom of the file) I sent previously.
 
Request: 9/30/2008 13:50:52.01064 (+7.1719 seconds)
 
 4C 43 4D 20 31 20 31 0D 70 72 65 70 6F 73 20 31   LCM 1 1.prepos 1
 20 31 0D                                                               1.             
 
Answer: 9/30/2008 13:50:52.02664 (+0.0156 seconds)
 
 4C 43 4D 20 31 20 31 0D 0A 54 43 38 38 30 30 20   LCM 1 1..TC8800 
 3E 20 70 72 65 70 6F 73 20 31 20 31 0D 0A 54 43   > prepos 1 1..TC
 38 38 30 30 20 3E 20                                             8800 >          
 
 
Hope this helps.  Let me know if you need further clarification.
 
Rick

________________________________________
From: Andriy Fomenko [mailto:afomenko@videonext.com] 
Sent: Friday, October 03, 2008 9:45 AM
To: Rick Romito
Cc: Chris Gettings; Jeff Whirley; Chuck Perkinson; Gary Stalnaker
Subject: RE: Advantor Interface with VideoNEXT
Rick,

Thanks for explanation. We will proceed as you suggested.

Let me ask you to clarify on how exactly you want to call the camera up in GUI (how you send "popup!" signal to us).

Ideally, I would like to get sequence of commands you will use from your side similar to one you provided down below in email thread for video loss communications.

Sincerely,
Andiy  F.


From: Rick Romito [mailto:rick.romito@infrasafe.com] 
Sent: Friday, October 03, 2008 9:26 AM
To: Andriy Fomenko
Cc: Chris Gettings; Jeff Whirley; Chuck Perkinson; Gary Stalnaker
Subject: RE: Advantor Interface with VideoNEXT

Andriy,
 
In our conference call with Chris, it was agreed our system would communicate via serial RS-232, using either the Pelco or Bosch/Burle ASCII protocol.  We have already implemented both of these for our camera callup as part of our Air Force certified ASN V5.0 system.  
 
We also agreed we want to look down the road for the relationship and how we can more efficiently handle cameras tied to our system.  That option needs to be thought through based on a standard interface which would not need changed all the time because of the Certification issues.
 
For now, we need to proceed as originally agreed. Please let me know if you need further information on our implementation.
 
Regards,
Rick Romito


________________________________________
From: Andriy Fomenko [mailto:afomenko@videonext.com] 
Sent: Thursday, October 02, 2008 6:00 PM
To: Rick Romito
Cc: Chris Gettings; Andriy Fomenko
Subject: RE: Advantor Interface with VideoNEXT
Rick,

Another question

Reading protocol description, I've realised it is SERIAL COMMUNICATIONS interface!
Is it possible to bypass physical connections and go with direct IP (TCP Socket for example)?

It does not look to be an elegant solution to communicate over slow/archaic serial connection while all the stuff works as a software anyway on both sides.

What do you think?

Thanks,
A.F.




From: Rick Romito [mailto:rick.romito@infrasafe.com] 
Sent: Tuesday, September 30, 2008 4:06 PM
To: Andriy Fomenko
Cc: Chris Gettings
Subject: RE: Advantor Interface with VideoNEXT

Andriy,
 
Here is the other information I said I would send.  The attached file shows communications between us and the Bosch 8600 switcher with only 1 camera connected - the file shows errors where cameras 2-4 are not connected where expected.
 
Rick
 
 
The standard commands we use.
Command: <header>LCM <camera> <monitor><term>
Command: <header>prepos <camera> <preset><term>
Command: <header>video-status<term>
Command: <header>ver<term>
Theres no <header>.
<term> is 0x0D
"UNINSTALL-ALL" is sent to set video loss detection off on all cameras.
"INSTALL-CAM <camera> 1" is sent to turn on video loss detection for the specific <camera>.
"video-status" is sent to request the current video loss status. The message that is returned and decoded is more complex - look at the manual to figure out how that works.  This is sent about every 20 seconds.
"ver" is sent as a PING every 20 seconds to verify were are still talking.


________________________________________

From: Rick Romito [mailto:rick.romito@infrasafe.com] 
Sent: Monday, September 29, 2008 5:58 PM
To: Andriy Fomenko
Cc: Chris Gettings
Subject: RE: Advantor Interface with VideoNEXT

Andriy,
 
We prefer using the Bosch/Burle ASCII format which is defined in the attached document.  Tomorrow I will connect to our model 8600 switcher and capture all of the messages we send and receive and send that to you.  We only use a small subset of available commands.
 
Regards,
Rick
 

________________________________________
From: Andriy Fomenko [mailto:afomenko@videonext.com] 
Sent: Monday, September 29, 2008 5:20 PM
To: Rick Romito; Rick Romito
Cc: Chris Gettings
Subject: RE: Advantor Interface with VideoNEXT
Rick,
Can you please provide more information on messaging format you would expect for video loss signalling and to call up the camera?
Thank you,

Andriy Fomenko
Chief Software Architect
videoNEXT Network Solutions, Inc
3852 Dulles South Court, Suite I
Chantilly, VA 20151

AFomenko@videonext.com

703-657-1209 Direct
703-209-5432 Mobile
866-723-3077 24x7 Support




________________________________________


From: Rick Romito [mailto:rick.romito@infrasafe.com] 
Sent: Thursday, September 25, 2008 3:04 PM
To: Ron Nau; jeremiah.morrill@videonext.com
Subject: Advantor Interface with VideoNEXT

Hi Guys, 

My name is Rick Romito.  I got your names from Chris Gettings in a conference call this morning.  I am the software engineer working the interface between ASN, out alarm monitoring system, and VideoNEXT for the Hanscom upgrade and future integration using XML, etc.

The immediate concern is the connection of our Air Force certified ASN V5.0 system to your system.  I am to connect and control cameras at Hansom using your system as a matrix switcher.  Our preferred connection is using Bosch/Alligent/Burle 8600 ASCII protocol, as this it the AF certified switcher, and the only protocol we currently have implemented that reports video loss.  Other switchers we can communicate with are Pelco ASCII (not Pelco-D) and Vicon.  At the present we use a limited subset of all of these protocols.  Basically what we implement are: select a camera to a monitor, with or without a preset number; video loss detect; and ping.  I can send specific messages if you require them.

For the future we hope to communicate to you via XML.  I have implemented protocols ICD-002 and ICD-0100 for connecting to radars and a fence sensor.  If you have implemented either of these we may have an easy time of extending our controls to fit your system.

Best regards, 
Rick Romito 
Advantor Systems Corp. 
Software Engineering Manager 
romito@advantor.com 
407.926.6968 

Notice of Confidentiality: 
This e-mail communication and the attachments hereto, if any, are intended solely for the information and use of the addressee(s) identified above and may contain information which is legally privileged and/or otherwise confidential. If a recipient of this e-mail communication is not an addressee (or an authorized representative of an addressee), such recipient is hereby advised that any review, disclosure, reproduction, re-transmission or other dissemination or use of this e-mail communication (or any information contained herein) is strictly prohibited. If you are not an addressee and have received this e-mail communication in error, please advise the sender of that circumstance either by reply e-mail or by telephone at (800) 238-2686, immediately delete this e-mail communication from any computer and destroy all physical copies of same. 

Replies Filtered: 
Any incoming e-mail reply to this communication will be electronically filtered for "spam" and/or "viruses." That filtering process may result in such reply being quarantined (i.e., potentially not received at our site at all) and/or delayed in reaching us. For that reason, we cannot guarantee that we will receive your reply and/or that we will receive it in a timely manner. Accordingly, you should consider sending communications to us which are particularly important or time-sensitive by means other than e-mail. 


------ End of Forwarded Message