Mdot Join failure for Australian channel plan!

Home › Forums › mDot/xDot › Mdot Join failure for Australian channel plan!

Tagged: 

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • June 19, 2018 at 5:30 pm #23912
    Ajay K
    Participant

    We have a gateway configured for the AU915 channel plan and is configured for Private Lorawan mode. Although I see an additional option of private mts and not sure what that option provides?

    Anyway the mdot executes the join request and although, the conduit reports that the mdot joined successfully, the MDot reports a join failure and all i see in the logs is receive time outs. The radio node and the gateway are right next to each other just may be a few feet away.

    We have Ack’s enabled and in AUTO_OTA mode.

    Here is some part of the logs that we see in the serial o/p.

    6/19/2018 2:37:54 PM: [DEBUG] Current LORA Network name: multitechgw1

6/19/2018 2:37:54 PM: [DEBUG] Current LORA Frequency Sub-Band: 4

6/19/2018 2:37:54 PM: [TRACE] ADR Turned ON....

6/19/2018 2:37:54 PM: [TRACE] saving config...

6/19/2018 2:37:54 PM: [DEBUG] Saving config to flash

6/19/2018 2:37:54 PM: [DEBUG] Settings not changed, nothing to save

6/19/2018 2:37:54 PM: [TRACE] Attempting to join orsat network....

6/19/2018 2:37:54 PM: [DEBUG] getNextTxMs: 0

6/19/2018 2:37:54 PM: [TRACE] Initiating join...

6/19/2018 2:37:54 PM: [TRACE] Join Network - Auto OTA

6/19/2018 2:37:54 PM: [TRACE] Join attempt #1

6/19/2018 2:37:54 PM: [TRACE] Disabling auto sleep mode

6/19/2018 2:37:54 PM: [INFO] Send join request RxDelay: 5 Rx1Offset: 0 Rx2Freq: 923300000 Rx2Dr: 8

6/19/2018 2:37:54 PM: [TRACE] DevEUI: 008000000001226d

6/19/2018 2:37:54 PM: [TRACE] AppEUI: 22247f3087bde45a

6/19/2018 2:37:54 PM: [TRACE] AppKey: f61d7caef5a416332e5f7267129ca229

6/19/2018 2:37:54 PM: [INFO] Configure radio for TX

6/19/2018 2:37:54 PM: [DEBUG] Session pwr: 20 ant: 3 max: 30

6/19/2018 2:37:54 PM: [DEBUG] Radio Power index: 20 output: 19 total: 22

6/19/2018 2:37:54 PM: [DEBUG] TX PWR: 20 DR: 0 SF: 12 BW: 0 CR: 1 PL: 8 CRC: 1 IQ: 0

6/19/2018 2:37:54 PM: [TRACE] Sending 23 bytes

6/19/2018 2:37:54 PM: [TRACE] Number of available channels: 8

6/19/2018 2:37:54 PM: [DEBUG] Using channel 29 : 921000000

6/19/2018 2:37:54 PM: [INFO] Configure radio for TX

6/19/2018 2:37:54 PM: [DEBUG] Session pwr: 20 ant: 3 max: 21

6/19/2018 2:37:54 PM: [DEBUG] Radio Power index: 20 output: 19 total: 22

6/19/2018 2:37:54 PM: [DEBUG] TX PWR: 20 DR: 0 SF: 12 BW: 0 CR: 1 PL: 8 CRC: 1 IQ: 0

6/19/2018 2:37:54 PM: [INFO] Configure radio for TX

6/19/2018 2:37:54 PM: [DEBUG] Session pwr: 20 ant: 3 max: 21

6/19/2018 2:37:54 PM: [DEBUG] Radio Power index: 20 output: 19 total: 22

6/19/2018 2:37:54 PM: [DEBUG] TX PWR: 20 DR: 0 SF: 12 BW: 0 CR: 1 PL: 8 CRC: 1 IQ: 0

6/19/2018 2:37:54 PM: [DEBUG] mDotEvent - TxStart

6/19/2018 2:37:55 PM: [DEBUG] mDotEvent - TxDone

6/19/2018 2:37:55 PM: [TRACE] Event: OK

6/19/2018 2:37:55 PM: [TRACE] Flags Tx: 1 Rx: 0 RxData: 0 RxSlot: 0 LinkCheck: 0 JoinAccept: 0

6/19/2018 2:37:55 PM: [TRACE] Info: Status: 0 ACK: 0 Retries: 0 TxDR: 0 RxPort: 0 RxSize: 0 RSSI: 0 SNR: 0 Energy: 0 Margin: 0 Gateways: 0

6/19/2018 2:38:00 PM: [INFO] Rx Window 1

6/19/2018 2:38:01 PM: [DEBUG] mDotEvent - RxTimeout on Slot 1

6/19/2018 2:38:01 PM: [TRACE] Event: RX_TIMEOUT

6/19/2018 2:38:01 PM: [TRACE] Flags Tx: 0 Rx: 0 RxData: 0 RxSlot: 1 LinkCheck: 0 JoinAccept: 0

6/19/2018 2:38:01 PM: [TRACE] Info: Status: 3 ACK: 0 Retries: 0 TxDR: 0 RxPort: 0 RxSize: 0 RSSI: 0 SNR: 0 Energy: 0 Margin: 0 Gateways: 0

6/19/2018 2:38:01 PM: [INFO] Rx Window 2

6/19/2018 2:38:02 PM: [DEBUG] mDotEvent - RxTimeout on Slot 2

6/19/2018 2:38:02 PM: [TRACE] Event: RX_TIMEOUT

6/19/2018 2:38:02 PM: [TRACE] Flags Tx: 0 Rx: 0 RxData: 0 RxSlot: 2 LinkCheck: 0 JoinAccept: 0

6/19/2018 2:38:02 PM: [TRACE] Info: Status: 3 ACK: 0 Retries: 0 TxDR: 0 RxPort: 0 RxSize: 0 RSSI: 0 SNR: 0 Energy: 0 Margin: 0 Gateways: 0

6/19/2018 2:38:02 PM: [ERROR] Failed to join network

6/19/2018 2:38:02 PM: [ERROR] Failed to join network Error Code: -4, Error: Join Error, Join Attempts: 1

6/19/2018 2:38:02 PM: [DEBUG] getNextTxMs: 1000

6/19/2018 2:38:03 PM: [TRACE] Initiating join...

6/19/2018 2:38:03 PM: [TRACE] Join Network - Auto OTA

6/19/2018 2:38:03 PM: [TRACE] Join attempt #2

6/19/2018 2:38:03 PM: [TRACE] Disabling auto sleep mode

6/19/2018 2:38:03 PM: [INFO] Send join request RxDelay: 5 Rx1Offset: 0 Rx2Freq: 923300000 Rx2Dr: 8

6/19/2018 2:38:03 PM: [TRACE] DevEUI: 008000000001226d

6/19/2018 2:38:03 PM: [TRACE] AppEUI: 22247f3087bde45a

6/19/2018 2:38:03 PM: [TRACE] AppKey: f61d7caef5a416332e5f7267129ca229

6/19/2018 2:38:03 PM: [INFO] Configure radio for TX

6/19/2018 2:38:03 PM: [DEBUG] Session pwr: 20 ant: 3 max: 21

6/19/2018 2:38:03 PM: [DEBUG] Radio Power index: 20 output: 19 total: 22

6/19/2018 2:38:03 PM: [DEBUG] TX PWR: 20 DR: 4 SF: 8 BW: 0 CR: 1 PL: 8 CRC: 1 IQ: 0

6/19/2018 2:38:03 PM: [TRACE] Sending 23 bytes

6/19/2018 2:38:03 PM: [TRACE] Number of available channels: 8

6/19/2018 2:38:03 PM: [DEBUG] Using channel 25 : 920200000

6/19/2018 2:38:03 PM: [INFO] Configure radio for TX

6/19/2018 2:38:03 PM: [DEBUG] Session pwr: 20 ant: 3 max: 21

6/19/2018 2:38:03 PM: [DEBUG] Radio Power index: 20 output: 19 total: 22

6/19/2018 2:38:03 PM: [DEBUG] TX PWR: 20 DR: 4 SF: 8 BW: 0 CR: 1 PL: 8 CRC: 1 IQ: 0

6/19/2018 2:38:03 PM: [INFO] Configure radio for TX

6/19/2018 2:38:03 PM: [DEBUG] Session pwr: 20 ant: 3 max: 21

6/19/2018 2:38:03 PM: [DEBUG] Radio Power index: 20 output: 19 total: 22

6/19/2018 2:38:03 PM: [DEBUG] TX PWR: 20 DR: 4 SF: 8 BW: 0 CR: 1 PL: 8 CRC: 1 IQ: 0

6/19/2018 2:38:03 PM: [DEBUG] mDotEvent - TxStart

6/19/2018 2:38:03 PM: [DEBUG] mDotEvent - TxDone

6/19/2018 2:38:03 PM: [TRACE] Event: OK

6/19/2018 2:38:03 PM: [TRACE] Flags Tx: 1 Rx: 0 RxData: 0 RxSlot: 0 LinkCheck: 0 JoinAccept: 0

6/19/2018 2:38:03 PM: [TRACE] Info: Status: 0 ACK: 0 Retries: 0 TxDR: 4 RxPort: 0 RxSize: 0 RSSI: 0 SNR: 0 Energy: 0 Margin: 0 Gateways: 0

6/19/2018 2:38:08 PM: [INFO] Rx Window 1

6/19/2018 2:38:08 PM: [DEBUG] mDotEvent - RxTimeout on Slot 1

6/19/2018 2:38:08 PM: [TRACE] Event: RX_TIMEOUT

6/19/2018 2:38:08 PM: [TRACE] Flags Tx: 0 Rx: 0 RxData: 0 RxSlot: 1 LinkCheck: 0 JoinAccept: 0

6/19/2018 2:38:08 PM: [TRACE] Info: Status: 3 ACK: 0 Retries: 0 TxDR: 4 RxPort: 0 RxSize: 0 RSSI: 0 SNR: 0 Energy: 0 Margin: 0 Gateways: 0

6/19/2018 2:38:09 PM: [INFO] Rx Window 2

6/19/2018 2:38:09 PM: [DEBUG] mDotEvent - RxTimeout on Slot 2

6/19/2018 2:38:09 PM: [TRACE] Event: RX_TIMEOUT

6/19/2018 2:38:09 PM: [TRACE] Flags Tx: 0 Rx: 0 RxData: 0 RxSlot: 2 LinkCheck: 0 JoinAccept: 0

6/19/2018 2:38:09 PM: [TRACE] Info: Status: 3 ACK: 0 Retries: 0 TxDR: 4 RxPort: 0 RxSize: 0 RSSI: 0 SNR: 0 Energy: 0 Margin: 0 Gateways: 0

6/19/2018 2:38:09 PM: [ERROR] Failed to join network

6/19/2018 2:38:09 PM: [ERROR] Failed to join network Error Code: -4, Error: Join Error, Join Attempts: 2

6/19/2018 2:38:09 PM: [DEBUG] getNextTxMs: 0

6/19/2018 2:38:10 PM: [TRACE] Initiating join...

6/19/2018 2:38:10 PM: [TRACE] Join Network - Auto OTA

6/19/2018 2:38:10 PM: [TRACE] Join attempt #3

6/19/2018 2:38:10 PM: [TRACE] Disabling auto sleep mode

6/19/2018 2:38:10 PM: [INFO] Send join request RxDelay: 5 Rx1Offset: 0 Rx2Freq: 923300000 Rx2Dr: 8

6/19/2018 2:38:10 PM: [TRACE] DevEUI: 008000000001226d

6/19/2018 2:38:10 PM: [TRACE] AppEUI: 22247f3087bde45a

6/19/2018 2:38:10 PM: [TRACE] AppKey: f61d7caef5a416332e5f7267129ca229

6/19/2018 2:38:10 PM: [INFO] Configure radio for TX

6/19/2018 2:38:10 PM: [DEBUG] Session pwr: 20 ant: 3 max: 21

6/19/2018 2:38:10 PM: [DEBUG] Radio Power index: 20 output: 19 total: 22

6/19/2018 2:38:10 PM: [DEBUG] TX PWR: 20 DR: 0 SF: 12 BW: 0 CR: 1 PL: 8 CRC: 1 IQ: 0

    Thanks,
    Ajay

    June 20, 2018 at 6:44 am #23916
    Jason Reiss
    Keymaster

    Looks like you have AEP 1.4.16
    What version of mDot libarary are you using?

    Try Private MTS mode. Unless you are using the libmDot-dev-mbed5 library there is not a compatible mode on the mDot. This is the legacy private mode for mDot v3.0.0 and before. The downlink channels differ from LoRaWAN, they are fixed according to frequencySubBand setting.

    Introduction to LoRa

    Private LoRaWAN mode will have downlink channels according to the protocol using the private network sync word.

    June 20, 2018 at 10:40 am #23942
    Ajay K
    Participant

    Hi Jason,

    Thanks for your response. We have installed the latest gateway software. It was on private mts mode earlier and then I switched it to private mode, because the mdot wasn’t able to join in that private mts mode, although in both modes the conduit kept indicating that the mdot successfully joined, but as mentioned earlier the mdot has receive timeouts and indicates a join failure all the time.

    We have two versions of the custom firmware, one which is built using mdot sdk 2.0.16-1 and the other built with 3.0.0 production version. So are you saying for both these firmware versions i need to set it in “private” mode and not “private mts” mode? If so I have already done that.

    Also in the 3.0.0 build do i need to set the channel plan explicitly. I have done that too, just because the mdot getInstance method required that and I have set it to AU915 channel plan.

    Thanks,
    Ajay.

    June 20, 2018 at 10:49 am #23943
    Ajay K
    Participant

    Hi Jason,

    Thanks for your response. We have installed the latest gateway software. It was on private mts mode earlier and then I switched it to private mode, because the mdot wasn’t able to join in that private mts mode, although in both modes the conduit kept indicating that the mdot successfully joined, but as mentioned earlier the mdot has receive timeouts and indicates a join failure all the time.

    We have two versions of the custom firmware, one which is built using mdot sdk 2.0.16-1 and the other built with 3.0.0 production version. So are you saying for both these firmware versions i need to set it in “private” mode and not “private mts” mode? If so I have already done that.

    Also in the 3.0.0 build do i need to set the channel plan explicitly. I have done that too, just because the mdot getInstance method required that and I have set it to AU915 channel plan. On the version prior to 3.0.0 mdot sdk, I am guessing I don’t have to select a channel plan?

    Thanks,
    Ajay.

    June 20, 2018 at 10:54 am #23944
    Jason Reiss
    Keymaster

    2.0.16 and 3.0.0 versions only have ability to do the Private MTS and Public LoRaWAN modes available on AEP 1.4.16

    The other thing to check is the Join Delay it must match on Conduit and End-device.

    AT+JD

    See troubleshooting guide for more info.
    http://www.multitech.net/developer/wp-content/uploads/downloads/2018/04/LoRaWANTroubleShootingGuide-04132018.pdf

    June 20, 2018 at 11:42 am #23945
    Ajay K
    Participant

    Do you have to set the join delay explicitly in the mdot code or is there a default. Currently the join delay for private mts mode is set to 1 second on the conduit, should I be setting this join delay explcitly in the mdot? I am not sure what is going on here shouldn’t an upgrade to the conduit firmware not disrupt what has been working for so long and since we haven’t changed the mdot custom firmware over a while now?

    After upgrading our US version of the conduit to the latest firmware, even the join failures have started to replicate. Is there a way to revert the conduit version to the previous version of the gateway?

    Thanks,
    Ajay.

    June 20, 2018 at 11:42 am #23946
    Ajay K
    Participant

    Also I forgot to mention previously we have ADR enabled as well.

    June 20, 2018 at 4:24 pm #23951
    Ajay K
    Participant

    Hi Jason,

    An update to the Australian channel plan issue and also the US Plan. When we reverted back to the Conduit firmware to 1.4.3 and our application firmware for US Channel connected immediately with the 2.0.16 and 3.0.0 Prod MDOT SDK. However for the Australian Channel Plan version of our Application firmware, I could only get it join with 3.0.0 SDK version of the mDot and work consistently.

    Does this anyway shed a light as to why our application firmware doesn’t work with Conduit firmware version 1.4.16?

    Thanks,
    Ajay

    June 21, 2018 at 8:56 am #23956
    Jason Reiss
    Keymaster

    The join delay should be set explicitly on the end-device to match the network.

    The upgrade to AEP-1.4.16 should be backward compatible with 2.0.16 and 3.0.0. The Private/Public network setting and Join Delay should be preserved during the upgrade and operate on the same frequencies. AEP-1.4.16 does support the LoRaWAN 1.0.2 datarates DR0-DR6 for ADR, these will be mismatched in ADR commands sent from the network server to the 2.0.16 and 3.0.0 end-devices.

    Min/Max datarates can be updated on the Conduit to accommodate the older firmware, Max DR should not be set above 4 until all end-devices are updated to the next release or dev libraries.

    Private MTS mode is provided for end-devices with 2.0.16 and 3.0.0 that are set with AT+PN=0 or setPublicNetwork(false) in AU/US channel plans.

    June 21, 2018 at 3:23 pm #23964
    Ajay K
    Participant

    Thanks a lot Jason for the detailed explanation. I will try changing or limiting the number of available DRs on the conduit and see if that helps.

    When is the next version of the mdot sdk planned to be released?

    Thanks,
    Ajay.

  • Author
    Posts
Viewing 10 posts - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.