[CRTech] Christian Radio Tech [MSG 75595]
[Thread Prev] [-- Thread Index --] [Thread Next] [Date Prev] [-- Date Index --] [Date Next]
[no subject]
Bill

-----Original Message-----
From: Nathan Steele [mailto:nathaniel.steele@icloud.com] 
Sent: Friday, April 08, 2016 7:35 AM
To: CRTech
Subject: Re: [CRTech] PI codes

Id like af to work though.



----------
On April 8, 2016 8:26:11 AM Mark Humphrey <mark3xy@gmail.com> wrote:

> In the case of an HD secondary channel rebroadcast on an analog 
> translator, I think the best choice for PI code would be 0000 (in hex) 
> -- and make sure your AF list is empty.
>
> The main reason for PI is verification of alternate frequency tuning.  
> I've only come across one receiver that decodes PI back to an FCC
callsign, and
> that was in my old Motorola Droid X.   Practically every other RDS
receiver
> shows the eight character PS field on the display.
>
> Mark
>
> On Fri, Apr 8, 2016 at 9:40 AM, Willie Barnett 
> <wbradiolists@gmail.com>
> wrote:
>
>> Won't work. To make the large number of possible callsigns "fit" into 
>> a simple 16 bit binary code, they had to cut some corners. The first 
>> letter decodes to either W or K. The other three letters are then 
>> encoded into the remaining 15 bits. (One of the bits selects the W or 
>> the K)
>>
>> Willie...
>>
>>
>> On Fri, Apr 8, 2016 at 9:06 AM, Scott Todd <stodd@kloveair1.com> wrote:
>>
>> > The letters N and A are used in ham radio.  Wonder if they could be 
>> > used for PI codes too?
>> >
>> > Scott Todd
>> >
>> >
>>



---------------------------------------------------------------------
For CRTech resources visit http://CRTech.org/ To unsubscribe, e-mail:
crtech-unsubscribe@crtech.org List problems?  E-mail: TechStaff@CRTech.org

Prev by date: [no subject]
(Unknown, Sun Jun 04 00:50:48 2017)
Next by date: [no subject]
(Unknown, Sun Jun 04 01:32:09 2017)
Prev by thread: [no subject]
(Unknown, Sun Jun 04 00:50:48 2017)
Next by thread: [no subject]
(Unknown, Sun Jun 04 01:32:09 2017)
CRTech.org