[3.4.1] Simulated Time issue

oozeBot

When printing a file without simulated time after a file with simulated time, the simulated time from the previous print is still displayed/used in 3.4.1.

mfs12

Hey @oozeBot, can you be more specific about howto reproduce the problem?

dc42

@oozeBot also, is this only a problem with the display on PanelDue, or does it affect DWC too?

oozeBot

@mfs12 @dc42 Sorry for the delay.

This appears to just be an issue on the PanelDue. And yes - this is the "official" build of 3.4.1, not a version we compiled. To recreate, simply start a job with simulated time.

Stop the job, and then start a job without simulated time. Note the sim'd time is the same as previous file.

dc42

@oozeBot this looks like one for @mfs12 to me.

mfs12

@oozeBot can you describe the process step by step. Which buttons do you press exactly?

I can't reproduce it.

As there's no stop button. What do you mean by stopping?

mfs12

@dc42 after debuggin this issue I get the following simulated time reported despite i hit the print button.

;dbg  150 ProcessReceivedValue(1346): rcvJobFileSimulatedTime 5261
;dbg  150 EndReceivedMessage(1029): seq job 1 DONE
;dbg  151 ProcessReceivedValue(1346): rcvJobFileSimulatedTime 5261
;dbg  151 EndReceivedMessage(1029): seq job 1 DONE
;dbg  151 main(2587): requesting volumes
N277 M409 K"volumes" F"v"*47897
;dbg  151 EndReceivedMessage(1029): seq volumes 1 DONE
N278 M409 F"d99f"*31524
;dbg  151 FindSeqByKey(604): key
;dbg  152 UpdateSeq(626): state 5 -> 7
;dbg  152 UpdateSeq(626): volumes 229 -> 233
;dbg  152 main(2587): requesting state

mfs12

according to paneldue's code any simulated time reported will be used.

chrishamm

@mfs12 I think the issue is that the simulated time isn't cleared when a new file without a simulated time is started, i.e. when it changes to null or 0.

mfs12

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

mfs12 created this issue in Duet3D/PanelDueFirmware

[3.4.1] Simulated Time issue

closed Wrong simulated time is displayed #289