Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 134.1
edited by Edwin Chen
on 2024/02/08 00:17
Change comment: Uploaded new attachment "image-20240208001740-1.png", version {1}
To version 53.2
edited by Xiaoling
on 2023/08/02 11:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -1,13 +11,3 @@
1 -(% class="wikigeneratedid" id="HTableofContents:" %)
2 -**Table of Contents:**
3 -
4 -{{toc/}}
5 -
6 -
7 -
8 -
9 -
10 -
11 11  = 1. The use of this guideline =
12 12  
13 13  
... ... @@ -14,200 +14,143 @@
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 =
7 += 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. Insert the SIM card to Sensor
26 -1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
27 -
28 -[[image:image-20230808205045-1.png||height="293" width="438"]]
29 -
30 -After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
31 -
32 32  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.
33 33  
34 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
35 -|(% 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**
36 -|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
37 -**[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
38 38  
39 -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
40 -)))|(% style="width:135px" %)
41 -|(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
42 -|(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
13 +== 2.1 1NCE SIM Card. ==
43 43  
44 -== 2.2 Speed Up Network Attach time ==
45 45  
16 +(% border="1" cellspacing="4" style="width:510px;background-color:#F2F2F2" %)
17 +|(% 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
18 +|1NCE| | |
19 +|China Mobile| | |
46 46  
47 -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.
48 48  
49 -(% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
50 -
51 -(% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
52 -
53 -(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
54 -
55 -(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
56 -(% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
57 -(% style="color:#037691" %)**Telstra**(%%)        AT+QBAND=1,28
58 -(% style="color:#037691" %)**Softband**(%%)     AT+QBAND=2,3,8
59 -
60 -After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
61 -
62 -
63 -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/]]**
64 -
65 -
66 66  = 3. Configure to connect to different servers =
67 67  
68 -== 3.1 General UDP Connection ==
69 69  
25 += NB-IoT 服务器对接例子 =
70 70  
27 += 1. General UDP Connection =
28 +
71 71  The NB-IoT Sensor can send packet to server use UDP protocol.
72 72  
31 +== 1.1 Simulate UDP Connection by PC tool ==
73 73  
74 -=== 3.1.1 Simulate UDP Connection by PC tool ===
75 -
76 -
77 77  We can use PC tool to simulate UDP connection to make sure server works ok.
78 78  
79 -[[image:image-20230802112413-1.png||height="468" width="1024"]]
35 +[[image:image-20230802112413-1.png]]
80 80  
37 +== 1.2 Configure NB-IoT Sensor ==
81 81  
82 -=== 3.1.2 Configure NB-IoT Sensor ===
39 +=== 1.2.1 AT Commands ===
83 83  
84 -==== 3.1.2.1 AT Commands ====
41 +AT Commands:
85 85  
43 +* AT+PRO=2,0 ~/~/  Set to use UDP protocol to uplink  ,  Payload Type select Hex payload
44 +* AT+SERVADDR=120.24.4.116,5601    ~/~/  Set UDP server address and port
45 +* AT+CFM=1        ~/~/  If the server does not respond, this command is unnecessary
86 86  
87 -(% style="color:blue" %)**AT Commands:**
88 -
89 -* (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/  Set to use UDP protocol to uplink ,Payload Type select Hex payload
90 -
91 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
92 -
93 -* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
94 -
95 95  [[image:image-20230802112413-2.png]]
96 96  
49 +=== 1.2.2 Uplink Example ===
97 97  
98 -==== 3.1.2.2 Uplink Example ====
99 99  
100 -
101 101  [[image:image-20230802112413-3.png]]
102 102  
103 103  
104 -== 3.2 General MQTT Connection ==
55 += 2. General MQTT Connection =
105 105  
106 -
107 107  The NB-IoT Sensor can send packet to server use MQTT protocol.
108 108  
109 -Below are the commands.
59 +Below are the commands
110 110  
111 -(% style="color:blue" %)**AT Commands:**
61 +AT Commands:
112 112  
113 -* (% style="color:#037691" %)**AT+PRO=3,0**   (%%) ~/~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
63 +* AT+PRO=3,0 ~/~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
64 +* AT+SERVADDR=120.24.4.116,1883    ~/~/  Set MQTT server address and port
65 +* AT+CLIENT=CLIENT        ~/~/  Set up the CLIENT of MQTT
66 +* AT+UNAME=UNAME                      ~/~/  Set the username of MQTT
67 +* AT+PWD=PWD                          ~/~/  Set the password of MQTT
68 +* AT+PUBTOPIC=NSE01_PUB               ~/~/  Set the sending topic of MQTT
69 +* AT+SUBTOPIC=NSE01_SUB           ~/~/  Set the subscription topic of MQTT
114 114  
115 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883**  (%%) ~/~/  Set MQTT server address and port
116 -
117 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT**     (%%) ~/~/  Set up the CLIENT of MQTT
118 -
119 -* (% style="color:#037691" %)**AT+UNAME=UNAME**        (%%) ~/~/  Set the username of MQTT
120 -
121 -* (% style="color:#037691" %)**AT+PWD=PWD**             (%%) ~/~/  Set the password of MQTT
122 -
123 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB**  (%%) ~/~/  Set the sending topic of MQTT
124 -
125 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB**  (%%) ~/~/  Set the subscription topic of MQTT
126 -
127 127  [[image:image-20230802112413-4.png]]
128 128  
129 -[[image:image-20230802112413-5.png||height="530" width="987"]]
73 +[[image:image-20230802112413-5.png]]
130 130  
131 -(% 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.**
75 +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.
132 132  
133 133  
134 -== 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
135 135  
136 -=== 3.3.1 Get MQTT Credentials ===
79 += 3. [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) =
137 137  
81 +== 1.1 Get MQTT Credentials ==
138 138  
139 139  [[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.
140 140  
141 -[[image:image-20230802112413-6.png||height="336" width="925"]]
85 +[[image:image-20230802112413-6.png]]
142 142  
143 143  [[image:image-20230802112413-7.png]]
144 144  
145 145  
146 -=== 3.3.2 Simulate with MQTT.fx ===
90 +== 1.2. Simulate with MQTT.fx ==
147 147  
148 -==== 3.3.2.1 Establish MQTT Connection ====
92 +=== 1.2.1 Establish MQTT Connection ===
149 149  
150 -
151 151  After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
152 152  
153 153  [[image:image-20230802112413-8.png]]
154 154  
155 -* (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
98 +* Broker Address: mqtt3.thingspeak.com
99 +* Broker Port: 1883
100 +* Client ID: <Your ThingSpeak MQTT ClientID>
101 +* User Name: <Your ThingSpeak MQTT User Name>
102 +* Password: <Your ThingSpeak MQTT Password>
156 156  
157 -* (% style="color:#037691" %)**Broker Port:**(%%) 1883
158 158  
159 -* (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID>
105 +=== 1.2.2 Publish Data to ThingSpeak Channel ===
160 160  
161 -* (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name>
162 -
163 -* (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
164 -
165 -==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
166 -
167 -
168 168  [[image:image-20230802112413-9.png]]
169 169  
170 170  [[image:image-20230802112413-10.png]]
171 171  
111 +In MQTT.fx, we can publish below info:
172 172  
173 -(% style="color:blue" %)**In MQTT.fx, we can publish below info:**
113 +* Topic: channels/YOUR_CHANNEL_ID/publish
114 +* Payload: field1=63&field2=67&status=MQTTPUBLISH
174 174  
175 -* (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
176 176  
177 -* (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH
178 -
179 179  Where 63 and 67 are the value to be published to field1 & field2.
180 180  
181 181  
182 -(% style="color:blue" %)**Result: **
120 +Result:
183 183  
184 -[[image:image-20230802112413-11.png||height="539" width="901"]]
122 +[[image:image-20230802112413-11.png]]
185 185  
186 186  
187 -=== 3.3.3 Configure NB-IoT Sensor for connection ===
125 +== 1.3 Configure NB-IoT Sensor for connection ==
188 188  
189 -==== 3.3.3.1 AT Commands: ====
127 +=== 1.3.1 AT Commands: ===
190 190  
191 -
192 192  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
193 193  
194 -* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
131 +* AT+PRO=3,1   ~/~/Set to use ThingSpeak Server and Related Payload
132 +* AT+CLIENT=<Your ThingSpeak MQTT ClientID>
133 +* AT+UNAME=<Your ThingSpeak MQTT User Name>
134 +* AT+PWD=<Your ThingSpeak MQTT Password>
135 +* AT+PUBTOPIC=<YOUR_CHANNEL_ID>
136 +* AT+SUBTOPIC=<YOUR_CHANNEL_ID>
195 195  
196 -* (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
197 197  
198 -* (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
199 199  
200 -* (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>**
140 +=== 1.3.2 Uplink Examples ===
201 201  
202 -* (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
142 +For S31-NB
203 203  
204 -* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
205 -
206 -==== 3.3.3.2 Uplink Examples ====
207 -
208 -
209 -[[image:image-20230816201942-1.png]]
210 -
211 211  For SE01-NB
212 212  
213 213  For DDS20-NB
... ... @@ -231,305 +231,340 @@
231 231  For SN50V3-NB
232 232  
233 233  
234 -==== 3.3.3.3 Map fields to sensor value ====
167 +=== 1.3.2 Map fields to sensor value ===
235 235  
236 -
237 237  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.
238 238  
239 239  
240 -[[image:image-20230802112413-12.png||height="504" width="1011"]]
172 +[[image:image-20230802112413-12.png]]
241 241  
242 -[[image:image-20230802112413-13.png||height="331" width="978"]]
174 +[[image:image-20230802112413-13.png]]
243 243  
244 244  
245 245  Below is the NB-IoT Product Table show the mapping.
246 246  
247 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
248 -|(% 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
249 -|(% 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" %)
250 -|(% 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" %)
251 -|(% 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" %)
252 -|(% 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" %)
253 -|(% 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" %)
254 -|(% 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" %)
255 -|(% 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" %)
256 -|(% 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" %)
257 -|(% 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" %)
258 -|(% 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" %)
259 -|(% 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
260 -|(% 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" %)
261 -|(% 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" %)
262 -|(% 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" %)
263 -|(% 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" %)
264 -|(% 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" %)
265 -|(% 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" %)
179 +|(% 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" %)(((
180 +Field9
266 266  
267 -== 3.4 [[Datacake>>https://datacake.co/]] ==
182 +
183 +)))|(% colspan="1" rowspan="1" %)(((
184 +Field10
268 268  
186 +
187 +)))
188 +|(% 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" %)
189 +|(% 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" %)
190 +|(% colspan="1" rowspan="1" %)DDS20-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
191 +Battery
269 269  
270 -(% class="wikigeneratedid" %)
271 -Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
193 +
194 +)))|(% 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" %)
195 +|(% colspan="1" rowspan="1" %)DDS45-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
196 +Battery
272 272  
198 +
199 +)))|(% 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" %)
200 +|(% colspan="1" rowspan="1" %)DDS75-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
201 +Battery
273 273  
274 -(% class="wikigeneratedid" %)
275 -As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
203 +
204 +)))|(% 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" %)
205 +|(% colspan="1" rowspan="1" %)NMDS120-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
206 +Battery
276 276  
277 -* (% 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.
208 +
209 +)))|(% 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" %)
210 +|(% 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" %)
211 +|(% 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" %)
212 +|(% 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" %)
213 +|(% 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" %)
214 +|(% 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
215 +|(% 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" %)
216 +|(% 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" %)
217 +|(% colspan="1" rowspan="1" %)mod2|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
218 +DS18B20 Temp
278 278  
279 -* (% 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.
220 +
221 +)))|(% colspan="1" rowspan="1" %)(((
222 +exit_state/input PA4
280 280  
281 -=== 3.4.1 For device Already has template ===
224 +
225 +)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
226 +|(% colspan="1" rowspan="1" %)mod3|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
227 +Battery
282 282  
283 -==== 3.4.1.1 Create Device ====
229 +
230 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
231 +exit_state/input PA4
284 284  
285 -(% style="color:blue" %)**Add Device**(%%) in DataCake.
233 +
234 +)))|(% colspan="1" rowspan="1" %)adc1|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)adc4|(% colspan="1" rowspan="1" %)
235 +|(% colspan="1" rowspan="1" %)mod4|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
236 +Battery
286 286  
287 -[[image:image-20230808162301-1.png||height="453" width="952"]]
238 +
239 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
240 +DS18B20 Temp
288 288  
242 +
243 +)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
244 +exit_state/input PA4
289 289  
290 -[[image:image-20230808162342-2.png||height="541" width="952"]]
246 +
247 +)))|(% colspan="1" rowspan="1" %)(((
248 +DS18B20 Temp2
291 291  
250 +
251 +)))|(% colspan="1" rowspan="1" %)(((
252 +DS18B20 Temp3
292 292  
293 -(% style="color:blue" %)**Choose the correct model**(%%) from template.
254 +
255 +)))|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
256 +|(% colspan="1" rowspan="1" %)mod5|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
257 +Battery
294 294  
295 -[[image:image-20230808162421-3.png]]
259 +
260 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
261 +DS18B20 Temp
296 296  
263 +
264 +)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
265 +exit_state/input PA4
297 297  
298 -(% 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.
267 +
268 +)))|(% colspan="1" rowspan="1" %)Weight|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
269 +|(% colspan="1" rowspan="1" %)mod6|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
270 +Battery
299 299  
300 -[[image:image-20230808163612-7.png||height="549" width="952"]]
272 +
273 +)))|(% 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" %)
301 301  
302 -[[image:image-20230808163035-5.png]]
303 303  
304 -[[image:image-20230808163049-6.png||height="544" width="926"]]
276 += 4. Datacake =
305 305  
278 +== 1.1 Define Product ==
306 306  
307 -=== 3.4.2 For Device already registered in DataCake before shipped ===
280 +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.1 Scan QR Code to get the device info ====
310 310  
311 -Users can use their phones or computers to scan QR codes to obtain device data information.
283 +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  
313 -[[image:image-20230808170051-8.png||height="255" width="259"]]
285 +[[image:image-20230802112413-14.png]]
314 314  
315 -[[image:image-20230808170548-9.png]]
287 +== 1.2 Create Device ==
316 316  
289 +In the second step you have to define the device which should be added to the product.
317 317  
318 -==== 3.4.2.2 Claim Device to User Account ====
291 +[[image:image-20230802112413-15.png]]
319 319  
320 -By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
293 +Enter a name here (such as "My First MQTT Device") and complete the creation of the device by clicking on the "Next" button.
321 321  
322 322  
296 +== 1.3 Create Database Fields ==
323 323  
324 -=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
298 +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  
326 -**Step1:Add a device**
300 +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".
327 327  
328 -[[image:image-20240129170024-1.png||height="330" width="900"]]
302 +[[image:image-20230802112413-16.png]]
329 329  
330 -**Step2:Choose your device type,please select dragino NB-IOT device**
304 +[[image:image-20230802112413-17.png]]
331 331  
332 -[[image:image-20240129170216-2.png||height="534" width="643"]]
306 +To create a first database field, please click on the "Add Field" button as marked in the screenshot above.
333 333  
334 -**Step3:Choose to create a new device**
308 +This will open another modal asking for some required input for your first field.
335 335  
336 -[[image:image-20240129170539-3.png||height="459" width="646"]]
310 +[[image:image-20230802112413-18.png]]
337 337  
338 -**Step4:Fill in the device ID of your NB device**
312 +[[image:image-20230802112413-19.png]]
339 339  
340 -[[image:image-20240202111546-1.png||height="378" width="651"]]
314 +== 1.4 Set up Broker ==
341 341  
342 -**Step5:Please select your device plan according to your needs and complete the creation of the device**
316 +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.
343 343  
344 -[[image:image-20240129171236-6.png||height="450" width="648"]]
318 +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.
345 345  
346 -**Step6:Please add the decoder at the payload decoder of the device configuration.**
320 +View your Personal Access Token
347 347  
348 -**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]]
322 +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:
349 349  
350 -[[image:image-20240129172056-7.png||height="457" width="816"]]
324 +[[image:image-20230802112413-20.png]]
351 351  
352 -[[image:image-20240129173116-9.png||height="499" width="814"]]
326 +MQTT Client-ID
353 353  
354 -**Step6:Add the output of the decoder as a field**
328 +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.
355 355  
356 -[[image:image-20240129173541-10.png||height="592" width="968"]]
330 +AT+CLIENT=“Any value”
357 357  
358 -**Step7:Customize the dashboard and use fields as parameters of the dashboard**
332 +AT+UNAME=Token
359 359  
360 -[[image:image-20240129174518-11.png||height="147" width="1042"]]
334 +AT+PWD=Token
361 361  
362 -[[image:image-20240129174657-12.png||height="538" width="916"]]
336 +[[image:image-20230802112413-21.png]]
363 363  
364 -[[image:image-20240129174840-13.png||height="536" width="750"]]
365 365  
339 +== 1.6 Create your first Subscription ==
366 366  
367 -=== 3.4.4 For device have not configured to connect to DataCake ===
341 +Subscribe
368 368  
369 -(% class="lead" %)
370 -Use AT command for connecting to DataCake
343 +Data is published according to the following structure:
371 371  
372 -(% style="color:blue" %)**AT+PRO=2,0**
345 +dtck~/~//
373 373  
374 -(% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
347 +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.
375 375  
376 376  
377 -== 3.5 Node-Red (via MQTT) ==
350 +[[image:image-20230802112413-22.png]]
378 378  
379 -=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
380 380  
353 +[[image:image-20230802112413-23.png]]
381 381  
382 -Take S31-NB UDP protocol as an example.
383 383  
384 -Dragino provides input flow examples for the sensors.
356 +[[image:image-20230802112413-24.png]]
385 385  
386 -User can download the required JSON file through Dragino Node-RED input flow template.
387 387  
388 -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]]
359 +example:
389 389  
390 -We can directly import the template.
361 +AT+PUBTOPIC=dtck-pub/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
391 391  
392 -The templates for S31-NB and NB95S31B are the same.
363 +[[image:image-20230802112413-25.png]]
393 393  
365 +== 1.7 Define Publish Topic ==
394 394  
395 -[[image:image-20230809173127-4.png]]
367 +Publish
396 396  
369 +To upload data into the Datacake Cloud and into a specific device, you publish the data to the respective topic structure.
397 397  
398 -Please select the NB95S31B template.
371 +Due to the nature of MQTT, the topic prefix differs as follows:
399 399  
400 -[[image:image-20230809173310-5.png||height="558" width="926"]]
373 +dtck-pub~/~//
401 401  
402 -[[image:image-20230809173438-6.png]]
375 +example:
403 403  
404 -[[image:image-20230809173800-7.png]]
377 +AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
405 405  
379 +== 1.8 upload data ==
406 406  
407 -Successfully imported template.
381 +[[image:image-20230802112413-26.png]]
408 408  
409 -[[image:image-20230809173835-8.png||height="515" width="860"]]
383 +[[image:image-20230802112413-27.png]]
410 410  
385 +[[image:image-20230802112413-28.png]]
411 411  
412 -Users can set UDP port.
387 += =
413 413  
414 -[[image:image-20230809174053-9.png]]
389 += 5. Node-Red (via MQTT) =
415 415  
416 416  
417 -=== 3.5.2 Simulate Connection ===
392 +== 1.1 Configure Node-Red ==
418 418  
394 +[[image:image-20230802112413-29.png]]
419 419  
420 -We have completed the configuration of UDP. We can try sending packets to node red.
396 +[[image:image-20230802112413-30.png]]
421 421  
422 -[[image:image-20230810083934-1.png]]
398 +== 1.2 Simulate Connection ==
423 423  
424 -[[image:image-20230810084048-2.png||height="535" width="1052"]]
400 +[[image:image-20230802112413-31.png]]
425 425  
402 +== 1.3 Configure NB-IoT Sensors ==
426 426  
427 -=== 3.5.3 Configure NB-IoT Sensors ===
404 +* AT+PRO=3,0(hex format) or 3,5(json format)    ~/~/Set to mqtt Server and  Payload
405 +* AT+CLIENT=any value
406 +* AT+UNAME=any value
407 +* AT+PWD=any value
408 +* AT+PUBTOPIC=any value
409 +* AT+SUBTOPIC=any value
428 428  
429 429  
430 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
431 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
432 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
433 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
434 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
435 -* (% style="color:#037691" %)**AT+PWD=“Your device token”**
412 += 6. ThingsBoard.Cloud (via MQTT) =
436 436  
437 -== 3.6 ThingsBoard.Cloud (via MQTT) ==
414 +== 1.1 Configure ThingsBoard ==
438 438  
439 -=== 3.6.1 Configure ThingsBoard ===
416 +=== 1.1.1 Create Device ===
440 440  
441 -==== 3.6.1.1 Create Device ====
418 +Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]].
442 442  
420 +[[image:image-20230802112413-32.png]]
443 443  
444 -Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
422 +=== 1.1.2 Create Uplink & Downlink Converter ===
445 445  
446 -[[image:image-20230802112413-32.png||height="583" width="1066"]]
424 +Uplink Converter
447 447  
448 -
449 -==== 3.6.1.2 Create Uplink & Downlink Converter ====
450 -
451 -
452 -(% style="color:blue" %)**Uplink Converter**
453 -
454 454  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.
455 455  
456 -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.
428 +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.
457 457  
458 -[[image:image-20230802112413-33.png||height="597" width="1061"]]
430 +[[image:image-20230802112413-33.png]]
459 459  
460 460  
461 -(% style="color:blue" %)**Downlink Converter**
433 +Downlink Converter
462 462  
463 463  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
464 464  
465 -[[image:image-20230802112413-34.png||height="598" width="1063"]]
437 +[[image:image-20230802112413-34.png]]
466 466  
467 -(% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
439 +Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.
468 468  
441 +=== 1.1.3 MQTT Integration Setup ===
469 469  
470 -==== 3.6.1.3 MQTT Integration Setup ====
443 +Go to the Integrations center -> Integrations page and click “plus” icon to add a new integration. Name it “MQTT Integration”, select type MQTT;
471 471  
445 +[[image:image-20230802112413-35.png]]
472 472  
473 -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**;
474 -
475 -[[image:image-20230802112413-35.png||height="597" width="1062"]]
476 -
477 -
478 478  * The next steps is to add the recently created uplink and downlink converters;
479 479  
480 -[[image:image-20230802112413-36.png||height="598" width="1062"]]
449 +[[image:image-20230802112413-36.png]]
481 481  
482 -[[image:image-20230802112413-37.png||height="598" width="1064"]]
451 +[[image:image-20230802112413-37.png]]
483 483  
453 +Add a topic filter:
484 484  
485 -(% style="color:blue" %)**Add a topic filter:**
486 486  
487 -Consistent with the theme of the node setting.
456 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。
488 488  
489 489  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
490 490  
491 -[[image:image-20230802112413-38.png||height="598" width="1064"]]
460 +[[image:image-20230802112413-38.png]]
492 492  
462 +== 1.2 Simulate with MQTT.fx ==
493 493  
494 -=== 3.6.2 Simulate with MQTT.fx ===
495 -
496 -
497 497  [[image:image-20230802112413-39.png]]
498 498  
499 -[[image:image-20230802112413-40.png||height="525" width="980"]]
466 +[[image:image-20230802112413-40.png]]
500 500  
468 +== 1.3 Configure NB-IoT Sensor ==
501 501  
502 -=== 3.6.3 Configure NB-IoT Sensor ===
470 +AT Commands
503 503  
472 +AT+PRO=3,3  ~/~/ Use MQTT to connect to ThingsBoard.
504 504  
505 -(% style="color:blue" %)**AT Commands**
474 +AT+SUBTOPIC=device name ~-~-> 只需要 Device Name 吗?对的
506 506  
507 -* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
476 +AT+PUBTOPIC=device name ~-~-> 只需要 Device Name 吗?对的
508 508  
509 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
510 510  
511 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
479 +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 吧).这边不用提示了，客户不需要输入。（大部分客户还是会自己去设置这个的，提高安全性）
512 512  
513 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
481 +CLIENT :“Any value”
514 514  
515 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
483 +User Name:“Any value”
516 516  
517 -* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
485 +Password:“Any value”
518 518  
487 +
519 519  Test Uplink by click the button for 1 second
520 520  
521 -[[image:image-20230802112413-41.png||height="496" width="828"]]
490 +[[image:image-20230802112413-41.png]]
522 522  
523 523  [[image:image-20230802112413-42.png]]
524 524  
525 -[[image:image-20230802112413-43.png||height="407" width="825"]]
494 +[[image:image-20230802112413-43.png]]
526 526  
527 527  
528 -== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
497 += 7. [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) =
529 529  
530 -=== 3.7.1 Create device & Get Credentials ===
499 +== 5.1 Create device & Get Credentials ==
531 531  
532 -
533 533  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.
534 534  
535 535  [[image:image-20230802112413-44.png]]
... ... @@ -536,6 +536,7 @@
536 536  
537 537  [[image:image-20230802112413-45.png]]
538 538  
507 += =
539 539  
540 540  Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
541 541  
... ... @@ -542,131 +542,58 @@
542 542  [[image:image-20230802112413-46.png]]
543 543  
544 544  
545 -The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
514 +On the Connection Profile window, set the following information: (这边加一个截图)
546 546  
547 -(% style="color:blue" %)**On the Connection Profile window, set the following information:**
516 +* Profile Name: “Any name”
517 +* Broker Address: mqtt.tago.io
518 +* Broker Port: 1883
519 +* Client ID: “Any value”
548 548  
549 -* (% style="color:#037691" %)**Profile Name: “Any name”**
550 550  
551 -* (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
522 +On the section User credentials, set the following information:(这边加一个截图)
552 552  
553 -* (% style="color:#037691" %)**Broker Port: 8883**
524 +* User Name: “Any value” Tago validates your user by the token only
525 +* Password: “Your device token”
526 +* PUBTOPIC: “Any value”
527 +* SUBTOPIC: “Any value”
554 554  
555 -* (% style="color:#037691" %)**Client ID: “Any value”**
556 556  
557 -(% style="color:blue" %)**On the section User credentials, set the following information:**
530 +== 5.2 Simulate with MQTT.fx ==
558 558  
559 -* (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
532 +[[image:image-20230802112413-47.png]]
560 560  
561 -* (% style="color:#037691" %)**Password: “Your device token”**
534 +[[image:image-20230802112413-48.png]]
562 562  
563 -* (% style="color:#037691" %)**PUBTOPIC: “Any value”**
536 +Users can run the AT+PRO=3,5 command, and the payload will be converted to JSON format.
564 564  
565 -* (% style="color:#037691" %)**SUBTOPIC: “Any value”**
538 +[[image:image-20230802112413-49.png]]
566 566  
567 -(% style="color:blue" %)**AT command:**
540 +== 1.4. tago data ==
568 568  
569 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
570 570  
571 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
543 +[[image:image-20230802112413-50.png]]
572 572  
573 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
545 +[[image:image-20230802112413-51.png]]
574 574  
575 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
547 +== 1.4. TLS mode ==
576 576  
577 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
549 +Users can choose to use SSL/TLS mode.
578 578  
579 -* (% style="color:#037691" %)**AT+PWD=“Your device token”**
551 +On the SSL/TLS section, check the option Enable SSL/TLS, and click OK.
580 580  
581 -=== 3.7.2 Simulate with MQTT.fx ===
553 +The device needs to enable the TLS mode and set the AT+TLSMOD=1,0 command.
582 582  
555 +* Profile Name: “Any name”
556 +* Broker Address: mqtt.tago.io
557 +* Broker Port: 8883
558 +* Client ID: “Any value”
559 +* User Name: “Any value” Tago validates your user by the token only
560 +* Password: “Your device token”
561 +* PUBTOPIC: “Any value”
562 +* SUBTOPIC: “Any value”
583 583  
564 +
584 584  [[image:image-20230802112413-52.png]]
585 585  
586 586  
587 -[[image:image-20230808105300-2.png||height="553" width="1026"]]
588 -
589 -
590 -Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
591 -
592 -[[image:image-20230808105217-1.png||height="556" width="1031"]]
593 -
594 -[[image:image-20230808105329-3.png]]
595 -
596 -
597 -=== 3.7.3 tago data ===
598 -
599 -
600 -[[image:image-20230802112413-50.png||height="242" width="1037"]]
601 -
602 -[[image:image-20230802112413-51.png||height="184" width="696"]]
603 -
604 -
605 -== 3.8 TCP Connection ==
606 -
607 -
608 -(% style="color:blue" %)**AT command:**
609 -
610 -* (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
611 -
612 -* (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
613 -
614 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
615 -
616 -(% style="color:blue" %)**Sensor Console Output when Uplink:**
617 -
618 -[[image:image-20230807233631-1.png]]
619 -
620 -
621 -(% style="color:blue" %)**See result in TCP Server:**
622 -
623 -[[image:image-20230807233631-2.png]]
624 -
625 -
626 -= 4. FAQ =
627 -
628 -== 4.1 What is the usage of Multi Sampling and One Uplink? ==
629 -
630 -The NB series has the feature for Multi Sampling and one uplink. See one of them
631 -
632 -[[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]]
633 -
634 -User can use this feature for below purpose:
635 -
636 -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.
637 -1. Give more sampling data points.
638 -1. Increase reliable in transmission. For example. If user set
639 -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)
640 -1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
641 -1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
642 -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.
643 -
644 -
645 -= 5. Trouble Shooting: =
646 -
647 -== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
648 -
649 -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.
650 -
651 -If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
652 -
653 -[[image:image-20240207002003-1.png]]
654 -
655 -
656 -If fail to attach network, it will shows signal 99. as below:
657 -
658 -[[image:image-20240207002129-2.png]]
659 -
660 -
661 -(% class="lead" %)
662 -When see this issue, below are the checklist:
663 -
664 -* 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.
665 -* 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]].
666 -* 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]].
667 -* Check if the device is attached to Carrier network but reject. (need to check with operator).
668 -* Check if the antenna is connected firmly.
669 -
670 -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.
671 -
672 672  
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