Forum Replies Created
-
AuthorPosts
-
Hi Gilles,
can you send me the code you use and the library version.
Bye RenzoHi Morne,
First, try the example to send the email that you can find to the examples folder and give me the test response.
It seems correct, so there may be a network problem, but we’ll have the response with the standard test.
Bye RenzoHi ps2chiper,
I push the branch, you can find It here.I create a define for EthernetLarge
#define DEFAULT_EMAIL_NETWORK_TYPE_SAMD NETWORK_ETHERNET_LARGE
And you also must uncomment
#define SSLCLIENT_WRAPPER
but in the branch is already uncommented.
You must add thrust anchors with this command
emailSend.setTrustAnchors(TAs, (size_t)TAs_NUM, A3);
I don’t test It, but with your change on bearssl_ssl.h header.
/** \brief Optimal input buffer size. */ //#define BR_SSL_BUFSIZE_INPUT (16384 + 325) #define BR_SSL_BUFSIZE_INPUT (1024 + 325) /** \brief Optimal output buffer size. */ //#define BR_SSL_BUFSIZE_OUTPUT (16384 + 85) #define BR_SSL_BUFSIZE_OUTPUT (1024 + 85)
I also change SSLclient.h from this
unsigned char m_iobuf[2048];
To this
unsigned char m_iobuf[BR_SSL_BUFSIZE_BIDI];
as advised on your example.But I don’t understand how to manage TLS encryption.
Bye Renzo
Hi ps2chiper,
I’m going to create a branch of my library with a basic implementation.
When finished, I’m thrilled to help me complete the work.
I will write here when the version is created.
Bye RenzoHi all,
Can it be a solution to use a device (like esp32-s2) with USB OTG and connect It directly to the USB like Octoprint???
Bye RenzoHi Theo,
It seems all ok, try to make any change
WOR role
and
Tran Mode
of DTU, in a previous version of the E22 client, Ebyte made some parameters errors.If you have another E22, try to send a message to check if you have some receiving problem.
Bye Renzo
Hi Arkadiusz,
I don’t check the firmware, and I don’t know well the board, if you check that I think there wasn’t a way.
But I don’t know if the protocol was the same of standard communication via serial usb.We must check that possibility and we can go to use that to connect.
Bye Renzo
Ahh! Yes ok I didn’t remember that.
To set correct power you must add the define, you can refer to this paragraph.
But I think that the problem isn’t that.
For debug uncomment the define in LoRa_E22.h file, but I think also this can’t add more information.
Try to change/remove resistor and connect to 5v.
Bye Renzo
Hi olo,
I don’t know that board and to work a wifi module need more pins check
MKS WIFI for Makerbase Robin: boards and how to wiring esp12 & NodeMCU – 1I think it’s possible but now I don’t check that.
MKS WIFI need an esp8266.
Bye Renzo
Hi Theo,
I don’t know if e22 and e90 are compatible.You must declare the correct power, but it isn’t that the problem
The 30 need more ampere and it’s better if you use 5v
I test the module in Vero close position without problemBye Renzo
Hi,
if you uncomment the debug variable you can get additional info
But I think in your case there is a wiring problem
Try to remove/change the resistor.
What is the exact model you use?Very interesting,
probably I’m going to test SSLClient to implement TLS for WiFi also.
Keep in touch RenzoHi Theodoros,
It seems all ok; try to put it all on a breadboard and activate the debug.
Which error do you receive?
Bye RenzoHi ps2,
fantastic, can you share your coffee to integrate on the library..
Bye RenzoHi,
here an exampleEMailSender::FileDescriptior fileDescriptor[2]; fileDescriptor[1].filename = F("test.txt"); fileDescriptor[1].url = F("/test.txt"); fileDescriptor[1].storageType = EMailSender::EMAIL_STORAGE_TYPE_SD; fileDescriptor[0].filename = F("logo.jpg"); fileDescriptor[0].url = F("/logo.jpg"); fileDescriptor[0].mime = "image/jpg"; fileDescriptor[0].encode64 = true; fileDescriptor[0].storageType = EMailSender::EMAIL_STORAGE_TYPE_SD; EMailSender::Attachments attachs = {2, fileDescriptor}; EMailSender::Response resp = emailSend.send("<receipe@gmail.com>", message, attachs);
Bye Renzo
-
AuthorPosts