@kernelcnc you can use the logging function, or directly write to a file, to get the information in a CSV format to then load into a spreadsheet program.
Logging:
https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m929-startstop-event-logging-to-sd-card
Logging has the advantage that you can use M118 to add to the log, one its started. the disadvantage is that even in warning level, you still get entries from firmware warnings which you might not want.
Writing to a file:
https://docs.duet3d.com/en/User_manual/Reference/Gcode_meta_commands#echo-command
In this case you can append to a file with whatever information you want. Its probably the route i would take.
example:
;name the file
var file=exampleLog.txt"
; echo the file headings
echo >{var.file} "time,board temp,mcutemp"
while iterations < 100
G4 S1
echo >>{var.file} {state.time}^","^sensors.analog[0].lastReading^","^boards[1].mcuTemp.current
This is a simple example which will echo two temperatures from the object model into a text file, comma delimited, with a time stamp,
Object Model:
documentation for all the keys are herE:
https://github.com/Duet3D/RepRapFirmware/wiki/Object-Model-Documentation
As you are developing your logging code i would use the Object Model Browser in DWC (go to Plugins, Integrated Plugins, start the Object model Browser).
