Replies: 1 comment
-
Hello there. The short answer is yes, proprietary messaging formats are supported. The long answer is: yes, but because two or more manufacturers may use the same Proprietary B PGNs, and of course everyone shares the Proprietary A range with completely different message contents, you have to do the parsing yourself based on the message definition of the message you want to use, and the partner you want to communicate with. But, the CAN stack will of course deliver to you those messages and let you send those messages with full transport layer support up to the max that the Extended Transport Protocol allows. I suggest checking out the tutorial website, as it explains the basics you'll need to do this, and actually even the first example program sends a Proprietary A message to the broadcast address. For a more practical example though, let's say hypothetically I have a device where if I send it the Proprietary A PGN (just 0xEF00 as the can stack resolves the 00 to the proper destination automatically for you) with some multiplexer, it sends me back some message with content you want to receive. Assuming you've set up your partner control function to match the target device (see the Adding a Destination Tutorial for more info on that) and assuming you populate a buffer with the message contents you want to transmit with the Proprietary A message, then all you would need to do is send the message like this:
And that will send the message you constructed. I hope this helps! |
Beta Was this translation helpful? Give feedback.
-
Hello.
Is stack support proprietary message protocol?
Beta Was this translation helpful? Give feedback.
All reactions