Version 77.1 by Mengting Qiu on 2025/02/19 10:08

Show last authors
1 **Table of Contents:**
2
3 {{toc/}}
4
5
6
7 = 1. Overview =
8
9
10 There are some new models of Dragino sensors support OTA update via Private LoRa Protocol, (Even the sensor runs LoRaWAN protocol by default).
11
12 User can use the OTA update to update the configure file or firmware to the sensors.
13
14
15 = 2. Support Models =
16
17
18 Here list the models that support OTA Update.
19
20 {{velocity}}
21 $xwiki.ssfx.use("js/xwiki/table/table.css")
22 $xwiki.jsfx.use("js/xwiki/table/tablefilterNsort.js", true)
23 {{/velocity}}
24
25 (% border="1" cellspacing="5" class="doOddEven filterable grid sortable" id="tableid" style="background-color:#ffffff; width:670px" %)
26 (% class="sortHeader" %)|=(% style="width: 258px; background-color: rgb(217, 226, 243);" %)Models|=(% style="width: 158px; background-color: rgb(217, 226, 243);" %)Firmware Version|=(% style="width: 251px;background-color:#D9E2F3" %)Comments
27 |(% style="width:258px" %)RS485-LB/LS|(% style="width:158px" %)All firmware version|(% style="width:251px" %)
28 |(% style="width:258px" %)SN50v3-LB|(% style="width:158px" %)All firmware version|(% style="width:251px" %)
29 |(% style="width:258px" %)PS-LB-NA|(% style="width:158px" %)All firmware version|(% style="width:251px" %)
30 |(% style="width:258px" %)TS01-LB/LS|(% style="width:158px" %)All firmware version|(% style="width:251px" %)
31 |(% style="width:258px" %)CS01-LB|(% style="width:158px" %)All firmware version|(% style="width:251px" %)
32 |(% style="width:258px" %)AIS01-LB|(% style="width:158px" %)All firmware version|(% style="width:251px" %)
33 |(% style="width:258px" %)TC01-LB/ TC11-LB|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
34 |(% style="width:258px" %)LHT65N|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
35 |(% style="width:258px" %)LHT65N-PIR,LHT65N-E31F|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
36 |(% style="width:258px" %)D20-LB/D20S-LB/D22-LB/D23-LB|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
37 |(% style="width:258px" %)S31/S31B-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
38 |(% style="width:258px" %)AQS01-L|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
39 |(% style="width:258px" %)UV254-LB|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
40 |(% style="width:258px" %)SDI-12-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
41 |(% style="width:258px" %)SE01-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
42 |(% style="width:258px" %)PS-LB|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
43 |(% style="width:258px" %)SE02-LB|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
44 |(% style="width:258px" %)SPH01-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
45 |(% style="width:258px" %)LMS01-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
46 |(% style="width:258px" %)WL03A-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
47 |(% style="width:258px" %)DS03A-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
48 |(% style="width:258px" %)CPL03-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
49 |(% style="width:258px" %)SW3L-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
50 |(% style="width:258px" %)LCC01-LB|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
51 |(% style="width:258px" %)PS-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
52 |(% style="width:258px" %)LDS12-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
53 |(% style="width:258px" %)LDS40-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
54 |(% style="width:258px" %)DDS75-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
55 |(% style="width:258px" %)DDS45-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
56 |(% style="width:258px" %)DDS20-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
57 |(% style="width:258px" %)DDS04-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
58 |(% style="width:258px" %)MDS120-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
59 |(% style="width:258px" %)MDS200-LB/LS|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
60 |(% style="width:258px" %)DS20L|(% style="width:158px" %)All Firmware Version|(% style="width:251px" %)
61
62 = 3. How to do OTA update =
63
64 == 3.1 Required Components ==
65
66 * See FAQ 4.4 for how to update LA66 with the [[OTA Dongle Firmware>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/AFhmjtEOaipfBAFrpMCoWrI/LoRaWAN%20End%20Node/LA66%20LoRaWAN%20module/Firmware/OTA_Firmware?dl=0&rlkey=ojjcsw927eaow01dgooldq3nu&subfolder_nav_tracking=1]].
67 * Software: [[OTA_Tool>>https://www.dropbox.com/scl/fo/9kqeqf6wmet10o9hgxuwa/h?rlkey=4ikrg6kg5v0yjxwhp0i37wrv7&dl=0]]. Only support Windows now
68
69 [[image:image-20230513120722-2.png||height="409" width="866"]]
70
71
72 == 3.2 OTA Update Firmware via Mobile Phone + LA66 ==
73
74 === 3.2.1 LA66 upgrade ===
75
76 The LA66 USB connects to the phone via the USB-Type C adapter.
77
78 [[image:image-20250214161955-7.png]]
79
80
81 After the connection is successful, the phone will pop up a prompt box, check it, and click to "OK".
82
83 (% style="color:red" %)**Note:**(%%)**Some mobile phone models need to manually enable the OTG function to properly identify external devices.**
84
85 [[image:image-20250214162012-8.png]]
86
87
88 (% class="wikigeneratedid" id="H-1" %)
89 Then, the Device Tool will automatically jump to the main interface of the tool.
90
91 (% class="wikigeneratedid" %)
92 In the upper left corner of the main interface of the software, click (% _mstmutation="1" style="color:blue" %)**"Upgrade Device"**(%%) and select the "(% _mstmutation="1" style="color:blue" %)**LaA66"**(%%) type.
93
94 (% class="wikigeneratedid" %)
95 [[image:image-20250219095423-2.png]]
96
97 (% class="wikigeneratedid" %)
98 Follow the steps in order:
99
100 (% class="wikigeneratedid" %)
101 ① Click "SELECT UPGRADE FILE" to choose the firmware to upgrade.
102
103 (% class="wikigeneratedid" %)
104 ② After clicking Start, wait for the LA66 to burn in
105
106 (% class="wikigeneratedid" %)
107 [[image:image-20250214162029-9.png]]
108
109 (% class="wikigeneratedid" %)
110 (% style="color:red" %)**Note:**
111
112 (% class="wikigeneratedid" %)
113 **~1. In order to ensure that the LA66 USB works properly, make sure that there is a corresponding bootloader before updating the firmware.**
114
115 (% class="wikigeneratedid" %)
116 **2. If you don't have a bootloader, you need to use the "[[Tremo Programmer>>https://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H3.1.3Howtouploadbootloadertodevice3F]]" software to download it. Click to get [[bootlooder>>url:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/LoRa_OTA_Bootloader_v1.4.bin?rev=1.1]]**, **then refer to this [[link>>https://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LA66%20USB%20LoRaWAN%20Adapter%20User%20Manual/#H1.10.2Updatemethod:A0ForLA66withoutbootloader]] for instructions to burn.**
117
118
119 When the upgrade is complete, it will prompt:"**update successfully**".
120
121 [[image:image-20250214162110-12.png]]
122
123 === ===
124
125 === 3.2.2 LB series ===
126
127 * Upgrade of external tools: LA66 USB
128 [[image:image-20250214161740-1.png]][[image:image-20250214161758-2.png]]
129 * Before using LA66 as a firmware burning tool for -LB products, you need to burn OTA_DONGLE for LA66 first.
130 * Click to get [[bootlooder and OTA_DONGLE.>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/ALF3WtzilGPi-2nOdtQw1Z4/Utility/Sensor%20Manager%20Utility/OTA_Firmware?dl=0&rlkey=ojjcsw927eaow01dgooldq3nu&subfolder_nav_tracking=1]]
131
132 [[image:image-20250219094223-1.png||height="324" width="698"]]
133
134 * Refer to Section 3.2.1 to burn OTA DONGLEV1.1 for LA66.
135
136 The LA66 USB connects to the phone via the USB-Type c adapter.
137
138 [[image:image-20250214161844-3.png]]
139
140
141 After the connection is successful, the phone will pop up a prompt box, check it and click to confirm.
142
143 (% style="color:red" %)**Note:**(%%)**Some models of cell phones require the OTG function of the cell phone system to be enabled manually in order to recognize the external device correctly.**
144
145 [[image:image-20250214161907-4.png]]
146
147
148 (% class="wikigeneratedid" id="H-1" %)
149 Then, the Device Tool will automatically jump to the main interface of the tool.
150
151 (% class="wikigeneratedid" %)
152 In the upper left corner of the main interface of the software, click (% _mstmutation="1" style="color:blue" %)**"Upgrade Device"**(%%) and select the LB type.
153
154 (% class="wikigeneratedid" %)
155 Follow the steps in order:
156
157 (% class="wikigeneratedid" %)
158 ① Enter the DUIEI,
159
160 (% class="wikigeneratedid" %)
161 ② Enter the PIN (**the PIN is the last 8 bytes of APPSKEY**),
162
163 (% class="wikigeneratedid" %)
164 ③ Select the LoRa frequency to match the original frequency of the node,
165
166 (% class="wikigeneratedid" %)
167 ④ Choose the upgrade file,(% style="color:red" %)**(The firmware upgrade file format only supports .bin files)**
168
169 (% class="wikigeneratedid" %)
170 ⑤ After pressing the device's reset button, click start.
171
172 (% class="wikigeneratedid" %)
173 (% style="color:red" %)**Note:**
174
175 (% class="wikigeneratedid" %)
176 **~1. (If you are unable to access the upgrade for an extended period of time, you can perform the device reset step again.)**
177
178 (% class="wikigeneratedid" %)
179 **2. (If the user does not want to open the case, he/she can press and hold the ACT key for 5s until the device flashes green; this action is equivalent to pressing the reset button.)**
180
181 [[image:image-20250214161928-5.png]]
182
183
184 (% class="wikigeneratedid" id="H-2" %)
185 When the upgrade is complete, it will prompt:"**update successfully**".
186
187 [[image:image-20250214161941-6.png]]
188
189
190 == 3.3 OTA Update Firmware via PC ==
191
192
193 (% class="wikigeneratedid" %)
194 (% class="mark text-uppercase" %)**Video Instruction:**(%%) ~-~- OTA Upgrade Firmware (via LoRa) of LoRaWAN Sensors**: [[https:~~/~~/youtu.be/SSvOqvBrwGg>>https://youtu.be/SSvOqvBrwGg]]**
195
196
197 === (% style="color:blue" %)**Step1:**(%%) Plug LA66 USB to PC and run OTA_Tool. ===
198
199
200 [[image:image-20250121091115-1.png]]
201
202
203 === (% style="color:blue" %)**Step2:**(%%) Set up OTA Tool ===
204
205
206 * (% style="color:blue" %)**DevEUI**(%%): Input DevEUI of your sensor
207
208 * (% style="color:blue" %)**Password**(%%): Passord of your sensor**(Last eight bytes/** **Last 16 characters of APPSKEY)**
209
210 * (% style="color:blue" %)**Port**(%%): Com port of LA66 USB
211
212 * (% style="color:blue" %)**LoRa_Freq**(%%): Choose the shipped frequency band of your sensor.
213
214 * (% style="color:blue" %)**Upload_File**(%%): The firmware to be upload to the sensor. make sure the firmware is with surfix _without_bootloader. For example: LHT65N_EU868_v1.5_without_bootloader.
215
216 * (% style="color:blue" %)**DEUI_File**(%%): If customer has lots of sensors. He can also import the Dev EUI files and use droplist to choose the sensor to update. (If you did not ask us for a uniform update file, then you do not need to use this field, please ignore it.) Format is as below:
217
218 [[image:image-20230114174640-3.png||height="130" width="1169"]]
219
220
221 === (% style="color:blue" %)**Step3:**(%%) After re-plugging the LA66 USB, click "Start" in the OTA tool. ===
222
223
224 Upon re-plugging, the LA66 USB will reboot and broadcast the update process using the Dev EUI and passcode
225
226
227 === (% style="color:blue" %)**Step4:** (%%)Press reset button on the end node, or re-activate the end node. ===
228
229 When the OTA Tool displays “**LA66 is scanning for sensor Dev EUI ‘(% style="color:blue" %)DevEUI(%%)’. Please reset the sensor for connection and update**”, press and hold the ACT button on the terminal node for 5 seconds to perform a terminal node reset so that the OTA Tool can connect successfully.
230
231 [[image:image-20250121093705-3.png]]
232
233 In every reboot/ reactivate, the end node will check if there is update request. If end node gets the update request from LA66. End node will check if the Dev EUI and Password match. If match, End node will establish connection with LA66 USB for OTA update.
234
235
236 === (% style="color:blue" %)**Step5:**(%%) Check result. ===
237
238
239 Below shows the update successul result.
240
241 [[image:image-20250121093834-4.png]]
242
243
244 = 4. FAQ =
245
246 == 4.1 OTA_Tool supports two upgrade methods for -LB products. ==
247
248
249 (% style="color:red" %)**Note: The premise of using OTA_Tool is that all your devices have bootloaders.**
250
251 (% style="color:red" %)**1. **(%%)Only devices with bootloader can perform OTA upgrades(OTA upgrade method).
252
253 (% style="color:red" %)**2.**(%%) This is because the boot loader's address is (% style="color:blue" %)**0x08000000**(%%), the general functional firmware's address is (% style="color:blue" %)**0x0800D000**(%%), and burning the firmware through OTA_Tool will only write content to the address (% style="color:blue" %)**0x0800D000**(%%). So whether you use the OTA_Tool's OTA upgrade method or the UART upgrade method, you can only use it to download firmware without a bootloader, otherwise you will incorrectly place the bootloader at address (% style="color:blue" %)**0x08000000**(%%).
254
255 * For OTA_Tool, you can choose to use the (% style="color:blue" %)**OTA upgrade method**(%%), refer to the above upgrade steps in this user manual.
256
257 [[image:image-20250122104151-4.png||height="318" width="673"]]
258
259 * Of course, if you have a USB-TTL adapter, you can also choose to use the [[UART upgrade method>>https://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H3.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]] via OTA_Tool.
260
261 [[image:image-20250122104131-3.png||height="330" width="674"]]
262
263
264 == 4.2 Where to find OTA Password? ==
265
266
267 Each device has a shipped label with OTA Password which is 16 chars. like below. If user don't find this, please send us a photo for the device with Dev EUI to [[support@dragino.com>>mailto:support@dragino.com]] . and we will search the password for you.
268
269 [[image:image-20230519102907-2.png||height="286" width="580"]]
270
271
272 == 4.3 How about if i upgrade a crashed firmware via OTA update? ==
273
274
275 OTA update is done via Bootloader and only change the firmware partition. So update a crash firmware via OTA update won't destroy bootloader and user can use OTA method to update again.
276
277 (% style="color:red" %)**Here are notice:**
278
279 ~1. OTA update frequency depend on the firmware frequency. If there is no frequency in the firmware. Bootloader will use EU868 as default frequency.
280
281 2. OTA update require a reset or reactivate action. If the crash firmware doesn't have them work, user need to manuall push the physic reset button on the PCB or power off/on device.
282
283
284 == 4.4 How to update the LA66 OTA Dongle V1.1 via mobile phone? ==
285
286
287 [[image:image-20250122113225-5.png||height="259" width="615"]]
288
289 * If you have never downloaded LA66 OTA DongleV1.0 to your LA66, you can directly upgrade the LA66 OTA DongleV1.1 program from your phone using the following method.
290
291 [[bootlooder>>url:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/LoRa_OTA_Bootloader_v1.4.bin?rev=1.1]] and [[OTA_firmware>>url:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/LA66%20OTA%20DONGLE%20v1.1.bin?rev=1.1]].
292
293 Tool Download: [[Download link form Dropbox.>>https://www.dropbox.com/scl/fo/gyscmfn1s03oz3n8rif8w/AJW7JoMQsQ56dtlls2SNf9c?rlkey=3q2cxwriyzh26vuairx01yebc&st=be5jv92w&dl=0]] 
294
295 Operation instructions: [[Reference for operating procedures.>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1.3.3LA66upgrade]]
296
297 * If you have burned LA66 OTA DONGLE V1.0 for your LA66 according to previously existing instructions. Then you need to re-burn your LA66 boot loader first: [[LA66 USB LoRaWAN Adapter User Manual - DRAGINO>>url:https://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LA66%20USB%20LoRaWAN%20Adapter%20User%20Manual/#H1.10.2Updatemethod:A0ForLA66withoutbootloader]]
298
299 Please refer to FAQ 4.7 for detailed reasons.
300
301
302 == 4.5 Will OTA update effect the Local LoRaWAN Network. ==
303
304 User can configure the OTA_Frequency.txt file to change the Update frequency point so it won't conflict with the general LoRa Frequency. See below for the file as reference and explain. The OTA update also use a none-use SF (SF=5) which won't conflict with the current use SF.
305
306 (% class="mark" %)#Define the OTA frequency use for OTA.
307 #End Node has FRE1 and SF=5. So don't change FRE1 settings
308 #FRE2 include several frequencies point.
309 #PC first use FRE1 to create connection to end node, then use one of FRE2 frequencies to process downlink.
310
311 (% class="mark" %)#Format:
312 #Frequency Band;FRE1;FRE2
313 EU868;869.0;868.7,868.9
314 IN865;866.9;865.1,865.3
315 KZ865;866.5;866.1,866.3
316 KR920;921.7;921.3,921.5
317 MA869;870.5;870.7,870.9
318 US915;923.1;923.7,924.1
319 CN470;505.5;605.7,505.9
320 AU915;923.7;924.7,925.5
321 AS923;923.5;923.3,923.7
322 AS923-2;921.2;921.8,922.0
323 AS923-3;916.4;917.0,917.2
324 AS923-4;917.1;917.6,917.8
325 EU433;434.5;433.9,434.1
326 RU864;869.3;869.5,869.7
327
328
329 == 4.6 The old version LA66 is different from the new version LA66. Can OTA_Tool be used for both versions? ==
330
331
332 The most obvious hardware difference between LA66 V1 and LA66v2 when burning is the presence of a "RESET "button, and the RESET operation is only for LA66 without a boot loader, you can refer to this link to learn how to upgrade LA66 without a boot loader:[[LA66 USB LoRaWAN Adapter User Manual - DRAGINO>>url:https://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LA66%20USB%20LoRaWAN%20Adapter%20User%20Manual/#H1.10.2Updatemethod:A0ForLA66withoutbootloader]]
333
334 [[image:image-20250122134752-6.png||height="288" width="543"]]
335
336 In summary, as long as your LA66 has a boot loader, either LA66 V1 or LA66 V2 can use OTA_Tool.
337
338
339 == 4.7 Why can't LA66 burn its own working firmware after it is used for OTA upgrade of -LB products? ==
340
341
342 We are sorry for the inadequacy of LA66 for OTA updates in the past.
343
344 * In the past, the download address of LA66 OTA DONGLE V1.0 was (% style="color:blue" %)**0x08000000**(%%), and the address of the bootloader that existed by default when the LA66 was shipped was also (% style="color:blue" %)**0x08000000**(%%).
345
346 Therefore, when you burn OTA_Firmwar v1.0 (LA66 OTA DONGLE v1.0) for the LA66 in order to use the LA66‘s ability to perform OTA upgrades for -LB products, the LA66’s bootloader is overridden.
347
348 So if you need to switch back to the LA66's working firmware, you'll need to refer to this [[link>>https://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LA66%20USB%20LoRaWAN%20Adapter%20User%20Manual/#H1.10.2Updatemethod:A0ForLA66withoutbootloader]] for instructions to burn firmware with a bootloader for the LA66.
349
350 [[image:image-20250122113225-5.png||height="336" width="798"]]
351
352 * For the new version of LA66 OTA DONGLE V1.1, we have changed the supported download address to (% style="color:blue" %)**0x0800D000**(%%) the same as other working firmware addresses, so you can simply use OTA_Tool to burn LA66 OTA DONGLE V1.1 and LA66 working firmware for LA66.
353
354 = 5. OTA Tool Known Bug: =
355
356
357 ~1. If user click "(% style="color:blue" %)**Start**"(%%) but there is issue during update. User may need to close and open the tool again.
358
359
360