7 ms·
The PCB stores the state persistently, but it doesn't expose it. After all, how would it? ADC, I2C, SPI, PWM? Those pins cost unjustified $, what percentage of
by randunel 2y ago
The PCB stores the state persistently, but it doesn't expose it. After all, how would it? ADC, I2C, SPI, PWM? Those pins cost unjustified $, what percentage of buyers would even know what those letters mean?
You can check state persistence by cutting the gate's power during operation. When the power comes back on, your next button press will trigger the next operation in order, not the previous one (if you cut the power during opening, the next button press closes it and viceversa).
- PenguinCoder 2y agoOver thinking it I suppose. All it takes is a simple relay board, registering a signal on whatever pinout is available, be it GPIO or SPI. Example: https://www.seco-larm.com/product/sr-1212-c7alq https://www.seco-larm.com/product/sr-1212-c7alq And https://www.seco-larm.com/product/sm-226l-3q/ https://www.seco-larm.com/product/sm-226l-3q/
- stavros 2y agoThese switches do expose their state over Zigbee, it's just that their state is only on when the door is moving (I believe). Other than that, they don't know what the door's status is, that's why the OP had a door sensor.
- ssl-3 2y agoAccording to the manufacturer-supplied diagram shown (and the video of the board in-situ), the gate control board knows that the gate is open or closed based on the status of two limit switch inputs, labeled SWO and SWC. Such an interface cannot get any more exposed than that. There's no reason to throw a stew of TLAs at the problem. (I have a strong suspicion that nobody responding here actually -- you know -- looked at this problem as it actually exists before deciding that it somehow cannot be resolved.)