• Please visit and share your knowledge at our sister communities:
  • If you have not, please join our official Homebrewing Facebook Group!

    Homebrewing Facebook Group

HOWTO - Make a BrewPi Fermentation Controller For Cheap

Homebrew Talk

Help Support Homebrew Talk:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
Status
Not open for further replies.
[...]Google doesn't really show that anyone has done this, so you might be on your own.

There are 4700+ posts on this thread alone, and most of those are either folks needing assistances or folks providing assistance.

That might advise folks not to put themselves on an island...

Cheers! ;)
 
The BrewPi system has three distinct parts. There is the controller code, which runs on an Arduino (or now Spark), there is the logger/interface, which is a Python script that talks to the controller over a serial link, and there is the web app, which runs under the web server, and talks to the logger via a socket.

It is possible to run the logger and the web app on any Linux box (based on what I have gleaned from the web) so it ought to be possible to run it on a Beaglebone (since it's just another Linux box).

Google doesn't really show that anyone has done this, so you might be on your own.

Yeah, I've searched for a couple days now without finding anything. Bummer. I'll have to work at it and see where I get before giving up and getting another pi.
 
Yeah, I've searched for a couple days now without finding anything. Bummer. I'll have to work at it and see where I get before giving up and getting another pi.
Well, on the one hand, you can't have too many Pis. On the other, how hard can it be...
 
If your installation didn't actually use more than half of that 16GB SD card, and you have a USB card reader that you can plug into your RPi, then there is a way to clone your 16GB card to the 8GB card.

Check out this page http://sysmatt.blogspot.com/2014/08/backup-restore-customize-and-clone-your.html

It takes awhile to do, but the procedure totally works - I've used it often.
You'll definitely want to save that link.

Note that before embarking on the above, one should stop any BrewPi scripts through the gui, stop the flowmon service for RaspberryPints ('$sudo /etc/init.d/flowmon stop') if installed, and generally stop any "live" applications (like web cams that record on movement, etc) to avoid issues with file locking.

Cheers!

You rock. Thanks. Now to borrow an sd card reader from someone...
 
Having a problem getting the script to run
I've done many of the updates suggested to no avail

When I run if config command in the text it says

WLAN 100567 kb transmitted 0 errors 60432 dropped 0 skipped

Is this telling me that when I downloaded the program that it missed a whole bunch of info?

If so that would explain a lot
 
Note that before embarking on the above, one should stop any BrewPi scripts through the gui, stop the flowmon service for RaspberryPints ('$sudo /etc/init.d/flowmon stop') if installed, and generally stop any "live" applications (like web cams that record on movement, etc) to avoid issues with file locking.

Cheers!

As I'm sitting here for the last hour watching my files get copied, it dawned on me...is the motion detector one of the services I should have stopped? Palm hits forehead.

How do I stop it, besides commenting it out in the autostart file and rebooting?

Could this be why I got "kernel in use" errors when running the sd card partitioning scripts?
 
You're fine, the motion detector doesn't write any files, it just pokes at functions, so file locking is a non-issue.

I've appended one of my stream-of-consciousness tomes covering the cloning process.
There's all kinds of messages included so you can see what to expect along the way (including those kernel messages you mentioned - they're normal).
It's kinda huge so apologies to others.

[edit] I should note how I came about the linked site that drove the procedure below: let's say your Pi fleet was built using 8GB uSD cards, and you have an extra card. SD cards have varying real capacities as flash chips are hardly ever perfect and the factory initialization accounts for defects by reducing the usable size. So it's pretty darned rare to have even two SD cards with exactly the same capacity, never mind a fleet of them.

One day I decided to use win32diskimager to create a cloned SD card from an image, but the program flat out refused because the target card was 64KB lower capacity than the source card. And in fact when I checked all of my SD cards, the spare one had the lowest real capacity, so I couldn't clone it from an image. Hence having to do a live-image clone was the only way to find joy, and fortunately, Matthew E Hoskins had a nicely documented procedure out there for the using...


Code:
HOW TO CLONE SD CARD

Created backup image to obelisk e:

Create new SD card from live image:

pi$ sudo su
root# apt-get install dosfstools
root# apt-get install rsync

Stop Motion Service and disconnect camera

$ motionstop

Plugged in USB2 SOHOUSB reader

root# dmesg

[10346.000962] usb 1-1.2.2: new high-speed USB device number 10 using dwc_otg
[10346.105028] usb 1-1.2.2: New USB device found, idVendor=05e3, idProduct=0716
[10346.105065] usb 1-1.2.2: New USB device strings: Mfr=0, Product=1, SerialNumber=2
[10346.105081] usb 1-1.2.2: Product: USB Storage
[10346.105096] usb 1-1.2.2: SerialNumber: 000000009740
[10346.112454] usb-storage 1-1.2.2:1.0: USB Mass Storage device detected
[10346.116135] scsi0 : usb-storage 1-1.2.2:1.0
[10347.112586] scsi 0:0:0:0: Direct-Access     Generic  STORAGE DEVICE-6 9740 PQ: 0 ANSI: 0
[10347.120131] sd 0:0:0:0: [sda] Attached SCSI removable disk
[10347.123249] scsi 0:0:0:1: Direct-Access     Generic  STORAGE DEVICE-6 9740 PQ: 0 ANSI: 0
[10347.126441] sd 0:0:0:1: [sdb] Attached SCSI removable disk
[10347.129775] scsi 0:0:0:2: Direct-Access     Generic  STORAGE DEVICE-6 9740 PQ: 0 ANSI: 0
[10347.138187] sd 0:0:0:2: [sdc] Attached SCSI removable disk
[10347.139607] scsi 0:0:0:3: Direct-Access     Generic  STORAGE DEVICE-6 9740 PQ: 0 ANSI: 0
[10347.152948] sd 0:0:0:3: [sdd] Attached SCSI removable disk
[10347.153733] scsi 0:0:0:4: Direct-Access     Generic  STORAGE DEVICE-6 9740 PQ: 0 ANSI: 0
[10347.162079] sd 0:0:0:4: [sde] Attached SCSI removable disk
[10347.455181] sd 0:0:0:0: Attached scsi generic sg0 type 0
[10347.456126] sd 0:0:0:1: Attached scsi generic sg1 type 0
[10347.457169] sd 0:0:0:2: Attached scsi generic sg2 type 0
[10347.458213] sd 0:0:0:3: Attached scsi generic sg3 type 0
[10347.459125] sd 0:0:0:4: Attached scsi generic sg4 type 0
[10355.503741] bcm2835_audio_set_ctls:558  Controls set for stream 0
[10364.234904] sd 0:0:0:2: [sdc] 30703616 512-byte logical blocks: (15.7 GB/14.6 GiB)
[10364.237255] sd 0:0:0:2: [sdc] No Caching mode page found
[10364.237292] sd 0:0:0:2: [sdc] Assuming drive cache: write through
[10364.251476] sd 0:0:0:2: [sdc] No Caching mode page found
[10364.251516] sd 0:0:0:2: [sdc] Assuming drive cache: write through
[10364.253192]  sdc: sdc1
[10365.962691] bcm2835_audio_set_ctls:558  Controls set for stream 0
root@rpints:/home/pi#


So new SD card is SDC: SDC1

First, we need to create the two partitions to hold our /boot and / (slash) filesystems. 
We do this with the GNU parted utility.

root@rpints:/home/pi# parted /dev/sdc

GNU Parted 2.3
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mklabel msdos

Warning: Partition(s) on /dev/sdc are being used.
Ignore/Cancel? I
Warning: The existing disk label on /dev/sdc will be destroyed and all data on this disk will be lost. Do you want to continue?
Yes/No?
Y
Error: Partition(s) 1 on /dev/sdc have been written, but we have been unable to inform the kernel of the change, probably because
it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.
Ignore/Cancel? I
(parted)  quit

Restarted system

root@rpints:/home/pi# parted /dev/sdc
GNU Parted 2.3
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mkpart primary fat16 1MiB 64MB
(parted) mkpart primary ext4 64MB -1s
(parted) print
Model: Generic STORAGE DEVICE-6 (scsi)
Disk /dev/sdc: 15.7GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  64.0MB  62.9MB  primary               lba
 2      64.0MB  15.7GB  15.7GB  primary

(parted) quit
Information: You may need to update /etc/fstab.

Next format the two partitions

root@rpints:/home/pi# mkfs.vfat /dev/sdc1
mkfs.fat 3.0.26 (2014-03-07)

root@rpints:/home/pi# mkfs.ext4 -j /dev/sdc2
mke2fs 1.42.5 (29-Jul-2012)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
956592 inodes, 3822336 blocks
191116 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=3917479936
117 block groups
32768 blocks per group, 32768 fragments per group
8176 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

root@rpints:/home/pi# 

Stop mysql server:

root@rpints:/home/pi# service mysql stop (start, restart)  


Now we need to mount these two partitions somewhere so we can copy data to it. 
Let's make a temporary directory under /tmp/newpi and do all our work under it. 
Below are the commands to mount our SD cards:


root@rpints: /home/pi# mkdir /tmp/newpi
root@rpints: mount /dev/sdc2 /tmp/newpi
root@rpints: mkdir /tmp/newpi/boot 
root@rpints: mount /dev/sdc1 /tmp/newpi/boot
root@rpints: df -h

Filesystem      Size  Used Avail Use% Mounted on
rootfs           13G  3.6G  8.8G  30% /
/dev/root        13G  3.6G  8.8G  30% /
devtmpfs        215M     0  215M   0% /dev
tmpfs            44M  320K   44M   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs            88M     0   88M   0% /run/shm
/dev/mmcblk0p5   60M  9.6M   50M  17% /boot
/dev/mmcblk0p3   27M  397K   25M   2% /media/SETTINGS
/dev/sdc2        15G   37M   14G   1% /tmp/newpi
/dev/sdc1        60M     0   60M   0% /tmp/newpi/boot

root@rpints:/home/pi# 

The output of the "df" command will show us that both slash and boot have been mounted and are the expected sizes. 


Next, we will execute a command to copy our existing raspbian OS installed on our running pi into our mounted SD card. 

Now, a couple notes about live cloning. 
If you are running any services that keep data files open (like mysql, postgresql, apt-get, or other applications) these should be shutdown to insure you get a clean copy. 

We will use the rsync utility for this copy, we will tell it to only copy / (slash) and /boot, further, we will also tell rsync not to cross filesystem boundaries (--one-file-system).

Why do we specify slash (/) and boot separately? If you look above at the df listing you can see lots of other filesystems mounted. 
Some of these are ramdisks and virtual filesystems (/sys, /dev, /tmp, and /proc for instance). 
We do not want to copy these at all. By using the --one-file-system and specifying explicitly slash (/) and /boot, we only capture the OS tree of files. ( Note, the rsync is sensitive to trailing slashes on the source and destination directory names, make sure you run it exactly as below)

root@rpints:/home/pi# rsync -av --one-file-system / /boot /tmp/newpi/

[bazillion files copied to SD card!]


(NOOBs Users: If you are running a SD card created with NOOBs, you will need to manually modify the boot/cmdline.txt and etc/fstab files on your new SD card before you can boot. You must edit and substitute the mmcblk0p* device names for the proper ones. 

In the etcfstab, slash (/) should be /dev/mmcblk0p and /boot should be /dev/mmcblk0p1. 

In the boot/cmdline.txt file, root= part should be root=/dev/mmcblk0p2. 

*** NOTE: NO CHANGES APPEAR TO BE NECESSARY

Once you have done that the OS that you backed up will be the only OS on the new SD card even if your NOOBs SD had multiple flavors of raspberry pi OS installed. My scripts on github discussed in the next section handle all of this automatically, which makes things a bit easier.)
These are just a few examples. 

When your ready to try out your cloned SD card, you should unmount it using the following commands. 
Make sure you close any shells or change your current working directory (cd) off the new devices or you will get an error when you try to unmount.

root# umount /tmp/newpi/boot
root# umount /tmp/newpi

You can now safely pull the SD card out and put it in your destination raspberry pi. 
It should boot and work just like any other SD card.

AND IT WORKS! YAY!
 
Thanks, seeing the error messages help a lot, as well as having the commands related to stopping the 'pints stuff handy in one "tome" as you put it.

Edit - it really does work.. I've got a small army of 2 backups now. Yay me. Now if I fry everything while trying to get BrewPi working, I can always go back to the comfort of my taplist by swapping out to a stable place.
 
Hi I'm trying to set up a Multiple Fermentation Chamber system. When i try the ls /dev/ttyACM* command I get no such file or directory. I've done a lot of searching but cant find the answer to my problems. I have cheap unos from ebay.
 
Hi I'm trying to set up a Multiple Fermentation Chamber system. When i try the ls /dev/ttyACM* command I get no such file or directory. I've done a lot of searching but cant find the answer to my problems. I have cheap unos from ebay.

Could you provide a link to the "Uno" you bought?

Obviously, simply "pinging" the USB root ports for attached devices is pretty basic functionality. Even with a dodgy power scheme (eg: relying on the USB port to power the Uno) the thing should at least cough up an ACK.

Perhaps it'd be worth plugging something known to work into the host USB ports just to make sure they work?

Cheers!
 
Hi I'm trying to set up a Multiple Fermentation Chamber system. When i try the ls /dev/ttyACM* command I get no such file or directory. I've done a lot of searching but cant find the answer to my problems. I have cheap unos from ebay.

try

ls /dev/tty*

mine was ttyUSB0
 
When i try the ls /dev/ttyACM* command I get no such file or directory. I've done a lot of searching but cant find the answer to my problems. I have cheap unos from ebay.

Perhaps it'd be worth plugging something known to work into the host USB ports just to make sure they work?

And try a different USB cable. I could not get my cheap Inland UNO to be seen on a linux laptop (Could see it fine on a Windows 8 machine) until I switched to a better USB cable.
 
I am running into an issue installing on a RP2. I got to the steps following IsaacR454 mentioned earlier.

I get an error when trying to clone.


Cloning into '/home/brewpi'...
/home/brewpi/.git: No space left on device


I am using a 8gb card and all i have installed is raspbian wheezy and supporting brewpi things What do I do with this error?
 
I am running into an issue installing on a RP2. I got to the steps following IsaacR454 mentioned earlier.

I get an error when trying to clone.


Cloning into '/home/brewpi'...
/home/brewpi/.git: No space left on device


I am using a 8gb card and all i have installed is raspbian wheezy and supporting brewpi things What do I do with this error?
There should be plenty of space, of course. After you wrote the Raspbian image onto the card and booted it up did you run raspi-config and select option 1 to expand the filesystem?
http://elinux.org/RPi_raspi-config

If you didn't then that could explain the problem.
 
That was it! ok so i followed the instructions from IsaacR454. I went to my IP to upload the HEX file to audrino UNO. It says script not running. I click the button to start script but nothing happens.

This is the code Im trying to have in my CRON job:

* * * * * brewpi python /home/brewpi/brewpi.py --checkstartuponly --dontrunfile; [ $? != 0 ] && python -u /home/brewpi/brewpi.py 1>/home/brewpi/logs/stdout.txt 2>>/home/brewpi/logs/stderr.txt &

but its owned by root and has this in the file

stderrpath="/home/brewpi/logs/stderr.txt"
stdoutpath="/home/brewpi/logs/stdout.txt"
scriptpath="/home/brewpi"
entries="brewpi wifichecker"
# entry:wifichecker
*/10 * * * * root sudo -u brewpi touch $stdoutpath $stderrpath; $scriptpath/utils/wifiChecker.sh 1>>$stdoutpath 2>>$stderrpath &
# entry:brewpi
* * * * * brewpi python $scriptpath/brewpi.py --checkstartuponly --dontrunfile $scriptpath/brewpi.py 1>/dev/null 2>>$stderrpath; [ $? != 0 ] && python -u $scriptpath/brewpi.py 1>$stdoutpath 2>>$stderrpath &


is this correct? Please help me figure out why my script is not running.

I tried to upload the HEX file (brewpi-arduino-uno-revC-0_2_10.hex) and this is what it is saying " also script is not running"

Traceback (most recent call last):
File "/home/brewpi/brewpi.py", line 21, in
from BrewPiUtil import printStdErr
File "/home/brewpi/BrewPiUtil.py", line 22, in
import autoSerial
File "/home/brewpi/autoSerial.py", line 6, in
from serial.tools import list_ports
ImportError: No module named tools
Traceback (most recent call last):
File "/home/brewpi/brewpi.py", line 21, in
from BrewPiUtil import printStdErr
File "/home/brewpi/BrewPiUtil.py", line 22, in
import autoSerial
File "/home/brewpi/autoSerial.py", line 6, in
from serial.tools import list_ports
ImportError: No module named tools
Traceback (most recent call last):
File "/home/brewpi/brewpi.py", line 21, in
from BrewPiUtil import printStdErr
File "/home/brewpi/BrewPiUtil.py", line 22, in
import autoSerial
File "/home/brewpi/autoSerial.py", line 6, in
from serial.tools import list_ports
ImportError: No module named tools
Traceback (most recent call last):
File "/home/brewpi/brewpi.py", line 21, in
from BrewPiUtil import printStdErr
File "/home/brewpi/BrewPiUtil.py", line 22, in
import autoSerial
File "/home/brewpi/autoSerial.py", line 6, in
from serial.tools import list_ports
ImportError: No module named tools
 
Heres the UNO: http://www.ebay.com/itm/131648832689?_trksid=p2057872.m2749.l2649&ssPageName=STRK:MEBIDX:IT
I bought two and am having same problem with both.

So I tried using a new usb cable. Ive put my wifi dongle keyboard and mouse on usb hub, they all work great. I've directly plugged UNO into rpi. I tried codes $ ls /dev/ttyusb, $ ls /dev/ttyusb*, $ ls /dev/ttyusb0, $ ls /dev/ttyusb1, $ ls /dev/usb1*, $ ls /dev/ttyACM, $ ls /dev/ttyACM*, they all return ls: cannot access /dev/tty(whatever it was): No such file or directory.

When I go to $ ls /dev/ after I plug in UNO there is a ttyusb0 that wasn't there before I pluged it in. There is also a ttyusb1 if I plug both in. I've also plugged the UNO into a 12v wall power as well as the usb connection.I've tried all the codes every time I changed something.

Thanks for all your help.
 
this post should have never been posted....

Stupid forum....

or stupid IPAs over 7% ABV

Ruination you ruined me!
 
Heres the UNO: http://www.ebay.com/itm/131648832689?_trksid=p2057872.m2749.l2649&ssPageName=STRK:MEBIDX:IT
I bought two and am having same problem with both.

So I tried using a new usb cable. Ive put my wifi dongle keyboard and mouse on usb hub, they all work great. I've directly plugged UNO into rpi. I tried codes $ ls /dev/ttyusb, $ ls /dev/ttyusb*, $ ls /dev/ttyusb0, $ ls /dev/ttyusb1, $ ls /dev/usb1*, $ ls /dev/ttyACM, $ ls /dev/ttyACM*, they all return ls: cannot access /dev/tty(whatever it was): No such file or directory.

When I go to $ ls /dev/ after I plug in UNO there is a ttyusb0 that wasn't there before I pluged it in. There is also a ttyusb1 if I plug both in. I've also plugged the UNO into a 12v wall power as well as the usb connection.I've tried all the codes every time I changed something.

Thanks for all your help.

Just use ttyUSB0 (zero) and as the back up ttyUSB1 in the config file

eg

port = /dev/ttyUSB0
altport = /dev/ttyUSB1

in the config.cfg file

try

$ sudo nano /home/brewpi/settings/config.cfg

and make the edits and save the file and exit

then continue with the install
 
I got my script to start by updating some more python exts. when i try to upload the HEX file still i get the no module tools error.

also Im still unsure on which Cron text we should be using with this legacy version.
 
Just use ttyUSB0 (zero) and as the back up ttyUSB1 in the config file



eg



port = /dev/ttyUSB0

altport = /dev/ttyUSB1



in the config.cfg file



try



$ sudo nano /home/brewpi/settings/config.cfg



and make the edits and save the file and exit



then continue with the install


If he intends to use both UNOs then using usb1 as altport will give issues in the future. but yes use the ttyusb0 in config. it seems you are having problems getting the script to start. have you given it enough time to start up and update the browser. and are you using the browser in rasbian or are you using something like safari or internet explorer, because then your browser will not show that the script is running.
 
I can start my script manually with SSH and it shows running. But soon as I close the SSH connection it kills my script. I can't seem to get the CRON job to work properly.
 
For the cron job issue, did you execute the fix_permissions script at any point since you completed the installation?

Also, which version of Raspbian are you using? Wheezy, or Jessie? (hopefully the former)

Cheers!
 
I did use the fix_permissions script when instructed. I am using Raspbian Wheezy. I just tried fixing permissions and I went with this in my cron job.

stderrpath="/home/brewpi/logs/stderr.txt"
stdoutpath="/home/brewpi/logs/stdout.txt"
scriptpath="/home/brewpi"
entries="brewpi wifichecker"
# entry:wifichecker
*/10 * * * * root sudo -u brewpi touch $stdoutpath $stderrpath; $scriptpath/utils/wifiChecker.sh 1>>$stdoutpath 2>>$stderrpath &
# entry:brewpi
* * * * * brewpi python $scriptpath/brewpi.py --checkstartuponly --dontrunfile $scriptpath/brewpi.py 1>/dev/null 2>>$stderrpath; [ $? != 0 ] && python -u $scriptpath/brewpi.py 1>$stdoutpath 2>>$stderrpath &



i restarted and it seemed to start up.

now trying to figure out my issue why the hex error.
 
Great, at least you're not working with the handicap that has been Jessie around here ;)

fwiw, here's an example cron from one of my systems.
I've used both entries without apparent issue - the first one is actually from the version 0.3 (?) BrewPi from roughly a year ago, the second is what I believe is being provided by the current version.

Code:
PYTHON=/usr/bin/python
stderrpath="/home/brewpi/brewpi4w/logs/stderr.txt"
stdoutpath="/home/brewpi/brewpi4w/logs/stdout.txt"
SCRIPTPATH=/home/brewpi/brewpi4w
MAILTO=""
* * * * * brewpi $PYTHON $SCRIPTPATH/brewpi.py --config $SCRIPTPATH/settings/config.cfg --checkstartuponly --dontrunfile; [ $? != 0 ] && $PYTHON -u $SCRIPTPATH/brewpi.py --config $SCRIPTPATH/settings/config.cfg 1>$SCRIPTPATH/logs/stdout.txt 2>>$SCRIPTPATH/logs/stderr.txt &
#
#* * * * * brewpi $python $scriptpath/brewpi.py --checkstartuponly --dontrunfile $scriptpath/brewpi.py 1>/dev/null 2>>$stderrpath; [ $? != 0 ] && python -u $scriptpath/brewpi.py 1>$stdoutpath 2>>$stderrpath &

Cheers!
 
Before I embark on my reload of this for the who knows how many times, I'm wondering if I can do all the steps to set this up using the Ethernet connection and then have it run over wifi thereafter?

I can't help but think that I'm not uploading all this code through the wifi reliably and that's were I'm running into difficulties.

Thanks
 
Thank you! do you have any insight into why when i try to load the HEX it gets half way down and then i start to have error: no module tool. I have the uno but i see in the config.cfg file it says board is boardType = leonardo should I change this? or does it get written once the aurdino is uploaded with HEX

Traceback (most recent call last):
File "/home/brewpi/brewpi.py", line 21, in
from BrewPiUtil import printStdErr
File "/home/brewpi/BrewPiUtil.py", line 22, in
import autoSerial
File "/home/brewpi/autoSerial.py", line 6, in
from serial.tools import list_ports
ImportError: No module named tools
Traceback (most recent call last):
File "/home/brewpi/brewpi.py", line 21, in
from BrewPiUtil import printStdErr
File "/home/brewpi/BrewPiUtil.py", line 22, in
import autoSerial
File "/home/brewpi/autoSerial.py", line 6, in
from serial.tools import list_ports
ImportError: No module named tools
Traceback (most recent call last):
File "/home/brewpi/brewpi.py", line 21, in
from BrewPiUtil import printStdErr
File "/home/brewpi/BrewPiUtil.py", line 22, in
import autoSerial
File "/home/brewpi/autoSerial.py", line 6, in
from serial.tools import list_ports
ImportError: No module named tools
Traceback (most recent call last):
File "/home/brewpi/brewpi.py", line 21, in
from BrewPiUtil import printStdErr
File "/home/brewpi/BrewPiUtil.py", line 22, in
import autoSerial
File "/home/brewpi/autoSerial.py", line 6, in
from serial.tools import list_ports
ImportError: No module named tools

should I try Xloader instead? this is the last piece of my puzzle to solve I think.

* edit I just tried using Xloader and it uploaded fine. I made sure to use fix permissions and then I retried to do the hex again with brewpi and this time it worked and found brewpi version and uno board. and now it is idle and has the count down!!!
 
Either your eeprom had problems uploading the hex and a simple ide upload of blink or eeprom clear would fix it, or there is still an issue with the latest Python serial lobraries
 
So I can grasp the diagram regarding connecting everything. But my question is. ..how do I connect this to the fridge to cool the fermenting beer?
 
Status
Not open for further replies.

Latest posts

Back
Top