HR FHD264-R, Руководство пользователя

Страница: 19 / 28

Dynamic Virtual Matrix™
© Copyright 2018 Hall Research, Inc.
19
5.5.1 FHD SoIP Protocol
To perform a full Duplex SoIP with FHD, the 3rd party controller requires the following Client
and server architecture.

UDP Client: To send commands to FHD264 UDP port # 9002 for registration. The
controller should register its IP address with the FHD264 to receive the response on
the TCP server. The FHD sends the serial device response to only one registered
controller. We recommend repeating this process at regular intervals (one Minute).
In case of a reboot or power failure, the FHD264 will not remember the controller's
IP address. Registration can also be done using telnet command "
master_set ". The
registration message format (31 bytes) using UDP is as follows:

TCP Client: To send commands to FHD264 TCP port # 7000 . Maximum command
length is 100 bytes

TCP Server: Listen on port # 5050 to receive the response from serial device.
Maximum command length is 100 bytes

Ping Protocol: FHD264 uses ping to verify the controller’s presence
See the FHD SoIP application notes for more details and examples.
5.6 Fail-Safe (FS) Video Routing
Fail-Safe is a recovery system for the Receiver in case of a loss of video at the Sender end.
When FS is activated, the Receiver can switch to the assigned backup source (FS Group ID)
if video is lost in the current group. The Receiver switches back to its original group when the
video signal is restored. This powerful feature provides a layer of protection for systems that
need built-in video redundancy.
Figure 16 – Fail-Safe