i was running a long carve on my foreman and received a communication error, i fixed the problem, restarted the machine homed the machine and went to restore the carve, it pulls the file up and jumps to where i was, but when i try to start it says “moving to position” but nothing is moving. I’ve tried power cycling and homing and reloading it several times but get the same result. looking around in here it looked like support said this was a know issue and was supposed to be resolved a few months ago, but my software is up to date
I’ve never had this work for me on my Redline controller and I’d also caution you on doing a manual move after you’ve canceled a restore if you’re using the same system.
What I’ve found that it’s almost like the motion controller gets the spacial coordinates and stores/caches them but never the command to execute the move. I’m still very new to this so don’t know the appropriate g-code commands or where in the programming cycle / what command might be missing. BUT, if you cancel the restore and execute a manual move the machine will quickly move to the cached/stored coordinates prior to executing your manual move. Depending on what’s in the way, well it seems kind’ve dicey. When working with any piece of equipment I tend to keep my important bits out of the way, but it’s a bit of shock if the restore position is a substantial distance away from the current location of the spindle.
To be fair, it does warn that the feature is in beta (at least the last time I attempted to use it) but I avoid it currently.
1 Like
yeah i noticed that same thing. after doing that i attempted to move the tool to the same coordinates it was at when the error occurred (luckily i took a picture) and still get the same problem issue of the machine not moving
1 Like