Last modified by Kilight Cao on 2025/07/23 16:27

From version 100.4
edited by Xiaoling
on 2023/08/15 17:06
Change comment: There is no comment for this version
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
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,105 +14,81 @@
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 19  
20 -To attache NB-IoT sensors to NB-IoT Network, You need to:
21 -
22 -1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
23 -1. Insert the SIM card to Sensor
24 -1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
25 -
26 -[[image:image-20230808205045-1.png||height="293" width="438"]]
27 -
28 -After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
29 -
30 30  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.
31 31  
32 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
33 -|(% 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**
34 -|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
35 -**[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
36 36  
37 -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
38 -)))|(% style="width:135px" %)
39 -|(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
40 -|(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
13 +== 2.1 1NCE SIM Card. ==
41 41  
42 42  
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| | |
43 43  
21 +
44 44  = 3. Configure to connect to different servers =
45 45  
46 -== 3.1 General UDP Connection ==
47 47  
25 += NB-IoT 服务器对接例子 =
48 48  
27 += 1. General UDP Connection =
28 +
49 49  The NB-IoT Sensor can send packet to server use UDP protocol.
50 50  
31 +== 1.1 Simulate UDP Connection by PC tool ==
51 51  
52 -=== 3.1.1 Simulate UDP Connection by PC tool ===
53 -
54 -
55 55  We can use PC tool to simulate UDP connection to make sure server works ok.
56 56  
57 57  [[image:image-20230802112413-1.png]]
58 58  
37 +== 1.2 Configure NB-IoT Sensor ==
59 59  
60 -=== 3.1.2 Configure NB-IoT Sensor ===
39 +=== 1.2.1 AT Commands ===
61 61  
62 -==== 3.1.2.1 AT Commands ====
41 +AT Commands:
63 63  
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
64 64  
65 -(% style="color:blue" %)**AT Commands:**
66 -
67 -* (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/  Set to use UDP protocol to uplink ,Payload Type select Hex payload
68 -
69 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
70 -
71 -* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
72 -
73 73  [[image:image-20230802112413-2.png]]
74 74  
49 +=== 1.2.2 Uplink Example ===
75 75  
76 -==== 3.1.2.2 Uplink Example ====
77 77  
78 -
79 79  [[image:image-20230802112413-3.png]]
80 80  
81 81  
82 -== 3.2 General MQTT Connection ==
55 += 2General MQTT Connection =
83 83  
84 -
85 85  The NB-IoT Sensor can send packet to server use MQTT protocol.
86 86  
87 -Below are the commands.
59 +Below are the commands
88 88  
89 -(% style="color:blue" %)**AT Commands:**
61 +AT Commands:
90 90  
91 -* (% 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
92 92  
93 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883**  (%%) ~/~/  Set MQTT server address and port
94 -
95 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT**     (%%) ~/~/  Set up the CLIENT of MQTT
96 -
97 -* (% style="color:#037691" %)**AT+UNAME=UNAME**        (%%) ~/~/  Set the username of MQTT
98 -
99 -* (% style="color:#037691" %)**AT+PWD=PWD**             (%%) ~/~/  Set the password of MQTT
100 -
101 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB**  (%%) ~/~/  Set the sending topic of MQTT
102 -
103 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB**  (%%) ~/~/  Set the subscription topic of MQTT
104 -
105 105  [[image:image-20230802112413-4.png]]
106 106  
107 107  [[image:image-20230802112413-5.png]]
108 108  
109 -(% 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.
110 110  
111 111  
112 -== 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
113 113  
114 -=== 3.3.1 Get MQTT Credentials ===
79 += 3. [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) =
115 115  
81 +== 1.1 Get MQTT Credentials ==
116 116  
117 117  [[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.
118 118  
... ... @@ -121,73 +121,58 @@
121 121  [[image:image-20230802112413-7.png]]
122 122  
123 123  
124 -=== 3.3.2 Simulate with MQTT.fx ===
90 +== 1.2Simulate with MQTT.fx ==
125 125  
126 -==== 3.3.2.1 Establish MQTT Connection ====
92 +=== 1.2.1 Establish MQTT Connection ===
127 127  
128 -
129 129  After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
130 130  
131 131  [[image:image-20230802112413-8.png]]
132 132  
133 -* (% 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>
134 134  
135 -* (% style="color:#037691" %)**Broker Port:**(%%) 1883
136 136  
137 -* (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID>
105 +=== 1.2.2 Publish Data to ThingSpeak Channel ===
138 138  
139 -* (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name>
140 -
141 -* (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
142 -
143 -
144 -
145 -==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
146 -
147 -
148 148  [[image:image-20230802112413-9.png]]
149 149  
150 150  [[image:image-20230802112413-10.png]]
151 151  
111 +In MQTT.fx, we can publish below info:
152 152  
153 -(% 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
154 154  
155 -* (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
156 156  
157 -* (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH
158 -
159 159  Where 63 and 67 are the value to be published to field1 & field2.
160 160  
161 161  
162 -(% style="color:blue" %)**Result: **
120 +Result:
163 163  
164 164  [[image:image-20230802112413-11.png]]
165 165  
166 166  
167 -=== 3.3.3 Configure NB-IoT Sensor for connection ===
125 +== 1.3 Configure NB-IoT Sensor for connection ==
168 168  
169 -==== 3.3.3.1 AT Commands: ====
127 +=== 1.3.1 AT Commands: ===
170 170  
171 -
172 172  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
173 173  
174 -* (% 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>
175 175  
176 -* (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
177 177  
178 -* (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
179 179  
180 -* (% style="color:blue" %)**AT+PWD=<Your ThingSpeaMQTT Password>**
140 +=== 1.3.2 Uplink Examples ===
181 181  
182 -* (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
183 -
184 -* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
185 -
186 -
187 -
188 -==== 3.3.3.2 Uplink Examples ====
189 -
190 -
191 191  For S31-NB
192 192  
193 193  For SE01-NB
... ... @@ -213,9 +213,8 @@
213 213  For SN50V3-NB
214 214  
215 215  
216 -==== 3.3.3.3 Map fields to sensor value ====
167 +=== 1.3.Map fields to sensor value ===
217 217  
218 -
219 219  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.
220 220  
221 221  
... ... @@ -226,327 +226,393 @@
226 226  
227 227  Below is the NB-IoT Product Table show the mapping.
228 228  
229 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
230 -|(% 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
231 -|(% 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" %)
232 -|(% 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" %)
233 -|(% 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" %)
234 -|(% 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" %)
235 -|(% 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" %)
236 -|(% 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" %)
237 -|(% 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" %)
238 -|(% 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" %)
239 -|(% 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" %)
240 -|(% 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" %)
241 -|(% 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
242 -|(% 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" %)
243 -|(% 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" %)
244 -|(% 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" %)
245 -|(% 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" %)
246 -|(% 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" %)
247 -|(% 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
248 248  
182 +
183 +)))|(% colspan="1" rowspan="1" %)(((
184 +Field10
249 249  
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
250 250  
251 -== 3.4 [[Datacake>>https://datacake.co/]] ==
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
252 252  
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
253 253  
254 -(% class="wikigeneratedid" %)
255 -Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
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
256 256  
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
257 257  
258 -(% class="wikigeneratedid" %)
259 -As example for S31B-NB. there are two versions: S31B-NB-1D and S31B-NB-GE.
220 +
221 +)))|(% colspan="1" rowspan="1" %)(((
222 +exit_state/input PA4
260 260  
261 -* (% 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.
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
262 262  
263 -* (% 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.
229 +
230 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
231 +exit_state/input PA4
264 264  
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
265 265  
238 +
239 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
240 +DS18B20 Temp
266 266  
267 -=== 3.4.1 Create device ===
242 +
243 +)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
244 +exit_state/input PA4
268 268  
246 +
247 +)))|(% colspan="1" rowspan="1" %)(((
248 +DS18B20 Temp2
269 269  
270 -(% style="color:blue" %)**Add Device**(%%) in DataCake.
250 +
251 +)))|(% colspan="1" rowspan="1" %)(((
252 +DS18B20 Temp3
271 271  
272 -[[image:image-20230808162301-1.png]]
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
273 273  
259 +
260 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
261 +DS18B20 Temp
274 274  
275 -[[image:image-20230808162342-2.png]]
263 +
264 +)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
265 +exit_state/input PA4
276 276  
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
277 277  
278 -(% style="color:blue" %)**Choose the correct model**(%%) from template.
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" %)
279 279  
280 -[[image:image-20230808162421-3.png]]
281 281  
276 += 4. Datacake =
282 282  
283 -(% 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.
278 +== 1.Define Product ==
284 284  
285 -[[image:image-20230808163612-7.png]]
280 +Firstly, we need to set the MQTT mode to datacakeand 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.
286 286  
287 -[[image:image-20230808163035-5.png]]
288 288  
289 -[[image:image-20230808163049-6.png]]
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".
290 290  
285 +[[image:image-20230802112413-14.png]]
291 291  
292 -=== 3.4.2 Scan QR code to obtain data ===
287 +== 1.2 Create Device ==
293 293  
289 +In the second step you have to define the device which should be added to the product.
294 294  
295 -Users can use their phones or computers to scan QR codes to obtain device data information.
291 +[[image:image-20230802112413-15.png]]
296 296  
297 -[[image:image-20230808170051-8.png||height="255" width="259"]]
293 +Enter a name here (such as "My First MQTT Device") and complete the creation of the device by clicking on the "Next" button.
298 298  
299 -[[image:image-20230808170548-9.png]]
300 300  
296 +== 1.3 Create Database Fields ==
301 301  
302 -=== 3.4.2 AT command for connecting to DataCake ===
298 +After creating the device, it is listed in the table of the fleet view. Noopen the device by clicking othe entry in the list.
303 303  
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".
304 304  
305 -(% style="color:blue" %)**AT+PRO=2,0**
302 +[[image:image-20230802112413-16.png]]
306 306  
307 -(% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
304 +[[image:image-20230802112413-17.png]]
308 308  
306 +To create a first database field, please click on the "Add Field" button as marked in the screenshot above.
309 309  
310 -== 3.5 Node-Red (via MQTT) ==
308 +This will open another modal asking for some required input for your first field.
311 311  
312 -=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
310 +[[image:image-20230802112413-18.png]]
313 313  
312 +[[image:image-20230802112413-19.png]]
314 314  
315 -Take S31-NB UDP protocol as an example.
314 +== 1.4 Set up Broker ==
316 316  
317 -Dragino provides input flow examples for the sensors.
316 +The broker is running on mqtt.datacake.co on ports 1883 and 8883. Port 1883 is unsecured and should not be used in productioenvironments. Port 8883 uses a CA signed server certificate.
318 318  
319 -User can download the required JSON file through Dragino Node-RED input flow template.
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.
320 320  
321 -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]]
320 +View youPersonal Access Token
322 322  
323 -We can directly import the template.
322 +You can view your own token via the User-Settings-Menu. You can reach thimenu by clicking on "Edit Profile" at the end of the list using the Workspace Selector:
324 324  
325 -The templates for S31-NB and NB95S31B are the same.
324 +[[image:image-20230802112413-20.png]]
326 326  
326 +MQTT Client-ID
327 327  
328 -[[image:image-20230809173127-4.png]]
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.
329 329  
330 +AT+CLIENT=“Any value”
330 330  
331 -Please select the NB95S31B template.
332 +AT+UNAME=Token
332 332  
333 -[[image:image-20230809173310-5.png]]
334 +AT+PWD=Token
334 334  
335 -[[image:image-20230809173438-6.png]]
336 +[[image:image-20230802112413-21.png]]
336 336  
337 -[[image:image-20230809173800-7.png]]
338 338  
339 +== 1.6 Create your first Subscription ==
339 339  
340 -Successfully imported template.
341 +Subscribe
341 341  
342 -[[image:image-20230809173835-8.png]]
343 +Data is published according to the following structure:
343 343  
345 +dtck~/~//
344 344  
345 -Users can set UDP port.
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.
346 346  
347 -[[image:image-20230809174053-9.png]]
348 348  
350 +[[image:image-20230802112413-22.png]]
349 349  
350 -=== 3.5.2 Simulate Connection ===
351 351  
353 +[[image:image-20230802112413-23.png]]
352 352  
353 -We have completed the configuration of UDP. We can try sending packets to node red.
354 354  
355 -[[image:image-20230810083934-1.png]]
356 +[[image:image-20230802112413-24.png]]
356 356  
357 -[[image:image-20230810084048-2.png]]
358 358  
359 -=== 3.5.3 Configure NB-IoT Sensors ===
359 +example:
360 360  
361 +AT+PUBTOPIC=dtck-pub/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
361 361  
362 -* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
363 +[[image:image-20230802112413-25.png]]
363 363  
364 -* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
365 +== 1.7 Define Publish Topic ==
365 365  
366 -== 3.6 ThingsBoard.Cloud (via MQTT) ==
367 +Publish
367 367  
368 -=== 3.6.1 ConfigurThingsBoard ===
369 +To upload data into the Datacake Cloud and into a specific device, you publish thdata to the respective topic structure.
369 369  
370 -==== 3.6.1.1 Create Device ====
371 +Due to the naturof MQTT, the topic prefix differs as follows:
371 371  
373 +dtck-pub~/~//
372 372  
373 -Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
375 +example:
374 374  
375 -[[image:image-20230802112413-32.png]]
377 +AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
376 376  
379 +== 1.8 upload data ==
377 377  
378 -==== 3.6.1.2 Create Uplink & Downlink Converter ====
381 +[[image:image-20230802112413-26.png]]
379 379  
383 +[[image:image-20230802112413-27.png]]
380 380  
381 -(% style="color:blue" %)**Uplink Converter**
385 +[[image:image-20230802112413-28.png]]
382 382  
383 -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.
387 += =
384 384  
385 -To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page anclick (% 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.
389 += 5. Node-Red (via MQTT) =
386 386  
387 -[[image:image-20230802112413-33.png||height="732" width="1302"]]
388 388  
392 +== 1.1 Configure Node-Red ==
389 389  
390 -(% style="color:blue" %)**Downlink Converter**
394 +[[image:image-20230802112413-29.png]]
391 391  
392 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
396 +[[image:image-20230802112413-30.png]]
393 393  
394 -[[image:image-20230802112413-34.png||height="734" width="1305"]]
398 +== 1.2 Simulate Connection ==
395 395  
396 -(% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
400 +[[image:image-20230802112413-31.png]]
397 397  
402 +== 1.3 Configure NB-IoT Sensors ==
398 398  
399 -==== 3.6.1.3 MQTT Integration Setup ====
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
400 400  
401 401  
402 -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**;
412 += 6. ThingsBoard.Clou(via MQTT) =
403 403  
404 -[[image:image-20230802112413-35.png||height="738" width="1312"]]
414 +== 1.1 Configure ThingsBoard ==
405 405  
416 +=== 1.1.1 Create Device ===
406 406  
407 -* The next steps is to add threcently created uplinand downlink converters;
418 +Create a New Device i[[ThingsBoard>>url:https://thingsboard.cloud/]].
408 408  
409 -[[image:image-20230802112413-36.png||height="736" width="1308"]]
420 +[[image:image-20230802112413-32.png]]
410 410  
411 -[[image:image-20230802112413-37.png||height="735" width="1307"]]
422 +=== 1.1.2 Create Uplink & Downlink Converter ===
412 412  
424 +Uplink Converter
413 413  
414 -(% style="color:blue" %)**Add a topic filter:**
426 +The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consumedeviceName andeviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
415 415  
416 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
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 modfor now.
417 417  
418 -You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
430 +[[image:image-20230802112413-33.png]]
419 419  
420 -[[image:image-20230802112413-38.png||height="731" width="1300"]]
421 421  
433 +Downlink Converter
422 422  
423 -=== 3.6.2 Simulate with MQTT.fx ===
435 +The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
424 424  
437 +[[image:image-20230802112413-34.png]]
425 425  
426 -[[image:image-20230802112413-39.png]]
439 +Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.
427 427  
428 -[[image:image-20230802112413-40.png]]
441 +=== 1.1.3 MQTT Integration Setup ===
429 429  
443 +Go to the Integrations center -> Integrations page and click “plus” icon to add a new integration. Name it “MQTT Integration”, select type MQTT;
430 430  
431 -=== 3.6.3 Configure NB-IoT Sensor ===
445 +[[image:image-20230802112413-35.png]]
432 432  
447 +* The next steps is to add the recently created uplink and downlink converters;
433 433  
434 -(% style="color:blue" %)**AT Commands**
449 +[[image:image-20230802112413-36.png]]
435 435  
436 -* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
451 +[[image:image-20230802112413-37.png]]
437 437  
438 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
453 +Add a topic filter:
439 439  
440 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
441 441  
442 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
456 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。
443 443  
444 -* (% style="color:#037691" %)**AT+UNAME=<devicname> or User Defined**
458 +You can also select an MQTT Qolevel. We use MQTT QoS level 0 (At most once) by default;
445 445  
446 -* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
460 +[[image:image-20230802112413-38.png]]
447 447  
448 -Test Uplink by click thbutton for 1 second
462 +== 1.2 Simulate with MQTT.fx ==
449 449  
450 -[[image:image-20230802112413-41.png]]
464 +[[image:image-20230802112413-39.png]]
451 451  
452 -[[image:image-20230802112413-42.png]]
466 +[[image:image-20230802112413-40.png]]
453 453  
454 -[[image:image-20230802112413-43.png]]
468 +== 1.3 Configure NB-IoT Sensor ==
455 455  
470 +AT Commands
456 456  
457 -== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
472 +AT+PRO=3,3  ~/~/ Use MQTT to connect to ThingsBoard.
458 458  
459 -=== 3.7.1 Create device & Get Credentials ===
474 +AT+SUBTOPIC=device nam~-~-> 只需要 Device Name 吗?对的
460 460  
476 +AT+PUBTOPIC=device name ~-~-> 只需要 Device Name 吗?对的
461 461  
462 -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.
463 463  
464 -[[image:image-20230802112413-44.png]]
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 吧).这边不用提示了,客户不需要输入。(大部分客户还是会自己去设置这个的,提高安全性)
465 465  
466 -[[image:image-20230802112413-45.png]]
481 +CLIENT :“Any value
467 467  
483 +User Name:“Any value”
468 468  
469 -Go to the Device section and create a device. Then, go to the section tokens and copyour device-token.
485 +Password:“Any value
470 470  
471 -[[image:image-20230802112413-46.png]]
472 472  
488 +Test Uplink by click the button for 1 second
473 473  
474 -The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
490 +[[image:image-20230802112413-41.png]]
475 475  
476 -(% style="color:blue" %)**On the Connection Profile window, set the following information:**
492 +[[image:image-20230802112413-42.png]]
477 477  
478 -* (% style="color:#037691" %)**Profile Name: “Any name”**
494 +[[image:image-20230802112413-43.png]]
479 479  
480 -* (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
481 481  
482 -* (% style="color:#037691" %)**Broker Port: 8883**
497 += 7. [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) =
483 483  
484 -* (% style="color:#037691" %)**ClienID: “Any value”**
499 +== 5.1 Create device & Get Credentials ==
485 485  
486 -(% style="color:blue" %)**On the section User credentials, sethe following information:**
501 +We usMQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.
487 487  
488 -* (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
503 +[[image:image-20230802112413-44.png]]
489 489  
490 -* (% style="color:#037691" %)**Password: “Your device token”**
505 +[[image:image-20230802112413-45.png]]
491 491  
492 -* (% style="color:#037691" %)**PUBTOPIC: “Any value”**
507 += =
493 493  
494 -* (% style="color:#037691" %)**SUBTOPIC: “Any value”**
509 +Go to the Device section and create a device. Then, go to the sectiotokens and copy your device-token.
495 495  
496 -(% style="color:blue" %)**AT command:**
511 +[[image:image-20230802112413-46.png]]
497 497  
498 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
499 499  
500 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
514 +On the ConnectioProfilwindow, set the following information: (这边加一个截图)
501 501  
502 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
516 +* Profile Name: “Any name”
517 +* Broker Address: mqtt.tago.io
518 +* Broker Port: 1883
519 +* Client ID: “Any value”
503 503  
504 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
505 505  
506 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
522 +On the sectioUsecredentials, set the following information:(这边加一个截图)
507 507  
508 -* (% style="color:#037691" %)**AT+PWD=“Your device token”**
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”
509 509  
510 -=== 3.7.2 Simulate with MQTT.fx ===
511 511  
530 +== 5.2 Simulate with MQTT.fx ==
512 512  
513 -[[image:image-20230802112413-52.png]]
532 +[[image:image-20230802112413-47.png]]
514 514  
534 +[[image:image-20230802112413-48.png]]
515 515  
516 -[[image:image-20230808105300-2.png]]
536 +Users can run the AT+PRO=3,5 command, and the payload will be converted to JSON format.
517 517  
538 +[[image:image-20230802112413-49.png]]
518 518  
519 -Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
540 +== 1.4. tago data ==
520 520  
521 -[[image:image-20230808105217-1.png]]
522 522  
523 -[[image:image-20230808105329-3.png]]
524 -
525 -
526 -=== 3.7.3 tago data ===
527 -
528 -
529 529  [[image:image-20230802112413-50.png]]
530 530  
531 -[[image:image-20230802112413-51.png||height="184" width="696"]]
545 +[[image:image-20230802112413-51.png]]
532 532  
547 +== 1.4. TLS mode ==
533 533  
534 -== 3.8 TCP Connection ==
549 +Users can choose to use SSL/TLS mode.
535 535  
551 +On the SSL/TLS section, check the option Enable SSL/TLS, and click OK.
536 536  
537 -(% style="color:blue" %)**AT command:**
553 +The device needs to enable the TLS mode and set the AT+TLSMOD=1,0 command.
538 538  
539 -* (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
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”
540 540  
541 -* (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
542 542  
543 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
565 +[[image:image-20230802112413-52.png]]
544 544  
545 -(% style="color:blue" %)**Sensor Console Output when Uplink:**
546 546  
547 -[[image:image-20230807233631-1.png]]
548 -
549 -
550 -(% style="color:blue" %)**See result in TCP Server:**
551 -
552 -[[image:image-20230807233631-2.png]]
568 +
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