Hi folks, I hope you’re all well…
I did a few roasts today using the Recipe Function, making tweaks to each subsequent roast using the Recipe editor, and using Recipe Playback to do each roast… mostly it was fine, but there are some very clunky things that could be improved upon. 7/ is my most wanted feature…
1/ when creating recipe, if you have chosen in Settings to see IBTS as “Primary Measure”, the recipe should default to IBTS, not to probe.
2/ when creating recipe, one should be able to have events listed in the order they were created, and have the ability to drag drop to reorder the events in the order you foresee them occurring.
3/ when creating a recipe, the time elapsed based events should be able to be triggered by elapsed time past a previous or any specified event, for example, the ability to create a trigger to activate 1 minute after 200°C is reached, etc.
4/ When you create a recipe, all events are added with time AND temp, even if you are choosing ONLY temperature (and not time). This causes a mess because typically the default time is “Time Elapsed (>=) 00:05” which means the events are randomly ordered due to this unneeded time value.
5/ similarly, it would be good to be able to click to remove timing from an event once it is already in the event ( ie: to be able to have a Temperature-based event that does not have any Time Elapsed info)
6/ recipe bug - After creating a recipe, if you then save and go back to the list of recipes, and then click on one of your recipes and go to the recipe editing interface, then edit the name of the recipe and click save, it does not save. You have to make at least one change to one of the events and then press save. Otherwise it does not save. This is repeatable bug, but you have to first create a recipe, then go back to recipe list, then back to edit name.
7/ This is an important feature request! it would make a huge difference to be able to have graphic indication of the recipe in progress when you Start Playback in recipe mode. At the moment, you roast blind, and you can only watch Roastime monitoring the roast, but really, it is in Playback mode, so it would make sense and be VERY useful for the user to see the P F D timeline below the graph so one can see how things are going and anticipate what is about to be triggered.
8/ Fan greyed out bug? If you have a previous TEMP based event, say 180°c to set P6 F3 and then you try to set another TEMP based event, say 190°c to change the fan to F4, you cannot, it is greyed out. It seems the cause is the unnecessary and forced addition of TIME to a TEMP-based action. If you ignore this unnecessary time parameter, it will default to 00:05 for both your TEMP-based events. This should not happen, even with the times clashing, as the one would go off at 180 as it is past 00:05 and then the next should trigger as it is also past 00:05 and at 190°… greying it out makes no sense, and also it is an illustration of the unnecessary and time-wasting nature of adding TIME parameters to a TEMP event.
Tx people,
Mark
