Hi Stan
I've been working steadily on the next version of RM steadily for the last 6 months, hoping to get it out in tandem with the release of iOS 10, but development ran long. It’s basically a complete overhaul–same concepts, but a lot different in the interface. I'm going to redo the screencasts then, with a different approach - kind of a “tidbits” thing so each one isn’t such a daunting task, and I can afford to be more faithful with them.
1) Yes, Delta Curves is the verbiage RM uses for RoR curves. With that turned on, you will see them in the full-screen Roast Analyzer.
2) In an effort to keep the workflow as simple as possible for those not needing advanced functions (and a lack of screen real estate in iOS), I’ve designed many concepts as “opt in”. Some of the roast metrics fit that category. The turning point is defined by an Event. Events can be created in any curve as simple text-based markers, or static types, like Turning Point, Drying End, etc.
Events can be entered “on the fly” in the analyzer by selecting the target curve, then tapping the curve icon in the upper left corner. Once saved, the event will be pinned to that time in the current roast.
You can also define events in a curve before the roast begins, and set them to “Auto Trigger” at a specific temperature. Events play a role in some of the metrics available in reporting, so it’s good to use them.
Now, it would be cumbersome to define all of this in each roast, so Profiles have the ability to define “Curve Templates”. You can set up a profile with reference reading curves by copying and pasting from a roast into the profile, then creating corresponding curve templates, with auto-trigger events for for the things you’re interested in at the appropriate temperatures, as well as the probe binding, color and other details.
Then, when you tag that profile in a roast, the curve templates will spawn identical curves as “Data Curves” in the roast, with the probe already bound, and events ready to go. Using profiles makes it quite literally a one (or two) tap affair.
3) Auto-trigger events will help you here too. You could define control curves, but they are formed by time, not temperature. The way I roast is by having certain triggers set on my “Bean Temp” curve, like “Open Damper full” at 185° C, etc. Make sure to set the “Alert Type” so that it either dings or alarms at the appropriate temp. You’ll get a banner alert, along with a sound if specified, in the analyzer when they are triggered.
4) The best thing here, if you’re trying to capture all the data you can, is by defining “Control” curve templates in your profile. Then you can enter the actual data in the control curve as you change it on the roaster. That would give you a static record of what control changes you made and when. I used to always record my control changes in control curves. I’ve since just come to rely on auto-trigger events and intuition. But, you can use both in tandem.
Hope this helps. If you have any other questions, let me know.
Danny
