auto drop did not start cooling fans

[prmango43]

My last roast where auto drop worked happened 072825 -- I was running x64-3.2.0. On 073025, I installed continuous release x64-3.2.1 due to the mouse problem. On my next roast 081625, auto drop worked only partially. I auto drop and AS marked the drop on the graph, but cooling fans did not start. I'm not roasting daily, just for my consumption, so it will be several days before I roast/test again. I have checked the internet and although I did find that last year there was a problem with auto drop it was related to sensitivity in BT and where auto drop was not working at all in those cases. My auto drop works does work but not as intended.

I conducted 2 dry runs to check that the PC buttons including drop and on cooling were working. Drop and on cooling, as well as DE, FCs, FCe, FSs, FSe, and cool end all worked. I have included the file RGarcia082025.zip.txt containing the log and alarm files for the roast where the auto drop problem occurred. Is there a ways to test auto drop outside of doing a roast??

Edited: just added my settings file to the zip

M2s AS 64x-3.2.1 W10Pro 22H2 19045.6216
RGarcia082025.7z.txt

[roasterdave]

From the description it sounds like auto DROP is working properly since it marked the event. Auto DROP does the same thing as pressing the DROP button. The DROP button only marks the event. Actions, such as turning on the cooling fan, can be defined that are triggered by DROP. The machine setup provided with Artisan does not include an action triggered by DROP that turns on the cooling fan.

In your settings file there is nothing triggered by DROP that would turn on the fan. There are three actions defined that are triggered by DROP. The first turns off the heater and the second sends a message to the roaster saying a DROP event has occurred. These two actions are part of the Kaleido machine setup provided with Artisan. The third action in your settings is an alarm that turns Artisan OFF 15 seconds after DROP. Did anything change in your settings?

Is it possible the roaster previously turned the fan on when it received the DROP message? I don't have this roaster so I don't know what it does after receiving a DROP message from Artisan. You may benefit from contacting the manufacturer.

[prmango43]

Sorry for the confusion I created. More precisely (just edited #1961), it's not the "fan" but the "fans" as in cooling mode. I appreciate the effort because I was unaware that the drop function is also supposed to turn the burner off. In my case that has not been the action since day one. I have to manually turn the burner off. Now I'll have to run another dry run to confirm what the drop button does on my machine -- so far pressing the button marks the graph and starts cooling.

Perhaps you can help on another matter before I start looking elsewhere. Kaleido has a number of default buttons which I assume are part of the default (factory??) settings -- yes? I would appreciate it if you know what the values mean (eg EV and numbers 1-9). TIA

[roasterdave]

The roaster is notified when events occur. The EV number corresponds to the event. EV=1 is CHARGE, EV=3 is DRY END and so on.

In the case of DROP a Multiple Event is used. Click on the Buttons tab to see that the first action, button #1, calls button #9 which turns off START HEATING. Maybe that does not turn off the heater on your model? The second action is button #2 that sends EV=8 DROP to the roaster.

[Terracotta-6]

The roaster is notified when events occur. The EV number corresponds to the event. EV=1 is CHARGE, EV=3 is DRY END and so on.

In the case of DROP a Multiple Event is used. Click on the Buttons tab to see that the first action, button #1, calls button #9 which turns off START HEATING. Maybe that does not turn off the heater on your model? The second action is button #2 that sends EV=8 DROP to the roaster.

[prmango43]

Thanks roasterdave and Terracotta. Well It appears my M2s is setup differently -- or at least this is what I understand. The call button #9 in event/config/buttons has label \S\n\h (\Start\new line character\HEATING) and by calling this action while the roaster is in the heating mode will stop the heater. Right? But it doesn't -- pressing the drop button marks drop and starts cooling. Dry run testing confirms this action, but I intend on doing a repeat test soon. The drop marking and on cooling were also happening when I did a "manual" drop at the machine, except now drop is marked but cooling did not start. What would be the "manual" drop expected time interval between mark and on cooling, if it were working properly?

I also understand the option of using an alarm to start cooling, but pressing drop button already does this. If the default action on my machine is -- press drop = mark; on cooling --, might an extra call for cooling by alarm cause cooling to turn off?

The EV=8 is supposed to send command to roaster, but not listed as such in events/config dialog. How would one know what this command is? Is this internal coding provided by Kaleido or Artisan?

I appreciate your help, but as there appears no way to conduct a dry run to do a manual drop and I don't have $$ to waste coffee, the discussion will have to hold till next roast. Except I'll post dry run to test drop button action.

[prmango43]

It's a new day and I feel I've achieved some clarity. It was right in front of me all the time, but as I had not used the Kaleido Pad much I forgot how the pad drop button works -- internally couples activities to mark drop and automatically start cooling fans. Their pad instruction manual is clear too. It instructs user to turn burner to zero (our Off Burner, # 27) before the drop. Do you see the difference -- #9 vs #27?? So in error, I believed the the call # 1 = (9,0) was supposed to start cooling not stop heating. And in fact may (should) be expecting a different call command -- call #2 = (27,0) maybe??.

I speculated the command for the burner zero as their fail safe check ensuring user has followed their instructions -- set burner and air to zero before pressing drop. But testing Kaleido Pad today it doesn't matter if burner and/or air are not zero'd down, when I press drop the cooling fans will automatically start without delay. Only time this is not the case is if the user has selected cooling control switch in setup, which adds cooling button to main panel screen and converts the drop button function to just a marker.

Artisan receives the auto drop signal from my M2s and without delay marks the drop, but the coupled (start cooling) part of the drop button is not executed in a timely fashion. In what way(s) is the execution of auto drop different from the press of the drop button other than meeting the BT threshold? I don't see any time delay or more specifically an appreciable difference between KPad and PC regarding the press drop button function. So basically, no difference between one system being hardwired and the other communicating via Bluetooth/WiFi. Any delay when user presses the drop button in either system is likely the result of a small timing "error" between the button press and sampling interval.

[prmango43]

No, that was not my purpose -- I'm quite serious. I was hoping to read an entry a non-coder could digest. The switch example did not enlighten me. You're not saying that the BT threshold = step-adjustable?? That would be prior to marking the drop which was very fast. The slooow part is after. How so?? Pls explain the step-adjustable analogy. Can't have fun unless at least 2 play. 3 days till my next roast where alarms get their opportunity to improve on the time.

[Terracotta-6]

No, that was not my purpose -- I'm quite serious. I was hoping to read an entry a non-coder could digest. The switch example did not enlighten me. You're not saying that the BT threshold = step-adjustable?? That would be prior to marking the drop which was very fast. The slooow part is after. How so?? Pls explain the step-adjustable analogy. Can't have fun unless at least 2 play. 3 days till my next roast where alarms get their opportunity to improve on the time.

I fully concur! Your dedication to exploring the underlying principles of matters is particularly valuable, and I offer my full support. Regrettably, due to the lack of an identical hardware and firmware environment as yours, I am unable to engage in practical operations, and can only attentively listen to your experience sharing and summarized insights.

[prmango43]

Thanks for the support. Is there anything which would prevent me from changing sampling rate near the roast end?

I'm also interested in trying the dual system connection. You mentioned something about this but that post is no longer here and I didn't have any opportunity to copy it. Can you re-post it and explain how I might try the test or at least a link(s) to articles on it's use.

TIA

[MAKOMO]

Is there anything which would prevent me from changing sampling rate near the roast end?

The sampling rate cannot be changed during a recording