Changes for page General Configure/Commands to Connect to IoT server for -NB & -NS NB-IoT models

Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 66 added, 0 removed)
  • image-20230807233631-1.png
  • image-20230807233631-2.png
  • image-20230808105217-1.png
  • image-20230808105300-2.png
  • image-20230808105329-3.png
  • image-20230808162301-1.png
  • image-20230808162342-2.png
  • image-20230808162421-3.png
  • image-20230808162727-4.png
  • image-20230808163035-5.png
  • image-20230808163049-6.png
  • image-20230808163612-7.png
  • image-20230808170051-8.png
  • image-20230808170548-9.png
  • image-20230808205045-1.png
  • image-20230809165928-1.png
  • image-20230809170225-2.png
  • image-20230809170532-3.png
  • image-20230809173127-4.png
  • image-20230809173310-5.png
  • image-20230809173438-6.png
  • image-20230809173800-7.png
  • image-20230809173835-8.png
  • image-20230809174053-9.png
  • image-20230809180523-10.png
  • image-20230810083934-1.png
  • image-20230810084048-2.png
  • image-20230816201942-1.png
  • image-20240129170024-1.png
  • image-20240129170216-2.png
  • image-20240129170539-3.png
  • image-20240129171029-4.png
  • image-20240129171113-5.png
  • image-20240129171236-6.png
  • image-20240129172056-7.png
  • image-20240129172136-8.png
  • image-20240129173116-9.png
  • image-20240129173541-10.png
  • image-20240129174518-11.png
  • image-20240129174657-12.png
  • image-20240129174840-13.png
  • image-20240202111546-1.png
  • image-20240207002003-1.png
  • image-20240207002129-2.png
  • image-20240208001740-1.png
  • image-20240208102804-1.png
  • image-20240226111928-1.png
  • image-20240229233154-1.png
  • image-20240417173549-1.png
  • image-20240417180145-2.png
  • image-20240417180737-3.png
  • image-20240418144337-1.png
  • image-20240418144714-2.png
  • image-20240418150435-3.png
  • image-20240418150932-4.png
  • image-20240701114700-1.png
  • image-20240729141300-1.png
  • image-20240729142505-3.png
  • image-20240729144058-4.png
  • image-20240729150142-5.png
  • image-20240729160802-7.png
  • image-20240729161543-9.png
  • image-20240729172234-11.png
  • image-20240729172305-12.png
  • image-20240729172415-13.png
  • image-20240729172500-14.png

Details

Page properties

Author

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

Content

...	...	@@ -1,9 +1,13 @@
1		-(% class="wikigeneratedid" %)
	1	+(% class="wikigeneratedid" id="HTableofContents:" %)
2	2	**Table of Contents:**
3	3
4	4	{{toc/}}
5	5
6	6
	7	+
	8	+
	9	+
	10	+
7	7	= 1. The use of this guideline =
8	8
9	9
...	...	@@ -12,28 +12,57 @@
12	12
13	13	= 2. Attach Network =
14	14
	19	+== 2.1 General Configure to attach network ==
15	15
	21	+
16	16	To attache NB-IoT sensors to NB-IoT Network, You need to:
17	17
18	18	1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
19		-1. Insert the SIM card to Sensor
20		-1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor
	25	+1. Power Off End Node ( See below for the power off/on position)
	26	+1. Insert the SIM card to Sensor. ( See below for direction)
	27	+1. Power On End Node
	28	+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
21	21
	30	+[[image:image-20240208102804-1.png||height="286" width="696"]]
	31	+
	32	+[[image:image-20230808205045-1.png||height="293" width="438"]]
	33	+
22	22	After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
23	23
24	24	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.
25	25
26	26	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
27		-|(% style="background-color:#4f81bd; color:white; width:114px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:154px" %)**APN**|(% style="background-color:#4f81bd; color:white; width:474px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
28		-|(% style="width:114px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:154px" %)iot.1nce.net|(% style="width:474px" %)(((
	39	+|(% 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**
	40	+|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
29	29	**[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
30	30
31		-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, US Virgin Islands
32		-)))|(% style="width:135px" %)
33		-|(% style="width:114px" %)China Mobile|(% style="width:154px" %) |(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
34		-|(% style="width:114px" %)China Telecom|(% style="width:154px" %) |(% style="width:474px" %)China Mainland|(% style="width:135px" %)
	43	+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
	44	+)))|(% style="width:135px" %)UK: Band20
	45	+|(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
	46	+|(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
35	35
	48	+== 2.2 Speed Up Network Attach time ==
36	36
	50	+
	51	+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.
	52	+
	53	+(% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
	54	+(% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
	55	+(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
	56	+(% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=10,8,20,28,2,4,12,13,66,85,5**
	57	+
	58	+(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
	59	+(% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
	60	+(% style="color:#037691" %)**Telstra**(%%)        AT+QBAND=1,28
	61	+(% style="color:#037691" %)**Softband**(%%)     AT+QBAND=2,3,8
	62	+
	63	+After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
	64	+
	65	+By default, device will search network for 5 minutes. User can set the time to 10 minutes by (% style="color:#037691" %)**AT+CSQTIME=10 **(%%)so it can search longer.
	66	+
	67	+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/]]**
	68	+
	69	+
37	37	= 3. Configure to connect to different servers =
38	38
39	39	== 3.1 General UDP Connection ==
...	...	@@ -47,7 +47,7 @@
47	47
48	48	We can use PC tool to simulate UDP connection to make sure server works ok.
49	49
50		-[[image:image-20230802112413-1.png]]
	83	+[[image:image-20230802112413-1.png||height="468" width="1024"]]
51	51
52	52
53	53	=== 3.1.2 Configure NB-IoT Sensor ===
...	...	@@ -61,8 +61,6 @@
61	61
62	62	* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
63	63
64		-* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
65		-
66	66	[[image:image-20230802112413-2.png]]
67	67
68	68
...	...	@@ -97,7 +97,7 @@
97	97
98	98	[[image:image-20230802112413-4.png]]
99	99
100		-[[image:image-20230802112413-5.png]]
	131	+[[image:image-20230802112413-5.png||height="530" width="987"]]
101	101
102	102	(% 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.**
103	103
...	...	@@ -109,7 +109,7 @@
109	109
110	110	[[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.
111	111
112		-[[image:image-20230802112413-6.png]]
	143	+[[image:image-20230802112413-6.png||height="336" width="925"]]
113	113
114	114	[[image:image-20230802112413-7.png]]
115	115
...	...	@@ -133,6 +133,8 @@
133	133
134	134	* (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
135	135
	167	+
	168	+
136	136	==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
137	137
138	138
...	...	@@ -152,7 +152,7 @@
152	152
153	153	(% style="color:blue" %)**Result: **
154	154
155		-[[image:image-20230802112413-11.png]]
	188	+[[image:image-20230802112413-11.png||height="539" width="901"]]
156	156
157	157
158	158	=== 3.3.3 Configure NB-IoT Sensor for connection ===
...	...	@@ -174,10 +174,12 @@
174	174
175	175	* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
176	176
	210	+
	211	+
177	177	==== 3.3.3.2 Uplink Examples ====
178	178
179	179
180		-For S31-NB
	215	+[[image:image-20230816201942-1.png]]
181	181
182	182	For SE01-NB
183	183
...	...	@@ -208,186 +208,222 @@
208	208	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.
209	209
210	210
211		-[[image:image-20230802112413-12.png]]
	246	+[[image:image-20230802112413-12.png||height="504" width="1011"]]
212	212
213		-[[image:image-20230802112413-13.png]]
	248	+[[image:image-20230802112413-13.png||height="331" width="978"]]
214	214
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:1386px" %)
219		-|(% style="background-color:#4f81bd; width:124px" %) |(% style="background-color:#4f81bd; color:white; width:91px" %)Field1|(% style="background-color:#4f81bd; color:white; width:102px" %)Field2|(% style="background-color:#4f81bd; color:white; width:159px" %)Field3|(% style="background-color:#4f81bd; color:white; width:153px" %)Field4|(% style="background-color:#4f81bd; color:white; width:152px" %)Field5|(% style="background-color:#4f81bd; color:white; width:148px" %)Field6|(% style="background-color:#4f81bd; color:white; width:164px" %)Field7|(% style="background-color:#4f81bd; color:white; width:152px" %)Field8|(% style="background-color:#4f81bd; color:white; width:66px" %)Field9|(% style="background-color:#4f81bd; color:white; width:66px" %)Field10
220		-|(% style="background-color:#4f81bd; color:white; width:124px" %)S31x-NB|(% style="width:91px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:159px" %)Battery|(% style="width:153px" %)RSSI|(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
221		-|(% style="background-color:#4f81bd; color:white; width:124px" %)SE01-NB|(% style="width:91px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:159px" %)conduct|(% style="width:153px" %)dielectric_constant|(% style="width:152px" %)Battery|(% style="width:148px" %)RSSI|(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
222		-|(% style="background-color:#4f81bd; color:white; width:124px" %)DDS20-NB|(% style="width:91px" %)distance|(% style="width:102px" %)Battery|(% style="width:159px" %)RSSI|(% style="width:153px" %) |(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
223		-|(% style="background-color:#4f81bd; color:white; width:124px" %)DDS45-NB|(% style="width:91px" %)distance|(% style="width:102px" %)Battery|(% style="width:159px" %)RSSI|(% style="width:153px" %) |(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
224		-|(% style="background-color:#4f81bd; color:white; width:124px" %)DDS75-NB|(% style="width:91px" %)distance|(% style="width:102px" %)Battery|(% style="width:159px" %)RSSI|(% style="width:153px" %) |(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
225		-|(% style="background-color:#4f81bd; color:white; width:124px" %)NMDS120-NB|(% style="width:91px" %)distance|(% style="width:102px" %)Battery|(% style="width:159px" %)RSSI|(% style="width:153px" %) |(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
226		-|(% rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SPH01-NB|(% style="width:91px" %)ph|(% style="width:102px" %)Temperature|(% style="width:159px" %)Battery|(% style="width:153px" %)RSSI|(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% colspan="1" rowspan="1" style="width:66px" %)
227		-|(% style="background-color:#4f81bd; color:white; width:124px" %)NLM01-NB|(% style="width:91px" %)Humidity|(% style="width:102px" %)Temperature|(% style="width:159px" %)Battery|(% style="width:153px" %)RSSI|(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
228		-|(% style="background-color:#4f81bd; color:white; width:124px" %)NMDS200-NB|(% style="width:91px" %)distance1|(% style="width:102px" %)distance2|(% style="width:159px" %)Battery|(% style="width:153px" %)RSSI|(% style="width:152px" %) |(% style="width:148px" %) |(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
229		-|(% style="background-color:#4f81bd; color:white; width:124px" %)CPN01-NB|(% style="width:91px" %)alarm|(% style="width:102px" %)count|(% style="width:159px" %)door open duration|(% style="width:153px" %)calc flag|(% style="width:152px" %)Battery|(% style="width:148px" %)RSSI|(% style="width:164px" %) |(% style="width:152px" %) |(% style="width:66px" %) |(% style="width:66px" %)
230		-|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)DS03A-NB|(% colspan="1" rowspan="1" style="width:91px" %)level|(% colspan="1" rowspan="1" style="width:102px" %)alarm|(% colspan="1" rowspan="1" style="width:159px" %)pb14door open num|(% colspan="1" rowspan="1" style="width:153px" %)pb14 last open time|(% colspan="1" rowspan="1" style="width:152px" %)pb15 level status|(% colspan="1" rowspan="1" style="width:148px" %)pb15 alarm status|(% colspan="1" rowspan="1" style="width:164px" %)pb15 door open num|(% colspan="1" rowspan="1" style="width:152px" %)pb15 last open time|(% colspan="1" rowspan="1" style="width:66px" %)Battery|(% colspan="1" rowspan="1" style="width:66px" %)RSSI
231		-|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)SN50V3-NB|(% colspan="1" rowspan="1" style="width:91px" %) |(% colspan="1" rowspan="1" style="width:102px" %) |(% colspan="1" rowspan="1" style="width:159px" %) |(% colspan="1" rowspan="1" style="width:153px" %) |(% colspan="1" rowspan="1" style="width:152px" %) |(% colspan="1" rowspan="1" style="width:148px" %) |(% colspan="1" rowspan="1" style="width:164px" %) |(% colspan="1" rowspan="1" style="width:152px" %) |(% colspan="1" rowspan="1" style="width:66px" %) |(% colspan="1" rowspan="1" style="width:66px" %)
232		-|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod1|(% colspan="1" rowspan="1" style="width:91px" %)mod|(% colspan="1" rowspan="1" style="width:102px" %)Battery|(% colspan="1" rowspan="1" style="width:159px" %)RSSI|(% colspan="1" rowspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:148px" %)adc0|(% colspan="1" rowspan="1" style="width:164px" %)Temperature |(% colspan="1" rowspan="1" style="width:152px" %)Humidity|(% colspan="1" rowspan="1" style="width:66px" %) |(% colspan="1" rowspan="1" style="width:66px" %)
233		-|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod2|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" style="width:148px" %)adc0|(% colspan="1" style="width:164px" %)distance|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
234		-|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod3|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:152px" %)exit_state/input PA4|(% colspan="1" style="width:148px" %)adc1|(% colspan="1" style="width:164px" %)Temperature|(% colspan="1" style="width:152px" %)Humidity|(% colspan="1" style="width:66px" %)adc4|(% colspan="1" style="width:66px" %)
235		-|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod4|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" style="width:152px" %)adc0|(% colspan="1" style="width:148px" %)exit_state/input PA4|(% colspan="1" style="width:164px" %)DS18B20 Temp2|(% colspan="1" style="width:152px" %)DS18B20 Temp3|(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
236		-|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod5|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)DS18B20 Temp|(% colspan="1" style="width:152px" %)adc0|(% colspan="1" style="width:148px" %)exit_state/input PA4|(% colspan="1" style="width:164px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
237		-|(% colspan="1" style="background-color:#4f81bd; color:white; width:124px" %)mod6|(% colspan="1" style="width:91px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:159px" %)RSSI|(% colspan="1" style="width:153px" %)count|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:148px" %) |(% colspan="1" style="width:164px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:66px" %) |(% colspan="1" style="width:66px" %)
	253	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
	254	+|(% 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
	255	+|(% 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" %)
	256	+|(% 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" %)
	257	+|(% 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" %)
	258	+|(% 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" %)
	259	+|(% 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" %)
	260	+|(% 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" %)
	261	+|(% 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" %)
	262	+|(% 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" %)
	263	+|(% 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" %)
	264	+|(% 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" %)
	265	+|(% 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
	266	+|(% 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" %)
	267	+|(% 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" %)
	268	+|(% 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" %)
	269	+|(% 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" %)
	270	+|(% 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" %)
	271	+|(% 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" %)
238	238
239		-== 3.4 Datacake ==
240	240
241		-=== 3.4.1 Define Product ===
	274	+== 3.4 [[Datacake>>https://datacake.co/]] ==
242	242
243	243
244		-Firstly, we need to set the MQTT mode to datacake, and we need to run(% style="color:blue" %)** AT+PRO=3,2**(%%). This command is set to datacake. After running the command, the device automatically sets the server address, port.
	277	+(% class="wikigeneratedid" %)
	278	+Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
245	245
246		-By chosing to add the device under a (% style="color:blue" %)**"New Product"**(%%) you are required to give a name for this product. You can name it something like (% style="color:blue" %)**"My First MQTT Product"**.
247	247
248		-[[image:image-20230802112413-14.png||height="1095" width="1302"]]
	281	+(% class="wikigeneratedid" %)
	282	+As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
249	249
	284	+* (% 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.
250	250
251		-=== 3.4.2 Create Device ===
	286	+* (% 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.
252	252
253	253
254		-In the second step you have to define the device which should be added to the product.
255	255
256		-[[image:image-20230802112413-15.png||height="859" width="1290"]]
	290	+=== 3.4.1 For device Already has template ===
257	257
258		-Enter a name here (such as "My First MQTT Device") and complete the creation of the device by clicking on the (% style="color:blue" %)**"Next"**(%%) button.
	292	+==== 3.4.1.1 Create Device ====
259	259
260	260
261		-=== 3.4.3 Create Database Fields ===
	295	+(% style="color:blue" %)**Add Device**(%%) in DataCake.
262	262
	297	+[[image:image-20230808162301-1.png||height="453" width="952"]]
263	263
264		-After creating the device, it is listed in the table of the fleet view. Now open the device by clicking on the entry in the list.
265	265
266		-You will then see a device view with an empty dashboard. Now, the first thing we want to do is navigate to the Device configuration. To do this, use the tab bar and click on (% style="color:blue" %)**"Configuration"**.
	300	+[[image:image-20230808162342-2.png||height="541" width="952"]]
267	267
268		-[[image:image-20230802112413-16.png||height="495" width="1310"]]
269	269
270		-[[image:image-20230802112413-17.png||height="741" width="1303"]]
	303	+(% style="color:blue" %)**Choose the correct model**(%%) from template.
271	271
272		-To create a first database field, please click on the (% style="color:blue" %)**"Add Field"**(%%) button as marked in the screenshot above.
	305	+[[image:image-20230808162421-3.png]]
273	273
274		-This will open another modal asking for some required input for your first field.
275	275
276		-[[image:image-20230802112413-18.png||height="878" width="1305"]]
	308	+(% 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.
277	277
278		-[[image:image-20230802112413-19.png]]
	310	+[[image:image-20230808163612-7.png||height="549" width="952"]]
279	279
	312	+[[image:image-20230808163035-5.png]]
280	280
281		-=== 3.4.4 Set up Broker ===
	314	+[[image:image-20230808163049-6.png||height="544" width="926"]]
282	282
283	283
284		-The broker is running on mqtt.datacake.co on ports (% style="color:blue" %)**1883 and 8883**(%%). Port 1883 is unsecured and should not be used in production environments. Port 8883 uses a CA signed server certificate.
	317	+=== 3.4.2 For Device already registered in DataCake before shipped ===
285	285
286		-You will need an access token to log into the Datacake MQTT Broker. You can use your own personal token or create a token explicitly for individual devices or groups of devices.
	319	+==== 3.4.2.1 Scan QR Code to get the device info ====
287	287
288		-View your Personal Access Token
289	289
290		-You can view your own token via the User-Settings-Menu. You can reach this menu by clicking on (% style="color:blue" %)**"Edit Profile"**(%%) at the end of the list using the Workspace Selector:
	322	+Users can use their phones or computers to scan QR codes to obtain device data information.
291	291
292		-[[image:image-20230802112413-20.png]]
	324	+[[image:image-20230808170051-8.png||height="255" width="259"]]
293	293
	326	+[[image:image-20230808170548-9.png]]
294	294
295		-(% style="color:blue" %)**MQTT Client-ID**
296	296
297		-The Datacake Broker manages the client IDs internally. You do not need to worry about a client ID. If your client optionally supports the specification of a client ID, please leave this
298		-specification blank. Your client then creates a randomly generated ID.
	329	+==== 3.4.2.2 Claim Device to User Account ====
299	299
300		-* (% style="color:blue" %)**AT+CLIENT=“Any value”**
301	301
302		-* (% style="color:blue" %)**AT+UNAME=Token**
	332	+By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
303	303
304		-* (% style="color:blue" %)**AT+PWD=Token**
305	305
306		-[[image:image-20230802112413-21.png]]
	335	+=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
307	307
308	308
309		-=== 3.4.5 Create your first Subscription ===
	338	+**Step1: Add a device**
310	310
	340	+[[image:image-20240129170024-1.png||height="330" width="900"]]
311	311
312		-(% style="color:blue" %)**Subscribe**
313	313
314		-Data is published according to the following structure: (% style="color:blue" %)**dtck~/~//**(%%)** **
	343	+**Step2: Choose your device type,please select dragino NB-IOT device**
315	315
316		-Subscribe to topics using this structure to receive messages via MQTT when readings (via API or MQTT) arrive in the Datacake Cloud. Messages are published whenever there is a change to a corresponding database field.
	345	+[[image:image-20240129170216-2.png||height="534" width="643"]]
317	317
318	318
319		-[[image:image-20230802112413-22.png]]
	348	+**Step3: Choose to create a new device**
320	320
	350	+[[image:image-20240129170539-3.png||height="459" width="646"]]
321	321
322		-[[image:image-20230802112413-23.png]]
323	323
	353	+**Step4: Fill in the device ID of your NB device**
324	324
325		-[[image:image-20230802112413-24.png]]
	355	+[[image:image-20240202111546-1.png||height="378" width="651"]]
326	326
327	327
328		-(% style="color:blue" %)**example:**
	358	+**Step5: Please select your device plan according to your needs and complete the creation of the device**
329	329
330		-AT+PUBTOPIC=dtck-pub/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
	360	+[[image:image-20240129171236-6.png||height="450" width="648"]]
331	331
332		-[[image:image-20230802112413-25.png]]
333	333
	363	+**Step6: Please add the decoder at the payload decoder of the device configuration.**
334	334
335		-=== 3.4.6 Define Publish Topic ===
	365	+**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]]
336	336
	367	+**Due to version update, please use the following decoder for the new version firmware:**
	368	+[[dragino-end-node-decoder/Datacake-Dragino_NB_New_Version at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB_New_Version]]
337	337
338		-(% style="color:blue" %)**Publish**
	370	+[[image:image-20240129172056-7.png||height="457" width="816"]]
339	339
340		-To upload data into the Datacake Cloud and into a specific device, you publish the data to the respective topic structure.
	372	+[[image:image-20240129173116-9.png||height="499" width="814"]]
341	341
342		-Due to the nature of MQTT, the topic prefix differs as follows: (% style="color:blue" %)**dtck-pub~/~//**
343	343
344		-(% style="color:blue" %)**example:**
	375	+**Step7: Add the output of the decoder as a field**
345	345
346		-AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
	377	+[[image:image-20240129173541-10.png||height="592" width="968"]]
347	347
348	348
349		-=== 3.4.7 upload data ===
	380	+**Step8: Customize the dashboard and use fields as parameters of the dashboard**
350	350
	382	+[[image:image-20240129174518-11.png||height="147" width="1042"]]
351	351
352		-[[image:image-20230802112413-26.png]]
	384	+[[image:image-20240129174657-12.png||height="538" width="916"]]
353	353
354		-[[image:image-20230802112413-27.png]]
	386	+[[image:image-20240129174840-13.png||height="536" width="750"]]
355	355
356		-[[image:image-20230802112413-28.png]]
357	357
	389	+=== 3.4.4 For device have not configured to connect to DataCake ===
358	358
	391	+
	392	+(% class="lead" %)
	393	+Use AT command for connecting to DataCake
	394	+
	395	+(% style="color:blue" %)**AT+PRO=2,0**
	396	+
	397	+(% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
	398	+
	399	+
359	359	== 3.5 Node-Red (via MQTT) ==
360	360
361	361	=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
362	362
363	363
364		-[[image:image-20230802112413-29.png]]
	405	+Take S31-NB UDP protocol as an example.
365	365
	407	+Dragino provides input flow examples for the sensors.
366	366
367		-[[image:image-20230802112413-30.png]]
	409	+User can download the required JSON file through Dragino Node-RED input flow template.
368	368
	411	+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]]
369	369
370		-=== 3.5.2 Simulate Connection ===
	413	+We can directly import the template.
371	371
	415	+The templates for S31-NB and NB95S31B are the same.
372	372
373		-[[image:image-20230802112413-31.png]]
374	374
	418	+[[image:image-20230809173127-4.png]]
375	375
376		-=== 3.5.3 Configure NB-IoT Sensors ===
377	377
	421	+Please select the NB95S31B template.
378	378
379		-* (% style="color:blue" %)**AT+PRO=3,0(hex format) or 3,5(json format)**(%%)    ~/~/  Set to mqtt Server and  Payload
	423	+[[image:image-20230809173310-5.png||height="558" width="926"]]
380	380
381		-* (% style="color:blue" %)**AT+CLIENT=any value**
	425	+[[image:image-20230809173438-6.png]]
382	382
383		-* (% style="color:blue" %)**AT+UNAME=any value**
	427	+[[image:image-20230809173800-7.png]]
384	384
385		-* (% style="color:blue" %)**AT+PWD=any value**
386	386
387		-* (% style="color:blue" %)**AT+PUBTOPIC=any value**
	430	+Successfully imported template.
388	388
389		-* (% style="color:blue" %)**AT+SUBTOPIC=any value**
	432	+[[image:image-20230809173835-8.png||height="515" width="860"]]
390	390
	434	+
	435	+Users can set UDP port.
	436	+
	437	+[[image:image-20230809174053-9.png]]
	438	+
	439	+
	440	+=== 3.5.2 Simulate Connection ===
	441	+
	442	+
	443	+We have completed the configuration of UDP. We can try sending packets to node red.
	444	+
	445	+[[image:image-20230810083934-1.png]]
	446	+
	447	+[[image:image-20230810084048-2.png||height="535" width="1052"]]
	448	+
	449	+
	450	+=== 3.5.3 Configure NB-IoT Sensors ===
	451	+
	452	+
	453	+* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
	454	+* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
	455	+* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
	456	+* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
	457	+* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
	458	+* (% style="color:#037691" %)**AT+PWD=“Your device token”**
	459	+
	460	+
	461	+
391	391	== 3.6 ThingsBoard.Cloud (via MQTT) ==
392	392
393	393	=== 3.6.1 Configure ThingsBoard ===
...	...	@@ -395,9 +395,9 @@
395	395	==== 3.6.1.1 Create Device ====
396	396
397	397
398		-Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]].
	469	+Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
399	399
400		-[[image:image-20230802112413-32.png]]
	471	+[[image:image-20230802112413-32.png||height="583" width="1066"]]
401	401
402	402
403	403	==== 3.6.1.2 Create Uplink & Downlink Converter ====
...	...	@@ -409,7 +409,7 @@
409	409
410	410	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.
411	411
412		-[[image:image-20230802112413-33.png||height="732" width="1302"]]
	483	+[[image:image-20230802112413-33.png||height="597" width="1061"]]
413	413
414	414
415	415	(% style="color:blue" %)**Downlink Converter**
...	...	@@ -416,9 +416,9 @@
416	416
417	417	The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
418	418
419		-[[image:image-20230802112413-34.png||height="734" width="1305"]]
	490	+[[image:image-20230802112413-34.png||height="598" width="1063"]]
420	420
421		-(% style="color:red" %)**Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
	492	+(% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
422	422
423	423
424	424	==== 3.6.1.3 MQTT Integration Setup ====
...	...	@@ -426,23 +426,23 @@
426	426
427	427	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**;
428	428
429		-[[image:image-20230802112413-35.png||height="738" width="1312"]]
	500	+[[image:image-20230802112413-35.png||height="597" width="1062"]]
430	430
431	431
432	432	* The next steps is to add the recently created uplink and downlink converters;
433	433
434		-[[image:image-20230802112413-36.png||height="736" width="1308"]]
	505	+[[image:image-20230802112413-36.png||height="598" width="1062"]]
435	435
436		-[[image:image-20230802112413-37.png||height="735" width="1307"]]
	507	+[[image:image-20230802112413-37.png||height="598" width="1064"]]
437	437
438	438
439	439	(% style="color:blue" %)**Add a topic filter:**
440	440
441		-tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
	512	+Consistent with the theme of the node setting.
442	442
443	443	You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
444	444
445		-[[image:image-20230802112413-38.png||height="731" width="1300"]]
	516	+[[image:image-20230802112413-38.png||height="598" width="1064"]]
446	446
447	447
448	448	=== 3.6.2 Simulate with MQTT.fx ===
...	...	@@ -450,7 +450,7 @@
450	450
451	451	[[image:image-20230802112413-39.png]]
452	452
453		-[[image:image-20230802112413-40.png]]
	524	+[[image:image-20230802112413-40.png||height="525" width="980"]]
454	454
455	455
456	456	=== 3.6.3 Configure NB-IoT Sensor ===
...	...	@@ -458,35 +458,109 @@
458	458
459	459	(% style="color:blue" %)**AT Commands**
460	460
461		-* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard.
	532	+* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
462	462
463		-* (% style="color:#037691" %)**AT+SUBTOPIC=device name** (%%) **~-~-> 只需要 Device Name 吗?对的**
	534	+* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
464	464
465		-* (% style="color:#037691" %)**AT+PUBTOPIC=device name** (%%) **~-~-> 只需要 Device Name 吗?对的**
	536	+* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
466	466
467		-Users do not need to fill in the client, username, and password. But the configuration information of the device requires setting the client, username, and password, which can be entered freely.** (软件自动填充为 Device Name 吧).这边不用提示了，客户不需要输入。（大部分客户还是会自己去设置这个的，提高安全性）**
	538	+* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
468	468
469		-(% style="color:blue" %)**CLIENT :“Any value”**
	540	+* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
470	470
471		-(% style="color:blue" %)**User Name:“Any value”**
	542	+* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
472	472
473		-(% style="color:blue" %)**Password:“Any value”**
474		-
475		-
476	476	Test Uplink by click the button for 1 second
477	477
478		-[[image:image-20230802112413-41.png]]
	546	+[[image:image-20230802112413-41.png||height="496" width="828"]]
479	479
480	480	[[image:image-20230802112413-42.png]]
481	481
482		-[[image:image-20230802112413-43.png]]
	550	+[[image:image-20230802112413-43.png||height="407" width="825"]]
483	483
484	484
485		-== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
	553	+== 3.7 ThingsBoard.Cloud (via COAP) ==
486	486
487		-=== 3.7.1 Create device & Get Credentials ===
	555	+=== 3.7.1 Configure ThingsBoard ===
488	488
	557	+==== 3.7.1.1 Create Uplink & Downlink Converter ====
489	489
	559	+
	560	+(% style="color:blue" %)**Uplink Converter**
	561	+
	562	+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.
	563	+
	564	+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.
	565	+
	566	+[[image:image-20240729141300-1.png||height="552" width="1115"]]
	567	+
	568	+
	569	+(% style="color:blue" %)**Downlink Converter**
	570	+
	571	+The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
	572	+
	573	+[[image:image-20240729142505-3.png||height="507" width="1023"]]
	574	+
	575	+
	576	+==== 3.7.1.2 COAP Integration Setup ====
	577	+
	578	+
	579	+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" %);
	580	+
	581	+[[image:image-20240729144058-4.png||height="506" width="1021"]]
	582	+
	583	+
	584	+The next steps is to add the recently created uplink converters;
	585	+
	586	+[[image:image-20240729150142-5.png||height="507" width="1023"]]
	587	+
	588	+
	589	+==== 3.7.1.3 Add COAP Integration ====
	590	+
	591	+
	592	+==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
	593	+
	594	+
	595	+=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
	596	+
	597	+==== 3.7.2.1 Instruction Description ====
	598	+
	599	+
	600	+* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
	601	+* AT+SERVADDR=COAP Server Address,5683
	602	+
	603	+Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
	604	+
	605	+[[image:image-20240729172305-12.png||height="361" width="624"]]
	606	+
	607	+Note:The port for the COAP protocol has been fixed to 5683
	608	+
	609	+
	610	+* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
	611	+
	612	+If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
	613	+
	614	+e.g.
	615	+
	616	+* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
	617	+
	618	+[[image:image-20240729172415-13.png||height="401" width="694"]]
	619	+
	620	+If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
	621	+
	622	+e.g.
	623	+
	624	+* AT+URL1=11, "i";
	625	+* AT+URL2=11,"/faaaa241f-af4a-b780-4468-c671bb574858"
	626	+
	627	+[[image:image-20240729172500-14.png||height="403" width="700"]]
	628	+
	629	+
	630	+== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
	631	+
	632	+=== 3.8.1 Create device & Get Credentials ===
	633	+
	634	+
490	490	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.
491	491
492	492	[[image:image-20230802112413-44.png]]
...	...	@@ -499,73 +499,311 @@
499	499	[[image:image-20230802112413-46.png]]
500	500
501	501
502		-On the Connection Profile window, set the following information: **(这边加一个截图)**
	647	+The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
503	503
504		-* (% style="color:blue" %)**Profile Name: “Any name”**
	649	+(% style="color:blue" %)**On the Connection Profile window, set the following information:**
505	505
506		-* (% style="color:blue" %)**Broker Address: mqtt.tago.io**
	651	+* (% style="color:#037691" %)**Profile Name: “Any name”**
507	507
508		-* (% style="color:blue" %)**Broker Port: 1883**
	653	+* (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
509	509
510		-* (% style="color:blue" %)**Client ID: “Any value”**
	655	+* (% style="color:#037691" %)**Broker Port: 8883**
511	511
512		-On the section User credentials, set the following information: **(这边加一个截图)**
	657	+* (% style="color:#037691" %)**Client ID: “Any value”**
513	513
514		-* (% style="color:blue" %)**User Name: “Any value”**  (%%) ~/~/  Tago validates your user by the token only
	659	+(% style="color:blue" %)**On the section User credentials, set the following information:**
515	515
516		-* (% style="color:blue" %)**Password: “Your device token”**
	661	+* (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
517	517
518		-* (% style="color:blue" %)**PUBTOPIC: “Any value”**
	663	+* (% style="color:#037691" %)**Password: “Your device token”**
519	519
520		-* (% style="color:blue" %)**SUBTOPIC: “Any value”**
	665	+* (% style="color:#037691" %)**PUBTOPIC: “Any value”**
521	521
522		-=== 3.7.2 Simulate with MQTT.fx ===
	667	+* (% style="color:#037691" %)**SUBTOPIC: “Any value”**
523	523
	669	+(% style="color:blue" %)**AT command:**
524	524
525		-[[image:image-20230802112413-47.png]]
	671	+* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
526	526
527		-[[image:image-20230802112413-48.png]]
	673	+* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
528	528
	675	+* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
	676	+
	677	+* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
	678	+
	679	+* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
	680	+
	681	+* (% style="color:#037691" %)**AT+PWD=“Your device token”**
	682	+
	683	+
	684	+
	685	+=== 3.8.2 Simulate with MQTT.fx ===
	686	+
	687	+
	688	+[[image:image-20230802112413-52.png]]
	689	+
	690	+
	691	+[[image:image-20230808105300-2.png||height="553" width="1026"]]
	692	+
	693	+
529	529	Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
530	530
	696	+[[image:image-20230808105217-1.png||height="556" width="1031"]]
531	531
532		-[[image:image-20230802112413-49.png]]
	698	+[[image:image-20230808105329-3.png]]
533	533
534	534
535		-=== 3.7.3 tago data ===
	701	+=== 3.8.3 tago data ===
536	536
537	537
538		-[[image:image-20230802112413-50.png]]
	704	+[[image:image-20230802112413-50.png||height="242" width="1037"]]
539	539
540		-[[image:image-20230802112413-51.png]]
	706	+[[image:image-20230802112413-51.png||height="184" width="696"]]
541	541
542	542
543		-=== 3.7.4 TLS mode ===
	709	+== 3.9 TCP Connection ==
544	544
545	545
546		-Users can choose to use (% style="color:blue" %)**SSL/TLS**(%%) mode.
	712	+(% style="color:blue" %)**AT command:**
547	547
548		-On the SSL/TLS section, check the option **Enable SSL/TLS**, and click OK.
	714	+* (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
549	549
550		-The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
	716	+* (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
551	551
552		-* (% style="color:blue" %)**Profile Name: “Any name”**
	718	+* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
553	553
554		-* (% style="color:blue" %)**Broker Address: mqtt.tago.io**
	720	+(% style="color:blue" %)**Sensor Console Output when Uplink:**
555	555
556		-* (% style="color:blue" %)**Broker Port: 8883**
	722	+[[image:image-20230807233631-1.png]]
557	557
558		-* (% style="color:blue" %)**Client ID: “Any value”**
559	559
560		-* (% style="color:blue" %)**User Name: “Any value”** (%%) ~/~/ Tago validates your user by the token only
	725	+(% style="color:blue" %)**See result in TCP Server:**
561	561
562		-* (% style="color:blue" %)**Password: “Your device token”**
	727	+[[image:image-20230807233631-2.png]]
563	563
564		-* (% style="color:blue" %)**PUBTOPIC: “Any value”**
565	565
566		-* (% style="color:blue" %)**SUBTOPIC: “Any value”**
	730	+== 3.10 AWS Connection ==
567	567
568		-[[image:image-20230802112413-52.png]]
569	569
	733	+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]]
570	570
	735	+
	736	+= 4. MQTT/UDP/TCP downlink =
	737	+
	738	+== 4.1 MQTT (via MQTT.fx) ==
	739	+
	740	+
	741	+Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
	742	+
	743	+**1.** Configure node MQTT connection (via MQTT.fx):
	744	+
	745	+(% style="color:blue" %)**AT command:**
	746	+
	747	+* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
	748	+
	749	+* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
	750	+
	751	+* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
	752	+
	753	+* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
	754	+
	755	+* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
	756	+
	757	+* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
	758	+
	759	+(% 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.**
	760	+
	761	+[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
	762	+
	763	+
	764	+**2. **When the node uplink packets, we can observe the data in MQTT.fx.
	765	+
	766	+[[image:image-20240418144337-1.png||height="709" width="802"]]
	767	+
	768	+**3. **The downlink command can be successfully sent only when the downlink port is open.
	769	+
	770	+ The downlink port is opened for about 3 seconds after uplink packets are sent.
	771	+
	772	+ 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.
	773	+
	774	+[[image:image-20240418150435-3.png||height="582" width="659"]]
	775	+
	776	+[[image:image-20240418150932-4.png||height="492" width="1061"]]
	777	+
	778	+(% 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.**
	779	+
	780	+
	781	+= 5. FAQ =
	782	+
	783	+== 5.1 What is the usage of Multi Sampling and One Uplink? ==
	784	+
	785	+
	786	+The NB series has the feature for Multi Sampling and one uplink. See one of them
	787	+
	788	+[[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]]
	789	+
	790	+User can use this feature for below purpose:
	791	+
	792	+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.
	793	+1. Give more sampling data points.
	794	+1. Increase reliable in transmission. For example. If user set
	795	+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)
	796	+1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
	797	+1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
	798	+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.
	799	+
	800	+== 5.2 Why the uplink JSON format is not standard? ==
	801	+
	802	+
	803	+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.
	804	+
	805	+The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
	806	+
	807	+[[image:image-20240229233154-1.png]]
	808	+
	809	+
	810	+= 6. Trouble Shooting: =
	811	+
	812	+== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
	813	+
	814	+
	815	+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.
	816	+
	817	+If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
	818	+
	819	+[[image:image-20240207002003-1.png]]
	820	+
	821	+
	822	+If fail to attach network, it will shows signal 99. as below:
	823	+
	824	+[[image:image-20240207002129-2.png]]
	825	+
	826	+
	827	+(% class="lead" %)
	828	+When see this issue, below are the checklist:
	829	+
	830	+* 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.
	831	+* 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]].
	832	+* 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]].
	833	+* Check if the device is attached to Carrier network but reject. (need to check with operator).
	834	+* Check if the antenna is connected firmly.
	835	+
	836	+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.
	837	+
	838	+
	839	+== 6.2 Issue: "NBIOT did not respond" ==
	840	+
	841	+
	842	+(% class="box errormessage" %)
	843	+(((
	844	+11:24:22.397 [44596]NBIOT did not respond.
	845	+11:24:24.315 [46530]NBIOT did not respond.
	846	+11:24:26.256 [48464]NBIOT did not respond.
	847	+11:24:28.196 [50398]NBIOT did not respond.
	848	+11:24:30.115 [52332]NBIOT did not respond.
	849	+11:24:32.127 [54266]NBIOT did not respond.
	850	+11:24:32.127 [54299]Restart the module...
	851	+11:24:39.181 [61332]No response when shutting down
	852	+)))
	853	+
	854	+This issue might due to initiate issue for NB-IoT module. In this case, please try:
	855	+
	856	+1) Open Enclosure
	857	+
	858	+2) Power off device by pull out the power on Jumper
	859	+
	860	+3) Power on device by connect back the power jumper.
	861	+
	862	+4) push reset button.
	863	+
	864	+[[image:image-20240208001740-1.png]]
	865	+
	866	+
	867	+== 6.3 Issue: "Failed to readI MSI number" ==
	868	+
	869	+
	870	+(% class="box errormessage" %)
	871	+(((
	872	+[18170]Failed to read IMSI:1umber.
	873	+[20109]Failed to read IMSI numoer.
	874	+[22048]Failed to read IMSI number.
	875	+[29842lRestart the module...
	876	+)))
	877	+
	878	+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"]].
	879	+
	880	+
	881	+== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
	882	+
	883	+
	884	+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.
	885	+
	886	+[[image:image-20240226111928-1.png]]
	887	+
	888	+
	889	+== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
	890	+
	891	+(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
	892	+=== UDP: ===
	893	+
	894	+(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
	895	+Its downlink command is the same as the AT command, but brackets are required.
	896	+Example:
	897	+
	898	+{AT+TDC=300}
	899	+
	900	+
	901	+(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
	902	+=== MQTT: ===
	903	+
	904	+Json：
	905	+
	906	+The Json format in MQTT mode needs to be configured with all commands.
	907	+If you have configurations that need to be changed, please change them in the template below.
	908	+Template:
	909	+
	910	+{
	911	+"AT+SERVADDR":"119.91.62.30,1882",
	912	+"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
	913	+"AT+UNAME":"usenamedragino",
	914	+"AT+PWD":"passworddragino",
	915	+"AT+PUBTOPIC":"123",
	916	+"AT+SUBTOPIC":"321",
	917	+"AT+TDC":"7200",
	918	+"AT+INTMOD":"0",
	919	+"AT+APN":"NULL",
	920	+"AT+5VT":"0",
	921	+"AT+PRO":"3,5",
	922	+"AT+TR":"900",
	923	+"AT+NOUD":"0",
	924	+"AT+CSQTIME":"5",
	925	+"AT+DNSTIMER":"0",
	926	+"AT+TLSMOD":"0,0",
	927	+"AT+MQOS":"0",
	928	+"AT+TEMPALARM1":"0",
	929	+"AT+TEMPALARM2":"10",
	930	+"AT+TEMPALARM3":"0"
	931	+}
	932	+
	933	+Hex：
	934	+
	935	+MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
	936	+
	937	+The supported commands are consistent with LoRaWAN's hex commands.
	938	+Please refer to the following link to obtain the hex format:
	939	+
	940	+[[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/]]
	941	+
	942	+
	943	+== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
	944	+
	945	+
	946	+* **AT Command: AT** **+GETLOG**
	947	+
	948	+This command can be used to query upstream logs of data packets.
	949	+
	950	+[[image:image-20240701114700-1.png]]
	951	+
	952	+
	953	+
571	571

image-20230807233631-1.png

Author

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

Size

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

Content

image-20230807233631-2.png

Author

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

Size

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

Content

image-20230808105217-1.png

Author

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

Size

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

Content

image-20230808105300-2.png

Author

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

Size

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

Content

image-20230808105329-3.png

Author

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

Size

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

Content

image-20230808162301-1.png

Author

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

Size

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

Content

image-20230808162342-2.png

Author

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

Size

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

Content

image-20230808162421-3.png

Author

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

Size

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

Content

image-20230808162727-4.png

Author

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

Size

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

Content

image-20230808163035-5.png

Author

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

Size

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

Content

image-20230808163049-6.png

Author

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

Size

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

Content

image-20230808163612-7.png

Author

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

Size

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

Content

image-20230808170051-8.png

Author

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

Size

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

Content

image-20230808170548-9.png

Author

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

Size

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

Content

image-20230808205045-1.png

Author

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

Size

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

Content

image-20230809165928-1.png

Author

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

Size

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

Content

image-20230809170225-2.png

Author

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

Size

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

Content

image-20230809170532-3.png

Author

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

Size

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

Content

image-20230809173127-4.png

Author

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

Size

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

Content

image-20230809173310-5.png

Author

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

Size

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

Content

image-20230809173438-6.png

Author

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

Size

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

Content

image-20230809173800-7.png

Author

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

Size

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

Content

image-20230809173835-8.png

Author

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

Size

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

Content

image-20230809174053-9.png

Author

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

Size

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

Content

image-20230809180523-10.png

Author

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

Size

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

Content

image-20230810083934-1.png

Author

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

Size

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

Content

image-20230810084048-2.png

Author

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

Size

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

Content

image-20230816201942-1.png

Author

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

Size

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

Content

image-20240129170024-1.png

Author

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

Size

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

Content

image-20240129170216-2.png

Author

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

Size

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

Content

image-20240129170539-3.png

Author

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

Size

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

Content

image-20240129171029-4.png

Author

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

Size

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

Content

image-20240129171113-5.png

Author

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

Size

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

Content

image-20240129171236-6.png

Author

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

Size

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

Content

image-20240129172056-7.png

Author

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

Size

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

Content

image-20240129172136-8.png

Author

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

Size

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

Content

image-20240129173116-9.png

Author

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

Size

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

Content

image-20240129173541-10.png

Author

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

Size

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

Content

image-20240129174518-11.png

Author

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

Size

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

Content

image-20240129174657-12.png

Author

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

Size

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

Content

image-20240129174840-13.png

Author

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

Size

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

Content

image-20240202111546-1.png

Author

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

Size

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

Content

image-20240207002003-1.png

Author

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

Size

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

Content

image-20240207002129-2.png

Author

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

Size

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

Content

image-20240208001740-1.png

Author

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

Size

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

Content

image-20240208102804-1.png

Author

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

Size

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

Content

image-20240226111928-1.png

Author

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

Size

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

Content

image-20240229233154-1.png

Author

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

Size

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

Content

image-20240417173549-1.png

Author

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

Size

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

Content

image-20240417180145-2.png

Author

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

Size

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

Content

image-20240417180737-3.png

Author

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

Size

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

Content

image-20240418144337-1.png

Author

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

Size

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

Content

image-20240418144714-2.png

Author

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

Size

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

Content

image-20240418150435-3.png

Author

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

Size

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

Content

image-20240418150932-4.png

Author

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

Size

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

Content

image-20240701114700-1.png

Author

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

Size

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

Content

image-20240729141300-1.png

Author

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

Size

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

Content

image-20240729142505-3.png

Author

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

Size

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

Content

image-20240729144058-4.png

Author

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

Size

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

Content

image-20240729150142-5.png

Author

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

Size

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

Content

image-20240729160802-7.png

Author

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

Size

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

Content

image-20240729161543-9.png

Author

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

Size

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

Content

image-20240729172234-11.png

Author

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

Size

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

Content

image-20240729172305-12.png

Author

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

Size

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

Content

image-20240729172415-13.png

Author

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

Size

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

Content

image-20240729172500-14.png

Author

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

Size

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

Content