Hello,

generally in case that some negotiated system of messaging is defined with devices, it is expected that you send one message (command f.ex.) to device and wait for answer. Waiting for answer can be checked like some timeout defined to have some received data or not and then you can do what is expected, maybe send again or do other steps. Send more messages at time is not expected here due logical reason, after receive some data you don't know maybe to what send message that data are received. Again, all depends to protocol used, its requirements. Maybe nbetter describe what protocol exactly and what messages you want send, byte sequence or documentation snippet as screenshot to know that for sure.

Hello,

more problems I see in your screenshots.

1. you have ADHOC disabled at TRCV block what can bring receive data problems especially at different message lengts. In case of use ADHOC, LEN parameter can be 0.

2. I see your TCON DONE saved as false. I don't know what you do inside your code but it indicates simply disconnection and not connected previously.

3. in case of use CHAR data type be careful with correct use of special characters but you probably know that.

4. after send and receive, you can send another message but I don't see that mechanisms you do to handle this flow correctly.

5. I don't see at your SEND block next parameters (arrow down click pls) like LEN and then it is no clear how much data you send, for sure.

6. One tip for receive, you can try leave EN_R always ON after connection is established in this case. I also see from your code false. Really is hard to say what you do in your code, sry/