Wiki source code of General Configure/Commands to Connect to IoT server for -NB & -NS NB-IoT models

Version 221.1 by Xiaoling on 2024/12/31 15:51

version	line-number	content
83.3	1	(% class="wikigeneratedid" id="HTableofContents:" %)
	2	Table of Contents:
53.3	3
	4	{{toc/}}
	5
	6
100.2	7
	8
	9
	10
1.1	11	= 1. The use of this guideline =
	12
1.2	13
1.1	14	This configure instruction is for Dragino NB-IoT models with -NB or -NS suffix, for example DDS75-NB. These models use the same NB-IoT Module [[BC660K-GL>>https://www.quectel.com/product/lpwa-bc660k-gl-nb2]] and has the same software structure. The have the same configure instruction to different IoT servers. Use can follow the instruction here to see how to configure to connect to those servers.
	15
	16
55.1	17	= 2. Attach Network =
1.1	18
103.1	19	== 2.1 General Configure to attach network ==
1.1	20
104.4	21
54.1	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)
137.1	25	1. Power Off End Node ( See below for the power off/on position)
	26	1. Insert the SIM card to Sensor. ( See below for direction)
	27	1. Power On End Node
150.1	28	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
54.1	29
137.1	30	[[image:image-20240208102804-1.png\|\|height="286" width="696"]]
	31
83.1	32	[[image:image-20230808205045-1.png\|\|height="293" width="438"]]
60.1	33
54.1	34	After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
	35
1.3	36	The -NB and -NS models support (% style="color:blue" %)LTE Cat NB2(%%), with below frequency band: multiple frequency bands of (% style="color:blue" %)B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85(%%) . Make sure you use a the NB-IoT SIM card.
1.1	37
54.1	38	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
99.1	39	\|(% 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
56.2	40	\|(% style="width:117px" %)[[1NCE>>https://1nce.com]]\|(% style="width:151px" %)iot.1nce.net\|(% style="width:474px" %)(((
54.1	41	[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]
1.1	42
161.1	43	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
	44	)))\|(% style="width:135px" %)UK: Band20
57.1	45	\|(% style="width:117px" %)China Mobile\|(% style="width:151px" %)No need configure\|(% style="width:474px" %)China Mainland, HongKong\|(% style="width:135px" %)
66.1	46	\|(% style="width:117px" %)China Telecom\|(% style="width:151px" %)ctnb\|(% style="width:474px" %)China Mainland\|(% style="width:135px" %)
53.27	47
184.1	48	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
219.2	49	\|(% style="background-color:#4f81bd; color:white; width:152px" %)SIM Provider\|(% style="background-color:#4f81bd; color:white; width:169px" %)AT+QCGDEFCONT=\|(% style="background-color:#4f81bd; color:white; width:427px" %)Command Explanation\|(% style="background-color:#4f81bd; color:white; width:135px" %)Comments
	50	\|(% style="width:152px" %)[[1NCE>>https://1nce.com]]/[[NB card purchased by the customer>>https://1nce.com]]\|(% style="width:169px" %)iot.1nce.net/xxx\|(% style="width:427px" %)This command sets the PSD connection settings for PDN connection on power-up. When the MT attaches to the NB-IoT network on power-on, a PDN connection setup is performed. Therefore, PDN connection settings are stored in NVRAM so that they can be used by the modem during the attachment.\|(% style="width:135px" %)
184.1	51
103.1	52	== 2.2 Speed Up Network Attach time ==
99.3	53
104.2	54
149.1	55	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.
102.2	56
107.1	57	(% style="color:#037691" %)AT+QBAND? (%%) ~/~/ Check what is the current used frequency band
	58	(% style="color:#037691" %)AT+QBAND=1,4 (%%) ~/~/ Set to use 1 frequency band. Band4
129.1	59	(% style="color:#037691" %)Europe General(%%) AT+QBAND=2,8,20 ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
147.1	60	(% style="color:#037691" %)Global General(%%) : AT+QBAND=10,8,20,28,2,4,12,13,66,85,5
104.1	61
129.1	62	(% style="color:#037691" %)Verizon(%%) AT+QBAND=1,13
	63	(% style="color:#037691" %)AT&T(%%) AT+QBAND=3,12,4,2
	64	(% style="color:#037691" %)Telstra(%%) AT+QBAND=1,28
	65	(% style="color:#037691" %)Softband(%%) AT+QBAND=2,3,8
104.4	66
107.1	67	After connection is successful, user can use (% style="color:#037691" %)AT+QENG=0 (%%) to check which band is actually in used.
	68
165.1	69	By default, device will search network for 5 minutes. User can set the time to 10 minutes by (% style="color:#037691" %)AT+CSQTIME=10 (%%)so it can search longer.
107.1	70
105.1	71	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/]]
	72
	73
1.1	74	= 3. Configure to connect to different servers =
	75
53.3	76	== 3.1 General UDP Connection ==
53.2	77
	78
	79	The NB-IoT Sensor can send packet to server use UDP protocol.
	80
	81
53.3	82	=== 3.1.1 Simulate UDP Connection by PC tool ===
	83
	84
53.2	85	We can use PC tool to simulate UDP connection to make sure server works ok.
	86
105.2	87	[[image:image-20230802112413-1.png\|\|height="468" width="1024"]]
53.2	88
	89
53.3	90	=== 3.1.2 Configure NB-IoT Sensor ===
53.2	91
53.3	92	==== 3.1.2.1 AT Commands ====
53.2	93
53.3	94
53.4	95	(% style="color:blue" %)AT Commands:
53.3	96
53.5	97	* (% style="color:#037691" %)AT+PRO=2,0 (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload
53.8	98
53.5	99	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5601 (%%) ~/~/ Set UDP server address and port
53.8	100
53.2	101	[[image:image-20230802112413-2.png]]
	102
	103
53.3	104	==== 3.1.2.2 Uplink Example ====
53.2	105
53.3	106
53.2	107	[[image:image-20230802112413-3.png]]
	108
	109
53.7	110	== 3.2 General MQTT Connection ==
53.2	111
53.6	112
53.2	113	The NB-IoT Sensor can send packet to server use MQTT protocol.
	114
53.6	115	Below are the commands.
53.2	116
53.8	117	(% style="color:blue" %)AT Commands:
53.2	118
53.9	119	* (% style="color:#037691" %)AT+PRO=3,0 (%%) ~/~/ Set to use MQTT protocol to uplink, Payload Type select Hex payload.
53.2	120
53.9	121	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,1883 (%%) ~/~/ Set MQTT server address and port
53.8	122
53.9	123	* (% style="color:#037691" %)AT+CLIENT=CLIENT (%%) ~/~/ Set up the CLIENT of MQTT
53.8	124
53.9	125	* (% style="color:#037691" %)AT+UNAME=UNAME (%%) ~/~/ Set the username of MQTT
53.8	126
53.9	127	* (% style="color:#037691" %)AT+PWD=PWD (%%) ~/~/ Set the password of MQTT
53.8	128
	129	* (% style="color:#037691" %)AT+PUBTOPIC=NSE01_PUB (%%) ~/~/ Set the sending topic of MQTT
	130
	131	* (% style="color:#037691" %)AT+SUBTOPIC=NSE01_SUB (%%) ~/~/ Set the subscription topic of MQTT
	132
53.2	133	[[image:image-20230802112413-4.png]]
	134
102.1	135	[[image:image-20230802112413-5.png\|\|height="530" width="987"]]
53.2	136
53.9	137	(% style="color:red" %)Notice: MQTT protocol has a much higher power consumption compare with UDP/CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
53.2	138
	139
53.7	140	== 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
53.2	141
53.9	142	=== 3.3.1 Get MQTT Credentials ===
53.2	143
53.9	144
53.2	145	[[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.
	146
102.1	147	[[image:image-20230802112413-6.png\|\|height="336" width="925"]]
53.2	148
	149	[[image:image-20230802112413-7.png]]
	150
	151
53.27	152	=== 3.3.2 Simulate with MQTT.fx ===
53.2	153
53.27	154	==== 3.3.2.1 Establish MQTT Connection ====
53.2	155
53.9	156
53.2	157	After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
	158
	159	[[image:image-20230802112413-8.png]]
	160
53.9	161	* (% style="color:#037691" %)Broker Address:(%%) mqtt3.thingspeak.com
53.2	162
53.9	163	* (% style="color:#037691" %)Broker Port:(%%) 1883
53.10	164
53.9	165	* (% style="color:#037691" %)Client ID:(%%) <Your ThingSpeak MQTT ClientID>
53.10	166
53.9	167	* (% style="color:#037691" %)User Name:(%%) <Your ThingSpeak MQTT User Name>
53.10	168
53.9	169	* (% style="color:#037691" %)Password:(%%) <Your ThingSpeak MQTT Password>
53.2	170
53.28	171	==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
	172
	173
53.2	174	[[image:image-20230802112413-9.png]]
	175
	176	[[image:image-20230802112413-10.png]]
	177
53.43	178
53.10	179	(% style="color:blue" %)In MQTT.fx, we can publish below info:
53.2	180
53.10	181	* (% style="color:#037691" %)Topic:(%%) channels/YOUR_CHANNEL_ID/publish
53.2	182
53.10	183	* (% style="color:#037691" %)Payload:(%%) field1=63&field2=67&status=MQTTPUBLISH
	184
53.2	185	Where 63 and 67 are the value to be published to field1 & field2.
	186
	187
53.10	188	(% style="color:blue" %)Result:
53.2	189
102.1	190	[[image:image-20230802112413-11.png\|\|height="539" width="901"]]
53.2	191
	192
53.28	193	=== 3.3.3 Configure NB-IoT Sensor for connection ===
53.2	194
53.28	195	==== 3.3.3.1 AT Commands: ====
53.2	196
53.10	197
53.2	198	In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
	199
99.3	200	* (% style="color:blue" %)AT+PRO=3,1 (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
53.9	201
53.26	202	* (% style="color:blue" %)AT+CLIENT=<Your ThingSpeak MQTT ClientID>
53.9	203
53.26	204	* (% style="color:blue" %)AT+UNAME=<Your ThingSpeak MQTT User Name>
53.9	205
53.26	206	* (% style="color:blue" %)AT+PWD=<Your ThingSpeak MQTT Password>
53.9	207
53.26	208	* (% style="color:blue" %)AT+PUBTOPIC=<YOUR_CHANNEL_ID>
53.9	209
53.26	210	* (% style="color:blue" %)AT+SUBTOPIC=<YOUR_CHANNEL_ID>
53.2	211
53.28	212	==== 3.3.3.2 Uplink Examples ====
53.10	213
104.4	214
102.1	215	[[image:image-20230816201942-1.png]]
53.10	216
53.2	217	For SE01-NB
	218
	219	For DDS20-NB
	220
	221	For DDS45-NB
	222
	223	For DDS75-NB
	224
	225	For NMDS120-NB
	226
	227	For SPH01-NB
	228
	229	For NLM01-NB
	230
	231	For NMDS200-NB
	232
	233	For CPN01-NB
	234
	235	For DS03A-NB
	236
	237	For SN50V3-NB
	238
	239
53.28	240	==== 3.3.3.3 Map fields to sensor value ====
53.2	241
53.10	242
53.2	243	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.
	244
	245
102.1	246	[[image:image-20230802112413-12.png\|\|height="504" width="1011"]]
53.2	247
102.1	248	[[image:image-20230802112413-13.png\|\|height="331" width="978"]]
53.2	249
	250
	251	Below is the NB-IoT Product Table show the mapping.
	252
83.4	253	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
	254	\|(% 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
	255	\|(% 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" %)
	256	\|(% 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" %)
	257	\|(% 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" %)
	258	\|(% 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" %)
	259	\|(% 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" %)
	260	\|(% 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" %)
	261	\|(% 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" %)
	262	\|(% 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" %)
	263	\|(% 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" %)
	264	\|(% 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" %)
	265	\|(% 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
	266	\|(% 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" %)
	267	\|(% 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" %)
	268	\|(% 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" %)
	269	\|(% 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" %)
	270	\|(% 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" %)
	271	\|(% 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" %)
53.2	272
100.1	273	== 3.4 [[Datacake>>https://datacake.co/]] ==
99.3	274
53.2	275
100.1	276	(% class="wikigeneratedid" %)
	277	Dragino NB-IoT sensors has its template in [[Datacake>>https://datacake.co/]] Platform. There are two version for NB Sensor,
	278
	279
	280	(% class="wikigeneratedid" %)
100.5	281	As example for S31B-NB. there are two versions: S31B-NB-1D and S31B-NB-GE.
100.1	282
100.2	283	* (% 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.
100.1	284
100.2	285	* (% 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.
100.1	286
109.1	287	=== 3.4.1 For device Already has template ===
53.2	288
109.1	289	==== 3.4.1.1 Create Device ====
83.4	290
180.1	291
100.4	292	(% style="color:blue" %)Add Device(%%) in DataCake.
100.1	293
105.2	294	[[image:image-20230808162301-1.png\|\|height="453" width="952"]]
53.11	295
	296
105.2	297	[[image:image-20230808162342-2.png\|\|height="541" width="952"]]
78.1	298
	299
100.3	300	(% style="color:blue" %)Choose the correct model(%%) from template.
100.1	301
78.1	302	[[image:image-20230808162421-3.png]]
	303
83.4	304
100.3	305	(% 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.
78.1	306
105.2	307	[[image:image-20230808163612-7.png\|\|height="549" width="952"]]
78.1	308
	309	[[image:image-20230808163035-5.png]]
	310
105.2	311	[[image:image-20230808163049-6.png\|\|height="544" width="926"]]
78.1	312
83.4	313
109.1	314	=== 3.4.2 For Device already registered in DataCake before shipped ===
81.1	315
126.1	316	==== 3.4.2.1 Scan QR Code to get the device info ====
83.4	317
145.2	318
81.1	319	Users can use their phones or computers to scan QR codes to obtain device data information.
	320
100.1	321	[[image:image-20230808170051-8.png\|\|height="255" width="259"]]
81.1	322
	323	[[image:image-20230808170548-9.png]]
	324
83.4	325
126.1	326	==== 3.4.2.2 Claim Device to User Account ====
	327
145.2	328
126.1	329	By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
	330
	331
109.1	332	=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
81.1	333
	334
145.2	335	Step1: Add a device
	336
123.1	337	[[image:image-20240129170024-1.png\|\|height="330" width="900"]]
	338
	339
145.2	340	Step2: Choose your device type,please select dragino NB-IOT device
	341
123.1	342	[[image:image-20240129170216-2.png\|\|height="534" width="643"]]
	343
	344
145.2	345	Step3: Choose to create a new device
	346
123.1	347	[[image:image-20240129170539-3.png\|\|height="459" width="646"]]
	348
	349
145.2	350	Step4: Fill in the device ID of your NB device
	351
125.1	352	[[image:image-20240202111546-1.png\|\|height="378" width="651"]]
123.1	353
	354
145.2	355	Step5: Please select your device plan according to your needs and complete the creation of the device
	356
123.1	357	[[image:image-20240129171236-6.png\|\|height="450" width="648"]]
	358
	359
145.2	360	Step6: Please add the decoder at the payload decoder of the device configuration.
	361
180.1	362	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]]
127.1	363
180.1	364	Due to version update, please use the following decoder for the new version firmware:
179.1	365	[[dragino-end-node-decoder/Datacake-Dragino_NB_New_Version at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB_New_Version]]
	366
123.1	367	[[image:image-20240129172056-7.png\|\|height="457" width="816"]]
	368
	369	[[image:image-20240129173116-9.png\|\|height="499" width="814"]]
	370
	371
145.2	372	Step7: Add the output of the decoder as a field
	373
123.1	374	[[image:image-20240129173541-10.png\|\|height="592" width="968"]]
	375
	376
145.2	377	Step8: Customize the dashboard and use fields as parameters of the dashboard
	378
123.1	379	[[image:image-20240129174518-11.png\|\|height="147" width="1042"]]
	380
	381	[[image:image-20240129174657-12.png\|\|height="538" width="916"]]
	382
	383	[[image:image-20240129174840-13.png\|\|height="536" width="750"]]
	384
	385
109.1	386	=== 3.4.4 For device have not configured to connect to DataCake ===
	387
145.2	388
109.1	389	(% class="lead" %)
	390	Use AT command for connecting to DataCake
	391
83.4	392	(% style="color:blue" %)AT+PRO=2,0
81.1	393
83.4	394	(% style="color:blue" %)AT+SERVADDR=67.207.76.90,4445
81.1	395
83.4	396
53.21	397	== 3.5 Node-Red (via MQTT) ==
53.2	398
53.48	399	=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
53.2	400
53.32	401
93.1	402	Take S31-NB UDP protocol as an example.
53.2	403
93.1	404	Dragino provides input flow examples for the sensors.
53.32	405
93.1	406	User can download the required JSON file through Dragino Node-RED input flow template.
53.2	407
93.1	408	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]]
53.24	409
93.1	410	We can directly import the template.
53.2	411
93.1	412	The templates for S31-NB and NB95S31B are the same.
53.21	413
53.2	414
93.1	415	[[image:image-20230809173127-4.png]]
53.2	416
99.3	417
93.1	418	Please select the NB95S31B template.
53.2	419
105.2	420	[[image:image-20230809173310-5.png\|\|height="558" width="926"]]
53.2	421
93.1	422	[[image:image-20230809173438-6.png]]
53.2	423
93.1	424	[[image:image-20230809173800-7.png]]
53.21	425
99.3	426
93.1	427	Successfully imported template.
53.21	428
105.2	429	[[image:image-20230809173835-8.png\|\|height="515" width="860"]]
53.21	430
	431
93.1	432	Users can set UDP port.
53.21	433
93.1	434	[[image:image-20230809174053-9.png]]
83.8	435
99.3	436
93.1	437	=== 3.5.2 Simulate Connection ===
83.8	438
99.3	439
93.1	440	We have completed the configuration of UDP. We can try sending packets to node red.
	441
98.1	442	[[image:image-20230810083934-1.png]]
93.1	443
105.2	444	[[image:image-20230810084048-2.png\|\|height="535" width="1052"]]
93.1	445
105.2	446
93.1	447	=== 3.5.3 Configure NB-IoT Sensors ===
	448
	449
106.1	450	* (% style="color:#037691" %)AT+PRO=3,0 or 3,5 (%%) ~/~/ hex format or json format
	451	* (% style="color:#037691" %)AT+SUBTOPIC=<device name>or User Defined
	452	* (% style="color:#037691" %)AT+PUBTOPIC=<device name>or User Defined
	453	* (% style="color:#037691" %)AT+CLIENT=<device name> or User Defined
	454	* (% style="color:#037691" %)AT+UNAME=<device name> or User Defined
	455	* (% style="color:#037691" %)AT+PWD=“Your device token”
93.1	456
53.21	457	== 3.6 ThingsBoard.Cloud (via MQTT) ==
	458
	459	=== 3.6.1 Configure ThingsBoard ===
	460
53.22	461	==== 3.6.1.1 Create Device ====
53.2	462
53.32	463
59.1	464	Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
53.2	465
105.2	466	[[image:image-20230802112413-32.png\|\|height="583" width="1066"]]
53.2	467
	468
53.23	469	==== 3.6.1.2 Create Uplink & Downlink Converter ====
	470
53.32	471
53.22	472	(% style="color:blue" %)Uplink Converter
53.2	473
	474	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.
	475
53.42	476	To create an uplink converter go to the (% style="color:blue" %)Integrations center(%%) -> (% style="color:blue" %)Data converters(%%) page and click (% style="color:blue" %)“plus” (%%)button. Name it (% style="color:blue" %)“MQTT Uplink Converter”(%%) and select type (% style="color:blue" %)"Uplink"(%%). Use debug mode for now.
53.2	477
105.2	478	[[image:image-20230802112413-33.png\|\|height="597" width="1061"]]
53.2	479
	480
53.22	481	(% style="color:blue" %)Downlink Converter
53.2	482
	483	The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
	484
105.2	485	[[image:image-20230802112413-34.png\|\|height="598" width="1063"]]
53.2	486
83.8	487	(% style="color:red" %)Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.
53.2	488
53.22	489
53.23	490	==== 3.6.1.3 MQTT Integration Setup ====
53.2	491
	492
53.44	493	Go to the (% style="color:blue" %)Integrations center(%%) -> (% style="color:blue" %)Integrations page(%%) and click “(% style="color:blue" %)plus(%%)” icon to add a new integration. Name it (% style="color:blue" %)“MQTT Integration”(%%), select type (% style="color:blue" %)MQTT;
53.24	494
105.2	495	[[image:image-20230802112413-35.png\|\|height="597" width="1062"]]
53.2	496
53.32	497
53.2	498	* The next steps is to add the recently created uplink and downlink converters;
	499
105.2	500	[[image:image-20230802112413-36.png\|\|height="598" width="1062"]]
53.2	501
105.2	502	[[image:image-20230802112413-37.png\|\|height="598" width="1064"]]
53.2	503
53.33	504
53.24	505	(% style="color:blue" %)Add a topic filter:
53.2	506
108.1	507	Consistent with the theme of the node setting.
53.2	508
	509	You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
	510
105.2	511	[[image:image-20230802112413-38.png\|\|height="598" width="1064"]]
53.2	512
	513
53.23	514	=== 3.6.2 Simulate with MQTT.fx ===
	515
53.2	516	[[image:image-20230802112413-39.png]]
	517
105.2	518	[[image:image-20230802112413-40.png\|\|height="525" width="980"]]
53.2	519
	520
53.23	521	=== 3.6.3 Configure NB-IoT Sensor ===
53.2	522
53.25	523
53.23	524	(% style="color:blue" %)AT Commands
53.2	525
59.1	526	* (% style="color:#037691" %)AT+PRO=3,3 (%%) ~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
53.2	527
83.4	528	* (% style="color:#037691" %)AT+SUBTOPIC=<device name>
	529
59.1	530	* (% style="color:#037691" %)AT+PUBTOPIC=<device name>
83.4	531
59.1	532	* (% style="color:#037691" %)AT+CLIENT=<device name> or User Defined
83.4	533
59.1	534	* (% style="color:#037691" %)AT+UNAME=<device name> or User Defined
83.4	535
59.1	536	* (% style="color:#037691" %)AT+PWD=<device name> or User Defined
53.2	537
	538	Test Uplink by click the button for 1 second
	539
105.2	540	[[image:image-20230802112413-41.png\|\|height="496" width="828"]]
53.2	541
	542	[[image:image-20230802112413-42.png]]
	543
105.2	544	[[image:image-20230802112413-43.png\|\|height="407" width="825"]]
53.2	545
	546
173.2	547	== 3.7 ThingsBoard.Cloud (via COAP) ==
53.2	548
173.2	549	=== 3.7.1 Configure ThingsBoard ===
53.23	550
173.2	551	==== 3.7.1.1 Create Uplink & Downlink Converter ====
	552
	553
	554	(% style="color:blue" %)Uplink Converter
	555
	556	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.
	557
	558	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" %)“COAP Uplink Converter”(%%) and select type (% style="color:blue" %)"Uplink"(%%). Use debug mode for now.
	559
	560	[[image:image-20240729141300-1.png\|\|height="552" width="1115"]]
	561
	562
	563	(% style="color:blue" %)Downlink Converter
	564
	565	The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
	566
	567	[[image:image-20240729142505-3.png\|\|height="507" width="1023"]]
	568
	569
	570	==== 3.7.1.2 COAP Integration Setup ====
	571
	572
179.1	573	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" %)“CoAP Integration”(%%), select type COAP (% style="color:blue" %);
173.2	574
	575	[[image:image-20240729144058-4.png\|\|height="506" width="1021"]]
	576
	577
	578	The next steps is to add the recently created uplink converters;
	579
	580	[[image:image-20240729150142-5.png\|\|height="507" width="1023"]]
	581
	582
	583	==== 3.7.1.3 Add COAP Integration ====
	584
180.1	585
220.2	586	(% class="wikigeneratedid" id="H" %)
	587	[[image:image-20240729161543-9.png\|\|height="500" width="1009"]]
173.2	588
	589
	590	=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
	591
	592	==== 3.7.2.1 Instruction Description ====
	593
180.1	594
178.1	595	* AT+PRO=1,0(HEX format uplink) &AT+PRO=1,5(JSON format uplink)
173.2	596	* AT+SERVADDR=COAP Server Address,5683
	597
	598	Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
	599
178.1	600	[[image:image-20240729172305-12.png\|\|height="361" width="624"]]
	601
173.2	602	Note:The port for the COAP protocol has been fixed to 5683
	603
	604
178.1	605	* AT+URL1=11,(% style="color:red" %)character length(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
173.2	606
178.1	607	If the module used is (% style="color:red" %)BC660K, only one (%%)URL directive needs to be configured,
	608
	609	e.g.
	610
	611	* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
	612
	613	[[image:image-20240729172415-13.png\|\|height="401" width="694"]]
	614
	615	If you are using a (% style="color:red" %)BG95-M2(%%) module, you need to configure (% style="color:red" %)TWO(%%) URL commands,
	616
	617	e.g.
	618
186.1	619	* AT+URL1=11, "i"
185.1	620	* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
178.1	621
	622	[[image:image-20240729172500-14.png\|\|height="403" width="700"]]
	623
	624
173.2	625	== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
	626
	627	=== 3.8.1 Create device & Get Credentials ===
	628
	629
53.2	630	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.
	631
	632	[[image:image-20230802112413-44.png]]
	633
	634	[[image:image-20230802112413-45.png]]
	635
	636
	637	Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
	638
	639	[[image:image-20230802112413-46.png]]
	640
	641
70.1	642	The device needs to enable the TLS mode and set the (% style="color:blue" %)AT+TLSMOD=1,0(%%) command.
53.2	643
83.8	644	(% style="color:blue" %)On the Connection Profile window, set the following information:
70.1	645
83.8	646	* (% style="color:#037691" %)Profile Name: “Any name”
53.2	647
83.8	648	* (% style="color:#037691" %)Broker Address: mqtt.tago.io
53.23	649
83.8	650	* (% style="color:#037691" %)Broker Port: 8883
53.23	651
83.8	652	* (% style="color:#037691" %)Client ID: “Any value”
53.23	653
83.8	654	(% style="color:blue" %)On the section User credentials, set the following information:
53.2	655
83.8	656	* (% style="color:#037691" %)User Name: “Any value” (%%) ~/~/ Tago validates your user by the token only
53.2	657
83.8	658	* (% style="color:#037691" %)Password: “Your device token”
53.2	659
83.8	660	* (% style="color:#037691" %)PUBTOPIC: “Any value”
53.23	661
83.8	662	* (% style="color:#037691" %)SUBTOPIC: “Any value”
53.23	663
70.1	664	(% style="color:blue" %)AT command:
	665
83.8	666	* (% style="color:#037691" %)AT+PRO=3,0 or 3,5 (%%) ~/~/ hex format or json format
70.1	667
83.5	668	* (% style="color:#037691" %)AT+SUBTOPIC=<device name>or User Defined
70.1	669
83.5	670	* (% style="color:#037691" %)AT+PUBTOPIC=<device name>or User Defined
	671
	672	* (% style="color:#037691" %)AT+CLIENT=<device name> or User Defined
	673
	674	* (% style="color:#037691" %)AT+UNAME=<device name> or User Defined
	675
	676	* (% style="color:#037691" %)AT+PWD=“Your device token”
	677
173.2	678	=== 3.8.2 Simulate with MQTT.fx ===
53.23	679
99.3	680
70.1	681	[[image:image-20230802112413-52.png]]
53.23	682
53.2	683
105.2	684	[[image:image-20230808105300-2.png\|\|height="553" width="1026"]]
53.2	685
99.3	686
53.38	687	Users can run the (% style="color:blue" %)AT+PRO=3,5(%%) command, and the payload will be converted to JSON format.
53.2	688
105.2	689	[[image:image-20230808105217-1.png\|\|height="556" width="1031"]]
53.44	690
70.1	691	[[image:image-20230808105329-3.png]]
53.2	692
	693
173.2	694	=== 3.8.3 tago data ===
53.2	695
53.23	696
105.2	697	[[image:image-20230802112413-50.png\|\|height="242" width="1037"]]
53.2	698
59.1	699	[[image:image-20230802112413-51.png\|\|height="184" width="696"]]
53.2	700
	701
173.2	702	== 3.9 TCP Connection ==
63.1	703
83.6	704
83.5	705	(% style="color:blue" %)AT command:
63.1	706
83.5	707	* (% style="color:#037691" %)AT+PRO=4,0 (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
63.1	708
83.5	709	* (% style="color:#037691" %)AT+PRO=4,1 (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
63.1	710
83.8	711	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5600 (%%) ~/~/ to set TCP server address and port
83.5	712
83.6	713	(% style="color:blue" %)Sensor Console Output when Uplink:
83.5	714
63.1	715	[[image:image-20230807233631-1.png]]
	716
	717
83.6	718	(% style="color:blue" %)See result in TCP Server:
63.1	719
	720	[[image:image-20230807233631-2.png]]
132.1	721
	722
173.2	723	== 3.10 AWS Connection ==
132.1	724
	725
164.1	726	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]]
	727
	728
203.2	729	== 3.11 ThingsEye (via MQTT) ==
	730
	731	=== 3.11.1 Configure ThingsEye ===
	732
	733	==== 3.11.1.1 Create MQTT integration ====
	734
	735
	736	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_NB”(%%), select type (% style="color:blue" %)MQTT;
	737
	738	[[image:image-20241126175509-1.png\|\|height="518" width="1081"]]
	739
	740
	741	Next, directly select to create a new Uplink data converter and downlink data converter.
	742
	743	[[image:image-20241126180135-2.png\|\|height="535" width="1092"]]
	744
	745	[[image:image-20241126180223-3.png\|\|height="518" width="1093"]]
	746
	747
	748	(% style="color:blue" %)Add a topic filter:
	749
	750	Consistent with the theme of the node setting.
	751
	752	(% style="color:red" %)Note: Recommended MQTT broker: lns1.thingseye.io 8883, fixed use. Topic can be changed on their own, but it need to be consistent with the node's publish and subscribe topic.
	753
	754	You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
	755
	756	[[image:image-20241126181024-4.png\|\|height="521" width="1081"]]
	757
	758
	759	==== 3.11.1.2 Add credentials to the MQTT integration ====
	760
	761
	762	Click on the MQTT integration you just created.
	763
	764	[[image:image-20241126181837-5.png\|\|height="365" width="1079"]]
	765
	766
	767	Click the edit icon in the upper right corner to enter the edit mode.
	768
	769	[[image:image-20241126184523-13.png\|\|height="330" width="1075"]]
	770
	771
	772	(% style="color:blue" %)Add credential files.
	773
217.1	774	Click this [[link>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]] to download the certificates.
203.2	775
	776	[[image:image-20241126183032-8.png\|\|height="757" width="976"]]
	777
	778	When the addition is complete, save the Settings.
	779
	780	[[image:image-20241126184303-12.png\|\|height="284" width="975"]]
	781
	782	[[image:image-20241126184211-11.png\|\|height="161" width="977"]]
	783
	784
220.2	785	==== 3.11.1.3 Setup uplink and downlink converters ====
203.2	786
	787
217.1	788	First, you need to download the [[MQTT uplink/downlink JS code>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]].
203.2	789
	790	* (% style="color:blue" %)Uplink Converter
	791
	792	The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume.
	793
	794	Go to the (% style="color:blue" %)Integrations center(%%) -> (% style="color:blue" %)Data converters(%%) page, and find that MQTT uplink converter that was newly created when the integration was created.
	795
	796	[[image:image-20241126184906-14.png\|\|height="424" width="1100"]]
	797
	798	Enter edit mode and apply MQTT uplink JS code to this uplink converter.
	799
	800	[[image:image-20241126190131-15.png\|\|height="542" width="1103"]]
	801
	802
	803	* (% style="color:blue" %)Downlink Converter
	804
	805	Go to the (% style="color:blue" %)Integrations center(%%) -> (% style="color:blue" %)Data converters(%%) page, and find that MQTT downlink converter that was newly created when the integration was created.
	806
	807	[[image:image-20241126190251-16.png\|\|height="372" width="1113"]]
	808
	809	Enter edit mode and apply MQTT downlink JS code to this downlink converter.
	810
	811	[[image:image-20241126190737-17.png\|\|height="527" width="1114"]]
	812
	813
216.1	814	=== 3.11.2 Simulate with MQTT.fx ===
203.2	815
	816
216.1	817	[[image:image-20241126191118-18.png\|\|height="605" width="835"]]
203.2	818
216.1	819	[[image:image-20241126193252-25.png\|\|height="663" width="803"]]
203.2	820
	821
220.2	822	=== 3.11.3 Configure -NB node ===
203.2	823
	824
216.1	825	First you need to configure the certificate to the -NB node. Follow the instructions in this [[link>>https://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H4.1.2Configurecertificate]] to configure the certificate.
	826
	827	Screenshot of successful certificate configuration:
	828
	829	* Configuring the CA Certificate
	830
220.2	831	[[image:image-20241126192009-19.png\|\|height="431" width="697"]]
216.1	832
220.2	833	[[image:image-20241126192130-21.png\|\|height="426" width="694"]]
	834
216.1	835	* Configure client certificate
	836
	837	[[image:image-20241126192246-22.png\|\|height="397" width="693"]][[image:image-20241126192315-23.png\|\|height="402" width="645"]]
	838
	839	* Configure client private key
	840
	841	[[image:image-20241126192415-24.png\|\|height="435" width="737"]]
	842
	843
	844	When the certificate is configured, burn the boot program, burn the working firmware, and then restart the device.
	845
	846	Then configure the -NB node to connect to the ThingsEye platform:
	847
203.2	848	(% style="color:blue" %)AT Commands
	849
216.1	850	* (% style="color:#037691" %)AT+PRO=3,5 (%%) ~/~/ Use MQTT Connection & Json Payload
217.2	851	* (% style="color:#037691" %)AT+SERVADDR=lns1.thingseye.io,8883
220.2	852	* (% style="color:#037691" %)AT+SUBTOPIC=8899 (%%)~/~/ Consistent with the Topic of MQTT integration created by ThingsEye
	853	* (% style="color:#037691" %)AT+PUBTOPIC=8899 (%%)~/~/ Consistent with the Topic of MQTT integration created by ThingsEye
216.1	854	* (% style="color:#037691" %)AT+CLIENT=NULL
	855	* (% style="color:#037691" %)AT+UNAME=NULL
	856	* (% style="color:#037691" %)AT+PWD=NULL
	857	* (% style="color:#037691" %)AT+TLSMOD=1,0
203.2	858
216.1	859	Test Uplink by click the button for 1~~3 seconds, the MQTT integration in ThingsEye allows you to view the data upstream from the device:
203.2	860
216.1	861	[[image:image-20241126193458-26.png\|\|height="375" width="1012"]]
203.2	862
216.1	863	[[image:image-20241126193609-27.png\|\|height="424" width="1014"]]
203.2	864
	865
216.1	866	Go to (% style="color:blue" %)"Device" (%%) -> (% style="color:blue" %) "Search Device"(%%), enter the (% style="color:blue" %) IMEI(%%) of the device to find the device.
203.2	867
216.1	868	[[image:image-20241126194018-28.png\|\|height="318" width="1076"]]
203.2	869
216.1	870	You can view the data that has just been uplink on the device:
203.2	871
216.1	872	[[image:image-20241126194123-29.png\|\|height="486" width="1073"]]
203.2	873
216.1	874
154.1	875	= 4. MQTT/UDP/TCP downlink =
145.2	876
154.1	877	== 4.1 MQTT (via MQTT.fx) ==
	878
180.1	879
154.1	880	Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
	881
160.1	882	1. Configure node MQTT connection (via MQTT.fx):
154.1	883
	884	(% style="color:blue" %)AT command:
	885
160.1	886	* (% style="color:#037691" %)AT+PRO=3,0 or 3,5 (%%)~/~/ hex format or json format
154.1	887
	888	* (% style="color:#037691" %)AT+SUBTOPIC=User Defined
	889
	890	* (% style="color:#037691" %)AT+PUBTOPIC=User Defined
	891
	892	* (% style="color:#037691" %)AT+UNAME=<device name> or User Defined
	893
	894	* (% style="color:#037691" %)AT+PWD=<device name> or User Defined
	895
160.1	896	* (% style="color:#037691" %)AT+SERVADDR=8.217.91.207,1883 (%%) ~/~/ to set MQTT server address and port
154.1	897
	898	(% 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.
	899
160.1	900	[[image:image-20240417180145-2.png\|\|height="434" width="587"]][[image:image-20240417180737-3.png\|\|height="431" width="584"]]
154.1	901
	902
160.1	903	2. When the node uplink packets, we can observe the data in MQTT.fx.
154.1	904
160.1	905	[[image:image-20240418144337-1.png\|\|height="709" width="802"]]
154.1	906
160.1	907	3. The downlink command can be successfully sent only when the downlink port is open.
154.1	908
160.1	909	The downlink port is opened for about 3 seconds after uplink packets are sent.
154.1	910
160.1	911	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.
154.1	912
160.1	913	[[image:image-20240418150435-3.png\|\|height="582" width="659"]]
	914
	915	[[image:image-20240418150932-4.png\|\|height="492" width="1061"]]
	916
	917	(% 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.
	918
	919
154.1	920	= 5. FAQ =
	921
	922	== 5.1 What is the usage of Multi Sampling and One Uplink? ==
	923
	924
133.1	925	The NB series has the feature for Multi Sampling and one uplink. See one of them
	926
	927	[[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]]
	928
	929	User can use this feature for below purpose:
	930
	931	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.
	932	1. Give more sampling data points.
	933	1. Increase reliable in transmission. For example. If user set
	934	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)
219.2	935	1. AT+NOUD=24* ~/~/ The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
	936	1. AT+TDC=7200* ~/~/ Uplink every 2 hours.
148.2	937	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.
133.1	938
154.1	939	== 5.2 Why the uplink JSON format is not standard? ==
145.1	940
148.2	941
145.1	942	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.
	943
148.1	944	The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
	945
145.1	946	[[image:image-20240229233154-1.png]]
	947
	948
219.2	949	== 5.3 What is the data consumption for different transfer mode？ ==
219.1	950
	951
	952	For the data consumption of NB-IoT End node in different transfer mode, reference link:
	953
	954	[[https:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20~~-~~-%20NBCB/>>https://wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20--%20NBCB/]]
	955
219.2	956
154.1	957	= 6. Trouble Shooting: =
133.1	958
154.1	959	== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
133.1	960
145.2	961
132.1	962	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.
	963
	964	If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
	965
	966	[[image:image-20240207002003-1.png]]
	967
	968
	969	If fail to attach network, it will shows signal 99. as below:
	970
	971	[[image:image-20240207002129-2.png]]
	972
	973
	974	(% class="lead" %)
	975	When see this issue, below are the checklist:
	976
	977	* 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.
	978	* 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]].
	979	* 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]].
	980	* Check if the device is attached to Carrier network but reject. (need to check with operator).
	981	* Check if the antenna is connected firmly.
	982
	983	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.
	984
135.1	985
154.1	986	== 6.2 Issue: "NBIOT did not respond" ==
135.1	987
145.2	988
135.1	989	(% class="box errormessage" %)
	990	(((
	991	11:24:22.397 [44596]NBIOT did not respond.
	992	11:24:24.315 [46530]NBIOT did not respond.
	993	11:24:26.256 [48464]NBIOT did not respond.
	994	11:24:28.196 [50398]NBIOT did not respond.
	995	11:24:30.115 [52332]NBIOT did not respond.
	996	11:24:32.127 [54266]NBIOT did not respond.
	997	11:24:32.127 [54299]Restart the module...
	998	11:24:39.181 [61332]No response when shutting down
	999	)))
	1000
	1001	This issue might due to initiate issue for NB-IoT module. In this case, please try:
	1002
	1003	1) Open Enclosure
	1004
	1005	2) Power off device by pull out the power on Jumper
	1006
	1007	3) Power on device by connect back the power jumper.
	1008
	1009	4) push reset button.
	1010
	1011	[[image:image-20240208001740-1.png]]
138.1	1012
	1013
154.1	1014	== 6.3 Issue: "Failed to readI MSI number" ==
138.1	1015
145.2	1016
138.1	1017	(% class="box errormessage" %)
	1018	(((
	1019	[18170]Failed to read IMSI:1umber.
	1020	[20109]Failed to read IMSI numoer.
	1021	[22048]Failed to read IMSI number.
	1022	[29842lRestart the module...
	1023	)))
	1024
141.1	1025	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"]].
	1026
	1027
161.2	1028	== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
141.1	1029
145.2	1030
142.1	1031	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.
141.1	1032
	1033	[[image:image-20240226111928-1.png]]
161.2	1034
	1035
	1036	== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
	1037
219.2	1038
163.1	1039	(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
	1040	=== UDP: ===
161.2	1041
219.2	1042
163.1	1043	(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
161.2	1044	Its downlink command is the same as the AT command, but brackets are required.
	1045	Example:
	1046
	1047	{AT+TDC=300}
	1048
163.1	1049
	1050	(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
	1051	=== MQTT: ===
	1052
219.2	1053
163.1	1054	Json：
	1055
	1056	The Json format in MQTT mode needs to be configured with all commands.
	1057	If you have configurations that need to be changed, please change them in the template below.
	1058	Template:
	1059
	1060	{
	1061	"AT+SERVADDR":"119.91.62.30,1882",
	1062	"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
	1063	"AT+UNAME":"usenamedragino",
	1064	"AT+PWD":"passworddragino",
	1065	"AT+PUBTOPIC":"123",
	1066	"AT+SUBTOPIC":"321",
	1067	"AT+TDC":"7200",
	1068	"AT+INTMOD":"0",
	1069	"AT+APN":"NULL",
	1070	"AT+5VT":"0",
	1071	"AT+PRO":"3,5",
	1072	"AT+TR":"900",
	1073	"AT+NOUD":"0",
	1074	"AT+CSQTIME":"5",
	1075	"AT+DNSTIMER":"0",
	1076	"AT+TLSMOD":"0,0",
	1077	"AT+MQOS":"0",
	1078	"AT+TEMPALARM1":"0",
	1079	"AT+TEMPALARM2":"10",
	1080	"AT+TEMPALARM3":"0"
	1081	}
	1082
	1083	Hex：
	1084
	1085	MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
	1086
	1087	The supported commands are consistent with LoRaWAN's hex commands.
	1088	Please refer to the following link to obtain the hex format:
	1089
	1090	[[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/]]
	1091
167.1	1092
180.1	1093	== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
167.1	1094
180.1	1095
167.1	1096	* AT Command: AT +GETLOG
	1097
	1098	This command can be used to query upstream logs of data packets.
	1099
	1100	[[image:image-20240701114700-1.png]]
	1101
	1102
181.1	1103	== 6.7 How to find the AT Command Password if lost? ==
167.1	1104
181.1	1105
182.1	1106	=== Why can't the password access AT command after upgrade(-NB)? ===
181.1	1107
	1108
	1109	Because the new version of -NB firmware has updated the factory reset function, users can choose to restore all parameters to factory Settings, or keep the password to restore the rest of the parameters to factory Settings.
	1110
	1111	This update changes the password address of the firmware, so the password will be invalid after the customer upgrades from the old version of firmware (without FDR1 function) to the new version of firmware (with FDR1 function).
	1112
	1113	Two different restore factory Settings configurations.
	1114
	1115	(% style="color:blue" %)AT command:
	1116
	1117	* (% style="color:#037691; font-weight:bold" %)AT+FDR(%%) ~/~/ Reset Parameters to Factory Default.
	1118	* (% style="color:#037691; font-weight:bold" %)AT+FDR1(%%) ~/~/ Reset parameters to factory default values except for passwords.(new)
	1119
219.2	1120
182.1	1121	=== Version Confirmation ===
181.1	1122
220.1	1123
181.1	1124	We are now dividing the old firmware(without FDR1 function) with the new firmware(with FDR1 function) by whether it contains FDR1 functionality. Please refer to the table:
	1125
	1126	(% border="1" style="background-color:#f2f2f2; width:510px" %)
	1127	\|(% style="background-color:#4f81bd; color:white; width:210px" %)General Model\|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
	1128	Firmware version
	1129
	1130	(without FDR1 function)
	1131	)))\|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
	1132	Firmware version
	1133
	1134	(with FDR1 function)
	1135	)))
	1136	\|(% style="width:210px" %)(((
	1137	CPL03-NB, S31-NB, SN50V3-NB, TS01-NB, D20-NB, DS03A-NB, DDS04-NB, DDS45-NB, DDS20-NB, DDS75-NB, LDS12-NB, LDS40-NB, LMS01-NB, MDS120-NB, MDS200-NB, SE01-NB, SPH01-NB;
	1138	)))\|(% style="width:150px" %)Before V1.2.1\|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
	1139	\|(% style="width:210px" %)(((
	1140	WL03A-NB, SDI-12-NB;
	1141	)))\|(% style="width:150px" %)Before V1.0.2\|(% style="width:150px" %)(((
	1142	After V1.0.8 (including V1.0.2)
	1143	)))
	1144	\|(% style="width:210px" %)(((
	1145	SW3L-NB, PS-NB;
	1146	)))\|(% style="width:150px" %)Before V1.0.5\|(% style="width:150px" %)(((
	1147	After V1.0.5 (including V1.0.5)
	1148	)))
	1149	\|(% style="width:210px" %)RS485-NB\|(% style="width:150px" %)Before V1.0.8\|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
	1150
219.2	1151
182.1	1152	=== UART connection and firmware update methods ===
181.1	1153
	1154
	1155	Users can query passwords only using the UART interface via the STM32CubeProgrammer.
	1156
	1157	See [[UART Connection>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]].
	1158
	1159	update firmware through UART TTL interface : [[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]].
	1160
	1161
182.1	1162	=== query the password via STM32CubeProgrammer ===
181.1	1163
	1164
	1165	Users can use the password address to query the password through STM32CubeProgrammer.
	1166
	1167	* The password address for old firmware(without FDR1 function) : 0x08019000
	1168	* The password address for new firmware(with FDR1 function) : 0x08025D00
	1169
	1170	(% style="color:red" %)Notice: The password can only be queried after the firmware is run once.
	1171
	1172
	1173	Procedure for querying the password(old firmware):
	1174
	1175	* After the firmware upgrade is complete, switch back to the FLASH and reset the node to run the firmware once.
	1176	* Then place the switch at the ISP and connect to the STM32CubeProgrammer (same as when burning the firmware).
	1177	* Click "Device memory", enter 0x08019000 in "Address", and click "Read"
	1178	* Find the 0x08019000 address field and then read the current password as shown in the screenshot below.
	1179
	1180	[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827171901-3.png?width=912&height=528&rev=1.1\|\|alt="image-20240827171901-3.png"]]
	1181
	1182
	1183	Procedure for querying the password(new firmware):
	1184
183.1	1185	Refer to [[the old and new firmware division>>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/#HVersionConfirmation]] above, and run the firmware first after updating the firmware.
181.1	1186
	1187	* After the firmware upgrade is complete, switch back to the FLASH and reset the node to run the new firmware once.
	1188	* Then place the switch at the ISP and connect to the STM32CubeProgrammer (same as when burning the firmware).
	1189	* Click "Device memory", enter 0x08025D00 in "Address", and click "Read"
	1190	* Find the 0x08025D00 address field and then read the current password as shown in the screenshot below.
	1191
	1192	[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827180414-1.png?width=910&height=527&rev=1.1\|\|alt="image-20240827180414-1.png"]]
	1193
	1194
182.1	1195	=== Special case ===
181.1	1196
	1197
	1198	If the user has never changed the password manually, the user cannot find the valid password through the above two password addresses. In this case, the valid password is still the original password on the node box label (AT+PIN).
	1199
	1200	Invalid query screenshot example:
	1201
	1202	[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827181447-4.png?width=889&height=519&rev=1.1\|\|alt="image-20240827181447-4.png"]]
	1203
	1204	[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827181431-3.png?width=892&height=515&rev=1.1\|\|alt="image-20240827181431-3.png"]]
	1205
	1206
	1207
161.2	1208

Wiki source code of General Configure/Commands to Connect to IoT server for -NB & -NS NB-IoT models

Applications

Navigation