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