<
From version < 3.1 >
edited by Edwin Chen
on 2024/06/02 21:55
To version < 34.2 >
edited by Mengting Qiu
on 2024/08/19 17:46
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.ting
Content
... ... @@ -23,48 +23,164 @@
23 23  1. Power On End Node
24 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>), example AT+APN=iot.1nce.net
25 25  
26 -[[image:image-20240208102804-1.png||height="286" width="696"]]
26 +[[image:image-20240602220856-1.png]]
27 27  
28 -[[image:image-20230808205045-1.png||height="293" width="438"]]
29 29  
29 +放一张如何插卡图片。
30 +
31 +
30 30  After doing above, the end nodes should be able to attach to NB-IoT network .
31 31  
32 32  The -CB and -CS models support (% style="color:blue" %)**LTE Cat NB2 and LTE-M (CAT-M1)**(%%), with below frequency band: multiple frequency bands of
33 33  
34 -~-~-(% style="color:blue" %)**CAT-NB2: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B28/B66/B71/B85 **(%%).
36 +~-~-(% style="color:blue" %)** CAT-NB2: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B28/B66/B71/B85 **(%%).
35 35  
36 -~-~-(% style="color:blue" %)**CAT-M1: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85 **(%%).
38 +~-~-(% style="color:blue" %)** CAT-M1: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85 **(%%).
37 37  
38 -Make sure you use a the NB-IoT SIM card.
40 +Make sure you use a the NB-IoT or LTE-M SIM card.
39 39  
40 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
41 -|(% 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**
42 -|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
42 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1134px" %)
43 +|(% 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:406px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:351px" %)**LTE-M Coverage**|(% style="background-color:#4f81bd; color:white; width:120px" %)**Comments**
44 +|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:406px" %)(((
43 43  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
44 44  
45 -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
46 -)))|(% style="width:135px" %)UK: Band20
47 -|(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
48 -|(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
47 +Austria, Belgium, Bulgaria, China, Croatia, Czech Republic, Denmark, Estonia, Finland, Germany, Great Britain, Greece, Hungary, Ireland,Italy, Latvia, Malta, Netherlands, Norway, Portugal, Puerto Rico, Russia, Slovak,Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands
48 +)))|(% style="width:351px" %)(((
49 +Argentina, Austria, Australia, Belgium, Canada, Denmark,Estonia, Finland, France, Germany, Great Britain, Hungary, Ireland, Japan,Jersey, Korea, Repiblic of, Latvia, Luxembourg, Mexico, Netherlands, New Zealand, Norway, Poland, Puerto Rico, Romania, Spain, Sweden, Switzerland,Taiwan, USA, US Virgin Islands.
50 +)))|(% style="width:120px" %)UK: Band20
51 +|(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:406px" %)China Mainland, HongKong|(% style="width:351px" %) |(% style="width:120px" %)
52 +|(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:406px" %)China Mainland|(% style="width:351px" %) |(% style="width:120px" %)
49 49  
50 50  == 2.2 Speed Up Network Attach time ==
51 51  
52 -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 +**BG95-M2** supports multi bands (% style="color:blue" %)**in NB-IoT and LTE-M. **(%%) 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**.
53 53  
54 -(% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
55 -(% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
56 -(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
57 -(% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=10,8,20,28,2,4,12,13,66,85,5**
58 +**Note:**Before using the NB module command, users need to power on the NB module. Run the AT+QSW command to turn on and off the NB module.Remember to shut down after using the NB module command, otherwise it will consume power.
58 58  
59 -(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
60 -(% style="color:#037691" %)**AT&T**(%%) AT+QBAND=3,12,4,2
61 -(% style="color:#037691" %)**Telstra**(%%) AT+QBAND=1,28
62 -(% style="color:#037691" %)**Softband**(%%) AT+QBAND=2,3,8
60 +Attache to 1NCE card for Australia use:
63 63  
64 -After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
62 +* AT+COPS=1,2,"50501",8
63 +* AT+QCFG="band",0,0x8000000,0x8000000,1
65 65  
65 +After connection is successful, user can use (% style="color:#037691" %)**AT+QENG="servingcell"**(%%) to check which band is actually in used.
66 +
67 +AT+QENG="servingcell"
68 ++QENG: "servingcell","NOCONN","eMTC","FD
69 +D",505,01,90D2C0B,258,9410,28,5,5,901A,-112,-17,-80,10,27
70 +
71 +
66 66  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/]]**
67 67  
74 +=== **1.Configure Frequency Band** ===
75 +
76 +AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
77 +
78 +<GSM_bandval>:
79 +
80 +0 No change 
81 +0x1 EGSM900
82 +0x2 DCS1800
83 +0x4 GSM850 
84 +0x8 PCS1900 
85 +0xF All of the supported bands above
86 +
87 +<eMTC_bandval>:
88 +
89 +0 No change 
90 +0x1  LTE B1
91 +0x2  LTE B2 
92 +0x4  LTE B3 
93 +0x8  LTE B4 
94 +0x10  LTE B5 
95 +0x80  LTE B8 
96 +0x800  LTE B12 
97 +0x1000  LTE B13 
98 +0x20000  LTE B18 
99 +0x40000  LTE B19 
100 +0x80000  LTE B20 
101 +0x1000000  LTE B25 
102 +0x2000000  LTE B26 
103 +0x4000000  LTE B27 
104 +0x8000000  LTE B28 
105 +0x40000000  LTE B31 
106 +0x20000000000000000  LTE B66 
107 +0x800000000000000000  LTE B72 
108 +0x1000000000000000000  LTE B73 
109 +0x1000000000000000000000  LTE B85
110 +
111 +<NB-IoT_bandval>:
112 +
113 +0 No change 
114 +0x1  LTE B1
115 +0x2  LTE B2 
116 +0x4  LTE B3 
117 +0x8  LTE B4 
118 +0x10  LTE B5 
119 +0x80  LTE B8 
120 +0x800  LTE B12 
121 +0x1000  LTE B13 
122 +0x20000  LTE B18 
123 +0x40000  LTE B19 
124 +0x80000  LTE B20 
125 +0x1000000  LTE B25 
126 +0x8000000  LTE B28 
127 +0x40000000  LTE B31 
128 +0x20000000000000000  LTE B66
129 +
130 +0x400000000000000000  LTE B71
131 +0x800000000000000000  LTE B72 
132 +0x1000000000000000000  LTE B73 
133 +0x1000000000000000000000  LTE B85
134 +
135 +For example, setting the LTE-M network frequency band to 3.
136 +
137 +AT+QCFG="band",0xF,0x4,0,1
138 +
139 +When searching for all bands, the value of this command is set to:
140 +
141 +AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
142 +
143 +
144 +=== **2.Configure search network sequence** ===
145 +
146 +AT+QCFG="nwscanseq",<scanseq>,1
147 +
148 +<scanseq>:
149 +
150 +00 Automatic (eMTC → NB-IoT → GSM) 
151 +01 GSM 
152 +02 eMTC 
153 +03 NB-IoT
154 +
155 +AT+QCFG="nwscanseq",02,1  ~/~/Priority search for eMTC
156 +
157 +=== **3.Configure Network Category to be Searched for under LTE RAT** ===
158 +
159 +AT+QCFG="iotopmode",mode,1
160 +
161 +0 eMTC 
162 +1 NB-IoT 
163 +2 eMTC and NB-IoT
164 +
165 +=== **4.AT command to set frequency band and network category** ===
166 +
167 +AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f  ~/~/<eMTC_bandval>,<NB-IoT_bandval>
168 +
169 +AT+IOTMOD=0  ~/~/ 0 eMTC  1 NB-IoT  2 eMTC and NB-IoT
170 +
171 +**Example :**
172 +
173 +Taking the use of 1nce cards in **the United States** as an example.
174 +
175 +AT+APN=iot.1nce.net  ~/~/set APN
176 +
177 +AT+QBAND=0x100180A,0  ~/~/ eMTC :Set frequency band B2,B4,B12,B13,B25  NB-IoT:No change
178 +
179 +AT+IOTMOD=0  ~/~/ Set  eMTC Network
180 +
181 +**Setting the above commands in the United States will greatly reduce the network search time of the NB module.**
182 +
183 +
68 68  = 3. Configure to connect to different servers =
69 69  
70 70  == 3.1 General UDP Connection ==
... ... @@ -87,12 +87,34 @@
87 87  
88 88  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/ Set UDP server address and port
89 89  
90 -[[image:image-20230802112413-2.png]]
206 +[[image:image-20240819102802-1.png]]
91 91  
92 92  ==== 3.1.2.2 Uplink Example ====
93 93  
94 -[[image:image-20230802112413-3.png]]
210 +[[image:image-20240819105418-8.png||height="671" width="1414"]]
95 95  
212 +== 3.2 General COAP Connection ==
213 +
214 +The NB-IoT Sensor can send packet to server use COAP protocol.
215 +
216 +Below are the commands.
217 +
218 +(% style="color:blue" %)**AT Commands:**
219 +
220 +* (% style="color:#037691" %)**AT+PRO=1,0**   (%%) ~/~/ Set to use COAP protocol to uplink, Payload Type select Hex payload.
221 +
222 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%) ~/~/ Set COAP server address and port
223 +
224 +* (% style="color:#037691" %)**AT+URI1=11,"I"**  (%%) ~/~/  Configure CoAP Message Options
225 +* (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**    (%%) ~/~/ Configure CoAP Message Options
226 +
227 +[[image:image-20240819103212-2.png]]
228 +
229 +=== 3.2.1 Uplink Example ===
230 +
231 +[[image:image-20240819103909-4.png||height="453" width="955"]]
232 +
233 +
96 96  == 3.2 General MQTT Connection ==
97 97  
98 98  The NB-IoT Sensor can send packet to server use MQTT protocol.
... ... @@ -115,10 +115,11 @@
115 115  
116 116  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB**  (%%) ~/~/ Set the subscription topic of MQTT
117 117  
118 -[[image:image-20230802112413-4.png]]
256 +[[image:image-20240819105003-7.png||height="613" width="458"]]
119 119  
120 -[[image:image-20230802112413-5.png||height="530" width="987"]]
121 121  
259 +[[image:image-20240819104942-6.png||height="702" width="974"]]
260 +
122 122  (% 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.**
123 123  
124 124  == 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
... ... @@ -127,9 +127,9 @@
127 127  
128 128  [[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.
129 129  
130 -[[image:image-20230802112413-6.png||height="336" width="925"]]
269 +[[image:image-20240819173602-1.png||height="401" width="743"]]
131 131  
132 -[[image:image-20230802112413-7.png]]
271 +[[image:image-20240819173706-3.png||height="595" width="597"]]
133 133  
134 134  === 3.3.2 Simulate with MQTT.fx ===
135 135  
... ... @@ -137,7 +137,7 @@
137 137  
138 138  After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
139 139  
140 -[[image:image-20230802112413-8.png]]
279 +[[image:image-20240819173826-4.png||height="534" width="734"]]
141 141  
142 142  * (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
143 143  
... ... @@ -151,9 +151,9 @@
151 151  
152 152  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
153 153  
154 -[[image:image-20230802112413-9.png]]
293 +[[image:image-20240819174033-5.png]]
155 155  
156 -[[image:image-20230802112413-10.png]]
295 +[[image:image-20240819174209-6.png]]
157 157  
158 158  (% style="color:blue" %)**In MQTT.fx, we can publish below info:**
159 159  
... ... @@ -165,7 +165,7 @@
165 165  
166 166  (% style="color:blue" %)**Result: **
167 167  
168 -[[image:image-20230802112413-11.png||height="539" width="901"]]
307 +[[image:image-20240819174314-7.png||height="469" width="785"]]
169 169  
170 170  === 3.3.3 Configure NB-IoT Sensor for connection ===
171 171  
... ... @@ -187,7 +187,7 @@
187 187  
188 188  ==== 3.3.3.2 Uplink Examples ====
189 189  
190 -[[image:image-20230816201942-1.png]]
329 +[[image:image-20240819174540-8.png]]
191 191  
192 192  For SE01-NB
193 193  
... ... @@ -215,9 +215,9 @@
215 215  
216 216  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.
217 217  
218 -[[image:image-20230802112413-12.png||height="504" width="1011"]]
357 +[[image:image-20240819174610-9.png]]
219 219  
220 -[[image:image-20230802112413-13.png||height="331" width="978"]]
359 +[[image:image-20240819174618-10.png]]
221 221  
222 222  Below is the NB-IoT Product Table show the mapping.
223 223  
... ... @@ -559,7 +559,7 @@
559 559  
560 560  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]]
561 561  
562 -= 4. MQTT/UDP/TCP downlink =
701 += 4. COAP/UDP/MQTT/TCP downlink =
563 563  
564 564  == 4.1 MQTT (via MQTT.fx) ==
565 565  
... ... @@ -601,6 +601,24 @@
601 601  
602 602  (% 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.**
603 603  
743 += 5. GPS positioning function =
744 +
745 +=== 1. Turn on GPS function ===
746 +
747 +(% class="wikigeneratedid" %)
748 +AT+GPS=1 or 0  ~/~/GPS function on or off
749 +
750 +
751 +=== 2.Extend the time to turn on GNSS ===
752 +
753 +AT+GNSST=30  ~/~/GPS search for positioning information for 30 seconds
754 +
755 +
756 +=== 3.Get or set GPS positioning interval in units of hour ===
757 +
758 +AT+GTDC=24  ~/~/The device will activate GPS positioning every 24 hours
759 +
760 +
604 604  = 5. FAQ =
605 605  
606 606  == 5.1 What is the usage of Multi Sampling and One Uplink? ==
... ... @@ -652,7 +652,6 @@
652 652  
653 653  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.
654 654  
655 -
656 656  
657 657  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
658 658  
image-20240602220856-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +250.9 KB
Content
image-20240819102802-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +41.5 KB
Content
image-20240819103212-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +49.5 KB
Content
image-20240819103826-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +122.4 KB
Content
image-20240819103909-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +122.2 KB
Content
image-20240819104904-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +52.1 KB
Content
image-20240819104942-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +52.1 KB
Content
image-20240819105003-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +48.2 KB
Content
image-20240819105418-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +163.8 KB
Content
image-20240819112109-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +12.9 KB
Content
image-20240819173602-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +52.3 KB
Content
image-20240819173659-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +44.8 KB
Content
image-20240819173706-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +44.8 KB
Content
image-20240819173826-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +42.3 KB
Content
image-20240819174033-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +33.1 KB
Content
image-20240819174209-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +18.9 KB
Content
image-20240819174314-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +48.4 KB
Content
image-20240819174540-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +99.8 KB
Content
image-20240819174610-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +127.8 KB
Content
image-20240819174618-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +34.6 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0