This is the one I got from you - would be nice to know the possible way of doing things with it
![]()
That board is for hot side control through BrewManiacEx; from @pocketmon;
Not getting any of my sensors up - they do work on the same card with BrewPiLess - strangest thing ever....
They even use the same PIN (D6 for data)
The easiest way is to use the custom script in my brewpi-tools fork, though the script only completes steps 1 & 4 of the below. Alternatively, you can install this manually by doing the following:
Install esptool using PIP (pip install esptool)
Hook up the ESP8266 to your Raspberry Pi with a USB cable
Locate the USB serial bridge device. Generally this will be /dev/ttyUSB0, however if there is any question you can see a mapping of all USB serial devices by looking in /dev/serial/by-id.
Download the repo to your Raspberry Pi using git clone
Change to the bin directory (cd /home/brewpi/esp8266/bin, or the appropriate directory)
If you have already flashed the device I tend to run the following command with wifi-reset.bin first instead of brewpi-esp8266.v0.8.wifi.bin both take about 25-30 seconds to flash with my RPI3
*****Flash the firmware (esptool --port /dev/ttyUSB0 write_flash -fm=dio -fs=32m 0x00000 /home/brewpi/esp8266/bin/brewpi-esp8266.v0.8.wifi.bin)
Note: If you receive an error stating command not found when flashing the firmware, it may be that the esptool is not in your path. Use the following command with explicit paths:*****
python /usr/local/lib/python2.7/dist-packages/esptool.py --port /dev/ttyUSB0 write_flash -fm=dio -fs=32m 0x00000 /home/brewpi/esp8266/bin/brewpi-esp8266.v0.6.wifi.bin
Little help please. How do edit the boot directory?
To utilize this, prior to the initial boot on a newly flashed Raspbian installation, create a wpa_supplicant.conf file in the /boot directory of the SD card with the following contents (adjusting to match your network configuration):
Little help please. How do edit the boot directory?
To utilize this, prior to the initial boot on a newly flashed Raspbian installation, create a wpa_supplicant.conf file in the /boot directory of the SD card with the following contents (adjusting to match your network configuration):
If you are doing it with the Pi,
sudo nano /boot/wpa_supplicant.conf
If you are doing it with Windows the boot partition is accessible when you put the SD card into a card reader. You can use your favourite editor to put a file there.
I'm using win7 with notebook++ as the editor and today's version of 2017-03-02-raspbian-jessie-lite.img
I can pull up the boot file but I'm not sure where to add the extra stuffOk. Can you connect the SD card to the PC? A built-in card reader or USB reader?
If so, when you put the card in it should pop up as a drive letter. That's your boot partition.
I can pull up the boot file but I'm not sure where to add the extra stuff
No LCD Support, no buzzer, with screw connectors, and through-hole components.
Purchase Boards
Eagle Files:
Bill of Materials:
- TBD
1x 2-Pin 5mm Pitch Screw Terminal
1x 4-Pin 5mm Pitch Screw Terminal (Alternatively, 4x 2-pin terminals)
1x 10k 1/4 Watt Axial Resistor
1x RJ-11 Jack
1x WeMos D1 Mini ESP8266 board
LCD Support with DuPont connectors, and surface-mount level converter components.
LCD Support with DuPont connectors, through-hole components, and a SparkFun-based level converter sub-board.
LCD Support with screw connectors, through-hole components, and a SparkFun-based level converter sub-board.
Purchase Boards
Eagle Files:
Bill of Materials:
1x 2-Pin 5mm Pitch Screw Terminal
2x 4-Pin 5mm Pitch Screw Terminal (Alternatively, 4x 2-pin terminals)
1x 2-Pin Pin Header
1x 10k 1/4 Watt Axial Resistor
1x Sparkfun (or compatible) Level Shifter
1x RJ-11 Jack
1x WeMos D1 Mini ESP8266 board
1x LCD 20x4 I2C LCD Screen
I am useless when it comes to building circuit boards, so I have to ask, do the SMD boards come with the SMD components on them or do I have to figure out how to do that myself? Or just stick to the discrete components boards?
That's how I spent my day, striping and soldering wire splices.I need to find a heat source that can shrink down the shrink tubing- the soldering iron made a mess of it.I ended up with a set of three probes, a 25 foot main wire that will plug in to the board and the probes will plug in to a 3 way phone splitter.On a separate note, I have decided that I detest the strip-and-splice method for doing RJ-11 temperature sensors, so I'm going to be making a board shortly with a single RJ-11 jack (to connect to the PCBs linked) and 11 screw terminals ( 3x3 for the room/chamber/beer sensor, 1x2 for door). Completely optional, and a complement (not replacement) for the linked PCBs. Just a personal preference thing.
I gave up on the wifi for now and just plugged in an ethernet cable. Program loaded with out a hitch-Thanks Thorrak and team.I flashed my D1 Mini with the program from the github site posted above nodemcu -flasher. but I cant find it on the network. I'll play around with it later on tonight.On my windows PC I have a "boot" drive shown when I insert the SD card:
View attachment 393645
When I open it, I show a bunch of files, similar to the following:
View attachment 393649
I right click, and choose "Create new text document", and then name a file "ssh". I then do the same, but named "wpa_supplicant.conf".
Once that's done, you can open wpa_supplicant.conf and edit it in Notepad++.
Hmm ... now you need a small 3D printed enclosure for THAT.On a separate note, I have decided that I detest the strip-and-splice method for doing RJ-11 temperature sensors, so I'm going to be making a board shortly with a single RJ-11 jack (to connect to the PCBs linked) and 11 screw terminals ( 3x3 for the room/chamber/beer sensor, 1x2 for door). Completely optional, and a complement (not replacement) for the linked PCBs. Just a personal preference thing.
When pulling up the graph on my mobile devices, I only get a red box.
I tried dygraphs.com/css.html on my mobile devices and they pull up that instance of the graph fine.
I'm no front end developer, but after messing around with things it looks like is going on with the responsive updates to the div "panel panel-red" when you change window size horizontally.
I have no idea how to submit an issue in Github and do this the right way.
On a separate note, I have decided that I detest the strip-and-splice method for doing RJ-11 temperature sensors, so I'm going to be making a board shortly with a single RJ-11 jack (to connect to the PCBs linked) and 11 screw terminals ( 3x3 for the room/chamber/beer sensor, 1x2 for door). Completely optional, and a complement (not replacement) for the linked PCBs. Just a personal preference thing.
Is there any way to enable a sub-site?
I have a tiltpi app - which I would love ro run as sub on the site.
Best reg,
Stig
This one: https://bitbucket.org/lgpaulsen/
PS. I`m not familiar with NginX, if someone could point me in the right directions - thanks in advanced.
It works - and shows nice graphs.
sudo apt-get install php5-fpm
server {
listen 80;
# Where your tiltpi files are located
root /var/www/tiltpi;
index index.php index.html index.htm;
server_name tiltpi.192.168.1.2.nip.io;
location / {
try_files $uri $uri/ /index.html;
}
# pass the PHP scripts to FastCGI
location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_pass unix:/var/run/php5-fpm.sock;
}
}
Forgive me if this has been asked already, but how do I configure multi chamber.
I have a pi zero w and a d1 mini working. Do I need to add another d1 mini or have additional pin headers on the d1 mini beem programmed for an extra chamber heat and cool function.
Many thanks
You need to add additional D1 Minis & sensors - One set per chamber.
Sure, I would create a new nginx server in /etc/nginx/sites-enabled/tiltpi
and use nip.io for a hostname (maps ip to hostname) for example if
the raspberry pi has ip 192.168.1.2 then use "server_name tiltpi.192.168.1.2.nip.io;"
You also need to enable php which your can read about here:
https://www.raspberrypi.org/documentation/remote-access/web-server/nginx.md
Basiclly:
Code:sudo apt-get install php5-fpm
Something like:
Code:server { listen 80; # Where your tiltpi files are located root /var/www/tiltpi; index index.php index.html index.htm; server_name tiltpi.192.168.1.2.nip.io; location / { try_files $uri $uri/ /index.html; } # pass the PHP scripts to FastCGI location ~ \.php$ { include snippets/fastcgi-php.conf; fastcgi_pass unix:/var/run/php5-fpm.sock; } }
- Then access to tiltpi via: http://tiltpi.192.168.1.2.nip.io
- And Fermentrack will be default or for example: http://fermentrack.192.168.1.2.nip.io