Forum Replies Created
-
Posts
-
Hi Fernando,
sorry for the late response.I think the problem can be that From core 2 to core 3, TX2 and RX2 pins are changed
Try to force the pin number
LoRa_E32 e32ttl100(16, 17, &Serial2, 15, 21, 19, UART_BPS_RATE_9600); // RX AUX M0 M1Bye Renzo
Hi,
sorry for the late responseThe error (SSLClient)(SSL_ERROR)(m_print_br_error): Incoming protocol or record version is unsupported. indicates that the SSL/TLS version the server expects is not supported by your client. Check if your server enforces a specific SSL/TLS version (like TLS 1.2 or 1.3). Ensure that your ESP32 or SSLClient library supports the required version.
Try to modify the SSL settings on your server to allow older versions like TLS 1.1 or ensure the client can handle TLS 1.2+.
Bye RenzoHi,
I think that, as described in the error, the problem is that the version of SSL is not supported by SSLClient; try to check the server security settings.
Bye RenzoHi Edge,
to show the frequency as you need, you must put one of these define before the library include.#define FREQUENCY_868 #include "LoRa_E32.h"Bye RM
Hi Adi,
I don’t think it’s possible for the E22 to communicate with the E32 directly. They use different chips and have different cryptographic systems, which makes them incompatible for direct communication.
Best,
RenzoHi Adam,
You are right. The C1 is correct. It is also in the library. I verified that but also checked the other set that must be respected; if you receive that message, you have something wrong or some noise with the device setting. But if it works for the other operation, we will never discover what it is :D.Bye Renzo
Ahh! Yes, I already found that some models of E220 have this “issue,” but they’re working correctly.
Sometimes, there is a power supply problem. In your case, it’s more rare, but you can ignore that response.
Bye RenzoHi Adam,
If it’s well connected, there are two other options:- the power supply is not sufficient;
- the device is broken.
Try to use an external power supply for the module.
Bye Renzo
Ahh, wait, you use uart directly to send messages.
If I remember, I applied encoding in the library to prevent problems with not-in-range characters.
Use the library.
Bye RenzoNo, no, the Arduino esp8266 core.
probably the problem is that you don’t connect the AUX pin, and the waiting time is too long.
I’m going to add some tricks to prevent the brownout.
Bye RenzoThe structure can’t be the same if you read the first 3 bytes.
Check the last sketch in the link I posted before.
Bye RM
Aaah, no, wait, you read the first 3 bytes, then you try to reread the first 3 bytes again.
You must create a structure for the remaining data.Check this article that explains how to manage the initial message.
Bye RM
