CAN acceptance filtering (LPC4357)

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

CAN acceptance filtering (LPC4357)

493 Views
andreaskneissl
Contributor II

There are some discussion to similar subject, but they do not solve my problem.
I am using acceptance filter:

e.g. identifier  0x64   

-> all is working, when the CAN-message does not use an extended frame. With extended frame I do not get this message. So I thougt to change the identifier to 0x64 + (0x1<<30) to mark the extended frame. But this does not help to get the message.
e.g. identifier 0x1234  -> all is working. This message can be only sended as extended frame. It is not necessary to modify the identifier with (0x1<<30)
1) is there any way to get all messages from a identifier (e.g. 0x100) independed from the CAN- format 2.0a or 2.0b ?

2) If not, how I have to define the identifier to get messages sended in the extended format ?

3) Do I need two filter - one for 2.0A and the other for 2.0b ?
Thanks for any help in advance.

Andreas

Labels (1)
0 Kudos
1 Reply

295 Views
Carlos_Mendoza
NXP Employee
NXP Employee

Hi Andreas,

You could try setting the Identifier mask accordingly so the bits in the extended identifier of the message can not inhibit the match in the acceptance filtering. You can also change the Mask extend identifier to make the extended identifier bit (IDE) have no effect on acceptance filtering.


Hope it helps!

Best Regards,
Carlos Mendoza
Technical Support Engineer

0 Kudos