Re: Symbol Sync Block Python Source File Passing Wrong Constellation

[Daniel Estévez]

Hi Ceren,




Best,
Daniel.

On 06/12/2024 09:30, Ceren Karaköse wrote:

I believe the Gardner TED does not use or require a constellation (unlike some of the other TEDs supported by Symbol Sync). Thus, the constellation you supply in the call to symbol_sync_cc() is ignored. You can read through the C++ code to make sure that this is indeed the case.

Hi all,



         self.digital_symbol_sync_xx_0_0_0 = digital.symbol_sync_cc(
             digital.TED_GARDNER,
             xsample,
             my_loopbw,
             my_damp_fac,
             my_ted,
             my_maxdev,
             1,
*digital.constellation_qpsk().base(),*
             digital.IR_PFB_MF,
             nfilts,
             rrc_taps)



Thanks a lot,
Best regards,
Ceren

I'm using Symbol Sync from core GNU library. Although when Gardner TED is selected, the parameters section ***do not***have any option to define a slicer constellation, the generated python file passes qpsk.base as slicer argument as follows: I would like to modify the default qpsk.base constellation as I'm using a different one. My question is can I do so without messing with the generated .py file? I would much prefer passing the argument using GNU interface instead of manually modifying .py file.

OpenPGP_signature.asc
Description: OpenPGP digital signature