{"action":"closed","issue":{"url":"https://api.github.com/repos/grbl/grbl/issues/556","repository_url":"https://api.github.com/repos/grbl/grbl","labels_url":"https://api.github.com/repos/grbl/grbl/issues/556/labels{/name}","comments_url":"https://api.github.com/repos/grbl/grbl/issues/556/comments","events_url":"https://api.github.com/repos/grbl/grbl/issues/556/events","html_url":"https://github.com/grbl/grbl/issues/556","id":51539514,"number":556,"title":"Resuming after soft limit without homing cycle","user":{"login":"matthijskooijman","id":194491,"avatar_url":"https://avatars.githubusercontent.com/u/194491?v=3","gravatar_id":"","url":"https://api.github.com/users/matthijskooijman","html_url":"https://github.com/matthijskooijman","followers_url":"https://api.github.com/users/matthijskooijman/followers","following_url":"https://api.github.com/users/matthijskooijman/following{/other_user}","gists_url":"https://api.github.com/users/matthijskooijman/gists{/gist_id}","starred_url":"https://api.github.com/users/matthijskooijman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/matthijskooijman/subscriptions","organizations_url":"https://api.github.com/users/matthijskooijman/orgs","repos_url":"https://api.github.com/users/matthijskooijman/repos","events_url":"https://api.github.com/users/matthijskooijman/events{/privacy}","received_events_url":"https://api.github.com/users/matthijskooijman/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2014-12-10T10:05:43Z","updated_at":"2016-07-06T15:56:13Z","closed_at":"2016-07-06T15:56:13Z","body":"- When soft limits are used, doing a homing cycle after startup is mandatory.\r\n- When a soft limit is triggered, a soft reset is required to continue.\r\n- After a soft reset, a homing run is again required, even though the machine position is not lost.\r\n\r\nI realize that you can do a `$X` to unlock grbl after the soft reset, but that command is really something that is marked as unsafe and shouldn't be normally used.\r\n\r\nIs there any other way to more elegantly deal with soft limits? If not, should one be added?\r\n\r\nI mostly ran into this while jogging manually, where I'd like the soft limits to prevent me from jogging too far, but then continue to respond to subsequent jogging commands. When playing a full gcode file, I guess this is different - it shouldn't just continue with the next command when the previous command would end up past the soft limits."}}
{"actor":{"display_login":"chamnit"}}