hi guys,

is there a good (+simple/convenient) roast logging tool people use for hh506ra?

here's the major features i'm looking for:

1. Show graph of BT/MET as the roast is going.

2. Graph width (length of minutes shown) should be adjustable... in the freebie logging tool, u can see a chart, but it's not useful as roast starts since it shows just captured data up to that moment, making it harder to see the 'shape' you are heading towards.

3. Set basic roast info like date, time, coffee, batch size, comments

4. Buttons to start/end roast, mark 1C, 2C. Dropdowns to choose current power/fan settings.

5. Show critical data points like Elapsed Time, MET, BT, Max MET, *Rates of Change per minute*.

6. Enable alerts (e.g. speech of current Time/BT/MET per set interval and/or when reaches certain 'alarm' points).

7. Save/load/print data (make smaller labels with profile data/chart to stick on jars).

8. Allow to load 'target' roast... which will show a previous graph (in dotted line) as u roast the current, so can see if u stay on track, or make a small change in desired section for comparison/learning. Would be nice to be able to offset this chart as needed... in case recovery point comes a bit later, u can shift it to still see the 2 graphs together.

I got a prototype started that does most of this, but thought maybe i should ask first if something exists already... might save me the few hours of finishing it, or get more ideas to add into it.

I am working on one. ETA Christmas.



I sent an email to Omega asking for little info but received no answer back. But the hh506ra looks easy to interface and there is some info on the internet. I can already load hh506ra files directly (not real time) and postedit all the roast properties but I don't own/hold the hh506ra meter myself. Once I get a hold of one hh506ra I could make it work (real time).

Cheers

cool, looks nice, i like that you incorporate taste objectives.

in case u didn't run into this page: http://www.jacquesf.com/blog/2010/03/om...-protocol/

he shows how to pull the current probe temps by sending: #001N\r\n

it works great.... u get glitches here and there, but i'm querying every 1 sec, u can see just 2 happened in today's test run... i'm going to adjust to it skips over those. i just gotta add the BT/MET change rates & loading of target profile, and i think it can become very helpful... i like the speech feature during pre-heat... i can set the roaster to coast on certain temp and listen from upstairs as i watch TV that it stays at my target

What do you mean by speech feature? I have plans to start a C pop detector (through sound card) sometime next year.

Cheers

not as sophisticated as that

...notice the 'Enable Speech, Alert Interval (sec)' option there under Start Roast button -- if it's checked the tool will just 'speak' the current Time, MET, BT every x seconds.

OK. That's cool.

I have mine set up to print the profile after each roast. But by Christmas I hope to upgrade to a full report. That way I can tag each coffee canister.

Cheers

Probably not ideal for this application but it should work:

Roast Logger with multimeter USB cable & webcam input

I wonder how critical it is to log the Fan/Power...
On the M3 i also noticed the fan is super sensitive (and effective)... I use it a lot sometimes to control the MET, so i think by trying to reproduce a roast profile by replicating your input controls won't be always simple (i kinda gave up on setting which power/fan i'm currently on). I guess initially it can give u idea of how roaster works, but once u get it, i'm thinking it becomes second nature to know what to change to reach what u need.

With Moka Kadir below, i found it's just perfect if 1C starts at 440f MET and maintained. Very nice spread out crack activity... if i wanted to stretch it further, i think i'd come in at 440, and start dropping a bit after 1C ends (?):


I can print the tool screen itself with File->Print, and it automatically resizes it to print all the data + chart in size that fits (and i can read clearly) on a mason jar:


I separated the ability to start logging data, and starting the roast, so i can capture some of the graph data before/after roast... but still when u hit 'start roast' chart will shift data so roast start time is at 0:00 so charts will be consistent and easy to tell differences by a quick glance. I also thought to add an 'auto charge detect', so it'll recognize by itself roast started when BT drops. When you hit button to end roast, it'll stop updating the displayed MET/BT (but still log in the chart), so those are the temps right before dropping beans. Looking at the ones below, it's quick to see one on top had longer drying period due to the lower charge temp (accident)... and one on bottom right, i got charge temp right, but came in higher than 440 into 1C, therefore it was quicker finish stage (3min vs 4). Bottom left i reached the goal i wanted. Very cool, now i'm hoping i can start relating some of these differences to taste :

Ben -

What are your plans for your roast logger software? If your intentions are for it to become an open source application, then I would love to try and write an interface to the TC4 Arduino shield I'm using with my roaster.

A small group on homeroasters.org has collaborated and written a modest open source Processing application for realtime graphing and roast monitoring on a PC (serial interface). But your application is far more advanced, and I suspect it could be adapted without too much difficulty to read the data stream coming from the Arduino shield.

Jim

I don't really have any plans for it, originally, i thought maybe something out there can do it already...
I'm eager to see the final tool arpi will make. For now, i was just adding a few features to work for my needs... though i don't think it needs much else -- the ability to see a graph as I roast has proven to be so helpful... i can't imagine going back to what i was doing before [looking at my omega and trying to count in my head to get the feel of current rate, and writing down on a piece of tape vital data].

It's not professional code at all, since i was speed-writing it... but if anyone wants to glance at it, i can send it... just msg me your email... (it's written in .NET3.5, c#)

The old labels below (since i was too lazy to keep transferring data to excel and formatting charts):