Wiki source code of LCC01-LB -- LoRaWAN Load Cell Converter User Manual
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | (% style="display:none" %) | ||
2 | |||
3 | [[image:image-20240124140905-2.png||data-xwiki-image-style-alignment="center" height="470" width="474"]] | ||
4 | |||
5 | |||
6 | |||
7 | |||
8 | |||
9 | |||
10 | **Table of Contents:** | ||
11 | |||
12 | {{toc/}} | ||
13 | |||
14 | |||
15 | |||
16 | |||
17 | |||
18 | |||
19 | |||
20 | |||
21 | |||
22 | |||
23 | |||
24 | |||
25 | = 1. Introduction = | ||
26 | |||
27 | == 1.1 What is LoRaWAN Load Cell Converter == | ||
28 | |||
29 | |||
30 | Dragino LCC01-LB is a (% style="color:blue" %)**LoRaWAN Load Cell Converter**(%%) for IoT solutions. It is used to accurately (% style="color:blue" %)**measure the weight of objects**(%%) and then upload it to the IoT server through the LoRaWAN wireless protocol. | ||
31 | |||
32 | The LCC01-LB has a (% style="color:blue" %)**standard 4-wire interface**(%%) which can connect to different type of load cell. It supports (% style="color:blue" %)**different scaling from gram to ton**. | ||
33 | |||
34 | With LCC01-LB and a suitable load cell, user can build up a weight measurement loT solution. Applications are suitable for such as: truck scales, railway scales, supermarketscales, bench scales, heavy duty scales or any type of standard scale. | ||
35 | |||
36 | The LoRa wireless technology used in the LCC01-LB allows the device to send data at low data rates and reach extremely long distances. It provides ultra-long-distance spread spectrum communications and high interference immunity while minimizing current consumption. | ||
37 | |||
38 | LCC01-LB (% style="color:blue" %)**supports BLE configure**(%%) and (% style="color:blue" %)**wireless OTA update**(%%) which make user easy to use. | ||
39 | |||
40 | LCC01-LB is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%) , which can last up to 5 years of long-term use. | ||
41 | |||
42 | Each LCC01-LB is pre-load with a set of unique keys for LoRaWAN registrations, register these keys to LoRaWAN server and it will auto connect after power on. | ||
43 | |||
44 | |||
45 | == 1.2 Features == | ||
46 | |||
47 | |||
48 | * LoRaWAN 1.0.3 Class A | ||
49 | * Ultra-low power consumption | ||
50 | * Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865 | ||
51 | * Standard 4-wire interface to 3rd party load cell | ||
52 | * Weigh Measurement, scale from 100g to 10T | ||
53 | * Support Bluetooth v5.1 and LoRaWAN remote configure | ||
54 | * Support wireless OTA update firmware | ||
55 | * Uplink on periodically | ||
56 | * Downlink to change configure | ||
57 | * 8500mAh Li/SOCl2 Battery | ||
58 | |||
59 | == 1.3 Specification == | ||
60 | |||
61 | |||
62 | (% style="color:#037691" %)**Common DC Characteristics:** | ||
63 | |||
64 | * Supply Voltage: Built-in Battery , 2.5v ~~ 3.6v | ||
65 | * Operating Temperature: -40 ~~ 85°C | ||
66 | |||
67 | (% style="color:#037691" %)**LoRa Spec:** | ||
68 | |||
69 | * Frequency Range, Band 1 (HF): 862 ~~ 1020 Mhz | ||
70 | * Max +22 dBm constant RF output vs. | ||
71 | * RX sensitivity: down to -139 dBm. | ||
72 | * Excellent blocking immunity | ||
73 | |||
74 | (% style="color:#037691" %)**Battery:** | ||
75 | |||
76 | * Li/SOCI2 un-chargeable battery | ||
77 | * Capacity: 8500mAh | ||
78 | * Self-Discharge: <1% / Year @ 25°C | ||
79 | * Max continuously current: 130mA | ||
80 | * Max boost current: 2A, 1 second | ||
81 | |||
82 | (% style="color:#037691" %)**Power Consumption** | ||
83 | |||
84 | * Sleep Mode: 5uA @ 3.3v | ||
85 | * LoRa Transmit Mode: 125mA @ 20dBm, 82mA @ 14dBm | ||
86 | |||
87 | == 1.4 Applicationes == | ||
88 | |||
89 | Weight Measurments | ||
90 | |||
91 | [[image:image-20240127190247-1.png]] | ||
92 | |||
93 | |||
94 | == 1.5 Sleep mode and working mode == | ||
95 | |||
96 | |||
97 | (% style="color:blue" %)**Deep Sleep Mode: **(%%)Sensor doesn't have any LoRaWAN activate. This mode is used for storage and shipping to save battery life. | ||
98 | |||
99 | (% style="color:blue" %)**Working Mode:** (%%)In this mode, Sensor will work as LoRaWAN Sensor to Join LoRaWAN network and send out sensor data to server. Between each sampling/tx/rx periodically, sensor will be in IDLE mode), in IDLE mode, sensor has the same power consumption as Deep Sleep mode. | ||
100 | |||
101 | |||
102 | == 1.6 Button & LEDs == | ||
103 | |||
104 | |||
105 | [[image:image-20250419084721-1.jpeg]] | ||
106 | |||
107 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
108 | |=(% style="width: 167px;background-color:#4F81BD;color:white" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 226px;background-color:#4F81BD;color:white" %)**Action** | ||
109 | |[[image:1749540410711-996.png]] 1~~3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)((( | ||
110 | If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once. | ||
111 | Meanwhile, BLE module will be active and user can connect via BLE to configure device. | ||
112 | ))) | ||
113 | |[[image:1749540413312-506.png]] >3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)((( | ||
114 | (% style="color:green" %)**Green led**(%%) will fast blink 5 times, device will enter (% style="color:#037691" %)**OTA mode**(%%) for 3 seconds. And then start to JOIN LoRaWAN network. | ||
115 | (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network. | ||
116 | Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device join or not join LoRaWAN network. | ||
117 | ))) | ||
118 | |[[image:1749540402049-845.png]] x5|(% style="width:117px" %)Deactivate Device|(% style="width:225px" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means device is in Deep Sleep Mode. | ||
119 | |||
120 | == 1.7 BLE connection == | ||
121 | |||
122 | |||
123 | LCC01-LB supports BLE remote configure. | ||
124 | |||
125 | BLE can be used to configure the parameter of LCC01-LB or see the console output from LCC01-LB. BLE will be only activate on below case: | ||
126 | |||
127 | * Press button to send an uplink | ||
128 | * Press button to active device. | ||
129 | * Device Power on or reset. | ||
130 | |||
131 | If there is no activity connection on BLE in 60 seconds, LCC01-LB will shut down BLE module to enter low power mode. | ||
132 | |||
133 | |||
134 | == 1.8 Mechanical == | ||
135 | |||
136 | |||
137 | [[image:image-20250401161453-1.jpeg]] | ||
138 | |||
139 | |||
140 | == 1.9 Installation == | ||
141 | |||
142 | |||
143 | (% style="color:red" %)**LCC01-LB doesn't include load cell, user need to find the suitable load cell for their application and connect to LCC01-LB.** | ||
144 | |||
145 | |||
146 | === 1.9.1 Connection to the mother board === | ||
147 | |||
148 | |||
149 | One end of the electronic scale transmitter module is connected to the LCC01-LB motherboard and the other end to the load cell. | ||
150 | |||
151 | The electronic scale transmitter and the mother board are connected by default, and the customer does not need to manually connect. | ||
152 | |||
153 | [[image:image-20241015135455-1.jpeg||height="630" width="858"]] | ||
154 | |||
155 | |||
156 | === 1.9.2 Connect Load Cell to LCC01-LB === | ||
157 | |||
158 | |||
159 | Load Cell normally has four wires: S+,S-, E+,E-, Below are the pin mapping to LCC01-LB. The other four wires (EXT,GND,3.3v,5v) are for extra features , which is not used in most of case. | ||
160 | |||
161 | [[image:image-20240119112612-1.png||height="368" width="598"]] | ||
162 | |||
163 | ((( | ||
164 | (% style="color:blue" %)**Wire color Sensor pin Function** | ||
165 | ))) | ||
166 | |||
167 | ((( | ||
168 | ((( | ||
169 | purple(1) <~-~-> EXT_ Input <~-~-> Interrupt trigger pin (Input) | ||
170 | black(2) <~-~-> GND <~-~-> External power supply GND | ||
171 | white(3) <~-~-> VCC-3.3V <~-~-> Used for interrupt triggering or External Power Supply | ||
172 | red(4) <~-~-> +5V Out <~-~-> +5v Power Output | ||
173 | yellow(5) <~-~-> Load Cell (S+) <~-~-> Load Cell Signal + | ||
174 | gray(6) <~-~-> Load Cell (E-) <~-~-> Load Cell Excitation - | ||
175 | blue(7) <~-~-> Load Cell (E+) <~-~-> Load Cell Excitation + | ||
176 | green(8) <~-~-> Load Cell (S-) <~-~-> Load Cell Signal - | ||
177 | ))) | ||
178 | ))) | ||
179 | |||
180 | |||
181 | The package box of LCC01-LB. has four Solder Seal Sleeves which for the easy connect the Load Cell to LCC01-LB., Below shows how to connect wires: | ||
182 | |||
183 | [[image:image-20240110231958-1.png||height="472" width="445"]] | ||
184 | |||
185 | |||
186 | == 1.10 Calibrate LCC01-LB to different scale Load Cells == | ||
187 | |||
188 | === 1.10.1 Configure Utility & Download === | ||
189 | |||
190 | |||
191 | Calibrate is necessary when connecting LCC01-LB. and a Load Cell. The Load Cell Configure Tool is used to calibrate the LCC01-LB. to match different scales of Load Cells and provide the proper output. | ||
192 | |||
193 | **[[Download Link>>https://www.dropbox.com/scl/fo/qy2ghw6ytl8yoyp2n1xdc/h?rlkey=6sr4kdn5y7y6yn5xe9n7q8a4f&dl=0]]. (% style="color:red" %)(Support Windows OS only)(%%)** | ||
194 | |||
195 | |||
196 | === 1.10.2 Hardware Wiring and User Interface === | ||
197 | |||
198 | |||
199 | **Connect LCC01-LB**.** to PC using USB to TTL Adapter.** | ||
200 | |||
201 | [[image:image-20240618090037-1.jpeg]] | ||
202 | |||
203 | |||
204 | (% style="color:blue" %)**Utility Interface** | ||
205 | |||
206 | [[image:image-20240115181015-1.png||height="514" width="507"]] | ||
207 | |||
208 | |||
209 | (% style="color:blue" %)**Detailed instructions for use** | ||
210 | |||
211 | [[image:image-20240115181015-3.png]] | ||
212 | |||
213 | 1. Choose the correct COM port for USB TTL | ||
214 | 1. USB TTL Baud Rate: 9600 | ||
215 | 1. & 4. Connect / Disconnect COM port | ||
216 | |||
217 | [[image:image-20240115181015-4.png||height="322" width="459"]] | ||
218 | |||
219 | 1. AT Password for accessing LCC01-LB. UART | ||
220 | 1. AT Command Input Box | ||
221 | 1. Send an AT Command | ||
222 | 1. Output for LCC01-LB. UART interface | ||
223 | 1. Clear Output | ||
224 | |||
225 | [[image:image-20240115181015-5.png||height="269" width="537"]] | ||
226 | |||
227 | 1. Shows the value obtained by (% style="color:blue" %)**Read the weight once**(%%)** button or (% style="color:blue" %)Continuous reading weight(%%) button** | ||
228 | 1. Read the weight once | ||
229 | 1. Continuous reading weight button | ||
230 | 1. Stop continuous reading button | ||
231 | 1. Time interval for continuous weight reading drop-down box | ||
232 | 1. Drop-down box for median filtering (recommended to use default values) | ||
233 | 1. Drop-down box for average filtering(Please do not input manually for less than 3 seconds) | ||
234 | 1. Weight input box (Use for Weight Calibrate) | ||
235 | 1. Scale Factor ~-~-> Set different Scale. | ||
236 | 1. Write median filtering and average filtering parameters button | ||
237 | 1. Button for writing weight parameters and Scale Factor | ||
238 | 1. ZEROCAL: Zero Calibration | ||
239 | 1. TARE: zero-setting and tare button | ||
240 | 1. More use see below example. | ||
241 | |||
242 | (% style="color:blue" %)**Use of programs** | ||
243 | |||
244 | [[image:image-20240115181015-6.png]] | ||
245 | |||
246 | |||
247 | Then select the corresponding COM port and baud rate. If only one USB-TTL serial port is inserted into the computer, the default program settings can be used directly. | ||
248 | The following screen is the default configuration: | ||
249 | |||
250 | [[image:image-20240115181015-7.png||height="597" width="589"]] | ||
251 | |||
252 | Finally, select the values according to the desired settings or click the button. | ||
253 | |||
254 | (% style="color:red" %)**Please note that only after entering the password and connecting to the serial port will other buttons be available.** | ||
255 | |||
256 | |||
257 | === 1.10.3 Calibrate Steps === | ||
258 | |||
259 | |||
260 | (% class="lead" %) | ||
261 | (% style="color:blue" %)**Step1:**(%%) Zero Calibration | ||
262 | |||
263 | Set the required weight to 0 (normally no objects are placed on the weighing scale) and click the ZEROCAL button | ||
264 | |||
265 | [[image:image-20240116162422-1.png||height="527" width="508"]] | ||
266 | |||
267 | |||
268 | (% class="lead" %) | ||
269 | (% style="color:blue" %)**Step2:**(%%) Determine Scale Factor | ||
270 | |||
271 | Enter Scale Factor according to requirements. The weight reading range is 0~~65535(g). If user want to Calibate to a high scale for example 1T, he should set the scale factory. | ||
272 | |||
273 | For example, | ||
274 | |||
275 | * If the load cell range is 0~~50kg, Use 1 as scale factor | ||
276 | * If the load cell range is 0~~500kg, use 10 as scale factor. the reading range = Weight Reading x Scale Factor = 0 ~~ 655350g (655.35kg) | ||
277 | |||
278 | [[image:image-20240116162714-2.png||height="532" width="516"]] | ||
279 | |||
280 | |||
281 | (% class="lead" %) | ||
282 | (% style="color:blue" %)**Step3:**(%%) Weight Calibration | ||
283 | |||
284 | Place an object of known weight on the weighing scale, enter the weight value of the object, and then click the "WEIGHTCAL" button | ||
285 | |||
286 | When the calibration is completed, Calibrate the Weight Reading to XXXXg OK will be output on the serial port. | ||
287 | |||
288 | (% style="color:red" %)Notice: The best is use a weight close the max range of Load Cell to calibrate | ||
289 | |||
290 | [[image:image-20240116163324-3.png||height="544" width="525"]] | ||
291 | |||
292 | |||
293 | (% class="lead" %) | ||
294 | (% style="color:blue" %)**Step4:**(%%) Verify Weight | ||
295 | |||
296 | Replace other items with known weights and click the "Read the weight once "button to check whether the calibration is completed. | ||
297 | |||
298 | [[image:image-20240116163729-4.png||height="541" width="529"]] | ||
299 | |||
300 | |||
301 | = 2. Configure LCC01-LB to connect to LoRaWAN network = | ||
302 | |||
303 | == 2.1 How it works == | ||
304 | |||
305 | |||
306 | The LCC01-LB is configured as (% style="color:#037691" %)**LoRaWAN OTAA Class A**(%%) mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and press the button to activate the LCC01-LB. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes. | ||
307 | |||
308 | |||
309 | == 2.2 Quick guide to connect to LoRaWAN server (OTAA) == | ||
310 | |||
311 | |||
312 | Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LPS8v2>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/228-lps8v2.html]] as a LoRaWAN gateway in this example. | ||
313 | |||
314 | The LPS8V2 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server. | ||
315 | |||
316 | [[image:image-20240124150739-3.png||height="390" width="749"]] | ||
317 | |||
318 | (% style="color:blue" %)**Step 1:**(%%) Create a device in TTN with the OTAA keys from LCC01-LB. | ||
319 | |||
320 | Each LCC01-LB is shipped with a sticker with the default device EUI as below: | ||
321 | |||
322 | [[image:image-20230426084152-1.png||alt="图片-20230426084152-1.png" height="233" width="502"]](% style="display:none" %) | ||
323 | |||
324 | |||
325 | You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot: | ||
326 | |||
327 | **Create the application.** | ||
328 | |||
329 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SAC01L_LoRaWAN_Temperature%26Humidity_Sensor_User_Manual/WebHome/image-20250423093843-1.png?width=756&height=264&rev=1.1||alt="image-20250423093843-1.png"]] | ||
330 | |||
331 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111305-2.png?width=1000&height=572&rev=1.1||alt="image-20240907111305-2.png"]] | ||
332 | |||
333 | |||
334 | **Add devices to the created Application.** | ||
335 | |||
336 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111659-3.png?width=977&height=185&rev=1.1||alt="image-20240907111659-3.png"]] | ||
337 | |||
338 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111820-5.png?width=975&height=377&rev=1.1||alt="image-20240907111820-5.png"]] | ||
339 | |||
340 | |||
341 | **Enter end device specifics manually.** | ||
342 | |||
343 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907112136-6.png?width=697&height=687&rev=1.1||alt="image-20240907112136-6.png"]] | ||
344 | |||
345 | |||
346 | **Add DevEUI and AppKey. Customize a platform ID for the device.** | ||
347 | |||
348 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907112427-7.png?rev=1.1||alt="image-20240907112427-7.png"]] | ||
349 | |||
350 | |||
351 | (% style="color:blue" %)**Step 2:**(%%) Add decoder. | ||
352 | |||
353 | In TTN, user can add a custom payload so it shows friendly reading. | ||
354 | |||
355 | Click this link to get the decoder: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/]] | ||
356 | |||
357 | Below is TTN screen shot: | ||
358 | |||
359 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS25-LBLDS25-LS--LoRaWAN_LiDAR_Distance_Auto-Clean_Sensor_User_Manual/WebHome/image-20241009140556-1.png?width=1184&height=488&rev=1.1||alt="image-20241009140556-1.png" height="488" width="1184"]] | ||
360 | |||
361 | [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS25-LBLDS25-LS--LoRaWAN_LiDAR_Distance_Auto-Clean_Sensor_User_Manual/WebHome/image-20241009140603-2.png?width=1168&height=562&rev=1.1||alt="image-20241009140603-2.png" height="562" width="1168"]] | ||
362 | |||
363 | |||
364 | (% style="color:blue" %)**Step 3:**(%%) Activate on LCC01-LB | ||
365 | |||
366 | Press the button for 5 seconds to activate the LCC01-LB. | ||
367 | |||
368 | (% style="color:green" %)**Green led**(%%) will fast blink 5 times, device will enter (% style="color:blue" %)**OTA mode**(%%) for 3 seconds. And then start to JOIN LoRaWAN network. (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network. | ||
369 | |||
370 | After join success, it will start to upload messages to TTN and you can see the messages in the panel. | ||
371 | |||
372 | |||
373 | == 2.3 Uplink Payload == | ||
374 | |||
375 | === 2.3.1 Device Status, FPORT~=5 === | ||
376 | |||
377 | |||
378 | Users can use the downlink command(**0x26 01**) to ask Load Cell Converter(LCC) to send device configure detail, include device configure status. LCC will uplink a payload via FPort=5 to server. | ||
379 | |||
380 | The Payload format is as below. | ||
381 | |||
382 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
383 | |(% colspan="6" style="background-color:#4f81bd; color:white" %)**Device Status (FPORT=5)** | ||
384 | |(% style="width:103px" %)**Size (bytes)**|(% style="width:72px" %)**1**|**2**|(% style="width:91px" %)**1**|(% style="width:86px" %)**1**|(% style="width:44px" %)**2** | ||
385 | |(% style="width:103px" %)Value|(% style="width:72px" %)Sensor Model|Firmware Version|(% style="width:91px" %)Frequency Band|(% style="width:86px" %)Sub-band|(% style="width:44px" %)BAT | ||
386 | |||
387 | Example parse in TTNv3 | ||
388 | |||
389 | [[image:1704766955231-196.png]] | ||
390 | |||
391 | |||
392 | (% style="color:#037691" %)**Sensor Model**(%%): For LCC01-LB, this value is 0x32 | ||
393 | |||
394 | (% style="color:#037691" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version | ||
395 | |||
396 | (% style="color:#037691" %)**Frequency Band**: | ||
397 | |||
398 | 0x01: EU868 | ||
399 | |||
400 | 0x02: US915 | ||
401 | |||
402 | 0x03: IN865 | ||
403 | |||
404 | 0x04: AU915 | ||
405 | |||
406 | 0x05: KZ865 | ||
407 | |||
408 | 0x06: RU864 | ||
409 | |||
410 | 0x07: AS923 | ||
411 | |||
412 | 0x08: AS923-1 | ||
413 | |||
414 | 0x09: AS923-2 | ||
415 | |||
416 | 0x0a: AS923-3 | ||
417 | |||
418 | 0x0b: CN470 | ||
419 | |||
420 | 0x0c: EU433 | ||
421 | |||
422 | 0x0d: KR920 | ||
423 | |||
424 | 0x0e: MA869 | ||
425 | |||
426 | |||
427 | (% style="color:#037691" %)**Sub-Band**: | ||
428 | |||
429 | AU915 and US915:value 0x00 ~~ 0x08 | ||
430 | |||
431 | CN470: value 0x0B ~~ 0x0C | ||
432 | |||
433 | Other Bands: Always 0x00 | ||
434 | |||
435 | |||
436 | (% style="color:#037691" %)**Battery Info**: | ||
437 | |||
438 | Check the battery voltage. | ||
439 | |||
440 | Ex1: 0x0B45 = 2885mV | ||
441 | |||
442 | Ex2: 0x0B49 = 2889mV | ||
443 | |||
444 | |||
445 | === 2.3.2 Sensor Data. FPORT~=2 === | ||
446 | |||
447 | |||
448 | (% style="color:red" %)**MOD=1(Collect current object weight regularly.)** | ||
449 | |||
450 | Uplink Payload totals 9 bytes. | ||
451 | |||
452 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:423px" %) | ||
453 | |=(% style="width: 62px;background-color:#4F81BD;color:white" %)((( | ||
454 | **Size(bytes)** | ||
455 | )))|=(% style="width: 45px; background-color: #4F81BD;color:white" %)2|=(% style="width: 52px; background-color:#4F81BD;color:white" %)1|=(% style="width: 94px; background-color:#4F81BD;color:white" %)3|=(% style="width: 95px; background-color:#4F81BD;color:white" %)**1**|=(% style="width: 75px; background-color:#4F81BD;color:white" %)2 | ||
456 | |(% style="width:99px" %)Value|(% style="width:45px" %)((( | ||
457 | BAT | ||
458 | )))|(% style="width:52px" %)MOD|(% style="width:94px" %)Weight Reading|(% style="width:95px" %)Sensor State|(% style="width:75px" %)Scale Factor | ||
459 | |||
460 | [[image:1704780311677-598.png]] | ||
461 | |||
462 | |||
463 | ==== (% style="color:blue" %)**Battery Info**(%%) ==== | ||
464 | |||
465 | Check the battery voltage for LCC01-LB. | ||
466 | |||
467 | Ex1: 0x0E10 = 3600mV | ||
468 | |||
469 | |||
470 | ==== (% style="color:blue" %)**Weight Reading**(%%) ==== | ||
471 | |||
472 | **Example**: | ||
473 | |||
474 | If payload is: 0x00002322H: weight Reading = 2322H = 8994 & Actually weight is | ||
475 | |||
476 | 8994 x Scale Factor (g) | ||
477 | |||
478 | |||
479 | ==== (% style="color:blue" %)**Sensor State**(%%) ==== | ||
480 | |||
481 | Ex1: 0x00=8994g | ||
482 | |||
483 | Ex2: 0x01=-8994g | ||
484 | |||
485 | |||
486 | ==== (% style="color:blue" %)**Scale Factor**(%%) ==== | ||
487 | |||
488 | The (% style="color:red" %)**Weight Reading**(%%) x (% style="color:red" %)**Scale Factor**(%%) determine the actual weight. Default Scale Factor is 1g(gram) | ||
489 | |||
490 | **Example**: | ||
491 | |||
492 | (% border="1" cellspacing="3" style="width:490px" %) | ||
493 | |(% style="background-color:#4f81bd; color:white; width:102px" %)**Weight Info**|(% style="background-color:#4f81bd; color:white; width:103px" %)**Scale Factor**|(% style="background-color:#4f81bd; color:white; width:285px" %)**Actual Weight** | ||
494 | |(% style="width:102px" %)**8994**|(% style="width:103px" %)1|(% style="width:280px" %)8994 x 1g = 8994g = 8.994Kg | ||
495 | |(% style="width:102px" %)**8994**|(% style="width:103px" %)10|(% style="width:280px" %)8994 x 10g = 89940g = 89.94Kg | ||
496 | |(% style="width:102px" %)**8994**|(% style="width:103px" %)255|(% style="width:280px" %)8994 x 255 = 2293470g = 2293.47kg = 2.29347T | ||
497 | |||
498 | (% style="color:red" %)**MOD=2(Collect the weight of objects all the time, and send the current weight if it exceeds the set threshold.)** | ||
499 | |||
500 | Uplink Payload totals 10 bytes. | ||
501 | |||
502 | **This mode is combined with (% style="color:#037691" %)AT+THRESHOLD=weight,Scale Factor.(%%)** | ||
503 | |||
504 | (% border="1" cellspacing="3" style="width:475px" %) | ||
505 | |(% style="background-color:#4f81bd; color:white; width:65px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:40px" %)**2**|(% style="background-color:#4f81bd; color:white; width:40px" %)**1**|(% style="background-color:#4f81bd; color:white; width:90px" %)**3**|(% style="background-color:#4f81bd; color:white; width:80px" %)**1**|(% style="background-color:#4f81bd; color:white; width:80px" %)**2**|(% style="background-color:#4f81bd; color:white; width:80px" %)**1** | ||
506 | |(% style="width:93px" %)Value|(% style="width:42px" %)BAT|(% style="width:53px" %)MOD|(% style="width:73px" %)Weight Reading|(% style="width:63px" %)Sensor State|(% style="width:57px" %)Scale Factor|(% style="width:99px" %)Weight Flag | ||
507 | |||
508 | [[image:1704770093136-213.png]] | ||
509 | |||
510 | |||
511 | ==== (% style="color:blue" %)**Weight Flag**(%%) ==== | ||
512 | |||
513 | This flag indicates whether the object is always weighed. | ||
514 | |||
515 | (% style="color:red" %)**0:**(%%) It means that the object is not weighed repeatedly, | ||
516 | |||
517 | (% style="color:red" %)**1:**(%%) It means that the object has been weighed | ||
518 | |||
519 | |||
520 | == 2.4 Payload Decoder file == | ||
521 | |||
522 | |||
523 | In TTN, use can add a custom payload so it shows friendly reading | ||
524 | |||
525 | In the page (% style="color:#037691" %)**Applications ~-~-> Payload Formats ~-~-> Custom ~-~-> decoder**(%%) to add the decoder from: | ||
526 | [[dragino-end-node-decoder/LCC01-LB at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/LCC01-LB]] | ||
527 | |||
528 | |||
529 | |||
530 | (% aria-label="数据 URI 图像图像小部件" contenteditable="false" role="region" style="background-image:url(http://wiki1.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" tabindex="-1" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||alt="数据 URI 图片" draggable="true" height="15" role="presentation" title="单击并拖动以移动" width="15"]](% aria-label="数据 URI 图像图像小部件" contenteditable="false" role="region" style="background-image:url(http://wiki1.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220, 220, 220, 0.5); display:none" tabindex="-1" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||alt="数据 URI 图片" draggable="true" height="15" role="presentation" title="单击并拖动以移动" width="15"]](% aria-label="数据 URI 图像图像小部件" contenteditable="false" role="region" style="background-image:url(http://wiki1.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" tabindex="-1" title="单击并拖动以调整大小" %)的(% aria-label="数据 URI 图像图像小部件" contenteditable="false" role="region" style="background-image:url(http://wiki1.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" tabindex="-1" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||alt="数据 URI 图片" draggable="true" height="15" role="presentation" title="单击并拖动以移动" width="15"]](% aria-label="数据 URI 图像图像小部件" contenteditable="false" role="region" style="background-image:url(http://wiki1.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220, 220, 220, 0.5); display:none" tabindex="-1" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||alt="数据 URI 图片" draggable="true" height="15" role="presentation" title="单击并拖动以移动" width="15"]](% aria-label="数据 URI 图像图像小部件" contenteditable="false" role="region" style="background-image:url(http://wiki1.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" tabindex="-1" title="单击并拖动以调整大小" %)的 | ||
531 | |||
532 | == 2.5 Frequency Plans == | ||
533 | |||
534 | |||
535 | The LCC01-LB uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets. | ||
536 | |||
537 | [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/]] | ||
538 | |||
539 | |||
540 | = 3. Configure LCC01-LB = | ||
541 | |||
542 | == 3.1 Configure Methods == | ||
543 | |||
544 | |||
545 | LCC01-LB supports below configure method: | ||
546 | |||
547 | * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]]. | ||
548 | * AT Command via UART Connection : See [[UART Connection>>http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]]. | ||
549 | * LoRaWAN Downlink. Instruction for different platforms: See [[IoT LoRaWAN Server>>http://wiki.dragino.com/xwiki/bin/view/Main/]] section. | ||
550 | |||
551 | == 3.2 General Commands == | ||
552 | |||
553 | |||
554 | These commands are to configure: | ||
555 | |||
556 | * General system settings like: uplink interval. | ||
557 | * LoRaWAN protocol & radio related command. | ||
558 | |||
559 | They are same for all Dragino Devices which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki: | ||
560 | |||
561 | [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]] | ||
562 | |||
563 | |||
564 | == 3.3 Commands special design for LCC01-LB == | ||
565 | |||
566 | |||
567 | These commands only valid for LCC01-LB, as below: | ||
568 | |||
569 | |||
570 | === 3.3.1 Set Transmit Interval Time === | ||
571 | |||
572 | |||
573 | Feature: Change LoRaWAN End Node Transmit Interval. | ||
574 | |||
575 | (% style="color:blue" %)**AT Command: AT+TDC** | ||
576 | |||
577 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
578 | |=(% style="width: 156px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 137px;background-color:#4F81BD;color:white" %)**Function**|=(% style="background-color:#4F81BD;color:white" %)**Response** | ||
579 | |(% style="width:156px" %)AT+TDC=?|(% style="width:137px" %)Show current transmit Interval|((( | ||
580 | 30000 | ||
581 | OK | ||
582 | the interval is 30000ms = 30s | ||
583 | ))) | ||
584 | |(% style="width:156px" %)AT+TDC=60000|(% style="width:137px" %)Set Transmit Interval|((( | ||
585 | OK | ||
586 | Set transmit interval to 60000ms = 60 seconds | ||
587 | ))) | ||
588 | |||
589 | (% style="color:blue" %)**Downlink Command: 0x01** | ||
590 | |||
591 | Format: Command Code (0x01) followed by 3 bytes time value. | ||
592 | |||
593 | If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01. | ||
594 | |||
595 | * Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds | ||
596 | * Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds | ||
597 | |||
598 | === 3.3.2 Get Device Status === | ||
599 | |||
600 | |||
601 | Send a LoRaWAN downlink to ask device send Alarm settings. | ||
602 | |||
603 | (% style="color:blue" %)**Downlink Payload: **(%%)0x26 01 | ||
604 | |||
605 | Sensor will upload Device Status via FPORT=5. See payload section for detail. | ||
606 | |||
607 | |||
608 | === 3.3.3 Set Interrupt Mode === | ||
609 | |||
610 | |||
611 | Feature, Set Interrupt mode for PA8 of pin. | ||
612 | |||
613 | When AT+INTMOD=0 is set, PA8 is used as a digital input port. | ||
614 | |||
615 | (% style="color:blue" %)**AT Command: AT+INTMOD** | ||
616 | |||
617 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
618 | |=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 197px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 158px;background-color:#4F81BD;color:white" %)**Response** | ||
619 | |(% style="width:154px" %)AT+INTMOD=?|(% style="width:196px" %)Show current interrupt mode|(% style="width:157px" %)((( | ||
620 | 0 | ||
621 | OK | ||
622 | the mode is 0 =Disable Interrupt | ||
623 | ))) | ||
624 | |(% style="width:154px" %)AT+INTMOD=2|(% style="width:196px" %)((( | ||
625 | Set Transmit Interval | ||
626 | 0. (Disable Interrupt), | ||
627 | ~1. (Trigger by rising and falling edge) | ||
628 | 2. (Trigger by falling edge) | ||
629 | 3. (Trigger by rising edge) | ||
630 | )))|(% style="width:157px" %)OK | ||
631 | |||
632 | (% style="color:blue" %)**Downlink Command: 0x06** | ||
633 | |||
634 | Format: Command Code (0x06) followed by 3 bytes. | ||
635 | |||
636 | This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06. | ||
637 | |||
638 | * Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode | ||
639 | * Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger | ||
640 | |||
641 | === 3.3.4 Get Current Object Weight === | ||
642 | |||
643 | |||
644 | **AT Command: (% style="color:blue" %)AT+GETVALUE(%%)** | ||
645 | |||
646 | **Command format: (% style="color:blue" %)AT+GETVALUE=A300A2A4A5(%%)** | ||
647 | |||
648 | **Return data format:** | ||
649 | |||
650 | (% border="1" cellspacing="3" style="width:510px" %) | ||
651 | |(% style="background-color:#4f81bd; color:white; width:51px" %)**Byte1**|(% style="background-color:#4f81bd; color:white; width:51px" %)**Byte2**|(% style="background-color:#4f81bd; color:white; width:51px" %)**Byte3**|(% style="background-color:#4f81bd; color:white; width:51px" %)**Byte4**|(% style="background-color:#4f81bd; color:white; width:51px" %)**Byte5**|(% style="background-color:#4f81bd; color:white; width:51px" %)**Byte6**|(% style="background-color:#4f81bd; color:white; width:51px" %)**Byte7**|(% style="background-color:#4f81bd; color:white; width:51px" %)**Byte8**|(% style="background-color:#4f81bd; color:white; width:51px" %)**Byte9**|(% style="background-color:#4f81bd; color:white; width:51px" %)**Byte10** | ||
652 | |(% style="width:57px" %)0xAA|(% style="width:59px" %)0xA3|(% style="width:57px" %)0x00|(% style="width:58px" %)0x00|(% style="width:58px" %)0x00|(% style="width:58px" %)0x23|(% style="width:59px" %)0x22|(% style="width:58px" %)0x00|(% style="width:57px" %)0xE8|(% style="width:64px" %)0xFF | ||
653 | |||
654 | **Example**: | ||
655 | |||
656 | **Ex1:** | ||
657 | |||
658 | Accepted: AA A3 00 00 23 22 00 E8 FF | ||
659 | |||
660 | Weight=00*65535+23*256+22=8994, Byte4 is 0, which means positive, and the weight is 8994 | ||
661 | |||
662 | |||
663 | **Ex2:** | ||
664 | |||
665 | Accepted: AA A3 00 01 23 22 00 E8 FF | ||
666 | |||
667 | Weight t=00*65535+23*256+22=8994, Byte4 is 1, which means negative, and the weight t is -8994 | ||
668 | |||
669 | |||
670 | If a negative number appears, it may be that the 0 point has not been calibrated properly. Just follow the calibration process again. | ||
671 | |||
672 | If after recalibration, after placing the object, it was originally 100, but the result shows -100, this situation is caused by the sensor signal line being connected incorrectly, or the pressure sensor being installed incorrectly. | ||
673 | |||
674 | |||
675 | (% style="color:blue" %)**Final weight obtained: Weight x Scale Factor** | ||
676 | |||
677 | **Output:** | ||
678 | |||
679 | Weight Reading= 8994; Scale Factor= 1 | ||
680 | |||
681 | Actual Weight= 8994(g) | ||
682 | |||
683 | |||
684 | === 3.3.5 Set Zero Calibration === | ||
685 | |||
686 | |||
687 | **AT Command: (% style="color:blue" %)AT+ZEROCAL(%%)** | ||
688 | |||
689 | **Command format: (% style="color:blue" %)AT+ZEROCAL=AA00A9ABA8(%%)** | ||
690 | |||
691 | Return success and output Zero Calibration OK. If unsuccessful, return the result and Fail. | ||
692 | |||
693 | |||
694 | === 3.3.6 Set Weight Calibration === | ||
695 | |||
696 | |||
697 | **AT Command: (% style="color:blue" %)AT+WEIGHCAL(%%)** | ||
698 | |||
699 | AT+WEIGHCAL=1000,1 | ||
700 | |||
701 | Calibrate the Weight Reading to 1000 (0x03E8). | ||
702 | |||
703 | Scale Factor to 1(0x01) | ||
704 | |||
705 | |||
706 | **Return:** | ||
707 | |||
708 | Calibrate the weight Reading to 1000g, OK? | ||
709 | |||
710 | |||
711 | === 3.3.7 Set Filter === | ||
712 | |||
713 | |||
714 | **AT Command: (% style="color:blue" %)AT+FILTER(%%)** | ||
715 | |||
716 | **Command format: (% style="color:blue" %)AT+FILTER=03,03(%%)** | ||
717 | |||
718 | Send command format description: | ||
719 | |||
720 | **Data1:** Median filter range: 1, 3, 5, 7, 9 | ||
721 | |||
722 | **Data2:** Average filter range: 1~~50 | ||
723 | |||
724 | |||
725 | Return success and output Median filter, average filter settings OK. If unsuccessful, return the result and Fail. | ||
726 | |||
727 | |||
728 | === 3.3.8 Set Tare === | ||
729 | |||
730 | |||
731 | **AT Command: (% style="color:blue" %)AT+TARE(%%)** | ||
732 | |||
733 | **Command format: (% style="color:blue" %)AT+TARE=AB00AAACAD(%%)** | ||
734 | |||
735 | Return success and output Tare (set to zero, temporarily cleared) OK. | ||
736 | |||
737 | |||
738 | === 3.3.9 Set Threshold === | ||
739 | |||
740 | |||
741 | Feature, when the weighing exceeds the set value, the current weight will be sent immediately | ||
742 | |||
743 | **AT Command: (% style="color:blue" %)AT+THRESHOLD(%%)** | ||
744 | |||
745 | **Command format: (% style="color:blue" %)AT+THRESHOLD=1000,1(%%)** | ||
746 | |||
747 | Send command format description: | ||
748 | |||
749 | **Data1:** weight | ||
750 | |||
751 | **Data2:** Scale Factor | ||
752 | |||
753 | |||
754 | = 4. Battery & Power Consumption = | ||
755 | |||
756 | |||
757 | LCC01-LB use ER26500 + SPC1520 battery pack . See below link for detail information about the battery info and how to replace. | ||
758 | |||
759 | [[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . | ||
760 | |||
761 | |||
762 | = 5. OTA Firmware update = | ||
763 | |||
764 | |||
765 | User can change firmware LCC01-LB to: | ||
766 | |||
767 | * Change Frequency band/ region. | ||
768 | * Update with new features. | ||
769 | * Fix bugs. | ||
770 | |||
771 | Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/scl/fo/3p5c6x13o0z23q3bupf88/h?rlkey=gvrvpf4x51lwng0ih13kn6wfl&dl=0]]** | ||
772 | |||
773 | |||
774 | Methods to Update Firmware: | ||
775 | |||
776 | * (Recommanded way) OTA firmware update via wireless : **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/]]** | ||
777 | * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]]**. | ||
778 | |||
779 | = 6. FAQ = | ||
780 | |||
781 | |||
782 | |||
783 | = 7. Order Info = | ||
784 | |||
785 | |||
786 | Part Number: (% style="color:blue" %)**LCC01-LB-XX** | ||
787 | |||
788 | (% style="color:red" %)**XX**(%%): The default frequency band | ||
789 | |||
790 | * (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band | ||
791 | |||
792 | * (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band | ||
793 | |||
794 | * (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band | ||
795 | |||
796 | * (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band | ||
797 | |||
798 | * (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band | ||
799 | |||
800 | * (% style="color:red" %)**US915**(%%): LoRaWAN US915 band | ||
801 | |||
802 | * (% style="color:red" %)**IN865**(%%): LoRaWAN IN865 band | ||
803 | |||
804 | * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band | ||
805 | |||
806 | = 8. Packing Info = | ||
807 | |||
808 | |||
809 | (% style="color:#037691" %)**Package Includes**: | ||
810 | |||
811 | * LCC01-LB LoRaWAN Load Cell Converter x 1 | ||
812 | |||
813 | (% style="color:#037691" %)**Dimension and weight**: | ||
814 | |||
815 | * Device Size: cm | ||
816 | |||
817 | * Device Weight: g | ||
818 | |||
819 | * Package Size / pcs : cm | ||
820 | |||
821 | * Weight / pcs : g | ||
822 | |||
823 | = 9. Support = | ||
824 | |||
825 | |||
826 | * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. | ||
827 | |||
828 | * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[Support@dragino.cc>>mailto:Support@dragino.cc]]. |