DivotMaker
New member
Edit: For those of you who don't know, I'm testing a new digitally-controlled Smokin-It Model 2. This is the first smoke in that unit. Read about the testing here:
http://smokinitforums.com/index.php?topic=1345.0
Today, I'm finally doing a test of the new Electronic Model 2 prototype under "actual operational conditions." Hehe...I'm giddy with excitement!!
The "test subjects" are 3 racks of baby back ribs from Sam's. Big, meaty ribs, coming in at 10.57 lbs! They got the silverskin removed, coated with olive oil (trying it as a binder instead of mustard) and Famous Dave's rib rub.
In the smoker they went at 10:30. There was 3 oz of hickory & cherry (50/50) and a pan of apple juice already in there to keep them company, so the ribs were happy.
To test my theory on preventing the "smoke belch," I initially set the temp to 140. Smoke began at :11 in, and the temp climbed to 140 within about 30 minutes. When the controller went into "maintenance mode" (green light instead of red), I let it "rest" there for 5 minutes, then upped the temp to 170. When the controller hit 170, there was a very small smoke belch. It pulsed a little (sucked air in the top hole), then stopped. I let it rest at 170 for 5 minutes before increasing temp to 225.
When the temp increased from 170, an interesting thing happened; the onboard controller and the Maverick stayed within 1-2 degrees until the box temp hit 210. At that point, the SI temp kept climbing to 219, and it went into maintenance mode. Hmm. The box temp actually dropped to 201, and the controller showed 221. I increased the set temp to 230, and the element came back on.
Once it hit 230 (1 hour into the cook), the box temp has varied from 215 to 234. The controller temp has only varied a few degrees above or below 230. So, it appears the temp probe is not reacting fast enough. The controller board "thinks" it's holding 230, when it's really not.
The ribs should be ready about 4-4:30, so I'll update you on the results! I have a feeling they'll be good! I know these temp swings are not any more than my #1, and will "even out" over the length of the smoke.
http://smokinitforums.com/index.php?topic=1345.0
Today, I'm finally doing a test of the new Electronic Model 2 prototype under "actual operational conditions." Hehe...I'm giddy with excitement!!
The "test subjects" are 3 racks of baby back ribs from Sam's. Big, meaty ribs, coming in at 10.57 lbs! They got the silverskin removed, coated with olive oil (trying it as a binder instead of mustard) and Famous Dave's rib rub.
In the smoker they went at 10:30. There was 3 oz of hickory & cherry (50/50) and a pan of apple juice already in there to keep them company, so the ribs were happy.
To test my theory on preventing the "smoke belch," I initially set the temp to 140. Smoke began at :11 in, and the temp climbed to 140 within about 30 minutes. When the controller went into "maintenance mode" (green light instead of red), I let it "rest" there for 5 minutes, then upped the temp to 170. When the controller hit 170, there was a very small smoke belch. It pulsed a little (sucked air in the top hole), then stopped. I let it rest at 170 for 5 minutes before increasing temp to 225.
When the temp increased from 170, an interesting thing happened; the onboard controller and the Maverick stayed within 1-2 degrees until the box temp hit 210. At that point, the SI temp kept climbing to 219, and it went into maintenance mode. Hmm. The box temp actually dropped to 201, and the controller showed 221. I increased the set temp to 230, and the element came back on.
Once it hit 230 (1 hour into the cook), the box temp has varied from 215 to 234. The controller temp has only varied a few degrees above or below 230. So, it appears the temp probe is not reacting fast enough. The controller board "thinks" it's holding 230, when it's really not.
The ribs should be ready about 4-4:30, so I'll update you on the results! I have a feeling they'll be good! I know these temp swings are not any more than my #1, and will "even out" over the length of the smoke.
. Updates???
