Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,393 +1,349 @@
1		-~(% class="wikigeneratedid" id="HTableofContents:" %)
2		-~*~*Table of Contents:~*~*
	1	+​
3	3
4		-~{~{toc/}}
5	5
	4	+(% class="wikigeneratedid" id="HTableofContents:" %)
	5	+**Table of Contents:**
6	6
	7	+{{toc/}}
7	7
	9	+= 1. The use of this guideline =
8	8
9		-~= 1. The use of this guideline =
	11	+This configure instruction is for Dragino NB-IoT models with -CB or -CS suffix, for example DDS75-CB. These models use the same NB-IoT Module **[[BG95-M2>>https://www.dropbox.com/sh/3ilyaswz4odgaru/AADR86cAgL9UGlmLuEH-UZgla?st=x1ry6v5j&dl=0]]** 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.
10	10
11	11
12		-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.
	14	+= 2. Attach Network =
13	13
	16	+== 2.1 General Configure to attach network ==
14	14
15		-~= 2. Attach Network =
	18	+To attache end nodes to NB-IoT or LTE-M Network, You need to:
16	16
17		-~== 2.1 General Configure to attach network ==
	20	+1. Get a NB-IoT or LTE-M SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
	21	+1. Power Off End Node ( See below for the power off/on position)
	22	+1. Insert the SIM card to Sensor. ( See below for direction)
	23	+1. Power On End Node
	24	+1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>), example AT+APN=iot.1nce.net
18	18
	26	+[[image:image-20240208102804-1.png||height="286" width="696"]]
19	19
20		-To attache NB-IoT sensors to NB-IoT Network, You need to:
	28	+[[image:image-20230808205045-1.png||height="293" width="438"]]
21	21
22		-~1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
23		-~1. Power Off End Node ( See below for the power off/on position)
24		-~1. Insert the SIM card to Sensor. ( See below for direction)
25		-~1. Power On End Node
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>), example AT+APN=iot.1nce.net
	30	+After doing above, the end nodes should be able to attach to NB-IoT network .
27	27
28		-~[~[image~:image-20240208102804-1.png||height="286" width="696"]]
	32	+The -CB and -CS models support (% style="color:blue" %)**LTE Cat NB2 and LTE-M (CAT-M1)**(%%), with below frequency band: multiple frequency bands of
29	29
30		-~[~[image~:image-20230808205045-1.png||height="293" width="438"]]
	34	+~-~-(% style="color:blue" %)**CAT-NB2: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B28/B66/B71/B85 **(%%).
31	31
32		-After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
	36	+~-~-(% style="color:blue" %)**CAT-M1: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85 **(%%).
33	33
34		-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.
	38	+Make sure you use a the NB-IoT SIM card.
35	35
36		-~(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
37		-~|~(% 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~*~*
38		-~|~(% style="width:117px" %)~*~*~[~[1NCE>>https:~/~/1nce.com]]~*~*|~(% style="width:151px" %)iot.1nce.net|~(% style="width:474px" %)~(~(~(
39		-~*~*~[~[Coverage Reference Link>>https:~/~/1nce.com/en-ap/1nce-connect]]~*~*
	40	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
	41	+|(% 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**
	42	+|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
	43	+**[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
40	40
41	41	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, UK, US Virgin Islands
42		-~)~)~)|~(% style="width:135px" %)UK: Band20
43		-~|~(% style="width:117px" %)China Mobile|~(% style="width:151px" %)No need configure|~(% style="width:474px" %)China Mainland, HongKong|~(% style="width:135px" %)
44		-~|~(% style="width:117px" %)China Telecom|~(% style="width:151px" %)ctnb|~(% style="width:474px" %)China Mainland|~(% style="width:135px" %)
	46	+)))|(% style="width:135px" %)UK: Band20
	47	+|(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
	48	+|(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
45	45
46		-~== 2.2 Speed Up Network Attach time ==
	50	+== 2.2 Speed Up Network Attach time ==
47	47
	52	+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 and show **Signal Strenght:99**. User can lock the band to specify band for its operator to make this faster.
48	48
49		-BC660K-GL supports multi bands ~(% style="color:blue" %)~*~*B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85. ~*~*~(%%) It will search one by one and try to attach, this will take a lot of time and even cause attach fail and show ~*~*Signal Strenght:99~*~*. User can lock the band to specify band for its operator to make this faster.
	54	+(% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
	55	+(% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
	56	+(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
	57	+(% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=10,8,20,28,2,4,12,13,66,85,5**
50	50
51		-~(% style="color:#037691" %)~*~*AT+QBAND?       ~*~*~(%%) ~~/~~/ Check what is the current used frequency band
52		-~(% style="color:#037691" %)~*~*AT+QBAND=1,4    ~*~*~(%%) ~~/~~/ Set to use 1 frequency band. Band4
53		-~(% style="color:#037691" %)~*~*Europe General~*~*~(%%) ~*~*AT+QBAND=2,8,20 ~*~* ~~/~~/ Set to use 2 frequency bands. Band 8 and Band 20
54		-~(% style="color:#037691" %)~*~*Global General~*~*~(%%) : ~*~*AT+QBAND=10,8,20,28,2,4,12,13,66,85,5~*~*
	59	+(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
	60	+(% style="color:#037691" %)**AT&T**(%%) AT+QBAND=3,12,4,2
	61	+(% style="color:#037691" %)**Telstra**(%%) AT+QBAND=1,28
	62	+(% style="color:#037691" %)**Softband**(%%) AT+QBAND=2,3,8
55	55
56		-~(% style="color:#037691" %)~*~*Verizon~*~*~(%%)~*~* ~*~*      AT+QBAND=1,13
57		-~(% style="color:#037691" %)~*~*AT&T~*~*~(%%)           AT+QBAND=3,12,4,2
58		-~(% style="color:#037691" %)~*~*Telstra~*~*~(%%)        AT+QBAND=1,28
59		-~(% style="color:#037691" %)~*~*Softband~*~*~(%%)     AT+QBAND=2,3,8
	64	+After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
60	60
61		-After connection is successful, user can use ~(% style="color:#037691" %)~*~*AT+QENG=0 ~*~*~(%%) to check which band is actually in used.
	66	+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/]]**
62	62
	68	+= 3. Configure to connect to different servers =
63	63
64		-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/]]~*~*
	70	+== 3.1 General UDP Connection ==
65	65
	72	+The NB-IoT Sensor can send packet to server use UDP protocol.
66	66
67		-~= 3. Configure to connect to different servers =
	74	+=== 3.1.1 Simulate UDP Connection by PC tool ===
68	68
69		-~== 3.1 General UDP Connection ==
	76	+We can use PC tool to simulate UDP connection to make sure server works ok.
70	70
	78	+[[image:image-20230802112413-1.png||height="468" width="1024"]]
71	71
72		-The NB-IoT Sensor can send packet to server use UDP protocol.
	80	+=== 3.1.2 Configure NB-IoT Sensor ===
73	73
	82	+==== 3.1.2.1 AT Commands ====
74	74
75		-~=== 3.1.1 Simulate UDP Connection by PC tool ===
	84	+(% style="color:blue" %)**AT Commands:**
76	76
	86	+* (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload
77	77
78		-We can use PC tool to simulate UDP connection to make sure server works ok.
	88	+* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/ Set UDP server address and port
79	79
80		-~[~[image~:image-20230802112413-1.png||height="468" width="1024"]]
	90	+[[image:image-20230802112413-2.png]]
81	81
	92	+==== 3.1.2.2 Uplink Example ====
82	82
83		-~=== 3.1.2 Configure NB-IoT Sensor ===
	94	+[[image:image-20230802112413-3.png]]
84	84
85		-~==== 3.1.2.1 AT Commands ====
	96	+== 3.2 General MQTT Connection ==
86	86
	98	+The NB-IoT Sensor can send packet to server use MQTT protocol.
87	87
88		-~(% style="color:blue" %)~*~*AT Commands:~*~*
	100	+Below are the commands.
89	89
90		-~* ~(% style="color:#037691" %)~*~*AT+PRO=2,0~*~*  ~(%%)       ~~/~~/  Set to use UDP protocol to uplink ,Payload Type select Hex payload
	102	+(% style="color:blue" %)**AT Commands:**
91	91
92		-~* ~(% style="color:#037691" %)~*~*AT+SERVADDR=120.24.4.116,5601~*~*  ~(%%)    ~~/~~/  Set UDP server address and port
	104	+* (% style="color:#037691" %)**AT+PRO=3,0**   (%%) ~/~/ Set to use MQTT protocol to uplink, Payload Type select Hex payload.
93	93
94		-~[~[image~:image-20230802112413-2.png]]
	106	+* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883**  (%%) ~/~/ Set MQTT server address and port
95	95
	108	+* (% style="color:#037691" %)**AT+CLIENT=CLIENT**     (%%) ~/~/ Set up the CLIENT of MQTT
96	96
97		-~==== 3.1.2.2 Uplink Example ====
	110	+* (% style="color:#037691" %)**AT+UNAME=UNAME**        (%%) ~/~/ Set the username of MQTT
98	98
	112	+* (% style="color:#037691" %)**AT+PWD=PWD**             (%%) ~/~/ Set the password of MQTT
99	99
100		-~[~[image~:image-20230802112413-3.png]]
	114	+* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB**  (%%) ~/~/ Set the sending topic of MQTT
101	101
	116	+* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB**  (%%) ~/~/ Set the subscription topic of MQTT
102	102
103		-~== 3.2 General MQTT Connection ==
	118	+[[image:image-20230802112413-4.png]]
104	104
	120	+[[image:image-20230802112413-5.png||height="530" width="987"]]
105	105
106		-The NB-IoT Sensor can send packet to server use MQTT protocol.
	122	+(% style="color:red" %)**Notice: MQTT protocol has a much higher power consumption compare with UDP/CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.**
107	107
108		-Below are the commands.
	124	+== 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
109	109
110		-~(% style="color:blue" %)~*~*AT Commands:~*~*
	126	+=== 3.3.1 Get MQTT Credentials ===
111	111
112		-~* ~(% style="color:#037691" %)~*~*AT+PRO=3,0~*~*   ~(%%)   ~~/~~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
	128	+[[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.
113	113
114		-~* ~(% style="color:#037691" %)~*~*AT+SERVADDR=120.24.4.116,1883~*~*  ~(%%)      ~~/~~/  Set MQTT server address and port
	130	+[[image:image-20230802112413-6.png||height="336" width="925"]]
115	115
116		-~* ~(% style="color:#037691" %)~*~*AT+CLIENT=CLIENT~*~*     ~(%%)                            ~~/~~/  Set up the CLIENT of MQTT
	132	+[[image:image-20230802112413-7.png]]
117	117
118		-~* ~(% style="color:#037691" %)~*~*AT+UNAME=UNAME~*~*        ~(%%)                      ~~/~~/  Set the username of MQTT
	134	+=== 3.3.2 Simulate with MQTT.fx ===
119	119
120		-~* ~(% style="color:#037691" %)~*~*AT+PWD=PWD~*~*             ~(%%)                           ~~/~~/  Set the password of MQTT
	136	+==== 3.3.2.1 Establish MQTT Connection ====
121	121
122		-~* ~(% style="color:#037691" %)~*~*AT+PUBTOPIC=NSE01_PUB~*~*  ~(%%)                  ~~/~~/  Set the sending topic of MQTT
	138	+After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
123	123
124		-~* ~(% style="color:#037691" %)~*~*AT+SUBTOPIC=NSE01_SUB~*~*  ~(%%)                  ~~/~~/  Set the subscription topic of MQTT
	140	+[[image:image-20230802112413-8.png]]
125	125
126		-~[~[image~:image-20230802112413-4.png]]
	142	+* (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
127	127
128		-~[~[image~:image-20230802112413-5.png||height="530" width="987"]]
	144	+* (% style="color:#037691" %)**Broker Port:**(%%) 1883
129	129
130		-~(% 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.~*~*
	146	+* (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID>
131	131
	148	+* (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name>
132	132
133		-~== 3.3 ~[~[ThingSpeak>>url:https:~/~/thingspeak.com/]] (via MQTT) ==
	150	+* (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
134	134
135		-~=== 3.3.1 Get MQTT Credentials ===
	152	+==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
136	136
	154	+[[image:image-20230802112413-9.png]]
137	137
138		-~[~[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.
	156	+[[image:image-20230802112413-10.png]]
139	139
140		-~[~[image~:image-20230802112413-6.png||height="336" width="925"]]
	158	+(% style="color:blue" %)**In MQTT.fx, we can publish below info:**
141	141
142		-~[~[image~:image-20230802112413-7.png]]
	160	+* (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
143	143
	162	+* (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH
144	144
145		-~=== 3.3.2 Simulate with MQTT.fx ===
	164	+Where 63 and 67 are the value to be published to field1 & field2.
146	146
147		-~==== 3.3.2.1 Establish MQTT Connection ====
	166	+(% style="color:blue" %)**Result: **
148	148
	168	+[[image:image-20230802112413-11.png||height="539" width="901"]]
149	149
150		-After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
	170	+=== 3.3.3 Configure NB-IoT Sensor for connection ===
151	151
152		-~[~[image~:image-20230802112413-8.png]]
	172	+==== 3.3.3.1 AT Commands: ====
153	153
154		-~* ~(% style="color:#037691" %)~*~*Broker Address:~*~*~(%%) mqtt3.thingspeak.com
	174	+In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
155	155
156		-~* ~(% style="color:#037691" %)~*~*Broker Port:~*~*~(%%) 1883
	176	+* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
157	157
158		-~* ~(% style="color:#037691" %)~*~*Client ID:~*~*~(%%) <Your ThingSpeak MQTT ClientID>
	178	+* (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
159	159
160		-~* ~(% style="color:#037691" %)~*~*User Name:~*~*~(%%) <Your ThingSpeak MQTT User Name>
	180	+* (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
161	161
162		-~* ~(% style="color:#037691" %)~*~*Password:~*~*~(%%) <Your ThingSpeak MQTT Password>
	182	+* (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>**
163	163
164		-~==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
	184	+* (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
165	165
	186	+* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
166	166
167		-~[~[image~:image-20230802112413-9.png]]
	188	+==== 3.3.3.2 Uplink Examples ====
168	168
169		-~[~[image~:image-20230802112413-10.png]]
	190	+[[image:image-20230816201942-1.png]]
170	170
	192	+For SE01-NB
171	171
172		-~(% style="color:blue" %)~*~*In MQTT.fx, we can publish below info:~*~*
	194	+For DDS20-NB
173	173
174		-~* ~(% style="color:#037691" %)~*~*Topic:~*~*~(%%) channels/YOUR_CHANNEL_ID/publish
	196	+For DDS45-NB
175	175
176		-~* ~(% style="color:#037691" %)~*~*Payload:~*~*~(%%) field1=63&field2=67&status=MQTTPUBLISH
	198	+For DDS75-NB
177	177
178		-Where 63 and 67 are the value to be published to field1 & field2.
	200	+For NMDS120-NB
179	179
	202	+For SPH01-NB
180	180
181		-~(% style="color:blue" %)~*~*Result: ~*~*
	204	+For NLM01-NB
182	182
183		-~[~[image~:image-20230802112413-11.png||height="539" width="901"]]
	206	+For NMDS200-NB
184	184
	208	+For CPN01-NB
185	185
186		-~=== 3.3.3 Configure NB-IoT Sensor for connection ===
	210	+For DS03A-NB
187	187
188		-~==== 3.3.3.1 AT Commands: ====
	212	+For SN50V3-NB
189	189
	214	+==== 3.3.3.3 Map fields to sensor value ====
190	190
191		-In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
	216	+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.
192	192
193		-~* ~(% style="color:blue" %)~*~*AT+PRO=3,1~*~* ~(%%)    ~~/~~/ Set to use ThingSpeak Server and Related Payload
	218	+[[image:image-20230802112413-12.png||height="504" width="1011"]]
194	194
195		-~* ~(% style="color:blue" %)~*~*AT+CLIENT=<Your ThingSpeak MQTT ClientID>~*~*
	220	+[[image:image-20230802112413-13.png||height="331" width="978"]]
196	196
197		-~* ~(% style="color:blue" %)~*~*AT+UNAME=<Your ThingSpeak MQTT User Name>~*~*
	222	+Below is the NB-IoT Product Table show the mapping.
198	198
199		-~* ~(% style="color:blue" %)~*~*AT+PWD=<Your ThingSpeak MQTT Password>~*~*
	224	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
	225	+|(% 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
	226	+|(% 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" %)
	227	+|(% 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" %)
	228	+|(% 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" %)
	229	+|(% 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" %)
	230	+|(% 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" %)
	231	+|(% 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" %)
	232	+|(% 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" %)
	233	+|(% 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" %)
	234	+|(% 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" %)
	235	+|(% 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" %)
	236	+|(% 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
	237	+|(% 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" %)
	238	+|(% 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" %)
	239	+|(% 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" %)
	240	+|(% 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" %)
	241	+|(% 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" %)
	242	+|(% 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" %)
200	200
201		-~* ~(% style="color:blue" %)~*~*AT+PUBTOPIC=<YOUR_CHANNEL_ID>~*~*
	244	+== 3.4 [[Datacake>>https://datacake.co/]] ==
202	202
203		-~* ~(% style="color:blue" %)~*~*AT+SUBTOPIC=<YOUR_CHANNEL_ID>~*~*
	246	+(% class="wikigeneratedid" %)
	247	+Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
204	204
205		-~==== 3.3.3.2 Uplink Examples ====
	249	+(% class="wikigeneratedid" %)
	250	+As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
206	206
	252	+* (% 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.
207	207
208		-~[~[image~:image-20230816201942-1.png]]
	254	+* (% 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.
209	209
210		-For SE01-NB
	256	+=== 3.4.1 For device Already has template ===
211	211
212		-For DDS20-NB
	258	+==== 3.4.1.1 Create Device ====
213	213
214		-For DDS45-NB
	260	+(% style="color:blue" %)**Add Device**(%%) in DataCake.
215	215
216		-For DDS75-NB
	262	+[[image:image-20230808162301-1.png||height="453" width="952"]]
217	217
218		-For NMDS120-NB
	264	+[[image:image-20230808162342-2.png||height="541" width="952"]]
219	219
220		-For SPH01-NB
	266	+(% style="color:blue" %)**Choose the correct model**(%%) from template.
221	221
222		-For NLM01-NB
	268	+[[image:image-20230808162421-3.png]]
223	223
224		-For NMDS200-NB
	270	+(% 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.
225	225
226		-For CPN01-NB
	272	+[[image:image-20230808163612-7.png||height="549" width="952"]]
227	227
228		-For DS03A-NB
	274	+[[image:image-20230808163035-5.png]]
229	229
230		-For SN50V3-NB
	276	+[[image:image-20230808163049-6.png||height="544" width="926"]]
231	231
	278	+=== 3.4.2 For Device already registered in DataCake before shipped ===
232	232
233		-~==== 3.3.3.3 Map fields to sensor value ====
	280	+==== 3.4.2.1 Scan QR Code to get the device info ====
234	234
235		-
236		-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.
237		-
238		-
239		-~[~[image~:image-20230802112413-12.png||height="504" width="1011"]]
240		-
241		-~[~[image~:image-20230802112413-13.png||height="331" width="978"]]
242		-
243		-
244		-Below is the NB-IoT Product Table show the mapping.
245		-
246		-~(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
247		-~|~(% 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
248		-~|~(% 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" %)
249		-~|~(% 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" %)
250		-~|~(% 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" %)
251		-~|~(% 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" %)
252		-~|~(% 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" %)
253		-~|~(% 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" %)
254		-~|~(% 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" %)
255		-~|~(% 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" %)
256		-~|~(% 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" %)
257		-~|~(% 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" %)
258		-~|~(% 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
259		-~|~(% 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" %)
260		-~|~(% 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" %)
261		-~|~(% 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" %)
262		-~|~(% 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" %)
263		-~|~(% 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" %)
264		-~|~(% 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" %)
265		-
266		-~== 3.4 ~[~[Datacake>>https:~/~/datacake.co/]] ==
267		-
268		-
269		-~(% class="wikigeneratedid" %)
270		-Dragino NB-IoT sensors has its template in ~*~*~[~[Datacake>>https:~/~/datacake.co/]]~*~* Platform. There are two version for NB Sensor,
271		-
272		-
273		-~(% class="wikigeneratedid" %)
274		-As example for S31B-NB. there are two versions: ~*~*S31B-NB-1D and S31B-NB-GE.~*~*
275		-
276		-~* ~(% 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.
277		-
278		-~* ~(% 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.
279		-
280		-~=== 3.4.1 For device Already has template ===
281		-
282		-~==== 3.4.1.1 Create Device ====
283		-
284		-~(% style="color:blue" %)~*~*Add Device~*~*~(%%) in DataCake.
285		-
286		-~[~[image~:image-20230808162301-1.png||height="453" width="952"]]
287		-
288		-
289		-~[~[image~:image-20230808162342-2.png||height="541" width="952"]]
290		-
291		-
292		-~(% style="color:blue" %)~*~*Choose the correct model~*~*~(%%) from template.
293		-
294		-~[~[image~:image-20230808162421-3.png]]
295		-
296		-
297		-~(% 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.
298		-
299		-~[~[image~:image-20230808163612-7.png||height="549" width="952"]]
300		-
301		-~[~[image~:image-20230808163035-5.png]]
302		-
303		-~[~[image~:image-20230808163049-6.png||height="544" width="926"]]
304		-
305		-
306		-~=== 3.4.2 For Device already registered in DataCake before shipped ===
307		-
308		-~==== 3.4.2.1 Scan QR Code to get the device info ====
309		-
310		-
311	311	Users can use their phones or computers to scan QR codes to obtain device data information.
312	312
313		-~[~[image~:image-20230808170051-8.png||height="255" width="259"]]
	284	+[[image:image-20230808170051-8.png||height="255" width="259"]]
314	314
315		-~[~[image~:image-20230808170548-9.png]]
	286	+[[image:image-20230808170548-9.png]]
316	316
	288	+==== 3.4.2.2 Claim Device to User Account ====
317	317
318		-~==== 3.4.2.2 Claim Device to User Account ====
319		-
320		-
321	321	By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
322	322
	292	+=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
323	323
324		-~=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
	294	+**Step1: Add a device**
325	325
	296	+[[image:image-20240129170024-1.png||height="330" width="900"]]
326	326
327		-~*~*Step1: Add a device~*~*
	298	+**Step2: Choose your device type,please select dragino NB-IOT device**
328	328
329		-~[~[image~:image-20240129170024-1.png||height="330" width="900"]]
	300	+[[image:image-20240129170216-2.png||height="534" width="643"]]
330	330
	302	+**Step3: Choose to create a new device**
331	331
332		-~*~*Step2: Choose your device type,please select dragino NB-IOT device~*~*
	304	+[[image:image-20240129170539-3.png||height="459" width="646"]]
333	333
334		-~[~[image~:image-20240129170216-2.png||height="534" width="643"]]
	306	+**Step4: Fill in the device ID of your NB device**
335	335
	308	+[[image:image-20240202111546-1.png||height="378" width="651"]]
336	336
337		-~*~*Step3: Choose to create a new device~*~*
	310	+**Step5: Please select your device plan according to your needs and complete the creation of the device**
338	338
339		-~[~[image~:image-20240129170539-3.png||height="459" width="646"]]
	312	+[[image:image-20240129171236-6.png||height="450" width="648"]]
340	340
	314	+**Step6: Please add the decoder at the payload decoder of the device configuration.**
341	341
342		-~*~*Step4: Fill in the device ID of your NB device~*~*
	316	+**Decoder location:**[[dragino-end-node-decoder/Datacake-Dragino_NB at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB]]
343	343
344		-~[~[image~:image-20240202111546-1.png||height="378" width="651"]]
	318	+[[image:image-20240129172056-7.png||height="457" width="816"]]
345	345
	320	+[[image:image-20240129173116-9.png||height="499" width="814"]]
346	346
347		-~*~*Step5: Please select your device plan according to your needs and complete the creation of the device~*~*
	322	+**Step7: Add the output of the decoder as a field**
348	348
349		-~[~[image~:image-20240129171236-6.png||height="450" width="648"]]
	324	+[[image:image-20240129173541-10.png||height="592" width="968"]]
350	350
	326	+**Step8: Customize the dashboard and use fields as parameters of the dashboard**
351	351
352		-~*~*Step6: Please add the decoder at the payload decoder of the device configuration.~*~*
	328	+[[image:image-20240129174518-11.png||height="147" width="1042"]]
353	353
354		-~*~*Decoder location:~*~*~[~[dragino-end-node-decoder/Datacake-Dragino_NB at main · dragino/dragino-end-node-decoder (github.com)>>url:https:~/~/github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB]]
	330	+[[image:image-20240129174657-12.png||height="538" width="916"]]
355	355
356		-~[~[image~:image-20240129172056-7.png||height="457" width="816"]]
	332	+[[image:image-20240129174840-13.png||height="536" width="750"]]
357	357
358		-~[~[image~:image-20240129173116-9.png||height="499" width="814"]]
	334	+=== 3.4.4 For device have not configured to connect to DataCake ===
359	359
360		-
361		-~*~*Step7: Add the output of the decoder as a field~*~*
362		-
363		-~[~[image~:image-20240129173541-10.png||height="592" width="968"]]
364		-
365		-
366		-~*~*Step8: Customize the dashboard and use fields as parameters of the dashboard~*~*
367		-
368		-~[~[image~:image-20240129174518-11.png||height="147" width="1042"]]
369		-
370		-~[~[image~:image-20240129174657-12.png||height="538" width="916"]]
371		-
372		-~[~[image~:image-20240129174840-13.png||height="536" width="750"]]
373		-
374		-
375		-~=== 3.4.4 For device have not configured to connect to DataCake ===
376		-
377		-
378		-~(% class="lead" %)
	336	+(% class="lead" %)
379	379	Use AT command for connecting to DataCake
380	380
381		-~(% style="color:blue" %)~*~*AT+PRO=2,0~*~*
	339	+(% style="color:blue" %)**AT+PRO=2,0**
382	382
383		-~(% style="color:blue" %)~*~*AT+SERVADDR=67.207.76.90,4445~*~*
	341	+(% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
384	384
	343	+== 3.5 Node-Red (via MQTT) ==
385	385
386		-~== 3.5 Node-Red (via MQTT) ==
	345	+=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
387	387
388		-~=== 3.5.1 Configure ~[~[Node-Red>>http:~/~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
389		-
390		-
391	391	Take S31-NB UDP protocol as an example.
392	392
393	393	Dragino provides input flow examples for the sensors.
...	...	@@ -394,420 +394,330 @@
394	394
395	395	User can download the required JSON file through Dragino Node-RED input flow template.
396	396
397		-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]]
	353	+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]]
398	398
399	399	We can directly import the template.
400	400
401	401	The templates for S31-NB and NB95S31B are the same.
402	402
	359	+[[image:image-20230809173127-4.png]]
403	403
404		-~[~[image~:image-20230809173127-4.png]]
405		-
406		-
407	407	Please select the NB95S31B template.
408	408
409		-~[~[image~:image-20230809173310-5.png||height="558" width="926"]]
	363	+[[image:image-20230809173310-5.png||height="558" width="926"]]
410	410
411		-~[~[image~:image-20230809173438-6.png]]
	365	+[[image:image-20230809173438-6.png]]
412	412
413		-~[~[image~:image-20230809173800-7.png]]
	367	+[[image:image-20230809173800-7.png]]
414	414
415		-
416	416	Successfully imported template.
417	417
418		-~[~[image~:image-20230809173835-8.png||height="515" width="860"]]
	371	+[[image:image-20230809173835-8.png||height="515" width="860"]]
419	419
420		-
421	421	Users can set UDP port.
422	422
423		-~[~[image~:image-20230809174053-9.png]]
	375	+[[image:image-20230809174053-9.png]]
424	424
	377	+=== 3.5.2 Simulate Connection ===
425	425
426		-~=== 3.5.2 Simulate Connection ===
427		-
428		-
429	429	We have completed the configuration of UDP. We can try sending packets to node red.
430	430
431		-~[~[image~:image-20230810083934-1.png]]
	381	+[[image:image-20230810083934-1.png]]
432	432
433		-~[~[image~:image-20230810084048-2.png||height="535" width="1052"]]
	383	+[[image:image-20230810084048-2.png||height="535" width="1052"]]
434	434
	385	+=== 3.5.3 Configure NB-IoT Sensors ===
435	435
436		-~=== 3.5.3 Configure NB-IoT Sensors ===
	387	+* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
	388	+* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
	389	+* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
	390	+* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
	391	+* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
	392	+* (% style="color:#037691" %)**AT+PWD=“Your device token”**
437	437
	394	+== 3.6 ThingsBoard.Cloud (via MQTT) ==
438	438
439		-~* ~(% style="color:#037691" %)~*~*AT+PRO=3,0 or 3,5 ~*~* ~(%%)   ~*~*~~/~~/ hex format or json format~*~*
440		-~* ~(% style="color:#037691" %)~*~*AT+SUBTOPIC=<device name>or User Defined~*~*
441		-~* ~(% style="color:#037691" %)~*~*AT+PUBTOPIC=<device name>or User Defined~*~*
442		-~* ~(% style="color:#037691" %)~*~*AT+CLIENT=<device name> or User Defined~*~*
443		-~* ~(% style="color:#037691" %)~*~*AT+UNAME=<device name> or User Defined~*~*
444		-~* ~(% style="color:#037691" %)~*~*AT+PWD=“Your device token”~*~*
	396	+=== 3.6.1 Configure ThingsBoard ===
445	445
446		-~== 3.6 ThingsBoard.Cloud (via MQTT) ==
	398	+==== 3.6.1.1 Create Device ====
447	447
448		-~=== 3.6.1 Configure ThingsBoard ===
	400	+Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
449	449
450		-~==== 3.6.1.1 Create Device ====
	402	+[[image:image-20230802112413-32.png||height="583" width="1066"]]
451	451
	404	+==== 3.6.1.2 Create Uplink & Downlink Converter ====
452	452
453		-Create a New Device in ~[~[ThingsBoard>>url:https:~/~/thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
	406	+(% style="color:blue" %)**Uplink Converter**
454	454
455		-~[~[image~:image-20230802112413-32.png||height="583" width="1066"]]
	408	+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.
456	456
	410	+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.
457	457
458		-~==== 3.6.1.2 Create Uplink & Downlink Converter ====
	412	+[[image:image-20230802112413-33.png||height="597" width="1061"]]
459	459
	414	+(% style="color:blue" %)**Downlink Converter**
460	460
461		-~(% style="color:blue" %)~*~*Uplink Converter~*~*
	416	+The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
462	462
463		-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.
	418	+[[image:image-20230802112413-34.png||height="598" width="1063"]]
464	464
465		-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.
	420	+(% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
466	466
467		-~[~[image~:image-20230802112413-33.png||height="597" width="1061"]]
	422	+==== 3.6.1.3 MQTT Integration Setup ====
468	468
	424	+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**;
469	469
470		-~(% style="color:blue" %)~*~*Downlink Converter~*~*
	426	+[[image:image-20230802112413-35.png||height="597" width="1062"]]
471	471
472		-The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
	428	+* The next steps is to add the recently created uplink and downlink converters;
473	473
474		-~[~[image~:image-20230802112413-34.png||height="598" width="1063"]]
	430	+[[image:image-20230802112413-36.png||height="598" width="1062"]]
475	475
476		-~(% style="color:red" %)~*~*Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.~*~*
	432	+[[image:image-20230802112413-37.png||height="598" width="1064"]]
477	477
	434	+(% style="color:blue" %)**Add a topic filter:**
478	478
479		-~==== 3.6.1.3 MQTT Integration Setup ====
480		-
481		-
482		-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~*~*;
483		-
484		-~[~[image~:image-20230802112413-35.png||height="597" width="1062"]]
485		-
486		-
487		-~* The next steps is to add the recently created uplink and downlink converters;
488		-
489		-~[~[image~:image-20230802112413-36.png||height="598" width="1062"]]
490		-
491		-~[~[image~:image-20230802112413-37.png||height="598" width="1064"]]
492		-
493		-
494		-~(% style="color:blue" %)~*~*Add a topic filter:~*~*
495		-
496	496	Consistent with the theme of the node setting.
497	497
498		-You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
	438	+You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
499	499
500		-~[~[image~:image-20230802112413-38.png||height="598" width="1064"]]
	440	+[[image:image-20230802112413-38.png||height="598" width="1064"]]
501	501
	442	+=== 3.6.2 Simulate with MQTT.fx ===
502	502
503		-~=== 3.6.2 Simulate with MQTT.fx ===
	444	+[[image:image-20230802112413-39.png]]
504	504
	446	+[[image:image-20230802112413-40.png||height="525" width="980"]]
505	505
506		-~[~[image~:image-20230802112413-39.png]]
	448	+=== 3.6.3 Configure NB-IoT Sensor ===
507	507
508		-~[~[image~:image-20230802112413-40.png||height="525" width="980"]]
	450	+(% style="color:blue" %)**AT Commands**
509	509
	452	+* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
510	510
511		-~=== 3.6.3 Configure NB-IoT Sensor ===
	454	+* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
512	512
	456	+* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
513	513
514		-~(% style="color:blue" %)~*~*AT Commands~*~*
	458	+* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
515	515
516		-~* ~(% style="color:#037691" %)~*~*AT+PRO=3,3  ~*~*~(%%)~*~*  ~*~*~~/~~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
	460	+* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
517	517
518		-~* ~(% style="color:#037691" %)~*~*AT+SUBTOPIC=<device name>~*~*
	462	+* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
519	519
520		-~* ~(% style="color:#037691" %)~*~*AT+PUBTOPIC=<device name>~*~*
	464	+Test Uplink by click the button for 1 second
521	521
522		-~* ~(% style="color:#037691" %)~*~*AT+CLIENT=<device name> or User Defined~*~*
	466	+[[image:image-20230802112413-41.png||height="496" width="828"]]
523	523
524		-~* ~(% style="color:#037691" %)~*~*AT+UNAME=<device name> or User Defined~*~*
	468	+[[image:image-20230802112413-42.png]]
525	525
526		-~* ~(% style="color:#037691" %)~*~*AT+PWD=<device name> or User Defined~*~*
	470	+[[image:image-20230802112413-43.png||height="407" width="825"]]
527	527
528		-Test Uplink by click the button for 1 second
	472	+== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
529	529
530		-~[~[image~:image-20230802112413-41.png||height="496" width="828"]]
	474	+=== 3.7.1 Create device & Get Credentials ===
531	531
532		-~[~[image~:image-20230802112413-42.png]]
	476	+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.
533	533
534		-~[~[image~:image-20230802112413-43.png||height="407" width="825"]]
	478	+[[image:image-20230802112413-44.png]]
535	535
	480	+[[image:image-20230802112413-45.png]]
536	536
537		-~== 3.7 ~[~[Tago.io>>url:https:~/~/admin.tago.io/]] (via MQTT) ==
	482	+Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
538	538
539		-~=== 3.7.1 Create device & Get Credentials ===
	484	+[[image:image-20230802112413-46.png]]
540	540
	486	+The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
541	541
542		-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.
	488	+(% style="color:blue" %)**On the Connection Profile window, set the following information:**
543	543
544		-~[~[image~:image-20230802112413-44.png]]
	490	+* (% style="color:#037691" %)**Profile Name: “Any name”**
545	545
546		-~[~[image~:image-20230802112413-45.png]]
	492	+* (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
547	547
	494	+* (% style="color:#037691" %)**Broker Port: 8883**
548	548
549		-Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
	496	+* (% style="color:#037691" %)**Client ID: “Any value”**
550	550
551		-~[~[image~:image-20230802112413-46.png]]
	498	+(% style="color:blue" %)**On the section User credentials, set the following information:**
552	552
	500	+* (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
553	553
554		-The device needs to enable the TLS mode and set the ~(% style="color:blue" %)~*~*AT+TLSMOD=1,0~*~*~(%%) command.
	502	+* (% style="color:#037691" %)**Password: “Your device token”**
555	555
556		-~(% style="color:blue" %)~*~*On the Connection Profile window, set the following information:~*~*
	504	+* (% style="color:#037691" %)**PUBTOPIC: “Any value”**
557	557
558		-~* ~(% style="color:#037691" %)~*~*Profile Name: “Any name”~*~*
	506	+* (% style="color:#037691" %)**SUBTOPIC: “Any value”**
559	559
560		-~* ~(% style="color:#037691" %)~*~*Broker Address: mqtt.tago.io~*~*
	508	+(% style="color:blue" %)**AT command:**
561	561
562		-~* ~(% style="color:#037691" %)~*~*Broker Port: 8883~*~*
	510	+* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
563	563
564		-~* ~(% style="color:#037691" %)~*~*Client ID: “Any value”~*~*
	512	+* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
565	565
566		-~(% style="color:blue" %)~*~*On the section User credentials, set the following information:~*~*
	514	+* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
567	567
568		-~* ~(% style="color:#037691" %)~*~*User Name: “Any value”~*~* ~(%%)      ~*~*~~/~~/ Tago validates your user by the token only~*~*
	516	+* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
569	569
570		-~* ~(% style="color:#037691" %)~*~*Password: “Your device token”~*~*
	518	+* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
571	571
572		-~* ~(% style="color:#037691" %)~*~*PUBTOPIC: “Any value”~*~*
	520	+* (% style="color:#037691" %)**AT+PWD=“Your device token”**
573	573
574		-~* ~(% style="color:#037691" %)~*~*SUBTOPIC: “Any value”~*~*
	522	+=== 3.7.2 Simulate with MQTT.fx ===
575	575
576		-~(% style="color:blue" %)~*~*AT command:~*~*
	524	+[[image:image-20230802112413-52.png]]
577	577
578		-~* ~(% style="color:#037691" %)~*~*AT+PRO=3,0 or 3,5 ~*~* ~(%%)   ~*~*~~/~~/ hex format or json format~*~*
	526	+[[image:image-20230808105300-2.png||height="553" width="1026"]]
579	579
580		-~* ~(% style="color:#037691" %)~*~*AT+SUBTOPIC=<device name>or User Defined~*~*
	528	+Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
581	581
582		-~* ~(% style="color:#037691" %)~*~*AT+PUBTOPIC=<device name>or User Defined~*~*
	530	+[[image:image-20230808105217-1.png||height="556" width="1031"]]
583	583
584		-~* ~(% style="color:#037691" %)~*~*AT+CLIENT=<device name> or User Defined~*~*
	532	+[[image:image-20230808105329-3.png]]
585	585
586		-~* ~(% style="color:#037691" %)~*~*AT+UNAME=<device name> or User Defined~*~*
	534	+=== 3.7.3 tago data ===
587	587
588		-~* ~(% style="color:#037691" %)~*~*AT+PWD=“Your device token”~*~*
	536	+[[image:image-20230802112413-50.png||height="242" width="1037"]]
589	589
590		-~=== 3.7.2 Simulate with MQTT.fx ===
	538	+[[image:image-20230802112413-51.png||height="184" width="696"]]
591	591
	540	+== 3.8 TCP Connection ==
592	592
593		-~[~[image~:image-20230802112413-52.png]]
	542	+(% style="color:blue" %)**AT command:**
594	594
	544	+* (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
595	595
596		-~[~[image~:image-20230808105300-2.png||height="553" width="1026"]]
	546	+* (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
597	597
	548	+* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
598	598
599		-Users can run the ~(% style="color:blue" %)~*~*AT+PRO=3,5~*~*~(%%) command, and the payload will be converted to ~*~*JSON format~*~*.
	550	+(% style="color:blue" %)**Sensor Console Output when Uplink:**
600	600
601		-~[~[image~:image-20230808105217-1.png||height="556" width="1031"]]
	552	+[[image:image-20230807233631-1.png]]
602	602
603		-~[~[image~:image-20230808105329-3.png]]
	554	+(% style="color:blue" %)**See result in TCP Server:**
604	604
	556	+[[image:image-20230807233631-2.png]]
605	605
606		-~=== 3.7.3 tago data ===
	558	+== 3.9 AWS Connection ==
607	607
	560	+Users can refer to [[Dragino NB device connection to AWS platform instructions>>http://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H1.LogintotheplatformandfindIoTcore]]
608	608
609		-~[~[image~:image-20230802112413-50.png||height="242" width="1037"]]
	562	+= 4. MQTT/UDP/TCP downlink =
610	610
611		-~[~[image~:image-20230802112413-51.png||height="184" width="696"]]
	564	+== 4.1 MQTT (via MQTT.fx) ==
612	612
	566	+Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
613	613
614		-~== 3.8 TCP Connection ==
	568	+**1.** Configure node MQTT connection (via MQTT.fx):
615	615
	570	+(% style="color:blue" %)**AT command:**
616	616
617		-~(% style="color:blue" %)~*~*AT command:~*~*
	572	+* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
618	618
619		-~* ~(% style="color:#037691" %)~*~*AT+PRO=4,0   ~*~* ~(%%) ~~/~~/ Set to use TCP protocol to uplink(HEX format)
	574	+* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
620	620
621		-~* ~(% style="color:#037691" %)~*~*AT+PRO=4,1   ~*~* ~(%%) ~~/~~/ Set to use TCP protocol to uplink(JSON format)
	576	+* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
622	622
623		-~* ~(% style="color:#037691" %)~*~*AT+SERVADDR=120.24.4.116,5600 ~*~*  ~(%%) ~~/~~/ to set TCP server address and port
	578	+* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
624	624
625		-~(% style="color:blue" %)~*~*Sensor Console Output when Uplink:~*~*
	580	+* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
626	626
627		-~[~[image~:image-20230807233631-1.png]]
	582	+* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
628	628
	584	+(% style="color:red" %)**Note: To uplink and downlink via MQTT.fx, we need set the publish topic and subscribe topic different, for example: AT+SUBTOPIC=SE01_SUB & AT+PUBTOPIC=SE01_PUB.**
629	629
630		-~(% style="color:blue" %)~*~*See result in TCP Server:~*~*
	586	+[[image:image-20240417180145-2.png||height="434" width="587"]][[ width="584">> width="584"]]
631	631
632		-~[~[image~:image-20230807233631-2.png]]
	588	+**2. **When the node uplink packets, we can observe the data in MQTT.fx.
633	633
	590	+[[image:image-20240418144337-1.png||height="709" width="802"]]
634	634
635		-~== 3.9 AWS Connection ==
	592	+**3. **The downlink command can be successfully sent only when the downlink port is open.
636	636
637		-
638		-Users can refer to ~[~[Dragino NB device connection to AWS platform instructions>>http:~/~/wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H1.LogintotheplatformandfindIoTcore]]
639		-
640		-
641		-
642		-~= 4. MQTT/UDP/TCP downlink =
643		-
644		-~== 4.1 MQTT (via MQTT.fx) ==
645		-
646		-Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx~/~/.~/~/
647		-
648		-~*~*1.~*~* Configure node MQTT connection (via MQTT.fx):
649		-
650		-~(% style="color:blue" %)~*~*AT command:~*~*
651		-
652		-~* ~(% style="color:#037691" %)~*~*AT+PRO=3,0 or 3,5 ~*~*  ~(%%)~~/~~/ hex format or json format
653		-
654		-~* ~(% style="color:#037691" %)~*~*AT+SUBTOPIC=User Defined~*~*
655		-
656		-~* ~(% style="color:#037691" %)~*~*AT+PUBTOPIC=User Defined~*~*
657		-
658		-~* ~(% style="color:#037691" %)~*~*AT+UNAME=<device name> or User Defined~*~*
659		-
660		-~* ~(% style="color:#037691" %)~*~*AT+PWD=<device name> or User Defined~*~*
661		-
662		-~* ~(% style="color:#037691" %)~*~*AT+SERVADDR=8.217.91.207,1883 ~*~*  ~(%%) ~~/~~/ to set MQTT server address and port
663		-
664		-~(% style="color:red" %)~*~*Note: To uplink and downlink via MQTT.fx, we need set the publish topic and subscribe topic different, for example: AT+SUBTOPIC=SE01_SUB & AT+PUBTOPIC=SE01_PUB.~*~*
665		-
666		-~[~[image~:image-20240417180145-2.png||height="434" width="587"]]~[~[image:image-20240417180737-3.png||height="431" width="584"]]
667		-
668		-
669		-~*~*2. ~*~*When the node uplink packets, we can observe the data in MQTT.fx.
670		-
671		-~[~[image~:image-20240418144337-1.png||height="709" width="802"]]
672		-
673		-~*~*3. ~*~*The downlink command can be successfully sent only when the downlink port is open.
674		-
675	675	The downlink port is opened for about 3 seconds after uplink packets are sent.
676	676
677		- Therefore, when we see the node uplink packets in the ~*~*Subscribe~*~* window, we need to immediately switch to the ~*~*publish~*~* window to publish the ~*~*hex format~*~* command.
	596	+ Therefore, when we see the node uplink packets in the **Subscribe** window, we need to immediately switch to the **publish** window to publish the **hex format** command.
678	678
679		-~[~[image~:image-20240418150435-3.png||height="582" width="659"]]
	598	+[[image:image-20240418150435-3.png||height="582" width="659"]]
680	680
681		-~[~[image~:image-20240418150932-4.png||height="492" width="1061"]]
	600	+[[image:image-20240418150932-4.png||height="492" width="1061"]]
682	682
683		-~(% style="color:red" %)~*~*Note: Users can edit the hex command in advance. When the node uplink, directly click the publish button several times to increase the success rate of command configuration.~*~*
	602	+(% style="color:red" %)**Note: Users can edit the hex command in advance. When the node uplink, directly click the publish button several times to increase the success rate of command configuration.**
684	684
	604	+= 5. FAQ =
685	685
	606	+== 5.1 What is the usage of Multi Sampling and One Uplink? ==
686	686
687		-
688		-~= 5. FAQ =
689		-
690		-~== 5.1 What is the usage of Multi Sampling and One Uplink? ==
691		-
692		-
693	693	The NB series has the feature for Multi Sampling and one uplink. See one of them
694	694
695		-~[~[http:~~~~/~~~~/wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink>>http:~/~/wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink]]
	610	+[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink]]
696	696
697	697	User can use this feature for below purpose:
698	698
699		-~1. ~*~*Reduce power consumption~*~*. The NB-IoT transmit power is much more higher than the sensor sampling power. To save battery life, we can sampling often and send in one uplink.
700		-~1. Give more sampling data points.
701		-~1. Increase reliable in transmission. For example. If user set
702		-~1*. ~*~*AT+TR=1800~*~*        ~~/~~/ The unit is seconds, and the default is to record data once every 1800 seconds (30 minutes, the minimum can be set to 180 seconds)
703		-~1*. ~*~*AT+NOUD=24~*~*    ~~/~~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
704		-~1*. ~*~*AT+TDC=7200~*~*  ~~/~~/ Uplink every 2 hours.
705		-~1*. this will mean each uplink will actually include the 6 uplink data (24 set data which cover 12 hours). So if device doesn't lost 6 continue data. There will not data lost.
	614	+1. **Reduce power consumption**. The NB-IoT transmit power is much more higher than the sensor sampling power. To save battery life, we can sampling often and send in one uplink.
	615	+1. Give more sampling data points.
	616	+1. Increase reliable in transmission. For example. If user set
	617	+1*. **AT+TR=1800** ~/~/ The unit is seconds, and the default is to record data once every 1800 seconds (30 minutes, the minimum can be set to 180 seconds)
	618	+1*. **AT+NOUD=24** ~/~/ The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
	619	+1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours.
	620	+1*. this will mean each uplink will actually include the 6 uplink data (24 set data which cover 12 hours). So if device doesn't lost 6 continue data. There will not data lost.
706	706
707		-~== 5.2 Why the uplink JSON format is not standard? ==
	622	+== 5.2 Why the uplink JSON format is not standard? ==
708	708
709		-
710	710	The json format in uplink packet is not standard Json format. Below is the example. This is to make the payload as short as possible, due to NB-IoT transmit limition, a standard Json is not able to include 32 sets of sensors data with timestamp.
711	711
712	712	The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
713	713
714		-~[~[image~:image-20240229233154-1.png]]
	628	+[[image:image-20240229233154-1.png]]
715	715
	630	+= 6. Trouble Shooting: =
716	716
717		-~= 6. Trouble Shooting: =
	632	+== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
718	718
719		-~== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
720		-
721		-
722	722	There are many different providers provide NB-IoT service in the world. They might use different band, different APN & different operator configuration. Which makes connection to NB-IoT network is complicate.
723	723
724		-If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~~~31)
	636	+If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
725	725
726		-~[~[image~:image-20240207002003-1.png]]
	638	+[[image:image-20240207002003-1.png]]
727	727
728		-
729	729	If fail to attach network, it will shows signal 99. as below:
730	730
731		-~[~[image~:image-20240207002129-2.png]]
	642	+[[image:image-20240207002129-2.png]]
732	732
733		-
734		-~(% class="lead" %)
	644	+(% class="lead" %)
735	735	When see this issue, below are the checklist:
736	736
737		-~* Does your SIM card support NB-IoT network? If SIM card doesn't not specify support NB-IoT clearly, normally it doesn't support. You need to confirm with your operator.
738		-~* Do you configure the correct APN? ~[~[Check here for APN settings>>http:~/~/wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.1GeneralConfiguretoattachnetwork]].
739		-~* Do you lock the frequency band? This is the most case we see. ~[~[Explain and Instruction>>http:~/~/wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.2SpeedUpNetworkAttachtime]].
740		-~* Check if the device is attached to Carrier network but reject. (need to check with operator).
741		-~* Check if the antenna is connected firmly.
	647	+* Does your SIM card support NB-IoT network? If SIM card doesn't not specify support NB-IoT clearly, normally it doesn't support. You need to confirm with your operator.
	648	+* Do you configure the correct APN? [[Check here for APN settings>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.1GeneralConfiguretoattachnetwork]].
	649	+* Do you lock the frequency band? This is the most case we see. [[Explain and Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.2SpeedUpNetworkAttachtime]].
	650	+* Check if the device is attached to Carrier network but reject. (need to check with operator).
	651	+* Check if the antenna is connected firmly.
742	742
743		-If you have check all above and still fail. please send console log files (as many as possible) to ~[~[support@dragino.com>>mailto~:support@dragino.com]] so we can check.
	653	+If you have check all above and still fail. please send console log files (as many as possible) to [[support@dragino.com>>mailto:support@dragino.com]] so we can check.
744	744
	655	+
745	745
746		-~== 6.2 Issue: "NBIOT did not respond" ==
	657	+== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
747	747
748		-
749		-~(% class="box errormessage" %)
750		-~(~(~(
751		-11:24:22.397 [44596]NBIOT did not respond.
752		-11:24:24.315 [46530]NBIOT did not respond.
753		-11:24:26.256 [48464]NBIOT did not respond.
754		-11:24:28.196 [50398]NBIOT did not respond.
755		-11:24:30.115 [52332]NBIOT did not respond.
756		-11:24:32.127 [54266]NBIOT did not respond.
757		-11:24:32.127 [54299]Restart the module...
758		-11:24:39.181 [61332]No response when shutting down
759		-~)~)~)
760		-
761		-This issue might due to initiate issue for NB-IoT module. In this case, please try:
762		-
763		-1) Open Enclosure
764		-
765		-2) Power off device by pull out the power on Jumper
766		-
767		-3) Power on device by connect back the power jumper.
768		-
769		-4) push reset button.
770		-
771		-~[~[image~:image-20240208001740-1.png]]
772		-
773		-
774		-~== 6.3 Issue: "Failed to readI MSI number" ==
775		-
776		-
777		-~(% class="box errormessage" %)
778		-~(~(~(
779		-[18170]Failed to read IMSI:1umber.
780		-[20109]Failed to read IMSI numoer.
781		-[22048]Failed to read IMSI number.
782		-[29842lRestart the module...
783		-~)~)~)
784		-
785		-Make sure that the SIM card is insert in correct direction and device is power off/on during insert. Here is reference link: ~[~[Insert SIM Card>>||anchor="H2.1GeneralConfiguretoattachnetwork"]].
786		-
787		-
788		-~== ~(% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?~(%%) ==
789		-
790		-
791	791	When the MCU is communicating with the NB-IoT module, the MCU response of AT Command will become slower, it might takes several seconds to response.
792	792
793		-~[~[image~:image-20240226111928-1.png]]
	661	+[[image:image-20240226111928-1.png]]
794	794
	663	+== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
795	795
796		-~== ~(% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?~(%%) ==
	665	+(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
	666	+=== UDP: ===
797	797
798		-~(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
799		-~=== UDP: ===
800		-
801		-~(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
	668	+(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
802	802	Its downlink command is the same as the AT command, but brackets are required.
803	803	Example:
804	804
805	805	{AT+TDC=300}
806	806
	674	+(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
	675	+=== MQTT: ===
807	807
808		-~(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
809		-~=== MQTT: ===
810		-
811	811	Json：
812	812
813	813	The Json format in MQTT mode needs to be configured with all commands.
...	...	@@ -844,6 +844,7 @@
844	844	The supported commands are consistent with LoRaWAN's hex commands.
845	845	Please refer to the following link to obtain the hex format:
846	846
847		-~[~[http:~~~~/~~~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http:~/~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
	713	+[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
848	848
849	849
	716	+​