Hello,

1. Both PV780 and PV450 in which Murphy standard configuration Ver. 2.7 is installed cannot receive "No Stored Codes" of DM2. Please advise how to receive the "No Stored Codes".

2. Regarding the MPY std configuration Ver. 2.3, the displays sometimes cannot receive the "No Stored Codes" of DM2 as well as Ver. 2.7. The case is when any DM2 diagnostic information has not been broadcasted. After the display has received some DM2 diag. just one time, it can receive the "No stored Codes" correctly. It seems that the attached programming flow of "DM2.Receiving" does not work correctly. Please advise how to fix it.

Thank you,
tshiii

Something you might check in the configuration for the Diagnostic Messages Application if the "Always Allow No Codes Response" is checked. Are you expecting a No Codes response (SPN 0, FMI 0) to return from your controller?
The Library DTC setup could be dropping SPN 0, FMI 0.

Hello Boyce,

Thank you for your reply. The question 1 (Ver. 2.7) has been fixed.

How about the question 2 (Ver. 2.3)?

DM2 flow of State Machines was customized as attached but DM2 Receiving flow does not work correctly.

Please advise which points need to be changed to fix the problem.

Thank you,
tshiii

I'm glad it is working right in PV2.7 but it looks like bad news for PV2.3. It doesn't look like a state machine problem, it appears there is a bug in the DM2 firmware in handling the No Stored Codes response. Because of the bug it will show status Timeout when SPI 0 FMI 0 is dropped and status OK and SPN 0 FMI 0 in the diagnostic message list when SPI 0 FMI 0 is not dropped.

I will add this bug to the programming backlog but I can not say when it will be worked on and a patch provided.

Well I looked at your message a little more and may suggest something. If you are just wanting to replace the Timeout message with a No Stored Codes message you can do the following:
I changed the Requesting state to timeout to the No Stored Codes state since it did not transition to the Receiving state. This may be the only thing that was keeping it from working for you. The No Stored Codes state just sets the DM2Status to 5.
Added the NO STORED CODES string.

Hello Boyce,

Thank you for the suggestion.

Our customer tried that but it did not work correctly as follows.

1) TIMEOUT is displayed when NO STORED CODES is received
2) NO STORED CODES is displayed during no response.

It seems that these matters are displayed alternately.

The problem is that the flow from REQUESTING to RECEIVING does work correctly if any DM2 diagnostic information has not been broadcasted. As I explained before, it becomes working correctly after DM2 diag is broadcasted just one time.

Is it a bug in the DM2 firmware and there is no solution at this moment as you mentioned?

Thank you,
tshiii

Yes, that would make sense. What you could do is have both the REQUESTING and RECEIVING states do the Dm2.VariablesWriteFail event to the No Stored Codes state. That would replace the TIMEOUT message with the NO STORED CODES message. The NO STORED CODES message would show when there was an actual SPN 0 FMI 0 or when no controllers responded. I would say that version 2.3 did not implement the No Stored Codes message. The Diagnostic Message application was rewritten in version 2.7 and it implemented the No Stored Codes message. At any case, I did enter the No Stored Codes message support for version 2.3 in the developers backlog. I can't promise when it will be worked on, but there will be a patch release with this fix.

Hello Boyce,

Thank you for your support!

tshiii