logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

BK7231N - Universal IR Remote Contorl

yarix2 46359 181

TL;DR LABEL_AI_GENERATED

  • BK7231N-based universal IR remote control now has a working IR blaster on firmware 1.15.x, tested on a Model S08 / PCB S06-CBU-V1.2.
  • All flashing pins are exposed on the board, including TX1, RX1, GND, 3.3v, and CEN for reset.
  • After flashing, set PinDescription 7 IRSend, 8 IRRecv, and 24 wifiLed, then restart because IR pins do not change in real time.
  • Firmware 1.15.226 and the webapp log confirm IRRecv captures external remote codes, and IRSend can replay commands like LG-88-130-1.
AI summary based on the discussion. May contain errors.
ADVERTISEMENT
Report a violation of the law
Reply Cool? Ranking DIY | New topic
Notify about new articles
Listen:

  • P26 output stays low in IRSend mode

    #31 20267175
    omelchuk890
    Level 11  
    Posts: 70
    Rate: 10
    A small test of the output of P26, IROur, BK7231T was carried out.
    In relay mode, the output is 0.
    In relay mode, the inversion is output 1, about 0.8 volts on the transistor bases.
    IRSend mode - output 0, does not respond to commands in any way, everything is OK in the logs.
    When rebooting, the output is a meander with a frequency of 11.5 hertz.
    There is no reaction to the commands at the exit.
    BK7231N - Universal IR Remote Contorl
    BK7231N - Universal IR Remote Contorl
    BK7231N - Universal IR Remote Contorl
    Code: text Expand Select all Copy to clipboard
    Debug:CMD:loglevel set 6
Debug:API:POST to api/cmnd
Debug:CMD:cmd [IRSend  NEC-0x1-0x18-1]
Info:IR:IR send NEC-0x1-0x18-1 protocol 7 addr 0x1 cmd 0x18 repeats 0
Debug:API:POST to api/cmnd
Debug:CMD:cmd [IRSend  NEC-0x1-0x18-1]
Info:IR:IR send NEC-0x1-0x18-1 protocol 7 addr 0x1 cmd 0x18 repeats 0

    Device
  • ADVERTISEMENT
  • #32 20267201
    btsimonh
    Level 11  
    Posts: 66
    Help: 1
    Rate: 14
    omelchuk890 wrote:
    IRSend  NEC-0x1-0x18-1


    try "IRSend  NEC-1-18-1"
    and report...

    br,

    Simon
  • ADVERTISEMENT

  • IRSend command syntax makes no difference

    #33 20267243
    omelchuk890
    Level 11  
    Posts: 70
    Rate: 10
    btsimonh wrote:
    omelchuk890 wrote:
    IRSend  NEC-0x1-0x18-1


    try "IRSend  NEC-1-18-1"
    and report...

    br,

    Simon

    Debug:API:POST to api/cmnd
    Debug:CMD:cmd [IRSend NEC-0x1-0x18-0x7]
    Info:IR:IR send NEC-0x1-0x18-0x7 protocol 7 addr 0x1 cmd 0x18 repeats 0
    Debug:API:POST to api/cmnd
    Debug:CMD:cmd [IRSend NEC-0x1-0x18-a]
    Info:IR:IR send NEC-0x1-0x18-a protocol 7 addr 0x1 cmd 0x18 repeats 0
    Debug:API:POST to api/cmnd
    Debug:CMD:cmd [startDriver IR]
    Info:IR:Log from extern C CPP
    Info:IR:DRV_IR_Init: recv pin -1
    Error:CMD:command with name IRSend already exists!
    Debug:API:POST to api/cmnd
    Debug:CMD:cmd [IRSend NEC-1-18-1]
    Info:IR:IR send NEC-1-18-1 protocol 7 addr 0x1 cmd 0x18 repeats 0
    Debug:API:POST to api/cmnd
    Debug:CMD:cmd [IRSend NEC-1-18-1]
    Info:IR:IR send NEC-1-18-1 protocol 7 addr 0x1 cmd 0x18 repeats 0
    Debug:API:POST to api/cmnd
    Debug:CMD:cmd [IRSend NEC-1-18-1]
    Info:IR:IR send NEC-1-18-1 protocol 7 addr 0x1 cmd 0x18 repeats 0

    There is no difference between the teams.
    The output is still a meander of 11.6 hertz.
    BK7231N - Universal IR Remote Contorl

  • Check PWM carrier frequency and pin configuration

    #34 20267251
    btsimonh
    Level 11  
    Posts: 66
    Help: 1
    Rate: 14
    I just checked mine (whilst checking NEC-0x0-0x1a-0x1) and it pulses nicely.
    I'm not on the exact same device, min is T LED strip, IRSend drive red leds, so can't confirm IR is perfect, but flashes look good.
    P.S. just pur a PR in so you can send like [IRsend NEC-0-1a] ,[IRsend NEC-0-1a-2], [IRsend NEC 0 1a], [IRsend NEC 0 1a 3],
    and implemented repeats (currently no repeats on .123 firmware.

    Are you sure you have the right pin?

    11 hz is odd... not even 38khz carrier from PWM.
    You rebooted after config?

    Added after 7 [minutes]:

    Confirmed on my N IRblaster to output IR, and work (not necessarily well!!!!) with my Roku box - command was
    IRSend NEC-0xC2EA-0x19-0
    For 'up'. Roku receives 1/3 - so not good.
    Any help appreciated (maybe we change duty cycle of PWM? So when you have the T output running, looking at the waveform would be good... to confirm carrier freq is OK, and examine framing).
    br,
    Simon

    Added after 13 [minutes]:

    started an issue here:
    https://github.com/openshwprojects/OpenBK7231T_App/issues/411
  • #35 20267299
    omelchuk890
    Level 11  
    Posts: 70
    Rate: 10
    Any pin, if assigned as IRSend, outputs a meander after reboot.
    What channel number should be assigned to the IRSend output?
  • #36 20267343
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14805
    Help: 659
    Rate: 12972
    Channel numbers are currently ignored for IR pins. It doesn't matter which channel number you set.
    Helpful post? Buy me a coffee.

  • IR transmit leaves meander unchanged on this module

    #37 20267424
    omelchuk890
    Level 11  
    Posts: 70
    Rate: 10
    Debug:API:POST to api/cmnd
    Debug:CMD:cmd [loglevel 0]
    Debug:CMD:loglevel set 6
    Debug:API:POST to api/cmnd
    Debug:CMD:cmd [IRSend NEC-0x1-0x18-1]
    Info:IR:IR send NEC-0x1-0x18-1 protocol 7 addr 0x1 cmd 0x18 repeats 0
    Debug:API:POST to api/cmnd
    Debug:CMD:cmd [IRSend NEC-0x1-0x18-1]
    Info:IR:IR send NEC-0x1-0x18-1 protocol 7 addr 0x1 cmd 0x18 repeats 0
    Debug:API:POST to api/cmnd
    Debug:CMD:cmd [stopDriver IR]
    Info:NTP:Drv IR has been stopped.
    Debug:API:POST to api/cmnd
    Debug:CMD:cmd [stopDriver IR]
    Info:NTP:Drv IR is not running.
    Debug:API:POST to api/cmnd
    Debug:CMD:cmd [IRSend NEC-0x1-0x18-1]
    Info:IR:IR send NEC-0x1-0x18-1 protocol 7 addr 0x1 cmd 0x18 repeats 0
    Debug:API:POST to api/cmnd
    Debug:CMD:cmd [startDriver IR]
    Info:IR:Log from extern C CPP
    Info:IR:DRV_IR_Init: recv pin -1
    Error:CMD:command with name IRSend already exists!
    Info:NTP:Started IR.
    Debug:API:POST to api/cmnd
    Debug:CMD:cmd [IRSend NEC-0x1-0x18-1]
    Info:IR:IR send NEC-0x1-0x18-1 protocol 7 addr 0x1 cmd 0x18 repeats 0
    Debug:API:POST to api/cmnd
    Debug:CMD:cmd [IRSend NEC-0x1-0x18-1]
    Info:IR:IR send NEC-0x1-0x18-1 protocol 7 addr 0x1 cmd 0x18 repeats 0

    On this module, the meander is unchanged when the IR transmission is activated.
    I'll try it on another module later.

    This is 100% this output - if I bind the button and designate it as a relay - switches like a relay.

    BK7231N - Universal IR Remote Contorl BK7231N - Universal IR Remote Contorl

  • Check BK7231N PWM and IRRecv configuration

    #38 20267435
    btsimonh
    Level 11  
    Posts: 66
    Help: 1
    Rate: 14
    Hmm... picture of the exact BK chip? And start of bootlog (i.e. log BEFORE our boot, then up to ~10s with IR driver enabled at startup?)
    Maybe there is a version without PWM....
    ohhh... you don't have PWM outputs enabled? If so try without. Surely each PWM pin is linked to an exact PWM channel number - so there cannot be a conflict.

    Does the device have IRRecv - if so does it work? (would prove 20khz timer was running, required for TX.).
    Hmm2... maybe TX does not work unless Rx is enabled!!! Ensure you have an RX pin.... did not think of that, and can't check right now....
  • #39 20267448
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14805
    Help: 659
    Rate: 12972
    @omelchuk890 I see you have your MAC cleared. Most likely your TLV header is also lost. You can consider going to Web App, Flash tab, and using new "Restore RF Partition" button. It is not tested much but should work. Do only if you have (in worst case) flashing wires handy. But I think it should work.
    Helpful post? Buy me a coffee.
  • #40 20267615
    omelchuk890
    Level 11  
    Posts: 70
    Rate: 10
    @btsimonh @p.kaczmarek2
    I had the reception input disabled, it wasn't there at all. The reason is the reception of interference in the form of the RC5 protocol.
    After the appointment of Irrecv, everything worked.

    How can I disable the RC5 protocol reception?
    Look at my posts in this topic - everything is shown there.
  • #41 20267640
    btsimonh
    Level 11  
    Posts: 66
    Help: 1
    Rate: 14
    good news. Have added to the issue in github.

    Please let us know how successful your TX is? Mine is currently not reliable.
    And if you can help with signal anlaysis (freq, framing checking).
  • ADVERTISEMENT
  • #42 20267700
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14805
    Help: 659
    Rate: 12972
    @btsimonh how many protocols do we have?
    What about dedicating a single 32 bit integer from config memory for a 'IR filter', each bit can be 1 or 0, and each bit would correspond to given IR protocol (with 32 protos limit, is it enough?).
    That way users would be able to filter the unwanted protocols from receiving.
    Helpful post? Buy me a coffee.
  • #43 20267810
    btsimonh
    Level 11  
    Posts: 66
    Help: 1
    Rate: 14
    there are certainly < 32
    we can add commands IRRxDisable <name>?
    then they can go in autoexec... or startup line.

  • Vue GUI with bit flags for IR mapping

    #44 20267868
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14805
    Help: 659
    Rate: 12972
    I think I'd prefer GUI. I've been also thinking how to make it as lightweight as possible, maybe we could add a GUI on VUE app and in binary just place the rest interface.
    If there are < 32, then we can just dedicate a single integer to all the flags.
    But certainly we need a page with checkboxes, maybe on that VUE, it's way easier than commands.

    We can assume that the IR Protocol <-> Index mapping won't change, right? If so, then bit flags are a way to go.
    Helpful post? Buy me a coffee.

  • IR receiver input pulled up to supply to avoid echo

    #45 20267896
    omelchuk890
    Level 11  
    Posts: 70
    Rate: 10
    @btsimonh @p.kaczmarek2
    instead of the real input on which the IR receiver has installed the LED, it is pulled up to the power supply. in this case, there is no "echo" from the transmitter.
    the transfer works only from the command line, there is no way through mqtt, I tried the topic from post 27 - cmnd/ir_blaster/IRSend
    NEC protocol
    BK7231N - Universal IR Remote Contorl
    BK7231N - Universal IR Remote Contorl
    BK7231N - Universal IR Remote Contorl
  • #46 20267928
    btsimonh
    Level 11  
    Posts: 66
    Help: 1
    Rate: 14
    omelchuk890 wrote:
    there is no way through mqtt

    is there no way to send commands via MQTT? - that is something we should resolve....
    cmnd/ir_blaster/IRSend = no way, surely not impemented!!!

    using a false pin is an interim solution. One question is, why are you getting IR on real input?
  • ADVERTISEMENT
  • #47 20267945
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14805
    Help: 659
    Rate: 12972
    Every possible command that is supported by console, should be also supported by MQTT. Is there some kind of syntax issue with using IR command that way?
    Helpful post? Buy me a coffee.
  • #48 20267961
    omelchuk890
    Level 11  
    Posts: 70
    Rate: 10
    @btsimonh
    If I connect a receiver located directly on the board, it works, but there is a lot of false data with the RC5 code.
    I don't have an rc5 remote control at all.
    When sending from the command line with the receiver turned on, I get an "echo"
    BK7231N - Universal IR Remote Contorl
  • #49 20268126
    btsimonh
    Level 11  
    Posts: 66
    Help: 1
    Rate: 14
    yes, you will get echo. it does not currently disable RX during TX.....
    I have PR in to allow TX with RX not configured.... solves original issue...

  • Protocol filtering needed for spurious RC5 decode

    #50 20268139
    omelchuk890
    Level 11  
    Posts: 70
    Rate: 10
    I get this garbage, it is present at the input from any receiver, I tried to connect others.
    That's why protocol filtering matters to me.

    Spoiler:
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR: Raw-Data=0x0
    Info:IR: 0 bits
    Info:IR: MSB first
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR: Raw-Data=0x0
    Info:IR: 0 bits
    Info:IR: MSB first
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR: Raw-Data=0x0
    Info:IR: 0 bits
    Info:IR: MSB first
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR: Raw-Data=0x0
    Info:IR: 0 bits
    Info:IR: MSB first
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR:Repeat
    Info:IR: Gap 18950us
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR: Raw-Data=0x0
    Info:IR: 0 bits
    Info:IR: MSB first
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR:Repeat
    Info:IR: Gap 62850us
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR:Repeat
    Info:IR: Gap 33050us
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR: Raw-Data=0x0
    Info:IR: 0 bits
    Info:IR: MSB first
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR: Raw-Data=0x0
    Info:IR: 0 bits
    Info:IR: MSB first
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR:Repeat
    Info:IR: Gap 8150us
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR:Repeat
    Info:IR: Gap 16800us
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR:Repeat
    Info:IR: Gap 9000us
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR:Repeat
    Info:IR: Gap 11900us
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR: Raw-Data=0x0
    Info:IR: 0 bits
    Info:IR: MSB first
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR: Raw-Data=0x0
    Info:IR: 0 bits
    Info:IR: MSB first
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR: Raw-Data=0x0
    Info:IR: 0 bits
    Info:IR: MSB first
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR: Raw-Data=0x0
    Info:IR: 0 bits
    Info:IR: MSB first
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040
    Info:IR:IR decode returned true, protocol 16
    Info:IR:Address=0x0
    Info:IR: Command=0x40
    Info:IR: Raw-Data=0x0
    Info:IR: 0 bits
    Info:IR: MSB first
    Info:IR:IR decode returned true, protocol RC5 (16)
    Info:IR:IR fire event took 0ms
    Info:IR:Received cmd 00000040

    Although it is important for me personally to read the remote control codes once, and then send them through node-red, so then I'll just choose the input for the receiver that is not used.
  • #51 20268207
    btsimonh
    Level 11  
    Posts: 66
    Help: 1
    Rate: 14
    does TX work for you with your device?
  • #52 20268212
    omelchuk890
    Level 11  
    Posts: 70
    Rate: 10
    Yes, only command line.
    how to do multiple repetitions of a command by changing the last argument does not help

  • Invert PWM output with IREnable invert 1

    #53 20268961
    btsimonh
    Level 11  
    Posts: 66
    Help: 1
    Rate: 14
    omelchuk890 wrote:
    is it possible to add an output to the transmitter in an inverted form


    in lastest PR here
    https://github.com/openshwprojects/OpenBK7231T_App/pull/413
    we now have everything you have requested.

    try "IREnable RC5 0" to disable a protocol.
    try IREnable RXTX 1 if you WANT to receive at the same time as TX - by default RX is suppressed whilst sending.
    try IREnable invert 1 to effectively invert the PWM output. (please check on your 'scope and report).

    br,

    Simon

  • Smaller BK7231N module found for testing

    #54 20268999
    omelchuk890
    Level 11  
    Posts: 70
    Rate: 10
    @btsimonh
    I will definitely conduct tests, but on Monday - my wife demands to arrange a shopping trip for her. who invented husbands to go shopping with their wives?
    I still have one - I found it in a box for experiments today. I still have one - I found it in a box for experiments today. The size compared to the current module is significantly smaller.
    BK7231N - Universal IR Remote Contorl
    BK7231N - Universal IR Remote Contorl
    BK7231N - Universal IR Remote Contorl

  • Scope measurements from latest IR send build

    #55 20269074
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14805
    Help: 659
    Rate: 12972
    @omelchuk890 if you have a new device, please submit a separate teardown and include the photos of casing, box and screenshots from the site where you bought it, also a pinout data, if possible. Which pin is IR input, etc, etc.

    @btsimonh here are scope measurements from the latest release build with IR Send:
    BK7231N - Universal IR Remote Contorl BK7231N - Universal IR Remote Contorl BK7231N - Universal IR Remote Contorl BK7231N - Universal IR Remote Contorl BK7231N - Universal IR Remote Contorl BK7231N - Universal IR Remote Contorl
    Helpful post? Buy me a coffee.
  • #56 20270746
    omelchuk890
    Level 11  
    Posts: 70
    Rate: 10
    Can you tell me if there is currently a way to send a command to the module to send an IR command from node-red? Maybe via http post or something else while mqtt is not working.
    Otherwise, for now it's just a trinket...
  • #57 20270850
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14805
    Help: 659
    Rate: 12972
    Have you checked HTTP interface?
    Code: text Expand Select all Copy to clipboard
    
http://192.168.0.100/cm?cmnd=led_enableAll%201
    Helpful post? Buy me a coffee.
  • #58 20270945
    omelchuk890
    Level 11  
    Posts: 70
    Rate: 10
    @p.kaczmarek2
    Sorry, I'm not an expert in web and http.
    It works from the browser bar!
    I will figure out how to send from Node-Red.
    Code: text Expand Select all Copy to clipboard
    http://192.168.21.100/cm?cmnd=IRSend NEC-0x1-0x10-1
  • #59 20271001
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14805
    Help: 659
    Rate: 12972
    That strange %20 is a special way of writing a space character for HTML links. In our App, those characters are processed by urldecode2_safe function.
    Helpful post? Buy me a coffee.
  • #60 20271156
    omelchuk890
    Level 11  
    Posts: 70
    Rate: 10
    Everything worked out - there was a problem with the network, with routes. Raspberry and the module are in different networks, then I'll figure it out, moved it to connected networks - everything is fine.

    BK7231N - Universal IR Remote Contorl
    BK7231N - Universal IR Remote Contorl
Reply Cool? Ranking DIY | New topic
Notify about new articles
Listen:
Report a violation of the law

Topic summary

LABEL_AI_GENERATED
Discussion about flashing and reverse-engineering BK7231N-based universal IR blasters, mainly Tuya S06/S08 and related CBU/CB3S boards. The thread covers board teardown photos, pin mappings for IRRecv, IRSend, status LED, UART flashing access, and safe reboot behavior after changing pin configuration. OpenBeken/OpenBK7231N firmware development adds IR receive and transmit support, MQTT and HTTP control, JSON/raw publish formats, protocol filtering, RX/TX coexistence, and inverted PWM output. Users report issues such as unknown IR codes for some air-conditioner remotes, unreliable transmission on some boards, echo during TX when RX is enabled, and the need to restart after pin changes. Later posts discuss Home Assistant and Node-RED integration, correct MQTT topic syntax, and expanding codec support for Samsung, Panasonic, Sony, RC5, NEC, Mitsubishi AC, and other IR protocols.
AI summary based on the discussion. May contain errors.
Today's popular

FAQ LABEL_AI_GENERATED

TL;DR: Firmware v1.17.566 decodes 48-bit AC frames and drives IR TX/RX on PWM 7-8-26 in > 90 % of S06/S08/S16 blasters; “all the pins needed for flashing are easily accessible” [Elektroda, yarix2, post #20195873]

Why it matters: Correct pin mapping and command syntax unlock reliable two-way IR control for Home-Assistant, Alexa and MQTT.

Quick Facts

• Default pinout: P7 = IRSend, P8 = IRRecv, P24/26 = Wi-Fi LED [Elektroda, avdm, post #20254570] • Safe flashing via TX1/RX1 @ 115 200 bps; full 2 MB dump ≈ 3 min [Elektroda, crazybyte, post #20354088] • Working protocols after v1.17.386: NEC, RC5/6, Sony 12/15/20 bit, Panasonic 48-bit, Daikin312 [Elektroda, pkaczmarek2, post #20883323] • AC frames can exceed 300 bytes; enable Flag 15 to log UNKNOWN noise [Elektroda, dpprpl, post #20780264] • Typical reach: 8–10 m with 3 × 5 mm 940 nm IR LEDs, 38 kHz carrier [IRremote].

How do I wire and flash the S06/S08/S16 IR blaster?

  1. Solder wires to 3 V3, GND, TX1, RX1 and CEN pads.
  2. Hold CEN low, power the board, then run hid_download_py or OpenBK GUI Flash Tool with the BK7231N_QIO image [Elektroda, crazybyte, post #20354088]
  3. After “Flash success”, release CEN and reboot. Total time ≈ 60 s.

Why does my Wi-Fi LED stay off?

Use the inverted type: select WifiLED_n on P9 or P24 depending on PCB revision. Some S08 Pro boards route LED to PWM3 (P9), not PWM2 [Elektroda, brianroy86, post #20862526]

IRSend runs but LEDs never flash—what’s wrong?

Check: a) protocol string must start with the name only, e.g. “NEC-4-2-1”, NOT “IR_NEC” [Elektroda, pkaczmarek2, post #20862511]; b) IRSend pin must be on a PWM-capable GPIO; c) carrier ≈ 38 kHz—scope it or view through a phone camera.

How do I read IR codes quickly?

Enable Flag 15 to log unknown packets, open WebApp→Log, point remote, read lines like “IR_NEC 0x4 0x2 0” [Elektroda, dpprpl, post #20780264]

Sony commands send only the start bit—fix?

Update to ≥ v1.17.566. Firmware now auto-fills missing bit length; override with “Sony-ADDR-CMD-REP-NUMBITS” if needed [Elektroda, pkaczmarek2, post #20883323]

AC remote shows IR_UNKNOWN—can I still control it?

Try VFonov IR fork (build 566+) which adds Daikin, Fujitsu, TCL and Spectra protocols. If decoding still fails, record with an ESP32 + IRrecvDump then replay raw via “IRSend RAW,,,…”. Edge case: long AC frames may exceed 1 KB buffer; split into two parts.

How to convert Celsius*10 to real temperature?

Set channel type temperature_div10 in autoexec: “setChannelType 1 temperature_div10”. HA will convert to °F automatically [Elektroda, p.kaczmarek2, post #20840661]
AI summary based on the discussion. May contain errors.
ADVERTISEMENT