CCS/LAUNCHXL-CC1310: Sub-1 GHz forum

Shubha J

Prodigy 60 points

Part Number: LAUNCHXL-CC1310
Other Parts Discussed in Thread: CC1310

Tool/software: Code Composer Studio

Hi Team,

I wanted the board to work on 868MHz, so configured as follows,

/*! Setting for Phy ID */
#define CONFIG_PHY_ID (APIMAC_GENERIC_ETSI_LRM_863_PHY_131)

in the config.h file. The board does not work with this configuration. In the sense, it nodes do not connect to the network.

The board works fine when configured to 915MHz.

I believe the board is optimized for 915MHz.

So, to work with 868MHz with the same board what is that I need to do, and could you please let me know the procedure for extending the range of it.

Thanks in advance.

Regards,

Shubha

over 6 years ago

0 Toby over 6 years ago

TI__Mastermind 35070 points

Hi,

Is this on a launchpad or a custom board?

Have you used the same CONFIG_PHY_ID on both boards?

What mode are you using (beacon, non-beacon, or frequency hopping)?

Regards,
Toby

0 Shubha J over 6 years ago in reply to Toby

Prodigy 60 points

Hi,

Yes, this is on the launchpad. And I have used the same CONFIG_PHY_ID on both the boards, it is working in non beacon mode.

Regards,

Shubha

0 Toby over 6 years ago in reply to Shubha J

TI__Mastermind 35070 points

Thank you for the details.

I tried the default examples (only changing CONFIG_PHY_ID) from the 3.10 SDK and they work.

Please try with the latest 3.20 CC1310 SDK: http://www.ti.com/tool/download/SIMPLELINK-CC13X0-SDK

0 Shubha J over 6 years ago in reply to Toby

Prodigy 60 points

Thanks Toby, that worked. I was using the older version of SDK.

It would be of a great help if you could share the procedure to extend the range.

Regards,

Shubha

0 Toby over 6 years ago in reply to Shubha J

TI__Mastermind 35070 points

Thanks for confirming.

Please refer to these related posts:
- https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/p/738471/2726375
- https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/t/675946?CC1310-CC1310-Range-Test

If you need further hardware advice on increasing range, please post another thread specifying the range you are seeing and the range you are attempting to achieve.

0 Chan100 over 6 years ago in reply to Toby

Genius 3040 points

Hi Toby,

I am using SDK version 2.10, and operating in non-beacon mode. I too have the same problem with using APIMAC_GENERIC_ETSI_LRM_863_PHY_131 but for some reasons cannot migrate to a newer SDK version as you suggested. I am using CC1310 launchpad for the sensor and a custom board as a collector. I noticed that the beaconNotifyIndCb() is not being called on the sensor side (if this observation could help). I changed the CONFIG_PHY_ID in both collector.c and sensor.c

Can you suggest how to solve this problem?

Thanks in advance

-Chandrasekhar DVS

0 Toby over 6 years ago in reply to Chan100

TI__Mastermind 35070 points

Hi,

I recommend using the latest SDK, as this is proven by Shubha to work.

Can you describe in detail how you are attempting to migrate?
You would just download the latest SDK from http://www.ti.com/tool/download/SIMPLELINK-CC13X0-SDK, then import the relevant example into CCS, build the examples, then flash them onto the hardware.

The sensor not entering beaconNotifyIndCb() indicates one of the following:
- collector did not receive the Beacon Request, and thus will not send a Beacon
- collector sends the beacon, but sensor does not receive any beacon

Since you are using a custom board, please use SmartRF Studio to determine check PER between the custom board and the launchpad. This will help determine whether it is a hardware issue or not.

Regards,
Toby

0 Chan100 over 6 years ago in reply to Toby

Genius 3040 points

Hi Toby,

The thing is, we have modified the sensor and collector codes as per our requirement and are using them in developing a product. I have taken a look at the changes between examples from SDK 2.10 and 3.10. To apply our changes in the newer SDK version, we are short of time as a demonstration has been scheduled with a client.

Let us say in the case that collector sends the beacon, but sensor does not receive any beacon, can you suggest what could be the reason?

In the meantime, I shall check PER between custom board and launchpad but can you suggest any other ways that would help me in operating 'APIMAC_GENERIC_ETSI_LRM_863_PHY_131' mode using SDK 2.10?

Thanks in advance.

-Chandrasekhar DVS

0 Chan100 over 6 years ago in reply to Toby

Genius 3040 points

Hi Toby,

Solved the issue with the aid of the following forum post.

https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/t/754297?tisearch=e2e-sitesearch&keymatch=APIMAC_GENERIC_ETSI_LRM_863_PHY_131

However the same problem occurs when I use 'APIMAC_GENERIC_CHINA_LRM_433_PHY_130'. The sensor cannot receive the beacon.

Can you suggest what can be done to be able to operate with the above CONFIG_PHY_ID?

Thanks in advance

-Chandrasekhar DVS

0 Toby over 6 years ago in reply to Chan100

TI__Mastermind 35070 points

Thanks for the update.

Since the post you referenced fixes your issue, are you using PG 2.0?

Can you provide a spectrum analyzer screenshot to see what's happening over-the-air?

0 Chan100 over 6 years ago in reply to Toby

Genius 3040 points

Hi Toby,

Sorry for the late reply. I don't know about PG 2.0(I tried searching but in vain) and also unfortunately cannot provide a spectrum analyzer screenshot. However I asked my technical head and the die version of cc1310 I am using does not support 433 MHz apparently. The board revision is 1.3 by the way

Thanks for your support.

-Chandrasekhar DVS

0 Toby over 6 years ago in reply to Chan100

TI__Mastermind 35070 points

Feel free to create another thread if you have other inquiries.

Regards,
Toby