Error: G1: intermediate position outside machine limits

droftarts

@Aurimas Okay, but something is different about this machine. Are you saying the same SD card works in the other machine?

Otherwise, something is generating interference that is somehow either sending gcode, or corrupting the Gcode being sent from the SD card. Do you have a PanelDue connected, some other display, or anything else connected to serial or spi? Perhaps try disconnecting that.

Ian

T3P3Tony

@Aurimas what is different between the two machines? Is the firmware on both the toolboard and the Mainboard in sync when you try 3.5.3 and 3.6b2?

Also as @droftarts mentioned have you tried a different SD card?

Aurimas

@droftarts not sure why are you talking about the SD card - you cannot swap them out since it runs firmware of it - it is Mini5+ board.
since then I have recreated new config file and same gcode files work just fine.
So the issue is internal related to the firmware and not the SD card and/or gcode file.
I have supplied gcode file so that you guys can have a look that there is nothing causing issue in there. I have been logging those issues and there is a warning for every single move

2024-12-18 15:02:37 [warn] 6 points probed, min error -0.165, max error 0.655, mean 0.232, deviation 0.261
Height map saved to file 0:/sys/heightmap.csv
2024-12-18 15:02:49 [warn] HTTP client 192.168.1.141 login succeeded (session key 3163552733)
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:57 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:57 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:57 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:57 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:57 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:57 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:57 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:57 [warn] Error: G1: intermediate position outside machine limits

Aurimas

@T3P3Tony there is no difference - same setup, same hardware. this machine has been running non stop for few years now and suddenly getting these errors without making any changes

T3P3Tony

@Aurimas thanks for the update.

If the same machine hardware configuration with the same firmware is running the same gcode file fine. then it's most likely corruption or interference. The other machine you are testing on that has the same hardware, are you are using 3.5.4 or 3.6b2 on that as well? If it's not then change the firmware to 3.5.4 and check the same gcode still has no errors, that will rule out a firmware issue.

It's possible, that the SD card is partly corrupted (they tend to die outright though). If this was the case then swapping the SD card would rule that out.

Trying without the panel due connected would rule out that source of possible interference (however once again, if it's every more then also unlikely but worth trying.

If neither of those work then try swapping the mini5+ out and see if that resolves the issue.

droftarts

@Aurimas Do you have a daemon.g file in /sys?
I think the logging (M111) should show the Gcode sent if you turn it on, which might give a clue where it's coming from. Send M111 P3 S1 and connect a serial monitor (eg YAT) via USB.

Ian

Aurimas

@droftarts @T3P3Tony @dc42 is it possible that bed mesh compensation might be creating this issue in the latest firmware versions?
For instance if Z axis min is set to 0 and the bed mesh has to go to -0.2mm or similar - would that throw an error?

droftarts

@Aurimas I don't think you get an error if the mesh can't reach position, it just doesn't get there, though this may have changed in recent firmware. It's easy to test; disable mesh levelling. Did you try the thinks @T3P3Tony suggested?

Ian

Aurimas

@droftarts All of the suggested kindergarten stuff has been done before asking for expert help in the forum

dc42

@Aurimas what is in config-override.g?

Do you still get the error messages if you comment out the G29 line in the job file?

Aurimas

@dc42 just yesterday I had that issue, changed the Z minimum to allow negative value and it was printing since.
although it would be difficult to test your suggestion since the error didn't happen 100% of the time or in the same spot.
so my theory would be that if there is some inconsistency in the measurements at different spots of the bed it wants to compensate below minim and that is when it has fits.
It is always in the random spots on the bed (mostly well within limits) and not always - only sometimes.