Native ESP8266 BrewPi Firmware - WiFi BrewPi, no Arduino needed!

[Birkmose]

Yep, constructive discussion and dissemination of information.

Blanket statements that don’t rightfully depict the majority of the population is not constructive. The author of the program acknowledges and empathizes with your situation and is working to remedy the issue.

Your post, quite frankly is rude.

Cheers! (Shaking head too)

And how did you interpret my statement as representing the entire population? Opinions written by me in here can always just relate to me and me alone.

So when I say Fermentracker doesn't seem like the right tool to track the Tilt, I mean it's not right for me. How can that be rude? Or have I misunderstood, and this thread is all about being nice and praise the tool?

You must meet a lot of rude people if everyone that voices their opinion are rude?

(Shaking my head vigorously)

 

[PhillyBrewDoug]

ESP8266

@jangevaa Have you tried Sparkfun.com? It's more expensive, but then again, everything is compared to Aliexpress. The Lolin Aliexpress store is definitely empty, don't know if they'll restock.

 

[jangevaa]

@jangevaa Have you tried Sparkfun.com? It's more expensive, but then again, everything is compared to Aliexpress. The Lolin Aliexpress store is definitely empty, don't know if they'll restock.

I have a couple spare here to play around with, not super desperate. I was intending to get a bunch of people from my homebrew club running with some of these great ESP32 projects, so bulk discount is ideal

 

[Thorrak]

I have a couple spare here to play around with, not super desperate. I was intending to get a bunch of people from my homebrew club running with some of these great ESP32 projects, so bulk discount is ideal

I’m anticipating (hoping?) LoLin will be back up and running in the next few weeks as China goes back to work following the new year and Coronavirus concerns. I’d give it a bit before buying other boards, as if nothing else the form factor will be substantially different.

 

[Thorrak]

For what it’s worth, I fired up a debugger and babysat the Tilt monitor process for a good 45 minutes tonight looking for errors. I didn’t find any - it worked as intended. That doesn’t mean they aren’t there, just that I didn’t see them.

I did tweak a few things in the dev branch to hopefully make future debugging easier - I haven’t done a lot with the raw Python Sentry client, but it’s added to the tilt scanner utility now so hopefully I can get true error reports. This is now available on dev.

 

[cripplecreek]

@Thorrak thank you for all of your efforts!! I will update later today and report back my findings.

For what it's worth, should we take a look at Tilt Pi's code for clues? As I've mentioned, it works without issue on my hardware, where Fermentrack is not.

I have a background in IT. I'm not a programmer. But I'm happy to help in any way / shape I can. Let me know how I can help.

Cheers!

 

[Thorrak]

@Thorrak thank you for all of your efforts!! I will update later today and report back my findings.

For what it's worth, should we take a look at Tilt Pi's code for clues? As I've mentioned, it works without issue on my hardware, where Fermentrack is not.

I have a background in IT. I'm not a programmer. But I'm happy to help in any way / shape I can. Let me know how I can help.

Cheers!

HEH. Ironically, Tilt Pi and I use the same libraries - or at least did as of a few months ago.

I think a big part of the issue is that the underlying library - aioblescan - has since been updated in a way that broke backwards compatibility. The Tilt guys (apparently intelligently!) created a custom version which they locked before the change.

If you are comfortable with a command line, after upgrading log into your pi, run the following, and send me the output (your upgrade.log) via a PM:


sudo su fermentrack
cd ~/fermentrack/
cat upgrade.log

 

[marshodbrew]

I am just now catching up on all this. I am having the same problem where temperatures are not displaying and the tilt is not being recorded. I am excited to try to fix on my lunch break. So,
step 1: update fermentrack through the web interface
Step 2: reboot pi

That’s it? Or is there something that should be done through the command line also? I am obvy a little confused

 

[Thorrak]

I have a couple spare here to play around with, not super desperate. I was intending to get a bunch of people from my homebrew club running with some of these great ESP32 projects, so bulk discount is ideal

They appear to be back!

 

[cripplecreek]

@Thorrak , no problem. Here is the output:

fermentrack@tiltpi:~/fermentrack$ cat upgrade.log
::: Triggering upgrade from branch dev
::: Waiting 1 second for Fermentrack to send updates if triggered from the web...
::: Stopping circus...
::: Updating from git...
::: Updating requirements via pip3...
::: Running manage.py migrate...
::: Running manage.py collectstatic...
::: Relaunching circus...
::: Complete!
v'
Your branch is behind 'origin/dev' by 12 commits, and can be fast-forwarded.
(use "git pull" to update your local branch)
Updating 7e1afc5..1dd08d9
Fast-forward
app/api/clog.py | 6 +-
app/templates/site_help.html | 6 +-
app/views.py | 24 ++-----
brewpi-script/scriptlibs/pinList.py | 40 +++++++++---
docs/source/develop/changelog.rst | 22 +++++++
gravity/api/sensors.py | 2 +-
gravity/models.py | 10 ++-
gravity/tilt/tilt_monitor_aio.py | 6 ++
requirements.txt | 4 +-
utils/force_upgrade.sh | 124 ------------------------------------
utils/force_upgrade3.sh | 22 +++----
utils/upgrade.sh | 123 -----------------------------------
utils/upgrade3.sh | 22 +++----
13 files changed, 106 insertions(+), 305 deletions(-)
delete mode 100755 utils/force_upgrade.sh
delete mode 100755 utils/upgrade.sh
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already up-to-date: Django<1.12,>=1.11 in /home/fermentrack/venv/lib/python3.7/site-packages (from -r requirements.txt (line 1)) (1.11.28)
Requirement already up-to-date: configobj in /home/fermentrack/venv/lib/python3.7/site-packages (from -r requirements.txt (line 2)) (5.0.6)
Requirement already up-to-date: pytz in /home/fermentrack/venv/lib/python3.7/site-packages (from -r requirements.txt (line 4)) (2019.3)
Requirement already up-to-date: raven in /home/fermentrack/venv/lib/python3.7/site-packages (from -r requirements.txt (line 5)) (6.10.0)
Requirement already up-to-date: django-constance[database] in /home/fermentrack/venv/lib/python3.7/site-packages (from -r requirements.txt (line 6)) (2.6.0)
Requirement already up-to-date: GitPython in /home/fermentrack/venv/lib/python3.7/site-packages (from -r requirements.txt (line 7)) (3.0.8)
Requirement already up-to-date: zeroconf in /home/fermentrack/venv/lib/python3.7/site-packages (from -r requirements.txt (line 8)) (0.24.4)
Requirement already up-to-date: circus<0.17.0,>=0.16.0 in /home/fermentrack/venv/lib/python3.7/site-packages (from -r requirements.txt (line 9)) (0.16.1)
Requirement already up-to-date: chaussette in /home/fermentrack/venv/lib/python3.7/site-packages (from -r requirements.txt (line 11)) (1.3.0)
Requirement already up-to-date: huey>=2.0 in /home/fermentrack/venv/lib/python3.7/site-packages (from -r requirements.txt (line 12)) (2.1.3)
Requirement already up-to-date: pid in /home/fermentrack/venv/lib/python3.7/site-packages (from -r requirements.txt (line 13)) (2.2.5)
Requirement already up-to-date: pyserial in /home/fermentrack/venv/lib/python3.7/site-packages (from -r requirements.txt (line 14)) (3.4)
Requirement already up-to-date: pyudev in /home/fermentrack/venv/lib/python3.7/site-packages (from -r requirements.txt (line 16)) (0.22.0)
Collecting requests
Downloading requests-2.23.0-py2.py3-none-any.whl (58 kB)
Requirement already up-to-date: esptool in /home/fermentrack/venv/lib/python3.7/site-packages (from -r requirements.txt (line 19)) (2.8)
Requirement already up-to-date: redis in /home/fermentrack/venv/lib/python3.7/site-packages (from -r requirements.txt (line 21)) (3.4.1)
Requirement already up-to-date: pybluez==0.23 in /home/fermentrack/venv/lib/python3.7/site-packages (from -r requirements.txt (line 23)) (0.23)
Requirement already up-to-date: aioblescan==0.2.6 in /home/fermentrack/venv/lib/python3.7/site-packages (from -r requirements.txt (line 24)) (0.2.6)
Requirement already satisfied, skipping upgrade: six in /home/fermentrack/venv/lib/python3.7/site-packages (from configobj->-r requirements.txt (line 2)) (1.14.0)
Requirement already satisfied, skipping upgrade: django-picklefield; extra == "database" in /home/fermentrack/venv/lib/python3.7/site-packages (from django-constance[database]->-r requirements.txt (line 6)) (2.1.1)
Requirement already satisfied, skipping upgrade: gitdb2>=3 in /home/fermentrack/venv/lib/python3.7/site-packages (from GitPython->-r requirements.txt (line 7)) (3.0.2)
Requirement already satisfied, skipping upgrade: ifaddr in /home/fermentrack/venv/lib/python3.7/site-packages (from zeroconf->-r requirements.txt (line 8)) (0.1.6)
Requirement already satisfied, skipping upgrade: psutil in /home/fermentrack/venv/lib/python3.7/site-packages (from circus<0.17.0,>=0.16.0->-r requirements.txt (line 9)) (5.6.7)
Requirement already satisfied, skipping upgrade: tornado<5.0,>=3.0 in /home/fermentrack/venv/lib/python3.7/site-packages (from circus<0.17.0,>=0.16.0->-r requirements.txt (line 9)) (4.5.3)
Requirement already satisfied, skipping upgrade: pyzmq>=17.0 in /home/fermentrack/venv/lib/python3.7/site-packages (from circus<0.17.0,>=0.16.0->-r requirements.txt (line 9)) (18.1.1)
Requirement already satisfied, skipping upgrade: urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 in /home/fermentrack/venv/lib/python3.7/site-packages (from requests->-r requirements.txt (line 17)) (1.25.8)
Requirement already satisfied, skipping upgrade: idna<3,>=2.5 in /home/fermentrack/venv/lib/python3.7/site-packages (from requests->-r requirements.txt (line 17)) (2.8)
Requirement already satisfied, skipping upgrade: chardet<4,>=3.0.2 in /home/fermentrack/venv/lib/python3.7/site-packages (from requests->-r requirements.txt (line 17)) (3.0.4)
Requirement already satisfied, skipping upgrade: certifi>=2017.4.17 in /home/fermentrack/venv/lib/python3.7/site-packages (from requests->-r requirements.txt (line 17)) (2019.11.28)
Requirement already satisfied, skipping upgrade: pyaes in /home/fermentrack/venv/lib/python3.7/site-packages (from esptool->-r requirements.txt (line 19)) (1.6.1)
Requirement already satisfied, skipping upgrade: ecdsa in /home/fermentrack/venv/lib/python3.7/site-packages (from esptool->-r requirements.txt (line 19)) (0.15)
Requirement already satisfied, skipping upgrade: smmap2>=2.0.0 in /home/fermentrack/venv/lib/python3.7/site-packages (from gitdb2>=3->GitPython->-r requirements.txt (line 7)) (2.0.5)
Installing collected packages: requests
Attempting uninstall: requests
Found existing installation: requests 2.22.0
Uninstalling requests-2.22.0:
Successfully uninstalled requests-2.22.0
Successfully installed requests-2.23.0
Operations to perform:
Apply all migrations: admin, app, auth, contenttypes, database, external_push, firmware_flash, gravity, sessions
Running migrations:
No migrations to apply.
ok
ok
fermentrack@tiltpi:~/fermentrack$

 

[Birkmose]

For what it’s worth, I fired up a debugger and babysat the Tilt monitor process for a good 45 minutes tonight looking for errors. I didn’t find any - it worked as intended. That doesn’t mean they aren’t there, just that I didn’t see them.

I did tweak a few things in the dev branch to hopefully make future debugging easier - I haven’t done a lot with the raw Python Sentry client, but it’s added to the tilt scanner utility now so hopefully I can get true error reports. This is now available on dev.

Did an interresting experiment today. As I wrote earlier i made a fresh install with Pi 3 Model B, Raspbian Buster. And I could not make it work no matter what i did with different updates of Bluetooth libraries and so on.

Today I made the exact same setup only with a Raspberry Pi 4. Did no updates other than updating Raspbian after install, and it works !

Only strange thing is that i logs every 15 seconds, but I guess i can change that somehow?

 

[marshodbrew]

Ok maybe this will help out someone else. Not sure.

I reinstalled raspbian buster and fermentrack. At the end of my install it gave me the message that fermentrack could be accessed at http://x.x.x.12

I checked my router and it was showing two separate IPs for my raspberry pi. One simply was named raspberrypi and was at address x.x.x.55 and the other was named “Rowlandbrew” (name I gave during fermentrack set up) and was at location x.x.x.12.

so, I went through the x.x.x.12 site as before and reassigned my fermentrack settings and controller through the guided set up as usual. Again it was working but not logging data. The LCD type display (in the web interface) was showing the beer temps but the other areas were not as before. So, I logged onto the x.x.x.55 and boom all the values showed up. Went back to the x.x.x.12 pages and they were all there now. Not sure why the glitch but seems to be working at the moment.

 

[day_trippr]

Browser cache?
[edit] Or maybe router ARP cache?

Cheers!

 

[cripplecreek]

Ok maybe this will help out someone else. Not sure.

I reinstalled raspbian buster and fermentrack. At the end of my install it gave me the message that fermentrack could be accessed at http://x.x.x.12

I checked my router and it was showing two separate IPs for my raspberry pi. One simply was named raspberrypi and was at address x.x.x.55 and the other was named “Rowlandbrew” (name I gave during fermentrack set up) and was at location x.x.x.12.

so, I went through the x.x.x.12 site as before and reassigned my fermentrack settings and controller through the guided set up as usual. Again it was working but not logging data. The LCD type display (in the web interface) was showing the beer temps but the other areas were not as before. So, I logged onto the x.x.x.55 and boom all the values showed up. Went back to the x.x.x.12 pages and they were all there now. Not sure why the glitch but seems to be working at the moment.

If you had Wifi enabled and ethernet plugged into the Pi, you would also see a similar behavior. You'd get two IPs on the Pi and there is a chance that Fermentrack would bind to the first interface that was up and passing traffic (most likely ethernet b/c there is a lag time for the Pi to connect to your wireless network).

 

[cripplecreek]

So I have a TiltBridge that was flashed within the last 2 weeks. It can see my Tilt without issue and displays changes on the LCD. However, it is not reporting data into Fermentrack. During the setup, fermentrack discovered the Bridge without issue, but it wont pass data. I've rebooted the Pi and the TiltBridge several times. I was planning on using this as a workaround the to the bluetooth Tilt problems that are well discussed here. Sorta of bummed b/c I have a brew planned for this weekend. I read where people are saying that a Pi 4 works for them, but I had to have to buy another $60+/- Pi just to get Fermentrack working...

 

[jangevaa]

So I have a TiltBridge that was flashed within the last 2 weeks. It can see my Tilt without issue and displays changes on the LCD. However, it is not reporting data into Fermentrack. During the setup, fermentrack discovered the Bridge without issue, but it wont pass data. I've rebooted the Pi and the TiltBridge several times. I was planning on using this as a workaround the to the bluetooth Tilt problems that are well discussed here. Sorta of bummed b/c I have a brew planned for this weekend. I read where people are saying that a Pi 4 works for them, but I had to have to buy another $60+/- Pi just to get Fermentrack working...

You can run fermentrack in a docker container on a desktop computer if you like.

 

[Thorrak]

So I have a TiltBridge that was flashed within the last 2 weeks. It can see my Tilt without issue and displays changes on the LCD. However, it is not reporting data into Fermentrack. During the setup, fermentrack discovered the Bridge without issue, but it wont pass data. I've rebooted the Pi and the TiltBridge several times. I was planning on using this as a workaround the to the bluetooth Tilt problems that are well discussed here. Sorta of bummed b/c I have a brew planned for this weekend. I read where people are saying that a Pi 4 works for them, but I had to have to buy another $60+/- Pi just to get Fermentrack working...

I was out of town this past weekend, but going through and checking all the functionality of TiltBridge (including Fermentrack) is at the top of the list as I push forward with getting the next release of TiltBridge out.

A Pi 4 shouldn’t make any difference. I do most of my testing on a Pi 3, but the version of the Pi shouldn’t matter at all for TiltBridge builds.

 

[kdw2pd]

As a complete electrical novice, I was able to wire this up and get it working, so if you're looking for a minimal BoM to get going, this will work. If you're ordering parts for a Fermentrak build, I'd strongly recommend wiring it up with Thorrak's breakout boxes, as that makes for a much neater build. I went this route because I had all of the parts on hand from a different build.

Thanks to day_trippr for pointing me in this direction.

 

[chucknorris101]

Going to be brewing my first batch tomorrow using this controller and my new glycol setup - from reading previous posts it looks like the best plan is to use the fridge constant mode? Are there tweaks to the heating or cooling overshoot? Im thinking the cooling one the overshoot time should be reduced alot. Any other tweaks for those running glycol? I know Thorrak said hes going to get to it, but guessing its not ready quite done yet.

Any other watchouts to first use? havent really tested too much other than wiring and controlling my system in the on-off sense

 

[Scotty11]

I can't wait for glycol support either and to be able to set a profile. I'm now on my second batch with the following settings and it is working well. My set up is:

2 - 1BBL S&S brewtech fremertors
1 - SS brewtech gylcol chiller
1 - fermentrack controller
2 - ESP6266 controls

I'm using the heating pad from s&s brewtech and a single 12V 30 amp power supply. The gylcol loop is 24VAC zone values. The Fridge sensor is in the thermelwells.

my settings are as followings. Please somebody tell my I should change something because several of the settings where best guess. But they been working so far. The last beer I brewed was a pilnser and the graph below shows the beginning of the diacetyl rest.

the settings:

Min Temperature: 33.8
Max Temperature: 86
PID: Kp: 0
PID: Ki: 0
PID: Kd: 0
PID: maximum: 18
Integrator: Max temp error C: 0.8
Temperature idle range top: 0.5
Temperature idle range bottom: -0.5
Heating target upper bound: 0.5
Heating target lower bound: -0.6
Cooling target upper bound: 0.5
Cooling target lower bound: -0.6
Maximum time in seconds for heating overshoot estimator: 120
Maximum time in seconds for cooling overshoot estimator: 120
Beer fast filter delay time: 1
Beer slow filter delay time: 1
Beer slope filter delay time: 1
Fridge fast filter delay time: 1
Fridge slow filter delay time: 1
Fridge slope filter delay time: 1
Use half steps for rotary encoder? No
Using light as heater? No
Temperature format: Fahrenheit

 

[chucknorris101]

Why set the PID Terms to 0? or does the PID not work on fridge temp?

 

[Thorrak]

I got my glycol chiller yesterday.

 

[Scotty11]

Why set the PID Terms to 0? or does the PID not work on fridge temp?

Yes that is my understanding. And you need to set constant fridge temp and need to use the fridge chamber temp probe is the primary temperature probe

 

[Scotty11]

I got my glycol chiller yesterday.

That is great news!!

 

[chucknorris101]

Scratch the Mayday. Looks like it was faulty dupont connections...

 

[chucknorris101]

Disregard above, definitely still have an issue with my main chamber controller, and wondering if there is a relay board issue or what might be wrong. Heat works great but cool won't activate the relay. I attached a picture of the setup. I've tried checking continuity from the main pcb to each of these resistors in the picture. Specifically with the device in cool mode, which is on IN1 side (far side in picture). Cool wire is continuous to all resistors except r2 and r3, which seem to control the relay. I get continuity of the heat wire to both r2 and r3. The5v wire is continuous to most things, except to the led of the cool side. The led won't light up where continuity checking the hot side led it lights up. Wondering if the board is just defective or I shorted something while assembling somehow?

 

[lateknightucd]

@Thorrak, first of all, thanks for all of the work you've done on this project! Fermentrack (and the Tilt support) has been a life-saver as I travel (well, traveled before all of this) for work quite a bit. I had an interesting issue with my last batch that I wanted to run past the group. I'm running FermenTrack on a Pi-Zero W and have an ESP8266 on one of your boards with the sensor board connected via RJ-11. Twice in my last batch (fortunately an ale) the ESP appears to have lost all pin configuration info. Both times I've been able to go in and simply reconfigure the proper sensors and relays but I'm getting ready to brew a lager and had hoped to fox this once and for all before starting that batch.

/tldr - Any idea why the ESP8266 would "forget" pin configuration after 5-7 days?

 

[day_trippr]

I'm curious about that, as I once saw the same syndrome while working on connecting an Uno via Wifi for BrewPi service many years ago.
Early attempts led to dodgy connections which caused the BrewPi host code to send a full-on reset to the Uno which put everything to their initial, default settings.
I wonder if you're seeing the same code executing...

Cheers!

 

[lateknightucd]

I'm curious about that, as I once saw the same syndrome while working on connecting an Uno via Wifi for BrewPi service many years ago.
Early attempts led to dodgy connections which caused the BrewPi host code to send a full-on reset to the Uno which put everything to their initial, default settings.
I wonder if you're seeing the same code executing...

Cheers!

That's an interesting thought. Any suggestion on a particular log or somewhere to look on the Pi to run down that theory? My Raspberry Pi is connected via Ethernet to a switch in the same basement space and the ESP8266 is probably three feet from a WiFi access point so I'm not sure about a dodgy connection between the two. That said I may reflash the ESP8266 and leave it connected to the Raspberry Pi by serial/USB connection and see if the problem replicates.

 

[day_trippr]

As I recall there was enough evidential dialog in the BrewPi log for the running instance to see the host was getting frustrated and finally shot the poor Uno in the head...

Cheers!

 

[chucknorris101]

Solved my relay problem above. Found it after testing a new relay and then installing it. Problem was with the 200lb gorilla installing it. Popped the LED off both the original and the replacement relay, and that is critical for these relays to engage apparently. So replaced it with one of the spares i ordered, didnt screw down that side's nut again and good to go.

 

[kdw2pd]

So everything was going smoothly with my ESP8266 Fermentrack setup until I hit a snag yesterday: the program stopped recognizing the OneWire beer and chamber temp probes. The probes had been working consistently for about a week with no issues. It happened for the first time yesterday morning. First thing I tried was unassigning the pins, no go. I opened the box up, the soldering looked okay. Plugged it back in, and the OneWires were available for assignment, and everything was cooperating again.

I started fermentation at about 8 p.m. last night, everything was going fine until 1 a.m., when the probes cut out again. I tried resetting EEPROM with no success. In an Arduino BrewPi thread, a couple folks suggested that this is often a power supply issue, and suggested plugging in the Arduino power supply as well as the Pi. However, I have the ESP powered through the Pi via a new Samsung-branded micro USB cable, so can't power it directly. The Pi is powered via a 5W 2.5A CanaKit supply plugged into the wall, so that part should be good to go too. I could, I suppose, re-flash the ESP firmware and set it up to run via WiFi, then power it directly through a 1A 3.3W supply separately from the Pi if that would make any difference.

I'd appreciate any points on what to try next. This beer is fermenting at ambient in my basement, so the temp probes aren't a huge loss atm, but I'd like it to work properly moving forward.

 

[lateknightucd]

This is the same issue I described above. Interestingly, my ESP was connected via WiFi at the time and is directly wired to a power supply module via Thorrak's breakout board so I think it's unlikely power was my issue. I reflashed to the serial firmware and have it connected directly to the PI at the moment (albeit via a powered USB hub) and it's been working in a stable manner for the past 48-72 hours so I'm hopeful that was the issue. If I'm reading your post correctly, are you already using the serial firmware?

 

[LBussy]

The WiFi radio takes quite a bit more power than you would think. Always troubleshoot with a separate power supply. Since both BrewPi Remix and Fermentrack will talk via WiFi, there's no reason other than convenience to try to power via the USB.

Speaking of which, how convenient is it that the sensors go out?

 

[kdw2pd]

Ignore me: it's a wiring issue. When I take the top off the project enclosure, they pop right up on Fermentrack. I'm super confused, but it's not an ESP/Fermentrack issue.

 

[Thorrak]

Ignore me: it's a wiring issue. When I take the top off the project enclosure, they pop right up on Fermentrack. I'm super confused, but it's not an ESP/Fermentrack issue.

Did you end up figuring out what was causing it? Was something being shorted against the case or something?

 

[kdw2pd]

Did you end up figuring out what was causing it? Was something being shorted against the case or something?

Bad soldering of the DS18B20s. My fiancee resoldered them after the initial issues because I suck at soldering, and they worked just fine. Same issue again today, except it was only the beer probe. Opened it up and one of the wires on the beer probe wasn't attached to the terminal on the 3.5mm connector. The fridge probe worked in both female connectors in the case, so it's only a probe issue.

Opening up the case involved me unplugging and then plugging back in the pins, which likely temporarily bent the poorly soldered wire against the terminal, where it made a connection for a short period of time before falling off again. So just a coincidence that opening up the case helped.

 

[Deric]

Does this look right?

ETA ... probably not since I get lines of solid squares on the screen instead of text.

View attachment 370245

View attachment 370320

Can someone verify the attached wiring for the logic level converter? I added this LCD https://www.amazon.com/gp/product/B07MTFDHXZ/ref=ppx_yo_dt_b_asin_title_o01_s01?ie=UTF8&psc=1
And this logic level converter https://www.amazon.com/gp/product/B073D4DJDC/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1

When I started it up I got the same "squares" as LBussy. I bypassed the logic converter and it works fine. Double checked wiring (still doesn't mean I didn't miss something) and even swapped out the logic converter and get the same thing.... Just want to make sure I have it wired right before looking elsewhere...

Thanks

 

[Thorrak]

Can someone verify the attached wiring for the logic level converter? I added this LCD https://www.amazon.com/gp/product/B07MTFDHXZ/ref=ppx_yo_dt_b_asin_title_o01_s01?ie=UTF8&psc=1
And this logic level converter https://www.amazon.com/gp/product/B073D4DJDC/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1

When I started it up I got the same "squares" as LBussy. I bypassed the logic converter and it works fine. Double checked wiring (still doesn't mean I didn't miss something) and even swapped out the logic converter and get the same thing.... Just want to make sure I have it wired right before looking elsewhere...

Thanks

If you can bypass the logic converter and it works, then you can probably just leave it out. Most of those LCDs require 5V logic - if you have one that works at 3v3, that's awesome.

 

[Deric]

Thanks! Will call it good. Ordered a power supply and some jacks for temp probes. Time to start planning an enclosure.