树莓派Python双传感器计数器计数不一致问题排查咨询

Hey there, let's dig into why your two counters are acting inconsistently—this could stem from both code oversights and hardware quirks. Let's break down each possible cause and how to fix them:

Code-Related Issues #

1. Missing Global Variable Declarations #

Looking at your callback functions, you're modifying countery and counterz but haven't declared them as global variables inside the functions. In Python, if you try to modify a global variable within a function without using the global keyword, Python will treat it as a local variable instead. This means your callbacks are actually creating local versions of the counters that don't affect the global values you're displaying in your Tkinter GUI.

Fix: Add global declarations at the start of each callback:

countery = 0
counterz = 0

def counteryPlus(channel):
    global countery
    if GPIO.input(channel):
        countery += 1

def counterzPlus(channel):
    global counterz
    if GPIO.input(channel):
        counterz += 1

2. Backwards Edge Detection Logic #

You're using GPIO.FALLING edge detection, which triggers the callback when the pin goes from HIGH to LOW. But your callback checks if GPIO.input(channel)—which is equivalent to checking if the pin is HIGH. By the time the FALLING edge triggers the callback, the pin is already LOW, so this condition will almost always be false, leading to countery += 0 (no count increment). The times it does count are likely due to signal bouncing where the pin briefly jumps back to HIGH before settling LOW.

Fix: Since you're using edge detection, you don't need to re-check the pin state—the edge detection already confirms the sensor triggered. Simplify your callbacks:

def counteryPlus(channel):
    global countery
    countery += 1

def counterzPlus(channel):
    global counterz
    counterz += 1

3. Tkinter Thread Safety Issues #

Raspberry Pi GPIO callbacks run in a background thread, but Tkinter GUI updates must happen in the main thread. If you're updating your GUI directly from the GPIO callbacks, this can cause race conditions where the GUI reads the counter values mid-update, leading to inconsistent displays (or even crashes).

Fix: Use Tkinter's after() method to let the main thread periodically update the GUI:

import tkinter as tk

root = tk.Tk()
label_y = tk.Label(root, text="Counter Y: 0")
label_z = tk.Label(root, text="Counter Z: 0")
label_y.pack()
label_z.pack()

def update_gui():
    label_y.config(text=f"Counter Y: {countery}")
    label_z.config(text=f"Counter Z: {counterz}")
    root.after(100, update_gui)  # Refresh every 100ms

# Start the GUI update loop before launching the main Tkinter loop
update_gui()
root.mainloop()

Hardware-Related Issues #

1. Dangerous Level Mismatch (Critical!) #

You mentioned connecting the Raspberry Pi GPIO directly to the relay's Normally Open (NO) pin, which is powered by 24V. Raspberry Pi GPIO pins only tolerate 3.3V input—plugging in 24V will damage the pins over time, leading to intermittent signal reading (or complete failure).

Fix: Use an optocoupler or level shifter module to convert the 24V relay signal to 3.3V compatible with the Pi's GPIO. This isolates the high-voltage circuit from your Pi and protects the GPIO pins.

2. Signal Bouncing & Power Interference #

Even with bouncetime=800, relay contacts can bounce longer than expected, leading to missed or duplicate counts. Additionally, 24V power supplies can introduce electrical noise that interferes with the Pi's GPIO readings, especially if grounds aren't shared properly.

Fixes:

• Increase the bouncetime to 1000ms (1 second) to account for longer relay bounce.
• Ensure the 24V sensor/relay circuit shares a common ground with the Raspberry Pi to eliminate ground loop interference.
• Use a filtered power supply for the 24V circuit to reduce electrical noise.

3. Loose or Faulty Wiring #

Intermittent counts often come from loose connections. If the relay's NO pin isn't making consistent contact with the Pi's GPIO, you'll get random missed triggers.

Fix:

• Inspect all wiring for loose plugs or frayed wires.
• Use a multimeter to test the relay's output: when the sensor triggers, confirm the NO pin correctly switches from HIGH (24V) to LOW (0V).

内容的提问来源于stack exchange，提问作者Brandon Lok