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