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

PID variable reset #310

Closed
greencardigan opened this issue Feb 5, 2019 · 0 comments
Closed

PID variable reset #310

greencardigan opened this issue Feb 5, 2019 · 0 comments

Comments

@greencardigan
Copy link

Expected Behavior

PID variables should be reset when clicking Reset Button. PID should not start with output remembered from previous roast.

Actual Behavior

PID remembers values from previous roast. Output/Heater is turned on even if SV < BT when PID is activated on subsequent roast.

Steps to Reproduce the Problem

  1. Roast 1 ended with SV > BT
  2. Click reset button
  3. Start Roast 2
  4. Set SV < BT
  5. Activate PID
  6. PID Output starts high and Heater turns on.

https://youtu.be/1E2D7b4z9ck

Specifications

  • Artisan Version: 1.5.0
  • Artisan Build (number in brackets shown in the about box): fc6ebda and
  • Platform (Mac/Windows/Linux + OS version): Mac Darwin-18.0.0-x86_64-i386-64bit+ Linux-4.14.79-v7+armv7l-with-debian-9.6
  • Connected devices or roasting machine: TC4 on MAC or External program on Linux

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.

artisan-settingsPID_BUG.txt

@MAKOMO MAKOMO added this to the v1.6 milestone Feb 5, 2019
MAKOMO added a commit that referenced this issue Feb 5, 2019
- roles back organization domain to have settings location compatible with v1.5
- deactivates plus module
@MAKOMO MAKOMO closed this as completed Feb 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants