Please include the following information, in order for us to help you as effectively as possible.
What product do you wish to discuss? RAK4631, RAK3372, RAK11200, RAK11310, RAK11722?
RAK3172
What firmware are you using? (RUI3 or Arduino BSP or other IDE (e.g. STM32CubeIDE)?
Arduino IDE
What firmware version? Can it be obtained with AT+VER=?
AT+VER=RUI_4.2.0_RAK3172-E.
Computer OS? (MacOS, Linux, Windows)
Windows
What Computer OS version?
22H2
How often does the problem happen?
How can we replicate the problem?
Provide source code if custom firmware is used or link to example if RAKwireless example code is used.
We are going to deploy a system that uses 5–10 RAK3172 devices. The device that powers on first will act as the master (Tx), while the others will operate as slaves (Rx). If the master device stops functioning, the next device—based on the timestamp—will automatically assume the role of master. This architecture will be implemented to monitor various parameters, and we want to ensure that no other LoRa device can connect to our network if it is using our designated frequency.
We have successfully developed a solution for 1-to-1 communication; however, the message (string) length is too small. How can we upgrade it? as of api.lora.psend(sizeof(payload), payload); this command in code.
And is there any network stack available for the RAK3172 so we can update it as per our requirement
The payload size of LoRa is limited to 255 bytes, you cannot extend it.
It is not advisable to send “text” as payload. If you are measuring sensor values, send the values only in a defined format.
An example could be to use LPP format. There is a library for it called Cayenne LPP.
Ohhh! sorry previous byte length i added by mistakenly, but the logs are 25 bytes.
but still why it is not receiving the all the payload data?
and the response is coming only for the 2 -3 mins later it stops the receiving the data.
So there must be something else in your “real” code that is not in the examples you shared. They would not be able to communicate anyway with the different P2P settings.
For now, I have removed the board to take steady screenshots and to make any further changes I need to, as it is still not sending more than a 12-byte payload. There seems to be a significant difference between your response and mine, and I’m not sure why.
Thank you for confirming your code’s functionality. It’s helpful to know it works in your testing. However, I’m using RUI3 version 4.2.0, and there seems to be a discrepancy as I’m still facing the problem.
Therefore, I’ll be adapting the code to address the issue within my specific environment. I appreciate your assistance.