logo elektroda
logo elektroda
X
logo elektroda

[Youtube] How to make BK7231 development board - NodeMCU conversion - soldering guide, hot air, SMD

p.kaczmarek2 6300 37
ADVERTISEMENT
  • #31 21361708
    p.kaczmarek2
    Moderator Smart Home
    Here are mine:
    Various prototype boards and electronic modules on a wooden surface. A hand holding an electronic device with an LCD display module.
    I am thinking about using them with Wemos D1 converted to BK7231
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #32 21361714
    divadiow
    Level 35  
    ah i see. shields are hats, extensions, add-ons. of course :)
  • ADVERTISEMENT
  • #33 21362685
    p.kaczmarek2
    Moderator Smart Home
    Those markings are so misleading:
    Two NodeMCU modules with pin labels visible on a dark background.
    I wonder how hard would it be to make a custom build (or a skin, or a script?) of OBK that will have NodeMCU-style pin names next to classic pin names...
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #34 21362718
    divadiow
    Level 35  
    interesting idea. Almost daily I'm referring to some mapping image on here or one I've made for various modules/ESP adaptors. Even some kind of basic ASCII selection to map choice1<->choice2. dunno
  • #35 21362780
    p.kaczmarek2
    Moderator Smart Home
    Ok, so here is initial draft:
    https://openbekeniot.github.io/webapp/test1.html
    Open link and hover mouse cursor over pin name to higlight it.
    That's how it looks like:
    NodeMCU board diagram with highlighted GPIO pins.
    Next step would be to integrate it into pins chooser and GPIO doctor, I guess?
    Who knows html and js? @max4elektroda ? But maybe I will try to do it first myself. Keep the canvas and stuff as separate JS module on web app. Fetch it from web on pins page load. Allow user to select his board type, so NodeMCU, raw CB3S, etc, etc.

    Added after 3 [hours] 14 [minutes]:

    I added drawing handles:
    NodeMCU board pin diagram with highlighted pins.

    Added after 49 [minutes]:

    something like this, maybe?


    Helpful post? Buy me a coffee.
  • #36 21363276
    max4elektroda
    Level 20  
    That's really a very useful feature to easily identify the pins. Thanks!
    p.kaczmarek2 wrote:
    Who knows html and js? @max4elektroda ? But maybe I will try to do it first myself.

    You don't even allow some time to read before you present a nice realization ;-)
  • ADVERTISEMENT
  • #37 21363284
    p.kaczmarek2
    Moderator Smart Home
    I think I may get initial version working soon, but we will need to create our own "boards.json":
    ESP32 board pin diagram with a dropdown list for board selection.
    And there is also question where would we store board information, but since it's not a critical piece of information, I may just decid to store it in Cookie so it's a developer only feature remembered by current browser? Idk.... or add a command for that
    Helpful post? Buy me a coffee.
  • #38 21364328
    p.kaczmarek2
    Moderator Smart Home
    Recently I've did a very simple classic CB2S to NiceMCU transplant: CB2S/WB2S cheap dev board made from NiceMCU_WB3S_V1 (replace WB3S with WB2S/etc) . It might be good idea for anyone looking for cheap CB2S/WB2S dev boards, as NiceMCU is very cheap (as low as 1$ for new clients) and with my approach, the pin indexes on silkscreen are not mixed after conversion.
    Helpful post? Buy me a coffee.

Topic summary

The discussion centers on converting a cheap NodeMCU ESP8266 development board into a BK7231 development board by transplanting a BK7231 WiFi module (CB3S or WB3S) onto the NodeMCU PCB after desoldering the original ESP12 module using a hot air station. This method offers a cost-effective and flexible alternative to buying dedicated BK7231 dev boards, especially for users who have BK7231 modules salvaged from IoT devices. Key tools include a hot air station and basic soldering equipment, with some users exploring alternative heating methods like dual soldering irons due to lack of a heat gun. The transplant process involves careful desoldering, pad cleanup, and pin mapping verification, with some discussion on correcting pinout diagrams for I2C lines (S3, SK, SC) to ensure sensor compatibility (e.g., BMP280, AHT20). UART logging configuration is also addressed, recommending UART1 for logging due to CH340 USB interface connection. Additional topics include testing of TM1638 displays, power cycling via CEN or reset buttons, and the use of ShiftRegister for driving more LEDs. The community also explores software tools for pin mapping visualization and integration with OpenBK firmware. Alternative inexpensive boards without pre-soldered ESP modules are noted as options to avoid destructive desoldering. The conversation extends to related modules and development boards such as BK7238 NiceMCU, WEMOS W1F1 D1, and various BK series modules (CB2S, WB2S, CB3L, etc.), with interest in Arduino shield compatibility and custom firmware adaptations.
Summary generated by the language model.
ADVERTISEMENT