Last modified by Kilight Cao on 2025/07/23 16:27
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 28 removed)
- image-20230807233631-1.png
- image-20230807233631-2.png
- image-20230808105217-1.png
- image-20230808105300-2.png
- image-20230808105329-3.png
- image-20230808162301-1.png
- image-20230808162342-2.png
- image-20230808162421-3.png
- image-20230808162727-4.png
- image-20230808163035-5.png
- image-20230808163049-6.png
- image-20230808163612-7.png
- image-20230808170051-8.png
- image-20230808170548-9.png
- image-20230808205045-1.png
- image-20230809165928-1.png
- image-20230809170225-2.png
- image-20230809170532-3.png
- image-20230809173127-4.png
- image-20230809173310-5.png
- image-20230809173438-6.png
- image-20230809173800-7.png
- image-20230809173835-8.png
- image-20230809174053-9.png
- image-20230809180523-10.png
- image-20230810083934-1.png
- image-20230810084048-2.png
- image-20230816201942-1.png
Details
- Page properties
-
- Content
-
... ... @@ -1,13 +11,3 @@ 1 -(% class="wikigeneratedid" id="HTableofContents:" %) 2 -**Table of Contents:** 3 - 4 -{{toc/}} 5 - 6 - 7 - 8 - 9 - 10 - 11 11 = 1. The use of this guideline = 12 12 13 13 ... ... @@ -14,190 +14,143 @@ 14 14 This configure instruction is for Dragino NB-IoT models with -NB or -NS suffix, for example DDS75-NB. These models use the same NB-IoT Module **[[BC660K-GL>>https://www.quectel.com/product/lpwa-bc660k-gl-nb2]]** and has the same software structure. The have the same configure instruction to different IoT servers. Use can follow the instruction here to see how to configure to connect to those servers. 15 15 16 16 17 -= 2. AttachNetwork =7 += 2. Network Connection = 18 18 19 -== 2.1 General Configure to attach network == 20 20 21 -To attache NB-IoT sensors to NB-IoT Network, You need to: 22 - 23 -1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone) 24 -1. Insert the SIM card to Sensor 25 -1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>) 26 - 27 -[[image:image-20230808205045-1.png||height="293" width="438"]] 28 - 29 -After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network . 30 - 31 31 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. 32 32 33 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %) 34 -|(% 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** 35 -|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)((( 36 -**[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]** 37 37 38 -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 39 -)))|(% style="width:135px" %) 40 -|(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %) 41 -|(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %) 13 +== 2.1 1NCE SIM Card. == 42 42 43 -(% class="wikigeneratedid" %) 44 -== == 45 45 46 -== 2.2 Speed Up Network Attach time == 16 +(% border="1" cellspacing="4" style="width:510px;background-color:#F2F2F2" %) 17 +|(% style="background-color:#4F81BD;color:white" %)SIM Provider|(% style="background-color:#4F81BD;color:white" %)APN|(% style="background-color:#4F81BD;color:white" %)NB-IoT Coverage|(% style="background-color:#4F81BD;color:white" %)Comments 18 +|1NCE| | | 19 +|China Mobile| | | 47 47 48 48 49 -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. 50 - 51 -(% style="color:#037691" %)**AT+QBAND? ** (%%) ~/~/ Check what is the current used frequency band 52 - 53 -(% style="color:#037691" %)**AT+QBAND=1,4 ** (%%) ~/~/ Set to use 1 frequency band. Band4 54 - 55 -(% style="color:#037691" %)**AT+QBAND=2,8,20** (%%) ~/~/ Set to use 2 frequency bands. Band 8 and Band 20 56 - 57 57 = 3. Configure to connect to different servers = 58 58 59 -== 3.1 General UDP Connection == 60 60 25 += NB-IoT 服务器对接例子 = 61 61 27 += 1. General UDP Connection = 28 + 62 62 The NB-IoT Sensor can send packet to server use UDP protocol. 63 63 31 +== 1.1 Simulate UDP Connection by PC tool == 64 64 65 -=== 3.1.1 Simulate UDP Connection by PC tool === 66 - 67 - 68 68 We can use PC tool to simulate UDP connection to make sure server works ok. 69 69 70 70 [[image:image-20230802112413-1.png]] 71 71 37 +== 1.2 Configure NB-IoT Sensor == 72 72 73 -=== 3.1.2 Configure NB-IoT Sensor===39 +=== 1.2.1 AT Commands === 74 74 75 - ==== 3.1.2.1AT Commands====41 +AT Commands: 76 76 43 +* AT+PRO=2,0 ~/~/ Set to use UDP protocol to uplink , Payload Type select Hex payload 44 +* AT+SERVADDR=120.24.4.116,5601 ~/~/ Set UDP server address and port 45 +* AT+CFM=1 ~/~/ If the server does not respond, this command is unnecessary 77 77 78 -(% style="color:blue" %)**AT Commands:** 79 - 80 -* (% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload 81 - 82 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601** (%%) ~/~/ Set UDP server address and port 83 - 84 -* (% style="color:#037691" %)**AT+CFM=1** (%%) ~/~/ If the server does not respond, this command is unnecessary 85 - 86 86 [[image:image-20230802112413-2.png]] 87 87 49 +=== 1.2.2 Uplink Example === 88 88 89 -==== 3.1.2.2 Uplink Example ==== 90 90 91 - 92 92 [[image:image-20230802112413-3.png]] 93 93 94 94 95 -= =3.2=55 += 2. General MQTT Connection = 96 96 97 - 98 98 The NB-IoT Sensor can send packet to server use MQTT protocol. 99 99 100 -Below are the commands .59 +Below are the commands 101 101 102 - (% style="color:blue" %)**AT Commands:**61 +AT Commands: 103 103 104 -* (% style="color:#037691" %)**AT+PRO=3,0** (%%) ~/~/ Set to use MQTT protocol to uplink, Payload Type select Hex payload. 63 +* AT+PRO=3,0 ~/~/ Set to use MQTT protocol to uplink, Payload Type select Hex payload. 64 +* AT+SERVADDR=120.24.4.116,1883 ~/~/ Set MQTT server address and port 65 +* AT+CLIENT=CLIENT ~/~/ Set up the CLIENT of MQTT 66 +* AT+UNAME=UNAME ~/~/ Set the username of MQTT 67 +* AT+PWD=PWD ~/~/ Set the password of MQTT 68 +* AT+PUBTOPIC=NSE01_PUB ~/~/ Set the sending topic of MQTT 69 +* AT+SUBTOPIC=NSE01_SUB ~/~/ Set the subscription topic of MQTT 105 105 106 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883** (%%) ~/~/ Set MQTT server address and port 107 - 108 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT** (%%) ~/~/ Set up the CLIENT of MQTT 109 - 110 -* (% style="color:#037691" %)**AT+UNAME=UNAME** (%%) ~/~/ Set the username of MQTT 111 - 112 -* (% style="color:#037691" %)**AT+PWD=PWD** (%%) ~/~/ Set the password of MQTT 113 - 114 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB** (%%) ~/~/ Set the sending topic of MQTT 115 - 116 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB** (%%) ~/~/ Set the subscription topic of MQTT 117 - 118 118 [[image:image-20230802112413-4.png]] 119 119 120 -[[image:image-20230802112413-5.png ||height="530" width="987"]]73 +[[image:image-20230802112413-5.png]] 121 121 122 - (% style="color:red" %)**Notice: MQTT protocol has a much higher power consumption compare with UDP/CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.**75 +Notice: MQTT protocol has a much higher power consumption compare with UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 123 123 124 124 125 -== 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) == 126 126 127 -= ==3.3.1Get MQTTCredentials===79 += 3. [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) = 128 128 81 +== 1.1 Get MQTT Credentials == 129 129 130 130 [[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. 131 131 132 -[[image:image-20230802112413-6.png ||height="336" width="925"]]85 +[[image:image-20230802112413-6.png]] 133 133 134 134 [[image:image-20230802112413-7.png]] 135 135 136 136 137 -== =3.3.2=90 +== 1.2. Simulate with MQTT.fx == 138 138 139 -=== =3.3.2.1 Establish MQTT Connection ====92 +=== 1.2.1 Establish MQTT Connection === 140 140 141 - 142 142 After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine. 143 143 144 144 [[image:image-20230802112413-8.png]] 145 145 146 -* (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com 98 +* Broker Address: mqtt3.thingspeak.com 99 +* Broker Port: 1883 100 +* Client ID: <Your ThingSpeak MQTT ClientID> 101 +* User Name: <Your ThingSpeak MQTT User Name> 102 +* Password: <Your ThingSpeak MQTT Password> 147 147 148 -* (% style="color:#037691" %)**Broker Port:**(%%) 1883 149 149 150 - * (% style="color:#037691"%)**ClientID:**(%%)<YourThingSpeakMQTTClientID>105 +=== 1.2.2 Publish Data to ThingSpeak Channel === 151 151 152 -* (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name> 153 - 154 -* (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password> 155 - 156 -==== 3.3.2.2 Publish Data to ThingSpeak Channel ==== 157 - 158 - 159 159 [[image:image-20230802112413-9.png]] 160 160 161 161 [[image:image-20230802112413-10.png]] 162 162 111 +In MQTT.fx, we can publish below info: 163 163 164 -(% style="color:blue" %)**In MQTT.fx, we can publish below info:** 113 +* Topic: channels/YOUR_CHANNEL_ID/publish 114 +* Payload: field1=63&field2=67&status=MQTTPUBLISH 165 165 166 -* (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish 167 167 168 -* (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH 169 - 170 170 Where 63 and 67 are the value to be published to field1 & field2. 171 171 172 172 173 - (% style="color:blue" %)**Result:**120 +Result: 174 174 175 -[[image:image-20230802112413-11.png ||height="539" width="901"]]122 +[[image:image-20230802112413-11.png]] 176 176 177 177 178 -== =3.3.3Configure NB-IoT Sensor for connection ===125 +== 1.3 Configure NB-IoT Sensor for connection == 179 179 180 -=== =3.3.3.1 AT Commands: ====127 +=== 1.3.1 AT Commands: === 181 181 182 - 183 183 In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx 184 184 185 -* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload 131 +* AT+PRO=3,1 ~/~/Set to use ThingSpeak Server and Related Payload 132 +* AT+CLIENT=<Your ThingSpeak MQTT ClientID> 133 +* AT+UNAME=<Your ThingSpeak MQTT User Name> 134 +* AT+PWD=<Your ThingSpeak MQTT Password> 135 +* AT+PUBTOPIC=<YOUR_CHANNEL_ID> 136 +* AT+SUBTOPIC=<YOUR_CHANNEL_ID> 186 186 187 -* (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>** 188 188 189 -* (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>** 190 190 191 - * (% style="color:blue" %)**AT+PWD=<YourThingSpeakMQTT Password>**140 +=== 1.3.2 Uplink Examples === 192 192 193 - * (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**142 +For S31-NB 194 194 195 -* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>** 196 - 197 -==== 3.3.3.2 Uplink Examples ==== 198 - 199 -[[image:image-20230816201942-1.png]] 200 - 201 201 For SE01-NB 202 202 203 203 For DDS20-NB ... ... @@ -221,336 +221,405 @@ 221 221 For SN50V3-NB 222 222 223 223 224 -=== =3.3.3.3Map fields to sensor value ====167 +=== 1.3.2 Map fields to sensor value === 225 225 226 - 227 227 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. 228 228 229 229 230 -[[image:image-20230802112413-12.png ||height="504" width="1011"]]172 +[[image:image-20230802112413-12.png]] 231 231 232 -[[image:image-20230802112413-13.png ||height="331" width="978"]]174 +[[image:image-20230802112413-13.png]] 233 233 234 234 235 235 Below is the NB-IoT Product Table show the mapping. 236 236 237 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %) 238 -|(% 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 239 -|(% 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" %) 240 -|(% 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" %) 241 -|(% 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" %) 242 -|(% 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" %) 243 -|(% 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" %) 244 -|(% 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" %) 245 -|(% 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" %) 246 -|(% 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" %) 247 -|(% 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" %) 248 -|(% 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" %) 249 -|(% 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 250 -|(% 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" %) 251 -|(% 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" %) 252 -|(% 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" %) 253 -|(% 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" %) 254 -|(% 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" %) 255 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod6|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)count|(% colspan="1" style="width:153px" %) |(% colspan="1" style="width:151px" %) |(% colspan="1" style="width:160px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %) 179 +|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)Field1|(% colspan="1" rowspan="1" %)Field2|(% colspan="1" rowspan="1" %)Field3|(% colspan="1" rowspan="1" %)Field4|(% colspan="1" rowspan="1" %)Field5|(% colspan="1" rowspan="1" %)Field6|(% colspan="1" rowspan="1" %)Field7|(% colspan="1" rowspan="1" %)Field8|(% colspan="1" rowspan="1" %)((( 180 +Field9 256 256 257 -== 3.4 [[Datacake>>https://datacake.co/]] == 182 + 183 +)))|(% colspan="1" rowspan="1" %)((( 184 +Field10 258 258 186 + 187 +))) 188 +|(% colspan="1" rowspan="1" %)S31x-NB|(% colspan="1" rowspan="1" %)Temperature |(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) 189 +|(% colspan="1" rowspan="1" %)SE01-NB|(% colspan="1" rowspan="1" %)Temperature |(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)conduct|(% colspan="1" rowspan="1" %)dielectric_constant|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) 190 +|(% colspan="1" rowspan="1" %)DDS20-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)((( 191 +Battery 259 259 260 -(% class="wikigeneratedid" %) 261 -Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor, 193 + 194 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) 195 +|(% colspan="1" rowspan="1" %)DDS45-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)((( 196 +Battery 262 262 198 + 199 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) 200 +|(% colspan="1" rowspan="1" %)DDS75-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)((( 201 +Battery 263 263 264 -(% class="wikigeneratedid" %) 265 -As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.** 203 + 204 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) 205 +|(% colspan="1" rowspan="1" %)NMDS120-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)((( 206 +Battery 266 266 267 -* (% style="color:blue" %)**S31B-NB-1D**(%%): This version have pre-configure DataCake connection. User just need to Power on this device, it will auto connect send data to DataCake Server. 208 + 209 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) 210 +|(% colspan="1" rowspan="1" %)SPH01-NB|(% colspan="1" rowspan="1" %)ph|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) 211 +|(% colspan="1" rowspan="1" %)NLM01-NB|(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) 212 +|(% colspan="1" rowspan="1" %)NMDS200-NB|(% colspan="1" rowspan="1" %)distance1|(% colspan="1" rowspan="1" %)distance2|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) 213 +|(% colspan="1" rowspan="1" %)CPN01-NB|(% colspan="1" rowspan="1" %)alarm|(% colspan="1" rowspan="1" %)count|(% colspan="1" rowspan="1" %)door open duration|(% colspan="1" rowspan="1" %)calc flag|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) 214 +|(% colspan="1" rowspan="1" %)DS03A-NB|(% colspan="1" rowspan="1" %)level|(% colspan="1" rowspan="1" %)alarm|(% colspan="1" rowspan="1" %)pb14door open num|(% colspan="1" rowspan="1" %)pb14 last open time|(% colspan="1" rowspan="1" %)pb15 level status|(% colspan="1" rowspan="1" %)pb15 alarm status|(% colspan="1" rowspan="1" %)pb15 door open num|(% colspan="1" rowspan="1" %)pb15 last open time|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI 215 +|(% colspan="1" rowspan="1" %)SN50V3-NB|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) 216 +|(% colspan="1" rowspan="1" %)mod1|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)DS18B20 Temp|(% colspan="1" rowspan="1" %)exit_state/input PA4|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)Temperature |(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) 217 +|(% colspan="1" rowspan="1" %)mod2|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)((( 218 +DS18B20 Temp 268 268 269 -* (% style="color:blue" %)**S31B-NB-GE**(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction. 220 + 221 +)))|(% colspan="1" rowspan="1" %)((( 222 +exit_state/input PA4 270 270 271 -=== 3.4.1 Create device === 224 + 225 +)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) 226 +|(% colspan="1" rowspan="1" %)mod3|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)((( 227 +Battery 272 272 229 + 230 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)((( 231 +exit_state/input PA4 273 273 274 -(% style="color:blue" %)**Add Device**(%%) in DataCake. 233 + 234 +)))|(% colspan="1" rowspan="1" %)adc1|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)adc4|(% colspan="1" rowspan="1" %) 235 +|(% colspan="1" rowspan="1" %)mod4|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)((( 236 +Battery 275 275 276 -[[image:image-20230808162301-1.png||height="473" width="994"]] 238 + 239 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)((( 240 +DS18B20 Temp 277 277 242 + 243 +)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)((( 244 +exit_state/input PA4 278 278 279 -[[image:image-20230808162342-2.png]] 246 + 247 +)))|(% colspan="1" rowspan="1" %)((( 248 +DS18B20 Temp2 280 280 250 + 251 +)))|(% colspan="1" rowspan="1" %)((( 252 +DS18B20 Temp3 281 281 282 -(% style="color:blue" %)**Choose the correct model**(%%) from template. 254 + 255 +)))|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) 256 +|(% colspan="1" rowspan="1" %)mod5|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)((( 257 +Battery 283 283 284 -[[image:image-20230808162421-3.png]] 259 + 260 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)((( 261 +DS18B20 Temp 285 285 263 + 264 +)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)((( 265 +exit_state/input PA4 286 286 287 -(% style="color:blue" %)**Fill Device ID**(%%). The device ID needs to be filled in with IMEI, and a prefix of(% style="color:blue" %)** 'f' **(%%)needs to be added. 267 + 268 +)))|(% colspan="1" rowspan="1" %)Weight|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) 269 +|(% colspan="1" rowspan="1" %)mod6|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)((( 270 +Battery 288 288 289 -[[image:image-20230808163612-7.png]] 272 + 273 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)count|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) 290 290 291 -[[image:image-20230808163035-5.png]] 292 292 293 - [[image:image-20230808163049-6.png]]276 += 4. Datacake = 294 294 278 +== 1.1 Define Product == 295 295 296 - === 3.4.2 ScanQRobtain===280 +Firstly, we need to set the MQTT mode to datacake, and we need to run AT+PRO=3,2. This command is set to datacake. After running the command, the device automatically sets the server address, port. 297 297 298 298 299 - Userscan usetheir phones orcomputerstoscanQR codestoobtaindevicedatainformation.283 +By chosing to add the device under a "New Product" you are required to give a name for this product. You can name it something like "My First MQTT Product". 300 300 301 -[[image:image-2023080 8170051-8.png||height="255" width="259"]]285 +[[image:image-20230802112413-14.png]] 302 302 303 - [[image:image-20230808170548-9.png]]287 +== 1.2 Create Device == 304 304 289 +In the second step you have to define the device which should be added to the product. 305 305 306 - === 3.4.2 AT command for connecting to DataCake===291 +[[image:image-20230802112413-15.png]] 307 307 293 +Enter a name here (such as "My First MQTT Device") and complete the creation of the device by clicking on the "Next" button. 308 308 309 -(% style="color:blue" %)**AT+PRO=2,0** 310 310 311 - (%style="color:blue"%)**AT+SERVADDR=67.207.76.90,4445**296 +== 1.3 Create Database Fields == 312 312 298 +After creating the device, it is listed in the table of the fleet view. Now open the device by clicking on the entry in the list. 313 313 314 - == 3.5Node-Red(viaMQTT) ==300 +You will then see a device view with an empty dashboard. Now, the first thing we want to do is navigate to the Device configuration. To do this, use the tab bar and click on "Configuration". 315 315 316 - === 3.5.1 Configure[[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]]===302 +[[image:image-20230802112413-16.png]] 317 317 304 +[[image:image-20230802112413-17.png]] 318 318 319 -Ta keS31-NB UDP protocolxample.306 +To create a first database field, please click on the "Add Field" button as marked in the screenshot above. 320 320 321 - Draginovidesputflow examplesforthesensors.308 +This will open another modal asking for some required input for your first field. 322 322 323 - User can download the required JSON file through Dragino Node-REDinput flow template.310 +[[image:image-20230802112413-18.png]] 324 324 325 - 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]]312 +[[image:image-20230802112413-19.png]] 326 326 327 - Wecan directly importthe template.314 +== 1.4 Set up Broker == 328 328 329 -The templates forS31-NBandNB95S31Bareheme.316 +The broker is running on mqtt.datacake.co on ports 1883 and 8883. Port 1883 is unsecured and should not be used in production environments. Port 8883 uses a CA signed server certificate. 330 330 318 +You will need an access token to log into the Datacake MQTT Broker. You can use your own personal token or create a token explicitly for individual devices or groups of devices. 331 331 332 - [[image:image-20230809173127-4.png]]320 +View your Personal Access Token 333 333 322 +You can view your own token via the User-Settings-Menu. You can reach this menu by clicking on "Edit Profile" at the end of the list using the Workspace Selector: 334 334 335 - Pleaseselect the NB95S31B template.324 +[[image:image-20230802112413-20.png]] 336 336 337 - [[image:image-20230809173310-5.png]]326 +MQTT Client-ID 338 338 339 - [[image:image-20230809173438-6.png]]328 +The Datacake Broker manages the client IDs internally. You do not need to worry about a client ID. If your client optionally supports the specification of a client ID, please leave this specification blank. Your client then creates a randomly generated ID. 340 340 341 - [[image:image-20230809173800-7.png]]330 +AT+CLIENT=“Any value” 342 342 332 +AT+UNAME=Token 343 343 344 - Successfully imported template.334 +AT+PWD=Token 345 345 346 -[[image:image-2023080 9173835-8.png]]336 +[[image:image-20230802112413-21.png]] 347 347 348 348 349 - Userscan setUDP port.339 +== 1.6 Create your first Subscription == 350 350 351 - [[image:image-20230809174053-9.png]]341 +Subscribe 352 352 343 +Data is published according to the following structure: 353 353 354 - === 3.5.2 Simulate Connection===345 +dtck~/~// 355 355 347 +Subscribe to topics using this structure to receive messages via MQTT when readings (via API or MQTT) arrive in the Datacake Cloud. Messages are published whenever there is a change to a corresponding database field. 356 356 357 -We have completed the configuration of UDP. We can try sending packets to node red. 358 358 359 -[[image:image-202308 10083934-1.png]]350 +[[image:image-20230802112413-22.png]] 360 360 361 -[[image:image-20230810084048-2.png]] 362 362 363 - === 3.5.3 ConfigureNB-IoT Sensors ===353 +[[image:image-20230802112413-23.png]] 364 364 365 365 366 - * (% style="color:blue" %)**AT+PRO=2,0(hex format) or2,1(jsonformat) **(%%)** **~/~/ Set to UDP Server and Payload356 +[[image:image-20230802112413-24.png]] 367 367 368 -* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port **(%%)** **~/~/ Set Server IP and port 369 369 370 - == 3.6 ThingsBoard.Cloud (via MQTT) ==359 +example: 371 371 372 -= ==3.6.1 ConfigurehingsBoard ===361 +AT+PUBTOPIC=dtck-pub/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature 373 373 374 - ==== 3.6.1.1 CreateDevice====363 +[[image:image-20230802112413-25.png]] 375 375 365 +== 1.7 Define Publish Topic == 376 376 377 - Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which isused for MQTT connection.367 +Publish 378 378 379 - [[image:image-20230802112413-32.png]]369 +To upload data into the Datacake Cloud and into a specific device, you publish the data to the respective topic structure. 380 380 371 +Due to the nature of MQTT, the topic prefix differs as follows: 381 381 382 - ==== 3.6.1.2 Create Uplink& Downlink Converter ====373 +dtck-pub~/~// 383 383 375 +example: 384 384 385 - (%style="color:blue" %)**Uplink Converter**377 +AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature 386 386 387 - 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 areoptional. Attributes andtelemetry are flat key-value objects. Nestedobjectsare notsupported.379 +== 1.8 upload data == 388 388 389 - To create an uplink convertergo to the(% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) pageand click (% style="color:blue" %)**“plus”** (%%)button.Name it (% style="color:blue" %)**“MQTT Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debugmode for now.381 +[[image:image-20230802112413-26.png]] 390 390 391 -[[image:image-20230802112413- 33.png||height="732" width="1302"]]383 +[[image:image-20230802112413-27.png]] 392 392 385 +[[image:image-20230802112413-28.png]] 393 393 394 - (% style="color:blue"%)**Downlink Converter**387 += = 395 395 396 - TheDownlink converter transforming outgoingRPC message andthen the Integration sends it to externalMQTTbroke389 += 5. Node-Red (via MQTT) = 397 397 398 -[[image:image-20230802112413-34.png||height="734" width="1305"]] 399 399 400 - (% style="color:red"%)**Note: Ourdevice payload is already humanreadable data. Therefore,users do not needtowritedecoders. Simply create bydefault.**392 +== 1.1 Configure Node-Red == 401 401 394 +[[image:image-20230802112413-29.png]] 402 402 403 - ====3.6.1.3MQTT Integration Setup ====396 +[[image:image-20230802112413-30.png]] 404 404 398 +== 1.2 Simulate Connection == 405 405 406 - Go to the (% style="color:blue" %)**Integrations center**(%%) **->** (% style="color:blue" %)**Integrations page**(%%) and click **“(% style="color:blue" %)plus(%%)”**icon toadd a new integration. Nameit (% style="color:blue" %)**“MQTT Integration”**(%%), select type (% style="color:blue" %)**MQTT**;400 +[[image:image-20230802112413-31.png]] 407 407 408 - [[image:image-20230802112413-35.png||height="738"width="1312"]]402 +== 1.3 Configure NB-IoT Sensors == 409 409 404 +* AT+PRO=3,0(hex format) or 3,5(json format) ~/~/Set to mqtt Server and Payload 405 +* AT+CLIENT=any value 406 +* AT+UNAME=any value 407 +* AT+PWD=any value 408 +* AT+PUBTOPIC=any value 409 +* AT+SUBTOPIC=any value 410 410 411 -* The next steps is to add the recently created uplink and downlink converters; 412 412 413 - [[image:image-20230802112413-36.png||height="736" width="1308"]]412 += 6. ThingsBoard.Cloud (via MQTT) = 414 414 415 - [[image:image-20230802112413-37.png||height="735" width="1307"]]414 +== 1.1 Configure ThingsBoard == 416 416 416 +=== 1.1.1 Create Device === 417 417 418 - (% style="color:blue" %)**Addatopicfilter:**418 +Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. 419 419 420 - tb/mqtt-integration-tutorial/sensors~/~/temperature~-~-> Temperature **固定的? 对的。**420 +[[image:image-20230802112413-32.png]] 421 421 422 - Youcan also selectanMQTTQoSlevel.We use MQTT QoS level 0 (Atmost once) by default;422 +=== 1.1.2 Create Uplink & Downlink Converter === 423 423 424 - [[image:image-20230802112413-38.png||height="731" width="1300"]]424 +Uplink Converter 425 425 426 +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. 426 426 427 - === 3.6.2SimulatewithMQTT.fx ===428 +To create an uplink converter go to the Integrations center -> Data converters page and click “plus” button. Name it “MQTT Uplink Converter” and select type Uplink. Use debug mode for now. 428 428 430 +[[image:image-20230802112413-33.png]] 429 429 430 -[[image:image-20230802112413-39.png]] 431 431 432 - [[image:image-20230802112413-40.png]]433 +Downlink Converter 433 433 435 +The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke 434 434 435 - === 3.6.3 ConfigureNB-IoT Sensor ===437 +[[image:image-20230802112413-34.png]] 436 436 439 +Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default. 437 437 438 - (% style="color:blue"%)**ATCommands**441 +=== 1.1.3 MQTT Integration Setup === 439 439 440 - * (% style="color:#037691" %)**AT+PRO=3,3**(%%)** **~/~/UseMQTTto connecttoThingsBoard. PayloadTypeo 3.443 +Go to the Integrations center -> Integrations page and click “plus” icon to add a new integration. Name it “MQTT Integration”, select type MQTT; 441 441 442 - * (% style="color:#037691" %)**AT+SUBTOPIC=<devicename>**445 +[[image:image-20230802112413-35.png]] 443 443 444 -* (%style="color:#037691" %)**AT+PUBTOPIC=<device name>**447 +* The next steps is to add the recently created uplink and downlink converters; 445 445 446 - * (% style="color:#037691" %)**AT+CLIENT=<devicename> or User Defined**449 +[[image:image-20230802112413-36.png]] 447 447 448 - * (% style="color:#037691" %)**AT+UNAME=<devicename> or User Defined**451 +[[image:image-20230802112413-37.png]] 449 449 450 - * (% style="color:#037691" %)**AT+PWD=<devicename>or User Defined**453 +Add a topic filter: 451 451 452 -Test Uplink by click the button for 1 second 453 453 454 - [[image:image-20230802112413-41.png]]456 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。 455 455 456 - [[image:image-20230802112413-42.png]]458 +You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default; 457 457 458 -[[image:image-20230802112413- 43.png]]460 +[[image:image-20230802112413-38.png]] 459 459 462 +== 1.2 Simulate with MQTT.fx == 460 460 461 - == 3.7[[Tago.io>>url:https://admin.tago.io/]](via MQTT) ==464 +[[image:image-20230802112413-39.png]] 462 462 463 - === 3.7.1 Createdevice& Get Credentials ===466 +[[image:image-20230802112413-40.png]] 464 464 468 +== 1.3 Configure NB-IoT Sensor == 465 465 466 - We use MQTTConnection to send data to [[Tago.io>>url:https://admin.tago.io/]]. Weneedto Create Device and Get MQTT Credentialsfirst.470 +AT Commands 467 467 468 - [[image:image-20230802112413-44.png]]472 +AT+PRO=3,3 ~/~/ Use MQTT to connect to ThingsBoard. 469 469 470 - [[image:image-20230802112413-45.png]]474 +AT+SUBTOPIC=device name ~-~-> 只需要 Device Name 吗?对的 471 471 476 +AT+PUBTOPIC=device name ~-~-> 只需要 Device Name 吗?对的 472 472 473 -Go to the Device section and create a device. Then, go to the section tokens and copy your device-token. 474 474 475 - [[image:image-20230802112413-46.png]]479 +Users do not need to fill in the client, username, and password. But the configuration information of the device requires setting the client, username, and password, which can be entered freely. (软件自动填充为 Device Name 吧).这边不用提示了,客户不需要输入。(大部分客户还是会自己去设置这个的,提高安全性) 476 476 481 +CLIENT :“Any value” 477 477 478 - The device needstoenablethe TLSmodeand set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.483 +User Name:“Any value” 479 479 480 - (%style="color:blue" %)**Onthe Connection Profilewindow, set the following information:**485 +Password:“Any value” 481 481 482 -* (% style="color:#037691" %)**Profile Name: “Any name”** 483 483 484 - * (%style="color:#037691" %)**BrokerAddress:mqtt.tago.io**488 +Test Uplink by click the button for 1 second 485 485 486 - * (% style="color:#037691" %)**Broker Port:8883**490 +[[image:image-20230802112413-41.png]] 487 487 488 - * (% style="color:#037691" %)**Client ID: “Any value”**492 +[[image:image-20230802112413-42.png]] 489 489 490 - (% style="color:blue" %)**On the section User credentials, set the following information:**494 +[[image:image-20230802112413-43.png]] 491 491 492 -* (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only** 493 493 494 - * (% style="color:#037691" %)**Password:“Yourdevicetoken”**497 += 7. [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) = 495 495 496 - *(% style="color:#037691" %)**PUBTOPIC:“Anyvalue”**499 +== 5.1 Create device & Get Credentials == 497 497 498 - * (%style="color:#037691" %)**SUBTOPIC:“Anyvalue”**501 +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. 499 499 500 - (% style="color:blue" %)**AT command:**503 +[[image:image-20230802112413-44.png]] 501 501 502 - * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5** (%%) **~/~/ hex format or jsonformat**505 +[[image:image-20230802112413-45.png]] 503 503 504 - * (% style="color:#037691"%)**AT+SUBTOPIC=<device name>orUserDefined**507 += = 505 505 506 - * (% style="color:#037691" %)**AT+PUBTOPIC=<devicename>or User Defined**509 +Go to the Device section and create a device. Then, go to the section tokens and copy your device-token. 507 507 508 - * (% style="color:#037691" %)**AT+CLIENT=<devicename> or User Defined**511 +[[image:image-20230802112413-46.png]] 509 509 510 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined** 511 511 512 - * (% style="color:#037691" %)**AT+PWD=“Yourdeviceoken”**514 +On the Connection Profile window, set the following information: (这边加一个截图) 513 513 514 -=== 3.7.2 Simulate with MQTT.fx === 516 +* Profile Name: “Any name” 517 +* Broker Address: mqtt.tago.io 518 +* Broker Port: 1883 519 +* Client ID: “Any value” 515 515 516 516 517 - [[image:image-20230802112413-52.png]]522 +On the section User credentials, set the following information:(这边加一个截图) 518 518 524 +* User Name: “Any value” Tago validates your user by the token only 525 +* Password: “Your device token” 526 +* PUBTOPIC: “Any value” 527 +* SUBTOPIC: “Any value” 519 519 520 -[[image:image-20230808105300-2.png]] 521 521 530 +== 5.2 Simulate with MQTT.fx == 522 522 523 - Users can run the(% style="color:blue" %)**AT+PRO=3,5**(%%) command, and theayload will be converted to **JSON format**.532 +[[image:image-20230802112413-47.png]] 524 524 525 -[[image:image-2023080 8105217-1.png]]534 +[[image:image-20230802112413-48.png]] 526 526 527 - [[image:image-20230808105329-3.png]]536 +Users can run the AT+PRO=3,5 command, and the payload will be converted to JSON format. 528 528 538 +[[image:image-20230802112413-49.png]] 529 529 530 -== =3.7.3tago data ===540 +== 1.4. tago data == 531 531 532 532 533 533 [[image:image-20230802112413-50.png]] 534 534 535 -[[image:image-20230802112413-51.png ||height="184" width="696"]]545 +[[image:image-20230802112413-51.png]] 536 536 547 +== 1.4. TLS mode == 537 537 538 - == 3.8 TCP Connection ==549 +Users can choose to use SSL/TLS mode. 539 539 551 +On the SSL/TLS section, check the option Enable SSL/TLS, and click OK. 540 540 541 - (% style="color:blue" %)**AT:**553 +The device needs to enable the TLS mode and set the AT+TLSMOD=1,0 command. 542 542 543 -* (% style="color:#037691" %)**AT+PRO=4,0 ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format) 555 +* Profile Name: “Any name” 556 +* Broker Address: mqtt.tago.io 557 +* Broker Port: 8883 558 +* Client ID: “Any value” 559 +* User Name: “Any value” Tago validates your user by the token only 560 +* Password: “Your device token” 561 +* PUBTOPIC: “Any value” 562 +* SUBTOPIC: “Any value” 544 544 545 -* (% style="color:#037691" %)**AT+PRO=4,1 ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format) 546 546 547 - * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address andport565 +[[image:image-20230802112413-52.png]] 548 548 549 -(% style="color:blue" %)**Sensor Console Output when Uplink:** 550 550 551 -[[image:image-20230807233631-1.png]] 552 - 553 - 554 -(% style="color:blue" %)**See result in TCP Server:** 555 - 556 -[[image:image-20230807233631-2.png]] 568 +
- image-20230807233631-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -21.9 KB - Content
- image-20230807233631-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -9.6 KB - Content
- image-20230808105217-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -68.5 KB - Content
- image-20230808105300-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -70.1 KB - Content
- image-20230808105329-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -21.1 KB - Content
- image-20230808162301-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -76.9 KB - Content
- image-20230808162342-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -63.8 KB - Content
- image-20230808162421-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -59.2 KB - Content
- image-20230808162727-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -54.2 KB - Content
- image-20230808163035-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -71.6 KB - Content
- image-20230808163049-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -61.5 KB - Content
- image-20230808163612-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -53.4 KB - Content
- image-20230808170051-8.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -21.5 KB - Content
- image-20230808170548-9.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -54.1 KB - Content
- image-20230808205045-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -373.9 KB - Content
- image-20230809165928-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -74.4 KB - Content
- image-20230809170225-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -39.9 KB - Content
- image-20230809170532-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -38.7 KB - Content
- image-20230809173127-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -82.5 KB - Content
- image-20230809173310-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -51.9 KB - Content
- image-20230809173438-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -41.0 KB - Content
- image-20230809173800-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -46.8 KB - Content
- image-20230809173835-8.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -88.8 KB - Content
- image-20230809174053-9.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -58.0 KB - Content
- image-20230809180523-10.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -91.9 KB - Content
- image-20230810083934-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -85.1 KB - Content
- image-20230810084048-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -63.7 KB - Content
- image-20230816201942-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -99.8 KB - Content