LAUNCHXL-CC1310: RF Parameter/Frame create

Meaning that you don't have anything that you can use as a sync word in your protocol?

yes no sync word

Hi,

Have you tried using SmartRF studio for testing the performance of your protocol.

I am not sure if no sync word option is supported. But you can modify the length of preamble and syncword and have your own syncword. 

https://www.ti.com/tool/SMARTRFTM-STUDIO

Regards,

Sid

hi Sid,

I think this system used RF address, is this can replace with sync word? yes I tried with SmartRF

regards

Stanes

Hi SId,

I have found proper RF protocol that we used in exciting - product attached here.

can you please clarify me on following questions.

1. Is Preamble can be edited? - the current system used different type preamble
2. Sync word could be replaced with address that mentioned current protocol (6DF in nibbles)
3. Do I need to send checksum or there is any way to modify the checksum, because in the current systems used different checksum for different modes.
4. In any chance that we can send packets in nibble format

Thank you 

Staneslouse

Hi Staneslouse,

Could you confirm the following Phy properties in your protocol?

1. Seems to be OOK modulation.

2. Symbol rate of 1k Symbols/second.

3. Looking at the first row of bits, the data seems to be Manchester encoded.

Regards,

Sid

Hi Sid,

answers for your questions are below,

Modulation : OOK

Data rate : 2Kbps

and yes its Manchester encoded, please refer below image for more about Manchester encoding 

Kind regards

Staneslouse

CC1310 has some limitations:

Minimum preamble is 1 bit, minimum sync word is 8 bit, see smartRF studio.

You can try to do manchester coding/ encoding in FW and use part of your "preamble" as sync word. You will get some false syncs but I assume that you got that with the "old" receiver.

RF receives designed the latests 15 years are designed to use preamble (to settle the AGC, gain in the front end), and sync word to do bit/ byte sync. You will be able to receive legacy formats as you describe but with limitations in the performance since the receiver is designed to receive a different format. In TX you can always send whatever you want. 

Hi yes I can see some limitation in RF studio, I tried to find to modify the preamble and sync word in FW unfortunately, I can only export RF settings from Smart RF studio. If you have any link to go through for this FW modifications, please share with me.

Kind regards

Staneslouse

Hi Staneslouse,

SmartRF Studio is used to evaluate your protocol. What TheGhostOf is saying, which is also our recommendation is to set all your requirements on SmartRF Studio on a TX device and an RX device and use it to evaluate the protocol's performance.

Then these settings can be exported to your firmware to run the radio in the same settings, so that you get the same observed performance.

The limitations of minimum 1 bit preamble and 8bit syncword is going to be there even in the firmware. 

TheGhostOf said:

You can try to do manchester coding/ encoding in FW and use part of your "preamble" as sync word

Here TheGhostof is saying that since your have a legacy frame format you have to work with, our default settings for preamble and sync word wont work, you would likely have to modify the lengths and values to accommodate your your protocol frame.

Hope this helps.

Regards,

Sid 

Hi Sid,

Thank you for your explanation, I have tried what TheGostOf suggested setup as follow:

Preamble – 1 byte start with 1

Sync Word – 32 bits add additional 1 byte that for rest of the preamble.    

Data – used hex value as per the data bytes

Manchester Encode - Enabled 

Below pictures shows the TX settings and received packets and I can see there are some additional data received (d7 and f9) also, first data added in to seq.no.

Please correct me if I went wrong with settings.

Also, I tried with our current RX devices unfortunately it did not recognize the data that sent from dev kit.

Further I give a try to receive the data from our TX device with one of the Dev kit in RX mode sadly no response. But, in continuous RX mode I can see some pulses (see below image). Is this continuous RX mode give us any interesting step forward?

Thank you 

Kind regards

Staneslouse

When you use this methos you have to do manchester en/decoding in FW.

Hi Stanes, 

Please can you post better pictures of your settings, specifically the exact value of the Syncword you are using. 

Regards,

Sid

hi Sid,

Sorry for bad images, please check following images and

I have changed fecMode to 0x0A to enable Manchester 

Please can you explain how your frame matches the setting you have used? With the preamble, syncword and payload?

hi SId,

I set the above frame as per following setting:

Preample – 1 byte start with 1 (moved second byte to sync word)

Sync Word – AC 69 9A AA

Data – set in hex that equal to the binary data

Also, enabled Manchester encoded both end by set feMode to 0xA

I hope you can understand the frame setting.

Regards

Staneslouse

Hi Stan, 

I do see your setting, but what I do not understand is how this setting is same as the earlier description of your frame?

Hi Sid,

the way I was followed that TheGostOf suggested earlier, so I moved the second byte of preamble to syncword.

I can see that Preamble can't modify just  only can vary the length and change the start bit value 1 or 0, my question is this legacy protocol can be build up using  CC1310? if yes please let me know how to modify settings in SmartRF or any other way

Thank you

Kind regards

Stanes 

Staneslouse Sadeesh said:

feMode to 0xA

This will only do manchester on the payload. You also have to do CRC manually. Have you checked what you actually send/ receive with your settings? In RX, set sync to 0xAA (or whatever that allows you to receive everything on the air and compare.  

hi Sid,

I solved the issues and now I can communicate with existing product. thank you for all the advices 

regards

Stanes