hey – I have a problem reading the configuration from my device EBYTE E220-900-T22D with arduino nano. The only thing displayed on my serial monitor is the following:
also when I try to set the configuration, there is a slight problem because I get the unsuccess information, but here it seems to me that the code partially works because after changing the transmitter frequency to a different frequency than the receiver one, the receiver stops reading the data.
Success
1
Success
1
Save mode returned not recognized!
11
Success
1
I checked with the ebyte configurator (using FTDI232) and was able to load and save configurations for all my ebyte modules . I created a simple code using an array of bytes representing config: byte loraConfig[] = {0xc0, 0x00, 0x09, 0x00, 0x03, 0x62, 0x05, 0x00, 0x03, 0x00, 0x00, 0x10};. With this code in my arduino ide, I can change my LoRa parameters. Now I will implement load configurations. I will let You know if it works…
Hi Renzo, finally I did it. My code is receiving all 12 bytes as a hex. One thing is interesting – when I configure my config as:
byte loraConfig[] = {0xc0, 0x00, 0x09, 0x00, 0x03, 0x62, 0xc5, 0x00, 0x03, 0x00, 0x00, 0x10};
Ahh! Yes, I already found that some models of E220 have this “issue,” but they’re working correctly.
Sometimes, there is a power supply problem. In your case, it’s more rare, but you can ignore that response.
Bye Renzo
Hi, just ready implement get config – and start to make set config. Regarding C1 – this is not an issue. Just founded in the manual that this is normal procedure after reading config from lora.
hey Renzo, I have currently implemented a library that reads and changes values for e220-900T22D. However, I don’t know how to run RSSI. Should I implement code on the transmitter and receiver to enable this function? Isn’t this CHANNEL RSSI? How is signal strength information transmitted?
Hi Adam,
You are right. The C1 is correct. It is also in the library. I verified that but also checked the other set that must be respected; if you receive that message, you have something wrong or some noise with the device setting. But if it works for the other operation, we will never discover what it is :D.
Hi, Renzo I try out how to get RSSI data but I would like to do it my self (not using library). Can You check my code? I set channel RSSI mode as enable.
#include
// Pin definitions
#define LORA_RX 10
#define LORA_TX 11
#define LORA_M0 7
#define LORA_M1 8
char DataRSSI[10];
String command = "C0 C1 C2 C3";
// Initialize SoftwareSerial for communication with the LoRa module
SoftwareSerial loraSerial(LORA_RX, LORA_TX);
void setup() {
// Set pin modes
pinMode(LORA_M0, OUTPUT);
pinMode(LORA_M1, OUTPUT);
// Set M0 and M1 pins to receive mode
digitalWrite(LORA_M0, LOW);
digitalWrite(LORA_M1, LOW);
// Initialize serial communication
Serial.begin(9600);
loraSerial.begin(9600);
Serial.println("LoRa Receiver is ready.");
}
void loop() {
// Check if data is available for reading
if (loraSerial.available()) {
String message = "";
// Read data
while (loraSerial.available()) {
char c = loraSerial.read();
message += c;
delay(10); // Small delay for stable reception
}
// Send command (if necessary)
loraSerial.println(command);
// Read RSSI (if RSSI is sent as 4 bytes)
if (loraSerial.available() >= 4) { // Check if at least 4 bytes are available
loraSerial.readBytes(DataRSSI, 4);
Serial.print("RSSI: ");
Serial.println(String(DataRSSI)); // Convert char array to String
}
// Display the received message
Serial.println("Received message: " + message);
}
}
Here’s the situation:
RSSI Value Not Showing:
The code should be reading RSSI values when at least 4 bytes are available. Despite enabling RSSI on the receiver, I’m not seeing any RSSI values in the output.
Transmitter Details:
I have a transmitter sending a simple “hello” message. The receiver successfully receives this message, but it doesn’t provide the RSSI.
Configuration Check:
I’ve set the M0 and M1 pins for receive mode based on the module’s documentation, but I’m not sure if this is correct.
Communication Confirmation:
The receiver does get the transmitted message, so it seems like communication is working fine otherwise.
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.