EasyManua.ls Logo

FMUser RDS-C - Page 51

Default Icon
53 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
FMUSER INTERNATIONAL GROUP INC. 广州市汉婷生物技术开发有限公司
50
14.2.3 TDC group coding (5A, 5B)
Group format in hexadecimal representation (version A): 50BBCCCCDDDD,
group format in hexadecimal representation (version B): 58BB0000DDDD,
where BB, CCCC and DDDD represent the contents of the block 2 (bits 4 to 0), block 3 and block 4.
14.2.4 IH group coding (6A, 6B)
Group format in hexadecimal representation (version A): 60BBCCCCDDDD,
group format in hexadecimal representation (version B): 68BB0000DDDD,
where BB, CCCC and DDDD represent the contents of the block 2 (bits 4 to 0), block 3 and block 4.
14.2.5 AID for ODA group coding (3A)
Group format in hexadecimal representation: 30BBCCCCDDDD,
where BB, CCCC and DDDD represent the contents of the block 2 (bits 4 to 0), block 3 and block 4.
These groups are used to identify the Open Data Application in use, on an RDS transmission. The type 3A group
conveys, to a receiver, information about which Open Data Applications are carried on a particular transmission
(AID Code) and in which groups they will be found (Application group type code).
The Application group type code and the AID Code are obligatory, while the Message field is optional and should be
set to zeros if not used.
Since the 3A groups usually carry fixed static content, they may be inserted using either the UDG1= or UDG2=
command for automatic cyclic transmission while the ODA application groups may be inserted by any command or
method (G=, UDG1=, UDG2= or UECP MEC 24 or 42).