Mint NextMove PCI Manual de usuario descargar pdf (Pagina 14)

4-4 Using the MintMT ActiveX Control

Figure 2 shows a diagram of the MintMT controller software architecture.

Figure 2 - MintMT software architecture

When an MML function is called by a PC application the ActiveX sends a data packet to the controller.

This data packet contains data about the MML function to be called and any associated parameters. The

controller then processes the MML function call and returns a data packet to the PC application containing

an error code and any returned data from the MML function call.

All MML function call requests pass through the MML Interface, so only one MML function call can be in

progress at any time. This means that there is no danger of data contention. MintMT controllers can

process ICM function calls while running MintMT programs.

Calling functions from a PC application is particularly useful if there is a large amount of processing to do,

for example the calculation of multi-axis paths. The PC application can do the processing and send

commands to the controller. For example, the MintMT program could be programmed to handle the I/O

and the PC application could be used to calculate positional data and load moves using the MML function

call setVectorA().

There is a one-to-one correlation between MintMT keywords that call MML functions, and the MintMT

ActiveX control functions. For example, within a MintMT program, the MOVER keyword is used to create a

relative positional move on an axis:

MOVER.0 = 10

Equivalent functionality can be achieved via the MintMT ActiveX control calling the function setMoveR.

MintController.setMoveR 0, 10

The keyword has been prefixed with set.

Host PC

MintMT

MML Interface

Mint Motion Library

Servo Loop

Profiler Digital I/O

Analog I/O

Controller

ICM Interface

MintMT ActiveX

Control

PC Application

DPR

1 2 ... 9 10 11 12 13 14 15 16 17 18 19 ... 69 70

Sin comentarios

Mint NextMove PCI Manual de usuario Pagina 14