logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda
3D printer for home or business?
3D printer for home or business? Here are the perfect 3D printers to start with »
ADVERTISEMENT

BK7231N Thermostat (RTK2409 , XKX , RT-V4-1.OPROD 200100163 )

leon22heart 366 9
ADVERTISEMENT
Report a violation of the law
Reply | New topic
  • #1 21861369
    leon22heart
    Level 4  
    Hello again . Gotten in the past a tuya BK7231N based Thermostat . So now i attempted to flash the the openbk firmware . Flashed the chip successfully but i cant see logs of the TUyaMCU driver . Below i attach my autoexec bat . Tried both the 9600 and 115200 baud rate . I recall seeing in the past the picture in the board in one post , but i cant seem to find it again .


    Red PCB inside a black casing with chips, connectors, and a white QR-code label.

    Code: text Expand Select all Copy to clipboard
    startDriver TuyaMCU

# Set the baud rate (TuyaMCU standard is 9600)
tuyaMcu_setBaudRate 9600

# Map DPIDs to Channels
# DPID 1 & 2 are usually the two sockets
setChannelType 1 toggle
linkTuyaMCUOutputToChannel 1 bool 1

setChannelType 2 toggle
linkTuyaMCUOutputToChannel 2 bool 2

# Power Monitoring (Common DPIDs for this model)
# Voltage (101), Current (102), Power (103)
setChannelType 3 Voltage_div10
linkTuyaMCUOutputToChannel 101 val 3

setChannelType 4 Current_div1000
linkTuyaMCUOutputToChannel 102 val 4

setChannelType 5 Power
linkTuyaMCUOutputToChannel 103 val 5
    Attachments:
    • readResult_BK7231N_QIO_2026-12-3-19-34-02.bin (2 MB) You must be logged in to download this attachment.
  • ADVERTISEMENT
  • #3 21861380
    leon22heart
    Level 4  
    >>21861376 Thank you will check and post . Added firmware backup.
  • ADVERTISEMENT
  • #4 21861808
    divadiow
    Level 38  
    ah yes. this was that odd baud one - 38400. I wonder if @hard3d got a fully working device in the end
  • #5 21861824
    leon22heart
    Level 4  
    >>21861808 i dont think he didi. Retraced all his steps , desoldered resistors and bridged mccu rx and tx but never managed to get mcu logs. Either i didn't get something right either it never worked ?



    Red PCB with SMD components, QR code label, and thin wires soldered to test pads
  • Helpful post
    #6 21861826
    divadiow
    Level 38  
    hmm. maybe @hard3d will see these pings and come online to confirm/advise

    Added after 36 [minutes]:

    hmm. this might be a tough one. Looks to be an Rti-Tek device. string 
    Rti-Tek@2020
    can be seen in the decrypted app partition. I don't see evidence the protocol is known anywhere.

    Datasheet for the CA51F452L2 MCU attached.
    Attachments:
    • 20220615_5342925f1d9fc99540dbe7bed45fc4ee.pdf (2.71 MB) You must be logged in to download this attachment.
  • ADVERTISEMENT
  • ADVERTISEMENT
  • #8 21863072
    leon22heart
    Level 4  
    >>21861857 Sorry for the late reply , was off town for the weekend. From what you said is there a problem with the tuya firmware backup ? Or should i retrace the github comments and apply the autoexec.bat ?
  • #9 21863104
    divadiow
    Level 38  
    I don't think there's an issue with the backup. I have it flashed to a test device and I've been trying to emulate your flavour of TuyaMCU in Python. It seems to be a bit different to the usual protocol. Not sure what this means for OBK supporting this device at present though.

    It'd be interesting to know what you can find out.
  • #10 21863134
    leon22heart
    Level 4  
    >>21863104 Well frankly i don't care truly about the thermostat. It was just pure curiosity if the device could support the obk firmware . if it works its ok if not also okay. Will tinker and report back. Hope that removing the transistors has not affected the logs.
Reply | New topic
Report a violation of the law

Topic summary

✨ The discussion centers on flashing openbk firmware onto a BK7231N-based thermostat (models RTK2409, XKX, RT-V4-1.OPROD 200100163) originally running Tuya firmware. The user successfully flashed the chip but cannot retrieve logs from the TuyaMCU driver despite trying standard baud rates (9600 and 115200). Attempts to capture MCU logs involved desoldering resistors and bridging MCU RX and TX lines, but no MCU output was obtained. A suggested alternative baud rate of 38400 was mentioned, referencing a similar case. The device appears to be an Rti-Tek product, with the CA51F452L2 MCU identified from the decrypted app partition. However, the TuyaMCU protocol for this device is not confirmed to be supported or documented. Shared links include firmware backups, board images, and datasheets. The challenge remains in successfully interfacing with the TuyaMCU and obtaining meaningful logs for further development or debugging.
Generated by the language model.
Today's popular
ADVERTISEMENT