Version 219.2 by Xiaoling on 2024/12/12 11:35
Show last authors
1 (% class="wikigeneratedid" id="HTableofContents:" %)
2 **Table of Contents:**
3
4 {{toc/}}
5
6
7
8
9
10
11 = 1. The use of this guideline =
12
13
14 This configure instruction is for Dragino NB-IoT models with -NB or -NS suffix, for example DDS75-NB. These models use the same NB-IoT Module **[[BC660K-GL>>https://www.quectel.com/product/lpwa-bc660k-gl-nb2]]** and has the same software structure. The have the same configure instruction to different IoT servers. Use can follow the instruction here to see how to configure to connect to those servers.
15
16
17 = 2. Attach Network =
18
19 == 2.1 General Configure to attach network ==
20
21
22 To attache NB-IoT sensors to NB-IoT Network, You need to:
23
24 1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
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
29
30 [[image:image-20240208102804-1.png||height="286" width="696"]]
31
32 [[image:image-20230808205045-1.png||height="293" width="438"]]
33
34 After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
35
36 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.
37
38 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
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**
40 |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
41 **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
42
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
45 |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
46 |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
47
48 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
49 |(% style="background-color:#4f81bd; color:white; width:152px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:169px" %)**AT+QCGDEFCONT=**|(% style="background-color:#4f81bd; color:white; width:427px" %)**Command Explanation**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
50 |(% style="width:152px" %)**[[1NCE>>https://1nce.com]]/[[NB card purchased by the customer>>https://1nce.com]]**|(% style="width:169px" %)iot.1nce.net/xxx|(% style="width:427px" %)This command sets the PSD connection settings for PDN connection on power-up. When the MT attaches to the NB-IoT network on power-on, a PDN connection setup is performed. Therefore, PDN connection settings are stored in NVRAM so that they can be used by the modem during the attachment.|(% style="width:135px" %)
51
52 == 2.2 Speed Up Network Attach time ==
53
54
55 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
57 (% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
58 (% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
59 (% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
60 (% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=10,8,20,28,2,4,12,13,66,85,5**
61
62 (% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
63 (% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
64 (% style="color:#037691" %)**Telstra**(%%)        AT+QBAND=1,28
65 (% style="color:#037691" %)**Softband**(%%)     AT+QBAND=2,3,8
66
67 After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
68
69 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.
70
71 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/]]**
72
73
74 = 3. Configure to connect to different servers =
75
76 == 3.1 General UDP Connection ==
77
78
79 The NB-IoT Sensor can send packet to server use UDP protocol.
80
81
82 === 3.1.1 Simulate UDP Connection by PC tool ===
83
84
85 We can use PC tool to simulate UDP connection to make sure server works ok.
86
87 [[image:image-20230802112413-1.png||height="468" width="1024"]]
88
89
90 === 3.1.2 Configure NB-IoT Sensor ===
91
92 ==== 3.1.2.1 AT Commands ====
93
94
95 (% style="color:blue" %)**AT Commands:**
96
97 * (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/  Set to use UDP protocol to uplink ,Payload Type select Hex payload
98
99 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
100
101 [[image:image-20230802112413-2.png]]
102
103
104 ==== 3.1.2.2 Uplink Example ====
105
106
107 [[image:image-20230802112413-3.png]]
108
109
110 == 3.2 General MQTT Connection ==
111
112
113 The NB-IoT Sensor can send packet to server use MQTT protocol.
114
115 Below are the commands.
116
117 (% style="color:blue" %)**AT Commands:**
118
119 * (% style="color:#037691" %)**AT+PRO=3,0**   (%%) ~/~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
120
121 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883**  (%%) ~/~/  Set MQTT server address and port
122
123 * (% style="color:#037691" %)**AT+CLIENT=CLIENT**     (%%) ~/~/  Set up the CLIENT of MQTT
124
125 * (% style="color:#037691" %)**AT+UNAME=UNAME**        (%%) ~/~/  Set the username of MQTT
126
127 * (% style="color:#037691" %)**AT+PWD=PWD**             (%%) ~/~/  Set the password of MQTT
128
129 * (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB**  (%%) ~/~/  Set the sending topic of MQTT
130
131 * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB**  (%%) ~/~/  Set the subscription topic of MQTT
132
133 [[image:image-20230802112413-4.png]]
134
135 [[image:image-20230802112413-5.png||height="530" width="987"]]
136
137 (% 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.**
138
139
140 == 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
141
142 === 3.3.1 Get MQTT Credentials ===
143
144
145 [[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.
146
147 [[image:image-20230802112413-6.png||height="336" width="925"]]
148
149 [[image:image-20230802112413-7.png]]
150
151
152 === 3.3.2 Simulate with MQTT.fx ===
153
154 ==== 3.3.2.1 Establish MQTT Connection ====
155
156
157 After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
158
159 [[image:image-20230802112413-8.png]]
160
161 * (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
162
163 * (% style="color:#037691" %)**Broker Port:**(%%) 1883
164
165 * (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID>
166
167 * (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name>
168
169 * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
170
171
172 ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
173
174
175 [[image:image-20230802112413-9.png]]
176
177 [[image:image-20230802112413-10.png]]
178
179
180 (% style="color:blue" %)**In MQTT.fx, we can publish below info:**
181
182 * (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
183
184 * (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH
185
186 Where 63 and 67 are the value to be published to field1 & field2.
187
188
189 (% style="color:blue" %)**Result: **
190
191 [[image:image-20230802112413-11.png||height="539" width="901"]]
192
193
194 === 3.3.3 Configure NB-IoT Sensor for connection ===
195
196 ==== 3.3.3.1 AT Commands: ====
197
198
199 In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
200
201 * (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
202
203 * (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
204
205 * (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
206
207 * (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>**
208
209 * (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
210
211 * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
212
213
214 ==== 3.3.3.2 Uplink Examples ====
215
216
217 [[image:image-20230816201942-1.png]]
218
219 For SE01-NB
220
221 For DDS20-NB
222
223 For DDS45-NB
224
225 For DDS75-NB
226
227 For NMDS120-NB
228
229 For SPH01-NB
230
231 For NLM01-NB
232
233 For NMDS200-NB
234
235 For CPN01-NB
236
237 For DS03A-NB
238
239 For SN50V3-NB
240
241
242 ==== 3.3.3.3 Map fields to sensor value ====
243
244
245 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.
246
247
248 [[image:image-20230802112413-12.png||height="504" width="1011"]]
249
250 [[image:image-20230802112413-13.png||height="331" width="978"]]
251
252
253 Below is the NB-IoT Product Table show the mapping.
254
255 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
256 |(% style="background-color:#4f81bd; width:143px" %) |(% style="background-color:#4f81bd; color:white; width:103px" %)Field1|(% style="background-color:#4f81bd; color:white; width:102px" %)Field2|(% style="background-color:#4f81bd; color:white; width:157px" %)Field3|(% style="background-color:#4f81bd; color:white; width:154px" %)Field4|(% style="background-color:#4f81bd; color:white; width:153px" %)Field5|(% style="background-color:#4f81bd; color:white; width:151px" %)Field6|(% style="background-color:#4f81bd; color:white; width:160px" %)Field7|(% style="background-color:#4f81bd; color:white; width:152px" %)Field8|(% style="background-color:#4f81bd; color:white; width:67px" %)Field9|(% style="background-color:#4f81bd; color:white; width:69px" %)Field10
257 |(% style="background-color:#4f81bd; color:white; width:143px" %)S31x-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
258 |(% style="background-color:#4f81bd; color:white; width:143px" %)SE01-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)conduct|(% style="width:154px" %)dielectric_constant|(% style="width:153px" %)Battery|(% style="width:151px" %)RSSI|(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
259 |(% style="background-color:#4f81bd; color:white; width:143px" %)DDS20-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
260 |(% style="background-color:#4f81bd; color:white; width:143px" %)DDS45-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
261 |(% style="background-color:#4f81bd; color:white; width:143px" %)DDS75-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
262 |(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS120-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
263 |(% rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SPH01-NB|(% style="width:103px" %)ph|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% colspan="1" rowspan="1" style="width:69px" %)
264 |(% style="background-color:#4f81bd; color:white; width:143px" %)NLM01-NB|(% style="width:103px" %)Humidity|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
265 |(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS200-NB|(% style="width:103px" %)distance1|(% style="width:102px" %)distance2|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
266 |(% style="background-color:#4f81bd; color:white; width:143px" %)CPN01-NB|(% style="width:103px" %)alarm|(% style="width:102px" %)count|(% style="width:157px" %)door open duration|(% style="width:154px" %)calc flag|(% style="width:153px" %)Battery|(% style="width:151px" %)RSSI|(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
267 |(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)DS03A-NB|(% colspan="1" rowspan="1" style="width:103px" %)level|(% colspan="1" rowspan="1" style="width:102px" %)alarm|(% colspan="1" rowspan="1" style="width:157px" %)pb14door open num|(% colspan="1" rowspan="1" style="width:154px" %)pb14 last open time|(% colspan="1" rowspan="1" style="width:153px" %)pb15 level status|(% colspan="1" rowspan="1" style="width:151px" %)pb15 alarm status|(% colspan="1" rowspan="1" style="width:160px" %)pb15 door open num|(% colspan="1" rowspan="1" style="width:152px" %)pb15 last open time|(% colspan="1" rowspan="1" style="width:67px" %)Battery|(% colspan="1" rowspan="1" style="width:69px" %)RSSI
268 |(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod1|(% colspan="1" rowspan="1" style="width:103px" %)mod|(% colspan="1" rowspan="1" style="width:102px" %)Battery|(% colspan="1" rowspan="1" style="width:157px" %)RSSI|(% colspan="1" rowspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:151px" %)adc0|(% colspan="1" rowspan="1" style="width:160px" %)Temperature |(% colspan="1" rowspan="1" style="width:152px" %)Humidity|(% colspan="1" rowspan="1" style="width:67px" %) |(% colspan="1" rowspan="1" style="width:69px" %)
269 |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod2|(% 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" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)adc0|(% colspan="1" style="width:160px" %)distance|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
270 |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod3|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)adc0|(% colspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)adc1|(% colspan="1" style="width:160px" %)Temperature|(% colspan="1" style="width:152px" %)Humidity|(% colspan="1" style="width:67px" %)adc4|(% colspan="1" style="width:69px" %)
271 |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod4|(% 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" %)DS18B20 Temp2|(% colspan="1" style="width:152px" %)DS18B20 Temp3|(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
272 |(% 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" %)
273 |(% 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" %)
274
275
276 == 3.4 [[Datacake>>https://datacake.co/]] ==
277
278
279 (% class="wikigeneratedid" %)
280 Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
281
282
283 (% class="wikigeneratedid" %)
284 As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
285
286 * (% 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.
287
288 * (% 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.
289
290
291 === 3.4.1 For device Already has template ===
292
293 ==== 3.4.1.1 Create Device ====
294
295
296 (% style="color:blue" %)**Add Device**(%%) in DataCake.
297
298 [[image:image-20230808162301-1.png||height="453" width="952"]]
299
300
301 [[image:image-20230808162342-2.png||height="541" width="952"]]
302
303
304 (% style="color:blue" %)**Choose the correct model**(%%) from template.
305
306 [[image:image-20230808162421-3.png]]
307
308
309 (% 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.
310
311 [[image:image-20230808163612-7.png||height="549" width="952"]]
312
313 [[image:image-20230808163035-5.png]]
314
315 [[image:image-20230808163049-6.png||height="544" width="926"]]
316
317
318 === 3.4.2 For Device already registered in DataCake before shipped ===
319
320 ==== 3.4.2.1 Scan QR Code to get the device info ====
321
322
323 Users can use their phones or computers to scan QR codes to obtain device data information.
324
325 [[image:image-20230808170051-8.png||height="255" width="259"]]
326
327 [[image:image-20230808170548-9.png]]
328
329
330 ==== 3.4.2.2 Claim Device to User Account ====
331
332
333 By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
334
335
336 === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
337
338
339 **Step1: Add a device**
340
341 [[image:image-20240129170024-1.png||height="330" width="900"]]
342
343
344 **Step2: Choose your device type,please select dragino NB-IOT device**
345
346 [[image:image-20240129170216-2.png||height="534" width="643"]]
347
348
349 **Step3: Choose to create a new device**
350
351 [[image:image-20240129170539-3.png||height="459" width="646"]]
352
353
354 **Step4: Fill in the device ID of your NB device**
355
356 [[image:image-20240202111546-1.png||height="378" width="651"]]
357
358
359 **Step5: Please select your device plan according to your needs and complete the creation of the device**
360
361 [[image:image-20240129171236-6.png||height="450" width="648"]]
362
363
364 **Step6: Please add the decoder at the payload decoder of the device configuration.**
365
366 **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]]
367
368 **Due to version update, please use the following decoder for the new version firmware:**
369 [[dragino-end-node-decoder/Datacake-Dragino_NB_New_Version at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB_New_Version]]
370
371 [[image:image-20240129172056-7.png||height="457" width="816"]]
372
373 [[image:image-20240129173116-9.png||height="499" width="814"]]
374
375
376 **Step7: Add the output of the decoder as a field**
377
378 [[image:image-20240129173541-10.png||height="592" width="968"]]
379
380
381 **Step8: Customize the dashboard and use fields as parameters of the dashboard**
382
383 [[image:image-20240129174518-11.png||height="147" width="1042"]]
384
385 [[image:image-20240129174657-12.png||height="538" width="916"]]
386
387 [[image:image-20240129174840-13.png||height="536" width="750"]]
388
389
390 === 3.4.4 For device have not configured to connect to DataCake ===
391
392
393 (% class="lead" %)
394 Use AT command for connecting to DataCake
395
396 (% style="color:blue" %)**AT+PRO=2,0**
397
398 (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
399
400
401 == 3.5 Node-Red (via MQTT) ==
402
403 === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
404
405
406 Take S31-NB UDP protocol as an example.
407
408 Dragino provides input flow examples for the sensors.
409
410 User can download the required JSON file through Dragino Node-RED input flow template.
411
412 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]]
413
414 We can directly import the template.
415
416 The templates for S31-NB and NB95S31B are the same.
417
418
419 [[image:image-20230809173127-4.png]]
420
421
422 Please select the NB95S31B template.
423
424 [[image:image-20230809173310-5.png||height="558" width="926"]]
425
426 [[image:image-20230809173438-6.png]]
427
428 [[image:image-20230809173800-7.png]]
429
430
431 Successfully imported template.
432
433 [[image:image-20230809173835-8.png||height="515" width="860"]]
434
435
436 Users can set UDP port.
437
438 [[image:image-20230809174053-9.png]]
439
440
441 === 3.5.2 Simulate Connection ===
442
443
444 We have completed the configuration of UDP. We can try sending packets to node red.
445
446 [[image:image-20230810083934-1.png]]
447
448 [[image:image-20230810084048-2.png||height="535" width="1052"]]
449
450
451 === 3.5.3 Configure NB-IoT Sensors ===
452
453
454 * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
455 * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
456 * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
457 * (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
458 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
459 * (% style="color:#037691" %)**AT+PWD=“Your device token”**
460
461
462 == 3.6 ThingsBoard.Cloud (via MQTT) ==
463
464 === 3.6.1 Configure ThingsBoard ===
465
466 ==== 3.6.1.1 Create Device ====
467
468
469 Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
470
471 [[image:image-20230802112413-32.png||height="583" width="1066"]]
472
473
474 ==== 3.6.1.2 Create Uplink & Downlink Converter ====
475
476
477 (% style="color:blue" %)**Uplink Converter**
478
479 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.
480
481 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.
482
483 [[image:image-20230802112413-33.png||height="597" width="1061"]]
484
485
486 (% style="color:blue" %)**Downlink Converter**
487
488 The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
489
490 [[image:image-20230802112413-34.png||height="598" width="1063"]]
491
492 (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
493
494
495 ==== 3.6.1.3 MQTT Integration Setup ====
496
497
498 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**;
499
500 [[image:image-20230802112413-35.png||height="597" width="1062"]]
501
502
503 * The next steps is to add the recently created uplink and downlink converters;
504
505 [[image:image-20230802112413-36.png||height="598" width="1062"]]
506
507 [[image:image-20230802112413-37.png||height="598" width="1064"]]
508
509
510 (% style="color:blue" %)**Add a topic filter:**
511
512 Consistent with the theme of the node setting.
513
514 You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
515
516 [[image:image-20230802112413-38.png||height="598" width="1064"]]
517
518
519 === 3.6.2 Simulate with MQTT.fx ===
520
521 [[image:image-20230802112413-39.png]]
522
523 [[image:image-20230802112413-40.png||height="525" width="980"]]
524
525
526 === 3.6.3 Configure NB-IoT Sensor ===
527
528
529 (% style="color:blue" %)**AT Commands**
530
531 * (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
532
533 * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
534
535 * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
536
537 * (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
538
539 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
540
541 * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
542
543 Test Uplink by click the button for 1 second
544
545 [[image:image-20230802112413-41.png||height="496" width="828"]]
546
547 [[image:image-20230802112413-42.png]]
548
549 [[image:image-20230802112413-43.png||height="407" width="825"]]
550
551
552 == 3.7 ThingsBoard.Cloud (via COAP) ==
553
554 === 3.7.1 Configure ThingsBoard ===
555
556 ==== 3.7.1.1 Create Uplink & Downlink Converter ====
557
558
559 (% style="color:blue" %)**Uplink Converter**
560
561 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.
562
563 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.
564
565 [[image:image-20240729141300-1.png||height="552" width="1115"]]
566
567
568 (% style="color:blue" %)**Downlink Converter**
569
570 The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
571
572 [[image:image-20240729142505-3.png||height="507" width="1023"]]
573
574
575 ==== 3.7.1.2 COAP Integration Setup ====
576
577
578 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" %);
579
580 [[image:image-20240729144058-4.png||height="506" width="1021"]]
581
582
583 The next steps is to add the recently created uplink converters;
584
585 [[image:image-20240729150142-5.png||height="507" width="1023"]]
586
587
588 ==== 3.7.1.3 Add COAP Integration ====
589
590
591 ==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
592
593
594 === 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
595
596 ==== 3.7.2.1 Instruction Description ====
597
598
599 * AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
600 * AT+SERVADDR=COAP Server Address,5683
601
602 Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
603
604 [[image:image-20240729172305-12.png||height="361" width="624"]]
605
606 Note:The port for the COAP protocol has been fixed to 5683
607
608
609 * AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
610
611 If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
612
613 e.g.
614
615 * AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
616
617 [[image:image-20240729172415-13.png||height="401" width="694"]]
618
619 If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
620
621 e.g.
622
623 * AT+URL1=11, "i"
624 * AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
625
626 [[image:image-20240729172500-14.png||height="403" width="700"]]
627
628
629 == 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
630
631 === 3.8.1 Create device & Get Credentials ===
632
633
634 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.
635
636 [[image:image-20230802112413-44.png]]
637
638 [[image:image-20230802112413-45.png]]
639
640
641 Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
642
643 [[image:image-20230802112413-46.png]]
644
645
646 The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
647
648 (% style="color:blue" %)**On the Connection Profile window, set the following information:**
649
650 * (% style="color:#037691" %)**Profile Name: “Any name”**
651
652 * (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
653
654 * (% style="color:#037691" %)**Broker Port: 8883**
655
656 * (% style="color:#037691" %)**Client ID: “Any value”**
657
658 (% style="color:blue" %)**On the section User credentials, set the following information:**
659
660 * (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
661
662 * (% style="color:#037691" %)**Password: “Your device token”**
663
664 * (% style="color:#037691" %)**PUBTOPIC: “Any value”**
665
666 * (% style="color:#037691" %)**SUBTOPIC: “Any value”**
667
668 (% style="color:blue" %)**AT command:**
669
670 * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
671
672 * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
673
674 * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
675
676 * (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
677
678 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
679
680 * (% style="color:#037691" %)**AT+PWD=“Your device token”**
681
682 === 3.8.2 Simulate with MQTT.fx ===
683
684
685 [[image:image-20230802112413-52.png]]
686
687
688 [[image:image-20230808105300-2.png||height="553" width="1026"]]
689
690
691 Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
692
693 [[image:image-20230808105217-1.png||height="556" width="1031"]]
694
695 [[image:image-20230808105329-3.png]]
696
697
698 === 3.8.3 tago data ===
699
700
701 [[image:image-20230802112413-50.png||height="242" width="1037"]]
702
703 [[image:image-20230802112413-51.png||height="184" width="696"]]
704
705
706 == 3.9 TCP Connection ==
707
708
709 (% style="color:blue" %)**AT command:**
710
711 * (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
712
713 * (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
714
715 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
716
717 (% style="color:blue" %)**Sensor Console Output when Uplink:**
718
719 [[image:image-20230807233631-1.png]]
720
721
722 (% style="color:blue" %)**See result in TCP Server:**
723
724 [[image:image-20230807233631-2.png]]
725
726
727 == 3.10 AWS Connection ==
728
729
730 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]]
731
732
733 == 3.11 ThingsEye (via MQTT) ==
734
735 === 3.11.1 Configure ThingsEye ===
736
737 ==== 3.11.1.1 Create MQTT integration ====
738
739
740 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_NB”**(%%), select type (% style="color:blue" %)**MQTT**;
741
742 [[image:image-20241126175509-1.png||height="518" width="1081"]]
743
744
745 Next, directly select to create a new Uplink data converter and downlink data converter.
746
747 [[image:image-20241126180135-2.png||height="535" width="1092"]]
748
749 [[image:image-20241126180223-3.png||height="518" width="1093"]]
750
751
752 (% style="color:blue" %)**Add a topic filter:**
753
754 Consistent with the theme of the node setting.
755
756 (% style="color:red" %)**Note: Recommended MQTT broker: lns1.thingseye.io 8883, fixed use. Topic can be changed on their own, but it need to be consistent with the node's publish and subscribe topic.**
757
758 You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
759
760 [[image:image-20241126181024-4.png||height="521" width="1081"]]
761
762
763 ==== 3.11.1.2 Add credentials to the MQTT integration ====
764
765
766 Click on the MQTT integration you just created.
767
768 [[image:image-20241126181837-5.png||height="365" width="1079"]]
769
770
771 Click the edit icon in the upper right corner to enter the edit mode.
772
773 [[image:image-20241126184523-13.png||height="330" width="1075"]]
774
775
776 (% style="color:blue" %)**Add credential files.**
777
778 Click this [[link>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]] to download the certificates.
779
780 [[image:image-20241126183032-8.png||height="757" width="976"]]
781
782 When the addition is complete, save the Settings.
783
784 [[image:image-20241126184303-12.png||height="284" width="975"]]
785
786 [[image:image-20241126184211-11.png||height="161" width="977"]]
787
788
789 ==== 3.11.1.2 Setup uplink and downlink converters ====
790
791
792 First, you need to download the [[**MQTT uplink/downlink JS** **code**>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]].
793
794 * (% style="color:blue" %)**Uplink Converter**
795
796 The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume.
797
798 Go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page, and find that MQTT uplink converter that was newly created when the integration was created.
799
800 [[image:image-20241126184906-14.png||height="424" width="1100"]]
801
802 Enter edit mode and apply **MQTT uplink JS code** to this uplink converter.
803
804 [[image:image-20241126190131-15.png||height="542" width="1103"]]
805
806
807 * (% style="color:blue" %)**Downlink Converter**
808
809 Go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page, and find that MQTT downlink converter that was newly created when the integration was created.
810
811 [[image:image-20241126190251-16.png||height="372" width="1113"]]
812
813 Enter edit mode and apply **MQTT downlink JS code** to this downlink converter.
814
815 [[image:image-20241126190737-17.png||height="527" width="1114"]]
816
817
818 === 3.11.2 Simulate with MQTT.fx ===
819
820
821 [[image:image-20241126191118-18.png||height="605" width="835"]]
822
823 [[image:image-20241126193252-25.png||height="663" width="803"]]
824
825
826 === 3.6.3 Configure -NB node ===
827
828
829 First you need to configure the certificate to the -NB node. Follow the instructions in this **[[link>>https://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H4.1.2Configurecertificate]]** to configure the certificate.
830
831 Screenshot of successful certificate configuration:
832
833 * Configuring the CA Certificate
834
835 [[image:image-20241126192009-19.png||height="431" width="697"]][[image:image-20241126192130-21.png||height="426" width="694"]]
836
837 * Configure client certificate
838
839 [[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]]
840
841 * Configure client private key
842
843 [[image:image-20241126192415-24.png||height="435" width="737"]]
844
845
846 When the certificate is configured, burn the boot program, burn the working firmware, and then restart the device.
847
848 Then configure the -NB node to connect to the ThingsEye platform:
849
850 (% style="color:blue" %)**AT Commands**
851
852 * (% style="color:#037691" %)**AT+PRO=3,5  **(%%)** **~/~/ Use MQTT Connection & Json Payload
853 * (% style="color:#037691" %)**AT+SERVADDR=lns1.thingseye.io,8883**
854 * (% style="color:#037691" %)**AT+SUBTOPIC=8899     **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye
855 * (% style="color:#037691" %)**AT+PUBTOPIC=8899     **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye
856 * (% style="color:#037691" %)**AT+CLIENT=NULL**
857 * (% style="color:#037691" %)**AT+UNAME=NULL**
858 * (% style="color:#037691" %)**AT+PWD=NULL**
859 * (% style="color:#037691" %)**AT+TLSMOD=1,0**
860
861 Test Uplink by click the button for 1~~3 seconds, the MQTT integration in ThingsEye allows you to view the data upstream from the device:
862
863 [[image:image-20241126193458-26.png||height="375" width="1012"]]
864
865 [[image:image-20241126193609-27.png||height="424" width="1014"]]
866
867
868 Go to (% style="color:blue" %)**"Device" **(%%) -> (% style="color:blue" %)** "Search Device"**(%%), enter the (% style="color:blue" %)** IMEI**(%%) of the device to find the device.
869
870 [[image:image-20241126194018-28.png||height="318" width="1076"]]
871
872 You can view the data that has just been uplink on the device:
873
874 [[image:image-20241126194123-29.png||height="486" width="1073"]]
875
876
877 = 4. MQTT/UDP/TCP downlink =
878
879 == 4.1 MQTT (via MQTT.fx) ==
880
881
882 Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
883
884 **1.** Configure node MQTT connection (via MQTT.fx):
885
886 (% style="color:blue" %)**AT command:**
887
888 * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
889
890 * (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
891
892 * (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
893
894 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
895
896 * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
897
898 * (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
899
900 (% 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.**
901
902 [[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
903
904
905 **2. **When the node uplink packets, we can observe the data in MQTT.fx.
906
907 [[image:image-20240418144337-1.png||height="709" width="802"]]
908
909 **3. **The downlink command can be successfully sent only when the downlink port is open.
910
911 The downlink port is opened for about 3 seconds after uplink packets are sent.
912
913 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.
914
915 [[image:image-20240418150435-3.png||height="582" width="659"]]
916
917 [[image:image-20240418150932-4.png||height="492" width="1061"]]
918
919 (% 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.**
920
921
922 = 5. FAQ =
923
924 == 5.1 What is the usage of Multi Sampling and One Uplink? ==
925
926
927 The NB series has the feature for Multi Sampling and one uplink. See one of them
928
929 [[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]]
930
931 User can use this feature for below purpose:
932
933 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.
934 1. Give more sampling data points.
935 1. Increase reliable in transmission. For example. If user set
936 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)
937 1*. **AT+NOUD=24**  ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
938 1*. **AT+TDC=7200**  ~/~/  Uplink every 2 hours.
939 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.
940
941
942 == 5.2 Why the uplink JSON format is not standard? ==
943
944
945 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.
946
947 The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
948
949 [[image:image-20240229233154-1.png]]
950
951
952 == 5.3 What is the data consumption for different transfer mode？ ==
953
954
955 For the data consumption of NB-IoT End node in different transfer mode, reference link:
956
957 [[https:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20~~-~~-%20NBCB/>>https://wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20--%20NBCB/]]
958
959
960 = 6. Trouble Shooting: =
961
962 == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
963
964
965 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.
966
967 If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
968
969 [[image:image-20240207002003-1.png]]
970
971
972 If fail to attach network, it will shows signal 99. as below:
973
974 [[image:image-20240207002129-2.png]]
975
976
977 (% class="lead" %)
978 When see this issue, below are the checklist:
979
980 * 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.
981 * 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]].
982 * 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]].
983 * Check if the device is attached to Carrier network but reject. (need to check with operator).
984 * Check if the antenna is connected firmly.
985
986 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.
987
988
989 == 6.2 Issue: "NBIOT did not respond" ==
990
991
992 (% class="box errormessage" %)
993 (((
994 11:24:22.397 [44596]NBIOT did not respond.
995 11:24:24.315 [46530]NBIOT did not respond.
996 11:24:26.256 [48464]NBIOT did not respond.
997 11:24:28.196 [50398]NBIOT did not respond.
998 11:24:30.115 [52332]NBIOT did not respond.
999 11:24:32.127 [54266]NBIOT did not respond.
1000 11:24:32.127 [54299]Restart the module...
1001 11:24:39.181 [61332]No response when shutting down
1002 )))
1003
1004 This issue might due to initiate issue for NB-IoT module. In this case, please try:
1005
1006 1) Open Enclosure
1007
1008 2) Power off device by pull out the power on Jumper
1009
1010 3) Power on device by connect back the power jumper.
1011
1012 4) push reset button.
1013
1014 [[image:image-20240208001740-1.png]]
1015
1016
1017 == 6.3 Issue: "Failed to readI MSI number" ==
1018
1019
1020 (% class="box errormessage" %)
1021 (((
1022 [18170]Failed to read IMSI:1umber.
1023 [20109]Failed to read IMSI numoer.
1024 [22048]Failed to read IMSI number.
1025 [29842lRestart the module...
1026 )))
1027
1028 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"]].
1029
1030
1031 == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
1032
1033
1034 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.
1035
1036 [[image:image-20240226111928-1.png]]
1037
1038
1039 == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
1040
1041
1042 (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1043 === UDP: ===
1044
1045
1046 (% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1047 Its downlink command is the same as the AT command, but brackets are required.
1048 Example:
1049
1050 {AT+TDC=300}
1051
1052
1053 (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1054 === MQTT: ===
1055
1056
1057 Json：
1058
1059 The Json format in MQTT mode needs to be configured with all commands.
1060 If you have configurations that need to be changed, please change them in the template below.
1061 Template:
1062
1063 {
1064 "AT+SERVADDR":"119.91.62.30,1882",
1065 "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
1066 "AT+UNAME":"usenamedragino",
1067 "AT+PWD":"passworddragino",
1068 "AT+PUBTOPIC":"123",
1069 "AT+SUBTOPIC":"321",
1070 "AT+TDC":"7200",
1071 "AT+INTMOD":"0",
1072 "AT+APN":"NULL",
1073 "AT+5VT":"0",
1074 "AT+PRO":"3,5",
1075 "AT+TR":"900",
1076 "AT+NOUD":"0",
1077 "AT+CSQTIME":"5",
1078 "AT+DNSTIMER":"0",
1079 "AT+TLSMOD":"0,0",
1080 "AT+MQOS":"0",
1081 "AT+TEMPALARM1":"0",
1082 "AT+TEMPALARM2":"10",
1083 "AT+TEMPALARM3":"0"
1084 }
1085
1086 Hex：
1087
1088 MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1089
1090 The supported commands are consistent with LoRaWAN's hex commands.
1091 Please refer to the following link to obtain the hex format:
1092
1093 [[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/]]
1094
1095
1096 == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
1097
1098
1099 * **AT Command: AT** **+GETLOG**
1100
1101 This command can be used to query upstream logs of data packets.
1102
1103 [[image:image-20240701114700-1.png]]
1104
1105
1106 == 6.7 How to find the AT Command Password if lost? ==
1107
1108
1109 === Why can't the password access AT command after upgrade(-NB)? ===
1110
1111
1112 Because the new version of -NB firmware has updated the factory reset function, users can choose to restore all parameters to factory Settings, or keep the password to restore the rest of the parameters to factory Settings.
1113
1114 This update changes the password address of the firmware, so the password will be invalid after the customer upgrades from the old version of firmware (without FDR1 function) to the new version of firmware (with FDR1 function).
1115
1116 Two different restore factory Settings configurations.
1117
1118 (% style="color:blue" %)**AT command:**
1119
1120 * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
1121 * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values except for passwords.(new)
1122
1123
1124 === Version Confirmation ===
1125
1126 We are now dividing the **old firmware**(without FDR1 function) with the **new firmware**(with FDR1 function) by whether it contains FDR1 functionality. Please refer to the table:
1127
1128 (% border="1" style="background-color:#f2f2f2; width:510px" %)
1129 |(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1130 **Firmware version**
1131
1132 **(without FDR1 function)**
1133 )))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1134 **Firmware version**
1135
1136 **(with FDR1 function)**
1137 )))
1138 |(% style="width:210px" %)(((
1139 CPL03-NB, S31-NB, SN50V3-NB, TS01-NB, D20-NB, DS03A-NB, DDS04-NB, DDS45-NB, DDS20-NB, DDS75-NB, LDS12-NB, LDS40-NB, LMS01-NB, MDS120-NB,  MDS200-NB, SE01-NB, SPH01-NB;
1140 )))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1141 |(% style="width:210px" %)(((
1142 WL03A-NB, SDI-12-NB;
1143 )))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1144 After V1.0.8 (including V1.0.2)
1145 )))
1146 |(% style="width:210px" %)(((
1147 SW3L-NB, PS-NB;
1148 )))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1149 After V1.0.5 (including V1.0.5)
1150 )))
1151 |(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
1152
1153
1154 === UART connection and firmware update methods ===
1155
1156
1157 Users can query passwords only using the UART interface via the STM32CubeProgrammer.
1158
1159 See **[[UART Connection>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]]**.
1160
1161 update firmware through UART TTL interface :** [[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
1162
1163
1164 === query the password via STM32CubeProgrammer ===
1165
1166
1167 Users can use the password address to query the password through STM32CubeProgrammer.
1168
1169 * The password address for old firmware(without FDR1 function) : **0x08019000**
1170 * The password address for new firmware(with FDR1 function) : **0x08025D00**
1171
1172 (% style="color:red" %)**Notice: The password can only be queried after the firmware is run once.**
1173
1174
1175 **Procedure for querying the password(old firmware):**
1176
1177 * After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the firmware once**.
1178 * Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1179 * Click "Device memory", enter **0x08019000** in "Address", and click "Read"
1180 * Find the 0x08019000 address field and then read the current password as shown in the screenshot below.
1181
1182 [[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827171901-3.png?width=912&height=528&rev=1.1||alt="image-20240827171901-3.png"]]
1183
1184
1185 **Procedure for querying the password(new firmware):**
1186
1187 Refer to [[the old and new firmware division>>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/#HVersionConfirmation]] above, and run the firmware first after updating the firmware.
1188
1189 * After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the new firmware once**.
1190 * Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1191 * Click "Device memory", enter **0x08025D00** in "Address", and click "Read"
1192 * Find the 0x08025D00 address field and then read the current password as shown in the screenshot below.
1193
1194 [[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827180414-1.png?width=910&height=527&rev=1.1||alt="image-20240827180414-1.png"]]
1195
1196
1197
1198 === Special case ===
1199
1200
1201 If the user has never changed the password manually, the user cannot find the valid password through the above two password addresses. In this case, the valid password is still the original password on the node box label (**AT+PIN**).
1202
1203 Invalid query screenshot example:
1204
1205
1206 [[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827181447-4.png?width=889&height=519&rev=1.1||alt="image-20240827181447-4.png"]]
1207
1208 [[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827181431-3.png?width=892&height=515&rev=1.1||alt="image-20240827181431-3.png"]]
1209
1210
1211
1212

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0