Changes for page Notes for Helium
Last modified by Edwin Chen on 2024/03/25 08:22
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Kilight - Content
-
... ... @@ -1,4 +1,4 @@ 1 -**~ Table ofContents:**1 +**~ Contents:** 2 2 3 3 {{toc/}} 4 4 ... ... @@ -5,11 +5,10 @@ 5 5 6 6 7 7 8 -= **1. 8 += **1. Use Dragino Gateways/Hotspots with Helium** = 9 9 10 -== **1.1 10 +== **1.1 Support Models** == 11 11 12 - 13 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 14 15 15 ((( ... ... @@ -28,105 +28,97 @@ 28 28 29 29 **Frequencies on the Helium Network** 30 30 31 -* //The frequencies currently available are CN470/EU868/US915/AU915//30 +* The frequencies currently available are CN470/EU868/US915/AU915 32 32 33 - 34 34 (% style="color:red" %)**Note: more information refer to this link [[Helium Frequency plan>>url:https://docs.helium.com/lorawan-on-helium/frequency-plans/]]** 35 35 36 36 35 += 2. Connect Data-Only Hotspot to Helium = 37 37 38 -= **2.Connect Data-Only Hotspotto Helium**=37 +== 2.1 Prerequisites == 39 39 40 - ==**2.1Prerequisites** ==39 +* Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]] 41 41 41 +== 2.2 Step 1: Configure Frequency Band == 42 42 43 - *//FirmwareRequirement:> [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//43 +Each country has a requirement for frequency region. Choose the right one for your area. 44 44 45 - 46 - 47 -== **2.2 Step 1: Configure Frequency Band** == 48 - 49 - 50 -//Each country has a requirement for frequency region. Choose the right one for your area.// 51 - 52 52 [[image:image-20220531175337-1.png]] 53 53 47 +Select fre 54 54 55 55 56 -== **2.3**==50 +== 2.3 Step 2: Download the Helium-gateway-rs == 57 57 52 +Click Download Helium Server and the gateway will download the Helium-gateway-rs 58 58 59 - //Click Download HeliumServerand theatewaywilldownloadthe Helium-gateway-rs//54 +[[image:image-20220615150600-1.png||height="667" width="1247"]] 60 60 61 - [[image:image-20220615150600-1.png||height="559"width="1045"]]56 +Start download the Helium-gatewayrs 62 62 63 63 64 - //**Start download to Helium-gateway-rs**//59 +[[image:image-20220615150627-2.png||height="712" width="1244"]] 65 65 66 - [[image:image-20220615150627-2.png||height="598"width="1044"]]61 +Helium-gatewayrs download success 67 67 68 -//**Helium-gatewayrs download success**// 69 69 64 +If download fails, click and download again 70 70 71 - //**If download fails, clickanddownload again**//66 +[[image:image-20220615150717-3.png||height="722" width="1239"]] 72 72 73 - [[image:image-20220615150717-3.png||height="605"width="1039"]]68 +Helium-gatewayrs download fail 74 74 75 75 76 -== **2.4**==71 +== 2.4 Step 3: Install the Helium-gateway-rs == 77 77 73 +Click **Install Helium Server** to install gateway-rs. 78 78 79 - //Click **Install HeliumServer** toinstallgateway-rs.//75 +[[image:image-20220615150734-4.png||height="742" width="1241"]] 80 80 81 -[[image:image-20220615150734-4.png||height="619" width="1035"]] 82 - 83 83 Install the Helium gateway-rs 84 84 79 +**Note**: User will see the echo characters of Helium gateway-rs have been installed successfully. 85 85 86 -(% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.** 87 87 82 +== 2.5 Step 4: Save&start the Helium Server == 88 88 89 89 90 - ==**2.5Step4:Save&startthe HeliumServer**==85 +By default, Region is US915, After configuring the Configure Frequency Band, click Save&Apply on the Helium IoT screen to modify the Region. 91 91 87 +[[image:image-20220615150903-5.png||height="710" width="1236"]] 92 92 93 - //By default, Region is US915, After configuring theConfigure Frequency Band, clickIoTscreentomodifytheRegion.//89 +Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status. 94 94 95 -[[image:image-20220615150 903-5.png||height="592" width="1031"]]91 +[[image:image-20220615151057-6.png||height="697" width="1233"]] 96 96 93 +Start Helium-gateway-rs 97 97 98 -//Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.// 99 99 100 - [[image:image-20220615151057-6.png||height="580"width="1026"]]96 +== 2.6 Step 5: Check Gateway Connection before onboarding == 101 101 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. 102 102 103 - 104 -== **2.6 Step 5: Check Gateway Connection before onboarding** == 105 - 106 - 107 -//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.// 108 - 109 109 ((( 110 - //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. 111 111 ))) 112 112 113 113 [[image:image-20220526094537-1.png||height="395" width="1323"]] 114 114 106 +Check if the packet is transferred via LPS8 115 115 116 - (% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**108 +**Note:** The hotspot is not valid for search in Helium Console before onboarding. 117 117 118 118 119 119 == 2.7 Step 6: Onboarding Data-Only Hotspot == 120 120 121 -(% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlinktowork.otherwise,thedownlink messageforLoRa won'twork.**113 +(% style="color:red" %)**Note: Onboarding a Data-Only hotspot is not necessary, and it will gain very, very small awards on HNT by data-transfer .** 122 122 123 - //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 +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. 124 124 125 - //Below are the steps we do as per above link here.//117 +Below are the steps we do as per above link here. 126 126 127 - 128 128 ((( 129 - //**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. 130 130 ))) 131 131 132 132 (% class="box" %) ... ... @@ -154,12 +154,12 @@ 154 154 ))) 155 155 156 156 ((( 157 - (% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.**148 +**Note**: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance. 158 158 ))) 159 159 160 160 161 161 ((( 162 - //**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. 163 163 ))) 164 164 165 165 (% class="box" %) ... ... @@ -191,13 +191,8 @@ 191 191 ))) 192 192 193 193 ((( 194 -//We got the txn info from this step.// 195 -\\//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**// 196 - 197 - 198 -(% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.** 199 - 200 -//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. 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. 201 201 ))) 202 202 203 203 (% class="box" %) ... ... @@ -240,7 +240,7 @@ 240 240 ))) 241 241 242 242 ((( 243 - //**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//229 +4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2. 244 244 ))) 245 245 246 246 (% class="box" %) ... ... @@ -295,24 +295,23 @@ 295 295 ))) 296 296 297 297 ((( 298 - **Note: The add hotspot and assert location step might need some time to be effect.**284 +Note: The add hotspot and assert location step might need some time to be effect. 299 299 ))) 300 300 301 301 ((( 302 - //After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//288 +After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain. 303 303 304 304 305 305 ))) 306 306 307 -== **2.8 Debug Connection**==293 +== 2.8 Debug Connection == 308 308 309 -=== **2.8.1 Check pkt-fwd running Log**===295 +=== 2.8.1 Check pkt-fwd running Log === 310 310 297 +This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors. 311 311 312 -//This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.// 313 - 314 314 ((( 315 - //Below logs shows the gateway receive two LoRaWAN packets.//300 +Below logs shows the gateway receive two LoRaWAN packets. 316 316 ))) 317 317 318 318 (% class="box" %) ... ... @@ -337,20 +337,19 @@ 337 337 ))) 338 338 339 339 340 -=== **2.8.2 Check gateway-rs Log**===325 +=== 2.8.2 Check gateway-rs Log === 341 341 327 +SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log. 342 342 343 -//SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.// 344 - 345 345 [[image:image-20220531175809-7.png]] 346 346 331 +Helium-gatewayrs log 347 347 348 348 **Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system. 349 349 350 350 351 -=== **2.8.3 View the public key address and animal name**===336 +=== 2.8.3 View the public key address and animal name === 352 352 353 - 354 354 (% class="box" %) 355 355 ((( 356 356 ((( ... ... @@ -372,87 +372,80 @@ 372 372 Hostpot key and animal name 373 373 374 374 375 -=== **2.8.4 Backup/Restor gateway-rs key**===359 +=== 2.8.4 Backup/Restor gateway-rs key === 376 376 377 377 ((( 378 - //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.//362 +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. 379 379 ))) 380 380 381 381 [[image:image-20220531175919-9.png]] 382 382 367 +Backup and restore key 383 383 384 384 385 -== **2.9 Forward the data to the other server**==370 +== 2.9 Forward the data to the other server == 386 386 387 -=== **2.9.1 Introduction**===372 +=== 2.9.1 Introduction === 388 388 389 - 390 390 ((( 391 - //The Dragino gateway has supports the double server settings.//375 +The Dragino gateway has supports the double server settings. 392 392 ))) 393 393 394 394 ((( 395 - //Users can back to the page of Semtech UDP to configure other server settings.//379 +Users can back to the page of Semtech UDP to configure other server settings. 396 396 397 397 398 398 ))) 399 399 400 -=== **2.9.2 Example**===384 +=== 2.9.2 Example === 401 401 386 +The following takes The Things Network as another LoRaWAN server as an example. 402 402 403 -//The following takes The Things Network as another LoRaWAN server as an example.// 404 404 389 +==== 2.9.2.1 Step 1: Back to Semtech UDP page ==== 405 405 406 -==== **2.9.2.1 Step 1: Back to Semtech UDP page** ==== 407 - 408 - 409 409 [[image:image-20220531180002-10.png]] 410 410 411 411 Back to Semtech UDP page 412 412 413 413 414 -==== **2.9.2.2 Step 2: Configure the double server forwarding**====396 +==== 2.9.2.2 Step 2: Configure the double server forwarding ==== 415 415 416 - 417 417 [[image:image-20220531180048-11.png]] 418 418 400 +Configure the double server 419 419 420 - //The user can configure the secondary server and then click the button of**Save&Apply**.//402 +The user can configure the secondary server and then click the button of Save&Apply. 421 421 422 422 423 -== **2.10 Connect Full Hotspot to Helium**==405 +== 2.10 Connect Full Hotspot to Helium == 424 424 425 -= **3. Use Dragino Sensors with Helium**=407 += 3. Use Dragino Sensors with Helium = 426 426 409 +== 3.1 How to add up user's end-node with Helium console == 427 427 428 -== **3.1Howto add upuser'send-node with Helium console**==411 +=== 3.1.1 Step 1: Login the Helium console === 429 429 413 +User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]] 430 430 431 -=== **3.1.1 Step 1: Login the Helium console** === 432 - 433 - 434 -//User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]// 435 - 436 436 [[image:image-20220531180150-12.png]] 437 437 438 438 login Helium console 439 439 440 440 441 -=== **3.1.2 Step 2: Add up your end-node's key**===420 +=== 3.1.2 Step 2: Add up your end-node's key === 442 442 422 +User add up end-node's key from console ~-~->dervice 443 443 444 -//User add up end-node's key from console ~-~->dervice// 445 - 446 446 [[image:image-20220531180224-13.png]] 447 447 448 448 To add a device 449 449 450 450 451 -=== **3.1.3 Step 3:Activate the end-node**===429 +=== 3.1.3 Step 3:Activate the end-node === 452 452 453 - 454 454 ((( 455 - //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**//432 +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** 456 456 ))) 457 457 458 458 [[image:image-20220531105239-2.png]] ... ... @@ -460,19 +460,17 @@ 460 460 end-node traffic. 461 461 462 462 463 -== **3.2 How to use decoder**==440 +== 3.2 How to use decoder == 464 464 465 -=== **3.2.1 Step 1:Users can create decoders on functions**===442 +=== 3.2.1 Step 1:Users can create decoders on functions === 466 466 467 - 468 468 [[image:image-20220531105325-3.png]] 469 469 470 470 Decoder. 471 471 472 472 473 -=== **3.2.2 Step 2:Add a decoder in functions and apply it to the specified label**===449 +=== 3.2.2 Step 2:Add a decoder in functions and apply it to the specified label === 474 474 475 - 476 476 [[image:image-20220526095629-6.png]] 477 477 478 478 ... ... @@ -481,28 +481,23 @@ 481 481 482 482 [[image:image-20220526100057-8.png||height="352" width="1133"]] 483 483 459 +Decoder. 484 484 485 - **//Add decoder complete.//**461 +Add decoder complete. 486 486 487 -=== **3.2.3 Where is the decoder?** === 488 488 489 - [[console-decoders/Draginoatmaster·helium/console-decoders· GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]464 +== 3.3 How to send a downlink to end device from Helium == 490 490 491 -[[image:image-20220617140118-1.png||height="550" width="883"]] 492 - 493 -== **3.3 How to send a downlink to end device from Helium** == 494 - 495 - 496 496 ((( 497 - //The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example~://467 +The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example: 498 498 ))) 499 499 500 500 ((( 501 - //The Downlink command comes from this link:[[End Device Downlink Command>>End Device AT Commands and Downlink Command]]//471 +The Downlink command comes from this link:[[End Device Downlink Command>>End Device AT Commands and Downlink Command]] 502 502 ))) 503 503 504 504 ((( 505 - //Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds//475 +Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds 506 506 ))) 507 507 508 508 (% class="box" %) ... ... @@ -515,56 +515,55 @@ 515 515 Downlink 516 516 517 517 518 -== **3.4 How to add integration to different IoT Servers**==488 +== 3.4 How to add integration to different IoT Servers == 519 519 520 -=== **3.4.1 TagoIO**===490 +=== 3.4.1 TagoIO === 521 521 492 +The steps to add integration are very simple. Please see the following process. 522 522 523 -**//The steps to add integration are very simple. Please see the following process.//** 524 - 525 - 526 526 [[image:image-20220526102429-23.png||height="630" width="1198"]] 527 527 496 +TagoIO. 528 528 529 529 530 - **//Generate the authorization code and then copy it.//**499 +Generate the authorization code and then copy it. 531 531 532 - 533 533 [[image:image-20220526100452-10.png||height="314" width="1188"]] 534 534 503 +TagoIO. 535 535 536 536 537 - //**Apply Integration to Label.**//506 +Apply Integration to Label. 538 538 539 - 540 540 [[image:image-20220526100802-13.png]] 541 541 542 542 511 +TagoIO. 543 543 513 + 544 544 [[image:image-20220526100927-14.png]] 545 545 516 +TagoIO. 546 546 547 547 548 - **//Click LoRaWAN Helium,select the device.//**519 +Click LoRaWAN Helium,select the device. 549 549 550 - 551 551 [[image:image-20220526101215-15.png||height="599" width="1117"]] 552 552 523 +TagoIO. 553 553 554 554 555 - **//Fill in DEVEUI and create my device.//**526 +Fill in DEVEUI and create my device. 556 556 557 - 558 558 [[image:image-20220526101419-16.png]] 559 559 560 560 TagoIO. 561 561 562 562 563 -=== **3.4.2 Cayenne**===533 +=== 3.4.2 Cayenne === 564 564 535 +The process of creating devices is similar to Tago. 565 565 566 -//The process of creating devices is similar to Tago.// 567 - 568 568 [[image:image-20220526101616-18.png||height="456" width="1097"]] 569 569 570 570 Cayenne. ... ... @@ -595,83 +595,78 @@ 595 595 Cayenne. 596 596 597 597 598 -== **3.5 Trouble Shooting**==567 +== 3.5 Trouble Shooting == 599 599 600 -=== **3.5.1 Trouble to Join Helium**===569 +=== 3.5.1 Trouble to Join Helium === 601 601 602 - 603 603 ((( 604 -**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://** 605 - 606 - 572 +Assume the device is powered correctly. If you don't see data in Helium. The possibilities are: 607 607 ))) 608 608 609 609 ((( 610 - //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)//576 +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) 611 611 ))) 612 612 613 613 ((( 614 - //2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)//580 +2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches) 615 615 ))) 616 616 617 617 ((( 618 - //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)//584 +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) 619 619 620 620 621 621 ))) 622 622 623 -=== **3.5.2 Packet Loss for AU915 / US915 Band**===589 +=== 3.5.2 Packet Loss for AU915 / US915 Band === 624 624 625 - 626 626 ((( 627 - //The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.//592 +The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different. 628 628 ))) 629 629 630 630 ((( 631 - //The reason for this problem is that the node does not lock the channel after joining the network.//596 +The reason for this problem is that the node does not lock the channel after joining the network. 632 632 ))) 633 633 634 634 ((( 635 -**Solution:** 636 - 637 - 600 +Solution: 638 638 ))) 639 639 640 640 ((( 641 - //(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.//604 +(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. 642 642 ))) 643 643 644 644 * ((( 645 - //AT Command: AT+CHE//608 +AT Command: AT+CHE 646 646 ))) 647 647 648 648 * ((( 649 - //Example:**AT+CHE=2**~/~/set channel mode to 1//612 +Example:AT+CHE=1 ~/~/set channel mode to 1 650 650 ))) 651 651 652 652 * ((( 653 - //Downlink Command: 0x24//616 +Downlink Command: 0x24 654 654 ))) 655 655 656 656 ((( 657 - //Format: Command Code (0x24) followed by 1 bytes channel value.//620 +Format: Command Code (0x24) followed by 1 bytes channel value. 658 658 ))) 659 659 660 660 ((( 661 - //If the downlink payload=0x2402, it means set channel mode touse sub-band 2, while type code is 24.//624 +If the downlink payload=2401, it means set channel mode to 1, while type code is 24. 662 662 ))) 663 663 664 664 * ((( 665 -//Example 1: Downlink Payload: **0x2402** ~/~/ set channel mode to 2// 628 +Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1 629 +))) 666 666 667 - 668 - 631 +* ((( 632 +Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5 669 669 ))) 670 670 671 671 ((( 672 - //(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.//636 +(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. 673 673 ))) 674 674 675 675 ((( 676 - //The latest firmware for end node will have this bug fixed.//640 +The latest firmware for end node will have this bug fixed. 677 677 )))
- image-20220617140118-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -55.5 KB - Content