Try [c]M98 P/macros/test[/c]

@theruleslawyer Some slicer allow you to set a minimum layer time so that it will slow down the print, there may also be an option to set a percentage of minimum printing speed on top of that since a very slow print may lead to the hotend staying too long at a spot.

http://reprap.org/wiki/G-code#M581:_Configure_external_trigger
You can try using this to set up triggers and corresponding g-code to achieve what you need.

@siam I believe what it means is that the current layer number is read from the file, but it does not say the 'total number of layers' is read from the file.

If I haven't read from the wrong branch of code, here is what's in RFF for reading number of layers

unsigned int GCodeFileInfo::GetNumLayers() const noexcept
{
	if (layerHeight <= 0.0) { return 0; }
	const float nl = (firstLayerHeight > 0.0)
						? (objectHeight - firstLayerHeight)/layerHeight + 1
							: objectHeight/layerHeight;
	return (unsigned int)lrintf(max<float>(nl, 0.0));
}

@siam Are you sure? I am printing a file with 295 layers but DWC is showing total of 140 layers. I am using RRF 3.3RC2.

First layer height 0.2 and total height is 27.980, which sounds like it calculated total layers from that.

I believe RRF currently uses object height, first layer height and layer height to calculate total number of layers. However it is not incorrect for variable layer height prints.

Some slicers (at least in PrusaSlicer and Cura but not Kisslicer) can output total number of layers in the gcode file, will it be possible for RRF to parse that similar to reading other info from file?

I can now get the current layer, but it is reporting the wrong total layers since I am using variable layer height.
Found [total_layer_count] in prusaslicer placeholder but don't know what keyword RRF use to read total layers.

update: Looked through the source code and it seems that it is currently calculated instead of directly reading from the file.

@jay_s_uk
Thanks, will try that when I get home.

@phaedrux test.gcode

I haven't tried the E after ; thing yet, but everything used to work fine with the same start and end gcode.

@phaedrux The layer change portion looks like this

;LAYER_CHANGE
;Z:0.6
;HEIGHT:0.2
G1 Z0.600 F12000.000
G1 X-0.799 Y92.614
;TYPE:Perimeter
;WIDTH:0.45
G1 F1800.000

I am using RRF and DWC 3.3RC2 on my Duet 2 Wifi, but I think my problem is more related to slicer rather than the firmware.

I haven't been able to see the layer time or current printing layer for some time though the prints are fine (sliced with Prusaslicer). Have tried searching for related topic but all I found is putting E after ; in the gcode to exclude it from layer count.

I remember seeing posts on what RRF actually reads in the gcode to determine layer info but couldn't find it anymore (keyword probably too generic). Can someone tell me again what syntax is required so I can put it in the custom layer change g-code

@dc42 It's now working with 3.3RC1+1. Thank you.

@dc42 Thanks for the quick follow up.