Hi Andy, and Happy New Year to you as well!!

That's not surprising...Roast Complement is my own invention to provide a means of qualifying the roast, instead of the greens themselves.

In cuppings circles that might use the SCA(A) protocol (buyers, brokers, famers, etc.), the "language" of the cupping attributes is fairly ubiquitous, especially being tied to a country of origin. And, all of those qualifiers are based on a standardized, basic roast profile.

The one thing that bugged me about relying only on standardized cupping protocols in Roastmaster, was that it provided no means of helping roasters know whether a cupping score was achieved via the quality of the beans, or the quality of the roast profile. So, I did some research into many different cupping protocols beyond just the SCAA protocol, and some heavy thinking, and came up with 2 different protocols designed to help solve this dilemma.

The Roast-centric protocol (and Green-centric simply for the sake of being thorough) are meant to complement the standard SCA protocol. It helps achieve a couple of goals:

• Allowing you, as the roaster, to declare your intent when cupping. Whether that’s to evaluate the quality of the greens, or the quality of your roast profile, perhaps as you try to perfect it over time, you’ll have an easy means of know how each score should be interpreted, by virtue of which protocol you used.
• Providing a means of auditing beans in the long term via reports, by both the quality of the green and varietal attributes themselves, along with how well you think you’re doing them justice with your roasting habits. By scoring the “Roast Complement” attribute, you can tell your “future self” how well you think a particular roast hit the sweet spot of the green you roasted.

Hopefully you find them helpful!

I hate relying on deletion for organization, so that was kind of my thinking behind the "Manual" sort order, so you could organize more often-used probes first.

But, I admit, it's not a perfect solution. I've already got the code completed for a filter, similar to sort, that lets you view by a time frame. I do plan on enabling that in Beans, Roasts, Blends, Cuppings, and Profiles when I get some time to do the testing. This will let you "hide" older stuff, yet still allow you keep it in the database for future use.

Another good idea!

Believe it or not, the code is already built for that aggregated list, sectioned by roaster. I could add an entry on the main app menu called "Profiles", and have them all list in that fashion. Tapping the + button would simply prompt for the target roaster if there are more than one.

I like it!

Hi Tod

Merry Christmas to you as well!

Great idea - funny, I envisioned something similar when designing that HUD. I originally wanted multiple HUDs that could be placed for each curve, then realized the clutter that would cause, so kept it simple.

I think I'll model an attribute for curves - something to signify their prominence, with a switch that can be toggled on or off. That way, the setting can be made in individual profiles once, and remembered forever.

Thanks for the idea!

Stephen - Sorry, I was out of the office after Wednesday. I sat down this morning to test, and see if I could reproduce that dialog you were getting, but see you've gotten it figured out. That dialog, as you seem to have discovered, will present if you're trying to use a probe with more than one curve.

The heading of that section you mention in the Probe details screen used to say LCD (for the old BlueTherm Duo). That made a little more sense, but I changed it when adding Battery and Signal level for the ThermaQ Blue. I can see where that would be misleading. Maybe I'll change that to something more descriptive.

For a few different reasons, the copy feature constructs the new roast's Data Curves from the profile of the source roast. So, if the profile in questions contains Curve Templates, those will form new data curves in the copied roast.

If you already use profiles containing Target Curves as a means of targeting temperature data, just add the corresponding Curve Templates to you profiles. Then, when you copy a roast, the data curves will automatically be configured. If not, you could create 1 general profile with Curve Templates and use that for all roasts.

But, a better solution for the scenario you mention is to use the Build Roasts by Yield feature. In the roast list, tap the gear icon in the bottom toolbar to access it. Then, just enter your desired roasted yield weight, and choose the appropriate profile. Roastmaster will build all 17 roasts at once. The same rules apply for Data Curves using this feature - the Curve Templates of the profile you choose for building the roasts will be used to create those data curves. If those curve templates have their probe binding set, the curves will be linked without any additional input on your part.

This screencast talks about the process so you can see it visually... https://rainfroginc.com/documentation/roasting-with-roastmaster-part-2-building-and-targeting-a-profile

I just moved the instructions to a new documentation article Upgrading to Phidgets Lib22 from Lib21.

If you are using a Windows machine as your host, and having connection issues after installing Lib22, it's likely that Windows firewall is blocking the Phidgets traffic. Phidgets changed the default port fro 5001 to 5661. There's some help on that page, and a link to a tech article on adding a Windows firewall exception rule.

If not, it's likely that Lib 21 is still running in the background and mucking up the works. Try manually uninstalling or at least disabling the old Control Panel (Windows), Preference Pane (Mac) or Package (SBC). Then, reboot your host.