{"action":"created","issue":{"url":"https://api.github.com/repos/Doodle3D/print3d/issues/36","repository_url":"https://api.github.com/repos/Doodle3D/print3d","labels_url":"https://api.github.com/repos/Doodle3D/print3d/issues/36/labels{/name}","comments_url":"https://api.github.com/repos/Doodle3D/print3d/issues/36/comments","events_url":"https://api.github.com/repos/Doodle3D/print3d/issues/36/events","html_url":"https://github.com/Doodle3D/print3d/issues/36","id":133678830,"number":36,"title":"Craftbot: print3d hangs after M104 because the response is interpreted as a M105 response","user":{"login":"companje","id":156066,"avatar_url":"https://avatars.githubusercontent.com/u/156066?v=3","gravatar_id":"","url":"https://api.github.com/users/companje","html_url":"https://github.com/companje","followers_url":"https://api.github.com/users/companje/followers","following_url":"https://api.github.com/users/companje/following{/other_user}","gists_url":"https://api.github.com/users/companje/gists{/gist_id}","starred_url":"https://api.github.com/users/companje/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/companje/subscriptions","organizations_url":"https://api.github.com/users/companje/orgs","repos_url":"https://api.github.com/users/companje/repos","events_url":"https://api.github.com/users/companje/events{/privacy}","received_events_url":"https://api.github.com/users/companje/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-02-15T10:32:18Z","updated_at":"2016-02-15T16:21:13Z","closed_at":null,"body":"The Craftbot firmware has some small differences causing print3d to hang. For example \"M104 S200\" returns ok wíth temperature which is different from Marlin. Here's (http://reprap.org/wiki/G-code#M104:_Set_Extruder_Temperature) a description of M104 on the RepRap site."},"comment":{"url":"https://api.github.com/repos/Doodle3D/print3d/issues/comments/184278920","html_url":"https://github.com/Doodle3D/print3d/issues/36#issuecomment-184278920","issue_url":"https://api.github.com/repos/Doodle3D/print3d/issues/36","id":184278920,"user":{"login":"olijf","id":5834926,"avatar_url":"https://avatars.githubusercontent.com/u/5834926?v=3","gravatar_id":"","url":"https://api.github.com/users/olijf","html_url":"https://github.com/olijf","followers_url":"https://api.github.com/users/olijf/followers","following_url":"https://api.github.com/users/olijf/following{/other_user}","gists_url":"https://api.github.com/users/olijf/gists{/gist_id}","starred_url":"https://api.github.com/users/olijf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/olijf/subscriptions","organizations_url":"https://api.github.com/users/olijf/orgs","repos_url":"https://api.github.com/users/olijf/repos","events_url":"https://api.github.com/users/olijf/events{/privacy}","received_events_url":"https://api.github.com/users/olijf/received_events","type":"User","site_admin":false},"created_at":"2016-02-15T16:21:13Z","updated_at":"2016-02-15T16:21:13Z","body":"After sending `M104 S180` at the end of the printing process it seems to stop te printer somehow. This only happens at the end of a print. \r\nDisabling the line in you printer config (in the advanced part of the printer config webpage) seems to be an easy fix and workaround.\r\n\r\nRelevant part of the log\r\n`15-02 14:50:18  [ABD] printNextLine(): 2903/2906\r\n15-02 14:50:18  [MLD] sendCode(): M104 S180\r\n15-02 14:50:18  [MLD] extractGCodeInfo()\r\n15-02 14:50:18  [MLD]   (extractGCodeInfo) targetTemperature_: 180\r\n15-02 14:50:18  [MLD] readCode(): 'ok T:230'\r\n15-02 14:50:18  [MLD] parseTemperatures(): 'ok T:230'\r\n15-02 14:50:18  [MLD]   checkTemperatureInterval_: '5000'\r\n15-02 14:50:20  [MLD] update temp()\r\n15-02 14:50:20  [MLD]   check temp\r\n15-02 14:50:20  [MLD] sendCode(): M105\r\n15-02 14:50:20  [MLD] extractGCodeInfo()\r\n15-02 14:50:20  [MLD] readCode(): 'ok T:230 B:70'` \r\n\r\nPrint3D seems to think the response `ok T:230` is a reaction to a `M105` command resulting in not returning the control to the users, forcing him to restart his doodl3d box.\r\n\r\nPlease advice users about this current workaround. "}}