Is your feature request related to a problem? Please describe.
A failed G28 homing makes the machine think that the homing file is still active. This will cause the next G28 homing to fail with an error message: "Error : G28 cannot be used inside a homing file".
The above error message is misleading as the machine is actually in the state idle.
The suspicion is there is abort used inside the homing file , so the homing failed when one of the condition was not met.
Describe the solution you propose.
Clear the flag which thinks that the homing file is still active when a homing failed and exited the macro. Especially if the machine state is idle!
Describe alternatives you've considered
For now, i have fixed this problem by calling the M98 P"homeall.g" instead of doing it with G28. In this case the above mentioned problem never occurs.
Provide any additional context or information.
Ex. Photos, mockups, etc.
Is your feature request related to a problem? Please describe.
A failed G28 homing makes the machine think that the homing file is still active. This will cause the next G28 homing to fail with an error message: "Error : G28 cannot be used inside a homing file".
The above error message is misleading as the machine is actually in the state idle.
The suspicion is there is abort used inside the homing file , so the homing failed when one of the condition was not met.
Describe the solution you propose.
Clear the flag which thinks that the homing file is still active when a homing failed and exited the macro. Especially if the machine state is idle!
Describe alternatives you've considered
For now, i have fixed this problem by calling the M98 P"homeall.g" instead of doing it with G28. In this case the above mentioned problem never occurs.
Provide any additional context or information.
Ex. Photos, mockups, etc.