You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
List of events in roasting report should be indentical to events recorded in roast log
Actual Behavior
Event 2 in roasting report is a duplicate of event 1. Actual event 2 overwritten
Steps to Reproduce the Problem
Menu File->Open "FZ-9456.alog"
Menu File->Report->Roast
Scroll down to events section: event 1 and 2 are identical, actual event 2 overwritten
Not just for this particular FZ-9456.alog but for any *.alog
Specifications
Artisan Version: 1.3.0
Artisan Build (number in brackets shown in the about box): ca3c5f1
Platform (Mac/Windows/Linux + OS version): win 10
Connected devices or roasting machine: coffeetech fz94 log.zip
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.
The text was updated successfully, but these errors were encountered:
Expected Behavior
List of events in roasting report should be indentical to events recorded in roast log
Actual Behavior
Event 2 in roasting report is a duplicate of event 1. Actual event 2 overwritten
Steps to Reproduce the Problem
Menu File->Open "FZ-9456.alog"
Menu File->Report->Roast
Scroll down to events section: event 1 and 2 are identical, actual event 2 overwritten
Not just for this particular FZ-9456.alog but for any *.alog
Specifications
log.zip
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.The text was updated successfully, but these errors were encountered: