SV mode as background

[prmango43]

In this auto roast (SumaWet021226cpy.alog) effort I setup control SV mode as background, PID input BT, with the default 8sec look ahead. Thought roast BT would follow the background BT curve closer without need to use alignment as when using SV mode manual. I left the background "default" values -- align charge. The only settings I manually changed during roast were drum values which should not have any affect on the SV background controlled roast. Roasting outside ambient T ~68F/20C. How precise does the charge temp need to be -- the slop??

Maybe not enough look ahead as the sampling interval is 3sec?? How does the SV mode as background make use of (or ignore??) any burner events -- background events, background data events, or burner alarms??

EDIT: Maybe should untick playback events??

Kaleido Dual M2S AS 4.0.2 Windows 10 Pro

TIA

roast -- SumaWet021226cpy.alog
aset -- artisan-settings020726cpy.aset
background -- Sumatra010226cpy.alog

SumaWet021226cpy.alog.txt

artisan-settings020726cpy.aset.txt

Sumatra010226cpy.alog.txt

[davidk21770]

Kaleido does not expose the burner directly. Aritsan is forced to drive Kaleido's PID not using it's internal PID. I have found it very non-optimal. The response time of the combination seems to be about 30-45 seconds for my machine and setting, but Kaleido's PID's response is set to be very fast (seconds). If I do not pre-synch it very close during the drying phase, it is quite ugly as it sync's itself -- usually burning my beans.

SO, I start off manual and synch it to so close that I can not see the difference between the BT and the background graph. When I'm entering Milliard / 2nd phase (DE) or a little before I have it synced and can typically switch to background/BT + Auto. But even then, I keep an eye and manually set the burner when it tries to go to 70-80-90-100% to bring it up a degree! Then back to auto -- remembering that while in manual, the SV is not updating... (or a long 0% losing momentum, I set it to a nominal % and try a resynch when it's looking better).

I wish that Kaleido and Artisan would get it's collective act together (probably more Kaleido than Artisan since Kaleido controls the firmware) and make it more usable. Especially since Artisan is now the primary controller for Kaleido.

(Or did I miss a firmware update that does this?)

[MAKOMO]

Kaleido does not expose the burner directly. Aritsan is forced to drive Kaleido's PID not using it's internal PID. I have found it very non-optimal.

Hm. Is this true? What happens if you click the custom event button "MANUAL Burner" in artisan scopes default Kaleido setup?

For sure, the artisan internal PID cannot be used with the Kaleido as the configuration links the CONTROL dialog and SV slider to the machines (external) PID. Next version will offer a flag to break this link allowing to use scopes internal PID to control the burner. This will only work well if this PID is proper tuned for the machine which is connected. This will then be up to the user!