AT+SENB behaviour not compliant with specification

[Luca Bertoldo]

I’m working with:
MultiTech xDot
Firmware : 3.1.0-mbed161
Library : 3.1.0-mbed161
MTS-Lora : 3.1.0

I’m referring the AT Command Reference Guide – Part Number: S000643, Version 3.1

Referring to AT+SENDB command I’m expecting to send a packet (binary packet) and to receive the “OK” string. Nothing else is described inside the documentation.

I report below a coupe of example of what I can observe using this command:
Example A

at+sendb=01010100000000

OK

Example B

at+sendb=010102000205fa
550601025bb49826d618

OK

In the Example B I receive a packet before the “OK” string… so I have not expected data before AT+SENB confirmation.
This is a packet that I receive very closed after transmission… but, in any case, I’m not expecting to see it within AT+SENB command execution.

I’m expecting to close the SEND command with its confirmation and then to check receive the new packet using AT+RECV command instead.

What’s wrong?

Thanks,
Luca

[Jason Reiss]

Doc of AT+SENDB on page 79 shows possible data received from the network to be printed before the OK following an AT+SENDB command.

http://www.multitech.com/documents/publications/manuals/s000643.pdf

You can disable waiting for rx windows before AT+SENDx commands return if ACKs are not enabled.
AT+TXW=0

[Luca Bertoldo]

Thanks for clarification.

Luca

[Author]

Posts