Replies: 1 comment 2 replies
-
|
Artisan implements multiple mechanisms for automation: alarm rules, event replay (from a background profile), PID control (which may be configured to replicating a background curve). It offers the freedom to combine all of those in various ways. They are not exclusive, but very inclusive. Alarms which did not fire yet will fire as soon as all of their pre-conditions hold. Events will be replayed by time and or temperature as configured. Note that the background profile can be shifted around during a roast which may influence event replay. The PID controller will move the configured positive and/or negative sliders if active. You forgot to tell us which roasting machine you are using and how Artisan is exactly configured (best done by attaching your artisan-settings.aset file (export via menu Help >> Save Settings), renaming it to end in .txt and drag-and-drop it here on a comment field. You also forgot to attach the profile your screenshot shows as .alog file (again it needs to be renamed to end in .txt before you can drag-and-drop it here). |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Although as a home roaster I prefer to roast manually, there are times when the auto roasting is handy. To keep discussions narrowly focused I will, where possible, split query concerning the background theme. Mind you I have looked at AS guide and whatever was related on the net. If someone has a link(s) with a more detailed explanation -- pls post.
As I understand it, the auto roast process requires a roast (background) containing event data. I've already found out this is true -- tested and nearly lost batch. What is the command flow/priority between the events table and a set of alarms that may not correspond to those events? See roast example image. Near TP the B70 is from the background and because I neglected to correct the alarms table, a B80 is also posted shortly after. Also, on charge my alarms set includes a D65 and the events table a D60. Unfortunately my limited understanding of what the roaster can/cannot do while in auto roast is limited. And so I kept moving the slider to D65 and machine reverting to D60. At some point I was able to do D65, but cannot say I understand why. The roast properties data set does not show D65 at 00:36, just D60. Maybe it is stacked and will be seen when I export the Excel file??
I believe that the difference in time shown in the image between background and real time events is due to my alignment shifts of the curves.

TIA....
Beta Was this translation helpful? Give feedback.
All reactions