KUKA Standard Interface Subprograms

You are viewing an old version of the documentation. You can switch to the documentation of the latest version by clicking the top-right corner of the page.

The KUKA Standard Interface provides the following subprograms:

  1. Multiple parameters should be separated by commas.

  2. Variable-type parameters should use local variables, which take effect only in the program.

  3. Parameters can be defined as IN parameters or OUT parameters.

The KUKA Standard Interface provides the following subprograms.

Initialize Communication

This subprogram sets the name of the XML file used for setting up the TCP/IP communication, flag for successful communication, flag for successful data reception, and wait time before the program stops trying to establish the communication.

Subprogram

MM_Init_Socket(XML_Name[]:IN,Alive_Flag:IN,Recv_Flag:IN,Time_Out:IN)

Parameters

Name Description

IN parameters

XML_Name[]

Name of the XML file, case-sensitive.

Alive_Flag

ALIVE flag number in the XML file. When the flag is set to ON, the communication is successfully established.

Recv_Flag

RECEIVE flag number in the XML file. When the flag is set to ON, the robot has successfully received data.

Time_Out

Wait time in seconds before stopping connection attempt.

Example

MM_Init_Socket(“XML_Kuka_MMIND”,873,871,60)

This example sets the XML file for setting up communication as XML_Kuka_MMMIND, the flag for successful communication as 873, the flag for successful data reception as 871, and wait time as 60 seconds.

Start Mech-Vision Project

This subprogram is for applications that use Mech-Vision. It runs the corresponding project to acquire and process data. It applies for applications that use Mech-Vision but not Mech-Viz.

Subprogram

MM_Start_Vis(Job:IN,Pos_Num_Need:IN,SendPos_Type:IN,MM_J:IN)

Parameters

Name Description

IN parameters

Job

Mech-Vision project ID, which can be viewed before the project name in the Project List panel in Mech-Vision.

Pos_Num_Need

The expected number of vision points for Mech-Vision to send. The vision point contains the vision pose, corresponding point cloud, label, scaling, etc. Value range: 0–20, in which 0 indicates that all vision points will be received.

SendPos_Type

The type of the robot pose to be sent to Mech-Vision. Value range: 0 to 3.

  • 0: No robot poses need to be sent to the vision system. If the camera is mounted in the Eye To Hand mode, the image capturing process is independent of the robot pose, and therefore the robot pose is not needed.

  • 1: The robot pose in the current joint positions together with the current flange pose will be sent to the vision system. It is recommended to set this value when the camera is mounted in the Eye In Hand mode. When this parameter is set to this value, the “Path Planning” Step in the Mech-Vision project will use the joint positions sent by the robot. If the flange pose data are all 0, the vision system ignores the flange pose data.

  • 2: The robot pose in the current flange pose will be sent to the vision system. It is recommended to set this value when the camera is mounted in the Eye In Hand mode or in other scenarios where only the flange pose data is available (such as truss robots).

  • 3: The robot pose in the joint positions defined by the user will be sent to the vision system. It is recommended to set this value when the camera is mounted in the Eye To Hand mode. When the Mech-Vision project contains the “Path Planning” Step, the joint positions sent by the robot will be used as the start pose.

MM_J

E6AXIS variable for storing the joint positions of the start point when SendPose_Type = 3.

Example

MM_Start_Vis(1,1,1,MM_J)

This example triggers Mech-Vision project No.1 to run, and asks the Mech-Vision project to send over one vision point. The robot sends its current joint positions and flange pose when this subprogram is called as the image-capturing pose.

Get Vision Target(s)

This subprogram is for applications that use Mech-Vision but not Mech-Viz. It obtains the vision result from the corresponding Mech-Vision project.

Subprogram

MM_Get_VisData(Job:IN,Pos_Num:OUT,MM_Status:OUT)

Parameters

Name Description

IN parameters

Job

Mech-Vision project ID, which can be viewed before the project name in the Project List panel in Mech-Vision.

OUT parameters

Pos_Num

Variable for storing the number of received vision points.

MM_Status

Variable for storing the status code. Please see Status Codes and Troubleshooting for detailed information.

Example

MM_Get_VisData(1,Pose_Num,Status)

This example obtains the vision result from Mech-Vision project No.1. The number of returned vision points is stored in the variable Pos_Num, and the status code is stored in the variable Status.

Start Mech-Viz Project

This subprogram is for applications that use both Mech-Vision and Mech-Viz. It starts the Mech-Viz project that triggers the corresponding Mech-Vision project, and therefore the Mech-Viz project can plan the robot path based on the vision points received from Mech-Vision.

Subprogram

MM_Start_Viz(SendPos_Type:IN,MM_J:IN)

Parameters

Name Description

IN parameters

SendPos_Type

Robot pose type. Value range: 0 to 2.

  • 0: No robot poses need to be sent to Mech-Viz. The simulated robot in Mech-Viz will start from joint positions [0,0,0,0,0,0] and move to the first waypoint.

  • 1: The current joint positions and flange pose of the real robot need to be sent to Mech-Viz. The simulated robot in Mech-Viz will start from the current joint positions of the real robot and move to the first waypoint.

  • 2: Joint positions of a specific start point will be sent to Mech-Viz. This setting is recommended for projects in the Eye-To-Hand mode. The simulated robot in Mech-Viz moves from the predefined joint positions to the first waypoint.

MM_J

E6AXIS variable for storing the joint positions of the start point when SendPose_Type = 2.

Example

MM_Start_Viz(1,MM_J)

This subprogram triggers the Mech-Viz project to run and sends the current joint positions and flange pose of the robot to Mech-Viz.

Get Planned Path from Mech-Viz

This subprogram obtains the planned path from Mech-Viz.

Subprogram

MM_Get_VizData(Jps_Pos:IN,Pos_Num:OUT,VisPos_Num:OUT,MM_Status:OUT)

Parameters

Name Description

IN parameters

Jps_Pos

This parameter specifies the type of waypoint pose to be obtained. The value is 1 or 2.
1: Mech-Viz sends joint positions.
2: Mech-Viz sends TCPs.

OUT parameters

Pos_Num

Variable for storing the number of received vision points.

VisPos_Num

Variable for storing the position of the first Vision Move waypoint in the path. For example, in the workflow “Fixed-Point Move 1, Fixed-Point Move 2, Vision Move 1, Fixed-Point Move 3”, the position of the first Vision Move waypoint is 3. If the path does not contain Vision Move waypoint, the returned value is 0.

MM_Status

Variable for storing the status code. Please see Status Codes and Troubleshooting for detailed information.

Example

MM_Get_VizData(2,Pose_Num,VisPos_Num,Status)

This example obtains the planned path from Mech-Viz in the form of TCP. The number of poses received is stored in the variable Pos_Num, the position of the Vision Move waypoint is stored in the variable VisPos_Num, and the received status code is stored in variable Status.

Obtain Vision Point Pose

This subprogram stores a vision pose returned by Mech-Vision or a waypoint pose (as a TCP) returned by Mech-Viz in the specified variable.

Subprogram

MM_Get_Pose(Serial:IN,MM_P:OUT,MM_Label:OUT,MM_Speed:OUT)

Parameters

Name Description

IN parameters

Serial

Specify the index of the pose to be stored.

OUT parameters

MM_P

P variable for storing the specified pose.

MM_Label

Variable for storing the label corresponding to the specified set of joint positions.

MM_Speed

Variable for storing the velocity corresponding to the specified set of joint positions.

Example

MM_Get_Pose(1,XP1,Label,Pose_Speed)

This example stores the first set of received pose to XP1, the corresponding label to Label, and the corresponding velocity to Pose_Speed.

Obtain Joint Positions (Available when Mech-Viz is used)

This subprogram stores a vision pose returned by Mech-Vision or the JPs of a waypoint returned by Mech-Viz in the specified position variable.

Subprogram

MM_Get_Jps(Serial:IN,MM_J:OUT,MM_Label:OUT,MM_Speed:OUT)

Parameters

Name Description

IN parameters

Serial

Specify the index of the pose to be stored.

OUT parameters

MM_J

Variable for storing the specified set of joint positions.

MM_Label

Variable for storing the label corresponding to the specified set of joint positions.

MM_Speed

Variable for storing the velocity corresponding to the specified set of joint positions.

Example

MM_Get_Jps(1,JP1,Label,Pose_Speed)

This example stores the first set of received joint positions to JP1, the corresponding label to Label, and the corresponding velocity to Pose_Speed.

Switch Mech-Vision Recipe

This subprogram specifies which parameter recipe of the Mech-Vision project to use. Parameter recipes can be used to switch parameter settings, including point cloud model for matching, ROI, confidence threshold, etc, in the same Mech-Vision project when it is used to recognize different workpieces. This subprogram must be called BEFORE MM_Start_Vis.

Subprogram

MM_Switch_Model(Job:IN,Model_Number:IN)

Parameters

Name Description

IN parameters

Job

Mech-Vision Project ID, which can be checked and adjusted in the Project List panel of Mech-Vision.

Model_Number

The ID of a parameter recipe in the Mech-Vision project, from 1 to 99.

Example

MM_Switch_Model(2,2)

This example switches the parameter recipe used to No.2 in Mech-Vision project No.2.

Select Mech-Viz Branch

This subprogram is used to select along which branch the Mech-Viz project should proceed. Such branching is achieved by adding Branch by Msg Step(s) to the Mech-Viz project. This subprogram specifies which exit port such Step(s) should take. MM_Start_Viz should be called BEFORE this subprogram. When executing the “Branch by Msg” Step, Mech-Viz waits for the exit port No. sent by Command 203.

Subprogram

MM_Set_Branch(Branch_Num:IN,Export_Num:IN)

Parameters

Name Description

IN parameters

Branch_Num

Step ID of the “Branch by Msg” Step. Its value is an integer. The Step ID can be viewed in the Step Parameters panel.

Export_Num

The number of the exit port to take plus 1. For example, to select exit port 0 in Mech-Viz, set the value of this parameter to 1. Value range: 1 to 99.

Example

MM_Set_Branch(1,3)

This example tells Mech-Viz to take exit port 3 for the “Branch by Msg” Step whose Step ID is 1.

Set Move Index

This subprogram sets the index value for move-type Steps that contain index parameters. These Steps include Move by List, Move by Grid, Custom Pallet Pattern, and Predefined Pallet Pattern. MM_Start_Viz must be called BEFORE this subprogram.

Subprogram

MM_Set_Index(Skill_Num:IN,Index_Num:IN)

Parameters

Name Description

IN parameters

Skill_Num

ID of the Step, an integer. The Step ID can be viewed in the Step Parameters panel.

Index_Num

The index value that should be set the next time this Step is executed.

When this subprogram is sent, the current index value in Mech-Viz will become the parameter value minus 1.

When the Mech-Viz project runs to the Step specified by this subprogram, the Current Index value in Mech-Viz will be increased by 1 to become the parameter’s value.

Example

MM_Set_Index(2,10)

This example sets the Current Index value to 9 for the Step 2 in the Mech-Viz project. When the Step is executed, the Current Index value will be added 1 and become 10.

Get Software Status

This subprogram is used to obtain the software execution status of Mech-Vision, Mech-Viz, and Communication Component. Currently, this subprogram can only be used to check whether Mech-Vision is ready to run.

Subprogram

MM_Get_Status(MM_Status:OUT)

Parameters

Name Description

OUT parameters

MM_Status

Variable for storing the status code. Please see Status Codes and Troubleshooting for detailed information.

Example

MM_Get_Status(Status)

This example obtains the status code and stores it in Status.

Input Object Dimensions to Mech-Vision

This subprogram is used to dynamically input object dimensions into the Mech-Vision project. This subprogram must be called BEFORE MM_Start_Vis.

Subprogram

MM_Set_BoxSize(Job:IN,Length:IN,Width:IN,Height:IN)

Parameters

Name Description

IN parameters

Job

Mech-Vision Project ID, which can be checked and adjusted in the Project List panel of Mech-Vision.

Length

Length of the object in mm.

Width

Width of the object in mm.

Height

Height of the object in mm.

Example

MM_Set_BoxSize(1,500,300,200)

This example sets the object dimensions in the Read Object Dimensions Step in the Mech-Vision project No.1 to 500×300×200 mm.

Get Gripper DO List

This subprogram obtains the gripper DO list planned by Mech-Vision or Mech-Viz. To apply the DO signals to the gripper, call the mm_set_dolist subprogram.

Subprogram

MM_Get_DoList(Resource:IN)

Parameters

Name Description

IN parameters

Resource

This parameter specifies the source of the gripper DO list.

  • 0: Get the gripper DO list from Mech-Viz.

  • Positive integer: Get the gripper DO list from Mech-Vision. The positive integer is the Mech-Vision project ID.

Example

MM_Get_DoList(0)

This example stores the DO signal list obtained from Mech-Viz in Do_Port[i].

Set Gripper DO List

This subprogram sets the obtained DO signals to the robot’s gripper.

MM_Get_DoList must be called BEFORE this subprogram.

Subprogram

MM_Set_DoList()

Example

MM_Get_DoList(0)
MM_Set_DoList()

This example stores the DO signal list obtained from Mech-Viz in Do_Port[i], and then sets the values in Do_Port[i] to the corresponding DO signals in the robot program.

Calibration

This subprogram is used for hand-eye calibration (camera extrinsic parameter calibration). It automates the calibration process in conjunction with the Camera Calibration subprogram in Mech-Vision.

Subprogram

MM_CALIB(Move_Type:IN,PosJps:IN,WaitTime:IN,E1:IN)

Parameters

Name Description

IN parameters

Move_Type

The move type of the robot, 1 or 2. 1: MoveL. 2: MoveJ.

PosJps

Pose as flange pose or joint positions, 1 or 2. 1: Flange pose. 2: Joint positions.

WaitTime

The time the robot waits to avoid shaking after it moves to the calibration point; the default value is 2 (s).

E1

Data of the external 7th axis in mm.

Example

MM_CALIB(2,2,2,0)

This example moves the robot in Joint motion type, receives pose data in the form of joint positions, and sets the wait time to 2 seconds to avoid the robot from shaking after it moves to the calibration point. Moreover, the robot does not have an external axis installed.

Get Custom Output Data from Mech-Vision

This subprogram is used to obtain the vision result that includes custom port outputs from the corresponding Mech-Vision project. “Custom port outputs” refers to data output by ports other than poses and labels of the “Procedure Out” Step. The output ports can be customized if the Port Type parameter of the Step is set to “Custom”.

Subprogram

MM_GET_DY_DATA(Job:IN,Pos_Num:OUT,MM_Status:OUT)

Parameters

Name Description

IN parameters

Job

Mech-Vision project ID, which can be viewed before the project name in the Project List panel in Mech-Vision.

OUT parameters

Pos_Num

INT variable for storing the number of received vision points.

MM_Status

INT variable for storing the status code.

Example

MM_GET_DY_DATA(1,Pose_Num,Status)

This example obtains the vision result that includes custom port outputs from Mech-Vision project No.1. The number of vision points received is stored in Pose_Num, and the status code is stored in Status.

Save Custom Output data of Mech-Vision to Specified Variables

This subprogram stores the data in a vision point returned by Mech-Vision in the specified variables. This subprogram should be called AFTER Mech-Vision MM_Get_Dy_Data.

Subprogram

MM_GET_DYPOSE(Serial:IN,MM_P:OUT,MM_Label:OUT)

Parameters

Name Description

IN parameters

Serial

Specify the index of the vision point whose custom data need to be obtained.

OUT parameters

MM_P

Variable for storing the pose in the specified vision point.

MM_Label

REAL-typed variable for storing the label in the specified vision point.

MM_UserData

Predefined global variable for storing the custom port outputs in the specified vision point. The maximum length is 50.

Example

MM_GET_DYPOSE(1,XP1,Label)

This example stores the pose in the first received vision point to XP1, the corresponding label to Label, and the corresponding custom port outputs to MM_UserData.

Get Vision Move Data or Custom Output Data

This subprogram obtains the Vision Move output from the Mech-Vision project, or the Vision Move output or custom output from the Mech-Viz project.Call MM_Get_PlanPose or MM_Get_PlanJps to assign the received data to variables.

Subprogram

MM_GET_PLANDATA(Resource:IN,Jps_Pos:IN,Pos_Num:OUT,VisPos_Num:out,MM_Status:OUT)

Parameters

Name Description

IN parameters

Resource

This parameter specifies the source of the Vision Move output.

  • 0: Get Vision Move Data from Mech-Viz.

  • Positive integer: Get Vision Move output from Mech-Vision. The positive integer is the Mech-Vision project ID.

Jps_Pos

This parameter specifies the returned data format. Details are provided below.

OUT parameters

Pos_Num

Variable for storing the number of received waypoints.

VisPos_Num

Variable for storing the position of the first Vision Move waypoint in the path.

MM_Status

Variable for storing the status code.

  • When the value of Resource is 0, the valid value range of Jps_Pos is 1 to 4. Details are provided below.

    Value of Jps_Pos Format of returned data (Explained below)

    1

    Pose (joint positions), motion type, tool ID, velocity, element 1 in custom output data, … element N in custom output data

    2

    Pose (TCP), motion type, tool ID, velocity, element 1 in custom output data, … element N in custom output data

    3

    Pose (joint positions), motion type, tool ID, velocity, Mech-Viz Vision Move data, element 1 in custom output data, … element N in custom output data

    4

    Pose (TCP), motion type, tool ID, velocity, Mech-Viz Vision Move data, element 1 in custom output data, … element N in custom output data

  • When the value of Resource is a positive integer, the valid value range of Jps_Pos is 1 to 2. Details are provided below.

    Value of Jps_Pos Format of returned data (Explained below)

    1

    Pose (joint positions), motion type, tool ID, velocity, Mech-Vision Vision Move data

    2

    Pose (TCP), motion type, tool ID, velocity, Mech-Vision Vision Move data

Pose

The pose of waypoints can be either robot joint positions (JPs, measured in degrees) or tool center point (TCP, where the three-dimensional coordinates are measured in millimeters, and the Euler angles are measured in degrees), depending on the value of the parameter Jps_Pos in the subprogram called by the robot.

Motion type

  • 1: Joint motion (MOVEJ)

  • 2: Linear motion (MOVEL)

Tool ID

The ID of the tool to be used at this waypoint. The value “-1” means that no tool will be used at this waypoint.

Velocity

The velocity at this waypoint.

Vision Move data

Vision Move data: Refers to data output by the “Vision Move” Step in Mech-Vision or Mech-Viz, including labels of picked workobjects, number of picked workobjects, number of workobjects to be picked this time, edge/corner ID of vacuum gripper, TCP offset, orientation of workobject group, orientation of workobject, dimensions of workobject group.

Element in custom output data

“Custom output data” refers to the data output by ports other than poses and labels of the “Procedure Out” Step in the Mech-Vision project. The output ports can be customized if the “Port Type” parameter of the Step is set to “Custom”. The custom port outputs are arranged in alphabetical order of the custom port names.

Example

MM_GET_PLANDATA(0,2,Pose_Num,VisPos_Num,Status)

This example obtains the planned path that includes custom port outputs from Mech-Viz, and the value of Jps_Pos is 2. The number of waypoints received is stored in Pose_Num. The position of the Vision Move waypoint is stored in VisPose_Num. The status code is stored in Status.

Save Waypoint to Specified Variables

This subprogram is called AFTER MM_GET_PLANDATA to store the obtained data in variables. The obtained values are assigned to different variables based on the value of the Jps_Pos parameter in the MM_GET_PLANDATA subprogram.

Subprogram

MM_Get_PlanPose(Serial:IN,Jps_Pos:IN,MM_P:OUT,MM_MoveType:OUT,MM_ToolNum:OUT,MM_Speed:OUT) (When the value of Jps_Pos is 2 or 4)
MM_Get_PlanJps(Serial:IN,Jps_Pos:IN,MM_J:OUT,MM_MoveType:OUT,MM_ToolNum:OUT,MM_Speed:OUT)  (When the value of Jps_Pos is 1 or 3)

Parameters

Name Description

IN parameters

Serial

Specify the index of the waypoint to be stored.

Jps_Pos

The same as the value of Jps_Pos in the Get Vision Move Data or Custom Output Data subprogram.

OUT parameters

MM_P

Variable for storing the TCP in the specified waypoint.

MM_J

Variable for storing the joint positions in the specified waypoint.

MM_MoveType

Variable for storing the motion type in the specified waypoint. 1 stands for joint motion, and 2 stands for linear motion.

MM_ToolNum

Variable for storing the tool ID in the specified waypoint. The value “-1” means that no tool will be used at this waypoint.

MM_Speed

Variable for storing the velocity in the specified waypoint.

MM_UserData

Predefined global variable for storing the custom port outputs in the specified waypoint. The size of the array is 50.

MM_Plan_Results

Predefined global variable for storing the Vision Move data in the specified waypoint. The size of the array is 21.

Content of the MM_Plan_Results array is explained in the table below.

Value Description Variable

Labels of picked workobjects

Consists of 10 integers. By default, its value is ten 0s.

MM_Plan_Results[1] ~ MM_Plan_Results[10]

Number of picked workobjects

The total number of workobjects that have been picked.

MM_Plan_Results[11]

Number of workobjects to be picked this time

Number of workobjects to be picked this time

MM_Plan_Results[12]

Edge/corner ID of vacuum gripper

The ID of the edge/corner used to pick workobjects this time.

MM_Plan_Results[13]

TCP offset

The XYZ offset between the center of the workobject group and the tool center point.

MM_Plan_Results[14] ~ MM_Plan_Results[16]

Orientation of workobject group

The relative position between the workobject group and the length of the vacuum gripper. The value is 0 or 1, where 0 stands for parallel and 1 for vertical.

MM_Plan_Results[17]

Orientation of workobject

The relative position between the length of a workobject and that of the vacuum gripper. The value is 0 or 1, where 0 stands for parallel and 1 for vertical.

MM_Plan_Results[18]

Dimensions of the workobject group

The length, width and height of the workobject group to be picked this time.

MM_Plan_Results[19] ~ MM_Plan_Results[21]

Example

  • Example 1

    MM_Get_PlanPose(1,4,XP1,MoveType,ToolNum,Pose_Speed)

    This example stores the TCP in the first received waypoint to XP1, the corresponding motion type to MoveType, the corresponding tool ID to ToolNum, the corresponding velocity to Pose_Speed, the corresponding custom port outputs to MM_UserData, and the corresponding Vision Move data to MM_Plan_Results.

  • Example 2

    MM_Get_PlanJps(1,3,JP1,MoveType,ToolNum,Pose_Speed)

    This example stores the joint position in the first received waypoint to P1, the corresponding motion type to MoveType, the corresponding tool ID to ToolNum, the corresponding velocity to Pose_Speed, the corresponding custom port outputs to MM_UserData, and the corresponding Vision Move data to MM_Plan_Results.

Get Result of Step “Path Planning” in Mech-Vision

This subprogram obtains the collision-free path planned by the “Path Planning” Step from the corresponding Mech-Vision project.

The Port Type parameter of the “Procedure Out” Step in the Mech-Vision project must be set to “Predefined (robot path)”.

Subprogram

MM_GET_VISPATH(Job:IN,Jps_Pos:IN,Pos_Num:OUT,VisPos_Num:OUT,MM_Status:OUT)

Parameters

Name Description

IN parameters

Job

Mech-Vision project ID, which can be viewed before the project name in the Project List panel in Mech-Vision.

Jps_Pos

The pose type of waypoints returned by the “Path Planning” Step.
1: Waypoints will be returned in the form of joint positions.
2: Waypoints will be returned in the form of TCPs.

OUT parameters

Pos_Num

Variable for storing the number of received waypoints.

VisPos_Num

Variable for storing the position of the first Vision Move waypoint in the path. For example, if the path is composed of Steps Fixed-Point Move_1, Fixed-Point Move_2, Vision Move and Fixed-Point Move_3 sequentially, the position of Vision Move is 3. If the path does not contain “Vision Move”, the value of this parameter is 0.

MM_Status

Variable for storing the status code.

Example

MM_GET_VISPATH(1,1,Pose_Num,VisPos_Num,Status)

This example obtains the planned path from Mech-Vision project No.1 in the form of joint positions.The number of waypoints is stored in Pos_Num, the position of the Vision Move waypoint is stored in VisPos_Num, and the status code is stored in Status.

Read Mech-Viz Step Parameter

This subprogram reads the parameter value of a specific Step in the Mech-Viz project.

Subprogram

mm_get_property(Get_id:IN,MM_Status:OUT,Viz_Prop:OUT)

Parameters

Name Description

IN parameters

Get_id

This parameter corresponds to the Config ID field defined in the property_config file.

OUT parameters

MM_Status

An integer variable used to store the status code.

Viz_Prop

An integer variable used to store the returned parameter value of the specified Step.

From the toolbar of Mech-Vision, go to Robot Communication Configuration  Next  Advanced Settings. Click Property Configuration to open the property_config file.

get property config

Before calling this function, users should define a Config ID and its corresponding Step ID and parameter key name in the following format in the property_config file.

read, Config ID, Step ID, parameter key name

read

Indicates that this line is used to read the parameter value of a Step.

Config ID

Specifies a unique ID, which in a positive integer. One Config ID corresponds to only one parameter value of a Step. To read multiple parameter values, you should set different Config IDs.

Step ID

The Step ID of the Step whose parameter is to be read.

Parameter key name

Specifies the key name of the parameter whose value the robot requires to read.

  • User can check the parameter key name in the Key Query Tool. From the menu bar of Mech-Viz, go to Tools  Key Query Tool. Click a Step icon, and all key names of the Step will be displayed in the middle column. Each key name corresponds to a Step parameter name displayed in the parameter panel. You can also click a key name and check its corresponding parameter name in the “Details” panel.

    parameter key name

  • In the property_config file, lines starting with “#” are comments, which will not be executed by the program.

  • Remember to save the file after editing, and then restart the interface service on the toolbar of Mech-Vision.

The property_config file can have multiple read commands. The Config ID in these commands must be different.

Example

In the line below, “5” is the Config ID; “3” is the Step ID; and “xCount” is the parameter key name. Add this line to the property_config file. Add this line to the property_config file.

read, 5, 3, xCount

When the robot calls the subprogram below, it receives the value of the parameter whose key name is “xCount”.

mm_get_property(5,MM_Status,Viz_Prop)

This example stores the value of the parameter whose key name is “xCount” of Step 3 in the Mech-Viz project to the Viz_Prop variable, and stores the received status code to the “MM_Status” variable.

Set Mech-Viz Step Parameter

This subprogram sets the parameter value of a specific Step in the Mech-Viz project.

Subprogram

mm_set_property(Set_id:IN,MM_Status:OUT)

Parameters

Name Description

IN parameters

Set_id

This parameter corresponds to the Config ID field defined in the property_config file.

OUT parameters

MM_Status

An integer variable used to store the status code.

From the toolbar of Mech-Vision, go to Robot Communication Configuration  Next  Advanced Settings. Click Property Configuration to open the property_config file.

get property config

Before sending this command, users should define a Config ID and its corresponding Step ID, parameter key name and parameter value in the following format in the property_config file.

write, Config ID, Step ID, parameter key name, parameter value

write

Indicates that this line is used to set the parameter value of a Step.

Config ID

Specifies an ID, which is a positive integer and can be used repeatedly.

Step ID

Specifies the Step whose parameter value the robot requires to read.

Parameter key name

Specifies the key name of the parameter whose value the robot requires to set.

Parameter value

Specifies the value that the robot sets for the parameter.

  • The property_config file can contain more than one “write” command, and these commands can use a Config ID repeatedly. That is, one Config ID can be used to set values for multiple parameters.

  • User can check the parameter key name in the Key Query Tool. From the menu bar of Mech-Viz, go to Tools  Key Query Tool. Click a Step icon, and all key names of the Step will be displayed in the middle column. Each key name corresponds to a Step parameter name displayed in the parameter panel. You can also click a key name and check its corresponding parameter name in the “Details” panel.

    parameter key name

  • In the property_config file, lines starting with “#” are comments, which will not be executed by the program.

  • Remember to save the file after editing, and then restart the interface service on the toolbar of Mech-Vision.

Example

In the line below, “1” is the Config ID, and “3” is the Step ID. “xOffset”, “yOffset” and “zOffset” are parameter key names; and “10”, “20” and “30” are their respective values. Add this line to the property_config file.

write, 1, 3, xOffset, 10
write, 1, 3, yOffset, 20
write, 1, 3, zOffset, 30

When the robot calls the subprogram below, Mech-Viz sets the values of the parameters whose key names are “xOffset”, “yOffset” and “zOffset” respectively to “10”, “20” and “30”.

mm_set_property(1,MM_Status)

This example sets the values of the parameters whose key names are “xOffset”, “yOffset” and “zOffset” respectively to “10”, “20” and “30”, and stores the received status code in the “MM_Status” variable.

Get Message from Notify Step

After the Mech-Vision or Mech-Viz project is triggered, this subprogram can be called to get message from the “Notify” Step.

Subprogram

MM_Get_Notify(MM_NotifyMsg:OUT)

Parameters

Name Description

OUT parameters

MM_NotifyMsg

INT variable for storing the message from the “Notify” Step. Only integers are supported by now.

Example

MM_Get_Notify(MM_NotifyMsg)

In this example, the message from the “Notify” Step is stored in the variable MM_NotifyMsg.

Stop Mech-Viz Project

This subprogram stops the Mech-Viz project.

Subprogram

MM_Stop_Viz()

Example

MM_Stop_Viz()

In this example, the robot programs calls the subprogram to stop the Mech-Viz project.

We Value Your Privacy

We use cookies to provide you with the best possible experience on our website. By continuing to use the site, you acknowledge that you agree to the use of cookies. If you decline, a single cookie will be used to ensure you're not tracked or remembered when you visit this website.

  • Preference
  • I accept
  • I don't accept