Videohub Rs-422 Protocol - Blackmagicdesign Videohub Installation And Operation Manual

To forcibly unlock a port that has been locked by another client, send an update to the port with
the character "F" instead of using the usual unlock character "U". For example, to override a
lock on port 7:
SERIAL PORT LOCKS:↵
7 F↵
↵
ACK↵
↵
SERIAL PORT LOCKS:↵
7 U↵
↵
Hardware status blocks can only be sent by the Videohub Server. If a client sends hardware
status blocks, they will be ignored.
Requesting a Status Dump
The client may request that the Videohub Server resend the complete state of any status block
by sending the header of the block, followed by a blank line. In the following example, the client
requests the Videohub Server resend the output labels:
OUTPUT LABELS:↵
↵
ACK↵
↵
OUTPUT LABELS:↵
0 output label 1↵
1 output label 2↵
2 output label 3↵
...
↵
Checking the Connection
While the connection to the Videohub Server is established, a client may send a special
no-operation command to check that the Videohub Server is still responding:
PING:↵
↵
If the Videohub Server is responding, it will respond with an ACK message as for any other
recognized command.

Videohub RS-422 Protocol

General
The RS-422 protocol can be used to control many Videohub models as RS-422 slave devices,
for router crosspoint switching. This feature is available on any Videohub model with an
"RS-422 Control" port.
Depending on your model of Videohub, the RS-422 port may be either a DB9 or RJ11 connector.
DB9 cables are commonly available in electrical stores. The RJ11 connector is the same used in
many landline telephone connections. By modifying an RS-422 to USB adapter cable
terminated with an RJ11 connector you can control Videohub using external controllers via USB.
In "Leitch Server" mode, these Videohub models implement the router (server) side of the
Leitch Serial Pass-Through Protocol as specified in section 4 of Leitch document SPR-MAN
revision D. In "Leitch Client" mode, the Videohub implements the controller (client) side of the
Leitch terminal protocol.
Developer Information 79