Last modified by Mengting Qiu on 2025/03/08 11:33
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Edwin - Content
-
... ... @@ -310,7 +310,6 @@ 310 310 311 311 ==== 3.4.2.1 Scan QR Code to get the device info ==== 312 312 313 - 314 314 Users can use their phones or computers to scan QR codes to obtain device data information. 315 315 316 316 [[image:image-20230808170051-8.png||height="255" width="259"]] ... ... @@ -320,40 +320,34 @@ 320 320 321 321 ==== 3.4.2.2 Claim Device to User Account ==== 322 322 323 - 324 324 By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account. 325 325 326 326 325 + 327 327 === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) === 328 328 328 +**Step1:Add a device** 329 329 330 -**Step1: Add a device** 331 - 332 332 [[image:image-20240129170024-1.png||height="330" width="900"]] 333 333 332 +**Step2:Choose your device type,please select dragino NB-IOT device** 334 334 335 -**Step2: Choose your device type,please select dragino NB-IOT device** 336 - 337 337 [[image:image-20240129170216-2.png||height="534" width="643"]] 338 338 336 +**Step3:Choose to create a new device** 339 339 340 -**Step3: Choose to create a new device** 341 - 342 342 [[image:image-20240129170539-3.png||height="459" width="646"]] 343 343 340 +**Step4:Fill in the device ID of your NB device** 344 344 345 -**Step4: Fill in the device ID of your NB device** 346 - 347 347 [[image:image-20240202111546-1.png||height="378" width="651"]] 348 348 344 +**Step5:Please select your device plan according to your needs and complete the creation of the device** 349 349 350 -**Step5: Please select your device plan according to your needs and complete the creation of the device** 351 - 352 352 [[image:image-20240129171236-6.png||height="450" width="648"]] 353 353 348 +**Step6:Please add the decoder at the payload decoder of the device configuration.** 354 354 355 -**Step6: Please add the decoder at the payload decoder of the device configuration.** 356 - 357 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 358 359 359 [[image:image-20240129172056-7.png||height="457" width="816"]] ... ... @@ -360,14 +360,12 @@ 360 360 361 361 [[image:image-20240129173116-9.png||height="499" width="814"]] 362 362 356 +**Step6:Add the output of the decoder as a field** 363 363 364 -**Step7: Add the output of the decoder as a field** 365 - 366 366 [[image:image-20240129173541-10.png||height="592" width="968"]] 367 367 360 +**Step7:Customize the dashboard and use fields as parameters of the dashboard** 368 368 369 -**Step8: Customize the dashboard and use fields as parameters of the dashboard** 370 - 371 371 [[image:image-20240129174518-11.png||height="147" width="1042"]] 372 372 373 373 [[image:image-20240129174657-12.png||height="538" width="916"]] ... ... @@ -377,7 +377,6 @@ 377 377 378 378 === 3.4.4 For device have not configured to connect to DataCake === 379 379 380 - 381 381 (% class="lead" %) 382 382 Use AT command for connecting to DataCake 383 383 ... ... @@ -639,7 +639,6 @@ 639 639 640 640 == 4.1 What is the usage of Multi Sampling and One Uplink? == 641 641 642 - 643 643 The NB series has the feature for Multi Sampling and one uplink. See one of them 644 644 645 645 [[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]] ... ... @@ -655,20 +655,18 @@ 655 655 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. 656 656 657 657 658 - 659 659 == 4.2 Why the uplink JSON format is not standard? == 660 660 661 - 662 662 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. 663 663 664 664 [[image:image-20240229233154-1.png]] 665 665 666 666 654 + 667 667 = 5. Trouble Shooting: = 668 668 669 669 == 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. == 670 670 671 - 672 672 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. 673 673 674 674 If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31) ... ... @@ -695,7 +695,6 @@ 695 695 696 696 == 5.2 Issue: "NBIOT did not respond" == 697 697 698 - 699 699 (% class="box errormessage" %) 700 700 ((( 701 701 11:24:22.397 [44596]NBIOT did not respond. ... ... @@ -723,7 +723,6 @@ 723 723 724 724 == 5.3 Issue: "Failed to readI MSI number" == 725 725 726 - 727 727 (% class="box errormessage" %) 728 728 ((( 729 729 [18170]Failed to read IMSI:1umber. ... ... @@ -737,7 +737,6 @@ 737 737 738 738 == 5.4 Why sometime the AT Command is slow in reponse? == 739 739 740 - 741 741 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. 742 742 743 743 [[image:image-20240226111928-1.png]]