Stokerlog Version 6

Brian (Lonewolf) · Oct 26, 2009

Hey Amir--

Early report but have 6.3 running for a couple of hours and so far, no issues... I'll keep you posted!

Amir · Oct 26, 2009

Great. Pls let me know if you see any text in red in the status line.

I have fixed a few other minor things outside of the exception bug. Will post them later when I have more mileage on it....

phil g · Oct 26, 2009

I tried running 6.1 this weekend while smoking a brisket. I ran into several errors... Including my wireless bridge dying :-(

I ended up getting a new bridge and rand with 6.2 for several hours with no issues.

I just loaded 249 of the stoker firmware and put 6.3 on my XP based laptop. I will run it for several days and see what happens and let you know!

Thanks for a great addition to the stoker!

Amir · Oct 26, 2009

Thanks Phil.

FYI, I find 249 revision of stoker firmware disappointing. It is super slow. I had to increase timeouts by a factor of 3 to keep things working. It takes almost 45 seconds to update changes to stoker!

Once we are past the current set of issues, I like to find a more performant version of the firmware to standardize on. With Twitter functionality in stokerlog now, I think we can go back a few revisions to find that. I will also contact the developer to see what his opinion is.

Steve Carson · Oct 27, 2009

Amir,
I'm 13.5 hours into a two butt cook using your 6.3 test release. I am using stoker firmware 2.1.321. I am using the email log feature. I am not using the twitter feature.

Issues:

none, zero, zilch, nada

Good work Amir!

phil g · Oct 27, 2009

The Twitter function in the stoker seemed fragile to me. I was not able to get it to work. Kaytat makde 249 with the debug as a result of my questions trying to get it to work. But he had to stop working on it because of other commitments.

I am happy to move backwards to a previous version and test with that...

Perhaps 221 or 226? That was before all of the JSON aupport... Or do you think something further back?

--

FYI... Running for 8 1/2 hours with 249 and 6.3. No problems!

phil

Brian (Lonewolf) · Oct 27, 2009

Interesting -- so would the latest released (not beta) firmware be the best? Maybe I should move back to it.

Just a follow up to my last post but all seemed to go well for another few hours. The real test will be a large cook later this week.

Amir -- I didn't see any red in the status-- guessing no errors occuring, or if they are they're handled which is great -- I figure I might walk away from the PC for awhile and seeing the exception brings everything to halt so it's great it can keep chugging along.

Amir · Oct 27, 2009

Thanks guys. I am glad the new logic is working well!

I just updated 6.3 with the latest fixes as I mentioned above. Be sure to look at the Twitter interval before turning on the feature as it is now in minutes as suggested, rather than seconds.

http://www.amir-views.com/downloads/SetupV63.msi

phil g · Oct 27, 2009

Starting another test with stoker 221 and v6.3 of stokerlog - report tonight on how that works.

D Casten · Oct 27, 2009

dang phil, do you smoke every night?

phil g · Oct 27, 2009

Wish I could smoke every night

Just have the stoker running in the house, with no fan attached...

Phil

DavidH · Oct 27, 2009

Hi all,

After upgrading to latest firmware (.249) and rel. 6.3, I started testing inside on the dining room table with "dual cookers" (probes and fans). About 15 minutes in I got an exception failure. I backed off to 2.1.321 and rel. 6.3 - failure changed to hung stoker log (no response).

As before, no options were set in stoker log other than temp and alarms. Not sure what to try next. Suggestions?

phil g · Oct 27, 2009

Been running V6.3 with version 2.6.221 since this morning. 16 hours and looking good!

Amir · Oct 27, 2009

Originally posted by DavidH:
Hi all,

After upgrading to latest firmware (.249) and rel. 6.3, I started testing inside on the dining room table with "dual cookers" (probes and fans). About 15 minutes in I got an exception failure. I backed off to 2.1.321 and rel. 6.3 - failure changed to hung stoker log (no response).

As before, no options were set in stoker log other than temp and alarms. Not sure what to try next. Suggestions?

Do you remember the exception? Can you try to duplicate and post the message that comes up there?

Amir · Oct 27, 2009

One more thing. Can you post the last few lines from telnet text file? Pls see the instructions a few posts earlier.

DavidH · Oct 28, 2009

Hi Amir,

I'll try to recreate and post the info. tonight. Thanks for the help AND the great s/w.

MarkMi · Oct 28, 2009

Amir,
I upgraded to 6.3 of stokerlog. I succesfully ran it with probes only and the .249 firmware without any exceptions for over 20 hours.
I did have a problem with the Twitter setting. It appears that not matter what I put in the "Update Interval", it updates twitter every minute. Although the field is labeled "(seconds)", your post indicated that the minutes should be entered. I've used 10,3,100 and it always updates on the minute.
Nice job getting these exceptions ironed out and for the great new features!
Thanks

Mark

Amir · Oct 28, 2009

Thanks Mark. I am not home so can't check it.

One thing that comes to mind is that I act on that number when you start logging. If you change it after that, it won't take effect. Do you recall when you changed it?

DavidH · Oct 28, 2009

Amir,

See below for exception error details. It took about 20 minutes to occur. Sorry for the data dump, but last few lines of telnet input are included. I saved the entire file if needed.

Firmware is xx.249 & Stoker log is 6.3

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
----------------------------------------
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.

Telnet input data:

4200001267B71030: 1 31.9 89.4 -20.6 0.5 1.3 0.8 20.1 68.3 PID: NORM tgt:24.4 error:21.4 drive:0.8 istate:36.8 on:9 off:1 blwr

n

4200001267B71030: 1 31.9 89.4 -20.6 0.5 1.3 0.8 20.1 68.3 PID: NORM tgt:24.4 error:21.4 drive:0.8 istate:36.8 on:9 off:1 blwr

n

760000127E6AD630: 3 18.6 65.5 -5.6 0.1 0.7 0.6 18.1 64.6 PID: NORM tgt:22.2 error:20.5 drive:0.8 istate:31.7 on:8 off:2 blwr

ff

C00000127E845930: 3 18.8 65.8 -9.4 0.2 0.7 0.5 15.9 60.6

8500001267933930: 1 31.8 89.1 -23.8 0.6 1.3 0.7 18.1 64.6

4200001267B71030: 1 31.9 89.4 -20.6 0.5 1.3 0.8 20.1 68.3 PID: NORM tgt:24.4 error:21.4 drive:0.8 istate:37 on:9 off:1 blwr