ARMmbed
/
mbed-os
mirror of https://github.com/ARMmbed/mbed-os.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Lora: Reformate LoRaWANBase documentation 

- Modified "user" to "you"
- Modified line length to ~100 characters.
pull/7719/head
Kimmo Vaisanen 2018-08-09 14:38:07 +03:00
parent 71341ec44e
commit 57f89a2576
1 changed files with 142 additions and 177 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

319
features/lorawan/LoRaWANBase.h
View File

@ -31,8 +31,7 @@ public:
*
* @param queue A pointer to EventQueue provided by the application.
*
* @return LORAWAN_STATUS_OK on success, a negative error code on
* failure:
* @return LORAWAN_STATUS_OK on success, a negative error code on failure:
* LORAWAN_STATUS_PARAMETER_INVALID is NULL queue is given.
*/
virtual lorawan_status_t initialize(events::EventQueue *queue) = 0;
@ -40,92 +39,88 @@ public:
/** Connect OTAA or ABP using the Mbed OS config system
*
* Connect by Over The Air Activation or Activation By Personalization.
* You need to configure the connection properly using the Mbed OS configuration
* system.
* You need to configure the connection properly using the Mbed OS configuration system.
*
* When connecting through OTAA, the return code for success (LORAWAN_STATUS_CONNECT_IN_PROGRESS) is negative.
* However, this is not a real error. It tells you that the connection is in progress, and an event will
* notify you of the completion. By default, after the Join Accept message
* is received, base stations may provide the node with a CF-List that replaces
* all user-configured channels except the Join/Default channels. A CF-List can
* configure a maximum of five channels other than the default channels.
* When connecting through OTAA, the return code for success (LORAWAN_STATUS_CONNECT_IN_PROGRESS)
* is negative. However, this is not a real error. It tells you that the connection is in progress,
* and an event will notify you of the completion. By default, after the Join Accept message is
* received, base stations may provide the node with a CF-List that replaces all user-configured
* channels except the Join/Default channels. A CF-List can configure a maximum of five channels
* other than the default channels.
*
* To configure more channels, we recommend that you use the `set_channel_plan()` API after the connection.
* By default, the PHY layers configure only the mandatory Join channels. The retransmission back-off restrictions
* on these channels are severe, and you may experience long delays or even failures in the confirmed traffic.
* If you add more channels, the aggregated duty cycle becomes much more relaxed as compared to the Join (default) channels only.
* By default, the PHY layers configure only the mandatory Join channels. The retransmission back-off
* restrictions on these channels are severe, and you may experience long delays or even failures
* in the confirmed traffic. If you add more channels, the aggregated duty cycle becomes much more
* relaxed as compared to the Join (default) channels only.
*
* **NOTES ON RECONNECTION:**
* Currently, the Mbed OS LoRaWAN implementation does not support non-volatile
* memory storage. Therefore, the state and frame counters cannot be restored after
* a power cycle. However, if you use the `disconnect()` API to shut down the LoRaWAN
* protocol, the state and frame counters are saved. Connecting again
* restores the previous session. According to the LoRaWAN 1.0.2 specification, the frame counters are always reset
* to 0 for OTAA, and a new Join request lets the network server know
* that the counters need a reset. The same is said about the ABP, but there
* is no way to convey this information to the network server. For a network
* server, an ABP device is always connected. That's why storing the frame counters
* is important for ABP. That's why we restore frame counters from
* session information after a disconnection.
* Currently, the Mbed OS LoRaWAN implementation does not support non-volatile memory storage.
* Therefore, the state and frame counters cannot be restored after a power cycle. However,
* if you use the `disconnect()` API to shut down the LoRaWAN protocol, the state and frame
* counters are saved. Connecting again restores the previous session. According to the LoRaWAN
* 1.0.2 specification, the frame counters are always reset to 0 for OTAA, and a new Join request
* lets the network server know that the counters need a reset. The same is said about the ABP,
* but there is no way to convey this information to the network server. For a network server,
* an ABP device is always connected. That's why storing the frame counters is important for ABP.
* That's why we restore frame counters from session information after a disconnection.
*
* @return Common: LORAWAN_STATUS_NOT_INITIALIZED if system is not initialized with initialize(),
* LORAWAN_STATUS_PARAMETER_INVALID if connection parameters are invalid.
* @return Common: LORAWAN_STATUS_NOT_INITIALIZED if system is not initialized with initialize(),
* LORAWAN_STATUS_PARAMETER_INVALID if connection parameters are invalid.
*
* For ABP: If everything goes well, LORAWAN_STATUS_OK is returned for first call followed by
* a 'CONNECTED' event. Otherwise a negative error code is returned:
* For ABP: If everything goes well, LORAWAN_STATUS_OK is returned for first call
* followed by a 'CONNECTED' event. Otherwise a negative error code is returned:
* Any subsequent call will return LORAWAN_STATUS_ALREADY_CONNECTED and no event follows.
*
* For OTAA: When a JoinRequest is sent, LORAWAN_STATUS_CONNECT_IN_PROGRESS is returned for the first call.
* Any subsequent call will return either LORAWAN_STATUS_BUSY (if the previous request for connection
* is still underway) or LORAWAN_STATUS_ALREADY_CONNECTED (if a network was already joined successfully).
* For OTAA: When a JoinRequest is sent, LORAWAN_STATUS_CONNECT_IN_PROGRESS is returned for
* the first call. Any subsequent call will return either LORAWAN_STATUS_BUSY
* (if the previous request for connection is still underway) or
* LORAWAN_STATUS_ALREADY_CONNECTED (if a network was already joined successfully).
* A 'CONNECTED' event is sent to the application when the JoinAccept is received.
*/
virtual lorawan_status_t connect() = 0;
/** Connect OTAA or ABP with parameters
*
* All connection parameters are chosen by the user and provided in the
* data structure passed down.
* All connection parameters are chosen by you and provided in the data structure passed down.
*
* When connecting using OTAA, the return code for success (LORAWAN_STATUS_CONNECT_IN_PROGRESS) is negative.
* However, this is not a real error. It tells you that connection is in progress, and an event will
* notify you of completion. By default, after Join Accept message
* is received, base stations may provide the node with a CF-List that replaces
* all user-configured channels except the Join/Default channels. A CF-List can
* configure a maximum of five channels other than the default channels.
* When connecting using OTAA, the return code for success (LORAWAN_STATUS_CONNECT_IN_PROGRESS)
* is negative. However, this is not a real error. It tells you that connection is in progress,
* and an event will notify you of completion. By default, after Join Accept message is received,
* base stations may provide the node with a CF-List that replaces all user-configured channels
* except the Join/Default channels. A CF-List can configure a maximum of five channels other
* than the default channels.
*
* To configure more channels, we recommend that you use the `set_channel_plan()` API after the connection.
* By default, the PHY layers configure only the mandatory Join
* channels. The retransmission back-off restrictions on these channels
* are severe, and you may experience long delays or even
* failures in the confirmed traffic. If you add more channels, the aggregated duty
* cycle becomes much more relaxed as compared to the Join (default) channels only.
* To configure more channels, we recommend that you use the `set_channel_plan()` API after
* the connection. By default, the PHY layers configure only the mandatory Join channels.
* The retransmission back-off restrictions on these channels are severe, and you may experience
* long delays or even failures in the confirmed traffic. If you add more channels, the aggregated
* duty cycle becomes much more relaxed as compared to the Join (default) channels only.
*
* **NOTES ON RECONNECTION:**
* Currently, the Mbed OS LoRaWAN implementation does not support non-volatile
* memory storage. Therefore, the state and frame counters cannot be restored after
* a power cycle. However, if you use the `disconnect()` API to shut down the LoRaWAN
* protocol, the state and frame counters are saved. Connecting again
* restores the previous session. According to the LoRaWAN 1.0.2 specification, the frame counters are always reset
* to zero for OTAA, and a new Join request lets the network server know
* that the counters need a reset. The same is said about the ABP, but there
* is no way to convey this information to the network server. For a network
* server, an ABP device is always connected. That's why storing the frame counters
* is important for ABP. That's why we restore frame counters from
* session information after a disconnection.
* Currently, the Mbed OS LoRaWAN implementation does not support non-volatile memory storage.
* Therefore, the state and frame counters cannot be restored after a power cycle. However,
* if you use the `disconnect()` API to shut down the LoRaWAN protocol, the state and frame
* counters are saved. Connecting again restores the previous session. According to the LoRaWAN
* 1.0.2 specification, the frame counters are always reset to zero for OTAA, and a new Join
* request lets the network server know that the counters need a reset. The same is said about
* the ABP, but there is no way to convey this information to the network server. For a network
* server, an ABP device is always connected. That's why storing the frame counters is important
* for ABP. That's why we restore frame counters from session information after a disconnection.
*
* @param connect Options for an end device connection to the gateway.
*
* @return Common: LORAWAN_STATUS_NOT_INITIALIZED if system is not initialized with initialize(),
* LORAWAN_STATUS_PARAMETER_INVALID if connection parameters are invalid.
* @return Common: LORAWAN_STATUS_NOT_INITIALIZED if system is not initialized with initialize(),
* LORAWAN_STATUS_PARAMETER_INVALID if connection parameters are invalid.
*
* For ABP: If everything goes well, LORAWAN_STATUS_OK is returned for first call followed by
* a 'CONNECTED' event. Otherwise a negative error code is returned.
* For ABP: If everything goes well, LORAWAN_STATUS_OK is returned for first call followed
* by a 'CONNECTED' event. Otherwise a negative error code is returned.
* Any subsequent call will return LORAWAN_STATUS_ALREADY_CONNECTED and no event follows.
*
* For OTAA: When a JoinRequest is sent, LORAWAN_STATUS_CONNECT_IN_PROGRESS is returned for the first call.
* Any subsequent call will return either LORAWAN_STATUS_BUSY (if the previous request for connection
* is still underway) or LORAWAN_STATUS_ALREADY_CONNECTED (if a network was already joined successfully).
* For OTAA: When a JoinRequest is sent, LORAWAN_STATUS_CONNECT_IN_PROGRESS is returned for the
* first call. Any subsequent call will return either LORAWAN_STATUS_BUSY
* (if the previous request for connection is still underway) or LORAWAN_STATUS_ALREADY_CONNECTED
* (if a network was already joined successfully).
* A 'CONNECTED' event is sent to the application when the JoinAccept is received.
*/
virtual lorawan_status_t connect(const lorawan_connect_t &connect) = 0;
@ -133,34 +128,30 @@ public:
/** Disconnect the current session.
*
* @return LORAWAN_STATUS_DEVICE_OFF on success, a negative error code on failure:
* LORAWAN_STATUS_NOT_INITIALIZED if system is not initialized with initialize(),
* LORAWAN_STATUS_NOT_INITIALIZED if system is not initialized with initialize(),
*/
virtual lorawan_status_t disconnect() = 0;
/** Validate the connectivity with the network.
*
* Application may use this API to submit a request to the stack for
* validation of its connectivity to a Network Server. Under the hood, this
* API schedules a Link Check Request command (LinkCheckReq) for the network
* server and once the response, i.e., LinkCheckAns MAC command is received
* from the Network Server, user provided method is called.
* Application may use this API to submit a request to the stack for validation of its connectivity
* to a Network Server. Under the hood, this API schedules a Link Check Request command (LinkCheckReq)
* for the network server and once the response, i.e., LinkCheckAns MAC command is received from
* the Network Server, user provided method is called.
*
* One way to use this API may be the validation of connectivity after a long
* deep sleep. Mbed LoRaWANStack follows the MAC commands with data
* frame payload, so the application needs send something, and the Network
* Server may respond during the RX slots.
* One way to use this API may be the validation of connectivity after a long deep sleep.
* Mbed LoRaWANStack follows the MAC commands with data frame payload, so the application needs
* send something, and the Network Server may respond during the RX slots.
*
* This API is usable only when the 'link_check_resp' callback is set by
* the application. See add_lora_app_callbacks API. If the above mentioned
* callback is not set, a LORAWAN_STATUS_PARAMETER_INVALID error is thrown.
* This API is usable only when the 'link_check_resp' callback is set by the application.
* See add_lora_app_callbacks API. If the above mentioned callback is not set,
* a LORAWAN_STATUS_PARAMETER_INVALID error is thrown.
*
* The first parameter to callback function is the demodulation margin, and
* the second parameter is the number of gateways that successfully received
* the last request.
* The first parameter to callback function is the demodulation margin, and the second parameter
* is the number of gateways that successfully received the last request.
*
* A 'Link Check Request' MAC command remains set for every subsequent
* transmission, until/unless application explicitly turns it off using
* remove_link_check_request() API.
* A 'Link Check Request' MAC command remains set for every subsequent transmission, until/unless
* application explicitly turns it off using remove_link_check_request() API.
*
* @return LORAWAN_STATUS_OK on successfully queuing a request, or
* a negative error code on failure:
@ -172,18 +163,15 @@ public:
/** Removes link check request sticky MAC command.
*
* Any already queued request may still be completed. However, no new
* requests will be made.
* Any already queued request may still be completed. However, no new requests will be made.
*/
virtual void remove_link_check_request() = 0;
/** Sets up a particular data rate
*
* @param data_rate The intended data rate, for example DR_0 or DR_1.
* Please note, that the macro DR_* can mean different
* things in different regions.
* @return LORAWAN_STATUS_OK if everything goes well, otherwise
* a negative error code:
* Please note, that the macro DR_* can mean different things in different regions.
* @return LORAWAN_STATUS_OK if everything goes well, otherwise a negative error code:
* LORAWAN_STATUS_NOT_INITIALIZED if system is not initialized with initialize(),
* LORAWAN_STATUS_PARAMETER_INVALID if ADR is enabled or invalid data rate is given
*/
@ -192,11 +180,10 @@ public:
/** Enables adaptive data rate (ADR)
*
* The underlying LoRaPHY and LoRaMac layers handle the data rate automatically
* for the user, based on the radio conditions (network congestion).
* based on the radio conditions (network congestion).
*
* @return LORAWAN_STATUS_OK on success, negative error code
* on failure:
* LORAWAN_STATUS_NOT_INITIALIZED if system is not initialized with initialize()
* @return LORAWAN_STATUS_OK on success, negative error code on failure:
* LORAWAN_STATUS_NOT_INITIALIZED if system is not initialized with initialize()
*/
virtual lorawan_status_t enable_adaptive_datarate() = 0;
@ -214,42 +201,39 @@ public:
*
* Valid for confirmed messages only.
*
* The number of trials to transmit the frame, if the LoRaMAC layer did not
* receive an acknowledgment. The MAC performs a data rate adaptation as in
* the LoRaWAN Specification V1.0.2, chapter 18.4, table on page 64.
* The number of trials to transmit the frame, if the LoRaMAC layer did not receive an
* acknowledgment. The MAC performs a data rate adaptation as in the LoRaWAN Specification
* V1.0.2, chapter 18.4, table on page 64.
*
* Note that if the number of retries is set to 1 or 2, MAC does not decrease
* the data rate, if the LoRaMAC layer did not receive an acknowledgment.
* Note that if the number of retries is set to 1 or 2, MAC does not decrease the data rate,
* if the LoRaMAC layer did not receive an acknowledgment.
*
* @param count The number of retries for confirmed messages.
*
* @return LORAWAN_STATUS_OK or a negative error code on failure:
* LORAWAN_STATUS_NOT_INITIALIZED if system is not initialized with initialize()
* LORAWAN_STATUS_NOT_INITIALIZED if system is not initialized with initialize()
* LORAWAN_STATUS_PARAMETER_INVALID if count >= 255
*/
virtual lorawan_status_t set_confirmed_msg_retries(uint8_t count) = 0;
/** Sets the channel plan.
*
* You can provide a list of channels with appropriate parameters filled
* in. However, this list is not absolute. The stack applies a CF-List whenever
* available, which means that the network can overwrite your channel
* frequency settings right after Join Accept is received. You may try
* to set up any channel or channels after that, and if the channel requested
* is already active, the request is silently ignored. A negative error
* code is returned if there is any problem with parameters.
* You can provide a list of channels with appropriate parameters filled in. However,
* this list is not absolute. The stack applies a CF-List whenever available, which means
* that the network can overwrite your channel frequency settings right after Join Accept
* is received. You may try to set up any channel or channels after that, and if the channel
* requested is already active, the request is silently ignored. A negative error code is
* returned if there is any problem with parameters.
*
* Please note that you can also use this API to add a single channel to the
* existing channel plan.
* Please note that you can also use this API to add a single channel to the existing channel plan.
*
* There is no reverse mechanism in the 1.0.2 specification for a node to request
* a particular channel. Only the network server can initiate such a request.
* There is no reverse mechanism in the 1.0.2 specification for a node to request a particular
* channel. Only the network server can initiate such a request.
* You need to ensure that the corresponding base station supports the channel or channels being added.
*
* If your list includes a default channel (a channel where Join Requests
* are received), you cannot fully configure the channel parameters.
* Either leave the channel settings to default or check your
* corresponding PHY layer implementation. For example, LoRaPHYE868.
* If your list includes a default channel (a channel where Join Requests are received),
* you cannot fully configure the channel parameters. Either leave the channel settings to default
* or check your corresponding PHY layer implementation. For example, LoRaPHYE868.
*
* @param channel_plan The channel plan to set.
*
@ -266,16 +250,15 @@ public:
/** Gets the channel plans from the LoRa stack.
*
* Once you have selected a particular PHY layer, a set of channels
* is automatically activated. Right after connecting, you can use this API
* to see the current plan. Otherwise, this API returns the channel
* plan that you have set using `set_channel_plan()`.
* Once you have selected a particular PHY layer, a set of channels is automatically activated.
* Right after connecting, you can use this API to see the current plan. Otherwise, this API
* returns the channel plan that you have set using `set_channel_plan()`.
*
* @param channel_plan The current channel plan information.
*
* @return LORAWAN_STATUS_OK on success, a negative error code on failure:
* LORAWAN_STATUS_NOT_INITIALIZED if system is not initialized with initialize(),
* LORAWAN_STATUS_SERVICE_UNKNOWN if custom channel plans are disabled in PHY
* LORAWAN_STATUS_NOT_INITIALIZED if system is not initialized with initialize(),
* LORAWAN_STATUS_SERVICE_UNKNOWN if custom channel plans are disabled in PHY
*/
virtual lorawan_status_t get_channel_plan(lorawan_channelplan_t &channel_plan) = 0;
@ -307,27 +290,23 @@ public:
/** Send message to gateway
*
* @param port The application port number. Port numbers 0 and 224
* are reserved, whereas port numbers from 1 to 223
* (0x01 to 0xDF) are valid port numbers.
* @param port The application port number. Port numbers 0 and 224 are reserved,
* whereas port numbers from 1 to 223 (0x01 to 0xDF) are valid port numbers.
* Anything out of this range is illegal.
*
* @param data A pointer to the data being sent. The ownership of the
* buffer is not transferred. The data is copied to the
* internal buffers.
* @param data A pointer to the data being sent. The ownership of the buffer is not transferred.
* The data is copied to the internal buffers.
*
* @param length The size of data in bytes.
*
* @param flags A flag used to determine what type of
* message is being sent, for example:
* @param flags A flag used to determine what type of message is being sent, for example:
*
* MSG_UNCONFIRMED_FLAG = 0x01
* MSG_CONFIRMED_FLAG = 0x02
* MSG_MULTICAST_FLAG = 0x04
* MSG_CONFIRMED_FLAG = 0x02
* MSG_MULTICAST_FLAG = 0x04
* MSG_PROPRIETARY_FLAG = 0x08
*
* All flags are mutually exclusive, and MSG_MULTICAST_FLAG
* cannot be set.
* All flags are mutually exclusive, and MSG_MULTICAST_FLAG cannot be set.
*
* @return The number of bytes sent, or a negative error code on failure:
* LORAWAN_STATUS_NOT_INITIALIZED if system is not initialized with initialize(),
@ -340,32 +319,27 @@ public:
/** Receives a message from the Network Server on a specific port.
*
* @param port The application port number. Port numbers 0 and 224
* are reserved, whereas port numbers from 1 to 223
* (0x01 to 0xDF) are valid port numbers.
* @param port The application port number. Port numbers 0 and 224 are reserved,
* whereas port numbers from 1 to 223 (0x01 to 0xDF) are valid port numbers.
* Anything out of this range is illegal.
*
* @param data A pointer to buffer where the received data will be
* stored.
* @param data A pointer to buffer where the received data will be stored.
*
* @param length The size of data in bytes.
*
* @param flags A flag is used to determine what type of
* message is being sent, for example:
* @param flags A flag is used to determine what type of message is being sent, for example:
*
* MSG_UNCONFIRMED_FLAG = 0x01
* MSG_CONFIRMED_FLAG = 0x02
* MSG_MULTICAST_FLAG = 0x04
* MSG_CONFIRMED_FLAG = 0x02
* MSG_MULTICAST_FLAG = 0x04
* MSG_PROPRIETARY_FLAG = 0x08
*
* All flags can be used in conjunction with
* one another depending on the intended use case or reception
* expectation.
* All flags can be used in conjunction with one another depending on the intended
* use case or reception expectation.
*
* For example, MSG_CONFIRMED_FLAG and MSG_UNCONFIRMED_FLAG are
* not mutually exclusive. In other words, the user can subscribe to
* receive both CONFIRMED AND UNCONFIRMED messages at
* the same time.
* receive both CONFIRMED AND UNCONFIRMED messages at the same time.
*
* @return It could be one of these:
* i) 0 if there is nothing else to read.
@ -380,8 +354,7 @@ public:
/** Receives a message from the Network Server on any port.
*
* @param data A pointer to buffer where the received data will be
* stored.
* @param data A pointer to buffer where the received data will be stored.
*
* @param length The size of data in bytes
*
@ -389,8 +362,8 @@ public:
*
* @param flags Return flags to determine what type of message was received.
* MSG_UNCONFIRMED_FLAG = 0x01
* MSG_CONFIRMED_FLAG = 0x02
* MSG_MULTICAST_FLAG = 0x04
* MSG_CONFIRMED_FLAG = 0x02
* MSG_MULTICAST_FLAG = 0x04
* MSG_PROPRIETARY_FLAG = 0x08
*
* @return It could be one of these:
@ -398,7 +371,7 @@ public:
* ii) Number of bytes written to user buffer.
* iii) A negative error code on failure:
* LORAWAN_STATUS_NO_ACTIVE_SESSIONS if connection is not open,
* LORAWAN_STATUS_PARAMETER_INVALID if NULL data or length is given,
* LORAWAN_STATUS_PARAMETER_INVALID if NULL data or length is given,
* LORAWAN_STATUS_WOULD_BLOCK if there is nothing available to read at the moment.
*/
virtual int16_t receive(uint8_t *data, uint16_t length, uint8_t &port, int &flags) = 0;
@ -413,15 +386,15 @@ public:
*
* int main()
* {
* lorawan.initialize();
* cbs.lorawan_events = mbed::callback(my_event_handler);
* lorawan.add_app_callbacks(&cbs);
* lorawan.connect();
* lorawan.initialize();
* cbs.lorawan_events = mbed::callback(my_event_handler);
* lorawan.add_app_callbacks(&cbs);
* lorawan.connect();
* }
*
* static void my_event_handler(lorawan_event_t event)
* {
* switch(event) {
* switch(event) {
* case CONNECTED:
* //do something
* break;
@ -433,7 +406,7 @@ public:
* break;
* default:
* break;
* }
* }
* }
*
* @param callbacks A pointer to the structure containing application callbacks.
@ -458,14 +431,11 @@ public:
/** Get hold of TX meta-data
*
* Use this method to acquire any TX meta-data related to previous
* transmission.
* Use this method to acquire any TX meta-data related to previous transmission.
* TX meta-data is only available right after the transmission is completed.
* In other words, you can check for TX meta-data right after receiving the
* TX_DONE event.
* In other words, you can check for TX meta-data right after receiving the TX_DONE event.
*
* @param metadata the inbound structure that will be filled if the meta-data
* is available.
* @param metadata the inbound structure that will be filled if the meta-data is available.
*
* @return LORAWAN_STATUS_OK if the meta-data is available,
* otherwise other negative error code if request failed:
@ -476,14 +446,11 @@ public:
/** Get hold of RX meta-data
*
* Use this method to acquire any RX meta-data related to current
* reception.
* Use this method to acquire any RX meta-data related to current reception.
* RX meta-data is only available right after the reception is completed.
* In other words, you can check for RX meta-data right after receiving the
* RX_DONE event.
* In other words, you can check for RX meta-data right after receiving the RX_DONE event.
*
* @param metadata the inbound structure that will be filled if the meta-data
* is available.
* @param metadata the inbound structure that will be filled if the meta-data is available.
*
* @return LORAWAN_STATUS_OK if the meta-data is available,
* otherwise other negative error code if request failed:
@ -494,17 +461,15 @@ public:
/** Get hold of backoff time
*
* In the TX path, because of automatic duty cycling, the transmission is delayed
* by a certain amount of time which is the backoff time. While the system schedules
* application data to be sent, the application can inquire about how much time is
* left in the actual transmission to happen.
* In the TX path, because of automatic duty cycling, the transmission is delayed by a certain
* amount of time which is the backoff time. While the system schedules application data to be sent,
* the application can inquire about how much time is left in the actual transmission to happen.
*
* The system will provide you with a backoff time only if the application data is
* in the TX pipe. If however, the event is already queued for the transmission, this
* API returns a LORAWAN_STATUS_METADATA_NOT_AVAILABLE error code.
* The system will provide you with a backoff time only if the application data is in the TX pipe.
* If however, the event is already queued for the transmission, this API returns a
* LORAWAN_STATUS_METADATA_NOT_AVAILABLE error code.
*
* @param backoff the inbound integer that will be carry the backoff time if it
* is available.
* @param backoff the inbound integer that will be carry the backoff time if it is available.
*
* @return LORAWAN_STATUS_OK if the meta-data is available,
* otherwise other negative error code if request failed: