I have an accuracy issue with my Auber temperature sensor, and it goes something like this. I have a separate thermometer, and when the Auber is first on, the rwo agree within a degree. As the Auber probe remains in the pot however, the difference in measurements increase, until after some time, I see this.

Pot equilibrated to a measurement of 144, a few minutes after adding chicken. Note the temp difference between the two probes. Who to believe?
So who to believe? I’m concerned the Auber is underestimating temperature, because of the beef color of cuts like this, which was supposed to be cooked at 130 to 132 degrees F.
So yes, I’m looking into how to accurately gauge and calibrate temperature with this setup. I’ve also been playing with higher temperatures, in part so I can cook chicken, which is a substantially smaller portion of meat than some of these big steaks I’ve been eating.
Jimmy (@EatItAtlanta) tweeted before my experiments that he wasn’t happy with the meat near the bone of chicken cooked at 140 F. Since I’m using a PID controller, and it overshoots temp by 2 degrees during the first couple hours, then the kinds of temperatures I’m looking at for my setpoint are 2 degrees below the cooking point. But if it’s actually running 3 degrees cool, I need to compensate by 5 degrees. Does that make sense?

PID controllers overshoot and then narrow in on their target temperatures. That first overshoot peak defines the actual cooking temperature for my controller. In practice, I overshoot by about 2 degrees F. Image above from Wikimedia, and the PID controller article on Wikipedia.
The French Culinary Institute’s PDF on sous-vide recommends 1-2 hours for chicken at 65-66C (149-151 F), and that means the two Auber temperature settings I needed to test are 144 F and 147 F. So we tested those.

Spiced and sealed. I used cracked black pepper, red pepper, crushed red pepper (pizza pepper), some onion and garlic powder, and a dusting of poultry seasoning.

Cooked 90 minutes at 144 from room temp and plated. 2.5 hrs at 147 from frozen has a similar appearance. I prefer the flavor and texture of the hotter product.
Results? I liked my chicken better at 147 than 144. The looks are about the same at both, and at both, you really do need to trim off the chicken fat, because unlike frying, the fat that results from this technique isn’t much fun to eat. The chicken is amazingly juicy, and you might find it not cooked enough for your tastes. If so, just keep ramping up the temperatures until you’re happy with what comes out of the controller.
As for me, I need a better way to calibrate my device. I would like to nail a good medium rare on the steak side. For now, I have a useful working temperature on the chicken side.



March 16, 2012 at 1:04 pm
There are folks on our board that have fiddled around with it for a couple years. and I agree Jimmy is a good source of data and experience.
Did you sous vide the Brussels sprouts? I would be interested in that …
Practice makes perfect.
March 16, 2012 at 11:22 pm
My understanding is that sous-vide and vegetables is something of a lost cause, compared to other cooking methods. Those Brussels sprouts were steamed in the microwave.
March 16, 2012 at 5:12 pm
When I’m using heat – as opposed to sous vide – I pull meat for MR at 117 degrees so that after resting (and carry over heating) the steak is about 123 degrees. It’s always MR. I don’t trust anyone who says that 140 is rare. I pull mine (for rare) at 104 degrees.
Just my $.02
March 17, 2012 at 2:22 pm
Certain vegetables are amazing sous vide, but never sous vide greens. (Per Thomas Keller)
Try carrots or beats. They are stunning. You have to cook at 185F though, for at least one hour.
My PID is off too, but I’ve just figured out the exact variance and keep that in mind when I’m setting the temperature. It could probably be calculated, but my PID is very….rustic and came with unintelligible instructions.
May 7, 2012 at 5:19 pm
Agree: 147F is perfect for chicken thighs!