Nexmon is our C-based firmware patching framework for Broadcom/Cypress WiFi chips that enables you to write your own firmware patches, for example, to enable monitor mode with radiotap headers and frame injection.
The I-CUBE-LRWAN Expansion Package consists of a set of libraries and application examples for STM32L0 Series, STM32L1 Series, and STM32L4 Series microcontrollers acting as end devices. This package supports the Semtech LoRa®radio expansion boards SX1276MB1MAS, SX1276MB1LAS, SX1272MB2DAS, and the new generation sx126x mounted on SX1262DVK1DAS, SX1262DVK1CAS, and SX1262DVK1BAS.
When a flowgraph which has been generated by version 3.7 is opened in GRC version 3.8, much of the conversion process is done automatically. However, there are certain things which must be updated by hand.
WX GUI blocks: Since the WX GUI blocks are deprecated in version 3.8, the user must find corresponding blocks in the QT GUIs.
If blocks have different names between versions 3.7 and 3.8, they must be replaced by hand.
End devices in a LoRaWAN network come in three classes: Class A, Class B and Class C. While end devices can always send uplinks at will, the device’s class determines when it can receive downlinks. The class also determines a device’s energy efficiency. The more energy efficient a device, the longer the battery life.
All end devices must support Class A(“Aloha”) communications. Class A end devices spend most of their time in sleep mode. Because LoRaWAN is not a “slotted” protocol, end devices can communicate with the network server any time there is a change in a sensor reading or when a timer fires. Basically, they can wake up and talk to the server at any moment. After the device sends an uplink, it “listens” for a message from the network one and two seconds after the uplink (receive windows) before going back to sleep.
Class A is the most energy efficient and results in the longest battery life In contrast, rather than only waiting for one of its sensors to notice a change in the environment or fire a timer, Class B end devices also wake up and open a receive window to listen for a downlink according to a configurable, network-defined schedule. A periodic beacon signal transmitted by the network allows those end devices to synchronize their internal clocks with the network server.
Finally, Class C (“Continuous”) end devices never go to sleep. They constantly listen for downlink messages from the network, except when transmitting data in response to a sensor event. These devices are more energy-intensive, and usually require a constant power source, rather than relying on a battery.