discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] gr-rds


From: Michael Thelen DK4MT
Subject: Re: [Discuss-gnuradio] gr-rds
Date: Tue, 25 Aug 2015 14:08:09 +0200
User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0

Hi Andreas,

thanks for the hint. However I am using a Ettus B200 and do not have
access to a different SDR right now. I will test outside and then trying
to find out what is going on.

BR
Mike


> Hi Michael,
> 
> i read your mail and i could remember i had a similar problem with a lot
> of lost sync and bad block messages.
> 
> My solution was to use a different RTL USB stick and to play with
> antenna type / antenna position and the gain of the RTL stick.
> 
> I used a "classical" lamda / 2 dipol UKW Radio antenna. The stick was a
> noname.
> 
> regards,
> Andreas
> 
> 
> 
> 
> 
> 
> Am 23.08.2015 um 20:02 schrieb Michael Thelen DK4MT:
>> Hi Marcus,
>>
>> thanks, tried your script and found out, that it is always a little bit
>> uncomely if something is not really reproducible. This is the status:
>>
>> With your script I did not get the earlier error anymore. However with
>> my original I did not get it either. Instead I get the following message
>> in GRC:
>> @@@@@ Sync State Detected
>> @@@@@ Lost Sync (Got 50 bad blocks on 50 total)
>>
>> I do not get this message if I run your script. Both scripts though do
>> not show RDS information. So before I steal somebody's time I wonder if
>> one reason could be, that I can only receive one station really at the
>> limit and only if I set gain to a max. I can hear fairly clear audio,
>> but I am not sure if I can conclude from, that RDS decoding should work.
>> I am pretty much insulated from RF at my place. What would be in favor
>> by people being sensitive to EM waves, but for experimenting it is
>> pretty bad.
>>
>> So I might gonna check this outside, where I can see in my car, that RDS
>> reception is working on my radio and then I can compare. Just want to
>> make sure we or you aren't chasing an error which might be based on poor
>> reception.
>>
>> However the messages in the terminal have been there last time and the I
>> copied to also were there. Still don't no if this is part of the problem
>> though. Therefore probably more testing on my side.
>>
>> Best regards,
>> Mike
>>
>>
>>
>>> Hi Mike,
>>>
>>> dashed only means "message port connection" rather than "item stream",
>>> so that's nothing to worry about, usually.
>>> So the bad news is that this is possible a GRC bug, which on the other
>>> hand is good news, because it means that gr-rds isn't broken, GRC just
>>> has a hard time correctly generating the python file.
>>> Since that worked for me: can you try the attached python file?
>>>
>>> Best regards,
>>> Marcus
>>>
>>> On 22.08.2015 11:26, Michael Thelen DK4MT wrote:
>>>> Hi,
>>>>
>>>> I am using GNU Radio 3.7.7.2 and I checked out out and built gr-rds.
>>>> However RDS Decoding is not working. I found that there are to two
>>>> connections have dashed lines (see picture). And in the terminal all I
>>>> get is Error: Cannot create connection. But I could not find a hint,
>>>> what is going wrong. Can somebody tell me, what to check for?
>>>>
>>>> Best regards,
>>>> Mike
>>>>
>>>>
>>>> _______________________________________________
>>>> Discuss-gnuradio mailing list
>>>> address@hidden
>>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>
>>>
>>> _______________________________________________
>>> Discuss-gnuradio mailing list
>>> address@hidden
>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>
>> _______________________________________________
>> Discuss-gnuradio mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]