Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 103.1
edited by Edwin Chen
on 2023/10/02 18:27
Change comment: There is no comment for this version
To version 136.1
edited by Edwin Chen
on 2024/02/08 10:28
Change comment: Uploaded new attachment "image-20240208102804-1.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -18,6 +18,7 @@
18 18  
19 19  == 2.1 General Configure to attach network ==
20 20  
21 +
21 21  To attache NB-IoT sensors to NB-IoT Network, You need to:
22 22  
23 23  1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
... ... @@ -42,10 +42,26 @@
42 42  
43 43  == 2.2 Speed Up Network Attach time ==
44 44  
45 -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. User can lock the band to specify band for its operator to make this faster.
46 46  
47 +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.
47 47  
49 +(% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
48 48  
51 +(% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
52 +
53 +(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
54 +
55 +(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
56 +(% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
57 +(% style="color:#037691" %)**Telstra**(%%)        AT+QBAND=1,28
58 +(% style="color:#037691" %)**Softband**(%%)     AT+QBAND=2,3,8
59 +
60 +After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
61 +
62 +
63 +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/]]**
64 +
65 +
49 49  = 3. Configure to connect to different servers =
50 50  
51 51  == 3.1 General UDP Connection ==
... ... @@ -59,7 +59,7 @@
59 59  
60 60  We can use PC tool to simulate UDP connection to make sure server works ok.
61 61  
62 -[[image:image-20230802112413-1.png]]
79 +[[image:image-20230802112413-1.png||height="468" width="1024"]]
63 63  
64 64  
65 65  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -145,7 +145,6 @@
145 145  
146 146  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
147 147  
148 -
149 149  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
150 150  
151 151  
... ... @@ -187,9 +187,9 @@
187 187  
188 188  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
189 189  
190 -
191 191  ==== 3.3.3.2 Uplink Examples ====
192 192  
208 +
193 193  [[image:image-20230816201942-1.png]]
194 194  
195 195  For SE01-NB
... ... @@ -248,7 +248,6 @@
248 248  |(% 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" %)
249 249  |(% 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" %)
250 250  
251 -
252 252  == 3.4 [[Datacake>>https://datacake.co/]] ==
253 253  
254 254  
... ... @@ -263,16 +263,16 @@
263 263  
264 264  * (% 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.
265 265  
281 +=== 3.4.1 For device Already has template ===
266 266  
267 -=== 3.4.1 Create device ===
283 +==== 3.4.1.1 Create Device ====
268 268  
269 -
270 270  (% style="color:blue" %)**Add Device**(%%) in DataCake.
271 271  
272 -[[image:image-20230808162301-1.png||height="473" width="994"]]
287 +[[image:image-20230808162301-1.png||height="453" width="952"]]
273 273  
274 274  
275 -[[image:image-20230808162342-2.png]]
290 +[[image:image-20230808162342-2.png||height="541" width="952"]]
276 276  
277 277  
278 278  (% style="color:blue" %)**Choose the correct model**(%%) from template.
... ... @@ -282,15 +282,16 @@
282 282  
283 283  (% 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.
284 284  
285 -[[image:image-20230808163612-7.png]]
300 +[[image:image-20230808163612-7.png||height="549" width="952"]]
286 286  
287 287  [[image:image-20230808163035-5.png]]
288 288  
289 -[[image:image-20230808163049-6.png]]
304 +[[image:image-20230808163049-6.png||height="544" width="926"]]
290 290  
291 291  
292 -=== 3.4.2 Scan QR code to obtain data ===
307 +=== 3.4.2 For Device already registered in DataCake before shipped ===
293 293  
309 +==== 3.4.2.1 Scan QR Code to get the device info ====
294 294  
295 295  Users can use their phones or computers to scan QR codes to obtain device data information.
296 296  
... ... @@ -299,9 +299,60 @@
299 299  [[image:image-20230808170548-9.png]]
300 300  
301 301  
302 -=== 3.4.2 AT command for connecting to DataCake ===
318 +==== 3.4.2.2 Claim Device to User Account ====
303 303  
320 +By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
304 304  
322 +
323 +
324 +=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
325 +
326 +**Step1:Add a device**
327 +
328 +[[image:image-20240129170024-1.png||height="330" width="900"]]
329 +
330 +**Step2:Choose your device type,please select dragino NB-IOT device**
331 +
332 +[[image:image-20240129170216-2.png||height="534" width="643"]]
333 +
334 +**Step3:Choose to create a new device**
335 +
336 +[[image:image-20240129170539-3.png||height="459" width="646"]]
337 +
338 +**Step4:Fill in the device ID of your NB device**
339 +
340 +[[image:image-20240202111546-1.png||height="378" width="651"]]
341 +
342 +**Step5:Please select your device plan according to your needs and complete the creation of the device**
343 +
344 +[[image:image-20240129171236-6.png||height="450" width="648"]]
345 +
346 +**Step6:Please add the decoder at the payload decoder of the device configuration.**
347 +
348 +**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]]
349 +
350 +[[image:image-20240129172056-7.png||height="457" width="816"]]
351 +
352 +[[image:image-20240129173116-9.png||height="499" width="814"]]
353 +
354 +**Step6:Add the output of the decoder as a field**
355 +
356 +[[image:image-20240129173541-10.png||height="592" width="968"]]
357 +
358 +**Step7:Customize the dashboard and use fields as parameters of the dashboard**
359 +
360 +[[image:image-20240129174518-11.png||height="147" width="1042"]]
361 +
362 +[[image:image-20240129174657-12.png||height="538" width="916"]]
363 +
364 +[[image:image-20240129174840-13.png||height="536" width="750"]]
365 +
366 +
367 +=== 3.4.4 For device have not configured to connect to DataCake ===
368 +
369 +(% class="lead" %)
370 +Use AT command for connecting to DataCake
371 +
305 305  (% style="color:blue" %)**AT+PRO=2,0**
306 306  
307 307  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
... ... @@ -330,7 +330,7 @@
330 330  
331 331  Please select the NB95S31B template.
332 332  
333 -[[image:image-20230809173310-5.png]]
400 +[[image:image-20230809173310-5.png||height="558" width="926"]]
334 334  
335 335  [[image:image-20230809173438-6.png]]
336 336  
... ... @@ -339,7 +339,7 @@
339 339  
340 340  Successfully imported template.
341 341  
342 -[[image:image-20230809173835-8.png]]
409 +[[image:image-20230809173835-8.png||height="515" width="860"]]
343 343  
344 344  
345 345  Users can set UDP port.
... ... @@ -354,16 +354,19 @@
354 354  
355 355  [[image:image-20230810083934-1.png]]
356 356  
357 -[[image:image-20230810084048-2.png]]
424 +[[image:image-20230810084048-2.png||height="535" width="1052"]]
358 358  
426 +
359 359  === 3.5.3 Configure NB-IoT Sensors ===
360 360  
361 361  
362 -* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
430 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
431 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
432 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
433 +* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
434 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
435 +* (% style="color:#037691" %)**AT+PWD=“Your device token”**
363 363  
364 -* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
365 -
366 -
367 367  == 3.6 ThingsBoard.Cloud (via MQTT) ==
368 368  
369 369  === 3.6.1 Configure ThingsBoard ===
... ... @@ -373,7 +373,7 @@
373 373  
374 374  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
375 375  
376 -[[image:image-20230802112413-32.png]]
446 +[[image:image-20230802112413-32.png||height="583" width="1066"]]
377 377  
378 378  
379 379  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -385,7 +385,7 @@
385 385  
386 386  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.
387 387  
388 -[[image:image-20230802112413-33.png||height="732" width="1302"]]
458 +[[image:image-20230802112413-33.png||height="597" width="1061"]]
389 389  
390 390  
391 391  (% style="color:blue" %)**Downlink Converter**
... ... @@ -392,7 +392,7 @@
392 392  
393 393  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
394 394  
395 -[[image:image-20230802112413-34.png||height="734" width="1305"]]
465 +[[image:image-20230802112413-34.png||height="598" width="1063"]]
396 396  
397 397  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
398 398  
... ... @@ -402,23 +402,23 @@
402 402  
403 403  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**;
404 404  
405 -[[image:image-20230802112413-35.png||height="738" width="1312"]]
475 +[[image:image-20230802112413-35.png||height="597" width="1062"]]
406 406  
407 407  
408 408  * The next steps is to add the recently created uplink and downlink converters;
409 409  
410 -[[image:image-20230802112413-36.png||height="736" width="1308"]]
480 +[[image:image-20230802112413-36.png||height="598" width="1062"]]
411 411  
412 -[[image:image-20230802112413-37.png||height="735" width="1307"]]
482 +[[image:image-20230802112413-37.png||height="598" width="1064"]]
413 413  
414 414  
415 415  (% style="color:blue" %)**Add a topic filter:**
416 416  
417 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
487 +Consistent with the theme of the node setting.
418 418  
419 419  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
420 420  
421 -[[image:image-20230802112413-38.png||height="731" width="1300"]]
491 +[[image:image-20230802112413-38.png||height="598" width="1064"]]
422 422  
423 423  
424 424  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -426,7 +426,7 @@
426 426  
427 427  [[image:image-20230802112413-39.png]]
428 428  
429 -[[image:image-20230802112413-40.png]]
499 +[[image:image-20230802112413-40.png||height="525" width="980"]]
430 430  
431 431  
432 432  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -448,11 +448,11 @@
448 448  
449 449  Test Uplink by click the button for 1 second
450 450  
451 -[[image:image-20230802112413-41.png]]
521 +[[image:image-20230802112413-41.png||height="496" width="828"]]
452 452  
453 453  [[image:image-20230802112413-42.png]]
454 454  
455 -[[image:image-20230802112413-43.png]]
525 +[[image:image-20230802112413-43.png||height="407" width="825"]]
456 456  
457 457  
458 458  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
... ... @@ -508,7 +508,6 @@
508 508  
509 509  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
510 510  
511 -
512 512  === 3.7.2 Simulate with MQTT.fx ===
513 513  
514 514  
... ... @@ -515,12 +515,12 @@
515 515  [[image:image-20230802112413-52.png]]
516 516  
517 517  
518 -[[image:image-20230808105300-2.png]]
587 +[[image:image-20230808105300-2.png||height="553" width="1026"]]
519 519  
520 520  
521 521  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
522 522  
523 -[[image:image-20230808105217-1.png]]
592 +[[image:image-20230808105217-1.png||height="556" width="1031"]]
524 524  
525 525  [[image:image-20230808105329-3.png]]
526 526  
... ... @@ -528,7 +528,7 @@
528 528  === 3.7.3 tago data ===
529 529  
530 530  
531 -[[image:image-20230802112413-50.png]]
600 +[[image:image-20230802112413-50.png||height="242" width="1037"]]
532 532  
533 533  [[image:image-20230802112413-51.png||height="184" width="696"]]
534 534  
... ... @@ -552,3 +552,76 @@
552 552  (% style="color:blue" %)**See result in TCP Server:**
553 553  
554 554  [[image:image-20230807233631-2.png]]
624 +
625 +
626 += 4. FAQ =
627 +
628 +== 4.1 What is the usage of Multi Sampling and One Uplink? ==
629 +
630 +The NB series has the feature for Multi Sampling and one uplink. See one of them
631 +
632 +[[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]]
633 +
634 +User can use this feature for below purpose:
635 +
636 +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.
637 +1. Give more sampling data points.
638 +1. Increase reliable in transmission. For example. If user set
639 +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)
640 +1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
641 +1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
642 +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.
643 +
644 += 5. Trouble Shooting: =
645 +
646 +== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
647 +
648 +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.
649 +
650 +If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
651 +
652 +[[image:image-20240207002003-1.png]]
653 +
654 +
655 +If fail to attach network, it will shows signal 99. as below:
656 +
657 +[[image:image-20240207002129-2.png]]
658 +
659 +
660 +(% class="lead" %)
661 +When see this issue, below are the checklist:
662 +
663 +* 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.
664 +* 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]].
665 +* 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]].
666 +* Check if the device is attached to Carrier network but reject. (need to check with operator).
667 +* Check if the antenna is connected firmly.
668 +
669 +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.
670 +
671 +
672 +== 5.2 NBIOT did not respond issue. ==
673 +
674 +(% class="box errormessage" %)
675 +(((
676 +11:24:22.397 [44596]NBIOT did not respond.
677 +11:24:24.315 [46530]NBIOT did not respond.
678 +11:24:26.256 [48464]NBIOT did not respond.
679 +11:24:28.196 [50398]NBIOT did not respond.
680 +11:24:30.115 [52332]NBIOT did not respond.
681 +11:24:32.127 [54266]NBIOT did not respond.
682 +11:24:32.127 [54299]Restart the module...
683 +11:24:39.181 [61332]No response when shutting down
684 +)))
685 +
686 +This issue might due to initiate issue for NB-IoT module. In this case, please try:
687 +
688 +1) Open Enclosure
689 +
690 +2) Power off device by pull out the power on Jumper
691 +
692 +3) Power on device by connect back the power jumper.
693 +
694 +4) push reset button.
695 +
696 +[[image:image-20240208001740-1.png]]
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