Lora E32 Serial communication

Hello, I have a project containing 2 arduino nano, 2 lora E32 and a mpu6050. My project is that the mpu module send data including acceleration ang angle with e32 communication module to another arduino. Briefly it is serial communication. But there is a problem about receiving part. I used Lora EBYTE library code to transmit and receive. When I open transmit serial port like COM3
it send the data, but in receiving serial port there is nothing about the data. I controlled wiring many times but it is correct wiring. So how can I solve this problem?

If you want help from us solving this problem, you have to provide much more information. Post the complete code of your project, a wiring diagram, links to all hardware used and links to the libraries you used if they are not available in the Library Manager.

what Lora E32 library are you using ?
upload a schematic of the wiring - the nano uses 5V logic the E32 3.3V logic therefore you will require a potential divider on the Nano TX to E32 Rx lines
what serial library are you using?
what does the transmitter and receiver Serial Monitors show
there can be a problem with some Arduino Nanos that the power supply cannot supply the requirements of the Lora modules during transmission - see post decimals-strings-and-lora

E32_receiver_ayarli.ino (5.7 KB)


E32_TRANSM_TTER.ino (5.6 KB)

Rx => 10
Tx => 11
M0 => 7
M1 => 6
AUX => NULL
GND
VCC => 5V

sendFixedTransmission
receiveFixedTransmission

These libraries just in transmit code I addedd mpu code

it looks from the image of post 4 you have connected the E5 VCC to nano 5volts - most examples show it powered from 3.3V

The LoRa E32 can be powered by either 3.3V or 5V but the communication is strictly 3.3V so you must use level converters for these signals (at least voltage dividers).
You must check the modules for damages after you installed the level converters because the to high signal voltage may have fried them already.

That the E32 modules use LoRa is not that significant, the serial protocol that the modules use is specific to Ebyte.

Standard SPI based LoRa module comms are straight forward to debug, since you can easily test the read and write of the LoRa device registers over SPI.

The most important step in debugging most all LoRa setups like this is to have some independant mechanism for testing that the devices are actually transmitting. If both devices can transmit, then its highly likely that one of them will receive.

I have a UHF handheld handy on my desk, if I am testing 434Mhz modules the handheld will make a noise if the LoRa device is transmitting. You can use a low cost SDR to do much the same test.

Quite so.

If your debugging a setup, then you need to be fairly certain that the modules themselves are OK.

If there is a risk that modules may have been damadged due to inappropriate connections, then its time to get new modules, connect them correctly, and start testing again.

I will try to wire vcc to 3.3V but I asked manufacturer that does arduino provides sufficient voltage to work lora modules he said yes it is not a problem. Are there any problem about codes?

The data sheet for the E32 lists the voltage level for the IO pins as 3.6v max.

The Arduino Nano puts out 5v.

From the datasheet;

"If the communication level is higher than the allowed maximum value, the module may be damaged"

I get it thank you ı will change old module with new modules

That wasn't the problem! You can power it by 3.3V or 5V, but the serial pins must have voltage levels below 3.6V!

And don't connect them directly to the Nano again. You must use level shifters for the serial pins!

if you are testing a 3.3V device why not use a 3.3V host microcomputer ?
e.g. a Grove_LoRa_E5 connected to ESP32 Serial1 hardware port - give us Lora peer-to-peer, LoRaWAN, WiFi, Bluetooth Classic 2.0 and BLE

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.