Issue link: https://read.uberflip.com/i/1540208
Regional Parameters RP002-1.0.5 ©2022-2025 LoRa Alliance ® Page 105 of 116 The authors reserve the right to change specifications without notice. Example: This is a valid EU868 beacon frame (SF9): 2138 2139 Field RFU Param Time CRC InfoDesc Lat Lng CRC Value Hex 00 00 CC020000 7EA2 0 002001 038100 55DE Table 116: Example of beacon CRC calculation (SF9) 2140 Example: Over the air, the octets are sent in the following order: 2141 00 00 | 00 00 02 CC | A2 7E | 00 | 01 20 00 | 00 81 03 | DE 55 2142 The first CRC is calculated on [00 00 00 00 02 CC]. 2143 The OPTIONAL gateway-specific part provides additional information regarding the gateway 2144 sending a beacon and therefore can differ for each gateway. The OPTIONAL part is protected 2145 by a CRC-16 computed on the GwSpecific + RFU fields. The CRC-16 definition SHALL 2146 be the same as for the mandatory part. 2147 Example: This is a valid US915 beacon (SF12): 2148 2149 Field RFU Param Time CRC InfoDesc Lat Lng RFU CRC Value Hex 0000 00 CC020000 7EA2 00 002001 038100 00 D450 Table 117: Example of beacon CRC calculation 2150 Example: Over the air, the octets are sent in the following order: 2151 00 00 00 | 00 00 02 CC | A2 7E | 00 | 01 20 00 | 00 81 03 | 00 | 50 D4 2152 5.2 FSK Description 2153 5.2.1 FSK Packet Physical Structure 2154 FSK messages can be built either by the software stack or by the hardware transceiver, 2155 depending on the end-device architecture. 2156 The PHYPayloadLength field contains the length in bytes of the PHYPayload field. 2157 The CRC field is computed on PHYPayloadLength and PHYPayload fields, using the CRC- 2158 CCITT algorithm. 2159 PHY: 2160 Size (bytes) 5 3 1 L bytes from PHYPayloadLength 2 Packet Structure Preamble SyncWord PHYPayloadLength PHYPayload CRC Table 118: FSK PHY structure 2161 2162