Stokerlog Version 6


 
They all work but some work better than others. When I updated to the last version, it was very slow and I compensated in stokerlog by changing the timeouts. At some point I may go back and reduce the timeouts in which case, that version wouldn't work as well. But for now, I think they are all OK, sans whatever causes the above errors
icon_smile.gif
.
 
I may have missed it... Stoker on order...
but can the Stoker be controlled to ramp up the pit temp during the cook cycle, say..

pit 180 until food is 140,
pit to 200, until food is 180,
pit to 225, until food is 200,
pit to 205, food done @ 200.
 
Amir,

I was playing around with stokerlog the other day, and came across an issue that I wanted to run by you. The improvement you made where you can power cycle the stoker itself and stokerlog will keep trying to reconnect is great. However, is there any way for the stokerlog to alarm if it has been disconnected for a certain period of time, say 10 minutes? My reasoning is that if I'm doing an overnight cook and the power to my stoker goes out, I won't know about it until I actually look at stokerlog. I would like to have an option for an audible alarm.

And I know I can use an older version, but I really like the timer feature in the current one.


Thanks again,

Pat
 
Originally posted by BMerrill:
I may have missed it... Stoker on order...
but can the Stoker be controlled to ramp up the pit temp during the cook cycle, say..

pit 180 until food is 140,
pit to 200, until food is 180,
pit to 225, until food is 200,
pit to 205, food done @ 200.
Click to expand...
No, it has a time based system that changes the target temp but not based on current food temp. What would be the application of having it work this way?
 
Pat, I am not home right now so can't recall whether the current connection lost alarm is completely broken or not.

Let me look at that when I get a few minutes and report back.
 
I hadn't thought about an alarm before... it'd be great if StokerLog could set off an alarm if it loses connection... and if it could power-cycle the stoker in those cases, that, too, would be good. I'll be watching closely for those options!
icon_biggrin.gif
 
Originally posted by Amir:
<BLOCKQUOTE class="ip-ubbcode-quote"><div class="ip-ubbcode-quote-title">quote:</div><div class="ip-ubbcode-quote-content">Originally posted by BMerrill:
I may have missed it... Stoker on order...
but can the Stoker be controlled to ramp up the pit temp during the cook cycle, say..

pit 180 until food is 140,
pit to 200, until food is 180,
pit to 225, until food is 200,
pit to 205, food done @ 200.
Click to expand...
No, it has a time based system that changes the target temp but not based on current food temp. What would be the application of having it work this way? </div></BLOCKQUOTE>

Take for example the all forgiven pork butt. The theory is keep the pit temp as low as possible for as long as possible in the hot smoke temp range (165-180) allowing the meat to absorb as much smoke as possible. It is a general consensus meat absorbs the most smoke below a meat temp of 140. The first ramp up would occur at meat temp of 140 and basically stay 25-30 degrees above the meat temp until target temp is reached. This close pit-temp to food-temp provides a more overall even temp in the meat and less loss of moisture.
You mention the temp increase is time based, but the time is related to our approximate guess or measurement of doneness (food temp). Why not just use the food temp?
If you could add this to the wish list it would be greatly appreciated.
Best regards,
Billy
 
Take for example the all forgiven pork butt. The theory is keep the pit temp as low as possible for as long as possible in the hot smoke temp range (165-180) allowing the meat to absorb as much smoke as possible. It is a general consensus meat absorbs the most smoke below a meat temp of 140. The first ramp up would occur at meat temp of 140 and basically stay 25-30 degrees above the meat temp until target temp is reached. This close pit-temp to food-temp provides a more overall even temp in the meat and less loss of moisture.
You mention the temp increase is time based, but the time is related to our approximate guess or measurement of doneness (food temp). Why not just use the food temp?
If you could add this to the wish list it would be greatly appreciated.
Best regards,
Billy
Click to expand...

I don't agree with much of what you say.

Who is cooking pork at 165-180 in order to absorb as much smoke as possible? What theory is that?

What consensus exists about smoke absorption below 140? Smoke ring formation, perhaps, but smoke flavor no. Cook 2 butts, take one off at 140 and put it in the oven. Continue to pour on the smoke for the second one and see if it is different.

Seems like a long way to cook a pork butt, especially on a WSM. Probably have it on for 20 hours at least.
 
Originally posted by BMerrill:
You mention the temp increase is time based, but the time is related to our approximate guess or measurement of doneness (food temp). Why not just use the food temp?
Click to expand...
The main use for time based is for things like ribs where you don't use temp probes but rather follow schemes like 3-1-1.

If you could add this to the wish list it would be greatly appreciated.
Best regards,
Billy
Click to expand...
It is not too much work. If there is more consensus for usefulness of it, I will add it in.
 
Thanks for the reply. I'll try to answer some of your questions.

Originally posted by Pat McCreight:
I don't agree with much of what you say.
Click to expand...

Sorry you don't agree with much about the posted cooking methods.

This thread is for discussions of Stokerlog and the post was in reply to Amir's responses to a feature request I made. The cook log was provided as an example of using food temps as a control trigger to raise pit temps. If you cook this way as many do, having an option to regulate pit temps by meat temp would be a welcoming addition to the StokerLog program. If you use the "Keep Warm" feature, then you are using food temp to control pit temp.

Who is cooking pork at 165-180 in order to absorb as much smoke as possible? What theory is that?
Click to expand...

I know of many pitmasters that do, others use straight 225 or 250 or ###. This also depends on the type of smoker/cooker you are using. Some smokers/cookers can not maintain a fire at such low pit temps.

Theory or fact? Longer in the smoke the more smoke flavor.

What consensus exists about smoke absorption below 140? Smoke ring formation, perhaps, but smoke flavor no. Cook 2 butts, take one off at 140 and put it in the oven. Continue to pour on the smoke for the second one and see if it is different.
Click to expand...

We have all read from various forums and websites the "140 theory" that meat stops taking on more smoke flavor around 140. I agree with you on this as I have never read anything but what seems speculation lacking hard facts. For those that start a smoke at low pit temps (165-180), the 140 temp (within 25d of pit temp)is a good place to start ramping up the pit temp. Maybe I should have left the reference to the "140 theory" out of the post.

Seems like a long way to cook a pork butt, especially on a WSM. Probably have it on for 20 hours at least.
Click to expand...

Takes about 14 to 16 hours on my smoker. YMMV

Not everyone who uses the Stoker and StokerLog are WSM owners. The TVWBB just happens to be the venue Amir has chosen to interact with the Stoker/Stokerlog users. It is from suggestions through this forum that StokerLog has evolved into a great webapp/program that Amir has freely shared. Thanks Amir!
 
Any idea what's going on here? This is the first time that I have used StokerLog on the new computer. Windows 7 64bit.

StokerLogError.jpg
[/IMG]
 
Click on Detail and post what you see in addition to telling us a bit more about what led to it.

In general, the only known error is permissions so be sure you are running as admin. There is a file that is being put some place where you don't have permission (on todo list to fix
icon_smile.gif
).
 
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.UnauthorizedAccessException: Access to the path 'C:\Program Files (x86)\AmirM Software\StokerLog\StokerLog.txt' is denied.
at Microsoft.VisualBasic.CompilerServices.Symbols.Container.InvokeMethod(Method TargetProcedure, Object[] Arguments, Boolean[] CopyBack, BindingFlags Flags)
at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateGet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack)
at StokerLog.StokerLog.StartButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
StokerLog
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/AmirM%20Software/StokerLog/StokerLog.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
ZedGraph
Assembly Version: 5.0.7.40149
Win32 Version: 5.0.7.40149
CodeBase: file:///C:/Program%20Files%20(x86)/AmirM%20Software/StokerLog/ZedGraph.DLL
----------------------------------------
AxInterop.WMPLib
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/AmirM%20Software/StokerLog/AxInterop.WMPLib.DLL
----------------------------------------
Interop.WMPLib
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/AmirM%20Software/StokerLog/Interop.WMPLib.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
 
You must log in or register to reply here.

 

Back
Top