ops_keisha
@kstewart · Joined March 2025
Plant manager · food and beverage
- Topics
- 8
- Replies
- 64
- Points
- 0
Forum Replies Created
Normal Upload with IO0 bridged and it flashed first time. I’m sending jam as 0/1 rather than true/false so it charts. Thank you.
We still have a few of these on line counters, so I’ve been through it.
P6 is the RUN pin. Shorting its two holes resets the board, so solder in two header pins and wire a normal momentary push button across them. That’s your reset button, nothing else needed.
P5 on a rev 2 board is extra power and GPIO:
P5-1 5V P5-2 3.3V
P5-3 GPIO28 P5-4 GPIO29
P5-5 GPIO30 P5-6 GPIO31
P5-7 GND P5-8 GNDGPIO28/29 can be a second I2C bus. It’s meant to be fitted from underneath, so pin numbering looks mirrored from the top, the square pad is pin 1. For a temperature logger you don’t need P5, use the main header (a DS18B20 on GPIO4 is the easy one). Everything is 3.3 V logic, never 5 V into a GPIO.
Is the sensor powered from 3.3 V or 5 V? Some of those boards output more than 3.3 V on 5 V supply.
Changed the line, the on_connect had the old four arguments so that needed fixing too. Service is up, readings back on the board and I tested the alarm by opening the chiller door for a few minutes. Thanks Aoife, and Ciarán for the stopgap.
How many probes? Matters for whether a redesign pays off.
Contractor swapped the Uno for an ESP32-ETH board last week, same photo-eye. The ERP job now pulls the hourly increases, and the first full week matched the hand count within 2 cases. One snag: they first sent the count as text in quotes, so it showed as a latest value but nothing charted. Sending a number fixed it.
You nailed it. dnsIP was an internal server and the lookup failed. IT added a forwarder for the broker host, the node is back on DHCP and connected first try. They were happier to do that than to see a static IP.
One total per shift, shifts change at 06:00, 14:00 and 22:00. The ERP is on a server inside our network and IT won’t open it to the internet, that was already a fight.
2.1.0. The tech’s notes say 1.6.1.
Same trap with a display library last year, it re-initialised the bus behind our back.
Which meter is it? The manual’s register map says whether a value is a float or a scaled integer.
Sent that exact question. Vendor two sent a PDF with the advertising format the same day. Vendor one said “the app has a CSV export”. Ordering two from vendor two to test with a gateway.
Tip from commissioning skids: while you’re testing, send the raw count next to the volts. When a reading looks wrong in three months you can tell a gain mistake from a sensor problem straight from the chart.
We do the same on our line sensors. One tip from the floor: print the setup AP name on a sticker on the case. Nobody remembers which node is “ESP-3C84A1” six months later.
“Same SD card as the receipt printer” is the clue. Check /boot/firmware/config.txt (on Bookworm it moved from /boot) for dtoverlay=disable-bt. Our integrator put that in for an RS-485 hat on a line gateway and six months later someone spent a day trying to pair a scanner to the same Pi.
On the Pi 4 the Bluetooth chip hangs off the good UART. disable-bt gives that UART to the GPIO pins and Bluetooth disappears completely, which matches your rfkill output. Comment the line out, then:
sudo systemctl enable --now hciuart
sudo reboot
# after reboot
rfkill list # should show hci0: Bluetooth
bluetoothctl showIf you need both a hardware UART and Bluetooth on the Pi 4, dtoverlay=miniuart-bt keeps Bluetooth on the mini UART, or use one of the extra UARTs (uart2 to uart5) the Pi 4 has.