Problem with ESP32-C3-AWS-Expresslink-Devkit (IDFGH-10296) with parse error, connection port, ERR14 5 UNABLE TO CONNECT Failed to login AWS (MQTT) broker, ERR2 PARSE ERROR #17 , ERR3 COMMAND NOT FOUND, ERR10 INVALID KEY NAME, ERR4 PARAMETER ERROR with AT COMMAND
geb212 opened this issue · 1 comments
Answers checklist.
- I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
- I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
- I have searched the issue tracker for a similar issue and not found a similar issue.
IDF version.
v1.0
Operating System used.
Windows
How did you build your project?
Other (please specify in More Information)
If you are using Windows, please specify command line type.
CMD
What is the expected behavior?
I encountered these problems with two identical boards and I managed to make them work only today after more than a week of testing, the strange thing is that I did the same thing the other day and last week and they didn't work and today yes, after having done the factory reset several times yesterday and last week too, putting the credentials back on and they weren't working, but today yes, then the problems encountered were these, an error is the one that does not identify me the communication with the door even if "it works for me" , the other is ERR2 PARSE ERROR, this is an error that pops up on most of the at commands without a valid reason, another is: ERR14 2 UNABLE TO CONNECT Failed to access network and the last one is this : ERR14 5 UNABLE TO CONNECT Failed to login AWS (MQTT) broker, even though I entered the correct credentials and port.
After this last error, I rewrote the at command connect and it connected, then the problem I was having with the quick connect to use the AWS IoT demo was an error code 400 and the terminal shut down saying Thing doesn't exist , this problem was solved precisely after using another terminal which is Hercules SETUP, I did all the resets and put the credentials back and reconnected after trying several times, I would like to understand why two brand new boards have the same problem, searching on the net I saw that there is no explanation regarding these problems encountered, and they have not only software problems but also hardware problems since most of the time the ports are not identified
Thanks
What is the actual behavior?
I encountered these problems with two identical boards and I managed to make them work only today after more than a week of testing, the strange thing is that I did the same thing the other day and last week and they didn't work and today yes, after having done the factory reset several times yesterday and last week too, putting the credentials back on and they weren't working, but today yes, then the problems encountered were these, an error is the one that does not identify me the communication with the door even if "it works for me" , the other is ERR2 PARSE ERROR, this is an error that pops up on most of the at commands without a valid reason, another is: ERR14 2 UNABLE TO CONNECT Failed to access network and the last one is this : ERR14 5 UNABLE TO CONNECT Failed to login AWS (MQTT) broker, even though I entered the correct credentials and port.
After this last error, I rewrote the at command connect and it connected, then the problem I was having with the quick connect to use the AWS IoT demo was an error code 400 and the terminal shut down saying Thing doesn't exist , this problem was solved precisely after using another terminal which is Hercules SETUP, I did all the resets and put the credentials back and reconnected after trying several times, I would like to understand why two brand new boards have the same problem, searching on the net I saw that there is no explanation regarding these problems encountered, and they have not only software problems but also hardware problems since most of the time the ports are not identified
Thanks
Steps to reproduce.
I encountered these problems with two identical boards and I managed to make them work only today after more than a week of testing, the strange thing is that I did the same thing the other day and last week and they didn't work and today yes, after having done the factory reset several times yesterday and last week too, putting the credentials back on and they weren't working, but today yes, then the problems encountered were these, an error is the one that does not identify me the communication with the door even if "it works for me" , the other is ERR2 PARSE ERROR, this is an error that pops up on most of the at commands without a valid reason, another is: ERR14 2 UNABLE TO CONNECT Failed to access network and the last one is this : ERR14 5 UNABLE TO CONNECT Failed to login AWS (MQTT) broker, even though I entered the correct credentials and port.
After this last error, I rewrote the at command connect and it connected, then the problem I was having with the quick connect to use the AWS IoT demo was an error code 400 and the terminal shut down saying Thing doesn't exist , this problem was solved precisely after using another terminal which is Hercules SETUP, I did all the resets and put the credentials back and reconnected after trying several times, I would like to understand why two brand new boards have the same problem, searching on the net I saw that there is no explanation regarding these problems encountered, and they have not only software problems but also hardware problems since most of the time the ports are not identified
Thanks
Build or installation Logs.
No response
More Information.
No response
This is the command that i used and the errors encountered
AT+FACTORY_RESET
OK{0D}{0A}
AT+CONNECT
ERR2 PARSE ERROR{0D}{0A}
AT+CONNECT?
OK 0 0 DISCONNECTED STAGING{0D}{0A}
AT+CONF SSID=dexh_main
ERR9 INVALID KEY LENGTH{0D}{0A}
AT+CONF SSID=dexh_main
ERR2 PARSE ERROR{0D}{0A}
AT+FACTORY_RESET
OK{0D}{0A}
Serial port COM12 closed
Serial port COM12 opened
AT
AT
A+CONNECT
AT+CONNECT
Serial port COM12 closed
Serial port COM12 opened
AT
OK{0D}{0A}
AT+CONNECT
ERR14 2 UNABLE TO CONNECT Failed to access network{0D}{0A}
AT+CONNECT?
OK 0 0 DISCONNECTED STAGING{0D}{0A}
AT+CONF SSID=dexh_main
OK{0D}{0A}
AT+CONF Passphrase=DitecDemo0121
ERR10 INVALID KEY NAME{0D}{0A}
AT+CONF Passphrase=DitecDemo0121
OK{0D}{0A}
AT+CONNECT
ERR2 PARSE ERROR{0D}{0A}
AT+CONNECT
ERR14 2 UNABLE TO CONNECT Failed to access network{0D}{0A}
AT+CONNECT
ERR14 2 UNABLE TO CONNECT Failed to access network{0D}{0A}
AT+CONNET?
ERR3 COMMAND NOT FOUND{0D}{0A}
AT+CONNECT?
ERR2 PARSE ERROR{0D}{0A}AT+CONNECT
ERR14 2 UNABLE TO CONNECT Failed to access network{0D}{0A}
AT+CONNECT?
OK 0 0 DISCONNECTED STAGING{0D}{0A}
OK+CONNECT
AT+CONNECT
ERR14 2 UNABLE TO CONNECT Failed to access network{0D}{0A}
AT+CONF? SSID
OK dexh_main{0D}{0A}
AT+CONF? Passphrase
ERR13 KEY WRITEONLY{0D}{0A}
Serial port COM12 closed
Serial port COM12 opened
AT
OK{0D}{0A}
AT+CONNECT
ERR2 PARSE ERROR{0D}{0A}
AT+CONNECT
ERR14 5 UNABLE TO CONNECT Failed to login AWS (MQTT) broker{0D}{0A}
AT+CONNECT
OK 1 CONNECTED{0D}{0A}