Hi,
I’ve noticed that the our module rarely misinterprets the commands sent to the modem.
This is the log from the modem sent to our application:
1148401 - +KSUP: 0
1197534 - AT
1197534 -
1197535 - OK
1197544 - AT+CREG?
1197545 -
1197546 - +CREG: 0,4
1197547 -
1197547 - OK
1197554 - AT+KCNXCFG=1,“GPRS”,“”
1197564 -
1197564 - OK
1197574 - AT+CGATT?
1197576 -
1197577 - +CGATT: 1
1197577 -
1197577 - OK
1197586 - AT+KUDPCFG=1,0,53439,0,“172.30.0.128”,8899
1197616 -
1197617 - +KUDPCFG: 1
1197618 -
1197618 - OK
1197625 -
1197626 - +KCNX_IND: 1,1,0
1199644 -
1199645 - +KUDP_IND: 1,1
1199648 - AT+KUDPSND=1,47
1199661 -
1199662 - CONNECT
1199681 -
1199681 - OK
1200110 -
1200111 - +CEREG: 5,“0007”,“0189F216”,7,“00000100”,“00111000”
1200526 -
1200527 - +KUDP_DATA: 1,131
1200535 - AT+KUDPRCV=1,131
1200546 -
1200547 - CONNECT
1200548 - k<,�d
1200549 - jihgfe+�����d8:!��!y–EOF–Pattern–
1200549 - OK
1200549 -
1200561 - +KUDP_RCV: “172.30.0.128”,34574
1200565 - AT+�UDPCLOSE=1
1200568 -
1200568 - ERROR
And this is the communication captured from our application to the modem:
AT
AT+CREG?
AT+KCNXCFG=1,“GPRS”,“”
AT+CGATT?
AT+KUDPCFG=1,0,53439,0,“172.30.0.128”,8899
AT+KUDPSND=1,47
k8:!▒▒!{▒"3D▒OF–Pattern–AT+KUDPRCV=1,131
AT+KUDPCLOSE=1
Has anybody else experienced this?
Best regards
Martin