Recent Posts

Pages: [1] 2 3 ... 10
1
P132, P232 and P332 RDS Encoders / Re: Integration with Zetta
« Last post by Jan on Yesterday at 08:46:52 pm »
The P332 accepts both the TEXT= and RT1=, they are equivalent. Complete data format is

TEXT=the text here<CR>

where <CR> is carriage return character. This information should be enough for the RCS support to provide working configuration file. It's been some time I played with Zetta, this software is rare here in Central Europe. Maybe someone else will know more about its configuration specifics.

To see the result in real time, either show the P332 embedded website or connect to the P332 from RDS Spy decoder. The website shows also connection status and bytes being received from the software.
(The Magic RDS shows RT1 in the On Air box only if it is driven by this application.)
2
P132, P232 and P332 RDS Encoders / Re: Integration with Zetta
« Last post by bobcvols on Yesterday at 05:43:31 pm »
That was certainly helpful - I took the sample you sent and adapted it for what we would like to have displayed.  I did change the TEXT= command to RT1= ; don't know if that was necessary.

Should the data be displayed on the RT1 line on the computer dashboard?  I am not getting anything yet, although I do need to troubleshoot and make sure we are wired correctly here.  When I test the .xlst file, it gives me 4 lines of text:

RT1= Artist1 - Title
RT1= Artist1 - Title
RT1= FAITH RADIO
RT1= FAITH RADIO

Is that what I should be getting?

Thanks!


Anything else that I might need to check?
3
P132, P232 and P332 RDS Encoders / Re: Integration with Zetta
« Last post by Jan on February 14, 2019, 07:35:37 pm »
There are at least 4 methods how you can output text from Zetta to P332:
  • using the now playing export in Zetta
  • using the MetaRadio
  • using the MagicRDS
  • using the HTTP request

For the first method you'll need to set the export as active in the Zetta, configure either the serial or the TCP connection to P332, select the option "Keep connection open", and add (+) the format for the data. Select Start with ZettaLite.

Zetta uses a configuration by .xlst file. Here's an example of such file:

Code: [Select]
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
   <xsl:output method="text" />
   <xsl:strip-space elements="*" />
   <xsl:variable name="newline">
      <xsl:text>&#13;</xsl:text>
   </xsl:variable>
   <xsl:template match="/">
      <xsl:apply-templates />
   </xsl:template>
   <xsl:template match="LogEventCollection">
      <xsl:for-each select="LogEvent">
         <xsl:text>TEXT=</xsl:text>
         <xsl:choose>
            <xsl:when test="@Type='SONG'">
               <xsl:value-of select="Asset/@Title" />
               <xsl:text> - </xsl:text>
               <xsl:value-of select="Asset/@Artist1" />
            </xsl:when>
            <xsl:otherwise>
               <xsl:text>Your station slogan here</xsl:text>
            </xsl:otherwise>
         </xsl:choose>
         <xsl:value-of select="$newline" />
      </xsl:for-each>
      <xsl:apply-templates />
   </xsl:template>
</xsl:stylesheet>
In the P332, make sure that Radiotext 1 (RT1) is enabled.

For more details, please follow the documentation from RCS.

Simply put, the example above tells the Zetta to use a command TEXT= followed by title and artist.
Complete list of commands accepted by the P332 is available in the Technical manual, section 10 Broadcast Automation System Link-up.

Let us know if you need a further help.
4
P132, P232 and P332 RDS Encoders / Integration with Zetta
« Last post by bobcvols on February 14, 2019, 04:58:43 pm »
We are attempting to get our P332 up and running.  We have a Zetta automation system from RCS.  The RCS rep I spoke to said to contact Pira.cz tech support to find out about the format needed for the .xlst file to integrate to the RDS unit.  Does anyone have Zetta and can advise me on this?
5
P132, P232 and P332 RDS Encoders / Re: Alternative Frequency Switching
« Last post by Jan on February 09, 2019, 08:34:51 am »
Quote from: Tony on February 09, 2019, 12:18:02 am
My challenge is that I am looking for a true and tried method of seeing the AF switch.

Don't waste your time. It would be nice to see that working but this is not the case of RDS. The AF feature is fully passive in the RDS. That means the RDS only provides to the receivers a list of alternative frequencies. All other functionality must implement the receiver itself, without further support from the FM network. The receiver must find the best frequency, evaluate the reception quality and decide for the switching. The RDS standard does not describe the methodology in more details. As a result, each receiver behaves differently.
6
P132, P232 and P332 RDS Encoders / Re: Alternative Frequency Switching
« Last post by Tony on February 09, 2019, 12:18:02 am »
this information was very helpful thank you!  One other question concerning.  Can I look at the hex code on the RDS spy software and find the switch command?  Also does this work in that two radio station with the same PI code but different RF strengths is the key....so station A has the RDS present as does station B but A is higher RF level and thus it knows to switch?
My challenge is that I am looking for a true and tried method of seeing the AF switch.  The US radio do not all switch and so it is a crap shot....I do have an FM analyzer but think that maybe there is a particular radio or device that might help.
Any advice you might have would be helpful!
thanks again.
7
P132, P232 and P332 RDS Encoders / Re: Alternative Frequency Switching
« Last post by Tony Mielec on February 08, 2019, 04:57:54 am »
Thank you kindly for your response...very helpful!
8
P132, P232 and P332 RDS Encoders / Re: Alternative Frequency Switching
« Last post by Jan on January 31, 2019, 09:24:53 am »
The term "tuning frequency" belongs to AF method B only. You should use AF method A as I suppose both transmitters carry the same program for entire day. The AF method B requires to enter the frequency pairs in correct order and also requires that listeners use correct setting of Regional switch on each car radio.

The AF method A uses only one list on each transmitter and each frequency occurs only once in each list. In your example:
Transmitter 92.1:
AF=92.1,106.1
Transmitter 106.1:
AF=106.1,92.1

There's nothing more to be set in the RDS data.

If it does not work well for you, then check:
  • whether the AF switching is enabled in your receiver
  • whether the RDS level is not too high, causing low error rate in case of bad reception
  • in case of changes in AF or PI, tune your station manually by Up/Down buttons and store it again into the car radio preset memory
9
P132, P232 and P332 RDS Encoders / Alternative Frequency Switching
« Last post by amielec on January 31, 2019, 05:17:52 am »
Hi all, first what a great product!!
We are having an issue with setting up Alternate freq switching and I am sure it might be a setting issue?
We have two low power FM translators that share same PI code D1F8...this is the PI code set for each location.  One is 106.1 and the other is 92.1....the tuning freq has been set for the unit that it is on.  So for example on the 92.1 unit the tuning frew is 92.1 and the AF is 106.1  and vice versus for the 106.1 unit.
Still it does not seem to be working and I can't help but think we are missing something of have the tuning freq and alt backward.....any incite will be helpful...

thank you!!
10
PIRA32 RDS Encoder / Re: External TA
« Last post by Jan on January 21, 2019, 12:10:22 pm »
Yes, the TA input is directly designed for that kind of use.
Pages: [1] 2 3 ... 10