Changes for page Notes for Helium

Last modified by Edwin Chen on 2024/03/25 08:22
<
From version < 90.1 >
edited by Xiaoye
on 2022/08/17 10:28
To version < 72.2 >
edited by Xiaoling
on 2022/05/31 18:01
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoye
1 +XWiki.Xiaoling
Content
... ... @@ -1,4 +1,4 @@
1 -**~ Table of Contents:**
1 +**~ Contents:**
2 2  
3 3  {{toc/}}
4 4  
... ... @@ -5,15 +5,14 @@
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 +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.
12 12  
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 -
15 15  (((
16 -//Dragino has different gateway models that support different types.//
15 +Dragino has different gateway models that support different types.
17 17  )))
18 18  
19 19  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -23,114 +23,97 @@
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 -(% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]**
32 +**Note**: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]
34 34  
35 35  
35 += 2. Connect Data-Only Hotspot to Helium =
36 36  
37 -= **2.  Connect Data-Only Hotspot to Helium** =
37 +== 2.1 Prerequisites ==
38 38  
39 -== **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/]]
40 40  
41 +== 2.2 Step 1: Configure Frequency Band ==
41 41  
42 -* //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.
43 43  
44 -
45 -== **2.2  Step 1: Configure Frequency Band** ==
46 -
47 -
48 -//Each country has a requirement for frequency region. Choose the right one for your area.//
49 -
50 50  [[image:image-20220531175337-1.png]]
51 51  
47 +Select fre
52 52  
53 53  
54 -== **2.3  Step 2: Download the Helium-gateway-rs** ==
50 +== 2.3 Step 2: Download the Helium-gateway-rs ==
55 55  
52 +Click Download Helium Server and the gateway will download the Helium-gateway-rs
56 56  
57 -//Click Download Helium Server and the gateway will download the Helium-gateway-rs//
54 +[[image:image-20220531175421-2.png]]
58 58  
59 -[[image:image-20220615150600-1.png||height="559" width="1045"]]
56 +Start download the Helium-gatewayrs
60 60  
61 61  
62 -//**Start download to Helium-gateway-rs**//
59 +[[image:image-20220531175500-3.png]]
63 63  
64 -[[image:image-20220615150627-2.png||height="598" width="1044"]]
61 +Helium-gatewayrs download success
65 65  
66 -//**Helium-gatewayrs download success**//
67 67  
64 +If download fails, click and download again
68 68  
69 -//**If download fails, click and download again**//
66 +[[image:image-20220531175530-4.png]]
70 70  
71 -[[image:image-20220615150717-3.png||height="605" width="1039"]]
68 +Helium-gatewayrs download fail
72 72  
73 73  
71 +== 2.4 Step 3: Install the Helium-gateway-rs ==
74 74  
75 -== **2.4  Step 3: Install the Helium-gateway-rs** ==
73 +Click **Install Helium Server** to install gateway-rs.
76 76  
75 +[[image:image-20220531175610-5.png]]
77 77  
78 -//Click **Install Helium Server** to install gateway-rs.//
79 -
80 -[[image:image-20220615150734-4.png||height="619" width="1035"]]
81 -
82 82  Install the Helium gateway-rs
83 83  
79 +**Note**: User will see the echo characters of Helium gateway-rs have been installed successfully.
84 84  
85 -(% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
86 86  
82 +== 2.5 Step 4: Save&start the Helium Server ==
87 87  
84 +Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status.
88 88  
89 -== **2.5  Step 4: Save&start the Helium Server** ==
86 +[[image:image-20220531175650-6.png]]
90 90  
88 +Start Helium-gateway-rs
91 91  
92 -//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  
91 +== 2.6 Step 5: Check Gateway Connection before onboarding ==
94 94  
95 -[[image:image-20220615150903-5.png||height="592" width="1031"]]
93 +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.
96 96  
97 -
98 -
99 -//Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.//
100 -
101 -[[image:image-20220615151057-6.png||height="580" width="1026"]]
102 -
103 -
104 -
105 -== **2.6  Step 5: Check Gateway Connection before onboarding** ==
106 -
107 -
108 -//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.//
109 -
110 110  (((
111 -//Check end device event from [[Helium Console>>url:https://staging-console.helium.wtf/]], We can see the LGT92 data arrived Helium via our hotspot.//
96 +Check end device event from [[Helium Console>>url:https://staging-console.helium.wtf/]], We can see the LGT92 data arrived Helium via our hotspot.
112 112  )))
113 113  
114 114  [[image:image-20220526094537-1.png||height="395" width="1323"]]
115 115  
101 +Check if the packet is transferred via LPS8
116 116  
117 -(% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**
103 +**Note:** The hotspot is not valid for search in Helium Console before onboarding.
118 118  
119 119  
106 +== 2.7 Step 6: Onboarding Data-Only Hotspot ==
120 120  
121 -== **2.7  Step 6: Onboarding Data-Only Hotspot** ==
108 +(% 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 .**
122 122  
110 +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.
123 123  
124 -(% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .**
112 +Below are the steps we do as per above link here.
125 125  
126 -
127 -//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.//
128 -
129 -//Below are the steps we do as per above link here.//
130 -
131 -
132 132  (((
133 -(% 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.**//
115 +~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.
134 134  )))
135 135  
136 136  (% class="box" %)
... ... @@ -157,15 +157,13 @@
157 157  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
158 158  )))
159 159  
160 -
161 161  (((
162 -(% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.**
143 +**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.**//
148 +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.//
180 +We got the txn info from this step.
181 +\\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.**//
224 +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" %)
... ... @@ -306,27 +306,24 @@
306 306  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
307 307  )))
308 308  
309 -
310 310  (((
311 -(% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.**
279 +Note: The add hotspot and assert location step might need some time to be effect.
312 312  )))
313 313  
314 314  (((
315 -//After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//
283 +After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.
316 316  
317 -
318 318  
319 319  )))
320 320  
321 -== **2.8  Debug Connection** ==
288 +== 2.8 Debug Connection ==
322 322  
323 -=== **2.8.1  Check pkt-fwd running Log** ===
290 +=== 2.8.1 Check pkt-fwd running Log ===
324 324  
292 +This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.
325 325  
326 -//This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
327 -
328 328  (((
329 -//Below logs shows the gateway receive two LoRaWAN packets.//
295 +Below logs shows the gateway receive two LoRaWAN packets.
330 330  )))
331 331  
332 332  (% class="box" %)
... ... @@ -351,22 +351,19 @@
351 351  )))
352 352  
353 353  
320 +=== 2.8.2 Check gateway-rs Log ===
354 354  
355 -=== **2.8.2  Check gateway-rs Log** ===
322 +SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.
356 356  
357 -
358 -//SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
359 -
360 360  [[image:image-20220531175809-7.png]]
361 361  
326 +Helium-gatewayrs log
362 362  
363 -(% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
328 +**Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.
364 364  
365 365  
331 +=== 2.8.3 View the public key address and animal name ===
366 366  
367 -=== **2.8.3  View the public key address and animal name** ===
368 -
369 -
370 370  (% class="box" %)
371 371  (((
372 372  (((
... ... @@ -388,97 +388,80 @@
388 388  Hostpot key and animal name
389 389  
390 390  
354 +=== 2.8.4 Backup/Restor gateway-rs key ===
391 391  
392 -=== **2.8.4  Backup/Restor gateway-rs key** ===
393 -
394 -
395 395  (((
396 -//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.//
357 +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.
397 397  )))
398 398  
399 399  [[image:image-20220531175919-9.png]]
400 400  
362 +Backup and restore key
401 401  
402 402  
403 -== **2.9  Forward the data to the other server** ==
365 +== 2.9 Forward the data to the other server ==
404 404  
405 -=== **2.9.1  Introduction** ===
367 +=== 2.9.1 Introduction ===
406 406  
407 -
408 408  (((
409 -//The Dragino gateway has supports the double server settings.//
370 +The Dragino gateway has supports the double server settings.
410 410  )))
411 411  
412 412  (((
413 -//Users can back to the page of Semtech UDP to configure other server settings.//
374 +Users can back to the page of Semtech UDP to configure other server settings.
414 414  
415 -
416 416  
417 417  )))
418 418  
419 -=== **2.9.2  Example** ===
379 +=== 2.9.2 Example ===
420 420  
381 +The following takes The Things Network as another LoRaWAN server as an example.
421 421  
422 -//The following takes The Things Network as another LoRaWAN server as an example.//
423 423  
384 +==== 2.9.2.1 Step 1: Back to Semtech UDP page ====
424 424  
425 -
426 -==== (% style="color:blue" %)**Step 1: Back to Semtech UDP page**(%%) ====
427 -
428 -
429 429  [[image:image-20220531180002-10.png]]
430 430  
431 431  Back to Semtech UDP page
432 432  
433 433  
391 +==== 2.9.2.2 Step 2: Configure the double server forwarding ====
434 434  
435 -==== (% style="color:blue" %)**Step 2: Configure the double server forwarding**(%%) ====
436 -
437 -
438 438  [[image:image-20220531180048-11.png]]
439 439  
395 +Configure the double server
440 440  
441 -//The user can configure the secondary server and then click the button of **Save&Apply**.//
397 +The user can configure the secondary server and then click the button of Save&Apply.
442 442  
443 443  
400 +== 2.10 Connect Full Hotspot to Helium ==
444 444  
445 -== **2.10  Connect Full Hotspot to Helium** ==
402 += 3. Use Dragino Sensors with Helium =
446 446  
404 +== 3.1 How to add up user's end-node with Helium console ==
447 447  
406 +=== 3.1.1 Step 1: Login the Helium console ===
448 448  
449 -= **3.  Use Dragino Sensors with Helium** =
408 +User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]
450 450  
451 -
452 -== **3.1  How to add up user's end-node with Helium console** ==
453 -
454 -
455 -=== **3.1.1  Step 1: Login the Helium console** ===
456 -
457 -
458 -//User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]//
459 -
460 460  [[image:image-20220531180150-12.png]]
461 461  
462 462  login Helium console
463 463  
464 464  
415 +=== 3.1.2 Step 2: Add up your end-node's key ===
465 465  
466 -=== **3.1.2  Step 2: Add up your end-node's key** ===
417 +User add up end-node's key from console ~-~->dervice
467 467  
419 +[[image:image-20220524171027-14.png]]
468 468  
469 -//User add up end-node's key from console ~-~->dervice//
470 -
471 -[[image:image-20220531180224-13.png]]
472 -
473 473  To add a device
474 474  
475 475  
424 +=== 3.1.3 Step 3:Activate the end-node ===
476 476  
477 -=== **3.1.3  Step 3: Activate the end-node** ===
478 -
479 -
480 480  (((
481 -//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**//
427 +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**
482 482  )))
483 483  
484 484  [[image:image-20220531105239-2.png]]
... ... @@ -486,21 +486,17 @@
486 486  end-node traffic.
487 487  
488 488  
435 +== 3.2 How to use decoder ==
489 489  
490 -== **3.2  How to use decoder** ==
437 +=== 3.2.1 Step 1:Users can create decoders on functions ===
491 491  
492 -=== **3.2.1  Step 1: Users can create decoders on functions** ===
493 -
494 -
495 495  [[image:image-20220531105325-3.png]]
496 496  
497 497  Decoder.
498 498  
499 499  
444 +=== 3.2.2 Step 2:Add a decoder in functions and apply it to the specified label ===
500 500  
501 -=== **3.2.2  Step 2: Add a decoder in functions and apply it to the specified label** ===
502 -
503 -
504 504  [[image:image-20220526095629-6.png]]
505 505  
506 506  
... ... @@ -509,37 +509,28 @@
509 509  
510 510  [[image:image-20220526100057-8.png||height="352" width="1133"]]
511 511  
512 -**//Add decoder complete.//**
454 +Decoder.
513 513  
456 +Add decoder complete.
514 514  
515 515  
516 -=== **3.2.3  Where is the decoder？** ===
459 +== 3.3 How to send a downlink to end device from Helium ==
517 517  
518 -
519 -[[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
520 -
521 -[[image:image-20220617140118-1.png||height="550" width="883"]]
522 -
523 -
524 -
525 -== **3.3  How to send a downlink to end device from Helium** ==
526 -
527 -
528 528  (((
529 -//The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://
462 +The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example:
530 530  )))
531 531  
532 532  (((
533 -//The Downlink command comes from this link：[[End Device Downlink Command>>End Device AT Commands and Downlink Command]]//
466 +The Downlink command comes from this link：[[End Device Downlink Command>>End Device AT Commands and Downlink Command]]
534 534  )))
535 535  
536 536  (((
537 -//Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds//
470 +Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
538 538  )))
539 539  
540 540  (% class="box" %)
541 541  (((
542 -**01 00 00 3C ~-~-> AQAAPA==**
475 +01 00 00 3C ~-~-> AQAAPA==
543 543  )))
544 544  
545 545  [[image:image-20220524171341-21.png]]
... ... @@ -547,58 +547,55 @@
547 547  Downlink
548 548  
549 549  
483 +== 3.4 How to add integration to different IoT Servers ==
550 550  
551 -== **3.4  How to add integration to different IoT Servers** ==
485 +=== 3.4.1 TagoIO ===
552 552  
553 -=== **3.4.1  TagoIO** ===
487 +The steps to add integration are very simple. Please see the following process.
554 554  
555 -
556 -**//The steps to add integration are very simple. Please see the following process.//**
557 -
558 -
559 559  [[image:image-20220526102429-23.png||height="630" width="1198"]]
560 560  
491 +TagoIO.
561 561  
562 562  
563 -**//Generate the authorization code and then copy it.//**
494 +Generate the authorization code and then copy it.
564 564  
565 -
566 566  [[image:image-20220526100452-10.png||height="314" width="1188"]]
567 567  
498 +TagoIO.
568 568  
569 569  
570 -//**Apply Integration to Label.**//
501 +Apply Integration to Label.
571 571  
572 -
573 573  [[image:image-20220526100802-13.png]]
574 574  
575 575  
506 +TagoIO.
576 576  
508 +
577 577  [[image:image-20220526100927-14.png]]
578 578  
511 +TagoIO.
579 579  
580 580  
581 -**//Click LoRaWAN Helium,select the device.//**
514 +Click LoRaWAN Helium,select the device.
582 582  
583 -
584 584  [[image:image-20220526101215-15.png||height="599" width="1117"]]
585 585  
518 +TagoIO.
586 586  
587 587  
588 -**//Fill in DEVEUI and create my device.//**
521 +Fill in DEVEUI and create my device.
589 589  
590 -
591 591  [[image:image-20220526101419-16.png]]
592 592  
593 593  TagoIO.
594 594  
595 595  
528 +=== 3.4.2 Cayenne ===
596 596  
597 -=== **3.4.2  Cayenne** ===
530 +The process of creating devices is similar to Tago.
598 598  
599 -
600 -//The process of creating devices is similar to Tago.//
601 -
602 602  [[image:image-20220526101616-18.png||height="456" width="1097"]]
603 603  
604 604  Cayenne.
... ... @@ -629,95 +629,78 @@
629 629  Cayenne.
630 630  
631 631  
562 +== 3.5 Trouble Shooting ==
632 632  
633 -== **3.5  Trouble Shooting** ==
564 +=== 3.5.1 Trouble to Join Helium ===
634 634  
635 -=== **3.5.1  Trouble to Join Helium** ===
636 -
637 -
638 638  (((
639 -**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
640 -
641 -
567 +Assume the device is powered correctly. If you don't see data in Helium. The possibilities are:
642 642  )))
643 643  
644 644  (((
645 -//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)//
571 +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)
646 646  )))
647 647  
648 648  (((
649 -//2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)//
575 +2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)
650 650  )))
651 651  
652 652  (((
653 -//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)//
579 +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)
654 654  
655 -4) Your gateway is not onboarding to the helium explore, after 23 versions, the data-only hotspot(Gateway) is requested onboarding to helium explore. ~-~-> Please refer to [[Step 2.7>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20Helium/#H2.7A0Step6:OnboardingData-OnlyHotspot]] to do it.
656 -
657 -5). You have to use the frequency plan that is compatible with your region.
658 -
659 -For example, if you are in USA, you have to use the US915 frequency plan. More frequency plans details on the helium network: [[https:~~/~~/docs.helium.com/lorawan-on-helium/frequency-plans>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans]]
660 -
661 -
662 662  
663 663  )))
664 664  
665 -=== **3.5.2  Packet Loss for AU915 / US915 Band** ===
584 +=== 3.5.2 Packet Loss for AU915 / US915 Band ===
666 666  
667 -
668 668  (((
669 -//The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.//
587 +The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.
670 670  )))
671 671  
672 672  (((
673 -//The reason for this problem is that the node does not lock the channel after joining the network.//
674 -
675 -
591 +The reason for this problem is that the node does not lock the channel after joining the network.
676 676  )))
677 677  
678 678  (((
679 -(% style="color:red" %)**Solution:**
680 -
681 -
595 +Solution:
682 682  )))
683 683  
684 684  (((
685 -//(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.//
599 +(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.
686 686  )))
687 687  
688 688  * (((
689 -(% style="color:blue" %)**//AT Command: AT+CHE//**
603 +AT Command: AT+CHE
690 690  )))
691 691  
692 692  * (((
693 -//**Example: ** (% style="color:#037691" %)**AT+CHE=2**(%%)  ~/~/set channel mode to 1//
607 +Example:AT+CHE=1 ~/~/set channel mode to 1
694 694  )))
695 695  
696 696  * (((
697 -(% style="color:blue" %)**//Downlink Command: 0x24//**
698 -
699 -
611 +Downlink Command: 0x24
700 700  )))
701 701  
702 702  (((
703 -//Format: Command Code (0x24) followed by 1 bytes channel value.//
615 +Format: Command Code (0x24) followed by 1 bytes channel value.
704 704  )))
705 705  
706 -
707 707  (((
708 -//If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.//
619 +If the downlink payload=2401, it means set channel mode to 1, while type code is 24.
709 709  )))
710 710  
711 711  * (((
712 -//**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2//
623 +Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1
624 +)))
713 713  
714 -
626 +* (((
627 +Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5
715 715  )))
716 716  
717 717  (((
718 -//(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.//
631 +(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.
719 719  )))
720 720  
721 721  (((
722 -//The latest firmware for end node will have this bug fixed.//
635 +The latest firmware for end node will have this bug fixed.
723 723  )))
image-20220531180224-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -65.0 KB
Content
image-20220615150600-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -37.6 KB
Content
image-20220615150627-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -42.6 KB
Content
image-20220615150717-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -44.6 KB
Content
image-20220615150734-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -42.8 KB
Content
image-20220615150903-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -63.1 KB
Content
image-20220615151057-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -64.0 KB
Content
image-20220617140118-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -55.5 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0