{"action":"created","issue":{"url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/15674","repository_url":"https://api.github.com/repos/MarlinFirmware/Marlin","labels_url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/15674/labels{/name}","comments_url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/15674/comments","events_url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/15674/events","html_url":"https://github.com/MarlinFirmware/Marlin/issues/15674","id":512754139,"node_id":"MDU6SXNzdWU1MTI3NTQxMzk=","number":15674,"title":"[FR] RUNOUT big bugs ' in big printing' [Reflexions/Discussions]","user":{"login":"studiodyne","id":42887851,"node_id":"MDQ6VXNlcjQyODg3ODUx","avatar_url":"https://avatars3.githubusercontent.com/u/42887851?v=4","gravatar_id":"","url":"https://api.github.com/users/studiodyne","html_url":"https://github.com/studiodyne","followers_url":"https://api.github.com/users/studiodyne/followers","following_url":"https://api.github.com/users/studiodyne/following{/other_user}","gists_url":"https://api.github.com/users/studiodyne/gists{/gist_id}","starred_url":"https://api.github.com/users/studiodyne/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/studiodyne/subscriptions","organizations_url":"https://api.github.com/users/studiodyne/orgs","repos_url":"https://api.github.com/users/studiodyne/repos","events_url":"https://api.github.com/users/studiodyne/events{/privacy}","received_events_url":"https://api.github.com/users/studiodyne/received_events","type":"User","site_admin":false},"labels":[{"id":91737852,"node_id":"MDU6TGFiZWw5MTczNzg1Mg==","url":"https://api.github.com/repos/MarlinFirmware/Marlin/labels/T:%20Feature%20Request","name":"T: Feature Request","color":"1d76db","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2019-10-25T23:10:36Z","updated_at":"2019-10-26T15:23:33Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"**RUNOUT SYSTEM have so many bugs , but not very important for little printers , but for a MODIX 60/120, it's dramatic**\r\n\r\n- Motion sensor , is alone , but , like switch sensors , it's possible that they are multiples\r\n- Motion sensor is under ' RUNOUT DISTANCE DEFINE'  why ?  if we want to use it as jam detection ?\r\n\r\n- Runout bugs:\r\n  - RUnoutSwitch polling after block completed => if runoutdistance=25 , planner have made 24 , and the next planner block is 20 ' big outline with 0.8 nozzle ' , print dye\r\n  - Motion sensors  ... same issue\r\n  - If runout switch trig while a block not completed , impossible to know what distance of filament remains , (in little printing , no problem , but in big size printing , print dye ) \r\n  - If motions sensors have no regular polling , then you can sometimes have repetition of no change , the motion sensor must be checked every     1 pulse <Polling Motion sensor< 2 pulses , if not , impossible to have a serious detection , it's possible to have low state 1000x and no detection \r\n\r\nSolution ' extrusion segmentation'  in g1 command , motion sensor distance by pulse ,  and with switch , extrusion segmentation = remaining distance , no possibility to extrude more(of course , with substraction of the last block because no idea of the filament that have been used'\r\n\r\nExtrusion segmentation can make MARLIN the best secure firmware , with this we can have an very quick jam detection ' extrusion segmentation size of motion sensor pulse distance ' to poll the sensor and verify each pulse , and for the runout switch , to perform a better calculation of the remaining filament. \r\n\r\nTo stop a planner block is possible , but to restart it when out of filament pause park , need too much complexity , data storage and more it's why , extrusion segmentation can make the job , and easy to code\r\nExtrusion segmentation will reduce the feedrate , but , the user will make his own choice ' security , or speed '\r\nIf you have a MODIX 120 , that makes the first layer in 2 hours and waste 1/2 spool just for it , believe me if i tell you , the only thing i want is to have a STABLE PRINTING and no stupid issues\r\n\r\nA reasonnable motion sensor have 24 pulse per rotation , but , we can use multiple of 2 , or 4 , to have a good ration ' speed/security'\r\nThks\r\n\r\nps:\r\nI can write the code, but, not as well. I have never seen a code as well written in my life, the unit runout.h is a wonder, so beautiful that I took 48 hours to understand. So, I think that the author of this jewel, must himself write his update\r\n"},"comment":{"url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/comments/546612196","html_url":"https://github.com/MarlinFirmware/Marlin/issues/15674#issuecomment-546612196","issue_url":"https://api.github.com/repos/MarlinFirmware/Marlin/issues/15674","id":546612196,"node_id":"MDEyOklzc3VlQ29tbWVudDU0NjYxMjE5Ng==","user":{"login":"InsanityAutomation","id":38436470,"node_id":"MDQ6VXNlcjM4NDM2NDcw","avatar_url":"https://avatars2.githubusercontent.com/u/38436470?v=4","gravatar_id":"","url":"https://api.github.com/users/InsanityAutomation","html_url":"https://github.com/InsanityAutomation","followers_url":"https://api.github.com/users/InsanityAutomation/followers","following_url":"https://api.github.com/users/InsanityAutomation/following{/other_user}","gists_url":"https://api.github.com/users/InsanityAutomation/gists{/gist_id}","starred_url":"https://api.github.com/users/InsanityAutomation/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/InsanityAutomation/subscriptions","organizations_url":"https://api.github.com/users/InsanityAutomation/orgs","repos_url":"https://api.github.com/users/InsanityAutomation/repos","events_url":"https://api.github.com/users/InsanityAutomation/events{/privacy}","received_events_url":"https://api.github.com/users/InsanityAutomation/received_events","type":"User","site_admin":false},"created_at":"2019-10-26T15:23:33Z","updated_at":"2019-10-26T15:23:33Z","author_association":"CONTRIBUTOR","body":"I agree this is the next logical evolution. We're at the first stage of native jam detection and what's described here is probably a stage 3. Good goal to work towards for sure."}}
{"actor":{"display_login":"InsanityAutomation"}}