@Gregg TeHennepe no problems here with licensing, just launched BC and checked license. Did you by chance rename your computer? I did that once and I had to get in touch with BrunDog to update things.
Might wait for Windows 11Saw this new fanless mini pc from gigabyte with my search for the jasper lake N5105 10nm - 10w cpu... not available yet, and will not win any beauty contests, but is low power high performance and has a few other neat features like regular and m.2 ssd, along with being from a reputable manufacturer, I will likely get one for my BC implementation.
[Setup]
new string CC // declare a new string variable
CC = "1" // turn on lcd backlight
new string csroomtemp
new string csminisplitfinsensor
[Loop]
csroomtemp = "CS ROOM SENSOR" DisplayText // "CS ROOM SENSOR" is 1-wire temp input
display "ESP32-Cold Storage" 1 csroomtemp // "ESP32-Cold Storage" is interface
sleep 3000
csminisplitfinsensor = "CS MINI-SPLIT FIN SENSOR" DisplayText // "CS MINI-SPLIT FIN SENSOR" is 1-wire temp input
display "ESP32-Cold Storage" 1 csroomtemp // "ESP32-Cold Storage" is interface
sleep 3000
goto "Loop"
That is correct for the typo. I made correction to read csminisplitfinsensor.Not sure what your specific question is, but it looks like you have a copy/paste typo. Both of your display commands are writing the same string variable. I'm assuming the second display command should be for csminisplitfinsensor and not csroomtemp?
https://www.amazon.com/gp/product/B..._1?smid=AF7ERVVKLDA4G&psc=1&tag=forumyield-20What LCD hardware do you have, and how is it wired?
Before I move on with the return what is the most simple script I can send to ensure its not on BC end?I don't know if that is compatible... the amazon page shows the LCD which is correct, but I can't tell about the I2C "backpack" compatibility.
Thanks Pete, I'll check in in a few daysIt's likely not a script thing... its a firmware thing. The firmware is speaking one "language" while the LCD you have understands a different one.
I might be able to get you a basic firmware that will just write text... would be a couple of days though if you can hang.
GPIO | Input | Output | Notes |
0 | pulled up | OK | outputs PWM signal at boot |
1 | TX pin | OK | debug output at boot |
2 | OK | OK | connected to on-board LED |
3 | OK | RX pin | HIGH at boot |
4 | OK | OK | |
5 | OK | OK | outputs PWM signal at boot |
6 | x | x | connected to the integrated SPI flash |
7 | x | x | connected to the integrated SPI flash |
8 | x | x | connected to the integrated SPI flash |
9 | x | x | connected to the integrated SPI flash |
10 | x | x | connected to the integrated SPI flash |
11 | x | x | connected to the integrated SPI flash |
12 | OK | OK | boot fail if pulled high |
@BrunDog sorry if I am harassing you. Would it it be possible try again to integrate brucontrol into ispindel? Or maybe publish just a firmware version 7+ for us?@BrunDog I just checked iSpindel: Enable BruControl by BrunDog · Pull Request #428 · universam1/iSpindel
is there anything you could do?
The topic is marked as stale..
Hey Pete just checking in on this. ThanksIt's likely not a script thing... its a firmware thing. The firmware is speaking one "language" while the LCD you have understands a different one.
I might be able to get you a basic firmware that will just write text... would be a couple of days though if you can hang.
I have the LCD connected to a ESP32. I see Mega in the version name. Just checking if this is correct.OK... just added an LCD test firmware into the version 45 package. Download off the website, run the FW tool as usual, use the "BruControl.LCDTest.MEGA.S" version. This only displays a counter on a connected display, so should help you determine if the wiring and hardware are correct. This assumes the defaultI2C address on the backpack (no jumpers changed).
Thankyou. I'll give this a try next time I'm down thereYes. The order don’t change when you extend the wire length. But extending the wire length could introduce noise depending on the length and exposure. How long are they, and how many? You can use shielded wire (drained back at the controller ground only) and get better distances.
Edit: Updated the firmware again. ESP32 test LCD is in there. SDA and SCL are GPIO 21 and 22, respectively.
I don't understand the term "pull up" I have a resistor wired in per the diagrams on BC website. Although I'm using a 4.7K with 3.3v. it worked with a short single 1-wire probe. I'll give the 2.2K a shot.The nominal One-Wire pull-up resistor values are 2.2K for 3.3V applications and 4.7K for 5V applications.
fwiw, I have multiple One-Wire "networks" in my home including a few with 5 ds18b20 temperature sensors. Half of these networks are on 5V (Arduino UNO and MEGA usage) and the other half on 3.3V (Raspberry Pi and ESP8266/ESP32 applications), some with almost 20 meters of total wire, and all use the "nominal" pull-up values...
Cheers!
Enter your email address to join: