Home › Forums › Conduit: AEP Model › lora-in node on Node-Red
Lawrence Griffiths.
John BeattieHi,
I have a trivial flow: one lora-in node going to a debug node. I was hoping to see each incoming packet dumped to the debug window but I actually see nothing.
The trace in /var/log/lora-pkt-fwd-1.log seems to show that some packets are being seen, e.g.:
##### 2016-02-05 07:10:25 GMT #####
### [UPSTREAM] ###
# RF packets received by concentrator: 1
# CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
# RF packets forwarded: 1 (14 bytes)
# PUSH_DATA datagrams sent: 1 (233 bytes)
# PUSH_DATA acknowledged: 0.00%
### [DOWNSTREAM] ###
# PULL_DATA sent: 2 (100.00% acknowledged)
# PULL_RESP(onse) datagrams received: 0 (0 bytes)
# RF packets sent to concentrator: 0 (0 bytes)
# TX errors: 0
##### END #####
INFO: [down] PULL_ACK received in 1 ms
How do I check my configuration, please?
Thanks,
John
Andrew LindsayWhat are you using to send data to your Conduit?
Is it using the correct credentials?
Can you see that the device joined the network?
On the Conduit AEP gui, in the status and logs section, do you see the device showing as having joined?
Andrew
John BeattieHi Andrew,
A WiMOD device, running LoRaWAN software.
The conduit recognises the join request and puts the device into its db.
Communications between the device and the conduit are flakey but packets are recognised by the conduit, see the next answer.
The status page shows this:
Received
CRC Errors 2351
Duplicates 0
Join Duplicates 0
Join Requests 73
Total Packets 79
Sent
Duplicates Acked 6
Packets Acked 0
Total Join Responses 73
Join Responses Dropped 0
Total Packets 79
Packets Dropped 0
Node Address EUI Join Time RSSI (avg) SNR (avg) Pkts Up Pkts Down Details
00:00:00:01 07:06:05:04:03:02:01:00 2016-02-05 13:13:31 0 0 0 2
The CRC errors and the duplicates show what I mean by flakey 🙂 but a few packets have been seen, in addition to the join requests.
I was wondering where the Node-Red took its data from – is it from the packet forwarder or is it from the network server directly or is it something else.
Best regards,
John
Lawrence GriffithsJohn, I’ve seen with multitech end-nodes (mDots) join as far as AEP is concerned but end-node seems to timeout so has to re-join. What region are you in USA – EU? as in EU the join request on a fixed channel which has 0.1% duty cycle.
One useful thing is to have an MQTT in node connect to localhost port: 1883 and add the following to topic lora/+/joined and then add output to debug node.
where XX:XX is
{ “topic”: “lora/00:80:00:00:00:00:XX:XX/joined”, “payload”: “lora/00:80:00:00:00:00:XX:XX/joined – “, “qos”: 1, “retain”: false, “_topic”: “lora/00:80:00:00:00:00:XX:XX/joined”, “_msgid”: “93217baf.6cde88” }