[Andrew Neil]

That was it!

Many thanks!

[Andrew Neil]

Aha – I didn’t have the Network Server in ‘Public’ mode!

Will certainly try that …

[Andrew Neil]

The big question is: what, exactly, are the end-device settings needed to make this work?!

As noted, ST’s video is out-of-date – so I guess that there are now important settings that it doesn’t cover.

There is nothing getting as far as MQTT.

On the conduit, I have found /var/log/lora-network-server.log contains stuff like

:
Logger Level Changed to 30
Full MIC: e5.c5.52.bc.ee.73.c0.ff.3b.68.99.c4.86.e1.b4.28
Full MIC: 05.e8.72.ae.c5.d4.0a.02.65.99.e8.24.22.7e.68.94
Full MIC: 7d.cd.25.38.2f.bb.8c.b1.bd.92.14.37.7e.eb.9a.e9
Full MIC: 32.85.ad.f7.f9.26.43.20.9c.e3.3b.c8.7d.7b.2a.67
Full MIC: e2.20.e3.c4.2d.ea.58.ab.11.2e.31.c9.73.f9.e2.17
Full MIC: 98.0d.79.a8.d2.9c.c7.70.b9.f8.d9.bc.82.bd.f3.2d
Full MIC: 82.32.72.04.37.83.db.3f.a4.03.38.5b.72.cd.62.67
Full MIC: 88.62.e3.3e.c2.bf.53.10.80.57.65.f3.d4.40.91.21
:

But what does that mean?
What is, “Logger Level 30”? are there other levels? if so, how to select them?

also /var/log/messages – contains stuff like

Oct 20 16:55:57 mtcdt user.info lora-network-server: Parsing 1 rx packets
Oct 20 16:55:57 mtcdt user.info lora-network-server: Received join request
Oct 20 16:55:57 mtcdt user.info lora-network-server: Device found in DB, assigning address: 1
Oct 20 16:55:57 mtcdt user.info lora-network-server: Queue join response 33 bytes
Oct 20 16:55:57 mtcdt user.info lora-network-server: Send Join Accept – EUI: be-7a-00-00-00-00-00-c8 ADDR: 00000001
Oct 20 16:55:57 mtcdt user.info lora-network-server: Schedule TX Time on air: 81 ms
Oct 20 16:55:58 mtcdt user.info lora-network-server: Frame transmitted to 00:00:00:01 via GW (00:80:00:00:a0:00:05:a8 Chan LC2 127.0.0.1:34778) Seq# 0
Oct 20 16:55:58 mtcdt user.info lora-network-server: Update DC Band: 1 Duration: 71 time-on-air available: 35929 ms
Oct 20 16:55:58 mtcdt user.info lora-network-server: Transmit UDP message to Gateway 208 bytes

and a lot of

Oct 20 19:12:55 mtcdt user.info lora-network-server: Parsing 1 rx packets
Oct 20 19:12:55 mtcdt user.warn lora-network-server: Recv’d frame failed CRC check
Oct 20 19:13:24 mtcdt user.info lora-network-server: Parsing 1 rx packets
Oct 20 19:13:24 mtcdt user.warn lora-network-server: Recv’d frame failed CRC check
Oct 20 19:13:34 mtcdt user.info lora-network-server: Parsing 1 rx packets
Oct 20 19:13:34 mtcdt user.warn lora-network-server: Recv’d frame failed CRC check
Oct 20 19:15:00 mtcdt user.info lora-network-server: Parsing 1 rx packets
Oct 20 19:15:00 mtcdt user.warn lora-network-server: Recv’d frame failed CRC check
Oct 20 19:16:03 mtcdt user.info lora-network-server: Parsing 1 rx packets
Oct 20 19:16:03 mtcdt user.warn lora-network-server: Recv’d frame failed CRC check

This does seem to tie-in with the fact that the Conduit sees the Node as Joined, but the Node’s transmitted data packets are not then recognised.

Is there a way to log/view the raw received packets at the Gateway?

[Andrew Neil]

I would like to second the request for documentation on this!

[Author]

Posts