Changes for page Notes for Helium

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