Hi Amir,

I double checked the version. It is indeed 6.3. I've uninstalled the program and reinstalled it and will try it again.

Thanks for the help.

Another exception after only 15 minutes or so under the following conditions: Running 1 fan w/control and meat temp probes. Probes are old style. Rel .249 firmware and 6.3 stoker log.

Hope there is relevant data in this post.


Exception data:

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) in C:\Documents and Settings\Amir\My Documents\Visual Studio 2005\Projects\stoker\Stoker\Stoker\Stokerlog.vb:line 1069
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
----------------------------------------
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.


Telnet input file:



760000127E6AD630: 3 19.8 67.5 -5 0.1 0.8 0.7 19.6 67.3 PID: NORM tgt:22.2 error:12.8 drive:0.8 istate:54.5 on:9 off:1 blwrn

760000127E6AD630: 3 19.8 67.5 -5 0.1 0.8 0.7 19.6 67.3 PID: NORM tgt:22.2 error:12.8 drive:0.8 istate:54.5 on:9 off:1 blwrn

C00000127E845930: 3 19.9 67.8 -10 0.3 0.8 0.5 16.6 61.9

760000127E6AD630: 3 19.8 67.5 -5 0.1 0.8 0.7 19.6 67.3 PID: NORM tgt:22.2 error:12.8 drive:0.8 istate:54.6 on:9 off:1 blwrn

760000127E6AD630: 3 19.8 67.5 -5 0.1 0.8 0.7 19.6 67.3 PID: NORM tgt:22.2 error:12.8 drive:0.8 istate:54.6 on:9 off:1 blwrn

C00000127E845930: 3 19.9 67.8 -10 0.3 0.8 0.5 16.6 61.9

760000127E6AD630: 3 19.8 67.5 -5 0.1 0.8 0.7 19.6 67.3 PID: NORM tgt:22.2 error:12.8 drive:0.8 istate:54.8 on:9 off:1 blwrff

760000127E6AD630: 3 19.8 67.5 -5 0.1 0.8 0.7 19.6 67.3 PID: NORM tgt:22.2 error:12.8 drive:0.8 istate:54.8 on:9 off:1 blwrff

C00000127E845930: 3 19.9 67.8 -9.4 0.2 0.8 0.5 17 62.6

760000127E6AD630: 3 19.6 67.3 -5 0.1 0.8 0.7 19.5 67.1 PID: NORM tgt:22.2 error:13.6 drive:0.8 istate:54.9 on:9 off:1 blwrn

760000127E6AD630: 3 19.6 67.3 -5 0.1 0.8 0.7 19.5 67.1 PID: NORM tgt:22.2 error:13.6 drive:0.8 istate:54.9 on:9 off:1 blwrn

C00000127E845930: 3 20 68 -9.4 0.2 0.8 0.6 17.1 62.8

760000127E6AD630: 3 19.8 67.5 -5 0.1 0.8 0.7 19.6 67.3 PID: NORM tgt:22.2 error:12.8 drive:0.8 istate:55 on:9 off:1 blwrn

760000127E6AD630: 3 19.8 67.5 -5 0.1 0.8 0.7 19.6 67.3 PID: NORM tgt:22.2 error:12.8 drive:0.8 istate:55 on:9 off:1 blwrn

C00000127E845930: 3 19.9 67.8 -9.4 0.2 0.8 0.5 17 62.6

760000127E6AD630: 3 19.8 67.5 -5 0.1 0.8 0.7 19.6 67.3 PID: NORM tgt:22.2 error:12.8 drive:0.8 istate:55.1 on:9 off:1 blwrn

C00000127E845930: 3 19.9 67.8 -10 0.3 0.8 0.5 16.6 61.9

760000127E6AD630: 3 19.8 67.5 -5 0.1 0.8 0.7 19.6 67.3 PID: NORM tgt:22.2 error:12.8 drive:0.8 istate:55.3 on:9 off:1 blwrn

C00000127E845930: 3 19.9 67.8 -10 0.3 0.8 0.5 16.6 61.9

760000127E6AD630: 3 19.6 67.3 -5 0.1 0.8 0.7 19.5 67.1 PID: NORM tgt:22.2 error:13.6 drive:0.8 istate:55.4 on:9 off:1 blwrn

C00000127E845930: 3 19.9 67.8 -10 0.3 0.8 0.5 16.6 61.9

760000127E6AD630: 3 19.8 67.5 -5 0.1 0.8 0.7 19.6 67.3 PID: NORM tgt:22.2 error:12.8 drive:0.8 istate:55.5 on:9 off:1 blwrn

C00000127E845930: 3 19.9 67.8 -10 0.3 0.8 0.5 16.6 61.9

760000127E6AD630: 3 19.6 67.3 -5 0.1 0.8 0.7 19.5 67.1 PID: NORM tgt:22.2 error:13.6 drive:0.8 istate:55.7 on:9 off:1 blwrn

C00000127E845930: 3 20 68 -9.4 0.2 0.8 0.6 17.1 62.8

760000127E6AD630: 3 19.8 67.5 -5 0.1 0.8 0.7 19.6 67.3 PID: NORM tgt:22.2 error:12.8 drive:0.8 istate:55.8 on:9 off:1 blwrn

C00000127E845930: 3 19.9 67.8 -10 0.3 0.8 0.5 16.6 61.9

760000127E6AD630: 3 19.8 67.5 -5 0.1 0.8 0.7 19.6 67.3 PID: NORM tgt:22.2 error:12.8 drive:0.8 istate:55.9 on:9 off:1 blwrn

C00000127E845930: 3 19.9 67.8 -10 0.3 0.8 0.5 16.6 61.9

760000127E6AD630: 3 19.8 67.5 -5.6 0.1 0.8 0.6 19.3 66.6 PID: NORM tgt:22.2 error:14.8 drive:0.9 istate:56.1 on:10 off:0 blwrff

Boy, this is going to be tough to debug .

Please try this version (6.4): http://www.amir-views.com/downloads/SetupV64.msi

quote:

Boy, this is going to be tough to debug

That's why we pay you the big bucks.

Amir,

Running latest firmware and V 6.4. I'm 2 hrs into cook, actually still warming up smoker, and no exception errors yet. I still can't get the timed settings to work right as they tick off in a few minutes and drop the target temp to 52 degrees. I assume the timer settings are self explanatory but maybe I'm missing something. For grins I left the settings at the program defaults...

time 60 min temp 150
time 120 min temp 150
time 180 min temp 150
time 240 min temp 150

StokerLog still dropped the temp to 52 D F in a few minutes. Any explanation as to what I may be doing wrong?

Today's cook full turkey breast as a trial run for Thanksgiving.

Twitter seems to be running better too...

http://twitter.com/StokerStatus

edit: changed trail to trial

quote:

Hide Post
Boy, this is going to be tough to debug Smiler.

Hi Amir,

Can you give me a feel for what this error means? Is there something that I can check from a system standpoint - hdw./connections, .Net version, network drivers, etc.?

I'd like to be able to help out if I can.

I'll test 6.4 tonight and let you know.

Today's attempt. I'm playing with the camera too...

Amir what's a "Bad fan string"? This message keeps popping up in the status box of StokerLog during the cook. I have yet to receive an exception error though.

quote:

Originally posted by joe thomas:
Amir what's a "Bad fan string"? This message keeps popping up in the status box of StokerLog during the cook. I have yet to receive an exception error though.

This is the fix I just put in (which answers David's question also).

Basically, I have to parse (interpret) a string that tells me if the fan is on or not. Somehow the string is coming back different in newer firmware than it did for the ones we used to see. Stokerlog expects a number and instead sees a character. The compiler then generates an exception saying it can't convert a character to a number.

The fix simply catches this situation, puts up the error message you saw, and keeps going rather than crashing. Now that I have confirmed what the failure mode is, now I can focus on capturing the string that causes the problem and then fix it. For now though, the program should be usable other than once in a while missing the status of the blower.

quote:

Originally posted by DavidH:

quote:

Hide Post
Boy, this is going to be tough to debug Smiler.

Hi Amir,

Can you give me a feel for what this error means? Is there something that I can check from a system standpoint - hdw./connections, .Net version, network drivers, etc.?

I'd like to be able to help out if I can.

I'll test 6.4 tonight and let you know.

Per my other post, this is a change in the way the stoker now reports fan status. It must be putting some extra text in there that didn't used to be there. So the fix could simply be to go back a few revisions before twitter where this was not an issue. But I will try to debug it with another revision to try and see if I can patch it up.

The difficulty here is that we have no version control. I need to make stokerlog work with revisions of stoker firwmare without knowing which one is which. I did that once before when the fan status was changed (from 1 to 10 to 0 or 1). This one may or may not be easy to fix.

OK, now that the food is out I'm playing with the timer a little more. I have learned that the "Timed Cooking" window must remain open, if it is closed it throws everything out of whack.

Hi Joe. Your clue told me what was wrong with TimedCook. I just rewrote the logic. So please standby for the new version. I also put some diagnostics in there to help me figure out why the fan string is wrong.....

Amir,

Have you thought about packing Stokerlog as a Click-once project so clients auto-update? I'm new here so not sure if this rapid development is typical, but thought it might make your life a bit easier...

thanks for the suggestion Brian. I might do that.

The pace though is not like what you see here. I usually work for a couple of weeks intensively to get us to the next level of functionality. Then, leave well enough alone and we all go and cook with the thing rather than playing with it . A few months go by and I get the time to attack much needed features and the cycle starts again.

Running a test of just the stoker 2.6.0.221 / probes and stoker log 6.4 etc without cooking. So far working great ( 4 1/2hours).

Plan to cook something on sunday.

Amir... Which version of stoker firmware do you like the best?

249 also seemed to work fine with 6.3.

In general 6.3 and later seems to be pretty stable (well done).

Anything specific you would like me to try tomorrow other than just let it run?

OK, here is a new version with important changes:

1. TimedCook was really busted . As noted, if you didn't leave the window up a lot of bad things happened from exceptions to wrong things. All should be well.

Note that there is a new button "done" where you commit the changes. That way, you can play around with the numbers without impacting the cook. You can also hit the Update button to save the changes but leave the dialog up so that you can see all the timers running.

2. Twitter timer. This was broken and would not take effect. It is fixed now.

3. I save the corrupt fan string now in the log file.

I appreciate everyone banging on this new release as much as you can: http://www.amir-views.com/downloads/SetupV65.msi

I am especially interested to find the fan string problem but also testing Twitter and TimedCook to make sure they are solid is also good.

Let's see if we can officially release this baby this weekend! Thanks for everyone's help.

Phil, thanks for your help.

I have not yet tested the older releases. I know my stoker from last year was three times faster in HTTP/browser interface until I upgraded to 249! I have a note into the developer to look into it but he is on vacation right now.

When I get time, I will go back and find the one we should be running.

quote:

Originally posted by joe thomas:
Today's attempt. I'm playing with the camera too...

In that middle photo, are you making "Wood Stock"?

Don't know why I threw that in...

Was going to use some hickory for smoke. The piece is now laying on the back porch.

Hi Amir,

I will move my stoker back to 249 and run the new 6.5 version this weekend. Today just in the house tomorrow a 3 hour chicken :-)

I love the work you do on stoker log.

Phil