Lost ROR BT curve during roast

[fischto-gif]

Problem Description

I have defined an alarm "Charge" which sets the event 'Charge' at the temperature of 170°C just after the roast has started and the beans have been dropped. This event will be correctly postet at the BT-curve. The problem occurs, as this temperature is reached the second time during the roast. At that point the RoR BT curve disapears completely from the screen as well as the already existing mark "Charge". As the roast prgresses, the LCD for "RoR BT" continues normally. The RoR BT curve reapperars as the roast has been stopped.
The issue can be reproduced 100% of the time.
I'm running Artisan 4.0.2 in a full installation (.deb)

Steps To Reproduce

Alarm Settings_1.alrm.txt

Bazilian Yellow Burbon 13.alog.txt

Artisan Version

Other - include in Description

Computer OS and Version

Linux Mint 22.3

Connected devices or roasting machine

Phidget and Roaster "Cormorant"

Files

• A sample profile *.alog file, renamed to *.alog.txt is attached.

• A settings file (Help>> Save Settings) *.aset, renamed to *.aset.txt is attached.

• Screenshots are attached.

• No files are attached.

[roasterdave]

It always helps to attach your aset settings file (Help>> Save settings). I presume you have Automatic Marking CHARGE enabled (Config>> Events>> Config tab).

In this profile it was the Automatic Marking CHARGE or a manual press that actually marked CHARGE at the start of your roast. It was not your alarm. Your alarm Nr. 6 did not fire at the start of the roast. That is because your alarm is set to trigger when BT>170C and BT does not go above 168.7C at the start of the roast.

Later, at time 6:40, BT does rise above 170C and the alarm fired. When that alarm fired the existing CHARGE event was removed. Pressing any of the roast events buttons performs an "undo" removing the event and alarms that trigger events operate as if the event button is pressed. The RoR curve vanished because it is not plotted when there is no CHARGE event.

I recommend you use either Automatic Marking CHARGE or your alarm to mark CHARGE, but only one and not both. If using the alarm be sure BT is in the proper range.

[fischto-gif]

Hi David,Thank you very much for your reply. I’m a bit of a newbie on reporting an issue. I’m roasting with Artisan since approx 6 years and never had an issue before. You were right with your assumption, I had set the automatic marking for charge. Never detected the difference, probably because with my previous roasts I always was over the set value of 170°C for the charge alarm to be fired. Your explanation helped me also a great deal understanding how alarms work. I have deleted this alarm now and only rely on the automated marking. Many thanks againTorstenAm 04.04.2026 um 21:29 schrieb David Baxter ***@***.***>:roasterdave left a comment (artisan-roaster-scope/artisan#2157) It always helps to attach your aset settings file (Help>> Save settings). I presume you have Automatic Marking CHARGE enabled (Config>> Events>> Config tab). In this profile it was the Automatic Marking CHARGE or a manual press that actually marked CHARGE at the start of your roast. It was not your alarm. Your alarm Nr. 6 did not fire at the start of the roast. That is because your alarm is set to trigger when BT>170C and BT does not go above 168.7C at the start of the roast. Later, at time 6:40, BT does rise above 170C and the alarm fired. When that alarm fired the existing CHARGE event was removed. Pressing any of the roast events buttons performs an "undo" removing the event and alarms that trigger events operate as if the event button is pressed. The RoR curve vanished because it is not plotted when there is no CHARGE event. I recommend you use either Automatic Marking CHARGE or your alarm to mark CHARGE, but only one and not both. If using the alarm be sure BT is in the proper range. image.png (view on web) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[MAKOMO]

Next release will avoid doing an undo of an already set main event if that same event is triggered by an alarm (or from a custom event button).