BarryR wrote:I'm a Hottop (TC4C/HTC) + Artisan user. I think this is an excellent resource even as a non-Huky user. Hopefully it will continue to be developed to help fill in some of those knowledge gaps regarding Artisan features that are hard to find documented.

Kudos!

Thanks Barry if there is a configuration document for your setup that someone wants to give me permission to add as an addendum, I am happy to do so.

I may be telling you something you already know but
This link:
https://drive.google.com/file/d/0B4HTX5 ... tVUmM/edit
on this page:
https://github.com/artisan-roaster-scop ... /README.md

has very useful information for the Hottop.

It may be the case that everyone who needs it finds it easily enough already.

BarryR wrote:I may be telling you something you already know but

Haven't reviewed that yet but will for ideas. Thank you Barry. I am new to this and want to give back and share my learning. I don't see a reason to do more than reference this great work already.

I updated the document to refer people not using a North to the end of the document and I referenced Hottop there with a link.

There's some excellent data in this thread that you might want to include in your documentation:
US Roaster, Artisan Start Up

Thanks for collecting all these information. I wonder if a better format would be structured Wiki page where several authors could collaborate to extend and update this information in parallel. I could potentially add such a Wiki on the Artisan Github site, thus I will not have any time to maintain it...

Regarding some of your questions:

Q1. How do Quantifiers work?

Quantifiers allow to turn readings received from a connected device into custom events on their 0-100% scale. For example, if you have a channel configured to read burner output on a scale from 0-2000 you can decide to hide the corresponding curve (as it won't fit into the range of the standard temperature axis) and turn just the changes of its readings into events by defining a corresponding quantifier. You end up with a more readable and useful profile. See my post on quantifiers for some details:
https://artisan-roasterscope.blogspot.de/2014/04/event-quantifiers.html


Q2. How have people best configured Profile Background and why, including Playback Aid
and Playback Events?

Described here: https://artisan-roasterscope.blogspot.de/2017/10/profile-templates.html

Q7. Is the description of how Phases and Statistics intersect below accurate?

Roast phases can either be used in manual mode, where their temperature limits are defined in the corresponding dialog, or in automatic mode, where those limits are taken from the corresponding DRY and FCs events as keyed during a roast. In manual some activate AutoDRY and AutoFCs to let Artisan generate the corresponding events once the BT reaches the limits of the corresponding phases as manual defined in the dialog are reached. So yes, your description is fine.

Two further remarks on your manual:

..when you Charge the roaster by having the beans drop into the drum, hit Start at the top..

START should be hit some seconds before actually charging the beans to record the charge temperature balance and allow the autoCHARGE mechanism to do its magic (it needs about 5 readings before recognising anything). So START should be pressed about 5x<sampling interval> seconds before the CHARGE. If you set the sampling interval to the default 3sec this adds up to 15 seconds.

These aren't in order and I don't see a way to rearrange the order in Artisan

Alarms are unordered by definition. All alarm conditions of not-yet activated alarms are evaluated once per sampling interval and randomly one of those were all pre-conditions are fulfilled is fired. Note that each alarm is only fired once.

With Marko's replies I have updated the document, added info on the volume calculator and added some info on other roasters at the bottom. Questions are removed for now until more come up.

My biggest request that remains would be to see a combo of the value/type display of events. I like the plot graph of the type and would still like to see values with it.

Thanks everyone so far.

If you tick "Snap" in the Events dialog, the event values 0-100% are aligned to the temperature y-axis 0-100C. Further, you can click any of those markers (also those of the background profile and also during recording a roast) to get the underlying values displayed in the message line.

With this method, and I will try again, is that the lower values, 10, 20, are really compressed to the bottom. The benefit of the of the mixed type/value method I propose is twofold, there is visual up or down and there is more space for which to show the values, and even better might be a choice to show the delta values - like gas down 10 or air up 33 (low to medium). Thanks for the clarification. I added it to the document.

CarefreeBuzzBuzz wrote:My biggest request that remains would be to see a combo of the value/type display of events. I like the plot graph of the type and would still like to see values with it.

Like this?

MaKoMo wrote:Like this?

Thank you for the follow up Marko,

Hmmm hadn't thought of them on the BT line. I was thinking of them on the plot graph in the circles and squares limited to 4 letters/numbers, but I think this can work too, or a choice of which one.

I also wonder about why the choice has to be the first letter of the Type and the Value (I think that is how it is working). Why not allow the label (again probably need a limit of 4 letters/numbers) as your presentation looks very good below?




All the best, Michael