![timecode systems AirGlu2 Скачать руководство пользователя страница 13](http://html1.mh-extra.com/html/timecode-systems/airglu2/airglu2_user-manual_1117224013.webp)
UK Timecode Systems Ltd. Unit 6, Elgar Business Centre, Moseley Road, Hallow, Worcester.
WR26NJ. UK
BLink networks
BLink is a method of connecting client/slave devices to a master controlling device
via the TCS proprietary long-range RF link. The master device MUST be the device
that the clients are connected to for RF Timecode synchronisation.
All S1C commands are initially sent to the master device and then relayed to the
BLink client via the RF link. Responses from the BLink client are then replied back
through the RF link to the master and then back to the command originator.
Generally, all commands/requests are replied to but it must be noted some replies
may take over a second to be returned. If no reply is heard within, say 2 seconds,
the original request should be re-sent.
The master device continually polls the BLink network both obtaining basic status
information which is stored in a local table for fast responses to requests
The BLink master also looks for new devices being connected to the network. New
devices are auto allocated a new BLink ID which corresponds to a table entry of
status information. New clients will generally be allocated an empty table position but
if these get used up then entries from clients ‘not heard from’ will be re
-used. This
table may change as BLink devices come and go from the network.
New devices may re-use table entries of devices that have disappeared.
Table entries may exist of devices that have not been heard from for a long
time.
Returning devices may be allocated a new BLink network ID and therefore a
different position in the table, therefore reference to Unique ID must be
maintained.
The BLink system can be configured for in excess of 1000 clients but currently
restricted to around 50 clients depending upon the TCS device used as BLink
master. It must be considered that more BLink clients do reduce the speed of the
network.
Command use with BLink network
Example addressing of individual unit within BLink network
“#@1;GLSD?
\
n”
Requests Sync standard of Blink device 1
“#@42;GLSD=0
\
n”
Sets Sync standard of Blink device 42 to
Off.
Note;
“#@0;GLSD?
\
n”
Requests the Sync standard of the Blink Master and will
result in the same as “#GLSD?
\
n”
Broadcast commands to all units will be for a restricted set of commands/settings
only (not requests) and will be addresses using “#@;” prefix i.e. device number
missing. Broadcast messages are NOT responded to by the clients and there is no
way of knowing without checking that a command has been heard or actioned.
There are also Group addressing commands that can address groups of units that
are assigned to a particular group. There are 6 groups named ‘A’ through to ‘F’ and
should be addressed as #@A; for instance, to address group ‘A’ devic
es.