Tag: Roasting

  • Using Behmor 1600 Curves

    Using Behmor 1600 Curves

    Roastmaster provides the ability to create curves that match those on the Behmor® 1600 roaster. Behmor curves are display in the roasting graph just like standard curves, can be copied and pasted to profiles and programs, and can be time-shifted using the same algorithms the Behmor 1600 uses when performing time-shifts on the roaster’s console.

    The 1600 is unique in the way that it handles its internal roasting curves. They are calculated on-the-fly, based on 3 things:

    1. The Profile (the shape of the curve)
    2. The Program (the length of the roast calculated as a factor of the weight setting)
    3. The Weight setting (higher weight settings yield greater Program times).

    The 1600 allows some degree of customization based on the time shifts you apply to a curve. Time shifts you enter before a roast starts adjust every leg of the calculated heat curve evenly, adjusting each leg in proportion to fit the new time. Time shifts you apply after the roast begins affect only the final leg of the roast.

    How do I use them?

    You can create Behmor curves on the fly the same way you create regular curves in a roast as needed, or you can have them created automatically in roasts by turning the “Auto Behmor Curves” preference on in the preference settings. Then, whenever you choose an appropriate Profile, Program and Custom “Weight” Setting that is named in a way Roastmaster can identify, it will create the necessary curve automatically.

    Manual Behmor Curves

    The only thing you need to do is make sure the roaster entity in Roastmaster that represents your 1600 contains the string “Behmor” in the manufacturing field. Once you tag a roaster in a roast that meets this criterion, the “Create Behmor Curve…” option will be displayed when you tap the dark blue curve button on the roasting console.

    Automatic Behmor Curves

    Starting in Roastmaster iOS 7, you can simply select “Behmor 1600” in the add roaster setup assistant that appears when adding a new Roaster. Roastmaster will automatically create a Behmor roaster pre-configured for automatic Behmor curves, as well as enable the “Auto Behmor Curves” preference setting.

    First, verify that the “Auto Behmor Curves” preference setting in the Utilities section is turned on. Then, whenever you roast, you’ll need to choose the appropriately named Roaster for your roast, followed by one of its Profile, Program and Custom Weight Settings. These three entities are defined in the Roaster definition screen, and must all be present and chosen in a roast to trigger the creation of an automatic Behmor curve.

    To get started using automatic Behmor curves…

    1. Navigate to the Roaster section of the Utilities screen. Create a new roaster, and set the “Manufacturer” field to “Behmor”, and the model field to “1600″
    2. Within that roaster, create 5 Profiles, called “P1″, “P2″, “P3″, “P4″ and “P5″
    3. Create 4 Programs, called “A”, “B”, “C”, and “D”
    4. Create a Custom Setting Type called “Weight”, and within that Custom Setting Type, create 3 Custom Settings named “.25″ (or “1/4″), “.5″ (or “1/2″) or “1″.
    5. Save the Roaster, and you’re ready to roast.

    Or, simply import this Roaster definition on an iOS device to import directly into Roastmaster.

    In a new roast, simply choose that Roaster, and then the appropriate Profile, Program and Custom “Weight” Setting that correspond to the settings you will use on the Behmor itself. Roastmaster will reward you by automatically creating the necessary Behmor 1600 curve.

    Note: for any of the string patterns listed, the name must either match that string, or begin with that string followed by a space – e.g. a Profile titled either P1″ or “P1 Behmor Profile” would both be considered a positive match.

    How do they work?

    Once you’ve created a 1600 curve, and saved it to the current roast, selecting that curve in the graph will turn the new graph scale buttons (the “+” and “-” buttons) into time shift buttons. Tapping these buttons will apply the same logic to the curve that the Behmor 1600 applies to its internal curves, with respect to whether or not the roast is currently in progress. So, for every time shift you enter on the appliance, apply the same time shift to the selected Behmor 1600 curve in Roastmaster.

    If you need to look up the Behmor 1600 information contained in a 1600 curve, just go to the details screen of that curve. Swipe to the notes section – it will report the settings used to create the curve, as well as any time shifts you’ve applied to it – both before, and during, the roast.

    A few words about the design of Behmor 1600 curves in Roastmaster.

    Behmor curves are “opt-in”. Many 1600 users I’ve spoken with don’t care to track curves. They are quite happy roasting with the default settings, and not experimenting with time shifts. That, coupled with the fact that it is but one of the many roasters that folks are using, led me to design them to function modularly – the same way all other curves in Roastmaster work. In other words, a Behmor curve has no relationship to the details of the roast that contains it. The curve doesn’t care if you’ve tagged P1 in the roast – all it cares about is the setting you entered when you created the curve itself.

    Why? Well, Roastmaster is complex enough already, and at the end of the day simpler is better. If a Behmor 1600 curve were intrinsically linked with the profile/program data of the current roast, then (aside from making the interface more confusing) it would not be a viable curve outside of the context of a roast. Having a modular design gives you the freedom inherent in all curves, and will afford you the option to create custom Profiles for the 1600, based on curves you’ve tried and had success with.

    For instance, while testing the Behmor curves functionality, I happened upon a curve combination of P4/D that turns Central American beans into wonderful SO espresso! Go figure – surprised me too. The combination of the long roast time, and P4 heat ramp is a real winner.

    In future roasts where I want to target this same P4/D curve, I can record the Behmor details the standard way, and rely on the graph selector strip to find similar roasts for me, using the profile, program and curve buttons. In this scenario, the Behmor curves of previous roasts would be visible in the graph behind any current curves. I could create a new Behmor curve for each roast, and time shift to match the curves from the past roast(s) shown in the graph.

    I could, alternatively, copy and paste that P4/D curve into a new profile called “Central SO” that will sit along with the standard P1 – 5 default profiles, and tag only “Central SO” in the roast, ignoring the weight and program settings if I choose. In this scenario, every new roast with “Central SO” would automatically inherit that curve, and I could just look up the profile, program and time shift data in the curves detail screen, and set the Behmor console accordingly, ignoring all of the other custom Behmor settings. This would make roasting a bit quicker for often-used settings, as I wouldn’t have to do anything except tag the “Central SO” profile.

    I’ve learned a lot about this wonderful little (big) roaster while coding and testing 1600 curves. I hope it sheds a lot of light and helps you hone in on some winning combinations like it did for me.

  • Introducing the ThermoTooth 3000!

    Introducing the ThermoTooth 3000!

    Here it is – what I’ve affectionately dubbed the ThermoTooth 3000 – a fully wireless, dual channel, K style thermocouple prototype. She had her first successful Bluetooth session with my Mac tonight, and even with her limited code, she’s quite a smart gal! Over a simple wireless serial connection via terminal, I am able to select which thermocouple to monitor, and trigger individual Celsius or Fahrenheit readings, or both. No special drivers – just a Bluetooth serial connection.

    For the geeks like me, she’s built on an Arduino Uno prototyping controller board. Stacked on top of that is an XBee shield, providing the networking connectivity beyond the basic USB already present on the UNO. The XBee shield currently houses a Seeed Studio Bluetooth Bee, which provides the Bluetooth connection layer. The two K-style thermocouples connect to the Uno via two Max6675 chips, each providing cold-junction compensation and digital conversion of the thermocouple voltages for its independent channel. The sheer amount of electronics here is definitely overkill – I’m sure the cumulative brains of this could drive a car, but that’s how prototyping works.

    First off – it’s not meant for live production. I built it in the hopes I could pair it with an iOS device, and negotiate a wireless serial connection via Bluetooth. I know the device functions well, but the external connectivity of iOS itself still holds unknowns for me. The XBee shield offers the advantage of being able to swap a regular wireless network interface for the Bluetooth module in case the Bluetooth method is unsuccessful.

    Hopefully, a more permanent solution is on the way. I’ve been contacted by a manufacturer who is currently developing a Bluetooth thermocouple they plan to bring to market this fall. Naturally, this is great news for a lot of us looking for automated readings. They have not discussed the expected price, but the product itself sounds great! The manufacturer has agreed to sending me a prototype for evaluation once the release date gets closer, but in the mean time – I needed something to develop with now.

    This is why I built the TT3000. The majority of the code involved to implement thermocouple support will likely be designing the Roastmaster interfaces and its internal data structures, and setting up the communications framework to be used between roasting curves and wireless devices in general. The Bluetooth serial protocol has seemed quite easy to work with while prototyping the TT3000, so I’m hoping that this venture will be successful, and that adding support for the new product (as well as any others that may crop up), will be fairly easy to add ONCE I get support for wireless thermocouples in general built into Roastmaster.

    I’ll post back here with updates as development progresses. This isn’t at the absolute top of my development list – there are several feature requests/tweaks I want to finish up first, but I plan to be working on this until I find a workable solution.

    As always – if you have any input – please let me know.

    Cheers, Danny

  • The Big Roast

    The Big Roast

    Tonight’s roast is Java Kopi Sunda from the fine folks at Sweet Maria’s. It’s fairly exciting because it’s a new bean for me. I’m anxious to pull a couple of shots tomorrow! But, the excitement doesn’t end there… tonight’s roast is a bit more special – it’s my first roast with the dev version of Roastmaster on the iPad! Now – I know a lot of you are waiting very patiently – it’s not completed yet, but I’m hopeful that a large chunk of the hard work to out of the way.

    I have to say, I doubt I’ll ever go back to the iPhone for roasting. If you’re used to Roastmaster on the iPhone or iPod Touch, the best way to describe using it on the iPad is liberating. Liberating and liquid. Navigating the app is incredibly fluid. The extra screen real estate affords a less cluttered interface – and the ability to hone in on the details you are looking for much more easily than the iPhone version. And, pairing it with a bluetooth keyboard… well – it’s heaven for me!

    Take a look at the screenshots. I will undoubtedly make a few tweaks – a couple of things are bugging me at the moment, but I’m comfortable enough with them at the moment to share them. The first thing you’ll probably notice is the landscape orientation. This is long overdue, and for the iPad – in my opinion, it’s a necessity. Another difference I was able to work into the iPad version is static headers. Headers are nice – they’re a functional and efficient way to present important information for browsing through records, but on the iPhone it was imperative to get them out of the way via scrolling when it came time to enter data. Not so on the iPad! I played around with a couple of designs – one with scrolling headers like the iPhone, and the version that won hands down – static headers. I’m sure you’ll agree – it’s a great way to have a succinct summary to reference – even when entering data on static screens like beans, blends and cuppings. And for roasts, to be able to have the roasting console front and center while you browse the roast data, well… again, I’m in heaven.

    Thanks to all who’ve offered to beta-test. This is new territory for me – I’ve never dealt with public beta-testing for iOS. All of the initial Roastmaster testing was done with devices I had direct access to. I’ll be in touch soon to get the process started. I’ll also post if I end up needing more beta-testers in case anyone is interested. I doubt it at this point – many people have already been in touch, but things can always change.

    ‘Til then, know that I’ll be working very hard to get the universal version finished up as quickly as possible.

    Cheers,
    Danny