Currently I am using a BC66-NA module (revision BC66NADAR01A01_CS) connected to a serial port to a processor. I send AT commands from this processor to send UDP messages. All configuration seems to be ok, but after sending the message with an AT+SENDEX command the response “SEND OK” is not send. In fact no response at all is given anymore. The BC66 module does also not respond to “AT” commands after that. Only after triggering the reset pin the module will start responding and sends “SEND OK” and “OK” for all AT commands given after the SENDEX command. Although a “SEND OK” message is send after triggering the reset pin the message is not send.
Below the AT commands used (Lines starting with “Debug” shows the AT command, lines starting with “Got” shows the reponse of the BC66)
Debug AT
Got:
2 288212 Debug AT
Got: AT
OK
+CPIN: READY
AT
OK
AT
OK
AT
OK
Debug ATE0
Got: ATE0
OK
Debug AT+CEREG=1
Got: OK
Debug AT+QSCLK=0
Got: OK
Debug AT+CFUN=1
Got: OK
Debug AT+QBAND=1,8
Got: OK
Debug AT+QICFG="dataformat",0,0
Got: OK
Debug AT+QICFG=“showlength”,1
Got: OK
Debug AT+QICFG=“viewmode”,1
Got: OK
Debug AT+QCGDEFCONT="IP","cdp.iot.t-mobile.nl"
Got: OK
Debug AT+CGATT?
Got: +CGATT: 0
OK
Got: +CEREG: 5
Got: +IP: 10.128.1.30
Debug AT+CGATT?
Got: +CGATT: 1
OK
Debug AT+CSQ
Got: +CSQ: 20,0
OK
Debug AT+CGMR
Got: Revision: BC66NADAR01A01_CS
OK
Debug AT+CGATT?
Got: +CGATT: 1
OK
Debug AT+QICLOSE=0
Got: OK
Got: CLOSE OK
Debug AT+QIOPEN=1,0,"UDP","172.27.xxx.xxx",15481,9000,1,0
Got: OK
Got: +QIOPEN: 0,0
Debug AT+QISENDEX=0,14,"a20000012447310bae0ef10003a2"
Now we expect a response like “SEND OK” or “ERROR” but this is not send, also not after long time waiting (60 seconds).
Any ideas what the problem might be?
Kind regards,
Bart.