Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 92.1
edited by David Huang
on 2023/08/09 17:40
Change comment: Uploaded new attachment "image-20230809174053-9.png", version {1}
To version 176.1
edited by kai
on 2024/07/29 17:24
Change comment: Uploaded new attachment "image-20240729172415-13.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.David
1 +XWiki.kai
Content
... ... @@ -4,6 +4,10 @@
4 4  {{toc/}}
5 5  
6 6  
7 +
8 +
9 +
10 +
7 7  = 1. The use of this guideline =
8 8  
9 9  
... ... @@ -12,13 +12,19 @@
12 12  
13 13  = 2. Attach Network =
14 14  
19 +== 2.1 General Configure to attach network ==
15 15  
21 +
16 16  To attache NB-IoT sensors to NB-IoT Network, You need to:
17 17  
18 18  1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
19 -1. Insert the SIM card to Sensor
20 -1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (% class="mark" %)(补充 APN 指令(%%))
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
21 21  
30 +[[image:image-20240208102804-1.png||height="286" width="696"]]
31 +
22 22  [[image:image-20230808205045-1.png||height="293" width="438"]]
23 23  
24 24  After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
... ... @@ -26,17 +26,37 @@
26 26  The -NB and -NS models support (% style="color:blue" %)**LTE Cat NB2**(%%), with below frequency band: multiple frequency bands of (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85**(%%) . Make sure you use a the NB-IoT SIM card.
27 27  
28 28  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
29 -|(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**APN**|(% style="background-color:#4f81bd; color:white; width:474px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
39 +|(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**AT+APN=**|(% style="background-color:#4f81bd; color:white; width:474px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
30 30  |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
31 31  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
32 32  
33 -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
34 -)))|(% style="width:135px" %)
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
35 35  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
36 36  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
37 37  
48 +== 2.2 Speed Up Network Attach time ==
38 38  
39 39  
51 +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.
52 +
53 +(% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
54 +(% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
55 +(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
56 +(% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=10,8,20,28,2,4,12,13,66,85,5**
57 +
58 +(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
59 +(% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
60 +(% style="color:#037691" %)**Telstra**(%%)        AT+QBAND=1,28
61 +(% style="color:#037691" %)**Softband**(%%)     AT+QBAND=2,3,8
62 +
63 +After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
64 +
65 +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.
66 +
67 +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/]]**
68 +
69 +
40 40  = 3. Configure to connect to different servers =
41 41  
42 42  == 3.1 General UDP Connection ==
... ... @@ -50,7 +50,7 @@
50 50  
51 51  We can use PC tool to simulate UDP connection to make sure server works ok.
52 52  
53 -[[image:image-20230802112413-1.png]]
83 +[[image:image-20230802112413-1.png||height="468" width="1024"]]
54 54  
55 55  
56 56  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -64,8 +64,6 @@
64 64  
65 65  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
66 66  
67 -* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
68 -
69 69  [[image:image-20230802112413-2.png]]
70 70  
71 71  
... ... @@ -100,7 +100,7 @@
100 100  
101 101  [[image:image-20230802112413-4.png]]
102 102  
103 -[[image:image-20230802112413-5.png]]
131 +[[image:image-20230802112413-5.png||height="530" width="987"]]
104 104  
105 105  (% 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.**
106 106  
... ... @@ -112,7 +112,7 @@
112 112  
113 113  [[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.
114 114  
115 -[[image:image-20230802112413-6.png]]
143 +[[image:image-20230802112413-6.png||height="336" width="925"]]
116 116  
117 117  [[image:image-20230802112413-7.png]]
118 118  
... ... @@ -136,8 +136,6 @@
136 136  
137 137  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
138 138  
139 -
140 -
141 141  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
142 142  
143 143  
... ... @@ -157,7 +157,7 @@
157 157  
158 158  (% style="color:blue" %)**Result: **
159 159  
160 -[[image:image-20230802112413-11.png]]
186 +[[image:image-20230802112413-11.png||height="539" width="901"]]
161 161  
162 162  
163 163  === 3.3.3 Configure NB-IoT Sensor for connection ===
... ... @@ -167,7 +167,7 @@
167 167  
168 168  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
169 169  
170 -* (% style="color:blue" %)**AT+PRO=3,1** (%%) **~/~/ Set to use ThingSpeak Server and Related Payload**
196 +* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
171 171  
172 172  * (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
173 173  
... ... @@ -179,12 +179,10 @@
179 179  
180 180  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
181 181  
182 -
183 -
184 184  ==== 3.3.3.2 Uplink Examples ====
185 185  
186 186  
187 -For S31-NB
211 +[[image:image-20230816201942-1.png]]
188 188  
189 189  For SE01-NB
190 190  
... ... @@ -215,9 +215,9 @@
215 215  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.
216 216  
217 217  
218 -[[image:image-20230802112413-12.png]]
242 +[[image:image-20230802112413-12.png||height="504" width="1011"]]
219 219  
220 -[[image:image-20230802112413-13.png]]
244 +[[image:image-20230802112413-13.png||height="331" width="978"]]
221 221  
222 222  
223 223  Below is the NB-IoT Product Table show the mapping.
... ... @@ -242,44 +242,121 @@
242 242  |(% 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" %)
243 243  |(% 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" %)
244 244  
269 +== 3.4 [[Datacake>>https://datacake.co/]] ==
245 245  
246 246  
247 -== 3.4 Datacake ==
272 +(% class="wikigeneratedid" %)
273 +Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
248 248  
249 -=== 3.4.1 Create device ===
250 250  
276 +(% class="wikigeneratedid" %)
277 +As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
251 251  
252 -[[image:image-20230808162301-1.png]]
279 +* (% style="color:blue" %)**S31B-NB-1D**(%%): This version have pre-configure DataCake connection. User just need to Power on this device, it will auto connect send data to DataCake Server.
253 253  
281 +* (% 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.
254 254  
255 -[[image:image-20230808162342-2.png]]
283 +=== 3.4.1 For device Already has template ===
256 256  
285 +==== 3.4.1.1 Create Device ====
257 257  
287 +(% style="color:blue" %)**Add Device**(%%) in DataCake.
288 +
289 +[[image:image-20230808162301-1.png||height="453" width="952"]]
290 +
291 +
292 +[[image:image-20230808162342-2.png||height="541" width="952"]]
293 +
294 +
295 +(% style="color:blue" %)**Choose the correct model**(%%) from template.
296 +
258 258  [[image:image-20230808162421-3.png]]
259 259  
260 260  
261 -The device ID needs to be filled in with IMEI, and a prefix of** 'f' **needs to be added.
300 +(% 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.
262 262  
263 -[[image:image-20230808163612-7.png]]
302 +[[image:image-20230808163612-7.png||height="549" width="952"]]
264 264  
265 265  [[image:image-20230808163035-5.png]]
266 266  
267 -[[image:image-20230808163049-6.png]]
306 +[[image:image-20230808163049-6.png||height="544" width="926"]]
268 268  
269 269  
270 -=== 3.4.2 Scan QR code to obtain data ===
309 +=== 3.4.2 For Device already registered in DataCake before shipped ===
271 271  
311 +==== 3.4.2.1 Scan QR Code to get the device info ====
272 272  
313 +
273 273  Users can use their phones or computers to scan QR codes to obtain device data information.
274 274  
275 -[[image:image-20230808170051-8.png]]
316 +[[image:image-20230808170051-8.png||height="255" width="259"]]
276 276  
277 277  [[image:image-20230808170548-9.png]]
278 278  
279 279  
280 -=== 3.4.2 AT command for connecting to DataCake ===
321 +==== 3.4.2.2 Claim Device to User Account ====
281 281  
282 282  
324 +By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
325 +
326 +
327 +=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
328 +
329 +
330 +**Step1: Add a device**
331 +
332 +[[image:image-20240129170024-1.png||height="330" width="900"]]
333 +
334 +
335 +**Step2: Choose your device type,please select dragino NB-IOT device**
336 +
337 +[[image:image-20240129170216-2.png||height="534" width="643"]]
338 +
339 +
340 +**Step3: Choose to create a new device**
341 +
342 +[[image:image-20240129170539-3.png||height="459" width="646"]]
343 +
344 +
345 +**Step4: Fill in the device ID of your NB device**
346 +
347 +[[image:image-20240202111546-1.png||height="378" width="651"]]
348 +
349 +
350 +**Step5: Please select your device plan according to your needs and complete the creation of the device**
351 +
352 +[[image:image-20240129171236-6.png||height="450" width="648"]]
353 +
354 +
355 +**Step6: Please add the decoder at the payload decoder of the device configuration.**
356 +
357 +**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]]
358 +
359 +[[image:image-20240129172056-7.png||height="457" width="816"]]
360 +
361 +[[image:image-20240129173116-9.png||height="499" width="814"]]
362 +
363 +
364 +**Step7: Add the output of the decoder as a field**
365 +
366 +[[image:image-20240129173541-10.png||height="592" width="968"]]
367 +
368 +
369 +**Step8: Customize the dashboard and use fields as parameters of the dashboard**
370 +
371 +[[image:image-20240129174518-11.png||height="147" width="1042"]]
372 +
373 +[[image:image-20240129174657-12.png||height="538" width="916"]]
374 +
375 +[[image:image-20240129174840-13.png||height="536" width="750"]]
376 +
377 +
378 +=== 3.4.4 For device have not configured to connect to DataCake ===
379 +
380 +
381 +(% class="lead" %)
382 +Use AT command for connecting to DataCake
383 +
283 283  (% style="color:blue" %)**AT+PRO=2,0**
284 284  
285 285  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
... ... @@ -290,35 +290,61 @@
290 290  === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
291 291  
292 292  
293 -[[image:image-20230802112413-29.png]]
394 +Take S31-NB UDP protocol as an example.
294 294  
396 +Dragino provides input flow examples for the sensors.
295 295  
296 -[[image:image-20230802112413-30.png]]
398 +User can download the required JSON file through Dragino Node-RED input flow template.
297 297  
400 +Download sample JSON file link: [[https:~~/~~/www.dropbox.com/sh/mduw85jcuwsua22/AAAvwPhg9z6dLjJhmZjqBf_ma?dl=0>>url:https://www.dropbox.com/sh/mduw85jcuwsua22/AAAvwPhg9z6dLjJhmZjqBf_ma?dl=0]]
298 298  
299 -=== 3.5.2 Simulate Connection ===
402 +We can directly import the template.
300 300  
404 +The templates for S31-NB and NB95S31B are the same.
301 301  
302 -[[image:image-20230802112413-31.png]]
303 303  
407 +[[image:image-20230809173127-4.png]]
304 304  
305 -=== 3.5.3 Configure NB-IoT Sensors ===
306 306  
410 +Please select the NB95S31B template.
307 307  
308 -* (% style="color:blue" %)**AT+PRO=3,0(hex format) or 3,5(json format)**(%%)    **~/~/  Set to mqtt Server and  Payload**
412 +[[image:image-20230809173310-5.png||height="558" width="926"]]
309 309  
310 -* (% style="color:blue" %)**AT+CLIENT=any value**
414 +[[image:image-20230809173438-6.png]]
311 311  
312 -* (% style="color:blue" %)**AT+UNAME=any value**
416 +[[image:image-20230809173800-7.png]]
313 313  
314 -* (% style="color:blue" %)**AT+PWD=any value**
315 315  
316 -* (% style="color:blue" %)**AT+PUBTOPIC=any value**
419 +Successfully imported template.
317 317  
318 -* (% style="color:blue" %)**AT+SUBTOPIC=any value**
421 +[[image:image-20230809173835-8.png||height="515" width="860"]]
319 319  
320 320  
424 +Users can set UDP port.
321 321  
426 +[[image:image-20230809174053-9.png]]
427 +
428 +
429 +=== 3.5.2 Simulate Connection ===
430 +
431 +
432 +We have completed the configuration of UDP. We can try sending packets to node red.
433 +
434 +[[image:image-20230810083934-1.png]]
435 +
436 +[[image:image-20230810084048-2.png||height="535" width="1052"]]
437 +
438 +
439 +=== 3.5.3 Configure NB-IoT Sensors ===
440 +
441 +
442 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
443 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
444 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
445 +* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
446 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
447 +* (% style="color:#037691" %)**AT+PWD=“Your device token”**
448 +
322 322  == 3.6 ThingsBoard.Cloud (via MQTT) ==
323 323  
324 324  === 3.6.1 Configure ThingsBoard ===
... ... @@ -328,7 +328,7 @@
328 328  
329 329  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
330 330  
331 -[[image:image-20230802112413-32.png]]
458 +[[image:image-20230802112413-32.png||height="583" width="1066"]]
332 332  
333 333  
334 334  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -340,7 +340,7 @@
340 340  
341 341  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.
342 342  
343 -[[image:image-20230802112413-33.png||height="732" width="1302"]]
470 +[[image:image-20230802112413-33.png||height="597" width="1061"]]
344 344  
345 345  
346 346  (% style="color:blue" %)**Downlink Converter**
... ... @@ -347,7 +347,7 @@
347 347  
348 348  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
349 349  
350 -[[image:image-20230802112413-34.png||height="734" width="1305"]]
477 +[[image:image-20230802112413-34.png||height="598" width="1063"]]
351 351  
352 352  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
353 353  
... ... @@ -357,23 +357,23 @@
357 357  
358 358  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**;
359 359  
360 -[[image:image-20230802112413-35.png||height="738" width="1312"]]
487 +[[image:image-20230802112413-35.png||height="597" width="1062"]]
361 361  
362 362  
363 363  * The next steps is to add the recently created uplink and downlink converters;
364 364  
365 -[[image:image-20230802112413-36.png||height="736" width="1308"]]
492 +[[image:image-20230802112413-36.png||height="598" width="1062"]]
366 366  
367 -[[image:image-20230802112413-37.png||height="735" width="1307"]]
494 +[[image:image-20230802112413-37.png||height="598" width="1064"]]
368 368  
369 369  
370 370  (% style="color:blue" %)**Add a topic filter:**
371 371  
372 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
499 +Consistent with the theme of the node setting.
373 373  
374 374  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
375 375  
376 -[[image:image-20230802112413-38.png||height="731" width="1300"]]
503 +[[image:image-20230802112413-38.png||height="598" width="1064"]]
377 377  
378 378  
379 379  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -381,7 +381,7 @@
381 381  
382 382  [[image:image-20230802112413-39.png]]
383 383  
384 -[[image:image-20230802112413-40.png]]
511 +[[image:image-20230802112413-40.png||height="525" width="980"]]
385 385  
386 386  
387 387  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -401,22 +401,76 @@
401 401  
402 402  * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
403 403  
404 -
405 -
406 406  Test Uplink by click the button for 1 second
407 407  
408 -[[image:image-20230802112413-41.png]]
533 +[[image:image-20230802112413-41.png||height="496" width="828"]]
409 409  
410 410  [[image:image-20230802112413-42.png]]
411 411  
412 -[[image:image-20230802112413-43.png]]
537 +[[image:image-20230802112413-43.png||height="407" width="825"]]
413 413  
414 414  
415 -== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
416 416  
417 -=== 3.7.1 Create device & Get Credentials ===
541 +== 3.7 ThingsBoard.Cloud (via COAP) ==
418 418  
543 +=== 3.7.1 Configure ThingsBoard ===
419 419  
545 +==== 3.7.1.1 Create Uplink & Downlink Converter ====
546 +
547 +
548 +(% style="color:blue" %)**Uplink Converter**
549 +
550 +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.
551 +
552 +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.
553 +
554 +[[image:image-20240729141300-1.png||height="552" width="1115"]]
555 +
556 +
557 +(% style="color:blue" %)**Downlink Converter**
558 +
559 +The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
560 +
561 +[[image:image-20240729142505-3.png||height="507" width="1023"]]
562 +
563 +
564 +==== 3.7.1.2 COAP Integration Setup ====
565 +
566 +
567 +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" %);
568 +
569 +[[image:image-20240729144058-4.png||height="506" width="1021"]]
570 +
571 +
572 +The next steps is to add the recently created uplink converters;
573 +
574 +[[image:image-20240729150142-5.png||height="507" width="1023"]]
575 +
576 +
577 +==== 3.7.1.3 Add COAP Integration ====
578 +
579 +==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
580 +
581 +
582 +=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
583 +
584 +==== 3.7.2.1 Instruction Description ====
585 +
586 +* AT+SERVADDR=COAP Server Address,5683
587 +
588 +Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
589 +
590 +Note:The port for the COAP protocol has been fixed to 5683
591 +
592 +AT+URL1=11,character length,""
593 +
594 +If the module used is BC660K, only one URL directive needs to be configured, e.g. AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
595 +
596 +== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
597 +
598 +=== 3.8.1 Create device & Get Credentials ===
599 +
600 +
420 420  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.
421 421  
422 422  [[image:image-20230802112413-44.png]]
... ... @@ -441,8 +441,6 @@
441 441  
442 442  * (% style="color:#037691" %)**Client ID: “Any value”**
443 443  
444 -
445 -
446 446  (% style="color:blue" %)**On the section User credentials, set the following information:**
447 447  
448 448  * (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
... ... @@ -453,8 +453,6 @@
453 453  
454 454  * (% style="color:#037691" %)**SUBTOPIC: “Any value”**
455 455  
456 -
457 -
458 458  (% style="color:blue" %)**AT command:**
459 459  
460 460  * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
... ... @@ -469,34 +469,33 @@
469 469  
470 470  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
471 471  
649 +=== 3.8.2 Simulate with MQTT.fx ===
472 472  
473 473  
474 -=== 3.7.2 Simulate with MQTT.fx ===
475 -
476 476  [[image:image-20230802112413-52.png]]
477 477  
478 478  
479 -[[image:image-20230808105300-2.png]]
655 +[[image:image-20230808105300-2.png||height="553" width="1026"]]
480 480  
657 +
481 481  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
482 482  
483 -[[image:image-20230808105217-1.png]]
660 +[[image:image-20230808105217-1.png||height="556" width="1031"]]
484 484  
485 485  [[image:image-20230808105329-3.png]]
486 486  
487 487  
488 -=== 3.7.3 tago data ===
665 +=== 3.8.3 tago data ===
489 489  
490 490  
491 -[[image:image-20230802112413-50.png]]
668 +[[image:image-20230802112413-50.png||height="242" width="1037"]]
492 492  
493 493  [[image:image-20230802112413-51.png||height="184" width="696"]]
494 494  
495 495  
673 +== 3.9 TCP Connection ==
496 496  
497 -== 3.8 TCP Connection ==
498 498  
499 -
500 500  (% style="color:blue" %)**AT command:**
501 501  
502 502  * (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
... ... @@ -505,8 +505,6 @@
505 505  
506 506  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
507 507  
508 -
509 -
510 510  (% style="color:blue" %)**Sensor Console Output when Uplink:**
511 511  
512 512  [[image:image-20230807233631-1.png]]
... ... @@ -517,4 +517,233 @@
517 517  [[image:image-20230807233631-2.png]]
518 518  
519 519  
694 +== 3.10 AWS Connection ==
695 +
696 +
697 +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]]
698 +
699 +
700 +
701 +
702 += 4. MQTT/UDP/TCP downlink =
703 +
704 +== 4.1 MQTT (via MQTT.fx) ==
705 +
706 +Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
707 +
708 +**1.** Configure node MQTT connection (via MQTT.fx):
709 +
710 +(% style="color:blue" %)**AT command:**
711 +
712 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
713 +
714 +* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
715 +
716 +* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
717 +
718 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
719 +
720 +* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
721 +
722 +* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
723 +
724 +(% 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.**
725 +
726 +[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
727 +
728 +
729 +**2. **When the node uplink packets, we can observe the data in MQTT.fx.
730 +
731 +[[image:image-20240418144337-1.png||height="709" width="802"]]
732 +
733 +**3. **The downlink command can be successfully sent only when the downlink port is open.
734 +
735 + The downlink port is opened for about 3 seconds after uplink packets are sent.
736 +
737 + 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.
738 +
739 +[[image:image-20240418150435-3.png||height="582" width="659"]]
740 +
741 +[[image:image-20240418150932-4.png||height="492" width="1061"]]
742 +
743 +(% 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.**
744 +
745 +
746 +
747 +
748 +
749 +
750 +
751 += 5. FAQ =
752 +
753 +== 5.1 What is the usage of Multi Sampling and One Uplink? ==
754 +
755 +
756 +The NB series has the feature for Multi Sampling and one uplink. See one of them
757 +
758 +[[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]]
759 +
760 +User can use this feature for below purpose:
761 +
762 +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.
763 +1. Give more sampling data points.
764 +1. Increase reliable in transmission. For example. If user set
765 +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)
766 +1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
767 +1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
768 +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.
769 +
770 +== 5.2 Why the uplink JSON format is not standard? ==
771 +
772 +
773 +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.
774 +
775 +The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
776 +
777 +[[image:image-20240229233154-1.png]]
778 +
779 +
780 += 6. Trouble Shooting: =
781 +
782 +== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
783 +
784 +
785 +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.
786 +
787 +If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
788 +
789 +[[image:image-20240207002003-1.png]]
790 +
791 +
792 +If fail to attach network, it will shows signal 99. as below:
793 +
794 +[[image:image-20240207002129-2.png]]
795 +
796 +
797 +(% class="lead" %)
798 +When see this issue, below are the checklist:
799 +
800 +* 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.
801 +* 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]].
802 +* 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]].
803 +* Check if the device is attached to Carrier network but reject. (need to check with operator).
804 +* Check if the antenna is connected firmly.
805 +
806 +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.
807 +
808 +
809 +== 6.2 Issue: "NBIOT did not respond" ==
810 +
811 +
812 +(% class="box errormessage" %)
813 +(((
814 +11:24:22.397 [44596]NBIOT did not respond.
815 +11:24:24.315 [46530]NBIOT did not respond.
816 +11:24:26.256 [48464]NBIOT did not respond.
817 +11:24:28.196 [50398]NBIOT did not respond.
818 +11:24:30.115 [52332]NBIOT did not respond.
819 +11:24:32.127 [54266]NBIOT did not respond.
820 +11:24:32.127 [54299]Restart the module...
821 +11:24:39.181 [61332]No response when shutting down
822 +)))
823 +
824 +This issue might due to initiate issue for NB-IoT module. In this case, please try:
825 +
826 +1) Open Enclosure
827 +
828 +2) Power off device by pull out the power on Jumper
829 +
830 +3) Power on device by connect back the power jumper.
831 +
832 +4) push reset button.
833 +
834 +[[image:image-20240208001740-1.png]]
835 +
836 +
837 +== 6.3 Issue: "Failed to readI MSI number" ==
838 +
839 +
840 +(% class="box errormessage" %)
841 +(((
842 +[18170]Failed to read IMSI:1umber.
843 +[20109]Failed to read IMSI numoer.
844 +[22048]Failed to read IMSI number.
845 +[29842lRestart the module...
846 +)))
847 +
848 +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"]].
849 +
850 +
851 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
852 +
853 +
854 +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.
855 +
856 +[[image:image-20240226111928-1.png]]
857 +
858 +
859 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
860 +
861 +(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
862 +=== UDP: ===
863 +
864 +(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
865 +Its downlink command is the same as the AT command, but brackets are required.
866 +Example:
867 +
868 +{AT+TDC=300}
869 +
870 +
871 +(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
872 +=== MQTT: ===
873 +
874 +Json：
875 +
876 +The Json format in MQTT mode needs to be configured with all commands.
877 +If you have configurations that need to be changed, please change them in the template below.
878 +Template:
879 +
880 +{
881 +"AT+SERVADDR":"119.91.62.30,1882",
882 +"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
883 +"AT+UNAME":"usenamedragino",
884 +"AT+PWD":"passworddragino",
885 +"AT+PUBTOPIC":"123",
886 +"AT+SUBTOPIC":"321",
887 +"AT+TDC":"7200",
888 +"AT+INTMOD":"0",
889 +"AT+APN":"NULL",
890 +"AT+5VT":"0",
891 +"AT+PRO":"3,5",
892 +"AT+TR":"900",
893 +"AT+NOUD":"0",
894 +"AT+CSQTIME":"5",
895 +"AT+DNSTIMER":"0",
896 +"AT+TLSMOD":"0,0",
897 +"AT+MQOS":"0",
898 +"AT+TEMPALARM1":"0",
899 +"AT+TEMPALARM2":"10",
900 +"AT+TEMPALARM3":"0"
901 +}
902 +
903 +Hex：
904 +
905 +MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
906 +
907 +The supported commands are consistent with LoRaWAN's hex commands.
908 +Please refer to the following link to obtain the hex format:
909 +
910 +[[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/]]
911 +
912 +
913 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs？(%%) ==
914 +
915 +* **AT Command: AT** **+GETLOG**
916 +
917 +This command can be used to query upstream logs of data packets.
918 +
919 +[[image:image-20240701114700-1.png]]
920 +
921 +
922 +
520 520  
image-20230809180523-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +91.9 KB
Content
image-20230810083934-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +85.1 KB
Content
image-20230810084048-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +63.7 KB
Content
image-20230816201942-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +99.8 KB
Content
image-20240129170024-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +52.3 KB
Content
image-20240129170216-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +56.0 KB
Content
image-20240129170539-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +55.0 KB
Content
image-20240129171029-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +36.1 KB
Content
image-20240129171113-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +47.2 KB
Content
image-20240129171236-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +49.8 KB
Content
image-20240129172056-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +69.8 KB
Content
image-20240129172136-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +80.4 KB
Content
image-20240129173116-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +110.8 KB
Content
image-20240129173541-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +95.4 KB
Content
image-20240129174518-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +23.2 KB
Content
image-20240129174657-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +141.9 KB
Content
image-20240129174840-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +92.9 KB
Content
image-20240202111546-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +33.3 KB
Content
image-20240207002003-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content
image-20240207002129-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +17.9 KB
Content
image-20240208001740-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +487.1 KB
Content
image-20240208102804-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +507.6 KB
Content
image-20240226111928-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +52.0 KB
Content
image-20240229233154-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +39.5 KB
Content
image-20240417173549-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +70.3 KB
Content
image-20240417180145-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +104.1 KB
Content
image-20240417180737-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +59.7 KB
Content
image-20240418144337-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +95.1 KB
Content
image-20240418144714-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +50.3 KB
Content
image-20240418150435-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +44.1 KB
Content
image-20240418150932-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +103.4 KB
Content
image-20240701114700-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +291.5 KB
Content
image-20240729141300-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +176.9 KB
Content
image-20240729142505-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +202.0 KB
Content
image-20240729144058-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +140.7 KB
Content
image-20240729150142-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +128.0 KB
Content
image-20240729160802-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +162.8 KB
Content
image-20240729161543-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +166.8 KB
Content
image-20240729172234-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +57.8 KB
Content
image-20240729172305-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +49.3 KB
Content
image-20240729172415-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +54.3 KB
Content