Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 185.1
edited by kai
on 2024/10/18 09:56
Change comment: There is no comment for this version
To version 100.5
edited by Xiaoling
on 2023/08/15 17:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.kai
1 +XWiki.Xiaoling
Content
... ... @@ -16,19 +16,13 @@
16 16  
17 17  = 2. Attach Network =
18 18  
19 -== 2.1 General Configure to attach network ==
20 20  
21 -
22 22  To attache NB-IoT sensors to NB-IoT Network, You need to:
23 23  
24 24  1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
25 -1. Power Off End Node ( See below for the power off/on position)
26 -1. Insert the SIM card to Sensor. ( See below for direction)
27 -1. Power On End Node
28 -1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>), example AT+APN=iot.1nce.net
23 +1. Insert the SIM card to Sensor
24 +1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
29 29  
30 -[[image:image-20240208102804-1.png||height="286" width="696"]]
31 -
32 32  [[image:image-20230808205045-1.png||height="293" width="438"]]
33 33  
34 34  After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
... ... @@ -40,37 +40,13 @@
40 40  |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
41 41  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
42 42  
43 -Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, UK, US Virgin Islands
44 -)))|(% style="width:135px" %)UK: Band20
37 +Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands
38 +)))|(% style="width:135px" %)
45 45  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
46 46  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
47 47  
48 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
49 -|(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**AT+QCGDEFCONT=**|(% style="background-color:#4f81bd; color:white; width:474px" %)**Command Explanation**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
50 -|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]/[[NB card purchased by the customer>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net/xxx|(% style="width:474px" %)This command sets the PSD connection settings for PDN connection on power-up. When the MT attaches to the NB-IoT network on power-on, a PDN connection setup is performed. Therefore, PDN connection settings are stored in NVRAM so that they can be used by the modem during the attachment.|(% style="width:135px" %)
51 51  
52 -== 2.2 Speed Up Network Attach time ==
53 53  
54 -
55 -BC660K-GL supports multi bands (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85. **(%%) It will search one by one and try to attach, this will take a lot of time and even cause attach fail and show **Signal Strenght:99**. User can lock the band to specify band for its operator to make this faster.
56 -
57 -(% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
58 -(% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
59 -(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
60 -(% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=10,8,20,28,2,4,12,13,66,85,5**
61 -
62 -(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
63 -(% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
64 -(% style="color:#037691" %)**Telstra**(%%)        AT+QBAND=1,28
65 -(% style="color:#037691" %)**Softband**(%%)     AT+QBAND=2,3,8
66 -
67 -After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
68 -
69 -By default, device will search network for 5 minutes. User can set the time to 10 minutes by (% style="color:#037691" %)**AT+CSQTIME=10 **(%%)so it can search longer.
70 -
71 -See bands used for different provider:** [[NB-IoT Deployment , Bands, Operator list>>http://wiki.dragino.com/xwiki/bin/view/Main/NB-IoT%20Deployment%20%2C%20Bands%2C%20Operator%20list/]]**
72 -
73 -
74 74  = 3. Configure to connect to different servers =
75 75  
76 76  == 3.1 General UDP Connection ==
... ... @@ -84,7 +84,7 @@
84 84  
85 85  We can use PC tool to simulate UDP connection to make sure server works ok.
86 86  
87 -[[image:image-20230802112413-1.png||height="468" width="1024"]]
57 +[[image:image-20230802112413-1.png]]
88 88  
89 89  
90 90  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -98,6 +98,8 @@
98 98  
99 99  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
100 100  
71 +* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
72 +
101 101  [[image:image-20230802112413-2.png]]
102 102  
103 103  
... ... @@ -132,7 +132,7 @@
132 132  
133 133  [[image:image-20230802112413-4.png]]
134 134  
135 -[[image:image-20230802112413-5.png||height="530" width="987"]]
107 +[[image:image-20230802112413-5.png]]
136 136  
137 137  (% style="color:red" %)**Notice: 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.**
138 138  
... ... @@ -144,7 +144,7 @@
144 144  
145 145  [[ThingSpeak>>url:https://thingspeak.com/]] connection uses MQTT Connection. So we need to get MQTT Credentials first. You need to point MQTT Devices to ThingSpeak Channel as well.
146 146  
147 -[[image:image-20230802112413-6.png||height="336" width="925"]]
119 +[[image:image-20230802112413-6.png]]
148 148  
149 149  [[image:image-20230802112413-7.png]]
150 150  
... ... @@ -168,6 +168,8 @@
168 168  
169 169  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
170 170  
143 +
144 +
171 171  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
172 172  
173 173  
... ... @@ -187,7 +187,7 @@
187 187  
188 188  (% style="color:blue" %)**Result: **
189 189  
190 -[[image:image-20230802112413-11.png||height="539" width="901"]]
164 +[[image:image-20230802112413-11.png]]
191 191  
192 192  
193 193  === 3.3.3 Configure NB-IoT Sensor for connection ===
... ... @@ -209,10 +209,12 @@
209 209  
210 210  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
211 211  
186 +
187 +
212 212  ==== 3.3.3.2 Uplink Examples ====
213 213  
214 214  
215 -[[image:image-20230816201942-1.png]]
191 +For S31-NB
216 216  
217 217  For SE01-NB
218 218  
... ... @@ -243,9 +243,9 @@
243 243  When NB-IoT sensor upload to ThingSpeak. The payload already specify which fileds related to which sensor value. Use need to create fileds in Channels Settings. with name so to see the value correctly.
244 244  
245 245  
246 -[[image:image-20230802112413-12.png||height="504" width="1011"]]
222 +[[image:image-20230802112413-12.png]]
247 247  
248 -[[image:image-20230802112413-13.png||height="331" width="978"]]
224 +[[image:image-20230802112413-13.png]]
249 249  
250 250  
251 251  Below is the NB-IoT Product Table show the mapping.
... ... @@ -270,6 +270,8 @@
270 270  |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod5|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
271 271  |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod6|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)count|(% colspan="1" style="width:153px" %) |(% colspan="1" style="width:151px" %) |(% colspan="1" style="width:160px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
272 272  
249 +
250 +
273 273  == 3.4 [[Datacake>>https://datacake.co/]] ==
274 274  
275 275  
... ... @@ -284,17 +284,17 @@
284 284  
285 285  * (% style="color:blue" %)**S31B-NB-GE**(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction.
286 286  
287 -=== 3.4.1 For device Already has template ===
288 288  
289 -==== 3.4.1.1 Create Device ====
290 290  
267 +=== 3.4.1 Create device ===
291 291  
269 +
292 292  (% style="color:blue" %)**Add Device**(%%) in DataCake.
293 293  
294 -[[image:image-20230808162301-1.png||height="453" width="952"]]
272 +[[image:image-20230808162301-1.png]]
295 295  
296 296  
297 -[[image:image-20230808162342-2.png||height="541" width="952"]]
275 +[[image:image-20230808162342-2.png]]
298 298  
299 299  
300 300  (% style="color:blue" %)**Choose the correct model**(%%) from template.
... ... @@ -304,18 +304,16 @@
304 304  
305 305  (% style="color:blue" %)**Fill Device ID**(%%). The device ID needs to be filled in with IMEI, and a prefix of(% style="color:blue" %)** 'f' **(%%)needs to be added.
306 306  
307 -[[image:image-20230808163612-7.png||height="549" width="952"]]
285 +[[image:image-20230808163612-7.png]]
308 308  
309 309  [[image:image-20230808163035-5.png]]
310 310  
311 -[[image:image-20230808163049-6.png||height="544" width="926"]]
289 +[[image:image-20230808163049-6.png]]
312 312  
313 313  
314 -=== 3.4.2 For Device already registered in DataCake before shipped ===
292 +=== 3.4.2 Scan QR code to obtain data ===
315 315  
316 -==== 3.4.2.1 Scan QR Code to get the device info ====
317 317  
318 -
319 319  Users can use their phones or computers to scan QR codes to obtain device data information.
320 320  
321 321  [[image:image-20230808170051-8.png||height="255" width="259"]]
... ... @@ -323,72 +323,9 @@
323 323  [[image:image-20230808170548-9.png]]
324 324  
325 325  
326 -==== 3.4.2.2 Claim Device to User Account ====
302 +=== 3.4.2 AT command for connecting to DataCake ===
327 327  
328 328  
329 -By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
330 -
331 -
332 -=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
333 -
334 -
335 -**Step1: Add a device**
336 -
337 -[[image:image-20240129170024-1.png||height="330" width="900"]]
338 -
339 -
340 -**Step2: Choose your device type,please select dragino NB-IOT device**
341 -
342 -[[image:image-20240129170216-2.png||height="534" width="643"]]
343 -
344 -
345 -**Step3: Choose to create a new device**
346 -
347 -[[image:image-20240129170539-3.png||height="459" width="646"]]
348 -
349 -
350 -**Step4: Fill in the device ID of your NB device**
351 -
352 -[[image:image-20240202111546-1.png||height="378" width="651"]]
353 -
354 -
355 -**Step5: Please select your device plan according to your needs and complete the creation of the device**
356 -
357 -[[image:image-20240129171236-6.png||height="450" width="648"]]
358 -
359 -
360 -**Step6: Please add the decoder at the payload decoder of the device configuration.**
361 -
362 -**Decoder location: **[[dragino-end-node-decoder/Datacake-Dragino_NB at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB]]
363 -
364 -**Due to version update, please use the following decoder for the new version firmware:**
365 -[[dragino-end-node-decoder/Datacake-Dragino_NB_New_Version at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB_New_Version]]
366 -
367 -[[image:image-20240129172056-7.png||height="457" width="816"]]
368 -
369 -[[image:image-20240129173116-9.png||height="499" width="814"]]
370 -
371 -
372 -**Step7: Add the output of the decoder as a field**
373 -
374 -[[image:image-20240129173541-10.png||height="592" width="968"]]
375 -
376 -
377 -**Step8: Customize the dashboard and use fields as parameters of the dashboard**
378 -
379 -[[image:image-20240129174518-11.png||height="147" width="1042"]]
380 -
381 -[[image:image-20240129174657-12.png||height="538" width="916"]]
382 -
383 -[[image:image-20240129174840-13.png||height="536" width="750"]]
384 -
385 -
386 -=== 3.4.4 For device have not configured to connect to DataCake ===
387 -
388 -
389 -(% class="lead" %)
390 -Use AT command for connecting to DataCake
391 -
392 392  (% style="color:blue" %)**AT+PRO=2,0**
393 393  
394 394  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
... ... @@ -417,7 +417,7 @@
417 417  
418 418  Please select the NB95S31B template.
419 419  
420 -[[image:image-20230809173310-5.png||height="558" width="926"]]
333 +[[image:image-20230809173310-5.png]]
421 421  
422 422  [[image:image-20230809173438-6.png]]
423 423  
... ... @@ -426,7 +426,7 @@
426 426  
427 427  Successfully imported template.
428 428  
429 -[[image:image-20230809173835-8.png||height="515" width="860"]]
342 +[[image:image-20230809173835-8.png]]
430 430  
431 431  
432 432  Users can set UDP port.
... ... @@ -441,19 +441,17 @@
441 441  
442 442  [[image:image-20230810083934-1.png]]
443 443  
444 -[[image:image-20230810084048-2.png||height="535" width="1052"]]
357 +[[image:image-20230810084048-2.png]]
445 445  
446 -
447 447  === 3.5.3 Configure NB-IoT Sensors ===
448 448  
449 449  
450 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
451 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
452 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
453 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
454 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
455 -* (% style="color:#037691" %)**AT+PWD=“Your device token”**
362 +* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
456 456  
364 +* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
365 +
366 +
367 +
457 457  == 3.6 ThingsBoard.Cloud (via MQTT) ==
458 458  
459 459  === 3.6.1 Configure ThingsBoard ===
... ... @@ -463,7 +463,7 @@
463 463  
464 464  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
465 465  
466 -[[image:image-20230802112413-32.png||height="583" width="1066"]]
377 +[[image:image-20230802112413-32.png]]
467 467  
468 468  
469 469  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -475,7 +475,7 @@
475 475  
476 476  To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** (%%)button. Name it (% style="color:blue" %)**“MQTT Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
477 477  
478 -[[image:image-20230802112413-33.png||height="597" width="1061"]]
389 +[[image:image-20230802112413-33.png||height="732" width="1302"]]
479 479  
480 480  
481 481  (% style="color:blue" %)**Downlink Converter**
... ... @@ -482,7 +482,7 @@
482 482  
483 483  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
484 484  
485 -[[image:image-20230802112413-34.png||height="598" width="1063"]]
396 +[[image:image-20230802112413-34.png||height="734" width="1305"]]
486 486  
487 487  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
488 488  
... ... @@ -492,23 +492,23 @@
492 492  
493 493  Go to the (% style="color:blue" %)**Integrations center**(%%) **->** (% style="color:blue" %)**Integrations page**(%%) and click **“(% style="color:blue" %)plus(%%)”** icon to add a new integration. Name it (% style="color:blue" %)**“MQTT Integration”**(%%), select type (% style="color:blue" %)**MQTT**;
494 494  
495 -[[image:image-20230802112413-35.png||height="597" width="1062"]]
406 +[[image:image-20230802112413-35.png||height="738" width="1312"]]
496 496  
497 497  
498 498  * The next steps is to add the recently created uplink and downlink converters;
499 499  
500 -[[image:image-20230802112413-36.png||height="598" width="1062"]]
411 +[[image:image-20230802112413-36.png||height="736" width="1308"]]
501 501  
502 -[[image:image-20230802112413-37.png||height="598" width="1064"]]
413 +[[image:image-20230802112413-37.png||height="735" width="1307"]]
503 503  
504 504  
505 505  (% style="color:blue" %)**Add a topic filter:**
506 506  
507 -Consistent with the theme of the node setting.
418 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
508 508  
509 509  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
510 510  
511 -[[image:image-20230802112413-38.png||height="598" width="1064"]]
422 +[[image:image-20230802112413-38.png||height="731" width="1300"]]
512 512  
513 513  
514 514  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -516,7 +516,7 @@
516 516  
517 517  [[image:image-20230802112413-39.png]]
518 518  
519 -[[image:image-20230802112413-40.png||height="525" width="980"]]
430 +[[image:image-20230802112413-40.png]]
520 520  
521 521  
522 522  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -538,95 +538,18 @@
538 538  
539 539  Test Uplink by click the button for 1 second
540 540  
541 -[[image:image-20230802112413-41.png||height="496" width="828"]]
452 +[[image:image-20230802112413-41.png]]
542 542  
543 543  [[image:image-20230802112413-42.png]]
544 544  
545 -[[image:image-20230802112413-43.png||height="407" width="825"]]
456 +[[image:image-20230802112413-43.png]]
546 546  
547 547  
548 -== 3.7 ThingsBoard.Cloud (via COAP) ==
459 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
549 549  
550 -=== 3.7.1 Configure ThingsBoard ===
461 +=== 3.7.1 Create device & Get Credentials ===
551 551  
552 -==== 3.7.1.1 Create Uplink & Downlink Converter ====
553 553  
554 -
555 -(% style="color:blue" %)**Uplink Converter**
556 -
557 -The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
558 -
559 -To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** (%%)button. Name it (% style="color:blue" %)**“COAP Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
560 -
561 -[[image:image-20240729141300-1.png||height="552" width="1115"]]
562 -
563 -
564 -(% style="color:blue" %)**Downlink Converter**
565 -
566 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
567 -
568 -[[image:image-20240729142505-3.png||height="507" width="1023"]]
569 -
570 -
571 -==== 3.7.1.2 COAP Integration Setup ====
572 -
573 -
574 -Go to the (% style="color:blue" %)**Integrations center**(%%) **->** (% style="color:blue" %)**Integrations page**(%%) and click **“(% style="color:blue" %)plus(%%)”** icon to add a new integration. Name it (% style="color:blue" %)**“CoAP Integration”**(%%), select type **COAP    **(% style="color:blue" %);
575 -
576 -[[image:image-20240729144058-4.png||height="506" width="1021"]]
577 -
578 -
579 -The next steps is to add the recently created uplink converters;
580 -
581 -[[image:image-20240729150142-5.png||height="507" width="1023"]]
582 -
583 -
584 -==== 3.7.1.3 Add COAP Integration ====
585 -
586 -
587 -==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
588 -
589 -
590 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
591 -
592 -==== 3.7.2.1 Instruction Description ====
593 -
594 -
595 -* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
596 -* AT+SERVADDR=COAP Server Address,5683
597 -
598 -Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
599 -
600 -[[image:image-20240729172305-12.png||height="361" width="624"]]
601 -
602 -Note:The port for the COAP protocol has been fixed to 5683
603 -
604 -
605 -* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
606 -
607 -If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
608 -
609 -e.g.
610 -
611 -* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
612 -
613 -[[image:image-20240729172415-13.png||height="401" width="694"]]
614 -
615 -If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
616 -
617 -e.g.
618 -
619 -* AT+URL1=11, "i";  
620 -* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
621 -
622 -[[image:image-20240729172500-14.png||height="403" width="700"]]
623 -
624 -
625 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
626 -
627 -=== 3.8.1 Create device & Get Credentials ===
628 -
629 -
630 630  We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.
631 631  
632 632  [[image:image-20230802112413-44.png]]
... ... @@ -675,31 +675,33 @@
675 675  
676 676  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
677 677  
678 -=== 3.8.2 Simulate with MQTT.fx ===
679 679  
680 680  
514 +=== 3.7.2 Simulate with MQTT.fx ===
515 +
516 +
681 681  [[image:image-20230802112413-52.png]]
682 682  
683 683  
684 -[[image:image-20230808105300-2.png||height="553" width="1026"]]
520 +[[image:image-20230808105300-2.png]]
685 685  
686 686  
687 687  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
688 688  
689 -[[image:image-20230808105217-1.png||height="556" width="1031"]]
525 +[[image:image-20230808105217-1.png]]
690 690  
691 691  [[image:image-20230808105329-3.png]]
692 692  
693 693  
694 -=== 3.8.3 tago data ===
530 +=== 3.7.3 tago data ===
695 695  
696 696  
697 -[[image:image-20230802112413-50.png||height="242" width="1037"]]
533 +[[image:image-20230802112413-50.png]]
698 698  
699 699  [[image:image-20230802112413-51.png||height="184" width="696"]]
700 700  
701 701  
702 -== 3.9 TCP Connection ==
538 +== 3.8 TCP Connection ==
703 703  
704 704  
705 705  (% style="color:blue" %)**AT command:**
... ... @@ -718,333 +718,3 @@
718 718  (% style="color:blue" %)**See result in TCP Server:**
719 719  
720 720  [[image:image-20230807233631-2.png]]
721 -
722 -
723 -== 3.10 AWS Connection ==
724 -
725 -
726 -Users can refer to [[Dragino NB device connection to AWS platform instructions>>http://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H1.LogintotheplatformandfindIoTcore]]
727 -
728 -
729 -= 4. MQTT/UDP/TCP downlink =
730 -
731 -== 4.1 MQTT (via MQTT.fx) ==
732 -
733 -
734 -Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
735 -
736 -**1.** Configure node MQTT connection (via MQTT.fx):
737 -
738 -(% style="color:blue" %)**AT command:**
739 -
740 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
741 -
742 -* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
743 -
744 -* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
745 -
746 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
747 -
748 -* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
749 -
750 -* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
751 -
752 -(% style="color:red" %)**Note: To uplink and downlink via MQTT.fx, we need set the publish topic and subscribe topic different, for example: AT+SUBTOPIC=SE01_SUB & AT+PUBTOPIC=SE01_PUB.**
753 -
754 -[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
755 -
756 -
757 -**2. **When the node uplink packets, we can observe the data in MQTT.fx.
758 -
759 -[[image:image-20240418144337-1.png||height="709" width="802"]]
760 -
761 -**3. **The downlink command can be successfully sent only when the downlink port is open.
762 -
763 - The downlink port is opened for about 3 seconds after uplink packets are sent.
764 -
765 - Therefore, when we see the node uplink packets in the **Subscribe** window, we need to immediately switch to the **publish** window to publish the **hex format** command.
766 -
767 -[[image:image-20240418150435-3.png||height="582" width="659"]]
768 -
769 -[[image:image-20240418150932-4.png||height="492" width="1061"]]
770 -
771 -(% style="color:red" %)**Note: Users can edit the hex command in advance. When the node uplink, directly click the publish button several times to increase the success rate of command configuration.**
772 -
773 -
774 -= 5. FAQ =
775 -
776 -== 5.1 What is the usage of Multi Sampling and One Uplink? ==
777 -
778 -
779 -The NB series has the feature for Multi Sampling and one uplink. See one of them
780 -
781 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink]]
782 -
783 -User can use this feature for below purpose:
784 -
785 -1. **Reduce power consumption**. The NB-IoT transmit power is much more higher than the sensor sampling power. To save battery life, we can sampling often and send in one uplink.
786 -1. Give more sampling data points.
787 -1. Increase reliable in transmission. For example. If user set
788 -1*. **AT+TR=1800** ~/~/ The unit is seconds, and the default is to record data once every 1800 seconds (30 minutes, the minimum can be set to 180 seconds)
789 -1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
790 -1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
791 -1*. this will mean each uplink will actually include the 6 uplink data (24 set data which cover 12 hours). So if device doesn't lost 6 continue data. There will not data lost.
792 -
793 -== 5.2 Why the uplink JSON format is not standard? ==
794 -
795 -
796 -The json format in uplink packet is not standard Json format. Below is the example. This is to make the payload as short as possible, due to NB-IoT transmit limition, a standard Json is not able to include 32 sets of sensors data with timestamp.
797 -
798 -The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
799 -
800 -[[image:image-20240229233154-1.png]]
801 -
802 -
803 -= 6. Trouble Shooting: =
804 -
805 -== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
806 -
807 -
808 -There are many different providers provide NB-IoT service in the world. They might use different band, different APN & different operator configuration. Which makes connection to NB-IoT network is complicate.
809 -
810 -If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
811 -
812 -[[image:image-20240207002003-1.png]]
813 -
814 -
815 -If fail to attach network, it will shows signal 99. as below:
816 -
817 -[[image:image-20240207002129-2.png]]
818 -
819 -
820 -(% class="lead" %)
821 -When see this issue, below are the checklist:
822 -
823 -* Does your SIM card support NB-IoT network? If SIM card doesn't not specify support NB-IoT clearly, normally it doesn't support. You need to confirm with your operator.
824 -* Do you configure the correct APN? [[Check here for APN settings>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.1GeneralConfiguretoattachnetwork]].
825 -* Do you lock the frequency band? This is the most case we see. [[Explain and Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.2SpeedUpNetworkAttachtime]].
826 -* Check if the device is attached to Carrier network but reject. (need to check with operator).
827 -* Check if the antenna is connected firmly.
828 -
829 -If you have check all above and still fail. please send console log files (as many as possible) to [[support@dragino.com>>mailto:support@dragino.com]] so we can check.
830 -
831 -
832 -== 6.2 Issue: "NBIOT did not respond" ==
833 -
834 -
835 -(% class="box errormessage" %)
836 -(((
837 -11:24:22.397 [44596]NBIOT did not respond.
838 -11:24:24.315 [46530]NBIOT did not respond.
839 -11:24:26.256 [48464]NBIOT did not respond.
840 -11:24:28.196 [50398]NBIOT did not respond.
841 -11:24:30.115 [52332]NBIOT did not respond.
842 -11:24:32.127 [54266]NBIOT did not respond.
843 -11:24:32.127 [54299]Restart the module...
844 -11:24:39.181 [61332]No response when shutting down
845 -)))
846 -
847 -This issue might due to initiate issue for NB-IoT module. In this case, please try:
848 -
849 -1) Open Enclosure
850 -
851 -2) Power off device by pull out the power on Jumper
852 -
853 -3) Power on device by connect back the power jumper.
854 -
855 -4) push reset button.
856 -
857 -[[image:image-20240208001740-1.png]]
858 -
859 -
860 -== 6.3 Issue: "Failed to readI MSI number" ==
861 -
862 -
863 -(% class="box errormessage" %)
864 -(((
865 -[18170]Failed to read IMSI:1umber.
866 -[20109]Failed to read IMSI numoer.
867 -[22048]Failed to read IMSI number.
868 -[29842lRestart the module...
869 -)))
870 -
871 -Make sure that the SIM card is insert in correct direction and device is power off/on during insert. Here is reference link: [[Insert SIM Card>>||anchor="H2.1GeneralConfiguretoattachnetwork"]].
872 -
873 -
874 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
875 -
876 -
877 -When the MCU is communicating with the NB-IoT module, the MCU response of AT Command will become slower, it might takes several seconds to response.
878 -
879 -[[image:image-20240226111928-1.png]]
880 -
881 -
882 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
883 -
884 -(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
885 -=== UDP: ===
886 -
887 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
888 -Its downlink command is the same as the AT command, but brackets are required.
889 -Example:
890 -
891 -{AT+TDC=300}
892 -
893 -
894 -(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
895 -=== MQTT: ===
896 -
897 -Json：
898 -
899 -The Json format in MQTT mode needs to be configured with all commands.
900 -If you have configurations that need to be changed, please change them in the template below.
901 -Template:
902 -
903 -{
904 -"AT+SERVADDR":"119.91.62.30,1882",
905 -"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
906 -"AT+UNAME":"usenamedragino",
907 -"AT+PWD":"passworddragino",
908 -"AT+PUBTOPIC":"123",
909 -"AT+SUBTOPIC":"321",
910 -"AT+TDC":"7200",
911 -"AT+INTMOD":"0",
912 -"AT+APN":"NULL",
913 -"AT+5VT":"0",
914 -"AT+PRO":"3,5",
915 -"AT+TR":"900",
916 -"AT+NOUD":"0",
917 -"AT+CSQTIME":"5",
918 -"AT+DNSTIMER":"0",
919 -"AT+TLSMOD":"0,0",
920 -"AT+MQOS":"0",
921 -"AT+TEMPALARM1":"0",
922 -"AT+TEMPALARM2":"10",
923 -"AT+TEMPALARM3":"0"
924 -}
925 -
926 -Hex：
927 -
928 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
929 -
930 -The supported commands are consistent with LoRaWAN's hex commands.
931 -Please refer to the following link to obtain the hex format:
932 -
933 -[[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/]]
934 -
935 -
936 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
937 -
938 -
939 -* **AT Command: AT** **+GETLOG**
940 -
941 -This command can be used to query upstream logs of data packets.
942 -
943 -[[image:image-20240701114700-1.png]]
944 -
945 -
946 -== 6.7 How to find the AT Command Password if lost? ==
947 -
948 -
949 -=== Why can't the password access AT command after upgrade(-NB)? ===
950 -
951 -
952 -Because the new version of -NB firmware has updated the factory reset function, users can choose to restore all parameters to factory Settings, or keep the password to restore the rest of the parameters to factory Settings.
953 -
954 -This update changes the password address of the firmware, so the password will be invalid after the customer upgrades from the old version of firmware (without FDR1 function) to the new version of firmware (with FDR1 function).
955 -
956 -Two different restore factory Settings configurations.
957 -
958 -(% style="color:blue" %)**AT command:**
959 -
960 -* (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
961 -* (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values except for passwords.(new)
962 -
963 -=== Version Confirmation ===
964 -
965 -We are now dividing the **old firmware**(without FDR1 function) with the **new firmware**(with FDR1 function) by whether it contains FDR1 functionality. Please refer to the table:
966 -
967 -(% border="1" style="background-color:#f2f2f2; width:510px" %)
968 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
969 -**Firmware version**
970 -
971 -**(without FDR1 function)**
972 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
973 -**Firmware version**
974 -
975 -**(with FDR1 function)**
976 -)))
977 -|(% style="width:210px" %)(((
978 -CPL03-NB, S31-NB, SN50V3-NB, TS01-NB, D20-NB, DS03A-NB, DDS04-NB, DDS45-NB, DDS20-NB, DDS75-NB, LDS12-NB, LDS40-NB, LMS01-NB, MDS120-NB,  MDS200-NB, SE01-NB, SPH01-NB;
979 -)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
980 -|(% style="width:210px" %)(((
981 -WL03A-NB, SDI-12-NB;
982 -)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
983 -After V1.0.8 (including V1.0.2)
984 -)))
985 -|(% style="width:210px" %)(((
986 -SW3L-NB, PS-NB;
987 -)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
988 -After V1.0.5 (including V1.0.5)
989 -)))
990 -|(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
991 -
992 -=== UART connection and firmware update methods ===
993 -
994 -
995 -Users can query passwords only using the UART interface via the STM32CubeProgrammer.
996 -
997 -See **[[UART Connection>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]]**.
998 -
999 -update firmware through UART TTL interface :** [[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
1000 -
1001 -
1002 -=== query the password via STM32CubeProgrammer ===
1003 -
1004 -
1005 -Users can use the password address to query the password through STM32CubeProgrammer.
1006 -
1007 -* The password address for old firmware(without FDR1 function) : **0x08019000**
1008 -* The password address for new firmware(with FDR1 function) : **0x08025D00**
1009 -
1010 -(% style="color:red" %)**Notice: The password can only be queried after the firmware is run once.**
1011 -
1012 -
1013 -**Procedure for querying the password(old firmware):**
1014 -
1015 -* After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the firmware once**.
1016 -* Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1017 -* Click "Device memory", enter **0x08019000** in "Address", and click "Read"
1018 -* Find the 0x08019000 address field and then read the current password as shown in the screenshot below.
1019 -
1020 -[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827171901-3.png?width=912&height=528&rev=1.1||alt="image-20240827171901-3.png"]]
1021 -
1022 -
1023 -**Procedure for querying the password(new firmware):**
1024 -
1025 -Refer to [[the old and new firmware division>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#HVersionConfirmation]] above, and run the firmware first after updating the firmware.
1026 -
1027 -* After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the new firmware once**.
1028 -* Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1029 -* Click "Device memory", enter **0x08025D00** in "Address", and click "Read"
1030 -* Find the 0x08025D00 address field and then read the current password as shown in the screenshot below.
1031 -
1032 -[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827180414-1.png?width=910&height=527&rev=1.1||alt="image-20240827180414-1.png"]]
1033 -
1034 -
1035 -
1036 -=== Special case ===
1037 -
1038 -
1039 -If the user has never changed the password manually, the user cannot find the valid password through the above two password addresses. In this case, the valid password is still the original password on the node box label (**AT+PIN**).
1040 -
1041 -Invalid query screenshot example:
1042 -
1043 -
1044 -[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827181447-4.png?width=889&height=519&rev=1.1||alt="image-20240827181447-4.png"]]
1045 -
1046 -[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827181431-3.png?width=892&height=515&rev=1.1||alt="image-20240827181431-3.png"]]
1047 -
1048 -
1049 -
1050 -
image-20230816201942-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -99.8 KB
Content
image-20240129170024-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.3 KB
Content
image-20240129170216-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -56.0 KB
Content
image-20240129170539-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -55.0 KB
Content
image-20240129171029-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -36.1 KB
Content
image-20240129171113-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -47.2 KB
Content
image-20240129171236-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.8 KB
Content
image-20240129172056-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -69.8 KB
Content
image-20240129172136-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -80.4 KB
Content
image-20240129173116-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -110.8 KB
Content
image-20240129173541-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -95.4 KB
Content
image-20240129174518-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -23.2 KB
Content
image-20240129174657-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -141.9 KB
Content
image-20240129174840-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -92.9 KB
Content
image-20240202111546-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -33.3 KB
Content
image-20240207002003-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -22.3 KB
Content
image-20240207002129-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -17.9 KB
Content
image-20240208001740-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -487.1 KB
Content
image-20240208102804-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -507.6 KB
Content
image-20240226111928-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -52.0 KB
Content
image-20240229233154-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -39.5 KB
Content
image-20240417173549-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -70.3 KB
Content
image-20240417180145-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -104.1 KB
Content
image-20240417180737-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -59.7 KB
Content
image-20240418144337-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -95.1 KB
Content
image-20240418144714-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -50.3 KB
Content
image-20240418150435-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -44.1 KB
Content
image-20240418150932-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -103.4 KB
Content
image-20240701114700-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -291.5 KB
Content
image-20240729141300-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -176.9 KB
Content
image-20240729142505-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -202.0 KB
Content
image-20240729144058-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -140.7 KB
Content
image-20240729150142-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -128.0 KB
Content
image-20240729160802-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -162.8 KB
Content
image-20240729161543-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -166.8 KB
Content
image-20240729172234-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -57.8 KB
Content
image-20240729172305-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -49.3 KB
Content
image-20240729172415-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -54.3 KB
Content
image-20240729172500-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -48.6 KB
Content