# Idle\_timeout with sonic pad **URL:** \ **Category:** General Discussion\ **Created:** [August 10, 2023, 8:34am UTC](https://klipper.discourse.group/t/idle-timeout-with-sonic-pad/9865 "2023-08-10T08:34:51Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![MCH47](https://avatars.discourse-cdn.com/v4/letter/m/d78d45/32.png) [@MCH47](https://klipper.discourse.group/u/MCH47)\ **Post date:** [August 10, 2023, 8:34am UTC](https://klipper.discourse.group/t/idle-timeout-with-sonic-pad/9865/1 "2023-08-10T08:34:51Z")
Printer Model: Creality Ender 5 Plus MCU / Printerboard: [klippy (5).log](https://klipper.discourse.group/uploads/short-url/kE0ICcdSze4Xgiswzzrw4Rgy55o.log) (2.1 MB) BIGTREETECH SKR MINI E3 V3.0 Hi everyone, I’ve got 2 Creality Ender 5 Plus upgraded with BIGTREETECH SKR MINI E3 V3.0 motherboards. The both are connected to a Sonic pad. When the filament sensor is true, the idle timeout is set to 600, so I edited my start gcode to : SET\_IDLE\_TIMEOUT TIMEOUT=43200 When a print start, the console show that the setting is saved : // idle\_timeout: Timeout set to 43200.00 s But when I remove the filament, the print is cancelled after 10min pause… I don’t understand why the setting added in the G-code doesn’t work. It’s also a setting called “pause timeout setting” on the Sonic Pad screen but it’s stuck on 10min, and I can’t edit it. My start G-code : ```auto M201 X500.00 Y500.00 Z100.00 E5000.00 ;Setup machine max acceleration M203 X500.00 Y500.00 Z10.00 E50.00 ;Setup machine max feedrate M204 P500.00 R1000.00 T500.00 ;Setup Print/Retract/Travel acceleration M205 X8.00 Y8.00 Z0.40 E5.00 ;Setup Jerk M220 S100 ;Reset Feedrate M221 S100 ;Reset Flowrate G28 ;Home M420 S1 Z2 ;Enable ABL using saved Mesh and Fade Height G92 E0 ;Reset Extruder G1 Z2.0 F3000 ;Move Z Axis up G1 X10.1 Y20 Z0.28 F5000.0 ;Move to start position G1 X10.1 Y200.0 Z0.28 F1500.0 E15 ;Draw the first line G1 X10.4 Y200.0 Z0.28 F5000.0 ;Move to side a little G1 X10.4 Y20 Z0.28 F1500.0 E30 ;Draw the second line G92 E0 ;Reset Extruder G1 Z2.0 F3000 ;Move Z Axis up SET_IDLE_TIMEOUT TIMEOUT=43200 ``` [E5P08\_printer cfg.txt](https://klipper.discourse.group/uploads/short-url/1CcMiAP2WLhOEba19AIZDOferaq.txt) (6.1 KB) Does anyone already meet this ? ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [August 10, 2023, 10:02am UTC](https://klipper.discourse.group/t/idle-timeout-with-sonic-pad/9865/2 "2023-08-10T10:02:46Z")
Add ```auto [idle_timeout] timeout: 43200 ``` to your cfg. ---
**Author:** ![MCH47](https://avatars.discourse-cdn.com/v4/letter/m/d78d45/32.png) [@MCH47](https://klipper.discourse.group/u/MCH47)\ **Post date:** [August 10, 2023, 10:26am UTC](https://klipper.discourse.group/t/idle-timeout-with-sonic-pad/9865/3 "2023-08-10T10:26:00Z")
> [@Sineos](#): > > ```auto > [idle_timeout] > timeout: 43200 > > ``` I already tried this before but it’s doesn’t work… I think the Sonic Pad’s settings overtake all. When I set the timeout on 100sec for exemple, the print is rightly cancelled after 100sec. But if I set the timeout over 600sec, the value is not effective… How can the .cfg settings overtake the Sonic Pad values ? ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [August 10, 2023, 10:30am UTC](https://klipper.discourse.group/t/idle-timeout-with-sonic-pad/9865/4 "2023-08-10T10:30:31Z")
Because the Sonic Pad is an abysmal crap? ---
**Author:** ![LifeOfBrian](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/lifeofbrian/32/2380_2.png) [@LifeOfBrian](https://klipper.discourse.group/u/LifeOfBrian)\ **Post date:** [August 10, 2023, 10:44am UTC](https://klipper.discourse.group/t/idle-timeout-with-sonic-pad/9865/5 "2023-08-10T10:44:06Z")
> [@Sineos](#): > > abysmal crap Very kind choice of words… 😃 But one can’t hide from the truth! ---
**Author:** ![MCH47](https://avatars.discourse-cdn.com/v4/letter/m/d78d45/32.png) [@MCH47](https://klipper.discourse.group/u/MCH47)\ **Post date:** [August 10, 2023, 12:03pm UTC](https://klipper.discourse.group/t/idle-timeout-with-sonic-pad/9865/6 "2023-08-10T12:03:44Z")
So there are no solutions ? 🙁 ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [August 10, 2023, 12:55pm UTC](https://klipper.discourse.group/t/idle-timeout-with-sonic-pad/9865/7 "2023-08-10T12:55:37Z")
I just know that in Klipper the timeout works as it should. How Creality has messed up this functionality is beyond my knowledge. I would recommend contacting the Creality staff. And to be honest, I have no intention to dig deeper into it as I think that this product is an overpriced rip-off of gullible customers. Also refer to [Creality Sonic Pad and Alternatives](https://klipper.discourse.group/t/creality-sonic-pad-and-alternatives/6324) ---
**Author:** ![MCH47](https://avatars.discourse-cdn.com/v4/letter/m/d78d45/32.png) [@MCH47](https://klipper.discourse.group/u/MCH47)\ **Post date:** [August 10, 2023, 1:02pm UTC](https://klipper.discourse.group/t/idle-timeout-with-sonic-pad/9865/8 "2023-08-10T13:02:23Z")
Thank’s for your answer, I will contact the Creality support; I hope they will patch this soon… ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [August 5, 2024, 10:20am UTC](https://klipper.discourse.group/t/idle-timeout-with-sonic-pad/9865/9 "2024-08-05T10:20:27Z")