Skip to Content

Changes for page Notes for Helium

Last modified by Xiaoling on 2025/07/31 17:59
From version 83.1
edited by Kilight Cao
on 2022/06/15 15: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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Kilight
1 +XWiki.Xiaoling
Content
... ... @@ -3,19 +3,17 @@
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 -//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.//
13 -
14 14  (((
15 -//Dragino has different gateway models that support different types.//
13 +Dragino has different gateway models that support different types.
16 16  )))
17 17  
18 -(% border="1" style="background-color:#ffffcc; width:510px" %)
16 +(% border="1" style="background-color:#ffffcc; width:560px" %)
19 19  |(% colspan="4" style="width:589px" %)(% style="color:green" %)**Dragino Hotspots for Helium**
20 20  |(% 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**
21 21  |(% style="width:132px" %)(((
... ... @@ -22,102 +22,89 @@
22 22  [[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]],
23 23  
24 24  [[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]]
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"]]
26 -|(% 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/]]
27 27  
28 28  **Frequencies on the Helium Network**
29 29  
30 -* //The frequencies currently available are CN470/EU868/US915/AU915//
28 +* The frequencies currently available are CN470/EU868/US915/AU915
31 31  
32 -(% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]**
30 +**Note**: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]
33 33  
32 += 2. Connect Data-Only Hotspot to Helium =
34 34  
35 -= **2. Connect Data-Only Hotspot to Helium** =
34 +== 2.1 Prerequisites ==
36 36  
37 -== **2.1 Prerequisites** ==
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 -* //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//
40 +Each country has a requirement for frequency region. Choose the right one for your area.
41 41  
42 -== **2.2 Step 1: Configure Frequency Band** ==
42 +[[image:image-20220524170317-1.png]]
43 43  
44 +Select fre
44 44  
45 -//Each country has a requirement for frequency region. Choose the right one for your area.//
46 +== 2.3 Step 2: Download the Helium-gateway-rs ==
46 46  
47 -[[image:image-20220531175337-1.png]]
48 +Click Download Helium Server and the gateway will download the Helium-gateway-rs
48 48  
50 +[[image:image-20220524170337-2.png]]
49 49  
50 -== **2.3 Step 2: Download the Helium-gateway-rs** ==
52 +Start download the Helium-gatewayrs
51 51  
54 +[[image:image-20220524170359-3.png]]
52 52  
53 -//Click Download Helium Server and the gateway will download the Helium-gateway-rs//
56 +Helium-gatewayrs download success
54 54  
55 -[[image:image-20220615150600-1.png||height="559" width="1045"]]
58 +If download fails, click and download again
56 56  
57 -//**Start download to Helium-gateway-rs**//
60 +[[image:image-20220524170437-4.png]]
58 58  
62 +Helium-gatewayrs download fail
59 59  
60 -[[image:image-20220615150627-2.png||height="598" width="1044"]]
64 +== 2.4 Step 3: Install the Helium-gateway-rs ==
61 61  
62 -//**Helium-gatewayrs download success**//
66 +Click **Install Helium Server** to install gateway-rs.
63 63  
68 +[[image:image-20220524170458-5.png]]
64 64  
65 -//**If download fails, click and download again**//
66 -
67 -[[image:image-20220615150717-3.png||height="605" width="1039"]]
68 -
69 -
70 -== **2.4 Step 3: Install the Helium-gateway-rs** ==
71 -
72 -
73 -//Click **Install Helium Server** to install gateway-rs.//
74 -
75 -[[image:image-20220615150734-4.png||height="619" width="1035"]]
76 -
77 77  Install the Helium gateway-rs
78 78  
79 -(% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
72 +**Note**: User will see the echo characters of Helium gateway-rs have been installed successfully.
80 80  
74 +== 2.5 Step 4: Save&start the Helium Server ==
81 81  
82 -== **2.5 Step 4: Save&start the Helium Server** ==
76 +Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status.
83 83  
78 +[[image:image-20220524170524-6.png]]
84 84  
85 -//By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
80 +Start Helium-gateway-rs
86 86  
87 -[[image:image-20220615150903-5.png||height="592" width="1031"]]
82 +== 2.6 Step 5: Check Gateway Connection before onboarding ==
88 88  
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.
89 89  
90 -//Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status.//
91 -
92 -[[image:image-20220615151057-6.png||height="580" width="1026"]]
93 -
94 -
95 -== **2.6 Step 5: Check Gateway Connection before onboarding** ==
96 -
97 -
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.//
99 -
100 100  (((
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.//
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.
102 102  )))
103 103  
104 -[[image:image-20220526094537-1.png||height="395" width="1323"]]
90 +[[image:image-20220526094537-1.png]]
105 105  
92 +Check if the packet is transferred via LPS8
106 106  
107 -(% 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.
108 108  
109 -
110 110  == 2.7 Step 6: Onboarding Data-Only Hotspot ==
111 111  
112 112  (% 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 .**
113 113  
114 -//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.
115 115  
116 -//Below are the steps we do as per above link here.//
102 +Below are the steps we do as per above link here.
117 117  
118 -
119 119  (((
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.**//
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.
121 121  )))
122 122  
123 123  (% class="box" %)
... ... @@ -145,12 +145,12 @@
145 145  )))
146 146  
147 147  (((
148 -(% 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.
149 149  )))
150 150  
151 151  
152 152  (((
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.**//
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.
154 154  )))
155 155  
156 156  (% class="box" %)
... ... @@ -182,13 +182,8 @@
182 182  )))
183 183  
184 184  (((
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.**//
187 -
188 -
189 -(% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.**
190 -
191 -//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.
192 192  )))
193 193  
194 194  (% class="box" %)
... ... @@ -231,7 +231,7 @@
231 231  )))
232 232  
233 233  (((
234 -//**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.
235 235  )))
236 236  
237 237  (% class="box" %)
... ... @@ -286,24 +286,21 @@
286 286  )))
287 287  
288 288  (((
289 -**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.
290 290  )))
291 291  
292 292  (((
293 -//After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//
294 -
295 -
273 +After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.
296 296  )))
297 297  
298 -== **2.8 Debug Connection** ==
276 +== 2.8 Debug Connection ==
299 299  
300 -=== **2.8.1 Check pkt-fwd running Log** ===
278 +=== 2.8.1 Check pkt-fwd running Log ===
301 301  
280 +This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.
302 302  
303 -//This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
304 -
305 305  (((
306 -//Below logs shows the gateway receive two LoRaWAN packets.//
283 +Below logs shows the gateway receive two LoRaWAN packets.
307 307  )))
308 308  
309 309  (% class="box" %)
... ... @@ -327,21 +327,18 @@
327 327  Sun Nov 14 14:28:19 2021 daemon.info lora_pkt_fwd[3145]: REPORT~~ ~#~## [DOWNSTREAM] ~#~##
328 328  )))
329 329  
307 +=== 2.8.2 Check gateway-rs Log ===
330 330  
331 -=== **2.8.2 Check gateway-rs Log** ===
309 +SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.
332 332  
311 +[[image:image-20220524170627-8.png]]
333 333  
334 -//SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
313 +Helium-gatewayrs log
335 335  
336 -[[image:image-20220531175809-7.png]]
337 -
338 -
339 339  **Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.
340 340  
317 +=== 2.8.3 View the public key address and animal name ===
341 341  
342 -=== **2.8.3 View the public key address and animal name** ===
343 -
344 -
345 345  (% class="box" %)
346 346  (((
347 347  (((
... ... @@ -358,137 +358,114 @@
358 358  )))
359 359  )))
360 360  
361 -[[image:image-20220531175844-8.png]]
335 +[[image:image-20220524170640-9.png]]
362 362  
363 363  Hostpot key and animal name
364 364  
339 +=== 2.8.4 Backup/Restor gateway-rs key ===
365 365  
366 -=== **2.8.4 Backup/Restor gateway-rs key** ===
367 -
368 368  (((
369 -//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.
370 370  )))
371 371  
372 -[[image:image-20220531175919-9.png]]
345 +[[image:image-20220524170701-10.png]]
373 373  
347 +Backup and restore key
374 374  
349 +== 2.9 Forward the data to the other server ==
375 375  
376 -== **2.9 Forward the data to the other server** ==
351 +=== 2.9.1 Introduction ===
377 377  
378 -=== **2.9.1 Introduction** ===
379 -
380 -
381 381  (((
382 -//The Dragino gateway has supports the double server settings.//
354 +The Dragino gateway has supports the double server settings.
383 383  )))
384 384  
385 385  (((
386 -//Users can back to the page of Semtech UDP to configure other server settings.//
387 -
388 -
358 +Users can back to the page of Semtech UDP to configure other server settings.
389 389  )))
390 390  
391 -=== **2.9.2 Example** ===
361 +=== 2.9.2 Example ===
392 392  
363 +The following takes The Things Network as another LoRaWAN server as an example,
393 393  
394 -//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 ====
395 395  
367 +[[image:image-20220524170722-11.png]]
396 396  
397 -==== **2.9.2.1 Step 1: Back to Semtech UDP page** ====
398 -
399 -
400 -[[image:image-20220531180002-10.png]]
401 -
402 402  Back to Semtech UDP page
403 403  
371 +==== 2.9.2.2 Step 2: Configure the double server forwarding ====
404 404  
405 -==== **2.9.2.2 Step 2: Configure the double server forwarding** ====
373 +[[image:image-20220524170800-12.png]]
406 406  
375 +Configure the double server
407 407  
408 -[[image:image-20220531180048-11.png]]
377 +The user can configure the secondary server and then click the button of Save&Apply.
409 409  
379 +== 2.10 Connect Full Hotspot to Helium ==
410 410  
411 -//The user can configure the secondary server and then click the button of **Save&Apply**.//
381 += 3. Use Dragino Sensors with Helium =
412 412  
383 +== 3.1 How to add up user's end-node with Helium console ==
413 413  
414 -== **2.10 Connect Full Hotspot to Helium** ==
385 +=== 3.1.1 Step 1:Login the Helium console ===
415 415  
416 -= **3. Use Dragino Sensors with Helium** =
387 +User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]
417 417  
389 +[[image:image-20220524170958-13.png]]
418 418  
419 -== **3.1 How to add up user's end-node with Helium console** ==
420 -
421 -
422 -=== **3.1.1 Step 1: Login the Helium console** ===
423 -
424 -
425 -//User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]//
426 -
427 -[[image:image-20220531180150-12.png]]
428 -
429 429  login Helium console
430 430  
393 +=== 3.1.2 Step 2:Add up your end-node's key ===
431 431  
432 -=== **3.1.2 Step 2: Add up your end-node's key** ===
395 +User add up end-node's key from console ~-~->dervice
433 433  
397 +[[image:image-20220524171027-14.png]]
434 434  
435 -//User add up end-node's key from console ~-~->dervice//
436 -
437 -[[image:image-20220531180224-13.png]]
438 -
439 439  To add a device
440 440  
401 +=== 3.1.3 Step 3:Activate the end-node ===
441 441  
442 -=== **3.1.3 Step 3:Activate the end-node** ===
443 -
444 -
445 445  (((
446 -//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**
447 447  )))
448 448  
449 -[[image:image-20220531105239-2.png]]
407 +[[image:image-20220524171045-15.png]]
450 450  
451 451  end-node traffic.
452 452  
411 +== 3.2 How to use decoder ==
453 453  
454 -== **3.2 How to use decoder** ==
413 +=== 3.2.1 Step 1:Users can create decoders on functions ===
455 455  
456 -=== **3.2.1 Step 1:Users can create decoders on functions** ===
415 +[[image:image-20220524171109-16.png]]
457 457  
458 -
459 -[[image:image-20220531105325-3.png]]
460 -
461 461  Decoder.
462 462  
419 +=== 3.2.2 Step 2:Add a decoder in functions and apply it to the specified label ===
463 463  
464 -=== **3.2.2 Step 2:Add a decoder in functions and apply it to the specified label** ===
421 +[[image:image-20220524171130-17.png]]
465 465  
423 +[[image:image-20220524171156-18.png]]
466 466  
467 -[[image:image-20220526095629-6.png]]
425 +[[image:image-20220524171317-20.png]]
468 468  
427 +Decoder.
469 469  
470 -[[image:image-20220526095553-5.png]]
429 +Add decoder complete.
471 471  
431 +== 3.3 How to send a downlink to end device from Helium ==
472 472  
473 -[[image:image-20220526100057-8.png||height="352" width="1133"]]
474 -
475 -
476 -**//Add decoder complete.//**
477 -
478 -
479 -== **3.3 How to send a downlink to end device from Helium** ==
480 -
481 -
482 482  (((
483 -//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:
484 484  )))
485 485  
486 486  (((
487 -//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]]
488 488  )))
489 489  
490 490  (((
491 -//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
492 492  )))
493 493  
494 494  (% class="box" %)
... ... @@ -500,167 +500,142 @@
500 500  
501 501  Downlink
502 502  
454 +== 3.4 How to add integration to different IoT Servers ==
503 503  
504 -== **3.4 How to add integration to different IoT Servers** ==
456 +=== 3.4.1 TagoIO ===
505 505  
506 -=== **3.4.1 TagoIO** ===
458 +The steps to add integration are very simple. Please see the following process.
507 507  
460 +[[image:image-20220524171412-22.png]]
508 508  
509 -**//The steps to add integration are very simple. Please see the following process.//**
462 +TagoIO.
510 510  
464 +Generate the authorization code and then copy it.
511 511  
512 -[[image:image-20220526102429-23.png||height="630" width="1198"]]
466 +[[image:image-20220524171432-23.png]]
513 513  
468 +TagoIO.
514 514  
470 +Apply Integration to Label.
515 515  
516 -**//Generate the authorization code and then copy it.//**
472 +[[image:image-20220524171451-24.png]]
517 517  
474 +TagoIO.
518 518  
519 -[[image:image-20220526100452-10.png||height="314" width="1188"]]
476 +[[image:image-20220524171510-25.png]]
520 520  
478 +TagoIO.
521 521  
480 +Click LoRaWAN Helium,select the device.
522 522  
523 -//**Apply Integration to Label.**//
482 +[[image:image-20220524171614-26.png]]
524 524  
484 +TagoIO.
525 525  
526 -[[image:image-20220526100802-13.png]]
486 +Fill in DEVEUI and create my device.
527 527  
488 +[[image:image-20220524171650-27.png]]
528 528  
529 -
530 -[[image:image-20220526100927-14.png]]
531 -
532 -
533 -
534 -**//Click LoRaWAN Helium,select the device.//**
535 -
536 -
537 -[[image:image-20220526101215-15.png||height="599" width="1117"]]
538 -
539 -
540 -
541 -**//Fill in DEVEUI and create my device.//**
542 -
543 -
544 -[[image:image-20220526101419-16.png]]
545 -
546 546  TagoIO.
547 547  
492 +=== 3.4.2 Cayenne ===
548 548  
549 -=== **3.4.2 Cayenne** ===
494 +The process of creating devices is similar to Tago.
550 550  
496 +[[image:image-20220524171744-29.png]]
551 551  
552 -//The process of creating devices is similar to Tago.//
553 -
554 -[[image:image-20220526101616-18.png||height="456" width="1097"]]
555 -
556 556  Cayenne.
557 557  
500 +[[image:image-20220524171826-30.png]]
558 558  
559 -[[image:image-20220526101547-17.png||height="656" width="1092"]]
560 -
561 561  Cayenne.
562 562  
504 +[[image:image-20220524171852-31.png]]
563 563  
564 -[[image:image-20220526101702-19.png||height="528" width="1109"]]
565 -
566 566  Cayenne.
567 567  
508 +[[image:image-20220524171915-32.png]]
568 568  
569 -[[image:image-20220526102303-22.png]]
570 -
571 571  Cayenne.
572 572  
512 +[[image:image-20220524171942-33.png]]
573 573  
574 -[[image:image-20220526102114-21.png]]
575 -
576 576  Cayenne.
577 577  
516 +[[image:image-20220524172009-34.png]]
578 578  
579 -[[image:image-20220526101940-20.png||height="543" width="1044"]]
580 -
581 581  Cayenne.
582 582  
520 +== 3.5 Trouble Shooting ==
583 583  
584 -== **3.5 Trouble Shooting** ==
522 +=== 3.5.1 Trouble to Join Helium ===
585 585  
586 -=== **3.5.1 Trouble to Join Helium** ===
587 -
588 -
589 589  (((
590 -**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
591 -
592 -
525 +Assume the device is powered correctly. If you don't see data in Helium. The possibilities are:
593 593  )))
594 594  
595 595  (((
596 -//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)
597 597  )))
598 598  
599 599  (((
600 -//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)
601 601  )))
602 602  
603 603  (((
604 -//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)//
605 -
606 -
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)
607 607  )))
608 608  
609 -=== **3.5.2 Packet Loss for AU915 / US915 Band** ===
540 +=== 3.5.2 Packet Loss for AU915 / US915 Band ===
610 610  
611 -
612 612  (((
613 -//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.
614 614  )))
615 615  
616 616  (((
617 -//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.
618 618  )))
619 619  
620 620  (((
621 -**Solution:**
622 -
623 -
551 +Solution:
624 624  )))
625 625  
626 626  (((
627 -//(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.
628 628  )))
629 629  
630 630  * (((
631 -//AT Command: AT+CHE//
559 +AT Command: AT+CHE
632 632  )))
633 633  
634 634  * (((
635 -//Example:AT+CHE=1 ~/~/set channel mode to 1//
563 +Example:AT+CHE=1 ~/~/set channel mode to 1
636 636  )))
637 637  
638 638  * (((
639 -//Downlink Command: 0x24//
567 +Downlink Command: 0x24
640 640  )))
641 641  
642 642  (((
643 -//Format: Command Code (0x24) followed by 1 bytes channel value.//
571 +Format: Command Code (0x24) followed by 1 bytes channel value.
644 644  )))
645 645  
646 646  (((
647 -//If the downlink payload=2401, it means set channel mode to 1, while type code is 24.//
575 +If the downlink payload=2401, it means set channel mode to 1, while type code is 24.
648 648  )))
649 649  
650 650  * (((
651 -//Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1//
579 +Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1
652 652  )))
653 653  
654 654  * (((
655 -//Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5//
656 -
657 -
583 +Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5
658 658  )))
659 659  
660 660  (((
661 -//(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.
662 662  )))
663 663  
664 664  (((
665 -//The latest firmware for end node will have this bug fixed.//
591 +The latest firmware for end node will have this bug fixed.
666 666  )))
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