P-nucleo-lrwan2 gateway can't transmit accept data

Gateways
1

hi

I use p-nucleo-lrwan2 gateway

gateway’s frimware is “st-nucleo-lora-gw-at-fw-v2.1.7-eu868-TTN.bin”

I changed gateway channel US915 and static ip.

TTN server is router.eu.thethings.network or router.us.thethings.network

my device try to join TTN server with US915.

so TTN send accept server join data.

but gateway’s log couldn’t be view to transmit accept data.

How should gateway transmit accept data?

please help me.

I attach the gateway log and gateway traffic

Powered by RisingHF & STMicroelectronics

       VERSION: 2.1.7, Nov  6 2018
           LOG: ON
       AT ECHO: ON
      BAUDRATE: 115200bps
       MACADDR: 00:80:E1:01:50:C9
      ETHERNET: STATIC
            IP: 192.168.100.139
          MASK: 255.255.255.0
       GATEWAY: 192.168.100.1
          DNS1: 168.126.63.1
          DNS2: 168.129.63.2
    NTP SERVER: 1.ubuntu.pool.ntp.org
   EUI PADDING: {3, FF}, {4, FF}
    GATEWAY ID: 0080E1FFFF0150C9
       LORAWAN: Public
LORAWAN SERVER: 52.169.76.203
UPLINK UDP PORT: 1700
DOWNLINK UDP PORT: 1700
      CHANNEL0: 902300000, A, SF7/SF12, BW125KHz    (LORA_MULTI_SF)
      CHANNEL1: 902500000, A, SF7/SF12, BW125KHz    (LORA_MULTI_SF)
      CHANNEL2: 902700000, A, SF7/SF12, BW125KHz    (LORA_MULTI_SF)
      CHANNEL3: 902900000, A, SF7/SF12, BW125KHz    (LORA_MULTI_SF)
      CHANNEL4: 903100000, B, SF7/SF12, BW125KHz    (LORA_MULTI_SF)
      CHANNEL5: 903300000, B, SF7/SF12, BW125KHz    (LORA_MULTI_SF)
      CHANNEL6: 903500000, B, SF7/SF12, BW125KHz    (LORA_MULTI_SF)
      CHANNEL7: 903700000, B, SF7/SF12, BW125KHz    (LORA_MULTI_SF)
      CHANNEL8: 903000000, A, SF8, BW500KHz         (LORA_STANDARD)
      CHANNEL9: OFF                                 (FSK)
-------------------------------------------------------------------------------
Concentrator starting...
Concentrator Radio A type SX1257
Concentrator Radio B type SX1257
Radio A, min:902150000, max:903250000
Radio B, min:902950000, max:903850000
Concentrator started (2926ms)
ST LoRa GW V2
Ethernet starting...
STATIC IP: 192.168.100.139
Ethernet started
Downlink UDP Connected
Uplink UDP Connected
LRX: 00D89EDFA99AEFC782156F356E37343933F3A94745FAB9
JUL: {"rxpk":[{"tmst":18578636,"chan":4,"rfch":1,"freq":903.100000,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","lsnr":9.8,"rssi":-19,"size":23,"data":"ANie36ma78eCFW81bjc0OTPzqUdF+rk="}]}
LRX: 00D89EDFA99AEFC782156F356E373439334C62867A5B53
JUL: {"rxpk":[{"tmst":28614332,"chan":5,"rfch":1,"freq":903.300000,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","lsnr":-11.3,"rssi":-93,"size":23,"data":"ANie36ma78eCFW81bjc0OTNMYoZ6W1M="}]}
LRX: 00D89EDFA99AEFC782156F356E37343933FDA395EE5052
JUL: {"rxpk":[{"tmst":38614884,"chan":5,"rfch":1,"freq":903.300000,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","lsnr":-12.5,"rssi":-124,"size":23,"data":"ANie36ma78eCFW81bjc0OTP9o5XuUFI="}]}

and gateway traffic

image

but gateway no tx join accept data.

If TTN should be set Gateway use frequency(US902), where do I set frquency range??

2

Surely you should be using US915 firmware and not EU868 firmware to operate on US915.

It’s notable that no messages are printed about commanded downlinks, so it’s hard to know if those are not making it over the Internet to the gateway, being rejected as being outside the transmit range of the EU868 firmware, or if this version of the packet forwarded just doesn’t print anything for those. It might be worth examining the source code to see if it should, or better yet rebuilding the software for the appropriate region and inserting additional debug.

If this gateway’s Internet access comes literally through a Linux box like an router where you could run a packet sniffer, you could see if it’s getting UDP acks to the uplink pushes, and if it’s getting pull acks or any downlink commands. But you have to run this on a box actually involved in the connection, not simply another one sitting on the same network next to it.

Also note that while it is not your current problem, this gateway has an extremely weak transmitter and will not be able to get messages back to more distant nodes. Since the network has no way of knowing that, it could constitute a denial-of-service attack on the network in the situation where this gateway is a bit closer and gets a stronger receive signal causing it to be elected to send the downlink, but another more traditional gateway with a proper transmitter is the only one that could get the response through.

So, arguably this shouldn’t be used on TTN, but only on bench-scale private test networks.

3

Hi @cslorabox

OK i understand, I want to test Semtech tracker(US915) with TTN.

But I don’t have “US915 firmware” with ST P-NUCLEO-LRWAN2 GATEWAY.

where does ST P-NUCLEO-LRWAN2 GATEWAY offer US915 firmware?

ST P-NUCLEO-LRWAN2 GATEWAY"st-nucleo-lora-gw-at-fw-v2.1.7-eu868-TTN.bin” is surported US902(min:902150000, max:903250000)

I think ST P-NUCLEO-LRWAN2 GATEWAY can’t operate downlink.

how can I test semtech tracker with TTN?