15.08.2013 Views

DESIGN OF A CUSTOM ASIC INCORPORATING CAN™ AND 1 ...

DESIGN OF A CUSTOM ASIC INCORPORATING CAN™ AND 1 ...

DESIGN OF A CUSTOM ASIC INCORPORATING CAN™ AND 1 ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

are compared to the values contained in these registers; see example below and also Figure 4.6.<br />

Thus always groups of eight identifiers can be defined to be accepted for any node.<br />

Example: MSB LSB<br />

The Acceptance Code Register (ACR) contains: 0 1 1 1 0 0 1 0<br />

The Acceptance Mask Register (AMR) contains: 0 0 1 1 1 0 0 0<br />

Messages with the following 11 – bit identifiers are accepted 0 1 x x x 0 1 0 x x x<br />

(x = don’t care) ID.10 ID.0<br />

Figure 4.6 CAN Node Message Acceptance Filtering [48].<br />

At the bit positions containing a “1” in the AMR, any value is allowed in the composition<br />

of the identifier. The AMR defines the bit positions, which are relevant for the comparison (0 =<br />

relevant, 1 = not relevant). The same is valid for the three least significant bits. Thus 64<br />

different identifiers are accepted in this example. The other bit positions must be equal to the<br />

values in the ACR. For accepting a message all relevant received bits have to match the<br />

respective bits in the ACR. Although using acceptance filters and acceptance masks does not<br />

provide a CAN node with a physical address, it does however provide a means to limit what<br />

types of messages and how many will be received into an individual CAN node’s receive<br />

buffers.<br />

89

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!