Libelium Waspmote 868LP User manual

Waspmote 868LP
Networking Guide

-2- v7.1
INDEX
1. Introduction .......................................................................................................................... 4
2. Hardware ...............................................................................................................................5
2.1. Specications..................................................................................................................................... 5
2.2. How to connect the module ............................................................................................................ 7
2.3. Expansion Radio Board (XBee 868LP) ........................................................................................... 8
3. General Considerations......................................................................................................10
3.1. Waspmote Libraries........................................................................................................................ 10
3.1.1. Waspmote XBee Files..........................................................................................................10
3.1.2. Constructor ..........................................................................................................................10
3.2. API Functions ................................................................................................................................... 10
3.3. API extension................................................................................................................................... 11
3.4. Waspmote reboot ........................................................................................................................... 11
3.5. Constants pre-dened.................................................................................................................... 11
4. Initialization ........................................................................................................................12
4.1. Setting ON........................................................................................................................................ 12
4.2. Setting OFF....................................................................................................................................... 12
5. Node Parameters................................................................................................................13
5.1. MAC Address ................................................................................................................................... 13
5.2. PAN ID .............................................................................................................................................. 13
5.3. Node Identier ................................................................................................................................ 14
5.4. Available frequencies ..................................................................................................................... 14
5.5. Channel Mask .................................................................................................................................. 16
5.6. Preamble ID ..................................................................................................................................... 16
6. Power Gain and Sensibility ................................................................................................ 17
6.1. Received Signal Strength Indicator ............................................................................................... 17
6.2. Power Level...................................................................................................................................... 17
7. Networking methods ......................................................................................................... 18
7.1. Topology........................................................................................................................................... 18
7.2. Addressing ....................................................................................................................................... 18
7.3. Maximum payloads ........................................................................................................................ 19
7.4. Sending data.................................................................................................................................... 19
7.4.1. Using Waspmote Frame .....................................................................................................19
7.4.2. Sending function .................................................................................................................19
7.4.3. Examples ..............................................................................................................................20
Document Version: v7.1 - 07/2017
© Libelium Comunicaciones Distribuidas S.L.
Index

-3- v7.1
Index
7.5. Receiving Data................................................................................................................................. 21
7.5.1. Receiving function...............................................................................................................21
7.5.2. Examples ..............................................................................................................................21
8. Node Discovery ..................................................................................................................22
8.1. Structure used in Discovery .......................................................................................................... 22
8.2. Searching specic nodes ............................................................................................................... 23
8.3. Node discovery to a specic node ............................................................................................... 23
8.4. Node Discovery Time ..................................................................................................................... 24
9. Sleep Mode........................................................................................................................... 25
10. Security and Data Encryption..........................................................................................26
10.1. Security and Data encryption Overview..................................................................................... 26
10.2. Security in API libraries ................................................................................................................ 26
10.2.1. Encryption Enable .............................................................................................................26
10.2.2. Encryption Key...................................................................................................................26
10.3. Security in a network.................................................................................................................... 27
11. Certications.....................................................................................................................28
12. Code examples and extended information ...................................................................29
13. API changelog .................................................................................................................... 30
14. Documentation changelog .............................................................................................. 31

-4- v7.1
Introduction
1. Introduction
This guide explains the new XBee 868LP library. This module was specically integrated for our new product lines
Waspmote v15, Plug & Sense! v15 and Meshlium v4.0, released on October 2016.
If you are using previous versions of our products, please use the corresponding guides, available on our
Development website
You can get more information about the generation change on the document “New generation of Libelium product
lines”.
To know the main dierences between XBee-PRO 868 and XBee 868LP see the table below.
[Old] XBee-PRO 868 [New] XBee 868LP
Frequency band 869.4 to 869.65 MHz 863 to 870 MHz
Tx power 25 dBm (software
selectable)
14 dBm (software
selectable)
Tx Current 500 mA typical at 3.3 V 48 mA typical at 3.3 V
RF data rate 24 kb/s 10 kb/s
Rx sensitivity -112 dBm -101 dBm
Max range, indoors/urban up to 550 m up to 112 m
Max range, outdoors (line of sight) with ~2.1dBi
antenna
up to 13 km up to 8.4 km
Regulatory approvals Europe Europe
XBee 868LP compatibility:
Item Compatible Notes
Waspmote 12 Yes New Waspmote API needed (v025 or newer)
Waspmote 15 Yes New Waspmote API needed (v025 or newer)
Old XBee-PRO 868 codes Depends Minor changes:
The XBee-PRO 868 library is capable of sending/
receiving packets with the new XBee 868LP.
However, conguring channels can only be
done by the newest API version.
Important:
•All documents and any examples they contain are provided as-is and are subject to change without notice.
Except to the extent prohibited by law, Libelium makes no express or implied representation or warranty of
any kind with regard to the documents, and specically disclaims the implied warranties and conditions of
merchantability and tness for a particular purpose.
•The information on Libelium’s websites has been included in good faith for general informational purposes
only. It should not be relied upon for any specic purpose and no representation or warranty is given as to its
accuracy or completeness.

-5- v7.1
Hardware
2. Hardware
2.1. Specications
Module Frequency TX Power Sensitivity Channels Distance
XBee 868LP 863 - 870 MHz 14 dBm -106 dBm 30 8.4 km
Figure : XBee 868LP
Note:The XBee 868LP module is provided with a 4.5 dBi antenna, which enables maximum range.
The frequency used is the 868 MHz band, using 30 software selectable channels. Channels are spaced 100 kHz
apart. The transmission rate is 10 kbps.
Note: To know what band is legal in your country, please check the ITU region map. Region 1 ISM free band is 868
MHz and Region 2 ISM free band is 900 MHz. You must also check the legal restrictions by region to use the proper
conguration and channel. It is the responsibility of the users to know the allowed frequency band and channels
in their country, and use them. Ignoring this, could lead to considerable penalties.
Remark: Libelium replaced the XBee 868 module with its natural evolution, the XBee 868LP, in October 2016. The XBee
868LP module is not compatible with other XBee products. Among other dierences, they use dierent baudrates
so they cannot interoperate. The new XBee 868LP features a lower transmission power with a good sensitivity, so
battery performance is improved due to lower consumption while good ranges remain.
Note: Due to the propagation characteristics of the 868/900 MHz band, the near eld eect could make that 2
modules cannot communicate if they are placed very close (< 1 m). We suggest to keep a minimum distance of 3
or 4 meters between modules.
Note: It is not recommended to work without an antenna screwed to the module. The module could be damaged
due to RF reections.

-6- v7.1
Hardware
Figure : Available frequencies for XBee 868LP
Encryption is provided through the AES 128 bits algorithm. Specically through the type AES-CTR. In this case the
Frame Counter eld has a unique ID and encrypts all the information contained in the Payload eld which is the
place in the link layer frame where the data to be sent is stored.
The way in which the libraries have been developed for module programming means that encryption activation is
as simple as running the initialization function and giving it a key to use in the encryption.
{
xbee868LP.setEncryptionMode(1);
xbee868LP.setLinkKey(key);
}
The classic topology for this type of network is Star topology, as the nodes can establish point to point connections
with brother nodes through the MAC address.
Figure : Star topology

-7- v7.1
Hardware
2.2. How to connect the module
This module can be connected to both SOCKET0 and SOCKET1 on the Waspmote board.
Figure : Module connected to Waspmote in SOCKET0
In order to connect the module to the SOCKET1, the user must use the Expansion Radio Board.

-8- v7.1
Hardware
2.3. Expansion Radio Board (XBee 868LP)
The Expansion Board allows to connect two communication modules at the same time in the Waspmote
sensor platform. This means a lot of dierent combinations are possible using any of the wireless radios
available for Waspmote: 802.15.4, ZigBee, DigiMesh, 868 MHz, 900 MHz, LoRa, WiFi, GPRS, GPRS+GPS,
3G, 4G, Sigfox, LoRaWAN, Bluetooth Pro, Bluetooth Low Energy and RFID/NFC. Besides, the following
Industrial Protocols modules are available: RS-485/Modbus, RS-232 Serial/Modbus and CAN Bus.
Some of the possible combinations are:
•LoRaWAN - GPRS
•802.15.4 - Sigfox
•868 MHz - RS-485
•RS-232 - WiFi
•DigiMesh - 4G
•RS-232 - RFID/NFC
•WiFi - 3G
•CAN Bus - Bluetooth
•etc.
Remark: GPRS, GPRS+GPS, 3G and 4G modules do not need the Expansion Board to be connected to Waspmote.
They can be plugged directly in the socket1.
In the next photo you can see the sockets available along with the UART assigned. On one hand, SOCKET0 allows
to plug any kind of radio module through the UART0. On the other hand, SOCKET1 permits to connect a radio
module through the UART1.
Figure: Use of the Expansion Board

-9- v7.1
Hardware
The API provides a function called ON() in order to switch the XBee module on. This function supports a parameter
which permits to select the SOCKET. It is possible to choose between SOCKET0 and SOCKET1.
Selecting SOCKET0 (both are valid):
xbee868LP.ON();
xbee868LP.ON(SOCKET0);
Selecting SOCKET1:
xbee868LP.ON(SOCKET1);
In the case two XBee 868LP modules are needed (each one in each socket), it will be necessary to create a new
object from WaspXBee868LP class. By default, there is already an object called xbee868LP normally used for
regular SOCKET0.
In order to create a new object it is necessary to put the following declaration in your Waspmote code:
WaspXBee868LP xbee868LP_2 = WaspXBee868LP();
Finally, it is necessary to initialize both modules. For example, xbee868LP is initialized in SOCKET0 and xbee868LP_2
in SOCKET1 as follows:
xbee868LP.ON(SOCKET0);
xbee868LP_2.ON(SOCKET1);
The rest of functions are used the same way as they are used with older API versions. In order to understand them
we recommend to read this guide.
Warnings:
•Avoid to use DIGITAL7 pin when working with Expansion Board. This pin is used for setting the XBee into sleep.
•Avoid to use DIGITAL6 pin when working with Expansion Board. This pin is used as power supply for the
Expansion Board.
•Incompatibility with Sensor Boards:
-Agriculture v30 and Agriculture PRO v30: Incompatible with Watermark and solar radiation sensors
-Events v30: Incompatible with interruption shift register
-Gases v30: DIGITAL6 is incompatible with CO2 (SOCKET_2) and DIGITAL7 is incompatible with NO2
(SOCKET_3)
-Smart Water v30: DIGITAL7 incompatible with conductivity sensor
-Smart Water Ions v30: Incompatible with ADC conversion (sensors cannot be read if the Expansion Board
is in use)
-Gases PRO v30: Incompatible with SOCKET_2 and SOCKET_3
-Cities PRO v30: Incompatible with SOCKET_3. I2C bus can be used. No gas sensor can be used.

-10- v7.1
General Considerations
3. General Considerations
3.1. Waspmote Libraries
3.1.1. Waspmote XBee Files
Waspmote API les:
WaspXBeeCore.h
WaspXBeeCore.cpp
WaspXBee868LP.h
WaspXBee868LP.cpp
It is mandatory to include the XBee 868LP library when using this module. The following line must be introduced
at the beginning of the code:
#include <WaspXBee868LP.h>
3.1.2. Constructor
To start using the Waspmote XBee 868LP library, an object from class WaspXBee868LP must be created. This object,
called xbee868LP, is created inside the Waspmote XBee 868LP library and it is public to all libraries. It is used
through the guide to show how the Waspmote XBee 868LP library works.
When creating this constructor, no variables are dened with a value by default.
3.2. API Functions
Through the guide there are many examples of using parameters. In these examples, API functions are called to
execute the commands, storing in their related variables the parameter value in each case.
Example of use
{
xbee868LP.getOwnMacLow(); // Get 32 lower bits of MAC Address
xbee868LP.getOwnMacHigh(); // Get 32 upper bits of MAC Address
}
Related Variables
sourceMacHigh[0-3] → stores the 32 upper bits of MAC address
sourceMacLow [0-3] → stores the 32 lower bits of MAC address
When returning from xbee868.getOwnMacLow() the variable xbee868.sourceMacLow() will be lled with the
appropriate values. Before calling the function, the related variable is created but it is empty.
There are three error ags that are lled when the function is executed:
•error_AT: it stores if some error occurred during the execution of an AT command function.
•error_RX: it stores if some error occurred during the reception of a packet.
•error_TX: it stores if some error occurred during the transmission of a packet.

-11- v7.1
General Considerations
All the functions also return a ag to know if the function called was successful or not. Available values for this ag:
•0 : Success. The function was executed without errors and the variable was lled.
•1 : Error. The function was executed but an error occurred while executing.
•2 : Not executed. An error occurred before executing the function.
•-1 : Function not allowed in this module.
To store the parameter changes after power cycles, it is needed to execute the writeValues function.
Example of use
{
xbee868LP.writeValues();
}
3.3. API extension
All the relevant and useful functions have been included in the Waspmote API, although any XBee AT commands
can be sent directly to the transceiver calling the sendCommandAT() function.
Example of use
{
xbee868LP.sendCommandAT(“CH#”);
}
Related Variables
commandAT[0-99] → stores the response given by the module up to 100 bytes
• Sending AT commands example:
http://www.libelium.com/development/waspmote/examples/868lp-11-send-atcommand
3.4. Waspmote reboot
When Waspmote is rebooted the application code will start again, creating all the variables and objects from the
beginning.
3.5. Constants pre-dened
There are some constants pre-dened in a le called ‘WaspXBeeCore.h’. These constants dene some parameters
like the maximum data size. The most important constants are explained next:
•MAX_DATA: (default value is 300) it denes the maximum available data size for a packet. This constant must be
equal or bigger than the data is sent on each packet. This size should not be bigger than 1500.
•MAX_PARSE: (default value is 300) it denes the maximum data that is parsed in each call to parse_message().
If more data are received, they will be stored in the UART buer until the next call to treatData(). However, if
the UART buer is full, the following data will be written on the buer, so be careful with this matter.
•MAX_BROTHERS: (default value is 5) it denes the maximum number of brothers that can be stored.

-12- v7.1
Initialization
4. Initialization
Before starting to use a module, it needs to be initialized. During this process, the UART to communicate with the
module has to be opened and the XBee switch has to be set on.
4.1. Setting ON
The ON() function initializes all the global variables, opens the correspondent UART and switches the XBee ON.
The baudrate used to open the UART is dened in the library (115200bps by default). .
•protocol : species the protocol used (XBEE_868 in this case)
•discoveryOptions : species the options in Node Discovery
•scanTime : species the time to scan each channel
•encryptMode : species if encryption mode is enabled
•timeRSSI : species the time RSSI LEDs are on
Example of use:
{
xbee868LP.ON();
}
4.2. Setting OFF
The OFF() function closes the UART and switches the XBee OFF.
Example of use
{
xbee868LP.OFF();
}

-13- v7.1
Node Parameters
5. Node Parameters
When conguring a node, it is necessary to set some parameters which will be used lately in the network, and
some parameters necessary for using the API functions.
5.1. MAC Address
A 64-bit RF module’s unique IEEE address. It is divided in two groups of 32 bits (High and Low).
It identies uniquely a node inside a network due to it can not be modied and it is given by the manufacturer.
Example of use
{
xbee868LP.getOwnMacLow(); // Get 32 lower bits of MAC Address
xbee868LP.getOwnMacHigh(); // Get 32 upper bits of MAC Address
}
Related Variables
sourceMacHigh[0-3] → stores the 32 upper bits of MAC address
sourceMacLow [0-3]→ stores the 32 lower bits of MAC address
Besides, XBee modules provide a stick on the bottom side where the MAC address is indicated:
Figure : MAC address
5.2. PAN ID
The Personal Area Network Identier (PAN ID) is the Network ID. The user network identier. Nodes must have
the same network identier to communicate. Only modules with matching IDs can communicate with each other
so all the nodes in the same network must have the same PAN ID. If using OEM network IDs, 0xFFFF will use the
factory value.
Parameter range: From 0 to 0x7FFF. Default: 0x7FFF.
Example of use
{
uint8_t panid[] = { 0x7F, 0xFF };
xbee868LP.setPAN(panid);
xbee868LP.getPAN();
}

-14- v7.1
Node Parameters
Related Variables
PAN_ID[0-7] → stores the 16-bit PAN ID. It is stored in the two first positions.
• XBee conguration example:
http://www.libelium.com/development/waspmote/examples/868lp-01-congure-xbee-parameters
5.3. Node Identier
It is an ASCII string of 20 characters at most which identies the node in a network. It is used to identify a node in
the application level. It is also used to search a node using its NI.
Example of use
{
 xbee868LP.setNodeIdentier(“node01”);
 xbee868LP.getNodeIdentier();
}
Related Variables
nodeID[0-19] → stores the 20-byte max string Node Identifier
5.4. Available frequencies
XBee 868LP denes 30 channels that are spaced 200 kHz apart:
•863-870MHz : 30 channels
Figure : Available frequencies for XBee 868LP

-15- v7.1
Node Parameters
This read-only command can be queried to return a biteld of the frequencies that are available in the module’s
region of operation. Each bit corresponds to a physical channel. Channels are spaced 200 kHz apart:
Biteld Frecuency (MHz)
Bit 0 863.150
Bit 1 863.350
Bit 2 863.550
Bit 3 863.750
Bit 4 863.950
Bit 5 864.150
Bit 6 864.350
Bit 7 864.550
Bit 8 864.750
Bit 9 864.950
Bit 10 865.150
Bit 11 865.350
Bit 12 865.550
Bit 13 865.750
Bit 14 865.950
Bit 15 866.150
Bit 16 866.350
Bit 17 866.550
Bit 18 866.750
Bit 19 866.950
Bit 20 867.150
Bit 21 867.350
Bit 22 867.550
Bit 23 867.750
Bit 24 867.950
Bit 25 868.150
Bit 26 868.350
Bit 27 868.550
Bit 28 868.750
Bit 29 868.950
Figure : Available frequencies on XBee 868LP
Parameter range: From 0 to 0x3FFFFFFF.
Example of use:
{
xbee868LP.getAvailableFreq();
}
Related variables:
_availableFreq[0-3] →stores the available frequencies biteld

-16- v7.1
Node Parameters
5.5. Channel Mask
The channel mask command allows channels to be selectively enabled or disabled. This is useful to avoid using
frequencies that experience unacceptable levels of RF interference. This command is a biteld. Each bit in the
biteld corresponds to a frequency as dened in the “Available Frequencies” section. When a bit in the Channel
Mask and the corresponding bit in the Available Frequencies are both set to 1 then that physical channel may be
chosen by the module as an active channel for communication.
At least two channels must be enabled, except when using only the g4 frequency. When using only the g4 frequency
(use 0x20000000) LBT+AFA will be disabled and requires the power level to be 5 mW e.r.p. or less.
All modules in a network must use an identical set of active channels. Separate networks which are in physical
range of each other should use dierent Preamble Patterns (HP) and/or Network ID’s (ID) to avoid receiving data
from the other network.
Parameter range: From 0 to 0x3FFFFFFF. Default: 0x3FFFFFFF.
Example of use
{
uint8_t channelMask[4] = {0xFF, 0xFF, 0xFF, 0xFF};
xbee868LP.setChannelMask( channelMask );
xbee868LP.getChannelMask();
}
Related Variables
_channelMask[0-3] → stores the operating channel
• XBee conguration example:
http://www.libelium.com/development/waspmote/examples/868lp-01-congure-xbee-parameters
5.6. Preamble ID
Only modules with matching preamble IDs can communicate with each other. Dierent preamble IDs minimize
interference between multiple sets of modules operating in the same vicinity. When receiving a packet this is
checked before the network ID, as it is encoded in the preamble, and the network ID is encoded in the MAC header.
Parameter range: From 0x00 to 0x09. Default: 0x00.
Example of use:
{
xbee868LP.setPreambleID( 0x00 );
xbee868LP.getPreambleID();
}
Related Variables
_preambleID → stores the preamble ID
• XBee conguration example:
http://www.libelium.com/development/waspmote/examples/868lp-01-congure-xbee-parameters

-17- v7.1
Power Gain and Sensibility
6. Power Gain and Sensibility
When conguring a node and a network, one important parameter is related with the Received Signal Strength
Indicator (RSSI).
6.1. Received Signal Strength Indicator
This command reports the received signal strength of the last received RF data packet. The getRSSI() command
only indicates the signal strength of the last hop. It does not provide an accurate quality measurement for a
multihop link. The command value is measured in -dBm. For example if it returns 0x60, then the RSSI of the last
packet received was -96 dBm.
Example of use:
{
xbee868LP.getRSSI();
}
Related variables:
valueRSSI → stores the RSSI of the last received packet
The ideal working mode is getting maximum coverage with the minimum power level. Thereby, a compromise
between power level and coverage appears. Each application scenario will need some tests to nd the best
combination of both parameters.
Get RSSI example:
http://www.libelium.com/development/waspmote/examples/868lp-05-get-rssi
6.2. Power Level
It is possible to set/get the power level at which the RF module transmits conducted power. Power level 4 is
calibrated and the other power levels are approximate.
Parameter range:
Parameter XBee 868LP
0 3 dBm, (2 mW)
17 dBm, (5 mW)
210 dBm, (10 mW)
312 dBm, (16 mW)
414 dBm, (25 mW) [Default]
Example of use:
{
xbee868LP.setPowerLevel(4);
xbee868LP.getPowerLevel();
}
Related variables:
powerLevel → Stored the power level set
Power level example:
http://www.libelium.com/development/waspmote/examples/868lp-12-set-power-level

-18- v7.1
Networking methods
7. Networking methods
Note: It is important to keep in mind that XBee networks are dened by the networking parameters. Every XBee
module within a network must share the same networking parameters. In the case of the XBee 868, every node in a
network must have the same:
• PAN ID
• Channel mask
• Preamble ID
7.1. Topology
The XBee 868LP provides a star topology to create a star network has a central node, which is linked to all other
nodes in the network. The central node gathers all data coming from the network nodes.
Figure : Star Topology
7.2. Addressing
Every RF data packet sent over-the-air contains a Source Address and Destination Address eld in its header. XBee
868LP supports long 64-bit addresses. A unique 64-bit IEEE source address is assigned at the factory and can be
read with the functions explained in the chapter related to MAC address.
XBee 868LP support Unicast and Broadcast transmissions:
•Unicast: The unicast mode is the only mode that supports acknowledgements (ACKs). When a packet is sent
using unicast mode, the receiving module sends an armative response to the sending module. If the sending
module does not receive the ACK, it will re-send the packet up to ten times or until the ACK is received. To send
a unicast message, the 64-bit receiver’s address must be set correctly.
•Broadcast: Used to transmit all modules in the same network. Any RF module within range will accept a
packet that contains a broadcast address. When a packet is sent using broadcast mode, receiving modules do
not send ACKs. All broadcast packets are automatically transmitted four times to ensure it is received. To send
a broadcast message, the receiver address must be set to 0x000000000000FFFF.

-19- v7.1
Networking methods
7.3. Maximum payloads
The maximum data payload size is dened as follows:
Unicast Broadcast
100Bytes 100Bytes
Figure : Maximum Payload Size
7.4. Sending data
7.4.1. Using Waspmote Frame
WaspFrame is a class that allows the user to create data frames with a specied format. It is a very useful tool to
set the payload of the packet to be sent. It is recommended to read the Waspmote Frame Programming Guide in
order to understand the XBee examples:
http://www.libelium.com/development/waspmote/documentation/data-frame-guide/
7.4.2. Sending function
The function send() sends a packet via XBee module.
Firstly, the destination address must be dened depending on the addressing mode:
•Dene unicast mode (must specify the destination MAC address). For example:
{
char rx_address[] = ”0013A2004030F6BC”;
}
•Dene broadcast mode:
{
char rx_address[] = ”000000000000FFFF”;
}
Finally, there are dierent sending function prototypes depending on the data sent. It is possible to send text
messages or binary data:
•Send strings:
{
  chardata[]=“this_is_the_data_eld”;
xbee868LP.send( rx_address, data);
}
•Send Waspmote Frames:
{
xbee868LP.send( rx_address, frame.buffer, frame.length );
}
•Send Array of bytes (it is mandatory to specify the length of the data eld):
{
uint8_t data[5] = {0x00, 0x01, 0x54, 0x76, 0x23};
xbee868LP.send( rx_address, data, 5);
}

-20- v7.1
Networking methods
The sending function implements application-level retries. By default, up to 3 retries are done in the case the
sending process fails. If a dierent number of maximum retries is needed, the setSendingRetries() function
permits to do it. This function changes the value of the API variable. When a new send() function is called, the
new maximum number of retries will be used.
Keep in mind that using a high number of retries could lead to a longer execution time of the send() function,
which means more power consumption on Waspmote and less channel availability for the rest of network nodes.
Probably, after 3 or 4 (failed) retries, it does not make sense to keep on trying.
Parameter range: From 0 to 15. Default: 10.
Example of use:
{
xbee868LP.setSendingRetries(10);
}
Related variables:
_send_retries → stores the maximum number of application-level retries
7.4.3. Examples
•Send packets in unicast mode:
http://www.libelium.com/development/waspmote/examples/868lp-02-send-packets
•Send packets in broadcast mode:
http://www.libelium.com/development/waspmote/examples/868lp-04a-send-broadcast
•Send packets using the expansion board:
http://www.libelium.com/development/waspmote/examples/868lp-06a-expansion-board-send
•Complete example, send packets in unicast mode and wait for a response:
http://www.libelium.com/development/waspmote/examples/868lp-08a-complete-example-send