I'm working on a project that uses LoRa transmission with the Ebyte E220-900T30D module on the ESP32 (LoRa_E220.h library), but I'm facing an inexplicable problem.
I configured both the transmitters and receivers to channel 50 using the Ebyte software, only changing their addresses. However, the channels are only maintained when I compile the code on a specific computer. If I compile on any other computer, the channel automatically changes to 133 and I can't establish communication.
Even if I comment out the "configuration.CHAN" function, it keeps changing the channel automatically. Does anyone have any idea what could be causing this? Tks!
M0 —– 25
M1 —– 26 (19 on the transmitter)
AUX —– 34 (18 on the transmitter)
TX —– RX2
RX —– TX2
GND —– GND
VCC —– 3.3V
I had to change the receiver's pin configuration to include an SD card, but even using the transmitter's pin configuration, the problem persists.
My guess is: the libraries of both computers are not the same. That is to say, some libraries are outdated, some are updated, but new and old are not the same on the two computers. I would discover the discrepancies first (so you can fallback when everything stop working), then update both computer libraries and resolve the problems that you will definitely have.
The library is properly updated on all computers. It's strange because I tested it on machines with same and different technical specifications, and yet the problem persists.
Hi @gabrixxxxl. I'm going to ask you to provide the full verbose output from a compilation of the sketch on each of the computers. We might be able to spot some difference that explains the different results from the program compiled by the specific computer.
This procedure is not intended to solve the problem. The purpose is to gather more information.
Please do this:
Open the sketch in Arduino IDE on the computer that produces the program that maintains the channels.
Select File > Preferences... (or Arduino IDE > Settings... for macOS users) from the Arduino IDE menus.
The "Preferences" dialog will open.
Check the box next to "Show verbose output during: ☐ compile" in the "Preferences" dialog.
Click the "OK" button.
The "Preferences" dialog will close.
Select Sketch > Verify/Compile from the Arduino IDE menus.
Wait for the compilation to finish.
Right click on the black "Output" panel at the bottom of the Arduino IDE window.
A context menu will open.
Select Copy All from the menu.
Open a forum reply here by clicking the "Reply" button.
Click the <CODE/> icon on the post composer toolbar.
This will add the forum's code block markup (```) to your reply to make sure the error messages are correctly formatted.
Press the Ctrl+V keyboard shortcut (Command+V for macOS users).
This will paste the compilation output into the code block.
Move the cursor outside of the code block markup.
Open the sketch in Arduino IDE on a computer that produces the program that changes the channel to 133.
Repeat the procedure described above on that computer.
Click the "Reply" button to publish the forum post that contains the compilation output.
In case the output is longer than the forum software will allow to be added to a post, you can instead save it to a .txt file and then attach that file to a reply here.
Open a forum reply here by clicking the "Reply" button.
Click the "Upload" icon () on the post composer toolbar:
The "Open" dialog will open.
Select the .txt file you saved from the "Open" dialog.
Click the "Open" button.
The dialog will close.
Click the "Reply" button to publish the post.
Alternatively, instead of using the "Upload" icon on the post composer toolbar as described in steps (5) - (7) above, you can simply drag and drop the .txt file onto the post composer field to attach it.
which specific ESP32 are you using?
is it the transmitters or receivers which have problems or both?
is it the devices with the SD cards which have problems - if so what happens if you remove the SD card code?
could you be having power supply problems on transmission?
have you pullup resistors on the RXD and TXD lines?
EDIT: try running example code
File>Examples>Ebyte LoRa E220 Library>01_getConfiguration
OK, great. I did spot a very significant difference in the outputs.
In this one:
We see that you have version 2.0.11 of the "esp32" boards platform installed on that computer:
Using board 'esp32' from platform in folder: C:\Users\Automação\AppData\Local\Arduino15\packages\esp32\hardware\esp32\2.0.11
In this one:
we see that you instead have version 3.0.0 of the platform installed:
Using board 'esp32' from platform in folder: C:\Users\Oficina 4.0 area 3\AppData\Local\Arduino15\packages\esp32\hardware\esp32\3.0.0
And in this one:
we see you have version 3.0.1 installed:
Using board 'esp32' from platform in folder: C:\Users\Win10\AppData\Local\Arduino15\packages\esp32\hardware\esp32\3.0.1
There have been some very significant changes to the "esp32" boards platform between the 2.0.11 version installed on the computer that produces the "good" behavior and the 3.0.0 version installed on the computer that produces the "bad" behavior.
You can test my hypothesis that this difference is the cause of the problem by performing an experiment of installing version 2.0.11 of the "esp32" boards platform on the computer that produces the "bad" behavior, uploading the sketch to the board from that computer, then checking to see whether it now produces the "good" behavior.
I'll provide instructions you can follow to do that:
Start Arduino IDE on one of the computers that produces the "bad" behavior.
Select Tools > Board > Boards Manager... from the Arduino IDE menus.
The "Boards Manager" dialog will open.
Wait for the updates to finish, as shown by the messages printed at the bottom of the "Boards Manager" dialog.
Scroll down through the list of boards platforms until you find the "esp32" entry. Click on it.
A "Select version" dropdown will appear in the entry.
Click on the "Select version" dropdown.
It will expand.
Select "2.0.11" from the menu.
Click the "Install" button in the "esp32" entry.
Wait for the installation to finish.
Click the "Close" button on the "Boards Manager" dialog.
The "Boards Manager" dialog will close.
Open your sketch.
Upload the sketch to your board, as usual.
Now check whether the board now exhibits the "good" or the "bad" behavior.
This procedure is not intended to solve the problem. The purpose is to gather more information.
) on the post composer toolbar: