Failed to get file info. Illegal parameter letter '_'
-
Hello all!
Just after I’ve updated My Duet3d MB 6HC firmware from V3.4.6 to V3.5.0_rc3 I get this error when I try to print or simulate a file: Failed to get file info for filename.gcode. Operation failed (Reason: Illegal parameter letter '_'. If I downgrade back to 3.4.6 the behavior reverts to normal.
Can someone shed a light on this, please. I’ve red changed log and could not figured out what’s the reason. -
Hello!
Found the culprit. Several files contained this 2 lines:
M280 P0 S160 : precautionary alarm release (reset BLTouch Probe)
and
END_PRINT
In the first one, the comment was preceded by a : instead of a ;
In the second one the comment was not preceded by ; (it was generated by the slicer – ORCA)
In the RRF/DWC V3.4.6 this was not causing any issue. But in V3.5.0_RC3 causes the error.
Hope this information may be useful for someone else. -
@Albatroz I'm glad you found what was causing the problems.
-
-
-
@Albatroz END_PRINT looks like a Klipper type macro invocation; in their infinite wisdom they decided to use bare words for this without regard for the GCode standard.
In RepRapFirmware this means the bare word is applied to the previous line as a parameter, which yields the error you observed.
You can replace END_PRINT with M0 if you want to invoke end of print behavior, which you can tweak using the 0:/sys/stop.g macro.
-
I have also replicated this issue with firmware version 3.5.4 using Orcaslicer GCODE. I was able to recover operation by toggling off "Exclude Objects"
Oddly, this was working fine for slicing normal STL files but occurred when I was running Orcaslicer's built-in pressure advance calibration tests.
-
@chrismbp said in Failed to get file info. Illegal parameter letter '_':
Exclude Objects
I'm running into the same thing when running the built-in calibration tests in Super Slicer 2.5.59.13 (which is based on Prusa Slicer).
Failed to get file info for First layer calibration_0.2mm_PETG_3m.gcode
Illegal parameter letter '_'I've searched through the GCode for the print job but cannot find the line items he had:
M280 P0 S160So...I guess that means SuperSlicer has added some other sorcery into the GCode I'm not seeing.
Anyone else running into issues with Not-So-Super-Slicer?Any help, as always is greatly appreciated!
- Cheers!
-
Illegal parameter letter '_'
Look in the file for an underscore. It looks like they are targeting Klipper exclusively and inserting the names of common klipper macros.
-
@Phaedrux said in Failed to get file info. Illegal parameter letter '_':
_
EDIT - I DID find one END_PRINT near the end, replaced it with an M0 (doh)
But there are a metric boatload ton of _ characters in that code...are they not supposed to be there?
EXAMPLES:START_PRINT EXTRUDER_TEMP=240 BED_TEMP=90
SET_PRESSURE_ADVANCE ADVANCE=0.05
SET_VELOCITY_LIMIT SQUARE_CORNER_VELOCITY=5
;WIPE_START
;WIPE_END...and so on and so forth...
Ugh. 1 of 4494 instances found
Thanks @Phaedrux , A hunting I will go!
Hopefully it's near the start of the code and not buried in the middle somewhere...
- Cheers!
-
@Electriceye those should all be comments or replaced with gcode commands.
I don't sure super slicer but you may be able to switch the output to RRF/Duet rather than Klipper?
-
That's why I was puzzled by the code output...I DID select RepRap Firmware in the output section of SuperSlicer.
Look's like it has it's mind made up on Klipper. Going to un-install and start over...something's not right there.Thanks again to all!
- Cheers!
-
@Electriceye Check the start and end gcode, Klipper commands have crept in there, that aren't controlled by the firmware type switch.
Ian