AnsweredAssumed Answered

LoRaWAN with MultiTech Conduit Gateway

Question asked by Andrew Neil on Oct 20, 2017
Latest reply on Oct 23, 2017 by Andrew Neil

I have:

  • B-L072Z-LRWAN1 Discovery board (based on muRata module)
  • P-NUCLEO-LRWAN1 Pack (Nucleo-64 board with Semtech SX1272 bare chip add-on).
  • I-CUBE-LRWAN firmware pack, v1.1.2
  • Keil MDK for STM32L0/F0, v5.24a
  • MultiTech Conduit gateway (as part of a LoRaWAN Starter Kit)

all of the above purchased/downloaded in the last couple of weeks - so up-to-date.

 

I have watched this video: Getting started STM32 Nucleo Pack for LoRa™ technology - YouTube 

But it is out-of-date with both the I-CUBE-LRWAN firmware  and the Conduit.

See: https://community.st.com/community/stm32-community/blog/2016/11/30/stm32-lora-kit#comment-3834 

 

It seems that the demo called "Class A" in the video is now called "End Node".

So I think I managed to find all the points to tweak as mentioned in the video.

 

Not mentioned in the video is that STATIC_DEVICE_EUI has to be set for the LORAWAN_DEVICE_EUI edits to be effective!

 

The code built fine for the two boards, and downloads and runs.

I only run one board at a time. Both boards behave identically.

 

The Conduit sees the board as "Joined", but the Node-RED does not see any incoming data.

 

 

 

I don't see any "JOINED" message in the UART output from the board (the video shows one, but the UM2073 documentation says nothing about what should currently be expected on the UART).

 

Using the 'Download Logs' from the Conduit, the messages log contains stuff like:

Oct 20 08:03:18 mtcdt user.info lora-network-server: Parsing 1 rx packets
Oct 20 08:03:18 mtcdt user.info lora-network-server: Received join request
Oct 20 08:03:18 mtcdt user.info lora-network-server: Device found in DB, assigning address: 1
Oct 20 08:03:18 mtcdt user.info lora-network-server: Queue join response 33 bytes
Oct 20 08:03:18 mtcdt user.info lora-network-server: Send Join Accept - EUI: be-7a-00-00-00-00-00-c8 ADDR: 00000001
Oct 20 08:03:18 mtcdt user.info lora-network-server: Schedule TX Time on air: 81 ms
Oct 20 08:03:19 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 08:03:19 mtcdt user.info lora-network-server: Update DC Band: 1 Duration: 71 time-on-air available: 35929 ms
Oct 20 08:03:19 mtcdt user.info lora-network-server: Transmit UDP message to Gateway 208 bytes
Oct 20 08:03:48 mtcdt user.info lora-network-server: Parsing 1 rx packets
Oct 20 08:03:48 mtcdt user.warn lora-network-server: Recv'd frame failed CRC check
Oct 20 08:03:49 mtcdt user.info lora-network-server: Parsing 1 rx packets
Oct 20 08:03:49 mtcdt user.warn lora-network-server: Recv'd frame failed CRC check

 

CRC errors would explain why the received data is not being seen.

 

 

So: has anyone actually got this working with a Conduit gateway using the current firmware?

 

The fact that the behaviour is the same for the 2 boards suggests that it's a configuration issue rather than a HW fault.

 

I also have some MultiTech mDot modules, and they communicated with the Conduit as originally configured.

Outcomes