How to use CAN 2.0A/2.0B for S12ZVC?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How to use CAN 2.0A/2.0B for S12ZVC?

Jump to solution
892 Views
aaronlee
Contributor V

Hi,

I use CAN 2.0A on S12ZVCA. It work fine @ 250kbps CAN and 12MHz crystal. (My code as attachments, The example code follow MSCAN on the MagniV (AN4975) with software.)

Now, I want to use CAN 2.0A and 2.0B together.

Do you have example code?

Best Regards,

Aaron

Tags (1)
0 Kudos
1 Solution
537 Views
lama
NXP TechSupport
NXP TechSupport

Hi,

CAN 2.A and 2.0B compatibility:

Source: https://www.opal-rt.com/KMP/index.php?/article/AA-00691/0/Opal-RT-CAN-solution-compatibility-with-CA...

CAN specifies two different formats for the Arbitration ID parameter. The standard message format uses a 11-bit ID, while the extended message format uses a 29-bit ID.

CAN 2.0A                 - specifies standard message format only (extended messages are treated as an error)
CAN 2.0B passive    - handles standard messages and ignores extended messages
CAN 2.0B active      - handles both standard and extended message formats

Opal-RT's hardware and software is 2.0B active compliant: it supports both standard (11-bit) and extended (29-bit) Arbitration IDs.

The following table displays the different versions of the CAN standard, the year they were adopted, and a brief synopsis of the changes made with each revision.

Version    Year       Additions
1.0           1995       Original CAN standard
1.1           1987       Respecified bit timing requirements
1.2           1990       Increased oscillator tolerance
2.0A         1991       Same as version 1.2
2.0B         1991       Introduced optional extended frame

 

The example for https://www.nxp.com/docs/en/application-note/AN4975.pdf

Together with https://www.nxp.com/docs/en/application-note-software/AN4975SW.zip

Simple example for CAN standard ID and loopback mode is attached.

best regards,

Ladislav

View solution in original post

0 Kudos
1 Reply
538 Views
lama
NXP TechSupport
NXP TechSupport

Hi,

CAN 2.A and 2.0B compatibility:

Source: https://www.opal-rt.com/KMP/index.php?/article/AA-00691/0/Opal-RT-CAN-solution-compatibility-with-CA...

CAN specifies two different formats for the Arbitration ID parameter. The standard message format uses a 11-bit ID, while the extended message format uses a 29-bit ID.

CAN 2.0A                 - specifies standard message format only (extended messages are treated as an error)
CAN 2.0B passive    - handles standard messages and ignores extended messages
CAN 2.0B active      - handles both standard and extended message formats

Opal-RT's hardware and software is 2.0B active compliant: it supports both standard (11-bit) and extended (29-bit) Arbitration IDs.

The following table displays the different versions of the CAN standard, the year they were adopted, and a brief synopsis of the changes made with each revision.

Version    Year       Additions
1.0           1995       Original CAN standard
1.1           1987       Respecified bit timing requirements
1.2           1990       Increased oscillator tolerance
2.0A         1991       Same as version 1.2
2.0B         1991       Introduced optional extended frame

 

The example for https://www.nxp.com/docs/en/application-note/AN4975.pdf

Together with https://www.nxp.com/docs/en/application-note-software/AN4975SW.zip

Simple example for CAN standard ID and loopback mode is attached.

best regards,

Ladislav

0 Kudos