after I finally got my module up working, I continued on actually getting my two LoRa modules to talk with each other. But to be honest, I’m lost yet again and overwhelmed with all the information and (honestly) not so clear examples to me.
So my two modules and goals are:
– E-Byte E32-900T20D (with an antenna attached to the SMA jack): This module should only listen for packages; it will be a simple gateway basically.
– HopeRF RFM95W (with a wire sodlered to it as an antenna: This module should only send packages; they will be installed into various sensors I have.
=> So I ultimately want to do a “fixed transmission”, as every RFM95W always directly talks to the E32. But I’m fine with having them at least communicate for now in ANY way…
My first tests were just leaving all the default config for both modules as they are, just setting the frequency on both sides to 868MHz and send a message. Obviously, this doesn’t work, as in: the RFM95W successfully sends the message, but my E32 module never receives something…
So something must still be off between those two.
I of course tested sending and receiving with two RFM95W and that does work. So *generally* sending data works.
So I tried setting the E32 to broadcast mode using your tutorials ad also tried switching off FEC (tried wit and without FEC):
I validated the response to setConfiguration included my changed settings, so I expect them saved.
Unfortunately still nothing: My RFM95W apparently sending packages, nothing received on the E32…
I think I understood how the E32 LoRa module communication works, at least that it’s a matter of address and channel who will receive the data I send. The address (seems to be) defined by ADDH(igh) & ADDL(ow). The channel seems to also effect the frequency that is used. So setting the frequency with #define FREQUENCY_868 actually sets it to 862 and with my channel set to 6, it actually uses my desired 868MHz. So if I understand it right, changing the channel to 4 would make the module communicate on 866MHz!? However, I need 868MHz.
Witout setting it to broadcast mode, my default settings are:
AddH BIN: 0
AddL BIN: 0
Chan BIN: 6 -> 868MHz
So I think I understood that side of the cake. But I can’t make it to receive what the RFM95W sends… Actually, your / the E32 is way better documented and understandable than the RFM95W and the famous Arduino lib to use it: https://github.com/sandeepmistry/arduino-LoRa. This lib/the RFM95W doesn’t have any ADDL/ADDH nor channel I can configure… It has a “sync word” which I still didn’t fully understand how it’s part of the whole sending/receiving process. Also setting the frequency is utterly complicated, split over three bits with a weird formula behind it… I can’t even figure out the *exact* frequency when I set it to 868E6…
I’m not asking you to understand how this lib works, but: This RFM95W is a *very* common module, so is this lib. I’m just wondering if you ever got an E-Byte and RFM95W to successfully communicate with each other, or if you have a hint where I could start searching what the issue is…
Hi ezcGman,
I think the two modules can’t be compatible.
RFM95W is a basic lora module, e32 is more complex, have a specified protocol with data criptyng, WOR, addressing and other features.
Bye Renzo
Ah man, that’s sad… I also did some crawling through issues on “the other side” and it seems people have been able to mock what the e32 sends and receive it on an rfm95w, but not other way around…
That’s super sad 🙁 Just getting into LoRa and seeing that different modules for the same tech can’t communicate is pretty sad 🙁
Will probably go for the RFM95W then, as it’s cheaper and if I gonna do multiple sensors, this will quickly add up :/
So the E32 uses the Semtech SX1267 or 78. The RFM95W is a copy of the SX1276. So theoretically, if I would be able to control the chip directly via SPI and not via the UART “bridge”, I should be able to use the Arduino Lora lib…
I looked through the E-Byte website, but couldn’t really find a module that exposes the SPI interface. Are you aware of any? :/ Maybe I overlooked something. Thx!
But quick question already: Will I be able to communicate with RFM95W modules with the E220?
The E32 SPI looks like it could work with the arduino-lora lib, hence I can have a quality module as a gateway working with the RFM95W has cheap alternatives for the sensors 🙂
I think It’s not possible, but the price of LoRa E220 it’s the same as RFM95W so you can use only that.
I don’t know if E32 SPI can communicate with RFM95W.
Bye Renzo
Maintaining a repository (or site or forum) is a lot like tending to a garden - it requires constant care and attention to keep it thriving. If you're a skilled gardener (or coder!) and want to help keep our repository blooming, we'd love to have you on board! We're also looking for talented writers and forum moderators to help us grow our community. Interested in joining our team? Don't hesitate to reach out and let us know how you can contribute!
Are you a fan of electronics or programming? Share your knowledge with others, write a simple tutorial or how to make a great project Contact me: share_your_ideas@mischianti.org
The content displayed on this website is protected under a CC BY-NC-ND license. Visitors are prohibited from using, redistributing, or altering any content from this website for commercial purposes, including generating revenue through advertising. Any unauthorized use is a violation of the license terms and legal action may be taken against individuals or entities found to be in violation.
You must also provide the link to the source.
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.