Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 145.2
edited by Xiaoling
on 2024/03/01 10:15
Change comment: There is no comment for this version
To version 53.9
edited by Xiaoling
on 2023/08/02 11:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
1 -(% class="wikigeneratedid" id="HTableofContents:" %)
1 +(% class="wikigeneratedid" %)
2 2  **Table of Contents:**
3 3  
4 4  {{toc/}}
... ... @@ -5,9 +5,6 @@
5 5  
6 6  
7 7  
8 -
9 -
10 -
11 11  = 1. The use of this guideline =
12 12  
13 13  
... ... @@ -14,59 +14,20 @@
14 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 15  
16 16  
17 -= 2. Attach Network =
14 += 2. Network Connection =
18 18  
19 -== 2.1 General Configure to attach network ==
20 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>)
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 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 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]]**
19 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
20 +|(% style="background-color:#4f81bd; color:white" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white" %)**APN**|(% style="background-color:#4f81bd; color:white" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white" %)**Comments**
21 +|1NCE| | |
22 +|China Mobile| | |
42 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, US Virgin Islands
44 -)))|(% style="width:135px" %)
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" %)
24 +== 2.1 1NCE SIM Card. ==
47 47  
48 -== 2.2 Speed Up Network Attach time ==
49 49  
50 50  
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.
52 -
53 -(% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
54 -
55 -(% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
56 -
57 -(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
58 -
59 -(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
60 -(% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
61 -(% style="color:#037691" %)**Telstra**(%%)        AT+QBAND=1,28
62 -(% style="color:#037691" %)**Softband**(%%)     AT+QBAND=2,3,8
63 -
64 -After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
65 -
66 -
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 -
70 70  = 3. Configure to connect to different servers =
71 71  
72 72  == 3.1 General UDP Connection ==
... ... @@ -80,7 +80,7 @@
80 80  
81 81  We can use PC tool to simulate UDP connection to make sure server works ok.
82 82  
83 -[[image:image-20230802112413-1.png||height="468" width="1024"]]
41 +[[image:image-20230802112413-1.png]]
84 84  
85 85  
86 86  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -94,6 +94,8 @@
94 94  
95 95  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
96 96  
55 +* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
56 +
97 97  [[image:image-20230802112413-2.png]]
98 98  
99 99  
... ... @@ -128,7 +128,7 @@
128 128  
129 129  [[image:image-20230802112413-4.png]]
130 130  
131 -[[image:image-20230802112413-5.png||height="530" width="987"]]
91 +[[image:image-20230802112413-5.png]]
132 132  
133 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.**
134 134  
... ... @@ -140,14 +140,14 @@
140 140  
141 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 142  
143 -[[image:image-20230802112413-6.png||height="336" width="925"]]
103 +[[image:image-20230802112413-6.png]]
144 144  
145 145  [[image:image-20230802112413-7.png]]
146 146  
147 147  
148 -=== 3.3.2 Simulate with MQTT.fx ===
108 +== 3.3.2 Simulate with MQTT.fx ==
149 149  
150 -==== 3.3.2.1 Establish MQTT Connection ====
110 +=== 3.3.2.1 Establish MQTT Connection ===
151 151  
152 152  
153 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.
... ... @@ -157,59 +157,51 @@
157 157  * (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
158 158  
159 159  * (% style="color:#037691" %)**Broker Port:**(%%) 1883
160 -
161 161  * (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID>
162 -
163 163  * (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name>
164 -
165 165  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
166 166  
167 -==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
124 +=== 3.3.2.2 Publish Data to ThingSpeak Channel ===
168 168  
169 -
170 170  [[image:image-20230802112413-9.png]]
171 171  
172 172  [[image:image-20230802112413-10.png]]
173 173  
130 +In MQTT.fx, we can publish below info:
174 174  
175 -(% style="color:blue" %)**In MQTT.fx, we can publish below info:**
132 +* Topic: channels/YOUR_CHANNEL_ID/publish
133 +* Payload: field1=63&field2=67&status=MQTTPUBLISH
176 176  
177 -* (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
178 -
179 -* (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH
180 -
181 181  Where 63 and 67 are the value to be published to field1 & field2.
182 182  
183 183  
184 -(% style="color:blue" %)**Result: **
138 +Result:
185 185  
186 -[[image:image-20230802112413-11.png||height="539" width="901"]]
140 +[[image:image-20230802112413-11.png]]
187 187  
188 188  
189 -=== 3.3.3 Configure NB-IoT Sensor for connection ===
143 +== 1.3 Configure NB-IoT Sensor for connection ==
190 190  
191 -==== 3.3.3.1 AT Commands: ====
145 +=== 1.3.1 AT Commands: ===
192 192  
193 -
194 194  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
195 195  
196 -* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
149 +* AT+PRO=3,1   ~/~/Set to use ThingSpeak Server and Related Payload
197 197  
198 -* (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
151 +* AT+CLIENT=<Your ThingSpeak MQTT ClientID>
199 199  
200 -* (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
153 +* AT+UNAME=<Your ThingSpeak MQTT User Name>
201 201  
202 -* (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>**
155 +* AT+PWD=<Your ThingSpeak MQTT Password>
203 203  
204 -* (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
157 +* AT+PUBTOPIC=<YOUR_CHANNEL_ID>
205 205  
206 -* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
159 +* AT+SUBTOPIC=<YOUR_CHANNEL_ID>
207 207  
208 -==== 3.3.3.2 Uplink Examples ====
161 +=== 1.3.2 Uplink Examples ===
209 209  
163 +For S31-NB
210 210  
211 -[[image:image-20230816201942-1.png]]
212 -
213 213  For SE01-NB
214 214  
215 215  For DDS20-NB
... ... @@ -233,315 +233,338 @@
233 233  For SN50V3-NB
234 234  
235 235  
236 -==== 3.3.3.3 Map fields to sensor value ====
188 +=== 1.3.2 Map fields to sensor value ===
237 237  
238 -
239 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 240  
241 241  
242 -[[image:image-20230802112413-12.png||height="504" width="1011"]]
193 +[[image:image-20230802112413-12.png]]
243 243  
244 -[[image:image-20230802112413-13.png||height="331" width="978"]]
195 +[[image:image-20230802112413-13.png]]
245 245  
246 246  
247 247  Below is the NB-IoT Product Table show the mapping.
248 248  
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" %)
200 +|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)Field1|(% colspan="1" rowspan="1" %)Field2|(% colspan="1" rowspan="1" %)Field3|(% colspan="1" rowspan="1" %)Field4|(% colspan="1" rowspan="1" %)Field5|(% colspan="1" rowspan="1" %)Field6|(% colspan="1" rowspan="1" %)Field7|(% colspan="1" rowspan="1" %)Field8|(% colspan="1" rowspan="1" %)(((
201 +Field9
268 268  
269 -== 3.4 [[Datacake>>https://datacake.co/]] ==
203 +
204 +)))|(% colspan="1" rowspan="1" %)(((
205 +Field10
270 270  
207 +
208 +)))
209 +|(% colspan="1" rowspan="1" %)S31x-NB|(% colspan="1" rowspan="1" %)Temperature |(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
210 +|(% colspan="1" rowspan="1" %)SE01-NB|(% colspan="1" rowspan="1" %)Temperature |(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)conduct|(% colspan="1" rowspan="1" %)dielectric_constant|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
211 +|(% colspan="1" rowspan="1" %)DDS20-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
212 +Battery
271 271  
272 -(% class="wikigeneratedid" %)
273 -Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
214 +
215 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
216 +|(% colspan="1" rowspan="1" %)DDS45-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
217 +Battery
274 274  
219 +
220 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
221 +|(% colspan="1" rowspan="1" %)DDS75-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
222 +Battery
275 275  
276 -(% class="wikigeneratedid" %)
277 -As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
224 +
225 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
226 +|(% colspan="1" rowspan="1" %)NMDS120-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
227 +Battery
278 278  
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.
229 +
230 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
231 +|(% colspan="1" rowspan="1" %)SPH01-NB|(% colspan="1" rowspan="1" %)ph|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
232 +|(% colspan="1" rowspan="1" %)NLM01-NB|(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
233 +|(% colspan="1" rowspan="1" %)NMDS200-NB|(% colspan="1" rowspan="1" %)distance1|(% colspan="1" rowspan="1" %)distance2|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
234 +|(% colspan="1" rowspan="1" %)CPN01-NB|(% colspan="1" rowspan="1" %)alarm|(% colspan="1" rowspan="1" %)count|(% colspan="1" rowspan="1" %)door open duration|(% colspan="1" rowspan="1" %)calc flag|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
235 +|(% colspan="1" rowspan="1" %)DS03A-NB|(% colspan="1" rowspan="1" %)level|(% colspan="1" rowspan="1" %)alarm|(% colspan="1" rowspan="1" %)pb14door open num|(% colspan="1" rowspan="1" %)pb14 last open time|(% colspan="1" rowspan="1" %)pb15 level status|(% colspan="1" rowspan="1" %)pb15 alarm status|(% colspan="1" rowspan="1" %)pb15 door open num|(% colspan="1" rowspan="1" %)pb15 last open time|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI
236 +|(% colspan="1" rowspan="1" %)SN50V3-NB|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
237 +|(% colspan="1" rowspan="1" %)mod1|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)DS18B20 Temp|(% colspan="1" rowspan="1" %)exit_state/input PA4|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)Temperature |(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
238 +|(% colspan="1" rowspan="1" %)mod2|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
239 +DS18B20 Temp
280 280  
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.
241 +
242 +)))|(% colspan="1" rowspan="1" %)(((
243 +exit_state/input PA4
282 282  
283 -=== 3.4.1 For device Already has template ===
245 +
246 +)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
247 +|(% colspan="1" rowspan="1" %)mod3|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
248 +Battery
284 284  
285 -==== 3.4.1.1 Create Device ====
250 +
251 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
252 +exit_state/input PA4
286 286  
287 -(% style="color:blue" %)**Add Device**(%%) in DataCake.
254 +
255 +)))|(% colspan="1" rowspan="1" %)adc1|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)adc4|(% colspan="1" rowspan="1" %)
256 +|(% colspan="1" rowspan="1" %)mod4|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
257 +Battery
288 288  
289 -[[image:image-20230808162301-1.png||height="453" width="952"]]
259 +
260 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
261 +DS18B20 Temp
290 290  
263 +
264 +)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
265 +exit_state/input PA4
291 291  
292 -[[image:image-20230808162342-2.png||height="541" width="952"]]
267 +
268 +)))|(% colspan="1" rowspan="1" %)(((
269 +DS18B20 Temp2
293 293  
271 +
272 +)))|(% colspan="1" rowspan="1" %)(((
273 +DS18B20 Temp3
294 294  
295 -(% style="color:blue" %)**Choose the correct model**(%%) from template.
275 +
276 +)))|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
277 +|(% colspan="1" rowspan="1" %)mod5|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
278 +Battery
296 296  
297 -[[image:image-20230808162421-3.png]]
280 +
281 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
282 +DS18B20 Temp
298 298  
284 +
285 +)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
286 +exit_state/input PA4
299 299  
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.
288 +
289 +)))|(% colspan="1" rowspan="1" %)Weight|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
290 +|(% colspan="1" rowspan="1" %)mod6|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
291 +Battery
301 301  
302 -[[image:image-20230808163612-7.png||height="549" width="952"]]
293 +
294 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)count|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
303 303  
304 -[[image:image-20230808163035-5.png]]
296 += 4. Datacake =
305 305  
306 -[[image:image-20230808163049-6.png||height="544" width="926"]]
298 +== 1.1 Define Product ==
307 307  
300 +Firstly, we need to set the MQTT mode to datacake, and we need to run AT+PRO=3,2. This command is set to datacake. After running the command, the device automatically sets the server address, port.
308 308  
309 -=== 3.4.2 For Device already registered in DataCake before shipped ===
310 310  
311 -==== 3.4.2.1 Scan QR Code to get the device info ====
303 +By chosing to add the device under a "New Product" you are required to give a name for this product. You can name it something like "My First MQTT Product".
312 312  
305 +[[image:image-20230802112413-14.png]]
313 313  
314 -Users can use their phones or computers to scan QR codes to obtain device data information.
307 +== 1.2 Create Device ==
315 315  
316 -[[image:image-20230808170051-8.png||height="255" width="259"]]
309 +In the second step you have to define the device which should be added to the product.
317 317  
318 -[[image:image-20230808170548-9.png]]
311 +[[image:image-20230802112413-15.png]]
319 319  
313 +Enter a name here (such as "My First MQTT Device") and complete the creation of the device by clicking on the "Next" button.
320 320  
321 -==== 3.4.2.2 Claim Device to User Account ====
322 322  
316 +== 1.3 Create Database Fields ==
323 323  
324 -By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
318 +After creating the device, it is listed in the table of the fleet view. Now open the device by clicking on the entry in the list.
325 325  
320 +You will then see a device view with an empty dashboard. Now, the first thing we want to do is navigate to the Device configuration. To do this, use the tab bar and click on "Configuration".
326 326  
327 -=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
322 +[[image:image-20230802112413-16.png]]
328 328  
324 +[[image:image-20230802112413-17.png]]
329 329  
330 -**Step1: Add a device**
326 +To create a first database field, please click on the "Add Field" button as marked in the screenshot above.
331 331  
332 -[[image:image-20240129170024-1.png||height="330" width="900"]]
328 +This will open another modal asking for some required input for your first field.
333 333  
330 +[[image:image-20230802112413-18.png]]
334 334  
335 -**Step2: Choose your device type,please select dragino NB-IOT device**
332 +[[image:image-20230802112413-19.png]]
336 336  
337 -[[image:image-20240129170216-2.png||height="534" width="643"]]
334 +== 1.4 Set up Broker ==
338 338  
336 +The broker is running on mqtt.datacake.co on ports 1883 and 8883. Port 1883 is unsecured and should not be used in production environments. Port 8883 uses a CA signed server certificate.
339 339  
340 -**Step3: Choose to create a new device**
338 +You will need an access token to log into the Datacake MQTT Broker. You can use your own personal token or create a token explicitly for individual devices or groups of devices.
341 341  
342 -[[image:image-20240129170539-3.png||height="459" width="646"]]
340 +View your Personal Access Token
343 343  
342 +You can view your own token via the User-Settings-Menu. You can reach this menu by clicking on "Edit Profile" at the end of the list using the Workspace Selector:
344 344  
345 -**Step4: Fill in the device ID of your NB device**
344 +[[image:image-20230802112413-20.png]]
346 346  
347 -[[image:image-20240202111546-1.png||height="378" width="651"]]
346 +MQTT Client-ID
348 348  
348 +The Datacake Broker manages the client IDs internally. You do not need to worry about a client ID. If your client optionally supports the specification of a client ID, please leave this specification blank. Your client then creates a randomly generated ID.
349 349  
350 -**Step5: Please select your device plan according to your needs and complete the creation of the device**
350 +AT+CLIENT=“Any value”
351 351  
352 -[[image:image-20240129171236-6.png||height="450" width="648"]]
352 +AT+UNAME=Token
353 353  
354 +AT+PWD=Token
354 354  
355 -**Step6: Please add the decoder at the payload decoder of the device configuration.**
356 +[[image:image-20230802112413-21.png]]
356 356  
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 358  
359 -[[image:image-20240129172056-7.png||height="457" width="816"]]
359 +== 1.6 Create your first Subscription ==
360 360  
361 -[[image:image-20240129173116-9.png||height="499" width="814"]]
361 +Subscribe
362 362  
363 +Data is published according to the following structure:
363 363  
364 -**Step7: Add the output of the decoder as a field**
365 +dtck~/~//
365 365  
366 -[[image:image-20240129173541-10.png||height="592" width="968"]]
367 +Subscribe to topics using this structure to receive messages via MQTT when readings (via API or MQTT) arrive in the Datacake Cloud. Messages are published whenever there is a change to a corresponding database field.
367 367  
368 368  
369 -**Step8: Customize the dashboard and use fields as parameters of the dashboard**
370 +[[image:image-20230802112413-22.png]]
370 370  
371 -[[image:image-20240129174518-11.png||height="147" width="1042"]]
372 372  
373 -[[image:image-20240129174657-12.png||height="538" width="916"]]
373 +[[image:image-20230802112413-23.png]]
374 374  
375 -[[image:image-20240129174840-13.png||height="536" width="750"]]
376 376  
376 +[[image:image-20230802112413-24.png]]
377 377  
378 -=== 3.4.4 For device have not configured to connect to DataCake ===
379 379  
379 +example:
380 380  
381 -(% class="lead" %)
382 -Use AT command for connecting to DataCake
381 +AT+PUBTOPIC=dtck-pub/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
383 383  
384 -(% style="color:blue" %)**AT+PRO=2,0**
383 +[[image:image-20230802112413-25.png]]
385 385  
386 -(% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
385 +== 1.7 Define Publish Topic ==
387 387  
387 +Publish
388 388  
389 -== 3.5 Node-Red (via MQTT) ==
389 +To upload data into the Datacake Cloud and into a specific device, you publish the data to the respective topic structure.
390 390  
391 -=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
391 +Due to the nature of MQTT, the topic prefix differs as follows:
392 392  
393 +dtck-pub~/~//
393 393  
394 -Take S31-NB UDP protocol as an example.
395 +example:
395 395  
396 -Dragino provides input flow examples for the sensors.
397 +AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
397 397  
398 -User can download the required JSON file through Dragino Node-RED input flow template.
399 +== 1.8 upload data ==
399 399  
400 -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]]
401 +[[image:image-20230802112413-26.png]]
401 401  
402 -We can directly import the template.
403 +[[image:image-20230802112413-27.png]]
403 403  
404 -The templates for S31-NB and NB95S31B are the same.
405 +[[image:image-20230802112413-28.png]]
405 405  
407 += =
406 406  
407 -[[image:image-20230809173127-4.png]]
409 += 5. Node-Red (via MQTT) =
408 408  
409 409  
410 -Please select the NB95S31B template.
412 +== 1.1 Configure Node-Red ==
411 411  
412 -[[image:image-20230809173310-5.png||height="558" width="926"]]
414 +[[image:image-20230802112413-29.png]]
413 413  
414 -[[image:image-20230809173438-6.png]]
416 +[[image:image-20230802112413-30.png]]
415 415  
416 -[[image:image-20230809173800-7.png]]
418 +== 1.2 Simulate Connection ==
417 417  
420 +[[image:image-20230802112413-31.png]]
418 418  
419 -Successfully imported template.
422 +== 1.3 Configure NB-IoT Sensors ==
420 420  
421 -[[image:image-20230809173835-8.png||height="515" width="860"]]
424 +* AT+PRO=3,0(hex format) or 3,5(json format)    ~/~/Set to mqtt Server and  Payload
425 +* AT+CLIENT=any value
426 +* AT+UNAME=any value
427 +* AT+PWD=any value
428 +* AT+PUBTOPIC=any value
429 +* AT+SUBTOPIC=any value
422 422  
431 += 6. ThingsBoard.Cloud (via MQTT) =
423 423  
424 -Users can set UDP port.
433 +== 1.1 Configure ThingsBoard ==
425 425  
426 -[[image:image-20230809174053-9.png]]
435 +=== 1.1.1 Create Device ===
427 427  
437 +Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]].
428 428  
429 -=== 3.5.2 Simulate Connection ===
439 +[[image:image-20230802112413-32.png]]
430 430  
441 +=== 1.1.2 Create Uplink & Downlink Converter ===
431 431  
432 -We have completed the configuration of UDP. We can try sending packets to node red.
443 +Uplink Converter
433 433  
434 -[[image:image-20230810083934-1.png]]
435 -
436 -[[image:image-20230810084048-2.png||height="535" width="1052"]]
437 -
438 -
439 -=== 3.5.3 Configure NB-IoT Sensors ===
440 -
441 -
442 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
443 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
444 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
445 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
446 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
447 -* (% style="color:#037691" %)**AT+PWD=“Your device token”**
448 -
449 -== 3.6 ThingsBoard.Cloud (via MQTT) ==
450 -
451 -=== 3.6.1 Configure ThingsBoard ===
452 -
453 -==== 3.6.1.1 Create Device ====
454 -
455 -
456 -Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
457 -
458 -[[image:image-20230802112413-32.png||height="583" width="1066"]]
459 -
460 -
461 -==== 3.6.1.2 Create Uplink & Downlink Converter ====
462 -
463 -
464 -(% style="color:blue" %)**Uplink Converter**
465 -
466 466  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.
467 467  
468 -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.
447 +To create an uplink converter go to the Integrations center -> Data converters page and click “plus” button. Name it “MQTT Uplink Converter” and select type Uplink. Use debug mode for now.
469 469  
470 -[[image:image-20230802112413-33.png||height="597" width="1061"]]
449 +[[image:image-20230802112413-33.png]]
471 471  
472 472  
473 -(% style="color:blue" %)**Downlink Converter**
452 +Downlink Converter
474 474  
475 475  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
476 476  
477 -[[image:image-20230802112413-34.png||height="598" width="1063"]]
456 +[[image:image-20230802112413-34.png]]
478 478  
479 -(% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
458 +Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.
480 480  
460 +=== 1.1.3 MQTT Integration Setup ===
481 481  
482 -==== 3.6.1.3 MQTT Integration Setup ====
462 +Go to the Integrations center -> Integrations page and click “plus” icon to add a new integration. Name it “MQTT Integration”, select type MQTT;
483 483  
464 +[[image:image-20230802112413-35.png]]
484 484  
485 -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**;
486 -
487 -[[image:image-20230802112413-35.png||height="597" width="1062"]]
488 -
489 -
490 490  * The next steps is to add the recently created uplink and downlink converters;
491 491  
492 -[[image:image-20230802112413-36.png||height="598" width="1062"]]
468 +[[image:image-20230802112413-36.png]]
493 493  
494 -[[image:image-20230802112413-37.png||height="598" width="1064"]]
470 +[[image:image-20230802112413-37.png]]
495 495  
472 +Add a topic filter:
496 496  
497 -(% style="color:blue" %)**Add a topic filter:**
498 498  
499 -Consistent with the theme of the node setting.
475 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。
500 500  
501 501  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
502 502  
503 -[[image:image-20230802112413-38.png||height="598" width="1064"]]
479 +[[image:image-20230802112413-38.png]]
504 504  
481 +== 1.2 Simulate with MQTT.fx ==
505 505  
506 -=== 3.6.2 Simulate with MQTT.fx ===
507 -
508 -
509 509  [[image:image-20230802112413-39.png]]
510 510  
511 -[[image:image-20230802112413-40.png||height="525" width="980"]]
485 +[[image:image-20230802112413-40.png]]
512 512  
487 +== 1.3 Configure NB-IoT Sensor ==
513 513  
514 -=== 3.6.3 Configure NB-IoT Sensor ===
489 +AT Commands
515 515  
491 +AT+PRO=3,3  ~/~/ Use MQTT to connect to ThingsBoard.
516 516  
517 -(% style="color:blue" %)**AT Commands**
493 +AT+SUBTOPIC=device name ~-~-> 只需要 Device Name 吗?对的
518 518  
519 -* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
495 +AT+PUBTOPIC=device name ~-~-> 只需要 Device Name 吗?对的
520 520  
521 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
522 522  
523 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
498 +Users do not need to fill in the client, username, and password. But the configuration information of the device requires setting the client, username, and password, which can be entered freely. (软件自动填充为 Device Name 吧).这边不用提示了，客户不需要输入。（大部分客户还是会自己去设置这个的，提高安全性）
524 524  
525 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
500 +CLIENT :“Any value”
526 526  
527 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
502 +User Name:“Any value”
528 528  
529 -* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
504 +Password:“Any value”
530 530  
506 +
531 531  Test Uplink by click the button for 1 second
532 532  
533 -[[image:image-20230802112413-41.png||height="496" width="828"]]
509 +[[image:image-20230802112413-41.png]]
534 534  
535 535  [[image:image-20230802112413-42.png]]
536 536  
537 -[[image:image-20230802112413-43.png||height="407" width="825"]]
513 +[[image:image-20230802112413-43.png]]
538 538  
539 539  
540 -== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
516 += 7. [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) =
541 541  
542 -=== 3.7.1 Create device & Get Credentials ===
518 +== 5.1 Create device & Get Credentials ==
543 543  
544 -
545 545  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.
546 546  
547 547  [[image:image-20230802112413-44.png]]
... ... @@ -548,6 +548,7 @@
548 548  
549 549  [[image:image-20230802112413-45.png]]
550 550  
526 += =
551 551  
552 552  Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
553 553  
... ... @@ -554,193 +554,55 @@
554 554  [[image:image-20230802112413-46.png]]
555 555  
556 556  
557 -The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
533 +On the Connection Profile window, set the following information: (这边加一个截图)
558 558  
559 -(% style="color:blue" %)**On the Connection Profile window, set the following information:**
535 +* Profile Name: “Any name”
536 +* Broker Address: mqtt.tago.io
537 +* Broker Port: 1883
538 +* Client ID: “Any value”
560 560  
561 -* (% style="color:#037691" %)**Profile Name: “Any name”**
540 +On the section User credentials, set the following information:(这边加一个截图)
562 562  
563 -* (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
542 +* User Name: “Any value” Tago validates your user by the token only
543 +* Password: “Your device token”
544 +* PUBTOPIC: “Any value”
545 +* SUBTOPIC: “Any value”
564 564  
565 -* (% style="color:#037691" %)**Broker Port: 8883**
547 +== 5.2 Simulate with MQTT.fx ==
566 566  
567 -* (% style="color:#037691" %)**Client ID: “Any value”**
549 +[[image:image-20230802112413-47.png]]
568 568  
569 -(% style="color:blue" %)**On the section User credentials, set the following information:**
551 +[[image:image-20230802112413-48.png]]
570 570  
571 -* (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
553 +Users can run the AT+PRO=3,5 command, and the payload will be converted to JSON format.
572 572  
573 -* (% style="color:#037691" %)**Password: “Your device token”**
555 +[[image:image-20230802112413-49.png]]
574 574  
575 -* (% style="color:#037691" %)**PUBTOPIC: “Any value”**
557 +== 1.4. tago data ==
576 576  
577 -* (% style="color:#037691" %)**SUBTOPIC: “Any value”**
578 578  
579 -(% style="color:blue" %)**AT command:**
560 +[[image:image-20230802112413-50.png]]
580 580  
581 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
562 +[[image:image-20230802112413-51.png]]
582 582  
583 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
564 +== 1.4. TLS mode ==
584 584  
585 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
566 +Users can choose to use SSL/TLS mode.
586 586  
587 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
568 +On the SSL/TLS section, check the option Enable SSL/TLS, and click OK.
588 588  
589 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
570 +The device needs to enable the TLS mode and set the AT+TLSMOD=1,0 command.
590 590  
591 -* (% style="color:#037691" %)**AT+PWD=“Your device token”**
572 +* Profile Name: “Any name”
573 +* Broker Address: mqtt.tago.io
574 +* Broker Port: 8883
575 +* Client ID: “Any value”
576 +* User Name: “Any value” Tago validates your user by the token only
577 +* Password: “Your device token”
578 +* PUBTOPIC: “Any value”
579 +* SUBTOPIC: “Any value”
592 592  
593 -=== 3.7.2 Simulate with MQTT.fx ===
594 -
595 -
596 596  [[image:image-20230802112413-52.png]]
597 597  
598 598  
599 -[[image:image-20230808105300-2.png||height="553" width="1026"]]
600 -
601 -
602 -Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
603 -
604 -[[image:image-20230808105217-1.png||height="556" width="1031"]]
605 -
606 -[[image:image-20230808105329-3.png]]
607 -
608 -
609 -=== 3.7.3 tago data ===
610 -
611 -
612 -[[image:image-20230802112413-50.png||height="242" width="1037"]]
613 -
614 -[[image:image-20230802112413-51.png||height="184" width="696"]]
615 -
616 -
617 -== 3.8 TCP Connection ==
618 -
619 -
620 -(% style="color:blue" %)**AT command:**
621 -
622 -* (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
623 -
624 -* (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
625 -
626 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
627 -
628 -(% style="color:blue" %)**Sensor Console Output when Uplink:**
629 -
630 -[[image:image-20230807233631-1.png]]
631 -
632 -
633 -(% style="color:blue" %)**See result in TCP Server:**
634 -
635 -[[image:image-20230807233631-2.png]]
636 -
637 -
638 -= 4. FAQ =
639 -
640 -== 4.1 What is the usage of Multi Sampling and One Uplink? ==
641 -
642 -
643 -The NB series has the feature for Multi Sampling and one uplink. See one of them
644 -
645 -[[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]]
646 -
647 -User can use this feature for below purpose:
648 -
649 -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.
650 -1. Give more sampling data points.
651 -1. Increase reliable in transmission. For example. If user set
652 -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)
653 -1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
654 -1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
655 -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.
656 -
657 -
658 -
659 -== 4.2 Why the uplink JSON format is not standard? ==
660 -
661 -
662 -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.
663 -
664 -[[image:image-20240229233154-1.png]]
665 -
666 -
667 -= 5. Trouble Shooting: =
668 -
669 -== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
670 -
671 -
672 -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.
673 -
674 -If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
675 -
676 -[[image:image-20240207002003-1.png]]
677 -
678 -
679 -If fail to attach network, it will shows signal 99. as below:
680 -
681 -[[image:image-20240207002129-2.png]]
682 -
683 -
684 -(% class="lead" %)
685 -When see this issue, below are the checklist:
686 -
687 -* 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.
688 -* 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]].
689 -* 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]].
690 -* Check if the device is attached to Carrier network but reject. (need to check with operator).
691 -* Check if the antenna is connected firmly.
692 -
693 -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.
694 -
695 -
696 -== 5.2 Issue: "NBIOT did not respond" ==
697 -
698 -
699 -(% class="box errormessage" %)
700 -(((
701 -11:24:22.397 [44596]NBIOT did not respond.
702 -11:24:24.315 [46530]NBIOT did not respond.
703 -11:24:26.256 [48464]NBIOT did not respond.
704 -11:24:28.196 [50398]NBIOT did not respond.
705 -11:24:30.115 [52332]NBIOT did not respond.
706 -11:24:32.127 [54266]NBIOT did not respond.
707 -11:24:32.127 [54299]Restart the module...
708 -11:24:39.181 [61332]No response when shutting down
709 -)))
710 -
711 -This issue might due to initiate issue for NB-IoT module. In this case, please try:
712 -
713 -1) Open Enclosure
714 -
715 -2) Power off device by pull out the power on Jumper
716 -
717 -3) Power on device by connect back the power jumper.
718 -
719 -4) push reset button.
720 -
721 -[[image:image-20240208001740-1.png]]
722 -
723 -
724 -== 5.3 Issue: "Failed to readI MSI number" ==
725 -
726 -
727 -(% class="box errormessage" %)
728 -(((
729 -[18170]Failed to read IMSI:1umber.
730 -[20109]Failed to read IMSI numoer.
731 -[22048]Failed to read IMSI number.
732 -[29842lRestart the module...
733 -)))
734 -
735 -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"]].
736 -
737 -
738 -== 5.4 Why sometime the AT Command is slow in reponse? ==
739 -
740 -
741 -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.
742 -
743 -[[image:image-20240226111928-1.png]]
744 -
745 -
746 746  
image-20230807233631-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -21.9 KB
Content
image-20230807233631-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -9.6 KB
Content
image-20230808105217-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -68.5 KB
Content
image-20230808105300-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -70.1 KB
Content
image-20230808105329-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -21.1 KB
Content
image-20230808162301-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -76.9 KB
Content
image-20230808162342-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -63.8 KB
Content
image-20230808162421-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -59.2 KB
Content
image-20230808162727-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -54.2 KB
Content
image-20230808163035-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -71.6 KB
Content
image-20230808163049-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -61.5 KB
Content
image-20230808163612-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -53.4 KB
Content
image-20230808170051-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -21.5 KB
Content
image-20230808170548-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -54.1 KB
Content
image-20230808205045-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -373.9 KB
Content
image-20230809165928-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -74.4 KB
Content
image-20230809170225-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 KB
Content
image-20230809170532-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -38.7 KB
Content
image-20230809173127-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -82.5 KB
Content
image-20230809173310-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -51.9 KB
Content
image-20230809173438-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -41.0 KB
Content
image-20230809173800-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -46.8 KB
Content
image-20230809173835-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -88.8 KB
Content
image-20230809174053-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -58.0 KB
Content
image-20230809180523-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -91.9 KB
Content
image-20230810083934-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -85.1 KB
Content
image-20230810084048-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -63.7 KB
Content
image-20230816201942-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -99.8 KB
Content
image-20240129170024-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.3 KB
Content
image-20240129170216-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -56.0 KB
Content
image-20240129170539-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -55.0 KB
Content
image-20240129171029-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -36.1 KB
Content
image-20240129171113-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -47.2 KB
Content
image-20240129171236-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.8 KB
Content
image-20240129172056-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -69.8 KB
Content
image-20240129172136-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -80.4 KB
Content
image-20240129173116-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -110.8 KB
Content
image-20240129173541-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -95.4 KB
Content
image-20240129174518-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -23.2 KB
Content
image-20240129174657-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -141.9 KB
Content
image-20240129174840-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -92.9 KB
Content
image-20240202111546-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -33.3 KB
Content
image-20240207002003-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -22.3 KB
Content
image-20240207002129-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -17.9 KB
Content
image-20240208001740-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -487.1 KB
Content
image-20240208102804-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -507.6 KB
Content
image-20240226111928-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -52.0 KB
Content
image-20240229233154-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -39.5 KB
Content