Changes for page General Configure/Commands to Connect to IoT server for -NB & -NS NB-IoT models

Last modified by Mengting Qiu on 2025/07/03 18:55

From 133.1 to 132.1 From 146.1 to 145.2

From version 145.2

edited by Xiaoling
on 2024/03/01 10:15

Change comment: There is no comment for this version

To version 133.1

edited by Edwin Chen
on 2024/02/07 23:40

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 4 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.Xiaoling
++XWiki.Edwin

Content

@@ -22,13 +22,9 @@
  To attache NB-IoT sensors to NB-IoT Network, You need to:
 . Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
--1. Power Off End Node ( See below for the power off/on position)
--1. Insert the SIM card to Sensor. ( See below for direction)
--1. Power On End Node
++1. Insert the SIM card to Sensor
 . [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
--[[image:image-20240208102804-1.png||height="286" width="696"]]
--
  [[image:image-20230808205045-1.png||height="293" width="438"]]
  After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
@@ -94,6 +94,8 @@
  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%)    ~/~/  Set UDP server address and port
++* (% style="color:#037691" %)**AT+CFM=1**    (%%)      ~/~/  If the server does not respond, this command is unnecessary
++
  [[image:image-20230802112413-2.png]]
@@ -310,7 +310,6 @@
  ==== 3.4.2.1 Scan QR Code to get the device info ====
--
  Users can use their phones or computers to scan QR codes to obtain device data information.
  [[image:image-20230808170051-8.png||height="255" width="259"]]
@@ -320,40 +320,34 @@
  ==== 3.4.2.2 Claim Device to User Account ====
--
  By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
++
  === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
++**Step1:Add a device**
--**Step1: Add a device**
--
  [[image:image-20240129170024-1.png||height="330" width="900"]]
++**Step2:Choose your device type,please select dragino NB-IOT device**
--**Step2: Choose your device type,please select dragino NB-IOT device**
--
  [[image:image-20240129170216-2.png||height="534" width="643"]]
++**Step3:Choose to create a new device**
--**Step3: Choose to create a new device**
--
  [[image:image-20240129170539-3.png||height="459" width="646"]]
++**Step4:Fill in the device ID of your NB device**
--**Step4: Fill in the device ID of your NB device**
--
  [[image:image-20240202111546-1.png||height="378" width="651"]]
++**Step5:Please select your device plan according to your needs and complete the creation of the device**
--**Step5: Please select your device plan according to your needs and complete the creation of the device**
--
  [[image:image-20240129171236-6.png||height="450" width="648"]]
++**Step6:Please add the decoder at the payload decoder of the device configuration.**
--**Step6: Please add the decoder at the payload decoder of the device configuration.**
--
  **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]]
  [[image:image-20240129172056-7.png||height="457" width="816"]]
@@ -360,14 +360,12 @@
  [[image:image-20240129173116-9.png||height="499" width="814"]]
++**Step6:Add the output of the decoder as a field**
--**Step7: Add the output of the decoder as a field**
--
  [[image:image-20240129173541-10.png||height="592" width="968"]]
++**Step7:Customize the dashboard and use fields as parameters of the dashboard**
--**Step8: Customize the dashboard and use fields as parameters of the dashboard**
--
  [[image:image-20240129174518-11.png||height="147" width="1042"]]
  [[image:image-20240129174657-12.png||height="538" width="916"]]
@@ -377,7 +377,6 @@
  === 3.4.4 For device have not configured to connect to DataCake ===
--
  (% class="lead" %)
  Use AT command for connecting to DataCake
@@ -639,7 +639,6 @@
  == 4.1 What is the usage of Multi Sampling and One Uplink? ==
--
  The NB series has the feature for Multi Sampling and one uplink. See one of them
  [[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,10 @@
 *. 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.
--
--== 4.2 Why the uplink JSON format is not standard? ==
--
--
--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.
--
--[[image:image-20240229233154-1.png]]
--
--
  = 5. Trouble Shooting: =
  == 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
--
  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.
  If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
@@ -692,55 +692,4 @@
  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.
--
--== 5.2 Issue: "NBIOT did not respond" ==
--
--
--(% class="box errormessage" %)
--(((
--11:24:22.397 [44596]NBIOT did not respond.
--11:24:24.315 [46530]NBIOT did not respond.
--11:24:26.256 [48464]NBIOT did not respond.
--11:24:28.196 [50398]NBIOT did not respond.
--11:24:30.115 [52332]NBIOT did not respond.
--11:24:32.127 [54266]NBIOT did not respond.
--11:24:32.127 [54299]Restart the module...
--11:24:39.181 [61332]No response when shutting down
--)))
--
--This issue might due to initiate issue for NB-IoT module. In this case, please try:
--
--1) Open Enclosure
--
--2) Power off device by pull out the power on Jumper
--
--3) Power on device by connect back the power jumper.
--
--4) push reset button.
--
--[[image:image-20240208001740-1.png]]
--
--
--== 5.3 Issue: "Failed to readI MSI number" ==
--
--
--(% class="box errormessage" %)
--(((
--[18170]Failed to read IMSI:1umber.
--[20109]Failed to read IMSI numoer.
--[22048]Failed to read IMSI number.
--[29842lRestart the module...
--)))
--
--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"]].
--
--
--== 5.4 Why sometime the AT Command is slow in reponse? ==
--
--
--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.
--
--[[image:image-20240226111928-1.png]]
--
--

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

Changes for page General Configure/Commands to Connect to IoT server for -NB & -NS NB-IoT models

Summary

Details

Applications

Navigation