Did you try ABP? Does your configuration work with ABP?
Where are the components (LoRa-Gateway-Bridge / LoRaServer / LoRaAppServer) installed? On the Kerlink or on a different machine? If on a different machine, how do you connect to it, by Ethernet or 3G?
Yes I tried ABP and it didn’t work. I don’t think that this is an issue with the endianness because I can see the JoinRequests on the App-Server for the device_eui.
Does the device do a JoinRequest on ABP or how do the device know that it is registered?
The node is a ultrasonic sensor from nemeus.fr.
LoRa-Gateway-Bridge is installed on the Kerlink Gateway.
LoRaServer / LoRaAppServer / MQTT / Postgres are installed on a virtual machine in a data center and it’s connected by ethernet. Ping is less than 2ms. As I can see it in the logs the gateway communicates with the loraserver.
When you both see the RX (received by the gateway) and TX (request to transmit by the gateway), then all keys should be alright. Have you had success with other LoRaWAN networks and this device? Just to make sure that it is not the device causing this issue.
The support says they tested their devices with the networks Objenious, Orange, SwissCom, KPN, TTN. I have no chance to See the tx from the Gateway this Device is a Black Box for me.
They care About the 75% crc fails in the log above. What Do you think?
The Gateway and the Device Are in the Same Room for testing.
They also told me that there is no apb anymore due to security reasons.
When I add a gateway, I can select a channel-configuration but after that when I look into the gateway configurations I can’t see a selected channel-configuration (it’s empty). And it shows no result if I click on it.
Is this right?
That could be a problem, specially if you are using SF12 (data rate 0) on the node. Try with DR5 and put the node more far away.
Sorry, who is “they”? Is it Kerlink? As far as I know, ABP is still part of the LoRaWAN specifications, so I really don’t understand what they mean by that… (but this is off-topic and not related to the problem you shared with us).
With they I mean the manufacturer of the ultrasonic sensor. So my node don’t support ABP anymore.
The support of my ultrasonic sensor told me the same to join the network at a higher distance to the gateway.
The second point could be that the JoinAccept message don’t list a CFList? How can I change it at loraserver?
I added extra channels at network-server and typed “0,1,2” for enabled channels. But there is no CFList.
I am no expert on LoRaWAN, but I think if joining by OTAA is not succesful, then the node doesn’t get information on available channels. But @brocaar will have a better answer to that.
So I would suggest first try to put the node farther away form the gateway, perhaps that will give a solution to all problems.
In the LoRaWAN Spec 1.0.2 you can see that there is an optional CFList in the JoinAccept message. But you’re right if the node don’t recive this message it can’t notice of a CFList. But my problem is that in the log I can’t see a CFList in the JoinAccept message.
But for now I will try it now a greater distance first
# Use this when ony a sub-set of the by default enabled channels are being
# used. For example when only using the first 8 channels of the US band.
See the extra_channels section in the loraserver.toml config:
# Extra channels to use for ISM bands that implement the CFList
#
# Use this for LoRaWAN regions where it is possible to extend the by default
# available channels with additional channels (e.g. the EU band).
# Note: the min_dr and max_dr are currently informative, but will be enforced
# in one of the next versions of LoRa Server!
Now I try to look into the JoinAccept Message
in SPF I got in
Base64 “IAbbPFqT775K7PYdfCox25plYITRzdVuqlyU/jTTv0py”
in Hex 20 06 db 3c 5a 93 ef be 4a ec f6 1d 7c 2a 31 db 9a 65 60 84 d1 cd d5 6e aa 5c 94 fe 34 d3 bf 4a 72
Means
MHDR 20
JoinAccept 06 db 3c 5a 93 ef be 4a ec f6 1d 7c 2a 31 db 9a 65 60 84 d1 cd d5 6e aa 5c 94 fe 34
MIC d3 bf 4a 72 (same as LoRaServer Frame Logs)
Could you try with a different type device? When the device is a blackbox and everything from the network-side looks ok (at least to me), I think it would be better to validate with a different type LoRaWAN device.
Is anybody using a Kerlink gateway with the semtech packet forwarder?
If yes could you send me your complete spf directory?
Does the execute_spf.sh script is calling the modem_on.sh script?
Do I have to start the modem_on.sh script by myself?