Novice here. I have looked through and tried solutions in the threads. I keep getting an rx timeout on the device (AB02S), and although the ttn console occasionally gets a connection the device never joins. I am running the verbatim example code. There’s a gateway about 500m from here.
Can you provide some detail - what sort of connection - what the actual text it is - no screen shots please.
This implies it’s not yours so you can’t see the gateway logs. No matter, if the device console shows a Join Request and shows its created a Join Accept and assuming that this remote gateway is able to transmit the JA because it doesn’t have any issues with duty cycle, then the next step is to get the antenna closer - or a better antenna - or both.
As numerous forum posts you can search for will explain, gateway = big antenna can hear JR, device = small antenna, less able to hear a JA.
Hi Nick, thanks for answering.
I can see activity in the TTN console, such as “forward join-accept message”, “accept join-request”, “successfully processed join-request”, etc., but the end device never gets the downlink response. I have been driving around the city to explore hot spots and in one or two places I managed to finally join. But it doesn’t make sense since Copenhagen should be well covered.
I think it may be the antenna. I’m using an 8cm one.
LoRa doesn’t really relate very well to the WiFi concept of hotspots - rather different propagation, reflection & absorption variables due to the marked difference in wavelength.
Should be because it’s the law? Or because it is the capital? The airport doesn’t seem to have any coverage nor does the immediate north-west quadrant just outside the centre - like Husum for instance.
Size is not the key issue, it’s the quality. And line of sight.
The glue-rod antenna supplied has a reasonable chance of being ‘upgraded’ by a 82mm of solid (single stranded) wire stuck in to the SMA connector.
I replaced the antenna which solved the connection issues. However, the CubeCell library still complain with Rx Timeout events for every communication even though it gets transmitted successfully through to TTN. What might be the reason?
Or… is this just the way the Heltec CubeCell libraries behave when the uplinkmode is unconfirmed?
Guessing here, due to lack of visibility of the logs / actual error messages, but pretty confident that this is due to the specification for LoRaWAN - it sends an uplink and then has to wait, speculatively, for any downlinks which it can only determine by listening & waiting until it’s gone past the time for any downlink to be heard, hence the error message.
Please re-read your posts and put yourself in the other persons chair to ask yourself if there is enough detail to answer with confidence. Saves on lots of back & forth asking for details!
Um, no, the library is based on an old copy of LoRaMac-node, the reference implementation for LW, so it’s generic and most other implementations report an Rx timeout as well.
Confirmed uplinks are a disaster for normal operations as they tie up the gateway responding and they eat in to your FUP allocation.
It seems you are starting out on the LW journey, there are many many great discussion on the forum so please use search. Plus there is https://www.thethingsnetwork.org/docs/lorawan/ which covers all the usual core questions. The video is well worth a watch but do it on YouTube where it has chapter links to make it more digestible.
The CubeCell was one of the devices I bought early on in my journey. They very shortly ended up in the “only use if you are desperate” draw as the LW is very old and the ASR MCU is quirky. Before you ask which is the best device to use, it depends on your use case!