[Dusan]

Hi Renzo, today I was trying to solve the problem with the Timeout error!! I managed to fix the error in the code // wait until aux pin goes back low
Status res = this->waitCompleteResponse(2000);
if (res == E220_SUCCESS) {
this->mode = mode;
}

return res;
} in the cpp file. By changing the value from 1000 to 2000 and changing WOR to the value WOR_1000_001. I wasn’t able to find the correct value for WOR_2000_011. At the same time, I confirmed that the cyclic restarting of ESP8266 is indeed caused by the library. :/ If the value of waitCompleteResponse() was too high, the ESP8266 would cyclically restart. I’m not a good programmer, so I have no idea how to fix this error. Have a nice day.

[Dusan]

Hello Renzo, the cyclic restarting issue was solved by adding delay(4000) at the beginning of the setup sequence. During my attempts, I found out that ESP8266 won’t boot when pin D5 is in a low state at the moment of the setup procedure. The difference in behavior between E32 and E220 modules is probably caused by different booting speeds or perhaps different hardware designs.I haven’t been able to solve the Timeout!! error on the server side yet…. This error is interesting because the module sends out WOR and data (attachment from SDR) and data from client are received. 🤔 Have a nice day!

Attachments:

You must be logged in to view attached files.

[Dusan]

With E32-900T30D module, it is not necessary to send messages with a maximum length of 58 bytes in individual packets. The module automatically splits packets when the length exceeds 58 bytes. Maximum possible lenght to send is up to 512 bytes. It is sufficient to change the #define MAX_SIZE_TX_PACKET in the library. Tested and working 🙂 Have a nice day!”

[Author]

Posts