RUI-3 Mesh Custom Data

[Shylendran7801]

Hii, the mesh logic works but if i need to send custom data. What should I do? I tried changing the data from timed_loop() function. But it gives the same output as before.

[beegee-tokyo]

Did you change the data_buffer in lines 226 to 230

convert_value.l_value = msg_cnt;
memcpy(&data_buffer[0], convert_value.b_values, 8);
memcpy(&data_buffer[8], convert_value.b_values, 8);
convert_value.l_value = g_this_device_addr;
memcpy(&data_buffer[16], convert_value.b_values, 8);

to something like

for (int idx = 0; idx < 24; idx++)
{
	databuffer[idx] = idx;
}

[Shylendran7801]

Yeah i changed it, i replaced it with ->
sprintf(data_buffer, "Hello from %08lX", g_this_device_addr);
Serial.printf("Sending: %s\n", data_buffer);

[beegee-tokyo]

Works for me. I fill the data buffer with numbers and the received payload shows the numbers.

Keep in mind, what you see in +EVT:RXP2P: is not only the payload, but as well the sender node address and the receiver node address.
In the screenshot below, RED is the mesh addressing, BLUE is the real payload.

[Shylendran7801]

Is there any other configuration that i need to change? I tried it but its not working.

[Shylendran7801]

I tried your logic and i get this output. I am not sure. By the way whats the decoder. Is it Hex to ASCII or Base64 or any other?

[Shylendran7801]

Can you share your libraries and code as a zip file, so i could analyse it.

[beegee-tokyo]

@Shylendran7801

I never tested the Mesh app with only two nodes (makes not really sense, that is just LoRa P2P).
Found some issues and fixed them
Updated example code is available now in the repo.
Added some info to the README for the packet structure.

There is no library. It is all in this example code.

Communication with two nodes with original payload:

Using your custom message:

[Shylendran7801]

I initally had 3 to 4 nodes. But the data does not seem to be relevant as i gave in my program so i just wanted to send data between two nodes for testing.

[Shylendran7801]

I even updated as per the latest repo. Its the same. I get this same hex every time -> 4C6F5204000000007BF012FE44F012FE00AA5500FFAA and with decoding it i got this -> LoR�{ð�þDð�þªUÿª .
I only removed oled scripts, as i dont need it and updated the frequency, coding rate and transmit power.

[beegee-tokyo]

Just added one missing information in the README.

The app by itself does not send data automatically. The RX/TX messages you see are the Mesh Map that is frequently interchanged between the nodes.

The example application does not send data automatically unless it is activated with an AT command.
ATC+SENDINT=30 sets the interval to send data to random nodes in the Mesh network every 30 seconds.

[Shylendran7801]

That worked! thanks for your valuable time.

[Shylendran7801]

Hi, I have worked using the mesh, considering three nodes are working. Node 1 is the bridge and node 2 is in range with node 1. Node 3 is out of range with node 1 but is in range with node 2. But the message isn't hopping from node 3 -> node 2 -> node 1. I assigned the bridge (master) for every nodes but i only get data from node 2. Any suggestions would be helpful. Thanks, Shylendran R

…

---------- Forwarded message --------- From: Bernd Giesecke ***@***.***> Date: Wed, 14 May, 2025, 4:37 pm Subject: Re: [RAKWireless/RUI3-Best-Practice] RUI-3 Mesh Custom Data (Discussion #7) To: RAKWireless/RUI3-Best-Practice ***@***.***> Cc: Shylendran7801 ***@***.***>, Mention < ***@***.***> Just added one missing information in the README. The app by itself does not send data automatically. The RX/TX messages you see are the Mesh Map that is frequently interchanged between the nodes. The example application does not send data automatically unless it is activated with an AT command. ATC+SENDINT=30 sets the interval to send data to random nodes in the Mesh network every 30 seconds. <https://github.com/RAKWireless/RUI3-Best-Practice/blob/main/RUI3-Mesh/README.md#%EF%B8%8F-info> — Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQU3QAJV5Q6NTQMXFNH2B7326MPXPAVCNFSM6AAAAAB5CLXJQ2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMJUGM2TSMI> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[beegee-tokyo]

How do you setup the configuration?
For testing of such a configuration I use enable the test with isolated nodes in mesh.cpp line 21 with the BROKEN_NET define.
Then in mesh.cpp line 397 I define the mesh structure

// To simulate a mesh where some nodes are out of range,
// replace the 3 node addresses below with real node addresses
// Requires at least 3 nodes in the net
// NODE 1 can only connect to NODE 3
// NODE 2 can only connect to NODE 3

#define BROKEN_NODE_1 0xFE0537A1
#define BROKEN_NODE_2 0xFE0A710C
#define BROKEN_NODE_3 0xFE0AF1B9

Tested with 3 nodes and master with this configuration

MASTER (FE0537A1) <====> NODE 1 (FE0AF1B9) <=====> NODE2 (FE0AF1B9)

Master receives messages from both Node 1 (bridge) and Node 2

---

Then I set Node 1 as master and bridge

NODE3 (FE0537A1) <====> MASTER (FE0AF1B9) <=====> NODE2 (FE0AF1B9)

Master/Bridge receives messages from both Node 3 and Node 2

[Shylendran7801]

Yeah i did the same thing. MASTER (FE12FF03) <====> NODE 1 (FE12F044) ===X=== NODE2 (FE12F07B). I am receiving only the data from FE12F044. I have set the master as FE12FF03 on Node 1 (FE12F044) as well as Node 2 (FE12F07B). In node 1 and node 2, i have set the send_interval as 30 seconds. The below image is the master getting data from node 1.

[Shylendran7801]

It shows in the mesh map. Tried different ways but unable to get the third far away node to send the data.

[Shylendran7801]

Is destination always zero?

[beegee-tokyo]

Once you have assigned a master node, the other nodes will only send packets to that master node. They will not send broadcast messages anymore.

So when

MASTER (FE0537A1) <====> NODE 1 (FE0AF1B9) <=====> NODE2 (FE0AF1B9)

Node 1 will only send to Master and never to Node 2
Node 2 will only send to Master and never to Node 1
Master will select a random node and send a packet to it.

Destination is 0 if the packet is sent as broadcast.

[Shylendran7801]

The master receives data, if Node 2 is in range I get the data's perfectly. However, in my case, I didn't receive data from Node 2. When I checked the log from Node 1, I saw packets being received from Node 2 (+EVT:RXP2P), but it doesn't forward it to the master. I thought the problem was in the forwarder/bridge (Node 1) and I am not sure though.