# Error while using MPSK Sync block in GRC 3.5.0

**URL:** <https://www.ruby-forum.com/t/error-while-using-mpsk-sync-block-in-grc-3-5-0/215717>\
**Category:** GNU Radio\
**Created:** [January 13, 2012, 4:38pm UTC](https://www.ruby-forum.com/t/error-while-using-mpsk-sync-block-in-grc-3-5-0/215717 "2012-01-13T16:38:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dubstep](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/cdc98d/32.png) [@dubstep](https://www.ruby-forum.com/u/dubstep)\
**Post date:** [January 13, 2012, 4:38pm UTC](https://www.ruby-forum.com/t/error-while-using-mpsk-sync-block-in-grc-3-5-0/215717/1 "2012-01-13T16:38:18Z")

</div>

Hello  
I was trying to use the MPSK Sync in GRC 3.5.0 but it seems that there  
is  
either no block declared in gr-digital for the same. All I could find  
was  
an xml file for the same. Is digital\_mpsk\_reciever\_cc.cc for the block?  
If it is then there is no place to declare M and theta. Also no  
Omega\_relative parameter to declare. Although there is a new parameter  
in  
the block Relative Phase, is it replacement for the Omega\_Relative  
parameter.  
Please help me to understand this doubt  
Thanks  
Shashank G.

---

<div class="post-metadata">

**Author:** ![shashank\_gaur](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ebca7d/32.png) [@shashank\_gaur](https://www.ruby-forum.com/u/shashank_gaur)\
**Post date:** [January 15, 2012, 8:04pm UTC](https://www.ruby-forum.com/t/error-while-using-mpsk-sync-block-in-grc-3-5-0/215717/2 "2012-01-15T20:04:34Z")

</div>

On Fri, Jan 13, 2012 at 10:37 AM, shashank gaur  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)wrote:

> Shashank G.  
> I’m confused. The gr\_mpsk\_receiver\_cc has been moved to gr-digital and  
> is  
> now digital\_mpsk\_recevier\_cc. It’s public constructor looks like:

DIGITAL\_API digital\_mpsk\_receiver\_cc\_sptr  
digital\_make\_mpsk\_receiver\_cc (unsigned int M, float theta,  
float loop\_bw,  
float fmin, float fmax,  
float mu, float gain\_mu,  
float omega, float gain\_omega, float omega\_rel);

The setting for M and omega\_rel are right there.

There is no set/get functions defined for these parameters, which might  
be  
where your question is coming from. It should be possible to add both.  
Setting the omega\_rel this way is easy. To set a new M value, though,  
would  
require a total reset of the blocks values because of the different want  
they are handled.

Tom

---

<div class="post-metadata">

**Author:** ![shashank\_gaur](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ebca7d/32.png) [@shashank\_gaur](https://www.ruby-forum.com/u/shashank_gaur)\
**Post date:** [January 16, 2012, 12:44am UTC](https://www.ruby-forum.com/t/error-while-using-mpsk-sync-block-in-grc-3-5-0/215717/3 "2012-01-16T00:44:02Z")

</div>

On Sun, Jan 15, 2012 at 2:03 PM, Tom R. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> > Please help me to understand this doubt  
> > float fmin, float fmax,
> 
> Tom

Just pushed a fix (on master and next) that adds set/get functions for  
the  
modulation order (M), the omega relative limit, and theta that were  
missing  
before.

Tom