Wiki source code of OTA Update Firmware/Configure for Sensors

Version 51.1 by Mengting Qiu on 2025/01/22 13:47

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

Wiki source code of OTA Update Firmware/Configure for Sensors

Applications

Navigation