Any sort of command history available with SBC?

tristanryerparke

I'm having trouble setting up M28/M559 on my Duet36HC + Pi4.
The goal is to track issues during jobs/macros that are occurring while I am not connected to DWC. In a perfect world I would like to see every command sent (including those inside a macro) in a text file so that I can debug the issue.
In my config.g I have the following lines:

M28 "0:/sys/history/history1.gco"
M559 P"0:/sys/history/history2.gco"

I am using M559 because M28 seems only to write the file, and not to fill it with any lines of code that are sent via macro, file or terminal. This post seemed to be a fix/alternative:
https://forum.duet3d.com/topic/17991/m28-writing-file-with-comments-possible
The M559 command seems to do nothing at all.

Does anybody with a duet3 + RPI have some kind of command history working?
Could I use an SD card in the duet3 slot instead of SBC internal storage?
Any workaround/fix/help would be appreciated.

M112:

=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3beta3.1 (2021-04-26 11:17:17) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J9D6-3S46R-KU2AD
Used output buffers: 1 of 40 (20 max)
=== RTOS ===
Static ram: 150600
Dynamic ram: 62152 of which 0 recycled
Never used RAM 95440, free system stack 126 words
Tasks: SBC(ready,6.3%,298) HEAT(delaying,0.0%,355) Move(notifyWait,0.0%,176) CanReceiv(notifyWait,0.0%,798) CanSender(notifyWait,0.0%,359) CanClock(delaying,0.0%,341) TMC(notifyWait,8.2%,59) MAIN(running,85.4%,1105) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:01:01 ago, cause: software
Last software reset at 2021-04-25 06:31, reason: User, none spinning, available RAM 92584, slot 1
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
Step timer max interval 133
MCU temperature: min 57.5, current 58.0, max 58.0
Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, reads 26238, writes 9 timeouts 0, SG min/max 0/605
Driver 1: position 0, standstill, reads 26238, writes 9 timeouts 0, SG min/max 0/555
Driver 2: position 0, standstill, reads 26242, writes 5 timeouts 0, SG min/max 0/87
Driver 3: position 0, standstill, reads 26241, writes 5 timeouts 0, SG min/max 0/176
Driver 4: position -1882, standstill, reads 26241, writes 5 timeouts 0, SG min/max 0/29
Driver 5: position 0, standstill, reads 26247, writes 0 timeouts 0, SG min/max not available
Date/time: 2021-04-25 06:32:48
Slowest loop: 97.13ms; fastest: 0.03ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 13169ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 18, completed moves 18, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 3], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue* is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 287, send timeouts 0, received 18, lost 0, longest wait 1ms for reply type 6042, peak Tx sync delay 5, free buffers 49 (min 48)
=== SBC interface ===
State: 0, failed transfers: 0
Last transfer: 1ms ago
RX/TX seq numbers: 2062/2063
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x2c95c
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.3-b3
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 35.18
Codes per second: 1.97
Maximum length of RX/TX data transfers: 4967/716

Thanks,
T

Serbitar

You can change the log level of duetcontrolserver to debug (/opt/dsf/conf/config,json. That will cause it to log every gcode that is run.
You can view the logs with
sudo journalctl --unit duetcontrolserver

tristanryerparke

@serbitar thanks!