P-nucleo-lrwan2 can't connect TTN server

Gateways
1

HI

I bought P-NUCLEO-LRWAN2 evboard. then I downloaded st-nucleo-lora-gw-at-fw-v2.1.7-eu868-TTN .bin file with P-NUCLEO-LRWAN2 GATEWAY

I have static ip so I setup gateway IP and change LoRa Channel US915.

but I can’t connect TTN server with P-NUCLEO-LRWAN2 GATEWAY.

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
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: ***.***.***.***
          MASK: ***.***.***.***
       GATEWAY: ***.***.***.***
          DNS1: ***.***.***.***
          DNS2: ***.***.***.***
    NTP SERVER: 1.ubuntu.pool.ntp.org
   EUI PADDING: {3, FF}, {4, FF}
    GATEWAY ID: 0080E1FFFF0150C9
       LORAWAN: Public
LORAWAN SERVER: router.eu.thethings.network
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
ERROR: UNKNOWN SERVER router.eu.thethings.network
ERROR: UNKNOWN SERVER router.eu.thethings.network
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

and router.us.thethings.network is same error.

so I change server IP(52.169.76.203).

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
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: ***.***.***.***
          MASK: ***.***.***.***
       GATEWAY: ***.***.***.***
          DNS1: ***.***.***.***
          DNS2: ***.***.***.***
    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
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

but TTN console view gateway status is no connect
image

how do p-nucleo-lrwan2 gateway connect TTN server?

and inform router.eu.thethings.network ip address and router.us.thethings.network ip address.

thank you.

2

As mentioned in many existing threads, it’s likely to show that unless you have a node actually sending uplinks through the gateway.

When you do, you’ll presumably see them in the gateways debug log first.

You really should setup DNS though, your harcoded server IP won’t survive any changes to infrastructure which might be needed.

3

Hi @cslorabox

I setup DNS server.

I cleared DNS, IP, gateway at Logs above.

my DNS setting
DNS1 is 168.126.63.1 / DNS2 is 168.126.63.2

////////////////////////////////////////////////////////////////////////////////////////////////////////////
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: 13.66.229.235

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: 00D89EDFA99AEFC782156F356E37343933628F0B54F253

JUL: {"rxpk":[{"tmst":35606860,"chan":7,"rfch":1,"freq":903.700000,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","lsnr":11.5,"rssi":-41,"size":23,"data":"ANie36ma78eCFW81bjc0OTNijwtU8lM="}]}

LRX: 00D89EDFA99AEFC782156F356E37343933E1D121B09BCA

JUL: {"rxpk":[{"tmst":55643108,"chan":0,"rfch":0,"freq":902.300000,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","lsnr":-15.0,"rssi":-118,"size":23,"data":"ANie36ma78eCFW81bjc0OTPh0SGwm8o="}]}

LRX: 00D89EDFA99AEFC782156F356E373439336E17E4886FA6

JUL: {"rxpk":[{"tmst":85640804,"chan":3,"rfch":0,"freq":902.900000,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","lsnr":3.0,"rssi":-117,"size":23,"data":"ANie36ma78eCFW81bjc0OTNuF+SIb6Y="}]}

LRX: 00D89EDFA99AEFC782156F356E3734393324E11B2CEA1C

JUL: {"rxpk":[{"tmst":115296129,"chan":8,"rfch":0,"freq":903.000000,"stat":1,"modu":"LORA","datr":"SF8BW500","codr":"4/5","lsnr":10.0,"rssi":-34,"size":23,"data":"ANie36ma78eCFW81bjc0OTMk4Rss6hw="}]}

LRX: 00D89EDFA99AEFC782156F356E37343933CE7994B97F2B

JUL: {"rxpk":[{"tmst":121773940,"chan":0,"rfch":0,"freq":902.300000,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","lsnr":8.8,"rssi":-33,"size":23,"data":"ANie36ma78eCFW81bjc0OTPOeZS5fys="}]}

LRX: 00D89EDFA99AEFC782156F356E37343933D2CD853490BB

JUL: {"rxpk":[{"tmst":124327964,"chan":0,"rfch":0,"freq":902.300000,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","lsnr":12.0,"rssi":-39,"size":23,"data":"ANie36ma78eCFW81bjc0OTPSzYU0kLs="}]}

LRX: 00D89EDFA99AEFC782156F356E3734393392139086287B

JUL: {"rxpk":[{"tmst":144364188,"chan":6,"rfch":1,"freq":903.500000,"stat":1,"modu":"LORA","datr":"SF10BW125","codr":"4/5","lsnr":-3.3,"rssi":-106,"size":23,"data":"ANie36ma78eCFW81bjc0OTOSE5CGKHs="}]}

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

but gateway status is not changed not connected.

image

what address is server ip 13.66.229.235?

what address is server ip 52.169.76.203?

thank you

4

I have the same issue, the gateway says

Downlink UDP Connected
Uplink UDP Connected

but TTN shows Not connected, only the firts time I read connected.
Nevertheless the node I have join the network and I can see packets in the TTN console.

5

So you are receiving data? Using The Things Stack Community Edition (V3) or The Things Network (V2)

6

Since RO V2 Data tab depricated & no longer shows traffic at either application or device level making debug and migration checks much harder :frowning:

7

The Things Stack Community Edition I believe, since I see the logo in the console.

8

After long time I dicovered the issue.
In ST documentation it is written to use this server
router.eu.thethings.network.
instead in TTN i found that the server is this one
eu1.cloud.thethings.network
Now the Gateway is connected again.

9

Sadly despite the transition from TTN V2 to TTNV3 (TTS(CE)) being announce >1year ago and effected nearly 4 months ago many vendors are/have been very slow to update their documentation, and many have still to do so. We on the forum would ask that where users discovering this please feed the problem back to the manufacturers and suppliers! There isnt much we can do on the forum other than have stories such as yours highlight the problem :wink:

10

I know that you can do nothing about this, I wrote my solution here just for other people getting same problem.
I will contact ST anyway.

1 Like
11

Worth remembering that this hardware doesn’t really make for an installation-worthy gateway to begin with. Because it is lacking a power amplifier, it should really only be used for bench tests with a private network server. Using it on TTN can potentially result in failed joins and downlinks for other community members, since it may seem like the best gateway to respond to a node, but can’t transmit at the expected power level of a gateway and so may fail to actually reach the node, when a traditional gateway a bit further away could.

12

Hmmmm… so this certificate means nothing?

13

In the context of Chris’s post not a lot. What you have pulled is the cert for the node module…not the gateway. STs own documents declare that the gateway is set for below normal levels of Tx power and lists as for development/experimental use only…

Google for WM-SG-SM-42 if you want to know more about this SX1272 based LoRaWAN module.

14

You’re right, ST nodes have certification, gateway not.
Anyway searching in Lorawan certified decices here
https://lora-alliance.org/showcase/search/?_sfm_lorawan_certified_device=certified
shows only nodes too.
The Terms of Use IMO mean the this evaluation borard cannot substituite a final product because it is not. Because I can’t sell it also inside aother products.
I din’t find any limitation in power but I don’t know wich requirements are requested for gateways.
Here
https://www.thethingsnetwork.org/docs/gateways/st/
I din’t find any limitation in it’s use. But this is V2 documentation. In V3 documentation
https://www.thethingsindustries.com/docs/gateways/
this gateway doesn’t appear.

Anyway this gateway will be placed on Mt.Etna, Italy where, in map, there is not any gateways around, only one in Catania. So I believe that there is not problems with nodes.
But I don’t want to break something or damaging the community so if you believe that there are problems in using this gateway in this community let me know.

15

The community does not believe there are problems - if you search the forum you’ll find prior discussions and there is the comment above about the lack of a power amplifier so whilst the gateway may be able to hear a device, it may not be able to pass on settings or downlinks which the servers will not be able to manage as it would be assumed that the gateway is capable.

The lack of a power amplifier is a known fact, so no belief is needed. If it’s on the side of a high peak, it will affect devices for 10’s of km’s.

Occasionally running this gateway on your desk with a 50Ω resistor for an antenna to test devices is one thing, deploying it could have catastrophic affects on data collection in a region that surely needs to rely on a whole range of telemetry to keep people safe.

2 Likes
16

So it is a experimental gateway? I think LoRaWAN is way past experiments.

There are 3 gateways I can see in Catenia.
EUI: 0080E1FFFF0151BF - 27.6km (57m}
EUI: 58A0CBFFFE803E21 - 18.1km (540m)
EUI: 00800000A0008D8D - 17.3km (594m)

All with LOS to Mt.Etna at a altitude of 3357 m

These nodes working the the above mentioned gateways could be closer. And if I look at the lay of the land most probably have LOS to Mt.Etna.

So if the you SNR is not too bad, the nodes will see your gateway at that distance. You will affect them.

image
image1091×602 102 KB

1 Like
17

There are atleast 3 publically vsible to the south and west of Etna region, and lets ignore the 2 south of Messina much further NNEast. The problem is 2 fold - 1) not all GWs are shown publically and therefore not all on the map. and nodes can be deployed anywhere in range of a GW (which in case of high mounted Gw’s on hills and mountains…or volcano’s!)…can be a very long way, potentially much more than 10km, 20km and even 100km. Also 2) community nodes can also be serviced by networks associated with and exchanging data with TTN through PacketBroker - these again will not show on either main TTN maps or individual community maps. Your faux GW may hear messages from others nodes and then be chosen by the NS to reply and interact with those nodes, but with crippled Tx power wont be able to reach them, and will keep failing unbenknowns to the NS and the nodes will be frustrated in there efforts to communicate and interact with the NS and back end systems. This might also happpen with your own nodes if you are intending to deploy over a wide range - debug & field operation then becomes a nightmare…

I also have one of these ST development cards but wont deploy for real world use and as commented above would only use in controlled development activity use cases where I can be confident t wont impact other users (i.e. off TTN), otherwise it has to collect dust on the shelf :wink: The node is just fine - go deploy! :slight_smile:

Update, just seen Johan posted a fraction before me basically showing with measurements part of what I explained above. Actual impact will also depend on your exact placement…

2 Likes
18

Thank you to all!

One point. Putting a gateway on the top of Mt.Etna will be very good but it is very difficult to mantain. The volcano is active and a gateway on the top will survive only few months. The idea was to put it at about 1000m height on the south flank but you’re right, this will have an impact to the others gateways and TTN so I will use it only for testing nodes.

Thank you again!

19

Exactly my point …