Skip to Content
Version 179.1 by Bei Jinggeng on 2024/08/07 11:24
Hide last authors
Xiaoling 83.3 1 (% class="wikigeneratedid" id="HTableofContents:" %)
2 **Table of Contents:**
Xiaoling 53.3 3
4 {{toc/}}
5
6
Xiaoling 100.2 7
8
9
10
Edwin Chen 1.1 11 = 1. The use of this guideline =
12
Xiaoling 1.2 13
Edwin Chen 1.1 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
Edwin Chen 55.1 17 = 2. Attach Network =
Edwin Chen 1.1 18
Edwin Chen 103.1 19 == 2.1 General Configure to attach network ==
Edwin Chen 1.1 20
Xiaoling 104.4 21
Edwin Chen 54.1 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)
Edwin Chen 137.1 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
Mengting Qiu 150.1 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
Edwin Chen 54.1 29
Edwin Chen 137.1 30 [[image:image-20240208102804-1.png||height="286" width="696"]]
31
Edwin Chen 83.1 32 [[image:image-20230808205045-1.png||height="293" width="438"]]
Edwin Chen 60.1 33
Edwin Chen 54.1 34 After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
35
Xiaoling 1.3 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.
Edwin Chen 1.1 37
Edwin Chen 54.1 38 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
Edwin Chen 99.1 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**
Xiaoling 56.2 40 |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
Edwin Chen 54.1 41 **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
Edwin Chen 1.1 42
Edwin Chen 161.1 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
Edwin Chen 57.1 45 |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
David Huang 66.1 46 |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
Xiaoling 53.27 47
Edwin Chen 103.1 48 == 2.2 Speed Up Network Attach time ==
Xiaoling 99.3 49
Xiaoling 104.2 50
Edwin Chen 149.1 51 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.
Xiaoling 102.2 52
Edwin Chen 107.1 53 (% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
54 (% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
Edwin Chen 129.1 55 (% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
Edwin Chen 147.1 56 (% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=10,8,20,28,2,4,12,13,66,85,5**
Edwin Chen 104.1 57
Edwin Chen 129.1 58 (% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
59 (% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
60 (% style="color:#037691" %)**Telstra**(%%)        AT+QBAND=1,28
61 (% style="color:#037691" %)**Softband**(%%)     AT+QBAND=2,3,8
Xiaoling 104.4 62
Edwin Chen 107.1 63 After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
64
Edwin Chen 165.1 65 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.
Edwin Chen 107.1 66
Edwin Chen 105.1 67 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/]]**
68
69
Edwin Chen 1.1 70 = 3. Configure to connect to different servers =
71
Xiaoling 53.3 72 == 3.1 General UDP Connection ==
Xiaoling 53.2 73
74
75 The NB-IoT Sensor can send packet to server use UDP protocol.
76
77
Xiaoling 53.3 78 === 3.1.1 Simulate UDP Connection by PC tool ===
79
80
Xiaoling 53.2 81 We can use PC tool to simulate UDP connection to make sure server works ok.
82
Xiaoling 105.2 83 [[image:image-20230802112413-1.png||height="468" width="1024"]]
Xiaoling 53.2 84
85
Xiaoling 53.3 86 === 3.1.2 Configure NB-IoT Sensor ===
Xiaoling 53.2 87
Xiaoling 53.3 88 ==== 3.1.2.1 AT Commands ====
Xiaoling 53.2 89
Xiaoling 53.3 90
Xiaoling 53.4 91 (% style="color:blue" %)**AT Commands:**
Xiaoling 53.3 92
Xiaoling 53.5 93 * (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/  Set to use UDP protocol to uplink ,Payload Type select Hex payload
Xiaoling 53.8 94
Xiaoling 53.5 95 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
Xiaoling 53.8 96
Xiaoling 53.2 97 [[image:image-20230802112413-2.png]]
98
99
Xiaoling 53.3 100 ==== 3.1.2.2 Uplink Example ====
Xiaoling 53.2 101
Xiaoling 53.3 102
Xiaoling 53.2 103 [[image:image-20230802112413-3.png]]
104
105
Xiaoling 53.7 106 == 3.2 General MQTT Connection ==
Xiaoling 53.2 107
Xiaoling 53.6 108
Xiaoling 53.2 109 The NB-IoT Sensor can send packet to server use MQTT protocol.
110
Xiaoling 53.6 111 Below are the commands.
Xiaoling 53.2 112
Xiaoling 53.8 113 (% style="color:blue" %)**AT Commands:**
Xiaoling 53.2 114
Xiaoling 53.9 115 * (% style="color:#037691" %)**AT+PRO=3,0**   (%%) ~/~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
Xiaoling 53.2 116
Xiaoling 53.9 117 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883**  (%%) ~/~/  Set MQTT server address and port
Xiaoling 53.8 118
Xiaoling 53.9 119 * (% style="color:#037691" %)**AT+CLIENT=CLIENT**     (%%) ~/~/  Set up the CLIENT of MQTT
Xiaoling 53.8 120
Xiaoling 53.9 121 * (% style="color:#037691" %)**AT+UNAME=UNAME**        (%%) ~/~/  Set the username of MQTT
Xiaoling 53.8 122
Xiaoling 53.9 123 * (% style="color:#037691" %)**AT+PWD=PWD**             (%%) ~/~/  Set the password of MQTT
Xiaoling 53.8 124
125 * (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB**  (%%) ~/~/  Set the sending topic of MQTT
126
127 * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB**  (%%) ~/~/  Set the subscription topic of MQTT
128
Xiaoling 53.2 129 [[image:image-20230802112413-4.png]]
130
Edwin Chen 102.1 131 [[image:image-20230802112413-5.png||height="530" width="987"]]
Xiaoling 53.2 132
Xiaoling 53.9 133 (% 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.**
Xiaoling 53.2 134
135
Xiaoling 53.7 136 == 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
Xiaoling 53.2 137
Xiaoling 53.9 138 === 3.3.1 Get MQTT Credentials ===
Xiaoling 53.2 139
Xiaoling 53.9 140
Xiaoling 53.2 141 [[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.
142
Edwin Chen 102.1 143 [[image:image-20230802112413-6.png||height="336" width="925"]]
Xiaoling 53.2 144
145 [[image:image-20230802112413-7.png]]
146
147
Xiaoling 53.27 148 === 3.3.2 Simulate with MQTT.fx ===
Xiaoling 53.2 149
Xiaoling 53.27 150 ==== 3.3.2.1 Establish MQTT Connection ====
Xiaoling 53.2 151
Xiaoling 53.9 152
Xiaoling 53.2 153 After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
154
155 [[image:image-20230802112413-8.png]]
156
Xiaoling 53.9 157 * (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
Xiaoling 53.2 158
Xiaoling 53.9 159 * (% style="color:#037691" %)**Broker Port:**(%%) 1883
Xiaoling 53.10 160
Xiaoling 53.9 161 * (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID>
Xiaoling 53.10 162
Xiaoling 53.9 163 * (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name>
Xiaoling 53.10 164
Xiaoling 53.9 165 * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
Xiaoling 53.2 166
Xiaoling 53.28 167 ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
168
169
Xiaoling 53.2 170 [[image:image-20230802112413-9.png]]
171
172 [[image:image-20230802112413-10.png]]
173
Xiaoling 53.43 174
Xiaoling 53.10 175 (% style="color:blue" %)**In MQTT.fx, we can publish below info:**
Xiaoling 53.2 176
Xiaoling 53.10 177 * (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
Xiaoling 53.2 178
Xiaoling 53.10 179 * (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH
180
Xiaoling 53.2 181 Where 63 and 67 are the value to be published to field1 & field2.
182
183
Xiaoling 53.10 184 (% style="color:blue" %)**Result: **
Xiaoling 53.2 185
Edwin Chen 102.1 186 [[image:image-20230802112413-11.png||height="539" width="901"]]
Xiaoling 53.2 187
188
Xiaoling 53.28 189 === 3.3.3 Configure NB-IoT Sensor for connection ===
Xiaoling 53.2 190
Xiaoling 53.28 191 ==== 3.3.3.1 AT Commands: ====
Xiaoling 53.2 192
Xiaoling 53.10 193
Xiaoling 53.2 194 In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
195
Xiaoling 99.3 196 * (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
Xiaoling 53.9 197
Xiaoling 53.26 198 * (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
Xiaoling 53.9 199
Xiaoling 53.26 200 * (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
Xiaoling 53.9 201
Xiaoling 53.26 202 * (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>**
Xiaoling 53.9 203
Xiaoling 53.26 204 * (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
Xiaoling 53.9 205
Xiaoling 53.26 206 * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
Xiaoling 53.2 207
Xiaoling 53.28 208 ==== 3.3.3.2 Uplink Examples ====
Xiaoling 53.10 209
Xiaoling 104.4 210
Edwin Chen 102.1 211 [[image:image-20230816201942-1.png]]
Xiaoling 53.10 212
Xiaoling 53.2 213 For SE01-NB
214
215 For DDS20-NB
216
217 For DDS45-NB
218
219 For DDS75-NB
220
221 For NMDS120-NB
222
223 For SPH01-NB
224
225 For NLM01-NB
226
227 For NMDS200-NB
228
229 For CPN01-NB
230
231 For DS03A-NB
232
233 For SN50V3-NB
234
235
Xiaoling 53.28 236 ==== 3.3.3.3 Map fields to sensor value ====
Xiaoling 53.2 237
Xiaoling 53.10 238
Xiaoling 53.2 239 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.
240
241
Edwin Chen 102.1 242 [[image:image-20230802112413-12.png||height="504" width="1011"]]
Xiaoling 53.2 243
Edwin Chen 102.1 244 [[image:image-20230802112413-13.png||height="331" width="978"]]
Xiaoling 53.2 245
246
247 Below is the NB-IoT Product Table show the mapping.
248
Xiaoling 83.4 249 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
250 |(% 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
251 |(% 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" %)
252 |(% 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" %)
253 |(% 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" %)
254 |(% 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" %)
255 |(% 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" %)
256 |(% 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" %)
257 |(% 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" %)
258 |(% 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" %)
259 |(% 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" %)
260 |(% 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" %)
261 |(% 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
262 |(% 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" %)
263 |(% 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" %)
264 |(% 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" %)
265 |(% 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" %)
266 |(% 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" %)
267 |(% 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" %)
Xiaoling 53.2 268
Edwin Chen 100.1 269 == 3.4 [[Datacake>>https://datacake.co/]] ==
Xiaoling 99.3 270
Xiaoling 53.2 271
Edwin Chen 100.1 272 (% class="wikigeneratedid" %)
273 Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
274
275
276 (% class="wikigeneratedid" %)
Xiaoling 100.5 277 As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
Edwin Chen 100.1 278
Xiaoling 100.2 279 * (% 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.
Edwin Chen 100.1 280
Xiaoling 100.2 281 * (% 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.
Edwin Chen 100.1 282
Edwin Chen 109.1 283 === 3.4.1 For device Already has template ===
Xiaoling 53.2 284
Edwin Chen 109.1 285 ==== 3.4.1.1 Create Device ====
Xiaoling 83.4 286
Xiaoling 100.4 287 (% style="color:blue" %)**Add Device**(%%) in DataCake.
Edwin Chen 100.1 288
Xiaoling 105.2 289 [[image:image-20230808162301-1.png||height="453" width="952"]]
Xiaoling 53.11 290
291
Xiaoling 105.2 292 [[image:image-20230808162342-2.png||height="541" width="952"]]
David Huang 78.1 293
294
Xiaoling 100.3 295 (% style="color:blue" %)**Choose the correct model**(%%) from template.
Edwin Chen 100.1 296
David Huang 78.1 297 [[image:image-20230808162421-3.png]]
298
Xiaoling 83.4 299
Xiaoling 100.3 300 (% 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.
David Huang 78.1 301
Xiaoling 105.2 302 [[image:image-20230808163612-7.png||height="549" width="952"]]
David Huang 78.1 303
304 [[image:image-20230808163035-5.png]]
305
Xiaoling 105.2 306 [[image:image-20230808163049-6.png||height="544" width="926"]]
David Huang 78.1 307
Xiaoling 83.4 308
Edwin Chen 109.1 309 === 3.4.2 For Device already registered in DataCake before shipped ===
David Huang 81.1 310
Edwin Chen 126.1 311 ==== 3.4.2.1 Scan QR Code to get the device info ====
Xiaoling 83.4 312
Xiaoling 145.2 313
David Huang 81.1 314 Users can use their phones or computers to scan QR codes to obtain device data information.
315
Edwin Chen 100.1 316 [[image:image-20230808170051-8.png||height="255" width="259"]]
David Huang 81.1 317
318 [[image:image-20230808170548-9.png]]
319
Xiaoling 83.4 320
Edwin Chen 126.1 321 ==== 3.4.2.2 Claim Device to User Account ====
322
Xiaoling 145.2 323
Edwin Chen 126.1 324 By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
325
326
Edwin Chen 109.1 327 === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
David Huang 81.1 328
329
Xiaoling 145.2 330 **Step1: Add a device**
331
Bei Jinggeng 123.1 332 [[image:image-20240129170024-1.png||height="330" width="900"]]
333
334
Xiaoling 145.2 335 **Step2: Choose your device type,please select dragino NB-IOT device**
336
Bei Jinggeng 123.1 337 [[image:image-20240129170216-2.png||height="534" width="643"]]
338
339
Xiaoling 145.2 340 **Step3: Choose to create a new device**
341
Bei Jinggeng 123.1 342 [[image:image-20240129170539-3.png||height="459" width="646"]]
343
344
Xiaoling 145.2 345 **Step4: Fill in the device ID of your NB device**
346
Bei Jinggeng 125.1 347 [[image:image-20240202111546-1.png||height="378" width="651"]]
Bei Jinggeng 123.1 348
349
Xiaoling 145.2 350 **Step5: Please select your device plan according to your needs and complete the creation of the device**
351
Bei Jinggeng 123.1 352 [[image:image-20240129171236-6.png||height="450" width="648"]]
353
354
Xiaoling 145.2 355 **Step6: Please add the decoder at the payload decoder of the device configuration.**
356
Bei Jinggeng 127.1 357 **Decoder location:**[[dragino-end-node-decoder/Datacake-Dragino_NB at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB]]
358
Bei Jinggeng 179.1 359 **Due to version update, please use the following decoder for the new version firmware**
360 [[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]]
361
Bei Jinggeng 123.1 362 [[image:image-20240129172056-7.png||height="457" width="816"]]
363
364 [[image:image-20240129173116-9.png||height="499" width="814"]]
365
366
Xiaoling 145.2 367 **Step7: Add the output of the decoder as a field**
368
Bei Jinggeng 123.1 369 [[image:image-20240129173541-10.png||height="592" width="968"]]
370
371
Xiaoling 145.2 372 **Step8: Customize the dashboard and use fields as parameters of the dashboard**
373
Bei Jinggeng 123.1 374 [[image:image-20240129174518-11.png||height="147" width="1042"]]
375
376 [[image:image-20240129174657-12.png||height="538" width="916"]]
377
378 [[image:image-20240129174840-13.png||height="536" width="750"]]
379
380
Edwin Chen 109.1 381 === 3.4.4 For device have not configured to connect to DataCake ===
382
Xiaoling 145.2 383
Edwin Chen 109.1 384 (% class="lead" %)
385 Use AT command for connecting to DataCake
386
Xiaoling 83.4 387 (% style="color:blue" %)**AT+PRO=2,0**
David Huang 81.1 388
Xiaoling 83.4 389 (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
David Huang 81.1 390
Xiaoling 83.4 391
Xiaoling 53.21 392 == 3.5 Node-Red (via MQTT) ==
Xiaoling 53.2 393
Xiaoling 53.48 394 === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
Xiaoling 53.2 395
Xiaoling 53.32 396
David Huang 93.1 397 Take S31-NB UDP protocol as an example.
Xiaoling 53.2 398
David Huang 93.1 399 Dragino provides input flow examples for the sensors.
Xiaoling 53.32 400
David Huang 93.1 401 User can download the required JSON file through Dragino Node-RED input flow template.
Xiaoling 53.2 402
David Huang 93.1 403 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]]
Xiaoling 53.24 404
David Huang 93.1 405 We can directly import the template.
Xiaoling 53.2 406
David Huang 93.1 407 The templates for S31-NB and NB95S31B are the same.
Xiaoling 53.21 408
Xiaoling 53.2 409
David Huang 93.1 410 [[image:image-20230809173127-4.png]]
Xiaoling 53.2 411
Xiaoling 99.3 412
David Huang 93.1 413 Please select the NB95S31B template.
Xiaoling 53.2 414
Xiaoling 105.2 415 [[image:image-20230809173310-5.png||height="558" width="926"]]
Xiaoling 53.2 416
David Huang 93.1 417 [[image:image-20230809173438-6.png]]
Xiaoling 53.2 418
David Huang 93.1 419 [[image:image-20230809173800-7.png]]
Xiaoling 53.21 420
Xiaoling 99.3 421
David Huang 93.1 422 Successfully imported template.
Xiaoling 53.21 423
Xiaoling 105.2 424 [[image:image-20230809173835-8.png||height="515" width="860"]]
Xiaoling 53.21 425
426
David Huang 93.1 427 Users can set UDP port.
Xiaoling 53.21 428
David Huang 93.1 429 [[image:image-20230809174053-9.png]]
Xiaoling 83.8 430
Xiaoling 99.3 431
David Huang 93.1 432 === 3.5.2 Simulate Connection ===
Xiaoling 83.8 433
Xiaoling 99.3 434
David Huang 93.1 435 We have completed the configuration of UDP. We can try sending packets to node red.
436
David Huang 98.1 437 [[image:image-20230810083934-1.png]]
David Huang 93.1 438
Xiaoling 105.2 439 [[image:image-20230810084048-2.png||height="535" width="1052"]]
David Huang 93.1 440
Xiaoling 105.2 441
David Huang 93.1 442 === 3.5.3 Configure NB-IoT Sensors ===
443
444
Saxer Lin 106.1 445 * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
446 * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
447 * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
448 * (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
449 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
450 * (% style="color:#037691" %)**AT+PWD=“Your device token”**
David Huang 93.1 451
Xiaoling 53.21 452 == 3.6 ThingsBoard.Cloud (via MQTT) ==
453
454 === 3.6.1 Configure ThingsBoard ===
455
Xiaoling 53.22 456 ==== 3.6.1.1 Create Device ====
Xiaoling 53.2 457
Xiaoling 53.32 458
Edwin Chen 59.1 459 Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
Xiaoling 53.2 460
Xiaoling 105.2 461 [[image:image-20230802112413-32.png||height="583" width="1066"]]
Xiaoling 53.2 462
463
Xiaoling 53.23 464 ==== 3.6.1.2 Create Uplink & Downlink Converter ====
465
Xiaoling 53.32 466
Xiaoling 53.22 467 (% style="color:blue" %)**Uplink Converter**
Xiaoling 53.2 468
469 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.
470
Xiaoling 53.42 471 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.
Xiaoling 53.2 472
Xiaoling 105.2 473 [[image:image-20230802112413-33.png||height="597" width="1061"]]
Xiaoling 53.2 474
475
Xiaoling 53.22 476 (% style="color:blue" %)**Downlink Converter**
Xiaoling 53.2 477
478 The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
479
Xiaoling 105.2 480 [[image:image-20230802112413-34.png||height="598" width="1063"]]
Xiaoling 53.2 481
Xiaoling 83.8 482 (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
Xiaoling 53.2 483
Xiaoling 53.22 484
Xiaoling 53.23 485 ==== 3.6.1.3 MQTT Integration Setup ====
Xiaoling 53.2 486
487
Xiaoling 53.44 488 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**;
Xiaoling 53.24 489
Xiaoling 105.2 490 [[image:image-20230802112413-35.png||height="597" width="1062"]]
Xiaoling 53.2 491
Xiaoling 53.32 492
Xiaoling 53.2 493 * The next steps is to add the recently created uplink and downlink converters;
494
Xiaoling 105.2 495 [[image:image-20230802112413-36.png||height="598" width="1062"]]
Xiaoling 53.2 496
Xiaoling 105.2 497 [[image:image-20230802112413-37.png||height="598" width="1064"]]
Xiaoling 53.2 498
Xiaoling 53.33 499
Xiaoling 53.24 500 (% style="color:blue" %)**Add a topic filter:**
Xiaoling 53.2 501
Mengting Qiu 108.1 502 Consistent with the theme of the node setting.
Xiaoling 53.2 503
504 You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
505
Xiaoling 105.2 506 [[image:image-20230802112413-38.png||height="598" width="1064"]]
Xiaoling 53.2 507
508
Xiaoling 53.23 509 === 3.6.2 Simulate with MQTT.fx ===
510
Xiaoling 53.32 511
Xiaoling 53.2 512 [[image:image-20230802112413-39.png]]
513
Xiaoling 105.2 514 [[image:image-20230802112413-40.png||height="525" width="980"]]
Xiaoling 53.2 515
516
Xiaoling 53.23 517 === 3.6.3 Configure NB-IoT Sensor ===
Xiaoling 53.2 518
Xiaoling 53.25 519
Xiaoling 53.23 520 (% style="color:blue" %)**AT Commands**
Xiaoling 53.2 521
Edwin Chen 59.1 522 * (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
Xiaoling 53.2 523
Xiaoling 83.4 524 * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
525
Edwin Chen 59.1 526 * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
Xiaoling 83.4 527
Edwin Chen 59.1 528 * (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
Xiaoling 83.4 529
Edwin Chen 59.1 530 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
Xiaoling 83.4 531
Edwin Chen 59.1 532 * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
Xiaoling 53.2 533
534 Test Uplink by click the button for 1 second
535
Xiaoling 105.2 536 [[image:image-20230802112413-41.png||height="496" width="828"]]
Xiaoling 53.2 537
538 [[image:image-20230802112413-42.png]]
539
Xiaoling 105.2 540 [[image:image-20230802112413-43.png||height="407" width="825"]]
Xiaoling 53.2 541
542
543
kai 173.2 544 == 3.7 ThingsBoard.Cloud (via COAP) ==
Xiaoling 53.2 545
kai 173.2 546 === 3.7.1 Configure ThingsBoard ===
Xiaoling 53.23 547
kai 173.2 548 ==== 3.7.1.1 Create Uplink & Downlink Converter ====
549
550
551 (% style="color:blue" %)**Uplink Converter**
552
553 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.
554
555 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.
556
557 [[image:image-20240729141300-1.png||height="552" width="1115"]]
558
559
560 (% style="color:blue" %)**Downlink Converter**
561
562 The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
563
564 [[image:image-20240729142505-3.png||height="507" width="1023"]]
565
566
567 ==== 3.7.1.2 COAP Integration Setup ====
568
569
Bei Jinggeng 179.1 570 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" %);
kai 173.2 571
572 [[image:image-20240729144058-4.png||height="506" width="1021"]]
573
574
575 The next steps is to add the recently created uplink converters;
576
577 [[image:image-20240729150142-5.png||height="507" width="1023"]]
578
579
580 ==== 3.7.1.3 Add COAP Integration ====
581
Bei Jinggeng 179.1 582 ==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
kai 173.2 583
584
585 === 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
586
587 ==== 3.7.2.1 Instruction Description ====
588
kai 178.1 589 * AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
kai 173.2 590 * AT+SERVADDR=COAP Server Address,5683
591
592 Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
593
kai 178.1 594 [[image:image-20240729172305-12.png||height="361" width="624"]]
595
kai 173.2 596 Note:The port for the COAP protocol has been fixed to 5683
597
598
kai 178.1 599 * AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
kai 173.2 600
kai 178.1 601 If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
602
603 e.g.
604
605 * AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
606
607 [[image:image-20240729172415-13.png||height="401" width="694"]]
608
609 If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
610
611 e.g.
612
Bei Jinggeng 179.1 613 * AT+URL1=11, "i";  
kai 178.1 614 * AT+URL2=11,"/faaaa241f-af4a-b780-4468-c671bb574858"
615
616 [[image:image-20240729172500-14.png||height="403" width="700"]]
617
618
kai 173.2 619 == 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
620
621 === 3.8.1 Create device & Get Credentials ===
622
623
Xiaoling 53.2 624 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.
625
626 [[image:image-20230802112413-44.png]]
627
628 [[image:image-20230802112413-45.png]]
629
630
631 Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
632
633 [[image:image-20230802112413-46.png]]
634
635
David Huang 70.1 636 The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
Xiaoling 53.2 637
Xiaoling 83.8 638 (% style="color:blue" %)**On the Connection Profile window, set the following information:**
David Huang 70.1 639
Xiaoling 83.8 640 * (% style="color:#037691" %)**Profile Name: “Any name”**
Xiaoling 53.2 641
Xiaoling 83.8 642 * (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
Xiaoling 53.23 643
Xiaoling 83.8 644 * (% style="color:#037691" %)**Broker Port: 8883**
Xiaoling 53.23 645
Xiaoling 83.8 646 * (% style="color:#037691" %)**Client ID: “Any value”**
Xiaoling 53.23 647
Xiaoling 83.8 648 (% style="color:blue" %)**On the section User credentials, set the following information:**
Xiaoling 53.2 649
Xiaoling 83.8 650 * (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
Xiaoling 53.2 651
Xiaoling 83.8 652 * (% style="color:#037691" %)**Password: “Your device token”**
Xiaoling 53.2 653
Xiaoling 83.8 654 * (% style="color:#037691" %)**PUBTOPIC: “Any value”**
Xiaoling 53.23 655
Xiaoling 83.8 656 * (% style="color:#037691" %)**SUBTOPIC: “Any value”**
Xiaoling 53.23 657
David Huang 70.1 658 (% style="color:blue" %)**AT command:**
659
Xiaoling 83.8 660 * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
David Huang 70.1 661
Xiaoling 83.5 662 * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
David Huang 70.1 663
Xiaoling 83.5 664 * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
665
666 * (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
667
668 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
669
670 * (% style="color:#037691" %)**AT+PWD=“Your device token”**
671
kai 173.2 672 === 3.8.2 Simulate with MQTT.fx ===
Xiaoling 53.23 673
Xiaoling 99.3 674
David Huang 70.1 675 [[image:image-20230802112413-52.png]]
Xiaoling 53.23 676
Xiaoling 53.2 677
Xiaoling 105.2 678 [[image:image-20230808105300-2.png||height="553" width="1026"]]
Xiaoling 53.2 679
Xiaoling 99.3 680
Xiaoling 53.38 681 Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
Xiaoling 53.2 682
Xiaoling 105.2 683 [[image:image-20230808105217-1.png||height="556" width="1031"]]
Xiaoling 53.44 684
David Huang 70.1 685 [[image:image-20230808105329-3.png]]
Xiaoling 53.2 686
687
kai 173.2 688 === 3.8.3 tago data ===
Xiaoling 53.2 689
Xiaoling 53.23 690
Xiaoling 105.2 691 [[image:image-20230802112413-50.png||height="242" width="1037"]]
Xiaoling 53.2 692
Edwin Chen 59.1 693 [[image:image-20230802112413-51.png||height="184" width="696"]]
Xiaoling 53.2 694
695
kai 173.2 696 == 3.9 TCP Connection ==
Edwin Chen 63.1 697
Xiaoling 83.6 698
Xiaoling 83.5 699 (% style="color:blue" %)**AT command:**
Edwin Chen 63.1 700
Xiaoling 83.5 701 * (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
Edwin Chen 63.1 702
Xiaoling 83.5 703 * (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
Edwin Chen 63.1 704
Xiaoling 83.8 705 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
Xiaoling 83.5 706
Xiaoling 83.6 707 (% style="color:blue" %)**Sensor Console Output when Uplink:**
Xiaoling 83.5 708
Edwin Chen 63.1 709 [[image:image-20230807233631-1.png]]
710
711
Xiaoling 83.6 712 (% style="color:blue" %)**See result in TCP Server:**
Edwin Chen 63.1 713
714 [[image:image-20230807233631-2.png]]
Edwin Chen 132.1 715
716
kai 173.2 717 == 3.10 AWS Connection ==
Edwin Chen 132.1 718
719
Mengting Qiu 164.1 720 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]]
721
722
723
724
Mengting Qiu 154.1 725 = 4. MQTT/UDP/TCP downlink =
Xiaoling 145.2 726
Mengting Qiu 154.1 727 == 4.1 MQTT (via MQTT.fx) ==
728
729 Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
730
Mengting Qiu 160.1 731 **1.** Configure node MQTT connection (via MQTT.fx):
Mengting Qiu 154.1 732
733 (% style="color:blue" %)**AT command:**
734
Mengting Qiu 160.1 735 * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
Mengting Qiu 154.1 736
737 * (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
738
739 * (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
740
741 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
742
743 * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
744
Mengting Qiu 160.1 745 * (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
Mengting Qiu 154.1 746
747 (% 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.**
748
Mengting Qiu 160.1 749 [[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
Mengting Qiu 154.1 750
751
Mengting Qiu 160.1 752 **2. **When the node uplink packets, we can observe the data in MQTT.fx.
Mengting Qiu 154.1 753
Mengting Qiu 160.1 754 [[image:image-20240418144337-1.png||height="709" width="802"]]
Mengting Qiu 154.1 755
Mengting Qiu 160.1 756 **3. **The downlink command can be successfully sent only when the downlink port is open.
Mengting Qiu 154.1 757
Mengting Qiu 160.1 758 The downlink port is opened for about 3 seconds after uplink packets are sent.
Mengting Qiu 154.1 759
Mengting Qiu 160.1 760 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.
Mengting Qiu 154.1 761
Mengting Qiu 160.1 762 [[image:image-20240418150435-3.png||height="582" width="659"]]
763
764 [[image:image-20240418150932-4.png||height="492" width="1061"]]
765
766 (% 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.**
767
768
769
770
771
772
773
Mengting Qiu 154.1 774 = 5. FAQ =
775
776 == 5.1 What is the usage of Multi Sampling and One Uplink? ==
777
778
Edwin Chen 133.1 779 The NB series has the feature for Multi Sampling and one uplink. See one of them
780
781 [[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]]
782
783 User can use this feature for below purpose:
784
785 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.
786 1. Give more sampling data points.
787 1. Increase reliable in transmission. For example. If user set
788 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)
789 1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
790 1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
Xiaoling 148.2 791 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.
Edwin Chen 133.1 792
Mengting Qiu 154.1 793 == 5.2 Why the uplink JSON format is not standard? ==
Edwin Chen 145.1 794
Xiaoling 148.2 795
Edwin Chen 145.1 796 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.
797
Edwin Chen 148.1 798 The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
799
Edwin Chen 145.1 800 [[image:image-20240229233154-1.png]]
801
802
Mengting Qiu 154.1 803 = 6. Trouble Shooting: =
Edwin Chen 133.1 804
Mengting Qiu 154.1 805 == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
Edwin Chen 133.1 806
Xiaoling 145.2 807
Edwin Chen 132.1 808 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.
809
810 If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
811
812 [[image:image-20240207002003-1.png]]
813
814
815 If fail to attach network, it will shows signal 99. as below:
816
817 [[image:image-20240207002129-2.png]]
818
819
820 (% class="lead" %)
821 When see this issue, below are the checklist:
822
823 * 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.
824 * 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]].
825 * 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]].
826 * Check if the device is attached to Carrier network but reject. (need to check with operator).
827 * Check if the antenna is connected firmly.
828
829 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.
830
Edwin Chen 135.1 831
Mengting Qiu 154.1 832 == 6.2 Issue: "NBIOT did not respond" ==
Edwin Chen 135.1 833
Xiaoling 145.2 834
Edwin Chen 135.1 835 (% class="box errormessage" %)
836 (((
837 11:24:22.397 [44596]NBIOT did not respond.
838 11:24:24.315 [46530]NBIOT did not respond.
839 11:24:26.256 [48464]NBIOT did not respond.
840 11:24:28.196 [50398]NBIOT did not respond.
841 11:24:30.115 [52332]NBIOT did not respond.
842 11:24:32.127 [54266]NBIOT did not respond.
843 11:24:32.127 [54299]Restart the module...
844 11:24:39.181 [61332]No response when shutting down
845 )))
846
847 This issue might due to initiate issue for NB-IoT module. In this case, please try:
848
849 1) Open Enclosure
850
851 2) Power off device by pull out the power on Jumper
852
853 3) Power on device by connect back the power jumper.
854
855 4) push reset button.
856
857 [[image:image-20240208001740-1.png]]
Edwin Chen 138.1 858
859
Mengting Qiu 154.1 860 == 6.3 Issue: "Failed to readI MSI number" ==
Edwin Chen 138.1 861
Xiaoling 145.2 862
Edwin Chen 138.1 863 (% class="box errormessage" %)
864 (((
865 [18170]Failed to read IMSI:1umber.
866 [20109]Failed to read IMSI numoer.
867 [22048]Failed to read IMSI number.
868 [29842lRestart the module...
869 )))
870
Edwin Chen 141.1 871 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"]].
872
873
Bei Jinggeng 161.2 874 == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
Edwin Chen 141.1 875
Xiaoling 145.2 876
Mengting Qiu 142.1 877 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.
Edwin Chen 141.1 878
879 [[image:image-20240226111928-1.png]]
Bei Jinggeng 161.2 880
881
882 == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
883
Bei Jinggeng 163.1 884 (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
885 === UDP: ===
Bei Jinggeng 161.2 886
Bei Jinggeng 163.1 887 (% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
Bei Jinggeng 161.2 888 Its downlink command is the same as the AT command, but brackets are required.
889 Example:
890
891 {AT+TDC=300}
892
Bei Jinggeng 163.1 893
894 (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
895 === MQTT: ===
896
897 Json：
898
899 The Json format in MQTT mode needs to be configured with all commands.
900 If you have configurations that need to be changed, please change them in the template below.
901 Template:
902
903 {
904 "AT+SERVADDR":"119.91.62.30,1882",
905 "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
906 "AT+UNAME":"usenamedragino",
907 "AT+PWD":"passworddragino",
908 "AT+PUBTOPIC":"123",
909 "AT+SUBTOPIC":"321",
910 "AT+TDC":"7200",
911 "AT+INTMOD":"0",
912 "AT+APN":"NULL",
913 "AT+5VT":"0",
914 "AT+PRO":"3,5",
915 "AT+TR":"900",
916 "AT+NOUD":"0",
917 "AT+CSQTIME":"5",
918 "AT+DNSTIMER":"0",
919 "AT+TLSMOD":"0,0",
920 "AT+MQOS":"0",
921 "AT+TEMPALARM1":"0",
922 "AT+TEMPALARM2":"10",
923 "AT+TEMPALARM3":"0"
924 }
925
926 Hex：
927
928 MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
929
930 The supported commands are consistent with LoRaWAN's hex commands.
931 Please refer to the following link to obtain the hex format:
932
933 [[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/]]
934
Bei Jinggeng 167.1 935
936 == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs？(%%) ==
937
938 * **AT Command: AT** **+GETLOG**
939
940 This command can be used to query upstream logs of data packets.
941
942 [[image:image-20240701114700-1.png]]
943
944
945
Bei Jinggeng 161.2 946