Fan setting seems to follow the heater setting

[RickGroszkiewicz]

I recently set up artisan on a different laptop running Linux Mint 20. The software behaves differently on my Hottop B-2K+ than it did on my prior laptop. The fan setting seems to follow the heater setting, which requires me to manually correct the fan setting during each roast.

I recently did two roasts of the same bean. The roast on the old Hottop was what I expected. The roast on the new Hottop was "unusual":

[RickGroszkiewicz]

Here are the events recorded during the roast. The suspect ones are the "Q events" - which are not created by my alarm file.

[roasterdave]

Do you have Quantifiers enabled? Config>> Events>> Quantifiers tab.

[RickGroszkiewicz]

Apparently they are enabled, but I didn't set this up (never used quantifiers). This must have been done automatically as part of the initial configuration via Config / Machine / Hottop / B2K+

[MAKOMO]

Could it be that your event types are wrongly labeled and thus the alarms trigger the wrong events. I see here one named "None". M

…

On 1. Dec 2021, at 20:40, Rick Groszkiewicz ***@***.***> wrote: Apparently they are enabled, but I didn't set this up (never used quantifiers). This must have been done automatically as part of the initial configuration via Config / Machine / Hottop / B2K+ — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[roasterdave]

Looks like the events were renamed? The default order for the Hottop B-2K is Air, Drum, Damper Burner.

[RickGroszkiewicz]

Yes, I did have to rename the event types. This was required so I could use my existing alarm files that were created last year on a different laptop running Linux Mint 18:

[RickGroszkiewicz]

Here are the alarms that were triggered during the roast:

[RickGroszkiewicz]

After I changed the quantifier settings to match the event types, I got the expected results in a simple test roast.
Here are the results for Config / Events / Quantifiers:

Here are the events that occurred during the test roast:

[roasterdave]

Good to hear! Be sure to save your settings to a file (Help>> Save settings).

[RickGroszkiewicz]

Unfortunately, I have more research to do on this problem. I basically started over from scratch with the test roast, as shown in my prior post.

During my recent roasting session, the "Q events" still occur. When I set the air to 25% via my alarm file, a "Q event" reduces it to 20%. Then I had to manually change the air back to 25%.:

I missed the change to 20% air near the end of the roast, which had little effect anyway.

[RickGroszkiewicz]

This looks like the effect of a "coarse" setting for the air. I carefully checked my settings (and looked in the file with a text editor), but none of the check boxes for "coarse" are selected.