User Tools
wiki:data_transmission
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
wiki:data_transmission [2020/03/16 14:29] ghi removed |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Data transmission ====== | ||
| - | Data can be sent to end-devices. It can be achieved using the web interface from the //Send data// menu (but also from other services). | ||
| - | |||
| - | {{:images:senddataselection_v1.0.png?600|Data can be sent manually or through a CSV file}} | ||
| - | |||
| - | The web interface only displays the last message sent. The web interface displays all the queued messages. \\ | ||
| - | |||
| - | __List of available status:__ | ||
| - | * Pending | ||
| - | * Queued | ||
| - | * Sent | ||
| - | * Failed | ||
| - | * Succeed | ||
| - | * Try 1, 2, 3, 4, 5 | ||
| - | |||
| - | {{:images:senddata_v1.0.png?800|TX data are displayed}} | ||
| - | |||
| - | ===== Sending data from a CSV file ===== | ||
| - | |||
| - | LoRa frames can be sent to end-devices from a CSV file, and all send frames can be downloaded from the web interface. | ||
| - | |||
| - | ==== File Format ==== | ||
| - | |||
| - | Depending on the version of the firmware, the template to use changes. Templates can be downloaded from the [[wiki:resources#templates|resources]] page. Make sure to use the template that suits your gateway. | ||
| - | |||
| - | <file csv TX_Data_Template_v1.1.1.csv> | ||
| - | endpoint_id,port,acknowledge,try_number,payload | ||
| - | </file> | ||
| - | |||
| - | * ''endpoint_id'': Device EUI or Device Address (depends on activation procedure). This field name may vary depending on SPN version. | ||
| - | * ''port'': Port used (in LoRaWAN protocol). | ||
| - | * ''acknowledge'': true or false. | ||
| - | * ''try_number'': Number of retry before abort. | ||
| - | * ''payload'': Payload in base 64 format. | ||
| - | |||
| - | ==== Example ==== | ||
| - | |||
| - | <file csv TX_Data_Example_v1.1.1.csv> | ||
| - | 18B20000000BAA,2,true,3,dGVzdA== | ||
| - | 18B20000000BAA,5,false,3,dGVzdA== | ||
| - | 18B20000000BAA,2,false,2,dGVzdA== | ||
| - | </file> | ||
| - | |||
| - | ===== class A communication ===== | ||
| - | |||
| - | "Following each uplink transmission the end-device opens two short receive windows. The receive window start times are defined using the end of the transmission as a reference." | ||
| - | |||
| - | "If the network intends to transmit a downlink to an end-device, it will always initiate the transmission precisely at the beginning of one of those two receive windows." | ||
| - | |||
| - | {{:wiki:class_a_transmition.png?450nolink|}} | ||
| - | |||
| - | //Extract from the LoRaWan Specification ([[https://www.lora-alliance.org/ |LoRa-alliance]])// | ||
| - | |||
| - | ===== class C communication ===== | ||
| - | |||
| - | "Class C devices implement the same two receive windows as Class A devices, but they do not close RX2 window until they need to send again. Therefore they may receive a downlink in the RX2 window at nearly any time, including downlinks sent for the purpose of MAC command or ACK transmission. A short listening window on RX2 frequency and data rate is also opened between the end of the transmission and the beginning of the RX1 receive window." | ||
| - | |||
| - | {{:wiki:class_c_transmition.png?600nolink|}} | ||
| - | |||
| - | //Extract from the LoRaWan Specification ([[https://www.lora-alliance.org/ |LoRa-alliance]])// | ||
wiki/data_transmission.1584365361.txt.gz · Last modified: 2020/03/16 14:29 by ghi
Page Tools
