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, 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

Author

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

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

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