The FrogPad
 
A forum to get help or talk about Roastmaster…or anything else coffee.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - quality45374

Pages: [1]
1
Support / Recording Maintenance in Version iOS 10.1
« on: July 29, 2017, 10:11:37 PM »
Sorry to be dumb, but I used to be able to reset the Behmor counter in the older versions of Roastmaster pretty easily. After roasting today I went to reset the counter as usual, but I find there is a newish maintenance interface, and for the life of me I can't find how to shut off the overdue cleaning notice. Clue a brother in? Thanks in advance.

2
Support / Artifact Data in Curves?
« on: December 24, 2016, 04:17:50 AM »
Your app is very polished and flexible. In a way it is similar to a computer algebra system like Mathematica or MATLAB, in that one can use it a fair amount and still only scratch the surface with respect to capabilities.

I use Roastmaster to track temperature data while roasting on a Behmor 1600+. In addition to the default P1... P5 Behmor profiles you have programmed into the app, I have added a few since I normally roast in manual mode.

I added some curves, as well, one for each of the custom profiles I added.

My question is regarding artifact data from the curves. Roastmaster seems to save the data from the first time the nodes of a particular curve are populated. And the artifact data is copied into every roast which then uses that curve. And I have no idea how to prevent this or how I should be using the app differently to prevent this.

For example, say I have created a profile called "Manual Mode." It uses a curve called "B-Sensor Temperature." So I roast a wide variety of beans using this profile, and I log the temperature data manually. But each time I start a roast using this profile, the curve appears in the roasting console, pre-populated with the nodes from what seems to be the first roast done with this curve. Those nodes are propagated to each roast using the curve, and unless one overwrites them or manually deletes them (one by one), they contaminate each use of the curve.

How can I prevent this? How should I be using the app differently so that it doesn't happen?

Pages: [1]