Summary

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

Details

Page properties

Content

...	...	@@ -16,8 +16,10 @@
16	16	* End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
17	17	* End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI)
18	18
19		-**~1. End Device Join Screen shot, we can check:**
20	20
	20	+
	21	+(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
	22	+
21	21	* If the device is sending join request to server?
22	22	* What frequency the device is sending?
23	23
...	...	@@ -26,7 +26,7 @@
26	26	Console Output from End device to see the transmit frequency
27	27
28	28
29		-**2. Gateway packet traffic in gateway web or ssh. we can check:**
	31	+(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
30	30
31	31	* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
32	32	* If the gateway gets the Join Accept message from server and transmit it via LoRa?
...	...	@@ -36,7 +36,7 @@
36	36	Console Output from Gateway to see packets between end node and server.
37	37
38	38
39		-**3. Gateway Traffic Page in LoRaWAN Server**
	41	+(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
40	40
41	41	* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
42	42	* If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
...	...	@@ -47,7 +47,7 @@
47	47	The Traffic for the End node in the server, use TTN as example
48	48
49	49
50		-**4. Data Page in LoRaWAN server**
	52	+(% style="color:blue" %)**4. Data Page in LoRaWAN server**
51	51
52	52	* If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
53	53
...	...	@@ -314,7 +314,6 @@
314	314
315	315
316	316
317		-
318	318	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
319	319
320	320