Skip to Content
Version 235.1 by Kilight Cao on 2025/07/23 16:25
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 ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
172
173
174 [[image:image-20230802112413-9.png]]
175
176 [[image:image-20230802112413-10.png]]
177
178
179 (% style="color:blue" %)**In MQTT.fx, we can publish below info:**
180
181 * (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
182
183 * (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH
184
185 Where 63 and 67 are the value to be published to field1 & field2.
186
187
188 (% style="color:blue" %)**Result: **
189
190 [[image:image-20230802112413-11.png||height="539" width="901"]]
191
192
193 === 3.3.3 Configure NB-IoT Sensor for connection ===
194
195 ==== 3.3.3.1 AT Commands: ====
196
197
198 In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
199
200 * (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
201
202 * (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
203
204 * (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
205
206 * (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>**
207
208 * (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
209
210 * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
211
212 ==== 3.3.3.2 Uplink Examples ====
213
214
215 [[image:image-20230816201942-1.png]]
216
217 For SE01-NB
218
219 For DDS20-NB
220
221 For DDS45-NB
222
223 For DDS75-NB
224
225 For NMDS120-NB
226
227 For SPH01-NB
228
229 For NLM01-NB
230
231 For NMDS200-NB
232
233 For CPN01-NB
234
235 For DS03A-NB
236
237 For SN50V3-NB
238
239
240 ==== 3.3.3.3 Map fields to sensor value ====
241
242
243 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.
244
245
246 [[image:image-20230802112413-12.png||height="504" width="1011"]]
247
248 [[image:image-20230802112413-13.png||height="331" width="978"]]
249
250
251 Below is the NB-IoT Product Table show the mapping.
252
253 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
254 |(% 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
255 |(% 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" %)
256 |(% 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" %)
257 |(% 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" %)
258 |(% 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" %)
259 |(% 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" %)
260 |(% 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" %)
261 |(% 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" %)
262 |(% 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" %)
263 |(% 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" %)
264 |(% 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" %)
265 |(% 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
266 |(% 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" %)
267 |(% 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" %)
268 |(% 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" %)
269 |(% 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" %)
270 |(% 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" %)
271 |(% 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" %)
272
273 == 3.4 [[Datacake>>https://datacake.co/]] ==
274
275
276 (% class="wikigeneratedid" %)
277 Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
278
279
280 (% class="wikigeneratedid" %)
281 As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
282
283 * (% 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.
284
285 * (% 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.
286
287 === 3.4.1 For device Already has template ===
288
289 ==== 3.4.1.1 Create Device ====
290
291
292 (% style="color:blue" %)**Add Device**(%%) in DataCake.
293
294 [[image:image-20230808162301-1.png||height="453" width="952"]]
295
296
297 [[image:image-20230808162342-2.png||height="541" width="952"]]
298
299
300 (% style="color:blue" %)**Choose the correct model**(%%) from template.
301
302 [[image:image-20230808162421-3.png]]
303
304
305 (% 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.
306
307 [[image:image-20230808163612-7.png||height="549" width="952"]]
308
309 [[image:image-20230808163035-5.png]]
310
311 [[image:image-20230808163049-6.png||height="544" width="926"]]
312
313
314 === 3.4.2 For Device already registered in DataCake before shipped ===
315
316 ==== 3.4.2.1 Scan QR Code to get the device info ====
317
318
319 Users can use their phones or computers to scan QR codes to obtain device data information.
320
321 [[image:image-20230808170051-8.png||height="255" width="259"]]
322
323 [[image:image-20230808170548-9.png]]
324
325
326 ==== 3.4.2.2 Claim Device to User Account ====
327
328
329 By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
330
331
332 === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
333
334
335 **Step1: Add a device**
336
337 [[image:image-20240129170024-1.png||height="330" width="900"]]
338
339
340 **Step2: Choose your device type,please select dragino NB-IOT device**
341
342 [[image:image-20240129170216-2.png||height="534" width="643"]]
343
344
345 **Step3: Choose to create a new device**
346
347 [[image:image-20240129170539-3.png||height="459" width="646"]]
348
349
350 **Step4: Fill in the device ID of your NB device**
351
352 [[image:image-20240202111546-1.png||height="378" width="651"]]
353
354
355 **Step5: Please select your device plan according to your needs and complete the creation of the device**
356
357 [[image:image-20240129171236-6.png||height="450" width="648"]]
358
359
360 **Step6: Please add the decoder at the payload decoder of the device configuration.**
361
362 **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]]
363
364 **Due to version update, please use the following decoder for the new version firmware:**
365 [[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]]
366
367 [[image:image-20240129172056-7.png||height="457" width="816"]]
368
369 [[image:image-20240129173116-9.png||height="499" width="814"]]
370
371
372 **Step7: Add the output of the decoder as a field**
373
374 [[image:image-20240129173541-10.png||height="592" width="968"]]
375
376
377 **Step8: Customize the dashboard and use fields as parameters of the dashboard**
378
379 [[image:image-20240129174518-11.png||height="147" width="1042"]]
380
381 [[image:image-20240129174657-12.png||height="538" width="916"]]
382
383 [[image:image-20240129174840-13.png||height="536" width="750"]]
384
385
386 === 3.4.4 For device have not configured to connect to DataCake ===
387
388
389 (% class="lead" %)
390 Use AT command for connecting to DataCake
391
392 (% style="color:blue" %)**AT+PRO=2,0**
393
394 (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
395
396
397 == 3.5 Telemetry2U ==
398
399
400 === Configuring the Dragino NB Sensor Settings ===
401
402
403 (% style="color:blue" %)**AT+SERVADDR=telemetry2u.com,4483**(%%) – Sets the server address and port for sending data to the Telemetry2U IoT platform.
404
405 (% style="color:blue" %)**AT+APN=simbase**(%%) – Sets the APN required for LTE-M connectivity using a Simbase global SIM card.
406
407 (% style="color:blue" %)**ATZ**(%%) – Reboots the device to apply the changes. It won’t transmit to Telemetry2U until added and configured on the platform.
408
409 (% style="color:blue" %)**AT+CFG**(%%) – Displays the current configuration. Take note of the 8-byte (HEX) **DEUI**, which you’ll need in the next setup step.
410
411 And that’s it! These simple steps will get your device up and running on our Telemetry2U servers in no time.
412
413
414 **Step 1: Log in Telemetry2U**
415
416
417 Users can register a Telemetry2U account for their first use
418
419 **[[https:~~/~~/telemetry2u.com/Identity/Account/Register>>https://telemetry2u.com/Identity/Account/Register]]**
420
421
422 **Step 2: Add the device**
423
424 [[image:1753258256594-216.png||height="686" width="1382"]]
425
426
427 **1. Select Network provide:**Users need to select Telemetry2U NB-IoT over UDP in order to connect to the platform
428
429 **2. Select device type:**Select the template you need to use
430
431 **3. Fill in Description:**Fill in the unique description
432
433 4. **Fill in IMEI:**The IMEI corresponds to the IME of the device
434
435 After completion, click "**Greate**"
436
437 [[image:1753258480811-335.png||height="789" width="1380"]]
438
439
440 **Step 3: Check the data**
441
442
443 [[image:1753258821265-310.png||height="681" width="1365"]]
444
445
446
447 For more information, please refer to the user manual on the Telemetry2U official website:
448
449 **[[https:~~/~~/telemetry2u.com/Documentation/dragino-lte-m-nb-iot-sensors-iot-platform-integration>>https://telemetry2u.com/Documentation/dragino-lte-m-nb-iot-sensors-iot-platform-integration]]**
450
451
452 == 3.5 Node-Red (via MQTT) ==
453
454 === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
455
456
457 Take S31-NB UDP protocol as an example.
458
459 Dragino provides input flow examples for the sensors.
460
461 User can download the required JSON file through Dragino Node-RED input flow template.
462
463 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]]
464
465 We can directly import the template.
466
467 The templates for S31-NB and NB95S31B are the same.
468
469
470 [[image:image-20230809173127-4.png]]
471
472
473 Please select the NB95S31B template.
474
475 [[image:image-20230809173310-5.png||height="558" width="926"]]
476
477 [[image:image-20230809173438-6.png]]
478
479 [[image:image-20230809173800-7.png]]
480
481
482 Successfully imported template.
483
484 [[image:image-20230809173835-8.png||height="515" width="860"]]
485
486
487 Users can set UDP port.
488
489 [[image:image-20230809174053-9.png]]
490
491
492 === 3.5.2 Simulate Connection ===
493
494
495 We have completed the configuration of UDP. We can try sending packets to node red.
496
497 [[image:image-20230810083934-1.png]]
498
499 [[image:image-20230810084048-2.png||height="535" width="1052"]]
500
501
502 === 3.5.3 Configure NB-IoT Sensors ===
503
504
505 * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
506 * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
507 * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
508 * (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
509 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
510 * (% style="color:#037691" %)**AT+PWD=“Your device token”**
511
512 == 3.6 ThingsBoard.Cloud (via MQTT) ==
513
514 === 3.6.1 Configure ThingsBoard ===
515
516 ==== 3.6.1.1 Create Device ====
517
518
519 Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
520
521 [[image:image-20230802112413-32.png||height="583" width="1066"]]
522
523
524 ==== 3.6.1.2 Create Uplink & Downlink Converter ====
525
526
527 (% style="color:blue" %)**Uplink Converter**
528
529 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.
530
531 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.
532
533 [[image:image-20230802112413-33.png||height="597" width="1061"]]
534
535
536 (% style="color:blue" %)**Downlink Converter**
537
538 The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
539
540 [[image:image-20230802112413-34.png||height="598" width="1063"]]
541
542 (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
543
544
545 ==== 3.6.1.3 MQTT Integration Setup ====
546
547
548 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**;
549
550 [[image:image-20230802112413-35.png||height="597" width="1062"]]
551
552
553 * The next steps is to add the recently created uplink and downlink converters;
554
555 [[image:image-20230802112413-36.png||height="598" width="1062"]]
556
557 [[image:image-20230802112413-37.png||height="598" width="1064"]]
558
559
560 (% style="color:blue" %)**Add a topic filter:**
561
562 Consistent with the theme of the node setting.
563
564 You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
565
566 [[image:image-20230802112413-38.png||height="598" width="1064"]]
567
568
569 === 3.6.2 Simulate with MQTT.fx ===
570
571 [[image:image-20230802112413-39.png]]
572
573 [[image:image-20230802112413-40.png||height="525" width="980"]]
574
575
576 === 3.6.3 Configure NB-IoT Sensor ===
577
578
579 (% style="color:blue" %)**AT Commands**
580
581 * (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
582
583 * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
584
585 * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
586
587 * (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
588
589 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
590
591 * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
592
593 Test Uplink by click the button for 1 second
594
595 [[image:image-20230802112413-41.png||height="496" width="828"]]
596
597 [[image:image-20230802112413-42.png]]
598
599 [[image:image-20230802112413-43.png||height="407" width="825"]]
600
601
602 == 3.7 ThingsBoard.Cloud (via COAP) ==
603
604 === 3.7.1 Configure ThingsBoard ===
605
606 ==== 3.7.1.1 Create Uplink & Downlink Converter ====
607
608
609 (% style="color:blue" %)**Uplink Converter**
610
611 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.
612
613 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.
614
615 [[image:image-20240729141300-1.png||height="552" width="1115"]]
616
617
618 (% style="color:blue" %)**Downlink Converter**
619
620 The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
621
622 [[image:image-20240729142505-3.png||height="507" width="1023"]]
623
624
625 ==== 3.7.1.2 COAP Integration Setup ====
626
627
628 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" %);
629
630 [[image:image-20240729144058-4.png||height="506" width="1021"]]
631
632
633 The next steps is to add the recently created uplink converters;
634
635 [[image:image-20240729150142-5.png||height="507" width="1023"]]
636
637
638 ==== 3.7.1.3 Add COAP Integration ====
639
640
641 (% class="wikigeneratedid" id="H" %)
642 [[image:image-20240729161543-9.png||height="500" width="1009"]]
643
644
645 === 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
646
647 ==== 3.7.2.1 Instruction Description ====
648
649
650 * AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
651 * AT+SERVADDR=COAP Server Address,5683
652
653 Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
654
655 [[image:image-20240729172305-12.png||height="361" width="624"]]
656
657 Note:The port for the COAP protocol has been fixed to 5683
658
659
660 * AT+URI1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform",
661
662 -NB/NS products use the (% style="color:red" %)**BC660K**(%%) module, only need to configure (% style="color:red" %)**only one URL**(%%) command.
663
664 e.g.
665
666 * AT+URI1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
667
668 [[image:image-20240729172415-13.png||height="401" width="694"]]
669
670
671 == 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
672
673 === 3.8.1 Create device & Get Credentials ===
674
675
676 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.
677
678 [[image:image-20230802112413-44.png]]
679
680 [[image:image-20230802112413-45.png]]
681
682
683 Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
684
685 [[image:image-20230802112413-46.png]]
686
687
688 The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
689
690 (% style="color:blue" %)**On the Connection Profile window, set the following information:**
691
692 * (% style="color:#037691" %)**Profile Name: “Any name”**
693
694 * (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
695
696 * (% style="color:#037691" %)**Broker Port: 8883**
697
698 * (% style="color:#037691" %)**Client ID: “Any value”**
699
700 (% style="color:blue" %)**On the section User credentials, set the following information:**
701
702 * (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
703
704 * (% style="color:#037691" %)**Password: “Your device token”**
705
706 * (% style="color:#037691" %)**PUBTOPIC: “Any value”**
707
708 * (% style="color:#037691" %)**SUBTOPIC: “Any value”**
709
710 (% style="color:blue" %)**AT command:**
711
712 * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
713
714 * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
715
716 * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
717
718 * (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
719
720 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
721
722 * (% style="color:#037691" %)**AT+PWD=“Your device token”**
723
724 === 3.8.2 Simulate with MQTT.fx ===
725
726
727 [[image:image-20230802112413-52.png]]
728
729
730 [[image:image-20230808105300-2.png||height="553" width="1026"]]
731
732
733 Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
734
735 [[image:image-20230808105217-1.png||height="556" width="1031"]]
736
737 [[image:image-20230808105329-3.png]]
738
739
740 === 3.8.3 tago data ===
741
742
743 [[image:image-20230802112413-50.png||height="242" width="1037"]]
744
745 [[image:image-20230802112413-51.png||height="184" width="696"]]
746
747
748 == 3.9 TCP Connection ==
749
750
751 (% style="color:blue" %)**AT command:**
752
753 * (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
754
755 * (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
756
757 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
758
759 (% style="color:blue" %)**Sensor Console Output when Uplink:**
760
761 [[image:image-20230807233631-1.png]]
762
763
764 (% style="color:blue" %)**See result in TCP Server:**
765
766 [[image:image-20230807233631-2.png]]
767
768
769 == 3.10 AWS Connection ==
770
771
772 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]]
773
774
775 == 3.11 ThingsEye (via MQTT) ==
776
777 === 3.11.1 Configure ThingsEye ===
778
779 ==== 3.11.1.1 Create MQTT integration ====
780
781
782 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**;
783
784 [[image:image-20241126175509-1.png||height="518" width="1081"]]
785
786
787 Next, directly select to create a new Uplink data converter and downlink data converter.
788
789 [[image:image-20241126180135-2.png||height="535" width="1092"]]
790
791 [[image:image-20241126180223-3.png||height="518" width="1093"]]
792
793
794 (% style="color:blue" %)**Add a topic filter:**
795
796 Consistent with the theme of the node setting.
797
798 (% 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.**
799
800 You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
801
802 [[image:image-20241126181024-4.png||height="521" width="1081"]]
803
804
805 ==== 3.11.1.2 Add credentials to the MQTT integration ====
806
807
808 Click on the MQTT integration you just created.
809
810 [[image:image-20241126181837-5.png||height="365" width="1079"]]
811
812
813 Click the edit icon in the upper right corner to enter the edit mode.
814
815 [[image:image-20241126184523-13.png||height="330" width="1075"]]
816
817
818 (% style="color:blue" %)**Add credential files.**
819
820 Click this [[link>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]] to download the certificates.
821
822 [[image:image-20241126183032-8.png||height="757" width="976"]]
823
824 When the addition is complete, save the Settings.
825
826 [[image:image-20241126184303-12.png||height="284" width="975"]]
827
828 [[image:image-20241126184211-11.png||height="161" width="977"]]
829
830
831 ==== 3.11.1.3 Setup uplink and downlink converters ====
832
833
834 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]].
835
836 * (% style="color:blue" %)**Uplink Converter**
837
838 The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume.
839
840 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.
841
842 [[image:image-20241126184906-14.png||height="424" width="1100"]]
843
844 Enter edit mode and apply **MQTT uplink JS code** to this uplink converter.
845
846 [[image:image-20241126190131-15.png||height="542" width="1103"]]
847
848
849 * (% style="color:blue" %)**Downlink Converter**
850
851 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.
852
853 [[image:image-20241126190251-16.png||height="372" width="1113"]]
854
855 Enter edit mode and apply **MQTT downlink JS code** to this downlink converter.
856
857 [[image:image-20241126190737-17.png||height="527" width="1114"]]
858
859
860 === 3.11.2 Simulate with MQTT.fx ===
861
862
863 [[image:image-20241126191118-18.png||height="605" width="835"]]
864
865 [[image:image-20241126193252-25.png||height="663" width="803"]]
866
867
868 === 3.11.3 Configure -NB node ===
869
870
871 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.
872
873 Screenshot of successful certificate configuration:
874
875 * Configuring the CA Certificate
876
877 [[image:image-20241126192009-19.png||height="431" width="697"]]
878
879 [[image:image-20241126192130-21.png||height="426" width="694"]]
880
881 * Configure client certificate
882
883 [[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]]
884
885 * Configure client private key
886
887 [[image:image-20241126192415-24.png||height="435" width="737"]]
888
889
890 When the certificate is configured, burn the boot program, burn the working firmware, and then restart the device.
891
892 Then configure the -NB node to connect to the ThingsEye platform:
893
894 (% style="color:blue" %)**AT Commands**
895
896 * (% style="color:#037691" %)**AT+PRO=3,5  **(%%)** **~/~/ Use MQTT Connection & Json Payload
897 * (% style="color:#037691" %)**AT+SERVADDR=lns1.thingseye.io,8883**
898 * (% style="color:#037691" %)**AT+SUBTOPIC=8899     **(%%)~/~/ Consistent with the Topic of MQTT integration created by ThingsEye
899 * (% style="color:#037691" %)**AT+PUBTOPIC=8899     **(%%)~/~/ Consistent with the Topic of MQTT integration created by ThingsEye
900 * (% style="color:#037691" %)**AT+CLIENT=NULL**
901 * (% style="color:#037691" %)**AT+UNAME=NULL**
902 * (% style="color:#037691" %)**AT+PWD=NULL**
903 * (% style="color:#037691" %)**AT+TLSMOD=1,2**
904
905 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:
906
907 [[image:image-20241126193458-26.png||height="375" width="1012"]]
908
909 [[image:image-20241126193609-27.png||height="424" width="1014"]]
910
911
912 Go to (% style="color:blue" %)**"Device" **(%%) -> (% style="color:blue" %)** "Search Device"**(%%), enter the (% style="color:blue" %)** IMEI**(%%) of the device to find the device.
913
914 [[image:image-20241126194018-28.png||height="318" width="1076"]]
915
916 You can view the data that has just been uplink on the device:
917
918 [[image:image-20241126194123-29.png||height="486" width="1073"]]
919
920
921 = 4. MQTT/UDP/TCP downlink =
922
923 == 4.1 MQTT (via MQTT.fx) ==
924
925
926 Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
927
928 **1.** Configure node MQTT connection (via MQTT.fx):
929
930 (% style="color:blue" %)**AT command:**
931
932 * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
933
934 * (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
935
936 * (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
937
938 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
939
940 * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
941
942 * (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
943
944 (% 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.**
945
946 [[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
947
948
949 **2. **When the node uplink packets, we can observe the data in MQTT.fx.
950
951 [[image:image-20240418144337-1.png||height="709" width="802"]]
952
953 **3. **The downlink command can be successfully sent only when the downlink port is open.
954
955 The downlink port is opened for about 3 seconds after uplink packets are sent.
956
957 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.
958
959 [[image:image-20240418150435-3.png||height="582" width="659"]]
960
961 [[image:image-20240418150932-4.png||height="492" width="1061"]]
962
963 (% 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.**
964
965
966 = 5. FAQ =
967
968 == 5.1 What is the usage of Multi Sampling and One Uplink? ==
969
970
971 The NB series has the feature for Multi Sampling and one uplink. See one of them
972
973 [[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]]
974
975 User can use this feature for below purpose:
976
977 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.
978 1. Give more sampling data points.
979 1. Increase reliable in transmission. For example. If user set
980 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)
981 1*. **AT+NOUD=24**  ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
982 1*. **AT+TDC=7200**  ~/~/  Uplink every 2 hours.
983 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.
984
985 == 5.2 Why the uplink JSON format is not standard? ==
986
987
988 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.
989
990 The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
991
992 [[image:image-20240229233154-1.png]]
993
994
995 == 5.3 What is the data consumption for different transfer mode？ ==
996
997
998 For the data consumption of NB-IoT End node in different transfer mode, reference link:
999
1000 [[https:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20~~-~~-%20NBCB/>>https://wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20--%20NBCB/]]
1001
1002
1003 = 6. Trouble Shooting: =
1004
1005 == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
1006
1007
1008 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.
1009
1010 If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
1011
1012 [[image:image-20240207002003-1.png]]
1013
1014
1015 If fail to attach network, it will shows signal 99. as below:
1016
1017 [[image:image-20240207002129-2.png]]
1018
1019
1020 (% class="lead" %)
1021 When see this issue, below are the checklist:
1022
1023 * 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.
1024 * 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]].
1025 * 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]].
1026 * Check if the device is attached to Carrier network but reject. (need to check with operator).
1027 * Check if the antenna is connected firmly.
1028
1029 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.
1030
1031
1032 == 6.2 Issue: "NBIOT did not respond" ==
1033
1034
1035 (% class="box errormessage" %)
1036 (((
1037 11:24:22.397 [44596]NBIOT did not respond.
1038 11:24:24.315 [46530]NBIOT did not respond.
1039 11:24:26.256 [48464]NBIOT did not respond.
1040 11:24:28.196 [50398]NBIOT did not respond.
1041 11:24:30.115 [52332]NBIOT did not respond.
1042 11:24:32.127 [54266]NBIOT did not respond.
1043 11:24:32.127 [54299]Restart the module...
1044 11:24:39.181 [61332]No response when shutting down
1045 )))
1046
1047 This issue might due to initiate issue for NB-IoT module. In this case, please try:
1048
1049 1) Open Enclosure
1050
1051 2) Power off device by pull out the power on Jumper
1052
1053 3) Power on device by connect back the power jumper.
1054
1055 4) push reset button.
1056
1057 [[image:image-20240208001740-1.png]]
1058
1059
1060 == 6.3 Issue: "Failed to readI MSI number" ==
1061
1062
1063 (% class="box errormessage" %)
1064 (((
1065 [18170]Failed to read IMSI:1umber.
1066 [20109]Failed to read IMSI numoer.
1067 [22048]Failed to read IMSI number.
1068 [29842lRestart the module...
1069 )))
1070
1071 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"]].
1072
1073
1074 == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
1075
1076
1077 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.
1078
1079 [[image:image-20240226111928-1.png]]
1080
1081
1082 == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 (%%)What is the Downlink Command Format for NB Devices? ==
1083
1084
1085 Firstly, it is recommended that users upgrade the firmware of the -NB node to the latest version, as the processing method for downlink commands varies depending on the firmware version. Below, we will introduce the latest downlink command format.
1086
1087 (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1088 === **UDP Protocol:** ===
1089
1090 Only supports valid **HEX-format downlink commands** corresponding to AT command.
1091
1092 Take the AT+TDC command of S31-NB as an example, that is, only the valid HEX format downstream command corresponding to the AT+TDC command can be used:
1093 Downward format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1094
1095 [[image:1750035991532-434.png||height="237" width="495"]]
1096
1097
1098 (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1099 === **MQTT Protocol:** ===
1100
1101 ==== **1. HEX-format** ====
1102
1103 Supports **HEX-format** downlink commands (corresponding to AT commands).
1104
1105 //Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
1106
1107 Downlink command:  (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1108
1109 [[image:1750035004731-376.png||height="276" width="557"]]
1110
1111
1112 ==== **2. JSON-format ** ====
1113
1114 ===== **2. 1 JSON format template.** =====
1115
1116 All -NB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.**
1117
1118 We can use templates to configure multiple commands AT once. Users only need to modify the parameters of the required AT commands in the correct template for each device.
1119 Template.
1120
1121 Take the template of D2x-NB as an example:
1122
1123 {
1124 "AT+SERVADDR":"119.91.62.30,1882",
1125 "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
1126 "AT+UNAME":"usenamedragino",
1127 "AT+PWD":"passworddragino",
1128 "AT+PUBTOPIC":"123",
1129 "AT+SUBTOPIC":"321",
1130 "AT+TDC":"7200",
1131 "AT+INTMOD":"0",
1132 "AT+APN":"NULL",
1133 "AT+5VT":"0",
1134 "AT+PRO":"3,5",
1135 "AT+TR":"900",
1136 "AT+NOUD":"0",
1137 "AT+CSQTIME":"5",
1138 "AT+DNSTIMER":"0",
1139 "AT+TLSMOD":"0,0",
1140 "AT+MQOS":"0",
1141 "AT+TEMPALARM1":"0",
1142 "AT+TEMPALARM2":"10",
1143 "AT+TEMPALARM3":"0"
1144 }
1145
1146 Explanations of two special commands in the template: AT+TR (set the detection interval: 0 ~~ 255 minutes) and AT+NOUD (set the number of groups) correspond to parameters in AT+CLOCKLOG.
1147
1148 [[image:1751538862245-924.png]]
1149
1150
1151 **Instructions for Using the Template:**
1152
1153 1. Modify the parameters for each AT command in the template as needed.
1154 1. Send the entire template in one downlink command.
1155
1156 (% style="color:red" %)**Note:**
1157
1158 * The template may vary depending on the device model.
1159 * **Currently, each specific template is being updated and tested**. If you need a template for your specific device, please contact **Dragino Technical Support** at [[support@dragino.com>>url:https://mailto:support@dragino.com/]] to request the latest downlink template.
1160
1161
1162
1163 ===== **2.2 Support sending json format commands separately** =====
1164
1165 Some models of nodes support sending json format commands separately：(% style="color:blue" %)**RS485-NB, LDS25-NB, CS01-NB, SDI-12-NB, SW3L-NB, WL03A-NB, PS-NB, LTC2-NB.**
1166
1167 //Example~:// For the PS-NB's uplink interval modification (AT+TDC=900):
1168
1169 Downlink command:  (% style="color:blue" %)**{AT+TDC=900}**(%%)**       **~/~/ The correct format is (% style="color:blue" %)**{AT Command}**(%%). No extra characters other than valid AT commands can be added within {}.
1170
1171 (% style="color:red" %)**Note:**
1172
1173 (% style="color:red" %)**1. Only when the correct and valid download command is used and the format is correct can the device be configured through the download command. Invalid download content cannot be processed by the device and will be automatically restarted.**
1174
1175 (% style="color:red" %)**2. Devices designed with downlink commands can utilize different downlink formats (e.g., JSON or HEX) for configuration. However, regardless of the format, the functionality is strictly limited to the downlink command specifications described in the user manual's AT command explanation.**
1176
1177 (% style="color:red" %)**For example, the HEX-format downlink command corresponding to AT+TDC can only be used to configure TDC and cannot be used for queries. There is no HEX-format downlink command equivalent to AT+TDC=? , so querying TDC via downlink is not supported.**
1178
1179
1180 == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1181
1182
1183 If user is not able to solve the connection issue, user can use below method and get the device log and send to Dragino (Support@dragino.cc) for further analyze.
1184
1185
1186 (% class="lead" %)
1187 Step1: Use Mobile Phone to connect device
1188
1189 See this link: **[[how to connect via Mobile Phone:>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1UseDraginoDeviceTooltoconfigureorupgradefirmware]]**
1190
1191
1192 (% class="lead" %)
1193 Step2: Get Log by different commands.
1194
1195 Use below three method to generate logs.
1196
1197 * **AT+CFG       ~-~-> Command to show the current configuration**
1198 * **AT** **+GETLOG   ~-~-> Command to get the previous upstream log**
1199 * **press the toggle button for 1 ~~2 seconds     ~-~-> Trigger a uplink**
1200
1201 Above are the output example for about three action:
1202
1203 [[image:image-20250121235119-1.png||height="493" width="455"]]
1204
1205 [[image:image-20240207002129-2.png]]
1206
1207
1208 (% class="lead" %)
1209 Step3: Export Log
1210
1211 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/image-20241230155425-16.png?width=330&height=85&rev=1.1||alt="image-20241230155425-16.png" height="85" width="330"]]
1212
1213 select the log you want to export, then click the share icon on the far right to enter the document that comes with your phone and choose to export it.
1214
1215 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/image-20241230155528-17.png?width=327&height=324&rev=1.1||alt="image-20241230155528-17.png" height="324" width="327"]]
1216
1217
1218 == 6.7 How to find the AT Command Password if lost? ==
1219
1220
1221 === Why can't the password access AT command after upgrade(-NB)? ===
1222
1223
1224 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.
1225
1226 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).
1227
1228 Two different restore factory Settings configurations.
1229
1230 (% style="color:blue" %)**AT command:**
1231
1232 * (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
1233 * (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values except for passwords.(new)
1234
1235 === Version Confirmation ===
1236
1237
1238 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:
1239
1240 (% border="1" style="background-color:#f2f2f2; width:912px" %)
1241 |(% style="background-color:#4f81bd; color:white; width:306px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:311px" %)(((
1242 **Firmware version (without FDR1 function)**
1243 )))|(% style="background-color:#4f81bd; color:white; width:289px" %)(((
1244 **Firmware version (with FDR1 function)**
1245 )))
1246 |(% style="width:306px" %)(((
1247 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;
1248 )))|(% style="width:311px" %)Before V1.2.1|(% style="width:289px" %)After V1.2.1 (including V1.2.1)
1249 |(% style="width:306px" %)(((
1250 WL03A-NB, SDI-12-NB;
1251 )))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1252 After V1.0.8 (including V1.0.2)
1253 )))
1254 |(% style="width:306px" %)(((
1255 SW3L-NB, PS-NB;
1256 )))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1257 After V1.0.5 (including V1.0.5)
1258 )))
1259 |(% style="width:306px" %)RS485-NB|(% style="width:311px" %)Before V1.0.8|(% style="width:289px" %)After V1.0.8 (including V1.0.8)
1260
1261 === UART connection and firmware update methods ===
1262
1263
1264 Users can query passwords only using the UART interface via the STM32CubeProgrammer.
1265
1266 See **[[UART Connection>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]]**.
1267
1268 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]]**.
1269
1270
1271 === query the password via STM32CubeProgrammer ===
1272
1273
1274 Users can use the password address to query the password through STM32CubeProgrammer.
1275
1276 * The password address for old firmware(without FDR1 function) : **0x08019000**
1277 * The password address for new firmware(with FDR1 function) : **0x08025D00**
1278
1279 (% style="color:red" %)**Notice: The password can only be queried after the firmware is run once.**
1280
1281
1282 **Procedure for querying the password(old firmware):**
1283
1284 * After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the firmware once**.
1285 * Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1286 * Click "Device memory", enter **0x08019000** in "Address", and click "Read"
1287 * Find the 0x08019000 address field and then read the current password as shown in the screenshot below.
1288
1289 [[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"]]
1290
1291
1292 **Procedure for querying the password(new firmware):**
1293
1294 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.
1295
1296 * After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the new firmware once**.
1297 * Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1298 * Click "Device memory", enter **0x08025D00** in "Address", and click "Read"
1299 * Find the 0x08025D00 address field and then read the current password as shown in the screenshot below.
1300
1301 [[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"]]
1302
1303
1304 === Special case ===
1305
1306
1307 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**).
1308
1309 Invalid query screenshot example:
1310
1311 [[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"]]
1312
1313 [[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"]]
1314
1315
1316
1317 == 6.8 ==
1318
1319
1320
1321
1322
1323
1324