the UECP format consists of a number of fixed obligatory bytes, optional bytes and message bytes.
MEC(Message element code): This the specific command code that the data that follows refers to. For example MEC = 0x01 is a PI definition.
DSN(Data set number): This is a byte that targets the command. An encoder can store various data sets that contain the information to be encoded and sent under different transmission conditions. By targeting the command the data in a specific data set can be changed, the current data set or all the data sets. This encoder design only has two data sets, the set being transmitted and the set pending transmission.
PSN(Programe service number): Allows a specific level of service to be programmed
MEL(Message element length): The length of the message element to follow. If any stuffing is inserted then this is the un stuffed length
MED(Message element data): This is the actual data of the command to be acted upon
An Command Example for PS (Program Service Name):
| Byte Definition | Byte Value Range | Byte Significance |
|---|---|---|
| MEC | 0x02 | Command Header |
| DSN | 0x00...0xFF | Data Set Number |
| PSN | 0x00...0xFF | Progam Service Number |
| MED | 0x00...0xFF | Data element 0 |
| MED | 0x00...0xFF | Data element 1 |
| MED | 0x00...0xFF | Data element 2 |
| MED | 0x00...0xFF | Data element 3 |
| MED | 0x00...0xFF | Data element 4 |
| MED | 0x00...0xFF | Data element 5 |
| MED | 0x00...0xFF | Data element 6 |
| MED | 0x00...0xFF | Data element 7 |
Note:: The MEL is not required since the data is always 8 bytes. The example name is padded by a space to 8 bytes
<0x02><0x00><0x02><0x52><0x41><0x44><0x49><0x4f><0x20><0x35><0x20>
This is "Radio 5 "