<
From version < 115.28 >
edited by Xiaoling
on 2022/07/11 08:37
To version < 116.1 >
edited by Xiaoling
on 2022/07/11 09:32
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -127,9 +127,13 @@
127 127  
128 128  === 1.5.2 BOOT MODE / SW1 ===
129 129  
130 +(((
130 130  1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
132 +)))
131 131  
134 +(((
132 132  2) Flash: work mode, device starts to work and send out console output for further debug
136 +)))
133 133  
134 134  
135 135  
... ... @@ -146,6 +146,9 @@
146 146  1. When boot the device in flash mode
147 147  1. Send an uplink packet
148 148  
153 +
154 +
155 +
149 149  = 2.  Use N95S31B to communicate with IoT Server =
150 150  
151 151  == 2.1  How it works ==
... ... @@ -183,23 +183,45 @@
183 183  === 2.2.1 Test Requirement ===
184 184  
185 185  
193 +(((
186 186  To use N95S31B in your city, make sure meet below requirements:
195 +)))
187 187  
188 -* Your local operator has already distributed a NB-IoT Network there.
189 -* The local NB-IoT network used the band that N95S31B supports.
190 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
197 +* (((
198 +Your local operator has already distributed a NB-IoT Network there.
199 +)))
200 +* (((
201 +The local NB-IoT network used the band that N95S31B supports.
202 +)))
203 +* (((
204 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
205 +)))
191 191  
207 +(((
192 192  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
209 +)))
193 193  
211 +(((
194 194  N95S31B supports different communication protocol such as :
213 +)))
195 195  
196 196  (((
197 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
198 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
199 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
200 -* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
216 +* (((
217 +CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
218 +)))
219 +* (((
220 +raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
221 +)))
222 +* (((
223 +MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
224 +)))
225 +* (((
226 +TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
227 +)))
201 201  
229 +(((
202 202  We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server.
231 +)))
203 203  
204 204  
205 205  )))
... ... @@ -369,28 +369,48 @@
369 369  == 2.3  Uplink Payload ==
370 370  
371 371  
401 +(((
372 372  NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
403 +)))
373 373  
374 374  
406 +(((
375 375  For example:
408 +)))
376 376  
410 +(((
377 377   (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
412 +)))
378 378  
379 379  
415 +(((
380 380  The uplink payloads are composed in  ASCII String. For example:
417 +)))
381 381  
419 +(((
382 382  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
421 +)))
383 383  
423 +(((
384 384  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
425 +)))
385 385  
386 386  
428 +(((
387 387  (% style="color:red" %)**NOTE:**
430 +)))
388 388  
389 389  (% style="color:red" %)
390 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
391 -1. By default, the device will send an uplink message every 1 hour.
433 +1. (((
434 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
435 +)))
436 +1. (((
437 +By default, the device will send an uplink message every 1 hour.
438 +)))
392 392  
393 393  
441 +
442 +
394 394  === 2.3.1  Payload Analyze ===
395 395  
396 396  N95S31B uplink payload includes in total 21 bytes
... ... @@ -780,8 +780,10 @@
780 780  (((
781 781  
782 782  
832 +(((
783 783  (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
784 784  )))
835 +)))
785 785  
786 786  
787 787  
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0