Questions about RAK4630 KR920 module — pinout, ESP32S3 connection, and USB Type-C

WisBlock
21

I understand what you mean. What I want to confirm is whether this LoRa Mesh topology example is intended for the RAK4630.

On the RAK4630, do things like node address assignment and confirming received packets all have to be implemented in code?

I know nodes need addresses—BLE Mesh does too. It’s essentially just a protocol channel. But in BLE Mesh the provisioner assigns node addresses proactively; I only need to implement the application-layer logic for acknowledging received data.

22

On WisDuo modules, there is no protocol implementation for LoRa P2P / LoRa Mesh.
It has to be done in the application code.

23

My customer is waiting for my product quote. I need to confirm that my understanding is correct.

24

OK I see.
Thanks for your help.

25

Hi
I’m working on the schematic now. I have a few questions.

  1. When updating firmware on the RAK4630 using USB+/- and powering via the VBAT pin, do we need to disconnect direct power to the SX and the nRF?

  2. The RAK4630 has two chips inside—an nRF and an SX. Do they have to be powered separately?

26
  1. No, you need both supplies. VBUS for the USB and VBat for the nRF52 and SX chip.
  2. What is your current plan for the power supply?
    By default, the supply is through VBat and 3.3V and this is powering both nRF and SX

For possible power supply options, check RAK4630 schematics Figure 3

The third option says LiMnO2 battery, but it is the same for Li-Ion battery. The third option is what we use with the RAK4630 in our WisBlock Modular System. RAK4631 schematics

27

ok
thanks for your help.