LoRa just CRC error

[Tom]

Hello!

We have a small LoRa network. We had some problem with the IP67 Base station(we have two of them), and they’ve got firmware and software upgraded in warranty. We got them back last week, and tried to reconfigure based on the manuals.

We had parking sensors configured with it before. After the upgrade, we cannot get it to work again.

15:10:9:545|INFO| GW:00-80-00-00-00-00-c1-ca|FRAME-RX|Parsing 1 packets
15:10:9:546|WARNING| GW:00-80-00-00-00-00-c1-ca|FRAME-RX|CRC-ERROR

All packets are shown as CRC error. Didn’t see any join requests in the log.
Network parameters (eui and key) are set back to previous one.

Added devices through AEP and mLinux too with AppEUI and APPkey for OTAA join, cleared whitelist, readded them and still no success.

What can we do without reconfiguring the parking sensors?

yrs.
Tom

[Tom]

Device: MTCDT-210L
Firmware: 1.4.16
Network server: 2.0.19
Packet forwarder: 3.1.0-r11.0

EU version

[Jason Reiss]

Did you try to change the Network Mode between public/private?

[Tom]

Sure. After upgrade it was defaulted to private mts, we switched it to LoRaWAN. Tried both, private and public, and got only CRC errors. Tried to change the datarate, but it had no impact.

[Jason Reiss]

What are the recommended settings for the sensor? Public or Private?
When do you expect the sensors to send join requests?
Can they be forced to send a join request?
Do you have any other end-device you can test with?

The join requests should be sent on the three default frequencies, 868.1, 868.3 and 868.5

You could try to set Additional Channels to 869.5 or 867.5
Although the channels will be sent to the devices in the Join Accept no matter the setting.

CRC errors can be caused by noise, they are not necessarily corrupted LoRa packets. They are not a sure indicator that the end-device is transmitting.

[Author]

Posts