2.8.6.5 End of Telegram (EOT)

EOT Before WCO

Before WCO, the receiver checks for a valid RF signal. During this period, the following EOT conditions can be enabled independently for path A and path B of each service in the eepServices.EOT1x variables:

Manchester coding fail (MANFEx)
Symbol timing fail (SYTFEx)
Modulation amplitude fail (AMPFEx)
Carrier fail (CARFEx)
WCO time-out fail (TMOFEA)
RSSI range fail (RRFEx)
EOT from other path (EOTxFE)


Address Service0	Name	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1	Bit 0
0x00C6	EOT1A	EOTBFE	RRFEA	TELREA	TMOFEA	MANFEA	SYTFEA	AMPFEA	CARFEA
0x00C7	EOT1B	EOTAFE	RRFEB	TELREB	TMOFEB	MANFEB	SYTFEB	AMPFEB	CARFEB

By default, the Manchester, symbol timing, modulation amplitude, carrier (FSK only) and WCO time-out are activated as an EOT1 condition.

An EOT event is triggered as soon as one of the enabled checks fails. The functionality and configuration of the checks is described in detail in Telegram Settings and Signal Checks.

The further flow depends on the intermittent WUP (eepServices.rxSetPathx.IWUPx) and demodulator auto restart (eepServices.rxSetPathx.DARx and eepServices.DMCRx.DMARx) configurations. If IWUPx is set, the path that received an EOT is restarted and continues searching for a WCO until a WCO time-out occurs. An active IWUPx setting can be useful in PollingMode if a channel has to be checked for a given time before switching to the next channel.

If IWUPx is not active or a WCO time-out occurs, the DARx/DMARx setting decides if the path (including the WCO time-out timer) is restarted or the reception is finished. The DARx/DMARx variables must be set in RXMode for standard applications. In PollingMode, these EEPROM settings are ignored because the function is automatically treated by the firmware.


Address Service0	Name	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1	Bit 0
0x00E0	rxSetPathA[1]	IWUPA	DARA	GAPMA	RXTEHA	—	—	—	RXMODA
0x00E2	rxSetPathB[1]	IWUPB	DARB	GAPMB	RXTEHB	—	—	—	RXMODB
0x00C0	DMCRA	DMARA	SY1TA	SASKA	DMPGA[4:0]
0x00C1	DMCRB	DMARB	SY1TB	SASKB	DMPGB[4:0]

EOT Between WCO and SOT

Between WCO and SOT, the receiver checks for the start of the data payload. During this period, the following EOT conditions can be enabled independently for path A and path B of each service in the eepServices.EOT2x variables:

Manchester coding fail (MANFEx)
Symbol timing fail (SYTFEx)
Modulation amplitude fail (AMPFEx)
Carrier fail (CARFEx)
SOT time-out fail (TMOFEA)
RSSI range fail (RRFEx)
EOT from other path (EOTxFE)


Address Service0	Name	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1	Bit 0
0x00C8	EOT2A	EOTBFE	RRFEA	TELREA	TMOFEA	MANFEA	SYTFEA	AMPFEA	CARFEA
0x00C9	EOT2B	EOTAFE	RRFEB	TELREB	TMOFEB	MANFEB	SYTFEB	AMPFEB	CARFEB

The default setting is to activate the Manchester, symbol timing, modulation amplitude, carrier (FSK only) and SOT time-out as an EOT2 condition.

An EOT event is triggered as soon as one of the enabled checks fails. The functionality and configuration of the checks are described in detail in Telegram Settings and Signal Checks.

The further flow depends on the gap mode (eepServices.rxSetPathx.GAPMx) and demodulator auto restart (eepServices.rxSetPathx.DARx and eepServices.DMCRx.DMARx) configurations. If GAPMx is set, the path that received an EOT is restarted with active WCO and continues searching for an SOT until an SOT time-out occurs. An active GAPMx setting can be useful in either RXMode or PollingMode for telegrams that have a gap with an inactive carrier between the wake-up and start of the frame pattern.

If GAPMx is not active or an SOT time-out occurs, the DARx/DMARx setting decides if the path (including the WCO and SOT time-out timer) is restarted or the reception is finished. The DARx and DMARx variables must be set in RXMode for standard applications. In PollingMode, these EEPROM settings are ignored because the function is automatically treated by the firmware.


Address Service0	Name	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1	Bit 0
0x00E0	rxSetPathA[1]	IWUPA	DARA	GAPMA	RXTEHA	—	—	—	RXMODA
0x00E2	rxSetPathB[1]	IWUPB	DARB	GAPMB	RXTEHB	—	—	—	RXMODB
0x00C0	DMCRA	DMARA	SY1TA	SASKA	DMPGA[4:0]
0x00C1	DMCRB	DMARB	SY1TB	SASKB	DMPGB[4:0]

EOT After SOT

After SOT, the actual payload data is received. During this period, the following EOT conditions can be enabled independently for path A and path B of each service in the eepServices.EOT3x variables:

Manchester coding fail (MANFEx)
Symbol timing fail (SYTFEx)
Modulation amplitude fail (AMPFEx)
Carrier fail (CARFEx)
RSSI range fail (RRFEx)
Telegram length


Address Service0	Name	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1	Bit 0
0x00CA	EOT3A	EOTBFE	RRFEA	TELREA	TMOFEA	MANFEA	SYTFEA	AMPFEA	CARFEA
0x00CB	EOT3B	EOTAFE	RRFEB	TELREB	TMOFEB	MANFEB	SYTFEB	AMPFEB	CARFEB

By default, the Manchester and symbol timing checks are activated as an EOT3 condition.

An EOT event is triggered as soon as one of the enabled checks fails. The functionality and configuration of the checks is described in detail in Telegram Settings and Signal Checks.

After an EOT, the ID check calculation is finished if activated. The further flow depends on the RX telegram end handling (eepServices.rxSetPathx.RXTEHx) configuration. If the variable is set, the receiver stays in RXMode after the EOT by restarting all active paths, otherwise IDLEMode is entered. In PollingMode, the RXTEHx setting is only evaluated after a telegram is successfully received.

If a telegram is received after a successful ID check, the firmware returns to IDLEMode independent of the RXTEHx setting. This is necessary to avoid corrupt FIFO content due to subsequent receptions with wrong IDs.


Address Service0	Name	Bit 7	Bit 6	Bit 5	Bit 4	Bit 3	Bit 2	Bit 1	Bit 0
0x00E0	rxSetPathA[1]	IWUPA	DARA	GAPMA	RXTEHA	—	—	—	RXMODA
0x00E2	rxSetPathB[1]	IWUPB	DARB	GAPMB	RXTEHB	—	—	—	RXMODB