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

Version 10.1 by David Huang on 2024/06/07 16:21

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
9.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
	144	2.Configure search network sequence
	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
	157	3.Configure Network Category to be Searched for under LTE RAT
	158
	159	AT+QCFG="iotopmode",mode,1
	160
	161	0 eMTC
	162	1 NB-IoT
	163	2 eMTC and NB-IoT
	164
	165
2.1	166	= 3. Configure to connect to different servers =
1.1	167
2.1	168	== 3.1 General UDP Connection ==
1.1	169
2.1	170	The NB-IoT Sensor can send packet to server use UDP protocol.
1.1	171
2.1	172	=== 3.1.1 Simulate UDP Connection by PC tool ===
1.1	173
2.1	174	We can use PC tool to simulate UDP connection to make sure server works ok.
1.1	175
2.1	176	[[image:image-20230802112413-1.png\|\|height="468" width="1024"]]
1.1	177
2.1	178	=== 3.1.2 Configure NB-IoT Sensor ===
1.1	179
2.1	180	==== 3.1.2.1 AT Commands ====
1.1	181
2.1	182	(% style="color:blue" %)AT Commands:
1.1	183
3.1	184	* (% style="color:#037691" %)AT+PRO=2,0 (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload
1.1	185
3.1	186	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5601 (%%) ~/~/ Set UDP server address and port
1.1	187
2.1	188	[[image:image-20230802112413-2.png]]
1.1	189
2.1	190	==== 3.1.2.2 Uplink Example ====
1.1	191
2.1	192	[[image:image-20230802112413-3.png]]
1.1	193
8.1	194	== 3.2 General COAP Connection ==
	195
	196	The NB-IoT Sensor can send packet to server use COAP protocol.
	197
	198	Below are the commands.
	199
	200	(% style="color:blue" %)AT Commands:
	201
	202	* (% style="color:#037691" %)AT+PRO=1,0 (%%) ~/~/ Set to use COAP protocol to uplink, Payload Type select Hex payload.
	203
	204	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5683 (%%) ~/~/ Set COAP server address and port
	205
	206	* (% style="color:#037691" %)AT+URI1=11,"I" (%%) ~/~/ Configure CoAP Message Options
9.1	207	* (% style="color:#037691" %)AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1" (%%) ~/~/ Configure CoAP Message Options
8.1	208
	209	=== 3.2.1 Uplink Example ===
	210
	211
	212
2.1	213	== 3.2 General MQTT Connection ==
1.1	214
2.1	215	The NB-IoT Sensor can send packet to server use MQTT protocol.
1.1	216
2.1	217	Below are the commands.
1.1	218
2.1	219	(% style="color:blue" %)AT Commands:
1.1	220
3.1	221	* (% style="color:#037691" %)AT+PRO=3,0 (%%) ~/~/ Set to use MQTT protocol to uplink, Payload Type select Hex payload.
1.1	222
3.1	223	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,1883 (%%) ~/~/ Set MQTT server address and port
1.1	224
3.1	225	* (% style="color:#037691" %)AT+CLIENT=CLIENT (%%) ~/~/ Set up the CLIENT of MQTT
1.1	226
3.1	227	* (% style="color:#037691" %)AT+UNAME=UNAME (%%) ~/~/ Set the username of MQTT
1.1	228
3.1	229	* (% style="color:#037691" %)AT+PWD=PWD (%%) ~/~/ Set the password of MQTT
1.1	230
3.1	231	* (% style="color:#037691" %)AT+PUBTOPIC=NSE01_PUB (%%) ~/~/ Set the sending topic of MQTT
1.1	232
3.1	233	* (% style="color:#037691" %)AT+SUBTOPIC=NSE01_SUB (%%) ~/~/ Set the subscription topic of MQTT
1.1	234
2.1	235	[[image:image-20230802112413-4.png]]
1.1	236
2.1	237	[[image:image-20230802112413-5.png\|\|height="530" width="987"]]
1.1	238
2.1	239	(% 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	240
2.1	241	== 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
1.1	242
2.1	243	=== 3.3.1 Get MQTT Credentials ===
1.1	244
2.1	245	[[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	246
2.1	247	[[image:image-20230802112413-6.png\|\|height="336" width="925"]]
1.1	248
2.1	249	[[image:image-20230802112413-7.png]]
1.1	250
2.1	251	=== 3.3.2 Simulate with MQTT.fx ===
1.1	252
2.1	253	==== 3.3.2.1 Establish MQTT Connection ====
1.1	254
2.1	255	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	256
2.1	257	[[image:image-20230802112413-8.png]]
1.1	258
2.1	259	* (% style="color:#037691" %)Broker Address:(%%) mqtt3.thingspeak.com
1.1	260
2.1	261	* (% style="color:#037691" %)Broker Port:(%%) 1883
1.1	262
2.1	263	* (% style="color:#037691" %)Client ID:(%%) <Your ThingSpeak MQTT ClientID>
1.1	264
2.1	265	* (% style="color:#037691" %)User Name:(%%) <Your ThingSpeak MQTT User Name>
1.1	266
2.1	267	* (% style="color:#037691" %)Password:(%%) <Your ThingSpeak MQTT Password>
1.1	268
2.1	269	==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
1.1	270
2.1	271	[[image:image-20230802112413-9.png]]
1.1	272
2.1	273	[[image:image-20230802112413-10.png]]
1.1	274
2.1	275	(% style="color:blue" %)In MQTT.fx, we can publish below info:
1.1	276
2.1	277	* (% style="color:#037691" %)Topic:(%%) channels/YOUR_CHANNEL_ID/publish
1.1	278
2.1	279	* (% style="color:#037691" %)Payload:(%%) field1=63&field2=67&status=MQTTPUBLISH
1.1	280
2.1	281	Where 63 and 67 are the value to be published to field1 & field2.
1.1	282
2.1	283	(% style="color:blue" %)Result:
1.1	284
2.1	285	[[image:image-20230802112413-11.png\|\|height="539" width="901"]]
1.1	286
2.1	287	=== 3.3.3 Configure NB-IoT Sensor for connection ===
1.1	288
2.1	289	==== 3.3.3.1 AT Commands: ====
1.1	290
2.1	291	In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
1.1	292
2.1	293	* (% style="color:blue" %)AT+PRO=3,1 (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
1.1	294
2.1	295	* (% style="color:blue" %)AT+CLIENT=<Your ThingSpeak MQTT ClientID>
1.1	296
2.1	297	* (% style="color:blue" %)AT+UNAME=<Your ThingSpeak MQTT User Name>
1.1	298
2.1	299	* (% style="color:blue" %)AT+PWD=<Your ThingSpeak MQTT Password>
1.1	300
2.1	301	* (% style="color:blue" %)AT+PUBTOPIC=<YOUR_CHANNEL_ID>
1.1	302
2.1	303	* (% style="color:blue" %)AT+SUBTOPIC=<YOUR_CHANNEL_ID>
1.1	304
2.1	305	==== 3.3.3.2 Uplink Examples ====
1.1	306
2.1	307	[[image:image-20230816201942-1.png]]
1.1	308
2.1	309	For SE01-NB
1.1	310
2.1	311	For DDS20-NB
1.1	312
2.1	313	For DDS45-NB
1.1	314
2.1	315	For DDS75-NB
1.1	316
2.1	317	For NMDS120-NB
1.1	318
2.1	319	For SPH01-NB
1.1	320
2.1	321	For NLM01-NB
1.1	322
2.1	323	For NMDS200-NB
1.1	324
2.1	325	For CPN01-NB
1.1	326
2.1	327	For DS03A-NB
1.1	328
2.1	329	For SN50V3-NB
1.1	330
2.1	331	==== 3.3.3.3 Map fields to sensor value ====
1.1	332
2.1	333	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	334
2.1	335	[[image:image-20230802112413-12.png\|\|height="504" width="1011"]]
1.1	336
2.1	337	[[image:image-20230802112413-13.png\|\|height="331" width="978"]]
1.1	338
2.1	339	Below is the NB-IoT Product Table show the mapping.
1.1	340
2.1	341	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
	342	\|(% 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	343	\|(% 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" %)
	344	\|(% 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" %)
	345	\|(% 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" %)
	346	\|(% 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" %)
	347	\|(% 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" %)
	348	\|(% 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" %)
	349	\|(% 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" %)
	350	\|(% 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" %)
	351	\|(% 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" %)
	352	\|(% 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	353	\|(% 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	354	\|(% 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" %)
	355	\|(% 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" %)
	356	\|(% 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" %)
	357	\|(% 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" %)
	358	\|(% 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" %)
	359	\|(% 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	360
2.1	361	== 3.4 [[Datacake>>https://datacake.co/]] ==
1.1	362
2.1	363	(% class="wikigeneratedid" %)
	364	Dragino NB-IoT sensors has its template in [[Datacake>>https://datacake.co/]] Platform. There are two version for NB Sensor,
1.1	365
2.1	366	(% class="wikigeneratedid" %)
	367	As example for S31B-NB. there are two versions: S31B-NB-1D and S31B-NB-GE.
1.1	368
2.1	369	* (% 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	370
2.1	371	* (% 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	372
2.1	373	=== 3.4.1 For device Already has template ===
1.1	374
2.1	375	==== 3.4.1.1 Create Device ====
1.1	376
2.1	377	(% style="color:blue" %)Add Device(%%) in DataCake.
1.1	378
2.1	379	[[image:image-20230808162301-1.png\|\|height="453" width="952"]]
1.1	380
2.1	381	[[image:image-20230808162342-2.png\|\|height="541" width="952"]]
1.1	382
2.1	383	(% style="color:blue" %)Choose the correct model(%%) from template.
1.1	384
2.1	385	[[image:image-20230808162421-3.png]]
1.1	386
3.1	387	(% 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	388
2.1	389	[[image:image-20230808163612-7.png\|\|height="549" width="952"]]
1.1	390
2.1	391	[[image:image-20230808163035-5.png]]
1.1	392
2.1	393	[[image:image-20230808163049-6.png\|\|height="544" width="926"]]
1.1	394
2.1	395	=== 3.4.2 For Device already registered in DataCake before shipped ===
1.1	396
2.1	397	==== 3.4.2.1 Scan QR Code to get the device info ====
1.1	398
	399	Users can use their phones or computers to scan QR codes to obtain device data information.
	400
2.1	401	[[image:image-20230808170051-8.png\|\|height="255" width="259"]]
1.1	402
2.1	403	[[image:image-20230808170548-9.png]]
1.1	404
2.1	405	==== 3.4.2.2 Claim Device to User Account ====
1.1	406
	407	By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
	408
2.1	409	=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
1.1	410
2.1	411	Step1: Add a device
1.1	412
2.1	413	[[image:image-20240129170024-1.png\|\|height="330" width="900"]]
1.1	414
2.1	415	Step2: Choose your device type,please select dragino NB-IOT device
1.1	416
2.1	417	[[image:image-20240129170216-2.png\|\|height="534" width="643"]]
1.1	418
2.1	419	Step3: Choose to create a new device
1.1	420
2.1	421	[[image:image-20240129170539-3.png\|\|height="459" width="646"]]
1.1	422
2.1	423	Step4: Fill in the device ID of your NB device
1.1	424
2.1	425	[[image:image-20240202111546-1.png\|\|height="378" width="651"]]
1.1	426
2.1	427	Step5: Please select your device plan according to your needs and complete the creation of the device
1.1	428
2.1	429	[[image:image-20240129171236-6.png\|\|height="450" width="648"]]
1.1	430
2.1	431	Step6: Please add the decoder at the payload decoder of the device configuration.
1.1	432
2.1	433	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	434
2.1	435	[[image:image-20240129172056-7.png\|\|height="457" width="816"]]
1.1	436
2.1	437	[[image:image-20240129173116-9.png\|\|height="499" width="814"]]
1.1	438
2.1	439	Step7: Add the output of the decoder as a field
1.1	440
2.1	441	[[image:image-20240129173541-10.png\|\|height="592" width="968"]]
1.1	442
2.1	443	Step8: Customize the dashboard and use fields as parameters of the dashboard
1.1	444
2.1	445	[[image:image-20240129174518-11.png\|\|height="147" width="1042"]]
1.1	446
2.1	447	[[image:image-20240129174657-12.png\|\|height="538" width="916"]]
1.1	448
2.1	449	[[image:image-20240129174840-13.png\|\|height="536" width="750"]]
1.1	450
2.1	451	=== 3.4.4 For device have not configured to connect to DataCake ===
1.1	452
2.1	453	(% class="lead" %)
1.1	454	Use AT command for connecting to DataCake
	455
2.1	456	(% style="color:blue" %)AT+PRO=2,0
1.1	457
2.1	458	(% style="color:blue" %)AT+SERVADDR=67.207.76.90,4445
1.1	459
2.1	460	== 3.5 Node-Red (via MQTT) ==
1.1	461
2.1	462	=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
1.1	463
	464	Take S31-NB UDP protocol as an example.
	465
	466	Dragino provides input flow examples for the sensors.
	467
	468	User can download the required JSON file through Dragino Node-RED input flow template.
	469
2.1	470	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	471
	472	We can directly import the template.
	473
	474	The templates for S31-NB and NB95S31B are the same.
	475
2.1	476	[[image:image-20230809173127-4.png]]
1.1	477
	478	Please select the NB95S31B template.
	479
2.1	480	[[image:image-20230809173310-5.png\|\|height="558" width="926"]]
1.1	481
2.1	482	[[image:image-20230809173438-6.png]]
1.1	483
2.1	484	[[image:image-20230809173800-7.png]]
1.1	485
	486	Successfully imported template.
	487
2.1	488	[[image:image-20230809173835-8.png\|\|height="515" width="860"]]
1.1	489
	490	Users can set UDP port.
	491
2.1	492	[[image:image-20230809174053-9.png]]
1.1	493
2.1	494	=== 3.5.2 Simulate Connection ===
1.1	495
	496	We have completed the configuration of UDP. We can try sending packets to node red.
	497
2.1	498	[[image:image-20230810083934-1.png]]
1.1	499
2.1	500	[[image:image-20230810084048-2.png\|\|height="535" width="1052"]]
1.1	501
2.1	502	=== 3.5.3 Configure NB-IoT Sensors ===
1.1	503
2.1	504	* (% style="color:#037691" %)AT+PRO=3,0 or 3,5 (%%) ~/~/ hex format or json format
	505	* (% style="color:#037691" %)AT+SUBTOPIC=<device name>or User Defined
	506	* (% style="color:#037691" %)AT+PUBTOPIC=<device name>or User Defined
	507	* (% style="color:#037691" %)AT+CLIENT=<device name> or User Defined
	508	* (% style="color:#037691" %)AT+UNAME=<device name> or User Defined
	509	* (% style="color:#037691" %)AT+PWD=“Your device token”
1.1	510
2.1	511	== 3.6 ThingsBoard.Cloud (via MQTT) ==
1.1	512
2.1	513	=== 3.6.1 Configure ThingsBoard ===
1.1	514
2.1	515	==== 3.6.1.1 Create Device ====
1.1	516
2.1	517	Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
1.1	518
2.1	519	[[image:image-20230802112413-32.png\|\|height="583" width="1066"]]
1.1	520
2.1	521	==== 3.6.1.2 Create Uplink & Downlink Converter ====
1.1	522
2.1	523	(% style="color:blue" %)Uplink Converter
1.1	524
2.1	525	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	526
2.1	527	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	528
2.1	529	[[image:image-20230802112413-33.png\|\|height="597" width="1061"]]
1.1	530
2.1	531	(% style="color:blue" %)Downlink Converter
1.1	532
2.1	533	The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
1.1	534
2.1	535	[[image:image-20230802112413-34.png\|\|height="598" width="1063"]]
1.1	536
2.1	537	(% 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	538
2.1	539	==== 3.6.1.3 MQTT Integration Setup ====
1.1	540
2.1	541	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	542
2.1	543	[[image:image-20230802112413-35.png\|\|height="597" width="1062"]]
1.1	544
2.1	545	* The next steps is to add the recently created uplink and downlink converters;
1.1	546
2.1	547	[[image:image-20230802112413-36.png\|\|height="598" width="1062"]]
1.1	548
2.1	549	[[image:image-20230802112413-37.png\|\|height="598" width="1064"]]
1.1	550
2.1	551	(% style="color:blue" %)Add a topic filter:
1.1	552
	553	Consistent with the theme of the node setting.
	554
2.1	555	You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
1.1	556
2.1	557	[[image:image-20230802112413-38.png\|\|height="598" width="1064"]]
1.1	558
2.1	559	=== 3.6.2 Simulate with MQTT.fx ===
1.1	560
2.1	561	[[image:image-20230802112413-39.png]]
1.1	562
2.1	563	[[image:image-20230802112413-40.png\|\|height="525" width="980"]]
1.1	564
2.1	565	=== 3.6.3 Configure NB-IoT Sensor ===
1.1	566
2.1	567	(% style="color:blue" %)AT Commands
1.1	568
3.1	569	* (% style="color:#037691" %)AT+PRO=3,3 (%%) ~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
1.1	570
2.1	571	* (% style="color:#037691" %)AT+SUBTOPIC=<device name>
1.1	572
2.1	573	* (% style="color:#037691" %)AT+PUBTOPIC=<device name>
1.1	574
2.1	575	* (% style="color:#037691" %)AT+CLIENT=<device name> or User Defined
1.1	576
2.1	577	* (% style="color:#037691" %)AT+UNAME=<device name> or User Defined
1.1	578
2.1	579	* (% style="color:#037691" %)AT+PWD=<device name> or User Defined
1.1	580
2.1	581	Test Uplink by click the button for 1 second
1.1	582
2.1	583	[[image:image-20230802112413-41.png\|\|height="496" width="828"]]
1.1	584
2.1	585	[[image:image-20230802112413-42.png]]
1.1	586
2.1	587	[[image:image-20230802112413-43.png\|\|height="407" width="825"]]
1.1	588
2.1	589	== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
1.1	590
2.1	591	=== 3.7.1 Create device & Get Credentials ===
1.1	592
2.1	593	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	594
2.1	595	[[image:image-20230802112413-44.png]]
1.1	596
2.1	597	[[image:image-20230802112413-45.png]]
1.1	598
2.1	599	Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
1.1	600
2.1	601	[[image:image-20230802112413-46.png]]
1.1	602
2.1	603	The device needs to enable the TLS mode and set the (% style="color:blue" %)AT+TLSMOD=1,0(%%) command.
1.1	604
2.1	605	(% style="color:blue" %)On the Connection Profile window, set the following information:
1.1	606
2.1	607	* (% style="color:#037691" %)Profile Name: “Any name”
1.1	608
2.1	609	* (% style="color:#037691" %)Broker Address: mqtt.tago.io
1.1	610
2.1	611	* (% style="color:#037691" %)Broker Port: 8883
1.1	612
2.1	613	* (% style="color:#037691" %)Client ID: “Any value”
1.1	614
2.1	615	(% style="color:blue" %)On the section User credentials, set the following information:
1.1	616
2.1	617	* (% style="color:#037691" %)User Name: “Any value” (%%) ~/~/ Tago validates your user by the token only
1.1	618
2.1	619	* (% style="color:#037691" %)Password: “Your device token”
1.1	620
2.1	621	* (% style="color:#037691" %)PUBTOPIC: “Any value”
1.1	622
2.1	623	* (% style="color:#037691" %)SUBTOPIC: “Any value”
1.1	624
2.1	625	(% style="color:blue" %)AT command:
1.1	626
2.1	627	* (% style="color:#037691" %)AT+PRO=3,0 or 3,5 (%%) ~/~/ hex format or json format
1.1	628
2.1	629	* (% style="color:#037691" %)AT+SUBTOPIC=<device name>or User Defined
1.1	630
2.1	631	* (% style="color:#037691" %)AT+PUBTOPIC=<device name>or User Defined
1.1	632
2.1	633	* (% style="color:#037691" %)AT+CLIENT=<device name> or User Defined
1.1	634
2.1	635	* (% style="color:#037691" %)AT+UNAME=<device name> or User Defined
1.1	636
2.1	637	* (% style="color:#037691" %)AT+PWD=“Your device token”
1.1	638
2.1	639	=== 3.7.2 Simulate with MQTT.fx ===
1.1	640
2.1	641	[[image:image-20230802112413-52.png]]
1.1	642
2.1	643	[[image:image-20230808105300-2.png\|\|height="553" width="1026"]]
1.1	644
2.1	645	Users can run the (% style="color:blue" %)AT+PRO=3,5(%%) command, and the payload will be converted to JSON format.
1.1	646
2.1	647	[[image:image-20230808105217-1.png\|\|height="556" width="1031"]]
1.1	648
2.1	649	[[image:image-20230808105329-3.png]]
1.1	650
2.1	651	=== 3.7.3 tago data ===
1.1	652
2.1	653	[[image:image-20230802112413-50.png\|\|height="242" width="1037"]]
1.1	654
2.1	655	[[image:image-20230802112413-51.png\|\|height="184" width="696"]]
1.1	656
2.1	657	== 3.8 TCP Connection ==
1.1	658
2.1	659	(% style="color:blue" %)AT command:
1.1	660
3.1	661	* (% style="color:#037691" %)AT+PRO=4,0 (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
1.1	662
3.1	663	* (% style="color:#037691" %)AT+PRO=4,1 (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
1.1	664
2.1	665	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5600 (%%) ~/~/ to set TCP server address and port
1.1	666
2.1	667	(% style="color:blue" %)Sensor Console Output when Uplink:
1.1	668
2.1	669	[[image:image-20230807233631-1.png]]
1.1	670
2.1	671	(% style="color:blue" %)See result in TCP Server:
1.1	672
2.1	673	[[image:image-20230807233631-2.png]]
1.1	674
2.1	675	== 3.9 AWS Connection ==
1.1	676
2.1	677	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	678
2.1	679	= 4. MQTT/UDP/TCP downlink =
1.1	680
2.1	681	== 4.1 MQTT (via MQTT.fx) ==
1.1	682
2.1	683	Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
1.1	684
2.1	685	1. Configure node MQTT connection (via MQTT.fx):
1.1	686
2.1	687	(% style="color:blue" %)AT command:
1.1	688
2.1	689	* (% style="color:#037691" %)AT+PRO=3,0 or 3,5 (%%)~/~/ hex format or json format
1.1	690
2.1	691	* (% style="color:#037691" %)AT+SUBTOPIC=User Defined
1.1	692
2.1	693	* (% style="color:#037691" %)AT+PUBTOPIC=User Defined
1.1	694
2.1	695	* (% style="color:#037691" %)AT+UNAME=<device name> or User Defined
1.1	696
2.1	697	* (% style="color:#037691" %)AT+PWD=<device name> or User Defined
1.1	698
2.1	699	* (% style="color:#037691" %)AT+SERVADDR=8.217.91.207,1883 (%%) ~/~/ to set MQTT server address and port
1.1	700
2.1	701	(% 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	702
3.1	703	[[image:image-20240417180145-2.png\|\|height="434" width="587"]][[ width="584">> width="584"]]
1.1	704
2.1	705	2. When the node uplink packets, we can observe the data in MQTT.fx.
1.1	706
2.1	707	[[image:image-20240418144337-1.png\|\|height="709" width="802"]]
1.1	708
2.1	709	3. The downlink command can be successfully sent only when the downlink port is open.
1.1	710
	711	The downlink port is opened for about 3 seconds after uplink packets are sent.
	712
2.1	713	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	714
2.1	715	[[image:image-20240418150435-3.png\|\|height="582" width="659"]]
1.1	716
2.1	717	[[image:image-20240418150932-4.png\|\|height="492" width="1061"]]
1.1	718
2.1	719	(% 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	720
10.1	721	= 5. GPS positioning function =
	722
	723	(% class="wikigeneratedid" id="H5.1WhatistheusageofMultiSamplingandOneUplink3F" %)
	724	~1. Turn on GPS function
	725
	726	(% class="wikigeneratedid" %)
	727	AT+GPS=1 or 0 ~/~/GPS function on or off
	728
	729
	730	2.Extend the time to turn on GNSS
	731
	732	AT+GNSST=30 ~/~/GPS search for positioning information for 30 seconds
	733
	734
	735	3.Get or set GPS positioning interval in units of hour
	736
	737	AT+GTDC=24 ~/~/The device will activate GPS positioning every 24 hours
	738
	739
2.1	740	= 5. FAQ =
1.1	741
2.1	742	== 5.1 What is the usage of Multi Sampling and One Uplink? ==
1.1	743
	744	The NB series has the feature for Multi Sampling and one uplink. See one of them
	745
2.1	746	[[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	747
	748	User can use this feature for below purpose:
	749
2.1	750	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.
	751	1. Give more sampling data points.
	752	1. Increase reliable in transmission. For example. If user set
	753	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)
	754	1. AT+NOUD=24* ~/~/ The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
	755	1. AT+TDC=7200* ~/~/ Uplink every 2 hours.
	756	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	757
2.1	758	== 5.2 Why the uplink JSON format is not standard? ==
1.1	759
	760	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.
	761
	762	The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
	763
2.1	764	[[image:image-20240229233154-1.png]]
1.1	765
2.1	766	= 6. Trouble Shooting: =
1.1	767
2.1	768	== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
1.1	769
	770	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.
	771
2.1	772	If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
1.1	773
2.1	774	[[image:image-20240207002003-1.png]]
1.1	775
	776	If fail to attach network, it will shows signal 99. as below:
	777
2.1	778	[[image:image-20240207002129-2.png]]
1.1	779
2.1	780	(% class="lead" %)
1.1	781	When see this issue, below are the checklist:
	782
2.1	783	* 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.
	784	* 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]].
	785	* 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]].
	786	* Check if the device is attached to Carrier network but reject. (need to check with operator).
	787	* Check if the antenna is connected firmly.
1.1	788
2.1	789	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	790
	791
2.1	792	== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
1.1	793
	794	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.
	795
2.1	796	[[image:image-20240226111928-1.png]]
1.1	797
2.1	798	== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
1.1	799
2.1	800	(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
	801	=== UDP: ===
1.1	802
2.1	803	(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1.1	804	Its downlink command is the same as the AT command, but brackets are required.
	805	Example:
	806
	807	{AT+TDC=300}
	808
2.1	809	(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
	810	=== MQTT: ===
1.1	811
	812	Json：
	813
	814	The Json format in MQTT mode needs to be configured with all commands.
	815	If you have configurations that need to be changed, please change them in the template below.
	816	Template:
	817
	818	{
	819	"AT+SERVADDR":"119.91.62.30,1882",
	820	"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
	821	"AT+UNAME":"usenamedragino",
	822	"AT+PWD":"passworddragino",
	823	"AT+PUBTOPIC":"123",
	824	"AT+SUBTOPIC":"321",
	825	"AT+TDC":"7200",
	826	"AT+INTMOD":"0",
	827	"AT+APN":"NULL",
	828	"AT+5VT":"0",
	829	"AT+PRO":"3,5",
	830	"AT+TR":"900",
	831	"AT+NOUD":"0",
	832	"AT+CSQTIME":"5",
	833	"AT+DNSTIMER":"0",
	834	"AT+TLSMOD":"0,0",
	835	"AT+MQOS":"0",
	836	"AT+TEMPALARM1":"0",
	837	"AT+TEMPALARM2":"10",
	838	"AT+TEMPALARM3":"0"
	839	}
	840
	841	Hex：
	842
	843	MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
	844
	845	The supported commands are consistent with LoRaWAN's hex commands.
	846	Please refer to the following link to obtain the hex format:
	847
2.1	848	[[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	849
	850
2.1	851

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

Applications

Navigation