timecode systems UltraSync ONE - What if a Slave Cannot Find a Master?

What if a Slave Cannot Find a Master?
Sometimes, your UltraSync ONE may be out of range of its master. In this situation,
your UltraSync ONE cannot receive timecode from the master and so uses its own
internal timecode instead. This is called 'free running'.
Typically, an UltraSync ONE will free run because the master is out of range.
With master-slave connection failures, there are several different scenarios to
consider:
Slave Connection to Master Result
Slave is trying to connect to a master
for the first time, but cannot establish
a connection.
Slave free-runs using its own timecode.
Slave was connected to an RF master,
but has lost the connection. The RF
master is an UltraSync ONE, SyncBac
PRO, or minitrx+.
Slave free-runs using its own timecode.
It will continue to be synchronised with
the master's timecode for
approximately one day.
The slave will connect with the first
master device that comes into range
and is using the same RF channel (as the
slave).
Slave turned on, connected to BLINK
master, but lost connection. The BLINK
master is a :pulse or :wave.
Slave free-runs using its own timecode.
It will continue to be synchronised with
the master's timecode for
approximately one day.
The slave will only re-connect with its
previous BLINK master. It will ignore any
other masters that come into range. If
you want the slave to connect to a
different master, you will need to
restart the slave.
26 UltraSync ONE User Guide