grillsrv icon indicating copy to clipboard operation
grillsrv copied to clipboard

Significance of the various HighTemp

Open mckaycr opened this issue 4 years ago • 2 comments

Great work on this. Can you explain the significance of the HighTemps you have listed when you read the buffer? You mentioned in the comments something about more bytes needed if the temp is high? Is there a specific threshold that would invoke the need for this extra data point?

mckaycr avatar Jan 25 '21 15:01 mckaycr

hey @mckaycr, unfortunately I dont have the Green Mountain anymore to verify (but this was all working for me as of a month ago). I dont believe the set high temp is needed based on the logic here https://github.com/FeatherKing/grillsrv/blob/a2149be6fa70bd3d92ae9ecfbf4d99c07027cd13/grill.go#L107

I do remember that the temperature bytes were split a few bits like 0F-##F and a few bits on the high side ##F-XXF. I dont recall what that was unfortunately. I can say that using the code as it exists at this moment I have captured temperatures as high as 384F. Im trying to remember if the code around 107 is shoving enough necessary bits that the flag you are seeing is not needed.

FeatherKing avatar Jan 28 '21 03:01 FeatherKing

Thanks, I actually figured it out lastnight while grilling stakess. you need the temp and the high temp in order to display the actual temp. Set my grill to 425 but my test scripts were only registering 169. But when I add the high temp value plus some clever math, I was getting the full 425 temp I was expecting to see.

This for me will be an easy fix for the grill temp and the first probe, but none of the code I poked through showed the bits for the second probe. I had to do some trial and error to find the temp set for that one. I'll now need to hunt down the High temp set as well.

On a separate note, why would you ever not have a Green Mountain Grill, I can't get enough of mine.

mckaycr avatar Jan 28 '21 14:01 mckaycr