• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 346 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RM46L852: Limitation on the Number of CAN Message IDs

Peman Montazemi
Intellectual 425 points
Part Number: RM46L852
Other Parts Discussed in Thread: HALCOGEN,

Hello,

The ISO 11898 CAN v1.0 communication protocol provisions for 11 bits (2,048) of message IDs. The CAN v2.0B communication protocol provisions for 29 bits (536,870,912) of message IDs. Looking at the HALCoGen v04.07.01 CAN sections, I only see 64 message configurations and associated IDs per CAN Bus, times 3 because there are 3 CAN buses on the RM46L852 Hercules MCU, that is 192 message configurations with associated message IDs. Is my understanding correct that the Hercules RM46L852 implements only 192 unique message IDs out of the 536,870,912 defined by the CAN v2.0B communication protocol?

Thanks,
Peyman

  • 0
    TI__Mastermind 21425 points

    Hello,

    hHello,
    CAN Modules got 64 message boxes on each module and each box can be activated or deactivated. The user can change the configuration of any message object or deactivate it when required ( Section 26.4.2.2 of device TRM ). You can use any ID depending on 11bit (standard) or 29bit (extended)  used.

    For example HALCoGen generates function ( canUpdateID ) that changes message box ID.