Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 97.2
edited by Xiaoling
on 2022/07/09 11:09
Change comment: There is no comment for this version
To version 122.1
edited by David Huang
on 2022/09/08 16:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NDDS75 NB-IoT Distance Detect Sensor User Manual
1 +N95S31B NB-IoT Temperature & Humidity Sensor User Manual
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.David
Content
... ... @@ -1,10 +1,12 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20220709085040-1.png||height="542" width="524"]]
2 +[[image:1657348034241-728.png||height="470" width="470"]]
3 3  
4 4  
5 5  
6 6  
7 7  
8 +
9 +
8 8  **Table of Contents:**
9 9  
10 10  {{toc/}}
... ... @@ -13,30 +13,42 @@
13 13  
14 14  
15 15  
16 -
17 17  = 1.  Introduction =
18 18  
19 -== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
20 20  
21 +== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
22 +
21 21  (((
22 22  
23 23  
24 24  (((
25 -The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
26 -\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
27 -\\NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
28 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
29 -\\NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
30 -\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
27 +The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*.
31 31  )))
32 32  
30 +(((
31 +The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use.
32 +)))
33 +
34 +(((
35 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
36 +)))
37 +
38 +(((
39 +N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report).
40 +)))
41 +
42 +(((
33 33  
34 34  )))
35 35  
36 -[[image:1654503236291-817.png]]
46 +(((
47 +~* make sure you have NB-IoT coverage locally.
48 +)))
37 37  
50 +
51 +)))
38 38  
39 -[[image:1657327959271-447.png]]
53 +[[image:1657348284168-431.png]]
40 40  
41 41  
42 42  
... ... @@ -44,20 +44,16 @@
44 44  
45 45  
46 46  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
47 -* Ultra low power consumption
48 -* Distance Detection by Ultrasonic technology
49 -* Flat object range 280mm - 7500mm
50 -* Accuracy: ±(1cm+S*0.3%) (S: Distance)
51 -* Cable Length: 25cm
61 +* Monitor Temperature & Humidity via SHT31
52 52  * AT Commands to change parameters
53 53  * Uplink on periodically
54 54  * Downlink to change configure
55 55  * IP66 Waterproof Enclosure
66 +* Ultra-Low Power consumption
67 +* AT Commands to change parameters
56 56  * Micro SIM card slot for NB-IoT SIM
57 57  * 8500mAh Battery for long term use
58 58  
59 -
60 -
61 61  == 1.3  Specification ==
62 62  
63 63  
... ... @@ -83,15 +83,9 @@
83 83  * Max continuously current: 130mA
84 84  * Max boost current: 2A, 1 second
85 85  
86 -(% style="color:#037691" %)**Power Consumption**
87 -
88 -* STOP Mode: 10uA @ 3.3v
89 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
90 -
91 -
92 -
93 93  == ​1.4  Applications ==
94 94  
98 +
95 95  * Smart Buildings & Home Automation
96 96  * Logistics and Supply Chain Management
97 97  * Smart Metering
... ... @@ -104,24 +104,64 @@
104 104  
105 105  
106 106  
107 -== 1.5  Pin Definitions ==
111 +== 1.5  Pin Definitions & Switch ==
108 108  
109 109  
110 -[[image:1657328609906-564.png]]
114 +N95S31B use the mother board from NBSN95 which as below.
111 111  
112 112  
117 +[[image:image-20220709144723-1.png]]
113 113  
114 -= 2.  Use NDDS75 to communicate with IoT Server =
115 115  
120 +
121 +=== 1.5.1 Jumper JP2 ===
122 +
123 +
124 +Power on Device when put this jumper.
125 +
126 +
127 +
128 +=== 1.5.2 BOOT MODE / SW1 ===
129 +
130 +
131 +(((
132 +1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
133 +)))
134 +
135 +(((
136 +2) Flash: work mode, device starts to work and send out console output for further debug
137 +)))
138 +
139 +
140 +
141 +=== 1.5.3 Reset Button ===
142 +
143 +
144 +Press to reboot the device.
145 +
146 +
147 +
148 +=== 1.5.4 LED ===
149 +
150 +
151 +It will flash:
152 +
153 +1. When boot the device in flash mode
154 +1. Send an uplink packet
155 +
156 += 2.  Use N95S31B to communicate with IoT Server =
157 +
158 +
116 116  == 2.1  How it works ==
117 117  
161 +
118 118  (((
119 -The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.
163 +The N95S31B is equipped with a NB-IoT module, the pre-loaded firmware in N95S31B will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by N95S31B.
120 120  )))
121 121  
122 122  
123 123  (((
124 -The diagram below shows the working flow in default firmware of NDDS75:
168 +The diagram below shows the working flow in default firmware of N95S31B:
125 125  )))
126 126  
127 127  (((
... ... @@ -128,7 +128,7 @@
128 128  
129 129  )))
130 130  
131 -[[image:1657328659945-416.png]]
175 +[[image:1657520100595-569.png]]
132 132  
133 133  (((
134 134  
... ... @@ -135,30 +135,69 @@
135 135  )))
136 136  
137 137  
138 -== 2.2 ​ Configure the NDDS75 ==
182 +== 2.2 ​ Configure the N95S31B ==
139 139  
140 140  
185 +=== 2.2.1  Power On N95S31B ===
186 +
187 +
188 +[[image:image-20220709150546-2.png]]
189 +
190 +
191 +
141 141  === 2.2.1 Test Requirement ===
142 142  
194 +
143 143  (((
144 -To use NDDS75 in your city, make sure meet below requirements:
196 +To use N95S31B in your city, make sure meet below requirements:
145 145  )))
146 146  
147 -* Your local operator has already distributed a NB-IoT Network there.
148 -* The local NB-IoT network used the band that NSE01 supports.
149 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
199 +* (((
200 +Your local operator has already distributed a NB-IoT Network there.
201 +)))
202 +* (((
203 +The local NB-IoT network used the band that N95S31B supports.
204 +)))
205 +* (((
206 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
207 +)))
150 150  
151 151  (((
152 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
210 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
153 153  )))
154 154  
213 +(((
214 +N95S31B supports different communication protocol such as :
215 +)))
155 155  
156 -[[image:1657328756309-230.png]]
217 +(((
218 +* (((
219 +CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
220 +)))
221 +* (((
222 +raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
223 +)))
224 +* (((
225 +MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
226 +)))
227 +* (((
228 +TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
229 +)))
157 157  
231 +(((
232 +We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server.
233 +)))
158 158  
235 +
236 +)))
159 159  
160 -=== 2.2.2 Insert SIM card ===
238 +[[image:1657350625843-586.png]]
161 161  
240 +
241 +
242 +=== 2.2.3  Insert SIM card ===
243 +
244 +
162 162  (((
163 163  Insert the NB-IoT Card get from your provider.
164 164  )))
... ... @@ -168,20 +168,24 @@
168 168  )))
169 169  
170 170  
171 -[[image:1657328884227-504.png]]
254 +[[image:1657351240556-536.png]]
172 172  
173 173  
174 174  
175 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
258 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
176 176  
260 +
177 177  (((
178 178  (((
179 -User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
263 +User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below.
264 +
265 +
180 180  )))
181 181  )))
182 182  
183 -[[image:image-20220709092052-2.png]]
269 +[[image:1657351312545-300.png]]
184 184  
271 +
185 185  **Connection:**
186 186  
187 187   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -200,149 +200,170 @@
200 200  * Flow Control: (% style="color:green" %)**None**
201 201  
202 202  (((
203 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
290 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
204 204  )))
205 205  
206 206  [[image:1657329814315-101.png]]
207 207  
295 +
208 208  (((
209 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
297 +(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**
210 210  )))
211 211  
212 212  
213 213  
214 -=== 2.2.4 Use CoAP protocol to uplink data ===
302 +=== 2.2.5  Use CoAP protocol to uplink data ===
215 215  
216 -(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
217 217  
305 +(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]**
218 218  
307 +
308 +(((
219 219  **Use below commands:**
310 +)))
220 220  
221 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
222 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
223 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
312 +* (((
313 +(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
314 +)))
315 +* (((
316 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
317 +)))
318 +* (((
319 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
320 +)))
224 224  
322 +(((
323 +
324 +
225 225  For parameter description, please refer to AT command set
326 +)))
226 226  
227 -[[image:1657330452568-615.png]]
328 +[[image:1657352146020-183.png]]
228 228  
229 229  
331 +(((
230 230  After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
333 +)))
231 231  
232 -[[image:1657330472797-498.png]]
335 +[[image:1657352185396-303.png]]
233 233  
234 234  
235 235  
236 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
339 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
237 237  
238 238  
239 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
342 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
240 240  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
241 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
344 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
242 242  
243 -[[image:1657330501006-241.png]]
346 +[[image:1657352391268-297.png]]
244 244  
245 245  
246 -[[image:1657330533775-472.png]]
349 +[[image:1657352403317-397.png]]
247 247  
248 248  
249 249  
250 -=== 2.2.6 Use MQTT protocol to uplink data ===
353 +=== 2.2.7  Use MQTT protocol to uplink data ===
251 251  
252 252  
253 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
254 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
255 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
256 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
257 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
258 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
259 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
356 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
260 260  
261 -[[image:1657249978444-674.png]]
358 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
359 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
360 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
361 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
362 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
363 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
364 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
262 262  
366 +[[image:1657352634421-276.png]]
263 263  
264 -[[image:1657330723006-866.png]]
265 265  
369 +[[image:1657352645687-385.png]]
266 266  
371 +
267 267  (((
268 -MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
373 +To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period.
269 269  )))
270 270  
271 271  
377 +(((
378 +MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
379 +)))
272 272  
273 -=== 2.2.7 Use TCP protocol to uplink data ===
274 274  
275 275  
383 +=== 2.2.8  Use TCP protocol to uplink data ===
384 +
385 +
386 +This feature is supported since firmware version v110
387 +
276 276  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
277 277  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
278 278  
279 -[[image:image-20220709093918-1.png]]
391 +[[image:1657352898400-901.png]]
280 280  
281 281  
282 -[[image:image-20220709093918-2.png]]
394 +[[image:1657352914475-252.png]]
283 283  
284 284  
285 285  
286 -=== 2.2.8 Change Update Interval ===
398 +=== 2.2.9  Change Update Interval ===
287 287  
400 +
288 288  User can use below command to change the (% style="color:green" %)**uplink interval**.
289 289  
290 290  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
291 291  
292 292  (((
293 -(% style="color:red" %)**NOTE:**
406 +
294 294  )))
295 295  
296 -(((
297 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
298 -)))
409 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
299 299  
411 +**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
300 300  
301 301  
302 302  == 2.3  Uplink Payload ==
303 303  
304 -In this mode, uplink payload includes in total 14 bytes
305 305  
417 +(((
418 +N95S31B has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
419 +)))
306 306  
307 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
308 -|=(% style="width: 80px;" %)(((
309 -**Size(bytes)**
310 -)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1**
311 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
312 312  
313 313  (((
314 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
423 +For example:
315 315  )))
316 316  
426 +(((
427 + (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
428 +)))
317 317  
318 -[[image:1657331036973-987.png]]
319 319  
320 320  (((
321 -The payload is ASCII string, representative same HEX:
432 +The uplink payloads are composed in  ASCII String. For example:
322 322  )))
323 323  
324 324  (((
325 -0x72403155615900640c6c19029200 where:
436 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
326 326  )))
327 327  
328 -* (((
329 -Device ID: 0x724031556159 = 724031556159
439 +(((
440 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
330 330  )))
331 -* (((
332 -Version: 0x0064=100=1.0.0
442 +
443 +
444 +(((
445 +(% style="color:red" %)**NOTE:**
333 333  )))
334 334  
335 -* (((
336 -BAT: 0x0c6c = 3180 mV = 3.180V
448 +(% style="color:red" %)
449 +1. (((
450 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
337 337  )))
338 -* (((
339 -Signal: 0x19 = 25
340 -)))
341 -* (((
342 -Distance: 0x0292= 658 mm
343 -)))
344 -* (((
345 -Interrupt: 0x00 = 0
452 +1. (((
453 +**By default, the device will send an uplink message every 1 hour.**
346 346  
347 347  
348 348  
... ... @@ -349,107 +349,153 @@
349 349  
350 350  )))
351 351  
352 -== 2.4  Payload Explanation and Sensor Interface ==
460 +=== 2.3.1  Payload Analyze ===
353 353  
354 354  
355 -=== 2.4.1  Device ID ===
463 +N95S31B uplink payload includes in total 21 bytes
356 356  
465 +
466 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
467 +|=(% style="width: 60px;" %)(((
468 +**Size(bytes)**
469 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2**
470 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
357 357  (((
358 -By default, the Device ID equal to the last 6 bytes of IMEI.
472 +Reserve/ Same as NBSN95 CFGMOD=1
359 359  )))
360 360  
361 361  (((
362 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
476 +No function here.
363 363  )))
478 +)))|(% style="width:77px" %)(((
479 +(((
480 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
481 +)))
364 364  
365 365  (((
366 -**Example:**
484 +By SHT31
367 367  )))
486 +)))|(% style="width:80px" %)(((
487 +(((
488 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
489 +)))
368 368  
369 369  (((
370 -AT+DEUI=A84041F15612
492 +By SHT31
371 371  )))
494 +)))
372 372  
373 373  (((
374 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
497 +
498 +
499 +(((
500 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
375 375  )))
502 +)))
376 376  
377 377  
505 +[[image:1657354294009-643.png]]
378 378  
379 -=== 2.4.2  Version Info ===
380 380  
508 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
509 +
510 +* Device ID: 0x724031607457 = 724031607457
511 +* Version: 0x006e=110=1.1.0
512 +
513 +* BAT: 0x0ccd = 3277 mV = 3.277V
514 +* Signal: 0x1b = 27
515 +* Model: 0x01 = 1
516 +* 0x00dc000ccc= reserve, ignore in N95S31B
517 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
518 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
519 +
381 381  (((
382 -Specify the software version: 0x64=100, means firmware version 1.00.
521 +
383 383  )))
384 384  
385 385  (((
386 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
525 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
387 387  )))
388 388  
528 +In this mode, uplink payload includes 91 bytes in total by default.
389 389  
530 +Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
390 390  
391 -=== 2.4.3  Battery Info ===
532 +|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4
533 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp .....
392 392  
393 -(((
394 -Check the battery voltage for LSE01.
395 -)))
535 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
396 396  
397 -(((
398 -Ex1: 0x0B45 = 2885mV
399 -)))
537 +[[image:image-20220908154949-1.png]]
400 400  
401 -(((
402 -Ex2: 0x0B49 = 2889mV
403 -)))
539 +The payload is ASCII string, representative same HEX:
404 404  
541 +0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where:
405 405  
543 +* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782
544 +* (% style="color:blue" %) Version: 0x000c=120=1.2
545 +* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V
546 +* (% style="color:red" %) Singal: 0x0c = 12
547 +* (% style="color:blue" %) Mod: 0x01 = 1
548 +* TemDS18B20: 0x0000= 0 = 0
549 +* (% style="color:green" %)Interrupt: 0x00= 0
550 +* (% style="color:green" %)adc: 0x0030= 48
551 +* SHTTEM: 0x0114= 276 = 27.6
552 +* SHTHUM:0x0231 =561=56.1%
553 +* (% style="color:red" %) Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
554 +* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
555 +* 8 sets of recorded data: SHTTEM(% style="color:red" %),SHTHUM,Time stamp : //**0113023163199c5e**//,.......
406 406  
407 -=== 2.4.4  Signal Strength ===
557 +=== 2.3.2  Device ID ===
408 408  
409 -(((
410 -NB-IoT Network signal Strength.
411 -)))
412 412  
413 413  (((
414 -**Ex1: 0x1d = 29**
561 +By default, the Device ID equal to the last 6 bytes of IMEI.
415 415  )))
416 416  
417 417  (((
418 -(% style="color:blue" %)**0**(%%)  -113dBm or less
565 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
419 419  )))
420 420  
421 421  (((
422 -(% style="color:blue" %)**1**(%%)  -111dBm
569 +**Example:**
423 423  )))
424 424  
425 425  (((
426 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
573 +AT+DEUI=A84041F15612
427 427  )))
428 428  
429 429  (((
430 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
431 -)))
577 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
432 432  
433 -(((
434 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
579 +
435 435  )))
436 436  
582 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
437 437  
438 438  
439 -=== 2.4.5  Distance ===
585 +By default, the Device ID equal to the last 15 bits of IMEI.
440 440  
441 -Get the distance. Flat object range 280mm - 7500mm.
587 +User can use **AT+DEUI** to set Device ID
442 442  
443 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
589 +**Example:**
444 444  
591 +AT+DEUI=868411056754138
592 +
593 +
594 +=== 2.3.3  Version Info ===
595 +
596 +
445 445  (((
598 +These bytes include the hardware and software version.
599 +)))
600 +
446 446  (((
447 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
602 +Higher byte: Specify hardware version: always 0x00 for N95S31B
448 448  )))
449 -)))
450 450  
451 451  (((
452 -
606 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
453 453  )))
454 454  
455 455  (((
... ... @@ -456,65 +456,85 @@
456 456  
457 457  )))
458 458  
459 -=== 2.4.6  Digital Interrupt ===
460 -
461 461  (((
462 -Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
614 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
463 463  )))
464 464  
465 465  (((
466 -The command is:
618 +
467 467  )))
468 468  
621 +
622 +=== 2.3.4  Battery Info ===
623 +
624 +
469 469  (((
470 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
626 +Ex1: 0x0B45 = 2885mV
471 471  )))
472 472  
473 -
474 474  (((
475 -The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
630 +Ex2: 0x0B49 = 2889mV
476 476  )))
477 477  
478 478  
634 +
635 +=== 2.3.5  Signal Strength ===
636 +
637 +
479 479  (((
480 -Example:
639 +NB-IoT Network signal Strength.
481 481  )))
482 482  
483 483  (((
484 -0x(00): Normal uplink packet.
643 +**Ex1: 0x1d = 29**
485 485  )))
486 486  
487 487  (((
488 -0x(01): Interrupt Uplink Packet.
647 +(% style="color:blue" %)**0**(%%)  -113dBm or less
489 489  )))
490 490  
491 -
492 -
493 -=== 2.4.7  ​+5V Output ===
494 -
495 495  (((
496 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
651 +(% style="color:blue" %)**1**(%%)  -111dBm
497 497  )))
498 498  
499 -
500 500  (((
501 -The 5V output time can be controlled by AT Command.
655 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
502 502  )))
503 503  
504 504  (((
505 -(% style="color:blue" %)**AT+5VT=1000**
659 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
506 506  )))
507 507  
508 508  (((
509 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
663 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
510 510  )))
511 511  
512 512  
513 513  
514 -== 2.5  Downlink Payload ==
668 +=== 2.3.6  Temperature & Humidity ===
515 515  
516 -By default, NDDS75 prints the downlink payload to console port.
517 517  
671 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
672 +
673 +[[image:image-20220709161741-3.png]]
674 +
675 +
676 +Convert the read byte to decimal and divide it by ten.
677 +
678 +
679 +**Example:**
680 +
681 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
682 +
683 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
684 +
685 +
686 +
687 +== 2.4  Downlink Payload ==
688 +
689 +
690 +By default, N95S31B prints the downlink payload to console port.
691 +
518 518  [[image:image-20220709100028-1.png]]
519 519  
520 520  
... ... @@ -551,7 +551,7 @@
551 551  )))
552 552  
553 553  (((
554 -If payload = 0x04FF, it will reset the NDDS75
728 +If payload = 0x04FF, it will reset the N95S31B
555 555  )))
556 556  
557 557  
... ... @@ -562,45 +562,61 @@
562 562  )))
563 563  
564 564  
739 +== 2.5 Humidity and Temperature alarm function ==
565 565  
566 -== 2.6  ​LED Indicator ==
741 +➢ AT Command:
567 567  
743 +AT+ SHHUM=min,max
568 568  
569 -The NDDS75 has an internal LED which is to show the status of different state.
745 +² When min=0, and max≠0, Alarm higher than max
570 570  
747 +² When min≠0, and max=0, Alarm lower than min
571 571  
572 -* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
573 -* Then the LED will be on for 1 second means device is boot normally.
574 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
575 -* For each uplink probe, LED will be on for 500ms.
749 +² When min≠0 and max≠0, Alarm higher than max or lower than min
576 576  
577 -(((
578 -
579 -)))
751 +Example:
580 580  
753 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
581 581  
582 582  
583 -== 2.7  ​Firmware Change Log ==
756 +AT+ SHTEMP=min,max
584 584  
758 +² When min=0, and max≠0, Alarm higher than max
585 585  
586 -Download URL & Firmware Change log
760 +² When min≠0, and max=0, Alarm lower than min
587 587  
588 -(((
589 -[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]
590 -)))
762 +² When min≠0 and max≠0, Alarm higher than max or lower than min
591 591  
764 +Example:
592 592  
593 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
766 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
594 594  
768 +== 2.6 Set the number of data to be uploaded and the recording time ==
595 595  
770 +➢ AT Command:
596 596  
772 +AT+TR=900  ~/~/The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
773 +
774 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
775 +
776 +== 2.7 Read or Clear cached data ==
777 +
778 +➢ AT Command:
779 +
780 +AT+CDP ~/~/ Read cached data
781 +
782 +[[image:image-20220908163102-2.png]]
783 +
784 +AT+CDP=0 ~/~/ Clear cached data
785 +
597 597  == 2.8  ​Battery Analysis ==
598 598  
788 +
599 599  === 2.8.1  ​Battery Type ===
600 600  
601 601  
602 602  (((
603 -The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
793 +The N95S31B battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
604 604  )))
605 605  
606 606  (((
... ... @@ -623,54 +623,35 @@
623 623  
624 624  === 2.8.2  Power consumption Analyze ===
625 625  
626 -(((
627 -Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
628 -)))
629 629  
630 -
631 631  (((
632 -Instruction to use as below:
818 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
633 633  )))
634 634  
635 635  (((
636 -(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
822 +
637 637  )))
638 638  
639 639  
640 -(((
641 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
642 -)))
826 +=== 2.8.3  ​Battery Note ===
643 643  
644 -* (((
645 -Product Model
646 -)))
647 -* (((
648 -Uplink Interval
649 -)))
650 -* (((
651 -Working Mode
652 -)))
653 653  
654 654  (((
655 -And the Life expectation in difference case will be shown on the right.
830 +The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to uplink data, then the battery life may be decreased.
656 656  )))
657 657  
658 -[[image:image-20220709110451-3.png]]
659 659  
660 660  
835 +=== 2.8.4  Replace the battery ===
661 661  
662 -=== 2.8.3  ​Battery Note ===
663 663  
664 664  (((
665 -The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
839 +You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board.
666 666  )))
667 667  
668 668  
669 -
670 -=== 2.8.4  Replace the battery ===
671 -
672 672  (((
673 -The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
844 +The default battery pack of N95S31B includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
674 674  )))
675 675  
676 676  
... ... @@ -677,6 +677,7 @@
677 677  
678 678  = 3. ​ Access NB-IoT Module =
679 679  
851 +
680 680  (((
681 681  Users can directly access the AT command set of the NB-IoT module.
682 682  )))
... ... @@ -683,6 +683,8 @@
683 683  
684 684  (((
685 685  The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
858 +
859 +
686 686  )))
687 687  
688 688  [[image:1657333200519-600.png]]
... ... @@ -691,11 +691,13 @@
691 691  
692 692  = 4.  Using the AT Commands =
693 693  
868 +
694 694  == 4.1  Access AT Commands ==
695 695  
696 -See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
697 697  
872 +See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]]
698 698  
874 +
699 699  AT+<CMD>?  : Help on <CMD>
700 700  
701 701  AT+<CMD>         : Run <CMD>
... ... @@ -735,7 +735,24 @@
735 735  
736 736  AT+SERVADDR  : Server Address
737 737  
914 +AT+TR      : Get or Set record time
738 738  
916 +AT+APN     : Get or set the APN
917 +
918 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
919 +
920 +AT+DNSCFG  : Get or Set DNS Server
921 +
922 +AT+GETSENSORVALUE   : Returns the current sensor measurement
923 +
924 +AT+NOUD      : Get or Set the number of data to be uploaded
925 +
926 +AT+CDP     : Read or Clear cached data
927 +
928 +AT+SHTEMP: Get or Set alarm of temp
929 +
930 +AT+SHHUM: Get or Set alarm of moisture
931 +
739 739  (% style="color:#037691" %)**COAP Management**      
740 740  
741 741  AT+URI            : Resource parameters
... ... @@ -769,6 +769,7 @@
769 769  
770 770  = ​5.  FAQ =
771 771  
965 +
772 772  == 5.1 ​ How to Upgrade Firmware ==
773 773  
774 774  
... ... @@ -781,13 +781,18 @@
781 781  )))
782 782  
783 783  (((
784 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
978 +
979 +
980 +(((
981 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
785 785  )))
983 +)))
786 786  
787 787  
788 788  
789 789  = 6.  Trouble Shooting =
790 790  
989 +
791 791  == 6.1  ​Connection problem when uploading firmware ==
792 792  
793 793  
... ... @@ -803,6 +803,7 @@
803 803  
804 804  == 6.2  AT Command input doesn't work ==
805 805  
1005 +
806 806  (((
807 807  In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
808 808  
... ... @@ -813,7 +813,7 @@
813 813  = 7. ​ Order Info =
814 814  
815 815  
816 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1016 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
817 817  
818 818  
819 819  (% class="wikigeneratedid" %)
... ... @@ -828,7 +828,7 @@
828 828  
829 829  (% style="color:#037691" %)**Package Includes**:
830 830  
831 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
1031 +* N95S31B NB-IoT Temperature and Humidity Sensor
832 832  * External antenna x 1
833 833  )))
834 834  
... ... @@ -837,11 +837,10 @@
837 837  
838 838  (% style="color:#037691" %)**Dimension and weight**:
839 839  
840 -
841 841  * Device Size: 13.0 x 5 x 4.5 cm
842 842  * Device Weight: 150g
843 -* Package Size / pcs : 15 x 12x 5.5 cm
844 -* Weight / pcs : 220g
1042 +* Package Size / pcs : 14.0 x 8x 5 cm
1043 +* Weight / pcs : 180g
845 845  )))
846 846  
847 847  (((
... ... @@ -853,5 +853,8 @@
853 853  
854 854  = 9.  Support =
855 855  
1055 +
856 856  * 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.
857 857  * 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.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
1058 +
1059 +
1657348034241-728.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +127.8 KB
Content
1657348284168-431.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +93.5 KB
Content
1657350248151-650.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
1657350625843-586.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +93.3 KB
Content
1657351240556-536.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +483.6 KB
Content
1657351312545-300.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +675.8 KB
Content
1657352146020-183.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +264.0 KB
Content
1657352185396-303.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.3 KB
Content
1657352391268-297.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +238.0 KB
Content
1657352403317-397.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +547.7 KB
Content
1657352634421-276.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +163.6 KB
Content
1657352645687-385.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.7 KB
Content
1657352898400-901.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +144.8 KB
Content
1657352914475-252.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +157.0 KB
Content
1657354294009-643.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.7 KB
Content
1657520100595-569.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
image-20220709144723-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +413.1 KB
Content
image-20220709150546-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +333.5 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +111.2 KB
Content
image-20220908154949-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +58.5 KB
Content
image-20220908163102-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +29.7 KB
Content