OTA Update Firmware/Configure for Sensors

(% 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/ALF3WtzilGPi-2nOdtQw1Z4/Utility/Sensor%20Manager%20Utility/OTA_Firmware?rlkey=ojjcsw927eaow01dgooldq3nu&e=1&subfolder_nav_tracking=1&dl=0]].

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-20250219103117-5.jpeg||height="289" width="718"]]

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-20250219100549-3.png||height="484" width="362"]]

122

123

124

=== 3.2.2 LB series ===

125

126

* Upgrade of external tools: LA66 USB

127

[[image:image-20250214161740-1.png]][[image:image-20250214161758-2.png]]

128

* Before using LA66 as a firmware burning tool for -LB products, you need to burn OTA_DONGLE for LA66 first.

129

* Click to get [[OTA_DONGLE V1.1.>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/ALF3WtzilGPi-2nOdtQw1Z4/Utility/Sensor%20Manager%20Utility/OTA_Firmware?dl=0&rlkey=ojjcsw927eaow01dgooldq3nu&subfolder_nav_tracking=1]]

130

131

[[image:image-20250219094223-1.png||height="324" width="698"]]

132

133

* Refer to [[Section 3.2.1>>||anchor="H3.2.1LA66upgrade"]] to burn OTA DONGLEV1.1 for LA66.

134

135

The LA66 USB connects to the phone via the USB-Type c adapter.

136

137

[[image:image-20250219103130-6.jpeg||height="301" width="747"]]

138

139

140

After the connection is successful, the phone will pop up a prompt box, check it and click to confirm.

141

142

(% 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.**

143

144

[[image:image-20250214161907-4.png]]

145

146

147

(% class="wikigeneratedid" id="H-1" %)

148

Then, the Device Tool will automatically jump to the main interface of the tool.

149

150

(% class="wikigeneratedid" %)

151

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.

152

153

(% class="wikigeneratedid" %)

154

[[image:image-20250219100821-4.png]]

155

156

157

(% class="wikigeneratedid" %)

158

Follow the steps in order:

159

160

(% class="wikigeneratedid" %)

161

① Enter the DUIEI,.

162

163

(% class="wikigeneratedid" %)

164

② Enter the PIN (**the PIN is the last 8 bytes of APPSKEY, It's 16 characters in total**).

165

166

(% class="wikigeneratedid" %)

167

③ Select the LoRa frequency to match the original frequency of the node.

168

169

(% class="wikigeneratedid" %)

170

④ Choose the upgrade file,(% style="color:red" %)**(The firmware upgrade file format only supports .bin files)**

171

172

(% class="wikigeneratedid" %)

173

⑤ Press the reset button of the device to be upgraded and click "Start".

174

175

(% class="wikigeneratedid" %)

176

(% style="color:red" %)**Note:**

177

178

(% class="wikigeneratedid" %)

179

**~1. If you are unable to access the upgrade for an extended period of time, you can perform the device reset step again.**

180

181

(% class="wikigeneratedid" %)

182

**2. If you do not want to open the cover of the device to be upgraded, you can hold down the ACT key for 5s until the device blinks green. This action is the equivalent of pressing the reset button.**

183

184

[[image:image-20250214161928-5.png]]

185

186

187

(% class="wikigeneratedid" id="H-2" %)

188

When the upgrade is complete, it will prompt:"**update successfully**".

189

190

[[image:image-20250214161941-6.png]]

191

192

193

== 3.3 OTA Update Firmware via PC ==

194

195

196

(% class="wikigeneratedid" %)

197

(% class="mark text-uppercase" %)**Video Instruction:**(%%) ~-~- OTA Upgrade Firmware (via LoRa) of LoRaWAN Sensors**: [[https:~~/~~/youtu.be/SSvOqvBrwGg>>https://youtu.be/SSvOqvBrwGg]]**

198

199

200

=== (% style="color:blue" %)**Step1:**(%%) Plug LA66 USB to PC and run OTA_Tool. ===

201

202

203

[[image:image-20250121091115-1.png]]

204

205

206

=== (% style="color:blue" %)**Step2:**(%%) Set up OTA Tool ===

207

208

209

* (% style="color:blue" %)**DevEUI**(%%): Input DevEUI of your sensor

210

211

* (% style="color:blue" %)**Password**(%%): Passord of your sensor**(Last eight bytes/** **Last 16 characters of APPSKEY)**

212

213

* (% style="color:blue" %)**Port**(%%): Com port of LA66 USB

214

215

* (% style="color:blue" %)**LoRa_Freq**(%%): Choose the shipped frequency band of your sensor.

216

217

* (% 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.

218

219

* (% 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:

220

221

[[image:image-20230114174640-3.png||height="130" width="1169"]]

222

223

224

=== (% style="color:blue" %)**Step3:**(%%) After re-plugging the LA66 USB, click "Start" in the OTA tool. ===

225

226

227

Upon re-plugging, the LA66 USB will reboot and broadcast the update process using the Dev EUI and passcode

228

229

230

=== (% style="color:blue" %)**Step4:** (%%)Press reset button on the end node, or re-activate the end node. ===

231

232

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.

233

234

[[image:image-20250121093705-3.png]]

235

236

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.

237

238

239

=== (% style="color:blue" %)**Step5:**(%%) Check result. ===

240

241

242

Below shows the update successul result.

243

244

[[image:image-20250121093834-4.png]]

= 4. FAQ =

== 4.1 OTA_Tool supports two upgrade methods for -LB products. ==

250

251

252

(% style="color:red" %)**Note: The premise of using OTA_Tool is that all your devices have bootloaders.**

253

254

(% style="color:red" %)**1. **(%%)Only devices with bootloader can perform OTA upgrades(OTA upgrade method).

255

256

(% 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**(%%).

257

258

* 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.

259

260

[[image:image-20250122104151-4.png||height="318" width="673"]]

261

262

* 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.

263

264

[[image:image-20250122104131-3.png||height="330" width="674"]]

265

266

267

== 4.2 Where to find OTA Password? ==

268

269

270

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.

271

272

[[image:image-20230519102907-2.png||height="286" width="580"]]

273

274

275

== 4.3 How about if i upgrade a crashed firmware via OTA update? ==

276

277

278

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.

279

280

(% style="color:red" %)**Here are notice:**

281

282

~1. OTA update frequency depend on the firmware frequency. If there is no frequency in the firmware. Bootloader will use EU868 as default frequency.

283

284

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.

285

286

287

== 4.4 How to update the LA66 OTA Dongle V1.1 via mobile phone? ==

288

289

290

[[image:image-20250122113225-5.png||height="259" width="615"]]

291

292

* 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.

293

294

[[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]].

295

296

Tool Download: [[Download link form Dropbox.>>https://www.dropbox.com/scl/fo/gyscmfn1s03oz3n8rif8w/AJW7JoMQsQ56dtlls2SNf9c?rlkey=3q2cxwriyzh26vuairx01yebc&st=be5jv92w&dl=0]]

297

298

Operation instructions: [[Reference for operating procedures.>>||anchor="H3.2.1LA66upgrade"]]

299

300

* 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]]

301

302

Please refer to FAQ 4.7 for detailed reasons.

303

304

305

== 4.5 Will OTA update effect the Local LoRaWAN Network. ==

306

307

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.

308

309

(% class="mark" %)#Define the OTA frequency use for OTA.

310

#End Node has FRE1 and SF=5. So don't change FRE1 settings

311

#FRE2 include several frequencies point.

312

#PC first use FRE1 to create connection to end node, then use one of FRE2 frequencies to process downlink.

313

314

(% class="mark" %)#Format:

315

#Frequency Band;FRE1;FRE2

316

EU868;869.0;868.7,868.9

317

IN865;866.9;865.1,865.3

318

KZ865;866.5;866.1,866.3

319

KR920;921.7;921.3,921.5

320

MA869;870.5;870.7,870.9

321

US915;923.1;923.7,924.1

322

CN470;505.5;605.7,505.9

323

AU915;923.7;924.7,925.5

324

AS923;923.5;923.3,923.7

325

AS923-2;921.2;921.8,922.0

326

AS923-3;916.4;917.0,917.2

327

AS923-4;917.1;917.6,917.8

328

EU433;434.5;433.9,434.1

329

RU864;869.3;869.5,869.7

330

331

332

== 4.6 The old version LA66 is different from the new version LA66. Can OTA_Tool be used for both versions? ==

333

334

335

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]]

336

337

[[image:image-20250122134752-6.png||height="288" width="543"]]

338

339

In summary, as long as your LA66 has a boot loader, either LA66 V1 or LA66 V2 can use OTA_Tool.

340

341

342

== 4.7 Why can't LA66 burn its own working firmware after it is used for OTA upgrade of -LB products? ==

343

344

345

We are sorry for the inadequacy of LA66 for OTA updates in the past.

346

347

* 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**(%%).

348

349

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.

350

351

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.

352

353

[[image:image-20250122113225-5.png||height="336" width="798"]]

354

355

* 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.

356

357

= 5. OTA Tool Known Bug: =

358

359

360

~1. If user click "(% style="color:blue" %)**Start**"(%%) but there is issue during update. User may need to close and open the tool again.

Wiki source code of OTA Update Firmware/Configure for Sensors

Applications

Navigation