IO.Bindings Namespace

P2P is misleading because there is no station addressing and all transmissions are broadcasts. Any station with the same RF settings (frequency, spreading factor, and chirp bandwidth) will be able to receive what you transmit with this library.

In test aka P2P mode, the Wio-E5 transmits unencrypted "implicit header" frames consisting of a configurable number of preamble bits, 1 to 253 payload bytes, and two CRC bytes. Upon reception of each frame, the Wio-E5 verifies the CRC, discarding erroneous frames and passing valid ones to the device driver.

Unlike LoRaWan mode, frames with up to 253 payload bytes can be sent and received using any data rate scheme (the combination of spreading factor, modulation bandwidth, and the derived RF symbol rate).

libwioe5ham1 supports Amateur Radio Unicast Flavor #1 (Personal Area Network with all stations using the same call sign). The first 12 bytes of the payload are reserved for the following unicast address information:

10 upper case characters for the network ID aka call sign, left justified and space padded.
1 binary byte for the destination node ID (ARCNET style: 0=broadcast or 1 to 255).
1 binary byte for the source node ID (ARCNET style: 1 to 255).

libwioe5ham1 drops any received frame that does not contain a matching network ID aka call sign and destination node ID, imposing a unicast address scheme onto the broadcast Wio-E5 test aka P2P mode.

See Wio-E5 LoRa Transceiver Peer to Peer Mode for more information.

In accordance with the digital data transparency required by U.S. Amateur Radio Service regulations, any Wio-E5 using the same RF settings (possibly using the related library libwioe5p2p) can monitor communications among a group of ham radio stations using libwioe5ham1.

P2P is misleading because there is no station addressing and all transmissions are broadcasts. Any station with the same RF settings (frequency, spreading factor, and chirp bandwidth) will be able to receive what you transmit with this library.

In test aka P2P mode, the Wio-E5 transmits unencrypted "implicit header" frames consisting of a configurable number of preamble bits, 1 to 253 payload bytes, and two CRC bytes. Upon reception of each frame, the Wio-E5 verifies the CRC, discarding erroneous frames and passing valid ones to the device driver.

Unlike LoRaWan mode, frames with up to 253 payload bytes can be sent and received using any data rate scheme (the combination of spreading factor, modulation bandwidth, and the derived RF symbol rate).

libwioe5ham2 supports Amateur Radio Unicast Flavor #2 (Local Area Network with stations using different call signs). The first 22 bytes of the payload are reserved for the following unicast address information:

10 upper case characters for the destination network ID aka callsign, left justified and space padded.
1 binary byte for the destination node ID (ARCNET style: 0=broadcast or 1 to 255).
10 upper case characters for the source network ID aka callsign, left justified and space padded.
1 binary byte for the source node ID (ARCNET style: 1 to 255).

libwioe5ham2 drops any received frame that does not contain a matching destination network ID aka call sign and destination node ID, imposing a unicast address scheme onto the broadcast Wio-E5 test aka P2P mode.

See Wio-E5 LoRa Transceiver Peer to Peer Mode for more information.

In accordance with the digital data transparency required by U.S. Amateur Radio Service regulations, any Wio-E5 using the same RF settings (possibly using the related library libwioe5p2p) can monitor communications among a group of ham radio stations using libwioe5ham2.

Wrapper class for the Wio-E5 LoRa Transceiver Module Driver Library libwioe5p2p.so using test mode aka P2P (Point to Point or Peer to Peer) broadcast mode.

P2P is misleading because there is no station addressing and all transmissions are broadcasts. Any station with the same RF settings (frequency, spreading factor, and chirp bandwidth) will be able to receive what you transmit with this library.

In test aka P2P mode, the Wio-E5 transmits unencrypted "implicit header" frames consisting of a configurable number of preamble bits, 1 to 253 payload bytes, and two CRC bytes. Upon reception of each frame, the Wio-E5 verifies the CRC, discarding erroneous frames and passing valid ones to the device driver.

Unlike LoRaWan mode, frames with up to 253 payload bytes can be sent and received using any data rate scheme (the combination of spreading factor, modulation bandwidth, and the derived RF symbol rate).