not recieving RS186 sensor data on gateway
Home › Forums › Conduit: AEP Model › not recieving RS186 sensor data on gateway
Tagged: RS1xx aep conduit
- This topic has 7 replies, 2 voices, and was last updated 5 years, 4 months ago by
Jason Reiss.
-
AuthorPosts
-
November 18, 2019 at 10:40 am #29907
Justine
ParticipantHi,
I have set up the AEP gateway and I successfully join a mDot to the gateway, I can see the payload in node-red when using AT+SEND.
I then tried to connect a RS186 sensor from Laird, I have succesfully used it with another gateway and the the things network, but I would like to be able to see the data sent locally.
I have commissioned the sensor to the gateway and I can see in the dashboard/LoraWan/Device session, that it was seen few minutes ago.
With the CLI, using lora query device stats, I can see the number of up and down increasing.My problem is that I would like to see my data in node-red, like I did with the mDot.
Does anyone has an idea where the issue is coming ? It seems that the data from the sensor are not “catched” when it looks like it is commissioned.
Thank you.
JustineNovember 20, 2019 at 7:24 am #29922Justine
ParticipantI tried to use the command mosquitto_sub -v -t lora/+/+
and I can see that my sensor is sending join request. I don’t know if it is joined or not. This is what I see :
lora/00-25-ca-0a-00-00-85-2f/join_request {“tmst”:1790585540,”chan”:0,”rfch”:0,”freq”:868.1,”stat”:1,”modu”:”LORA”,”datr”:”SF9BW125″,”codr”:”4/5″,”lsnr”:10.8,”rssi”:-38,”size”:23,”data”:”AMyDHOd9k8h/L4UAAArKJQDDFUPFZZc=”,”deveui”:”00-25-ca-0a-00-00-85-2f”,”joineui”:”7f-c8-93-7d-e7-1c-83-cc”,”nonce”:5571,”gweui”:”00-80-00-00-a0-00-36-86″}
lora/00-25-ca-0a-00-00-85-2f/packet_recv {“tmst”:1790585540,”chan”:0,”rfch”:0,”freq”:868.1,”stat”:1,”modu”:”LORA”,”datr”:”SF9BW125″,”codr”:”4/5″,”lsnr”:10.8,”rssi”:-38,”size”:23,”data”:”AMyDHOd9k8h/L4UAAArKJQDDFUPFZZc=”,”deveui”:”00-25-ca-0a-00-00-85-2f”,”joineui”:”7f-c8-93-7d-e7-1c-83-cc”,”nonce”:5571,”gweui”:”00-80-00-00-a0-00-36-86″}
lora/00-25-ca-0a-00-00-85-2f/joined {“remote_js”:false}
lora/00-25-ca-0a-00-00-85-2f/packet_sent {“appeui”:”7f-c8-93-7d-e7-1c-83-cc”,”codr”:”4/5″,”data”:”IFfTmdFmRjXWQYDef5q77Jyx5Up1xev9O2xeUphKE/DC”,”datr”:”SF9BW125″,”deveui”:”00-25-ca-0a-00-00-85-2f”,”freq”:868.10000000000002,”gweui”:”00-80-00-00-a0-00-36-86″,”id”:0,”ipol”:true,”mhdr”:””,”mic”:”4a13f0c2″,”modu”:”LORA”,”ncrc”:true,”opts”:”040002ffff”,”port”:0,”powe”:11,”rfch”:0,”seqn”:0,”size”:33,”tmst”:1791585540,”twnd”:1}
lora/00-25-ca-0a-00-00-85-2f/mac_sent {“appeui”:”7f-c8-93-7d-e7-1c-83-cc”,”deveui”:”00-25-ca-0a-00-00-85-2f”,”gweui”:”00-80-00-00-a0-00-36-86″,”opts”:”040002ffff”}and in the dashboard, under packets :
00-00-84-e0 868.300 SF7BW125 – – 33 00000000 JnAcc one minute ago See Packet Details
00-00-84-e0 868.300 SF7BW125 9 -38 23 00000000 JnReq one minute ago See Packet Details
00-00-84-e0 868.500 SF7BW125 – – 33 00000000 JnAcc one minute ago See Packet Details
00-00-84-e0 868.500 SF7BW125 6 -35 23 00000000 JnReq one minute ago See Packet Details
00-00-84-e0 868.100 SF7BW125 – – 33 00000000 JnAcc one minute ago See Packet Details
00-00-84-e0 868.100 SF7BW125 10 -38 23 00000000 JnReq one minute ago See Packet Details
00-00-84-e0 868.100 SF7BW125 – – 33 00000000 JnAcc 2 minutes ago See Packet Details
00-00-84-e0 868.100 SF7BW125 10 -41 23 00000000 JnReq 2 minutes ago See Packet Details
00-00-84-e0 868.300 SF8BW125 – – 33 00000000 JnAcc 2 minutes ago See Packet Details
00-00-84-e0 868.300 SF8BW125 11 -37 23 00000000 JnReq 2 minutes ago See Packet DetailsDoes anybody know if the sensor is joined ? If yes, why can’t I see any data ? If not, do you have any idea why ?
I have set the appEUI and appkey on the sensor, and the devEUI on the gateway, I don’t know what I’m doing wrong.Thanks.
JustineNovember 20, 2019 at 7:59 am #29923Jason Reiss
KeymasterThe device is commissioned correctly as the JoinAcc is being sent.
Perhaps the device is not receiving the downlink as another join request is sent?
November 20, 2019 at 10:20 am #29924Justine
ParticipantOk, I didn’t realise that.
Would you have any idea how I can investigate to know if the sensor got the downlink ?Thank you
November 22, 2019 at 7:26 am #29933Justine
ParticipantIs there any way to print the precise time of the recieved and sent packet ?
I’m thinking maybe that the downlink is sent outside the Rx windows of the sensor.
I tried to use the gateway with ttn, and it worked perfectly, which makes me think that the problem is comming from a configuration, but everything seems fine to me…Thank you
JustineNovember 22, 2019 at 7:48 am #29934Jason Reiss
KeymasterLooks like your join delay is set to 1 second. The tmst is a value in microseconds of the Rx and Tx packets.
Change the join delay of the network server to 5 seconds and it should succeed.
lora/00-25-ca-0a-00-00-85-2f/join_request {…, “tmst”:1790585540,”chan”:0,”rfch”:0,”freq”:8
lora/00-25-ca-0a-00-00-85-2f/packet_sent {…, ”tmst”:1791585540,”twnd”:1}November 26, 2019 at 7:53 am #29940Justine
ParticipantThank you, I was using the private_mts network, I switched to a public network and it worked.
You said tmst is a value in microseconds, but that doesn’t make 1 second. Do you have more information about this value, I couldn’t find a lot, only that’s a timestamp.Thanks
JustineDecember 2, 2019 at 7:32 am #29956Jason Reiss
KeymasterThe value is a us timestamp internal to the radio hardware. It is used to schedule downlink packets with precise offsets.
1791585540 – 1790585540 = 1000000 us = 1 s
-
AuthorPosts
- You must be logged in to reply to this topic.