Skip to Content

Changes for page Notes for Helium

Last modified by Xiaoling on 2025/07/31 17:59
From version 88.5
edited by Xiaoling
on 2022/07/23 14:37
Change comment: There is no comment for this version
To version 37.3
edited by Xiaoling
on 2022/05/26 09:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,22 +1,19 @@
1 -**~ Table of Contents:**
1 +**~ Contents:**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 += 1. Use Dragino Gateways/Hotspots with Helium =
6 6  
8 +== 1.1 Support Models ==
7 7  
8 -= **1.  Use Dragino Gateways/Hotspots with Helium** =
10 +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.
9 9  
10 -== **1.1  Support Models** ==
11 -
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.//
13 +Dragino has different gateway models that support different types.
17 17  )))
18 18  
19 -(% border="1" style="background-color:#ffffcc; width:510px" %)
16 +(% border="1" style="background-color:#ffffcc; width:560px" %)
20 20  |(% colspan="4" style="width:589px" %)(% style="color:green" %)**Dragino Hotspots for Helium**
21 21  |(% style="color:green; width:132px" %)**Model**|(% style="color:green; width:126px" %)**Hotspot Types**|(% style="color:green; width:121px" %)**Mining Ability**|(% style="color:green; width:203px" %)**Configure Instruction**
22 22  |(% style="width:132px" %)(((
... ... @@ -23,112 +23,89 @@
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.ConnectData-OnlyHotspottoHelium"]]
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]]
23 +)))|(% 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>>url:https://wiki.dragino.com/index.php/Notes_for_Helium#Connect_Data-Only_Hotspot_to_Helium]]
24 +|(% 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>>http://8.211.40.43/xwiki/bin/view/Main/User%20Manual%20for%20All%20Gateway%20models/HP0D/]]
28 28  
29 -
30 30  **Frequencies on the Helium Network**
31 31  
32 -* //The frequencies currently available are CN470/EU868/US915/AU915//
28 +* The frequencies currently available are CN470/EU868/US915/AU915
33 33  
30 +**Note**: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]
34 34  
32 += 2. Connect Data-Only Hotspot to Helium =
35 35  
36 -(% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]**
34 +== 2.1 Prerequisites ==
37 37  
36 +* Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
38 38  
38 +== 2.2 Step 1:Configure Frequency Band ==
39 39  
40 -= **2.  Connect Data-Only Hotspot to Helium** =
40 +Each country has a requirement for frequency region. Choose the right one for your area.
41 41  
42 -== **2.1  Prerequisites** ==
42 +[[image:image-20220524170317-1.png]]
43 43  
44 +Select fre
44 44  
45 -* //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//
46 +== 2.3 Step 2: Download the Helium-gateway-rs ==
46 46  
48 +Click Download Helium Server and the gateway will download the Helium-gateway-rs
47 47  
50 +[[image:image-20220524170337-2.png]]
48 48  
52 +Start download the Helium-gatewayrs
49 49  
50 -== **2.2  Step 1: Configure Frequency Band** ==
54 +[[image:image-20220524170359-3.png]]
51 51  
56 +Helium-gatewayrs download success
52 52  
53 -//Each country has a requirement for frequency region. Choose the right one for your area.//
58 +If download fails, click and download again
54 54  
55 -[[image:image-20220531175337-1.png]]
60 +[[image:image-20220524170437-4.png]]
56 56  
62 +Helium-gatewayrs download fail
57 57  
64 +== 2.4 Step 3: Install the Helium-gateway-rs ==
58 58  
59 -== **2.3  Step 2: Download the Helium-gateway-rs** ==
66 +Click **Install Helium Server** to install gateway-rs.
60 60  
68 +[[image:image-20220524170458-5.png]]
61 61  
62 -//Click Download Helium Server and the gateway will download the Helium-gateway-rs//
63 -
64 -[[image:image-20220615150600-1.png||height="559" width="1045"]]
65 -
66 -
67 -//**Start download to Helium-gateway-rs**//
68 -
69 -[[image:image-20220615150627-2.png||height="598" width="1044"]]
70 -
71 -//**Helium-gatewayrs download success**//
72 -
73 -
74 -//**If download fails, click and download again**//
75 -
76 -[[image:image-20220615150717-3.png||height="605" width="1039"]]
77 -
78 -
79 -== **2.4  Step 3: Install the Helium-gateway-rs** ==
80 -
81 -
82 -//Click **Install Helium Server** to install gateway-rs.//
83 -
84 -[[image:image-20220615150734-4.png||height="619" width="1035"]]
85 -
86 86  Install the Helium gateway-rs
87 87  
72 +**Note**: User will see the echo characters of Helium gateway-rs have been installed successfully.
88 88  
89 -(% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
74 +== 2.5 Step 4: Save&start the Helium Server ==
90 90  
76 +Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status.
91 91  
78 +[[image:image-20220524170524-6.png]]
92 92  
93 -== **2.5  Step 4: Save&start the Helium Server** ==
80 +Start Helium-gateway-rs
94 94  
82 +== 2.6 Step 5: Check Gateway Connection before onboarding ==
95 95  
96 -//By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
84 +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.
97 97  
98 -[[image:image-20220615150903-5.png||height="592" width="1031"]]
99 -
100 -
101 -//Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status.//
102 -
103 -[[image:image-20220615151057-6.png||height="580" width="1026"]]
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.//
87 +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 -[[image:image-20220526094537-1.png||height="395" width="1323"]]
90 +[[image:image-20220526094537-1.png]]
116 116  
92 +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.**
94 +**Note:** The hotspot is not valid for search in Helium Console before onboarding.
119 119  
120 -
121 121  == 2.7 Step 6: Onboarding Data-Only Hotspot ==
122 122  
123 -(% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .**
98 +(% 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 .**
124 124  
125 -//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.//
100 +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.
126 126  
127 -//Below are the steps we do as per above link here.//
102 +Below are the steps we do as per above link here.
128 128  
129 -
130 130  (((
131 -//**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.**//
105 +~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.
132 132  )))
133 133  
134 134  (% class="box" %)
... ... @@ -156,12 +156,12 @@
156 156  )))
157 157  
158 158  (((
159 -(% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.**
133 +**Note**: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.
160 160  )))
161 161  
162 162  
163 163  (((
164 -//**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.**//
138 +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.
165 165  )))
166 166  
167 167  (% class="box" %)
... ... @@ -193,13 +193,8 @@
193 193  )))
194 194  
195 195  (((
196 -//We got the txn info from this step.//
197 -\\//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**//
198 -
199 -
200 -(% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.**
201 -
202 -//Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.//
170 +We got the txn info from this step.
171 +\\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.
203 203  )))
204 204  
205 205  (% class="box" %)
... ... @@ -242,7 +242,7 @@
242 242  )))
243 243  
244 244  (((
245 -//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//
214 +4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.
246 246  )))
247 247  
248 248  (% class="box" %)
... ... @@ -297,24 +297,21 @@
297 297  )))
298 298  
299 299  (((
300 -**Note: The add hotspot and assert location step might need some time to be effect.**
269 +Note: The add hotspot and assert location step might need some time to be effect.
301 301  )))
302 302  
303 303  (((
304 -//After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//
305 -
306 -
273 +After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.
307 307  )))
308 308  
309 -== **2.8 Debug Connection** ==
276 +== 2.8 Debug Connection ==
310 310  
311 -=== **2.8.1 Check pkt-fwd running Log** ===
278 +=== 2.8.1 Check pkt-fwd running Log ===
312 312  
280 +This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.
313 313  
314 -//This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
315 -
316 316  (((
317 -//Below logs shows the gateway receive two LoRaWAN packets.//
283 +Below logs shows the gateway receive two LoRaWAN packets.
318 318  )))
319 319  
320 320  (% class="box" %)
... ... @@ -338,21 +338,18 @@
338 338  Sun Nov 14 14:28:19 2021 daemon.info lora_pkt_fwd[3145]: REPORT~~ ~#~## [DOWNSTREAM] ~#~##
339 339  )))
340 340  
307 +=== 2.8.2 Check gateway-rs Log ===
341 341  
342 -=== **2.8.2 Check gateway-rs Log** ===
309 +SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.
343 343  
311 +[[image:image-20220524170627-8.png]]
344 344  
345 -//SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
313 +Helium-gatewayrs log
346 346  
347 -[[image:image-20220531175809-7.png]]
348 -
349 -
350 350  **Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.
351 351  
317 +=== 2.8.3 View the public key address and animal name ===
352 352  
353 -=== **2.8.3 View the public key address and animal name** ===
354 -
355 -
356 356  (% class="box" %)
357 357  (((
358 358  (((
... ... @@ -369,142 +369,114 @@
369 369  )))
370 370  )))
371 371  
372 -[[image:image-20220531175844-8.png]]
335 +[[image:image-20220524170640-9.png]]
373 373  
374 374  Hostpot key and animal name
375 375  
339 +=== 2.8.4 Backup/Restor gateway-rs key ===
376 376  
377 -=== **2.8.4 Backup/Restor gateway-rs key** ===
378 -
379 379  (((
380 -//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.//
342 +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.
381 381  )))
382 382  
383 -[[image:image-20220531175919-9.png]]
345 +[[image:image-20220524170701-10.png]]
384 384  
347 +Backup and restore key
385 385  
349 +== 2.9 Forward the data to the other server ==
386 386  
387 -== **2.9 Forward the data to the other server** ==
351 +=== 2.9.1 Introduction ===
388 388  
389 -=== **2.9.1 Introduction** ===
390 -
391 -
392 392  (((
393 -//The Dragino gateway has supports the double server settings.//
354 +The Dragino gateway has supports the double server settings.
394 394  )))
395 395  
396 396  (((
397 -//Users can back to the page of Semtech UDP to configure other server settings.//
398 -
399 -
358 +Users can back to the page of Semtech UDP to configure other server settings.
400 400  )))
401 401  
402 -=== **2.9.2 Example** ===
361 +=== 2.9.2 Example ===
403 403  
363 +The following takes The Things Network as another LoRaWAN server as an example,
404 404  
405 -//The following takes The Things Network as another LoRaWAN server as an example.//
365 +==== 2.9.2.1 Step 1: Back to Semtech UDP page ====
406 406  
367 +[[image:image-20220524170722-11.png]]
407 407  
408 -==== **2.9.2.1 Step 1: Back to Semtech UDP page** ====
409 -
410 -
411 -[[image:image-20220531180002-10.png]]
412 -
413 413  Back to Semtech UDP page
414 414  
371 +==== 2.9.2.2 Step 2: Configure the double server forwarding ====
415 415  
416 -==== **2.9.2.2 Step 2: Configure the double server forwarding** ====
373 +[[image:image-20220524170800-12.png]]
417 417  
375 +Configure the double server
418 418  
419 -[[image:image-20220531180048-11.png]]
377 +The user can configure the secondary server and then click the button of Save&Apply.
420 420  
379 +== 2.10 Connect Full Hotspot to Helium ==
421 421  
422 -//The user can configure the secondary server and then click the button of **Save&Apply**.//
381 += 3. Use Dragino Sensors with Helium =
423 423  
383 +== 3.1 How to add up user's end-node with Helium console ==
424 424  
425 -== **2.10 Connect Full Hotspot to Helium** ==
385 +=== 3.1.1 Step 1:Login the Helium console ===
426 426  
427 -= **3. Use Dragino Sensors with Helium** =
387 +User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]
428 428  
389 +[[image:image-20220524170958-13.png]]
429 429  
430 -== **3.1 How to add up user's end-node with Helium console** ==
431 -
432 -
433 -=== **3.1.1 Step 1: Login the Helium console** ===
434 -
435 -
436 -//User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]//
437 -
438 -[[image:image-20220531180150-12.png]]
439 -
440 440  login Helium console
441 441  
393 +=== 3.1.2 Step 2:Add up your end-node's key ===
442 442  
443 -=== **3.1.2 Step 2: Add up your end-node's key** ===
395 +User add up end-node's key from console ~-~->dervice
444 444  
397 +[[image:image-20220524171027-14.png]]
445 445  
446 -//User add up end-node's key from console ~-~->dervice//
447 -
448 -[[image:image-20220531180224-13.png]]
449 -
450 450  To add a device
451 451  
401 +=== 3.1.3 Step 3:Activate the end-node ===
452 452  
453 -=== **3.1.3 Step 3:Activate the end-node** ===
454 -
455 -
456 456  (((
457 -//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**//
404 +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**
458 458  )))
459 459  
460 -[[image:image-20220531105239-2.png]]
407 +[[image:image-20220524171045-15.png]]
461 461  
462 462  end-node traffic.
463 463  
411 +== 3.2 How to use decoder ==
464 464  
465 -== **3.2 How to use decoder** ==
413 +=== 3.2.1 Step 1:Users can create decoders on functions ===
466 466  
467 -=== **3.2.1 Step 1:Users can create decoders on functions** ===
415 +[[image:image-20220524171109-16.png]]
468 468  
469 -
470 -[[image:image-20220531105325-3.png]]
471 -
472 472  Decoder.
473 473  
419 +=== 3.2.2 Step 2:Add a decoder in functions and apply it to the specified label ===
474 474  
475 -=== **3.2.2 Step 2:Add a decoder in functions and apply it to the specified label** ===
421 +[[image:image-20220524171130-17.png]]
476 476  
423 +[[image:image-20220524171156-18.png]]
477 477  
478 -[[image:image-20220526095629-6.png]]
425 +[[image:image-20220524171317-20.png]]
479 479  
427 +Decoder.
480 480  
481 -[[image:image-20220526095553-5.png]]
429 +Add decoder complete.
482 482  
431 +== 3.3 How to send a downlink to end device from Helium ==
483 483  
484 -[[image:image-20220526100057-8.png||height="352" width="1133"]]
485 -
486 -
487 -**//Add decoder complete.//**
488 -
489 -=== **3.2.3 Where is the decoder？** ===
490 -
491 -[[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
492 -
493 -[[image:image-20220617140118-1.png||height="550" width="883"]]
494 -
495 -== **3.3 How to send a downlink to end device from Helium** ==
496 -
497 -
498 498  (((
499 -//The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://
434 +The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example:
500 500  )))
501 501  
502 502  (((
503 -//The Downlink command comes from this link：[[End Device Downlink Command>>End Device AT Commands and Downlink Command]]//
438 +The Downlink command comes from this link：[[https:~~/~~/wiki.dragino.com/index.php?title=End_Device_Downlink_Command>>url:https://wiki.dragino.com/index.php?title=End_Device_Downlink_Command]]
504 504  )))
505 505  
506 506  (((
507 -//Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds//
442 +Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
508 508  )))
509 509  
510 510  (% class="box" %)
... ... @@ -516,164 +516,142 @@
516 516  
517 517  Downlink
518 518  
454 +== 3.4 How to add integration to different IoT Servers ==
519 519  
520 -== **3.4 How to add integration to different IoT Servers** ==
456 +=== 3.4.1 TagoIO ===
521 521  
522 -=== **3.4.1 TagoIO** ===
458 +The steps to add integration are very simple. Please see the following process.
523 523  
460 +[[image:image-20220524171412-22.png]]
524 524  
525 -**//The steps to add integration are very simple. Please see the following process.//**
462 +TagoIO.
526 526  
464 +Generate the authorization code and then copy it.
527 527  
528 -[[image:image-20220526102429-23.png||height="630" width="1198"]]
466 +[[image:image-20220524171432-23.png]]
529 529  
468 +TagoIO.
530 530  
470 +Apply Integration to Label.
531 531  
532 -**//Generate the authorization code and then copy it.//**
472 +[[image:image-20220524171451-24.png]]
533 533  
474 +TagoIO.
534 534  
535 -[[image:image-20220526100452-10.png||height="314" width="1188"]]
476 +[[image:image-20220524171510-25.png]]
536 536  
478 +TagoIO.
537 537  
480 +Click LoRaWAN Helium,select the device.
538 538  
539 -//**Apply Integration to Label.**//
482 +[[image:image-20220524171614-26.png]]
540 540  
484 +TagoIO.
541 541  
542 -[[image:image-20220526100802-13.png]]
486 +Fill in DEVEUI and create my device.
543 543  
488 +[[image:image-20220524171650-27.png]]
544 544  
545 -
546 -[[image:image-20220526100927-14.png]]
547 -
548 -
549 -
550 -**//Click LoRaWAN Helium,select the device.//**
551 -
552 -
553 -[[image:image-20220526101215-15.png||height="599" width="1117"]]
554 -
555 -
556 -
557 -**//Fill in DEVEUI and create my device.//**
558 -
559 -
560 -[[image:image-20220526101419-16.png]]
561 -
562 562  TagoIO.
563 563  
492 +=== 3.4.2 Cayenne ===
564 564  
565 -=== **3.4.2 Cayenne** ===
494 +The process of creating devices is similar to Tago.
566 566  
496 +[[image:image-20220524171744-29.png]]
567 567  
568 -//The process of creating devices is similar to Tago.//
569 -
570 -[[image:image-20220526101616-18.png||height="456" width="1097"]]
571 -
572 572  Cayenne.
573 573  
500 +[[image:image-20220524171826-30.png]]
574 574  
575 -[[image:image-20220526101547-17.png||height="656" width="1092"]]
576 -
577 577  Cayenne.
578 578  
504 +[[image:image-20220524171852-31.png]]
579 579  
580 -[[image:image-20220526101702-19.png||height="528" width="1109"]]
581 -
582 582  Cayenne.
583 583  
508 +[[image:image-20220524171915-32.png]]
584 584  
585 -[[image:image-20220526102303-22.png]]
586 -
587 587  Cayenne.
588 588  
512 +[[image:image-20220524171942-33.png]]
589 589  
590 -[[image:image-20220526102114-21.png]]
591 -
592 592  Cayenne.
593 593  
516 +[[image:image-20220524172009-34.png]]
594 594  
595 -[[image:image-20220526101940-20.png||height="543" width="1044"]]
596 -
597 597  Cayenne.
598 598  
520 +== 3.5 Trouble Shooting ==
599 599  
600 -== **3.5 Trouble Shooting** ==
522 +=== 3.5.1 Trouble to Join Helium ===
601 601  
602 -=== **3.5.1 Trouble to Join Helium** ===
603 -
604 -
605 605  (((
606 -**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
607 -
608 -
525 +Assume the device is powered correctly. If you don't see data in Helium. The possibilities are:
609 609  )))
610 610  
611 611  (((
612 -//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)//
529 +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)
613 613  )))
614 614  
615 615  (((
616 -//2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)//
533 +2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)
617 617  )))
618 618  
619 619  (((
620 -//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)//
621 -
622 -
537 +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)
623 623  )))
624 624  
625 -=== **3.5.2 Packet Loss for AU915 / US915 Band** ===
540 +=== 3.5.2 Packet Loss for AU915 / US915 Band ===
626 626  
627 -
628 628  (((
629 -//The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.//
543 +The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.
630 630  )))
631 631  
632 632  (((
633 -//The reason for this problem is that the node does not lock the channel after joining the network.//
547 +The reason for this problem is that the node does not lock the channel after joining the network.
634 634  )))
635 635  
636 636  (((
637 -**Solution:**
638 -
639 -
551 +Solution:
640 640  )))
641 641  
642 642  (((
643 -//(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.//
555 +(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.
644 644  )))
645 645  
646 646  * (((
647 -//AT Command: AT+CHE//
559 +AT Command: AT+CHE
648 648  )))
649 649  
650 650  * (((
651 -//Example:**AT+CHE=2** ~/~/set channel mode to 1//
563 +Example:AT+CHE=1 ~/~/set channel mode to 1
652 652  )))
653 653  
654 654  * (((
655 -//Downlink Command: 0x24//
567 +Downlink Command: 0x24
656 656  )))
657 657  
658 658  (((
659 -//Format: Command Code (0x24) followed by 1 bytes channel value.//
571 +Format: Command Code (0x24) followed by 1 bytes channel value.
660 660  )))
661 661  
662 662  (((
663 -//If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.//
575 +If the downlink payload=2401, it means set channel mode to 1, while type code is 24.
664 664  )))
665 665  
666 666  * (((
667 -//Example 1: Downlink Payload: **0x2402** ~/~/ set channel mode to 2//
579 +Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1
580 +)))
668 668  
669 -
670 -
582 +* (((
583 +Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5
671 671  )))
672 672  
673 673  (((
674 -//(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.//
587 +(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.
675 675  )))
676 676  
677 677  (((
678 -//The latest firmware for end node will have this bug fixed.//
591 +The latest firmware for end node will have this bug fixed.
679 679  )))
image-20220526095413-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -140.3 KB
Content
image-20220526095503-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -177.6 KB
Content
image-20220526095553-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -130.6 KB
Content
image-20220526095629-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -151.9 KB
Content
image-20220526095759-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -151.9 KB
Content
image-20220526100057-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -56.6 KB
Content
image-20220526100227-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -55.5 KB
Content
image-20220526100452-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -92.2 KB
Content
image-20220526100542-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -92.2 KB
Content
image-20220526100802-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -120.4 KB
Content
image-20220526100927-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -51.2 KB
Content
image-20220526101215-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -298.6 KB
Content
image-20220526101419-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -190.2 KB
Content
image-20220526101547-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -128.2 KB
Content
image-20220526101616-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -130.2 KB
Content
image-20220526101702-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -129.4 KB
Content
image-20220526101940-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -412.4 KB
Content
image-20220526102114-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -201.0 KB
Content
image-20220526102303-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.4 KB
Content
image-20220526102429-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -397.5 KB
Content
image-20220531105203-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -105.7 KB
Content
image-20220531105239-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -88.0 KB
Content
image-20220531105325-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -65.2 KB
Content
image-20220531175337-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -47.8 KB
Content
image-20220531175421-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -60.6 KB
Content
image-20220531175500-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -69.3 KB
Content
image-20220531175530-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -58.5 KB
Content
image-20220531175610-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -68.4 KB
Content
image-20220531175650-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -70.4 KB
Content
image-20220531175809-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -32.6 KB
Content
image-20220531175844-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -67.5 KB
Content
image-20220531175919-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -67.2 KB
Content
image-20220531180002-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -66.7 KB
Content
image-20220531180048-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -62.3 KB
Content
image-20220531180150-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -20.2 KB
Content
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