ops_keisha
@kstewart · Se unió el marzo 2025
Plant manager · food and beverage
- Temas
- 8
- Respuestas
- 64
- Puntos
- 0
Respuestas de foro creadas
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.
Traducido del English por IA ·
Todavía tenemos algunas de estas en contadores de líneas, así que las he estudiado.P6 es el pin RUN. Cortocircuitar sus dos agujeros reinicia la placa, así que suelde dos pines de cabecera y conecte un pulsador normal entre ellos. Ese es su botón de reinicio, no hace falta nada más.P5 en una placa rev 2 ofrece alimentación extra y 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 GNDLos GPIO28/29 pueden usarse como un segundo bus I2C. Está pensado para montarse por debajo, por lo que la numeración de pines parece invertida desde arriba; el pad cuadrado es el pin 1. Para un registrador de temperatura no necesita P5, use el conector principal (un DS18B20 en GPIO4 es la opción más sencilla). Todo funciona con lógica de 3,3 V, nunca aplique 5 V a un GPIO.
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.
Traducido del English por IA ·
Consejo de las unidades de puesta en marcha: mientras pruebas, registra la cuenta bruta junto a los voltios. Cuando una lectura parezca incorrecta dentro de tres meses, podrás distinguir un error de ganancia de un problema del sensor directamente en el gráfico.
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.
Traducido del English por IA ·
Nosotros hacemos lo mismo en nuestros sensores de línea. Un consejo de planta: imprime el nombre del AP de configuración en una etiqueta pegada en la carcasa. Nadie recuerda seis meses después cuál nodo es «ESP-3C84A1».
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.
Traducido del English por IA ·
«La misma tarjeta SD que la impresora de recibos» es la pista. Revisa /boot/firmware/config.txt (en Bookworm se movió desde /boot) buscando dtoverlay=disable-bt. Nuestro integrador lo puso para un hat RS-485 en una pasarela de línea y seis meses después alguien pasó un día intentando emparejar un escáner con la misma Pi.En la Pi 4, el chip Bluetooth está conectado a la UART buena. disable-bt cede esa UART a los pines GPIO y el Bluetooth desaparece por completo, lo que coincide con tu salida de rfkill. Comenta la línea y luego:
sudo systemctl enable --now hciuart
sudo reboot
# tras reiniciar
rfkill list # debería mostrar hci0: Bluetooth
bluetoothctl showSi necesitas a la vez una UART de hardware y Bluetooth en la Pi 4, dtoverlay=miniuart-bt mantiene el Bluetooth en la mini UART, o usa una de las UART adicionales (uart2 a uart5) que tiene la Pi 4.
«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.