First impression:
Nice box, it’s is very small and tiny.
I followed the @Fomi manual without any problems. The gateway was up and running in 20 minutes.
Currently it is connected to my outdoor antenna and checking the performance.
BR,
Jeroen
MY gateway is connected to the TTN, but I am unable to get any devices (RAK811 and the TTGO LoRa ESP32) to successfully join. Do I need to any configuration of the packet forwarder?
@megaplow
1.Is the gateway online on ttn?
2.Are DevEUI, AppEUI, and AppKey configured on RAK811 the same as on ttn?
3.Is the frequency band of RAK811 consistent with the gateway?
Im looking forward to seeing the results of this as im thinking of getting a better antenna myself.
the one the device comes with is quite good for testing in the surrounding area
@ZhuQI
Today I started all over (leaving the TTGO LoRa32 out of the mix for now). Both the Gateway and the RAK811 breakout are on the latest firmware. Both devices are set to use US915 as the frequency. TTN can see the gateway is up and running. TTN can see that the breakout node is trying to connect. The traffic on the gateway shows Join Request and Join Accept messages, but the node never joins properly. It keeps retrying then sleeps for a while.
The join requests are coming in at 904-905 mhz
The join responses are coming in at 923-925 mhz
That worked!
Join Success, now I have to make my nodes do things.
What does that do?
@megaplow
This is a minor issue with pkt_fwd, which may cause the gateway to drop join-accept. We are about to release new firmware for the gateway that will fix the problem.
1 Like
That fixed the ESP32 joining issues as well. Thank you!
I purchased a 915 MHz RAK7246G to replace what I thought was a broken RAK7243. When I received the 7246G it showed the same join issue at the 7243. I turns out they both have same pkt_fwd issue which is fixed by changing 16 to 17 in the /opt/ttn-gateway/packet_forwarder/lora_pkt_fwd/global_conf.json file as described above. I also have an issue with the GPS not working on the new RAK7246G gateway. It doesn’t ever get a GPS fix. I swapped the GPS antenna with the RAK7243 and both antennas work with that gateway. The syslog displays:
Mar 12 16:04:39 RAK-079DA8 ttn-gateway[429]: ### [GPS] ###
Mar 12 16:04:39 RAK-079DA8 ttn-gateway[429]: # Invalid time reference (age: 1584029049 sec)
Mar 12 16:04:39 RAK-079DA8 ttn-gateway[429]: # no valid GPS coordinates available yet
Mar 12 16:04:39 RAK-079DA8 ttn-gateway[429]: ##### END #####
-Mark
My GPS is working fine, time and location on the 7246G
Could something wrong with your antenna (connection)? Do you have free line of sight to the satellites?
How are you trying to get the GPS location. I would like to test mine as well.
Check this in your config:
“gateway_conf”: {
“gps”: true,
“gps_tty_path”: “/dev/ttyAMA0”,
“fake_gps”: false,
And check if you can see GPS data is coming from the GPS device:
cat /dev/ttyAMA0
you will get someting like:
pi@RAK-426DA6:~ $ cat /dev/ttyAMA0
,4,1,13,07,184,15,10,254,7113,04,0316,70,214,23,18,SV,4,3,13,20,47,1,49,065,25,26,4,27,58,288,2778,4,4,13,29,00,09GPGLL,5215.94601,191312.00,A,A6x▒▒5X▒91313.00,A,5215.00510.99449,E,0.320,A73
$GPV,0.096,N,0.177,KGPGGA,191313.00,^C
pi@RAK-426DA6:~ $
1 Like
The config of the 7246G gateway has the gps enabled and that section matches my 7243 gateway.
I get no output from cat /dev/ttyAMA0 on the 7245G gateway. The 7243 gateway shows GPS data as expected.
I swapped GPS antennas between gateways and get the same result so both antennas work on the 7243 gateway.
/var/log/syslog on the 7243 gateway contains:
Mar 12 20:03:05 rak-gateway ttn-gateway[714]: ### [GPS] ###
Mar 12 20:03:05 rak-gateway ttn-gateway[714]: # Valid time reference (age: 0 sec)
Mar 12 20:03:05 rak-gateway ttn-gateway[714]: # GPS coordinates: latitude 43.xxxxx, longitude -71.xxxxx, altitude 166 m
Mar 12 20:03:05 rak-gateway ttn-gateway[714]: ##### END #####
/var/log/syslog on the 7246G gateway contains:
Mar 12 20:04:40 RAK-079DA8 ttn-gateway[429]: ### [GPS] ###
Mar 12 20:04:40 RAK-079DA8 ttn-gateway[429]: # Invalid time reference (age: 1584043450 sec)
Mar 12 20:04:40 RAK-079DA8 ttn-gateway[429]: # no valid GPS coordinates available yet
Mar 12 20:04:40 RAK-079DA8 ttn-gateway[429]: ##### END #####
I did reprogram the microSD for the 7246G gateway with RAK7246_v4.1.1_20200109.zip when I couldn’t get the gateway working at first (due to the pkt-fwd issue). Perhaps I don’t have the correct firmware installed for the RAK7246G gateway.
I’m not sure what I did but the GPS is now working on my RAK7246G gateway. I didn’t change anything in the setup. I did move the gateway outside. I had tried that a few days ago without success. It looks like It’s now working properly. Thanks for your help.
-Mark
1 Like
@ZhuQI, when do you anticipate the new firmware being available? I think I’m having similar packet forwarding issues on my RAK7246. Any chance of getting a copy of the beta release now?
@focigod705
The latest firmware will be uploaded in the next week.
But you can use https://github.com/RAKWireless/rak_common_for_gateway to reinstall your gateway, we have fixed the problem on git.
@focigod705
The latest firmware will be uploaded in the next week.
But you can use https://github.com/RAKWireless/rak_common_for_gateway to reinstall your gateway, we have fixed the problem on git.
New firmware available at:
https://downloads.rakwireless.com/en/LoRa/NeoPi-Gateway-RAK7246/Firmware/
2020-03-12
- gateway-version displays more information
- The gateway ID displayed in gateway-config and gateway-version will be the same as that in local_conf.json
- Create a rak_ap file in the /boot directory which can restore the gateway to the AP mode
- When the power issued by NS does not exist, the nearest smaller power will be selected
- Delete the default dns 8.8.8.8 and 223.5.5.5
- When GPS is connected, the system time will be automatically updated to GPS time
- Modify TX power in global_conf.json