daata gathered from gcode

Tinchus

Hello. ON the DWC interface (duet3 sbc mode), on the jobs section, next to each uploaded gcode I can read some information that has been taken from the gcode, the slicer name for wxample. Apart from what it is already included on the defaul DWC interface, is there any aditional data that can be read from start.g routine for example? (in start.g I can read the object model values for example).
My objective is to read if a particular print profile is being used or not. Any ideas on how from the slicer I can generate some kind of tag that later can be detected from start.g?
Thanks in advance

T3P3Tony

@Tinchus currently what is read into the object model from a file is here:
https://github.com/Duet3D/RepRapFirmware/wiki/Object-Model-Documentation#jobfile

We have an open feature request that would do something like what you are asking for:
https://github.com/Duet3D/RepRapFirmware/issues/788

T3P3 created this issue in Duet3D/RepRapFirmware

closed Gcode comments -> Object Model #788

zapta

@Tinchus , can you inject from your slicer custom Goode that will identify the profile? E.g. setting a global variable or passing a parameter to a macro?

Tinchus

@zapta I was thinking exactly as you are thinking now I think and that was going to be my next question to @T3P3Tony too: I can produce custom gcode from the slicer in order to inject whatever I want. I was thinking on putting something like "global profile = whatever". This code will be inyected at the beggining og the gcode.

My question is this variable declaration will be read when the gcode is analized by the firmware when starting the print, and so start.g will already have access to this variable?

OwenD

@Tinchus
If you're using Prusa Slicer or Super Slicer, then you can use the placeholders to set your global variable (which you would need to define/create in config.g).
Something like this in your slicer start code.

set global.PrinterPreset = {printer_preset}

However, RRF's start.g is run before the slicer start gcode, so you would not be able to act on it there.
You'd need to call a macro further on in the slicer start gcode.