I’m facing a issue, when i’m trying to connect several differents nodes in OTAA,it’s never works
I have investigate in the differentsl logs in the lora_pkt_fwd, and i can see that the JoinAccept message is send.
It is displayed in the UI (last screenshot, you have to expand the meta-data). Please note that LoRa Server schedules the frame in advance to the gateway and that the gateway will keep a queue of frames to be transmitted. So a frame sent to the gateway does not mean it is instantly transmitted.
Does it mean that the tx packet is send with an other delay equal to 1495 seconds/ticks?
Should the pkt_fwd and lora-app-server start at the same time to the lora-app-server, to prevent timestamp issues?.
In fact i’m using the ic880a with an usb to spi adaptater, the C232HM from FTDI and working with 1MhZ frequency on the spi, 8Mhz is not stable.
All the spi logs looks good, but i’m asking myself if the tx is working or not, even in abp i’m not so sure if the tx works, i have try in confirmed and unconfirmed transmission. The logs looks good, but any of my sensor get the message.
And the leds on my ic880a never toggle only the power one is on.
You might want to upgrade your packet-forwarder on the gateway. The overwrite warning looks like it is outdated as the latest version implements a just-in-time queue.
I receive some UnconfirmedData and still my app-server automatically reply with a UnconfirmedData !!!
And the delay between the up and the down is always equal to 232 seconds. I think that it’s a bug.
My lora-app-server version: 0.20.1
My loraserver version: 0.26.1
Ok i found what we are answering, we are asking RXTimingSetupReq and RXParamSetupReq.
And because the end device don’t get the message, he never answered. But i’m still don’t understand this 232s delay.
I’m facing the same problem about the join procedure via OTAA. I have a 145+ nodes in production that take too much time to join the network, about +5h sometimes, after the join I’m able to send packets normally. It is important to say that after some (many) tries, the node seems to not send any other packet of join, only after many hours. I tried everything that i knew and i don’t have any approach left. I’m using the regional band US_902_928.
I was noticing that for some nodes (as in the image) the signal looks pretty bad with loraSNR -15 and sometimes with nodes that are closer to the gateway. This happens commonly with the multitech gateway.
I tried to verify the timestamp and looks ok. When I test the join procedure in the lab with a few nodes works fine. But in production, the things are mad.
By the way, I use the US915 in hybrid mode. The channels are already configured on the gateways and my nodes. I’m using in both the 8 first channels available.
[UPDATE]
I updated to the last version of the loraserver and is working fine along with Laird gateway, however, seems like there is a problem with the multitech gateway, probably it needs some updates.