Changes for page General Configure/Commands to Connect to IoT server for -NB & -NS NB-IoT models

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 27 added, 0 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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Xiaoling
	1	+XWiki.Edwin

Content

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