Hi
Just wondering if there is a bug with the ClientSendRequest macro in the ESP8266?
I've previously used this in v6 but in v8, after I connect to the server and issue the above, the the ESP replies with "no tail". This implies that a carriage return character is missing.
If I monitor what is being sent to the ESP8266 by the chip I can see that everything is fine up until the above request. When issuing the above I see AT+CIPSEND=0,73 with the required CR / LF at the end (0D and 0A)
However no further characters are sent from the chip after 0D and 0A, the ESP replies with "no tail" upon which the chip the closes the connection.
From another post I saw a similar "no tail" problem with the MQTT component and wonder if they are related?
Regards
ESP82666 bug? (no tail)
Moderator: Benj
-
chipfryer27
- Valued Contributor
- Posts: 664
- Joined: Fri Jun 06, 2014 3:53 pm
- Has thanked: 184 times
- Been thanked: 203 times
- Contact:
-
chipfryer27
- Valued Contributor
- Posts: 664
- Joined: Fri Jun 06, 2014 3:53 pm
- Has thanked: 184 times
- Been thanked: 203 times
- Contact:
Re: ESP82666 bug? (no tail)
Hi
I think there is a bug.
Figuring that the UART was already configured when the component was configured, I kept my code the same until I reached the ClientSendRequest macro.
Instead of using that macro I sent the required AT commands using the SendString macro in the UART.
e.g.
"AT+CIPSEND=0,73\r\n"
"blah blah"
Worked a treat.
Hope this helps.
Regards
I think there is a bug.
Figuring that the UART was already configured when the component was configured, I kept my code the same until I reached the ClientSendRequest macro.
Instead of using that macro I sent the required AT commands using the SendString macro in the UART.
e.g.
"AT+CIPSEND=0,73\r\n"
"blah blah"
Worked a treat.
Hope this helps.
Regards