{"action":"created","issue":{"url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/3750","repository_url":"https://api.github.com/repos/MarlinFirmware/Marlin","labels_url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/3750/labels{/name}","comments_url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/3750/comments","events_url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/3750/events","html_url":"https://github.com/MarlinFirmware/Marlin/issues/3750","id":154741957,"number":3750,"title":"Random loss of MESH settings","user":{"login":"WheresWaldo","id":651136,"avatar_url":"https://avatars.githubusercontent.com/u/651136?v=3","gravatar_id":"","url":"https://api.github.com/users/WheresWaldo","html_url":"https://github.com/WheresWaldo","followers_url":"https://api.github.com/users/WheresWaldo/followers","following_url":"https://api.github.com/users/WheresWaldo/following{/other_user}","gists_url":"https://api.github.com/users/WheresWaldo/gists{/gist_id}","starred_url":"https://api.github.com/users/WheresWaldo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/WheresWaldo/subscriptions","organizations_url":"https://api.github.com/users/WheresWaldo/orgs","repos_url":"https://api.github.com/users/WheresWaldo/repos","events_url":"https://api.github.com/users/WheresWaldo/events{/privacy}","received_events_url":"https://api.github.com/users/WheresWaldo/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-05-13T15:42:27Z","updated_at":"2016-05-13T19:25:21Z","closed_at":null,"body":"There are a bunch of us using RC6 on the Robo3D forums and they have all gradually been moving to MESH bed leveling. All of us have seen strange behaviour that we cannot duplicate on a consistent basis. We do not even know how to make it happen. The issue is:\r\n\r\nAfter performing the MESH routine, either on LCD screens or in terminal mode and then saving memory locations to EEPROM, we can all get a handful of prints that work perfectly. After a period of time a subsequent print will not print properly and upon investigation it is discovered that MESH is no longer enabled.\r\n\r\nIt can usually be restored by adding M501 to the start up gcode. Typical start up code will contain G28 followed by G29 (very useful to see if MESH is enabled). Most of us have made an adjustment to add M501 between the G28 and G29 commands. It does not appear to be 100% reliable. This is spread across several users, some with printers that stay on 24/7 (like mine) and others that are completely shut off between printing sessions.\r\n\r\nWe are at a loss to figure out why MESH leveling exhibits this behaviour and thought opening a ticket, despite having little details as to the circumstances might be the best approach to resolving this issue.\r\n"},"comment":{"url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/comments/219137147","html_url":"https://github.com/MarlinFirmware/Marlin/issues/3750#issuecomment-219137147","issue_url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/3750","id":219137147,"user":{"login":"WADZoQUADZ","id":10765797,"avatar_url":"https://avatars.githubusercontent.com/u/10765797?v=3","gravatar_id":"","url":"https://api.github.com/users/WADZoQUADZ","html_url":"https://github.com/WADZoQUADZ","followers_url":"https://api.github.com/users/WADZoQUADZ/followers","following_url":"https://api.github.com/users/WADZoQUADZ/following{/other_user}","gists_url":"https://api.github.com/users/WADZoQUADZ/gists{/gist_id}","starred_url":"https://api.github.com/users/WADZoQUADZ/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/WADZoQUADZ/subscriptions","organizations_url":"https://api.github.com/users/WADZoQUADZ/orgs","repos_url":"https://api.github.com/users/WADZoQUADZ/repos","events_url":"https://api.github.com/users/WADZoQUADZ/events{/privacy}","received_events_url":"https://api.github.com/users/WADZoQUADZ/received_events","type":"User","site_admin":false},"created_at":"2016-05-13T19:25:21Z","updated_at":"2016-05-13T19:25:21Z","body":"My problem may be related. It is homing all axis fine and never prints in the air but after a random number of prints the offset moves by itself and prints to close to the bed to extrude filament. Happens even with M501 in start code. After this happens iv even tried a G29 S4 Zx.xx to adjust the offset but it doesnt move the offset at all. Only fix is to rerun bed leveling where it works for a few more prints then reverts to the same issue. "}}