logo elektroda
logo elektroda
X
logo elektroda

OpenBeken 4-Relay Board: How to Script Break-Before-Make Logic With Delay?

dutchmhk 225 2
ADVERTISEMENT
  • #1 21636532
    dutchmhk
    Level 2  
    New to OpenBeken

    Just flashed 1.18.155 onto a BK7231N Cb3S chip. All good

    Chip controls 4 buttons and 4 relays.

    Was hoping I could create a template or script or rule to ensure "break before make" logic on the relays

    Is this possible?, if so, kindly help an old man
    AI: Could you please describe how your relays are wired and what they are controlling? For example, are they switching mains power, and do any of the relays need to be interlocked so they’re never on at the same time?
    4 buttons control 4 relays individually
    AI: Can you share a bit more about the exact “break before make” behavior you want—like, which relays should never be on together, and do you need a specific delay between turning one off and the next one on?
    Example: Push button 1 = relay 1 on. Push button 3 = relay 1 off - short delay - relay 3 on. etc etc.
  • ADVERTISEMENT
  • Helpful post
    #2 21636597
    p.kaczmarek2
    Moderator Smart Home
    Hmm, you can either do it manually in OBK script or Berry (we have Berry-enabled build), or maybe you could try the PinMutex driver which I made recently for one of our users?
    https://www.elektroda.com/rtvforum/topic3953586.html#21594298
    https://www.elektroda.com/rtvforum/topic4129224.html#21599650
    @spleefer90 is PinMutex still working good for you?
    Helpful post? Buy me a coffee.
  • #3 21636751
    dutchmhk
    Level 2  
    >>21636597 Hi and thank you for answering
    I am completely new to scripting in OpenBeken, but I am trying my best, but it seems my firmware is very limited in scripting functionality. I tried with various commands in my autoexec.bat:
    setChannel
    backlog
    led_enableAll
    gpio
    delay
    But the commands are not recognized at all. Tried the AI approach with ChatGPT, but no luck either.
    Do I need to enable a driver, or do I have some sort of minimal firmware? I am running on the latest 1.18.155
ADVERTISEMENT