Closed krishank652 closed 5 months ago
This library will definitely NOT work with these newer E220 series units. This library is for older units (E32, E51, E44). The programming byte definition is slightly different between the E220 and what this library expects
Answer No.1: What are you trying to do 1) change settings once then use or 2) change settings during run time?
Answer No.2: Key is a new concept for encryption found only in these new E220 units.
Answer No.3: I'm not sure what you are trying to do. have one sender many receivers, many senders one receiver, other?
Question No.4: Depends. do you want to change the configuration during run time? If so you will to control these lines otherwise, I think you can just pull them low
Question No.5: This doesn't surprise me. This library is reading and writing bytes per a different format. I'm guessing when you SetChannel, it's not really setting the channel since the lib is sending programming data in a different format. The PrintParameters call will print something, but it surely is not what is on the units SaveParameters saves something but since this lib is sending the programming bytes that is not consistent with the E220, who knows what it's sending
Have a look at the rate parameters for the E220 (which is NOT what this library is written for) UART is 7-6-5 bits
Look at the E49 (which is what this library is written for)
UART is bits 5-4-3
Dear @KrisKasprzak
I want to express my gratitude for providing the library. Thankyou. Your work is greatly appreciated, and it's been instrumental in getting my Ebyte E220-400T22S module up and running.
However, I'm encountering some difficulties in constructing a proper prototype project. Could you please assist me in resolving these issues?
Below are my inquiries. I would greatly appreciate your expert advice. Thank you.
Question No.1: If I utilize this library, do I still need to configure the LoRa parameters using the software provided by the manufacturer, Ebyte? (Please refer to the screenshot below for the software interface.)
Question No.2:
Through software we can settings for Address, Channel, and Key. Are these settings are same to those in the library, specifically:
If not, then how should I go about addressing each device, or what are the limitations regarding addressing? Please advise.
Question No.3: I noticed in the manual that there's a Fixed Transmission Mode that allows communication with predefined receivers, where the transmitter holds the receiver's address. In this mode, even with multiple devices nearby, the modules should not interfere with each other and only contact the predefined transmitters and receivers. How can I configure this using the library? I'm struggling to grasp this concept and would appreciate your guidance. (Please refer to the screenshot below for the Fixed Transmission.)
Question No.4: Is it possible to forego the utilization of the M0 and M1 terminals? I'm considering grounding these terminals with puting resistance 300 ohms in series , as suggested in the manual, if they are unnecessary.
Question No.5: Could you please review the code I've provided below? I've set different parameters for both the transmitter (Tx) device and the receiver (Rx) device. However, they are still communicating, which is perplexing to me. I am confused regarding the addressing aspect. Your assistance in this matter would be greatly appreciated.
Transmitter Code for Send:
Debug for TX:
Receiver code for Receive:
Debug for Receiver:
Your assistance in clarifying these points would be immensely helpful. Thank you for your support.
Best regards, Krishan
Software UI Screenshot:
Fixed Transmission Screenshot:
My Device: Connections Details: