Hi community,
Im use RAK3172, with short frame, it send good.
This is frame in side sender: AT+PSEND=0c1e0201061aff004c02154c53434f41435c6a4000004451143443434343
This is frame in side recieve:
+EVT:RXP2P:-29:8:0C1E0201061AFF004C02154C53434F41435C0A4002005437143443432343
+EVT:RXP2P RECEIVE ERROR
The received string is different from the original string.
It always takes place at the end of the sequence:
6a4000004451143443434343
0A4002005437143443432343
What is the reason for this and how can I avoid it?
We have known issue that sometimes on P2P reception, the data has mismatch when encryption is enabled. This is fixed on v4.0.6 and currently on validation stage.
When the error occurred, is it permanent? You cannot get any correct P2P TX anymore?
Or the issue is erratic on behavior?
On your shared AT commands, you received an +EVT:RXP2P RECEIVE ERROR so it appears that something is wrong on that TX transmission or on the RX reception of the payload.
This is log of both side sender and reciever.
The number of frames is wrong about 70% and random.
There will be times when frames are correct in a row.
This is AT command, Itβs not perfect, but has basic functions that can be used in P2P mode:
Im solve it. Problem is wire A and B of RS485 have noise (maybe antenna RF), so it change one or more bit in frame, lead to not String HEX in mode ATcommand or another error, so frame send and recieve sometime error.
Fixed by change wire.