Issue with PDU1 frame addressing
I'm trying to configure a encoder at SA=0x20. I'm having an issue implementing a J1939-21 CMDT exchange in IQAN. As part of the
configuration handshake the encoder sends a CTS (Clear To Send) frame to me (SA=0x01) to let me know that it is ready to receive
the new encoder configuration data. IQAN will NOT let me set the address of this frame as required. I've been able to configure the
encoder, as needed, but only if I skip receiving the CTS frame. I did note that I'm able to set the address for 60416 to SA=0x20, as required by the RTS (Request To Send) frame, so it seems
the the PDU1 handler (inside IQAN firmware) is partially working. Just not when the DA is set to 0x01.

Here is a screen snip from a logfile showing a successful configuration, using my IQAN test app, even though IQAN is not able to receive the CTS frame (encircled in RED).

Here is a more detailed info and a view of the configuration handshake acquired using Vector CANoe.
The configuration data is - as specified in document SAE J1939/21 – transmitted via J1939 CMDT transfer. A configuration is in principle possible also without J1939 stack or tool.
The transmission via EncoderSetup PG with listing of the raw frames on the bus starts atmoment 24.920140 and is concluded at moment 24.923872.
To this purpose, you must sent the frames marked with Dir: "Tx" (RTS and Sequence 1-3) andyou receive as an answer the two frames marked with "Rx" (CTS and EoMA).
After the configuration, how the encoder starts sending measured data can be seen as from moment 24.941659 ("EncoderPositionSpeedValues"

I have a fully functional test app built with IQANdesign 6.08.32 using a MD4-5 but can't attach it to this post as it's 6 mB over the 20 Mb limit. It doesn't work when built with IQANdesign7.05 either
I'm open to any, and all suggestions.
Thanks,
Mark
Customer support service by UserEcho
Here's a stripped version of my Test AppKubler Encoder 6.08.32 Test App_Stripped.idsx