Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: Custom Events #277

Closed
reizao opened this issue Oct 30, 2018 · 1 comment
Closed

Request: Custom Events #277

reizao opened this issue Oct 30, 2018 · 1 comment
Labels
Milestone

Comments

@reizao
Copy link

reizao commented Oct 30, 2018

Expected Behavior

Can in the future versions add events, and alarms can be fired by this events?

Can the Default events name be modified?

For example, can you add an event between Dry End and FC? And this event can start any alarm. For example, can 2 minutes after this event or 20 degrees after this event an alarm be fired?

Actual Behavior

Steps to Reproduce the Problem

Specifications

  • Artisan Version:
  • Artisan Build (number in brackets shown in the about box):
  • Platform (Mac/Windows/Linux + OS version):
  • Connected devices or roasting machine:

Please attach your current Artisan settings file (as exported via menu Help >> Save Setings as *.aset) file.
Please attach any relevant Artisan *.alog profiles.

Note that you need either add a .txt extension or zip the files before uploading. Otherwise you will receive a "Not a supported file type" error on uploading.

@MAKOMO
Copy link
Member

MAKOMO commented Oct 11, 2019

This will be possible in the next version using an event button that sets the event value of one type to a certain value, an additional Virtual Device to map event values to curves, and an alarm that triggers based on that the data in that additional curve. What is missing from v2.0 to enable this is mostly the mapping between event values and curve data which is broken in v2.0 and now has been fixed for v2.1.

@MAKOMO MAKOMO closed this as completed Oct 11, 2019
@MAKOMO MAKOMO added this to the v2.1 milestone Oct 11, 2019
@MAKOMO MAKOMO added the bug label Oct 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants