Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 75.1 >
edited by Xiaoling
on 2022/12/07 17:32
To version < 81.4 >
edited by Xiaoling
on 2022/12/07 18:13
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -51,8 +51,6 @@
51 51  * Micro SIM card slot for NB-IoT SIM
52 52  * 8500mAh Battery for long-term use
53 53  
54 -
55 -
56 56  == 1.3 Radar probe specification ==
57 57  
58 58  
... ... @@ -66,8 +66,6 @@
66 66  * Vertical Angel: 23°
67 67  
68 68  
69 -
70 -
71 71  == 1.4  Storage Temperature ==
72 72  
73 73  
... ... @@ -91,8 +91,6 @@
91 91  * Sewer
92 92  * Bottom water level monitoring
93 93  
94 -
95 -
96 96  == 1.6  Specification ==
97 97  
98 98  
... ... @@ -110,8 +110,6 @@
110 110  * B20 @H-FDD: 800MHz
111 111  * B28 @H-FDD: 700MHz
112 112  
113 -
114 -
115 115  == 1.7  Installation ==
116 116  
117 117  
... ... @@ -140,23 +140,21 @@
140 140  [[image:image-20221021110615-5.png]]
141 141  
142 142  
143 -== 2.2 ​ Configure NDS03A ==
135 +== 2.2 ​ Configure NMDS200 ==
144 144  
145 -=== 2.2.1 Test Requirement ===
146 146  
138 +To use NMDS200 in your city, make sure to meet below requirements:
147 147  
148 -To use NDS03A in your city, make sure to meet below requirements:
149 -
150 150  * Your local operator has already distributed an NB-IoT Network.
151 -* The local NB-IoT network used the band that NDS03A supports.
141 +* The local NB-IoT network used the band that NMDS200 supports.
152 152  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
153 153  
154 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDS03A will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
144 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NMDS200 will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
155 155  
156 -[[image:image-20221117142300-1.png]]
146 +[[image:image-20221207173300-4.png]]
157 157  
158 158  
159 -=== 2.2.2 Insert NB-IoT SIM card ===
149 +=== 2.2.1 Insert NB-IoT SIM card ===
160 160  
161 161  
162 162  Insert the NB-IoT Card get from your provider.
... ... @@ -166,10 +166,10 @@
166 166  [[image:image-20221021110745-6.png]] ​
167 167  
168 168  
169 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
159 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
170 170  
171 171  
172 -User need to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below.
162 +User need to configure NMDS200 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NMDS200 support AT Commands, user can use a USB to TTL adapter to connect to NMDS200 and use AT Commands to configure it, as below.
173 173  
174 174  (% style="color:blue" %)**Connection:**
175 175  
... ... @@ -192,11 +192,11 @@
192 192  
193 193  * Flow Control: (% style="color:red" %)**None**
194 194  
195 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
185 +Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
196 196  
197 197  ​[[image:image-20221021110817-7.png]]
198 198  
199 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
189 +NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
200 200  
201 201  
202 202  (% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
... ... @@ -203,7 +203,7 @@
203 203  
204 204  
205 205  
206 -=== 2.2.4 Use CoAP protocol to uplink data ===
196 +=== 2.2.3 Use CoAP protocol to uplink data ===
207 207  
208 208  
209 209  (% style="color:red" %)**Note: if you don't have a CoAP server, you can refer this link to set up a CoAP server: **(%%)[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
... ... @@ -222,12 +222,12 @@
222 222  [[image:image-20221021110948-8.png]]
223 223  
224 224  
225 -After configuring the server address and (% style="color:green" %)**reset NDS03A**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
215 +After configuring the server address and (% style="color:green" %)**reset NMDS200**(%%) (via AT+ATZ ), NMDS200 will start to uplink sensor values to the CoAP server.
226 226  
227 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
217 +[[image:1670405841875-916.png]] ​
228 228  
229 229  
230 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
220 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
231 231  
232 232  
233 233  (% style="color:blue" %)**AT Commands:**
... ... @@ -245,7 +245,7 @@
245 245  
246 246  ​
247 247  
248 -=== 2.2.6 Use MQTT protocol to uplink data ===
238 +=== 2.2.5 Use MQTT protocol to uplink data ===
249 249  
250 250  
251 251  (% style="color:blue" %)**AT Commands:**
... ... @@ -267,7 +267,7 @@
267 267  ​ [[image:image-20221118103445-7.png]]
268 268  
269 269  
270 -[[image:image-20221118103453-8.png||height="608" width="841"]]
260 +[[image:1670405928926-116.png]]
271 271  
272 272  ​
273 273  
... ... @@ -274,7 +274,7 @@
274 274  MQTT protocol has a much higher power consumption compare with UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
275 275  
276 276  
277 -=== 2.2.7 Use TCP protocol to uplink data ===
267 +=== 2.2.6 Use TCP protocol to uplink data ===
278 278  
279 279  
280 280  (% style="color:blue" %)**AT Commands:**
... ... @@ -283,18 +283,19 @@
283 283  
284 284  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
285 285  
286 -​ [[image:image-20221021111125-14.png]]
276 +​ [[image:1670406036256-101.png||height="676" width="713"]]
287 287  
278 +
288 288  [[image:image-20221021111131-15.png]]
289 289  
290 290  ​
291 291  
292 -=== 2.2.8 Change Update Interval ===
283 +=== 2.2.7 Change Update Interval ===
293 293  
294 294  
295 295  User can use below command to change the (% style="color:blue" %)**uplink interval**.
296 296  
297 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
288 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
298 298  
299 299  (% style="color:red" %)**NOTE:**
300 300  
... ... @@ -304,69 +304,50 @@
304 304  == 2.3  Uplink Payload ==
305 305  
306 306  
307 -The uplink payload includes 26 bytes in total by default.
298 +The uplink payload includes 23 bytes in total by default.
308 308  
309 309  Each time the device uploads a data package. The user can use the AT+NOUD command to upload the recorded data.Up to 32 sets of recorded data can be uploaded.
310 310  
311 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
312 312  
313 313  (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
314 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**1**|(% style="width:90px" %)**3**|(% style="width:100px" %)**3**
315 -|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
304 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:90px" %)**2**|(% style="width:100px" %)**2**
305 +|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) Distance 1 |(% style="width:93px" %) Distance  2
316 316  
317 317  (% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
318 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
308 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
319 319  **1-32 group**
320 320  )))
321 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
311 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
322 322  
323 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
313 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
324 324  
315 +[[image:1670406261143-723.png]]
325 325  
326 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
327 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:45px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:60px" %)**1**|(% style="width:60px" %)**1**|(% style="width:87px" %)**3**|(% style="width:80px" %)**3**
328 -|=(% style="width: 96px;" %)**Value**|(% style="width:66px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:70px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:55px" %)Door Status(pb14)|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb14)|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
329 329  
330 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
331 -|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:75px" %)**1**|(% style="width:75px" %)**3**
332 -|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
318 +The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
333 333  
334 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
335 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
336 -**1-32 group**
337 -)))
338 -|(% style="width:102px" %)last open time(pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:100px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
320 +**0x (% style="color:red" %)__f867787050471071__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)**
339 339  
340 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
341 -
342 -[[image:image-20221117145932-2.png]]
343 -
344 -
345 -The payload is ASCII string, representative same HEX:
346 -
347 -**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0ccf__(% style="color:#00b0f0" %) __19__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %) __000017__ (% style="color:#d60093" %)__637590df__(%%)**
348 -
349 349  **where:**
350 350  
351 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
324 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
352 352  
353 353  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
354 354  
355 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
328 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
356 356  
357 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
330 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
358 358  
359 359  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
360 360  
361 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
334 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
362 362  
363 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
336 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
364 364  
365 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
338 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
366 366  
367 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
340 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
368 368  
369 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
370 370  
371 371  == 2.4  Payload Explanation and Sensor Interface ==
372 372  
... ... @@ -389,13 +389,13 @@
389 389  
390 390  Specify the software version: 0x64=100, which means firmware version 1.00.
391 391  
392 -For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
364 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
393 393  
394 394  
395 395  === 2.4.3  Battery Info ===
396 396  
397 397  
398 -Check the battery voltage for NDS03A.
370 +Check the battery voltage for NMDS200.
399 399  
400 400  Ex1: 0x0B45 = 2885mV
401 401  
... ... @@ -420,38 +420,35 @@
420 420  **99**    Not known or not detectable
421 421  
422 422  
423 -=== 2.4.5  Disalarm: (default: 0) ===
395 +=== 2.4.5  Distance ===
424 424  
425 425  
426 -(% style="color:blue" %)**If Disalarm = 1**(%%), NDS03A will only send uplink at every TDC periodically. This is normally use for pulse meter application, in this application, there are many open/close event, and platform only care about the total number of pulse.
398 +[[image:1670407401682-959.png]]
427 427  
428 -(% style="color:blue" %)**If Disalarm = 0**(%%), NDS03A will send uplink at every TDC periodically and send data on each open/close event. This is useful for the application user need to monitor the open/close event in real-time.
400 +(% style="color:blue" %)**Object1 Distance:**
429 429  
430 - (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
402 +Distance between sensor probe to the first object. (unit: cm)
431 431  
404 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
432 432  
433 -=== 2.4.6  Keep Status & Keep Time ===
406 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
434 434  
435 435  
436 -Shows the configure value of Alarm Base on Timeout Feature
409 +(% style="color:blue" %)**Object2 Distance:**
437 437  
411 +Distance between sensor probe to the second object. (unit: cm)
438 438  
439 -=== 2.4.7  Timestamp ===
440 440  
414 +=== 2.4.6  Timestamp ===
441 441  
416 +
442 442  Timestamp : 0x6315537b =1662342011
443 443  
444 444  
445 -=== 2.4.8  Switch Dual Channel Mode ===
446 -
447 -
448 -NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
449 -
450 -
451 451  == 2.5  Downlink Payload ==
452 452  
453 453  
454 -By default, NDS03A prints the downlink payload to console port.
423 +By default, NMDS200 prints the downlink payload to console port.
455 455  
456 456  [[image:image-20221021111414-18.png]] ​
457 457  
... ... @@ -468,7 +468,7 @@
468 468  
469 469  * (% style="color:#037691" %)**Reset**
470 470  
471 -If payload = 0x04FF, it will reset the NDS03A
440 +If payload = 0x04FF, it will reset the NMDS200
472 472  
473 473  * (% style="color:#037691" %)**INTMOD**
474 474  
... ... @@ -478,50 +478,31 @@
478 478  == 2.6  ​LED Indicator ==
479 479  
480 480  
481 -The NDS03A has an internal LED which is to show the status of different states.
450 +The NMDS200 has an internal LED which is to show the status of different states.
482 482  
483 483  * When the device starts normally, the LED will light up for 1 second.
484 484  * After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
485 485  * For each uplink probe, LED will be on for 500ms.
486 486  
487 -== 2.7  Alarm Base on Timeout ==
488 488  
489 489  
490 -NDS03A can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are:
458 +== 2.7  Distance alarm function ==
491 491  
492 492  
493 -(% style="color:blue" %)**1. Keep Status: Status to be monitor**
461 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
494 494  
495 -Keep Status = 1: Monitor Close to Open event
463 +**Example 1:**
496 496  
497 -Keep Status = 0: Monitor Open to Close event
465 +AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
498 498  
467 +AT+ ALARM2 =min,max
499 499  
500 -(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
501 501  
502 -Range 0 ~~ 65535(0xFFFF) seconds.
470 +**Example 2:**
503 503  
504 -If keep time = 0, Disable Alarm Base on Timeout feature.
472 +AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
505 505  
506 -If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
507 507  
508 -
509 -(% style="color:blue" %)**AT Command to configure:**
510 -
511 -(% style="color:blue" %)**PB14 PIN:**
512 -
513 -(% style="color:#037691" %)**AT+TTRIG=1,30** (%%) **~-~->**  When the **Keep Status** change from connected to disconnect, and device remains in disconnect status for more than 30 seconds. NDS03A will send an uplink packet, the [[Alarm bit>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.
514 -
515 -(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
516 -
517 -
518 -(% style="color:blue" %)**PB15 PIN:**
519 -
520 -(% style="color:#037691" %)**AT+TTRIG2=1,30**
521 -
522 -(% style="color:#037691" %)**AT+TTRIG2=0,0 **
523 -
524 -
525 525  == 2.8  Set debug mode ==
526 526  
527 527  
1670405841875-916.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.1 KB
Content
1670405928926-116.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.7 KB
Content
1670406036256-101.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +181.0 KB
Content
1670406261143-723.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.9 KB
Content
1670407401682-959.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +23.7 KB
Content
image-20221207173300-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.0 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0