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

Version 134.1 by Mengting Qiu on 2024/10/18 15:41

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

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

Applications

Navigation