OMS MAXnet, Руководство пользователя

Страница: 27 / 67

INTRODUCTION COMMUNICATION INTERFACE
MAXnet User’s Manual 3-1
3. COMMUNICATION INTERFACE
3.1. INTRODUCTION
The MAXnet can be considered a motion co-processor to the host computer where it can execute the
motion process independent of the host CPU. The application software issues DLL function calls and
receives requested data from the support DLL. All communication is done between the motion controller
and the host PC via the DLL and the communication interface (Ethernet or RS-232). (See also
Functional and Data Flow Info Diagrams Figure 3-1.)
Simplified Data Dictionary of Figure 3.1 .
Event Notification = {New status flag data available, Query command text
response available}
Direct Commands = {Kill all motion}
Text Commands = {ASCII controller command strings}
Status Flags = {
Axis done flags = {X, Y, Z, T, U, V, R, S, W, K},
Axis over-travel limit flags = {X, Y, Z, T, U, V, R, S, W, K},
Axis encoder slip flags = {X, Y, Z, T, U, V, R, S, W, K},
Command error flag}
Text Responses = {Query command (RP, RE…) ASCII response strings}
Shared Memory Data = {Axis motor position data, axis encoder position data,
velocity profile data, and servo tuning data,}
Requested Data = {Null terminated ASCII text response string, velocity profile
data, servo tuning data, axis done flags, axis over-travel limit flags, axis encoder
slip flags, command error status}