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