Wiki source code of General Manual for -CB , -CS models

Version 129.3 by Xiaoling on 2024/09/14 10:54

version	line-number	content
2.1	1
1.1	2
	3
2.1	4	(% class="wikigeneratedid" id="HTableofContents:" %)
	5	Table of Contents:
1.1	6
2.1	7	{{toc/}}
1.1	8
2.1	9	= 1. The use of this guideline =
1.1	10
129.3	11
3.1	12	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.
1.1	13
3.1	14
2.1	15	= 2. Attach Network =
1.1	16
2.1	17	== 2.1 General Configure to attach network ==
1.1	18
129.3	19
3.1	20	To attache end nodes to NB-IoT or LTE-M Network, You need to:
1.1	21
3.1	22	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)
2.1	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
1.1	27
7.1	28	[[image:image-20240602220856-1.png]]
1.1	29
	30
129.3	31	[[image:http://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20230808205045-1.png?width=438&height=293&rev=1.1\|\|alt="image-20230808205045-1.png"]]
7.1	32
	33
3.1	34	After doing above, the end nodes should be able to attach to NB-IoT network .
1.1	35
3.1	36	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
1.1	37
5.1	38	~-~-(% style="color:blue" %) CAT-NB2: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B28/B66/B71/B85 (%%).
3.1	39
5.1	40	~-~-(% style="color:blue" %) CAT-M1: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85 (%%).
3.1	41
4.1	42	Make sure you use a the NB-IoT or LTE-M SIM card.
3.1	43
4.1	44	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1134px" %)
	45	\|(% 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:406px" %)NB-IoT Coverage\|(% style="background-color:#4f81bd; color:white; width:351px" %)LTE-M Coverage\|(% style="background-color:#4f81bd; color:white; width:120px" %)Comments
	46	\|(% style="width:117px" %)[[1NCE>>https://1nce.com]]\|(% style="width:151px" %)iot.1nce.net\|(% style="width:406px" %)(((
2.1	47	[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]
1.1	48
4.1	49	Austria, Belgium, Bulgaria, China, Croatia, Czech Republic, Denmark, Estonia, Finland, Germany, Great Britain, Greece, Hungary, Ireland,Italy, Latvia, Malta, Netherlands, Norway, Portugal, Puerto Rico, Russia, Slovak,Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands
	50	)))\|(% style="width:351px" %)(((
	51	Argentina, Austria, Australia, Belgium, Canada, Denmark,Estonia, Finland, France, Germany, Great Britain, Hungary, Ireland, Japan,Jersey, Korea, Repiblic of, Latvia, Luxembourg, Mexico, Netherlands, New Zealand, Norway, Poland, Puerto Rico, Romania, Spain, Sweden, Switzerland,Taiwan, USA, US Virgin Islands.
	52	)))\|(% style="width:120px" %)UK: Band20
	53	\|(% style="width:117px" %)China Mobile\|(% style="width:151px" %)No need configure\|(% style="width:406px" %)China Mainland, HongKong\|(% style="width:351px" %) \|(% style="width:120px" %)
	54	\|(% style="width:117px" %)China Telecom\|(% style="width:151px" %)ctnb\|(% style="width:406px" %)China Mainland\|(% style="width:351px" %) \|(% style="width:120px" %)
1.1	55
2.1	56	== 2.2 Speed Up Network Attach time ==
1.1	57
4.1	58	BG95-M2 supports multi bands (% style="color:blue" %)in NB-IoT and LTE-M. (%%) 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.
1.1	59
9.1	60	Note:Before using the NB module command, users need to power on the NB module. Run the AT+QSW command to turn on and off the NB module.Remember to shut down after using the NB module command, otherwise it will consume power.
1.1	61
4.1	62	Attache to 1NCE card for Australia use:
1.1	63
4.1	64	* AT+COPS=1,2,"50501",8
	65	* AT+QCFG="band",0,0x8000000,0x8000000,1
1.1	66
4.1	67	After connection is successful, user can use (% style="color:#037691" %)AT+QENG="servingcell"(%%) to check which band is actually in used.
	68
	69	AT+QENG="servingcell"
	70	+QENG: "servingcell","NOCONN","eMTC","FD
	71	D",505,01,90D2C0B,258,9410,28,5,5,901A,-112,-17,-80,10,27
	72
	73
2.1	74	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/]]
1.1	75
12.1	76	=== 1.Configure Frequency Band ===
5.1	77
9.1	78	AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
5.1	79
9.1	80	<GSM_bandval>:
	81
	82	0 No change
	83	0x1 EGSM900
	84	0x2 DCS1800
	85	0x4 GSM850
	86	0x8 PCS1900
	87	0xF All of the supported bands above
	88
	89	<eMTC_bandval>:
	90
	91	0 No change
	92	0x1 LTE B1
	93	0x2 LTE B2
	94	0x4 LTE B3
	95	0x8 LTE B4
	96	0x10 LTE B5
	97	0x80 LTE B8
	98	0x800 LTE B12
	99	0x1000 LTE B13
	100	0x20000 LTE B18
	101	0x40000 LTE B19
	102	0x80000 LTE B20
	103	0x1000000 LTE B25
	104	0x2000000 LTE B26
	105	0x4000000 LTE B27
	106	0x8000000 LTE B28
	107	0x40000000 LTE B31
	108	0x20000000000000000 LTE B66
	109	0x800000000000000000 LTE B72
	110	0x1000000000000000000 LTE B73
	111	0x1000000000000000000000 LTE B85
	112
	113	<NB-IoT_bandval>:
	114
	115	0 No change
	116	0x1 LTE B1
	117	0x2 LTE B2
	118	0x4 LTE B3
	119	0x8 LTE B4
	120	0x10 LTE B5
	121	0x80 LTE B8
	122	0x800 LTE B12
	123	0x1000 LTE B13
	124	0x20000 LTE B18
	125	0x40000 LTE B19
	126	0x80000 LTE B20
	127	0x1000000 LTE B25
	128	0x8000000 LTE B28
	129	0x40000000 LTE B31
	130	0x20000000000000000 LTE B66
	131
	132	0x400000000000000000 LTE B71
	133	0x800000000000000000 LTE B72
	134	0x1000000000000000000 LTE B73
	135	0x1000000000000000000000 LTE B85
	136
	137	For example, setting the LTE-M network frequency band to 3.
	138
	139	AT+QCFG="band",0xF,0x4,0,1
	140
	141	When searching for all bands, the value of this command is set to:
	142
	143	AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
	144
	145
12.1	146	=== 2.Configure search network sequence ===
9.1	147
	148	AT+QCFG="nwscanseq",<scanseq>,1
	149
	150	<scanseq>:
	151
	152	00 Automatic (eMTC → NB-IoT → GSM)
	153	01 GSM
	154	02 eMTC
	155	03 NB-IoT
	156
	157	AT+QCFG="nwscanseq",02,1 ~/~/Priority search for eMTC
	158
12.1	159	=== 3.Configure Network Category to be Searched for under LTE RAT ===
9.1	160
	161	AT+QCFG="iotopmode",mode,1
	162
	163	0 eMTC
	164	1 NB-IoT
	165	2 eMTC and NB-IoT
	166
13.1	167	=== 4.AT command to set frequency band and network category ===
9.1	168
13.1	169	AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f ~/~/<eMTC_bandval>,<NB-IoT_bandval>
	170
	171	AT+IOTMOD=0 ~/~/ 0 eMTC 1 NB-IoT 2 eMTC and NB-IoT
	172
	173	Example :
	174
	175	Taking the use of 1nce cards in the United States as an example.
	176
	177	AT+APN=iot.1nce.net ~/~/set APN
	178
	179	AT+QBAND=0x100180A,0 ~/~/ eMTC ：Set frequency band B2,B4,B12,B13,B25 NB-IoT：No change
	180
	181	AT+IOTMOD=0 ~/~/ Set eMTC Network
	182
	183	Setting the above commands in the United States will greatly reduce the network search time of the NB module.
	184
	185
2.1	186	= 3. Configure to connect to different servers =
1.1	187
2.1	188	== 3.1 General UDP Connection ==
1.1	189
2.1	190	The NB-IoT Sensor can send packet to server use UDP protocol.
1.1	191
129.1	192
2.1	193	=== 3.1.1 Simulate UDP Connection by PC tool ===
1.1	194
129.1	195
2.1	196	We can use PC tool to simulate UDP connection to make sure server works ok.
1.1	197
129.1	198	[[image:http://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20230802112413-1.png?width=1024&height=468&rev=1.1\|\|alt="image-20230802112413-1.png"]]
1.1	199
129.1	200
2.1	201	=== 3.1.2 Configure NB-IoT Sensor ===
1.1	202
2.1	203	==== 3.1.2.1 AT Commands ====
1.1	204
129.1	205
2.1	206	(% style="color:blue" %)AT Commands:
1.1	207
3.1	208	* (% style="color:#037691" %)AT+PRO=2,0 (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload
1.1	209
108.1	210	* (% style="color:#037691" %)AT+SERVADDR=8.217.91.207,1999 (%%) ~/~/ Set UDP server address and port
1.1	211
20.2	212	[[image:image-20240819102802-1.png]]
1.1	213
129.1	214
2.1	215	==== 3.1.2.2 Uplink Example ====
1.1	216
	217
129.1	218	[[image:image-20240819105418-8.png\|\|height="611" width="1287"]]
	219
	220
8.1	221	== 3.2 General COAP Connection ==
	222
129.1	223
8.1	224	The NB-IoT Sensor can send packet to server use COAP protocol.
	225
	226	Below are the commands.
	227
	228	(% style="color:blue" %)AT Commands:
	229
	230	* (% style="color:#037691" %)AT+PRO=1,0 (%%) ~/~/ Set to use COAP protocol to uplink, Payload Type select Hex payload.
	231
	232	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5683 (%%) ~/~/ Set COAP server address and port
	233
	234	* (% style="color:#037691" %)AT+URI1=11,"I" (%%) ~/~/ Configure CoAP Message Options
9.1	235	* (% style="color:#037691" %)AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1" (%%) ~/~/ Configure CoAP Message Options
8.1	236
20.2	237	[[image:image-20240819103212-2.png]]
	238
129.1	239
8.1	240	=== 3.2.1 Uplink Example ===
	241
129.1	242
20.2	243	[[image:image-20240819103909-4.png\|\|height="453" width="955"]]
8.1	244
	245
2.1	246	== 3.2 General MQTT Connection ==
1.1	247
129.1	248
2.1	249	The NB-IoT Sensor can send packet to server use MQTT protocol.
1.1	250
2.1	251	Below are the commands.
1.1	252
2.1	253	(% style="color:blue" %)AT Commands:
1.1	254
3.1	255	* (% style="color:#037691" %)AT+PRO=3,0 (%%) ~/~/ Set to use MQTT protocol to uplink, Payload Type select Hex payload.
1.1	256
3.1	257	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,1883 (%%) ~/~/ Set MQTT server address and port
1.1	258
3.1	259	* (% style="color:#037691" %)AT+CLIENT=CLIENT (%%) ~/~/ Set up the CLIENT of MQTT
1.1	260
3.1	261	* (% style="color:#037691" %)AT+UNAME=UNAME (%%) ~/~/ Set the username of MQTT
1.1	262
3.1	263	* (% style="color:#037691" %)AT+PWD=PWD (%%) ~/~/ Set the password of MQTT
1.1	264
3.1	265	* (% style="color:#037691" %)AT+PUBTOPIC=NSE01_PUB (%%) ~/~/ Set the sending topic of MQTT
1.1	266
3.1	267	* (% style="color:#037691" %)AT+SUBTOPIC=NSE01_SUB (%%) ~/~/ Set the subscription topic of MQTT
1.1	268
20.2	269	[[image:image-20240819105003-7.png\|\|height="613" width="458"]]
1.1	270
	271
20.2	272	[[image:image-20240819104942-6.png\|\|height="702" width="974"]]
	273
2.1	274	(% 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.
1.1	275
129.1	276
2.1	277	== 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
1.1	278
2.1	279	=== 3.3.1 Get MQTT Credentials ===
1.1	280
129.1	281
2.1	282	[[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.
1.1	283
34.2	284	[[image:image-20240819173602-1.png\|\|height="401" width="743"]]
1.1	285
34.2	286	[[image:image-20240819173706-3.png\|\|height="595" width="597"]]
1.1	287
129.1	288
2.1	289	=== 3.3.2 Simulate with MQTT.fx ===
1.1	290
2.1	291	==== 3.3.2.1 Establish MQTT Connection ====
1.1	292
129.1	293
2.1	294	After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
1.1	295
34.2	296	[[image:image-20240819173826-4.png\|\|height="534" width="734"]]
1.1	297
2.1	298	* (% style="color:#037691" %)Broker Address:(%%) mqtt3.thingspeak.com
1.1	299
2.1	300	* (% style="color:#037691" %)Broker Port:(%%) 1883
1.1	301
2.1	302	* (% style="color:#037691" %)Client ID:(%%) <Your ThingSpeak MQTT ClientID>
1.1	303
2.1	304	* (% style="color:#037691" %)User Name:(%%) <Your ThingSpeak MQTT User Name>
1.1	305
2.1	306	* (% style="color:#037691" %)Password:(%%) <Your ThingSpeak MQTT Password>
1.1	307
129.1	308
2.1	309	==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
1.1	310
129.1	311
34.2	312	[[image:image-20240819174033-5.png]]
1.1	313
34.2	314	[[image:image-20240819174209-6.png]]
1.1	315
2.1	316	(% style="color:blue" %)In MQTT.fx, we can publish below info:
1.1	317
2.1	318	* (% style="color:#037691" %)Topic:(%%) channels/YOUR_CHANNEL_ID/publish
1.1	319
2.1	320	* (% style="color:#037691" %)Payload:(%%) field1=63&field2=67&status=MQTTPUBLISH
1.1	321
2.1	322	Where 63 and 67 are the value to be published to field1 & field2.
1.1	323
2.1	324	(% style="color:blue" %)Result:
1.1	325
34.2	326	[[image:image-20240819174314-7.png\|\|height="469" width="785"]]
1.1	327
129.1	328
2.1	329	=== 3.3.3 Configure NB-IoT Sensor for connection ===
1.1	330
2.1	331	==== 3.3.3.1 AT Commands: ====
1.1	332
129.1	333
2.1	334	In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
1.1	335
2.1	336	* (% style="color:blue" %)AT+PRO=3,1 (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
1.1	337
2.1	338	* (% style="color:blue" %)AT+CLIENT=<Your ThingSpeak MQTT ClientID>
1.1	339
2.1	340	* (% style="color:blue" %)AT+UNAME=<Your ThingSpeak MQTT User Name>
1.1	341
2.1	342	* (% style="color:blue" %)AT+PWD=<Your ThingSpeak MQTT Password>
1.1	343
2.1	344	* (% style="color:blue" %)AT+PUBTOPIC=<YOUR_CHANNEL_ID>
1.1	345
2.1	346	* (% style="color:blue" %)AT+SUBTOPIC=<YOUR_CHANNEL_ID>
1.1	347
129.1	348
2.1	349	==== 3.3.3.2 Uplink Examples ====
1.1	350
129.1	351
34.2	352	[[image:image-20240819174540-8.png]]
1.1	353
2.1	354	For SE01-NB
1.1	355
2.1	356	For DDS20-NB
1.1	357
2.1	358	For DDS45-NB
1.1	359
2.1	360	For DDS75-NB
1.1	361
2.1	362	For NMDS120-NB
1.1	363
2.1	364	For SPH01-NB
1.1	365
2.1	366	For NLM01-NB
1.1	367
2.1	368	For NMDS200-NB
1.1	369
2.1	370	For CPN01-NB
1.1	371
2.1	372	For DS03A-NB
1.1	373
2.1	374	For SN50V3-NB
1.1	375
129.1	376
2.1	377	==== 3.3.3.3 Map fields to sensor value ====
1.1	378
129.1	379
2.1	380	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.
1.1	381
34.2	382	[[image:image-20240819174610-9.png]]
1.1	383
34.2	384	[[image:image-20240819174618-10.png]]
1.1	385
2.1	386	Below is the NB-IoT Product Table show the mapping.
1.1	387
129.1	388	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1353.82px" %)
	389	\|(% 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:139px" %)Field4\|(% style="background-color:#4f81bd; color:white; width:141px" %)Field5\|(% style="background-color:#4f81bd; color:white; width:142px" %)Field6\|(% style="background-color:#4f81bd; color:white; width:151px" %)Field7\|(% style="background-color:#4f81bd; color:white; width:137px" %)Field8\|(% style="background-color:#4f81bd; color:white; width:69px" %)Field9\|(% style="background-color:#4f81bd; color:white; width:65px" %)Field10
	390	\|(% style="background-color:#4f81bd; color:white; width:143px" %)S31x-NB\|(% style="width:103px" %)Temperature \|(% style="width:102px" %)Humidity\|(% style="width:157px" %)Battery\|(% style="width:139px" %)RSSI\|(% style="width:141px" %) \|(% style="width:142px" %) \|(% style="width:151px" %) \|(% style="width:137px" %) \|(% style="width:69px" %) \|(% style="width:65px" %)
	391	\|(% style="background-color:#4f81bd; color:white; width:143px" %)SE01-NB\|(% style="width:103px" %)Temperature \|(% style="width:102px" %)Humidity\|(% style="width:157px" %)conduct\|(% style="width:139px" %)dielectric_constant\|(% style="width:141px" %)Battery\|(% style="width:142px" %)RSSI\|(% style="width:151px" %) \|(% style="width:137px" %) \|(% style="width:69px" %) \|(% style="width:65px" %)
	392	\|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS20-NB\|(% style="width:103px" %)distance\|(% style="width:102px" %)Battery\|(% style="width:157px" %)RSSI\|(% style="width:139px" %) \|(% style="width:141px" %) \|(% style="width:142px" %) \|(% style="width:151px" %) \|(% style="width:137px" %) \|(% style="width:69px" %) \|(% style="width:65px" %)
	393	\|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS45-NB\|(% style="width:103px" %)distance\|(% style="width:102px" %)Battery\|(% style="width:157px" %)RSSI\|(% style="width:139px" %) \|(% style="width:141px" %) \|(% style="width:142px" %) \|(% style="width:151px" %) \|(% style="width:137px" %) \|(% style="width:69px" %) \|(% style="width:65px" %)
	394	\|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS75-NB\|(% style="width:103px" %)distance\|(% style="width:102px" %)Battery\|(% style="width:157px" %)RSSI\|(% style="width:139px" %) \|(% style="width:141px" %) \|(% style="width:142px" %) \|(% style="width:151px" %) \|(% style="width:137px" %) \|(% style="width:69px" %) \|(% style="width:65px" %)
	395	\|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS120-NB\|(% style="width:103px" %)distance\|(% style="width:102px" %)Battery\|(% style="width:157px" %)RSSI\|(% style="width:139px" %) \|(% style="width:141px" %) \|(% style="width:142px" %) \|(% style="width:151px" %) \|(% style="width:137px" %) \|(% style="width:69px" %) \|(% style="width:65px" %)
	396	\|(% 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:139px" %)RSSI\|(% style="width:141px" %) \|(% style="width:142px" %) \|(% style="width:151px" %) \|(% style="width:137px" %) \|(% style="width:69px" %) \|(% colspan="1" rowspan="1" style="width:65px" %)
	397	\|(% style="background-color:#4f81bd; color:white; width:143px" %)NLM01-NB\|(% style="width:103px" %)Humidity\|(% style="width:102px" %)Temperature\|(% style="width:157px" %)Battery\|(% style="width:139px" %)RSSI\|(% style="width:141px" %) \|(% style="width:142px" %) \|(% style="width:151px" %) \|(% style="width:137px" %) \|(% style="width:69px" %) \|(% style="width:65px" %)
	398	\|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS200-NB\|(% style="width:103px" %)distance1\|(% style="width:102px" %)distance2\|(% style="width:157px" %)Battery\|(% style="width:139px" %)RSSI\|(% style="width:141px" %) \|(% style="width:142px" %) \|(% style="width:151px" %) \|(% style="width:137px" %) \|(% style="width:69px" %) \|(% style="width:65px" %)
	399	\|(% 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:139px" %)calc flag\|(% style="width:141px" %)Battery\|(% style="width:142px" %)RSSI\|(% style="width:151px" %) \|(% style="width:137px" %) \|(% style="width:69px" %) \|(% style="width:65px" %)
	400	\|(% 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:139px" %)pb14 last open time\|(% colspan="1" rowspan="1" style="width:141px" %)pb15 level status\|(% colspan="1" rowspan="1" style="width:142px" %)pb15 alarm status\|(% colspan="1" rowspan="1" style="width:151px" %)pb15 door open num\|(% colspan="1" rowspan="1" style="width:137px" %)pb15 last open time\|(% colspan="1" rowspan="1" style="width:69px" %)Battery\|(% colspan="1" rowspan="1" style="width:65px" %)RSSI
	401	\|(% 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:139px" %)DS18B20 Temp\|(% colspan="1" rowspan="1" style="width:141px" %)exit_state/input PA4\|(% colspan="1" rowspan="1" style="width:142px" %)adc0\|(% colspan="1" rowspan="1" style="width:151px" %)Temperature \|(% colspan="1" rowspan="1" style="width:137px" %)Humidity\|(% colspan="1" rowspan="1" style="width:69px" %) \|(% colspan="1" rowspan="1" style="width:65px" %)
	402	\|(% 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:139px" %)DS18B20 Temp\|(% colspan="1" style="width:141px" %)exit_state/input PA4\|(% colspan="1" style="width:142px" %)adc0\|(% colspan="1" style="width:151px" %)distance\|(% colspan="1" style="width:137px" %) \|(% colspan="1" style="width:69px" %) \|(% colspan="1" style="width:65px" %)
	403	\|(% 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:139px" %)adc0\|(% colspan="1" style="width:141px" %)exit_state/input PA4\|(% colspan="1" style="width:142px" %)adc1\|(% colspan="1" style="width:151px" %)Temperature\|(% colspan="1" style="width:137px" %)Humidity\|(% colspan="1" style="width:69px" %)adc4\|(% colspan="1" style="width:65px" %)
	404	\|(% 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:139px" %)DS18B20 Temp\|(% colspan="1" style="width:141px" %)adc0\|(% colspan="1" style="width:142px" %)exit_state/input PA4\|(% colspan="1" style="width:151px" %)DS18B20 Temp2\|(% colspan="1" style="width:137px" %)DS18B20 Temp3\|(% colspan="1" style="width:69px" %) \|(% colspan="1" style="width:65px" %)
	405	\|(% 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:139px" %)DS18B20 Temp\|(% colspan="1" style="width:141px" %)adc0\|(% colspan="1" style="width:142px" %)exit_state/input PA4\|(% colspan="1" style="width:151px" %)Weight\|(% colspan="1" style="width:137px" %) \|(% colspan="1" style="width:69px" %) \|(% colspan="1" style="width:65px" %)
	406	\|(% 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:139px" %)count\|(% colspan="1" style="width:141px" %) \|(% colspan="1" style="width:142px" %) \|(% colspan="1" style="width:151px" %) \|(% colspan="1" style="width:137px" %) \|(% colspan="1" style="width:69px" %) \|(% colspan="1" style="width:65px" %)
1.1	407
2.1	408	== 3.4 [[Datacake>>https://datacake.co/]] ==
1.1	409
2.1	410	(% class="wikigeneratedid" %)
	411	Dragino NB-IoT sensors has its template in [[Datacake>>https://datacake.co/]] Platform. There are two version for NB Sensor,
1.1	412
2.1	413	(% class="wikigeneratedid" %)
46.2	414	As example for S31B-CB. there are two versions: S31B-CB-1D and S31B-CB-GE.
1.1	415
46.2	416	* (% style="color:blue" %)S31B-CB-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.
1.1	417
46.2	418	* (% style="color:blue" %)S31B-CB-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.
1.1	419
129.1	420
2.1	421	=== 3.4.1 For device Already has template ===
1.1	422
2.1	423	==== 3.4.1.1 Create Device ====
1.1	424
129.1	425
2.1	426	(% style="color:blue" %)Add Device(%%) in DataCake.
1.1	427
46.2	428	[[image:image-20240820110003-1.png]]
1.1	429
46.2	430	[[image:image-20240820110017-2.png]]
1.1	431
2.1	432	(% style="color:blue" %)Choose the correct model(%%) from template.
1.1	433
46.2	434	[[image:image-20240820110031-3.png]]
1.1	435
3.1	436	(% 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.
1.1	437
46.2	438	[[image:image-20240820110048-4.png]]
1.1	439
46.2	440	[[image:image-20240820110103-5.png]]
1.1	441
46.2	442	[[image:image-20240820110114-6.png]]
1.1	443
129.1	444
2.1	445	=== 3.4.2 For Device already registered in DataCake before shipped ===
1.1	446
2.1	447	==== 3.4.2.1 Scan QR Code to get the device info ====
1.1	448
129.1	449
1.1	450	Users can use their phones or computers to scan QR codes to obtain device data information.
	451
46.2	452	[[image:image-20240820110129-7.png]]
1.1	453
46.2	454	[[image:image-20240820110218-9.png]]
1.1	455
129.1	456
2.1	457	==== 3.4.2.2 Claim Device to User Account ====
1.1	458
	459	By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
	460
129.1	461
2.1	462	=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
1.1	463
129.1	464
2.1	465	Step1: Add a device
1.1	466
46.2	467	[[image:image-20240820110235-10.png]][[image:image-20240129170024-1.png\|\|height="330" width="900"]]
1.1	468
129.1	469
2.1	470	Step2: Choose your device type,please select dragino NB-IOT device
1.1	471
46.2	472	[[image:image-20240820110247-11.png]]
1.1	473
129.1	474
2.1	475	Step3: Choose to create a new device
1.1	476
75.2	477	[[image:image-20240820111016-12.png]]
1.1	478
129.1	479
2.1	480	Step4: Fill in the device ID of your NB device
1.1	481
75.2	482	[[image:image-20240820111101-13.png]]
1.1	483
129.1	484
2.1	485	Step5: Please select your device plan according to your needs and complete the creation of the device
1.1	486
75.2	487	[[image:image-20240820111113-14.png]]
1.1	488
129.1	489
2.1	490	Step6: Please add the decoder at the payload decoder of the device configuration.
1.1	491
2.1	492	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]]
1.1	493
75.2	494	[[image:image-20240820111236-15.png]]
1.1	495
75.2	496	[[image:image-20240820111248-16.png]]
1.1	497
129.1	498
2.1	499	Step7: Add the output of the decoder as a field
1.1	500
75.2	501	[[image:image-20240820111259-17.png]]
1.1	502
129.1	503
2.1	504	Step8: Customize the dashboard and use fields as parameters of the dashboard
1.1	505
75.2	506	[[image:image-20240820111312-18.png]]
1.1	507
75.2	508	[[image:image-20240820111322-19.png]]
1.1	509
75.2	510	[[image:image-20240820111333-20.png]]
1.1	511
129.1	512
2.1	513	=== 3.4.4 For device have not configured to connect to DataCake ===
1.1	514
129.1	515
2.1	516	(% class="lead" %)
1.1	517	Use AT command for connecting to DataCake
	518
2.1	519	(% style="color:blue" %)AT+PRO=2,0
1.1	520
2.1	521	(% style="color:blue" %)AT+SERVADDR=67.207.76.90,4445
1.1	522
129.1	523
2.1	524	== 3.5 Node-Red (via MQTT) ==
1.1	525
2.1	526	=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
1.1	527
129.1	528
1.1	529	Take S31-NB UDP protocol as an example.
	530
	531	Dragino provides input flow examples for the sensors.
	532
	533	User can download the required JSON file through Dragino Node-RED input flow template.
	534
2.1	535	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]]
1.1	536
	537	We can directly import the template.
	538
	539	The templates for S31-NB and NB95S31B are the same.
	540
75.2	541	[[image:image-20240820111353-21.png]]
1.1	542
	543	Please select the NB95S31B template.
	544
75.2	545	[[image:image-20240820111405-22.png]]
1.1	546
75.2	547	[[image:image-20240820111418-23.png]]
1.1	548
75.2	549	[[image:image-20240820111427-24.png]]
1.1	550
	551	Successfully imported template.
	552
75.2	553	[[image:image-20240820111438-25.png]]
1.1	554
	555	Users can set UDP port.
	556
75.2	557	[[image:image-20240820111448-26.png]]
1.1	558
129.1	559
2.1	560	=== 3.5.2 Simulate Connection ===
1.1	561
129.1	562
1.1	563	We have completed the configuration of UDP. We can try sending packets to node red.
	564
75.2	565	[[image:image-20240820111504-27.png]]
1.1	566
75.2	567	[[image:image-20240820111515-28.png]]
1.1	568
129.1	569
2.1	570	=== 3.5.3 Configure NB-IoT Sensors ===
1.1	571
129.1	572
2.1	573	* (% style="color:#037691" %)AT+PRO=3,0 or 3,5 (%%) ~/~/ hex format or json format
	574	* (% style="color:#037691" %)AT+SUBTOPIC=<device name>or User Defined
	575	* (% style="color:#037691" %)AT+PUBTOPIC=<device name>or User Defined
	576	* (% style="color:#037691" %)AT+CLIENT=<device name> or User Defined
	577	* (% style="color:#037691" %)AT+UNAME=<device name> or User Defined
	578	* (% style="color:#037691" %)AT+PWD=“Your device token”
1.1	579
129.1	580
2.1	581	== 3.6 ThingsBoard.Cloud (via MQTT) ==
1.1	582
2.1	583	=== 3.6.1 Configure ThingsBoard ===
1.1	584
2.1	585	==== 3.6.1.1 Create Device ====
1.1	586
129.1	587
2.1	588	Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
1.1	589
75.2	590	[[image:image-20240820112210-29.png]]
1.1	591
129.1	592
2.1	593	==== 3.6.1.2 Create Uplink & Downlink Converter ====
1.1	594
129.1	595
2.1	596	(% style="color:blue" %)Uplink Converter
1.1	597
2.1	598	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.
1.1	599
2.1	600	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.
1.1	601
75.2	602	[[image:image-20240820112222-30.png]]
1.1	603
2.1	604	(% style="color:blue" %)Downlink Converter
1.1	605
2.1	606	The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
1.1	607
75.2	608	[[image:image-20240820112236-31.png]]
1.1	609
2.1	610	(% style="color:red" %)Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.
1.1	611
129.1	612
2.1	613	==== 3.6.1.3 MQTT Integration Setup ====
1.1	614
129.1	615
2.1	616	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;
1.1	617
75.2	618	[[image:image-20240820112247-32.png]]
1.1	619
2.1	620	* The next steps is to add the recently created uplink and downlink converters;
1.1	621
75.2	622	[[image:image-20240820112302-33.png]]
1.1	623
75.2	624	[[image:image-20240820112316-34.png]]
1.1	625
2.1	626	(% style="color:blue" %)Add a topic filter:
1.1	627
	628	Consistent with the theme of the node setting.
	629
2.1	630	You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
1.1	631
75.2	632	[[image:image-20240820112330-35.png]]
1.1	633
129.1	634
2.1	635	=== 3.6.2 Simulate with MQTT.fx ===
1.1	636
75.2	637	[[image:image-20240820112340-36.png]]
1.1	638
75.2	639	[[image:image-20240820112351-37.png]]
1.1	640
129.1	641
2.1	642	=== 3.6.3 Configure NB-IoT Sensor ===
1.1	643
129.1	644
2.1	645	(% style="color:blue" %)AT Commands
1.1	646
3.1	647	* (% style="color:#037691" %)AT+PRO=3,3 (%%) ~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
1.1	648
2.1	649	* (% style="color:#037691" %)AT+SUBTOPIC=<device name>
1.1	650
2.1	651	* (% style="color:#037691" %)AT+PUBTOPIC=<device name>
1.1	652
2.1	653	* (% style="color:#037691" %)AT+CLIENT=<device name> or User Defined
1.1	654
2.1	655	* (% style="color:#037691" %)AT+UNAME=<device name> or User Defined
1.1	656
2.1	657	* (% style="color:#037691" %)AT+PWD=<device name> or User Defined
1.1	658
2.1	659	Test Uplink by click the button for 1 second
1.1	660
75.2	661	[[image:image-20240820112404-38.png]]
1.1	662
75.2	663	[[image:image-20240820112416-39.png]]
1.1	664
75.2	665	[[image:image-20240820112426-40.png]]
1.1	666
129.1	667
2.1	668	== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
1.1	669
2.1	670	=== 3.7.1 Create device & Get Credentials ===
1.1	671
129.1	672
2.1	673	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.
1.1	674
95.2	675	[[image:image-20240820112516-41.png]]
1.1	676
95.2	677	[[image:image-20240820112526-42.png]]
1.1	678
2.1	679	Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
1.1	680
95.2	681	[[image:image-20240820112539-43.png]]
1.1	682
2.1	683	The device needs to enable the TLS mode and set the (% style="color:blue" %)AT+TLSMOD=1,0(%%) command.
1.1	684
2.1	685	(% style="color:blue" %)On the Connection Profile window, set the following information:
1.1	686
2.1	687	* (% style="color:#037691" %)Profile Name: “Any name”
1.1	688
2.1	689	* (% style="color:#037691" %)Broker Address: mqtt.tago.io
1.1	690
2.1	691	* (% style="color:#037691" %)Broker Port: 8883
1.1	692
2.1	693	* (% style="color:#037691" %)Client ID: “Any value”
1.1	694
2.1	695	(% style="color:blue" %)On the section User credentials, set the following information:
1.1	696
2.1	697	* (% style="color:#037691" %)User Name: “Any value” (%%) ~/~/ Tago validates your user by the token only
1.1	698
2.1	699	* (% style="color:#037691" %)Password: “Your device token”
1.1	700
2.1	701	* (% style="color:#037691" %)PUBTOPIC: “Any value”
1.1	702
2.1	703	* (% style="color:#037691" %)SUBTOPIC: “Any value”
1.1	704
2.1	705	(% style="color:blue" %)AT command:
1.1	706
2.1	707	* (% style="color:#037691" %)AT+PRO=3,0 or 3,5 (%%) ~/~/ hex format or json format
1.1	708
2.1	709	* (% style="color:#037691" %)AT+SUBTOPIC=<device name>or User Defined
1.1	710
2.1	711	* (% style="color:#037691" %)AT+PUBTOPIC=<device name>or User Defined
1.1	712
2.1	713	* (% style="color:#037691" %)AT+CLIENT=<device name> or User Defined
1.1	714
2.1	715	* (% style="color:#037691" %)AT+UNAME=<device name> or User Defined
1.1	716
2.1	717	* (% style="color:#037691" %)AT+PWD=“Your device token”
1.1	718
129.1	719
2.1	720	=== 3.7.2 Simulate with MQTT.fx ===
1.1	721
129.1	722
95.2	723	[[image:image-20240820112552-44.png]]
1.1	724
95.2	725	[[image:image-20240820112604-45.png]]
1.1	726
2.1	727	Users can run the (% style="color:blue" %)AT+PRO=3,5(%%) command, and the payload will be converted to JSON format.
1.1	728
95.2	729	[[image:image-20240820112615-46.png]]
1.1	730
95.2	731	[[image:image-20240820112626-47.png]]
1.1	732
129.1	733
2.1	734	=== 3.7.3 tago data ===
1.1	735
129.1	736
95.2	737	[[image:image-20240820112637-48.png]]
1.1	738
95.2	739	[[image:image-20240820112647-49.png]]
1.1	740
129.1	741
2.1	742	== 3.8 TCP Connection ==
1.1	743
129.1	744
2.1	745	(% style="color:blue" %)AT command:
1.1	746
3.1	747	* (% style="color:#037691" %)AT+PRO=4,0 (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
1.1	748
3.1	749	* (% style="color:#037691" %)AT+PRO=4,1 (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
1.1	750
2.1	751	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5600 (%%) ~/~/ to set TCP server address and port
1.1	752
2.1	753	(% style="color:blue" %)Sensor Console Output when Uplink:
1.1	754
95.2	755	[[image:image-20240820112704-50.png]]
1.1	756
2.1	757	(% style="color:blue" %)See result in TCP Server:
1.1	758
95.2	759	[[image:image-20240820112716-51.png]]
1.1	760
129.1	761
2.1	762	== 3.9 AWS Connection ==
1.1	763
129.1	764
2.1	765	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]]
1.1	766
96.1	767
24.1	768	= 4. COAP/UDP/MQTT/TCP downlink =
1.1	769
2.1	770	== 4.1 MQTT (via MQTT.fx) ==
1.1	771
129.1	772
2.1	773	Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
1.1	774
2.1	775	1. Configure node MQTT connection (via MQTT.fx):
1.1	776
2.1	777	(% style="color:blue" %)AT command:
1.1	778
2.1	779	* (% style="color:#037691" %)AT+PRO=3,0 or 3,5 (%%)~/~/ hex format or json format
1.1	780
2.1	781	* (% style="color:#037691" %)AT+SUBTOPIC=User Defined
1.1	782
2.1	783	* (% style="color:#037691" %)AT+PUBTOPIC=User Defined
1.1	784
2.1	785	* (% style="color:#037691" %)AT+UNAME=<device name> or User Defined
1.1	786
2.1	787	* (% style="color:#037691" %)AT+PWD=<device name> or User Defined
1.1	788
2.1	789	* (% style="color:#037691" %)AT+SERVADDR=8.217.91.207,1883 (%%) ~/~/ to set MQTT server address and port
1.1	790
2.1	791	(% 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.
1.1	792
95.2	793	[[image:image-20240820112732-52.png]][[image:image-20240820112758-53.png]]
1.1	794
129.1	795
2.1	796	2. When the node uplink packets, we can observe the data in MQTT.fx.
1.1	797
95.2	798	[[image:image-20240820112813-54.png]]
1.1	799
129.1	800
2.1	801	3. The downlink command can be successfully sent only when the downlink port is open.
1.1	802
	803	The downlink port is opened for about 3 seconds after uplink packets are sent.
	804
2.1	805	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.
1.1	806
95.2	807	[[image:image-20240820112824-55.png]]
1.1	808
95.2	809	[[image:image-20240820112835-56.png]]
1.1	810
2.1	811	(% 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.
1.1	812
96.1	813
	814	== 4.2 UDP (via Thingseye) ==
	815
129.1	816
107.1	817	(% style="color:red" %)Note:(%%) The UDP service on the ThingsEye platform needs to be built by the user. (Description Link:[[UDP service building instructions>>http://www.ithingsboard.com/docs/user-guide/integrations/udp/]])
96.1	818
107.1	819	After the node is successfully connected to the platform, you need to select the corresponding node (you can refer to the node's IMEI to find it)
96.1	820
107.1	821	[[image:image-20240820141843-2.png\|\|height="546" width="821"]]
	822
	823	After clicking Show Node Details Page, (% style="color:blue" %)Select Properties ~-~-- select Shared Properties ~-~-- click Add Properties
	824
	825	[[image:image-20240820143316-3.png\|\|height="555" width="1170"]]
	826
	827	After clicking Add Shared Attribute, set the key to (% style="color:red" %)value(%%), and write the command that needs to be downlinked in the Downlink Command Input box
	828
	829	(% style="color:red" %)(Note: Downlinks can only be downlinked in string format, otherwise the node will not recognize the downlink command.)
	830
	831	[[image:image-20240820143820-4.png\|\|height="554" width="1168"]]
	832
	833	After the command is successfully added, the platform will send the command down on the node's next uplink.
	834
	835	[[image:image-20240820144913-6.png\|\|height="585" width="1232"]]
	836
	837	[[image:image-20240820145133-7.png\|\|height="582" width="1227"]]
	838
	839	Upon successful issuance, the platform automatically eliminates the attributes from the queue and waits for the next addition of new attributes
	840
	841	[[image:image-20240820145309-8.png]]
	842
	843
10.1	844	= 5. GPS positioning function =
	845
129.2	846	== 1. Turn on GPS function ==
10.1	847
129.2	848
10.1	849	(% class="wikigeneratedid" %)
129.2	850	AT+GPS=1 or 0 ~/~/ GPS function on or off
10.1	851
	852
129.2	853	== 2. Extend the time to turn on GNSS ==
10.1	854
	855
129.2	856	AT+GNSST=30 ~/~/ GPS search for positioning information for 30 seconds
10.1	857
	858
129.2	859	== 3. Get or set GPS positioning interval in units of hour ==
10.1	860
	861
129.2	862	AT+GTDC=24 ~/~/ The device will activate GPS positioning every 24 hours
1.1	863
	864
129.2	865	= 6. FAQ =
129.1	866
129.2	867	== 6.1 What is the usage of Multi Sampling and One Uplink? ==
	868
	869
1.1	870	The NB series has the feature for Multi Sampling and one uplink. See one of them
	871
2.1	872	[[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]]
1.1	873
	874	User can use this feature for below purpose:
	875
2.1	876	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.
	877	1. Give more sampling data points.
	878	1. Increase reliable in transmission. For example. If user set
	879	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)
	880	1. AT+NOUD=24* ~/~/ The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
	881	1. AT+TDC=7200* ~/~/ Uplink every 2 hours.
	882	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.
1.1	883
129.1	884
129.2	885	== 6.2 Why the uplink JSON format is not standard? ==
129.1	886
1.1	887
	888	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.
	889
	890	The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
	891
95.2	892	[[image:image-20240820112848-57.png]]
1.1	893
129.1	894
129.2	895	= 7. Trouble Shooting: =
1.1	896
129.2	897	== 7.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
1.1	898
129.1	899
1.1	900	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.
	901
2.1	902	If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
1.1	903
95.2	904	[[image:image-20240820112859-58.png]]
1.1	905
	906	If fail to attach network, it will shows signal 99. as below:
	907
95.2	908	[[image:image-20240820112908-59.png]]
1.1	909
2.1	910	(% class="lead" %)
1.1	911	When see this issue, below are the checklist:
	912
2.1	913	* 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.
	914	* 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]].
	915	* 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]].
	916	* Check if the device is attached to Carrier network but reject. (need to check with operator).
	917	* Check if the antenna is connected firmly.
1.1	918
2.1	919	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.
1.1	920
	921
129.2	922	== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.2 Why sometime the AT Command is slow in reponse?(%%) ==
1.1	923
129.1	924
1.1	925	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.
	926
95.2	927	[[image:image-20240820113015-60.png]]
1.1	928
129.1	929
129.2	930	== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.3 What is the Downlink Command by the -CB device?(%%) ==
1.1	931
2.1	932	(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
	933	=== UDP: ===
1.1	934
2.1	935	(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1.1	936	Its downlink command is the same as the AT command, but brackets are required.
	937	Example:
	938
	939	{AT+TDC=300}
	940
129.1	941
2.1	942	(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
	943	=== MQTT: ===
1.1	944
	945	Json：
	946
	947	The Json format in MQTT mode needs to be configured with all commands.
	948	If you have configurations that need to be changed, please change them in the template below.
	949	Template:
	950
	951	{
	952	"AT+SERVADDR":"119.91.62.30,1882",
	953	"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
	954	"AT+UNAME":"usenamedragino",
	955	"AT+PWD":"passworddragino",
	956	"AT+PUBTOPIC":"123",
	957	"AT+SUBTOPIC":"321",
	958	"AT+TDC":"7200",
	959	"AT+INTMOD":"0",
	960	"AT+APN":"NULL",
	961	"AT+5VT":"0",
	962	"AT+PRO":"3,5",
	963	"AT+TR":"900",
	964	"AT+NOUD":"0",
	965	"AT+CSQTIME":"5",
	966	"AT+DNSTIMER":"0",
	967	"AT+TLSMOD":"0,0",
	968	"AT+MQOS":"0",
	969	"AT+TEMPALARM1":"0",
	970	"AT+TEMPALARM2":"10",
	971	"AT+TEMPALARM3":"0"
	972	}
	973
	974	Hex：
	975
	976	MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
	977
	978	The supported commands are consistent with LoRaWAN's hex commands.
	979	Please refer to the following link to obtain the hex format:
	980
2.1	981	[[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/]]
1.1	982
108.2	983
129.2	984	== 7.4 What if the signal is good but the domain name resolution fails? ==
108.2	985
	986
	987	If the domain name resolution fails, first check whether the domain name is correct, users can use their own website domain name resolution tool to verify the domain name.
	988
112.1	989	[[image:image-20240827150705-6.png\|\|height="489" width="687"]]
	990
108.2	991	If the domain name is correct, but the domain name cannot be resolved, the user can turn off the domain name resolution function(AT+GDNS=1) and use the domain name communication directly.
	992
	993	* Set the DNS
	994
	995	(% style="color:blue" %)AT Command: AT+GDNS
	996
129.1	997	AT+GDNS=0 ~/~/ Default. Automatically resolves the domain name and uses the resolved IP to communicate.
108.2	998
129.1	999	AT+GDNS=1 ~/~/ Disabling Domain name resolution. Use the domain name directly to communicate.
108.2	1000
	1001	(% style="color:red" %)Note: For -CB products, with the exception of AT+PRO=2,5, all protocols and payload formats support direct domain communication.
	1002
	1003	Example:
	1004
112.1	1005	[[image:image-20240827150121-5.png\|\|height="476" width="680"]][[image:image-20240827145055-4.png\|\|height="484" width="678"]]
108.2	1006
	1007
129.2	1008	== 7.5 GPS debugging ==
108.2	1009
	1010
120.1	1011	Indoor GPS signal is very weak, outdoor positioning is generally recommended.
117.1	1012
127.1	1013	[[image:image-20240903104250-9.png\|\|height="275" width="614"]]
120.1	1014
	1015
127.1	1016	[[image:image-20240903104431-10.png\|\|height="291" width="621"]]
	1017
	1018
129.2	1019	=== 7.5.1 GPS commands ===
117.1	1020
	1021
114.1	1022	The following are three related AT commands that introduce GPS functions.
108.2	1023
114.1	1024	* Turn on/off GPS
108.2	1025
114.1	1026	(% style="color:blue" %)AT Command: (% style="color:#037691" %)AT+GPS
108.2	1027
114.1	1028	Ex1: AT+GPS=0 ~/~/ Turn off GPS
	1029
	1030	Ex2: AT+GPS=1 ~/~/ Turn on GPS
	1031
	1032	(% style="color:blue" %)Downlink command:(%%) (% style="color:#037691" %)0x11(%%)
	1033
	1034	Format: Command Code (0x11) followed by 1 byte.
	1035
	1036	Example: Downlink Payload: 11 01 ~/~/ AT+GPS=1
	1037
	1038	* Set GNSS open time
	1039
	1040	Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated.
	1041
	1042	(% style="color:blue" %)AT Command: (% style="color:#037691" %)AT+GNSST
	1043
	1044	Example: AT+GNSST=30 ~/~/ Set the GPS positioning time to 30 seconds
	1045
	1046	(% style="color:blue" %)Downlink command:(%%) (% style="color:#037691" %)0x10(%%)
	1047
	1048	Format: Command Code (0x10) followed by 2 bytes.
	1049
	1050	Example: Downlink Payload: 10 00 1E ~/~/ AT+GNSST=30
	1051
	1052	* Set GPS positioning interval
	1053
	1054	Feature: Set GPS positioning interval (unit: hour).
	1055
	1056	When GPS is enabled, the node automatically locates and uplinks each time it passes GTDC time after activation.
	1057
	1058	(% style="color:blue" %)AT Command: (% style="color:#037691" %)AT+GTDC
	1059
	1060	Example: AT+GTDC=24 ~/~/ Set the GPS positioning interval to 24h.
	1061
	1062	(% style="color:blue" %)Downlink command:(%%) (% style="color:#037691" %)0x12(%%)
	1063
	1064	Format: Command Code (0x12) followed by 3 bytes.
	1065
	1066	Example: 24 hours: 24(D)=0x18(H)
	1067
129.1	1068	Downlink Payload: 12 00 00 18 ~/~/ AT+GTDC=24
114.1	1069
	1070
129.2	1071	=== 7.5.2 GPS workflow ===
114.1	1072
	1073
117.1	1074	The whole working process after the GPS function is enabled((% style="color:#037691" %)AT+GPS=1(%%)) is as follows:
114.1	1075
117.1	1076	~1. When activate the node, the node will turn on the GNSS, if the GPS signal is good, the node will print and upload the position information with the first data packet immediately.
114.1	1077
117.1	1078	If the signal is not good, it may take the whole (% style="color:#037691" %)GNSST(%%) time but still can not search the latitude and longitude information, at this time the node uploads the latitude and longitude all to 0.
114.1	1079
117.1	1080	So if there is a failure of positioning, the user can extend the (% style="color:#037691" %)GNSST(%%) time appropriately.
114.1	1081
117.1	1082	2. Each TDC time node is not repositioned and the positioning interval is determined by the AT+GTDC time.
114.1	1083
117.1	1084	The latitude and longitude payload uplinked at each TDC time is the GPS positioning information from the previous (% style="color:#037691" %)GTDC(%%) time.
114.1	1085
117.1	1086	Only when the node is activated or every (% style="color:#037691" %)GTDC(%%) time is reached, the node turns on the GNSS and we can observe the GPS search information through the serial assistant or Bluetooth tool.
	1087
	1088
129.2	1089	=== 7.5.3 GPS debugging methods ===
117.1	1090
	1091
128.1	1092	In summary, we can deduce the methods of debugging GPS:
117.1	1093
127.1	1094	* Check whether the GPS function is enabled.
	1095
	1096	[[image:image-20240903102327-5.png\|\|height="271" width="529"]]
	1097
117.1	1098	* Check whether the GPS antenna is loose.
	1099
	1100	If the GPS antenna is loose, the GPS signal is weak, and the positioning fails.
	1101
	1102	[[image:image-20240903094214-1.png\|\|height="340" width="461"]]
	1103
	1104	* Use the AT+GNSST command to extend the positioning time.
	1105
	1106	The default AT+GNSST=30, that is, the default positioning time is 30 seconds.
	1107
	1108	If the location fails, users can extend the location time.
	1109
127.1	1110	[[image:image-20240903102641-8.png\|\|height="303" width="600"]]
117.1	1111
	1112
	1113
	1114
108.2	1115

Wiki source code of General Manual for -CB , -CS models

Applications

Navigation