Changes for page General Manual for -CB , -CS models

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 103 added, 0 removed)
  • image-20240602220856-1.png
  • image-20240819102802-1.png
  • image-20240819103212-2.png
  • image-20240819103826-3.png
  • image-20240819103909-4.png
  • image-20240819104904-5.png
  • image-20240819104942-6.png
  • image-20240819105003-7.png
  • image-20240819105418-8.png
  • image-20240819112109-1.png
  • image-20240819173602-1.png
  • image-20240819173659-2.png
  • image-20240819173706-3.png
  • image-20240819173826-4.png
  • image-20240819174033-5.png
  • image-20240819174209-6.png
  • image-20240819174314-7.png
  • image-20240819174540-8.png
  • image-20240819174610-9.png
  • image-20240819174618-10.png
  • image-20240820110003-1.png
  • image-20240820110017-2.png
  • image-20240820110031-3.png
  • image-20240820110048-4.png
  • image-20240820110103-5.png
  • image-20240820110114-6.png
  • image-20240820110129-7.png
  • image-20240820110142-8.png
  • image-20240820110218-9.png
  • image-20240820110235-10.png
  • image-20240820110247-11.png
  • image-20240820111016-12.png
  • image-20240820111101-13.png
  • image-20240820111113-14.png
  • image-20240820111236-15.png
  • image-20240820111248-16.png
  • image-20240820111259-17.png
  • image-20240820111312-18.png
  • image-20240820111322-19.png
  • image-20240820111333-20.png
  • image-20240820111353-21.png
  • image-20240820111405-22.png
  • image-20240820111418-23.png
  • image-20240820111427-24.png
  • image-20240820111438-25.png
  • image-20240820111448-26.png
  • image-20240820111504-27.png
  • image-20240820111515-28.png
  • image-20240820112210-29.png
  • image-20240820112222-30.png
  • image-20240820112236-31.png
  • image-20240820112247-32.png
  • image-20240820112302-33.png
  • image-20240820112316-34.png
  • image-20240820112330-35.png
  • image-20240820112340-36.png
  • image-20240820112351-37.png
  • image-20240820112404-38.png
  • image-20240820112416-39.png
  • image-20240820112426-40.png
  • image-20240820112516-41.png
  • image-20240820112526-42.png
  • image-20240820112539-43.png
  • image-20240820112552-44.png
  • image-20240820112604-45.png
  • image-20240820112615-46.png
  • image-20240820112626-47.png
  • image-20240820112637-48.png
  • image-20240820112647-49.png
  • image-20240820112704-50.png
  • image-20240820112716-51.png
  • image-20240820112732-52.png
  • image-20240820112758-53.png
  • image-20240820112813-54.png
  • image-20240820112824-55.png
  • image-20240820112835-56.png
  • image-20240820112848-57.png
  • image-20240820112859-58.png
  • image-20240820112908-59.png
  • image-20240820113015-60.png
  • image-20240820140935-1.png
  • image-20240820141136-2.png
  • image-20240820141746-1.png
  • image-20240820141843-2.png
  • image-20240820143316-3.png
  • image-20240820143820-4.png
  • image-20240820144823-5.png
  • image-20240820144913-6.png
  • image-20240820145133-7.png
  • image-20240820145309-8.png
  • image-20240827145055-4.png
  • image-20240827150121-5.png
  • image-20240827150705-6.png
  • image-20240903094214-1.png
  • image-20240903094457-2.png
  • image-20240903100736-3.png
  • image-20240903100832-4.png
  • image-20240903102327-5.png
  • image-20240903102542-6.png
  • image-20240903102621-7.png
  • image-20240903102641-8.png
  • image-20240903104250-9.png
  • image-20240903104431-10.png

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Edwin
	1	+XWiki.ting

Content

...	...	@@ -1,6 +1,5 @@
1	1	​
2	2
3		-
4	4
5	5	(% class="wikigeneratedid" id="HTableofContents:" %)
6	6	**Table of Contents:**
...	...	@@ -9,86 +9,248 @@
9	9
10	10	= 1. The use of this guideline =
11	11
12		-This configure instruction is for Dragino NB-IoT models with -NB or -NS suffix, for example DDS75-NB. These models use the same NB-IoT Module **[[BC660K-GL>>https://www.quectel.com/product/lpwa-bc660k-gl-nb2]]** and has the same software structure. The have the same configure instruction to different IoT servers. Use can follow the instruction here to see how to configure to connect to those servers.
13	13
	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.
	13	+
	14	+
14	14	= 2. Attach Network =
15	15
16	16	== 2.1 General Configure to attach network ==
17	17
18		-To attache NB-IoT sensors to NB-IoT Network, You need to:
19	19
20		-1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
	20	+To attache end nodes to NB-IoT or LTE-M Network, You need to:
	21	+
	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)
21	21	1. Power Off End Node ( See below for the power off/on position)
22	22	1. Insert the SIM card to Sensor. ( See below for direction)
23	23	1. Power On End Node
24	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
25	25
26		-[[image:image-20240208102804-1.png||height="286" width="696"]]
	28	+[[image:image-20240602220856-1.png]]
27	27
28		-[[image:image-20230808205045-1.png||height="293" width="438"]]
29	29
30		-After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
	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"]]
31	31
32		-The -NB and -NS models support (% style="color:blue" %)**LTE Cat NB2**(%%), with below frequency band: multiple frequency bands of (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85**(%%) . Make sure you use a the NB-IoT SIM card.
33	33
34		-(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
35		-|(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**AT+APN=**|(% style="background-color:#4f81bd; color:white; width:474px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
36		-|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
	34	+After doing above, the end nodes should be able to attach to NB-IoT network .
	35	+
	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
	37	+
	38	+~-~-(% style="color:blue" %)** CAT-NB2: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B28/B66/B71/B85 **(%%).
	39	+
	40	+~-~-(% style="color:blue" %)** CAT-M1: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85 **(%%).
	41	+
	42	+Make sure you use a the NB-IoT or LTE-M SIM card.
	43	+
	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" %)(((
37	37	**[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
38	38
39		-Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, UK, US Virgin Islands
40		-)))|(% style="width:135px" %)UK: Band20
41		-|(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
42		-|(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
	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" %)
43	43
44	44	== 2.2 Speed Up Network Attach time ==
45	45
46		-BC660K-GL supports multi bands (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85. **(%%) It will search one by one and try to attach, this will take a lot of time and even cause attach fail and show **Signal Strenght:99**. User can lock the band to specify band for its operator to make this faster.
47	47
48		-(% style="color:#037691" %)**AT+QBAND? **(%%) ~/~/ Check what is the current used frequency band
49		-(% style="color:#037691" %)**AT+QBAND=1,4 **(%%) ~/~/ Set to use 1 frequency band. Band4
50		-(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
51		-(% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=10,8,20,28,2,4,12,13,66,85,5**
	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**.
52	52
53		-(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
54		-(% style="color:#037691" %)**AT&T**(%%) AT+QBAND=3,12,4,2
55		-(% style="color:#037691" %)**Telstra**(%%) AT+QBAND=1,28
56		-(% style="color:#037691" %)**Softband**(%%) AT+QBAND=2,3,8
	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.
57	57
58		-After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
	63	+Attache to 1NCE card for Australia use:
59	59
	65	+* AT+COPS=1,2,"50501",8
	66	+* AT+QCFG="band",0,0x8000000,0x8000000,1
	67	+
	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	+
60	60	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/]]**
61	61
	77	+=== **1. Configure Frequency Band** ===
	78	+
	79	+AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
	80	+
	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	+
	147	+=== **2. Configure search network sequence** ===
	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	+
	161	+=== **3. Configure Network Category to be Searched for under LTE RAT** ===
	162	+
	163	+AT+QCFG="iotopmode",mode,1
	164	+
	165	+0 eMTC
	166	+1 NB-IoT
	167	+2 eMTC and NB-IoT
	168	+
	169	+
	170	+=== **4. AT command to set frequency band and network category** ===
	171	+
	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	+
62	62	= 3. Configure to connect to different servers =
63	63
64	64	== 3.1 General UDP Connection ==
65	65
	193	+
66	66	The NB-IoT Sensor can send packet to server use UDP protocol.
67	67
	196	+
68	68	=== 3.1.1 Simulate UDP Connection by PC tool ===
69	69
	199	+
70	70	We can use PC tool to simulate UDP connection to make sure server works ok.
71	71
72		-[[image:image-20230802112413-1.png||height="468" width="1024"]]
	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"]]
73	73
	204	+
74	74	=== 3.1.2 Configure NB-IoT Sensor ===
75	75
76	76	==== 3.1.2.1 AT Commands ====
77	77
	209	+
78	78	(% style="color:blue" %)**AT Commands:**
79	79
80		-* (% style="color:#037691" %)**AT+PRO=2,0** (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload
	212	+* (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload
81	81
82		-* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601** (%%) ~/~/ Set UDP server address and port
	214	+* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1999**  (%%) ~/~/ Set UDP server address and port
83	83
84		-[[image:image-20230802112413-2.png]]
	216	+[[image:image-20240819102802-1.png]]
85	85
	218	+
86	86	==== 3.1.2.2 Uplink Example ====
87	87
88		-[[image:image-20230802112413-3.png]]
89	89
	222	+[[image:image-20240819105418-8.png||height="611" width="1287"]]
	223	+
	224	+
	225	+== 3.2 General COAP Connection ==
	226	+
	227	+
	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	+
	238	+* (% style="color:#037691" %)**AT+URI1=11,"i"**  (%%) ~/~/  Configure CoAP Message Options
	239	+* (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**    (%%) ~/~/ Configure CoAP Message Options
	240	+
	241	+[[image:image-20240819103212-2.png]]
	242	+
	243	+
	244	+=== 3.2.1 Uplink Example ===
	245	+
	246	+
	247	+[[image:image-20240819103909-4.png||height="453" width="955"]]
	248	+
	249	+
90	90	== 3.2 General MQTT Connection ==
91	91
	252	+
92	92	The NB-IoT Sensor can send packet to server use MQTT protocol.
93	93
94	94	Below are the commands.
...	...	@@ -95,43 +95,48 @@
95	95
96	96	(% style="color:blue" %)**AT Commands:**
97	97
98		-* (% style="color:#037691" %)**AT+PRO=3,0** (%%) ~/~/ Set to use MQTT protocol to uplink, Payload Type select Hex payload.
	259	+* (% style="color:#037691" %)**AT+PRO=3,0**   (%%) ~/~/ Set to use MQTT protocol to uplink, Payload Type select Hex payload.
99	99
100		-* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883** (%%) ~/~/ Set MQTT server address and port
	261	+* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883**  (%%) ~/~/ Set MQTT server address and port
101	101
102		-* (% style="color:#037691" %)**AT+CLIENT=CLIENT** (%%) ~/~/ Set up the CLIENT of MQTT
	263	+* (% style="color:#037691" %)**AT+CLIENT=CLIENT**     (%%) ~/~/ Set up the CLIENT of MQTT
103	103
104		-* (% style="color:#037691" %)**AT+UNAME=UNAME** (%%) ~/~/ Set the username of MQTT
	265	+* (% style="color:#037691" %)**AT+UNAME=UNAME**        (%%) ~/~/ Set the username of MQTT
105	105
106		-* (% style="color:#037691" %)**AT+PWD=PWD** (%%) ~/~/ Set the password of MQTT
	267	+* (% style="color:#037691" %)**AT+PWD=PWD**             (%%) ~/~/ Set the password of MQTT
107	107
108		-* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB** (%%) ~/~/ Set the sending topic of MQTT
	269	+* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB**  (%%) ~/~/ Set the sending topic of MQTT
109	109
110		-* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB** (%%) ~/~/ Set the subscription topic of MQTT
	271	+* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB**  (%%) ~/~/ Set the subscription topic of MQTT
111	111
112		-[[image:image-20230802112413-4.png]]
	273	+[[image:image-20240819105003-7.png||height="613" width="458"]]
113	113
114		-[[image:image-20230802112413-5.png||height="530" width="987"]]
115	115
	276	+[[image:image-20240819104942-6.png||height="702" width="974"]]
	277	+
116	116	(% 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.**
117	117
	280	+
118	118	== 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
119	119
120	120	=== 3.3.1 Get MQTT Credentials ===
121	121
	285	+
122	122	[[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.
123	123
124		-[[image:image-20230802112413-6.png||height="336" width="925"]]
	288	+[[image:image-20240819173602-1.png||height="401" width="743"]]
125	125
126		-[[image:image-20230802112413-7.png]]
	290	+[[image:image-20240819173706-3.png||height="595" width="597"]]
127	127
	292	+
128	128	=== 3.3.2 Simulate with MQTT.fx ===
129	129
130	130	==== 3.3.2.1 Establish MQTT Connection ====
131	131
	297	+
132	132	After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
133	133
134		-[[image:image-20230802112413-8.png]]
	300	+[[image:image-20240819173826-4.png||height="534" width="734"]]
135	135
136	136	* (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
137	137
...	...	@@ -145,10 +145,11 @@
145	145
146	146	==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
147	147
148		-[[image:image-20230802112413-9.png]]
149	149
150		-[[image:image-20230802112413-10.png]]
	315	+[[image:image-20240819174033-5.png]]
151	151
	317	+[[image:image-20240819174209-6.png]]
	318	+
152	152	(% style="color:blue" %)**In MQTT.fx, we can publish below info:**
153	153
154	154	* (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
...	...	@@ -159,12 +159,14 @@
159	159
160	160	(% style="color:blue" %)**Result: **
161	161
162		-[[image:image-20230802112413-11.png||height="539" width="901"]]
	329	+[[image:image-20240819174314-7.png||height="469" width="785"]]
163	163
	331	+
164	164	=== 3.3.3 Configure NB-IoT Sensor for connection ===
165	165
166	166	==== 3.3.3.1 AT Commands: ====
167	167
	336	+
168	168	In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
169	169
170	170	* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
...	...	@@ -181,8 +181,9 @@
181	181
182	182	==== 3.3.3.2 Uplink Examples ====
183	183
184		-[[image:image-20230816201942-1.png]]
185	185
	354	+[[image:image-20240819174540-8.png]]
	355	+
186	186	For SE01-NB
187	187
188	188	For DDS20-NB
...	...	@@ -205,35 +205,37 @@
205	205
206	206	For SN50V3-NB
207	207
	378	+
208	208	==== 3.3.3.3 Map fields to sensor value ====
209	209
	381	+
210	210	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.
211	211
212		-[[image:image-20230802112413-12.png||height="504" width="1011"]]
	384	+[[image:image-20240819174610-9.png]]
213	213
214		-[[image:image-20230802112413-13.png||height="331" width="978"]]
	386	+[[image:image-20240819174618-10.png]]
215	215
216	216	Below is the NB-IoT Product Table show the mapping.
217	217
218		-(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
219		-|(% 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
220		-|(% 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" %)
221		-|(% 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" %)
222		-|(% 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" %)
223		-|(% 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" %)
224		-|(% 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" %)
225		-|(% 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" %)
226		-|(% 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" %)
227		-|(% 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" %)
228		-|(% 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" %)
229		-|(% 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" %)
230		-|(% 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
231		-|(% 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" %)
232		-|(% 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" %)
233		-|(% 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" %)
234		-|(% 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" %)
235		-|(% 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" %)
236		-|(% 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" %)
	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" %)
237	237
238	238	== 3.4 [[Datacake>>https://datacake.co/]] ==
239	239
...	...	@@ -241,92 +241,107 @@
241	241	Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
242	242
243	243	(% class="wikigeneratedid" %)
244		-As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
	416	+As example for S31B-CB. there are two versions: **S31B-CB-1D and S31B-CB-GE.**
245	245
246		-* (% 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.
	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.
247	247
248		-* (% 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.
	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.
249	249
250	250	=== 3.4.1 For device Already has template ===
251	251
252	252	==== 3.4.1.1 Create Device ====
253	253
	426	+
254	254	(% style="color:blue" %)**Add Device**(%%) in DataCake.
255	255
256		-[[image:image-20230808162301-1.png||height="453" width="952"]]
	429	+[[image:image-20240820110003-1.png]]
257	257
258		-[[image:image-20230808162342-2.png||height="541" width="952"]]
	431	+[[image:image-20240820110017-2.png]]
259	259
260	260	(% style="color:blue" %)**Choose the correct model**(%%) from template.
261	261
262		-[[image:image-20230808162421-3.png]]
	435	+[[image:image-20240820110031-3.png]]
263	263
264		-(% 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.
	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.
265	265
266		-[[image:image-20230808163612-7.png||height="549" width="952"]]
	439	+[[image:image-20240820110048-4.png]]
267	267
268		-[[image:image-20230808163035-5.png]]
	441	+[[image:image-20240820110103-5.png]]
269	269
270		-[[image:image-20230808163049-6.png||height="544" width="926"]]
	443	+[[image:image-20240820110114-6.png]]
271	271
	445	+
272	272	=== 3.4.2 For Device already registered in DataCake before shipped ===
273	273
274	274	==== 3.4.2.1 Scan QR Code to get the device info ====
275	275
	450	+
276	276	Users can use their phones or computers to scan QR codes to obtain device data information.
277	277
278		-[[image:image-20230808170051-8.png||height="255" width="259"]]
	453	+[[image:image-20240820110129-7.png]]
279	279
280		-[[image:image-20230808170548-9.png]]
	455	+[[image:image-20240820110218-9.png]]
281	281
	457	+
282	282	==== 3.4.2.2 Claim Device to User Account ====
283	283
284	284	By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
285	285
	462	+
286	286	=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
287	287
	465	+
288	288	**Step1: Add a device**
289	289
290		-[[image:image-20240129170024-1.png||height="330" width="900"]]
	468	+[[image:image-20240820110235-10.png]][[image:image-20240129170024-1.png||height="330" width="900"]]
291	291
	470	+
292	292	**Step2: Choose your device type,please select dragino NB-IOT device**
293	293
294		-[[image:image-20240129170216-2.png||height="534" width="643"]]
	473	+[[image:image-20240820110247-11.png]]
295	295
	475	+
296	296	**Step3: Choose to create a new device**
297	297
298		-[[image:image-20240129170539-3.png||height="459" width="646"]]
	478	+[[image:image-20240820111016-12.png]]
299	299
	480	+
300	300	**Step4: Fill in the device ID of your NB device**
301	301
302		-[[image:image-20240202111546-1.png||height="378" width="651"]]
	483	+[[image:image-20240820111101-13.png]]
303	303
	485	+
304	304	**Step5: Please select your device plan according to your needs and complete the creation of the device**
305	305
306		-[[image:image-20240129171236-6.png||height="450" width="648"]]
	488	+[[image:image-20240820111113-14.png]]
307	307
	490	+
308	308	**Step6: Please add the decoder at the payload decoder of the device configuration.**
309	309
310	310	**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]]
311	311
312		-[[image:image-20240129172056-7.png||height="457" width="816"]]
	495	+[[image:image-20240820111236-15.png]]
313	313
314		-[[image:image-20240129173116-9.png||height="499" width="814"]]
	497	+[[image:image-20240820111248-16.png]]
315	315
	499	+
316	316	**Step7: Add the output of the decoder as a field**
317	317
318		-[[image:image-20240129173541-10.png||height="592" width="968"]]
	502	+[[image:image-20240820111259-17.png]]
319	319
	504	+
320	320	**Step8: Customize the dashboard and use fields as parameters of the dashboard**
321	321
322		-[[image:image-20240129174518-11.png||height="147" width="1042"]]
	507	+[[image:image-20240820111312-18.png]]
323	323
324		-[[image:image-20240129174657-12.png||height="538" width="916"]]
	509	+[[image:image-20240820111322-19.png]]
325	325
326		-[[image:image-20240129174840-13.png||height="536" width="750"]]
	511	+[[image:image-20240820111333-20.png]]
327	327
	513	+
328	328	=== 3.4.4 For device have not configured to connect to DataCake ===
329	329
	516	+
330	330	(% class="lead" %)
331	331	Use AT command for connecting to DataCake
332	332
...	...	@@ -334,10 +334,12 @@
334	334
335	335	(% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
336	336
	524	+
337	337	== 3.5 Node-Red (via MQTT) ==
338	338
339	339	=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
340	340
	529	+
341	341	Take S31-NB UDP protocol as an example.
342	342
343	343	Dragino provides input flow examples for the sensors.
...	...	@@ -350,34 +350,38 @@
350	350
351	351	The templates for S31-NB and NB95S31B are the same.
352	352
353		-[[image:image-20230809173127-4.png]]
	542	+[[image:image-20240820111353-21.png]]
354	354
355	355	Please select the NB95S31B template.
356	356
357		-[[image:image-20230809173310-5.png||height="558" width="926"]]
	546	+[[image:image-20240820111405-22.png]]
358	358
359		-[[image:image-20230809173438-6.png]]
	548	+[[image:image-20240820111418-23.png]]
360	360
361		-[[image:image-20230809173800-7.png]]
	550	+[[image:image-20240820111427-24.png]]
362	362
363	363	Successfully imported template.
364	364
365		-[[image:image-20230809173835-8.png||height="515" width="860"]]
	554	+[[image:image-20240820111438-25.png]]
366	366
367	367	Users can set UDP port.
368	368
369		-[[image:image-20230809174053-9.png]]
	558	+[[image:image-20240820111448-26.png]]
370	370
	560	+
371	371	=== 3.5.2 Simulate Connection ===
372	372
	563	+
373	373	We have completed the configuration of UDP. We can try sending packets to node red.
374	374
375		-[[image:image-20230810083934-1.png]]
	566	+[[image:image-20240820111504-27.png]]
376	376
377		-[[image:image-20230810084048-2.png||height="535" width="1052"]]
	568	+[[image:image-20240820111515-28.png]]
378	378
	570	+
379	379	=== 3.5.3 Configure NB-IoT Sensors ===
380	380
	573	+
381	381	* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
382	382	* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
383	383	* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
...	...	@@ -391,12 +391,15 @@
391	391
392	392	==== 3.6.1.1 Create Device ====
393	393
	587	+
394	394	Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
395	395
396		-[[image:image-20230802112413-32.png||height="583" width="1066"]]
	590	+[[image:image-20240820112210-29.png]]
397	397
	592	+
398	398	==== 3.6.1.2 Create Uplink & Downlink Converter ====
399	399
	595	+
400	400	(% style="color:blue" %)**Uplink Converter**
401	401
402	402	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.
...	...	@@ -403,27 +403,29 @@
403	403
404	404	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.
405	405
406		-[[image:image-20230802112413-33.png||height="597" width="1061"]]
	602	+[[image:image-20240820112222-30.png]]
407	407
408	408	(% style="color:blue" %)**Downlink Converter**
409	409
410	410	The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
411	411
412		-[[image:image-20230802112413-34.png||height="598" width="1063"]]
	608	+[[image:image-20240820112236-31.png]]
413	413
414	414	(% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
415	415
	612	+
416	416	==== 3.6.1.3 MQTT Integration Setup ====
417	417
	615	+
418	418	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**;
419	419
420		-[[image:image-20230802112413-35.png||height="597" width="1062"]]
	618	+[[image:image-20240820112247-32.png]]
421	421
422	422	* The next steps is to add the recently created uplink and downlink converters;
423	423
424		-[[image:image-20230802112413-36.png||height="598" width="1062"]]
	622	+[[image:image-20240820112302-33.png]]
425	425
426		-[[image:image-20230802112413-37.png||height="598" width="1064"]]
	624	+[[image:image-20240820112316-34.png]]
427	427
428	428	(% style="color:blue" %)**Add a topic filter:**
429	429
...	...	@@ -431,19 +431,22 @@
431	431
432	432	You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
433	433
434		-[[image:image-20230802112413-38.png||height="598" width="1064"]]
	632	+[[image:image-20240820112330-35.png]]
435	435
	634	+
436	436	=== 3.6.2 Simulate with MQTT.fx ===
437	437
438		-[[image:image-20230802112413-39.png]]
	637	+[[image:image-20240820112340-36.png]]
439	439
440		-[[image:image-20230802112413-40.png||height="525" width="980"]]
	639	+[[image:image-20240820112351-37.png]]
441	441
	641	+
442	442	=== 3.6.3 Configure NB-IoT Sensor ===
443	443
	644	+
444	444	(% style="color:blue" %)**AT Commands**
445	445
446		-* (% style="color:#037691" %)**AT+PRO=3,3 **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
	647	+* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
447	447
448	448	* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
449	449
...	...	@@ -457,25 +457,99 @@
457	457
458	458	Test Uplink by click the button for 1 second
459	459
460		-[[image:image-20230802112413-41.png||height="496" width="828"]]
	661	+[[image:image-20240820112404-38.png]]
461	461
462		-[[image:image-20230802112413-42.png]]
	663	+[[image:image-20240820112416-39.png]]
463	463
464		-[[image:image-20230802112413-43.png||height="407" width="825"]]
	665	+[[image:image-20240820112426-40.png]]
465	465
466		-== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
467	467
468		-=== 3.7.1 Create device & Get Credentials ===
469	469
	669	+== 3.7 ThingsBoard.Cloud (via COAP) ==
	670	+
	671	+=== 3.7.1 Configure ThingsBoard ===
	672	+
	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	+
	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"]]
	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	+
	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"]]
	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	+
	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"]]
	698	+
	699	+
	700	+The next steps is to add the recently created uplink converters;
	701	+
	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"]]
	703	+
	704	+
	705	+==== 3.7.1.3 Add COAP Integration ====
	706	+
	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"]]
	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	+
	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"]]
	721	+
	722	+Note:The port for the COAP protocol has been fixed to 5683
	723	+
	724	+
	725	+* AT+URL1=11,"i"
	726	+* AT+URL2=11,"Needs to be consistent with the CoAP endpoint URL in the platform"
	727	+*
	728	+
	729	+-CB devices using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
	730	+
	731	+e.g.
	732	+
	733	+* AT+URL1=11, "i"
	734	+* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
	735	+
	736	+
	737	+[[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"]]
	738	+
	739	+
	740	+== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
	741	+
	742	+=== 3.8.1 Create device & Get Credentials ===
	743	+
	744	+
470	470	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.
471	471
472		-[[image:image-20230802112413-44.png]]
	747	+[[image:image-20240820112516-41.png]]
473	473
474		-[[image:image-20230802112413-45.png]]
	749	+[[image:image-20240820112526-42.png]]
475	475
476	476	Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
477	477
478		-[[image:image-20230802112413-46.png]]
	753	+[[image:image-20240820112539-43.png]]
479	479
480	480	The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
481	481
...	...	@@ -513,50 +513,59 @@
513	513
514	514	* (% style="color:#037691" %)**AT+PWD=“Your device token”**
515	515
516		-=== 3.7.2 Simulate with MQTT.fx ===
	791	+=== 3.8.2 Simulate with MQTT.fx ===
517	517
518		-[[image:image-20230802112413-52.png]]
519	519
520		-[[image:image-20230808105300-2.png||height="553" width="1026"]]
	794	+[[image:image-20240820112552-44.png]]
521	521
	796	+[[image:image-20240820112604-45.png]]
	797	+
522	522	Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
523	523
524		-[[image:image-20230808105217-1.png||height="556" width="1031"]]
	800	+[[image:image-20240820112615-46.png]]
525	525
526		-[[image:image-20230808105329-3.png]]
	802	+[[image:image-20240820112626-47.png]]
527	527
528		-=== 3.7.3 tago data ===
529	529
530		-[[image:image-20230802112413-50.png||height="242" width="1037"]]
	805	+=== 3.8.3 tago data ===
531	531
532		-[[image:image-20230802112413-51.png||height="184" width="696"]]
533	533
534		-== 3.8 TCP Connection ==
	808	+[[image:image-20240820112637-48.png]]
535	535
	810	+[[image:image-20240820112647-49.png]]
	811	+
	812	+
	813	+== 3.9 TCP Connection ==
	814	+
	815	+
536	536	(% style="color:blue" %)**AT command:**
537	537
538		-* (% style="color:#037691" %)**AT+PRO=4,0 ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
	818	+* (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
539	539
540		-* (% style="color:#037691" %)**AT+PRO=4,1 ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
	820	+* (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
541	541
542	542	* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
543	543
544	544	(% style="color:blue" %)**Sensor Console Output when Uplink:**
545	545
546		-[[image:image-20230807233631-1.png]]
	826	+[[image:image-20240820112704-50.png]]
547	547
548	548	(% style="color:blue" %)**See result in TCP Server:**
549	549
550		-[[image:image-20230807233631-2.png]]
	830	+[[image:image-20240820112716-51.png]]
551	551
552		-== 3.9 AWS Connection ==
553	553
	833	+== 3.10 AWS Connection ==
	834	+
	835	+
554	554	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]]
555	555
556		-= 4. MQTT/UDP/TCP downlink =
557	557
	839	+= 4. COAP/UDP/MQTT/TCP downlink =
	840	+
558	558	== 4.1 MQTT (via MQTT.fx) ==
559	559
	843	+
560	560	Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
561	561
562	562	**1.** Configure node MQTT connection (via MQTT.fx):
...	...	@@ -577,12 +577,14 @@
577	577
578	578	(% 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.**
579	579
580		-[[image:image-20240417180145-2.png||height="434" width="587"]][[ width="584"]]
	864	+[[image:image-20240820112732-52.png]][[image:image-20240820112758-53.png]]
581	581
	866	+
582	582	**2. **When the node uplink packets, we can observe the data in MQTT.fx.
583	583
584		-[[image:image-20240418144337-1.png||height="709" width="802"]]
	869	+[[image:image-20240820112813-54.png]]
585	585
	871	+
586	586	**3. **The downlink command can be successfully sent only when the downlink port is open.
587	587
588	588	The downlink port is opened for about 3 seconds after uplink packets are sent.
...	...	@@ -589,16 +589,69 @@
589	589
590	590	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.
591	591
592		-[[image:image-20240418150435-3.png||height="582" width="659"]]
	878	+[[image:image-20240820112824-55.png]]
593	593
594		-[[image:image-20240418150932-4.png||height="492" width="1061"]]
	880	+[[image:image-20240820112835-56.png]]
595	595
596	596	(% 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.**
597	597
598		-= 5. FAQ =
599	599
600		-== 5.1 What is the usage of Multi Sampling and One Uplink? ==
	885	+== 4.2 UDP (via Thingseye) ==
601	601
	887	+
	888	+(% 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/]])
	889	+
	890	+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)
	891	+
	892	+[[image:image-20240820141843-2.png||height="546" width="821"]]
	893	+
	894	+After clicking Show Node Details Page, (% style="color:blue" %)**Select Properties ~-~-- select Shared Properties ~-~-- click Add Properties**
	895	+
	896	+[[image:image-20240820143316-3.png||height="555" width="1170"]]
	897	+
	898	+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
	899	+
	900	+(% style="color:red" %)**(Note: Downlinks can only be downlinked in string format, otherwise the node will not recognize the downlink command.)**
	901	+
	902	+[[image:image-20240820143820-4.png||height="554" width="1168"]]
	903	+
	904	+After the command is successfully added, the platform will send the command down on the node's next uplink.
	905	+
	906	+[[image:image-20240820144913-6.png||height="585" width="1232"]]
	907	+
	908	+[[image:image-20240820145133-7.png||height="582" width="1227"]]
	909	+
	910	+Upon successful issuance, the platform automatically eliminates the attributes from the queue and waits for the next addition of new attributes
	911	+
	912	+[[image:image-20240820145309-8.png]]
	913	+
	914	+
	915	+= 5. GPS positioning function =
	916	+
	917	+== 1. Turn on GPS function ==
	918	+
	919	+
	920	+(% class="wikigeneratedid" %)
	921	+AT+GPS=1 or 0  ~/~/ GPS function on or off
	922	+
	923	+
	924	+== 2. Extend the time to turn on GNSS ==
	925	+
	926	+
	927	+AT+GNSST=30  ~/~/ GPS search for positioning information for 30 seconds
	928	+
	929	+
	930	+== 3. Get or set GPS positioning interval in units of hour ==
	931	+
	932	+
	933	+AT+GTDC=24  ~/~/ The device will activate GPS positioning every 24 hours
	934	+
	935	+
	936	+= 6. FAQ =
	937	+
	938	+== 6.1 What is the usage of Multi Sampling and One Uplink? ==
	939	+
	940	+
602	602	The NB series has the feature for Multi Sampling and one uplink. See one of them
603	603
604	604	[[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]]
...	...	@@ -613,27 +613,30 @@
613	613	1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours.
614	614	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.
615	615
616		-== 5.2 Why the uplink JSON format is not standard? ==
	955	+== 6.2 Why the uplink JSON format is not standard? ==
617	617
	957	+
618	618	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.
619	619
620	620	The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
621	621
622		-[[image:image-20240229233154-1.png]]
	962	+[[image:image-20240820112848-57.png]]
623	623
624		-= 6. Trouble Shooting: =
625	625
626		-== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
	965	+= 7. Trouble Shooting: =
627	627
	967	+== 7.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
	968	+
	969	+
628	628	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.
629	629
630	630	If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
631	631
632		-[[image:image-20240207002003-1.png]]
	974	+[[image:image-20240820112859-58.png]]
633	633
634	634	If fail to attach network, it will shows signal 99. as below:
635	635
636		-[[image:image-20240207002129-2.png]]
	978	+[[image:image-20240820112908-59.png]]
637	637
638	638	(% class="lead" %)
639	639	When see this issue, below are the checklist:
...	...	@@ -646,52 +646,17 @@
646	646
647	647	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.
648	648
649		-== 6.2 Issue: "NBIOT did not respond" ==
650	650
651		-(% class="box errormessage" %)
652		-(((
653		-11:24:22.397 [44596]NBIOT did not respond.
654		-11:24:24.315 [46530]NBIOT did not respond.
655		-11:24:26.256 [48464]NBIOT did not respond.
656		-11:24:28.196 [50398]NBIOT did not respond.
657		-11:24:30.115 [52332]NBIOT did not respond.
658		-11:24:32.127 [54266]NBIOT did not respond.
659		-11:24:32.127 [54299]Restart the module...
660		-11:24:39.181 [61332]No response when shutting down
661		-)))
	992	+== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.2 Why sometime the AT Command is slow in reponse?(%%) ==
662	662
663		-This issue might due to initiate issue for NB-IoT module. In this case, please try:
664	664
665		-1) Open Enclosure
666		-
667		-2) Power off device by pull out the power on Jumper
668		-
669		-3) Power on device by connect back the power jumper.
670		-
671		-4) push reset button.
672		-
673		-[[image:image-20240208001740-1.png]]
674		-
675		-== 6.3 Issue: "Failed to readI MSI number" ==
676		-
677		-(% class="box errormessage" %)
678		-(((
679		-[18170]Failed to read IMSI:1umber.
680		-[20109]Failed to read IMSI numoer.
681		-[22048]Failed to read IMSI number.
682		-[29842lRestart the module...
683		-)))
684		-
685		-Make sure that the SIM card is insert in correct direction and device is power off/on during insert. Here is reference link: [[Insert SIM Card>>||anchor="H2.1GeneralConfiguretoattachnetwork"]].
686		-
687		-== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
688		-
689	689	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.
690	690
691		-[[image:image-20240226111928-1.png]]
	997	+[[image:image-20240820113015-60.png]]
692	692
693		-== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
694	694
	1000	+== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.3 What is the Downlink Command by the -CB device?(%%) ==
	1001	+
695	695	(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
696	696	=== UDP: ===
697	697
...	...	@@ -701,6 +701,7 @@
701	701
702	702	{AT+TDC=300}
703	703
	1011	+
704	704	(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
705	705	=== MQTT: ===
706	706
...	...	@@ -742,5 +742,136 @@
742	742
743	743	[[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/]]
744	744
	1053	+
	1054	+== 7.4 What if the signal is good but the domain name resolution fails? ==
	1055	+
	1056	+
	1057	+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.
	1058	+
	1059	+[[image:image-20240827150705-6.png||height="489" width="687"]]
	1060	+
	1061	+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.
	1062	+
	1063	+* Set the DNS
	1064	+
	1065	+(% style="color:blue" %)**AT Command: AT+GDNS**
	1066	+
	1067	+**AT+GDNS=0**  ~/~/ Default. Automatically resolves the domain name and uses the resolved IP to communicate.
	1068	+
	1069	+**AT+GDNS=1    **~/~/ Disabling Domain name resolution. Use the domain name directly to communicate.
	1070	+
	1071	+(% style="color:red" %)**Note: For -CB products, with the exception of AT+PRO=2,5, all protocols and payload formats support direct domain communication.**
	1072	+
	1073	+Example:
	1074	+
	1075	+[[image:image-20240827150121-5.png||height="476" width="680"]][[image:image-20240827145055-4.png||height="484" width="678"]]
	1076	+
	1077	+
	1078	+== 7.5 GPS debugging ==
	1079	+
	1080	+
	1081	+Indoor GPS signal is very weak, **outdoor** positioning is generally recommended.
	1082	+
	1083	+[[image:image-20240903104250-9.png||height="275" width="614"]]
	1084	+
	1085	+
	1086	+[[image:image-20240903104431-10.png||height="291" width="621"]]
	1087	+
	1088	+
	1089	+=== 7.5.1 GPS commands ===
	1090	+
	1091	+
	1092	+The following are three related AT commands that introduce GPS functions.
	1093	+
	1094	+* **Turn on/off GPS**
	1095	+
	1096	+(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GPS **
	1097	+
	1098	+**Ex1:  **AT+GPS=0  ~/~/ Turn off GPS
	1099	+
	1100	+**Ex2:  **AT+GPS=1  ~/~/ Turn on GPS
	1101	+
	1102	+(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x11(%%)**
	1103	+
	1104	+Format: Command Code (0x11) followed by 1 byte.
	1105	+
	1106	+Example:  Downlink Payload: **11 01   **~/~/ AT+GPS=1
	1107	+
	1108	+* **Set GNSS open time**
	1109	+
	1110	+Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated.
	1111	+
	1112	+(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GNSST**
	1113	+
	1114	+Example: AT+GNSST=30  ~/~/ Set the GPS positioning time to 30 seconds
	1115	+
	1116	+(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x10(%%)**
	1117	+
	1118	+Format: Command Code (0x10) followed by 2 bytes.
	1119	+
	1120	+Example:  Downlink Payload: **10 00 1E    **~/~/ AT+GNSST=30
	1121	+
	1122	+* **Set GPS positioning interval**
	1123	+
	1124	+Feature: Set GPS positioning interval (unit: hour).
	1125	+
	1126	+When GPS is enabled, the node automatically locates and uplinks each time it passes **GTDC time** after activation.
	1127	+
	1128	+(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GTDC**
	1129	+
	1130	+Example: AT+GTDC=24  ~/~/ Set the GPS positioning interval to 24h.
	1131	+
	1132	+(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x12(%%)**
	1133	+
	1134	+Format: Command Code (0x12) followed by 3 bytes.
	1135	+
	1136	+Example: 24 hours:  24(D)=0x18(H)
	1137	+
	1138	+Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
	1139	+
	1140	+
	1141	+=== 7.5.2 GPS workflow ===
	1142	+
	1143	+
	1144	+The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
	1145	+
	1146	+~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.
	1147	+
	1148	+ 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.
	1149	+
	1150	+ So if there is a failure of positioning, the user can extend the (% style="color:#037691" %)**GNSST**(%%) time appropriately.
	1151	+
	1152	+2. Each TDC time node is not repositioned and the positioning interval is determined by the AT+GTDC time.
	1153	+
	1154	+ The latitude and longitude payload uplinked at each TDC time is the GPS positioning information from the previous (% style="color:#037691" %)**GTDC**(%%) time.
	1155	+
	1156	+ 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.
	1157	+
	1158	+
	1159	+=== 7.5.3 GPS debugging methods ===
	1160	+
	1161	+
	1162	+In summary, we can deduce the methods of debugging GPS:
	1163	+
	1164	+* **Check whether the GPS function is enabled.**
	1165	+
	1166	+[[image:image-20240903102327-5.png||height="271" width="529"]]
	1167	+
	1168	+* **Check whether the GPS antenna is loose**.
	1169	+
	1170	+If the GPS antenna is loose, the GPS signal is weak, and the positioning fails.
	1171	+
	1172	+[[image:image-20240903094214-1.png||height="340" width="461"]]
	1173	+
	1174	+* **Use the AT+GNSST command to extend the positioning time.**
	1175	+
	1176	+The default AT+GNSST=30, that is, the default positioning time is 30 seconds.
	1177	+
	1178	+If the location fails, users can extend the location time.
	1179	+
	1180	+[[image:image-20240903102641-8.png||height="303" width="600"]]
	1181	+
	1182	+
	1183	+
	1184	+
745	745
746		-​

image-20240602220856-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Edwin

Size

...	...	@@ -1,0 +1,1 @@
	1	+250.9 KB

Content

image-20240819102802-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+41.5 KB

Content

image-20240819103212-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+49.5 KB

Content

image-20240819103826-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+122.4 KB

Content

image-20240819103909-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+122.2 KB

Content

image-20240819104904-5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+52.1 KB

Content

image-20240819104942-6.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+52.1 KB

Content

image-20240819105003-7.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+48.2 KB

Content

image-20240819105418-8.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+163.8 KB

Content

image-20240819112109-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+12.9 KB

Content

image-20240819173602-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+52.3 KB

Content

image-20240819173659-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+44.8 KB

Content

image-20240819173706-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+44.8 KB

Content

image-20240819173826-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+42.3 KB

Content

image-20240819174033-5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+33.1 KB

Content

image-20240819174209-6.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+18.9 KB

Content

image-20240819174314-7.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+48.4 KB

Content

image-20240819174540-8.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+99.8 KB

Content

image-20240819174610-9.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+127.8 KB

Content

image-20240819174618-10.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+34.6 KB

Content

image-20240820110003-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+66.5 KB

Content

image-20240820110017-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+78.3 KB

Content

image-20240820110031-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+59.2 KB

Content

image-20240820110048-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+64.0 KB

Content

image-20240820110103-5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+71.6 KB

Content

image-20240820110114-6.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+77.4 KB

Content

image-20240820110129-7.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+10.7 KB

Content

image-20240820110142-8.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+54.1 KB

Content

image-20240820110218-9.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+66.7 KB

Content

image-20240820110235-10.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+21.2 KB

Content

image-20240820110247-11.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+49.8 KB

Content

image-20240820111016-12.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+65.8 KB

Content

image-20240820111101-13.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+36.3 KB

Content

image-20240820111113-14.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+55.7 KB

Content

image-20240820111236-15.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+42.0 KB

Content

image-20240820111248-16.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+58.4 KB

Content

image-20240820111259-17.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+58.0 KB

Content

image-20240820111312-18.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+13.9 KB

Content

image-20240820111322-19.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+68.2 KB

Content

image-20240820111333-20.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+47.0 KB

Content

image-20240820111353-21.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+82.5 KB

Content

image-20240820111405-22.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+57.6 KB

Content

image-20240820111418-23.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+41.0 KB

Content

image-20240820111427-24.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+46.8 KB

Content

image-20240820111438-25.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+139.6 KB

Content

image-20240820111448-26.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+58.0 KB

Content

image-20240820111504-27.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+85.1 KB

Content

image-20240820111515-28.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+45.3 KB

Content

image-20240820112210-29.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+96.9 KB

Content

image-20240820112222-30.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+149.6 KB

Content

image-20240820112236-31.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+170.6 KB

Content

image-20240820112247-32.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+105.5 KB

Content

image-20240820112302-33.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+112.9 KB

Content

image-20240820112316-34.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+96.4 KB

Content

image-20240820112330-35.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+127.0 KB

Content

image-20240820112340-36.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+24.7 KB

Content

image-20240820112351-37.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+68.4 KB

Content

image-20240820112404-38.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+40.2 KB

Content

image-20240820112416-39.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+40.9 KB

Content

image-20240820112426-40.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+101.4 KB

Content

image-20240820112516-41.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+78.6 KB

Content

image-20240820112526-42.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+128.5 KB

Content

image-20240820112539-43.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+31.2 KB

Content

image-20240820112552-44.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+28.4 KB

Content

image-20240820112604-45.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+60.9 KB

Content

image-20240820112615-46.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+60.5 KB

Content

image-20240820112626-47.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+21.1 KB

Content

image-20240820112637-48.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+53.1 KB

Content

image-20240820112647-49.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+37.8 KB

Content

image-20240820112704-50.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+21.9 KB

Content

image-20240820112716-51.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+9.6 KB

Content

image-20240820112732-52.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+95.3 KB

Content

image-20240820112758-53.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+34.7 KB

Content

image-20240820112813-54.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+127.7 KB

Content

image-20240820112824-55.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+24.0 KB

Content

image-20240820112835-56.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+70.6 KB

Content

image-20240820112848-57.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+39.5 KB

Content

image-20240820112859-58.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+22.3 KB

Content

image-20240820112908-59.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+17.9 KB

Content

image-20240820113015-60.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+52.0 KB

Content

image-20240820140935-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+159.2 KB

Content

image-20240820141136-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+107.6 KB

Content

image-20240820141746-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+122.2 KB

Content

image-20240820141843-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+123.2 KB

Content

image-20240820143316-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+152.3 KB

Content

image-20240820143820-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+161.7 KB

Content

image-20240820144823-5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+145.6 KB

Content

image-20240820144913-6.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+136.4 KB

Content

image-20240820145133-7.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+164.5 KB

Content

image-20240820145309-8.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+32.6 KB

Content

image-20240827145055-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+74.2 KB

Content

image-20240827150121-5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+86.0 KB

Content

image-20240827150705-6.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+86.7 KB

Content

image-20240903094214-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+4.5 MB

Content

image-20240903094457-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+2.6 MB

Content

image-20240903100736-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+250.8 KB

Content

image-20240903100832-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+181.5 KB

Content

image-20240903102327-5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+26.2 KB

Content

image-20240903102542-6.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+16.9 KB

Content

image-20240903102621-7.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+21.9 KB

Content

image-20240903102641-8.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+21.0 KB

Content

image-20240903104250-9.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+46.9 KB

Content

image-20240903104431-10.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+49.2 KB

Content