Changes for page Notes for Helium

Last modified by Edwin Chen on 2024/03/25 08:22
<
From version < 57.14 >
edited by Xiaoling
on 2022/05/31 10:43
To version < 88.17 >
edited by Xiaoling
on 2022/08/10 17:11
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
1 -**~ Contents:**
1 +**~ Table of Contents:**
2 2  
3 3  {{toc/}}
4 4  
... ... @@ -5,14 +5,15 @@
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.
13 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 14  (((
15 -Dragino has different gateway models that support different types.
16 +//Dragino has different gateway models that support different types.//
16 16  )))
17 17  
18 18  (% border="1" style="background-color:#ffffcc; width:510px" %)
... ... @@ -22,98 +22,116 @@
22 22  [[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]],
23 23  
24 24  [[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]]
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>>User Manual for All Gateway models.HP0D]]
26 +)))|(% 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.A0ConnectData-OnlyHotspottoHelium"]]
27 +|(% 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]]
27 27  
28 -**Frequencies on the Helium Network**
29 +(% style="color:blue" %)**Frequencies on the Helium Network**
29 29  
30 -* The frequencies currently available are CN470/EU868/US915/AU915
31 +* //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/]]
33 +(% 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 =
36 36  
37 -== 2.1 Prerequisites ==
37 += **2.  Connect Data-Only Hotspot to Helium** =
38 38  
39 -* Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
39 +== **2.1  Prerequisites** ==
40 40  
41 41  
42 -== 2.2 Step 1:Configure Frequency Band ==
42 +* //Firmware Requirement: > [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]//
43 43  
44 -Each country has a requirement for frequency region. Choose the right one for your area.
45 45  
46 -[[image:image-20220524170317-1.png]]
47 47  
48 -Select fre
49 49  
47 +== **2.2  Step 1: Configure Frequency Band** ==
50 50  
51 -== 2.3 Step 2: Download the Helium-gateway-rs ==
52 52  
53 -Click Download Helium Server and the gateway will download the Helium-gateway-rs
50 +//Each country has a requirement for frequency region. Choose the right one for your area.//
54 54  
55 -[[image:image-20220524170337-2.png]]
52 +[[image:image-20220531175337-1.png]]
56 56  
57 -Start download the Helium-gatewayrs
58 58  
59 59  
60 -[[image:image-20220524170359-3.png]]
56 +== **2.3  Step 2: Download the Helium-gateway-rs** ==
61 61  
62 -Helium-gatewayrs download success
63 63  
59 +//Click Download Helium Server and the gateway will download the Helium-gateway-rs//
64 64  
65 -If download fails, click and download again
61 +[[image:image-20220615150600-1.png||height="559" width="1045"]]
66 66  
67 -[[image:image-20220524170437-4.png]]
68 68  
69 -Helium-gatewayrs download fail
64 +//**Start download to Helium-gateway-rs**//
70 70  
66 +[[image:image-20220615150627-2.png||height="598" width="1044"]]
71 71  
72 -== 2.4 Step 3: Install the Helium-gateway-rs ==
68 +//**Helium-gatewayrs download success**//
73 73  
74 -Click **Install Helium Server** to install gateway-rs.
75 75  
76 -[[image:image-20220524170458-5.png]]
71 +//**If download fails, click and download again**//
77 77  
73 +[[image:image-20220615150717-3.png||height="605" width="1039"]]
74 +
75 +
76 +
77 +== **2.4  Step 3: Install the Helium-gateway-rs** ==
78 +
79 +
80 +//Click **Install Helium Server** to install gateway-rs.//
81 +
82 +[[image:image-20220615150734-4.png||height="619" width="1035"]]
83 +
78 78  Install the Helium gateway-rs
79 79  
80 -**Note**: User will see the echo characters of Helium gateway-rs have been installed successfully.
81 81  
87 +(% style="color:red" %)**Note: User will see the echo characters of Helium gateway-rs have been installed successfully.**
82 82  
83 -== 2.5 Step 4: Save&start the Helium Server ==
84 84  
85 -Click **Save&Apply** and gateway will start to connect the Helium. The UI shows the connect status.
86 86  
87 -[[image:image-20220524170524-6.png]]
91 +== **2.5  Step 4: Save&start the Helium Server** ==
88 88  
89 -Start Helium-gateway-rs
90 90  
94 +//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  
92 -== 2.6 Step 5: Check Gateway Connection before onboarding ==
93 93  
94 -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.
97 +[[image:image-20220615150903-5.png||height="592" width="1031"]]
95 95  
99 +
100 +
101 +//Click (% style="color:red" %)**Save&Apply**(%%) and gateway will start to connect the Helium. The UI shows the connect status.//
102 +
103 +[[image:image-20220615151057-6.png||height="580" width="1026"]]
104 +
105 +
106 +
107 +== **2.6  Step 5: Check Gateway Connection before onboarding** ==
108 +
109 +
110 +//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.//
111 +
96 96  (((
97 -Check end device event from [[Helium Console>>url:https://staging-console.helium.wtf/]], We can see the LGT92 data arrived Helium via our hotspot.
113 +//Check end device event from [[Helium Console>>url:https://staging-console.helium.wtf/]], We can see the LGT92 data arrived Helium via our hotspot.//
98 98  )))
99 99  
100 100  [[image:image-20220526094537-1.png||height="395" width="1323"]]
101 101  
102 -Check if the packet is transferred via LPS8
103 103  
104 -**Note:** The hotspot is not valid for search in Helium Console before onboarding.
119 +(% style="color:red" %)**Note: The hotspot is not valid for search in Helium Console before onboarding.**
105 105  
106 106  
107 -== 2.7 Step 6: Onboarding Data-Only Hotspot ==
108 108  
109 -(% 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 .**
123 +== **2.7  Step 6: Onboarding Data-Only Hotspot** ==
110 110  
111 -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.
112 112  
113 -Below are the steps we do as per above link here.
126 +(% style="color:red" %)**Note: Onboarding a Data-Only hotspot is necessary for downlink to work. otherwise, the downlink message for LoRa won't work .**
114 114  
128 +
129 +//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.//
130 +
131 +//Below are the steps we do as per above link here.//
132 +
133 +
115 115  (((
116 -~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.
135 +(% style="color:blue" %)//**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.**//
117 117  )))
118 118  
119 119  (% class="box" %)
... ... @@ -140,13 +140,15 @@
140 140  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
141 141  )))
142 142  
162 +
143 143  (((
144 -**Note**: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.
164 +(% style="color:red" %)**Note: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.**
145 145  )))
146 146  
147 147  
168 +
148 148  (((
149 -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.
170 +(% style="color:blue" %)//**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.**//
150 150  )))
151 151  
152 152  (% class="box" %)
... ... @@ -178,8 +178,17 @@
178 178  )))
179 179  
180 180  (((
181 -We got the txn info from this step.
182 -\\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.
202 +//We got the txn info from this step.//
203 +
204 +
205 +
206 +(% style="color:blue" %)//**3. Add Hotspot. In the computer with helium wallet. run below command, replace the txn with the txn you got in above step.**//
207 +
208 +
209 +(% style="color:red" %)**Note: below are two commands, the command without ~-~-commit is the preview mode.**
210 +
211 +
212 +//Check every detail in this mode and run the command with ~-~-commit to commit to the Helium Blockchain.//
183 183  )))
184 184  
185 185  (% class="box" %)
... ... @@ -222,7 +222,9 @@
222 222  )))
223 223  
224 224  (((
225 -4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.
255 +
256 +
257 +(% style="color:blue" %)//**4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.**//
226 226  )))
227 227  
228 228  (% class="box" %)
... ... @@ -276,24 +276,27 @@
276 276  +~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
277 277  )))
278 278  
311 +
279 279  (((
280 -Note: The add hotspot and assert location step might need some time to be effect.
313 +(% style="color:red" %)**Note: The add hotspot and assert location step might need some time to be effect.**
281 281  )))
282 282  
283 283  (((
284 -After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.
317 +//After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.//
285 285  
319 +
286 286  
287 287  )))
288 288  
289 -== 2.8 Debug Connection ==
323 +== **2.8  Debug Connection** ==
290 290  
291 -=== 2.8.1 Check pkt-fwd running Log ===
325 +=== **2.8.1  Check pkt-fwd running Log** ===
292 292  
293 -This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.
294 294  
328 +//This command can check if the LoRa Radio part runs correctly and if the gateway receives LoRa packets from LoRaWAN sensors.//
329 +
295 295  (((
296 -Below logs shows the gateway receive two LoRaWAN packets.
331 +//Below logs shows the gateway receive two LoRaWAN packets.//
297 297  )))
298 298  
299 299  (% class="box" %)
... ... @@ -318,19 +318,22 @@
318 318  )))
319 319  
320 320  
321 -=== 2.8.2 Check gateway-rs Log ===
322 322  
323 -SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.
357 +=== **2.8.2  Check gateway-rs Log** ===
324 324  
325 -[[image:image-20220524170627-8.png]]
326 326  
327 -Helium-gatewayrs log
360 +//SSH to gateway and run **logread | grep helium_gateway** to check Gateway-rs running log.//
328 328  
329 -**Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.
362 +[[image:image-20220531175809-7.png]]
330 330  
331 331  
332 -=== 2.8.3 View the public key address and animal name ===
365 +(% style="color:red" %)**Note**: **logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.**
333 333  
367 +
368 +
369 +=== **2.8.3  View the public key address and animal name** ===
370 +
371 +
334 334  (% class="box" %)
335 335  (((
336 336  (((
... ... @@ -347,101 +347,124 @@
347 347  )))
348 348  )))
349 349  
350 -[[image:image-20220524170640-9.png]]
388 +[[image:image-20220531175844-8.png]]
351 351  
352 352  Hostpot key and animal name
353 353  
354 354  
355 -=== 2.8.4 Backup/Restor gateway-rs key ===
356 356  
394 +=== **2.8.4  Backup/Restor gateway-rs key** ===
395 +
396 +
357 357  (((
358 -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.
398 +//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.//
359 359  )))
360 360  
361 -[[image:image-20220524170701-10.png]]
401 +[[image:image-20220531175919-9.png]]
362 362  
363 -Backup and restore key
364 364  
365 365  
366 -== 2.9 Forward the data to the other server ==
405 +== **2.9  Forward the data to the other server** ==
367 367  
368 -=== 2.9.1 Introduction ===
407 +=== **2.9.1  Introduction** ===
369 369  
409 +
370 370  (((
371 -The Dragino gateway has supports the double server settings.
411 +//The Dragino gateway has supports the double server settings.//
372 372  )))
373 373  
374 374  (((
375 -Users can back to the page of Semtech UDP to configure other server settings.
415 +//Users can back to the page of Semtech UDP to configure other server settings.//
376 376  
417 +
377 377  
378 378  )))
379 379  
380 -=== 2.9.2 Example ===
421 +=== **2.9.2  Example** ===
381 381  
382 -The following takes The Things Network as another LoRaWAN server as an example.
383 383  
424 +//The following takes The Things Network as another LoRaWAN server as an example.//
384 384  
385 -==== 2.9.2.1 Step 1: Back to Semtech UDP page ====
386 386  
387 -[[image:image-20220524170722-11.png]]
388 388  
428 +==== (% style="color:blue" %)**Step 1: Back to Semtech UDP page**(%%) ====
429 +
430 +
431 +[[image:image-20220531180002-10.png]]
432 +
389 389  Back to Semtech UDP page
390 390  
391 391  
392 -==== 2.9.2.2 Step 2: Configure the double server forwarding ====
393 393  
394 -[[image:image-20220524170800-12.png]]
437 +==== (% style="color:blue" %)**Step 2: Configure the double server forwarding**(%%) ====
395 395  
396 -Configure the double server
397 397  
398 -The user can configure the secondary server and then click the button of Save&Apply.
440 +[[image:image-20220531180048-11.png]]
399 399  
400 400  
401 -== 2.10 Connect Full Hotspot to Helium ==
443 +//The user can configure the secondary server and then click the button of **Save&Apply**.//
402 402  
403 -= 3. Use Dragino Sensors with Helium =
404 404  
405 -== 3.1 How to add up user's end-node with Helium console ==
406 406  
407 -=== 3.1.1 Step 1:Login the Helium console ===
447 +== **2.10  Connect Full Hotspot to Helium** ==
408 408  
409 -User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]
410 410  
411 -[[image:image-20220524170958-13.png]]
412 412  
451 += **3.  Use Dragino Sensors with Helium** =
452 +
453 +
454 +== **3.1  How to add up user's end-node with Helium console** ==
455 +
456 +
457 +=== **3.1.1  Step 1: Login the Helium console** ===
458 +
459 +
460 +//User can Login the [[Helium Console>>url:https://staging-console.helium.wtf/]]//
461 +
462 +[[image:image-20220531180150-12.png]]
463 +
413 413  login Helium console
414 414  
415 415  
416 -=== 3.1.2 Step 2:Add up your end-node's key ===
417 417  
418 -User add up end-node's key from console ~-~->dervice
468 +=== **3.1.2  Step 2: Add up your end-node's key** ===
419 419  
420 -[[image:image-20220524171027-14.png]]
421 421  
471 +//User add up end-node's key from console ~-~->dervice//
472 +
473 +[[image:image-20220531180224-13.png]]
474 +
422 422  To add a device
423 423  
424 424  
425 -=== 3.1.3 Step 3:Activate the end-node ===
426 426  
479 +=== **3.1.3  Step 3: Activate the end-node** ===
480 +
481 +
427 427  (((
428 -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**
483 +//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**//
429 429  )))
430 430  
431 -[[image:image-20220526095413-2.png||height="555" width="1352"]]
486 +[[image:image-20220531105239-2.png]]
432 432  
433 433  end-node traffic.
434 434  
435 -== 3.2 How to use decoder ==
436 436  
437 -=== 3.2.1 Step 1:Users can create decoders on functions ===
438 438  
439 -[[image:image-20220524171109-16.png]]
492 +== **3.2  How to use decoder** ==
440 440  
494 +=== **3.2.1  Step 1: Users can create decoders on functions** ===
495 +
496 +
497 +[[image:image-20220531105325-3.png]]
498 +
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  
502 +
503 +=== **3.2.2  Step 2: Add a decoder in functions and apply it to the specified label** ===
504 +
505 +
445 445  [[image:image-20220526095629-6.png]]
446 446  
447 447  
... ... @@ -450,28 +450,37 @@
450 450  
451 451  [[image:image-20220526100057-8.png||height="352" width="1133"]]
452 452  
453 -Decoder.
514 +**//Add decoder complete.//**
454 454  
455 -Add decoder complete.
456 456  
457 457  
458 -== 3.3 How to send a downlink to end device from Helium ==
518 +=== **3.2.3  Where is the decoder？** ===
459 459  
520 +
521 +[[console-decoders/Dragino at master · helium/console-decoders · GitHub>>url:https://github.com/helium/console-decoders/tree/master/Dragino]]
522 +
523 +[[image:image-20220617140118-1.png||height="550" width="883"]]
524 +
525 +
526 +
527 +== **3.3  How to send a downlink to end device from Helium** ==
528 +
529 +
460 460  (((
461 -The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example:
531 +//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]]
535 +//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
539 +//Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds//
470 470  )))
471 471  
472 472  (% class="box" %)
473 473  (((
474 -01 00 00 3C ~-~-> AQAAPA==
544 +**01 00 00 3C ~-~-> AQAAPA==**
475 475  )))
476 476  
477 477  [[image:image-20220524171341-21.png]]
... ... @@ -479,55 +479,58 @@
479 479  Downlink
480 480  
481 481  
482 -== 3.4 How to add integration to different IoT Servers ==
483 483  
484 -=== 3.4.1 TagoIO ===
553 +== **3.4  How to add integration to different IoT Servers** ==
485 485  
486 -The steps to add integration are very simple. Please see the following process.
555 +=== **3.4.1  TagoIO** ===
487 487  
557 +
558 +**//The steps to add integration are very simple. Please see the following process.//**
559 +
560 +
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.
565 +**//Generate the authorization code and then copy it.//**
494 494  
567 +
495 495  [[image:image-20220526100452-10.png||height="314" width="1188"]]
496 496  
497 -TagoIO.
498 498  
499 499  
500 -Apply Integration to Label.
572 +//**Apply Integration to Label.**//
501 501  
574 +
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.
583 +**//Click LoRaWAN Helium,select the device.//**
514 514  
585 +
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.
590 +**//Fill in DEVEUI and create my device.//**
521 521  
592 +
522 522  [[image:image-20220526101419-16.png]]
523 523  
524 524  TagoIO.
525 525  
526 526  
527 -=== 3.4.2 Cayenne ===
528 528  
529 -The process of creating devices is similar to Tago.
599 +=== **3.4.2  Cayenne** ===
530 530  
601 +
602 +//The process of creating devices is similar to Tago.//
603 +
531 531  [[image:image-20220526101616-18.png||height="456" width="1097"]]
532 532  
533 533  Cayenne.
... ... @@ -558,78 +558,89 @@
558 558  Cayenne.
559 559  
560 560  
561 -== 3.5 Trouble Shooting ==
562 562  
563 -=== 3.5.1 Trouble to Join Helium ===
635 +== **3.5  Trouble Shooting** ==
564 564  
637 +=== **3.5.1  Trouble to Join Helium** ===
638 +
639 +
565 565  (((
566 -Assume the device is powered correctly. If you don't see data in Helium. The possibilities are:
641 +**//Assume the device is powered correctly. If you don't see data in Helium. The possibilities are~://**
642 +
643 +
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)
647 +//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)
651 +//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)
655 +//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  
657 +
580 580  
581 581  )))
582 582  
583 -=== 3.5.2 Packet Loss for AU915 / US915 Band ===
661 +=== **3.5.2  Packet Loss for AU915 / US915 Band** ===
584 584  
663 +
585 585  (((
586 -The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.
665 +//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.
669 +//The reason for this problem is that the node does not lock the channel after joining the network.//
670 +
671 +
591 591  )))
592 592  
593 593  (((
594 -Solution:
675 +(% style="color:red" %)**Solution:**
676 +
677 +
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.
681 +//(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
685 +(% style="color:blue" %)**//AT Command: AT+CHE//**
603 603  )))
604 604  
605 605  * (((
606 -Example:AT+CHE=1 ~/~/set channel mode to 1
689 +//**Example: ** (% style="color:#037691" %)**AT+CHE=2**(%%)  ~/~/set channel mode to 1//
607 607  )))
608 608  
609 609  * (((
610 -Downlink Command: 0x24
693 +(% style="color:blue" %)**//Downlink Command: 0x24//**
694 +
695 +
611 611  )))
612 612  
613 613  (((
614 -Format: Command Code (0x24) followed by 1 bytes channel value.
699 +//Format: Command Code (0x24) followed by 1 bytes channel value.//
615 615  )))
616 616  
702 +
617 617  (((
618 -If the downlink payload=2401, it means set channel mode to 1, while type code is 24.
704 +//If the downlink payload=0x2402, it means set channel mode to use sub-band 2, while type code is 24.//
619 619  )))
620 620  
621 621  * (((
622 -Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1
623 -)))
708 +//**Example 1**: Downlink Payload: (% style="color:#037691" %)**0x2402** (%%) ~/~/ set channel mode to 2//
624 624  
625 -* (((
626 -Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5
710 +
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.
714 +//(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.
718 +//The latest firmware for end node will have this bug fixed.//
635 635  )))
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