Skip to content

releases pre certification results

Miguel Luis edited this page Nov 24, 2020 · 15 revisions

Releases pre-certification results

Introduction

Bellow one can find the pre-certification test results for a given release.

Starting from release 4.4.2 the rule stating that a release only happened once 2 test houses confirmed the pre-certification results has been changed in order to speedup the release process.

The LoRa-Alliance pre-certification tool LCTT is the tool used to run the pre-certification tests.

Releases

Pre-Release Version 4.5.0-rc.1

Release date

2020-11-24

LoRaWAN version

1.0.4

Pre-certification status

The pre-certification tests are run with a NucleoL073 + SX1261MBXBAS platform using the LoRaMac/periodic-uplink-lpp example.

Region Verdict LCTT (v3.0.0_R1) # Test houses Comments
EU868 PASS [x] 0 -
US915 PASS [x] 0 -
CN779 Not tested [ ] 0 No certification specification
EU433 Not tested [ ] 0 No certification specification
AU915 PASS [x] 0 -
CN470 Not tested [ ] 0 No certification specification
AS923 PASS [x] 0 -
KR920 PASS [x] 0 -
IN865 PASS [x] 0 -

Release Version 4.4.5

Release date

2020-10-14

LoRaWAN version

1.0.3

Pre-certification status

The pre-certification tests are run with a NucleoL476 + SX1261MBXBAS platform using the LoRaMac/periodic-uplink-lpp example.

Region Verdict LCTT # Test houses Comments
EU868 PASS [x] 0 -
US915 Not tested [ ] 0 -
CN779 Not tested [ ] 0 No certification specification
EU433 Not tested [ ] 0 No certification specification
AU915 Not tested [ ] 0 No certification specification
CN470 Not tested [ ] 0 No certification specification
AS923 Not tested [ ] 0 -
KR920 Not tested [ ] 0 -
IN865 Not tested [ ] 0 -

Release Version 4.4.4

Release date

2020-05-26

LoRaWAN version

1.0.3

Pre-certification status

The pre-certification tests are run with a NucleoL476 + SX1261MBXBAS platform using the LoRaMac/classA example.

Region Verdict LCTT # Test houses Comments
EU868 PASS [x] 0 -
US915 Not tested [ ] 0 -
CN779 Not tested [ ] 0 No certification specification
EU433 Not tested [ ] 0 No certification specification
AU915 Not tested [ ] 0 No certification specification
CN470 Not tested [ ] 0 No certification specification
AS923 Not tested [ ] 0 -
KR920 Not tested [ ] 0 -
IN865 Not tested [ ] 0 -

Release Version 4.4.3

Release date

2019-12-17

LoRaWAN version

1.0.3

Pre-certification status

The pre-certification tests have been run with a NucleoL476 + SX1261MBXBAS platform using the LoRaMac/classA example.

Region Verdict RWC5020A LCTT # Test houses Comments
EU868 PASS [x] [x] 0 -
US915 Not tested [ ] [ ] 0 -
CN779 Not tested [ ] [ ] 0 No certification specification
EU433 Not tested [ ] [ ] 0 No certification specification
AU915 Not tested [ ] [ ] 0 No certification specification
CN470 Not tested [ ] [ ] 0 No certification specification
AS923 Not tested [ ] [ ] 0 -
KR920 Not tested [ ] [ ] 0 -
IN865 Not tested [ ] [ ] 0 -

Release Version 4.4.2

Release date

2019-07-19

LoRaWAN version

1.0.3

Pre-certification status

The pre-certification tests have been run with a NucleoL476 + SX1261MBXBAS platform using the LoRaMac/classA example.

Region Verdict RWC5020A LCTT # Test houses Comments
EU868 PASS [x] [ ] 0 -
US915 PASS [x] [ ] 1 See Note 1 and Note 2 below
CN779 Not tested [ ] [ ] 0 No certification specification
EU433 Not tested [ ] [ ] 0 No certification specification
AU915 Not tested [ ] [ ] 0 No certification specification
CN470 Not tested [ ] [ ] 0 No certification specification
AS923 PASS [x] [ ] 0 -
KR920 PASS [x] [ ] 0 -
IN865 PASS [x] [ ] 1 See Note 3 below

Note 1: US915 Join procedure tests 2.1 and 2.2 fail due to the fact that the US915 region test specification hasn't yet been updated to be in sync with the latest regional parameters specification.
The issue is that the current released test specification mandates the tools to check that the end-device alternatively uses DR0 and DR4 to issue JoinReq frames while in the latest regional parameters specification the end-device can use other algorithms for the channels selection. The tool should only check that the end-device makes use of both datarates (DR0 and DR4) and not in which order.

Note 2: The Redwoodcomm RWC5020A tool only supports 8 channels while the specification mandates the usage of 64 channels for US915 regions. In order to run the tests using this tool the ClassA end-device example has been modified as follows:

Click to show the code changes!
/**
 * Main application entry point.
 */
int main( void )
{
    ...
                mibReq.Type = MIB_PUBLIC_NETWORK;
                mibReq.Param.EnablePublicNetwork = LORAWAN_PUBLIC_NETWORK;
                LoRaMacMibSetRequestConfirm( &mibReq );

                mibReq.Type = MIB_ADR;
                mibReq.Param.AdrEnable = LORAWAN_ADR_ON;
                LoRaMacMibSetRequestConfirm( &mibReq );

#if defined( REGION_EU868 ) || defined( REGION_RU864 ) || defined( REGION_CN779 ) || defined( REGION_EU433 )
                LoRaMacTestSetDutyCycleOn( LORAWAN_DUTYCYCLE_ON );
#endif
                mibReq.Type = MIB_SYSTEM_MAX_RX_ERROR;
                mibReq.Param.SystemMaxRxError = 20;
                LoRaMacMibSetRequestConfirm( &mibReq );
// BEGIN - RWC5020A US915 tests changed code
#if defined( REGION_US915 )
                // Enabling 1st block of 8 channels (0-7) + channel 64
                uint16_t channelMask[] = { 0x00FF, 0x0000, 0x0000, 0x0000, 0x0001, 0x0000};
                mibReq.Type = MIB_CHANNELS_MASK;
                mibReq.Param.ChannelsMask = channelMask;
                LoRaMacMibSetRequestConfirm( &mibReq );
                mibReq.Type = MIB_CHANNELS_DEFAULT_MASK;
                mibReq.Param.ChannelsDefaultMask = channelMask;
                LoRaMacMibSetRequestConfirm( &mibReq );
#endif
// END - RWC5020A US915 tests changed code
                LoRaMacStart( );

                mibReq.Type = MIB_NETWORK_ACTIVATION;
                status = LoRaMacMibGetRequestConfirm( &mibReq );
    ...
}

Note 3: On Redwoodcomm RWC5020A tool some tests for IN865 fail. Although a test house confirmed that the same failing tests were successful on their test setup.

The issue is currently under investigation.


Release Version 4.4.1

Release date

2018.03.07

LoRaWAN version

1.0.2 - Last version which is based on LoRaWAN v1.0.2

Pre-certification status
Region Verdict # Test houses Comments
EU868 PASS 2 -
US915 PASS 2 -
CN779 PASS 1 No certification specification - tests based on EU868 certification
EU433 PASS 1 No certification specification - tests based on EU868 certification
AU915 PASS 0 No certification specification - tests based on US915 certification
CN470 Not tested 0 No certification specification
AS923 PASS 2 -
KR920 PASS 1 -
IN865 PASS 2 -

Release Version 4.4.0

Release date

2017.09.08

LoRaWAN version

1.0.2

Pre-certification status
Region Verdict # Test houses Comments
EU868 PASS 2 -
US915 PASS 2 -
CN779 PASS 1 No certification specification - tests based on EU868 certification - All tests PASS except 1. Join Accept Rx2 parameters not being applied (under investigation)
EU433 PASS 1 No certification specification - tests based on EU868 certification
AU915 Not tested 0 No certification specification
CN470 Not tested 0 No certification specification
AS923 PASS 2 -
KR920 PASS 2 -
IN865 PASS 1 No certification specification - tests based on EU868 certification

Release Version 4.3.2

Release date

2017.04.19

LoRaWAN version

1.0.1 - Last version which is based on LoRaWAN v1.0.1

Pre-certification status
Region Verdict
EU868 PASS
US915 PASS

Release Version 4.3.1

Release date

2017.02.27

LoRaWAN version

1.0.1

Pre-certification status
Region Verdict
EU868 PASS
US915 PASS

Release Version 4.3.0

Release date

2016.06.22

LoRaWAN version

1.0.1

Pre-certification status
Region Verdict
EU868 PASS
US915 PASS

Release Version 4.2.0

Release date

2016.05.13

LoRaWAN version

1.0.0

Pre-certification status
Region Verdict
EU868 PASS
US915 PASS
Clone this wiki locally