AB7318-B Status for Multiple Frames Sharing the Same CAN ID
Hello,
I've been using an AB7318-B to interface with a CAN bus connected to an engine controller. This engine controller uses a data format that includes the 11-bit CAN ID followed by a MUX byte that identifies what the rest of the message contains.
In the current configuration, I have various Consume transactions configured each with multiple message frames with the constant MUX bytes as the first byte of the payload. This all works as expected, but there may be a case where some of the CAN messages are only sent when a condition is present.
For this reason, I'd like to know whether it is possible to get any sort of status within a Consume transaction to see if a particular frame is being received. The reception trigger byte or the transaction status byte doesn't really help if there are multiple frames within the transaction.
Thanks for the read.
-
Hello,
The reception trigger byte and the transaction status byte are both triggered by a change in the transaction, however, as you pointed out, they don't provide any information on the specific frame where the change occurred within the transaction.
Since only some CAN frames are concerned by this, then as a workaround for those, you can have a single frame per consume transaction...keeping in mind that you cannot setup more than 128 transactions in the configuration.
1 -
The documentation says that the first frame for each transaction must have a unique CAN ID, so wouldn't that prevent this workaround? There are plenty of instances where these frames share the same CAN ID due to the first byte being used as an identifier for the rest of the payload.
0
Please sign in to leave a comment.
Comments
2 comments