MC-Basic

Contents

• MC-Basic Commands Reference - a list of all MC-Basic commands
• Language Fundamentals
• Operators
• Programs
• Libraries
• C-Interface

This documentation covers all the commands and properties associated with the software components of the softMC. The application of these commands is covered in the MC Users Manual. The syntax and related properties and variables are shown for each command. Example are also shown to illustrate the use of the command. It is recommended that you review this manual and refer to it when you are using these functions.

Command Reference Format

Each description contains the information needed for correctly use of the command or property. All commands and properties contain the following items:

• Short Form
• Syntax
• Availability
• Description
• Type
• Range
• Units
• Default
• Scope
• Limitations
• Example
• See Also

Where applicable, a Short Form of the longer command can be used to simplify typing the command or property name. In such instances, the Short Form is denoted. The Short Form of a command or property name may be used interchangeably with the long version.

Various versions of the firmware add new features, and often significantly change the syntax or behavior of commands and properties. The attribute Availability included in the descriptions denotes the applicability of each function (command, property)to the specified version of the firmware.

When parameter values imply dimensional units of measurement, these units are specified in the description of the command or property where they apply.

Notation

In describing the syntax of an instruction, different forms of notation are used.

< >	Field to be filled by user. For example, ABS ( <expression> ) indicates that <expression> is the user’s data.
{ }	Optional data. Many instructions have optional fields, which are used to override default values. For example, the VelocityCruise property is optional within a Move command. However, there is an exception to this rule, in that { } are used for vector notation. When the optional data may be repeated, an asterisk (*) is used to indicate this.
|	OR. Indicates that one or another value may be used.

Scope of Operation

Instructions can be executed from any of three contexts: the configuration file (CONFIG.PRG), the terminal, and from within a task. Not all instructions can be executed from all three contexts; their scope of operation is limited. For each instruction, the scope of operation is defined.

Limitations of Operation

Even when an instruction can be executed in a given context, there may still be limitations on its use. For example, a MOVE command can be executed from within a task, but there is a limitation in that the motion element being moved must first be attached to the task by the ATTACH command.

See also

• FAQ MC-Basic - Ask the developers a question
• AMCS Firmware
• Error Codes
• Predefined constants