Skip to Content
Version 70.1 by Mengting Qiu on 2025/02/14 16:21
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
67 * 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]].
68 * Software: [[OTA_Tool>>https://www.dropbox.com/scl/fo/9kqeqf6wmet10o9hgxuwa/h?rlkey=4ikrg6kg5v0yjxwhp0i37wrv7&dl=0]]. Only support Windows now
69
70 [[image:image-20230513120722-2.png||height="409" width="866"]]
71
72
73 == 3.2 OTA Update Firmware via Mobile Phone + LA66 ==
74
75
76
77 == 3.3 OTA Update Firmware via PC ==
78
79
80 (% class="wikigeneratedid" %)
81 (% class="mark text-uppercase" %)**Video Instruction:**(%%) ~-~- OTA Upgrade Firmware (via LoRa) of LoRaWAN Sensors**: [[https:~~/~~/youtu.be/SSvOqvBrwGg>>https://youtu.be/SSvOqvBrwGg]]**
82
83
84 === (% style="color:blue" %)**Step1:**(%%) Plug LA66 USB to PC and run OTA_Tool. ===
85
86
87 [[image:image-20250121091115-1.png]]
88
89
90 === (% style="color:blue" %)**Step2:**(%%) Set up OTA Tool ===
91
92
93 * (% style="color:blue" %)**DevEUI**(%%): Input DevEUI of your sensor
94
95 * (% style="color:blue" %)**Password**(%%): Passord of your sensor**(Last eight bytes/** **Last 16 characters of APPSKEY)**
96
97 * (% style="color:blue" %)**Port**(%%): Com port of LA66 USB
98
99 * (% style="color:blue" %)**LoRa_Freq**(%%): Choose the shipped frequency band of your sensor.
100
101 * (% 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.
102
103 * (% 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:
104
105 [[image:image-20230114174640-3.png||height="130" width="1169"]]
106
107
108 === (% style="color:blue" %)**Step3:**(%%) After re-plugging the LA66 USB, click "Start" in the OTA tool. ===
109
110
111 Upon re-plugging, the LA66 USB will reboot and broadcast the update process using the Dev EUI and passcode
112
113
114 === (% style="color:blue" %)**Step4:** (%%)Press reset button on the end node, or re-activate the end node. ===
115
116 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.
117
118 [[image:image-20250121093705-3.png]]
119
120 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.
121
122
123 === (% style="color:blue" %)**Step5:**(%%) Check result. ===
124
125
126 Below shows the update successul result.
127
128 [[image:image-20250121093834-4.png]]
129
130
131 = 4. FAQ =
132
133 == 4.1 OTA_Tool supports two upgrade methods for -LB products. ==
134
135
136 (% style="color:red" %)**Note: The premise of using OTA_Tool is that all your devices have bootloaders.**
137
138 (% style="color:red" %)**1. **(%%)Only devices with bootloader can perform OTA upgrades(OTA upgrade method).
139
140 (% 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**(%%).
141
142 * 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.
143
144 [[image:image-20250122104151-4.png||height="318" width="673"]]
145
146 * 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.
147
148 [[image:image-20250122104131-3.png||height="330" width="674"]]
149
150
151 == 4.2 Where to find OTA Password? ==
152
153
154 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.
155
156 [[image:image-20230519102907-2.png||height="286" width="580"]]
157
158
159 == 4.3 How about if i upgrade a crashed firmware via OTA update? ==
160
161
162 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.
163
164 (% style="color:red" %)**Here are notice:**
165
166 ~1. OTA update frequency depend on the firmware frequency. If there is no frequency in the firmware. Bootloader will use EU868 as default frequency.
167
168 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.
169
170
171 == 4.4 How to update the LA66 OTA Dongle V1.1 via mobile phone? ==
172
173
174 [[image:image-20250122113225-5.png||height="259" width="615"]]
175
176 * 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.
177
178 [[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]].
179
180 Tool Download: [[Download link form Dropbox.>>https://www.dropbox.com/scl/fo/gyscmfn1s03oz3n8rif8w/AJW7JoMQsQ56dtlls2SNf9c?rlkey=3q2cxwriyzh26vuairx01yebc&st=be5jv92w&dl=0]] 
181
182 Operation instructions: [[Reference for operating procedures.>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1.3.3LA66upgrade]]
183
184 * 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]]
185
186 Please refer to FAQ 4.7 for detailed reasons.
187
188
189 == 4.5 Will OTA update effect the Local LoRaWAN Network. ==
190
191 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.
192
193 (% class="mark" %)#Define the OTA frequency use for OTA.
194 #End Node has FRE1 and SF=5. So don't change FRE1 settings
195 #FRE2 include several frequencies point.
196 #PC first use FRE1 to create connection to end node, then use one of FRE2 frequencies to process downlink.
197
198 (% class="mark" %)#Format:
199 #Frequency Band;FRE1;FRE2
200 EU868;869.0;868.7,868.9
201 IN865;866.9;865.1,865.3
202 KZ865;866.5;866.1,866.3
203 KR920;921.7;921.3,921.5
204 MA869;870.5;870.7,870.9
205 US915;923.1;923.7,924.1
206 CN470;505.5;605.7,505.9
207 AU915;923.7;924.7,925.5
208 AS923;923.5;923.3,923.7
209 AS923-2;921.2;921.8,922.0
210 AS923-3;916.4;917.0,917.2
211 AS923-4;917.1;917.6,917.8
212 EU433;434.5;433.9,434.1
213 RU864;869.3;869.5,869.7
214
215
216 == 4.6 The old version LA66 is different from the new version LA66. Can OTA_Tool be used for both versions? ==
217
218
219 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]]
220
221 [[image:image-20250122134752-6.png||height="288" width="543"]]
222
223 In summary, as long as your LA66 has a boot loader, either LA66 V1 or LA66 V2 can use OTA_Tool.
224
225
226 == 4.7 Why can't LA66 burn its own working firmware after it is used for OTA upgrade of -LB products? ==
227
228
229 We are sorry for the inadequacy of LA66 for OTA updates in the past.
230
231 * 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**(%%).
232
233 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.
234
235 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.
236
237 [[image:image-20250122113225-5.png||height="336" width="798"]]
238
239 * 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.
240
241 = 5. OTA Tool Known Bug: =
242
243
244 ~1. If user click "(% style="color:blue" %)**Start**"(%%) but there is issue during update. User may need to close and open the tool again.
245
246
247