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

From version 53.4
edited by Xiaoling
on 2023/08/02 11:44
Change comment: There is no comment for this version
To version 124.1
edited by Bei Jinggeng
on 2024/02/02 11:15
Change comment: Uploaded new attachment "image-20240202111546-1.png", version {1}

Summary

Details

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