Changes for page Notes for Helium

Last modified by Edwin Chen on 2024/03/25 08:22
<
From version < 57.8 >
edited by Xiaoling
on 2022/05/26 10:44
To version < 83.1 >
edited by Kilight Cao
on 2022/06/15 15:37
>
Change comment: There is no comment for this version

Summary

Details

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

Applications

Navigation

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