I’m new to this forum and I just started looking at a way to setup a point-to-point communication using E220-900T22D modules with Arduinos (or ESP32).
I’m a bit confused by some comments in the examples for fixed transmission and for receiving message as explained below:
Comments in the Arduino Fixed Transmission source :
// with this DESTINATION_ADDL 2 you must set
// FIXED SENDER configuration to the other device and
// FIXED RECEIVER to this device
#define DESTINATION_ADDL 2
Comments in the Arduino Receive Message source :
// with this RECEIVER_ADDL 3 you must set
// FIXED RECEIVER configuration to the other device and
// FIXED SENDER to this device
#define DESTINATION_ADDL T
The way it is written it looks like the Fixed Transmission device must be configured as a FIXED RECEIVER whilst the receiver must be configured as a FIXED SENDER.
Hi Robert,
Welcome to the forum, I think you get the library from Ebyte E220 (LLCC68) compatibility
And the example from the same topic.
You need another sketch to understand that comments. I created a setConfiguration file with a long set of configuration examples to simplify your work, and I named every configuration like FIXED SENDER or FIXED RECEIVER.
I have attached the setConfiguration file.
I will release the complete library and tutorial soon.
In fact I got the complete library and examples from github and I already looked at the setConfiguration file. You did a great job! It will surely simplify my work. Thanks a lot.
However, what I don’t understand is that in the fixed transmission file (Arduino_e22_04_SendFixedTransmission.ino) there is a comment saying that the the other device (i.e. the receiver of the fixed transmission) should be set as a FIXED SENDER and this device (i.e. the fixed sender) should be set as FIXED RECEIVER.
I would expect it to be just the other way around.
Same comment for the receive message file (Arduino_e22_08_receiveMessage.ino) where the configurations are reversed and saying that this device (i.e. the receiver) should be configured as a FIXED SENDER.
I am aware that the library is for the E22 series but I think it can be used with the E220 in my case as I only need a simple point-to-point fixed TX/RX link.
Maximum packet size of 200 is OK for me and I don’t need a network ID.
One major difference is that M1 & M0 both need to be “1” for configuring the device instead of “1” and “0” respectively for the E22 series.
I still need to check if there are other differences in the various registers bit settings.
I came across a discrepancy in the comments in the the E220 example file 01_setConfiguration.ino
The pin assignments for an Arduino Nano in the top of the comments do not match the pin assignments in the lines below that can be uncommented. See attached screen capture.
I presume that for an Arduino Nano I/O pins 6, 2 & 4 are used for AUX, M0 & M1 respectively in your library, right?
By the way, I presume I can use other I/O pins if it simplifies the PCB routing and change my source file accordingly, right?
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.