Technical data

ASTi ACE Studio Components Reference Guide Rev. M DOC-01-TELAS-CRG-4

16.0. Remote Control

16.1. URC-200

Summary: Interfaces with a single URC-200 live radio through an ACE-RIU

channel.

Description: This component provides a low level interface to an URC-200 radio,

through an ACE-RIU serial port.

The interface presented in the data viewer is similar to a combination Radio/RCU +

Radio/Transceiver data viewer. Essentially this means there is a ‘control’ section

and ‘status’ section to the component.

The ‘control’ section accepts user input, and drives the radio settings when

applicable. Radio items in the ‘control’ section will generally be prefixed with a

RCU string, as in RCU_Preset. Items in the ‘status’ section will not have a prefix

string, as in Preset.

If the live radio fails to respond to a query for a specific status item (for example, a

query for what its current preset is) the component will display an error indicator,

like the number -1 or the string ‘Unavailable’.

Input to the items in the ‘control’ section are naively checked for validity. One

should not expect the component to know what frequency ranges are valid during

live radio operation, for example. On the contrary, the component assumes the user

completely understands the constraints on parameters for different modes of

operation. If the user does input an invalid input, the transceiver will most likely

return a NAK, which will eventually be flagged as an error in the ErrorMask.

For a more intuitive interface, refer to the Remote Control feature of RMS. The

ideal interface to use with this component is the Live Radio Remote Control section

of RMS.

There is also a Python API for interfacing with the Remote Control components in

a model; this should allow programmatic control over live radio entities present in

the system. Contact ASTi for more information.

The command list below is the complete list of commands sent to the live radio

RS232 serial interface, from the component.