Ebyte SX1276 Lora module

[javrolijk]

Hi folks,

Could anyone provide a hand. I'm trying to fogure out how the FDRS sensor code would work with an Ebyte SC1276 module connected on an ESP32 MCU. I'm not a programmer but can follow instructions quite well.

The Ebyte SC1276 consists of the following pins: M0, M1, RXD, TXD, AUX, VCC and GND.

The FDRS Lora sensor configuration code is as follows:

Is there any modifications that needs to be done for it to work with this particular Lora module?

Below are some pictures of the Ebyte SC1276 as a reference.

In advance many thanks for any info.

The ESP32 MCU:

[timmbogner]

Unfortunately this is another situation like the REYAX module. The module you have would be more properly known as an Ebyte E32 module (no relation to ESP32), although I see that the Amazon listing makes this unclear. While it is built around the SX1276/8, the manufacturer again added an extra layer for addressing, making it incompatible with other LoRa modules.
Modules that access the SX1276 chip directly via the SPI interface are what will be compatible with FDRS. If the module has MISO, MOSI, CS, and SCK pins then you you are in good shape. If the module has RXD and TXD then you probably have an incompatible device. The LoRa library's repo has more on this.

Your RFM95W mentioned previously should work.

[timmbogner]

It's cool! You change it by editing the "fdrs_globals.h" file inside of your "Arduino/libraries/" folder.
I would encourage you to start using the latest FDRS version too, which is found in the 'dev' branch of the repo. It will become the new official release sometime in the next couple weeks.

[javrolijk]

It's cool! You change it by editing the "fdrs_globals.h" file inside of your "Arduino/libraries/" folder. I would encourage you to start using the latest FDRS version too, which is found in the 'dev' branch of the repo. It will become the new official release sometime in the next couple weeks.

Hi Timm,

Quick question. Should I replace the fdrs_functions.h and all other functions which was downloaded from the git 'main' branch with the functions in the scr folder of the git 'dev' branch?

[javrolijk]

I have some code to display sensor values as well as the ID and Gateway mac on these Lilygo Lora modules. Not sure if support for an OLED code can also be integrated in the FDRS system?

[timmbogner]

Hey! Sorry for the delay, I took a quick hiatus. How are things going?

Hopefully you got your upgrade situation figured out. Replacing them might work, but you're better off installing the repo in the Arduino 'libraries' folder.

I definitely like the idea of supporting OLEDs! Perhaps the top strip (yellow on some screens) could display the ID and GTWY_MAC, then the bulk of the screen could output messages from the DBG() function. Super-cool!
If you implement it, please do submit it as a pull request, or if you aren't so comfortable with that you could email the code to me.

[javrolijk]

Hi Timm,

Thanks for the follow-up.
Indeed, I've implemented the script for the OLED and it seems to work fine. Nonetheless, since I'm not a coder, I've just implemented the code as it seems logical to me based on other sources.

If you like, I can send the script of how I have the 'FDRS Sensor' working and you could review/revise the OLED code in the proper way.

Below is the 'FDRS Lora Sensor' displaying the relevant data on the OLED.
What's your email address?

Br,
Jairo

The Lora Gateway displaying the mac address and a packet counter.

[timmbogner]

Ay nice! Yeah I'd love to take a gander at your code... timmbogner@gmail.com. I'll add you as a contributor if I end up implementing it.

[javrolijk]

Ay nice! Yeah I'd love to take a gander at your code... timmbogner@gmail.com. I'll add you as a contributor if I end up implementing it.

Email sent with the OLED script.

[lamasseriadipolverara]

for e32 ebyte module there is this library
https://github.com/xreef/LoRa_E32_Series_Library
@timmbogner it's possible to include it or there are some conflicts?

[timmbogner]

It wouldn't be impossible, but it's not a great fit. Among other things it would tie up a UART interface, making it especially hard to use on ESP8266.