Echo output to file?

sinned6915

I am not sure where to post this question, this seemed to be the most logical place...

As part of my gcode macro, I want to dump a bunch system data at an event to a file, to be read/graphed later.

Is there any way to output 'echo' data to a file and append to it line by line?

I thought that M28 would write out to a file, but it seems to parse all INPUT and dump to that file, not the output.

The closest thing I have found is this bit, it writes data as filenames to be selected, downloaded and manipulated later.

M28 {"0:/macros/probe-results/"^ move.axes[2].machinePosition ^"-"^iterations}     
; Create a file, named as the probe result and iteration number in the
; 0:/macro/probe-results/ directory.  
M29 
; Close file

from this thread-

https://forum.duet3d.com/topic/18831/probe-accuracy-macro/2

EDIT: This was another that was of interest-
https://forum.duet3d.com/topic/6962/m48-measure-z-probe-repeatability-and-print-to-serial-output

I tried looking for the way the system generates the heightmap.csv but that seems to be hardcoded deep in the system, not as a user-level macro.

T3P3Tony

@sinned6915 the way to do this right now is using the logging facility:
https://duet3d.dozuki.com/Wiki/Gcode#Section_M929_Start_stop_event_logging_to_SD_card

combined with M118 to generate output for logging.

sinned6915

@t3p3tony thank you kind sir! I will delve into this.

o_lampe

@t3p3tony
can I also send variables with M118 or 'strings-only'?

Just a sidenote: I read about SD-card stuff yesterday and I thought 'all' relevant M-codes are M20-M32.
Now I see M929 is also related to SD-card, but there was no_word about it in the other M-codes. (playing hide and seek?)
OTOH, there are M33-M35 currently not used by RRF. Why not put the M929 function there?