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, 29 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
  • image-20230816201942-1.png
  • image-20240129170024-1.png

Details

Page properties

Author

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

Content

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

image-20230807233631-1.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+21.9 KB

Content

image-20230807233631-2.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+9.6 KB

Content

image-20230808105217-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+68.5 KB

Content

image-20230808105300-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+70.1 KB

Content

image-20230808105329-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+21.1 KB

Content

image-20230808162301-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+76.9 KB

Content

image-20230808162342-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+63.8 KB

Content

image-20230808162421-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+59.2 KB

Content

image-20230808162727-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+54.2 KB

Content

image-20230808163035-5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+71.6 KB

Content

image-20230808163049-6.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+61.5 KB

Content

image-20230808163612-7.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+53.4 KB

Content

image-20230808170051-8.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+21.5 KB

Content

image-20230808170548-9.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+54.1 KB

Content

image-20230808205045-1.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+373.9 KB

Content

image-20230809165928-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+74.4 KB

Content

image-20230809170225-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+39.9 KB

Content

image-20230809170532-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+38.7 KB

Content

image-20230809173127-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+82.5 KB

Content

image-20230809173310-5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+51.9 KB

Content

image-20230809173438-6.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+41.0 KB

Content

image-20230809173800-7.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+46.8 KB

Content

image-20230809173835-8.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+88.8 KB

Content

image-20230809174053-9.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+58.0 KB

Content

image-20230809180523-10.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+91.9 KB

Content

image-20230810083934-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+85.1 KB

Content

image-20230810084048-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+63.7 KB

Content

image-20230816201942-1.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+99.8 KB

Content

image-20240129170024-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Bei

Size

...	...	@@ -1,0 +1,1 @@
	1	+52.3 KB

Content