I’m encountering some issues with the E22-900T22S modules.
Here’s some context:
I have two boards:
– The first board (Flag) is equipped with an ESP32.
– The second board (Master) is equipped with an ESP32-S3.
The Flag board works correctly; I’m able to successfully send and receive data between Flag boards.
However, sending data from the Master to the Flag board isn’t working.
When retrieving the module configuration for the first time, I get error code 11: “Save mode not recognized.” This issue occurs only during the initial attempt.
Afterward, when configuring the E22 module, I receive a “success” message, and retrieving the configuration afterward returns the correct settings. Nevertheless, I’m uncertain whether the returned values are reliable.
Despite using the same NET-ID, Channel, and properly setting the LOW_ADDRESS of the receiver, I’m unable to send data from the Master to the Flag board in fixed transmission mode. The transmission returns “success” on the Master, but the Flag board doesn’t receive anything.
Here are my questions:
– What exactly does the error “Save mode not recognized” mean?
– Could my issue be hardware-related?
– I’m not currently using any pull-up resistors. Could this cause problems?
– Can the length of the AUX, RX, and TX traces affect the transmission?
For reference, here are the trace lengths on my setup:
– AUX: 21.6 mm
– LORA_RX: 34.6 mm
– LORA_TX: 39.2 mm
I’ve already tested with a new Ebyte module, but the issue persists.
I can share my code if needed.
At the beginning of the received frame, I noticed an unexpected 0xFC byte:
Serial available before read: 13
Received bytes: FC C1 00 09 00 06 12 62 00 04 43 00
Available buffer: 12, Structure size: 12
This extra byte (0xFC) shifts the configuration data by one byte. It’s consistently the same byte (0xFC), leading me to believe the issue is software-related, possibly with the ESP32-S3.
I verified this by capturing the frame with an FTDI device. The E22 module indeed sends the correct frame: C1 00 09 00 06 12 62 00 04 43 00 00, without the extra 0xFC.
I’m unsure about the cause, but I’ll continue investigating further tomorrow.
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.
Welcome to Our Family!
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.