M291 messages ignored by PanelDue

PaulHew

@mfs12
Thanks for your hard work.

I tested your script as is and it does as we expect.

Changed mine to look like yours and it still shutsdown the Pi after hitting cancel.

G4 P500
M291 R"** SHUTDOWN **" P" Are you sure you want to SHUTDOWN the printer and Pi?" S3
G4 S3
M400
M106 P10 S0
M7722



;G4 P500
;M291 P"S3 message" S3
;G4 S3
;M400
;M291 P"ok pressed" S1

I honestly do not think it is a PanelDue issue but RRF or DWC.
I re-opened my previous issue because something this simple should just work!

Regards,
Paul

mfs12

@flobler I think i understand what is happening.

PD has only one popup to display at a time. This means M291 S1 messages are directly overwritten by the following M291 S3 message. And as PD is polling quite slowly it doesn't see the other message.

You could make sleep command of 30s (i think it's G4 S30) followed by M400 after M291 S1 call and see what happens.

M291 S3 P"S3 message"
M291 S1 P"S1 message"
G4 S30
M400
M291 S3 P"S3 message 2"

mfs12

@paulhew sorry, i have no idea why this is failing... but i agree with you paneldue itself doesn't fail here. At least it looks like it.

flobler

@mfs12 sorry again for my late reply, I am currently moving and it is difficult to manage work, the move and these topics at the same time.

I tried what you suggested, but all it does is delaying whatever comes after the messages by 30 seconds and still does not display the second message (M291 S1) on the PanelDue (only on DWC).

mfs12

@flobler, "S1 message" is missed. This happens due to paneldue's polling interval of 500ms. If it's reduced to 250ms the "S1 message" is more likely seen. But same issue applies to DWC if a state update of the OM is missed then the message is lost.

@dc42 can this be improved on RRF side somehow so message are always catched?

mfs12

@flobler all messages which don't require any confirmation may be overwritten by any following message.

So if you want to be sure to see a S1 or S0 message which may be followed by another message you best add a timeout after the message, i.e. "G4 S20".

flobler

@mfs12 I tried that previously in this thread and it did not solve the problem but just caused a 20 second wait with the S1 message still not displaying on the PanelDue.

@flobler said in M291 messages ignored by PanelDue:

@mfs12 sorry again for my late reply, I am currently moving and it is difficult to manage work, the move and these topics at the same time.

I tried what you suggested, but all it does is delaying whatever comes after the messages by 30 seconds and still does not display the second message (M291 S1) on the PanelDue (only on DWC).

I just re-tried and saw the same behavior. This is what I did:

Test

M291 P"Do you want to load FILAMENT now? Press OK to continue or CANCEL to abort!" S3 ; requires user input to start the filament loading procedure
M291 P"Loading FILAMENT..." S1 T60                                                    ; message confirming that filament is being loaded
M291 P"Do you want to load FILAMENT now? Press OK to continue or CANCEL to abort!" S3 ; requires user input to start the filament loading procedure

The initial S3 messages pops-up on the PanelDue, I press OK and the following S1 message is being ignored. Instead both PanelDue and DWC direclty jump to the next S3 message.

Test

M291 P"Do you want to load FILAMENT now? Press OK to continue or CANCEL to abort!" S3 ; requires user input to start the filament loading procedure
M291 P"Loading FILAMENT..." S1 T60                                                    ; message confirming that filament is being loaded
G4 S30
M400
M291 P"Do you want to load FILAMENT now? Press OK to continue or CANCEL to abort!" S3 ; requires user input to start the filament loading procedure

The initial S3 message pops-up on the PanelDue, I press OK and then the following S1 message is only displayed in DWC and not on PanelDue, after 30 seconds the next S3 message pops-up on both PanelDue and DWC.

Any other ideas? I am setting this back to "unresolved".

Thank you for your help

mfs12

@flobler, i ran the following test

If macro is launched from dwc the s1 message is displayed on paneldue.
If macro is launched from paneldue the s1 message is not displayed on paneldue.

M291 S3 P"S3 message"
M291 S1 P"S1 message"
G4 S5
M400
M291 S3 P"S3 message 2"

Log from paneldue when launched from DWC

;dbg   19 FindSeqByKey(555): key
;dbg   19 UpdateSeq(577): state 70 -> 71
;dbg   19 UpdateSeq(577): volumes 73 -> 74
;dbg   19 main(2375): requesting state
N44 M409 K"state" F"vn"*124
;dbg   19 ProcessReceivedValue(1563): message S3 message
;dbg   19 main(2248): message updated last action time
;dbg   20 EndReceivedMessage(973): seq state 1 DONE
;dbg   20 main(2375): requesting volumes
N45 M409 K"volumes" F"v"*31
;dbg   20 EndReceivedMessage(973): seq volumes 1 DONE
N46 M409 F"d99f"*120
;dbg   20 FindSeqByKey(555): key
;dbg   21 UpdateSeq(577): state 71 -> 73
;dbg   21 main(2375): requesting state
N47 M409 K"state" F"vn"*127
;dbg   21 ProcessReceivedValue(1563): message S1 message
;dbg   21 main(2248): message updated last action time
;dbg   21 EndReceivedMessage(973): seq state 1 DONE
N48 M409 F"d99f"*118
;dbg   21 FindSeqByKey(555): key
N49 M409 F"d99f"*119
;dbg   22 FindSeqByKey(555): key
N50 M409 F"d99f"*127
;dbg   22 FindSeqByKey(555): key
N51 M409 F"d99f"*126
;dbg   23 FindSeqByKey(555): key
N52 M409 F"d99f"*125
;dbg   23 FindSeqByKey(555): key
N53 M409 F"d99f"*124
;dbg   24 FindSeqByKey(555): key
N54 M409 F"d99f"*123
;dbg   24 FindSeqByKey(555): key
N55 M409 F"d99f"*122
;dbg   25 FindSeqByKey(555): key
N56 M409 F"d99f"*121
;dbg   25 FindSeqByKey(555): key
;dbg   26 UpdateSeq(577): state 73 -> 74
;dbg   26 main(2375): requesting state
N57 M409 K"state" F"vn"*126
;dbg   26 ProcessReceivedValue(1563): message S3 message 2
;dbg   26 main(2248): message updated last action time
;dbg   26 EndReceivedMessage(973): seq state 1 DONE

Log from paneldue when launched from PanelDue

N239 M98 P"0:/macros/test-m291-s3s1-sleep.g"*41
N240 M409 F"d99f"*76
;dbg  117 FindSeqByKey(555): key
;dbg  118 UpdateSeq(577): state 75 -> 76
;dbg  118 UpdateSeq(577): volumes 75 -> 76
;dbg  118 main(2375): requesting state
N241 M409 K"state" F"vn"*75
;dbg  118 ProcessReceivedValue(1563): message S3 message
;dbg  118 main(2248): message updated last action time
;dbg  118 EndReceivedMessage(973): seq state 1 DONE
;dbg  118 main(2375): requesting volumes
N242 M409 K"volumes" F"v"*42
;dbg  119 EndReceivedMessage(973): seq volumes 1 DONE
N243 M409 F"d99f"*79
;dbg  119 FindSeqByKey(555): key
N244 M409 F"d99f"*72
;dbg  120 FindSeqByKey(555): key
N245 M409 F"d99f"*73
;dbg  120 FindSeqByKey(555): key
N246 M409 F"d99f"*74
;dbg  121 FindSeqByKey(555): key
N247 M409 F"d99f"*75
;dbg  121 FindSeqByKey(555): key
N248 M409 F"d99f"*68
;dbg  122 FindSeqByKey(555): key
N249 M409 F"d99f"*69
;dbg  122 FindSeqByKey(555): key
;dbg  122 main(2229): delta 4703 state 1
;dbg  122 main(2231): pressed
N250 M292 P0*109
N251 M409 F"d99f"*76
;dbg  123 FindSeqByKey(555): key
;dbg  123 UpdateSeq(577): state 76 -> 78
;dbg  123 main(2375): requesting state
N252 M409 K"state" F"vn"*73
;dbg  124 FindSeqByKey(555): key
;dbg  124 main(2375): requesting state
N253 M409 K"state" F"vn"*72
;dbg  125 FindSeqByKey(555): key
;dbg  125 main(2375): requesting state
N254 M409 K"state" F"vn"*79
;dbg  126 FindSeqByKey(555): key
;dbg  126 main(2375): requesting state
N255 M409 K"state" F"vn"*78
;dbg  127 FindSeqByKey(555): key
;dbg  127 main(2375): requesting state
N256 M409 K"state" F"vn"*77
;dbg  127 FindSeqByKey(555): key
;dbg  128 UpdateSeq(577): state 78 -> 79
;dbg  128 ProcessReceivedValue(1563): message S3 message 2
;dbg  128 main(2248): message updated last action time
;dbg  128 EndReceivedMessage(973): seq state 1 DONE
;dbg  128 ProcessReceivedValue(1563): message S3 message 2

To conclude, the sequence number on RRF side increment and when the state seq request is executed the S1 message is not delivered from RRF. To me it looks like an issue on RRF side.

I have to talk to @dc42 about this.

mfs12

@flobler, good news. It looks like we understood the problem so there might be a solution in reach.

flobler

@mfs12 awesome, thank you very much for investigating!

flobler

@mfs12 Is this the issue we are talking about here?
https://github.com/Duet3D/PanelDueFirmware/issues/239

dc42 created this issue in Duet3D/PanelDueFirmware

closed M291 S3 message not cleared #239

mfs12

@flobler said in M291 messages ignored by PanelDue:

https://github.com/Duet3D/PanelDueFirmware/issues/239

no, this is another issue.

flobler

@mfs12 it looks like upgrading everything to 3.4.0 fixed this for me and all messages are now displayed as they should thank you very much for your help along the way!!!