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

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 48 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

Details

Page properties

Content

...	...	@@ -1,4 +1,4 @@
1		-(% class="wikigeneratedid" %)
	1	+(% class="wikigeneratedid" id="HTableofContents:" %)
2	2	**Table of Contents:**
3	3
4	4	{{toc/}}
...	...	@@ -5,6 +5,9 @@
5	5
6	6
7	7
	8	+
	9	+
	10	+
8	8	= 1. The use of this guideline =
9	9
10	10
...	...	@@ -11,21 +11,59 @@
11	11	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.
12	12
13	13
14		-= 2. Network Connection =
	17	+= 2. Attach Network =
15	15
	19	+== 2.1 General Configure to attach network ==
16	16
	21	+
	22	+To attache NB-IoT sensors to NB-IoT Network, You need to:
	23	+
	24	+1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
	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>)
	29	+
	30	+[[image:image-20240208102804-1.png||height="286" width="696"]]
	31	+
	32	+[[image:image-20230808205045-1.png||height="293" width="438"]]
	33	+
	34	+After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
	35	+
17	17	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.
18	18
19		-(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
20		-|(% style="background-color:#4f81bd; color:white" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white" %)**APN**|(% style="background-color:#4f81bd; color:white" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white" %)**Comments**
21		-|1NCE| | |
22		-|China Mobile| | |
	38	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
	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" %)(((
	41	+**[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
23	23
	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, US Virgin Islands
	44	+)))|(% style="width:135px" %)
	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" %)
24	24
25		-== 2.1 1NCE SIM Card. ==
	48	+== 2.2 Speed Up Network Attach time ==
26	26
27	27
	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.
28	28
	53	+(% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
	54	+
	55	+(% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
	56	+
	57	+(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
	58	+
	59	+(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
	60	+(% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
	61	+(% style="color:#037691" %)**Telstra**(%%)        AT+QBAND=1,28
	62	+(% style="color:#037691" %)**Softband**(%%)     AT+QBAND=2,3,8
	63	+
	64	+After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
	65	+
	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	+
29	29	= 3. Configure to connect to different servers =
30	30
31	31	== 3.1 General UDP Connection ==
...	...	@@ -39,7 +39,7 @@
39	39
40	40	We can use PC tool to simulate UDP connection to make sure server works ok.
41	41
42		-[[image:image-20230802112413-1.png]]
	83	+[[image:image-20230802112413-1.png||height="468" width="1024"]]
43	43
44	44
45	45	=== 3.1.2 Configure NB-IoT Sensor ===
...	...	@@ -53,8 +53,6 @@
53	53
54	54	* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
55	55
56		-* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
57		-
58	58	[[image:image-20230802112413-2.png]]
59	59
60	60
...	...	@@ -73,15 +73,15 @@
73	73
74	74	(% style="color:blue" %)**AT Commands:**
75	75
76		-* (% style="color:#037691" %)**AT+PRO=3,0**  (%%) ~/~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
	115	+* (% style="color:#037691" %)**AT+PRO=3,0**   (%%) ~/~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
77	77
78		-* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883**  (%%)  ~/~/  Set MQTT server address and port
	117	+* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883**  (%%) ~/~/  Set MQTT server address and port
79	79
80		-* (% style="color:#037691" %)**AT+CLIENT=CLIENT**  (%%) ~/~/  Set up the CLIENT of MQTT
	119	+* (% style="color:#037691" %)**AT+CLIENT=CLIENT**     (%%) ~/~/  Set up the CLIENT of MQTT
81	81
82		-* (% style="color:#037691" %)**AT+UNAME=UNAME**  (%%) ~/~/  Set the username of MQTT
	121	+* (% style="color:#037691" %)**AT+UNAME=UNAME**        (%%) ~/~/  Set the username of MQTT
83	83
84		-* (% style="color:#037691" %)**AT+PWD=PWD**  (%%) ~/~/  Set the password of MQTT
	123	+* (% style="color:#037691" %)**AT+PWD=PWD**             (%%) ~/~/  Set the password of MQTT
85	85
86	86	* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB**  (%%) ~/~/  Set the sending topic of MQTT
87	87
...	...	@@ -89,72 +89,88 @@
89	89
90	90	[[image:image-20230802112413-4.png]]
91	91
92		-[[image:image-20230802112413-5.png]]
	131	+[[image:image-20230802112413-5.png||height="530" width="987"]]
93	93
94		-**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.**
	133	+(% 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.**
95	95
96	96
97	97	== 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
98	98
99		-== 1.1 Get MQTT Credentials ==
	138	+=== 3.3.1 Get MQTT Credentials ===
100	100
	140	+
101	101	[[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.
102	102
103		-[[image:image-20230802112413-6.png]]
	143	+[[image:image-20230802112413-6.png||height="336" width="925"]]
104	104
105	105	[[image:image-20230802112413-7.png]]
106	106
107	107
108		-== 1.2. Simulate with MQTT.fx ==
	148	+=== 3.3.2 Simulate with MQTT.fx ===
109	109
110		-=== 1.2.1 Establish MQTT Connection ===
	150	+==== 3.3.2.1 Establish MQTT Connection ====
111	111
	152	+
112	112	After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
113	113
114	114	[[image:image-20230802112413-8.png]]
115	115
116		-* Broker Address: mqtt3.thingspeak.com
117		-* Broker Port: 1883
118		-* Client ID: <Your ThingSpeak MQTT ClientID>
119		-* User Name: <Your ThingSpeak MQTT User Name>
120		-* Password: <Your ThingSpeak MQTT Password>
	157	+* (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
121	121
122		-=== 1.2.2 Publish Data to ThingSpeak Channel ===
	159	+* (% style="color:#037691" %)**Broker Port:**(%%) 1883
123	123
	161	+* (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID>
	162	+
	163	+* (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name>
	164	+
	165	+* (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
	166	+
	167	+==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
	168	+
	169	+
124	124	[[image:image-20230802112413-9.png]]
125	125
126	126	[[image:image-20230802112413-10.png]]
127	127
128		-In MQTT.fx, we can publish below info:
129	129
130		-* Topic: channels/YOUR_CHANNEL_ID/publish
131		-* Payload: field1=63&field2=67&status=MQTTPUBLISH
	175	+(% style="color:blue" %)**In MQTT.fx, we can publish below info:**
132	132
	177	+* (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
	178	+
	179	+* (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH
	180	+
133	133	Where 63 and 67 are the value to be published to field1 & field2.
134	134
135	135
136		-Result:
	184	+(% style="color:blue" %)**Result: **
137	137
138		-[[image:image-20230802112413-11.png]]
	186	+[[image:image-20230802112413-11.png||height="539" width="901"]]
139	139
140	140
141		-== 1.3 Configure NB-IoT Sensor for connection ==
	189	+=== 3.3.3 Configure NB-IoT Sensor for connection ===
142	142
143		-=== 1.3.1 AT Commands: ===
	191	+==== 3.3.3.1 AT Commands: ====
144	144
	193	+
145	145	In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
146	146
147		-* AT+PRO=3,1   ~/~/Set to use ThingSpeak Server and Related Payload
148		-* AT+CLIENT=<Your ThingSpeak MQTT ClientID>
149		-* AT+UNAME=<Your ThingSpeak MQTT User Name>
150		-* AT+PWD=<Your ThingSpeak MQTT Password>
151		-* AT+PUBTOPIC=<YOUR_CHANNEL_ID>
152		-* AT+SUBTOPIC=<YOUR_CHANNEL_ID>
	196	+* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
153	153
154		-=== 1.3.2 Uplink Examples ===
	198	+* (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
155	155
156		-For S31-NB
	200	+* (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
157	157
	202	+* (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>**
	203	+
	204	+* (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
	205	+
	206	+* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
	207	+
	208	+==== 3.3.3.2 Uplink Examples ====
	209	+
	210	+
	211	+[[image:image-20230816201942-1.png]]
	212	+
158	158	For SE01-NB
159	159
160	160	For DDS20-NB
...	...	@@ -178,338 +178,315 @@
178	178	For SN50V3-NB
179	179
180	180
181		-=== 1.3.2 Map fields to sensor value ===
	236	+==== 3.3.3.3 Map fields to sensor value ====
182	182
	238	+
183	183	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.
184	184
185	185
186		-[[image:image-20230802112413-12.png]]
	242	+[[image:image-20230802112413-12.png||height="504" width="1011"]]
187	187
188		-[[image:image-20230802112413-13.png]]
	244	+[[image:image-20230802112413-13.png||height="331" width="978"]]
189	189
190	190
191	191	Below is the NB-IoT Product Table show the mapping.
192	192
193		-|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)Field1|(% colspan="1" rowspan="1" %)Field2|(% colspan="1" rowspan="1" %)Field3|(% colspan="1" rowspan="1" %)Field4|(% colspan="1" rowspan="1" %)Field5|(% colspan="1" rowspan="1" %)Field6|(% colspan="1" rowspan="1" %)Field7|(% colspan="1" rowspan="1" %)Field8|(% colspan="1" rowspan="1" %)(((
194		-Field9
	249	+(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
	250	+|(% 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
	251	+|(% 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" %)
	252	+|(% 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" %)
	253	+|(% 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" %)
	254	+|(% 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" %)
	255	+|(% 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" %)
	256	+|(% 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" %)
	257	+|(% 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" %)
	258	+|(% 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" %)
	259	+|(% 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" %)
	260	+|(% 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" %)
	261	+|(% 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
	262	+|(% 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" %)
	263	+|(% 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" %)
	264	+|(% 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" %)
	265	+|(% 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" %)
	266	+|(% 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" %)
	267	+|(% 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" %)
195	195
196		-
197		-)))|(% colspan="1" rowspan="1" %)(((
198		-Field10
	269	+== 3.4 [[Datacake>>https://datacake.co/]] ==
199	199
200		-
201		-)))
202		-|(% colspan="1" rowspan="1" %)S31x-NB|(% colspan="1" rowspan="1" %)Temperature |(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
203		-|(% colspan="1" rowspan="1" %)SE01-NB|(% colspan="1" rowspan="1" %)Temperature |(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)conduct|(% colspan="1" rowspan="1" %)dielectric_constant|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
204		-|(% colspan="1" rowspan="1" %)DDS20-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
205		-Battery
206	206
207		-
208		-)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
209		-|(% colspan="1" rowspan="1" %)DDS45-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
210		-Battery
	272	+(% class="wikigeneratedid" %)
	273	+Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
211	211
212		-
213		-)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
214		-|(% colspan="1" rowspan="1" %)DDS75-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
215		-Battery
216	216
217		-
218		-)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
219		-|(% colspan="1" rowspan="1" %)NMDS120-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
220		-Battery
	276	+(% class="wikigeneratedid" %)
	277	+As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
221	221
222		-
223		-)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
224		-|(% colspan="1" rowspan="1" %)SPH01-NB|(% colspan="1" rowspan="1" %)ph|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
225		-|(% colspan="1" rowspan="1" %)NLM01-NB|(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
226		-|(% colspan="1" rowspan="1" %)NMDS200-NB|(% colspan="1" rowspan="1" %)distance1|(% colspan="1" rowspan="1" %)distance2|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
227		-|(% colspan="1" rowspan="1" %)CPN01-NB|(% colspan="1" rowspan="1" %)alarm|(% colspan="1" rowspan="1" %)count|(% colspan="1" rowspan="1" %)door open duration|(% colspan="1" rowspan="1" %)calc flag|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
228		-|(% colspan="1" rowspan="1" %)DS03A-NB|(% colspan="1" rowspan="1" %)level|(% colspan="1" rowspan="1" %)alarm|(% colspan="1" rowspan="1" %)pb14door open num|(% colspan="1" rowspan="1" %)pb14 last open time|(% colspan="1" rowspan="1" %)pb15 level status|(% colspan="1" rowspan="1" %)pb15 alarm status|(% colspan="1" rowspan="1" %)pb15 door open num|(% colspan="1" rowspan="1" %)pb15 last open time|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI
229		-|(% colspan="1" rowspan="1" %)SN50V3-NB|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
230		-|(% colspan="1" rowspan="1" %)mod1|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)DS18B20 Temp|(% colspan="1" rowspan="1" %)exit_state/input PA4|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)Temperature |(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
231		-|(% colspan="1" rowspan="1" %)mod2|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
232		-DS18B20 Temp
	279	+* (% 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.
233	233
234		-
235		-)))|(% colspan="1" rowspan="1" %)(((
236		-exit_state/input PA4
	281	+* (% 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.
237	237
238		-
239		-)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
240		-|(% colspan="1" rowspan="1" %)mod3|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
241		-Battery
	283	+=== 3.4.1 For device Already has template ===
242	242
243		-
244		-)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
245		-exit_state/input PA4
	285	+==== 3.4.1.1 Create Device ====
246	246
247		-
248		-)))|(% colspan="1" rowspan="1" %)adc1|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)adc4|(% colspan="1" rowspan="1" %)
249		-|(% colspan="1" rowspan="1" %)mod4|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
250		-Battery
	287	+(% style="color:blue" %)**Add Device**(%%) in DataCake.
251	251
252		-
253		-)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
254		-DS18B20 Temp
	289	+[[image:image-20230808162301-1.png||height="453" width="952"]]
255	255
256		-
257		-)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
258		-exit_state/input PA4
259	259
260		-
261		-)))|(% colspan="1" rowspan="1" %)(((
262		-DS18B20 Temp2
	292	+[[image:image-20230808162342-2.png||height="541" width="952"]]
263	263
264		-
265		-)))|(% colspan="1" rowspan="1" %)(((
266		-DS18B20 Temp3
267	267
268		-
269		-)))|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
270		-|(% colspan="1" rowspan="1" %)mod5|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
271		-Battery
	295	+(% style="color:blue" %)**Choose the correct model**(%%) from template.
272	272
273		-
274		-)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
275		-DS18B20 Temp
	297	+[[image:image-20230808162421-3.png]]
276	276
277		-
278		-)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
279		-exit_state/input PA4
280	280
281		-
282		-)))|(% colspan="1" rowspan="1" %)Weight|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
283		-|(% colspan="1" rowspan="1" %)mod6|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
284		-Battery
	300	+(% 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.
285	285
286		-
287		-)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)count|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
	302	+[[image:image-20230808163612-7.png||height="549" width="952"]]
288	288
289		-= 4. Datacake =
	304	+[[image:image-20230808163035-5.png]]
290	290
291		-== 1.1 Define Product ==
	306	+[[image:image-20230808163049-6.png||height="544" width="926"]]
292	292
293		-Firstly, we need to set the MQTT mode to datacake, and we need to run AT+PRO=3,2. This command is set to datacake. After running the command, the device automatically sets the server address, port.
294	294
	309	+=== 3.4.2 For Device already registered in DataCake before shipped ===
295	295
296		-By chosing to add the device under a "New Product" you are required to give a name for this product. You can name it something like "My First MQTT Product".
	311	+==== 3.4.2.1 Scan QR Code to get the device info ====
297	297
298		-[[image:image-20230802112413-14.png]]
299	299
300		-== 1.2 Create Device ==
	314	+Users can use their phones or computers to scan QR codes to obtain device data information.
301	301
302		-In the second step you have to define the device which should be added to the product.
	316	+[[image:image-20230808170051-8.png||height="255" width="259"]]
303	303
304		-[[image:image-20230802112413-15.png]]
	318	+[[image:image-20230808170548-9.png]]
305	305
306		-Enter a name here (such as "My First MQTT Device") and complete the creation of the device by clicking on the "Next" button.
307	307
	321	+==== 3.4.2.2 Claim Device to User Account ====
308	308
309		-== 1.3 Create Database Fields ==
310	310
311		-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.
	324	+By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
312	312
313		-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 "Configuration".
314	314
315		-[[image:image-20230802112413-16.png]]
	327	+=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
316	316
317		-[[image:image-20230802112413-17.png]]
318	318
319		-To create a first database field, please click on the "Add Field" button as marked in the screenshot above.
	330	+**Step1: Add a device**
320	320
321		-This will open another modal asking for some required input for your first field.
	332	+[[image:image-20240129170024-1.png||height="330" width="900"]]
322	322
323		-[[image:image-20230802112413-18.png]]
324	324
325		-[[image:image-20230802112413-19.png]]
	335	+**Step2: Choose your device type,please select dragino NB-IOT device**
326	326
327		-== 1.4 Set up Broker ==
	337	+[[image:image-20240129170216-2.png||height="534" width="643"]]
328	328
329		-The broker is running on mqtt.datacake.co on ports 1883 and 8883. Port 1883 is unsecured and should not be used in production environments. Port 8883 uses a CA signed server certificate.
330	330
331		-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.
	340	+**Step3: Choose to create a new device**
332	332
333		-View your Personal Access Token
	342	+[[image:image-20240129170539-3.png||height="459" width="646"]]
334	334
335		-You can view your own token via the User-Settings-Menu. You can reach this menu by clicking on "Edit Profile" at the end of the list using the Workspace Selector:
336	336
337		-[[image:image-20230802112413-20.png]]
	345	+**Step4: Fill in the device ID of your NB device**
338	338
339		-MQTT Client-ID
	347	+[[image:image-20240202111546-1.png||height="378" width="651"]]
340	340
341		-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 specification blank. Your client then creates a randomly generated ID.
342	342
343		-AT+CLIENT=“Any value”
	350	+**Step5: Please select your device plan according to your needs and complete the creation of the device**
344	344
345		-AT+UNAME=Token
	352	+[[image:image-20240129171236-6.png||height="450" width="648"]]
346	346
347		-AT+PWD=Token
348	348
349		-[[image:image-20230802112413-21.png]]
	355	+**Step6: Please add the decoder at the payload decoder of the device configuration.**
350	350
	357	+**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]]
351	351
352		-== 1.6 Create your first Subscription ==
	359	+[[image:image-20240129172056-7.png||height="457" width="816"]]
353	353
354		-Subscribe
	361	+[[image:image-20240129173116-9.png||height="499" width="814"]]
355	355
356		-Data is published according to the following structure:
357	357
358		-dtck~/~//
	364	+**Step7: Add the output of the decoder as a field**
359	359
360		-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.
	366	+[[image:image-20240129173541-10.png||height="592" width="968"]]
361	361
362	362
363		-[[image:image-20230802112413-22.png]]
	369	+**Step8: Customize the dashboard and use fields as parameters of the dashboard**
364	364
	371	+[[image:image-20240129174518-11.png||height="147" width="1042"]]
365	365
366		-[[image:image-20230802112413-23.png]]
	373	+[[image:image-20240129174657-12.png||height="538" width="916"]]
367	367
	375	+[[image:image-20240129174840-13.png||height="536" width="750"]]
368	368
369		-[[image:image-20230802112413-24.png]]
370	370
	378	+=== 3.4.4 For device have not configured to connect to DataCake ===
371	371
372		-example:
373	373
374		-AT+PUBTOPIC=dtck-pub/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
	381	+(% class="lead" %)
	382	+Use AT command for connecting to DataCake
375	375
376		-[[image:image-20230802112413-25.png]]
	384	+(% style="color:blue" %)**AT+PRO=2,0**
377	377
378		-== 1.7 Define Publish Topic ==
	386	+(% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
379	379
380		-Publish
381	381
382		-To upload data into the Datacake Cloud and into a specific device, you publish the data to the respective topic structure.
	389	+== 3.5 Node-Red (via MQTT) ==
383	383
384		-Due to the nature of MQTT, the topic prefix differs as follows:
	391	+=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
385	385
386		-dtck-pub~/~//
387	387
388		-example:
	394	+Take S31-NB UDP protocol as an example.
389	389
390		-AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
	396	+Dragino provides input flow examples for the sensors.
391	391
392		-== 1.8 upload data ==
	398	+User can download the required JSON file through Dragino Node-RED input flow template.
393	393
394		-[[image:image-20230802112413-26.png]]
	400	+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]]
395	395
396		-[[image:image-20230802112413-27.png]]
	402	+We can directly import the template.
397	397
398		-[[image:image-20230802112413-28.png]]
	404	+The templates for S31-NB and NB95S31B are the same.
399	399
400		-= =
401	401
402		-= 5. Node-Red (via MQTT) =
	407	+[[image:image-20230809173127-4.png]]
403	403
404	404
405		-== 1.1 Configure Node-Red ==
	410	+Please select the NB95S31B template.
406	406
407		-[[image:image-20230802112413-29.png]]
	412	+[[image:image-20230809173310-5.png||height="558" width="926"]]
408	408
409		-[[image:image-20230802112413-30.png]]
	414	+[[image:image-20230809173438-6.png]]
410	410
411		-== 1.2 Simulate Connection ==
	416	+[[image:image-20230809173800-7.png]]
412	412
413		-[[image:image-20230802112413-31.png]]
414	414
415		-== 1.3 Configure NB-IoT Sensors ==
	419	+Successfully imported template.
416	416
417		-* AT+PRO=3,0(hex format) or 3,5(json format)    ~/~/Set to mqtt Server and  Payload
418		-* AT+CLIENT=any value
419		-* AT+UNAME=any value
420		-* AT+PWD=any value
421		-* AT+PUBTOPIC=any value
422		-* AT+SUBTOPIC=any value
	421	+[[image:image-20230809173835-8.png||height="515" width="860"]]
423	423
424		-= 6. ThingsBoard.Cloud (via MQTT) =
425	425
426		-== 1.1 Configure ThingsBoard ==
	424	+Users can set UDP port.
427	427
428		-=== 1.1.1 Create Device ===
	426	+[[image:image-20230809174053-9.png]]
429	429
430		-Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]].
431	431
432		-[[image:image-20230802112413-32.png]]
	429	+=== 3.5.2 Simulate Connection ===
433	433
434		-=== 1.1.2 Create Uplink & Downlink Converter ===
435	435
436		-Uplink Converter
	432	+We have completed the configuration of UDP. We can try sending packets to node red.
437	437
	434	+[[image:image-20230810083934-1.png]]
	435	+
	436	+[[image:image-20230810084048-2.png||height="535" width="1052"]]
	437	+
	438	+
	439	+=== 3.5.3 Configure NB-IoT Sensors ===
	440	+
	441	+
	442	+* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
	443	+* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
	444	+* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
	445	+* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
	446	+* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
	447	+* (% style="color:#037691" %)**AT+PWD=“Your device token”**
	448	+
	449	+== 3.6 ThingsBoard.Cloud (via MQTT) ==
	450	+
	451	+=== 3.6.1 Configure ThingsBoard ===
	452	+
	453	+==== 3.6.1.1 Create Device ====
	454	+
	455	+
	456	+Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
	457	+
	458	+[[image:image-20230802112413-32.png||height="583" width="1066"]]
	459	+
	460	+
	461	+==== 3.6.1.2 Create Uplink & Downlink Converter ====
	462	+
	463	+
	464	+(% style="color:blue" %)**Uplink Converter**
	465	+
438	438	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.
439	439
440		-To create an uplink converter go to the Integrations center -> Data converters page and click “plus” button. Name it “MQTT Uplink Converter” and select type Uplink. Use debug mode for now.
	468	+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.
441	441
442		-[[image:image-20230802112413-33.png]]
	470	+[[image:image-20230802112413-33.png||height="597" width="1061"]]
443	443
444	444
445		-Downlink Converter
	473	+(% style="color:blue" %)**Downlink Converter**
446	446
447	447	The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
448	448
449		-[[image:image-20230802112413-34.png]]
	477	+[[image:image-20230802112413-34.png||height="598" width="1063"]]
450	450
451		-Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.
	479	+(% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
452	452
453		-=== 1.1.3 MQTT Integration Setup ===
454	454
455		-Go to the Integrations center -> Integrations page and click “plus” icon to add a new integration. Name it “MQTT Integration”, select type MQTT;
	482	+==== 3.6.1.3 MQTT Integration Setup ====
456	456
457		-[[image:image-20230802112413-35.png]]
458	458
	485	+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**;
	486	+
	487	+[[image:image-20230802112413-35.png||height="597" width="1062"]]
	488	+
	489	+
459	459	* The next steps is to add the recently created uplink and downlink converters;
460	460
461		-[[image:image-20230802112413-36.png]]
	492	+[[image:image-20230802112413-36.png||height="598" width="1062"]]
462	462
463		-[[image:image-20230802112413-37.png]]
	494	+[[image:image-20230802112413-37.png||height="598" width="1064"]]
464	464
465		-Add a topic filter:
466	466
	497	+(% style="color:blue" %)**Add a topic filter:**
467	467
468		-tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。
	499	+Consistent with the theme of the node setting.
469	469
470	470	You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
471	471
472		-[[image:image-20230802112413-38.png]]
	503	+[[image:image-20230802112413-38.png||height="598" width="1064"]]
473	473
474		-== 1.2 Simulate with MQTT.fx ==
475	475
476		-[[image:image-20230802112413-39.png]]
	506	+=== 3.6.2 Simulate with MQTT.fx ===
477	477
478		-[[image:image-20230802112413-40.png]]
479	479
480		-== 1.3 Configure NB-IoT Sensor ==
	509	+[[image:image-20230802112413-39.png]]
481	481
482		-AT Commands
	511	+[[image:image-20230802112413-40.png||height="525" width="980"]]
483	483
484		-AT+PRO=3,3  ~/~/ Use MQTT to connect to ThingsBoard.
485	485
486		-AT+SUBTOPIC=device name ~-~-> 只需要 Device Name 吗?对的
	514	+=== 3.6.3 Configure NB-IoT Sensor ===
487	487
488		-AT+PUBTOPIC=device name ~-~-> 只需要 Device Name 吗?对的
489	489
	517	+(% style="color:blue" %)**AT Commands**
490	490
491		-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 吧).这边不用提示了，客户不需要输入。（大部分客户还是会自己去设置这个的，提高安全性）
	519	+* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
492	492
493		-CLIENT :“Any value”
	521	+* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
494	494
495		-User Name:“Any value”
	523	+* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
496	496
497		-Password:“Any value”
	525	+* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
498	498
	527	+* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
499	499
	529	+* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
	530	+
500	500	Test Uplink by click the button for 1 second
501	501
502		-[[image:image-20230802112413-41.png]]
	533	+[[image:image-20230802112413-41.png||height="496" width="828"]]
503	503
504	504	[[image:image-20230802112413-42.png]]
505	505
506		-[[image:image-20230802112413-43.png]]
	537	+[[image:image-20230802112413-43.png||height="407" width="825"]]
507	507
508	508
509		-= 7. [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) =
	540	+== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
510	510
511		-== 5.1 Create device & Get Credentials ==
	542	+=== 3.7.1 Create device & Get Credentials ===
512	512
	544	+
513	513	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.
514	514
515	515	[[image:image-20230802112413-44.png]]
...	...	@@ -516,7 +516,6 @@
516	516
517	517	[[image:image-20230802112413-45.png]]
518	518
519		-= =
520	520
521	521	Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
522	522
...	...	@@ -523,55 +523,193 @@
523	523	[[image:image-20230802112413-46.png]]
524	524
525	525
526		-On the Connection Profile window, set the following information: (这边加一个截图)
	557	+The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
527	527
528		-* Profile Name: “Any name”
529		-* Broker Address: mqtt.tago.io
530		-* Broker Port: 1883
531		-* Client ID: “Any value”
	559	+(% style="color:blue" %)**On the Connection Profile window, set the following information:**
532	532
533		-On the section User credentials, set the following information:(这边加一个截图)
	561	+* (% style="color:#037691" %)**Profile Name: “Any name”**
534	534
535		-* User Name: “Any value” Tago validates your user by the token only
536		-* Password: “Your device token”
537		-* PUBTOPIC: “Any value”
538		-* SUBTOPIC: “Any value”
	563	+* (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
539	539
540		-== 5.2 Simulate with MQTT.fx ==
	565	+* (% style="color:#037691" %)**Broker Port: 8883**
541	541
542		-[[image:image-20230802112413-47.png]]
	567	+* (% style="color:#037691" %)**Client ID: “Any value”**
543	543
544		-[[image:image-20230802112413-48.png]]
	569	+(% style="color:blue" %)**On the section User credentials, set the following information:**
545	545
546		-Users can run the AT+PRO=3,5 command, and the payload will be converted to JSON format.
	571	+* (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
547	547
548		-[[image:image-20230802112413-49.png]]
	573	+* (% style="color:#037691" %)**Password: “Your device token”**
549	549
550		-== 1.4. tago data ==
	575	+* (% style="color:#037691" %)**PUBTOPIC: “Any value”**
551	551
	577	+* (% style="color:#037691" %)**SUBTOPIC: “Any value”**
552	552
553		-[[image:image-20230802112413-50.png]]
	579	+(% style="color:blue" %)**AT command:**
554	554
555		-[[image:image-20230802112413-51.png]]
	581	+* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
556	556
557		-== 1.4. TLS mode ==
	583	+* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
558	558
559		-Users can choose to use SSL/TLS mode.
	585	+* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
560	560
561		-On the SSL/TLS section, check the option Enable SSL/TLS, and click OK.
	587	+* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
562	562
563		-The device needs to enable the TLS mode and set the AT+TLSMOD=1,0 command.
	589	+* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
564	564
565		-* Profile Name: “Any name”
566		-* Broker Address: mqtt.tago.io
567		-* Broker Port: 8883
568		-* Client ID: “Any value”
569		-* User Name: “Any value” Tago validates your user by the token only
570		-* Password: “Your device token”
571		-* PUBTOPIC: “Any value”
572		-* SUBTOPIC: “Any value”
	591	+* (% style="color:#037691" %)**AT+PWD=“Your device token”**
573	573
	593	+=== 3.7.2 Simulate with MQTT.fx ===
	594	+
	595	+
574	574	[[image:image-20230802112413-52.png]]
575	575
576	576
	599	+[[image:image-20230808105300-2.png||height="553" width="1026"]]
	600	+
	601	+
	602	+Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
	603	+
	604	+[[image:image-20230808105217-1.png||height="556" width="1031"]]
	605	+
	606	+[[image:image-20230808105329-3.png]]
	607	+
	608	+
	609	+=== 3.7.3 tago data ===
	610	+
	611	+
	612	+[[image:image-20230802112413-50.png||height="242" width="1037"]]
	613	+
	614	+[[image:image-20230802112413-51.png||height="184" width="696"]]
	615	+
	616	+
	617	+== 3.8 TCP Connection ==
	618	+
	619	+
	620	+(% style="color:blue" %)**AT command:**
	621	+
	622	+* (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
	623	+
	624	+* (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
	625	+
	626	+* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
	627	+
	628	+(% style="color:blue" %)**Sensor Console Output when Uplink:**
	629	+
	630	+[[image:image-20230807233631-1.png]]
	631	+
	632	+
	633	+(% style="color:blue" %)**See result in TCP Server:**
	634	+
	635	+[[image:image-20230807233631-2.png]]
	636	+
	637	+
	638	+= 4. FAQ =
	639	+
	640	+== 4.1 What is the usage of Multi Sampling and One Uplink? ==
	641	+
	642	+
	643	+The NB series has the feature for Multi Sampling and one uplink. See one of them
	644	+
	645	+[[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]]
	646	+
	647	+User can use this feature for below purpose:
	648	+
	649	+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.
	650	+1. Give more sampling data points.
	651	+1. Increase reliable in transmission. For example. If user set
	652	+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)
	653	+1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
	654	+1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
	655	+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.
	656	+
	657	+
	658	+
	659	+== 4.2 Why the uplink JSON format is not standard? ==
	660	+
	661	+
	662	+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.
	663	+
	664	+[[image:image-20240229233154-1.png]]
	665	+
	666	+
	667	+= 5. Trouble Shooting: =
	668	+
	669	+== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
	670	+
	671	+
	672	+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.
	673	+
	674	+If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
	675	+
	676	+[[image:image-20240207002003-1.png]]
	677	+
	678	+
	679	+If fail to attach network, it will shows signal 99. as below:
	680	+
	681	+[[image:image-20240207002129-2.png]]
	682	+
	683	+
	684	+(% class="lead" %)
	685	+When see this issue, below are the checklist:
	686	+
	687	+* 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.
	688	+* 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]].
	689	+* 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]].
	690	+* Check if the device is attached to Carrier network but reject. (need to check with operator).
	691	+* Check if the antenna is connected firmly.
	692	+
	693	+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.
	694	+
	695	+
	696	+== 5.2 Issue: "NBIOT did not respond" ==
	697	+
	698	+
	699	+(% class="box errormessage" %)
	700	+(((
	701	+11:24:22.397 [44596]NBIOT did not respond.
	702	+11:24:24.315 [46530]NBIOT did not respond.
	703	+11:24:26.256 [48464]NBIOT did not respond.
	704	+11:24:28.196 [50398]NBIOT did not respond.
	705	+11:24:30.115 [52332]NBIOT did not respond.
	706	+11:24:32.127 [54266]NBIOT did not respond.
	707	+11:24:32.127 [54299]Restart the module...
	708	+11:24:39.181 [61332]No response when shutting down
	709	+)))
	710	+
	711	+This issue might due to initiate issue for NB-IoT module. In this case, please try:
	712	+
	713	+1) Open Enclosure
	714	+
	715	+2) Power off device by pull out the power on Jumper
	716	+
	717	+3) Power on device by connect back the power jumper.
	718	+
	719	+4) push reset button.
	720	+
	721	+[[image:image-20240208001740-1.png]]
	722	+
	723	+
	724	+== 5.3 Issue: "Failed to readI MSI number" ==
	725	+
	726	+
	727	+(% class="box errormessage" %)
	728	+(((
	729	+[18170]Failed to read IMSI:1umber.
	730	+[20109]Failed to read IMSI numoer.
	731	+[22048]Failed to read IMSI number.
	732	+[29842lRestart the module...
	733	+)))
	734	+
	735	+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"]].
	736	+
	737	+
	738	+== 5.4 Why sometime the AT Command is slow in reponse? ==
	739	+
	740	+
	741	+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.
	742	+
	743	+[[image:image-20240226111928-1.png]]
	744	+
	745	+
577	577

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