Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -9,9 +9,7 @@
9	9
10	10	There are three types of hotspots that can connect to Helium. They are full-hotspot, light hotspot and 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.
11	11
12		-(((
13	13	Dragino has different gateway models that support different types.
14		-)))
15	15
16	16	(% border="1" style="background-color:#ffffcc; width:785.989px" %)
17	17	|(% colspan="4" style="width:783px" %)(% style="color:green" %)**Dragino Hotspots for Helium**
...	...	@@ -125,9 +125,7 @@
125	125	+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--+
126	126	)))
127	127
128		-(((
129	129	**Note**: The wallet Address is 13oLxfjxcYajvfkxxxxxxxxxxxxxxxxxxxxxfY3yp4cz8r1NNux. and have about 18 HNT balance.
130		-)))
131	131
132	132
133	133	(((
...	...	@@ -206,9 +206,7 @@
206	206	+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
207	207	)))
208	208
209		-(((
210	210	4. Assert Location. In helium Wallet. run below command, note, the ~-~-gateway should input gateway address from step 2.
211		-)))
212	212
213	213	(% class="box" %)
214	214	(((
...	...	@@ -261,9 +261,7 @@
261	261	+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-+
262	262	)))
263	263
264		-(((
265	265	Note: The add hotspot and assert location step might need some time to be effect.
266		-)))
267	267
268	268	(((
269	269	After above steps finish, the mobile helium wallet should be able to show that this hotspot has been added to the helium blockchain.
...	...	@@ -334,9 +334,7 @@
334	334
335	335	=== 2.8.4 Backup/Restor gateway-rs key ===
336	336
337		-(((
338	338	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.
339		-)))
340	340
341	341	[[image:https://wiki.dragino.com/images/thumb/e/ef/Backup_and_restore_key.png/600px-Backup_and_restore_key.png||height="343" width="600"]]
342	342
...	...	@@ -346,13 +346,9 @@
346	346
347	347	=== 2.9.1 Introduction ===
348	348
349		-(((
350	350	The Dragino gateway has supports the double server settings.
351		-)))
352	352
353		-(((
354	354	Users can back to the page of Semtech UDP to configure other server settings.
355		-)))
356	356
357	357	=== 2.9.2 Example ===
358	358
...	...	@@ -396,9 +396,7 @@
396	396
397	397	=== 3.1.3 Step 3:Activate the end-node ===
398	398
399		-(((
400	400	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**
401		-)))
402	402
403	403	[[image:https://wiki.dragino.com/images/thumb/4/45/End-node_traffic.png/600px-End-node_traffic.png||height="239" width="600"]]
404	404
...	...	@@ -428,29 +428,22 @@
428	428
429	429	Add decoder complete.
430	430
	415	+
431	431	== 3.3 How to send a downlink to end device from Helium ==
432	432
433		-(((
434	434	The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example:
435		-)))
436	436
437		-(((
438	438	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]]
439		-)))
440	440
441		-(((
442	442	Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
443		-)))
444	444
445		-(% class="box" %)
446		-(((
447	447	01 00 00 3C ~-~-> AQAAPA==
448		-)))
449	449
450	450	[[image:https://wiki.dragino.com/images/thumb/c/c5/Helium_downlink.png/600px-Helium_downlink.png||height="360" width="600"]]
451	451
452	452	Downlink
453	453
	430	+
454	454	== 3.4 How to add integration to different IoT Servers ==
455	455
456	456	=== 3.4.1 TagoIO ===
...	...	@@ -521,72 +521,39 @@
521	521
522	522	=== 3.5.1 Trouble to Join Helium ===
523	523
524		-(((
525	525	Assume the device is powered correctly. If you don't see data in Helium. The possibilities are:
526		-)))
527	527
528		-(((
529	529	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)
530		-)))
531	531
532		-(((
533	533	2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)
534		-)))
535	535
536		-(((
537	537	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)
538		-)))
539	539
	509	+
540	540	=== 3.5.2 Packet Loss for AU915 / US915 Band ===
541	541
542		-(((
543	543	The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.
544		-)))
545	545
546		-(((
547	547	The reason for this problem is that the node does not lock the channel after joining the network.
548		-)))
549	549
550		-(((
551	551	Solution:
552		-)))
553	553
554		-(((
555	555	(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.
556		-)))
557	557
558		-* (((
559		-AT Command: AT+CHE
560		-)))
	520	+* AT Command: AT+CHE
561	561
562		-* (((
563		-Example:AT+CHE=1 ~/~/set channel mode to 1
564		-)))
	522	+* Example:AT+CHE=1 ~/~/set channel mode to 1
565	565
566		-* (((
567		-Downlink Command: 0x24
568		-)))
	524	+* Downlink Command: 0x24
569	569
570		-(((
571	571	Format: Command Code (0x24) followed by 1 bytes channel value.
572		-)))
573	573
574		-(((
575	575	If the downlink payload=2401, it means set channel mode to 1, while type code is 24.
576		-)))
577	577
578		-* (((
579		-Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1
580		-)))
	530	+* Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1
581	581
582		-* (((
583		-Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5
584		-)))
	532	+* Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5
585	585
586		-(((
587	587	(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.
588		-)))
589	589
590		-(((
591	591	The latest firmware for end node will have this bug fixed.
592		-)))