{"action":"created","issue":{"url":"https://api.github.com/repos/gnea/grbl/issues/510","repository_url":"https://api.github.com/repos/gnea/grbl","labels_url":"https://api.github.com/repos/gnea/grbl/issues/510/labels{/name}","comments_url":"https://api.github.com/repos/gnea/grbl/issues/510/comments","events_url":"https://api.github.com/repos/gnea/grbl/issues/510/events","html_url":"https://github.com/gnea/grbl/issues/510","id":354212735,"node_id":"MDU6SXNzdWUzNTQyMTI3MzU=","number":510,"title":"Disable EEPROM functionality?","user":{"login":"oxygenic","id":1139964,"node_id":"MDQ6VXNlcjExMzk5NjQ=","avatar_url":"https://avatars1.githubusercontent.com/u/1139964?v=4","gravatar_id":"","url":"https://api.github.com/users/oxygenic","html_url":"https://github.com/oxygenic","followers_url":"https://api.github.com/users/oxygenic/followers","following_url":"https://api.github.com/users/oxygenic/following{/other_user}","gists_url":"https://api.github.com/users/oxygenic/gists{/gist_id}","starred_url":"https://api.github.com/users/oxygenic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oxygenic/subscriptions","organizations_url":"https://api.github.com/users/oxygenic/orgs","repos_url":"https://api.github.com/users/oxygenic/repos","events_url":"https://api.github.com/users/oxygenic/events{/privacy}","received_events_url":"https://api.github.com/users/oxygenic/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":47,"created_at":"2018-08-27T07:37:15Z","updated_at":"2018-09-13T07:31:35Z","closed_at":"2018-08-27T18:00:10Z","author_association":"NONE","body":"It seems for me, GRBL become instable whenever some EEPROM-accesses / setting of $-parameters is involved - also in case of strict handshake, means when only one $-command is sent and then the application waits until the related response arrives.\r\n\r\nFor my application it is no problem to send all $-parameters on start-up, so my question/feature request: is there a (compile-time) option to disable all EEPROM-stuff and to keep these parameters in RAM only?\r\n\r\nOr any hints where to implement something like this?\r\n"},"comment":{"url":"https://api.github.com/repos/gnea/grbl/issues/comments/420911755","html_url":"https://github.com/gnea/grbl/issues/510#issuecomment-420911755","issue_url":"https://api.github.com/repos/gnea/grbl/issues/510","id":420911755,"node_id":"MDEyOklzc3VlQ29tbWVudDQyMDkxMTc1NQ==","user":{"login":"oxygenic","id":1139964,"node_id":"MDQ6VXNlcjExMzk5NjQ=","avatar_url":"https://avatars1.githubusercontent.com/u/1139964?v=4","gravatar_id":"","url":"https://api.github.com/users/oxygenic","html_url":"https://github.com/oxygenic","followers_url":"https://api.github.com/users/oxygenic/followers","following_url":"https://api.github.com/users/oxygenic/following{/other_user}","gists_url":"https://api.github.com/users/oxygenic/gists{/gist_id}","starred_url":"https://api.github.com/users/oxygenic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oxygenic/subscriptions","organizations_url":"https://api.github.com/users/oxygenic/orgs","repos_url":"https://api.github.com/users/oxygenic/repos","events_url":"https://api.github.com/users/oxygenic/events{/privacy}","received_events_url":"https://api.github.com/users/oxygenic/received_events","type":"User","site_admin":false},"created_at":"2018-09-13T07:31:35Z","updated_at":"2018-09-13T07:31:35Z","author_association":"NONE","body":"Short update: when I send something like\r\n\r\nF3000\r\nG1X10Y20Z30\r\nG1X0Y0Z0\r\n\r\nI sometimes can see some kind of memory leak (values returned by $$ contain random crap).\r\n\r\nIt does not seem to be caused by the relative high value of \"F3000\", the same happens with \"F300\" or \"F30\". More than this it seems to happen only after the last command. Means when I send\r\n\r\nG1X10Y20Z30\r\nG1X0Y0Z0\r\n\r\nmemory is corrupted after the \"G1X0Y0Z0\". When I send \r\n\r\nG1X10Y20Z30\r\n\r\nand then wait for the end, it is corrupted at this point. So this fits to my previous operation mode where I send one command and then wait until motion is finished - and sometimes get in troubles afterwards. Not sure yet if a permanent sending of \"?\" has an influence on this..."}}
{"actor":{"display_login":"oxygenic"}}