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

Version 13.1 by David Huang on 2024/08/17 09:23

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
3.1	11	This configure instruction is for Dragino NB-IoT models with -CB or -CS suffix, for example DDS75-CB. These models use the same NB-IoT Module [[BG95-M2>>https://www.dropbox.com/sh/3ilyaswz4odgaru/AADR86cAgL9UGlmLuEH-UZgla?st=x1ry6v5j&dl=0]] and has the same software structure. The have the same configure instruction to different IoT servers. Use can follow the instruction here to see how to configure to connect to those servers.
1.1	12
3.1	13
2.1	14	= 2. Attach Network =
1.1	15
2.1	16	== 2.1 General Configure to attach network ==
1.1	17
3.1	18	To attache end nodes to NB-IoT or LTE-M Network, You need to:
1.1	19
3.1	20	1. Get a NB-IoT or LTE-M SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
2.1	21	1. Power Off End Node ( See below for the power off/on position)
	22	1. Insert the SIM card to Sensor. ( See below for direction)
	23	1. Power On End Node
	24	1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>), example AT+APN=iot.1nce.net
1.1	25
7.1	26	[[image:image-20240602220856-1.png]]
1.1	27
	28
7.1	29	放一张如何插卡图片。
	30
	31
3.1	32	After doing above, the end nodes should be able to attach to NB-IoT network .
1.1	33
3.1	34	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	35
5.1	36	~-~-(% style="color:blue" %) CAT-NB2: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B28/B66/B71/B85 (%%).
3.1	37
5.1	38	~-~-(% style="color:blue" %) CAT-M1: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85 (%%).
3.1	39
4.1	40	Make sure you use a the NB-IoT or LTE-M SIM card.
3.1	41
4.1	42	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1134px" %)
	43	\|(% 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
	44	\|(% style="width:117px" %)[[1NCE>>https://1nce.com]]\|(% style="width:151px" %)iot.1nce.net\|(% style="width:406px" %)(((
2.1	45	[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]
1.1	46
4.1	47	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
	48	)))\|(% style="width:351px" %)(((
	49	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.
	50	)))\|(% style="width:120px" %)UK: Band20
	51	\|(% style="width:117px" %)China Mobile\|(% style="width:151px" %)No need configure\|(% style="width:406px" %)China Mainland, HongKong\|(% style="width:351px" %) \|(% style="width:120px" %)
	52	\|(% style="width:117px" %)China Telecom\|(% style="width:151px" %)ctnb\|(% style="width:406px" %)China Mainland\|(% style="width:351px" %) \|(% style="width:120px" %)
1.1	53
2.1	54	== 2.2 Speed Up Network Attach time ==
1.1	55
4.1	56	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	57
9.1	58	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	59
4.1	60	Attache to 1NCE card for Australia use:
1.1	61
4.1	62	* AT+COPS=1,2,"50501",8
	63	* AT+QCFG="band",0,0x8000000,0x8000000,1
1.1	64
4.1	65	After connection is successful, user can use (% style="color:#037691" %)AT+QENG="servingcell"(%%) to check which band is actually in used.
	66
	67	AT+QENG="servingcell"
	68	+QENG: "servingcell","NOCONN","eMTC","FD
	69	D",505,01,90D2C0B,258,9410,28,5,5,901A,-112,-17,-80,10,27
	70
	71
2.1	72	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	73
12.1	74	=== 1.Configure Frequency Band ===
5.1	75
9.1	76	AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
5.1	77
9.1	78	<GSM_bandval>:
	79
	80	0 No change
	81	0x1 EGSM900
	82	0x2 DCS1800
	83	0x4 GSM850
	84	0x8 PCS1900
	85	0xF All of the supported bands above
	86
	87	<eMTC_bandval>:
	88
	89	0 No change
	90	0x1 LTE B1
	91	0x2 LTE B2
	92	0x4 LTE B3
	93	0x8 LTE B4
	94	0x10 LTE B5
	95	0x80 LTE B8
	96	0x800 LTE B12
	97	0x1000 LTE B13
	98	0x20000 LTE B18
	99	0x40000 LTE B19
	100	0x80000 LTE B20
	101	0x1000000 LTE B25
	102	0x2000000 LTE B26
	103	0x4000000 LTE B27
	104	0x8000000 LTE B28
	105	0x40000000 LTE B31
	106	0x20000000000000000 LTE B66
	107	0x800000000000000000 LTE B72
	108	0x1000000000000000000 LTE B73
	109	0x1000000000000000000000 LTE B85
	110
	111	<NB-IoT_bandval>:
	112
	113	0 No change
	114	0x1 LTE B1
	115	0x2 LTE B2
	116	0x4 LTE B3
	117	0x8 LTE B4
	118	0x10 LTE B5
	119	0x80 LTE B8
	120	0x800 LTE B12
	121	0x1000 LTE B13
	122	0x20000 LTE B18
	123	0x40000 LTE B19
	124	0x80000 LTE B20
	125	0x1000000 LTE B25
	126	0x8000000 LTE B28
	127	0x40000000 LTE B31
	128	0x20000000000000000 LTE B66
	129
	130	0x400000000000000000 LTE B71
	131	0x800000000000000000 LTE B72
	132	0x1000000000000000000 LTE B73
	133	0x1000000000000000000000 LTE B85
	134
	135	For example, setting the LTE-M network frequency band to 3.
	136
	137	AT+QCFG="band",0xF,0x4,0,1
	138
	139	When searching for all bands, the value of this command is set to:
	140
	141	AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
	142
	143
12.1	144	=== 2.Configure search network sequence ===
9.1	145
	146	AT+QCFG="nwscanseq",<scanseq>,1
	147
	148	<scanseq>:
	149
	150	00 Automatic (eMTC → NB-IoT → GSM)
	151	01 GSM
	152	02 eMTC
	153	03 NB-IoT
	154
	155	AT+QCFG="nwscanseq",02,1 ~/~/Priority search for eMTC
	156
12.1	157	=== 3.Configure Network Category to be Searched for under LTE RAT ===
9.1	158
	159	AT+QCFG="iotopmode",mode,1
	160
	161	0 eMTC
	162	1 NB-IoT
	163	2 eMTC and NB-IoT
	164
13.1	165	=== 4.AT command to set frequency band and network category ===
9.1	166
13.1	167	AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f ~/~/<eMTC_bandval>,<NB-IoT_bandval>
	168
	169	AT+IOTMOD=0 ~/~/ 0 eMTC 1 NB-IoT 2 eMTC and NB-IoT
	170
	171	Example :
	172
	173	Taking the use of 1nce cards in the United States as an example.
	174
	175	AT+APN=iot.1nce.net ~/~/set APN
	176
	177	AT+QBAND=0x100180A,0 ~/~/ eMTC ：Set frequency band B2,B4,B12,B13,B25 NB-IoT：No change
	178
	179	AT+IOTMOD=0 ~/~/ Set eMTC Network
	180
	181	Setting the above commands in the United States will greatly reduce the network search time of the NB module.
	182
	183
2.1	184	= 3. Configure to connect to different servers =
1.1	185
2.1	186	== 3.1 General UDP Connection ==
1.1	187
2.1	188	The NB-IoT Sensor can send packet to server use UDP protocol.
1.1	189
2.1	190	=== 3.1.1 Simulate UDP Connection by PC tool ===
1.1	191
2.1	192	We can use PC tool to simulate UDP connection to make sure server works ok.
1.1	193
2.1	194	[[image:image-20230802112413-1.png\|\|height="468" width="1024"]]
1.1	195
2.1	196	=== 3.1.2 Configure NB-IoT Sensor ===
1.1	197
2.1	198	==== 3.1.2.1 AT Commands ====
1.1	199
2.1	200	(% style="color:blue" %)AT Commands:
1.1	201
3.1	202	* (% style="color:#037691" %)AT+PRO=2,0 (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload
1.1	203
3.1	204	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5601 (%%) ~/~/ Set UDP server address and port
1.1	205
2.1	206	[[image:image-20230802112413-2.png]]
1.1	207
2.1	208	==== 3.1.2.2 Uplink Example ====
1.1	209
2.1	210	[[image:image-20230802112413-3.png]]
1.1	211
8.1	212	== 3.2 General COAP Connection ==
	213
	214	The NB-IoT Sensor can send packet to server use COAP protocol.
	215
	216	Below are the commands.
	217
	218	(% style="color:blue" %)AT Commands:
	219
	220	* (% style="color:#037691" %)AT+PRO=1,0 (%%) ~/~/ Set to use COAP protocol to uplink, Payload Type select Hex payload.
	221
	222	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5683 (%%) ~/~/ Set COAP server address and port
	223
	224	* (% style="color:#037691" %)AT+URI1=11,"I" (%%) ~/~/ Configure CoAP Message Options
9.1	225	* (% style="color:#037691" %)AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1" (%%) ~/~/ Configure CoAP Message Options
8.1	226
	227	=== 3.2.1 Uplink Example ===
	228
	229
	230
2.1	231	== 3.2 General MQTT Connection ==
1.1	232
2.1	233	The NB-IoT Sensor can send packet to server use MQTT protocol.
1.1	234
2.1	235	Below are the commands.
1.1	236
2.1	237	(% style="color:blue" %)AT Commands:
1.1	238
3.1	239	* (% style="color:#037691" %)AT+PRO=3,0 (%%) ~/~/ Set to use MQTT protocol to uplink, Payload Type select Hex payload.
1.1	240
3.1	241	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,1883 (%%) ~/~/ Set MQTT server address and port
1.1	242
3.1	243	* (% style="color:#037691" %)AT+CLIENT=CLIENT (%%) ~/~/ Set up the CLIENT of MQTT
1.1	244
3.1	245	* (% style="color:#037691" %)AT+UNAME=UNAME (%%) ~/~/ Set the username of MQTT
1.1	246
3.1	247	* (% style="color:#037691" %)AT+PWD=PWD (%%) ~/~/ Set the password of MQTT
1.1	248
3.1	249	* (% style="color:#037691" %)AT+PUBTOPIC=NSE01_PUB (%%) ~/~/ Set the sending topic of MQTT
1.1	250
3.1	251	* (% style="color:#037691" %)AT+SUBTOPIC=NSE01_SUB (%%) ~/~/ Set the subscription topic of MQTT
1.1	252
2.1	253	[[image:image-20230802112413-4.png]]
1.1	254
2.1	255	[[image:image-20230802112413-5.png\|\|height="530" width="987"]]
1.1	256
2.1	257	(% 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	258
2.1	259	== 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
1.1	260
2.1	261	=== 3.3.1 Get MQTT Credentials ===
1.1	262
2.1	263	[[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	264
2.1	265	[[image:image-20230802112413-6.png\|\|height="336" width="925"]]
1.1	266
2.1	267	[[image:image-20230802112413-7.png]]
1.1	268
2.1	269	=== 3.3.2 Simulate with MQTT.fx ===
1.1	270
2.1	271	==== 3.3.2.1 Establish MQTT Connection ====
1.1	272
2.1	273	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	274
2.1	275	[[image:image-20230802112413-8.png]]
1.1	276
2.1	277	* (% style="color:#037691" %)Broker Address:(%%) mqtt3.thingspeak.com
1.1	278
2.1	279	* (% style="color:#037691" %)Broker Port:(%%) 1883
1.1	280
2.1	281	* (% style="color:#037691" %)Client ID:(%%) <Your ThingSpeak MQTT ClientID>
1.1	282
2.1	283	* (% style="color:#037691" %)User Name:(%%) <Your ThingSpeak MQTT User Name>
1.1	284
2.1	285	* (% style="color:#037691" %)Password:(%%) <Your ThingSpeak MQTT Password>
1.1	286
2.1	287	==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
1.1	288
2.1	289	[[image:image-20230802112413-9.png]]
1.1	290
2.1	291	[[image:image-20230802112413-10.png]]
1.1	292
2.1	293	(% style="color:blue" %)In MQTT.fx, we can publish below info:
1.1	294
2.1	295	* (% style="color:#037691" %)Topic:(%%) channels/YOUR_CHANNEL_ID/publish
1.1	296
2.1	297	* (% style="color:#037691" %)Payload:(%%) field1=63&field2=67&status=MQTTPUBLISH
1.1	298
2.1	299	Where 63 and 67 are the value to be published to field1 & field2.
1.1	300
2.1	301	(% style="color:blue" %)Result:
1.1	302
2.1	303	[[image:image-20230802112413-11.png\|\|height="539" width="901"]]
1.1	304
2.1	305	=== 3.3.3 Configure NB-IoT Sensor for connection ===
1.1	306
2.1	307	==== 3.3.3.1 AT Commands: ====
1.1	308
2.1	309	In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
1.1	310
2.1	311	* (% style="color:blue" %)AT+PRO=3,1 (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
1.1	312
2.1	313	* (% style="color:blue" %)AT+CLIENT=<Your ThingSpeak MQTT ClientID>
1.1	314
2.1	315	* (% style="color:blue" %)AT+UNAME=<Your ThingSpeak MQTT User Name>
1.1	316
2.1	317	* (% style="color:blue" %)AT+PWD=<Your ThingSpeak MQTT Password>
1.1	318
2.1	319	* (% style="color:blue" %)AT+PUBTOPIC=<YOUR_CHANNEL_ID>
1.1	320
2.1	321	* (% style="color:blue" %)AT+SUBTOPIC=<YOUR_CHANNEL_ID>
1.1	322
2.1	323	==== 3.3.3.2 Uplink Examples ====
1.1	324
2.1	325	[[image:image-20230816201942-1.png]]
1.1	326
2.1	327	For SE01-NB
1.1	328
2.1	329	For DDS20-NB
1.1	330
2.1	331	For DDS45-NB
1.1	332
2.1	333	For DDS75-NB
1.1	334
2.1	335	For NMDS120-NB
1.1	336
2.1	337	For SPH01-NB
1.1	338
2.1	339	For NLM01-NB
1.1	340
2.1	341	For NMDS200-NB
1.1	342
2.1	343	For CPN01-NB
1.1	344
2.1	345	For DS03A-NB
1.1	346
2.1	347	For SN50V3-NB
1.1	348
2.1	349	==== 3.3.3.3 Map fields to sensor value ====
1.1	350
2.1	351	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	352
2.1	353	[[image:image-20230802112413-12.png\|\|height="504" width="1011"]]
1.1	354
2.1	355	[[image:image-20230802112413-13.png\|\|height="331" width="978"]]
1.1	356
2.1	357	Below is the NB-IoT Product Table show the mapping.
1.1	358
2.1	359	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
	360	\|(% style="background-color:#4f81bd; width:143px" %) \|(% style="background-color:#4f81bd; color:white; width:103px" %)Field1\|(% style="background-color:#4f81bd; color:white; width:102px" %)Field2\|(% style="background-color:#4f81bd; color:white; width:157px" %)Field3\|(% style="background-color:#4f81bd; color:white; width:154px" %)Field4\|(% style="background-color:#4f81bd; color:white; width:153px" %)Field5\|(% style="background-color:#4f81bd; color:white; width:151px" %)Field6\|(% style="background-color:#4f81bd; color:white; width:160px" %)Field7\|(% style="background-color:#4f81bd; color:white; width:152px" %)Field8\|(% style="background-color:#4f81bd; color:white; width:67px" %)Field9\|(% style="background-color:#4f81bd; color:white; width:69px" %)Field10
3.1	361	\|(% style="background-color:#4f81bd; color:white; width:143px" %)S31x-NB\|(% style="width:103px" %)Temperature \|(% style="width:102px" %)Humidity\|(% style="width:157px" %)Battery\|(% style="width:154px" %)RSSI\|(% style="width:153px" %) \|(% style="width:151px" %) \|(% style="width:160px" %) \|(% style="width:152px" %) \|(% style="width:67px" %) \|(% style="width:69px" %)
	362	\|(% style="background-color:#4f81bd; color:white; width:143px" %)SE01-NB\|(% style="width:103px" %)Temperature \|(% style="width:102px" %)Humidity\|(% style="width:157px" %)conduct\|(% style="width:154px" %)dielectric_constant\|(% style="width:153px" %)Battery\|(% style="width:151px" %)RSSI\|(% style="width:160px" %) \|(% style="width:152px" %) \|(% style="width:67px" %) \|(% style="width:69px" %)
	363	\|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS20-NB\|(% style="width:103px" %)distance\|(% style="width:102px" %)Battery\|(% style="width:157px" %)RSSI\|(% style="width:154px" %) \|(% style="width:153px" %) \|(% style="width:151px" %) \|(% style="width:160px" %) \|(% style="width:152px" %) \|(% style="width:67px" %) \|(% style="width:69px" %)
	364	\|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS45-NB\|(% style="width:103px" %)distance\|(% style="width:102px" %)Battery\|(% style="width:157px" %)RSSI\|(% style="width:154px" %) \|(% style="width:153px" %) \|(% style="width:151px" %) \|(% style="width:160px" %) \|(% style="width:152px" %) \|(% style="width:67px" %) \|(% style="width:69px" %)
	365	\|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS75-NB\|(% style="width:103px" %)distance\|(% style="width:102px" %)Battery\|(% style="width:157px" %)RSSI\|(% style="width:154px" %) \|(% style="width:153px" %) \|(% style="width:151px" %) \|(% style="width:160px" %) \|(% style="width:152px" %) \|(% style="width:67px" %) \|(% style="width:69px" %)
	366	\|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS120-NB\|(% style="width:103px" %)distance\|(% style="width:102px" %)Battery\|(% style="width:157px" %)RSSI\|(% style="width:154px" %) \|(% style="width:153px" %) \|(% style="width:151px" %) \|(% style="width:160px" %) \|(% style="width:152px" %) \|(% style="width:67px" %) \|(% style="width:69px" %)
	367	\|(% rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SPH01-NB\|(% style="width:103px" %)ph\|(% style="width:102px" %)Temperature\|(% style="width:157px" %)Battery\|(% style="width:154px" %)RSSI\|(% style="width:153px" %) \|(% style="width:151px" %) \|(% style="width:160px" %) \|(% style="width:152px" %) \|(% style="width:67px" %) \|(% colspan="1" rowspan="1" style="width:69px" %)
	368	\|(% style="background-color:#4f81bd; color:white; width:143px" %)NLM01-NB\|(% style="width:103px" %)Humidity\|(% style="width:102px" %)Temperature\|(% style="width:157px" %)Battery\|(% style="width:154px" %)RSSI\|(% style="width:153px" %) \|(% style="width:151px" %) \|(% style="width:160px" %) \|(% style="width:152px" %) \|(% style="width:67px" %) \|(% style="width:69px" %)
	369	\|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS200-NB\|(% style="width:103px" %)distance1\|(% style="width:102px" %)distance2\|(% style="width:157px" %)Battery\|(% style="width:154px" %)RSSI\|(% style="width:153px" %) \|(% style="width:151px" %) \|(% style="width:160px" %) \|(% style="width:152px" %) \|(% style="width:67px" %) \|(% style="width:69px" %)
	370	\|(% style="background-color:#4f81bd; color:white; width:143px" %)CPN01-NB\|(% style="width:103px" %)alarm\|(% style="width:102px" %)count\|(% style="width:157px" %)door open duration\|(% style="width:154px" %)calc flag\|(% style="width:153px" %)Battery\|(% style="width:151px" %)RSSI\|(% style="width:160px" %) \|(% style="width:152px" %) \|(% style="width:67px" %) \|(% style="width:69px" %)
2.1	371	\|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)DS03A-NB\|(% colspan="1" rowspan="1" style="width:103px" %)level\|(% colspan="1" rowspan="1" style="width:102px" %)alarm\|(% colspan="1" rowspan="1" style="width:157px" %)pb14door open num\|(% colspan="1" rowspan="1" style="width:154px" %)pb14 last open time\|(% colspan="1" rowspan="1" style="width:153px" %)pb15 level status\|(% colspan="1" rowspan="1" style="width:151px" %)pb15 alarm status\|(% colspan="1" rowspan="1" style="width:160px" %)pb15 door open num\|(% colspan="1" rowspan="1" style="width:152px" %)pb15 last open time\|(% colspan="1" rowspan="1" style="width:67px" %)Battery\|(% colspan="1" rowspan="1" style="width:69px" %)RSSI
3.1	372	\|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod1\|(% colspan="1" rowspan="1" style="width:103px" %)mod\|(% colspan="1" rowspan="1" style="width:102px" %)Battery\|(% colspan="1" rowspan="1" style="width:157px" %)RSSI\|(% colspan="1" rowspan="1" style="width:154px" %)DS18B20 Temp\|(% colspan="1" rowspan="1" style="width:153px" %)exit_state/input PA4\|(% colspan="1" rowspan="1" style="width:151px" %)adc0\|(% colspan="1" rowspan="1" style="width:160px" %)Temperature \|(% colspan="1" rowspan="1" style="width:152px" %)Humidity\|(% colspan="1" rowspan="1" style="width:67px" %) \|(% colspan="1" rowspan="1" style="width:69px" %)
	373	\|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod2\|(% colspan="1" style="width:103px" %)mod\|(% colspan="1" style="width:102px" %)Battery\|(% colspan="1" style="width:157px" %)RSSI\|(% colspan="1" style="width:154px" %)DS18B20 Temp\|(% colspan="1" style="width:153px" %)exit_state/input PA4\|(% colspan="1" style="width:151px" %)adc0\|(% colspan="1" style="width:160px" %)distance\|(% colspan="1" style="width:152px" %) \|(% colspan="1" style="width:67px" %) \|(% colspan="1" style="width:69px" %)
	374	\|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod3\|(% colspan="1" style="width:103px" %)mod\|(% colspan="1" style="width:102px" %)Battery\|(% colspan="1" style="width:157px" %)RSSI\|(% colspan="1" style="width:154px" %)adc0\|(% colspan="1" style="width:153px" %)exit_state/input PA4\|(% colspan="1" style="width:151px" %)adc1\|(% colspan="1" style="width:160px" %)Temperature\|(% colspan="1" style="width:152px" %)Humidity\|(% colspan="1" style="width:67px" %)adc4\|(% colspan="1" style="width:69px" %)
	375	\|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod4\|(% colspan="1" style="width:103px" %)mod\|(% colspan="1" style="width:102px" %)Battery\|(% colspan="1" style="width:157px" %)RSSI\|(% colspan="1" style="width:154px" %)DS18B20 Temp\|(% colspan="1" style="width:153px" %)adc0\|(% colspan="1" style="width:151px" %)exit_state/input PA4\|(% colspan="1" style="width:160px" %)DS18B20 Temp2\|(% colspan="1" style="width:152px" %)DS18B20 Temp3\|(% colspan="1" style="width:67px" %) \|(% colspan="1" style="width:69px" %)
	376	\|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod5\|(% colspan="1" style="width:103px" %)mod\|(% colspan="1" style="width:102px" %)Battery\|(% colspan="1" style="width:157px" %)RSSI\|(% colspan="1" style="width:154px" %)DS18B20 Temp\|(% colspan="1" style="width:153px" %)adc0\|(% colspan="1" style="width:151px" %)exit_state/input PA4\|(% colspan="1" style="width:160px" %)Weight\|(% colspan="1" style="width:152px" %) \|(% colspan="1" style="width:67px" %) \|(% colspan="1" style="width:69px" %)
	377	\|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod6\|(% colspan="1" style="width:103px" %)mod\|(% colspan="1" style="width:102px" %)Battery\|(% colspan="1" style="width:157px" %)RSSI\|(% colspan="1" style="width:154px" %)count\|(% colspan="1" style="width:153px" %) \|(% colspan="1" style="width:151px" %) \|(% colspan="1" style="width:160px" %) \|(% colspan="1" style="width:152px" %) \|(% colspan="1" style="width:67px" %) \|(% colspan="1" style="width:69px" %)
1.1	378
2.1	379	== 3.4 [[Datacake>>https://datacake.co/]] ==
1.1	380
2.1	381	(% class="wikigeneratedid" %)
	382	Dragino NB-IoT sensors has its template in [[Datacake>>https://datacake.co/]] Platform. There are two version for NB Sensor,
1.1	383
2.1	384	(% class="wikigeneratedid" %)
	385	As example for S31B-NB. there are two versions: S31B-NB-1D and S31B-NB-GE.
1.1	386
2.1	387	* (% style="color:blue" %)S31B-NB-1D(%%): This version have pre-configure DataCake connection. User just need to Power on this device, it will auto connect send data to DataCake Server.
1.1	388
2.1	389	* (% style="color:blue" %)S31B-NB-GE(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction.
1.1	390
2.1	391	=== 3.4.1 For device Already has template ===
1.1	392
2.1	393	==== 3.4.1.1 Create Device ====
1.1	394
2.1	395	(% style="color:blue" %)Add Device(%%) in DataCake.
1.1	396
2.1	397	[[image:image-20230808162301-1.png\|\|height="453" width="952"]]
1.1	398
2.1	399	[[image:image-20230808162342-2.png\|\|height="541" width="952"]]
1.1	400
2.1	401	(% style="color:blue" %)Choose the correct model(%%) from template.
1.1	402
2.1	403	[[image:image-20230808162421-3.png]]
1.1	404
3.1	405	(% 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	406
2.1	407	[[image:image-20230808163612-7.png\|\|height="549" width="952"]]
1.1	408
2.1	409	[[image:image-20230808163035-5.png]]
1.1	410
2.1	411	[[image:image-20230808163049-6.png\|\|height="544" width="926"]]
1.1	412
2.1	413	=== 3.4.2 For Device already registered in DataCake before shipped ===
1.1	414
2.1	415	==== 3.4.2.1 Scan QR Code to get the device info ====
1.1	416
	417	Users can use their phones or computers to scan QR codes to obtain device data information.
	418
2.1	419	[[image:image-20230808170051-8.png\|\|height="255" width="259"]]
1.1	420
2.1	421	[[image:image-20230808170548-9.png]]
1.1	422
2.1	423	==== 3.4.2.2 Claim Device to User Account ====
1.1	424
	425	By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
	426
2.1	427	=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
1.1	428
2.1	429	Step1: Add a device
1.1	430
2.1	431	[[image:image-20240129170024-1.png\|\|height="330" width="900"]]
1.1	432
2.1	433	Step2: Choose your device type,please select dragino NB-IOT device
1.1	434
2.1	435	[[image:image-20240129170216-2.png\|\|height="534" width="643"]]
1.1	436
2.1	437	Step3: Choose to create a new device
1.1	438
2.1	439	[[image:image-20240129170539-3.png\|\|height="459" width="646"]]
1.1	440
2.1	441	Step4: Fill in the device ID of your NB device
1.1	442
2.1	443	[[image:image-20240202111546-1.png\|\|height="378" width="651"]]
1.1	444
2.1	445	Step5: Please select your device plan according to your needs and complete the creation of the device
1.1	446
2.1	447	[[image:image-20240129171236-6.png\|\|height="450" width="648"]]
1.1	448
2.1	449	Step6: Please add the decoder at the payload decoder of the device configuration.
1.1	450
2.1	451	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	452
2.1	453	[[image:image-20240129172056-7.png\|\|height="457" width="816"]]
1.1	454
2.1	455	[[image:image-20240129173116-9.png\|\|height="499" width="814"]]
1.1	456
2.1	457	Step7: Add the output of the decoder as a field
1.1	458
2.1	459	[[image:image-20240129173541-10.png\|\|height="592" width="968"]]
1.1	460
2.1	461	Step8: Customize the dashboard and use fields as parameters of the dashboard
1.1	462
2.1	463	[[image:image-20240129174518-11.png\|\|height="147" width="1042"]]
1.1	464
2.1	465	[[image:image-20240129174657-12.png\|\|height="538" width="916"]]
1.1	466
2.1	467	[[image:image-20240129174840-13.png\|\|height="536" width="750"]]
1.1	468
2.1	469	=== 3.4.4 For device have not configured to connect to DataCake ===
1.1	470
2.1	471	(% class="lead" %)
1.1	472	Use AT command for connecting to DataCake
	473
2.1	474	(% style="color:blue" %)AT+PRO=2,0
1.1	475
2.1	476	(% style="color:blue" %)AT+SERVADDR=67.207.76.90,4445
1.1	477
2.1	478	== 3.5 Node-Red (via MQTT) ==
1.1	479
2.1	480	=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
1.1	481
	482	Take S31-NB UDP protocol as an example.
	483
	484	Dragino provides input flow examples for the sensors.
	485
	486	User can download the required JSON file through Dragino Node-RED input flow template.
	487
2.1	488	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	489
	490	We can directly import the template.
	491
	492	The templates for S31-NB and NB95S31B are the same.
	493
2.1	494	[[image:image-20230809173127-4.png]]
1.1	495
	496	Please select the NB95S31B template.
	497
2.1	498	[[image:image-20230809173310-5.png\|\|height="558" width="926"]]
1.1	499
2.1	500	[[image:image-20230809173438-6.png]]
1.1	501
2.1	502	[[image:image-20230809173800-7.png]]
1.1	503
	504	Successfully imported template.
	505
2.1	506	[[image:image-20230809173835-8.png\|\|height="515" width="860"]]
1.1	507
	508	Users can set UDP port.
	509
2.1	510	[[image:image-20230809174053-9.png]]
1.1	511
2.1	512	=== 3.5.2 Simulate Connection ===
1.1	513
	514	We have completed the configuration of UDP. We can try sending packets to node red.
	515
2.1	516	[[image:image-20230810083934-1.png]]
1.1	517
2.1	518	[[image:image-20230810084048-2.png\|\|height="535" width="1052"]]
1.1	519
2.1	520	=== 3.5.3 Configure NB-IoT Sensors ===
1.1	521
2.1	522	* (% style="color:#037691" %)AT+PRO=3,0 or 3,5 (%%) ~/~/ hex format or json format
	523	* (% style="color:#037691" %)AT+SUBTOPIC=<device name>or User Defined
	524	* (% style="color:#037691" %)AT+PUBTOPIC=<device name>or User Defined
	525	* (% style="color:#037691" %)AT+CLIENT=<device name> or User Defined
	526	* (% style="color:#037691" %)AT+UNAME=<device name> or User Defined
	527	* (% style="color:#037691" %)AT+PWD=“Your device token”
1.1	528
2.1	529	== 3.6 ThingsBoard.Cloud (via MQTT) ==
1.1	530
2.1	531	=== 3.6.1 Configure ThingsBoard ===
1.1	532
2.1	533	==== 3.6.1.1 Create Device ====
1.1	534
2.1	535	Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
1.1	536
2.1	537	[[image:image-20230802112413-32.png\|\|height="583" width="1066"]]
1.1	538
2.1	539	==== 3.6.1.2 Create Uplink & Downlink Converter ====
1.1	540
2.1	541	(% style="color:blue" %)Uplink Converter
1.1	542
2.1	543	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	544
2.1	545	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	546
2.1	547	[[image:image-20230802112413-33.png\|\|height="597" width="1061"]]
1.1	548
2.1	549	(% style="color:blue" %)Downlink Converter
1.1	550
2.1	551	The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
1.1	552
2.1	553	[[image:image-20230802112413-34.png\|\|height="598" width="1063"]]
1.1	554
2.1	555	(% 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	556
2.1	557	==== 3.6.1.3 MQTT Integration Setup ====
1.1	558
2.1	559	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	560
2.1	561	[[image:image-20230802112413-35.png\|\|height="597" width="1062"]]
1.1	562
2.1	563	* The next steps is to add the recently created uplink and downlink converters;
1.1	564
2.1	565	[[image:image-20230802112413-36.png\|\|height="598" width="1062"]]
1.1	566
2.1	567	[[image:image-20230802112413-37.png\|\|height="598" width="1064"]]
1.1	568
2.1	569	(% style="color:blue" %)Add a topic filter:
1.1	570
	571	Consistent with the theme of the node setting.
	572
2.1	573	You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
1.1	574
2.1	575	[[image:image-20230802112413-38.png\|\|height="598" width="1064"]]
1.1	576
2.1	577	=== 3.6.2 Simulate with MQTT.fx ===
1.1	578
2.1	579	[[image:image-20230802112413-39.png]]
1.1	580
2.1	581	[[image:image-20230802112413-40.png\|\|height="525" width="980"]]
1.1	582
2.1	583	=== 3.6.3 Configure NB-IoT Sensor ===
1.1	584
2.1	585	(% style="color:blue" %)AT Commands
1.1	586
3.1	587	* (% style="color:#037691" %)AT+PRO=3,3 (%%) ~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
1.1	588
2.1	589	* (% style="color:#037691" %)AT+SUBTOPIC=<device name>
1.1	590
2.1	591	* (% style="color:#037691" %)AT+PUBTOPIC=<device name>
1.1	592
2.1	593	* (% style="color:#037691" %)AT+CLIENT=<device name> or User Defined
1.1	594
2.1	595	* (% style="color:#037691" %)AT+UNAME=<device name> or User Defined
1.1	596
2.1	597	* (% style="color:#037691" %)AT+PWD=<device name> or User Defined
1.1	598
2.1	599	Test Uplink by click the button for 1 second
1.1	600
2.1	601	[[image:image-20230802112413-41.png\|\|height="496" width="828"]]
1.1	602
2.1	603	[[image:image-20230802112413-42.png]]
1.1	604
2.1	605	[[image:image-20230802112413-43.png\|\|height="407" width="825"]]
1.1	606
2.1	607	== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
1.1	608
2.1	609	=== 3.7.1 Create device & Get Credentials ===
1.1	610
2.1	611	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	612
2.1	613	[[image:image-20230802112413-44.png]]
1.1	614
2.1	615	[[image:image-20230802112413-45.png]]
1.1	616
2.1	617	Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
1.1	618
2.1	619	[[image:image-20230802112413-46.png]]
1.1	620
2.1	621	The device needs to enable the TLS mode and set the (% style="color:blue" %)AT+TLSMOD=1,0(%%) command.
1.1	622
2.1	623	(% style="color:blue" %)On the Connection Profile window, set the following information:
1.1	624
2.1	625	* (% style="color:#037691" %)Profile Name: “Any name”
1.1	626
2.1	627	* (% style="color:#037691" %)Broker Address: mqtt.tago.io
1.1	628
2.1	629	* (% style="color:#037691" %)Broker Port: 8883
1.1	630
2.1	631	* (% style="color:#037691" %)Client ID: “Any value”
1.1	632
2.1	633	(% style="color:blue" %)On the section User credentials, set the following information:
1.1	634
2.1	635	* (% style="color:#037691" %)User Name: “Any value” (%%) ~/~/ Tago validates your user by the token only
1.1	636
2.1	637	* (% style="color:#037691" %)Password: “Your device token”
1.1	638
2.1	639	* (% style="color:#037691" %)PUBTOPIC: “Any value”
1.1	640
2.1	641	* (% style="color:#037691" %)SUBTOPIC: “Any value”
1.1	642
2.1	643	(% style="color:blue" %)AT command:
1.1	644
2.1	645	* (% style="color:#037691" %)AT+PRO=3,0 or 3,5 (%%) ~/~/ hex format or json format
1.1	646
2.1	647	* (% style="color:#037691" %)AT+SUBTOPIC=<device name>or User Defined
1.1	648
2.1	649	* (% style="color:#037691" %)AT+PUBTOPIC=<device name>or User Defined
1.1	650
2.1	651	* (% style="color:#037691" %)AT+CLIENT=<device name> or User Defined
1.1	652
2.1	653	* (% style="color:#037691" %)AT+UNAME=<device name> or User Defined
1.1	654
2.1	655	* (% style="color:#037691" %)AT+PWD=“Your device token”
1.1	656
2.1	657	=== 3.7.2 Simulate with MQTT.fx ===
1.1	658
2.1	659	[[image:image-20230802112413-52.png]]
1.1	660
2.1	661	[[image:image-20230808105300-2.png\|\|height="553" width="1026"]]
1.1	662
2.1	663	Users can run the (% style="color:blue" %)AT+PRO=3,5(%%) command, and the payload will be converted to JSON format.
1.1	664
2.1	665	[[image:image-20230808105217-1.png\|\|height="556" width="1031"]]
1.1	666
2.1	667	[[image:image-20230808105329-3.png]]
1.1	668
2.1	669	=== 3.7.3 tago data ===
1.1	670
2.1	671	[[image:image-20230802112413-50.png\|\|height="242" width="1037"]]
1.1	672
2.1	673	[[image:image-20230802112413-51.png\|\|height="184" width="696"]]
1.1	674
2.1	675	== 3.8 TCP Connection ==
1.1	676
2.1	677	(% style="color:blue" %)AT command:
1.1	678
3.1	679	* (% style="color:#037691" %)AT+PRO=4,0 (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
1.1	680
3.1	681	* (% style="color:#037691" %)AT+PRO=4,1 (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
1.1	682
2.1	683	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5600 (%%) ~/~/ to set TCP server address and port
1.1	684
2.1	685	(% style="color:blue" %)Sensor Console Output when Uplink:
1.1	686
2.1	687	[[image:image-20230807233631-1.png]]
1.1	688
2.1	689	(% style="color:blue" %)See result in TCP Server:
1.1	690
2.1	691	[[image:image-20230807233631-2.png]]
1.1	692
2.1	693	== 3.9 AWS Connection ==
1.1	694
2.1	695	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	696
2.1	697	= 4. MQTT/UDP/TCP downlink =
1.1	698
2.1	699	== 4.1 MQTT (via MQTT.fx) ==
1.1	700
2.1	701	Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
1.1	702
2.1	703	1. Configure node MQTT connection (via MQTT.fx):
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=User Defined
1.1	710
2.1	711	* (% style="color:#037691" %)AT+PUBTOPIC=User Defined
1.1	712
2.1	713	* (% style="color:#037691" %)AT+UNAME=<device name> or User Defined
1.1	714
2.1	715	* (% style="color:#037691" %)AT+PWD=<device name> or User Defined
1.1	716
2.1	717	* (% style="color:#037691" %)AT+SERVADDR=8.217.91.207,1883 (%%) ~/~/ to set MQTT server address and port
1.1	718
2.1	719	(% 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	720
3.1	721	[[image:image-20240417180145-2.png\|\|height="434" width="587"]][[ width="584">> width="584"]]
1.1	722
2.1	723	2. When the node uplink packets, we can observe the data in MQTT.fx.
1.1	724
2.1	725	[[image:image-20240418144337-1.png\|\|height="709" width="802"]]
1.1	726
2.1	727	3. The downlink command can be successfully sent only when the downlink port is open.
1.1	728
	729	The downlink port is opened for about 3 seconds after uplink packets are sent.
	730
2.1	731	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	732
2.1	733	[[image:image-20240418150435-3.png\|\|height="582" width="659"]]
1.1	734
2.1	735	[[image:image-20240418150932-4.png\|\|height="492" width="1061"]]
1.1	736
2.1	737	(% 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	738
10.1	739	= 5. GPS positioning function =
	740
11.1	741	=== 1. Turn on GPS function ===
10.1	742
	743	(% class="wikigeneratedid" %)
	744	AT+GPS=1 or 0 ~/~/GPS function on or off
	745
	746
11.1	747	=== 2.Extend the time to turn on GNSS ===
10.1	748
	749	AT+GNSST=30 ~/~/GPS search for positioning information for 30 seconds
	750
	751
11.1	752	=== 3.Get or set GPS positioning interval in units of hour ===
10.1	753
	754	AT+GTDC=24 ~/~/The device will activate GPS positioning every 24 hours
	755
	756
2.1	757	= 5. FAQ =
1.1	758
2.1	759	== 5.1 What is the usage of Multi Sampling and One Uplink? ==
1.1	760
	761	The NB series has the feature for Multi Sampling and one uplink. See one of them
	762
2.1	763	[[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	764
	765	User can use this feature for below purpose:
	766
2.1	767	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.
	768	1. Give more sampling data points.
	769	1. Increase reliable in transmission. For example. If user set
	770	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)
	771	1. AT+NOUD=24* ~/~/ The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
	772	1. AT+TDC=7200* ~/~/ Uplink every 2 hours.
	773	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	774
2.1	775	== 5.2 Why the uplink JSON format is not standard? ==
1.1	776
	777	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.
	778
	779	The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
	780
2.1	781	[[image:image-20240229233154-1.png]]
1.1	782
2.1	783	= 6. Trouble Shooting: =
1.1	784
2.1	785	== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
1.1	786
	787	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.
	788
2.1	789	If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
1.1	790
2.1	791	[[image:image-20240207002003-1.png]]
1.1	792
	793	If fail to attach network, it will shows signal 99. as below:
	794
2.1	795	[[image:image-20240207002129-2.png]]
1.1	796
2.1	797	(% class="lead" %)
1.1	798	When see this issue, below are the checklist:
	799
2.1	800	* 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.
	801	* 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]].
	802	* 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]].
	803	* Check if the device is attached to Carrier network but reject. (need to check with operator).
	804	* Check if the antenna is connected firmly.
1.1	805
2.1	806	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	807
	808
2.1	809	== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
1.1	810
	811	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.
	812
2.1	813	[[image:image-20240226111928-1.png]]
1.1	814
2.1	815	== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
1.1	816
2.1	817	(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
	818	=== UDP: ===
1.1	819
2.1	820	(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1.1	821	Its downlink command is the same as the AT command, but brackets are required.
	822	Example:
	823
	824	{AT+TDC=300}
	825
2.1	826	(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
	827	=== MQTT: ===
1.1	828
	829	Json：
	830
	831	The Json format in MQTT mode needs to be configured with all commands.
	832	If you have configurations that need to be changed, please change them in the template below.
	833	Template:
	834
	835	{
	836	"AT+SERVADDR":"119.91.62.30,1882",
	837	"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
	838	"AT+UNAME":"usenamedragino",
	839	"AT+PWD":"passworddragino",
	840	"AT+PUBTOPIC":"123",
	841	"AT+SUBTOPIC":"321",
	842	"AT+TDC":"7200",
	843	"AT+INTMOD":"0",
	844	"AT+APN":"NULL",
	845	"AT+5VT":"0",
	846	"AT+PRO":"3,5",
	847	"AT+TR":"900",
	848	"AT+NOUD":"0",
	849	"AT+CSQTIME":"5",
	850	"AT+DNSTIMER":"0",
	851	"AT+TLSMOD":"0,0",
	852	"AT+MQOS":"0",
	853	"AT+TEMPALARM1":"0",
	854	"AT+TEMPALARM2":"10",
	855	"AT+TEMPALARM3":"0"
	856	}
	857
	858	Hex：
	859
	860	MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
	861
	862	The supported commands are consistent with LoRaWAN's hex commands.
	863	Please refer to the following link to obtain the hex format:
	864
2.1	865	[[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	866
	867
2.1	868

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

Applications

Navigation