Stokerlog Version 6


 
Just a follow up..

I didn't run any test runs last night, was busy with family. I started the stoker, checked "Enable Twitter", checked "Timed Cook" and went to settings to set the times, bad move on my part. The program immediately cycled through the 0's in the timed cook section and crashed giving this error.

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.OverflowException: Arithmetic operation resulted in an overflow.
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.Timer1_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.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.3603 (GDR.050727-3600)
CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
StokerLog
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/AmirM%20Software/StokerLog/StokerLog.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
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.3053 (netfxsp.050727-3000)
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.3053 (netfxsp.050727-3000)
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.3053 (netfxsp.050727-3000)
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/AmirM%20Software/StokerLog/ZedGraph.DLL
----------------------------------------
AxInterop.WMPLib
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/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/AmirM%20Software/StokerLog/Interop.WMPLib.DLL
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.JScript
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.3053
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.JScript/8.0.0.0__b03f5f7f11d50a3a/Microsoft.JScript.dll
----------------------------------------
System.Web
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.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.
 
Also, either timed settings aren't working quite right or I'm doing something wrong.

I set my times as

timer #1 120 m 170 df
timer #3 300 m 170 df
timer #3 500 m 170 df
timer #4 1200 m 130 df

Notice your timer numbers are incorrect, no biggie though.

When I enable the timers with the above settings I get the timer notes on the graph with in a minute or two and the temp drops to 52 deg f.

Twitter if interested...

http://twitter.com/StokerStatus
 
Another crash...


See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidCastException: Conversion from string ":" to type 'Integer' is not valid. ---> System.FormatException: Input string was not in a correct format.
at Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble(String Value, NumberFormatInfo NumberFormat)
at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(String Value)
--- End of inner exception stack trace ---
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.Timer1_Tick(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.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.3603 (GDR.050727-3600)
CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
StokerLog
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/AmirM%20Software/StokerLog/StokerLog.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
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.3053 (netfxsp.050727-3000)
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.3053 (netfxsp.050727-3000)
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.3053 (netfxsp.050727-3000)
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/AmirM%20Software/StokerLog/ZedGraph.DLL
----------------------------------------
AxInterop.WMPLib
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/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/AmirM%20Software/StokerLog/Interop.WMPLib.DLL
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.JScript
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.3053
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.JScript/8.0.0.0__b03f5f7f11d50a3a/Microsoft.JScript.dll
----------------------------------------
System.Web
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.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.
 
Joe, the last one is the stoker firmware crash I mentioned to Mark. Everyone is getting that even with last version of stokerlog. I will have to look at it. Can you tell me what the revision of your firmware is?

And thanks for the other reports. I will look at it little later. Should be able to find and fix them.
 
Yikes. He told me he had fixed this. Let me load it into my stoker and see if I can replicate it.
 
Brand new to stokerlog -- cool app! I had already updated my stoker firmware to the latest version and getting the same exception every few minutes.
 
Thanks Brian. Just upgraded the firmware and testing.

Until it fails, can you do me a favor? Look on your system and find a file called "telnet_input.txt". You might find multiple files with that name. Look at the date and find the one that corresponds with the date you saw the exception. Once you find it, please post the last few lines here.

Thanks.
 
Originally posted by joe thomas:
Also, either timed settings aren't working quite right or I'm doing something wrong.

I set my times as

timer #1 120 m 170 df
timer #3 300 m 170 df
timer #3 500 m 170 df
timer #4 1200 m 130 df
Click to expand...
I am still testing this. But one question, did you check the box "Timed Cook" before or after you filled the table? If you did it before, as you type the individual digits in the table, the take effect! So you need to only change the table if Timed Cook is not checked.

Notice your timer numbers are incorrect, no biggie though.
Click to expand...
Can you please clarify what is incorrect?
 
Oops, I found the last issue with Timer names being wrong...
icon_smile.gif
 
Hi Amir,

Last few lines here, and entire log at the following:

telnet_input.txt
<pre class="ip-ubbcode-code-pre">
B10000116EEDF730: 3 17.4 63.3 156.9 3.9 0.7 4.6 115.5 240 PID: NORM tgt:121.1 error:27.8 drive:0.8 istate:22.9 on:9 off:1 blwr:on

B10000116EEDF730: 3 17.4 63.3 157.5 3.9 0.7 4.6 115.9 240.6 PID: NORM tgt:121.1 error:26 drive:0.8 istate:23.2 on:9 off:1 blwr:on

B10000116EEDF730: 3 17.4 63.3 156.9 3.9 0.7 4.6 115.5 240 PID: NORM tgt:121.1 error:27.8 drive:0.9 istate:23.5 on:9 off:1 blwr:on

B10000116EEDF730: 3 17.4 63.3 156.9 3.9 0.7 4.6 115.5 240 PID: NORM tgt:121.1 error:27.8 drive:0.9 istate:23.8 on:9 off:1 blwr:on

B10000116EEDF730: 3 17.4 63.3 156.9 3.9 0.7 4.6 115.5 240 PID: NORM tgt:121.1 error:27.8 drive:0.9 istate:24 on:9 off:1 blwr:off

B10000116EEDF730: 3 17.4 63.3 156.9 3.9 0.7 4.6 115.5 240 PID: NORM tgt:121.1 error:27.8 drive:0.9 istate:24.3 on:9 off:1 blwr:on

B10000116EEDF730: 3 17.4 63.3 156.9 3.9 0.7 4.6 115.5 240 PID: NORM tgt:121.1 error:27.8 drive:0.9 istate:24.6 on:9 off:1 blwr:on

B10000116EEDF730: 3 17.4 63.3 156.3 3.9 0.7 4.6 115.2 239.3 PID: NORM tgt:121.1 error:29.7 drive:0.9 istate:24.9 on:10 off:0 blwr:on
</pre>

Thanks Amir!
icon_smile.gif
 
Thanks Brian. Unfortunately there is nothing unusual there. Seems like the last entry did not get recorded.

My stoker is still running
icon_frown.gif
.

Do you recall if you did anything special/different to cause it?
 
Hi Amir--

I wasn't doing anything unusual -- didn't have any options set (twitter, timed, etc.) -- in this case, I was only doing a pit probe/blower, no meat probe.

If you're willing, send me (or post) a debug build and the pdb file, and I'll run it through the VS debugger...
 
Hi, everyone:

Just joined and this is my first post. I see that several others are having the same problem with their stokers.

Hoping to get some help resolving the issue and am happy to contribute my experience with the failures.

I get the unhandled exception error within about 30-45 mins. of starting the s/w. Test conditions are simply setting it up to run on my dining room table w/o a heat source - I just set temps and alarms for a few degrees higher than room temp.

I just upgraded the firmware to 2.6.0.249 from 2.6.0.200 based on recommendations in previous posts. Stoker works fine using the internal server. Failure only occurs when using the s/w. I am running a mixture of old and new style probes, but don't think that should matter. No options are set (twitter, timed cook, etc.), just a straight fan, pit and meat probes. It fails with either single or dual pit configurations, new or old style probes.

Hope this helps and isn't too redundant from other posts.

EDIT: Incidentally, I've gotten failures on 4.0, 4.1, 6.1 & 6.2 releases of Stoker log.
 
Amir,

This may or may not be pertinent. I run StokerLog on a laptop and when the second StokerLog crash occurred it took out my Synaptics Touchpad drivers.
 
Thanks guys. My stoker ran for 22 hours with no failure despite messing with its configuration many times
icon_frown.gif
.

So I decided to rewrite the logic and catch the exceptions internally. Since this is the heart of the program, I need everyone's help to test and make sure I haven't broken anything else.

Here is the new version: http://www.amir-views.com/downloads/SetupV63.msi

Brian, here is the pdb file: http://www.amir-views.com/downloads/StokerLog.pdb. The above link is a debug build.
 
You must log in or register to reply here.

 

Back
Top