Hello,

Display - PV350
Configuration Studio 2.6.20023

I have mapped a DTC message from a non-engine controller with an SPN=3171d and FMI=15d. If a DM1 message is sent from the controller with a 3171d/15d fault AND the CM bit is "0", the PV350 Dm1.SPN variable contains 3171d and Dm1.FMI variable contains 15d as expected. If the CM bit is "1", the PV350 Dm1.SPN variable contains 65535d and the Dm1.SPN variable still contains the expected 15d. As is happens, the controller that is sending me the DM1 messages uses the older DM1 format (J1939-73 rev. SEP2006 Section 5.7.1.11 version 3) where the CM bit is set to a "1" but still follows the expected byte/bit mapping of a typical (specified) DM1 message. Am I missing something?

Thanks,

Dan

Hello Dan,

Looks like you need to adjust the variable "Dtc.FaultConversion" where:
0 = Version 1
1 = Version 2
2 = Version 3

Regards,
ksaenz

Has anybody come across this issue? Right now, it seems my only solution is to abandon the built-in Dm1 handler and write custom code to parse out all 400+ Dm1 messages from the controller.

Any help appreciated.

Dan

dmsellers wrote:Hello,

Display - PV350
Configuration Studio 2.6.20023

I have mapped a DTC message from a non-engine controller with an SPN=3171d and FMI=15d. If a DM1 message is sent from the controller with a 3171d/15d fault AND the CM bit is "0", the PV350 Dm1.SPN variable contains 3171d and Dm1.FMI variable contains 15d as expected. If the CM bit is "1", the PV350 Dm1.SPN variable contains 65535d and the Dm1.SPN variable still contains the expected 15d. As is happens, the controller that is sending me the DM1 messages uses the older DM1 format (J1939-73 rev. SEP2006 Section 5.7.1.11 version 3) where the CM bit is set to a "1" but still follows the expected byte/bit mapping of a typical (specified) DM1 message. Am I missing something?

Thanks,

Dan

Thanks ksaenz for pointing me in the right direction. Setting the conversion variable to the proper initial value did the trick. Just so I understand the documentation and/or functionality, in document 00-02-0873 Apps Ref Manual, the Diagnostic Messages Variable Description Table describes the Dtc.FaultConversion variable as being Populated by the DM App as opposed to the Developer. Does that mean the DM App can overwrite the initial value?

Thanks,

Dan

ksaenz wrote:Hello Dan,

Looks like you need to adjust the variable "Dtc.FaultConversion" where:
0 = Version 1
1 = Version 2
2 = Version 3

Regards,
ksaenz

I see that and that is a mistake. The app will not overwrite the variable.

Regards,
ksaenz

Thanks

Dan