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

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