Always receiving failed CRC and failed MIC packages

[Eduardo Garcia]

Hello:

I am always receiving CRC check errors and MIC check errors from packages sent from a node that succesfully was connected and sending data before. I was the one that made a post on the “Conduit Manual Join to SX1276 MBED (Third party device)” thread, and with the help of Jason I could get the module connected.

I moved to work on other projects, and returned to testing the Multiconnect Conduit today. But now the node I had connected to the Lora always fails. The log only shows messages as follows:

10:58:9:892|INFO| Parsing 1 rx packets
10:58:9:892|WARNING| Recv'd frame failed CRC check

Are there some commands I could use as to debug what is going on? Like reading the raw data that the Conduit is getting? I also tried to remove the node, but I could not find a command to do so.

Thank you for your help,

-Ed

[Eduardo Garcia]

I also get the following:

11:8:51:418|INFO| Addr: 33:33:33:33 MIC Check: failed
11:8:51:418|WARNING| Dropping packet, Addr: 33:33:33:33 Duplicate: no
11:9:8:351|INFO| Parsing 1 rx packets
11:9:8:353|INFO| SeqNo: 00040000 PrevSeqNo: 00000000 Duplicate: no

[Eduardo Garcia]

I changed my device’s address from 33:33:33:33 to 33:33:33:31 I can receive the messages. Nothing else is different! What can be the cause of this, any idea?

[Brandon Bayer]

Eduardo,

When you changed the device address, did you do the node add command again?

I suspect your address lease expired. After network["leasetime"] in lora-network-server.conf (minutes), the node will be purged from the DB. If the device then transmits again, the server will reject it because the address lease has expired.

-Brandon

• This reply was modified 8 years, 5 months ago by Brandon Bayer.

[Eduardo Garcia]

Hi Brandon:

I did do the node add again after changing address, and with the new address it is working as of now. How can I remove the node of the expired address lease? Is it adding it again?

Thanks,

-Ed

[Brandon Bayer]

Eduardo,

Ok, then it probably was a lease related issue. Do node list to see if it’s still in the db. I think you can remove them with node remove.

-Brandon

[Eduardo Garcia]

Do you know the syntax of node remove or could you give me an example? I have tried node remove but I get a syntax error. I tried node remove 33:33:33:33 with no luck!

-Ed

[Eduardo Garcia]

It is also still on the DB

[Brandon Bayer]

Eduardo,

My mistake! The command is actually
node delete <NETWORK ADDRESS>

-Brandon

• This reply was modified 8 years, 5 months ago by Brandon Bayer.

[Eduardo Garcia]

Thanks Brandon!

Mysteriously the Conduit had all nodes erased this morning! But I will keep this command in mind.

Thanks!

[Claude Favreau]

Hi,

I got the same issue and I don’t knwow why. I just upgraded the firmware of the conduit to 1.3.3.`
19:5:41:882|INFO|Parsing 1 rx packets
19:5:41:883|WARNING|Recv'd frame failed CRC check
19:5:44:512|TRACE|Parse downstream message 12 bytes
19:5:44:513|TRACE|Gateway 00:80:00:00:00:00:bf:b5 seen IP address 127.0.0.1:50143
19:5:54:522|TRACE|Parse downstream message 12 bytes
`

I already tried to delete and add again the node. By the past I already received data from this node. Someone has an idea how to solve it or what is the origin of this issue?

• This reply was modified 7 years, 3 months ago by Claude Favreau.
• This reply was modified 7 years, 3 months ago by Claude Favreau.

[nabil islam]

hi, i have the same issue : in the DB i just keep my beacon filled with it’s informations, and when i try to connect it to the conduit dateway, here’s the log i get :

9:54:32:272|INFO| Queue join response 33 bytes
9:54:32:293|INFO| Send Join Accept – EUI: 70-b3-d5-32-60-00-01-e6 ADDR: 06000002
9:54:32:293|INFO| Schedule TX Time on air: 81 ms
9:54:33:22|INFO| Frame transmitted to 06:00:00:02 via GW (00:80:00:00:a0:00:01:d8 Chan LC2 127.0.0.1:46519) Seq# 0
9:54:33:31|INFO| Band: 1 Time off air: 7100 ms
9:54:33:31|INFO| Transmit UDP message to Gateway 206 bytes
9:54:37:615|INFO| Parsing 1 rx packets
9:54:37:615|WARNING| Recv’d frame failed CRC check
9:56:2:621|INFO| Parsing 1 rx packets
9:56:2:622|INFO| Received join request
9:56:31:713|INFO| Parsing 1 rx packets
9:56:31:714|INFO| Received join request
9:56:50:692|INFO| Parsing 1 rx packets
9:56:50:692|WARNING| Recv’d frame failed CRC check
9:57:7:549|INFO| Parsing 1 rx packets
9:57:7:550|INFO| Received join request

I’ve tryed a join method with OTAA since abp doesn’t work and crash my lora server when i add a node

the leasetime is at 0 so it shouldn’t provoke a timeout, but i still fail to connect a node to the gateway with this CRC error message

[Bryan Tran]

Hi nabil islam/Claude Favreau,

Please create support case at – http://www.multitech.com/support/support for further trouble shooting your issue.

Thanks,

BT

[AMIN BOUFELFEL]

hello evryone 🙂
Claude Favreau, i’m having the same issue as you.
i have no problem with the join method, it’s that after joining i can’t receive any sent packet from my mdot due to the “CRC fail check”
plz, have anyone found a solution yet ?

Apr 19 17:33:22 mtcdt user.debug lora-network-server: Gateway 00:80:00:00:00:00:c2:fa seen IP address 127.0.0.1:35048
Apr 19 17:33:31 mtcdt user.debug lora-network-server: Parse upstream message 508 bytes
Apr 19 17:33:31 mtcdt user.debug lora-network-server: Gateway 00:80:00:00:00:00:c2:fa seen
Apr 19 17:33:31 mtcdt user.info lora-network-server: Parsing 1 rx packets
Apr 19 17:33:31 mtcdt user.warn lora-network-server: Recv’d frame failed CRC check
Apr 19 17:33:32 mtcdt user.debug lora-network-server: Parse downstream message 12 bytes
Apr 19 17:33:32 mtcdt user.debug lora-network-server: Gateway 00:80:00:00:00:00:c2:fa seen IP address 127.0.0.1:35048
Apr 19 17:33:42 mtcdt user.debug lora-network-server: Parse downstream message 12 bytes
Apr 19 17:33:42 mtcdt user.debug lora-network-server: Gateway 00:80:00:00:00:00:c2:fa seen IP address 127.0.0.1:35048
Apr 19 17:33:53 mtcdt user.debug lora-network-server: Parse downstream message 12 bytes

• This reply was modified 7 years, 1 month ago by AMIN BOUFELFEL.

[Author]

Posts