Artisan marks DROP unexpectedly during roast

[harryf49]

I have been using Artisan for a few years with no problems, but recently it is giving me a headache.

During a roast, using PID control, when it gets to about 7mins, it generates a drop event and the heater turns off for a few seconds, with a corresponding fall in temp. It then seems to try to get power back on, but does not regain PID control.On checking the software updates, I saw one where 7 mins seemed to be significant?

I am running Artisan on Linux Lite on a desktop PC and am using a modified popper as per the directions in an Instructible from a few years back. Any help would be appreciated as this is ruining my roasts.

[roasterdave]

when it gets to about 7mins, it generates a drop event

The auto DROP detection mechanism can be fooled by a noisy BT signal. Sounds like what is happening. Turn off auto DROP by unchecking DROP from Config>> Events>> Config tab>> Automatic Marking section.

[harryf49]

Thanks so much for this, I will give that a try when I get a minute

[harryf49]

That has fixed the problem. There is a fair amount of ripple on the BT curve that must have triggered the drop event although I have not changed anything in years. I don't use event markers as I am keeping everything simple and basic.

Thanks again for your help.

[roasterdave]

I have not changed anything in years

Temperature probes will change with age.

Edit: Modified the title since there is no crash involved here.

[RisingRoaster]

Similar issue. I am a relatively new Kaleido M2 owner, only about 15 roasts under my belt using Artisan 3.20. I typically load a background profile to follow and make adjustments as needed. No automation, no PID activation, etc. Using reliable USB cable connection. A couple weeks ago on about my 5th roast at exactly 10 minutes, just a few seconds into 1st crack, cooldown (drop) was suddenly triggered on Artisan shutting down the burner and activating the cooling fans - essentially ruining my roast. Today, at exactly 8 minutes, the same issue happened - this time 33 seconds into first crack ... lost my roast again. Bean temp, exhaust temps only in 190s, SV temp setting at 215, burner was at 75%, not overheating by any means. I can't find any triggering event or safety issues. The exact timing at 10 minutes and 8 minutes speak to some kind of hidden trigger which I can't seem to locate. All other roasts have proceeded perfectly. Any ideas or remedies would be most appreciated.

[roasterdave]

Did you follow the advice in the first reply to this discussion thread?

The auto DROP detection mechanism can be fooled by a noisy BT signal. Sounds like what is happening. Turn off auto DROP by unchecking DROP from Config>> Events>> Config tab>> Automatic Marking section.

[RisingRoaster]

I greatly appreciate that advice. The 2 events I experienced were exactly at 10 minutes and 8 minutes respectively making me think that I was missing some kind of inappropriately triggered safety feature, but looking at the roast record did not reveal anything unusual. I am clearly an Artisan novice however. I am going to go with your recommendation - it makes complete sense that it should remedy the issue. Thanks again for such a timely response. Sounds like you've been around the block a few times! We need more people like you!

[ssemper23]

Hi Risingroaster, did you determine whether or not you had DROP detection checked in Config>Events during your 2 events?

[RisingRoaster]

Yes, under the Config menu --> Events... --> Config Tab --> Automatic Marking: The DROP box had been checked by default. I have since unchecked the box. Under the Default Buttons section where Drop is checked, I also changed the drop-down selection to I/O Command followed by a change in the text box from "1,2" to "kaleido(EV,8)" I have since completed another 15 roasts ranging between 9 and 12 minutes with no surprise drops. So I am deeply indebted to harryf49 for having raised the issue and for roasterdave to have offered a simple and successful solution to this problem. If I happen to experience it again, however, I will of course inform this thread, but I am optimistic that the problem has been solved.

[harryf49]

Yes I posted on Github that it had worked. ⁣Get TypeApp for Android ​

…

On 28 Aug 2025, 06:59, at 06:59, Dave Baxter ***@***.***> wrote: Did you follow the advice in the **first** reply to this discussion thread? >The auto DROP detection mechanism can be fooled by a noisy BT signal. Sounds like what is happening. Turn off auto DROP by unchecking DROP from Config>> Events>> Config tab>> Automatic Marking section. -- Reply to this email directly or view it on GitHub: #1960 (reply in thread) You are receiving this because you authored the thread. Message ID: ***@***.***>

[RisingRoaster]

It's good to hear your real-world experience. You are very kind to have kept up with the post with your update and successful resolution of the issue.

[harryf49]

This is what fixed it for me. The auto DROP detection mechanism can be fooled by a noisy BT signal. Sounds like what is happening. Turn off auto DROP by unchecking DROP from Config>> Events>> Config tab>> Automatic Marking section. ⁣Get TypeApp for Android ​

…

On 28 Aug 2025, 03:28, at 03:28, RisingRoaster ***@***.***> wrote: Similar issue. I am a relatively new Kaleido M2 owner, only about 15 roasts under my belt using Artisan 3.20. I typically load a background profile to follow and make adjustments as needed. No automation, no PID activation, etc. Using reliable USB cable connection. A couple weeks ago on about my 5th roast at exactly 10 minutes, just a few seconds into 1st crack, cooldown (drop) was suddenly triggered on Artisan shutting down the burner and activating the cooling fans - essentially ruining my roast. Today, at exactly 8 minutes, the same issue happened - this time 33 seconds into first crack ... lost my roast again. Bean temp, exhaust temps only in 190s, SV temp setting at 215, burner was at 75%, not overheating by any means. I can't find any triggering event or safety issues. The exact timing at 10 minutes and 8 minutes speak to some kind of hidden trigger which I can't seem to locate. All other roasts have proceeded perfectly. Any ideas or remedies would be most appreciated. -- Reply to this email directly or view it on GitHub: #1960 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

[RisingRoaster]

Perfect - much appreciated!

[harryf49]

Yes, that must have been the problem. Working OK now thanks ⁣Get TypeApp for Android ​

…

On 12 Sep 2025, 15:42, at 15:42, ssemper23 ***@***.***> wrote: Hi Risingroaster, did you determine whether or not you had DROP detection checked in Config>Events during your 2 events? -- Reply to this email directly or view it on GitHub: #1960 (reply in thread) You are receiving this because you authored the thread. Message ID: ***@***.***>