Changes for page Notes for Helium

Last modified by Edwin Chen on 2024/03/25 08:22

From version 1.16
edited by Xiaoling
on 2022/05/16 16:23
Change comment: There is no comment for this version
To version 1.17
edited by Xiaoling
on 2022/05/16 16:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -326,7 +326,9 @@
326 326  
327 327  === 2.8.4 Backup/Restor gateway-rs key ===
328 328  
329 +(((
329 329  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.
331 +)))
330 330  
331 331  [[image:https://wiki.dragino.com/images/thumb/e/ef/Backup_and_restore_key.png/600px-Backup_and_restore_key.png||height="343" width="600"]]
332 332  
... ... @@ -382,7 +382,9 @@
382 382  
383 383  === 3.1.3 Step 3:Activate the end-node ===
384 384  
387 +(((
385 385  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**
389 +)))
386 386  
387 387  [[image:https://wiki.dragino.com/images/thumb/4/45/End-node_traffic.png/600px-End-node_traffic.png||height="239" width="600"]]
388 388  
... ... @@ -412,22 +412,29 @@
412 412  
413 413  Add decoder complete.
414 414  
415 -
416 416  == 3.3 How to send a downlink to end device from Helium ==
417 417  
421 +(((
418 418  The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example:
423 +)))
419 419  
425 +(((
420 420  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]]
427 +)))
421 421  
429 +(((
422 422  Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
431 +)))
423 423  
433 +(% class="box" %)
434 +(((
424 424  01 00 00 3C ~-~-> AQAAPA==
436 +)))
425 425  
426 426  [[image:https://wiki.dragino.com/images/thumb/c/c5/Helium_downlink.png/600px-Helium_downlink.png||height="360" width="600"]]
427 427  
428 428  Downlink
429 429  
430 -
431 431  == 3.4 How to add integration to different IoT Servers ==
432 432  
433 433  === 3.4.1 TagoIO ===
... ... @@ -498,39 +498,72 @@
498 498  
499 499  === 3.5.1 Trouble to Join Helium ===
500 500  
512 +(((
501 501  Assume the device is powered correctly. If you don't see data in Helium. The possibilities are:
514 +)))
502 502  
516 +(((
503 503  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)
518 +)))
504 504  
520 +(((
505 505  2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)
522 +)))
506 506  
524 +(((
507 507  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)
526 +)))
508 508  
509 -
510 510  === 3.5.2 Packet Loss for AU915 / US915 Band ===
511 511  
530 +(((
512 512  The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.
532 +)))
513 513  
534 +(((
514 514  The reason for this problem is that the node does not lock the channel after joining the network.
536 +)))
515 515  
538 +(((
516 516  Solution:
540 +)))
517 517  
542 +(((
518 518  (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.
544 +)))
519 519  
520 -* AT Command: AT+CHE
546 +* (((
547 +AT Command: AT+CHE
548 +)))
521 521  
522 -* Example:AT+CHE=1 ~/~/set channel mode to 1
550 +* (((
551 +Example:AT+CHE=1 ~/~/set channel mode to 1
552 +)))
523 523  
524 -* Downlink Command: 0x24
554 +* (((
555 +Downlink Command: 0x24
556 +)))
525 525  
558 +(((
526 526  Format: Command Code (0x24) followed by 1 bytes channel value.
560 +)))
527 527  
562 +(((
528 528  If the downlink payload=2401, it means set channel mode to 1, while type code is 24.
564 +)))
529 529  
530 -* Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1
566 +* (((
567 +Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1
568 +)))
531 531  
532 -* Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5
570 +* (((
571 +Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5
572 +)))
533 533  
574 +(((
534 534  (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.
576 +)))
535 535  
578 +(((
536 536  The latest firmware for end node will have this bug fixed.
580 +)))