nabil islam

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • February 17, 2017 at 2:40 am in reply to: Lora server does not start after update #17284
    nabil islam
    Participant

    indeed, I’ve installed the AEP version on mlinux. Now I’ve removed it and intalled the correct version it’s working

    Thanks.

    February 9, 2017 at 4:00 am in reply to: Always receiving failed CRC and failed MIC packages #16847
    nabil islam
    Participant

    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

  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)