bvwelch

I'll try to keep notes here as I work thru the latest Openwrt. It's been a while since I've built OpenWrt from source.Here is a link to the main development web siteAnd here is a link to the current platforms, and also provides notes of any known problems or limitations. Here's the link to the instructions for using SVNWe will be trying out the 'Backfire' version. As of today, svn retrieved revision 22918 of the 'Backfire 10.3' release.The info on building from source is found on this page. scroll down to the developer's section.Today I will just start the process of building the cross-compilers, etc -- tons of downloading and compiling and waiting and waiting -- my host PC is an old system running Ubuntu -- very slow. I'll get it started and then check back later from time to time to see how it is progressing.Step #1: cd to the 'backfire' directory and type: 'make menuconfig' and answer the questions according to which router you are wanting to build. The script will also check and see if you are missing any required tools. oops, I am missing ncurses. I'll use apt-get to manually get that installed on my Ubuntu system. Well, I guess they want the development version so it can find ncurses.h ? Yep, that was it. In the menu, I just changed the first entry to ar71xx, then exited without making any other changes (later I may want to fine-tune but for now, just try the defaults).Step #2: 'make' # Now it is time for a walk. I started the make at about 2:30pm today. OK, the make finished sometime between 5:30 and 5:50pm. Meanwhile, I was reading this link about my router and noticed it recommended that I choose more stuff in the 'make menuconfig' step above, so I will re-do that now. Well, I did some reading on the Forum and I'm gonna run menuconfig and be sure to set up the wired LAN. Wow that was a lot of tedious menu navigation. Hope I got it right, otherwise I'll be doing tftp to recover. OK, restart the make now at 7:45pm. I checked again at 9pm - finished. I'll stop for tonite. I saved my 'dot config' from the 'make menuconfig' so I can refer to it later should I want to tweak my build procedure in the future.By the way, in case I forget to mention it, the convention for OpenWRT is that if all else fails, you should be able to reboot/reset a router such that for a few seconds, the router will listen on 192.168.1.1 for a new firmware image via tftp. This is true even if you normally want the router's LAN ports to some other range of IP addresses. Example, you have your wired LAN set for 10.0.0.0 and for whatever reason you messed up and need to reflash firmware. Use 192.168.1.1 for tftp. This may require temporarily setting up a PC to a static address like 192.168.1.100.Step #3: now it is time for testing. Depending on your setup, you may want to copy the new firmware to a laptop or other portable device. Then you'll plug into one of the router's LAN ports and use the 'firmware upgrade' feature available from the web interface in the original router's firmware -- OpenWrt's firmware file format is compatible. I chose the jff2 image (but later switched to squashfs) and followed the steps in this guide. The guide warned that the original firmware 'upgrade' might not like the syntax/format of the actual Openwrt filename. Weird but true, so I renamed it to have the same filename format as suggested in the guide.For the original router firmware, the LAN interface was 192.68.1.1, but after the firmware was loaded and the router automatically rebooted, the LAN interface switched to the value I specified during the 'make menuconfig' (192.168.4.1 in my case). There was no web interface built-in to my new firmware, so I just telnet 192.68.4.1 and then set a new root passwd. By convention, OpenWrt will disable telnet and enable SSH from now on since there is a password.I followed the guide above and started the wifi interface. My laptop is old but had no trouble connecting with WPA2.Next step: adding other packages and tweaking the router here and there. I may just be lazy and grab pre-compiled packages, but I could build them from source should I want to or need to.

T1 in shop

Here's an screenshot of the real-time display.[caption id="attachment_60" align="alignnone" width="300" caption="Yesterday's roast"]Yesterday's roast[/caption]

Here are some photos of assembling the TC-4 Arduino shield: http://bvwelch.com/?page_id=40

Jim Gallt has created a very useful variation of the 4-channel TC Arduino shield concept.  I like it, and recommend that you check it out here: http://code.google.com/p/tc4-shield/

This is a first cut at an Arduino shield for coffee home-roasters. It has four channels and also a prototyping area. Check it out here:

The most recent information - hardware and software, may be found hereI'm using Github to store the source code for the project. Check it out here.

The data logger worked well, after repairing a broken thermocouple.Here's a screenshot of the 'Processing' program that provides the real-time display.Here's the CSV data file.Here's a photo of the setup. Note this is a prototype board - we'll make a PCB for this project soon.