Duet3 Logging with M929: incomplete entries

[too]

I am trying to enable Logging on the Duet3, and if I enable it through M929 P"logging" S1 the logfile seems inclomplete:

2019-12-02 11:30:39 Event logging started
2019-12-02 11:30:51 
2019-12-02 11:30:51 
2019-12-02 11:30:51 
2019-12-02 11:30:52 
2019-12-02 11:30:52 
2019-12-02 11:30:52 
2019-12-02 11:30:52 
2019-12-02 11:30:52 
2019-12-02 11:30:52 
2019-12-02 11:30:52 
2019-12-02 11:30:53 Finished printing file 0:/gcodes/dir_testing/one.g, print time was 0h 0m
2019-12-02 11:31:40 Warning: Firmware halted
2019-12-02 11:31:40 Warning: Firmware reset imminent
2019-12-02 11:31:40 Warning: Controller has been reset
2019-12-02 11:31:40 
2019-12-02 11:31:40 
2019-12-02 11:31:40 
2019-12-02 11:31:40 
2019-12-02 11:31:41 
2019-12-02 11:31:41 
(...)
2019-12-02 11:31:41 Warning: heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C.
(...)
2019-12-02 11:31:41 
2019-12-02 11:31:41 
2019-12-02 11:31:41 
2019-12-02 11:31:41 
2019-12-02 11:31:41 Warning: heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C.

What are all those empty entries, did I miss a step when configuring the logging?

[dc42]

I presume you are running with a RPi connected, not in standalone mode. Which version of DSF are you using?

[too]

Board: Duet 3 MB6HC (MB6HC)
DSF Version: 1.1.0.5
Firmware: RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 3.0beta12+1 (2019-11-11b1)

Board EXP3HC firmware 3.0beta1 2019-11-08b2

[too]

@dc42 any idea why that is happening? Could it be because of the pre-release RRF I am running?

[too]

Did anyone else successfully use event logging on the Duet3?

[chrishamm]

Thanks, I'll fix it in the next DSF version. If you encounter more issues with DSF, please report them at GitHub.