Onenet Basic Communication Kit return to +cis error:50 problem solving

1. Scenario analysis, the main problem is that some operations return +cis ERROR:50

2. Look at the AT+MIPLOBSERVERSP in this directive is not return +cis error:50 error type, so should be in parsing this at command before the appearance, then why will appear, guess one, module into sleep, wake up after the first serial character is lost, But with their own board test, this probability is not high, the customer test almost 100% appear, guess two, is the external MCU into sleep after changing the RX level, so receive data more than a rising edge or falling edge, there is the time of the at+miplnotify appear, I don't see any difference between the following instructions for the time being.

3. There are 50 errors in the app_at.h there are three cases, I think it is necessary to further distinguish the three cases, so modified, one of the problems to note, if there is no this at command, then the reply is 50 error, I guess the following at_ret_not_ Numeric means that the AT command is not found, but it does not seem to mean the number. The 3rd of the following is a syntax error

    ,//     Incorrect parameters,       //Incorrect Parameters    ,    //Incorrect parameters

After the modification, test it, first of all the non-digital to see if it can be tested, the first is the character problem

[ -: +:44.372] Hair →◇at+cgsn=1- [ -: +:44.386] Collect ←+CGSN:865353030039314ok[ -: +:48.004] Hair →◇at+cgsn=a-[ -: +:48.016] Collect ← [ -: +:48.068] Collect ←+cis ERROR: -

Then the

[:58.380] →◇at+cgs2n=1 []: 58.393] Collect ←

Continue testing, so now guess, the previous error is probably the 53, syntax error

 [18 : 49 : 33.091 ] hair →◇at+miplop-[ 18 : 49 : 33.103   "collect ←  +cis ERROR: 53  [ 18 : 49 : 36.709 ] hair →◇at+miplop1en=0 , 300  -[ 18 : 49 : 36.730  ] collect ←  +cis ERROR: 53   

3. The only new addition is low power consumption, is it related to low power consumption? Could it be that the last instruction was not finished, the low power continued to execute, and then an at command came up? Positive into the test, found that registration will fail, only to the success of the connection, are registered successful has not been issued down. Is the array of saved parameters not enough 11? It is very likely that the at command is not found, it is estimated that the character is wrong, to verify that notify is not finished, continue to the next notify. Next use SECURECRT software, test the higher baud rate, see is reply what? The 9600 baud rate is problematic with the internal crystal oscillator when using STM32. However, if the baud rate is biased, then why only the 5th notify have problems? So the idea was blocked at the time.

4. There may be a situation in which the baud rate has a much lower tolerance rate after entering the PSM. Wait to enter PSM mode, PSM mode, the serial port should also be dormant, currently guessing 53 should be the previous 50. It is said that STM32 use internal LSI clock as the serial port 9600 baud rate clock source, then the temperature is high and low, the baud rate difference is very large, the current speculation is this problem, but good temperature how to rise? Does the chip run after a period of time, the consumption of power temperature rise?

Onenet Basic Communication Kit return to +cis error:50 problem solving