Here is an overview of the post:<\/p>\r\n
- \r\n
- Legal – please note<\/a><\/li>\r\n
- What is LoRa, LoRaWAN and LPWAN?<\/a><\/li>\r\n
- LoRA Modules<\/a><\/li>\r\n
- Ebyte LoRa Modules<\/a>\r\n
- \r\n
- Overview<\/a><\/li>\r\n
- Naming<\/a><\/li>\r\n
- Technical Data (Example E220-900T22D)<\/a><\/li>\r\n
- Pinout LoRa E220, E22, E32 Series<\/a><\/li>\r\n<\/ul>\r\n<\/li>\r\n
- Libraries for the Ebyte E220, E22 and E32 Series<\/a><\/li>\r\n
- Circuit for the Arduino Nano<\/a><\/li>\r\n
- How to make Settings<\/a>\r\n
- \r\n
- Configuration Sketch using the E220 Module Series<\/a><\/li>\r\n
- Configuration Sketches for the E22 and E32 series<\/a><\/li>\r\n
- Settings in Detail<\/a><\/li>\r\n<\/ul>\r\n<\/li>\r\n
- Response Container and Response Status<\/a><\/li>\r\n
- Transparent Transmission Mode<\/a><\/li>\r\n
- Sending and receiving Structures<\/a><\/li>\r\n
- Fixed Transmission Mode<\/a><\/li>\r\n
- RSSI Received Signal Strength Indicator<\/a><\/li>\r\n
- Using Wake On Radio (WOR)<\/a><\/li>\r\n
- Waking up the MCU with WOR<\/a><\/li>\r\n
- Range Test<\/a><\/li>\r\n
- Appendices – Transceiver Sketches with Settings for E220, E22, E32<\/a><\/li>\r\n<\/ul>\r\n\n
Legal – please note!<\/h2>\n\n
Important to know<\/strong>:<\/p>\r\n
- \r\n
- Radio transmission is regulated by law in almost every country in the world, e.g. regarding the permitted frequencies, the transmission power or the duty cycle (percentage of the actual transmission time).<\/li>\r\n
- Not everything you can buy in your country can be used without restrictions – and some things can’t be used at all!<\/li>\r\n<\/ul>\r\n
In Germany, the rules for radio are set by the Federal Network Agency. You can find the relevant details here<\/a> in the section “Funkanlagen mit geringer Reichweite”. Hobbyists mainly use the frequencies around 433 MHZ, 868 MHz, 915 MHz and 2.4 GHz – but they are not free of restrictions. You are responsible for complying with the regulations in your country<\/strong>.<\/p>\r\n\n
What is LoRa, LoRaWAN and LPWAN?<\/h2>\n\n
If you are dealing with LoRa, you will also come across the terms LoRaWAN and LPWAN. LoRa stands for Long<\/strong> Range<\/strong>, i.e. it is a radio technology for comparatively long distances. LoRa (like Sigfox<\/a>) belongs to the group of LPWAN radio technologies, which in turn is the abbreviation for Low-Power Wide Area Network. This name thus contains a second characteristic of this technology, namely its low-energy consumption. While LoRa refers to the special radio technology, LoRaWAN is a communication protocol based on it.<\/p>\r\n
I am neither a physicist nor a radio engineer. That’s why I prefer to hold back on explaining exactly how LoRa works. Just this much: It is a special modulation technology that achieves the long-range and low-energy consumption. The data transfer rates are comparatively low.<\/p>\r\n\n
LoRa Modules <\/h2>\n\n
Many different LoRa modules are offered in popular online stores such as Amazon or AliExpress. These also include ready-made solutions, e.g. ESP32-based boards with OLED displays. Originally, I had planned to give a broader overview of common modules and libraries. However, I then realized that the topic is simply too extensive to cover everything in one post. I will therefore initially limit myself to the E220, E22 and E32 series from Ebyte. They are close relatives that can be programmed in almost the same way. I may look at other modules in a later post.<\/p>\r\n\n
Ebyte LoRa Modules<\/h2>\n\n
Overview<\/h3>\n\n
Ebyte, more precisely Chengdu Ebyte Electronic Technology Co. Ltd<\/a>, offers various LoRa modules. If you are looking for specific models, take a look here<\/a>. I have summarized the most important differences between the module series here:<\/p>\r\n\n
![\"Overview](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2024\/03\/e220_e32_e22_comparison-2-1024x514.png\")
<\/a>Overview of the E220, E22 and E32 series<\/figcaption><\/figure>\n\n The modules all have the same pinout and are very similar in operation. <\/p>\r\n
An overview of the SX1262, SX1276 and SX1278 chips can be found here<\/a>. All chips and modules have their advantages and disadvantages.<\/p>\r\n\n
Naming<\/h3>\n\n
The modules are named according to the scheme Eaaa-bbb<\/em>Tcc<\/em>d<\/em>, e.g. E220-900T22D. The parameters are: <\/p>\r\n
- \r\n
- aaa: the “family name”,<\/li>\r\n
- bbb: represents the radio frequency,<\/li>\r\n
- cc: represents the signal strength in dBm,<\/li>\r\n
- d: stands for the design (DIP or SMD).<\/li>\r\n<\/ul>\r\n
Here, as an example, is an overview of some representatives of the E220 series:<\/p>\r\n\n
![\"Model](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2024\/03\/E220_series-1024x344.png\")
<\/a>Model overview of the LoRa E220 series (source: E220-900T22D data sheet)<\/figcaption><\/figure>\n\n Technical Data (Example E220-900T22D)<\/h3>\n\n
You can find data sheets and manuals on the Chengdu Ebyte website<\/a>. As an example, I have the technical data of the E220-900T22D model for you here:<\/p>\r\n\n
![\"Technical](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2024\/03\/e220_tech_data_1.png\")
<\/a>Technical data E220-900T22D LoRa module (source: E220-900T22D data sheet)<\/figcaption><\/figure>\n\n I found a data sheet for the same module elsewhere, but with slightly different information on the optimum voltage supply:<\/p>\r\n\n
![\"Version](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2024\/03\/e220_tech_data_2-1.png\")
<\/a>Version 2 of the E220-900T22D LoRa module.<\/figcaption><\/figure>\n\n If in doubt, try out whether you achieve better results with 5 volts. However, it is important to note that not all pins can handle 5 volts. For 5 volt MCUs, you should therefore use level shifters or voltage dividers.<\/p>\r\n\n
Pinout LoRa E220, E22, E32 Series<\/h3>\n\n
![\"Pinout](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2024\/03\/pins_e220_lora-1024x189.jpg\")
<\/a>Pinout LoRa E220, E22 and E32<\/figcaption><\/figure>\n\n - \r\n
- GND \/ VCC<\/strong>: Power supply<\/li>\r\n
- AUX<\/strong>: Indicates the status of the data buffers for sending and receiving and is used for the self-check.<\/li>\r\n
- RX \/ TX<\/strong>: Serial communication<\/li>\r\n
- M0 \/ M1 (E220)<\/strong>: Control of the four operating modes:\r\n
- \r\n
- M0 = LOW, M1 = LOW<\/strong>: Normal mode<\/li>\r\n
- M0 = HIGH, M1 = LOW<\/strong>: WOR Transmitter<\/li>\r\n
- M0 = LOW, M1 = HIGH<\/strong>: WOR Receiver<\/li>\r\n
- M0 = HIGH, M1 = HIGH<\/strong>: Deep sleep<\/li>\r\n<\/ol>\r\n<\/li>\r\n
- M0 \/M1 (E22)<\/strong>: Control of the four operating modes:\r\n
- \r\n
- M0 = LOW, M1 = LOW<\/strong>: Normal mode<\/li>\r\n
- M0 = HIGH, M1 = LOW<\/strong>: WOR mode (transmitter\/receiver)<\/li>\r\n
- M0 = LOW, M1 = HIGH<\/strong>: Configuration mode<\/li>\r\n
- M0 = HIGH, M1 = HIGH<\/strong>: Deep sleep<\/li>\r\n<\/ol>\r\n<\/li>\r\n
- M0 \/ M1 (E32)<\/strong>: Control of the four operating modes:\r\n
- \r\n
- M0 = LOW, M1 = LOW<\/strong>: Normal mode<\/li>\r\n
- M0 = HIGH, M1 = LOW<\/strong>: Wake-up mode (transmitter)<\/li>\r\n
- M0 = LOW, M1 = HIGH<\/strong>: Power saving<\/li>\r\n
- M0 = HIGH, M1<\/strong> = HIGH<\/strong>: Sleep<\/li>\r\n<\/ol>\r\n<\/li>\r\n<\/ul>\r\n\n
Libraries for the Ebyte E220, E22 and E32 Series<\/h2>\n\n
I selected the libraries of Renzo Mischianti<\/a> to control the modules. You can download them here from GitHub:<\/p>\r\n
- \r\n
- EByte_LoRa_E220_Series_Library<\/a><\/li>\r\n
- EByte_LoRa_E22_Series_Library<\/a><\/li>\r\n
- LoRa_E32_Series_Library<\/a><\/li>\r\n<\/ul>\r\n
… or install via the library manager of the Arduino IDE.<\/p>\r\n
In addition, the industrious Renzo Mischianti has created a multipart tutorial for each of the module series. Here are the links to the first parts: E220-Tutorial<\/a>, E22-Tutorial<\/a>, E32-Tutorial<\/a>.<\/p>\r\n
My motivation for writing my own article was to summarize things a little more compactly and to compare the module series. However, it is definitely worth taking a look at the tutorials. They offer a lot of additional information, such as example sketches and circuit diagrams for other boards.<\/p>\r\n
The tutorials and libraries for the various series are structured in the same way. This means you can quickly find your way around if you change the module series.<\/p>\r\n\n
Circuit for the Arduino Nano <\/h2>\n\n
In this article, I use the classic Arduino Nano as the controlling board. I connected it to the E220 module as follows (identical for E22 and E32):<\/p>\r\n
\n![\"Connection](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2024\/03\/e220_lora_arduino_connect.png\")
<\/a>Connection of the E220 module to the Arduino Nano<\/figcaption><\/figure>\n<\/div>\n A few comments on this:<\/p>\r\n
- \r\n
- If you do not want to use the WOR (Wake On Radio) or power-down modes, you can connect M0 and M1 to GND.<\/li>\r\n
- In principle, you can also leave AUX unconnected. In this case, the microcontroller does not know when the data transfer is complete, but the library provides a sufficient waiting time.<\/li>\r\n
- When using a 5 volt board, you must use a level shifter or a voltage divider (e.g. 2 k\u03a9 \/ 1 k\u03a9) for connecting M0, M1, RX to the board pins.<\/li>\r\n
- AUX, RX and TX require a pull-up resistor.<\/li>\r\n
- Example circuits for other MCU boards can be found in the tutorials by Renzo Mischianti.<\/li>\r\n
- The antennas for the E220-900T22D and E32-433T30D modules I used were special versions with a magnetic base for 868 MHz and 433 MHz. These are available for < \u20ac10 in online stores.<\/li>\r\n<\/ul>\r\n\n
This is what my setup looked like on the breadboard:<\/p>\r\n\n
![\"LoRa](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2024\/03\/Lora_E220_Arduino_Nano-1024x657.png\")
<\/a>LoRa E220 module connected to an Arduino Nano on the breadboard<\/figcaption><\/figure>\n\n How to make Settings<\/h2>\n\n
Configuration Sketch using the E220 Module Series<\/h3>\n\n
The libraries are equipped with separate example sketches for setting up and operating the modules. Use setConfiguration.ino to make the settings, and getConfiguration.ino to query them. These settings are retained even if the power supply is disconnected, provided you select the parameter WRITE_CFG_PWR_DWN_SAVE when saving the configuration <\/strong>(line 62 in the next sketch).<\/p>\r\n
When you open setConfiguration.ino<\/a>, you may be overwhelmed by its size. However, most of it is commented out, and many things are repeated. The upper section contains various examples of object creation for different boards. The middle section contains ready-made configuration examples that you can easily uncomment. At the end you will find the functions for outputting the settings. <\/p>\r\n\n
I have reduced setConfiguration.ino (E220 module) to the essentials for use on an Arduino Nano. But I have also added a few lines:<\/p>\r\n
- \r\n
- Lines 1 to 5 are used to output the correct frequency. Just uncomment the line with the correct frequency range.<\/li>\r\n
- Lines 6 and 7 are relevant for selecting the signal strength.<\/li>\r\n
- Line 8 ensures that the settings are output in detail.<\/li>\r\n
- Lines 57 and 58 allow you to encrypt your messages individually.<\/li>\r\n<\/ul>\r\n\n\r\n
\/\/ #define FREQUENCY_433 \/\/ default value without set \r\n\/\/ #define FREQUENCY_170\r\n\/\/ #define FREQUENCY_470\r\n#define FREQUENCY_868\r\n\/\/ #define FREQUENCY_915\r\n\/\/ #define E220_22 \/\/ default value without set \r\n\/\/ #define E220_30 \/\/ uncomment in case you use an E220...T30D or E220...T30S\r\n#define LoRa_E220_DEBUG \/\/ for printing the settings\r\n#include \"LoRa_E220.h\"\r\n\r\nSoftwareSerial mySerial(4, 5); \/\/ Arduino RX <-- e220 TX, Arduino TX --> e220 RX\r\nLoRa_E220 e220ttl(&mySerial, 3, 7, 6); \/\/ AUX M0 M1\r\n\/\/ LoRa_E220 e220ttl(4, 5, 3, 7, 6); \/\/ alternative function to create the LoRa_E220 object\r\n\r\nvoid printParameters(struct Configuration configuration);\r\nvoid printModuleInformation(struct ModuleInformation moduleInformation);\r\n\r\nvoid setup() {\r\n Serial.begin(9600);\r\n while(!Serial){};\r\n delay(500);\r\n\r\n Serial.println();\r\n\r\n\r\n \/\/ Startup all pins and UART\r\n e220ttl.begin();\r\n\r\n ResponseStructContainer c;\r\n c = e220ttl.getConfiguration();\r\n \/\/ It's important get configuration pointer before all other operation\r\n Configuration configuration = *(Configuration*) c.data;\r\n Serial.println(c.status.getResponseDescription());\r\n Serial.println(c.status.code);\r\n\r\n printParameters(configuration);\r\n\r\n\/\/\t----------------------- DEFAULT TRANSPARENT ----------------------- \r\n configuration.ADDL = 0x02; \/\/ Low byte of address\r\n configuration.ADDH = 0x00; \/\/ High byte of address\r\n\r\n configuration.CHAN = 18; \/\/ 868 MHz for Exxx-900 modules, choose 23 for Exxx-400 to set 433 MHz \r\n\r\n configuration.SPED.uartBaudRate = UART_BPS_9600; \/\/ Serial baud rate\r\n configuration.SPED.airDataRate = AIR_DATA_RATE_010_24; \/\/ Air baud rate\r\n configuration.SPED.uartParity = MODE_00_8N1; \/\/ Parity bit\r\n\r\n configuration.OPTION.subPacketSetting = SPS_200_00; \/\/ Packet size\r\n configuration.OPTION.RSSIAmbientNoise = RSSI_AMBIENT_NOISE_DISABLED; \/\/ Need to send special command\r\n configuration.OPTION.transmissionPower = POWER_22; \/\/ Device power\r\n\r\n configuration.TRANSMISSION_MODE.enableRSSI = RSSI_DISABLED; \/\/ Enable RSSI info\r\n configuration.TRANSMISSION_MODE.fixedTransmission = FT_TRANSPARENT_TRANSMISSION; \/\/ Transmission mode\r\n configuration.TRANSMISSION_MODE.enableLBT = LBT_DISABLED; \/\/ Check interference\r\n configuration.TRANSMISSION_MODE.WORPeriod = WOR_2000_011; \/\/ WOR timing\r\n\r\n configuration.CRYPT.CRYPT_H = 0x00; \/\/ encryption high byte, default: 0x00\r\n configuration.CRYPT.CRYPT_L = 0x00; \/\/ encryption low byte, default: 0x00\r\n\r\n \/* Set configuration changed and set to hold the configuration; chose \r\nWRITE_CFG_PWR_DWN_LOSE to not save the configuration permanently *\/\r\n ResponseStatus rs = e220ttl.setConfiguration(configuration, WRITE_CFG_PWR_DWN_SAVE);\r\n Serial.println(rs.getResponseDescription());\r\n Serial.println(rs.code);\r\n\r\n c = e220ttl.getConfiguration();\r\n \/\/ It's important get configuration pointer before all other operation\r\n configuration = *(Configuration*) c.data;\r\n Serial.println(c.status.getResponseDescription());\r\n Serial.println(c.status.code);\r\n\r\n printParameters(configuration);\r\n c.close();\r\n}\r\n\r\nvoid loop() {\r\n\r\n}\r\nvoid printParameters(struct Configuration configuration) {\r\n DEBUG_PRINTLN(\"----------------------------------------\");\r\n\r\n DEBUG_PRINT(F(\"HEAD : \")); DEBUG_PRINT(configuration.COMMAND, HEX);DEBUG_PRINT(\" \");DEBUG_PRINT(configuration.STARTING_ADDRESS, HEX);DEBUG_PRINT(\" \");DEBUG_PRINTLN(configuration.LENGHT, HEX);\r\n DEBUG_PRINTLN(F(\" \"));\r\n DEBUG_PRINT(F(\"AddH : \")); DEBUG_PRINTLN(configuration.ADDH, HEX);\r\n DEBUG_PRINT(F(\"AddL : \")); DEBUG_PRINTLN(configuration.ADDL, HEX);\r\n DEBUG_PRINTLN(F(\" \"));\r\n DEBUG_PRINT(F(\"Chan : \")); DEBUG_PRINT(configuration.CHAN, DEC); DEBUG_PRINT(\" -> \"); DEBUG_PRINTLN(configuration.getChannelDescription());\r\n DEBUG_PRINTLN(F(\" \"));\r\n DEBUG_PRINT(F(\"SpeedParityBit : \")); DEBUG_PRINT(configuration.SPED.uartParity, BIN);DEBUG_PRINT(\" -> \"); DEBUG_PRINTLN(configuration.SPED.getUARTParityDescription());\r\n DEBUG_PRINT(F(\"SpeedUARTDatte : \")); DEBUG_PRINT(configuration.SPED.uartBaudRate, BIN);DEBUG_PRINT(\" -> \"); DEBUG_PRINTLN(configuration.SPED.getUARTBaudRateDescription());\r\n DEBUG_PRINT(F(\"SpeedAirDataRate : \")); DEBUG_PRINT(configuration.SPED.airDataRate, BIN);DEBUG_PRINT(\" -> \"); DEBUG_PRINTLN(configuration.SPED.getAirDataRateDescription());\r\n DEBUG_PRINTLN(F(\" \"));\r\n DEBUG_PRINT(F(\"OptionSubPacketSett: \")); DEBUG_PRINT(configuration.OPTION.subPacketSetting, BIN);DEBUG_PRINT(\" -> \"); DEBUG_PRINTLN(configuration.OPTION.getSubPacketSetting());\r\n DEBUG_PRINT(F(\"OptionTranPower : \")); DEBUG_PRINT(configuration.OPTION.transmissionPower, BIN);DEBUG_PRINT(\" -> \"); DEBUG_PRINTLN(configuration.OPTION.getTransmissionPowerDescription());\r\n DEBUG_PRINT(F(\"OptionRSSIAmbientNo: \")); DEBUG_PRINT(configuration.OPTION.RSSIAmbientNoise, BIN);DEBUG_PRINT(\" -> \"); DEBUG_PRINTLN(configuration.OPTION.getRSSIAmbientNoiseEnable());\r\n DEBUG_PRINTLN(F(\" \"));\r\n DEBUG_PRINT(F(\"TransModeWORPeriod : \")); DEBUG_PRINT(configuration.TRANSMISSION_MODE.WORPeriod, BIN);DEBUG_PRINT(\" -> \"); DEBUG_PRINTLN(configuration.TRANSMISSION_MODE.getWORPeriodByParamsDescription());\r\n DEBUG_PRINT(F(\"TransModeEnableLBT : \")); DEBUG_PRINT(configuration.TRANSMISSION_MODE.enableLBT, BIN);DEBUG_PRINT(\" -> \"); DEBUG_PRINTLN(configuration.TRANSMISSION_MODE.getLBTEnableByteDescription());\r\n DEBUG_PRINT(F(\"TransModeEnableRSSI: \")); DEBUG_PRINT(configuration.TRANSMISSION_MODE.enableRSSI, BIN);DEBUG_PRINT(\" -> \"); DEBUG_PRINTLN(configuration.TRANSMISSION_MODE.getRSSIEnableByteDescription());\r\n DEBUG_PRINT(F(\"TransModeFixedTrans: \")); DEBUG_PRINT(configuration.TRANSMISSION_MODE.fixedTransmission, BIN);DEBUG_PRINT(\" -> \"); DEBUG_PRINTLN(configuration.TRANSMISSION_MODE.getFixedTransmissionDescription());\r\n\r\n\r\n DEBUG_PRINTLN(\"----------------------------------------\");\r\n}\r\nvoid printModuleInformation(struct ModuleInformation moduleInformation) {\r\n Serial.println(\"----------------------------------------\");\r\n DEBUG_PRINT(F(\"HEAD: \")); DEBUG_PRINT(moduleInformation.COMMAND, HEX);DEBUG_PRINT(\" \");DEBUG_PRINT(moduleInformation.STARTING_ADDRESS, HEX);DEBUG_PRINT(\" \");DEBUG_PRINTLN(moduleInformation.LENGHT, DEC);\r\n\r\n Serial.print(F(\"Model no.: \")); Serial.println(moduleInformation.model, HEX);\r\n Serial.print(F(\"Version : \")); Serial.println(moduleInformation.version, HEX);\r\n Serial.print(F(\"Features : \")); Serial.println(moduleInformation.features, HEX);\r\n Serial.println(\"----------------------------------------\");\r\n}<\/pre>\r\n<\/p>\r\n<\/div>\r\n\n
When trying things out, it can be a bit annoying to adjust the settings via a separate sketch, even if this saves resources. Perhaps you would prefer to make the settings directly in the sketches that you also use for control? And perhaps you would like to have an overview of all the setting options? Then take a look at Appendix 1<\/a> for the E220 series.<\/p>\r\n\n
Configuration Sketches for the E22 and E32 Series<\/h3>\n\n
In Appendix 2<\/a> and Appendix 3<\/a> you will find the counterparts to Appendix 1 for the E22 and E32 series respectively. The sketches also provide a good overview of the differences between the three module series.<\/p>\r\n\n
Settings in Detail <\/h3>\n\n
Address and Channel (configuration)<\/h4>\n\n
Each LoRa module has an address, which is made up of the higher byte
ADDH<\/code> and the lower byteADDL<\/code>. This allows you to set 65536 addresses. The address is assigned viaconfiguration.ADDL = ...<\/code> orconfiguration.ADDH = ...<\/code>.<\/p>\r\nThe modules I tested cover the frequencies 850 – 930 MHz and 410 to 493 MHz. Fine adjustment is made via the channel. The formula for the frequency \u03bd is<\/p>\r\n\n
<\/p>\r\n
<\/span> <\/span>
![\"\[](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/ql-cache\/quicklatex.com-d9f59811c2590eac059781d3714981cd_l3.png\" "\\"Rendered")
<\/p><\/p>\r\n\n<\/span> <\/span>
![\"\[](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/ql-cache\/quicklatex.com-2baff5daf0d7fc991550d9b45a8122bb_l3.png\" "\\"Rendered")
<\/p><\/p>\r\n\r\n\nFor the Exxx-900 modules, use
configuration.CHAN = 18<\/code> to set the frequency to 868.125 MHz. With the Exxx-400 models, you set 433.125 MHz withconfiguration.CHAN = 23<\/code>.<\/p>\r\nThere is a certain risk that you will transmit on a frequency that is not permitted in your country if you make the wrong selection. I’m just saying.<\/p>\r\n
A check with a tinySA Spectrum Analyzer<\/a> showed a good match with the target frequency within the accuracy of this device. Here is the result for channels 0, 18 and 80 of an E220-900T22D module:<\/p>\r\n\n
![\"Checking](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2024\/03\/frequency_check_e220_900_ebyte-1024x260.png\")
<\/a>Checking the transmission frequency for channel 0, 18 and 80 -> 850.13 \/ 868.20 \/ 930.12 MHz<\/figcaption><\/figure>\n\n The principle of channel setting is identical for all modules.<\/p>\r\n\n
Transmission Rate and Options (configuration.SPED)<\/h4>\n\n
You can set the following parameters for UART communication and data transmission over the air (example E220):<\/p>\r\n
- \r\n
- uartBaudRate<\/strong>: Baud rate UART_BPS_xxx
\r\n- \r\n
- xxx = 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200<\/li>\r\n<\/ul>\r\n<\/li>\r\n
- airDataRate<\/strong>: Data rate for radio transmission AIR_DATA_RATE_xxx\r\n
- \r\n
- AIR_DATA_RATE_010_24: 2.4 kbit\/s (default)<\/li>\r\n
- AIR_DATA_RATE_011_48: 4.8 kbit\/s<\/li>\r\n
- AIR_DATA_RATE_100_96: 9.6 kbit\/s<\/li>\r\n
- AIR_DATA_RATE_101_192: 19.2 kbit\/s<\/li>\r\n
- AIR_DATA_RATE_110_384: 38.4 kbit\/s<\/li>\r\n
- AIR_DATA_RATE_111_625: 62.5 kbit\/s<\/li>\r\n<\/ul>\r\n<\/li>\r\n
- uartParity<\/strong>: Parity MODE_xxx;\r\n
- \r\n
- MODE_00_8N1: none (default)<\/li>\r\n
- MODE_01_8O1: odd<\/li>\r\n
- MODE_10_8E1: even<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n\n
The options for the airDataRate differ for the E22 and 32 series. See Appendix 2<\/a> and 3<\/a>.<\/p>\r\n
Regarding the data rate via radio: the lower the data rate, the higher the maximum range.<\/p>\r\n\n
Further Transmission Options (configuration.OPTION)<\/h4>\n\n
Further options (example E220):<\/p>\r\n\n
- \r\n
- subPacketSetting<\/strong>: Maximum data packet size, i.e. the maximum length of your message that you can send continuously in one piece.
\r\n- \r\n
- SPS_200_00: 200 bytes<\/li>\r\n
- SPS_128_01: 128 bytes<\/li>\r\n
- SPS_064_10: 64 bytes<\/li>\r\n
- PLC_032_11: 32 bytes<\/li>\r\n<\/ul>\r\n<\/li>\r\n
- RSSIAmbientNoise<\/strong>: RSSI (Received Signal Strength Indicator) Ambient Noise enable
\r\n- \r\n
- RSSI_AMBIENT_NOISE_DISABLED: Function is switched off<\/li>\r\n
- RSSI_AMBIENT_NOISE_ENABLED: Function is switched on<\/li>\r\n<\/ul>\r\n<\/li>\r\n
- transmissionPower<\/strong>: Transmission power POWER_xx with xx = power in dbm. The setting options depend on the model you are using.
\r\n- \r\n
- xx for E220….22D: 22, 17, 13, 10<\/li>\r\n
- xx for E220….30D: 30, 27, 24, 21<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n\n
The subPacketSetting and transmissionPower settings differ for the E22 and E32 series (see Appendix 2<\/a> and 3<\/a>). RSSIAmbientNoise is not available on the E32 module.<\/p>\r\n\n
Mode Settings (configuration.TRANSMISSION_MODE)<\/h4>\n\n
I will come back to some of these settings later. Here are the options for the E220 series:<\/p>\r\n\n
- \r\n
- enableRSSI<\/strong>: Signal strength information (Received Signal Strength Indication)
\r\n- \r\n
- RSSI_DISABLED: disabled<\/li>\r\n
- RSSI_ENABLED: enabled<\/li>\r\n<\/ul>\r\n<\/li>\r\n
- fixedTransmission<\/strong>: Transmission mode\r\n
- \r\n
- FT_FIXED_TRANSMISSION: Transmission to a specific address \/ channel.<\/li>\r\n
- FT_TRANSPARENT_TRANSMISSION: Transmission to all modules with identical address and channel.<\/li>\r\n<\/ul>\r\n<\/li>\r\n
- enableLBT<\/strong>: LBT (Listen Before Talk) is a function that causes the module to wait up to two seconds for a favorable moment (with low interference) before transmitting.
\r\n- \r\n
- LBT_DISABLED: Function disabled<\/li>\r\n
- LBT_ENABLED: Function enabled<\/li>\r\n<\/ul>\r\n<\/li>\r\n
- WORPeriod<\/strong>: WOR (Wake On Radio) period WOR_xxx_yyy with xxx = wake-up period in milliseconds\r\n
- \r\n
- xxx_yyy = 500_000, 1000_001, 1500_010, 2000_011, 2500_100, 3000_101, 3500_110, 4000_111<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n
The WORPeriod parameter needs a little more explanation. This is the period after which the receiver wakes up to check whether a message is coming. Of course, the sender does not know when the receiver is awake and therefore sends a “preamble” with the length of the wake-up period. The WOR receiver then remains awake until the actual message is received. For this reason, the WOR Receiver and the WOR Transmitter must have the same WORPeriod set.<\/p>\r\n\n
The WORPeriod is called wirelessWakeUpTime when using the E32 series. The selectable periods are also different. The enableRSSI and enableLBT settings are not available on the E32 modules.<\/p>\r\n\n
Encryption (configuration.CRYPT)<\/h4>\n\n
All modules encrypt the messages. However, only the E22 and E220 series modules allow individual encryption. To do this, you define values for the two bytes CRYPT_H and CRYPT_L. The setting must, of course, be identical for the transmitter and receiver. A fixed encryption setting is used on the E32.<\/p>\r\n\n
Response Container and Response Status<\/h2>\n\n
Before we finally come to the pratical part, I need to explain two structures defined in the library, namely ResponseContainer and ResponseStatus. They contain information about the incoming and outgoing messages.<\/p>\r\n
The ResponseContainer contains the actual message
data<\/code>, the signal strength valuerssi<\/code>, and the ResponseStatusstatus<\/code>. <\/p>\r\nstruct ResponseContainer {\r\n String data;\r\n byte rssi; \/\/ only E22 and E220 series!\r\n ResponseStatus status;\r\n};<\/pre>\r\n\nThe ResponseStatus is also a structure. It contains the error code
code<\/code> and the functiongetResponseDescription()<\/code>, which returns a string that translates the code comprehensibly. For example, error code 1 (E220_SUCCESS) means “Success”.<\/p>\r\n\nstruct ResponseStatus {\r\n Status code;\r\n String getResponseDescription() {\r\n return getResponseDescriptionByParams(this->code);\r\n }\r\n};<\/pre>\r\n\nTransparent Transmission Mode<\/h2>\n\n
- xxx_yyy = 500_000, 1000_001, 1500_010, 2000_011, 2500_100, 3000_101, 3500_110, 4000_111<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n
- enableRSSI<\/strong>: Signal strength information (Received Signal Strength Indication)
- subPacketSetting<\/strong>: Maximum data packet size, i.e. the maximum length of your message that you can send continuously in one piece.
- uartBaudRate<\/strong>: Baud rate UART_BPS_xxx
- EByte_LoRa_E22_Series_Library<\/a><\/li>\r\n
- M0 = HIGH, M1 = LOW<\/strong>: Wake-up mode (transmitter)<\/li>\r\n
- M0 = HIGH, M1 = LOW<\/strong>: WOR mode (transmitter\/receiver)<\/li>\r\n
- M0 = HIGH, M1 = LOW<\/strong>: WOR Transmitter<\/li>\r\n
- AUX<\/strong>: Indicates the status of the data buffers for sending and receiving and is used for the self-check.<\/li>\r\n
- GND \/ VCC<\/strong>: Power supply<\/li>\r\n
- Configuration Sketches for the E22 and E32 series<\/a><\/li>\r\n
- Naming<\/a><\/li>\r\n
- What is LoRa, LoRaWAN and LPWAN?<\/a><\/li>\r\n
![\"Scheme](\"https:\/\/wolles-elektronikkiste.de\/wp-content\/uploads\/2024\/03\/lora_transparent_transmission_scheme-1024x468.png\")
<\/a>