You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While setting up the spindle speed map, the machine would sometimes take several seconds, up to a minute, before responding to spindle commands.
When running some simple g-code using a gcode sender via IP, there were long pauses between commands towards the end of the file. The pauses seem to get worse towards the end of the file with pause times of around 4-5 minutes between each and every command.
This seems to be a known issue. (link the issue here)
To work around this, g-code files should be run either directly from SD card or via USB if using a g-code sender.
The text was updated successfully, but these errors were encountered:
While setting up the spindle speed map, the machine would sometimes take several seconds, up to a minute, before responding to spindle commands.
When running some simple g-code using a gcode sender via IP, there were long pauses between commands towards the end of the file. The pauses seem to get worse towards the end of the file with pause times of around 4-5 minutes between each and every command.
This seems to be a known issue. (link the issue here)
To work around this, g-code files should be run either directly from SD card or via USB if using a g-code sender.
The text was updated successfully, but these errors were encountered: