Artisan 2.4.2 problem with alarm files #722
-
|
I thought I was finally ready to start roasting, but OH NO!! When I opened my alarm files to set up a profile for a roast, I noticed that the actions are incorrect. In the screen shot below, the action "Slider drum" should instead be "slider burner". See alarms 1, 4, and 9. The action "Slider burner" should be "slider fan". See alarms 2, 5, 8 and 10:
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
|
I assume this problem is related to how the devices are configured for my old Hottop with the TC4 (arduino shield). Here are screenshots of my current setup: Config - Device - Extra devices Config - Events - Config Config - Events - Sliders NOTE - I can't show you what my artisan setup looked like when I created the alarm files earlier this year. My Linux system got trashed, and I had no viable backups. I had to recreate it from scratch. |
Beta Was this translation helpful? Give feedback.
-
|
Rick, Artisan offers 4 event types which can be named freely in the Events dialog. In that dialog on can also define sliders for each of those event types to enter event data and potentially issue some action (like sending a command to an external device, like a roasting machine). An alarm can be defined that sets any of those slider to a defined value if its condition are fulfilled. Obviously your alarm targets do not fit your intended actions. Just correct them. A note on running Artisan with two different setups that are not compatible (which seems to be the case here for you; as you assigned different event names to the four event types in the two setups you are using): just save the Artisan settings for each setup/machine to a file (menu Help >> Save Settings) and load the corresponding setup for the machine you are going to roast and you should be always fine. |
Beta Was this translation helpful? Give feedback.
-
|
Marko, I will try what you suggested ... I have maintained two separate alarm files for my two Hottop roasters, for example: |
Beta Was this translation helpful? Give feedback.
-
|
Note that alarm configurations are saved along artisan app settings |
Beta Was this translation helpful? Give feedback.
-
|
I set up my Hottop B-2K+ roaster today. The alarm files look consistent with the older Hottop - thank goodness. |
Beta Was this translation helpful? Give feedback.
-
|
After MANY false starts and numerous changes in my artisan settings, I finally completed two roasts on each of my Hottop roasters today. I have learned enough that I now plan to get artisan version 2.4.6 working under Linux Mint 20. |
Beta Was this translation helpful? Give feedback.
-
|
Excellent Rick! Maybe you can sketch here what you have learned? Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
It has been so long since I set up the artisan software that I was simply doing things based on force of habit. I had forgotten exactly why I did stuff in a particular order - or what NOT to do. Working with two different Hottop models makes it more confusing. Here are the things that I re-learned this month
old Hottop TC4 notes Config / Device / ET/BT Config / Events / Sliders Config / Curves / Filters new Hottop B-2K+ notes Config / Device / ET/BT Config / Device / Extra Devices Config / Events / Sliders |
Beta Was this translation helpful? Give feedback.
Rick, Artisan offers 4 event types which can be named freely in the Events dialog. In that dialog on can also define sliders for each of those event types to enter event data and potentially issue some action (like sending a command to an external device, like a roasting machine). An alarm can be defined that sets any of those slider to a defined value if its condition are fulfilled. Obviously your alarm targets do not fit your intended actions. Just correct them.
A note on running Artisan with two different setups that are not compatible (which seems to be the case here for you; as you assigned different event names to the four event types in the two setups you are using): just save the …