Hi,

I was wondering if an example exists on receiving a free form data string message. I'm a little unclear about a couple of things for my application.

First, the PGN (Hex) field has space for 6 characters. Which of the 8 characters in an extended CAN identifier should I use? Priority, PGN, Receiving Node, Sending Node?

Second, My data string message is only 1, 8 byte message, a single packet, so do I just leave the continue packet blank and everything will still work? Or is this application only for multi-packet messages?

Finally, My data message does not have an identifier or sequence byte since it is not multi-packet, so can I leave the sequence byte at position 0 and length 0?

If this application only works for multiframe messages, then is my only option to use the scripting functions instead? I'm trying my best to take advantage of what's already built in rather than write something new.

Thanks,
Mike Smith, Pilot Systems

Hello Pilotsystems,

I am attaching some screen captures as examples of how one of our leading custom configuration developer handles messages containing string data.

The PGN is the PDU Format, PDU Specific and Source Address bytes of the identifier.

If you have the Standard Multi-Packet Compatible checked and the data is eight bytes or less, the message will not be handled as a multi-packet. By checking it, you can easily use a script similar to the example to parse the data from the message buffer to a string data variable.
Hope this can get you started.

This looks great! Thanks! I should be able to figure it out from this.