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

From version 3.1
edited by Edwin Chen
on 2024/06/02 21:55
Change comment: There is no comment for this version
To version 129.2
edited by Xiaoling
on 2024/09/14 10:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -23,48 +23,164 @@
23 23  1. Power On End Node
24 24  1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>), example AT+APN=iot.1nce.net
25 25  
26 -[[image:image-20240208102804-1.png||height="286" width="696"]]
26 +[[image:image-20240602220856-1.png]]
27 27  
28 -[[image:image-20230808205045-1.png||height="293" width="438"]]
29 29  
29 +放一张如何插卡图片。
30 +
31 +
30 30  After doing above, the end nodes should be able to attach to NB-IoT network .
31 31  
32 32  The -CB and -CS models support (% style="color:blue" %)**LTE Cat NB2 and LTE-M (CAT-M1)**(%%), with below frequency band: multiple frequency bands of
33 33  
34 -~-~-(% style="color:blue" %)**CAT-NB2: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B28/B66/B71/B85 **(%%).
36 +~-~-(% style="color:blue" %)** CAT-NB2: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B28/B66/B71/B85 **(%%).
35 35  
36 -~-~-(% style="color:blue" %)**CAT-M1: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85 **(%%).
38 +~-~-(% style="color:blue" %)** CAT-M1: B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85 **(%%).
37 37  
38 -Make sure you use a the NB-IoT SIM card.
40 +Make sure you use a the NB-IoT or LTE-M SIM card.
39 39  
40 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
41 -|(% 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**
42 -|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
42 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1134px" %)
43 +|(% 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:406px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:351px" %)**LTE-M Coverage**|(% style="background-color:#4f81bd; color:white; width:120px" %)**Comments**
44 +|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:406px" %)(((
43 43  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
44 44  
45 -Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, UK, US Virgin Islands
46 -)))|(% style="width:135px" %)UK: Band20
47 -|(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
48 -|(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
47 +Austria, Belgium, Bulgaria, China, Croatia, Czech Republic, Denmark, Estonia, Finland, Germany, Great Britain, Greece, Hungary, Ireland,Italy, Latvia, Malta, Netherlands, Norway, Portugal, Puerto Rico, Russia, Slovak,Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands
48 +)))|(% style="width:351px" %)(((
49 +Argentina, Austria, Australia, Belgium, Canada, Denmark,Estonia, Finland, France, Germany, Great Britain, Hungary, Ireland, Japan,Jersey, Korea, Repiblic of, Latvia, Luxembourg, Mexico, Netherlands, New Zealand, Norway, Poland, Puerto Rico, Romania, Spain, Sweden, Switzerland,Taiwan, USA, US Virgin Islands.
50 +)))|(% style="width:120px" %)UK: Band20
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 +|(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:406px" %)China Mainland|(% style="width:351px" %) |(% style="width:120px" %)
49 49  
50 50  == 2.2 Speed Up Network Attach time ==
51 51  
52 -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.
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**.
53 53  
54 -(% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
55 -(% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
56 -(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
57 -(% style="color:#037691" %)**Global General**(%%) : **AT+QBAND=10,8,20,28,2,4,12,13,66,85,5**
58 +**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 -(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
60 -(% style="color:#037691" %)**AT&T**(%%) AT+QBAND=3,12,4,2
61 -(% style="color:#037691" %)**Telstra**(%%) AT+QBAND=1,28
62 -(% style="color:#037691" %)**Softband**(%%) AT+QBAND=2,3,8
60 +Attache to 1NCE card for Australia use:
63 63  
64 -After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
62 +* AT+COPS=1,2,"50501",8
63 +* AT+QCFG="band",0,0x8000000,0x8000000,1
65 65  
65 +After connection is successful, user can use (% style="color:#037691" %)**AT+QENG="servingcell"**(%%) to check which band is actually in used.
66 +
67 +AT+QENG="servingcell"
68 ++QENG: "servingcell","NOCONN","eMTC","FD
69 +D",505,01,90D2C0B,258,9410,28,5,5,901A,-112,-17,-80,10,27
70 +
71 +
66 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 67  
74 +=== **1.Configure Frequency Band** ===
75 +
76 +AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
77 +
78 +<GSM_bandval>:
79 +
80 +0 No change 
81 +0x1 EGSM900
82 +0x2 DCS1800
83 +0x4 GSM850 
84 +0x8 PCS1900 
85 +0xF All of the supported bands above
86 +
87 +<eMTC_bandval>:
88 +
89 +0 No change 
90 +0x1  LTE B1
91 +0x2  LTE B2 
92 +0x4  LTE B3 
93 +0x8  LTE B4 
94 +0x10  LTE B5 
95 +0x80  LTE B8 
96 +0x800  LTE B12 
97 +0x1000  LTE B13 
98 +0x20000  LTE B18 
99 +0x40000  LTE B19 
100 +0x80000  LTE B20 
101 +0x1000000  LTE B25 
102 +0x2000000  LTE B26 
103 +0x4000000  LTE B27 
104 +0x8000000  LTE B28 
105 +0x40000000  LTE B31 
106 +0x20000000000000000  LTE B66 
107 +0x800000000000000000  LTE B72 
108 +0x1000000000000000000  LTE B73 
109 +0x1000000000000000000000  LTE B85
110 +
111 +<NB-IoT_bandval>:
112 +
113 +0 No change 
114 +0x1  LTE B1
115 +0x2  LTE B2 
116 +0x4  LTE B3 
117 +0x8  LTE B4 
118 +0x10  LTE B5 
119 +0x80  LTE B8 
120 +0x800  LTE B12 
121 +0x1000  LTE B13 
122 +0x20000  LTE B18 
123 +0x40000  LTE B19 
124 +0x80000  LTE B20 
125 +0x1000000  LTE B25 
126 +0x8000000  LTE B28 
127 +0x40000000  LTE B31 
128 +0x20000000000000000  LTE B66
129 +
130 +0x400000000000000000  LTE B71
131 +0x800000000000000000  LTE B72 
132 +0x1000000000000000000  LTE B73 
133 +0x1000000000000000000000  LTE B85
134 +
135 +For example, setting the LTE-M network frequency band to 3.
136 +
137 +AT+QCFG="band",0xF,0x4,0,1
138 +
139 +When searching for all bands, the value of this command is set to:
140 +
141 +AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
142 +
143 +
144 +=== **2.Configure search network sequence** ===
145 +
146 +AT+QCFG="nwscanseq",<scanseq>,1
147 +
148 +<scanseq>:
149 +
150 +00 Automatic (eMTC → NB-IoT → GSM) 
151 +01 GSM 
152 +02 eMTC 
153 +03 NB-IoT
154 +
155 +AT+QCFG="nwscanseq",02,1  ~/~/Priority search for eMTC
156 +
157 +=== **3.Configure Network Category to be Searched for under LTE RAT** ===
158 +
159 +AT+QCFG="iotopmode",mode,1
160 +
161 +0 eMTC 
162 +1 NB-IoT 
163 +2 eMTC and NB-IoT
164 +
165 +=== **4.AT command to set frequency band and network category** ===
166 +
167 +AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f  ~/~/<eMTC_bandval>,<NB-IoT_bandval>
168 +
169 +AT+IOTMOD=0  ~/~/ 0 eMTC  1 NB-IoT  2 eMTC and NB-IoT
170 +
171 +**Example :**
172 +
173 +Taking the use of 1nce cards in **the United States** as an example.
174 +
175 +AT+APN=iot.1nce.net  ~/~/set APN
176 +
177 +AT+QBAND=0x100180A,0  ~/~/ eMTC :Set frequency band B2,B4,B12,B13,B25  NB-IoT:No change
178 +
179 +AT+IOTMOD=0  ~/~/ Set  eMTC Network
180 +
181 +**Setting the above commands in the United States will greatly reduce the network search time of the NB module.**
182 +
183 +
68 68  = 3. Configure to connect to different servers =
69 69  
70 70  == 3.1 General UDP Connection ==
... ... @@ -71,30 +71,63 @@
71 71  
72 72  The NB-IoT Sensor can send packet to server use UDP protocol.
73 73  
190 +
74 74  === 3.1.1 Simulate UDP Connection by PC tool ===
75 75  
193 +
76 76  We can use PC tool to simulate UDP connection to make sure server works ok.
77 77  
78 -[[image:image-20230802112413-1.png||height="468" width="1024"]]
196 +[[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"]]
79 79  
198 +
80 80  === 3.1.2 Configure NB-IoT Sensor ===
81 81  
82 82  ==== 3.1.2.1 AT Commands ====
83 83  
203 +
84 84  (% style="color:blue" %)**AT Commands:**
85 85  
86 86  * (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload
87 87  
88 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/ Set UDP server address and port
208 +* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1999**  (%%) ~/~/ Set UDP server address and port
89 89  
90 -[[image:image-20230802112413-2.png]]
210 +[[image:image-20240819102802-1.png]]
91 91  
212 +
92 92  ==== 3.1.2.2 Uplink Example ====
93 93  
94 -[[image:image-20230802112413-3.png]]
95 95  
216 +[[image:image-20240819105418-8.png||height="611" width="1287"]]
217 +
218 +
219 +== 3.2 General COAP Connection ==
220 +
221 +
222 +The NB-IoT Sensor can send packet to server use COAP protocol.
223 +
224 +Below are the commands.
225 +
226 +(% style="color:blue" %)**AT Commands:**
227 +
228 +* (% style="color:#037691" %)**AT+PRO=1,0**   (%%) ~/~/ Set to use COAP protocol to uplink, Payload Type select Hex payload.
229 +
230 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%) ~/~/ Set COAP server address and port
231 +
232 +* (% style="color:#037691" %)**AT+URI1=11,"I"**  (%%) ~/~/  Configure CoAP Message Options
233 +* (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**    (%%) ~/~/ Configure CoAP Message Options
234 +
235 +[[image:image-20240819103212-2.png]]
236 +
237 +
238 +=== 3.2.1 Uplink Example ===
239 +
240 +
241 +[[image:image-20240819103909-4.png||height="453" width="955"]]
242 +
243 +
96 96  == 3.2 General MQTT Connection ==
97 97  
246 +
98 98  The NB-IoT Sensor can send packet to server use MQTT protocol.
99 99  
100 100  Below are the commands.
... ... @@ -115,29 +115,34 @@
115 115  
116 116  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB**  (%%) ~/~/ Set the subscription topic of MQTT
117 117  
118 -[[image:image-20230802112413-4.png]]
267 +[[image:image-20240819105003-7.png||height="613" width="458"]]
119 119  
120 -[[image:image-20230802112413-5.png||height="530" width="987"]]
121 121  
270 +[[image:image-20240819104942-6.png||height="702" width="974"]]
271 +
122 122  (% 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.**
123 123  
274 +
124 124  == 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
125 125  
126 126  === 3.3.1 Get MQTT Credentials ===
127 127  
279 +
128 128  [[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.
129 129  
130 -[[image:image-20230802112413-6.png||height="336" width="925"]]
282 +[[image:image-20240819173602-1.png||height="401" width="743"]]
131 131  
132 -[[image:image-20230802112413-7.png]]
284 +[[image:image-20240819173706-3.png||height="595" width="597"]]
133 133  
286 +
134 134  === 3.3.2 Simulate with MQTT.fx ===
135 135  
136 136  ==== 3.3.2.1 Establish MQTT Connection ====
137 137  
291 +
138 138  After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
139 139  
140 -[[image:image-20230802112413-8.png]]
294 +[[image:image-20240819173826-4.png||height="534" width="734"]]
141 141  
142 142  * (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
143 143  
... ... @@ -149,12 +149,14 @@
149 149  
150 150  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
151 151  
306 +
152 152  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
153 153  
154 -[[image:image-20230802112413-9.png]]
155 155  
156 -[[image:image-20230802112413-10.png]]
310 +[[image:image-20240819174033-5.png]]
157 157  
312 +[[image:image-20240819174209-6.png]]
313 +
158 158  (% style="color:blue" %)**In MQTT.fx, we can publish below info:**
159 159  
160 160  * (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
... ... @@ -165,12 +165,14 @@
165 165  
166 166  (% style="color:blue" %)**Result: **
167 167  
168 -[[image:image-20230802112413-11.png||height="539" width="901"]]
324 +[[image:image-20240819174314-7.png||height="469" width="785"]]
169 169  
326 +
170 170  === 3.3.3 Configure NB-IoT Sensor for connection ===
171 171  
172 172  ==== 3.3.3.1 AT Commands: ====
173 173  
331 +
174 174  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
175 175  
176 176  * (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
... ... @@ -185,10 +185,12 @@
185 185  
186 186  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
187 187  
346 +
188 188  ==== 3.3.3.2 Uplink Examples ====
189 189  
190 -[[image:image-20230816201942-1.png]]
191 191  
350 +[[image:image-20240819174540-8.png]]
351 +
192 192  For SE01-NB
193 193  
194 194  For DDS20-NB
... ... @@ -211,35 +211,37 @@
211 211  
212 212  For SN50V3-NB
213 213  
374 +
214 214  ==== 3.3.3.3 Map fields to sensor value ====
215 215  
377 +
216 216  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.
217 217  
218 -[[image:image-20230802112413-12.png||height="504" width="1011"]]
380 +[[image:image-20240819174610-9.png]]
219 219  
220 -[[image:image-20230802112413-13.png||height="331" width="978"]]
382 +[[image:image-20240819174618-10.png]]
221 221  
222 222  Below is the NB-IoT Product Table show the mapping.
223 223  
224 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
225 -|(% 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
226 -|(% 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" %)
227 -|(% 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" %)
228 -|(% 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" %)
229 -|(% 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" %)
230 -|(% 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" %)
231 -|(% 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" %)
232 -|(% 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" %)
233 -|(% 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" %)
234 -|(% 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" %)
235 -|(% 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" %)
236 -|(% 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
237 -|(% 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" %)
238 -|(% 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" %)
239 -|(% 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" %)
240 -|(% 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" %)
241 -|(% 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" %)
242 -|(% 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" %)
386 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1353.82px" %)
387 +|(% 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
388 +|(% 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" %)
389 +|(% 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" %)
390 +|(% 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" %)
391 +|(% 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" %)
392 +|(% 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" %)
393 +|(% 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" %)
394 +|(% 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" %)
395 +|(% 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" %)
396 +|(% 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" %)
397 +|(% 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" %)
398 +|(% 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
399 +|(% 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" %)
400 +|(% 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" %)
401 +|(% 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" %)
402 +|(% 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" %)
403 +|(% 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" %)
404 +|(% 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" %)
243 243  
244 244  == 3.4 [[Datacake>>https://datacake.co/]] ==
245 245  
... ... @@ -247,92 +247,108 @@
247 247  Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
248 248  
249 249  (% class="wikigeneratedid" %)
250 -As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
412 +As example for S31B-CB. there are two versions: **S31B-CB-1D and S31B-CB-GE.**
251 251  
252 -* (% 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.
414 +* (% 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.
253 253  
254 -* (% 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.
416 +* (% 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.
255 255  
418 +
256 256  === 3.4.1 For device Already has template ===
257 257  
258 258  ==== 3.4.1.1 Create Device ====
259 259  
423 +
260 260  (% style="color:blue" %)**Add Device**(%%) in DataCake.
261 261  
262 -[[image:image-20230808162301-1.png||height="453" width="952"]]
426 +[[image:image-20240820110003-1.png]]
263 263  
264 -[[image:image-20230808162342-2.png||height="541" width="952"]]
428 +[[image:image-20240820110017-2.png]]
265 265  
266 266  (% style="color:blue" %)**Choose the correct model**(%%) from template.
267 267  
268 -[[image:image-20230808162421-3.png]]
432 +[[image:image-20240820110031-3.png]]
269 269  
270 270  (% 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 -[[image:image-20230808163612-7.png||height="549" width="952"]]
436 +[[image:image-20240820110048-4.png]]
273 273  
274 -[[image:image-20230808163035-5.png]]
438 +[[image:image-20240820110103-5.png]]
275 275  
276 -[[image:image-20230808163049-6.png||height="544" width="926"]]
440 +[[image:image-20240820110114-6.png]]
277 277  
442 +
278 278  === 3.4.2 For Device already registered in DataCake before shipped ===
279 279  
280 280  ==== 3.4.2.1 Scan QR Code to get the device info ====
281 281  
447 +
282 282  Users can use their phones or computers to scan QR codes to obtain device data information.
283 283  
284 -[[image:image-20230808170051-8.png||height="255" width="259"]]
450 +[[image:image-20240820110129-7.png]]
285 285  
286 -[[image:image-20230808170548-9.png]]
452 +[[image:image-20240820110218-9.png]]
287 287  
454 +
288 288  ==== 3.4.2.2 Claim Device to User Account ====
289 289  
290 290  By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
291 291  
459 +
292 292  === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
293 293  
462 +
294 294  **Step1: Add a device**
295 295  
296 -[[image:image-20240129170024-1.png||height="330" width="900"]]
465 +[[image:image-20240820110235-10.png]][[image:image-20240129170024-1.png||height="330" width="900"]]
297 297  
467 +
298 298  **Step2: Choose your device type,please select dragino NB-IOT device**
299 299  
300 -[[image:image-20240129170216-2.png||height="534" width="643"]]
470 +[[image:image-20240820110247-11.png]]
301 301  
472 +
302 302  **Step3: Choose to create a new device**
303 303  
304 -[[image:image-20240129170539-3.png||height="459" width="646"]]
475 +[[image:image-20240820111016-12.png]]
305 305  
477 +
306 306  **Step4: Fill in the device ID of your NB device**
307 307  
308 -[[image:image-20240202111546-1.png||height="378" width="651"]]
480 +[[image:image-20240820111101-13.png]]
309 309  
482 +
310 310  **Step5: Please select your device plan according to your needs and complete the creation of the device**
311 311  
312 -[[image:image-20240129171236-6.png||height="450" width="648"]]
485 +[[image:image-20240820111113-14.png]]
313 313  
487 +
314 314  **Step6: Please add the decoder at the payload decoder of the device configuration.**
315 315  
316 316  **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]]
317 317  
318 -[[image:image-20240129172056-7.png||height="457" width="816"]]
492 +[[image:image-20240820111236-15.png]]
319 319  
320 -[[image:image-20240129173116-9.png||height="499" width="814"]]
494 +[[image:image-20240820111248-16.png]]
321 321  
496 +
322 322  **Step7: Add the output of the decoder as a field**
323 323  
324 -[[image:image-20240129173541-10.png||height="592" width="968"]]
499 +[[image:image-20240820111259-17.png]]
325 325  
501 +
326 326  **Step8: Customize the dashboard and use fields as parameters of the dashboard**
327 327  
328 -[[image:image-20240129174518-11.png||height="147" width="1042"]]
504 +[[image:image-20240820111312-18.png]]
329 329  
330 -[[image:image-20240129174657-12.png||height="538" width="916"]]
506 +[[image:image-20240820111322-19.png]]
331 331  
332 -[[image:image-20240129174840-13.png||height="536" width="750"]]
508 +[[image:image-20240820111333-20.png]]
333 333  
510 +
334 334  === 3.4.4 For device have not configured to connect to DataCake ===
335 335  
513 +
336 336  (% class="lead" %)
337 337  Use AT command for connecting to DataCake
338 338  
... ... @@ -340,10 +340,12 @@
340 340  
341 341  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
342 342  
521 +
343 343  == 3.5 Node-Red (via MQTT) ==
344 344  
345 345  === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
346 346  
526 +
347 347  Take S31-NB UDP protocol as an example.
348 348  
349 349  Dragino provides input flow examples for the sensors.
... ... @@ -356,34 +356,38 @@
356 356  
357 357  The templates for S31-NB and NB95S31B are the same.
358 358  
359 -[[image:image-20230809173127-4.png]]
539 +[[image:image-20240820111353-21.png]]
360 360  
361 361  Please select the NB95S31B template.
362 362  
363 -[[image:image-20230809173310-5.png||height="558" width="926"]]
543 +[[image:image-20240820111405-22.png]]
364 364  
365 -[[image:image-20230809173438-6.png]]
545 +[[image:image-20240820111418-23.png]]
366 366  
367 -[[image:image-20230809173800-7.png]]
547 +[[image:image-20240820111427-24.png]]
368 368  
369 369  Successfully imported template.
370 370  
371 -[[image:image-20230809173835-8.png||height="515" width="860"]]
551 +[[image:image-20240820111438-25.png]]
372 372  
373 373  Users can set UDP port.
374 374  
375 -[[image:image-20230809174053-9.png]]
555 +[[image:image-20240820111448-26.png]]
376 376  
557 +
377 377  === 3.5.2 Simulate Connection ===
378 378  
560 +
379 379  We have completed the configuration of UDP. We can try sending packets to node red.
380 380  
381 -[[image:image-20230810083934-1.png]]
563 +[[image:image-20240820111504-27.png]]
382 382  
383 -[[image:image-20230810084048-2.png||height="535" width="1052"]]
565 +[[image:image-20240820111515-28.png]]
384 384  
567 +
385 385  === 3.5.3 Configure NB-IoT Sensors ===
386 386  
570 +
387 387  * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
388 388  * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
389 389  * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
... ... @@ -391,6 +391,7 @@
391 391  * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
392 392  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
393 393  
578 +
394 394  == 3.6 ThingsBoard.Cloud (via MQTT) ==
395 395  
396 396  === 3.6.1 Configure ThingsBoard ===
... ... @@ -397,12 +397,15 @@
397 397  
398 398  ==== 3.6.1.1 Create Device ====
399 399  
585 +
400 400  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
401 401  
402 -[[image:image-20230802112413-32.png||height="583" width="1066"]]
588 +[[image:image-20240820112210-29.png]]
403 403  
590 +
404 404  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
405 405  
593 +
406 406  (% style="color:blue" %)**Uplink Converter**
407 407  
408 408  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.
... ... @@ -409,27 +409,29 @@
409 409  
410 410  To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** (%%)button. Name it (% style="color:blue" %)**“MQTT Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
411 411  
412 -[[image:image-20230802112413-33.png||height="597" width="1061"]]
600 +[[image:image-20240820112222-30.png]]
413 413  
414 414  (% style="color:blue" %)**Downlink Converter**
415 415  
416 416  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
417 417  
418 -[[image:image-20230802112413-34.png||height="598" width="1063"]]
606 +[[image:image-20240820112236-31.png]]
419 419  
420 420  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
421 421  
610 +
422 422  ==== 3.6.1.3 MQTT Integration Setup ====
423 423  
613 +
424 424  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**;
425 425  
426 -[[image:image-20230802112413-35.png||height="597" width="1062"]]
616 +[[image:image-20240820112247-32.png]]
427 427  
428 428  * The next steps is to add the recently created uplink and downlink converters;
429 429  
430 -[[image:image-20230802112413-36.png||height="598" width="1062"]]
620 +[[image:image-20240820112302-33.png]]
431 431  
432 -[[image:image-20230802112413-37.png||height="598" width="1064"]]
622 +[[image:image-20240820112316-34.png]]
433 433  
434 434  (% style="color:blue" %)**Add a topic filter:**
435 435  
... ... @@ -437,16 +437,19 @@
437 437  
438 438  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
439 439  
440 -[[image:image-20230802112413-38.png||height="598" width="1064"]]
630 +[[image:image-20240820112330-35.png]]
441 441  
632 +
442 442  === 3.6.2 Simulate with MQTT.fx ===
443 443  
444 -[[image:image-20230802112413-39.png]]
635 +[[image:image-20240820112340-36.png]]
445 445  
446 -[[image:image-20230802112413-40.png||height="525" width="980"]]
637 +[[image:image-20240820112351-37.png]]
447 447  
639 +
448 448  === 3.6.3 Configure NB-IoT Sensor ===
449 449  
642 +
450 450  (% style="color:blue" %)**AT Commands**
451 451  
452 452  * (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
... ... @@ -463,25 +463,27 @@
463 463  
464 464  Test Uplink by click the button for 1 second
465 465  
466 -[[image:image-20230802112413-41.png||height="496" width="828"]]
659 +[[image:image-20240820112404-38.png]]
467 467  
468 -[[image:image-20230802112413-42.png]]
661 +[[image:image-20240820112416-39.png]]
469 469  
470 -[[image:image-20230802112413-43.png||height="407" width="825"]]
663 +[[image:image-20240820112426-40.png]]
471 471  
665 +
472 472  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
473 473  
474 474  === 3.7.1 Create device & Get Credentials ===
475 475  
670 +
476 476  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.
477 477  
478 -[[image:image-20230802112413-44.png]]
673 +[[image:image-20240820112516-41.png]]
479 479  
480 -[[image:image-20230802112413-45.png]]
675 +[[image:image-20240820112526-42.png]]
481 481  
482 482  Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
483 483  
484 -[[image:image-20230802112413-46.png]]
679 +[[image:image-20240820112539-43.png]]
485 485  
486 486  The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
487 487  
... ... @@ -519,26 +519,32 @@
519 519  
520 520  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
521 521  
717 +
522 522  === 3.7.2 Simulate with MQTT.fx ===
523 523  
524 -[[image:image-20230802112413-52.png]]
525 525  
526 -[[image:image-20230808105300-2.png||height="553" width="1026"]]
721 +[[image:image-20240820112552-44.png]]
527 527  
723 +[[image:image-20240820112604-45.png]]
724 +
528 528  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
529 529  
530 -[[image:image-20230808105217-1.png||height="556" width="1031"]]
727 +[[image:image-20240820112615-46.png]]
531 531  
532 -[[image:image-20230808105329-3.png]]
729 +[[image:image-20240820112626-47.png]]
533 533  
731 +
534 534  === 3.7.3 tago data ===
535 535  
536 -[[image:image-20230802112413-50.png||height="242" width="1037"]]
537 537  
538 -[[image:image-20230802112413-51.png||height="184" width="696"]]
735 +[[image:image-20240820112637-48.png]]
539 539  
737 +[[image:image-20240820112647-49.png]]
738 +
739 +
540 540  == 3.8 TCP Connection ==
541 541  
742 +
542 542  (% style="color:blue" %)**AT command:**
543 543  
544 544  * (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
... ... @@ -549,20 +549,24 @@
549 549  
550 550  (% style="color:blue" %)**Sensor Console Output when Uplink:**
551 551  
552 -[[image:image-20230807233631-1.png]]
753 +[[image:image-20240820112704-50.png]]
553 553  
554 554  (% style="color:blue" %)**See result in TCP Server:**
555 555  
556 -[[image:image-20230807233631-2.png]]
757 +[[image:image-20240820112716-51.png]]
557 557  
759 +
558 558  == 3.9 AWS Connection ==
559 559  
762 +
560 560  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]]
561 561  
562 -= 4. MQTT/UDP/TCP downlink =
563 563  
766 += 4. COAP/UDP/MQTT/TCP downlink =
767 +
564 564  == 4.1 MQTT (via MQTT.fx) ==
565 565  
770 +
566 566  Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
567 567  
568 568  **1.** Configure node MQTT connection (via MQTT.fx):
... ... @@ -583,12 +583,14 @@
583 583  
584 584  (% 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.**
585 585  
586 -[[image:image-20240417180145-2.png||height="434" width="587"]][[ width="584">> width="584"]]
791 +[[image:image-20240820112732-52.png]][[image:image-20240820112758-53.png]]
587 587  
793 +
588 588  **2. **When the node uplink packets, we can observe the data in MQTT.fx.
589 589  
590 -[[image:image-20240418144337-1.png||height="709" width="802"]]
796 +[[image:image-20240820112813-54.png]]
591 591  
798 +
592 592  **3. **The downlink command can be successfully sent only when the downlink port is open.
593 593  
594 594   The downlink port is opened for about 3 seconds after uplink packets are sent.
... ... @@ -595,16 +595,69 @@
595 595  
596 596   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.
597 597  
598 -[[image:image-20240418150435-3.png||height="582" width="659"]]
805 +[[image:image-20240820112824-55.png]]
599 599  
600 -[[image:image-20240418150932-4.png||height="492" width="1061"]]
807 +[[image:image-20240820112835-56.png]]
601 601  
602 602  (% 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.**
603 603  
604 -= 5. FAQ =
605 605  
606 -== 5.1 What is the usage of Multi Sampling and One Uplink? ==
812 +== 4.2 UDP (via Thingseye) ==
607 607  
814 +
815 +(% 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/]])
816 +
817 +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)
818 +
819 +[[image:image-20240820141843-2.png||height="546" width="821"]]
820 +
821 +After clicking Show Node Details Page, (% style="color:blue" %)**Select Properties ~-~-- select Shared Properties ~-~-- click Add Properties**
822 +
823 +[[image:image-20240820143316-3.png||height="555" width="1170"]]
824 +
825 +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
826 +
827 +(% style="color:red" %)**(Note: Downlinks can only be downlinked in string format, otherwise the node will not recognize the downlink command.)**
828 +
829 +[[image:image-20240820143820-4.png||height="554" width="1168"]]
830 +
831 +After the command is successfully added, the platform will send the command down on the node's next uplink.
832 +
833 +[[image:image-20240820144913-6.png||height="585" width="1232"]]
834 +
835 +[[image:image-20240820145133-7.png||height="582" width="1227"]]
836 +
837 +Upon successful issuance, the platform automatically eliminates the attributes from the queue and waits for the next addition of new attributes
838 +
839 +[[image:image-20240820145309-8.png]]
840 +
841 +
842 += 5. GPS positioning function =
843 +
844 +== 1. Turn on GPS function ==
845 +
846 +
847 +(% class="wikigeneratedid" %)
848 +AT+GPS=1 or 0  ~/~/ GPS function on or off
849 +
850 +
851 +== 2. Extend the time to turn on GNSS ==
852 +
853 +
854 +AT+GNSST=30  ~/~/ GPS search for positioning information for 30 seconds
855 +
856 +
857 +== 3. Get or set GPS positioning interval in units of hour ==
858 +
859 +
860 +AT+GTDC=24  ~/~/ The device will activate GPS positioning every 24 hours
861 +
862 +
863 += 6. FAQ =
864 +
865 +== 6.1 What is the usage of Multi Sampling and One Uplink? ==
866 +
867 +
608 608  The NB series has the feature for Multi Sampling and one uplink. See one of them
609 609  
610 610  [[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]]
... ... @@ -619,27 +619,31 @@
619 619  1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours.
620 620  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.
621 621  
622 -== 5.2 Why the uplink JSON format is not standard? ==
623 623  
883 +== 6.2 Why the uplink JSON format is not standard? ==
884 +
885 +
624 624  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.
625 625  
626 626  The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
627 627  
628 -[[image:image-20240229233154-1.png]]
890 +[[image:image-20240820112848-57.png]]
629 629  
630 -= 6. Trouble Shooting: =
631 631  
632 -== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
893 += 7. Trouble Shooting: =
633 633  
895 +== 7.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
896 +
897 +
634 634  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.
635 635  
636 636  If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
637 637  
638 -[[image:image-20240207002003-1.png]]
902 +[[image:image-20240820112859-58.png]]
639 639  
640 640  If fail to attach network, it will shows signal 99. as below:
641 641  
642 -[[image:image-20240207002129-2.png]]
906 +[[image:image-20240820112908-59.png]]
643 643  
644 644  (% class="lead" %)
645 645  When see this issue, below are the checklist:
... ... @@ -652,16 +652,17 @@
652 652  
653 653  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.
654 654  
655 -
656 656  
657 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
920 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.2 Why sometime the AT Command is slow in reponse?(%%) ==
658 658  
922 +
659 659  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.
660 660  
661 -[[image:image-20240226111928-1.png]]
925 +[[image:image-20240820113015-60.png]]
662 662  
663 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
664 664  
928 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.3 What is the Downlink Command by the -CB device?(%%) ==
929 +
665 665  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
666 666  === UDP: ===
667 667  
... ... @@ -671,6 +671,7 @@
671 671  
672 672  {AT+TDC=300}
673 673  
939 +
674 674  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
675 675  === MQTT: ===
676 676  
... ... @@ -712,5 +712,136 @@
712 712  
713 713  [[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/]]
714 714  
981 +
982 +== 7.4 What if the signal is good but the domain name resolution fails? ==
983 +
984 +
985 +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.
986 +
987 +[[image:image-20240827150705-6.png||height="489" width="687"]]
988 +
989 +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.
990 +
991 +* Set the DNS
992 +
993 +(% style="color:blue" %)**AT Command: AT+GDNS**
994 +
995 +**AT+GDNS=0**  ~/~/ Default. Automatically resolves the domain name and uses the resolved IP to communicate.
996 +
997 +**AT+GDNS=1    **~/~/ Disabling Domain name resolution. Use the domain name directly to communicate.
998 +
999 +(% style="color:red" %)**Note: For -CB products, with the exception of AT+PRO=2,5, all protocols and payload formats support direct domain communication.**
1000 +
1001 +Example:
1002 +
1003 +[[image:image-20240827150121-5.png||height="476" width="680"]][[image:image-20240827145055-4.png||height="484" width="678"]]
1004 +
1005 +
1006 +== 7.5 GPS debugging ==
1007 +
1008 +
1009 +Indoor GPS signal is very weak, **outdoor** positioning is generally recommended.
1010 +
1011 +[[image:image-20240903104250-9.png||height="275" width="614"]]
1012 +
1013 +
1014 +[[image:image-20240903104431-10.png||height="291" width="621"]]
1015 +
1016 +
1017 +=== 7.5.1 GPS commands ===
1018 +
1019 +
1020 +The following are three related AT commands that introduce GPS functions.
1021 +
1022 +* **Turn on/off GPS**
1023 +
1024 +(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GPS **
1025 +
1026 +**Ex1:  **AT+GPS=0  ~/~/ Turn off GPS
1027 +
1028 +**Ex2:  **AT+GPS=1  ~/~/ Turn on GPS
1029 +
1030 +(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x11(%%)**
1031 +
1032 +Format: Command Code (0x11) followed by 1 byte.
1033 +
1034 +Example:  Downlink Payload: **11 01   **~/~/ AT+GPS=1
1035 +
1036 +* **Set GNSS open time**
1037 +
1038 +Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated.
1039 +
1040 +(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GNSST**
1041 +
1042 +Example: AT+GNSST=30  ~/~/ Set the GPS positioning time to 30 seconds
1043 +
1044 +(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x10(%%)**
1045 +
1046 +Format: Command Code (0x10) followed by 2 bytes.
1047 +
1048 +Example:  Downlink Payload: **10 00 1E    **~/~/ AT+GNSST=30
1049 +
1050 +* **Set GPS positioning interval**
1051 +
1052 +Feature: Set GPS positioning interval (unit: hour).
1053 +
1054 +When GPS is enabled, the node automatically locates and uplinks each time it passes **GTDC time** after activation.
1055 +
1056 +(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GTDC**
1057 +
1058 +Example: AT+GTDC=24  ~/~/ Set the GPS positioning interval to 24h.
1059 +
1060 +(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x12(%%)**
1061 +
1062 +Format: Command Code (0x12) followed by 3 bytes.
1063 +
1064 +Example: 24 hours:  24(D)=0x18(H)
1065 +
1066 +Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
1067 +
1068 +
1069 +=== 7.5.2 GPS workflow ===
1070 +
1071 +
1072 +The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
1073 +
1074 +~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.
1075 +
1076 + 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.
1077 +
1078 + So if there is a failure of positioning, the user can extend the (% style="color:#037691" %)**GNSST**(%%) time appropriately.
1079 +
1080 +2. Each TDC time node is not repositioned and the positioning interval is determined by the AT+GTDC time.
1081 +
1082 + The latitude and longitude payload uplinked at each TDC time is the GPS positioning information from the previous (% style="color:#037691" %)**GTDC**(%%) time.
1083 +
1084 + 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.
1085 +
1086 +
1087 +=== 7.5.3 GPS debugging methods ===
1088 +
1089 +
1090 +In summary, we can deduce the methods of debugging GPS:
1091 +
1092 +* **Check whether the GPS function is enabled.**
1093 +
1094 +[[image:image-20240903102327-5.png||height="271" width="529"]]
1095 +
1096 +* **Check whether the GPS antenna is loose**.
1097 +
1098 +If the GPS antenna is loose, the GPS signal is weak, and the positioning fails.
1099 +
1100 +[[image:image-20240903094214-1.png||height="340" width="461"]]
1101 +
1102 +* **Use the AT+GNSST command to extend the positioning time.**
1103 +
1104 +The default AT+GNSST=30, that is, the default positioning time is 30 seconds.
1105 +
1106 +If the location fails, users can extend the location time.
1107 +
1108 +[[image:image-20240903102641-8.png||height="303" width="600"]]
1109 +
1110 +
1111 +
1112 +
715 715  
716 -​
image-20240602220856-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +250.9 KB
Content
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