{"action":"created","issue":{"url":"https://api.github.com/repos/repetier/Repetier-Firmware/issues/811","repository_url":"https://api.github.com/repos/repetier/Repetier-Firmware","labels_url":"https://api.github.com/repos/repetier/Repetier-Firmware/issues/811/labels{/name}","comments_url":"https://api.github.com/repos/repetier/Repetier-Firmware/issues/811/comments","events_url":"https://api.github.com/repos/repetier/Repetier-Firmware/issues/811/events","html_url":"https://github.com/repetier/Repetier-Firmware/issues/811","id":348023314,"node_id":"MDU6SXNzdWUzNDgwMjMzMTQ=","number":811,"title":"Heater decoupled","user":{"login":"leoheck","id":1277920,"node_id":"MDQ6VXNlcjEyNzc5MjA=","avatar_url":"https://avatars2.githubusercontent.com/u/1277920?v=4","gravatar_id":"","url":"https://api.github.com/users/leoheck","html_url":"https://github.com/leoheck","followers_url":"https://api.github.com/users/leoheck/followers","following_url":"https://api.github.com/users/leoheck/following{/other_user}","gists_url":"https://api.github.com/users/leoheck/gists{/gist_id}","starred_url":"https://api.github.com/users/leoheck/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/leoheck/subscriptions","organizations_url":"https://api.github.com/users/leoheck/orgs","repos_url":"https://api.github.com/users/leoheck/repos","events_url":"https://api.github.com/users/leoheck/events{/privacy}","received_events_url":"https://api.github.com/users/leoheck/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":32,"created_at":"2018-08-06T17:55:27Z","updated_at":"2018-08-28T07:02:34Z","closed_at":null,"author_association":"NONE","body":"I am having this \"Heater decoupled\" very often.\r\nUsing Repetier-Firmware v0.92.9\r\n\r\nTried to print 3 times right now. The temperatures graphs are just fine. And suddenly I have this _Heater decoupled_ error which messes the printer job. \r\n\r\nMaybe it is a problem with the thermistor/cables but they look good. I just measured the thersmistor which was showing a steady ~102K today.\r\n\r\n![image](https://user-images.githubusercontent.com/1277920/43732343-d49854ce-9987-11e8-8f3c-7296d855cf96.png)\r\n\r\nI found this message, which may be related.\r\n\r\n![image](https://user-images.githubusercontent.com/1277920/43732218-5a44f89e-9987-11e8-9265-b30974b81c59.png)\r\n\r\nAny idea on what I can try to fix this thing?"},"comment":{"url":"https://api.github.com/repos/repetier/Repetier-Firmware/issues/comments/416473686","html_url":"https://github.com/repetier/Repetier-Firmware/issues/811#issuecomment-416473686","issue_url":"https://api.github.com/repos/repetier/Repetier-Firmware/issues/811","id":416473686,"node_id":"MDEyOklzc3VlQ29tbWVudDQxNjQ3MzY4Ng==","user":{"login":"Nibbels","id":3265671,"node_id":"MDQ6VXNlcjMyNjU2NzE=","avatar_url":"https://avatars3.githubusercontent.com/u/3265671?v=4","gravatar_id":"","url":"https://api.github.com/users/Nibbels","html_url":"https://github.com/Nibbels","followers_url":"https://api.github.com/users/Nibbels/followers","following_url":"https://api.github.com/users/Nibbels/following{/other_user}","gists_url":"https://api.github.com/users/Nibbels/gists{/gist_id}","starred_url":"https://api.github.com/users/Nibbels/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Nibbels/subscriptions","organizations_url":"https://api.github.com/users/Nibbels/orgs","repos_url":"https://api.github.com/users/Nibbels/repos","events_url":"https://api.github.com/users/Nibbels/events{/privacy}","received_events_url":"https://api.github.com/users/Nibbels/received_events","type":"User","site_admin":false},"created_at":"2018-08-28T07:02:34Z","updated_at":"2018-08-28T07:02:34Z","author_association":"NONE","body":"@leoheck in general the different method rules are there to search different \"working\" sets of Kp Ki and Kd.\r\nThe best strategy is that which finds a non-swing but least stable set of constants (Kp Ki and Kd). That is supposed to be the \"most reactive one which is stable in all situations\".\r\n\r\n-> When the temperature rises the hotends/heatbeds temperature line should not overshoot much and go straight into a constant line of temperature.\r\n-> And it should not swing afterwards.\r\n-> And it should not start to swing when you turn on your cooler fan or such. Then your stability is a bit to low.\r\n\r\nThe following list is my personal order of the methods according my feel of the heaters reactiveness/speed:\r\n\r\nreactive hotend ....\r\n3 = pessen integral rule\r\n0 = classic pid (ziegler nichols)\r\n1 = some overshoot\r\n2 = no overshoot\r\n4 = Tyreus-Lyben\r\n... 220v overpowered heatbed\r\n\r\nSo **I would** try myself from top to bottom for a hotend and from bottom to top for a heated bed and then make pictures like you did to compare the line of rising temperature (step response/Sprungantwort). \r\nAfterwards use the most pretty one.\r\n\r\n_Additional not really needed bonus information: You can decrease an initial overswing by setting #define xxxxxx_PID_INTEGRAL_DRIVE_MAX 230 to a bit lower number on that specific controller. But if you get this number like 5 too low, you will totally waste your controll 🗡 . So be aware that this method of overtune a near perfect set of constants is a bit work.\r\nAs example: My hotend had a good response but overswing at the first temperature rise of about 10°K. When I set my xxxxxx_PID_INTEGRAL_DRIVE_MAX 230 to 150 it was only 4°K, But When I set it to xxxxxx_PID_INTEGRAL_DRIVE_MAX 145 the controller did not reach the temperature anymore. So I set it to a number like 150..153_\r\n\r\nGreetings"}}
{"actor":{"display_login":"Nibbels"}}