HeaterMeter + LinkSys WiFi Router = LinkMeter


 
And talking about displays, I just grounded the 4 other data lines and I believe so far I have no gibberish

Now, i kinda don't understand why my open lid keeps going off

I have the pit set at 79
current pit temp is at 77.5
and it says lid open 1m38s
 
Originally posted by John Bostwick:
Now, i kinda don't understand why my open lid keeps going off
Click to expand...
Check in the menus and see if somehow your lid open offset didn't get messed up somehow. The default is 6% but it is triggering at 1-2%. The other option is that the left button is being detected as being pressed, either because of some sort of physical thing or that the signal from the buttons has some sporadic voltage on it which registers. The left button is the lowest voltage of them all, showing up as low as 0.39V.

@RJ: I haven't considered any other displays other than possibly an RF12 remote version. After I considered that I thought that it should have buttons too to control the grill then dismissed the whole idea entirely as that's what my phone and tablet are for. As far as on the device itself, I've never considered any other options. We've still got about 10k of the 31k of program space left and at least 512 bytes of RAM I think but what really constrains the design is the lack of available pins on the controller. I think we're down to 0 digital and 1 analog now.
 
Originally posted by John Bostwick:
So, if its at 0 then it wil detection will be more often then say 6% oe even 10%
Click to expand...
Yeah if it is 0 then it will kick in all the time. The formula being:

If (set - current) / set >= X% Then Activate

So as soon as it reached temperature it would turn on then probably turn right off again. Is yours set to 0? I hope so because that would mean it is working properly! :-D

Quick examples:
If you're set at 225F, setting lid detect to 5% means it would activate at 213.75F. 10% would let the temperature go lower before it kicked in at 202.5F.
 
one thing I would like to see, would be a start and stop on the graph to indicate the beginning of a cook and a timmer(up or down). Accually either one would be useful, as they both somewhat perfom the same function.

As you already have a degree per hour tab that pops up. Something that could be useful would be able to set a tempeture and have that same pop determine the degrees per hour to that set point. I know it would not be very accurate as the food has stalls and it depends alot on what you are monitoring.
 
Yeah I agree there should be a way to start and stop the logging, because it just runs all the time now. What you can do to clear the graph before you start is hit the special URL
/admin/lm/stashdb?reset=1

Which clears the database. Again this is something I'd like to have in the UI, as well as a way to "trim" a stashed database. Currently if you want to stop the logging, you can either stash the database at the time you want it to stop, or stop the linkmeter service from System -> Startup. You can still see web pages and the last update but the log stops being written.

The running timer is a good idea, I'll put that on my list.

I'd like to expand that degrees per hour thing to do more like you said. I'd like to use the alarm code built into heatermeter as the target for these points instead of being hard-coded like they are now. All the probes have high and low alarms currently, there's just no way to turn them on because I haven't tested them (despite adding them like 6 months ago!). There's also a pin on the AVR used for an audible alarm which hasn't been tested either because I'm not sure how to drive one of those little piezo speakers properly, or what part to buy from the 1,000s they have at Mouser.

But back to the alarms, I'd like to see it that when the alarm triggers you not only can have a sound, but also an email or call a web url to the notification service of your choice (twitter? Maybe I've never used twitter). Also I'd like it to have the ability to change the setpoint when the alarm triggers. Like when the food probe 1 temperature hits 195F, cut the setpoint to 180F or something.

EDIT: Also, I'm out of town again until next Wednesday 7/13 so everyone have a good weekend and keep the good ideas coming! (Also I pushed up a new version that has a slightly nicer stash list, and the ability to get the log as a CSV export!)
 
Thanks again Bryan, I gut this while upgrading:
is this just informational?


* resolve_conffiles: Existing conffile /etc/config/linkmeter is different from the conffile in the new package. The new conffile will be placed at /etc/config/linkmeter-opkg
 
today I recieved a new blower but I think it might be to powerful for the power supply from the router, and also run everything else. I have it running now but earlier I had the lcd turn off and the heatermeter locked up. Even after a restart, the button would not work. only after another restart did everything start working again.

Its a 12V Fan Blower BFB1012HH 1.5amp 15 watts 34.7 max CFM.


im not going to run it at CFM. but, the 6.7 cfm I had on my UDS did not seem to be doing much. So I thought I would try this to see if it would work. Hell, it only cost me 12 buck including shipping. I also added a gasket to the weber lid I use on the UDS to plug up any airleaks. It better work dam it lol. I have a Butt going on tonight
icon_smile.gif
 
I definately think getting the bigger fan has helped. A 6.7cfm is not big enough for a 55 gallon drum. the 34cfm and just closing down the ball valve.
 
It seems that all the files on MediaFire on this thread are now "file not found". Is there a way to restore them?

-- Mache
 
I may be to blame. I was the one that posted the thread to slashdot and maybe the traffic spike exceeded some limit on MediaFire.

-- Mache
 
I'm back! And because I've been in Washington for close to a week, I can not go to bed at 11pm East coast time.

Originally posted by Brian Hilgert:
I get an error: "~/8.09/build_dir/mipsel/rrdtool-1.4.5':configure: error: cannot run test program while cross compiling"

I checked out kamikaze source via :

svn co svn://svn.openwrt.org/openwrt/branches/8.09
svn co svn://svn.openwrt.org/openwrt/packages/ ./8.09/feeds/packages/
Click to expand...
I haven't tried building under Kamikaze, I've been building off trunk. The error you're experiencing is because the patches from [heatermeter]/openwrt/package/rrdtool/patches aren't being applied to the source. I'm not sure if the build process has changed from 8.09 to trunk (I don't believe it has) but for some reason the openwrt builder is downloading the rrdtool source, then trying to build it directly without patching it to fix the broken cross-compile configure stuff. You might try doing a
make package/rrdtool/compile V=99
and see if you see the build say that it is applying the patches, especially the 110-proper_timet_check.patch.

My build system was Ubuntu 11.04 running on a Win x64 Pro host under vmware originally but I have switched to a native Ubuntu 11.04 system since then because I had one available. You may also be the first person to try building LinkMeter from source/install.sh (maybe Ed has? Ed's tried everything!) so there may be a bug in the script. I've only tried it once and on my own system.
 
Originally posted by John Bostwick:
Washington, Lucky you, Im from WA. ...

Last weekend I smoke some pulled pork and I had used the more powerfull blower. It seemed to work fine at night with the cooler tempetures. During the day it got up to around 90 or so and I started to have problems with the heatermeter locking up, the router was fine. The heatermeter would continue to blow but the display would be lock on whatever it was showning at the time. Also when I hit the reset button, it would continue to graph like nothing ever happened.
Click to expand...
Yeah it was awesome in WA! I had only been to the Hoh Rainforest before so this time I went all over, from Cape Flattery to Winthrop. I just wish the bears were slightly more shy.

I don't think I've ever seen the HeaterMeter completely lock up, but it sounds like it was still running, just the LCD had stopped updating. Ahh display problems, will they never cease for you guys?
 
nope this is not a display problem this time
icon_smile.gif


It finally locked up at 414am this morning. When i loggin on my phone on my way home from work it was still reading as if it was 414am.

The graph just stops

Then when i got home I found the fan still blowing anf the screen was locked up I have to hit the reset button and then its fine. I did not have this problem until i put the bigger blower so, its probably overheating the mosfet and then it somehow causes the atmega to lock up.

The blower im using is much bigger then the 6.7cfm

Its a bfb1012hh

So im going to get some artic epoxy and attach a heatsink to the mosfet to see if it does anything.

The video gibberish has been fixed, I will get it once in a while but i know whats causing it and how to make it stable until i get it fixed, by making a new board down the line.
 
The IRL510 is rated up to 5.6A (4.0A at 100C) so theoretically it should be able to handle the load if properly heatsinked. One thing to worry about is the inductive kickback caused by the motor turning off, which happens 500 times a second. The 1N4001 diode there is supposed to block it but they're only good up to 50V/1A you might be seeing higher spikes than that at every turnoff. It could also be some sort of reverse leak coming through the MOSFET to the gate leg. I've seen some designs that have a resistor between gate and ground to prevent something from feeding back to the microcontroller.

I don't know this, these are just the wild conjectures of someone who has browsed the internet looking at schematics for 10 months.
 
I've moved the TODO page that used to be a text file on my server into the GitHub wiki. In other news, I've started the github wiki. I'll probably keep adding things there as needed and just referring to them here rather than the thread being the primary source of documentation from now on.
 
Welcome Back Bryan; I've been anticipating your return like a kid on Xx-mas ;-) Driving the poor wife crazy.
I haven't tried building under Kamikaze, I've been building off trunk. The error you're experiencing is because the patches from [heatermeter]/openwrt/package/rrdtool/patches aren't being applied to the source. I'm not sure if the build process has changed from 8.09 to trunk (I don't believe it has) but for some reason the openwrt builder is downloading the rrdtool source, then trying to build it directly without patching it to fix the broken cross-compile configure stuff. You might try doing a
make package/rrdtool/compile V=99
and see if you see the build say that it is applying the patches, especially the 110-proper_timet_check.patch.

My build system was Ubuntu 11.04 running on a Win x64 Pro host under vmware originally but I have switched to a native Ubuntu 11.04 system since then because I had one available. You may also be the first person to try building LinkMeter from source/install.sh (maybe Ed has? Ed's tried everything!) so there may be a bug in the script. I've only tried it once and on my own system.
Click to expand...

I'll give it another go; I've actually tried several versions of OpenWRT, with similar errors. I don't mean to hijack this thread, so I can start a new one if y'all prefer, but I figured there maybe others struggling as I am.


Here is my build process for backfire:

svn co svn://svn.openwrt.org/openwrt/branches/backfire
cd backfire
./scripts/feeds update -a
./scripts/feeds install -a
cd ~~/CapnBry/Heatermeater/openwrt
./install.sh ~~/firmwarez/backfire
cd ../..~/backfire
make menuconfig
make

At this point I don't even bother with the specifics of my target; I want to get it to build for the default BRCM first.

Funny thing is I have near half a dozen WRT54g routers, but they are all 2 meg flash
icon_mad.gif
 
Yeah, I was reading a webpage and a guy used an artic silver epoxy, thats what I was going to try to use to attach the heatsink.

I posted the question about the blower over at the Arduino forums and got a response that I should using a RFP30N06LE

I'll probably give the heatsink a try first as that will the easiest thing to do.
 
And you're right, the rrdtool isn't building properly. It is an issue with it not finding the lua binding libraries properly. I'll have it fixed later today.
Click to expand...
The problem is that the backfire lua adds a bunch of POSIX functions into the lua core and then rrdtool can't compile because the linker can't find the POSIX functions when linking liblua. I've modified the build patch to link this library during the configure step, which doesn't break the OpenWrt trunk build and fixes the backfire build.

You'll need to git pull and probably need to wipe out the build directory to force the build process to try again (because it doesn't realize the patch will enable a feature)
<pre class="ip-ubbcode-code-pre">
cd ~/CapnBry/heatermeter
git pull
cd ~/firmwarez/backfire
rm -fR build_dir/target-mipsel_uClibc-0.9.30.1/rrdtool-1.4.5
make
</pre>

EDIT: Oops I edited my post instead of replying to it. Dammit! For the record, here's the proper way to build for Backfire:
<pre class="ip-ubbcode-code-pre">
cd ~
mkdir firmwarez
cd firmwarez
svn co svn://svn.openwrt.org/openwrt/branches/backfire
cd ~/CapnBry/heatermeter/openwrt
./install.sh ~/firmwarez/backfire
cd ~/firmwarez/backfire
make menuconfig (exit and save)
make
</pre>
 
You must log in or register to reply here.

 

Back
Top