Wiki source code of Communicate with ABP End Node on the LPS8-V2 Gateway
Version 35.1 by Kilight Cao on 2022/08/06 15:00
Hide last authors
author | version | line-number | content |
---|---|---|---|
![]() |
3.2 | 1 | (% class="wikigeneratedid" %) |
![]() |
30.2 | 2 | **Table of Contents:** |
![]() |
3.2 | 3 | |
4 | {{toc/}} | ||
5 | |||
![]() |
2.1 | 6 | |
![]() |
3.2 | 7 | |
![]() |
30.2 | 8 | |
9 | = 1. Introduction = | ||
10 | |||
11 | |||
![]() |
3.1 | 12 | The LPS8-V2 of Dragino LoRaWAN gateway can communicate with LoRaWAN ABP End Node, the working is based on the built-in server TTN-Stack. |
![]() |
2.1 | 13 | |
![]() |
30.2 | 14 | **It can be used in some cases such as:** |
![]() |
3.1 | 15 | |
![]() |
2.1 | 16 | * No internet connection. |
17 | * Users want to get data forward in the gateway and forward it to their server based on MQTT/HTTP. | ||
![]() |
3.1 | 18 | * Forward the data to the built-in Application server Node-Red. |
19 | * Just storing the data on the gateway or external storage | ||
![]() |
2.1 | 20 | |
![]() |
30.4 | 21 | |
![]() |
30.2 | 22 | **The basic of this feature is the decoding of** (% style="color:blue" %)**LoRaWAN ABP End Node**(%%). **Requirements:** |
23 | |||
![]() |
2.1 | 24 | 1. LoRaWAN End Node in ABP mode. Make sure your end node works in this mode. End node most are default set to OTAA mode |
25 | 1. LoRaWAN Gateway model: LPS8-V2 | ||
26 | 1. System version: Since V.12 | ||
27 | |||
28 | |||
![]() |
30.4 | 29 | |
30 | |||
![]() |
30.2 | 31 | = 2. Quick Start = |
32 | |||
33 | |||
34 | The default factory version of LPS8-V2 is installed with the Built-in LoRaWAN Server: (% style="color:blue" %)**The Things Network - Stack (Open Source 3.19 Version).** | ||
35 | |||
![]() |
12.1 | 36 | Once the gateway is DHCP an IPV4 address, and then you can access the build-in server TTN-Stack. |
![]() |
2.1 | 37 | |
![]() |
3.1 | 38 | |
39 | |||
![]() |
30.2 | 40 | == 2.1. Configure the gateway mode == |
![]() |
3.1 | 41 | |
42 | |||
![]() |
30.2 | 43 | You can access the gateway's Manage Web UI, via the URL ( (% style="color:blue" %)__**//http:~/~/<hostname> or http:~/~/<local-IPV4-address> //**__(%%)) in your browser |
![]() |
3.1 | 44 | |
![]() |
30.2 | 45 | |
46 | |||
47 | === (% style="color:#037691" %)**Selecting the right frequency band**(%%) === | ||
48 | |||
49 | |||
![]() |
12.1 | 50 | [[image:image-20220802142103-1.png]] |
![]() |
3.1 | 51 | |
52 | |||
![]() |
12.1 | 53 | |
![]() |
30.2 | 54 | === (% style="color:#037691" %)**Configure the Semtech UDP forwarder**(%%) === |
55 | |||
56 | |||
![]() |
12.1 | 57 | [[image:image-20220802142147-3.png]] |
58 | |||
59 | |||
60 | |||
61 | == 2.2. Login to the built-in server TTN-Stack == | ||
62 | |||
![]() |
30.2 | 63 | |
![]() |
12.1 | 64 | You can access the gateway's built-in server of **The Things Network - Stack **via the URL( __**//http:~/~/<hostname>:8080 or http:~/~/<local-IPV4-address:8080> //**__) in your browser. |
65 | |||
66 | Such as __**//http:~/~/dragino-54ff12:8080 or [[http:~~/~~/<Local-IPV4-Address~>>>http://<Local-IPV4-Address>]]//**__ | ||
67 | |||
68 | |||
69 | Login account: | ||
70 | |||
![]() |
30.2 | 71 | (% style="background-color:yellow" %)**User ID: ** ** admin** |
![]() |
12.1 | 72 | |
![]() |
30.2 | 73 | (% style="background-color:yellow" %)**Password: ** ** dragino** |
![]() |
12.1 | 74 | |
75 | |||
76 | [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/WebHome/image-20220725171719-1.png?width=769&height=570&rev=1.1||alt="image-20220725171719-1.png"]] | ||
77 | |||
78 | |||
79 | |||
![]() |
30.2 | 80 | == 2.3. Add the gateway & the sensor == |
81 | |||
82 | |||
![]() |
14.1 | 83 | Here only show the image of the finish, more details about how to add the gateway & sensor refer to this wiki: |
![]() |
12.1 | 84 | |
![]() |
14.1 | 85 | |
![]() |
12.1 | 86 | |
![]() |
30.3 | 87 | === (% style="color:#037691" %)**Add the gateway**(%%) === |
88 | |||
89 | |||
![]() |
12.1 | 90 | [[image:image-20220802142946-5.png]] |
91 | |||
92 | |||
93 | |||
![]() |
30.3 | 94 | === (% style="color:#037691" %)**Add the Sensor**(%%) === |
95 | |||
96 | |||
![]() |
12.1 | 97 | [[image:image-20220802143031-6.png||height="794" width="1375"]] |
98 | |||
99 | |||
100 | |||
![]() |
30.3 | 101 | == 2.4. Add the decoder == |
![]() |
12.1 | 102 | |
![]() |
30.3 | 103 | |
![]() |
14.1 | 104 | If you use dragino sensors then you can find the recorder on this URL: |
105 | |||
![]() |
30.3 | 106 | |
![]() |
12.1 | 107 | [[image:image-20220802143129-7.png]] |
108 | |||
109 | |||
110 | |||
![]() |
30.3 | 111 | == 2.5. Visual Data == |
![]() |
12.1 | 112 | |
![]() |
30.3 | 113 | |
![]() |
14.1 | 114 | In this section, you can be seen that the payload of the sensor has been interpreted as visual data. |
![]() |
12.1 | 115 | |
![]() |
14.1 | 116 | And the next part will discuss where to let the data flow。 |
117 | |||
![]() |
30.3 | 118 | |
![]() |
12.1 | 119 | [[image:image-20220802143214-8.png]] |
120 | |||
121 | |||
![]() |
3.1 | 122 | |
![]() |
30.3 | 123 | = 3. Forward the data or store the data = |
124 | |||
125 | |||
![]() |
14.1 | 126 | You are done most of the work, now you just need to plan the flow of data to where. |
![]() |
3.1 | 127 | |
128 | |||
129 | |||
![]() |
30.3 | 130 | == 3.1 Forward data to an external server based on MQTT/HTTP. == |
![]() |
14.1 | 131 | |
![]() |
30.3 | 132 | |
133 | |||
134 | === (% style="color:#037691" %)**MQTT**(%%) === | ||
135 | |||
136 | |||
![]() |
14.1 | 137 | You need to connect to this public address on your external server and subscribe to the topic **(v3/<application_name>/devices/<devices_name>/up)**. |
138 | |||
139 | |||
140 | [[image:image-20220802144754-9.png]] | ||
141 | |||
![]() |
17.1 | 142 | |
143 | **subscribe to the topic and get the data** | ||
144 | |||
145 | [[image:image-20220802145408-10.png]] | ||
146 | |||
147 | |||
148 | |||
149 | |||
![]() |
30.3 | 150 | === (% style="color:#037691" %)**HTTP**(%%) === |
![]() |
14.1 | 151 | |
![]() |
30.3 | 152 | |
![]() |
17.1 | 153 | [[image:image-20220802145450-11.png||height="676" width="1164"]] |
![]() |
14.1 | 154 | |
![]() |
17.1 | 155 | |
156 | |||
![]() |
30.3 | 157 | == 3.2 Forward data to the built-in application server Node-Red. == |
![]() |
3.1 | 158 | |
159 | |||
![]() |
19.1 | 160 | [[image:image-20220802150715-1.png||height="739" width="1171"]] |
![]() |
14.1 | 161 | |
162 | |||
![]() |
3.1 | 163 | |
![]() |
30.3 | 164 | == 3.3 Just storing the data on the gateway or external storage. == |
![]() |
3.1 | 165 | |
![]() |
14.1 | 166 | |
![]() |
35.1 | 167 | Data can be stored or read by subscribing to topics: (% style="color:#037691" %)**v3/<application_name>/devices/<devices_name>/#**. |
![]() |
17.1 | 168 | |
![]() |
35.1 | 169 | Then add the storage node **(write file)**, Users can download the Node-Red flowchart from this link to test data storage:[[attach:test_data_storage.json||target="_blank"]] |
![]() |
3.1 | 170 | |
![]() |
35.1 | 171 | After the configuration is complete, users can find the node logs in the root/ directory |
172 | |||
173 | [[image:image-20220806144426-2.jpeg||height="540" width="1099"]] | ||
174 | |||
175 | [[image:image-20220806144606-3.jpeg||height="676" width="1102"]] | ||
176 | |||
177 | [[image:image-20220806144336-1.jpeg]] | ||
178 | |||
![]() |
30.3 | 179 | = 4. Sent the downlink to the sensor = |
![]() |
3.1 | 180 | |
![]() |
23.1 | 181 | |
![]() |
30.3 | 182 | Downlinks can be scheduled by publishing the message to the topic (% style="color:#037691" %)** v3/<application_name>/devices/<devices_name>/down/push**. |
![]() |
23.1 | 183 | |
![]() |
30.3 | 184 | (% style="color:red" %)**Note**: **Remember that the format of this topic for The Things Stack Open Source deployment would be (v3/<application_name>/devices/<devices_name>/down/push).** |
185 | |||
![]() |
23.1 | 186 | [[MQTT Server ~| The Things Stack for LoRaWAN (thethingsindustries.com)>>url:https://www.thethingsindustries.com/docs/integrations/mqtt/]] |
187 | |||
188 | |||
189 | Instead of /push, you can also use /replace to replace the downlink queue. Replacing with an empty array clears the downlink queue. Example: | ||
190 | |||
![]() |
27.1 | 191 | (% class="box" %) |
192 | ((( | ||
193 | { | ||
194 | "downlinks": [{ | ||
195 | "f_port": 2, | ||
196 | "frm_payload": "AwAA", | ||
197 | "priority": "HIGH", | ||
198 | "confirmed": true | ||
199 | }] | ||
200 | } | ||
201 | ))) | ||
![]() |
23.1 | 202 | |
![]() |
27.1 | 203 | [[image:image-20220802170358-4.png||height="656" width="898"]] |
![]() |
23.1 | 204 | |
![]() |
27.1 | 205 | |
![]() |
23.1 | 206 | [[image:image-20220802164844-3.png||height="345" width="1131"]] |
207 | |||
![]() |
27.1 | 208 | |
209 | |||
![]() |
30.3 | 210 | **Node-red** |
211 | |||
![]() |
27.1 | 212 | Users can download the Node-Red flowchart for testing [[attach:mqtt-test.json||target="_blank"]] |
213 | |||
214 | |||
![]() |
29.1 | 215 | [[image:image-20220802172021-6.png||height="455" width="1240"]] |
216 | |||
![]() |
30.3 | 217 | |
218 | |||
219 | = 5. Trouble Shootings = | ||
220 | |||
221 | |||
222 |