Last modified by Mengting Qiu on 2025/07/03 18:49

From version 8.1
edited by David Huang
on 2024/06/07 14:59
Change comment: There is no comment for this version
To version 136.1
edited by Bei Jinggeng
on 2025/01/13 10:38
Change comment: Uploaded new attachment "image-20250113103816-1.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.David
1 +XWiki.Bei
Content
... ... @@ -1,13 +1,15 @@
1 -​
1 +​**Table of Contents:**
2 2  
3 +{{toc/}}
3 3  
4 -(% class="wikigeneratedid" id="HTableofContents:" %)
5 -**Table of Contents:**
6 6  
7 -{{toc/}}
8 8  
7 +
8 +
9 +
9 9  = 1. The use of this guideline =
10 10  
12 +
11 11  This configure instruction is for Dragino NB-IoT models with -CB or -CS suffix, for example DDS75-CB. These models use the same NB-IoT Module **[[BG95-M2>>https://www.dropbox.com/sh/3ilyaswz4odgaru/AADR86cAgL9UGlmLuEH-UZgla?st=x1ry6v5j&dl=0]]** and has the same software structure. The have the same configure instruction to different IoT servers. Use can follow the instruction here to see how to configure to connect to those servers.
12 12  
13 13  
... ... @@ -15,6 +15,7 @@
15 15  
16 16  == 2.1 General Configure to attach network ==
17 17  
20 +
18 18  To attache end nodes to NB-IoT or LTE-M Network, You need to:
19 19  
20 20  1. Get a NB-IoT or LTE-M SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
... ... @@ -26,7 +26,7 @@
26 26  [[image:image-20240602220856-1.png]]
27 27  
28 28  
29 -放一张如何插卡图片。
32 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20230808205045-1.png?width=438&height=293&rev=1.1||alt="image-20230808205045-1.png"]]
30 30  
31 31  
32 32  After doing above, the end nodes should be able to attach to NB-IoT network .
... ... @@ -51,14 +51,19 @@
51 51  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:406px" %)China Mainland, HongKong|(% style="width:351px" %) |(% style="width:120px" %)
52 52  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:406px" %)China Mainland|(% style="width:351px" %) |(% style="width:120px" %)
53 53  
57 +(% class="wikigeneratedid" %)
58 +cccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc
59 +
54 54  == 2.2 Speed Up Network Attach time ==
55 55  
62 +
56 56  **BG95-M2** supports multi bands (% style="color:blue" %)**in NB-IoT and LTE-M. **(%%) It will search one by one and try to attach, this will take a lot of time and even cause attach fail and show **Signal Strenght:99**.
57 57  
65 +**Note:**Before using the NB module command, users need to power on the NB module. Run the AT+QSW command to turn on and off the NB module.Remember to shut down after using the NB module command, otherwise it will consume power.
58 58  
59 59  Attache to 1NCE card for Australia use:
60 60  
61 -* AT+COPS=1,2,"50501",8
69 +* AT+COPS=1,2,"50501",8 
62 62  * AT+QCFG="band",0,0x8000000,0x8000000,1
63 63  
64 64  After connection is successful, user can use (% style="color:#037691" %)**AT+QENG="servingcell"**(%%) to check which band is actually in used.
... ... @@ -70,38 +70,157 @@
70 70  
71 71  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/]]**
72 72  
81 +=== **1. Configure Frequency Band** ===
73 73  
83 +AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
74 74  
85 +<GSM_bandval>:
86 +
87 +0 No change 
88 +0x1 EGSM900
89 +0x2 DCS1800
90 +0x4 GSM850 
91 +0x8 PCS1900 
92 +0xF All of the supported bands above
93 +
94 +<eMTC_bandval>:
95 +
96 +0 No change 
97 +0x1  LTE B1
98 +0x2  LTE B2 
99 +0x4  LTE B3 
100 +0x8  LTE B4 
101 +0x10  LTE B5 
102 +0x80  LTE B8 
103 +0x800  LTE B12 
104 +0x1000  LTE B13 
105 +0x20000  LTE B18 
106 +0x40000  LTE B19 
107 +0x80000  LTE B20 
108 +0x1000000  LTE B25 
109 +0x2000000  LTE B26 
110 +0x4000000  LTE B27 
111 +0x8000000  LTE B28 
112 +0x40000000  LTE B31 
113 +0x20000000000000000  LTE B66 
114 +0x800000000000000000  LTE B72 
115 +0x1000000000000000000  LTE B73 
116 +0x1000000000000000000000  LTE B85
117 +
118 +<NB-IoT_bandval>:
119 +
120 +0 No change 
121 +0x1  LTE B1
122 +0x2  LTE B2 
123 +0x4  LTE B3 
124 +0x8  LTE B4 
125 +0x10  LTE B5 
126 +0x80  LTE B8 
127 +0x800  LTE B12 
128 +0x1000  LTE B13 
129 +0x20000  LTE B18 
130 +0x40000  LTE B19 
131 +0x80000  LTE B20 
132 +0x1000000  LTE B25 
133 +0x8000000  LTE B28 
134 +0x40000000  LTE B31 
135 +0x20000000000000000  LTE B66
136 +
137 +0x400000000000000000  LTE B71
138 +0x800000000000000000  LTE B72 
139 +0x1000000000000000000  LTE B73 
140 +0x1000000000000000000000  LTE B85
141 +
142 +For example, setting the LTE-M network frequency band to 3.
143 +
144 +AT+QCFG="band",0xF,0x4,0,1
145 +
146 +When searching for all bands, the value of this command is set to:
147 +
148 +AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
149 +
150 +
151 +=== **2. Configure search network sequence** ===
152 +
153 +AT+QCFG="nwscanseq",<scanseq>,1
154 +
155 +<scanseq>:
156 +
157 +00 Automatic (eMTC → NB-IoT → GSM) 
158 +01 GSM 
159 +02 eMTC 
160 +03 NB-IoT
161 +
162 +AT+QCFG="nwscanseq",02,1  ~/~/Priority search for eMTC
163 +
164 +
165 +=== **3. Configure Network Category to be Searched for under LTE RAT** ===
166 +
167 +AT+QCFG="iotopmode",mode,1
168 +
169 +0 eMTC 
170 +1 NB-IoT 
171 +2 eMTC and NB-IoT
172 +
173 +
174 +=== **4. AT command to set frequency band and network category** ===
175 +
176 +AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f  ~/~/<eMTC_bandval>,<NB-IoT_bandval>
177 +
178 +AT+IOTMOD=0  ~/~/ 0 eMTC  1 NB-IoT  2 eMTC and NB-IoT
179 +
180 +**Example :**
181 +
182 +Taking the use of 1nce cards in **the United States** as an example.
183 +
184 +AT+APN=iot.1nce.net  ~/~/set APN
185 +
186 +AT+QBAND=0x100180A,0  ~/~/ eMTC :Set frequency band B2,B4,B12,B13,B25  NB-IoT:No change
187 +
188 +AT+IOTMOD=0  ~/~/ Set  eMTC Network
189 +
190 +**Setting the above commands in the United States will greatly reduce the network search time of the NB module.**
191 +
192 +
75 75  = 3. Configure to connect to different servers =
76 76  
77 77  == 3.1 General UDP Connection ==
78 78  
197 +
79 79  The NB-IoT Sensor can send packet to server use UDP protocol.
80 80  
200 +
81 81  === 3.1.1 Simulate UDP Connection by PC tool ===
82 82  
203 +
83 83  We can use PC tool to simulate UDP connection to make sure server works ok.
84 84  
85 -[[image:image-20230802112413-1.png||height="468" width="1024"]]
206 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20230802112413-1.png?width=1024&height=468&rev=1.1||alt="image-20230802112413-1.png"]]
86 86  
208 +
87 87  === 3.1.2 Configure NB-IoT Sensor ===
88 88  
89 89  ==== 3.1.2.1 AT Commands ====
90 90  
213 +
91 91  (% style="color:blue" %)**AT Commands:**
92 92  
93 93  * (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload
94 94  
95 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/ Set UDP server address and port
218 +* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1999**  (%%) ~/~/ Set UDP server address and port
96 96  
97 -[[image:image-20230802112413-2.png]]
220 +[[image:image-20240819102802-1.png]]
98 98  
222 +
99 99  ==== 3.1.2.2 Uplink Example ====
100 100  
101 -[[image:image-20230802112413-3.png]]
102 102  
226 +[[image:image-20240819105418-8.png||height="611" width="1287"]]
227 +
228 +
103 103  == 3.2 General COAP Connection ==
104 104  
231 +
105 105  The NB-IoT Sensor can send packet to server use COAP protocol.
106 106  
107 107  Below are the commands.
... ... @@ -112,16 +112,21 @@
112 112  
113 113  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%) ~/~/ Set COAP server address and port
114 114  
115 -* (% style="color:#037691" %)**AT+URI1=11,"I"**  (%%) ~/~/  Configure CoAP Message Options
116 -* (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**  (%%) ~/~/ Configure CoAP Message Options
242 +* (% style="color:#037691" %)**AT+URI1=11,"i"**  (%%) ~/~/  Configure CoAP Message Options
243 +* (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**    (%%) ~/~/ Configure CoAP Message Options
117 117  
118 -(% class="wikigeneratedid" %)
245 +[[image:image-20240819103212-2.png]]
246 +
247 +
119 119  === 3.2.1 Uplink Example ===
120 120  
121 121  
251 +[[image:image-20240819103909-4.png||height="453" width="955"]]
122 122  
253 +
123 123  == 3.2 General MQTT Connection ==
124 124  
256 +
125 125  The NB-IoT Sensor can send packet to server use MQTT protocol.
126 126  
127 127  Below are the commands.
... ... @@ -142,29 +142,34 @@
142 142  
143 143  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB**  (%%) ~/~/ Set the subscription topic of MQTT
144 144  
145 -[[image:image-20230802112413-4.png]]
277 +[[image:image-20240819105003-7.png||height="613" width="458"]]
146 146  
147 -[[image:image-20230802112413-5.png||height="530" width="987"]]
148 148  
280 +[[image:image-20240819104942-6.png||height="702" width="974"]]
281 +
149 149  (% 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.**
150 150  
284 +
151 151  == 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
152 152  
153 153  === 3.3.1 Get MQTT Credentials ===
154 154  
289 +
155 155  [[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.
156 156  
157 -[[image:image-20230802112413-6.png||height="336" width="925"]]
292 +[[image:image-20240819173602-1.png||height="401" width="743"]]
158 158  
159 -[[image:image-20230802112413-7.png]]
294 +[[image:image-20240819173706-3.png||height="595" width="597"]]
160 160  
296 +
161 161  === 3.3.2 Simulate with MQTT.fx ===
162 162  
163 163  ==== 3.3.2.1 Establish MQTT Connection ====
164 164  
301 +
165 165  After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
166 166  
167 -[[image:image-20230802112413-8.png]]
304 +[[image:image-20240819173826-4.png||height="534" width="734"]]
168 168  
169 169  * (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
170 170  
... ... @@ -178,10 +178,11 @@
178 178  
179 179  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
180 180  
181 -[[image:image-20230802112413-9.png]]
182 182  
183 -[[image:image-20230802112413-10.png]]
319 +[[image:image-20240819174033-5.png]]
184 184  
321 +[[image:image-20240819174209-6.png]]
322 +
185 185  (% style="color:blue" %)**In MQTT.fx, we can publish below info:**
186 186  
187 187  * (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
... ... @@ -192,12 +192,14 @@
192 192  
193 193  (% style="color:blue" %)**Result: **
194 194  
195 -[[image:image-20230802112413-11.png||height="539" width="901"]]
333 +[[image:image-20240819174314-7.png||height="469" width="785"]]
196 196  
335 +
197 197  === 3.3.3 Configure NB-IoT Sensor for connection ===
198 198  
199 199  ==== 3.3.3.1 AT Commands: ====
200 200  
340 +
201 201  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
202 202  
203 203  * (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
... ... @@ -214,8 +214,9 @@
214 214  
215 215  ==== 3.3.3.2 Uplink Examples ====
216 216  
217 -[[image:image-20230816201942-1.png]]
218 218  
358 +[[image:image-20240819174540-8.png]]
359 +
219 219  For SE01-NB
220 220  
221 221  For DDS20-NB
... ... @@ -238,35 +238,37 @@
238 238  
239 239  For SN50V3-NB
240 240  
382 +
241 241  ==== 3.3.3.3 Map fields to sensor value ====
242 242  
385 +
243 243  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.
244 244  
245 -[[image:image-20230802112413-12.png||height="504" width="1011"]]
388 +[[image:image-20240819174610-9.png]]
246 246  
247 -[[image:image-20230802112413-13.png||height="331" width="978"]]
390 +[[image:image-20240819174618-10.png]]
248 248  
249 249  Below is the NB-IoT Product Table show the mapping.
250 250  
251 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
252 -|(% 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
253 -|(% 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" %)
254 -|(% 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" %)
255 -|(% 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" %)
256 -|(% 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" %)
257 -|(% 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" %)
258 -|(% 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" %)
259 -|(% 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" %)
260 -|(% 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" %)
261 -|(% 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" %)
262 -|(% 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" %)
263 -|(% 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
264 -|(% 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" %)
265 -|(% 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" %)
266 -|(% 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" %)
267 -|(% 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" %)
268 -|(% 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" %)
269 -|(% 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" %)
394 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1353.82px" %)
395 +|(% style="background-color:#4f81bd; width:143px" %) |(% style="background-color:#4f81bd; color:white; width:103px" %)Field1|(% style="background-color:#4f81bd; color:white; width:102px" %)Field2|(% style="background-color:#4f81bd; color:white; width:157px" %)Field3|(% style="background-color:#4f81bd; color:white; width:139px" %)Field4|(% style="background-color:#4f81bd; color:white; width:141px" %)Field5|(% style="background-color:#4f81bd; color:white; width:142px" %)Field6|(% style="background-color:#4f81bd; color:white; width:151px" %)Field7|(% style="background-color:#4f81bd; color:white; width:137px" %)Field8|(% style="background-color:#4f81bd; color:white; width:69px" %)Field9|(% style="background-color:#4f81bd; color:white; width:65px" %)Field10
396 +|(% style="background-color:#4f81bd; color:white; width:143px" %)S31x-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)Battery|(% style="width:139px" %)RSSI|(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
397 +|(% style="background-color:#4f81bd; color:white; width:143px" %)SE01-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)conduct|(% style="width:139px" %)dielectric_constant|(% style="width:141px" %)Battery|(% style="width:142px" %)RSSI|(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
398 +|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS20-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:139px" %) |(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
399 +|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS45-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:139px" %) |(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
400 +|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS75-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:139px" %) |(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
401 +|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS120-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:139px" %) |(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
402 +|(% rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SPH01-NB|(% style="width:103px" %)ph|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:139px" %)RSSI|(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% colspan="1" rowspan="1" style="width:65px" %)
403 +|(% style="background-color:#4f81bd; color:white; width:143px" %)NLM01-NB|(% style="width:103px" %)Humidity|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:139px" %)RSSI|(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
404 +|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS200-NB|(% style="width:103px" %)distance1|(% style="width:102px" %)distance2|(% style="width:157px" %)Battery|(% style="width:139px" %)RSSI|(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
405 +|(% style="background-color:#4f81bd; color:white; width:143px" %)CPN01-NB|(% style="width:103px" %)alarm|(% style="width:102px" %)count|(% style="width:157px" %)door open duration|(% style="width:139px" %)calc flag|(% style="width:141px" %)Battery|(% style="width:142px" %)RSSI|(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
406 +|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)DS03A-NB|(% colspan="1" rowspan="1" style="width:103px" %)level|(% colspan="1" rowspan="1" style="width:102px" %)alarm|(% colspan="1" rowspan="1" style="width:157px" %)pb14door open num|(% colspan="1" rowspan="1" style="width:139px" %)pb14 last open time|(% colspan="1" rowspan="1" style="width:141px" %)pb15 level status|(% colspan="1" rowspan="1" style="width:142px" %)pb15 alarm status|(% colspan="1" rowspan="1" style="width:151px" %)pb15 door open num|(% colspan="1" rowspan="1" style="width:137px" %)pb15 last open time|(% colspan="1" rowspan="1" style="width:69px" %)Battery|(% colspan="1" rowspan="1" style="width:65px" %)RSSI
407 +|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod1|(% colspan="1" rowspan="1" style="width:103px" %)mod|(% colspan="1" rowspan="1" style="width:102px" %)Battery|(% colspan="1" rowspan="1" style="width:157px" %)RSSI|(% colspan="1" rowspan="1" style="width:139px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:141px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:142px" %)adc0|(% colspan="1" rowspan="1" style="width:151px" %)Temperature |(% colspan="1" rowspan="1" style="width:137px" %)Humidity|(% colspan="1" rowspan="1" style="width:69px" %) |(% colspan="1" rowspan="1" style="width:65px" %)
408 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod2|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:139px" %)DS18B20 Temp|(% colspan="1" style="width:141px" %)exit_state/input PA4|(% colspan="1" style="width:142px" %)adc0|(% colspan="1" style="width:151px" %)distance|(% colspan="1" style="width:137px" %) |(% colspan="1" style="width:69px" %) |(% colspan="1" style="width:65px" %)
409 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod3|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:139px" %)adc0|(% colspan="1" style="width:141px" %)exit_state/input PA4|(% colspan="1" style="width:142px" %)adc1|(% colspan="1" style="width:151px" %)Temperature|(% colspan="1" style="width:137px" %)Humidity|(% colspan="1" style="width:69px" %)adc4|(% colspan="1" style="width:65px" %)
410 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod4|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:139px" %)DS18B20 Temp|(% colspan="1" style="width:141px" %)adc0|(% colspan="1" style="width:142px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)DS18B20 Temp2|(% colspan="1" style="width:137px" %)DS18B20 Temp3|(% colspan="1" style="width:69px" %) |(% colspan="1" style="width:65px" %)
411 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod5|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:139px" %)DS18B20 Temp|(% colspan="1" style="width:141px" %)adc0|(% colspan="1" style="width:142px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)Weight|(% colspan="1" style="width:137px" %) |(% colspan="1" style="width:69px" %) |(% colspan="1" style="width:65px" %)
412 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod6|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:139px" %)count|(% colspan="1" style="width:141px" %) |(% colspan="1" style="width:142px" %) |(% colspan="1" style="width:151px" %) |(% colspan="1" style="width:137px" %) |(% colspan="1" style="width:69px" %) |(% colspan="1" style="width:65px" %)
270 270  
271 271  == 3.4 [[Datacake>>https://datacake.co/]] ==
272 272  
... ... @@ -274,92 +274,107 @@
274 274  Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
275 275  
276 276  (% class="wikigeneratedid" %)
277 -As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
420 +As example for S31B-CB. there are two versions: **S31B-CB-1D and S31B-CB-GE.**
278 278  
279 -* (% style="color:blue" %)**S31B-NB-1D**(%%): This version have pre-configure DataCake connection. User just need to Power on this device, it will auto connect send data to DataCake Server.
422 +* (% style="color:blue" %)**S31B-CB-1D**(%%): This version have pre-configure DataCake connection. User just need to Power on this device, it will auto connect send data to DataCake Server.
280 280  
281 -* (% style="color:blue" %)**S31B-NB-GE**(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction.
424 +* (% style="color:blue" %)**S31B-CB-GE**(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction.
282 282  
283 283  === 3.4.1 For device Already has template ===
284 284  
285 285  ==== 3.4.1.1 Create Device ====
286 286  
430 +
287 287  (% style="color:blue" %)**Add Device**(%%) in DataCake.
288 288  
289 -[[image:image-20230808162301-1.png||height="453" width="952"]]
433 +[[image:image-20240820110003-1.png]]
290 290  
291 -[[image:image-20230808162342-2.png||height="541" width="952"]]
435 +[[image:image-20240820110017-2.png]]
292 292  
293 293  (% style="color:blue" %)**Choose the correct model**(%%) from template.
294 294  
295 -[[image:image-20230808162421-3.png]]
439 +[[image:image-20240820110031-3.png]]
296 296  
297 297  (% 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.
298 298  
299 -[[image:image-20230808163612-7.png||height="549" width="952"]]
443 +[[image:image-20240820110048-4.png]]
300 300  
301 -[[image:image-20230808163035-5.png]]
445 +[[image:image-20240820110103-5.png]]
302 302  
303 -[[image:image-20230808163049-6.png||height="544" width="926"]]
447 +[[image:image-20240820110114-6.png]]
304 304  
449 +
305 305  === 3.4.2 For Device already registered in DataCake before shipped ===
306 306  
307 307  ==== 3.4.2.1 Scan QR Code to get the device info ====
308 308  
454 +
309 309  Users can use their phones or computers to scan QR codes to obtain device data information.
310 310  
311 -[[image:image-20230808170051-8.png||height="255" width="259"]]
457 +[[image:image-20240820110129-7.png]]
312 312  
313 -[[image:image-20230808170548-9.png]]
459 +[[image:image-20240820110218-9.png]]
314 314  
461 +
315 315  ==== 3.4.2.2 Claim Device to User Account ====
316 316  
317 317  By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
318 318  
466 +
319 319  === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
320 320  
469 +
321 321  **Step1: Add a device**
322 322  
323 -[[image:image-20240129170024-1.png||height="330" width="900"]]
472 +[[image:image-20240820110235-10.png]][[image:image-20240129170024-1.png||height="330" width="900"]]
324 324  
474 +
325 325  **Step2: Choose your device type,please select dragino NB-IOT device**
326 326  
327 -[[image:image-20240129170216-2.png||height="534" width="643"]]
477 +[[image:image-20240820110247-11.png]]
328 328  
479 +
329 329  **Step3: Choose to create a new device**
330 330  
331 -[[image:image-20240129170539-3.png||height="459" width="646"]]
482 +[[image:image-20240820111016-12.png]]
332 332  
484 +
333 333  **Step4: Fill in the device ID of your NB device**
334 334  
335 -[[image:image-20240202111546-1.png||height="378" width="651"]]
487 +[[image:image-20240820111101-13.png]]
336 336  
489 +
337 337  **Step5: Please select your device plan according to your needs and complete the creation of the device**
338 338  
339 -[[image:image-20240129171236-6.png||height="450" width="648"]]
492 +[[image:image-20240820111113-14.png]]
340 340  
494 +
341 341  **Step6: Please add the decoder at the payload decoder of the device configuration.**
342 342  
343 343  **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]]
344 344  
345 -[[image:image-20240129172056-7.png||height="457" width="816"]]
499 +[[image:image-20240820111236-15.png]]
346 346  
347 -[[image:image-20240129173116-9.png||height="499" width="814"]]
501 +[[image:image-20240820111248-16.png]]
348 348  
503 +
349 349  **Step7: Add the output of the decoder as a field**
350 350  
351 -[[image:image-20240129173541-10.png||height="592" width="968"]]
506 +[[image:image-20240820111259-17.png]]
352 352  
508 +
353 353  **Step8: Customize the dashboard and use fields as parameters of the dashboard**
354 354  
355 -[[image:image-20240129174518-11.png||height="147" width="1042"]]
511 +[[image:image-20240820111312-18.png]]
356 356  
357 -[[image:image-20240129174657-12.png||height="538" width="916"]]
513 +[[image:image-20240820111322-19.png]]
358 358  
359 -[[image:image-20240129174840-13.png||height="536" width="750"]]
515 +[[image:image-20240820111333-20.png]]
360 360  
517 +
361 361  === 3.4.4 For device have not configured to connect to DataCake ===
362 362  
520 +
363 363  (% class="lead" %)
364 364  Use AT command for connecting to DataCake
365 365  
... ... @@ -367,10 +367,12 @@
367 367  
368 368  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
369 369  
528 +
370 370  == 3.5 Node-Red (via MQTT) ==
371 371  
372 372  === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
373 373  
533 +
374 374  Take S31-NB UDP protocol as an example.
375 375  
376 376  Dragino provides input flow examples for the sensors.
... ... @@ -383,34 +383,38 @@
383 383  
384 384  The templates for S31-NB and NB95S31B are the same.
385 385  
386 -[[image:image-20230809173127-4.png]]
546 +[[image:image-20240820111353-21.png]]
387 387  
388 388  Please select the NB95S31B template.
389 389  
390 -[[image:image-20230809173310-5.png||height="558" width="926"]]
550 +[[image:image-20240820111405-22.png]]
391 391  
392 -[[image:image-20230809173438-6.png]]
552 +[[image:image-20240820111418-23.png]]
393 393  
394 -[[image:image-20230809173800-7.png]]
554 +[[image:image-20240820111427-24.png]]
395 395  
396 396  Successfully imported template.
397 397  
398 -[[image:image-20230809173835-8.png||height="515" width="860"]]
558 +[[image:image-20240820111438-25.png]]
399 399  
400 400  Users can set UDP port.
401 401  
402 -[[image:image-20230809174053-9.png]]
562 +[[image:image-20240820111448-26.png]]
403 403  
564 +
404 404  === 3.5.2 Simulate Connection ===
405 405  
567 +
406 406  We have completed the configuration of UDP. We can try sending packets to node red.
407 407  
408 -[[image:image-20230810083934-1.png]]
570 +[[image:image-20240820111504-27.png]]
409 409  
410 -[[image:image-20230810084048-2.png||height="535" width="1052"]]
572 +[[image:image-20240820111515-28.png]]
411 411  
574 +
412 412  === 3.5.3 Configure NB-IoT Sensors ===
413 413  
577 +
414 414  * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
415 415  * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
416 416  * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
... ... @@ -424,12 +424,15 @@
424 424  
425 425  ==== 3.6.1.1 Create Device ====
426 426  
591 +
427 427  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
428 428  
429 -[[image:image-20230802112413-32.png||height="583" width="1066"]]
594 +[[image:image-20240820112210-29.png]]
430 430  
596 +
431 431  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
432 432  
599 +
433 433  (% style="color:blue" %)**Uplink Converter**
434 434  
435 435  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.
... ... @@ -436,27 +436,29 @@
436 436  
437 437  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.
438 438  
439 -[[image:image-20230802112413-33.png||height="597" width="1061"]]
606 +[[image:image-20240820112222-30.png]]
440 440  
441 441  (% style="color:blue" %)**Downlink Converter**
442 442  
443 443  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
444 444  
445 -[[image:image-20230802112413-34.png||height="598" width="1063"]]
612 +[[image:image-20240820112236-31.png]]
446 446  
447 447  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
448 448  
616 +
449 449  ==== 3.6.1.3 MQTT Integration Setup ====
450 450  
619 +
451 451  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**;
452 452  
453 -[[image:image-20230802112413-35.png||height="597" width="1062"]]
622 +[[image:image-20240820112247-32.png]]
454 454  
455 455  * The next steps is to add the recently created uplink and downlink converters;
456 456  
457 -[[image:image-20230802112413-36.png||height="598" width="1062"]]
626 +[[image:image-20240820112302-33.png]]
458 458  
459 -[[image:image-20230802112413-37.png||height="598" width="1064"]]
628 +[[image:image-20240820112316-34.png]]
460 460  
461 461  (% style="color:blue" %)**Add a topic filter:**
462 462  
... ... @@ -464,16 +464,19 @@
464 464  
465 465  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
466 466  
467 -[[image:image-20230802112413-38.png||height="598" width="1064"]]
636 +[[image:image-20240820112330-35.png]]
468 468  
638 +
469 469  === 3.6.2 Simulate with MQTT.fx ===
470 470  
471 -[[image:image-20230802112413-39.png]]
641 +[[image:image-20240820112340-36.png]]
472 472  
473 -[[image:image-20230802112413-40.png||height="525" width="980"]]
643 +[[image:image-20240820112351-37.png]]
474 474  
645 +
475 475  === 3.6.3 Configure NB-IoT Sensor ===
476 476  
648 +
477 477  (% style="color:blue" %)**AT Commands**
478 478  
479 479  * (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
... ... @@ -490,25 +490,98 @@
490 490  
491 491  Test Uplink by click the button for 1 second
492 492  
493 -[[image:image-20230802112413-41.png||height="496" width="828"]]
665 +[[image:image-20240820112404-38.png]]
494 494  
495 -[[image:image-20230802112413-42.png]]
667 +[[image:image-20240820112416-39.png]]
496 496  
497 -[[image:image-20230802112413-43.png||height="407" width="825"]]
669 +[[image:image-20240820112426-40.png]]
498 498  
499 -== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
500 500  
501 -=== 3.7.1 Create device & Get Credentials ===
502 502  
673 +== 3.7 ThingsBoard.Cloud (via COAP) ==
674 +
675 +=== 3.7.1 Configure ThingsBoard ===
676 +
677 +==== 3.7.1.1 Create Uplink & Downlink Converter ====
678 +
679 +
680 +(% style="color:blue" %)**Uplink Converter**
681 +
682 +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.
683 +
684 +To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** (%%)button. Name it (% style="color:blue" %)**“COAP Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
685 +
686 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729141300-1.png?width=1115&height=552&rev=1.1||alt="image-20240729141300-1.png" height="579" width="1168"]]
687 +
688 +
689 +(% style="color:blue" %)**Downlink Converter**
690 +
691 +The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
692 +
693 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729142505-3.png?width=1023&height=507&rev=1.1||alt="image-20240729142505-3.png" height="579" width="1168"]]
694 +
695 +
696 +==== 3.7.1.2 COAP Integration Setup ====
697 +
698 +
699 +Go to the (% style="color:blue" %)**Integrations center**(%%) **->** (% style="color:blue" %)**Integrations page**(%%) and click **“(% style="color:blue" %)plus(%%)”** icon to add a new integration. Name it (% style="color:blue" %)**“CoAP Integration”**(%%), select type **COAP    **(% style="color:blue" %);
700 +
701 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729144058-4.png?width=1021&height=506&rev=1.1||alt="image-20240729144058-4.png" height="583" width="1176"]]
702 +
703 +
704 +The next steps is to add the recently created uplink converters;
705 +
706 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729150142-5.png?width=1023&height=507&rev=1.1||alt="image-20240729150142-5.png" height="591" width="1193"]]
707 +
708 +
709 +==== 3.7.1.3 Add COAP Integration ====
710 +
711 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729161543-9.png?width=1009&height=500&rev=1.1||alt="image-20240729161543-9.png" height="590" width="1191"]]
712 +
713 +
714 +=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
715 +
716 +==== 3.7.2.1 Instruction Description ====
717 +
718 +
719 +* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
720 +* AT+SERVADDR=COAP Server Address,5683
721 +
722 +Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
723 +
724 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729172305-12.png?width=624&height=361&rev=1.1||alt="image-20240729172305-12.png" height="417" width="721"]]
725 +
726 +Note:The port for the COAP protocol has been fixed to 5683
727 +
728 +
729 +* AT+URL1=11,"i"
730 +* AT+URL2=11,"Needs to be consistent with the CoAP endpoint URL in the platform"
731 +*
732 +
733 +-CB devices using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
734 +
735 +e.g.
736 +
737 +* AT+URL1=11, "i"
738 +* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
739 +
740 +[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729172500-14.png?width=700&height=403&rev=1.1||alt="image-20240729172500-14.png" height="413" width="718"]]
741 +
742 +
743 +== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
744 +
745 +=== 3.8.1 Create device & Get Credentials ===
746 +
747 +
503 503  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.
504 504  
505 -[[image:image-20230802112413-44.png]]
750 +[[image:image-20240820112516-41.png]]
506 506  
507 -[[image:image-20230802112413-45.png]]
752 +[[image:image-20240820112526-42.png]]
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 -[[image:image-20230802112413-46.png]]
756 +[[image:image-20240820112539-43.png]]
512 512  
513 513  The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
514 514  
... ... @@ -546,50 +546,59 @@
546 546  
547 547  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
548 548  
549 -=== 3.7.2 Simulate with MQTT.fx ===
794 +=== 3.8.2 Simulate with MQTT.fx ===
550 550  
551 -[[image:image-20230802112413-52.png]]
552 552  
553 -[[image:image-20230808105300-2.png||height="553" width="1026"]]
797 +[[image:image-20240820112552-44.png]]
554 554  
799 +[[image:image-20240820112604-45.png]]
800 +
555 555  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
556 556  
557 -[[image:image-20230808105217-1.png||height="556" width="1031"]]
803 +[[image:image-20240820112615-46.png]]
558 558  
559 -[[image:image-20230808105329-3.png]]
805 +[[image:image-20240820112626-47.png]]
560 560  
561 -=== 3.7.3 tago data ===
562 562  
563 -[[image:image-20230802112413-50.png||height="242" width="1037"]]
808 +=== 3.8.3 tago data ===
564 564  
565 -[[image:image-20230802112413-51.png||height="184" width="696"]]
566 566  
567 -== 3.8 TCP Connection ==
811 +[[image:image-20240820112637-48.png]]
568 568  
813 +[[image:image-20240820112647-49.png]]
814 +
815 +
816 +== 3.9 TCP Connection ==
817 +
818 +
569 569  (% style="color:blue" %)**AT command:**
570 570  
571 571  * (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
572 572  
573 -* (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
823 +* (% style="color:#037691" %)**AT+PRO=4,5   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
574 574  
575 575  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
576 576  
577 577  (% style="color:blue" %)**Sensor Console Output when Uplink:**
578 578  
579 -[[image:image-20230807233631-1.png]]
829 +[[image:image-20240820112704-50.png]]
580 580  
581 581  (% style="color:blue" %)**See result in TCP Server:**
582 582  
583 -[[image:image-20230807233631-2.png]]
833 +[[image:image-20240820112716-51.png]]
584 584  
585 -== 3.9 AWS Connection ==
586 586  
836 +== 3.10 AWS Connection ==
837 +
838 +
587 587  Users can refer to [[Dragino NB device connection to AWS platform instructions>>http://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H1.LogintotheplatformandfindIoTcore]]
588 588  
589 -= 4. MQTT/UDP/TCP downlink =
590 590  
842 += 4. COAP/UDP/MQTT/TCP downlink =
843 +
591 591  == 4.1 MQTT (via MQTT.fx) ==
592 592  
846 +
593 593  Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
594 594  
595 595  **1.** Configure node MQTT connection (via MQTT.fx):
... ... @@ -610,12 +610,14 @@
610 610  
611 611  (% style="color:red" %)**Note: To uplink and downlink via MQTT.fx, we need set the publish topic and subscribe topic different, for example: AT+SUBTOPIC=SE01_SUB & AT+PUBTOPIC=SE01_PUB.**
612 612  
613 -[[image:image-20240417180145-2.png||height="434" width="587"]][[ width="584">> width="584"]]
867 +[[image:image-20240820112732-52.png]][[image:image-20240820112758-53.png]]
614 614  
869 +
615 615  **2. **When the node uplink packets, we can observe the data in MQTT.fx.
616 616  
617 -[[image:image-20240418144337-1.png||height="709" width="802"]]
872 +[[image:image-20240820112813-54.png]]
618 618  
874 +
619 619  **3. **The downlink command can be successfully sent only when the downlink port is open.
620 620  
621 621   The downlink port is opened for about 3 seconds after uplink packets are sent.
... ... @@ -622,16 +622,69 @@
622 622  
623 623   Therefore, when we see the node uplink packets in the **Subscribe** window, we need to immediately switch to the **publish** window to publish the **hex format** command.
624 624  
625 -[[image:image-20240418150435-3.png||height="582" width="659"]]
881 +[[image:image-20240820112824-55.png]]
626 626  
627 -[[image:image-20240418150932-4.png||height="492" width="1061"]]
883 +[[image:image-20240820112835-56.png]]
628 628  
629 629  (% style="color:red" %)**Note: Users can edit the hex command in advance. When the node uplink, directly click the publish button several times to increase the success rate of command configuration.**
630 630  
631 -= 5. FAQ =
632 632  
633 -== 5.1 What is the usage of Multi Sampling and One Uplink? ==
888 +== 4.2 UDP (via Thingseye) ==
634 634  
890 +
891 +(% style="color:red" %)**Note:**(%%) The UDP service on the ThingsEye platform needs to be built by the user. (Description Link:[[UDP service building instructions>>http://www.ithingsboard.com/docs/user-guide/integrations/udp/]])
892 +
893 +After the node is successfully connected to the platform, you need to select the corresponding node (you can refer to the node's IMEI to find it)
894 +
895 +[[image:image-20240820141843-2.png||height="546" width="821"]]
896 +
897 +After clicking Show Node Details Page, (% style="color:blue" %)**Select Properties ~-~-- select Shared Properties ~-~-- click Add Properties**
898 +
899 +[[image:image-20240820143316-3.png||height="555" width="1170"]]
900 +
901 +After clicking Add Shared Attribute, set the key to (% style="color:red" %)**value**(%%), and write the command that needs to be downlinked in the Downlink Command Input box
902 +
903 +(% style="color:red" %)**(Note: Downlinks can only be downlinked in string format, otherwise the node will not recognize the downlink command.)**
904 +
905 +[[image:image-20240820143820-4.png||height="554" width="1168"]]
906 +
907 +After the command is successfully added, the platform will send the command down on the node's next uplink.
908 +
909 +[[image:image-20240820144913-6.png||height="585" width="1232"]]
910 +
911 +[[image:image-20240820145133-7.png||height="582" width="1227"]]
912 +
913 +Upon successful issuance, the platform automatically eliminates the attributes from the queue and waits for the next addition of new attributes
914 +
915 +[[image:image-20240820145309-8.png]]
916 +
917 +
918 += 5. GPS positioning function =
919 +
920 +== 1. Turn on GPS function ==
921 +
922 +
923 +(% class="wikigeneratedid" %)
924 +AT+GPS=1 or 0  ~/~/ GPS function on or off
925 +
926 +
927 +== 2. Extend the time to turn on GNSS ==
928 +
929 +
930 +AT+GNSST=30  ~/~/ GPS search for positioning information for 30 seconds
931 +
932 +
933 +== 3. Get or set GPS positioning interval in units of hour ==
934 +
935 +
936 +AT+GTDC=24  ~/~/ The device will activate GPS positioning every 24 hours
937 +
938 +
939 += 6. FAQ =
940 +
941 +== 6.1 What is the usage of Multi Sampling and One Uplink? ==
942 +
943 +
635 635  The NB series has the feature for Multi Sampling and one uplink. See one of them
636 636  
637 637  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink]]
... ... @@ -646,27 +646,30 @@
646 646  1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours.
647 647  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.
648 648  
649 -== 5.2 Why the uplink JSON format is not standard? ==
958 +== 6.2 Why the uplink JSON format is not standard? ==
650 650  
960 +
651 651  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.
652 652  
653 653  The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
654 654  
655 -[[image:image-20240229233154-1.png]]
965 +[[image:image-20240820112848-57.png]]
656 656  
657 -= 6. Trouble Shooting: =
658 658  
659 -== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
968 += 7. Trouble Shooting: =
660 660  
970 +== 7.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
971 +
972 +
661 661  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.
662 662  
663 663  If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
664 664  
665 -[[image:image-20240207002003-1.png]]
977 +[[image:image-20240820112859-58.png]]
666 666  
667 667  If fail to attach network, it will shows signal 99. as below:
668 668  
669 -[[image:image-20240207002129-2.png]]
981 +[[image:image-20240820112908-59.png]]
670 670  
671 671  (% class="lead" %)
672 672  When see this issue, below are the checklist:
... ... @@ -680,14 +680,16 @@
680 680  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.
681 681  
682 682  
683 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
995 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.2 Why sometime the AT Command is slow in reponse?(%%) ==
684 684  
997 +
685 685  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.
686 686  
687 -[[image:image-20240226111928-1.png]]
1000 +[[image:image-20240820113015-60.png]]
688 688  
689 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
690 690  
1003 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.3 What is the Downlink Command by the -CB device?(%%) ==
1004 +
691 691  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
692 692  === UDP: ===
693 693  
... ... @@ -697,6 +697,7 @@
697 697  
698 698  {AT+TDC=300}
699 699  
1014 +
700 700  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
701 701  === MQTT: ===
702 702  
... ... @@ -738,5 +738,136 @@
738 738  
739 739  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
740 740  
1056 +
1057 +== 7.4 What if the signal is good but the domain name resolution fails? ==
1058 +
1059 +
1060 +If the domain name resolution fails, first check whether the domain name is correct, users can use their own website domain name resolution tool to verify the domain name.
1061 +
1062 +[[image:image-20240827150705-6.png||height="489" width="687"]]
1063 +
1064 +If the domain name is correct, but the domain name cannot be resolved, the user can turn off the domain name resolution function(AT+GDNS=1) and use the domain name communication directly.
1065 +
1066 +* Set the DNS
1067 +
1068 +(% style="color:blue" %)**AT Command: AT+GDNS**
1069 +
1070 +**AT+GDNS=0**  ~/~/ Default. Automatically resolves the domain name and uses the resolved IP to communicate.
1071 +
1072 +**AT+GDNS=1    **~/~/ Disabling Domain name resolution. Use the domain name directly to communicate.
1073 +
1074 +(% style="color:red" %)**Note: For -CB products, with the exception of AT+PRO=2,5, all protocols and payload formats support direct domain communication.**
1075 +
1076 +Example:
1077 +
1078 +[[image:image-20240827150121-5.png||height="473" width="676"]][[image:image-20240827145055-4.png||height="474" width="665"]]
1079 +
1080 +
1081 +== 7.5 GPS debugging ==
1082 +
1083 +
1084 +Indoor GPS signal is very weak, **outdoor** positioning is generally recommended.
1085 +
1086 +[[image:image-20240903104250-9.png||height="275" width="614"]]
1087 +
1088 +
1089 +[[image:image-20240903104431-10.png||height="291" width="621"]]
1090 +
1091 +
1092 +=== 7.5.1 GPS commands ===
1093 +
1094 +
1095 +The following are three related AT commands that introduce GPS functions.
1096 +
1097 +* **Turn on/off GPS**
1098 +
1099 +(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GPS **
1100 +
1101 +**Ex1:  **AT+GPS=0  ~/~/ Turn off GPS
1102 +
1103 +**Ex2:  **AT+GPS=1  ~/~/ Turn on GPS
1104 +
1105 +(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x11(%%)**
1106 +
1107 +Format: Command Code (0x11) followed by 1 byte.
1108 +
1109 +Example:  Downlink Payload: **11 01   **~/~/ AT+GPS=1
1110 +
1111 +* **Set GNSS open time**
1112 +
1113 +Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated.
1114 +
1115 +(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GNSST**
1116 +
1117 +Example: AT+GNSST=30  ~/~/ Set the GPS positioning time to 30 seconds
1118 +
1119 +(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x10(%%)**
1120 +
1121 +Format: Command Code (0x10) followed by 2 bytes.
1122 +
1123 +Example:  Downlink Payload: **10 00 1E    **~/~/ AT+GNSST=30
1124 +
1125 +* **Set GPS positioning interval**
1126 +
1127 +Feature: Set GPS positioning interval (unit: hour).
1128 +
1129 +When GPS is enabled, the node automatically locates and uplinks each time it passes **GTDC time** after activation.
1130 +
1131 +(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GTDC**
1132 +
1133 +Example: AT+GTDC=24  ~/~/ Set the GPS positioning interval to 24h.
1134 +
1135 +(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x12(%%)**
1136 +
1137 +Format: Command Code (0x12) followed by 3 bytes.
1138 +
1139 +Example: 24 hours:  24(D)=0x18(H)
1140 +
1141 +Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
1142 +
1143 +
1144 +=== 7.5.2 GPS workflow ===
1145 +
1146 +
1147 +The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
1148 +
1149 +~1. When activate the node, the node will turn on the GNSS, if the GPS signal is good, the node will print and upload the position information with the first data packet immediately.
1150 +
1151 + If the signal is not good, it may take the whole (% style="color:#037691" %)**GNSST**(%%) time but still can not search the latitude and longitude information, at this time the node uploads the latitude and longitude all to 0.
1152 +
1153 + So if there is a failure of positioning, the user can extend the (% style="color:#037691" %)**GNSST**(%%) time appropriately.
1154 +
1155 +2. Each TDC time node is not repositioned and the positioning interval is determined by the AT+GTDC time.
1156 +
1157 + The latitude and longitude payload uplinked at each TDC time is the GPS positioning information from the previous (% style="color:#037691" %)**GTDC**(%%) time.
1158 +
1159 + Only when the node is activated or every (% style="color:#037691" %)**GTDC**(%%) time is reached, the node turns on the GNSS and we can observe the GPS search information through the serial assistant or Bluetooth tool.
1160 +
1161 +
1162 +=== 7.5.3 GPS debugging methods ===
1163 +
1164 +
1165 +In summary, we can deduce the methods of debugging GPS:
1166 +
1167 +* **Check whether the GPS function is enabled.**
1168 +
1169 +[[image:image-20240903102327-5.png||height="271" width="529"]]
1170 +
1171 +* **Check whether the GPS antenna is loose**.
1172 +
1173 +If the GPS antenna is loose, the GPS signal is weak, and the positioning fails.
1174 +
1175 +[[image:image-20240903094214-1.png||height="340" width="461"]]
1176 +
1177 +* **Use the AT+GNSST command to extend the positioning time.**
1178 +
1179 +The default AT+GNSST=30, that is, the default positioning time is 30 seconds.
1180 +
1181 +If the location fails, users can extend the location time.
1182 +
1183 +[[image:image-20240903102641-8.png||height="303" width="600"]]
1184 +
1185 +
1186 +
1187 +
741 741  
742 -​
image-20240819102802-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +41.5 KB
Content
image-20240819103212-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +49.5 KB
Content
image-20240819103826-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +122.4 KB
Content
image-20240819103909-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +122.2 KB
Content
image-20240819104904-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +52.1 KB
Content
image-20240819104942-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +52.1 KB
Content
image-20240819105003-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +48.2 KB
Content
image-20240819105418-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +163.8 KB
Content
image-20240819112109-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +12.9 KB
Content
image-20240819173602-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +52.3 KB
Content
image-20240819173659-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +44.8 KB
Content
image-20240819173706-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +44.8 KB
Content
image-20240819173826-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +42.3 KB
Content
image-20240819174033-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +33.1 KB
Content
image-20240819174209-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +18.9 KB
Content
image-20240819174314-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +48.4 KB
Content
image-20240819174540-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +99.8 KB
Content
image-20240819174610-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +127.8 KB
Content
image-20240819174618-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +34.6 KB
Content
image-20240820110003-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +66.5 KB
Content
image-20240820110017-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +78.3 KB
Content
image-20240820110031-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +59.2 KB
Content
image-20240820110048-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +64.0 KB
Content
image-20240820110103-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +71.6 KB
Content
image-20240820110114-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +77.4 KB
Content
image-20240820110129-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +10.7 KB
Content
image-20240820110142-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +54.1 KB
Content
image-20240820110218-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +66.7 KB
Content
image-20240820110235-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +21.2 KB
Content
image-20240820110247-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +49.8 KB
Content
image-20240820111016-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +65.8 KB
Content
image-20240820111101-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +36.3 KB
Content
image-20240820111113-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +55.7 KB
Content
image-20240820111236-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +42.0 KB
Content
image-20240820111248-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +58.4 KB
Content
image-20240820111259-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +58.0 KB
Content
image-20240820111312-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +13.9 KB
Content
image-20240820111322-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +68.2 KB
Content
image-20240820111333-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +47.0 KB
Content
image-20240820111353-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +82.5 KB
Content
image-20240820111405-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +57.6 KB
Content
image-20240820111418-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +41.0 KB
Content
image-20240820111427-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +46.8 KB
Content
image-20240820111438-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +139.6 KB
Content
image-20240820111448-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +58.0 KB
Content
image-20240820111504-27.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +85.1 KB
Content
image-20240820111515-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +45.3 KB
Content
image-20240820112210-29.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +96.9 KB
Content
image-20240820112222-30.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +149.6 KB
Content
image-20240820112236-31.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +170.6 KB
Content
image-20240820112247-32.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +105.5 KB
Content
image-20240820112302-33.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +112.9 KB
Content
image-20240820112316-34.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +96.4 KB
Content
image-20240820112330-35.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +127.0 KB
Content
image-20240820112340-36.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +24.7 KB
Content
image-20240820112351-37.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +68.4 KB
Content
image-20240820112404-38.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +40.2 KB
Content
image-20240820112416-39.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +40.9 KB
Content
image-20240820112426-40.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +101.4 KB
Content
image-20240820112516-41.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +78.6 KB
Content
image-20240820112526-42.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +128.5 KB
Content
image-20240820112539-43.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +31.2 KB
Content
image-20240820112552-44.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +28.4 KB
Content
image-20240820112604-45.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +60.9 KB
Content
image-20240820112615-46.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +60.5 KB
Content
image-20240820112626-47.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +21.1 KB
Content
image-20240820112637-48.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +53.1 KB
Content
image-20240820112647-49.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +37.8 KB
Content
image-20240820112704-50.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +21.9 KB
Content
image-20240820112716-51.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +9.6 KB
Content
image-20240820112732-52.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +95.3 KB
Content
image-20240820112758-53.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +34.7 KB
Content
image-20240820112813-54.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +127.7 KB
Content
image-20240820112824-55.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +24.0 KB
Content
image-20240820112835-56.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +70.6 KB
Content
image-20240820112848-57.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +39.5 KB
Content
image-20240820112859-58.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content
image-20240820112908-59.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +17.9 KB
Content
image-20240820113015-60.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +52.0 KB
Content
image-20240820140935-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +159.2 KB
Content
image-20240820141136-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +107.6 KB
Content
image-20240820141746-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +122.2 KB
Content
image-20240820141843-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +123.2 KB
Content
image-20240820143316-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +152.3 KB
Content
image-20240820143820-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +161.7 KB
Content
image-20240820144823-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +145.6 KB
Content
image-20240820144913-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +136.4 KB
Content
image-20240820145133-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +164.5 KB
Content
image-20240820145309-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +32.6 KB
Content
image-20240827145055-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +74.2 KB
Content
image-20240827150121-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +86.0 KB
Content
image-20240827150705-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +86.7 KB
Content
image-20240903094214-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +4.5 MB
Content
image-20240903094457-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +2.6 MB
Content
image-20240903100736-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +250.8 KB
Content
image-20240903100832-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +181.5 KB
Content
image-20240903102327-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +26.2 KB
Content
image-20240903102542-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +16.9 KB
Content
image-20240903102621-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +21.9 KB
Content
image-20240903102641-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +21.0 KB
Content
image-20240903104250-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +46.9 KB
Content
image-20240903104431-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +49.2 KB
Content
image-20250113103816-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +13.6 KB
Content