next up previous
Next: The Available Tokens Up: The Lexical GUI builder Previous: The Lexical GUI builder

Introduction

The user must supply a file by the name of user_GUI.par that resides in the user directory under the RTiC-Lab source tree. This pure ASCII file has several roles:

  1. allows the user to create custom-made graphical user interfaces through which the user can update parameters in real time for the user's controller, defined in the file user_controller.c. The actual window that is affected by this script file can be found under the ``Options'' window, on the ``Controller'' tab, and ``Open''.
  2. allows the user to override xrtic defaults
  3. tells rtic how many inputs, how many outputs, and how many data points will be handled for the given control application

Each of these tokens associated with a user's parameter is identified via a unique identifier constant. Examples of this are shown in the Examples section, Section 3.3.

For example, in this file, the user may specify that a ``slider'' token (a widget which looks like a linear resistor) will be linked to the parameter with ID of ``3'', which is to be used in the real time tasks. So, if the user moves the slider bar to a value of ``15.2'', the real time parameter with the unique ID of ``3'' will receive the value of ``15.2''. Parameters in the user's controller may then be updated by the use the macro ``GET_SCALAR_PARAMETER(ID)''. So, from the previous slider example, we can update the value of a derivative gain in the embedded controller code by the following piece of code:

	/* get the value of the derivative gain */
	Td = GET_SCALAR_PARAMETER(3);

The next section describes the available tokens.


next up previous
Next: The Available Tokens Up: The Lexical GUI builder Previous: The Lexical GUI builder
Michael Barabanov 2001-06-19