timecode systems SyncBac PRO, Руководство пользователя

Страница: 25 / 64

What if a Slave Can't Find a Master?
If your SyncBac PRO cannot connect to a master device, it will use its own clock
settings instead. The most likely reasons for a slave being unable to connect to a
master are that the master is out of range or the devices in the BLINK network are
all set to run as slaves (so there is no master). A SyncBac PRO slave that runs using
its own clock is often described as 'free running'.
When a SyncBac PRO slave is 'free running', it will continue to try and find a master
device. As soon as it finds a master device within range and on the same BLINK
network, it will try to connect and synchronise with the master.
Example:
Let's say you want to film two riders in a mountain bike event. Both of the
riders are wearing HERO4™ cameras that have SyncBac PROs attached. The
first rider, Paul, has his SyncBac PROs set to run in GP Master TX mode and use
RF Channel 4. The second rider, Susan, has her SyncBac PRO set to run in RF
Slave mode and use RF Channel 4. At the start, Paul and Susan's SyncBac PROs
are within range of each other and so they synchronise their clocks.
During the event, Paul has a puncture and has to stop to repair it. During this
time, Susan continues ahead and goes out of range of Paul. At this point,
Susan's SyncBac PRO loses communication with Paul's master SyncBac PRO, and
so it carries on using the clock settings that it has in place.
Paul fixes his puncture and catches up with Susan. His master SyncBac PRO is
back in range of Susan's slave SyncBac PRO and so they connect and re-
synchronise.
SyncBac PRO User Guide 25