i-MARK 2 / i-MARK 3
USER
MANUAL
VISIBILITY DELIVERED.
PAGE 47 OF 55
i-MARKs that are not synchronized, rely on their own internal quartz clock to determine its broadcast
intervals. Over time, this clock-step may drift, causing possible disturbance to other units where LF
fields overlap. The Jitter feature causes a scatter in the time-step to avoid this scenario.
8.6
Details on Specific Settings
8.6.1
Operation Mode—Continuous/host only
Note: The factory pre-set operation mode is “continuous”.
In most applications the i-MARKs shall autonomously send its marker ID. This is the case in the
continuous operation mode.
In some cases an application may need to have full control to when the position marker transmits the
marker ID. This can be done by configuring the position marker in host only mode, in this mode, it will
send its marker ID only when instructed by the host.
8.6.2
Synchronization—Slave/master
Note: By standard slave mode is the factory setting. One of the i-MARKs will be set as master on site,
all others remain slaves.
The recommended configuration is, to have a host present on the RS422 bus. This would allow
retrieving devices status information and detecting any device failure in real-time.
In this situation, the host will be the master and must send the synchronization messages and all
position markers must be configured as slaves.
In some applications, where a connection to a host is not possible, the first marker in the Daisy-Chain
can be configured as a “MASTER”. This marker will take control over the synchronisation of the
“SLAVE” markers, connected to the i-BUS.
In slave mode the position marker will only transmit the LF telegram based on the synchronization
scheme or host request depending in the operating mode.
Active loop 1
Slot #
1 2 3 4 5 6 7 8 9 10 11 12
1 2 3 4 5 6 7 8 …
Cycle Delay