JN5179 RSSI issue with SKY66112 PA

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

JN5179 RSSI issue with SKY66112 PA

1,165 Views
hiteshgambhava
Contributor III

Hi,

We are using SKY66112 - PA with JN5179 chipset for Antenna diversity features. We are not able to exact match GPIO connection between SKY and JN5179 as per reference M16 module.

RFTX and RFRX connected on DIO3 and DIO2 of JN5179 respectively as per JN-UG-3118 application note, with this configuration we are facing the issue of poor RSSI value with "JN5179_001_M16_FCC" module configuration. When we stand alone configure SKY66112 in receive mode then we get good RSSI value.

Pinconfiguration between JN5179 and SKY66112

1. CRX ---> DIO2

2. CTX ---> DIO3

3. CSD ---> DIO17

4. CHL ----> DIO18

5. ANT_SEL ---> DIO1

6. CPS ---->DIO15

Please let us know what could be the exact configuration for M16 module with HP Tx and Rx_LNA mode OR share if you have any steps to configure M16 module for above GPIO settings.

Your prompt response will be highly appreciated.

Thanks!

Labels (1)
0 Kudos
4 Replies

695 Views
hiteshgambhava
Contributor III

Hi Mario,

During our testing, we also found Tx range issue with lower RSSI value with a combination of JN5179+SKY66112. We are getting only 150ft Line of Sight range with 20dbm Tx power. To give a little background:

  • We have used meandered inverted F PCB trace antenna in our design and did impedance matching with help of VNA (getting 52E impedance for low, mid and high channel), Also getting return loss (S11 parameter) almost -14dbm for all three channel.
  • We measured Tx power on antenna feed point on a spectrum analyzer and getting 19.4dbm peak power.

We also tested on M16 EVM and getting the almost similar range. Our target is to achieve atleast 200ft LOS distance (our competitor product is getting this much distance and have used other manufacturer Zigbee module).

Please help/suggests where we can look into the design to increase range. Also if possible let us know where we could go wrong in design which limits tx range.

Thanks!

0 Kudos

695 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi Hitesh,

Could you please take a look the next post?

https://community.nxp.com/thread/455276 

Note: As you know, the JN5179 has a limited support.

Best Regards,

Mario

0 Kudos

695 Views
hiteshgambhava
Contributor III

Hi Mario,

Thanks for the response.

We also want to test our module using Production test firmware "JN-AN-1210-JN517x-Customer-Module-Evaluation-Tool" , so we need to tweak this GPIOs for the production test firmware. As we see the "JN-AN-1210-JN517x-Customer-Module-Evaluation-Tool" firmware uses JN-SW-4263 production test API which resides in a library so we do not have access to the core functions.

How can we set the GPIOs in that firmware? do you have any guide or reference for that?

Thanks!

0 Kudos

695 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi Hitesh,

You can take a look at JN517x Integrated Peripherals API User Guide

5.1 Using the DIOs

https://www.nxp.com/docs/en/user-guide/JN-UG-3118.pdf 

 button example:

PUBLIC bool_t APP_bButtonInitialise(void)
{
    /* Set DIO lines to inputs with buttons connected */
    vAHI_DioSetDirection(APP_BUTTONS_DIO_MASK, 0);

    /* Turn on pull-ups for DIO lines with buttons connected */
    vAHI_DioSetPullup(APP_BUTTONS_DIO_MASK, 0);

    /* Set the edge detection for falling edges */
    vAHI_DioInterruptEdge(0, APP_BUTTONS_DIO_MASK);

    /* Enable interrupts to occur on selected edge */
    vAHI_DioInterruptEnable(APP_BUTTONS_DIO_MASK, 0);

    uint32 u32Buttons = u32AHI_DioReadInput() & APP_BUTTONS_DIO_MASK;
    if (u32Buttons != APP_BUTTONS_DIO_MASK)
    {
        return TRUE;
    }
    return FALSE;
}

Best Regards,

Mario

0 Kudos