Wiki source code of OTA Update Firmware/Configure for Sensors
Version 31.5 by Karry Zhuang on 2024/07/10 19:30
Hide last authors
| author | 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 | |||
| |
2.1 | 20 | |
| |
1.1 | 21 | {{velocity}} |
| 22 | $xwiki.ssfx.use("js/xwiki/table/table.css") | ||
| 23 | $xwiki.jsfx.use("js/xwiki/table/tablefilterNsort.js", true) | ||
| 24 | {{/velocity}} | ||
| 25 | |||
| |
20.2 | 26 | (% border="1" cellspacing="5" class="doOddEven filterable grid sortable" id="tableid" style="background-color:#f2f2f2; width:670px" %) |
| |
11.4 | 27 | (% class="sortHeader" %)|=(% style="width: 193px;background-color:#D9E2F3" %)Models|=(% style="width: 222px;background-color:#D9E2F3" %)Firmware Version|=(% style="width: 251px;background-color:#D9E2F3" %)Comments |
| |
31.2 | 28 | |(% style="width:193px" %)RS485-LB/LS|(% style="width:222px" %)All firmware version|(% style="width:251px" %) |
| |
11.1 | 29 | |(% style="width:193px" %)SN50v3-LB|(% style="width:222px" %)All firmware version|(% style="width:251px" %) |
| |
31.2 | 30 | |(% style="width:193px" %)PS-LB-NA|(% style="width:222px" %)All firmware version|(% style="width:251px" %) |
| 31 | |(% style="width:193px" %)TS01-LB/LS|(% style="width:222px" %)All firmware version|(% style="width:251px" %) | ||
| 32 | |(% style="width:193px" %)CS01-LB|(% style="width:222px" %)All firmware version|(% style="width:251px" %) | ||
| 33 | |(% style="width:193px" %)AIS01-LB|(% style="width:222px" %)All firmware version|(% style="width:251px" %) | ||
| 34 | |(% style="width:193px" %)TC01-LB/ TC11-LB|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) | ||
| 35 | |(% style="width:193px" %)LHT65N|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) | ||
| 36 | |(% style="width:193px" %)LHT65N-PIR,LHT65N-E31F|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) | ||
| 37 | |(% style="width:193px" %)D20-LB/D20S-LB/D22-LB/D23-LB|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) | ||
| 38 | |(% style="width:193px" %)S31/S31B-LB/LS|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) | ||
| |
28.1 | 39 | |(% style="width:193px" %)AQS01-L|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) |
| |
31.2 | 40 | |(% style="width:193px" %)UV254-LB|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) |
| 41 | |(% style="width:193px" %)SDI-12-LB/LS|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) | ||
| |
31.3 | 42 | |(% style="width:193px" %)SE01-LB/LS|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) |
| |
31.2 | 43 | |(% style="width:193px" %)PS-LB|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) |
| |
31.3 | 44 | |(% style="width:193px" %)SE02-LB|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) |
| |
31.4 | 45 | |(% style="width:193px" %)SPH01-LB/LS|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) |
| 46 | |(% style="width:193px" %)LMS01-LB/LS|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) | ||
| 47 | |(% style="width:193px" %)WL03A-LB/LS|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) | ||
| 48 | |(% style="width:193px" %)DS03A-LB/LS|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) | ||
| |
31.5 | 49 | |(% style="width:193px" %)CPL03-LB/LS|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) |
| 50 | |(% style="width:193px" %)SW3L-LB/LS|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) | ||
| 51 | |(% style="width:193px" %)LCC01-LB|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) | ||
| 52 | |(% style="width:193px" %)PS-LB/LS|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) | ||
| |
31.2 | 53 | |(% style="width:193px" %) |(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) |
| |
31.3 | 54 | |(% style="width:193px" %) |(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) |
| 55 | |(% style="width:193px" %) |(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) | ||
| 56 | |(% style="width:193px" %) |(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) | ||
| |
31.4 | 57 | |(% style="width:193px" %)DS20L|(% style="width:222px" %)All Firmware Version|(% style="width:251px" %) |
| |
2.1 | 58 | |
| |
10.2 | 59 | = 3. How to do OTA update = |
| 60 | |||
| 61 | == 3.1 Required Components == | ||
| 62 | |||
| 63 | |||
| |
7.1 | 64 | * Hardware: [[LA66 USB>>doc:Main.User Manual for LoRaWAN End Nodes.LA66 USB LoRaWAN Adapter User Manual.WebHome]] with [[OTA_firmware>>https://www.dropbox.com/sh/4qnjreg1esxu16i/AADbRjW_tuBP3IIkmf11nSoma?dl=0]] installed. |
| |
20.2 | 65 | |
| |
29.1 | 66 | * Software: [[OTA_Tool>>https://www.dropbox.com/scl/fo/9kqeqf6wmet10o9hgxuwa/h?rlkey=4ikrg6kg5v0yjxwhp0i37wrv7&dl=0]]. Only support Windows now |
| |
7.1 | 67 | |
| |
16.1 | 68 | [[image:image-20230513120722-2.png||height="409" width="866"]] |
| |
7.1 | 69 | |
| |
14.1 | 70 | |
| |
23.1 | 71 | == 3.2 OTA Update Firmware == |
| |
10.2 | 72 | |
| 73 | |||
| |
21.1 | 74 | (% class="wikigeneratedid" %) |
| |
24.1 | 75 | (% class="mark text-uppercase" %)**Video Instruction:**(%%) ~-~- OTA Upgrade Firmware (via LoRa) of LoRaWAN Sensors**: [[https:~~/~~/youtu.be/SSvOqvBrwGg>>https://youtu.be/SSvOqvBrwGg]]** |
| |
21.1 | 76 | |
| 77 | |||
| |
30.1 | 78 | === (% style="color:blue" %)**Step1:**(%%) Plug LA66 USB to PC and run OTA_Tool. === |
| |
10.2 | 79 | |
| 80 | |||
| |
27.1 | 81 | [[image:image-20231212171036-1.png]] |
| |
7.1 | 82 | |
| 83 | |||
| |
10.2 | 84 | === (% style="color:blue" %)**Step2:**(%%) Set up OTA Tool === |
| |
7.1 | 85 | |
| 86 | |||
| |
27.1 | 87 | * (% style="color:blue" %)**DevEUI**(%%): Input DevEUI of your sensor |
| |
10.2 | 88 | |
| |
31.1 | 89 | * (% style="color:blue" %)**Password**(%%): Passord of your sensor**(Last eight bytes of APPSKEY)** |
| |
10.2 | 90 | |
| 91 | * (% style="color:blue" %)**Port**(%%): Com port of LA66 USB | ||
| 92 | |||
| 93 | * (% style="color:blue" %)**LoRa_Freq**(%%): Choose the shipped frequency band of your sensor. | ||
| 94 | |||
| 95 | * (% 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. | ||
| 96 | |||
| 97 | * (% style="color:blue" %)**EUI File**(%%): If customer has lots of sensors. He can also import the Dev EUI files and use droplist to choose the sensor to update. Format is as below: | ||
| 98 | |||
| |
7.1 | 99 | [[image:image-20230114174640-3.png||height="130" width="1169"]] |
| 100 | |||
| 101 | |||
| |
10.2 | 102 | === (% style="color:blue" %)**Step3:**(%%) Press Start in OTA Tool and then Press Reset button to restart LA66 USB === |
| |
7.1 | 103 | |
| |
10.2 | 104 | |
| |
7.1 | 105 | After press reset button, LA66 USB will restart and broadcast update process with the Dev EUI and Password. |
| 106 | |||
| 107 | |||
| |
10.2 | 108 | === (% style="color:blue" %)**Step4:** (%%)Press reset button on the end node, or re-activate the end node. === |
| |
7.1 | 109 | |
| |
10.2 | 110 | |
| |
7.1 | 111 | 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. |
| 112 | |||
| 113 | |||
| |
10.2 | 114 | === (% style="color:blue" %)**Step5:**(%%) Check result. === |
| |
7.1 | 115 | |
| |
10.2 | 116 | |
| |
7.1 | 117 | Below shows the update successul result. |
| 118 | |||
| |
27.1 | 119 | [[image:image-20231212171543-2.png||height="575" width="753"]] |
| |
7.1 | 120 | |
| 121 | |||
| |
23.1 | 122 | == 3.3 OTA Update Configure == |
| 123 | |||
| |
30.1 | 124 | |
| |
24.1 | 125 | (% class="mark text-uppercase" %)**Video Instruction:**(%%) ~-~- OTA Upgrade Configure (via LoRa) of LoRaWAN Sensors**: [[https:~~/~~/youtu.be/5XedoNVkbQQ>>https://youtu.be/5XedoNVkbQQ]]** |
| |
23.1 | 126 | |
| 127 | OTA Update Configure is good for batch update configure in same type of sensors. | ||
| 128 | |||
| 129 | |||
| |
14.1 | 130 | = 4. FAQ = |
| |
7.1 | 131 | |
| |
14.1 | 132 | == 4.1 Can i use other devices to connect to PC if i don't have LA66 USB? == |
| 133 | |||
| 134 | |||
| |
20.2 | 135 | If user doesn't have LA66 USB Adapter, they can still use other Dragino Device to connect to PC for OTA update. |
| 136 | |||
| 137 | (% style="color:blue" %)**Steps:** | ||
| 138 | |||
| |
14.1 | 139 | * Find the suitable mode which base on LA66 chip ( All LoRaWAN model with LB or LS suffix , such as SN50v3-LB) |
| |
20.2 | 140 | |
| |
14.1 | 141 | * Update the LA66 USB OTA firmware to the device. |
| |
20.2 | 142 | |
| |
14.1 | 143 | * Connect the device to PC via UART interface. |
| |
20.2 | 144 | |
| |
14.1 | 145 | * Make sure power off or update the firmware back to original firmware , because the LA66 USB OTA fimware is not low power consumption firmware. it will consume the battery very fast. |
| 146 | |||
| |
19.1 | 147 | == 4.2 Where to find OTA Password? == |
| 148 | |||
| |
20.2 | 149 | |
| |
19.1 | 150 | 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. |
| 151 | |||
| 152 | [[image:image-20230519102907-2.png||height="286" width="580"]] | ||
| 153 | |||
| 154 | |||
| |
20.1 | 155 | == 4.3 How about if i upgrade a crashed firmware via OTA update? == |
| |
19.1 | 156 | |
| |
20.1 | 157 | |
| |
20.2 | 158 | 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 | 159 | |
| |
20.2 | 160 | (% style="color:red" %)**Here are notice:** |
| |
20.1 | 161 | |
| |
20.2 | 162 | ~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 | 163 | |
| |
20.2 | 164 | 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. |
| 165 | |||
| 166 | |||
| |
14.1 | 167 | = 5. OTA Tool Known Bug: = |
| 168 | |||
| 169 | |||
| |
10.2 | 170 | ~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 | 171 | |
| 172 | |||
| |
28.1 | 173 |