Specifications

FL-MDS-CAB.2

MOD-MDS.1 ***Confidential*** 14 of 28

full-one-bit

(1)

two half-zero-bits

(0)

1 1 1 1 0 1 0 1 1 0 1 0 0 0 1

Figure 7. a portion of the signal from HTRC110 to the MCU which carries the tag content and the corresponding

encoding

7.4 CANopen implementation

The CAB firmware application implements a CANopen slave device according to CiA 301. Because one of

the purposes of the CAB is the fastest and more accurate carrier identification possible, the carrier

identification process is managed and communicated through PDO messages, lighter and faster than SDO

messages.

The configuration of the firmware is exposed in the Object Dictionary (for example all the HTRC110 HITAG

reader parameters are r/w entries of the OD), and can be manipulated by the Master node of the CANopen

network as needed.

7.5 PDO messages specification

7.5.1 RPDO1 messages

RPDO1 messages, received by the CAB, carry the process command to the CAB. The requested operations

are activation/deactivation of one antenna, start of the HITAG sampling time calibration procedure, and so

on.

There are some remarks about the commands:

 On the single antenna CAB commands for antenna B are not valid;

 On the double antenna CAB is possible to activate only one antenna at a time, because the HITAG

decoder chip is unique.

 To change the active antenna on the double antenna CAB the antenna currently active must be

set OFF.

RPDO1

Unused

Command

Unused