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

From version 53.7
edited by Xiaoling
on 2023/08/02 11:49
Change comment: There is no comment for this version
To version 100.4
edited by Xiaoling
on 2023/08/15 17:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
1 -(% class="wikigeneratedid" %)
1 +(% class="wikigeneratedid" id="HTableofContents:" %)
2 2  **Table of Contents:**
3 3  
4 4  {{toc/}}
... ... @@ -5,6 +5,9 @@
5 5  
6 6  
7 7  
8 +
9 +
10 +
8 8  = 1. The use of this guideline =
9 9  
10 10  
... ... @@ -11,21 +11,33 @@
11 11  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.
12 12  
13 13  
14 -= 2. Network Connection =
17 += 2. Attach Network =
15 15  
16 16  
17 -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.
20 +To attache NB-IoT sensors to NB-IoT Network, You need to:
18 18  
19 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
20 -|(% style="background-color:#4f81bd; color:white" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white" %)**APN**|(% style="background-color:#4f81bd; color:white" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white" %)**Comments**
21 -|1NCE| | |
22 -|China Mobile| | |
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>)
23 23  
26 +[[image:image-20230808205045-1.png||height="293" width="438"]]
24 24  
25 -== 2.1 1NCE SIM Card. ==
28 +After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
26 26  
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.
27 27  
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]]**
28 28  
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" %)
41 +
42 +
43 +
29 29  = 3. Configure to connect to different servers =
30 30  
31 31  == 3.1 General UDP Connection ==
... ... @@ -50,7 +50,9 @@
50 50  (% style="color:blue" %)**AT Commands:**
51 51  
52 52  * (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/  Set to use UDP protocol to uplink ,Payload Type select Hex payload
68 +
53 53  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
70 +
54 54  * (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
55 55  
56 56  [[image:image-20230802112413-2.png]]
... ... @@ -69,27 +69,34 @@
69 69  
70 70  Below are the commands.
71 71  
72 -**AT Commands:**
89 +(% style="color:blue" %)**AT Commands:**
73 73  
74 -* **AT+PRO=3,0**  ~/~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
75 -* **AT+SERVADDR=120.24.4.116,1883**    ~/~/  Set MQTT server address and port
76 -* **AT+CLIENT=CLIENT**  ~/~/  Set up the CLIENT of MQTT
77 -* **AT+UNAME=UNAME**  ~/~/  Set the username of MQTT
78 -* **AT+PWD=PWD**  ~/~/  Set the password of MQTT
79 -* **AT+PUBTOPIC=NSE01_PUB**  ~/~/  Set the sending topic of MQTT
80 -* **AT+SUBTOPIC=NSE01_SUB**  ~/~/  Set the subscription topic of MQTT
91 +* (% style="color:#037691" %)**AT+PRO=3,0**   (%%) ~/~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
81 81  
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 +
82 82  [[image:image-20230802112413-4.png]]
83 83  
84 84  [[image:image-20230802112413-5.png]]
85 85  
86 -**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.**
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.**
87 87  
88 88  
89 89  == 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
90 90  
91 -== 1.1 Get MQTT Credentials ==
114 +=== 3.3.1 Get MQTT Credentials ===
92 92  
116 +
93 93  [[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.
94 94  
95 95  [[image:image-20230802112413-6.png]]
... ... @@ -97,54 +97,73 @@
97 97  [[image:image-20230802112413-7.png]]
98 98  
99 99  
100 -== 1.2. Simulate with MQTT.fx ==
124 +=== 3.3.2 Simulate with MQTT.fx ===
101 101  
102 -=== 1.2.1 Establish MQTT Connection ===
126 +==== 3.3.2.1 Establish MQTT Connection ====
103 103  
128 +
104 104  After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
105 105  
106 106  [[image:image-20230802112413-8.png]]
107 107  
108 -* Broker Address: mqtt3.thingspeak.com
109 -* Broker Port: 1883
110 -* Client ID: <Your ThingSpeak MQTT ClientID>
111 -* User Name: <Your ThingSpeak MQTT User Name>
112 -* Password: <Your ThingSpeak MQTT Password>
133 +* (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
113 113  
114 -=== 1.2.2 Publish Data to ThingSpeak Channel ===
135 +* (% style="color:#037691" %)**Broker Port:**(%%) 1883
115 115  
137 +* (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID>
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 +
116 116  [[image:image-20230802112413-9.png]]
117 117  
118 118  [[image:image-20230802112413-10.png]]
119 119  
120 -In MQTT.fx, we can publish below info:
121 121  
122 -* Topic: channels/YOUR_CHANNEL_ID/publish
123 -* Payload: field1=63&field2=67&status=MQTTPUBLISH
153 +(% style="color:blue" %)**In MQTT.fx, we can publish below info:**
124 124  
155 +* (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
156 +
157 +* (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH
158 +
125 125  Where 63 and 67 are the value to be published to field1 & field2.
126 126  
127 127  
128 -Result:
162 +(% style="color:blue" %)**Result: **
129 129  
130 130  [[image:image-20230802112413-11.png]]
131 131  
132 132  
133 -== 1.3 Configure NB-IoT Sensor for connection ==
167 +=== 3.3.3 Configure NB-IoT Sensor for connection ===
134 134  
135 -=== 1.3.1 AT Commands: ===
169 +==== 3.3.3.1 AT Commands: ====
136 136  
171 +
137 137  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
138 138  
139 -* AT+PRO=3,1   ~/~/Set to use ThingSpeak Server and Related Payload
140 -* AT+CLIENT=<Your ThingSpeak MQTT ClientID>
141 -* AT+UNAME=<Your ThingSpeak MQTT User Name>
142 -* AT+PWD=<Your ThingSpeak MQTT Password>
143 -* AT+PUBTOPIC=<YOUR_CHANNEL_ID>
144 -* AT+SUBTOPIC=<YOUR_CHANNEL_ID>
174 +* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
145 145  
146 -=== 1.3.2 Uplink Examples ===
176 +* (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeaMQTT ClientID>**
147 147  
178 +* (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
179 +
180 +* (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>**
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 +
148 148  For S31-NB
149 149  
150 150  For SE01-NB
... ... @@ -170,8 +170,9 @@
170 170  For SN50V3-NB
171 171  
172 172  
173 -=== 1.3.Map fields to sensor value ===
216 +==== 3.3.3.3 Map fields to sensor value ====
174 174  
218 +
175 175  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.
176 176  
177 177  
... ... @@ -182,388 +182,327 @@
182 182  
183 183  Below is the NB-IoT Product Table show the mapping.
184 184  
185 -|(% 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" %)(((
186 -Field9
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" %)
187 187  
188 -
189 -)))|(% colspan="1" rowspan="1" %)(((
190 -Field10
191 191  
192 -
193 -)))
194 -|(% 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" %)
195 -|(% 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" %)
196 -|(% colspan="1" rowspan="1" %)DDS20-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
197 -Battery
198 198  
199 -
200 -)))|(% 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" %)
201 -|(% colspan="1" rowspan="1" %)DDS45-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
202 -Battery
251 +== 3.4 [[Datacake>>https://datacake.co/]] ==
203 203  
204 -
205 -)))|(% 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" %)
206 -|(% colspan="1" rowspan="1" %)DDS75-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
207 -Battery
208 208  
209 -
210 -)))|(% 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" %)
211 -|(% colspan="1" rowspan="1" %)NMDS120-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
212 -Battery
254 +(% class="wikigeneratedid" %)
255 +Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
213 213  
214 -
215 -)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
216 -|(% colspan="1" rowspan="1" %)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" %)
217 -|(% 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" %)
218 -|(% 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" %)
219 -|(% 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" %)
220 -|(% 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
221 -|(% 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" %)
222 -|(% 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" %)
223 -|(% colspan="1" rowspan="1" %)mod2|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
224 -DS18B20 Temp
225 225  
226 -
227 -)))|(% colspan="1" rowspan="1" %)(((
228 -exit_state/input PA4
258 +(% class="wikigeneratedid" %)
259 +As example for S31B-NB. there are two versions: S31B-NB-1D and S31B-NB-GE.
229 229  
230 -
231 -)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
232 -|(% colspan="1" rowspan="1" %)mod3|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
233 -Battery
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.
234 234  
235 -
236 -)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
237 -exit_state/input PA4
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.
238 238  
239 -
240 -)))|(% colspan="1" rowspan="1" %)adc1|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)adc4|(% colspan="1" rowspan="1" %)
241 -|(% colspan="1" rowspan="1" %)mod4|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
242 -Battery
243 243  
244 -
245 -)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
246 -DS18B20 Temp
247 247  
248 -
249 -)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
250 -exit_state/input PA4
267 +=== 3.4.1 Create device ===
251 251  
252 -
253 -)))|(% colspan="1" rowspan="1" %)(((
254 -DS18B20 Temp2
255 255  
256 -
257 -)))|(% colspan="1" rowspan="1" %)(((
258 -DS18B20 Temp3
270 +(% style="color:blue" %)**Add Device**(%%) in DataCake.
259 259  
260 -
261 -)))|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
262 -|(% colspan="1" rowspan="1" %)mod5|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
263 -Battery
272 +[[image:image-20230808162301-1.png]]
264 264  
265 -
266 -)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
267 -DS18B20 Temp
268 268  
269 -
270 -)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
271 -exit_state/input PA4
275 +[[image:image-20230808162342-2.png]]
272 272  
273 -
274 -)))|(% colspan="1" rowspan="1" %)Weight|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
275 -|(% colspan="1" rowspan="1" %)mod6|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
276 -Battery
277 277  
278 -
279 -)))|(% 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" %)
278 +(% style="color:blue" %)**Choose the correct model**(%%) from template.
280 280  
281 -= 4. Datacake =
280 +[[image:image-20230808162421-3.png]]
282 282  
283 -== 1.1 Define Product ==
284 284  
285 -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 runninthe command, the device automatically sets the server address, port.
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.
286 286  
285 +[[image:image-20230808163612-7.png]]
287 287  
288 -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".
287 +[[image:image-20230808163035-5.png]]
289 289  
290 -[[image:image-20230802112413-14.png]]
289 +[[image:image-20230808163049-6.png]]
291 291  
292 -== 1.2 Create Device ==
293 293  
294 -In the second step you have to define the device which should badded to the product.
292 +=== 3.4.2 Scan QR code to obtain data ===
295 295  
296 -[[image:image-20230802112413-15.png]]
297 297  
298 -Enter a name here (such as "My First MQTT Device") ancompletthe creation of the device by clickinothe "Next" button.
295 +Users can use their phones or computers to scan QR codes to obtain device data information.
299 299  
297 +[[image:image-20230808170051-8.png||height="255" width="259"]]
300 300  
301 -== 1.3 Create Database Fields ==
299 +[[image:image-20230808170548-9.png]]
302 302  
303 -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.
304 304  
305 -You will then see a device view with an empty dashboard. Now, the first thing we want to do inavigate to the Device configuration. To do this, use the tab bar and click on "Configuration".
302 +=== 3.4.2 AT command for connecting to DataCake ===
306 306  
307 -[[image:image-20230802112413-16.png]]
308 308  
309 -[[image:image-20230802112413-17.png]]
305 +(% style="color:blue" %)**AT+PRO=2,0**
310 310  
311 -To create a first database field, please click on the "Add Field" button as marked in the screenshot above.
307 +(% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
312 312  
313 -This will open another modal asking for some required input for your first field.
314 314  
315 -[[image:image-20230802112413-18.png]]
310 +== 3.5 Node-Red (via MQTT) ==
316 316  
317 -[[image:image-20230802112413-19.png]]
312 +=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
318 318  
319 -== 1.4 Set up Broker ==
320 320  
321 -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.
315 +Take S31-NB UDP protocol as an example.
322 322  
323 -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.
317 +Dragino provides input flow examples for the sensors.
324 324  
325 -View your Personal Access Token
319 +User can download the required JSON file through Dragino Node-RED input flow template.
326 326  
327 -You can view your own token via the User-Settings-Menu. Yocan reach this menu by clicking on "Edit Profile" at the end of the lisusing the Workspace Selector:
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]]
328 328  
329 -[[image:image-20230802112413-20.png]]
323 +We can directly import the template.
330 330  
331 -MQTT Client-ID
325 +The templates for S31-NB and NB95S31B are the same.
332 332  
333 -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.
334 334  
335 -AT+CLIENT=“Any value
328 +[[image:image-20230809173127-4.png]]
336 336  
337 -AT+UNAME=Token
338 338  
339 -AT+PWD=Token
331 +Please select the NB95S31B template.
340 340  
341 -[[image:image-20230802112413-21.png]]
333 +[[image:image-20230809173310-5.png]]
342 342  
335 +[[image:image-20230809173438-6.png]]
343 343  
344 -== 1.6 Create your first Subscription ==
337 +[[image:image-20230809173800-7.png]]
345 345  
346 -Subscribe
347 347  
348 -Data is published according to the following structure:
340 +Successfully imported template.
349 349  
350 -dtck~/~//
342 +[[image:image-20230809173835-8.png]]
351 351  
352 -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.
353 353  
345 +Users can set UDP port.
354 354  
355 -[[image:image-20230802112413-22.png]]
347 +[[image:image-20230809174053-9.png]]
356 356  
357 357  
358 -[[image:image-20230802112413-23.png]]
350 +=== 3.5.2 Simulate Connection ===
359 359  
360 360  
361 -[[image:image-20230802112413-24.png]]
353 +We have completed the configuration of UDP. We can try sending packets to node red.
362 362  
355 +[[image:image-20230810083934-1.png]]
363 363  
364 -example:
357 +[[image:image-20230810084048-2.png]]
365 365  
366 -AT+PUBTOPIC=dtck-pub/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
359 +=== 3.5.3 Configure NB-IoT Sensors ===
367 367  
368 -[[image:image-20230802112413-25.png]]
369 369  
370 -== 1.7 Define Publish Topic ==
362 +* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
371 371  
372 -Publish
364 +* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
373 373  
374 -To upload data into the Datacake Cloud and into a specific device, you publish the data to the respective topic structure.
366 +== 3.6 ThingsBoard.Cloud (via MQTT) ==
375 375  
376 -Due to the nature of MQTT, the topic prefix differs as follows:
368 +=== 3.6.1 Configure ThingsBoard ===
377 377  
378 -dtck-pub~/~//
370 +==== 3.6.1.1 Create Device ====
379 379  
380 -example:
381 381  
382 -AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
373 +Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
383 383  
384 -== 1.8 upload data ==
375 +[[image:image-20230802112413-32.png]]
385 385  
386 -[[image:image-20230802112413-26.png]]
387 387  
388 -[[image:image-20230802112413-27.png]]
378 +==== 3.6.1.2 Create Uplink & Downlink Converter ====
389 389  
390 -[[image:image-20230802112413-28.png]]
391 391  
392 -= =
381 +(% style="color:blue" %)**Uplink Converter**
393 393  
394 -= 5. Node-Red (via MQTT) =
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.
395 395  
385 +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.
396 396  
397 -== 1.1 Configure Node-Red ==
387 +[[image:image-20230802112413-33.png||height="732" width="1302"]]
398 398  
399 -[[image:image-20230802112413-29.png]]
400 400  
401 -[[image:image-20230802112413-30.png]]
390 +(% style="color:blue" %)**Downlink Converter**
402 402  
403 -== 1.2 Simulate Connection ==
392 +The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
404 404  
405 -[[image:image-20230802112413-31.png]]
394 +[[image:image-20230802112413-34.png||height="734" width="1305"]]
406 406  
407 -== 1.3 Configure NB-IoSensors ==
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.**
408 408  
409 -* AT+PRO=3,0(hex format) or 3,5(json format)    ~/~/Set to mqtt Server and  Payload
410 -* AT+CLIENT=any value
411 -* AT+UNAME=any value
412 -* AT+PWD=any value
413 -* AT+PUBTOPIC=any value
414 -* AT+SUBTOPIC=any value
415 415  
416 -= 6. ThingsBoard.Cloud (via MQTT) =
399 +==== 3.6.1.3 MQTT Integration Setup ====
417 417  
418 -== 1.1 Configure ThingsBoard ==
419 419  
420 -=== 1.1.1 Create Device ===
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**;
421 421  
422 -Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]].
404 +[[image:image-20230802112413-35.png||height="738" width="1312"]]
423 423  
424 -[[image:image-20230802112413-32.png]]
425 425  
426 -=== 1.1.2 Create Uplink & Downlink Converter ===
407 +* The next steps is to add the recently created uplink and downlink converters;
427 427  
428 -Uplink Converter
409 +[[image:image-20230802112413-36.png||height="736" width="1308"]]
429 429  
430 -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.
411 +[[image:image-20230802112413-37.png||height="735" width="1307"]]
431 431  
432 -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.
433 433  
434 -[[image:image-20230802112413-33.png]]
414 +(% style="color:blue" %)**Add a topic filter:**
435 435  
416 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
436 436  
437 -Downlink Converter
418 +You can also select aMQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
438 438  
439 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
420 +[[image:image-20230802112413-38.png||height="731" width="1300"]]
440 440  
441 -[[image:image-20230802112413-34.png]]
442 442  
443 -Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.
423 +=== 3.6.2 Simulate with MQTT.fx ===
444 444  
445 -=== 1.1.3 MQTT Integration Setup ===
446 446  
447 -Go to the Integrations center -> Integrations page and click “plus” icon to add a new integration. Name it “MQTT Integration”, select type MQTT;
426 +[[image:image-20230802112413-39.png]]
448 448  
449 -[[image:image-20230802112413-35.png]]
428 +[[image:image-20230802112413-40.png]]
450 450  
451 -* The next steps is to add the recently created uplink and downlink converters;
452 452  
453 -[[image:image-20230802112413-36.png]]
431 +=== 3.6.3 Configure NB-IoT Sensor ===
454 454  
455 -[[image:image-20230802112413-37.png]]
456 456  
457 -Add a topic filter:
434 +(% style="color:blue" %)**AT Commands**
458 458  
436 +* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
459 459  
460 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。
438 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
461 461  
462 -You can also select an MQTT Qolevel. We use MQTT QoS level 0 (At most once) by default;
440 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
463 463  
464 -[[image:image-20230802112413-38.png]]
442 +* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
465 465  
466 -== 1.2 Simulatwith MQTT.fx ==
444 +* (% style="color:#037691" %)**AT+UNAME=<devicname> or User Defined**
467 467  
468 -[[image:image-20230802112413-39.png]]
446 +* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
469 469  
470 -[[image:image-20230802112413-40.png]]
448 +Test Uplink by click the button for 1 second
471 471  
472 -== 1.3 Configure NB-IoT Sensor ==
450 +[[image:image-20230802112413-41.png]]
473 473  
474 -AT Commands
452 +[[image:image-20230802112413-42.png]]
475 475  
476 -AT+PRO=3,3  ~/~/ Use MQTT to connect to ThingsBoard.
454 +[[image:image-20230802112413-43.png]]
477 477  
478 -AT+SUBTOPIC=device name ~-~-> 只需要 Device Name 吗?对的
479 479  
480 -AT+PUBTOPIC=device name ~-~-> 只需要 Device Name 吗?对的
457 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
481 481  
459 +=== 3.7.1 Create device & Get Credentials ===
482 482  
483 -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 吧).这边不用提示了,客户不需要输入。(大部分客户还是会自己去设置这个的,提高安全性)
484 484  
485 -CLIENT :“Any value
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.
486 486  
487 -User Name:“Any value
464 +[[image:image-20230802112413-44.png]]
488 488  
489 -Password:“Any value
466 +[[image:image-20230802112413-45.png]]
490 490  
491 491  
492 -Test Uplink by click the button for 1 second
469 +Go to the Device sectioand create a device. Then, go to the section tokens and copy youdevice-token.
493 493  
494 -[[image:image-20230802112413-41.png]]
471 +[[image:image-20230802112413-46.png]]
495 495  
496 -[[image:image-20230802112413-42.png]]
497 497  
498 -[[image:image-20230802112413-43.png]]
474 +The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
499 499  
476 +(% style="color:blue" %)**On the Connection Profile window, set the following information:**
500 500  
501 -= 7. [[Tago.io>>url:https://admin.tago.io/]] (viMQTT) =
478 +* (% style="color:#037691" %)**Profile Name: “Any name”**
502 502  
503 -== 5.1 Create device & Get Credentials ==
480 +* (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
504 504  
505 -We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. Wneed to Create Device and Get MQTT Credentials first.
482 +* (% style="color:#037691" %)**Broker Port: 8883**
506 506  
507 -[[image:image-20230802112413-44.png]]
484 +* (% style="color:#037691" %)**Client ID: “Any value”**
508 508  
509 -[[image:image-20230802112413-45.png]]
486 +(% style="color:blue" %)**On the section User credentials, set the following information:**
510 510  
511 -= =
488 +* (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
512 512  
513 -Go to the Device section and create a device. Then, go to the section tokens ancopy your device-token.
490 +* (% style="color:#037691" %)**Password: “Your device token”**
514 514  
515 -[[image:image-20230802112413-46.png]]
492 +* (% style="color:#037691" %)**PUBTOPIC: “Any value”**
516 516  
494 +* (% style="color:#037691" %)**SUBTOPIC: “Any value”**
517 517  
518 -On the Connection Profile window, set the following information: (这边加一个截图)
496 +(% style="color:blue" %)**AT command:**
519 519  
520 -* Profile Name: “Any name”
521 -* Broker Address: mqtt.tago.io
522 -* Broker Port: 1883
523 -* Client ID: “Any value”
498 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
524 524  
525 -On the sectioUsecredentials, set the following information:(这边加一个截图)
500 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
526 526  
527 -* User Name: “Any value” Tago validates your user by the token only
528 -* Password: “Your device token”
529 -* PUBTOPIC: “Any value”
530 -* SUBTOPIC: “Any value”
502 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
531 531  
532 -== 5.2 Simulate with MQTT.fx ==
504 +* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
533 533  
534 -[[image:image-20230802112413-47.png]]
506 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
535 535  
536 -[[image:image-20230802112413-48.png]]
508 +* (% style="color:#037691" %)**AT+PWD=“Your device token”**
537 537  
538 -Users can run the AT+PRO=3,5 command, and thpayload will be converted to JSON format.
510 +=== 3.7.2 Simulate with MQTT.fx ===
539 539  
540 -[[image:image-20230802112413-49.png]]
541 541  
542 -== 1.4. tago data ==
513 +[[image:image-20230802112413-52.png]]
543 543  
544 544  
516 +[[image:image-20230808105300-2.png]]
517 +
518 +
519 +Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
520 +
521 +[[image:image-20230808105217-1.png]]
522 +
523 +[[image:image-20230808105329-3.png]]
524 +
525 +
526 +=== 3.7.3 tago data ===
527 +
528 +
545 545  [[image:image-20230802112413-50.png]]
546 546  
547 -[[image:image-20230802112413-51.png]]
531 +[[image:image-20230802112413-51.png||height="184" width="696"]]
548 548  
549 -== 1.4. TLS mode ==
550 550  
551 -Users can choose to use SSL/TLS mode.
534 +== 3.8 TCP Connection ==
552 552  
553 -On the SSL/TLS section, check the option Enable SSL/TLS, and click OK.
554 554  
555 -The device needs tenable the TLS mode and set the AT+TLSMOD=1,0 command.
537 +(% style="color:blue" %)**AT command:**
556 556  
557 -* Profile Name: “Any name”
558 -* Broker Address: mqtt.tago.io
559 -* Broker Port: 8883
560 -* Client ID: “Any value”
561 -* User Name: “Any value” Tago validates your user by the token only
562 -* Password: “Your device token”
563 -* PUBTOPIC: “Any value”
564 -* SUBTOPIC: “Any value”
539 +* (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
565 565  
566 -[[image:image-20230802112413-52.png]]
541 +* (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
567 567  
543 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
568 568  
569 -
545 +(% style="color:blue" %)**Sensor Console Output when Uplink:**
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]]
image-20230807233631-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +21.9 KB
Content
image-20230807233631-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +9.6 KB
Content
image-20230808105217-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +68.5 KB
Content
image-20230808105300-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +70.1 KB
Content
image-20230808105329-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +21.1 KB
Content
image-20230808162301-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +76.9 KB
Content
image-20230808162342-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +63.8 KB
Content
image-20230808162421-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +59.2 KB
Content
image-20230808162727-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +54.2 KB
Content
image-20230808163035-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +71.6 KB
Content
image-20230808163049-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +61.5 KB
Content
image-20230808163612-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +53.4 KB
Content
image-20230808170051-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +21.5 KB
Content
image-20230808170548-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +54.1 KB
Content
image-20230808205045-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +373.9 KB
Content
image-20230809165928-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +74.4 KB
Content
image-20230809170225-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 KB
Content
image-20230809170532-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +38.7 KB
Content
image-20230809173127-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +82.5 KB
Content
image-20230809173310-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +51.9 KB
Content
image-20230809173438-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +41.0 KB
Content
image-20230809173800-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +46.8 KB
Content
image-20230809173835-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +88.8 KB
Content
image-20230809174053-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +58.0 KB
Content
image-20230809180523-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +91.9 KB
Content
image-20230810083934-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +85.1 KB
Content
image-20230810084048-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +63.7 KB
Content