Third-Party Access Control Systems supporting ASCII (clear text) transmission can trigger Alarms (and thus also scripting) or direct camera to monitor callups within Endura.
Pelco Video Management
Endura UDI5000-MTRX in ASCII mode All Versions
Clarify known methods for configuration within Third-Party Access Control Systems and UDI5000-MTRX.
note: The Example Third-Party Access Control System used for this article is Galaxy Access Control Systems. In reality, any system which can output the correct Pelco ASCII (cleartext) data - or user configurable ASCII - is capable of integration with Endura in this manner.
To begin, select one of the following Articles to configure and test the UDI5000-MTRX to receive the ASCII (cleartext):
a. Configuring UDI5000-MTRX in ASCII mode: Network Server, as shown in LL#11648. This means the UDI5000-MTRX will receive ASCII via TCP/IP (ethernet). This is the method which the remainder of this article covers for the example Galaxy Access Control System.
...the other options are...
b. Configuring UDI5000-MTRX in ASCII mode: REST/HTTP
c. Configuring UDI5000-MTRX in ASCII Mode: Network Client
d. Configuring UDI5000-MTRX in ASCII mode: Serial
e. Configuring UDI5000-MTRX in ASCII mode: UDP
Ensure that the Third-Party Access Control System has the appropriate license or module activated to send ASCII (clear text) data to the UDI5000-MTRX. In this example, the Galaxy Access Control System must be Registered for "CCTV Support" as described in Pages 6 through 10 of the SG CCTV Interface Guide.
In our example configuration, the Galaxy Access Control System was virtualized onto a Windows 2008 Server which had no physical RS232/422 Serial/COM Port. Based on that, the initial attempt was to configure Galaxy to send to its ASCII data to the UDI5000-MTRX using TCP/IP on Port 3002. This attempt failed however, as the Galaxy Access Control System sending-format had been developed for use with a Third-Party Communications Lantronix Terminal Device, and the data being received was not interpretable by the UDI5000-MTRX. A workaround was devised (continue to step 4)...
Click here to download and install the HW-Group VSP3 Virtual Serial Port Freeware Application using all default options during installation.
Launch the installed HW Virtual Serial Port application (shortcut should be on desktop), and configure as follows:
a. From the Virtual Serial Port tab, click the Login button and press OK...
b. Note (or change as desired) the COM PORT Number shown in the Port Name dropdown-menu.
c. Configure the IP Address field to point to the UDI5000-MTRXs' IP Address, and the Port field to 3002, or as configured from step 1a above.
d. Click the Create COM button, and wait for the VSP Status field to read "Created"...
Next, configure the Third-Party Access Control System to send its ASCII data to COM3 (or as-configured in step 5). For Galaxy Access Control, this is achieved as outlined on Page 11 "Adding a CCTV Switch" of the SG CCTV Interface Guide.
Finally, from within the Access Control System, configure what the various event types will send to the UDI5000-MTRX aka "CCTV Switch", as shown here from page 16 of the SG CCTV Interface Guide...
...in this illustration, a "Door Forced Open:" event at the Galaxy Access Control System level will trigger the following:
a. Alarm 2 will be sent to the UDI5000-MTRX, which is the ASCII command 2Ea.
b. The command to display Camera number 1 onto Monitor number 1 will be sent to the UDI5000-MTRX, which is the ASCII command 1Ma1#a.
c. The command to display Camera number 2 onto Monitors 4 and 5 will be sent to the UDI5000-MTRX as well, 4Ma2#a & 5Ma2#a.
note: The fields for DVR Camera and Manual Commands may not work for 2nd Generation Endura Devices, contact Galaxy Access Control Systems for details.