Summary

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

Details

Page properties

Content

...	...	@@ -300,12 +300,26 @@
300	300
301	301	Helium-gatewayrs log
302	302
303		-Note: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.
	303	+**Note**: logread is dynamic and FIFO, so helium log might be overwritten by other processes info in system.
304	304
305	305	=== 2.8.3 View the public key address and animal name ===
306	306
307		-{{{root@123123:~# helium_gateway key info { "address": "13KmbKLdpDfECx19kB2nX4suSzz3GskA4JVqKHAKiJ89kuyJx8T", "name": "great-mint-lizard" }}}}
	307	+(% class="box" %)
	308	+(((
	309	+(((
	310	+(((
	311	+{{{root@123123:~# helium_gateway key info }}}
	312	+{
	313	+)))
	314	+)))
308	308
	316	+(((
	317	+(% style="color:red" %){{{"address": "13KmbKLdpDfECx19kB2nX4suSzz3GskA4JVqKHAKiJ89kuyJx8T",}}}
	318	+{{{"name": "great-mint-lizard"}}}(%%)
	319	+(% style="color:black" %)}
	320	+)))
	321	+)))
	322	+
309	309	[[image:https://wiki.dragino.com/images/thumb/c/ce/Hostpot_key_and_animal_name.png/600px-Hostpot_key_and_animal_name.png||height="323" width="600"]]
310	310
311	311	Hostpot key and animal name
...	...	@@ -312,7 +312,9 @@
312	312
313	313	=== 2.8.4 Backup/Restor gateway-rs key ===
314	314
	329	+(((
315	315	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.
	331	+)))
316	316
317	317	[[image:https://wiki.dragino.com/images/thumb/e/ef/Backup_and_restore_key.png/600px-Backup_and_restore_key.png||height="343" width="600"]]
318	318
...	...	@@ -368,7 +368,9 @@
368	368
369	369	=== 3.1.3 Step 3:Activate the end-node ===
370	370
	387	+(((
371	371	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**
	389	+)))
372	372
373	373	[[image:https://wiki.dragino.com/images/thumb/4/45/End-node_traffic.png/600px-End-node_traffic.png||height="239" width="600"]]
374	374
...	...	@@ -398,22 +398,29 @@
398	398
399	399	Add decoder complete.
400	400
401		-
402	402	== 3.3 How to send a downlink to end device from Helium ==
403	403
	421	+(((
404	404	The Helium server needs to convert to Base64 format when sending the downlink command. Please refer to the following example:
	423	+)))
405	405
	425	+(((
406	406	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]]
	427	+)))
407	407
	429	+(((
408	408	Change Uplink Interval:Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
	431	+)))
409	409
	433	+(% class="box" %)
	434	+(((
410	410	01 00 00 3C ~-~-> AQAAPA==
	436	+)))
411	411
412	412	[[image:https://wiki.dragino.com/images/thumb/c/c5/Helium_downlink.png/600px-Helium_downlink.png||height="360" width="600"]]
413	413
414	414	Downlink
415	415
416		-
417	417	== 3.4 How to add integration to different IoT Servers ==
418	418
419	419	=== 3.4.1 TagoIO ===
...	...	@@ -484,39 +484,72 @@
484	484
485	485	=== 3.5.1 Trouble to Join Helium ===
486	486
	512	+(((
487	487	Assume the device is powered correctly. If you don't see data in Helium. The possibilities are:
	514	+)))
488	488
	516	+(((
489	489	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)
	518	+)))
490	490
	520	+(((
491	491	2) Your end node frequency band doesn't match the Helium gateway frequency band. (Please double-check if frequency band matches)
	522	+)))
492	492
	524	+(((
493	493	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)
	526	+)))
494	494
495		-
496	496	=== 3.5.2 Packet Loss for AU915 / US915 Band ===
497	497
	530	+(((
498	498	The node working on the AU915/US915 frequency has packet loss or the frequency channel and the gateway channel are different.
	532	+)))
499	499
	534	+(((
500	500	The reason for this problem is that the node does not lock the channel after joining the network.
	536	+)))
501	501
	538	+(((
502	502	Solution:
	540	+)))
503	503
	542	+(((
504	504	(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.
	544	+)))
505	505
506		-* AT Command: AT+CHE
	546	+* (((
	547	+AT Command: AT+CHE
	548	+)))
507	507
508		-* Example:AT+CHE=1 ~/~/set channel mode to 1
	550	+* (((
	551	+Example:AT+CHE=1 ~/~/set channel mode to 1
	552	+)))
509	509
510		-* Downlink Command: 0x24
	554	+* (((
	555	+Downlink Command: 0x24
	556	+)))
511	511
	558	+(((
512	512	Format: Command Code (0x24) followed by 1 bytes channel value.
	560	+)))
513	513
	562	+(((
514	514	If the downlink payload=2401, it means set channel mode to 1, while type code is 24.
	564	+)))
515	515
516		-* Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1
	566	+* (((
	567	+Example 1: Downlink Payload: 2401 ~/~/ set channel mode to 1
	568	+)))
517	517
518		-* Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5
	570	+* (((
	571	+Example 2: Downlink Payload: 2405 ~/~/ set channel mode to 5
	572	+)))
519	519
	574	+(((
520	520	(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.
	576	+)))
521	521
	578	+(((
522	522	The latest firmware for end node will have this bug fixed.
	580	+)))