DM1 Message Response of Simulated Nodes

[benboniface]

When setting up multiple simulated nodes under a single instance of the J1939 Custom Device, we have observed that if the simulated nodes are not added to the Custom Device in the numerical order of their Address, then upon request of the DM1 message the DM1 response is seen from the wrong simulated node.

For Example if we add in three simulated devices with the following addresses:
xF2
x9D
xF1

And add DTCs to these nodes and send a request for the DM1 messages on x9D, we will see a DM1 response from address xF2

If these nodes are added back in to the System Definition file in order
x9D
xF1
xF2

And we repeat the earlier test, we see a response from the correct address.

We also noticed when sending requests from the workspace control to the simulated node address for the DM1 message that the J1939 request frame has the wrong priority, 7, instead of 6. This leads to an incorrect CAN ID being broadcast by XNET and as a result we do not see any response from the simulated node. Instead we needed to send the request from a third party tool.

Lastly, the DM1 messages do not abide by the J1939 standard in regards to DM1 messages in ways

1. If DM1 message is less than 8 bytes the custom device does not pad the data packet as it should
2. When the node has no active DTCs it responds with no data as opposed to the following 8 bytes it should reply with "00 FF 00 00 00 00 FF FF"
3. There is no way to set the DM1 message to broadcast at it's regular 1 second interval