So, i did a bit more looking at this… using the AU_global_conf.json file on the RAK831 resulted in nothing being seen by the gateway. ( trying to join using the SAMR34 using 915 or 868 )
I swapped to the EU_global_conf.json file, and when i try to join using 868 I get some activity in theTTN console.
joining on AU915 doe’snt craete any join attempts.
The gateway is some 10meters away, and yes the gateway is being seen…
I have been looking at the syslogs as well. When configured for AU-915, i dont’ see anything being received… Using the EU-868 Config i see this; ( as well as in teh console )
pi@ttn-gateway:/var/log $ tail -1000 syslog | grep pk
Feb 5 12:07:43 ttn-gateway ttn-gateway[539]: INFO: Received pkt from mote: D0016F90 (fcnt=46037)
Feb 5 12:07:43 ttn-gateway ttn-gateway[539]: JSON up: {"rxpk":[{"tmst":170199772,"chan":2,"rfch":1,"freq":868.500000,"stat":1,"modu":"LORA","datr":"SF9BW125","codr":"4/5","lsnr":9.2,"rssi":-103,"size":23,"data":"AJBvAdB+1bNwMNYBGBklBACNFWC73A0="}]}
Feb 5 12:07:43 ttn-gateway ttn-gateway[539]: JSON down: {"txpk":{"imme":false,"tmst":176199772,"freq":923.3,"rfch":0,"powe":20,"modu":"LORA","datr":"SF12BW500","codr":"4/5","ipol":true,"size":17,"ncrc":true,"data":"IPuvvHfSHYTYjuMt/9qW1dQ="}}
Feb 5 12:11:15 ttn-gateway ttn-gateway[539]: INFO: Received pkt from mote: D0016F90 (fcnt=46037)
Feb 5 12:11:15 ttn-gateway ttn-gateway[539]: JSON up: {"rxpk":[{"tmst":448884852,"chan":2,"rfch":1,"freq":868.500000,"stat":1,"modu":"LORA","datr":"SF9BW125","codr":"4/5","lsnr":9.0,"rssi":-105,"size":23,"data":"AJBvAdB+1bNwMNYBGBklBAD/b6CJAA4="}]}
Feb 5 12:11:15 ttn-gateway ttn-gateway[539]: JSON down: {"txpk":{"imme":false,"tmst":454884852,"freq":923.3,"rfch":0,"powe":20,"modu":"LORA","datr":"SF12BW500","codr":"4/5","ipol":true,"size":17,"ncrc":true,"data":"IG0NKWKiFx6/qHr/k2W4DJI="}}
It appears that perhaps somethign else is in play to get the gateway configured to use the EU-868 band. ( I’m just trying to get it working as a starting point )
I’m perplexed as to why it does not see any packets when its set up for AU-915. I’m guessing the problem may lie with the SamR34. This is a very similar behaviour to what i saw on a known working system.