SSL Secure Socket Layer is a name for a techgnology already not used but the name become generic for TCP secure layer. (TLS is used now.)
the site uses https. it is http over secure layer. default https port is 443.
in CIPSTART use "SSL" instead of "TCP" and port 443
Juraj:
SSL Secure Socket Layer is a name for a techgnology already not used but the name become generic for TCP secure layer. (TLS is used now.)
the site uses https. it is http over secure layer. default https port is 443.
in CIPSTART use "SSL" instead of "TCP" and port 443
Hi Juraj,
Thanks for the reply. I've tried it out but it still won't connect unfortunately. But there is a slight difference whereby it is successful for CIP+SEND.
Juraj:
the second parameter is a server name or IP address. don't put https:// there
I've tried that earlier but it didn't work. But then I randomly tried to set AT+CIPSTART=1 instead of 0 and it worked! (I believe and I'm not sure what this does exactly)
But thank you as the SSL + 443 port actually did solve part of the problem I'm facing.
SSL connection can take longer then a second then the find will wait so with your haphazard code it sometimes connects sometimes not. and same applies for CIPSEND.
Juraj:
SSL connection can take longer then a second then the find will wait so with your haphazard code it sometimes connects sometimes not. and same applies for CIPSEND.
Haphazard code? If there a solution for this because I have no idea
send the command
check the count. not reached
send the command again ! AT firmware responses "busy p..." but you don't see it
find waits for timeout (1 sec) or for some characters. for SSL this can timeout
check the count. not reached
send the command, AT firmware responses "busy p..." but you don't see it
find waits for timeout (1 sec) or for some characters. some characters arrive but if it is not the expect response then find times out again.
if the connection failed AT firmware sends ERROR. you don't see it.
if the response it is not the expected OK, it repeats this (10 times) again, but you don't see it
I would recommend my WiFiEspAT library, but for SSL it requires AT firmware 2.1
Juraj:
SSL connection can take longer then a second then the find will wait so with your haphazard code it sometimes connects sometimes not. and same applies for CIPSEND.
I also don't understand what you mean by "haphazard".
haphazard is defined as marked by lack of plan, order, or direction
What does he need to do to fix his code to make it work?
That is the answer that would be the most useful.
ieee488:
I also don't understand what you mean by "haphazard".
haphazard is defined as marked by lack of plan, order, or direction
What does he need to do to fix his code to make it work?
That is the answer that would be the most useful.
.
yes haphazard is the right word. did you read my previous comment about the sendATcmd? how it send the command at least twice and on other then expected answer 20 times?
the esp8266 AT commands syntax and responses to them are inconsistent. so it takes a lot of code to handle the responses properly with one function. that is why I made a library. you can see the EspAtDrv class in my WiFiEspAT library.
Juraj:
yes haphazard is the right word. did you read my previous comment about the sendATcmd? how it send the command at least twice and on other then expected answer 20 times?
the esp8266 AT commands syntax and responses to them are inconsistent. so it takes a lot of code to handle the responses properly with one function. that is way a made a library. you can see the EspAtDrv class in my WiFiEspAT library.
Alirght I'll try this. So I should update my Esp8266 firmware to 2.1 first?
Juraj:
yes haphazard is the right word. did you read my previous comment about the sendATcmd? how it send the command at least twice and on other then expected answer 20 times?
the esp8266 AT commands syntax and responses to them are inconsistent. so it takes a lot of code to handle the responses properly with one function. that is way a made a library. you can see the EspAtDrv class in my WiFiEspAT library.
No haphazard is not the right word.
I know English is not your first language.
I am still not understanding what you are writing.
I find your explanation very difficult to understand.
You write : "that is way a made a library. you can see the EspAtDrv class in my WiFiEspAT library. "
huh?
Instead of just saying that something is wrong, you should provide a solution.
I don't see a fix for his code.
ieee488:
No haphazard is not the right word.
I know English is not your first language.
I am still not understanding what you are writing.
I find your explanation very difficult to understand.
You write : "that is way a made a library. you can see the EspAtDrv class in my WiFiEspAT library. "
huh?
Instead of just saying that something is wrong, you should provide a solution.
I don't see a fix for his code.
.
ieee488:
No haphazard is not the right word.
I know English is not your first language.
I am still not understanding what you are writing.
I find your explanation very difficult to understand.
You write : "that is way a made a library. you can see the EspAtDrv class in my WiFiEspAT library. "
huh?
Instead of just saying that something is wrong, you should provide a solution.
I don't see a fix for his code.
But I'm unable to update the AT to 2.1. How do I do that? I tried flashing the factory_WROOM-02. bin file into address 0x0 but it gives download failed.
did you see: "It is possible to build the AT 2 for esp8266 with 1 MB flash, but Espressif didn't publish a binary for this option. You can download it here."
Juraj:
did you see: "It is possible to build the AT 2 for esp8266 with 1 MB flash, but Espressif didn't publish a binary for this option. You can download it here."