Glad to hear - the Quest is a fun machine to roast on!

Yes, my plans actually account for both. Programmatically speaking, curve events would have a internal switch, something like "Dynamic" or "Static". Dynamic events could be temperature-driven and defined beforehand, in a new curve or a curve template. Once the temperature is triggered, an alert would be presented. The event could then potentially become a static, time-stamped marker on the curve at the point in which it happened, and display as some type of tappable note or pin icon on the curve.

This would allow you to create your own time-stamped notes on a curve during a roast, or have them automatically created on the curve based on temps. Those markers would then, of course, travel with that curve to future profiles and such.

For events you create before-hand, I envision a simple setup screen that includes a control for the action to be taken with that event when the temp trigger is met, with choices such as "Alert", "Create Marker" and "Both".

Hello.

Good choice on the Quest! Yes, you are correct. Just two parts: 1) Roastmaster/iPad, which communicates wirelessly to 2) Quest/Bluetherm/Probes.

Phidgets would afford the possibility of a third probe. Some people run 3 - I only run 2, and truth be told, I never even look at my second probe - I only pay attention to the BT. For me, all I need to know can be more easily ascertained by knowing the relative charge of the drum, and employing the temp projection markers in Roastmaster. Your mileage, or course, may vary.

Long story short - the Bluetherm Duo works great for the Quest. I got my fittings from Eric as well - I opted for the drilled M8s, because I swap probes a lot, and wanted to keep that process hassle-free.

Anything else? Beyond RM, iPad/Phone and the data logging option... just beans.

Let me know when you get the hardware - I'll send you a couple of profiles to get you started.

Danny