<
From version < 88.13 >
edited by Xiaoling
on 2022/07/23 15:14
To version < 81.1 >
edited by Kilight Cao
on 2022/06/15 15:22
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Kilight
Content
... ... @@ -1,4 +1,4 @@
1 -**~ Table of Contents:**
1 +**~ Contents:**
2 2  
3 3  {{toc/}}
4 4  
... ... @@ -5,11 +5,10 @@
5 5  
6 6  
7 7  
8 -= **1.  Use Dragino Gateways/Hotspots with Helium** =
8 += **1. Use Dragino Gateways/Hotspots with Helium** =
9 9  
10 -== **1.1  Support Models** ==
10 +== **1.1 Support Models** ==
11 11  
12 -
13 13  //There are three types of hotspots that can connect to Helium. They are (% style="color:#4f81bd" %)**full-hotspot**(%%), (% style="color:#4f81bd" %)**light hotspot** (%%)and (% style="color:#4f81bd" %)**data-only hotspot**(%%). Definition of these three types of hotspots can be found here: [[of Helium Hotspots>>url:https://docs.helium.com/mine-hnt%7CTypes]]. Different hotspots support different mining abilities.//
14 14  
15 15  (((
... ... @@ -23,115 +23,102 @@
23 23  [[LPS8>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]], [[DLOS8>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]],
24 24  
25 25  [[LG308>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]],[[LIG16>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]]
26 -)))|(% style="color:#4f81bd; width:126px" %)**Data-Only Hotspot**|(% style="width:121px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]]|(% style="width:203px" %)[[Data-Only Hotspot Instruction>>||anchor="H2.A0ConnectData-OnlyHotspottoHelium"]]
25 +)))|(% style="color:#4f81bd; width:126px" %)**Data-Only Hotspot**|(% style="width:121px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]]|(% style="width:203px" %)[[Data-Only Hotspot Instruction>>||anchor="H2.ConnectData-OnlyHotspottoHelium"]]
27 27  |(% style="width:132px" %)[[HP0D>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/195-hp0d.html]]|(% style="color:#4f81bd; width:126px" %)**Full Hotspo**t|(% style="width:121px" %)[[Helium Link>>url:https://docs.helium.com/mine-hnt/full-hotspots]]|(% style="color:green; width:203px" %)[[Full Hotspot Instuction-Not Finish>>doc:Main.User Manual for All Gateway models.HP0D.WebHome]]
28 28  
29 -(% style="color:blue" %)**Frequencies on the Helium Network**
28 +**Frequencies on the Helium Network**
30 30  
31 -* //The frequencies currently available are CN470/EU868/US915/AU915//
30 +* The frequencies currently available are CN470/EU868/US915/AU915
32 32  
33 -
34 -
35 35  (% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]**
36 36  
37 37  
35 += 2. Connect Data-Only Hotspot to Helium =
38 38  
39 -= **2.  Connect Data-Only Hotspot to Helium** =
37 +== 2.1 Prerequisites ==
40 40  
41 -== **2.1  Prerequisites** ==
39 +* Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
42 42  
41 +== 2.2 Step 1: Configure Frequency Band ==
43 43  
44 -* //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//
43 +Each country has a requirement for frequency region. Choose the right one for your area.
45 45  
46 -
47 -
48 -
49 -== **2.2  Step 1: Configure Frequency Band** ==
50 -
51 -
52 -//Each country has a requirement for frequency region. Choose the right one for your area.//
53 -
54 54  [[image:image-20220531175337-1.png]]
55 55  
47 +Select fre
56 56  
57 57  
58 -== **2.3  Step 2: Download the Helium-gateway-rs** ==
50 +== 2.3 Step 2: Download the Helium-gateway-rs ==
59 59  
52 +Click Download Helium Server and the gateway will download the Helium-gateway-rs
60 60  
61 -//Click Download Helium Server and the gateway will download the Helium-gateway-rs//
54 +[[image:image-20220615150600-1.png||height="667" width="1247"]]
62 62  
63 -[[image:image-20220615150600-1.png||height="559" width="1045"]]
56 +Start download the Helium-gatewayrs
64 64  
65 65  
66 -//**Start download to Helium-gateway-rs**//
59 +[[image:image-20220615150627-2.png||height="712" width="1244"]]
67 67  
68 -[[image:image-20220615150627-2.png||height="598" width="1044"]]
61 +Helium-gatewayrs download success
69 69  
70 -//**Helium-gatewayrs download success**//
71 71  
64 +If download fails, click and download again
72 72  
73 -//**If download fails, click and download again**//
66 +[[image:image-20220615150717-3.png||height="722" width="1239"]]
74 74  
75 -[[image:image-20220615150717-3.png||height="605" width="1039"]]
68 +Helium-gatewayrs download fail
76 76  
77 77  
78 -== **2.4  Step 3: Install the Helium-gateway-rs** ==
71 +== 2.4 Step 3: Install the Helium-gateway-rs ==
79 79  
73 +Click **Install Helium Server** to install gateway-rs.
80 80  
81 -//Click **Install Helium Server** to install gateway-rs.//
75 +[[image:image-20220615150734-4.png||height="742" width="1241"]]
82 82  
83 -[[image:image-20220615150734-4.png||height="619" width="1035"]]
84 -
85 85  Install the Helium gateway-rs
86 86  
79 +**Note**: User will see the echo characters of Helium gateway-rs have been installed successfully.
87 87  
88 -(% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
89 89  
82 +== 2.5 Step 4: Save&start the Helium Server ==
90 90  
91 91  
92 -== **2.5  Step 4: Save&start the Helium Server** ==
85 +By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.
93 93  
87 +[[image:image-20220615150903-5.png||height="710" width="1236"]]
94 94  
95 -//By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
89 +Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status.
96 96  
97 -[[image:image-20220615150903-5.png||height="592" width="1031"]]
91 +[[image:image-20220615151057-6.png||height="697" width="1233"]]
98 98  
93 +Start Helium-gateway-rs
99 99  
100 -//Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.//
101 101  
102 -[[image:image-20220615151057-6.png||height="580" width="1026"]]
96 +== 2.6 Step 5: Check Gateway Connection before onboarding ==
103 103  
98 +A hotspot can transfer data to Helium after finishing step4. We can add a device to Helium and see if the device can join Helium. For example, we add an LGT92 sensor and see below info.
104 104  
105 -
106 -== **2.6  Step 5: Check Gateway Connection before onboarding** ==
107 -
108 -
109 -//A hotspot can transfer data to Helium after finishing step4. We can add a device to Helium and see if the device can join Helium. For example, we add an LGT92 sensor and see below info.//
110 -
111 111  (((
112 -//Check end device event from [[Helium Console>>url:https://staging-console.helium.wtf/]], We can see the LGT92 data arrived Helium via our hotspot.//
101 +Check end device event from [[Helium Console>>url:https://staging-console.helium.wtf/]], We can see the LGT92 data arrived Helium via our hotspot.
113 113  )))
114 114  
115 115  [[image:image-20220526094537-1.png||height="395" width="1323"]]
116 116  
106 +Check if the packet is transferred via LPS8
117 117  
118 -(% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**
108 +**Note:** The hotspot is not valid for search in Helium Console before onboarding.
119 119  
120 120  
111 +== 2.7 Step 6: Onboarding Data-Only Hotspot ==
121 121  
122 -== **2.7  Step 6: Onboarding Data-Only Hotspot** ==
113 +(% style="color:red" %)**Note: Onboarding a Data-Only hotspot is not necessary, and it will gain very, very small awards on HNT by data-transfer .**
123 123  
115 +User can refer [[this link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]] for how to onboarding a data-only hotspot. After onboarding the data-only hotspot, user can see the hotspot on Helium Console.
124 124  
125 -(% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .**
117 +Below are the steps we do as per above link here.
126 126  
127 -
128 -//User can refer [[this link>>url:https://docs.helium.com/mine-hnt/data-only-hotspots]] for how to onboarding a data-only hotspot. After onboarding the data-only hotspot, user can see the hotspot on Helium Console.//
129 -
130 -//Below are the steps we do as per above link here.//
131 -
132 -
133 133  (((
134 -(% style="color:blue" %)//**1. Set up Helium-Wallet in my computer. [[https:~~/~~/docs.helium.com/wallets/cli-wallet>>url:https://docs.helium.com/wallets/cli-wallet]]. and funds this wallet. From this step, we got the wallet info as below.**//
120 +~1. Set up Helium-Wallet in my computer. [[https:~~/~~/docs.helium.com/wallets/cli-wallet>>url:https://docs.helium.com/wallets/cli-wallet]]. and funds this wallet. From this step, we got the wallet info as below.
135 135  )))
136 136  
137 137  (% class="box" %)
... ... @@ -159,13 +159,12 @@
159 159  )))
160 160  
161 161  (((
162 -(% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.**
148 +**Note**: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.
163 163  )))
164 164  
165 165  
166 -
167 167  (((
168 -(% style="color:blue" %)//**2. Get txn. In the data-only hotspot. run below command to add a hotspot, owner is the owner wallet of this hotspot, payer is the payer to pay transaction cost.**//
153 +2. Get txn. In the data-only hotspot. run below command to add a hotspot, owner is the owner wallet of this hotspot, payer is the payer to pay transaction cost.
169 169  )))
170 170  
171 171  (% class="box" %)
... ... @@ -197,17 +197,8 @@
197 197  )))
198 198  
199 199  (((
200 -//We got the txn info from this step.//
201 -
202 -
203 -
204 -(% style="color:blue" %)//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**//
205 -
206 -
207 -(% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.**
208 -
209 -
210 -//Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.//
185 +We got the txn info from this step.
186 +\\3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step. Note, below are two commands, the command without ~-~-commit is the preview mode. Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.
211 211  )))
212 212  
213 213  (% class="box" %)
... ... @@ -250,9 +250,7 @@
250 250  )))
251 251  
252 252  (((
253 -
254 -
255 -(% style="color:blue" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//
229 +4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.
256 256  )))
257 257  
258 258  (% class="box" %)
... ... @@ -307,25 +307,23 @@
307 307  )))
308 308  
309 309  (((
310 -(% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.**
284 +Note: The add hotspot and assert location step might need some time to be effect.
311 311  )))
312 312  
313 313  (((
314 -//After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//
288 +After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.
315 315  
316 -
317 317  
318 318  )))
319 319  
320 -== **2.8  Debug Connection** ==
293 +== 2.8 Debug Connection ==
321 321  
322 -=== **2.8.1  Check pkt-fwd running Log** ===
295 +=== 2.8.1 Check pkt-fwd running Log ===
323 323  
297 +This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.
324 324  
325 -//This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
326 -
327 327  (((
328 -//Below logs shows the gateway receive two LoRaWAN packets.//
300 +Below logs shows the gateway receive two LoRaWAN packets.
329 329  )))
330 330  
331 331  (% class="box" %)
... ... @@ -350,21 +350,19 @@
350 350  )))
351 351  
352 352  
325 +=== 2.8.2 Check gateway-rs Log ===
353 353  
354 -=== **2.8.2  Check gateway-rs Log** ===
327 +SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.
355 355  
356 -
357 -//SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
358 -
359 359  [[image:image-20220531175809-7.png]]
360 360  
331 +Helium-gatewayrs log
361 361  
362 -(% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
333 +**Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.
363 363  
364 364  
365 -=== **2.8.3  View the public key address and animal name** ===
336 +=== 2.8.3 View the public key address and animal name ===
366 366  
367 -
368 368  (% class="box" %)
369 369  (((
370 370  (((
... ... @@ -386,95 +386,80 @@
386 386  Hostpot key and animal name
387 387  
388 388  
359 +=== 2.8.4 Backup/Restor gateway-rs key ===
389 389  
390 -=== **2.8.4  Backup/Restor gateway-rs key** ===
391 -
392 -
393 393  (((
394 -//For the date-only hotspots, the key is the only unique identifier, the users can backup the key by the button of Download. And once the uses upgrade the gateway or the gateway lose the key, the gateway-rs will generate a new key for which the data-only hotspot is the new unit. so if the user would restore to last time which can upload your backup key to the gateway by the button of upload.//
362 +For the date-only hotspots, the key is the only unique identifier, the users can backup the key by the button of Download. And once the uses upgrade the gateway or the gateway lose the key, the gateway-rs will generate a new key for which the data-only hotspot is the new unit. so if the user would restore to last time which can upload your backup key to the gateway by the button of upload.
395 395  )))
396 396  
397 397  [[image:image-20220531175919-9.png]]
398 398  
367 +Backup and restore key
399 399  
400 400  
401 -== **2.9  Forward the data to the other server** ==
370 +== 2.9 Forward the data to the other server ==
402 402  
403 -=== **2.9.1  Introduction** ===
372 +=== 2.9.1 Introduction ===
404 404  
405 -
406 406  (((
407 -//The Dragino gateway has supports the double server settings.//
375 +The Dragino gateway has supports the double server settings.
408 408  )))
409 409  
410 410  (((
411 -//Users can back to the page of Semtech UDP to configure other server settings.//
379 +Users can back to the page of Semtech UDP to configure other server settings.
412 412  
413 413  
414 414  )))
415 415  
416 -=== **2.9.2  Example** ===
384 +=== 2.9.2 Example ===
417 417  
386 +The following takes The Things Network as another LoRaWAN server as an example.
418 418  
419 -//The following takes The Things Network as another LoRaWAN server as an example.//
420 420  
389 +==== 2.9.2.1 Step 1: Back to Semtech UDP page ====
421 421  
422 -
423 -==== (% style="color:blue" %)**Step 1: Back to Semtech UDP page**(%%) ====
424 -
425 -
426 426  [[image:image-20220531180002-10.png]]
427 427  
428 428  Back to Semtech UDP page
429 429  
430 430  
396 +==== 2.9.2.2 Step 2: Configure the double server forwarding ====
431 431  
432 -==== (% style="color:blue" %)**Step 2: Configure the double server forwarding**(%%) ====
433 -
434 -
435 435  [[image:image-20220531180048-11.png]]
436 436  
400 +Configure the double server
437 437  
438 -//The user can configure the secondary server and then click the button of **Save&Apply**.//
402 +The user can configure the secondary server and then click the button of Save&Apply.
439 439  
440 440  
441 -== **2.10  Connect Full Hotspot to Helium** ==
405 +== 2.10 Connect Full Hotspot to Helium ==
442 442  
407 += 3. Use Dragino Sensors with Helium =
443 443  
409 +== 3.1 How to add up user's end-node with Helium console ==
444 444  
445 -= **3.  Use Dragino Sensors with Helium** =
411 +=== 3.1.1 Step 1: Login the Helium console ===
446 446  
413 +User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]
447 447  
448 -== **3.1  How to add up user's end-node with Helium console** ==
449 -
450 -
451 -=== **3.1.1  Step 1: Login the Helium console** ===
452 -
453 -
454 -//User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]//
455 -
456 456  [[image:image-20220531180150-12.png]]
457 457  
458 458  login Helium console
459 459  
460 460  
420 +=== 3.1.2 Step 2: Add up your end-node's key ===
461 461  
462 -=== **3.1.2  Step 2: Add up your end-node's key** ===
422 +User add up end-node's key from console ~-~->dervice
463 463  
464 -
465 -//User add up end-node's key from console ~-~->dervice//
466 -
467 467  [[image:image-20220531180224-13.png]]
468 468  
469 469  To add a device
470 470  
471 471  
429 +=== 3.1.3 Step 3:Activate the end-node ===
472 472  
473 -=== **3.1.3  Step 3: Activate the end-node** ===
474 -
475 -
476 476  (((
477 -//Users can activate the end-node with OTAA in which the end-node will Join the network from the Helium server **Eventually you will see traffic**//
432 +Users can activate the end-node with OTAA in which the end-node will Join the network from the Helium server **Eventually you will see traffic**
478 478  )))
479 479  
480 480  [[image:image-20220531105239-2.png]]
... ... @@ -482,21 +482,17 @@
482 482  end-node traffic.
483 483  
484 484  
440 +== 3.2 How to use decoder ==
485 485  
486 -== **3.2  How to use decoder** ==
442 +=== 3.2.1 Step 1:Users can create decoders on functions ===
487 487  
488 -=== **3.2.1  Step 1: Users can create decoders on functions** ===
489 -
490 -
491 491  [[image:image-20220531105325-3.png]]
492 492  
493 493  Decoder.
494 494  
495 495  
449 +=== 3.2.2 Step 2:Add a decoder in functions and apply it to the specified label ===
496 496  
497 -=== **3.2.2  Step 2: Add a decoder in functions and apply it to the specified label** ===
498 -
499 -
500 500  [[image:image-20220526095629-6.png]]
501 501  
502 502  
... ... @@ -505,37 +505,28 @@
505 505  
506 506  [[image:image-20220526100057-8.png||height="352" width="1133"]]
507 507  
508 -**//Add decoder complete.//**
459 +Decoder.
509 509  
461 +Add decoder complete.
510 510  
511 511  
512 -=== **3.2.3  Where is the decoder?** ===
464 +== 3.3 How to send a downlink to end device from Helium ==
513 513  
514 -
515 -[[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
516 -
517 -[[image:image-20220617140118-1.png||height="550" width="883"]]
518 -
519 -
520 -
521 -== **3.3  How to send a downlink to end device from Helium** ==
522 -
523 -
524 524  (((
525 -//The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://
467 +The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example:
526 526  )))
527 527  
528 528  (((
529 -//The Downlink command comes from this link:[[End Device Downlink Command>>End Device AT Commands and Downlink Command]]//
471 +The Downlink command comes from this link:[[End Device Downlink Command>>End Device AT Commands and Downlink Command]]
530 530  )))
531 531  
532 532  (((
533 -//Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds//
475 +Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
534 534  )))
535 535  
536 536  (% class="box" %)
537 537  (((
538 -**01 00 00 3C ~-~-> AQAAPA==**
480 +01 00 00 3C ~-~-> AQAAPA==
539 539  )))
540 540  
541 541  [[image:image-20220524171341-21.png]]
... ... @@ -543,58 +543,55 @@
543 543  Downlink
544 544  
545 545  
488 +== 3.4 How to add integration to different IoT Servers ==
546 546  
547 -== **3.4  How to add integration to different IoT Servers** ==
490 +=== 3.4.1 TagoIO ===
548 548  
549 -=== **3.4.1  TagoIO** ===
492 +The steps to add integration are very simple. Please see the following process.
550 550  
551 -
552 -**//The steps to add integration are very simple. Please see the following process.//**
553 -
554 -
555 555  [[image:image-20220526102429-23.png||height="630" width="1198"]]
556 556  
496 +TagoIO.
557 557  
558 558  
559 -**//Generate the authorization code and then copy it.//**
499 +Generate the authorization code and then copy it.
560 560  
561 -
562 562  [[image:image-20220526100452-10.png||height="314" width="1188"]]
563 563  
503 +TagoIO.
564 564  
565 565  
566 -//**Apply Integration to Label.**//
506 +Apply Integration to Label.
567 567  
568 -
569 569  [[image:image-20220526100802-13.png]]
570 570  
571 571  
511 +TagoIO.
572 572  
513 +
573 573  [[image:image-20220526100927-14.png]]
574 574  
516 +TagoIO.
575 575  
576 576  
577 -**//Click LoRaWAN Helium,select the device.//**
519 +Click LoRaWAN Helium,select the device.
578 578  
579 -
580 580  [[image:image-20220526101215-15.png||height="599" width="1117"]]
581 581  
523 +TagoIO.
582 582  
583 583  
584 -**//Fill in DEVEUI and create my device.//**
526 +Fill in DEVEUI and create my device.
585 585  
586 -
587 587  [[image:image-20220526101419-16.png]]
588 588  
589 589  TagoIO.
590 590  
591 591  
533 +=== 3.4.2 Cayenne ===
592 592  
593 -=== **3.4.2  Cayenne** ===
535 +The process of creating devices is similar to Tago.
594 594  
595 -
596 -//The process of creating devices is similar to Tago.//
597 -
598 598  [[image:image-20220526101616-18.png||height="456" width="1097"]]
599 599  
600 600  Cayenne.
... ... @@ -625,92 +625,78 @@
625 625  Cayenne.
626 626  
627 627  
567 +== 3.5 Trouble Shooting ==
628 628  
629 -== **3.5  Trouble Shooting** ==
569 +=== 3.5.1 Trouble to Join Helium ===
630 630  
631 -=== **3.5.1  Trouble to Join Helium** ===
632 -
633 -
634 634  (((
635 -**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
636 -
637 -
572 +Assume the device is powered correctly. If you don't see data in Helium. The possibilities are:
638 638  )))
639 639  
640 640  (((
641 -//1) You are out of Helium Gateway coverage. (If you have other end nodes, you can check whether they work and what is the signal strength you see in the platform)//
576 +1) You are out of Helium Gateway coverage. (If you have other end nodes, you can check whether they work and what is the signal strength you see in the platform)
642 642  )))
643 643  
644 644  (((
645 -//2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)//
580 +2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)
646 646  )))
647 647  
648 648  (((
649 -//3) You have input the wrong keys into Helium Platform ( You can send us the screenshots for the keys and Dragino support team can check for you)//
584 +3) You have input the wrong keys into Helium Platform ( You can send us the screenshots for the keys and Dragino support team can check for you)
650 650  
651 -
652 652  
653 653  )))
654 654  
655 -=== **3.5.2  Packet Loss for AU915 / US915 Band** ===
589 +=== 3.5.2 Packet Loss for AU915 / US915 Band ===
656 656  
657 -
658 658  (((
659 -//The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.//
592 +The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.
660 660  )))
661 661  
662 662  (((
663 -//The reason for this problem is that the node does not lock the channel after joining the network.//
664 -
665 -
596 +The reason for this problem is that the node does not lock the channel after joining the network.
666 666  )))
667 667  
668 668  (((
669 -**Solution:**
670 -
671 -
600 +Solution:
672 672  )))
673 673  
674 674  (((
675 -//(1) If the user does not have a device to upgrade the firmware, you can use the AT+CHE command or the downlink command to set the channel. It is best to turn off the adaptive rate (ADR).Reset the device after setting the channel.//
604 +(1) If the user does not have a device to upgrade the firmware, you can use the AT+CHE command or the downlink command to set the channel. It is best to turn off the adaptive rate (ADR).Reset the device after setting the channel.
676 676  )))
677 677  
678 678  * (((
679 -(% style="color:blue" %)**//AT Command: AT+CHE//**
608 +AT Command: AT+CHE
680 680  )))
681 681  
682 682  * (((
683 -//**Example: ** (% style="color:#037691" %)**AT+CHE=2**(%%)  ~/~/set channel mode to 1//
612 +Example:AT+CHE=1 ~/~/set channel mode to 1
684 684  )))
685 685  
686 686  * (((
687 -(% style="color:blue" %)**//Downlink Command: 0x24//**
688 -
689 -
690 -
691 -
616 +Downlink Command: 0x24
692 692  )))
693 693  
694 694  (((
695 -//Format: Command Code (0x24) followed by 1 bytes channel value.//
620 +Format: Command Code (0x24) followed by 1 bytes channel value.
696 696  )))
697 697  
698 -
699 699  (((
700 -//If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.//
624 +If the downlink payload=2401, it means set channel mode to 1, while type code is 24.
701 701  )))
702 702  
703 703  * (((
704 -//**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2//
628 +Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1
629 +)))
705 705  
706 -
707 -
631 +* (((
632 +Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5
708 708  )))
709 709  
710 710  (((
711 -//(2) If the user has a device to upgrade the firmware, it is better to upgrade the device to the latest version. The latest version has fixed the problem that the AU915/US915 frequency does not lock the channel.//
636 +(2) If the user has a device to upgrade the firmware, it is better to upgrade the device to the latest version. The latest version has fixed the problem that the AU915/US915 frequency does not lock the channel.
712 712  )))
713 713  
714 714  (((
715 -//The latest firmware for end node will have this bug fixed.//
640 +The latest firmware for end node will have this bug fixed.
716 716  )))
image-20220617140118-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -55.5 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0