Changes for page Notes for Helium

Last modified by Edwin Chen on 2024/03/25 08:22
<
From version < 57.3 >
edited by Xiaoling
on 2022/05/26 10:31
To version < 87.1 >
edited by Edwin Chen
on 2022/06/28 12:08
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -3,14 +3,16 @@
3 3  {{toc/}}
4 4  
5 5  
6 -= 1. Use Dragino Gateways/Hotspots with Helium =
7 7  
8 -== 1.1 Support Models ==
9 9  
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.
8 += **1. Use Dragino Gateways/Hotspots with Helium** =
11 11  
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 +
12 12  (((
13 -Dragino has different gateway models that support different types.
15 +//Dragino has different gateway models that support different types.//
14 14  )))
15 15  
16 16  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -20,86 +20,89 @@
20 20  [[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]],
21 21  
22 22  [[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]]
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/]]
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]]
25 25  
26 26  **Frequencies on the Helium Network**
27 27  
28 -* The frequencies currently available are CN470/EU868/US915/AU915
30 +* //The frequencies currently available are CN470/EU868/US915/AU915//
29 29  
30 -**Note**: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]
32 +(% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]**
31 31  
32 32  
33 -= 2. Connect Data-Only Hotspot to Helium =
35 += **2. Connect Data-Only Hotspot to Helium** =
34 34  
35 -== 2.1 Prerequisites ==
37 +== **2.1 Prerequisites** ==
36 36  
37 -* Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
38 38  
40 +* //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//
39 39  
40 -== 2.2 Step 1:Configure Frequency Band ==
42 +== **2.2 Step 1: Configure Frequency Band** ==
41 41  
42 -Each country has a requirement for frequency region. Choose the right one for your area.
43 43  
44 -[[image:image-20220524170317-1.png]]
45 +//Each country has a requirement for frequency region. Choose the right one for your area.//
45 45  
46 -Select fre
47 +[[image:image-20220531175337-1.png]]
47 47  
48 48  
49 -== 2.3 Step 2: Download the Helium-gateway-rs ==
50 +== **2.3 Step 2: Download the Helium-gateway-rs** ==
50 50  
51 -Click Download Helium Server and the gateway will download the Helium-gateway-rs
52 52  
53 -[[image:image-20220524170337-2.png]]
53 +//Click Download Helium Server and the gateway will download the Helium-gateway-rs//
54 54  
55 -Start download the Helium-gatewayrs
55 +[[image:image-20220615150600-1.png||height="559" width="1045"]]
56 56  
57 57  
58 -[[image:image-20220524170359-3.png]]
58 +//**Start download to Helium-gateway-rs**//
59 59  
60 -Helium-gatewayrs download success
60 +[[image:image-20220615150627-2.png||height="598" width="1044"]]
61 61  
62 +//**Helium-gatewayrs download success**//
62 62  
63 -If download fails, click and download again
64 64  
65 -[[image:image-20220524170437-4.png]]
65 +//**If download fails, click and download again**//
66 66  
67 -Helium-gatewayrs download fail
67 +[[image:image-20220615150717-3.png||height="605" width="1039"]]
68 68  
69 69  
70 -== 2.4 Step 3: Install the Helium-gateway-rs ==
70 +== **2.4 Step 3: Install the Helium-gateway-rs** ==
71 71  
72 -Click **Install Helium Server** to install gateway-rs.
73 73  
74 -[[image:image-20220524170458-5.png]]
73 +//Click **Install Helium Server** to install gateway-rs.//
75 75  
75 +[[image:image-20220615150734-4.png||height="619" width="1035"]]
76 +
76 76  Install the Helium gateway-rs
77 77  
78 -**Note**: User will see the echo characters of Helium gateway-rs have been installed successfully.
79 +(% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
79 79  
80 80  
81 -== 2.5 Step 4: Save&start the Helium Server ==
82 +== **2.5 Step 4: Save&start the Helium Server** ==
82 82  
83 -Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status.
84 84  
85 -[[image:image-20220524170524-6.png]]
85 +//By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region.//
86 86  
87 -Start Helium-gateway-rs
87 +[[image:image-20220615150903-5.png||height="592" width="1031"]]
88 88  
89 89  
90 -== 2.6 Step 5: Check Gateway Connection before onboarding ==
90 +//Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status.//
91 91  
92 -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.
92 +[[image:image-20220615151057-6.png||height="580" width="1026"]]
93 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 +
94 94  (((
95 -Check end device event from [[Helium Console>>url:https://staging-console.helium.wtf/]], We can see the LGT92 data arrived Helium via our hotspot.
101 +//Check end device event from [[Helium Console>>url:https://staging-console.helium.wtf/]], We can see the LGT92 data arrived Helium via our hotspot.//
96 96  )))
97 97  
98 98  [[image:image-20220526094537-1.png||height="395" width="1323"]]
99 99  
100 -Check if the packet is transferred via LPS8
101 101  
102 -**Note:** The hotspot is not valid for search in Helium Console before onboarding.
107 +(% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**
103 103  
104 104  
105 105  == 2.7 Step 6: Onboarding Data-Only Hotspot ==
... ... @@ -106,12 +106,13 @@
106 106  
107 107  (% 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 .**
108 108  
109 -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.
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.//
110 110  
111 -Below are the steps we do as per above link here.
116 +//Below are the steps we do as per above link here.//
112 112  
118 +
113 113  (((
114 -~1. Set up Helium-Wallet in my computer. [[https:~~/~~/docs.helium.com/wallets/cli-wallet>>url:https://docs.helium.com/wallets/cli-wallet]]. and funds this wallet. From this step, we got the wallet info as below.
120 +//**1. Set up Helium-Wallet in my computer. [[https:~~/~~/docs.helium.com/wallets/cli-wallet>>url:https://docs.helium.com/wallets/cli-wallet]]. and funds this wallet. From this step, we got the wallet info as below.**//
115 115  )))
116 116  
117 117  (% class="box" %)
... ... @@ -139,12 +139,12 @@
139 139  )))
140 140  
141 141  (((
142 -**Note**: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.
148 +(% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.**
143 143  )))
144 144  
145 145  
146 146  (((
147 -2. Get txn. In the data-only hotspot. run below command to add a hotspot, owner is the owner wallet of this hotspot, payer is the payer to pay transaction cost.
153 +//**2. Get txn. In the data-only hotspot. run below command to add a hotspot, owner is the owner wallet of this hotspot, payer is the payer to pay transaction cost.**//
148 148  )))
149 149  
150 150  (% class="box" %)
... ... @@ -176,8 +176,13 @@
176 176  )))
177 177  
178 178  (((
179 -We got the txn info from this step.
180 -\\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.
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.//
181 181  )))
182 182  
183 183  (% class="box" %)
... ... @@ -220,7 +220,7 @@
220 220  )))
221 221  
222 222  (((
223 -4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.
234 +//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//
224 224  )))
225 225  
226 226  (% class="box" %)
... ... @@ -275,23 +275,24 @@
275 275  )))
276 276  
277 277  (((
278 -Note: The add hotspot and assert location step might need some time to be effect.
289 +**Note: The add hotspot and assert location step might need some time to be effect.**
279 279  )))
280 280  
281 281  (((
282 -After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.
293 +//After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//
283 283  
284 284  
285 285  )))
286 286  
287 -== 2.8 Debug Connection ==
298 +== **2.8 Debug Connection** ==
288 288  
289 -=== 2.8.1 Check pkt-fwd running Log ===
300 +=== **2.8.1 Check pkt-fwd running Log** ===
290 290  
291 -This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.
292 292  
303 +//This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
304 +
293 293  (((
294 -Below logs shows the gateway receive two LoRaWAN packets.
306 +//Below logs shows the gateway receive two LoRaWAN packets.//
295 295  )))
296 296  
297 297  (% class="box" %)
... ... @@ -316,19 +316,20 @@
316 316  )))
317 317  
318 318  
319 -=== 2.8.2 Check gateway-rs Log ===
331 +=== **2.8.2 Check gateway-rs Log** ===
320 320  
321 -SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.
322 322  
323 -[[image:image-20220524170627-8.png]]
334 +//SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
324 324  
325 -Helium-gatewayrs log
336 +[[image:image-20220531175809-7.png]]
326 326  
338 +
327 327  **Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.
328 328  
329 329  
330 -=== 2.8.3 View the public key address and animal name ===
342 +=== **2.8.3 View the public key address and animal name** ===
331 331  
344 +
332 332  (% class="box" %)
333 333  (((
334 334  (((
... ... @@ -345,101 +345,112 @@
345 345  )))
346 346  )))
347 347  
348 -[[image:image-20220524170640-9.png]]
361 +[[image:image-20220531175844-8.png]]
349 349  
350 350  Hostpot key and animal name
351 351  
352 352  
353 -=== 2.8.4 Backup/Restor gateway-rs key ===
366 +=== **2.8.4 Backup/Restor gateway-rs key** ===
354 354  
355 355  (((
356 -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.
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.//
357 357  )))
358 358  
359 -[[image:image-20220524170701-10.png]]
372 +[[image:image-20220531175919-9.png]]
360 360  
361 -Backup and restore key
362 362  
363 363  
364 -== 2.9 Forward the data to the other server ==
376 +== **2.9 Forward the data to the other server** ==
365 365  
366 -=== 2.9.1 Introduction ===
378 +=== **2.9.1 Introduction** ===
367 367  
380 +
368 368  (((
369 -The Dragino gateway has supports the double server settings.
382 +//The Dragino gateway has supports the double server settings.//
370 370  )))
371 371  
372 372  (((
373 -Users can back to the page of Semtech UDP to configure other server settings.
386 +//Users can back to the page of Semtech UDP to configure other server settings.//
374 374  
375 375  
376 376  )))
377 377  
378 -=== 2.9.2 Example ===
391 +=== **2.9.2 Example** ===
379 379  
380 -The following takes The Things Network as another LoRaWAN server as an example.
381 381  
394 +//The following takes The Things Network as another LoRaWAN server as an example.//
382 382  
383 -==== 2.9.2.1 Step 1: Back to Semtech UDP page ====
384 384  
385 -[[image:image-20220524170722-11.png]]
397 +==== **2.9.2.1 Step 1: Back to Semtech UDP page** ====
386 386  
399 +
400 +[[image:image-20220531180002-10.png]]
401 +
387 387  Back to Semtech UDP page
388 388  
389 389  
390 -==== 2.9.2.2 Step 2: Configure the double server forwarding ====
405 +==== **2.9.2.2 Step 2: Configure the double server forwarding** ====
391 391  
392 -[[image:image-20220524170800-12.png]]
393 393  
394 -Configure the double server
408 +[[image:image-20220531180048-11.png]]
395 395  
396 -The user can configure the secondary server and then click the button of Save&Apply.
397 397  
411 +//The user can configure the secondary server and then click the button of **Save&Apply**.//
398 398  
399 -== 2.10 Connect Full Hotspot to Helium ==
400 400  
401 -= 3. Use Dragino Sensors with Helium =
414 +== **2.10 Connect Full Hotspot to Helium** ==
402 402  
403 -== 3.1 How to add up user's end-node with Helium console ==
416 += **3. Use Dragino Sensors with Helium** =
404 404  
405 -=== 3.1.1 Step 1:Login the Helium console ===
406 406  
407 -User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]
419 +== **3.1 How to add up user's end-node with Helium console** ==
408 408  
409 -[[image:image-20220524170958-13.png]]
410 410  
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 +
411 411  login Helium console
412 412  
413 413  
414 -=== 3.1.2 Step 2:Add up your end-node's key ===
432 +=== **3.1.2 Step 2: Add up your end-node's key** ===
415 415  
416 -User add up end-node's key from console ~-~->dervice
417 417  
418 -[[image:image-20220524171027-14.png]]
435 +//User add up end-node's key from console ~-~->dervice//
419 419  
437 +[[image:image-20220531180224-13.png]]
438 +
420 420  To add a device
421 421  
422 422  
423 -=== 3.1.3 Step 3:Activate the end-node ===
442 +=== **3.1.3 Step 3:Activate the end-node** ===
424 424  
444 +
425 425  (((
426 -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**
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**//
427 427  )))
428 428  
429 -[[image:image-20220526095413-2.png||height="555" width="1352"]]
449 +[[image:image-20220531105239-2.png]]
430 430  
431 431  end-node traffic.
432 432  
433 -== 3.2 How to use decoder ==
434 434  
435 -=== 3.2.1 Step 1:Users can create decoders on functions ===
454 +== **3.2 How to use decoder** ==
436 436  
437 -[[image:image-20220524171109-16.png]]
456 +=== **3.2.1 Step 1:Users can create decoders on functions** ===
438 438  
458 +
459 +[[image:image-20220531105325-3.png]]
460 +
439 439  Decoder.
440 440  
441 -=== 3.2.2 Step 2:Add a decoder in functions and apply it to the specified label ===
442 442  
464 +=== **3.2.2 Step 2:Add a decoder in functions and apply it to the specified label** ===
465 +
466 +
443 443  [[image:image-20220526095629-6.png]]
444 444  
445 445  
... ... @@ -448,23 +448,28 @@
448 448  
449 449  [[image:image-20220526100057-8.png||height="352" width="1133"]]
450 450  
451 -Decoder.
452 452  
453 -Add decoder complete.
476 +**//Add decoder complete.//**
454 454  
478 +=== **3.2.3 Where is the decoder？** ===
455 455  
456 -== 3.3 How to send a downlink to end device from Helium ==
480 +[[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
457 457  
482 +[[image:image-20220617140118-1.png||height="550" width="883"]]
483 +
484 +== **3.3 How to send a downlink to end device from Helium** ==
485 +
486 +
458 458  (((
459 -The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example:
488 +//The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://
460 460  )))
461 461  
462 462  (((
463 -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]]
492 +//The Downlink command comes from this link：[[End Device Downlink Command>>End Device AT Commands and Downlink Command]]//
464 464  )))
465 465  
466 466  (((
467 -Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
496 +//Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds//
468 468  )))
469 469  
470 470  (% class="box" %)
... ... @@ -477,55 +477,56 @@
477 477  Downlink
478 478  
479 479  
480 -== 3.4 How to add integration to different IoT Servers ==
509 +== **3.4 How to add integration to different IoT Servers** ==
481 481  
482 -=== 3.4.1 TagoIO ===
511 +=== **3.4.1 TagoIO** ===
483 483  
484 -The steps to add integration are very simple. Please see the following process.
485 485  
514 +**//The steps to add integration are very simple. Please see the following process.//**
515 +
516 +
486 486  [[image:image-20220526102429-23.png||height="630" width="1198"]]
487 487  
488 -TagoIO.
489 489  
490 490  
491 -Generate the authorization code and then copy it.
521 +**//Generate the authorization code and then copy it.//**
492 492  
523 +
493 493  [[image:image-20220526100452-10.png||height="314" width="1188"]]
494 494  
495 -TagoIO.
496 496  
497 497  
498 -Apply Integration to Label.
528 +//**Apply Integration to Label.**//
499 499  
530 +
500 500  [[image:image-20220526100802-13.png]]
501 501  
502 502  
503 -TagoIO.
504 504  
505 -
506 506  [[image:image-20220526100927-14.png]]
507 507  
508 -TagoIO.
509 509  
510 510  
511 -Click LoRaWAN Helium,select the device.
539 +**//Click LoRaWAN Helium,select the device.//**
512 512  
541 +
513 513  [[image:image-20220526101215-15.png||height="599" width="1117"]]
514 514  
515 -TagoIO.
516 516  
517 517  
518 -Fill in DEVEUI and create my device.
546 +**//Fill in DEVEUI and create my device.//**
519 519  
548 +
520 520  [[image:image-20220526101419-16.png]]
521 521  
522 522  TagoIO.
523 523  
524 524  
525 -=== 3.4.2 Cayenne ===
554 +=== **3.4.2 Cayenne** ===
526 526  
527 -The process of creating devices is similar to Tago.
528 528  
557 +//The process of creating devices is similar to Tago.//
558 +
529 529  [[image:image-20220526101616-18.png||height="456" width="1097"]]
530 530  
531 531  Cayenne.
... ... @@ -556,78 +556,83 @@
556 556  Cayenne.
557 557  
558 558  
559 -== 3.5 Trouble Shooting ==
589 +== **3.5 Trouble Shooting** ==
560 560  
561 -=== 3.5.1 Trouble to Join Helium ===
591 +=== **3.5.1 Trouble to Join Helium** ===
562 562  
593 +
563 563  (((
564 -Assume the device is powered correctly. If you don't see data in Helium. The possibilities are:
595 +**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
596 +
597 +
565 565  )))
566 566  
567 567  (((
568 -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)
601 +//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)//
569 569  )))
570 570  
571 571  (((
572 -2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)
605 +//2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)//
573 573  )))
574 574  
575 575  (((
576 -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)
609 +//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)//
577 577  
578 578  
579 579  )))
580 580  
581 -=== 3.5.2 Packet Loss for AU915 / US915 Band ===
614 +=== **3.5.2 Packet Loss for AU915 / US915 Band** ===
582 582  
616 +
583 583  (((
584 -The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.
618 +//The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.//
585 585  )))
586 586  
587 587  (((
588 -The reason for this problem is that the node does not lock the channel after joining the network.
622 +//The reason for this problem is that the node does not lock the channel after joining the network.//
589 589  )))
590 590  
591 591  (((
592 -Solution:
626 +**Solution:**
627 +
628 +
593 593  )))
594 594  
595 595  (((
596 -(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.
632 +//(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.//
597 597  )))
598 598  
599 599  * (((
600 -AT Command: AT+CHE
636 +//AT Command: AT+CHE//
601 601  )))
602 602  
603 603  * (((
604 -Example:AT+CHE=1 ~/~/set channel mode to 1
640 +//Example:**AT+CHE=2** ~/~/set channel mode to 1//
605 605  )))
606 606  
607 607  * (((
608 -Downlink Command: 0x24
644 +//Downlink Command: 0x24//
609 609  )))
610 610  
611 611  (((
612 -Format: Command Code (0x24) followed by 1 bytes channel value.
648 +//Format: Command Code (0x24) followed by 1 bytes channel value.//
613 613  )))
614 614  
615 615  (((
616 -If the downlink payload=2401, it means set channel mode to 1, while type code is 24.
652 +//If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.//
617 617  )))
618 618  
619 619  * (((
620 -Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1
621 -)))
656 +//Example 1: Downlink Payload: **0x2402** ~/~/ set channel mode to 2//
622 622  
623 -* (((
624 -Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5
658 +
659 +
625 625  )))
626 626  
627 627  (((
628 -(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.
663 +//(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.//
629 629  )))
630 630  
631 631  (((
632 -The latest firmware for end node will have this bug fixed.
667 +//The latest firmware for end node will have this bug fixed.//
633 633  )))
image-20220531105203-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +105.7 KB
Content
image-20220531105239-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +88.0 KB
Content
image-20220531105325-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +65.2 KB
Content
image-20220531175337-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +47.8 KB
Content
image-20220531175421-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +60.6 KB
Content
image-20220531175500-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +69.3 KB
Content
image-20220531175530-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +58.5 KB
Content
image-20220531175610-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +68.4 KB
Content
image-20220531175650-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +70.4 KB
Content
image-20220531175809-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +32.6 KB
Content
image-20220531175844-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +67.5 KB
Content
image-20220531175919-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +67.2 KB
Content
image-20220531180002-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +66.7 KB
Content
image-20220531180048-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +62.3 KB
Content
image-20220531180150-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +20.2 KB
Content
image-20220531180224-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +65.0 KB
Content
image-20220615150600-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +37.6 KB
Content
image-20220615150627-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +42.6 KB
Content
image-20220615150717-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +44.6 KB
Content
image-20220615150734-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +42.8 KB
Content
image-20220615150903-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +63.1 KB
Content
image-20220615151057-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +64.0 KB
Content
image-20220617140118-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +55.5 KB
Content

Applications

Navigation

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