Forgot to answer you here too at the time :) This is not a problem, if you look the send and receive example codebase, it is practically a ping pong between your ESP and the Mega. If you interrupt the exchange breaking the connection, the rebound will be broken (as expected) and only a reset will resume the bidirectional exchange :) (because both devices will send a packet as soon as they boot engaging back the infinite ping pong exchange). This is a limit of this simple example's codebase rather than a problem of the PJON implementation.
btw, you have no idea how much your work means to me, i was looking so much for this, tried many other things like modbus and my own protocols, only yours has so many variety in communication types, its beautiful! and, its open source... made me wanna come back to my project and finally complete it...
@@GiovanniBluMitolo omg, you have routers, thats so amazing, i cannot stress how much i needed this, 5 mcus connected locally via one bus, then have multiple buses connected together, oh this is amazing...
In the example: PJON/examples/ESP8266/Local/SoftwareBitBang/SendAndReceive/ (Arduino MEGA + ESP8266 dev board 12E) when I disconnect PJON cable for short time the transmission is recovering, but if it takes too long (few seconds) then I will stop the communication. The serial monitor results are: BLINK BLINK (...) BLINK BLINK Connection with device ID 44 is lost. After that the communication stops until I do a restart of the boards. Do I miss a code, where the loop should ends? Or is this some kind of bug? Thank you in advance for your help!
Forgot to answer you here too at the time :)
This is not a problem, if you look the send and receive example codebase, it is practically a ping pong between your ESP and the Mega. If you interrupt the exchange breaking the connection, the rebound will be broken (as expected) and only a reset will resume the bidirectional exchange :) (because both devices will send a packet as soon as they boot engaging back the infinite ping pong exchange).
This is a limit of this simple example's codebase rather than a problem of the PJON implementation.
yea, i figure you can solve this by using smarter code, or in the end, fail sense device which resets devices via their reset pins, or something...
btw, you have no idea how much your work means to me, i was looking so much for this, tried many other things like modbus and my own protocols, only yours has so many variety in communication types, its beautiful! and, its open source... made me wanna come back to my project and finally complete it...
@@pahvalrehljkov thank you very much for your compliments, I hope PJON and PJDL will serve you well :)
@@GiovanniBluMitolo and your Agenda scheduler library is yummy also...
@@GiovanniBluMitolo omg, you have routers, thats so amazing, i cannot stress how much i needed this, 5 mcus connected locally via one bus, then have multiple buses connected together, oh this is amazing...
In the example:
PJON/examples/ESP8266/Local/SoftwareBitBang/SendAndReceive/ (Arduino MEGA + ESP8266 dev board 12E)
when I disconnect PJON cable for short time the transmission is recovering, but if it takes too long (few seconds) then I will stop the communication.
The serial monitor results are:
BLINK
BLINK
(...)
BLINK
BLINK
Connection with device ID 44 is lost.
After that the communication stops until I do a restart of the boards. Do I miss a code, where the loop should ends? Or is this some kind of bug?
Thank you in advance for your help!