Author Topic: RDS Encoder Addressing  (Read 789 times)

Mahesh Kakani

  • Newbie
  • *
  • Posts: 1
RDS Encoder Addressing
« on: November 18, 2016, 05:02:18 am »
Hello All,

While studying the UECP Protocol, I didn't understand the RDS Encoder addressing.

It was mentioned RDS Encoders were placed at Transmitter sites, when we need send the RDS Data we need to use the RDS Encoder which encodes the data.

But my doubt is RDS Encoder supports Multiple address //I didn't understand this point.

Again it was mentioned that Global Address i.e "0", must be accepted by any site & Encoder address. This is understandable.

If RDS Encoder supports multiple addresses, can some one help me how many address it supports??

Jan

  • Hero Member
  • *****
  • Posts: 509
Re: RDS Encoder Addressing
« Reply #1 on: November 18, 2016, 09:45:29 am »
The UECP protocol is an industry standard which is oversized in respect of the addressing to cover all possible situations. It was developed at a time when TCP/IP connectivity did not exists on most transmitter sites and sometimes only one serial data channel was available for entire site. Today, most of the addressing job is usually done either at the TCP/IP layer (by specifying IP address of the RDS encoder) or by taking the data from satellite channel which is usually particular for each station.

Thus most stations require no encoder address (use the "0" wildcard) or a single encoder address is sufficient. The same applies to the site address. Two or more site/encoder addresses may be useful in some special cases, for example if only a part of the network carries TMC data and all encoders are connected to one serial channel, while need to retain a possibility of individual configuration for each encoder.

Limit for the number of addresses is not specified anywhere. Our encoders support up to two addresses for the Encoder address and up to two addresses for the Site address.