I am quite new to LoRa so if I am in the wrong forum area I do apologise. If anyone has any information based on my issues below I would appreciate a reply.
I can send it AT commands so I know it’s there and active
This is my console for the gateway that says not connected:
I have loaded the following bin file to the gateway: st-nucleo-lora-gw-at-fw-v2.1.7-eu868-TTN.bin
I have loaded the I-NUCLEO_LRWAN1 with the AT_Master firmware as instructed.
So my questions are:
1: how do i get my gateway to be connected
2: do i need to use at commands on the I-Nucleo to communicate through it
3: how do i know if the I-Nucleo is sending it data?
4: how do i know if the gateway is receiving any data?
Did you pay attention to this instruction when settng up for TTN
provide the necessary gateway information after checking the [I’m using the legacy packet forwarder*]checkbox*
I believe this uses the UDP based PF (per last 2 lines) which doesnt allow for ‘useful’ names such as “rtrgateway1” for GW ID rather just names of the form eui-xxxxxxxx - in your case I suspect should be eui-080027ffff0c2338 looking at your screen shot (Please do not post pictures of screen shots but capture and post formatted text)
I think it may be mis-registered…try registering with correct name and EUI/GW ID
Hi Jeff,
Thanks for getting back to me. I re-registered the gateway and this is my result but I get the same result, could there be an issue with the company firewall maybe?:
In Tera Term I can still send AT commands: /// /// /// /// _/ / /// _/ / ///
_/ _/ _/ _/ _/ // _/ _/ _/ _/ / /// _/ // _/ _/ / / / // //// ///
_/ _/ _/ _/ _/ _/ // _/ _/ _/ _/ / / / /// /// /// _/ / /// _/ _/ _/
Powered by RisingHF & STMicroelectronics
VERSION: 2.1.7, Nov 6 2018
LOG: OFF
AT ECHO: ON
BAUDRATE: 115200bps
MACADDR: 08:00:27:0C:23:38
ETHERNET: DHCP
DNS1: 114.114.114.114
DNS2: 8.8.8.8
NTP SERVER: 1.ubuntu.pool.ntp.org
EUI PADDING: {3, FF}, {4, FF}
GATEWAY ID: 080027FFFF0C2338
LORAWAN: Public
LORAWAN SERVER: router.eu.thethings.network
Concentrator starting…
Concentrator Radio A type SX1257
Concentrator Radio B type SX1257
Concentrator started (2926ms)
ST LoRa GW V2
Ethernet starting…
Ethernet started
DHCP IP: 192.168.1.2
Downlink UDP Connected
Uplink UDP Connected
I have the I-NUCLEO-LWRAN1 Sensor Expansion board that comes with the LRWAN2 Gateway. I followed the instructions for setting this up too as outlined in the getting started document: https://www.thethingsnetwork.org/docs/gateways/st/UM2587_Rev1pub.pdf
This is all very new to me but am i right in assuming if my gateway is not connected I wont see data from my end node device either?
Is there a way to test the connection between the gateway and the end node without being connected to the internet?
If I suspect a corp firewall issue I usually quickly drop any WiFi enabled GW’s on to a mobile data tether on my phone or a field spare ( I carry several registered to different networks to allow for spotty coverage just in case ) as a quick check…can u do that with your phone?
update: ignore just remembered no WiFi on this… last time I had to do that was with a Dragino LPS8 where I was working with enterprise entet but fell back to WiFi’s for firewall test!
Where in world are you? Expectation is close to me and certainly in Europe given freq & router choice (& name if not presumptious) but see your 1st dns is away on China Net! Promote the google 8.8.8.8 to 1st dns and maybe populated 2nd with another or leave blank (perhaps 1.1.1.1 or dyndns or something?! Other than potentially behind the Great Firewall of China
Good detective work there . I’m based in Limerick, Ireland.
Yeah so no WiFi on this gateway, I presume I will find a change command in the AT referance manual to change the 1st and 2nd DNS.
I’ll get back to you shortly thanks.
Concentrator starting…
Concentrator Radio A type SX1257
Concentrator Radio B type SX1257
Concentrator started (2926ms)
ST LoRa GW V2
Ethernet starting…
Ethernet started
DHCP IP: 192.168.1.2
Downlink UDP Connected
Uplink UDP Connected
I have one here configured for default LoRiot use which I am >Month overdue moving to TTN so will hopefully get on to registering over next ~24hrs and let you know how I get on and will note steps and any gotcha’s along the way. Then I can to help map my experience to yours and see if working/problem areas.
That would be great thank you.
I am sure it is just a few simple things I am missing in my setup procedure.
If you have details on the Loriot setup I can try this in the mean time.
Loriot was the default installl in the ‘as shipped’ blister pack version of the product with simple set up guide on the enclosed info card. If you have now flashed the .bin/sw for the TTN operation that will have gone. If you didnt update s/w for the TTN build that may be root of problem, esp if tried & rebuild wasnt successful
No I definitely flashed the .bin/sw for TTN. I switched to TTN because of the forum and support sites.
I did try connecting using the LORIOT setup first but ran into the same problem with the gateway showing as not connected. I had not looked at changing the DNS values during this setup or any other parameters through AT commands before switching.
Electronic hardware design and debug is my background so this is a steep learning curve for me but one I need to make.
Possible big clue there then. Can you confirm if RisingHF card correctly reset and up and running? If LoRa module not running then may lead to not connected situation you have seen. Have you tried (with power off! ) removing and re-seating card etc. I have a Laird GW atop a mast that I cant acces yet where through remote diagnostics and login I know control board, enet & wifi all working but connection to LoRa board lost and so now shows as ‘not connected’ in the TTN console - even though the system ‘works’ as a networked comupte system
I have powered of and reseated the RisingHF card.
In Tera Term I get this:
Concentrator starting…
Concentrator Radio A type SX1257
Concentrator Radio B type SX1257
Concentrator started (2926ms)
ST LoRa GW V2
Ethernet starting…
Ethernet started
DHCP IP: 192.168.1.2
Downlink UDP Connected
Uplink UDP Connected
I have a solid green LED on the RisingHF card
I have a solid green LED on the Ethernet Port CN14 signifying 10\100\100Mbps traffic
I have a blinking Orange LED on the Ethernet Port CN14 signifying data being transferred
Still not connected.
You wouldn’t see data in the TTN console of course, but most gateways do print out a log message any time they receive a raw packet, and if you know what you are looking at your can figure out what sort of packet that is.
So far there’s no real indication that your gateway has ever received any packets over the air.
Hi again,
Interesting note, while i was waiting for Jeff to complete his switch over to TTN I decided to try the final third party firmware for the gateway from Actility.
I was able to get the gateway connected very quickly and easily, the I-NUCLEO-LRWAN1 sensor node was a little trickier as there wasn’t as much detail on adding devices as there was in adding the gateway.
I can now see packets being sent from the sensor node and being picked up by the gateway from within the Actility ThingPark Wireless NetworkPartner. I have not looked at sending those packets to an end site for readable sensor display yet but that is next on my agenda.
I might first try to reflash the gateway with the TTN firmware and re-register the gateway and node, now that i know the gatway is not being blocked by any firewalls here.
Just be careful that you don’t delete the existing registration in console as you won’t be able to reregister the same gw ID. Use the existing details to reload the gw. Btw you did double/triple check ID (padded enet MAC address) was entered correctly? Easy to get some characters wrong getting mine up and running is next but one task tonight/tomorrow
Update… triggered by my own question I just double checked what u posted and they don’t match!