Stokerlog only works in HTTP mode


 
R

R Addy

New member
Hi All,

I tried this topic in the version 5 thread, but no luck.

Stokerlog seems to be picking up a constant value for the temperature. I can telnet to it and log probe data which shows accurate temperature changes. The data which is being collected by stokerlog appears to be ambient temp. which is in the data stream as well. Stokerlog is picking up the fan data fine.

What I know:

Stokerlog is creating a connection with the unit via telnet.

The Stokerlog telnet input file shows the correct temp data.

Stokerlog in HTTP mode logs the correct temps.

I tried it on 4 different computers all with the same result.

The temp data that stokerlog is collecting is in the 10th column in the telnet data. The correct data is in the 16th column in the data. This using space delimiting in excel.

What I don't know.

Can I change the program to parse the data in the 16th column?

Can the Stoker be changed to put the correct data in the correct order?


I can still use the program in HTTP mode, but if I use alarms, I am going to chance waking the neighbors.

Anybody else have a similar problem?

Thanks,

Roger
 
That's really strange. Did you buy your stoker recently? I wonder if the firmware is changed somehow.

Anyway, current preview version of the program logs all the input from the stoker. My laptop with the source code has crashed so can't look up the file name/location
icon_frown.gif
. But search for a file which keeps growing as you run the program. Once you find it, post a section here.

There is also a regular log file. Would be good to have a sample of that too.

And to answer your question, no, there is no way for you to change the syntax. It took a long time to get all that right and it is hardwired logic.

My guess other than firmware change is that there is something unique in your configuration that is causing the data to show up somewhere else. So please post a screen snapshot too so that we can see what probes there are, etc.

Finally, no, no one else is having that problem that I have ever heard.
 
Thanks for replying Amir,

Here is the telnet input file capture. This capture is one without the fan control as it is too long of a string to put in. I'm holding the probe between my fingers to heat it up. You can see the temp increasing in the telnet data, but not the log data which matches different data in the telnet string.

1300001231379830: p:-116 sts:-29 sfr:-65 dp:0 dsts:32 dofs:0 3 29.1 84.4 1.9 0.1 1.2 1.2 33.3 91.9

1300001231379830: p:-116 sts:-29 sfr:-65 dp:0 dsts:32 dofs:0 3 29.3 84.7 2.5 0.1 1.2 1.3 33.8 92.8

1300001231379830: p:-116 sts:-29 sfr:-65 dp:0 dsts:32 dofs:0 3 29.1 84.4 2.5 0.1 1.2 1.2 33.7 92.6

1300001231379830: p:-116 sts:-29 sfr:-65 dp:0 dsts:32 dofs:0 3 29.1 84.4 2.5 0.1 1.2 1.2 33.7 92.6

1300001231379830: p:-116 sts:-29 sfr:-65 dp:0 dsts:32 dofs:0 3 29.1 84.4 3.1 0.1 1.2 1.3 34 93.3

1300001231379830: p:-116 sts:-29 sfr:-65 dp:0 dsts:32 dofs:0 3 29.1 84.4 3.1 0.1 1.2 1.3 34 93.3

1300001231379830: p:-116 sts:-29 sfr:-65 dp:0 dsts:32 dofs:0 3 29.3 84.7 3.8 0.1 1.2 1.3 34.5 94.2

1300001231379830: p:-116 sts:-29 sfr:-65 dp:0 dsts:32 dofs:0 3 29.3 84.7 3.1 0.1 1.2 1.3 34.2 93.5

1300001231379830: p:-116 sts:-29 sfr:-65 dp:0 dsts:32 dofs:0 3 29.1 84.4 3.1 0.1 1.2 1.3 34 93.3

1300001231379830: p:-116 sts:-29 sfr:-65 dp:0 dsts:32 dofs:0 3 29.3 84.7 3.8 0.1 1.2 1.3 34.5 94.2

1300001231379830: p:-116 sts:-29 sfr:-65 dp:0 dsts:32 dofs:0 3 29.1 84.4 3.1 0.1 1.2 1.3 34 93.3

1300001231379830: p:-116 sts:-29 sfr:-65 dp:0 dsts:32 dofs:0 3 29.3 84.7 3.8 0.1 1.2 1.3 34.5 94.2

1300001231379830: p:-116 sts:-29 sfr:-65 dp:0 dsts:32 dofs:0 3 29.3 84.7 3.8 0.1 1.2 1.3 34.5 94.2

1300001231379830: p:-116 sts:-29 sfr:-65 dp:0 dsts:32 dofs:0 3 29.3 84.7 3.8 0.1 1.2 1.3 34.5 94.2

1300001231379830: p:-116 sts:-29 sfr:-65 dp:0 dsts:32 dofs:0 3 29.1 84.4 3.8 0.1 1.2 1.3 34.4 93.9

1300001231379830: p:-116 sts:-29 sfr:-65 dp:0 dsts:32 dofs:0 3 29.3 84.7 3.8 0.1 1.2 1.3 34.5 94.2

1300001231379830: p:-116 sts:-29 sfr:-65 dp:0 dsts:32 dofs:0 3 29.1 84.4 3.8 0.1 1.2 1.3 34.4 93.9

Here is the stokerlog.txt file

Temps, 8/10/2008 12:29:44 PM,N/A, N/A,83.3
Temps, 8/10/2008 12:30:44 PM,N/A, N/A,83.3
Temps, 8/10/2008 12:31:45 PM,N/A, N/A,83.5
Temps, 8/10/2008 12:32:45 PM,N/A, N/A,83.5
Temps, 8/10/2008 12:33:46 PM,N/A, N/A,83.8
Temps, 8/10/2008 12:34:46 PM,N/A, N/A,83.8
Temps, 8/10/2008 12:35:47 PM,N/A, N/A,83.8
Temps, 8/10/2008 12:36:47 PM,N/A, N/A,84
Temps, 8/10/2008 12:37:48 PM,N/A, N/A,84
Temps, 8/10/2008 12:38:48 PM,N/A, N/A,84
Temps, 8/10/2008 12:39:49 PM,N/A, N/A,84.2
Temps, 8/10/2008 12:40:49 PM,N/A, N/A,84.2
Temps, 8/10/2008 12:41:50 PM,N/A, N/A,84.2
Temps, 8/10/2008 12:42:50 PM,N/A, N/A,84.4
Temps, 8/10/2008 12:43:51 PM,N/A, N/A,84.4
Temps, 8/10/2008 12:44:51 PM,N/A, N/A,84.4
Temps, 8/10/2008 12:45:51 PM,N/A, N/A,84.7
Temps, 8/10/2008 12:46:52 PM,N/A, N/A,84.7

I just got the stoker last week. It has the latest version of the firmware.

Thanks for the help.

Roger
 
Boy, it does seem like they changed the revision/formatting. Can you please look up your firmware revision?

I can fix this but I have to figure out how to tell the two versions reliably apart.
 
The firmware revision is: 2.1.287

I tried it with a crossover cable, bypassing the router with the same result.

Thanks again for your help.

Roger
 
Thanks.

I am not in front of my stoker but looks that that is a new revision. Looking on Rock's web site, seems we are all running on v.2.0.259.

I have email into them to see what all has changed. Stay tuned...
 
That newer version is listed as an alpha version on the Kaytat software site.

http://www.kaytat.com/


Version 2.1.287 (June 20, 2007)

* Small improvements in speed
* Add more output on the telnet interface


Maybe that's the official supported firmware version now?
 
OK, here is the latest. It seems that the wrong version got released with some stokers. The right version maintains backward compatibility. So the official version to run is 2.1.300 and should be posted soon. Everyone should be running that I am told.
 
Kelley, thanks for posting the software download address. I just looked there and indeed, version 2.1.300 is available there.

Roger, do you mind giving that a try and report back? I am travelling soon for a few days and won't be able to do so.
 
Looks like the updated firmware did the trick. I only tested it on my workbench, but everything appears to be working.

Thanks Amir. I'm looking forward to hooking it up to my Kamado.

Now on to the wireless setup.

Roger
 
Excellet.

BTW Roger, I have rarely seen anyone troubleshoot something as complicated as this, as well as you did! That made the resolution so much easier. So thanks for that and hope you enjoy your new setup.
 
Thanks Amir,

You've written a very useful and elegant program. The availability of your program was one of the deciding factors in purchasing the stoker.

I now have it hooked up to a linksys wrt54gl router running DD-WRT in client bridge mode.

Now, I must find something to smoke.

Roger
 
" Now, I must find something to smoke."

Well, if it's any help, there is smoke coming out of both my ears
icon_smile.gif
Reading this tech stuff makes my gray matter hurt.
icon_smile.gif


But it would be fun to have something like this work without all the tech headaches.
 
Worked for me without "all the tech headaches"...

Just plugged it into power, then into my wireless router, then turned it on. Worked as advertised.
 
You must log in or register to reply here.

 

Back
Top