Forum Replies Created
-
AuthorPosts
-
Hi Thayro,
sorry no time for that now, but It’s very strange the behavior of your e22 device.
Mine work correctly.
Bye RenzoHi Henk,
It can be possible, in this library (differently from pcf8574 lib) I implemented only INPUT and not INPUT_PULLUP.
You can try to set to 0 the debounce variable to prevent this problem#define READ_ELAPSED_TIME 10 // to 0
Bye Renzo
Hi Craig,
I think this is a more simple approach
Ebyte LoRa E32 device for Arduino, esp32 or esp8266: power saving and sending structured data – Part 5but in your sketch you write
struct Message message = *(tdata*) rt.data; Serial.println(message.type);
but in
tdata
not existtype
it an array, you can access It via index.Bye Renzo
Hi Craig,
Well, I’m glad you solved the problem. I hope the topic will be of help to others as well.
Bye RenzoHi craig,
check better if M0 and M1 changing correctly. With that 3.3v device sometime can be problem when one of that are LOW and HIGH at the sametime.
Bye RenzoFrom the log seems that you send only wake up message, but the receiver was already waked up.
If I understand the behavior you must do:
Master
– Wake up mode
– You must send wake up message to the slave with broadcast
– go in normal mode and wait response messagesSlave
– Sleep mode
– wake up via message
– after wake up set normal mode
– send data to the MasterBye Renzo
Sorry Craig,
I explain better.
In this list there isn’t the change mode log that allow send messagebelow is print screen from node after wake up 8:57:34.664 -> AUX HIGH! 18:57:34.664 -> Complete! 18:57:34.709 -> Clear buffer…ok! 18:57:34.709 -> Success 18:57:40.272 -> AUX HIGH! 18:57:40.272 -> Complete! 18:57:40.272 -> Clear buffer…ok! 18:57:40.318 -> Success 18:57:45.842 -> AUX HIGH! 18:57:45.842 -> Complete! 18:57:45.888 -> Clear buffer…ok! 18:57:45.888 -> Success 18:57:51.447 -> AUX HIGH! 18:57:51.447 -> Complete! 18:57:51.447 -> Clear buffer…ok! 18:57:51.491 -> Success 18:57:57.047 -> AUX HIGH!
It seems that not switch to Wake up mode
Bye Renzo
In the log I can’t see the mode change after Wake up, It’s possible that there isn’t??
Bye RenzoHi Craig,
the log sayWait no AUX pin!
there is a configuration problem, and you can’t change mode without fully connection.
Bye Renzo21 July 2021 at 00:07 in reply to: Constructor difference and HardwareSerial and SoftwareSerial difference #13759Hi Thayro,
I release It, you can find the program in the example list of Library.
Bye RenzoHi Craig,
also in this sketch you must calle32ttl.begin();
only one time, remove the others, you can’t change mode without connect M0 and M1, that these are needed to set LOW or HIGH to change the mode.
do these changes and retry.
Bye Renzo
Hi Craig,
for now the only problem I see is that you do begin 2 times, removee32ttl.setMode(MODE_2_POWER_SAVING);
and the second
e32ttl.begin();
and to have more information uncomment this line on LoRa_E32.h
// #define LoRa_E32_DEBUG
and put the client code also.
Bye Renzo
20 July 2021 at 10:16 in reply to: Constructor difference and HardwareSerial and SoftwareSerial difference #13713Hi Thayro,
you are right, has been ready for months, i try to publish as soon as possible.
Bye RenzoSorry your reply was in spam.
Change pin and use pin without internal resistor.
Bye RenzoHi AVM,
sorry if I reply only now, but your topic was went on Spam.Try to add AUX, without AUX the Success response is based only on empirical data. And check before that you got an error.
Write the constructor declaration o I check better if something was wrong.
Bye Renzo -
AuthorPosts