Wiki source code of General Configure/Commands to Connect to IoT server for -NB & -NS NB-IoT models
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
53.3 | 1 | (% class="wikigeneratedid" %) |
| 2 | **Table of Contents:** | ||
| 3 | |||
| 4 | {{toc/}} | ||
| 5 | |||
| 6 | |||
 |
1.1 | 7 | = 1. The use of this guideline = |
| 8 | |||
| |
1.2 | 9 | |
| |
1.1 | 10 | 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. |
| 11 | |||
| 12 | |||
| |
55.1 | 13 | = 2. Attach Network = |
| |
1.1 | 14 | |
| 15 | |||
| |
54.1 | 16 | To attache NB-IoT sensors to NB-IoT Network, You need to: |
| 17 | |||
| 18 | 1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone) | ||
| 19 | 1. Insert the SIM card to Sensor | ||
| 20 | 1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor | ||
| 21 | |||
| 22 | After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network . | ||
| 23 | |||
| |
1.3 | 24 | 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. |
| |
1.1 | 25 | |
| |
54.1 | 26 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %) |
| |
56.2 | 27 | |(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**APN**|(% style="background-color:#4f81bd; color:white; width:474px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments** |
| 28 | |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)((( | ||
| |
54.1 | 29 | **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]** |
| |
1.1 | 30 | |
| |
54.1 | 31 | 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 |
| 32 | )))|(% style="width:135px" %) | ||
| |
56.2 | 33 | |(% style="width:117px" %)China Mobile|(% style="width:151px" %) |(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %) |
| 34 | |(% style="width:117px" %)China Telecom|(% style="width:151px" %) |(% style="width:474px" %)China Mainland|(% style="width:135px" %) | ||
| |
53.27 | 35 | |
| |
56.2 | 36 | |
| 37 | |||
| |
1.1 | 38 | = 3. Configure to connect to different servers = |
| 39 | |||
| |
53.3 | 40 | == 3.1 General UDP Connection == |
| |
53.2 | 41 | |
| 42 | |||
| 43 | The NB-IoT Sensor can send packet to server use UDP protocol. | ||
| 44 | |||
| 45 | |||
| |
53.3 | 46 | === 3.1.1 Simulate UDP Connection by PC tool === |
| 47 | |||
| 48 | |||
| |
53.2 | 49 | We can use PC tool to simulate UDP connection to make sure server works ok. |
| 50 | |||
| 51 | [[image:image-20230802112413-1.png]] | ||
| 52 | |||
| 53 | |||
| |
53.3 | 54 | === 3.1.2 Configure NB-IoT Sensor === |
| |
53.2 | 55 | |
| |
53.3 | 56 | ==== 3.1.2.1 AT Commands ==== |
| |
53.2 | 57 | |
| |
53.3 | 58 | |
| |
53.4 | 59 | (% style="color:blue" %)**AT Commands:** |
| |
53.3 | 60 | |
| |
53.5 | 61 | * (% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload |
| |
53.8 | 62 | |
| |
53.5 | 63 | * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601** (%%) ~/~/ Set UDP server address and port |
| |
53.8 | 64 | |
| |
53.5 | 65 | * (% style="color:#037691" %)**AT+CFM=1** (%%) ~/~/ If the server does not respond, this command is unnecessary |
| |
53.2 | 66 | |
| 67 | [[image:image-20230802112413-2.png]] | ||
| 68 | |||
| 69 | |||
| |
53.3 | 70 | ==== 3.1.2.2 Uplink Example ==== |
| |
53.2 | 71 | |
| |
53.3 | 72 | |
| |
53.2 | 73 | [[image:image-20230802112413-3.png]] |
| 74 | |||
| 75 | |||
| |
53.7 | 76 | == 3.2 General MQTT Connection == |
| |
53.2 | 77 | |
| |
53.6 | 78 | |
| |
53.2 | 79 | The NB-IoT Sensor can send packet to server use MQTT protocol. |
| 80 | |||
| |
53.6 | 81 | Below are the commands. |
| |
53.2 | 82 | |
| |
53.8 | 83 | (% style="color:blue" %)**AT Commands:** |
| |
53.2 | 84 | |
| |
53.9 | 85 | * (% style="color:#037691" %)**AT+PRO=3,0** (%%) ~/~/ Set to use MQTT protocol to uplink, Payload Type select Hex payload. |
| |
53.2 | 86 | |
| |
53.9 | 87 | * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883** (%%) ~/~/ Set MQTT server address and port |
| |
53.8 | 88 | |
| |
53.9 | 89 | * (% style="color:#037691" %)**AT+CLIENT=CLIENT** (%%) ~/~/ Set up the CLIENT of MQTT |
| |
53.8 | 90 | |
| |
53.9 | 91 | * (% style="color:#037691" %)**AT+UNAME=UNAME** (%%) ~/~/ Set the username of MQTT |
| |
53.8 | 92 | |
| |
53.9 | 93 | * (% style="color:#037691" %)**AT+PWD=PWD** (%%) ~/~/ Set the password of MQTT |
| |
53.8 | 94 | |
| 95 | * (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB** (%%) ~/~/ Set the sending topic of MQTT | ||
| 96 | |||
| 97 | * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB** (%%) ~/~/ Set the subscription topic of MQTT | ||
| 98 | |||
| |
53.2 | 99 | [[image:image-20230802112413-4.png]] |
| 100 | |||
| 101 | [[image:image-20230802112413-5.png]] | ||
| 102 | |||
| |
53.9 | 103 | (% 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.** |
| |
53.2 | 104 | |
| 105 | |||
| |
53.7 | 106 | == 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) == |
| |
53.2 | 107 | |
| |
53.9 | 108 | === 3.3.1 Get MQTT Credentials === |
| |
53.2 | 109 | |
| |
53.9 | 110 | |
| |
53.2 | 111 | [[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. |
| 112 | |||
| 113 | [[image:image-20230802112413-6.png]] | ||
| 114 | |||
| 115 | [[image:image-20230802112413-7.png]] | ||
| 116 | |||
| 117 | |||
| |
53.27 | 118 | === 3.3.2 Simulate with MQTT.fx === |
| |
53.2 | 119 | |
| |
53.27 | 120 | ==== 3.3.2.1 Establish MQTT Connection ==== |
| |
53.2 | 121 | |
| |
53.9 | 122 | |
| |
53.2 | 123 | After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine. |
| 124 | |||
| 125 | [[image:image-20230802112413-8.png]] | ||
| 126 | |||
| |
53.9 | 127 | * (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com |
| |
53.2 | 128 | |
| |
53.9 | 129 | * (% style="color:#037691" %)**Broker Port:**(%%) 1883 |
| |
53.10 | 130 | |
| |
53.9 | 131 | * (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID> |
| |
53.10 | 132 | |
| |
53.9 | 133 | * (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name> |
| |
53.10 | 134 | |
| |
53.9 | 135 | * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password> |
| |
53.2 | 136 | |
| |
56.2 | 137 | |
| 138 | |||
| |
53.28 | 139 | ==== 3.3.2.2 Publish Data to ThingSpeak Channel ==== |
| 140 | |||
| 141 | |||
| |
53.2 | 142 | [[image:image-20230802112413-9.png]] |
| 143 | |||
| 144 | [[image:image-20230802112413-10.png]] | ||
| 145 | |||
| |
53.43 | 146 | |
| |
53.10 | 147 | (% style="color:blue" %)**In MQTT.fx, we can publish below info:** |
| |
53.2 | 148 | |
| |
53.10 | 149 | * (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish |
| |
53.2 | 150 | |
| |
53.10 | 151 | * (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH |
| 152 | |||
| |
53.2 | 153 | Where 63 and 67 are the value to be published to field1 & field2. |
| 154 | |||
| 155 | |||
| |
53.10 | 156 | (% style="color:blue" %)**Result: ** |
| |
53.2 | 157 | |
| 158 | [[image:image-20230802112413-11.png]] | ||
| 159 | |||
| 160 | |||
| |
53.28 | 161 | === 3.3.3 Configure NB-IoT Sensor for connection === |
| |
53.2 | 162 | |
| |
53.28 | 163 | ==== 3.3.3.1 AT Commands: ==== |
| |
53.2 | 164 | |
| |
53.10 | 165 | |
| |
53.2 | 166 | In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx |
| 167 | |||
| |
53.27 | 168 | * (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload |
| |
53.9 | 169 | |
| |
53.26 | 170 | * (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>** |
| |
53.9 | 171 | |
| |
53.26 | 172 | * (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>** |
| |
53.9 | 173 | |
| |
53.26 | 174 | * (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>** |
| |
53.9 | 175 | |
| |
53.26 | 176 | * (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>** |
| |
53.9 | 177 | |
| |
53.26 | 178 | * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>** |
| |
53.2 | 179 | |
| |
56.2 | 180 | |
| 181 | |||
| |
53.28 | 182 | ==== 3.3.3.2 Uplink Examples ==== |
| |
53.10 | 183 | |
| 184 | |||
| |
53.2 | 185 | For S31-NB |
| 186 | |||
| 187 | For SE01-NB | ||
| 188 | |||
| 189 | For DDS20-NB | ||
| 190 | |||
| 191 | For DDS45-NB | ||
| 192 | |||
| 193 | For DDS75-NB | ||
| 194 | |||
| 195 | For NMDS120-NB | ||
| 196 | |||
| 197 | For SPH01-NB | ||
| 198 | |||
| 199 | For NLM01-NB | ||
| 200 | |||
| 201 | For NMDS200-NB | ||
| 202 | |||
| 203 | For CPN01-NB | ||
| 204 | |||
| 205 | For DS03A-NB | ||
| 206 | |||
| 207 | For SN50V3-NB | ||
| 208 | |||
| 209 | |||
| |
53.28 | 210 | ==== 3.3.3.3 Map fields to sensor value ==== |
| |
53.2 | 211 | |
| |
53.10 | 212 | |
| |
53.2 | 213 | 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. |
| 214 | |||
| 215 | |||
| 216 | [[image:image-20230802112413-12.png]] | ||
| 217 | |||
| 218 | [[image:image-20230802112413-13.png]] | ||
| 219 | |||
| 220 | |||
| 221 | Below is the NB-IoT Product Table show the mapping. | ||
| 222 | |||
| |
53.25 | 223 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1386px" %) |
| 224 | |(% style="background-color:#4f81bd; width:124px" %) |(% style="background-color:#4f81bd; color:white; width:91px" %)Field1|(% style="background-color:#4f81bd; color:white; width:102px" %)Field2|(% style="background-color:#4f81bd; color:white; width:159px" %)Field3|(% style="background-color:#4f81bd; color:white; width:153px" %)Field4|(% style="background-color:#4f81bd; color:white; width:152px" %)Field5|(% style="background-color:#4f81bd; color:white; width:148px" %)Field6|(% style="background-color:#4f81bd; color:white; width:164px" %)Field7|(% style="background-color:#4f81bd; color:white; width:152px" %)Field8|(% style="background-color:#4f81bd; color:white; width:66px" %)Field9|(% style="background-color:#4f81bd; color:white; width:66px" %)Field10 | ||
| 225 | |(% style="background-color:#4f81bd; color:white; width:124px" %)S31x-NB|(% style="width:91px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:159px" %)Battery|(% style="width:153px" %)RSSI|(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %) | ||
| 226 | |(% style="background-color:#4f81bd; color:white; width:124px" %)SE01-NB|(% style="width:91px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:159px" %)conduct|(% style="width:153px" %)dielectric_constant|(% style="width:152px" %)Battery|(% style="width:148px" %)RSSI|(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %) | ||
| 227 | |(% style="background-color:#4f81bd; color:white; width:124px" %)DDS20-NB|(% style="width:91px" %)distance|(% style="width:102px" %)Battery|(% style="width:159px" %)RSSI|(% style="width:153px" %) |(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %) | ||
| 228 | |(% style="background-color:#4f81bd; color:white; width:124px" %)DDS45-NB|(% style="width:91px" %)distance|(% style="width:102px" %)Battery|(% style="width:159px" %)RSSI|(% style="width:153px" %) |(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %) | ||
| 229 | |(% style="background-color:#4f81bd; color:white; width:124px" %)DDS75-NB|(% style="width:91px" %)distance|(% style="width:102px" %)Battery|(% style="width:159px" %)RSSI|(% style="width:153px" %) |(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %) | ||
| 230 | |(% style="background-color:#4f81bd; color:white; width:124px" %)NMDS120-NB|(% style="width:91px" %)distance|(% style="width:102px" %)Battery|(% style="width:159px" %)RSSI|(% style="width:153px" %) |(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %) | ||
| 231 | |(% rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SPH01-NB|(% style="width:91px" %)ph|(% style="width:102px" %)Temperature|(% style="width:159px" %)Battery|(% style="width:153px" %)RSSI|(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% colspan="1" rowspan="1" style="width:66px" %) | ||
| 232 | |(% style="background-color:#4f81bd; color:white; width:124px" %)NLM01-NB|(% style="width:91px" %)Humidity|(% style="width:102px" %)Temperature|(% style="width:159px" %)Battery|(% style="width:153px" %)RSSI|(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %) | ||
| 233 | |(% style="background-color:#4f81bd; color:white; width:124px" %)NMDS200-NB|(% style="width:91px" %)distance1|(% style="width:102px" %)distance2|(% style="width:159px" %)Battery|(% style="width:153px" %)RSSI|(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %) | ||
| 234 | |(% style="background-color:#4f81bd; color:white; width:124px" %)CPN01-NB|(% style="width:91px" %)alarm|(% style="width:102px" %)count|(% style="width:159px" %)door open duration|(% style="width:153px" %)calc flag|(% style="width:152px" %)Battery|(% style="width:148px" %)RSSI|(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %) | ||
| 235 | |(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)DS03A-NB|(% colspan="1" rowspan="1" style="width:91px" %)level|(% colspan="1" rowspan="1" style="width:102px" %)alarm|(% colspan="1" rowspan="1" style="width:159px" %)pb14door open num|(% colspan="1" rowspan="1" style="width:153px" %)pb14 last open time|(% colspan="1" rowspan="1" style="width:152px" %)pb15 level status|(% colspan="1" rowspan="1" style="width:148px" %)pb15 alarm status|(% colspan="1" rowspan="1" style="width:164px" %)pb15 door open num|(% colspan="1" rowspan="1" style="width:152px" %)pb15 last open time|(% colspan="1" rowspan="1" style="width:66px" %)Battery|(% colspan="1" rowspan="1" style="width:66px" %)RSSI | ||
| 236 | |(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB|(% colspan="1" rowspan="1" style="width:91px" %) |(% colspan="1" rowspan="1" style="width:102px" %) |(% colspan="1" rowspan="1" style="width:159px" %) |(% colspan="1" rowspan="1" style="width:153px" %) |(% colspan="1" rowspan="1" style="width:152px" %) |(% colspan="1" rowspan="1" style="width:148px" %) |(% colspan="1" rowspan="1" style="width:164px" %) |(% colspan="1" rowspan="1" style="width:152px" %) |(% colspan="1" rowspan="1" style="width:66px" %) |(% colspan="1" rowspan="1" style="width:66px" %) | ||
| 237 | |(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod1|(% colspan="1" rowspan="1" style="width:91px" %)mod|(% colspan="1" rowspan="1" style="width:102px" %)Battery|(% colspan="1" rowspan="1" style="width:159px" %)RSSI|(% colspan="1" rowspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:148px" %)adc0|(% colspan="1" rowspan="1" style="width:164px" %)Temperature |(% colspan="1" rowspan="1" style="width:152px" %)Humidity|(% colspan="1" rowspan="1" style="width:66px" %) |(% colspan="1" rowspan="1" style="width:66px" %) | ||
| 238 | |(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod2|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" style="width:148px" %)adc0|(% colspan="1" style="width:164px" %)distance|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %) | ||
| 239 | |(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod3|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" style="width:148px" %)adc1|(% colspan="1" style="width:164px" %)Temperature|(% colspan="1" style="width:152px" %)Humidity|(% colspan="1" style="width:66px" %)adc4|(% colspan="1" style="width:66px" %) | ||
| 240 | |(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod4|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" style="width:152px" %)adc0|(% colspan="1" style="width:148px" %)exit_state/input PA4|(% colspan="1" style="width:164px" %)DS18B20 Temp2|(% colspan="1" style="width:152px" %)DS18B20 Temp3|(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %) | ||
| 241 | |(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod5|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" style="width:152px" %)adc0|(% colspan="1" style="width:148px" %)exit_state/input PA4|(% colspan="1" style="width:164px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %) | ||
| 242 | |(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod6|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)count|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:148px" %) |(% colspan="1" style="width:164px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %) | ||
| |
53.2 | 243 | |
| |
56.1 | 244 | |
| |
56.2 | 245 | |
| |
53.11 | 246 | == 3.4 Datacake == |
| |
53.2 | 247 | |
| |
56.1 | 248 | === === |
| 249 | |||
| |
53.29 | 250 | === 3.4.1 Define Product === |
| |
53.2 | 251 | |
| |
53.11 | 252 | |
| |
53.24 | 253 | Firstly, we need to set the MQTT mode to datacake, and we need to run(% style="color:blue" %)** AT+PRO=3,2**(%%). This command is set to datacake. After running the command, the device automatically sets the server address, port. |
| |
53.11 | 254 | |
| |
53.24 | 255 | By chosing to add the device under a (% style="color:blue" %)**"New Product"**(%%) you are required to give a name for this product. You can name it something like (% style="color:blue" %)**"My First MQTT Product"**. |
| |
53.11 | 256 | |
| |
53.42 | 257 | [[image:image-20230802112413-14.png||height="1095" width="1302"]] |
| |
53.2 | 258 | |
| 259 | |||
| |
53.21 | 260 | === 3.4.2 Create Device === |
| 261 | |||
| 262 | |||
| |
53.2 | 263 | In the second step you have to define the device which should be added to the product. |
| 264 | |||
| |
53.29 | 265 | [[image:image-20230802112413-15.png||height="859" width="1290"]] |
| |
53.2 | 266 | |
| |
53.24 | 267 | Enter a name here (such as "My First MQTT Device") and complete the creation of the device by clicking on the (% style="color:blue" %)**"Next"**(%%) button. |
| |
53.2 | 268 | |
| 269 | |||
| |
53.21 | 270 | === 3.4.3 Create Database Fields === |
| |
53.2 | 271 | |
| |
53.21 | 272 | |
| |
53.2 | 273 | 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. |
| 274 | |||
| |
53.24 | 275 | 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 (% style="color:blue" %)**"Configuration"**. |
| |
53.2 | 276 | |
| |
53.29 | 277 | [[image:image-20230802112413-16.png||height="495" width="1310"]] |
| |
53.2 | 278 | |
| |
53.29 | 279 | [[image:image-20230802112413-17.png||height="741" width="1303"]] |
| |
53.2 | 280 | |
| |
53.24 | 281 | To create a first database field, please click on the (% style="color:blue" %)**"Add Field"**(%%) button as marked in the screenshot above. |
| |
53.2 | 282 | |
| 283 | This will open another modal asking for some required input for your first field. | ||
| 284 | |||
| |
53.29 | 285 | [[image:image-20230802112413-18.png||height="878" width="1305"]] |
| |
53.2 | 286 | |
| 287 | [[image:image-20230802112413-19.png]] | ||
| 288 | |||
| 289 | |||
| |
53.21 | 290 | === 3.4.4 Set up Broker === |
| 291 | |||
| 292 | |||
| |
53.24 | 293 | The broker is running on mqtt.datacake.co on ports (% style="color:blue" %)**1883 and 8883**(%%). Port 1883 is unsecured and should not be used in production environments. Port 8883 uses a CA signed server certificate. |
| |
53.2 | 294 | |
| 295 | 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. | ||
| 296 | |||
| 297 | View your Personal Access Token | ||
| 298 | |||
| |
53.24 | 299 | You can view your own token via the User-Settings-Menu. You can reach this menu by clicking on (% style="color:blue" %)**"Edit Profile"**(%%) at the end of the list using the Workspace Selector: |
| |
53.2 | 300 | |
| 301 | [[image:image-20230802112413-20.png]] | ||
| 302 | |||
| |
53.44 | 303 | |
| |
53.21 | 304 | (% style="color:blue" %)**MQTT Client-ID** |
| |
53.2 | 305 | |
| |
53.41 | 306 | 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 |
| 307 | specification blank. Your client then creates a randomly generated ID. | ||
| |
53.2 | 308 | |
| |
53.41 | 309 | * (% style="color:blue" %)**AT+CLIENT=“Any value”** |
| |
53.2 | 310 | |
| |
53.41 | 311 | * (% style="color:blue" %)**AT+UNAME=Token** |
| |
53.2 | 312 | |
| |
53.41 | 313 | * (% style="color:blue" %)**AT+PWD=Token** |
| |
53.2 | 314 | |
| 315 | [[image:image-20230802112413-21.png]] | ||
| 316 | |||
| 317 | |||
| |
53.21 | 318 | === 3.4.5 Create your first Subscription === |
| |
53.2 | 319 | |
| 320 | |||
| |
53.21 | 321 | (% style="color:blue" %)**Subscribe** |
| 322 | |||
| |
53.31 | 323 | Data is published according to the following structure: (% style="color:blue" %)**dtck~/~//**(%%)** ** |
| |
53.2 | 324 | |
| 325 | 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. | ||
| 326 | |||
| 327 | |||
| 328 | [[image:image-20230802112413-22.png]] | ||
| 329 | |||
| 330 | |||
| 331 | [[image:image-20230802112413-23.png]] | ||
| 332 | |||
| 333 | |||
| 334 | [[image:image-20230802112413-24.png]] | ||
| 335 | |||
| 336 | |||
| |
53.21 | 337 | (% style="color:blue" %)**example:** |
| |
53.2 | 338 | |
| 339 | AT+PUBTOPIC=dtck-pub/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature | ||
| 340 | |||
| 341 | [[image:image-20230802112413-25.png]] | ||
| 342 | |||
| 343 | |||
| |
53.21 | 344 | === 3.4.6 Define Publish Topic === |
| |
53.2 | 345 | |
| |
53.21 | 346 | |
| 347 | (% style="color:blue" %)**Publish** | ||
| 348 | |||
| |
53.2 | 349 | To upload data into the Datacake Cloud and into a specific device, you publish the data to the respective topic structure. |
| 350 | |||
| |
53.30 | 351 | Due to the nature of MQTT, the topic prefix differs as follows: (% style="color:blue" %)**dtck-pub~/~//** |
| |
53.2 | 352 | |
| |
53.21 | 353 | (% style="color:blue" %)**example:** |
| |
53.2 | 354 | |
| 355 | AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature | ||
| 356 | |||
| 357 | |||
| |
53.21 | 358 | === 3.4.7 upload data === |
| 359 | |||
| 360 | |||
| |
53.2 | 361 | [[image:image-20230802112413-26.png]] |
| 362 | |||
| 363 | [[image:image-20230802112413-27.png]] | ||
| 364 | |||
| 365 | [[image:image-20230802112413-28.png]] | ||
| 366 | |||
| 367 | |||
| |
53.21 | 368 | == 3.5 Node-Red (via MQTT) == |
| |
53.2 | 369 | |
| |
53.48 | 370 | === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] === |
| |
53.2 | 371 | |
| |
53.32 | 372 | |
| |
53.2 | 373 | [[image:image-20230802112413-29.png]] |
| 374 | |||
| |
53.32 | 375 | |
| |
53.2 | 376 | [[image:image-20230802112413-30.png]] |
| 377 | |||
| |
53.24 | 378 | |
| |
53.21 | 379 | === 3.5.2 Simulate Connection === |
| |
53.2 | 380 | |
| |
53.21 | 381 | |
| |
53.2 | 382 | [[image:image-20230802112413-31.png]] |
| 383 | |||
| 384 | |||
| |
53.21 | 385 | === 3.5.3 Configure NB-IoT Sensors === |
| |
53.2 | 386 | |
| 387 | |||
| |
53.32 | 388 | * (% style="color:blue" %)**AT+PRO=3,0(hex format) or 3,5(json format)**(%%) ~/~/ Set to mqtt Server and Payload |
| |
53.2 | 389 | |
| |
53.25 | 390 | * (% style="color:blue" %)**AT+CLIENT=any value** |
| |
53.21 | 391 | |
| |
53.25 | 392 | * (% style="color:blue" %)**AT+UNAME=any value** |
| |
53.21 | 393 | |
| |
53.25 | 394 | * (% style="color:blue" %)**AT+PWD=any value** |
| |
53.21 | 395 | |
| |
53.25 | 396 | * (% style="color:blue" %)**AT+PUBTOPIC=any value** |
| |
53.21 | 397 | |
| |
53.25 | 398 | * (% style="color:blue" %)**AT+SUBTOPIC=any value** |
| |
53.21 | 399 | |
| |
56.2 | 400 | |
| 401 | |||
| |
53.21 | 402 | == 3.6 ThingsBoard.Cloud (via MQTT) == |
| 403 | |||
| 404 | === 3.6.1 Configure ThingsBoard === | ||
| 405 | |||
| |
53.22 | 406 | ==== 3.6.1.1 Create Device ==== |
| |
53.2 | 407 | |
| |
53.32 | 408 | |
| |
53.2 | 409 | Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. |
| 410 | |||
| 411 | [[image:image-20230802112413-32.png]] | ||
| 412 | |||
| 413 | |||
| |
53.23 | 414 | ==== 3.6.1.2 Create Uplink & Downlink Converter ==== |
| 415 | |||
| |
53.32 | 416 | |
| |
53.22 | 417 | (% style="color:blue" %)**Uplink Converter** |
| |
53.2 | 418 | |
| 419 | 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. | ||
| 420 | |||
| |
53.42 | 421 | 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. |
| |
53.2 | 422 | |
| |
53.32 | 423 | [[image:image-20230802112413-33.png||height="732" width="1302"]] |
| |
53.2 | 424 | |
| 425 | |||
| |
53.22 | 426 | (% style="color:blue" %)**Downlink Converter** |
| |
53.2 | 427 | |
| 428 | The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke | ||
| 429 | |||
| |
53.32 | 430 | [[image:image-20230802112413-34.png||height="734" width="1305"]] |
| |
53.2 | 431 | |
| |
53.22 | 432 | (% style="color:red" %)**Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.** |
| |
53.2 | 433 | |
| |
53.22 | 434 | |
| |
53.23 | 435 | ==== 3.6.1.3 MQTT Integration Setup ==== |
| |
53.2 | 436 | |
| 437 | |||
| |
53.44 | 438 | 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**; |
| |
53.24 | 439 | |
| |
53.32 | 440 | [[image:image-20230802112413-35.png||height="738" width="1312"]] |
| |
53.2 | 441 | |
| |
53.32 | 442 | |
| |
53.2 | 443 | * The next steps is to add the recently created uplink and downlink converters; |
| 444 | |||
| |
53.32 | 445 | [[image:image-20230802112413-36.png||height="736" width="1308"]] |
| |
53.2 | 446 | |
| |
53.32 | 447 | [[image:image-20230802112413-37.png||height="735" width="1307"]] |
| |
53.2 | 448 | |
| |
53.33 | 449 | |
| |
53.24 | 450 | (% style="color:blue" %)**Add a topic filter:** |
| |
53.2 | 451 | |
| |
53.44 | 452 | tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature **固定的? 对的。** |
| |
53.2 | 453 | |
| 454 | You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default; | ||
| 455 | |||
| |
53.32 | 456 | [[image:image-20230802112413-38.png||height="731" width="1300"]] |
| |
53.2 | 457 | |
| 458 | |||
| |
53.23 | 459 | === 3.6.2 Simulate with MQTT.fx === |
| 460 | |||
| |
53.32 | 461 | |
| |
53.2 | 462 | [[image:image-20230802112413-39.png]] |
| 463 | |||
| 464 | [[image:image-20230802112413-40.png]] | ||
| 465 | |||
| 466 | |||
| |
53.23 | 467 | === 3.6.3 Configure NB-IoT Sensor === |
| |
53.2 | 468 | |
| |
53.25 | 469 | |
| |
53.23 | 470 | (% style="color:blue" %)**AT Commands** |
| |
53.2 | 471 | |
| |
53.25 | 472 | * (% style="color:#037691" %)**AT+PRO=3,3 **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. |
| |
53.2 | 473 | |
| |
53.44 | 474 | * (% style="color:#037691" %)**AT+SUBTOPIC=device name** (%%) **~-~-> 只需要 Device Name 吗?对的** |
| |
53.2 | 475 | |
| |
53.44 | 476 | * (% style="color:#037691" %)**AT+PUBTOPIC=device name** (%%) **~-~-> 只需要 Device Name 吗?对的** |
| |
53.2 | 477 | |
| |
53.44 | 478 | 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 吧).这边不用提示了，客户不需要输入。（大部分客户还是会自己去设置这个的，提高安全性）** |
| |
53.2 | 479 | |
| |
53.23 | 480 | (% style="color:blue" %)**CLIENT :“Any value”** |
| |
53.2 | 481 | |
| |
53.23 | 482 | (% style="color:blue" %)**User Name:“Any value”** |
| |
53.2 | 483 | |
| |
53.23 | 484 | (% style="color:blue" %)**Password:“Any value”** |
| |
53.2 | 485 | |
| 486 | |||
| 487 | Test Uplink by click the button for 1 second | ||
| 488 | |||
| 489 | [[image:image-20230802112413-41.png]] | ||
| 490 | |||
| 491 | [[image:image-20230802112413-42.png]] | ||
| 492 | |||
| 493 | [[image:image-20230802112413-43.png]] | ||
| 494 | |||
| 495 | |||
| |
53.23 | 496 | == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) == |
| |
53.2 | 497 | |
| |
53.23 | 498 | === 3.7.1 Create device & Get Credentials === |
| |
53.2 | 499 | |
| |
53.23 | 500 | |
| |
53.2 | 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. |
| 502 | |||
| 503 | [[image:image-20230802112413-44.png]] | ||
| 504 | |||
| 505 | [[image:image-20230802112413-45.png]] | ||
| 506 | |||
| 507 | |||
| 508 | Go to the Device section and create a device. Then, go to the section tokens and copy your device-token. | ||
| 509 | |||
| 510 | [[image:image-20230802112413-46.png]] | ||
| 511 | |||
| 512 | |||
| |
53.44 | 513 | On the Connection Profile window, set the following information: **(这边加一个截图)** |
| |
53.2 | 514 | |
| |
53.23 | 515 | * (% style="color:blue" %)**Profile Name: “Any name”** |
| |
53.2 | 516 | |
| |
53.23 | 517 | * (% style="color:blue" %)**Broker Address: mqtt.tago.io** |
| 518 | |||
| 519 | * (% style="color:blue" %)**Broker Port: 1883** | ||
| 520 | |||
| 521 | * (% style="color:blue" %)**Client ID: “Any value”** | ||
| 522 | |||
| |
53.44 | 523 | On the section User credentials, set the following information: **(这边加一个截图)** |
| |
53.2 | 524 | |
| |
53.34 | 525 | * (% style="color:blue" %)**User Name: “Any value”** (%%) ~/~/ Tago validates your user by the token only |
| |
53.2 | 526 | |
| |
53.34 | 527 | * (% style="color:blue" %)**Password: “Your device token”** |
| |
53.2 | 528 | |
| |
53.34 | 529 | * (% style="color:blue" %)**PUBTOPIC: “Any value”** |
| |
53.23 | 530 | |
| |
53.34 | 531 | * (% style="color:blue" %)**SUBTOPIC: “Any value”** |
| |
53.23 | 532 | |
| |
56.2 | 533 | |
| 534 | |||
| |
53.23 | 535 | === 3.7.2 Simulate with MQTT.fx === |
| 536 | |||
| 537 | |||
| |
53.2 | 538 | [[image:image-20230802112413-47.png]] |
| 539 | |||
| 540 | [[image:image-20230802112413-48.png]] | ||
| 541 | |||
| |
53.38 | 542 | Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**. |
| |
53.2 | 543 | |
| |
53.44 | 544 | |
| |
53.2 | 545 | [[image:image-20230802112413-49.png]] |
| 546 | |||
| 547 | |||
| |
53.23 | 548 | === 3.7.3 tago data === |
| |
53.2 | 549 | |
| |
53.23 | 550 | |
| |
53.2 | 551 | [[image:image-20230802112413-50.png]] |
| 552 | |||
| 553 | [[image:image-20230802112413-51.png]] | ||
| 554 | |||
| 555 | |||
| |
53.23 | 556 | === 3.7.4 TLS mode === |
| |
53.2 | 557 | |
| 558 | |||
| |
53.23 | 559 | Users can choose to use (% style="color:blue" %)**SSL/TLS**(%%) mode. |
| |
53.2 | 560 | |
| |
53.23 | 561 | On the SSL/TLS section, check the option **Enable SSL/TLS**, and click OK. |
| |
53.2 | 562 | |
| |
53.23 | 563 | The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command. |
| 564 | |||
| 565 | * (% style="color:blue" %)**Profile Name: “Any name”** | ||
| 566 | |||
| 567 | * (% style="color:blue" %)**Broker Address: mqtt.tago.io** | ||
| 568 | |||
| 569 | * (% style="color:blue" %)**Broker Port: 8883** | ||
| 570 | |||
| 571 | * (% style="color:blue" %)**Client ID: “Any value”** | ||
| 572 | |||
| |
53.36 | 573 | * (% style="color:blue" %)**User Name: “Any value”** (%%) ~/~/ Tago validates your user by the token only |
| |
53.23 | 574 | |
| 575 | * (% style="color:blue" %)**Password: “Your device token”** | ||
| 576 | |||
| 577 | * (% style="color:blue" %)**PUBTOPIC: “Any value”** | ||
| 578 | |||
| 579 | * (% style="color:blue" %)**SUBTOPIC: “Any value”** | ||
| 580 | |||
| |
53.2 | 581 | [[image:image-20230802112413-52.png]] |
| 582 | |||
| 583 | |||
| |
53.43 | 584 |