MachCustomizeWiki - New pages [en]

UserDROs & UserLEDs

Awander — Mon, 02 Mar 2009 22:02:05 GMT

Summary:

Below is from an email from Art Fenerty to the mach1mach2cnc group:
----
'''UserDROs and UserLEDs'''

There are 255 user DROs and 255 User Leds.

They are used by dropping an LED or DRO on the screen,
and giving it an OEM value of 1000 plus the DRO number.

So a DRO of OEM number 1001 is UserDRO #1...etc...

They can be set or controlled by the macro commands:

SetUserDRO( 1, 2.345 ); for example
or
SetUserLED ( 1, 1) to turn on an LED, or (1,0) to turn it off...
----

I found, when using a UserDRO, I had to give the DRO on screen the OEM Value 1900, and also had to use GetUserDRO( 1900 )

[not GetUserDRO( 900 ) as is stated in Art's message]

Rs274ngc.h

Steffen — Mon, 08 Dec 2008 11:12:22 GMT

Summary:

==Head==
#ifndef RS274NGC_HH
#define RS274NGC_HH

==defines==
#define AA
#define BB
#define CC
/*
rs274ngc.hh

Declarations for the rs274abc translator.

*/

/**********************/
/* INCLUDE DIRECTIVES */
/**********************/

#include <stdio.h>
#include "canon.h"

/**********************/
/* COMPILER MACROS */
/**********************/

#define AND &&
#define IS ==
#define ISNT !=
#define MAX(x, y) ((x) > (y) ? (x) : (y))
#define NOT !
#define OR ||
#define SET_TO =

#ifndef TRUE
#define TRUE 1
#endif

#ifndef FALSE
#define FALSE 0
#endif

#define RS274NGC_TEXT_SIZE 256

/* numerical constants */
#define TOLERANCE_INCH 0.5
#define TOLERANCE_MM 12.5
#define TOLERANCE_CONCAVE_CORNER 0.2 /* angle threshold for concavity for
cutter compensation, in radians */
#define TINY 1e-12 /* for arc_data_r */
#define UNKNOWN 1e-20
#define TWO_PI 6.2831853071795864

#ifndef PI
#define PI 3.1415926535897932
#endif

#ifndef PI2
#define PI2 1.5707963267948966
#endif

// array sizes
#define RS274NGC_ACTIVE_G_CODES 13
#define RS274NGC_ACTIVE_M_CODES 7
#define RS274NGC_ACTIVE_SETTINGS 3

// name of parameter file for saving/restoring interpreter variables
#define RS274NGC_PARAMETER_FILE_NAME_DEFAULT "rs274ngc.var"
#define RS274NGC_PARAMETER_FILE_BACKUP_SUFFIX ".bak"

// max number of m codes on one line
#define MAX_EMS 4

// English - Metric conversion (long number keeps error buildup down)
#define MM_PER_INCH 25.4
#define INCH_PER_MM 0.039370078740157477

// on-off switch settings
#define OFF 0
#define ON 1

// feed_mode
#define UNITS_PER_MINUTE 0
#define INVERSE_TIME 1
#define UNITS_PER_REV 2

// cutter radius compensation mode, OFF already defined to 0
// not using CANON_SIDE since interpreter handles cutter radius comp
#define RIGHT 1
#define LEFT 2

// number of parameters in parameter table
#define RS274NGC_MAX_PARAMETERS 15000

// unary operations
// These are not enums because the "&" operator is used in
// reading the operation names and is illegal with an enum

#define ABS 1
#define ACOS 2
#define ASIN 3
#define ATAN 4
#define COS 5
#define EXP 6
#define FIX 7
#define FUP 8
#define LN 9
#define ROUND 10
#define SIN 11
#define SQRT 12
#define TAN 13

// binary operations
#define NO_OPERATION 0
#define DIVIDED_BY 1
#define MODULO 2
#define POWER 3
#define TIMES 4
#define AND2 5
#define EXCLUSIVE_OR 6
#define MINUS 7
#define NON_EXCLUSIVE_OR 8
#define PLUS 9
#define RIGHT_BRACKET 10

// G Codes are symbolic to be dialect-independent in source code
#define G_0 0
#define G_1 10
#define G_2 20
#define G_3 30
#define G_4 40
#define G_8 80
#define G_9 90
#define G_10 100
#define G_12 120
#define G_13 130
#define G_15 150
#define G_16 160
#define G_17 170
#define G_18 180
#define G_19 190
#define G_20 200
#define G_21 210
#define G_28 280
#define G_28_1 281
#define G_30 300
#define G_31 310
#define G_32 320
#define G_38_2 382
#define G_40 400
#define G_40_1 401
#define G_40_2 402
#define G_41 410
#define G_42 420
#define G_43 430
#define G_44 440
#define G_48 480
#define G_49 490
#define G_50 500
#define G_51 510
#define G_52 520
#define G_53 530
#define G_54 540
#define G_55 550
#define G_56 560
#define G_57 570
#define G_58 580
#define G_59 590
#define G_59_1 591
#define G_59_2 592
#define G_59_3 593
#define G_61 610
#define G_61_1 611
#define G_64 640
#define G_65 650
#define G_68 680
#define G_69 690
#define G_70 700
#define G_71 710
#define G_73 730
#define G_76 760
#define G_77 770
#define G_78 780
#define G_80 800
#define G_801 801
#define G_802 802
#define G_81 810
#define G_82 820
#define G_83 830
#define G_831 831
#define G_832 832
#define G_84 840
#define G_85 850
#define G_86 860
#define G_87 870
#define G_88 880
#define G_89 890
#define G_90 900
#define G_901 901
#define G_91 910
#define G_911 911
#define G_92 920
#define G_92_1 921
#define G_92_2 922
#define G_92_3 923
#define G_93 930
#define G_94 940
#define G_95 950
#define G_96 960
#define G_97 970
#define G_98 980
#define G_99 990

#define RS274NGC_OK 0
#define RS274NGC_EXIT 1
#define RS274NGC_EXECUTE_FINISH 2
#define RS274NGC_ENDFILE 3
#define NCE_A_FILE_IS_ALREADY_OPEN 4
#define NCE_ALL_AXES_MISSING_WITH_G92 5
#define NCE_ALL_AXES_MISSING_WITH_MOTION_CODE 6
#define NCE_ARC_RADIUS_TOO_SMALL_TO_REACH_END_POINT 7
#define NCE_ARGUMENT_TO_ACOS_OUT_OF_RANGE 8
#define NCE_ARGUMENT_TO_ASIN_OUT_OF_RANGE 9
#define NCE_ATTEMPT_TO_DIVIDE_BY_ZERO 10
#define NCE_ATTEMPT_TO_RAISE_NEGATIVE_TO_NON_INTEGER_POWER 11
#define NCE_BAD_CHARACTER_USED 12
#define NCE_BAD_FORMAT_UNSIGNED_INTEGER 13
#define NCE_BAD_NUMBER_FORMAT 14
#define NCE_BUG_BAD_G_CODE_MODAL_GROUP_0 15
#define NCE_BUG_CODE_NOT_G0_OR_G1 16
#define NCE_BUG_CODE_NOT_G17_G18_OR_G19 17
#define NCE_BUG_CODE_NOT_G20_OR_G21 18
#define NCE_BUG_CODE_NOT_G28_OR_G30 19
#define NCE_BUG_CODE_NOT_G2_OR_G3 20
#define NCE_BUG_CODE_NOT_G40_G41_OR_G42 21
#define NCE_BUG_CODE_NOT_G43_OR_G49 22
#define NCE_BUG_CODE_NOT_G4_G10_G28_G30_G53_OR_G92_SERIES 23
#define NCE_BUG_CODE_NOT_G61_G61_1_OR_G64 24
#define NCE_BUG_CODE_NOT_G90_OR_G91 25
#define NCE_BUG_CODE_NOT_G93_OR_G94 26
#define NCE_BUG_CODE_NOT_G98_OR_G99 27
#define NCE_BUG_CODE_NOT_IN_G92_SERIES 28
#define NCE_BUG_CODE_NOT_IN_RANGE_G54_TO_G593 29
#define NCE_BUG_CODE_NOT_M0_M1_M2_M30_M60 30
#define NCE_BUG_DISTANCE_MODE_NOT_G90_OR_G91 31
#define NCE_BUG_FUNCTION_SHOULD_NOT_HAVE_BEEN_CALLED 32
#define NCE_BUG_IN_TOOL_RADIUS_COMP 33
#define NCE_BUG_PLANE_NOT_XY_YZ_OR_XZ 34
#define NCE_BUG_SIDE_NOT_RIGHT_OR_LEFT 35
#define NCE_BUG_UNKNOWN_MOTION_CODE 36
#define NCE_BUG_UNKNOWN_OPERATION 37
#define NCE_CANNOT_CHANGE_AXIS_OFFSETS_WITH_CUTTER_RADIUS_COMP 38
#define NCE_CANNOT_CHANGE_UNITS_WITH_CUTTER_RADIUS_COMP 39
#define NCE_CANNOT_CREATE_BACKUP_FILE 40
#define NCE_CANNOT_DO_G1_WITH_ZERO_FEED_RATE 41
#define NCE_CANNOT_DO_ZERO_REPEATS_OF_CYCLE 42
#define NCE_CANNOT_MAKE_ARC_WITH_ZERO_FEED_RATE 43
#define NCE_CANNOT_MOVE_ROTARY_AXES_DURING_PROBING 44
#define NCE_CANNOT_OPEN_BACKUP_FILE 45
#define NCE_CANNOT_OPEN_VARIABLE_FILE 46
#define NCE_CANNOT_PROBE_IN_INVERSE_TIME_FEED_MODE 47
#define NCE_CANNOT_PROBE_WITH_CUTTER_RADIUS_COMP_ON 48
#define NCE_CANNOT_PROBE_WITH_ZERO_FEED_RATE 49
#define NCE_CANNOT_PUT_A_B_IN_CANNED_CYCLE 50
#define NCE_CANNOT_PUT_A_C_IN_CANNED_CYCLE 51
#define NCE_CANNOT_PUT_AN_A_IN_CANNED_CYCLE 52
#define NCE_CANNOT_TURN_CUTTER_RADIUS_COMP_ON_OUT_OF_XY_PLANE 53
#define NCE_CANNOT_TURN_CUTTER_RADIUS_COMP_ON_WHEN_ON 54
#define NCE_CANNOT_USE_A_WORD 55
#define NCE_CANNOT_USE_AXIS_VALUES_WITH_G80 56
#define NCE_CANNOT_USE_AXIS_VALUES_WITHOUT_A_G_CODE_THAT_USES_THEM 57
#define NCE_CANNOT_USE_B_WORD 58
#define NCE_CANNOT_USE_C_WORD 59
#define NCE_CANNOT_USE_G28_OR_G30_WITH_CUTTER_RADIUS_COMP 60
#define NCE_CANNOT_USE_G53_INCREMENTAL 61
#define NCE_CANNOT_USE_G53_WITH_CUTTER_RADIUS_COMP 62
#define NCE_CANNOT_USE_TWO_G_CODES_THAT_BOTH_USE_AXIS_VALUES 63
#define NCE_CANNOT_USE_XZ_PLANE_WITH_CUTTER_RADIUS_COMP 64
#define NCE_CANNOT_USE_YZ_PLANE_WITH_CUTTER_RADIUS_COMP 65
#define NCE_COMMAND_TOO_LONG 66
#define NCE_CONCAVE_CORNER_WITH_CUTTER_RADIUS_COMP 67
#define NCE_COORDINATE_SYSTEM_INDEX_PARAMETER_5220_OUT_OF_RANGE 68
#define NCE_CURRENT_POINT_SAME_AS_END_POINT_OF_ARC 69
#define NCE_CUTTER_GOUGING_WITH_CUTTER_RADIUS_COMP 70
#define NCE_D_WORD_WITH_NO_G41_OR_G42 71
#define NCE_DWELL_TIME_MISSING_WITH_G4 72
#define NCE_DWELL_TIME_P_WORD_MISSING_WITH_G82 73
#define NCE_DWELL_TIME_P_WORD_MISSING_WITH_G86 74
#define NCE_DWELL_TIME_P_WORD_MISSING_WITH_G88 75
#define NCE_DWELL_TIME_P_WORD_MISSING_WITH_G89 76
#define NCE_EQUAL_SIGN_MISSING_IN_PARAMETER_SETTING 77
#define NCE_F_WORD_MISSING_WITH_INVERSE_TIME_ARC_MOVE 78
#define NCE_F_WORD_MISSING_WITH_INVERSE_TIME_G1_MOVE 79
#define NCE_FILE_ENDED_WITH_NO_PERCENT_SIGN 80
#define NCE_FILE_ENDED_WITH_NO_PERCENT_SIGN_OR_PROGRAM_END 81
#define NCE_FILE_NAME_TOO_LONG 82
#define NCE_FILE_NOT_OPEN 83
#define NCE_G_CODE_OUT_OF_RANGE 84
#define NCE_H_WORD_WITH_NO_G43 85
#define NCE_I_WORD_GIVEN_FOR_ARC_IN_YZ_PLANE 86
#define NCE_I_WORD_MISSING_WITH_G87 87
#define NCE_I_WORD_WITH_NO_G2_OR_G3_OR_G87_TO_USE_IT 88
#define NCE_J_WORD_GIVEN_FOR_ARC_IN_XZ_PLANE 89
#define NCE_J_WORD_MISSING_WITH_G87 90
#define NCE_J_WORD_WITH_NO_G2_OR_G3_OR_G87_TO_USE_IT 91
#define NCE_K_WORD_GIVEN_FOR_ARC_IN_XY_PLANE 92
#define NCE_K_WORD_MISSING_WITH_G87 93
#define NCE_K_WORD_WITH_NO_G2_OR_G3_OR_G87_TO_USE_IT 94
#define NCE_L_WORD_WITH_NO_CANNED_CYCLE_OR_G10 95
#define NCE_LEFT_BRACKET_MISSING_AFTER_SLASH_WITH_ATAN 96
#define NCE_LEFT_BRACKET_MISSING_AFTER_UNARY_OPERATION_NAME 97
#define NCE_LINE_NUMBER_GREATER_THAN_99999 98
#define NCE_LINE_WITH_G10_DOES_NOT_HAVE_L2 99
#define NCE_M_CODE_GREATER_THAN_99 100
#define NCE_MIXED_RADIUS_IJK_FORMAT_FOR_ARC 101
#define NCE_MULTIPLE_A_WORDS_ON_ONE_LINE 102
#define NCE_MULTIPLE_B_WORDS_ON_ONE_LINE 103
#define NCE_MULTIPLE_C_WORDS_ON_ONE_LINE 104
#define NCE_MULTIPLE_D_WORDS_ON_ONE_LINE 105
#define NCE_MULTIPLE_F_WORDS_ON_ONE_LINE 106
#define NCE_MULTIPLE_H_WORDS_ON_ONE_LINE 107
#define NCE_MULTIPLE_I_WORDS_ON_ONE_LINE 108
#define NCE_MULTIPLE_J_WORDS_ON_ONE_LINE 109
#define NCE_MULTIPLE_K_WORDS_ON_ONE_LINE 110
#define NCE_MULTIPLE_L_WORDS_ON_ONE_LINE 111
#define NCE_MULTIPLE_P_WORDS_ON_ONE_LINE 112
#define NCE_MULTIPLE_Q_WORDS_ON_ONE_LINE 113
#define NCE_MULTIPLE_R_WORDS_ON_ONE_LINE 114
#define NCE_MULTIPLE_S_WORDS_ON_ONE_LINE 115
#define NCE_MULTIPLE_T_WORDS_ON_ONE_LINE 116
#define NCE_MULTIPLE_X_WORDS_ON_ONE_LINE 117
#define NCE_MULTIPLE_Y_WORDS_ON_ONE_LINE 118
#define NCE_MULTIPLE_Z_WORDS_ON_ONE_LINE 119
#define NCE_MUST_USE_G0_OR_G1_WITH_G53 120
#define NCE_NEGATIVE_ARGUMENT_TO_SQRT 121
#define NCE_NEGATIVE_D_WORD_TOOL_RADIUS_INDEX_USED 122
#define NCE_NEGATIVE_F_WORD_USED 123
#define NCE_NEGATIVE_G_CODE_USED 124
#define NCE_NEGATIVE_H_WORD_TOOL_LENGTH_OFFSET_INDEX_USED 125
#define NCE_NEGATIVE_L_WORD_USED 126
#define NCE_NEGATIVE_M_CODE_USED 127
#define NCE_NEGATIVE_OR_ZERO_Q_VALUE_USED 128
#define NCE_NEGATIVE_P_WORD_USED 129
#define NCE_NEGATIVE_SPINDLE_SPEED_USED 130
#define NCE_NEGATIVE_TOOL_ID_USED 131
#define NCE_NESTED_COMMENT_FOUND 132
#define NCE_NO_CHARACTERS_FOUND_IN_READING_REAL_VALUE 133
#define NCE_NO_DIGITS_FOUND_WHERE_REAL_NUMBER_SHOULD_BE 134
#define NCE_NON_INTEGER_VALUE_FOR_INTEGER 135
#define NCE_NULL_MISSING_AFTER_NEWLINE 136
#define NCE_OFFSET_INDEX_MISSING 137
#define NCE_P_VALUE_NOT_AN_INTEGER_WITH_G10_L2 138
#define NCE_P_VALUE_OUT_OF_RANGE_WITH_G10_L2 139
#define NCE_P_WORD_WITH_NO_G4_G10_G82_G86_G88_G89 140
#define NCE_PARAMETER_FILE_OUT_OF_ORDER 141
#define NCE_PARAMETER_NUMBER_OUT_OF_RANGE 142
#define NCE_Q_WORD_MISSING_WITH_G83 143
#define NCE_Q_WORD_WITH_NO_G83 144
#define NCE_QUEUE_IS_NOT_EMPTY_AFTER_PROBING 145
#define NCE_R_CLEARANCE_PLANE_UNSPECIFIED_IN_CYCLE 146
#define NCE_R_I_J_K_WORDS_ALL_MISSING_FOR_ARC 147
#define NCE_R_LESS_THAN_X_IN_CYCLE_IN_YZ_PLANE 148
#define NCE_R_LESS_THAN_Y_IN_CYCLE_IN_XZ_PLANE 149
#define NCE_R_LESS_THAN_Z_IN_CYCLE_IN_XY_PLANE 150
#define NCE_R_WORD_WITH_NO_G_CODE_THAT_USES_IT 151
#define NCE_RADIUS_TO_END_OF_ARC_DIFFERS_FROM_RADIUS_TO_START 152
#define NCE_RADIUS_TOO_SMALL_TO_REACH_END_POINT 153
#define NCE_REQUIRED_PARAMETER_MISSING 154
#define NCE_SELECTED_TOOL_SLOT_NUMBER_TOO_LARGE 155
#define NCE_SLASH_MISSING_AFTER_FIRST_ATAN_ARGUMENT 156
#define NCE_SPINDLE_NOT_TURNING_CLOCKWISE_IN_G84 157
#define NCE_SPINDLE_NOT_TURNING_IN_G86 158
#define NCE_SPINDLE_NOT_TURNING_IN_G87 159
#define NCE_SPINDLE_NOT_TURNING_IN_G88 160
#define NCE_SSCANF_FAILED 161
#define NCE_START_POINT_TOO_CLOSE_TO_PROBE_POINT 162
#define NCE_TOO_MANY_M_CODES_ON_LINE 163
#define NCE_TOOL_LENGTH_OFFSET_INDEX_TOO_BIG 164
#define NCE_TOOL_MAX_TOO_LARGE 165
#define NCE_TOOL_RADIUS_INDEX_TOO_BIG 166
#define NCE_TOOL_RADIUS_NOT_LESS_THAN_ARC_RADIUS_WITH_COMP 167
#define NCE_TWO_G_CODES_USED_FROM_SAME_MODAL_GROUP 168
#define NCE_TWO_M_CODES_USED_FROM_SAME_MODAL_GROUP 169
#define NCE_UNABLE_TO_OPEN_FILE 170
#define NCE_UNCLOSED_COMMENT_FOUND 171
#define NCE_UNCLOSED_EXPRESSION 172
#define NCE_UNKNOWN_G_CODE_USED 173
#define NCE_UNKNOWN_M_CODE_USED 174
#define NCE_UNKNOWN_OPERATION 175
#define NCE_UNKNOWN_OPERATION_NAME_STARTING_WITH_A 176
#define NCE_UNKNOWN_OPERATION_NAME_STARTING_WITH_M 177
#define NCE_UNKNOWN_OPERATION_NAME_STARTING_WITH_O 178
#define NCE_UNKNOWN_OPERATION_NAME_STARTING_WITH_X 179
#define NCE_UNKNOWN_WORD_STARTING_WITH_A 180
#define NCE_UNKNOWN_WORD_STARTING_WITH_C 181
#define NCE_UNKNOWN_WORD_STARTING_WITH_E 182
#define NCE_UNKNOWN_WORD_STARTING_WITH_F 183
#define NCE_UNKNOWN_WORD_STARTING_WITH_L 184
#define NCE_UNKNOWN_WORD_STARTING_WITH_R 185
#define NCE_UNKNOWN_WORD_STARTING_WITH_S 186
#define NCE_UNKNOWN_WORD_STARTING_WITH_T 187
#define NCE_UNKNOWN_WORD_WHERE_UNARY_OPERATION_COULD_BE 188
#define NCE_X_AND_Y_WORDS_MISSING_FOR_ARC_IN_XY_PLANE 189
#define NCE_X_AND_Z_WORDS_MISSING_FOR_ARC_IN_XZ_PLANE 190
#define NCE_X_VALUE_UNSPECIFIED_IN_YZ_PLANE_CANNED_CYCLE 191
#define NCE_X_Y_AND_Z_WORDS_ALL_MISSING_WITH_G38_2 192
#define NCE_Y_AND_Z_WORDS_MISSING_FOR_ARC_IN_YZ_PLANE 193
#define NCE_Y_VALUE_UNSPECIFIED_IN_XZ_PLANE_CANNED_CYCLE 194
#define NCE_Z_VALUE_UNSPECIFIED_IN_XY_PLANE_CANNED_CYCLE 195
#define NCE_ZERO_OR_NEGATIVE_ARGUMENT_TO_LN 196
#define NCE_ZERO_RADIUS_ARC 197
#define NCE_F_WORD_MISSING_WITH_THREADING 198
#define NCE_NO_SUBROUTINE_SPECIFIED 199
#define NCE_NO_SPINDLE_SPEED_WITH_G96 200
#define NCE_NO_SPINDLE_SPEED_WITH_G97 201
#define NCE_NO_R_WITH_ROTATION 202
#define NCE_NO_A_OR_B_WITH_ROTATION 203
#define NCE_NOG43INTURN 204
#define NCE_MULTIPLE_E_WORDS_ON_ONE_LINE 205

#define RS274NGC_MIN_ERROR 3
#define RS274NGC_MAX_ERROR 199
#define SEMI_COLON 999;

==typedefs==
/**********************/
/* TYPEDEFS */
/**********************/

/* distance_mode */
typedef enum
{ MODE_ABSOLUTE, MODE_INCREMENTAL } DISTANCE_MODE;

/* retract_mode for cycles */
typedef enum
{ R_PLANE, OLD_Z } RETRACT_MODE;

typedef int ON_OFF;

typedef struct block_struct
{
#ifdef AA
ON_OFF a_flag;
double a_number;
#endif
#ifdef BB
ON_OFF b_flag;
double b_number;
#endif
#ifdef CC
ON_OFF c_flag;
double c_number;
#endif
char comment[256];
int d_number;
int e_number;
double f_number;
int g_modes[14];

int h_number;
double h_double;
ON_OFF h_flag;

ON_OFF i_flag;
double i_number;
ON_OFF j_flag;
double j_number;
ON_OFF k_flag;
double k_number;
int l_number;
double l_double;
ON_OFF l_flag;
int line_number;
int motion_to_be;
int m_count;
int m_modes[10];
double p_number;
double q_number;
ON_OFF q_flag;
ON_OFF r_flag;
double r_number;
double s_number;
double t_number;
ON_OFF x_flag;
double x_number;
ON_OFF y_flag;
double y_number;
ON_OFF z_flag;
double z_number;
} block;

typedef block *block_pointer;

/*The current_x, current_y, and current_z are the location of the tool
in the current coordinate system. current_x and current_y differ from
program_x and program_y when cutter radius compensation is on.
current_z is the position of the tool tip in program coordinates when
tool length compensation is using the actual tool length; it is the
position of the spindle when tool length is zero.

In a setup, the axis_offset values are set by g92 and the origin_offset
values are set by g54 - g59.3. The net origin offset uses both values
and is not represented here

*/

typedef struct setup_struct
{

double AA_axis_offset; // A-axis g92 offset
double AA_current; // current A-axis position
double AA_origin_offset; // A-axis origin offset

double BB_axis_offset; // B-axis g92offset
double BB_current; // current B-axis position
double BB_origin_offset; // B-axis origin offset

double CC_axis_offset; // C-axis g92offset
double CC_current; // current C-axis position
double CC_origin_offset; // C-axis origin offset

int active_g_codes[RS274NGC_ACTIVE_G_CODES]; // array of active G codes
int active_m_codes[RS274NGC_ACTIVE_M_CODES]; // array of active M codes
double active_settings[RS274NGC_ACTIVE_SETTINGS]; // array of feed, speed, etc.
double axis_offset_x; // X-axis g92 offset
double axis_offset_y; // Y-axis g92 offset
double axis_offset_z; // Z-axis g92 offset
block block1; // parsed next block
char blocktext[RS274NGC_TEXT_SIZE]; // linetext downcased, white space gone
CANON_MOTION_MODE control_mode; // exact path or cutting mode
int current_slot; // carousel slot number of current tool
int current_offset_slot; //for turn offsets, current slot in use.
int current_tip; //current tip direction.
double cutter_tip_radius; //for turn offsets
// bool cutter_tip_on; // lathe tip radisu on/off
double current_x; // current X-axis position
double current_y; // current Y-axis position
double current_z; // current Z-axis position
double cutter_comp_radius; // current cutter compensation radius
int cutter_comp_side; // current cutter compensation side
double cycle_cc; // cc-value (normal) for canned cycles
double cycle_i; // i-value for canned cycles
double cycle_j; // j-value for canned cycles
double cycle_k; // k-value for canned cycles
int cycle_l; // l-value for canned cycles
double cycle_p; // p-value (dwell) for canned cycles
double cycle_q; // q-value for canned cycles
double cycle_r; // r-value for canned cycles
DISTANCE_MODE distance_mode; // absolute or incremental
int feed_mode; // G_93 (inverse time) or G_94 units/min
int spindle_mode;
ON_OFF feed_override; // whether feed override is enabled
double feed_rate; // feed rate in current units/min
char filename[RS274NGC_TEXT_SIZE]; // name of currently open NC code file
FILE *file_pointer; // file pointer for open NC code file
ON_OFF flood; // whether flood coolant is on
int length_offset_index; // for use with tool length offsets
int length_units; // millimeters or inches
int line_length; // length of line last read
char linetext[RS274NGC_TEXT_SIZE]; // text of most recent line read
ON_OFF mist; // whether mist coolant is on
int motion_mode; // active G-code for motion
int origin_index; // active origin (1=G54 to 9=G59.3)
double origin_offset_x; // origin offset x
double origin_offset_y; // origin offset y
double origin_offset_z; // origin offset z
double parameters[RS274NGC_MAX_PARAMETERS]; // system parameters
int parameter_occurrence; // parameter buffer index
int parameter_numbers[50]; // parameter number buffer
double parameter_values[50]; // parameter value buffer
ON_OFF percent_flag; // ON means first line was percent sign
CANON_PLANE plane; // active plane, XY-, YZ-, or XZ-plane
ON_OFF probe_flag; // flag indicating probing done
double program_x; // program x, used when cutter comp on
double program_y; // program y, used when cutter comp on
double program_z; // used in tnc
RETRACT_MODE retract_mode; // for cycles, old_z or r_plane
int selected_tool_slot; // tool slot selected but not active
int sequence_number; // sequence number of line last read
double speed; // current spindle speed in rpm
CANON_SPEED_FEED_MODE speed_feed_mode; // independent or synched
ON_OFF speed_override; // whether speed override is enabled
CANON_DIRECTION spindle_turning; // direction spindle is turning
int stack_index; // index into the stack
double tool_length_offset; // current tool length offset
double tool_xoffset;
int dummy;
int tool_max; // highest number tool slot in carousel
int tool_table_index; // tool index used with cutter comp
double traverse_rate; // rate for traverse motions
int IJMode;
double CurrentOrigins[6];
bool AutoTurnOff;
bool AutoEStop;
bool RadiusCompOff;
bool AutoToolOff;
int OverRideTime;
bool OptionalStop;
bool Rewind;
bool ProgramSafety;
bool HotKeyCheck;
double JogPercent;
int ColorUnRef;
int ColorRef;
int ColorBac;
bool GougeCheck;
double xscale,
yscale,
zscale,
ascale,
bscale,
cscale;
bool xmirror,
ymirror,
zmirror,
amirror,
bmirror,
cmirror;
double Diameters[3];
bool startagain;
bool drawtocenter;
bool G92Off;
bool OriginsOff;
int LightLine;
bool ForceRefresh;
char stack[50][80]; // stack of calls for error reporting
bool Threading;
double Cylinder;
bool MillMode;

//threading variables...
double XStart;
double ZStart;
double XEnd;
double ZEnd;
int Spring;
double Pitch;
double Passes;
double DepthCut;
double Infeed;
double Chamfer;
double ClearanceX;
double ClearanceZ;
double DepthLastPass;
double MinPerPass;
double Taper;
double Tapers[256];
double ThreadDepths[256];
double InFeeds[256];
double IncludedAngle;
block MacroBlock;
bool polar;
double polarx;
double polary;
double polAngle;
double polRadius;
double G73PullOff;
int LastMotionMode;
bool Diameter;
bool Redraw;
int CutType;
int InFeedType;
double tempspeed;
double Rotation;
double RotationX;
double RotationY;
double PausedAt[6];
double CSSLimit;
double peck;
bool CompInUse;
} setup;

typedef setup *setup_pointer;

// pointer to function that reads
typedef int (*read_function_pointer) (char *, int *, block_pointer, double *);

/*************************************************************************/
/*

==Interface==

Interface functions to call to tell the interpreter what to do.
Return values indicate status of execution.
These functions may change the state of the interpreter.

*/

// close the currently open NC code file
extern int rs274ngc_close ();

// execute a line of NC code
#ifndef NOT_OLD_EMC_INTERP_COMPATIBLE
extern int rs274ngc_execute (const char *command = 0);
#else
extern int rs274ngc_execute ();
#endif

// stop running
extern int rs274ngc_exit ();

// get ready to run
extern int rs274ngc_init ();

// load a tool table
extern int rs274ngc_load_tool_table ();

// open a file of NC code
extern int rs274ngc_open (const char *filename);

// read the mdi or the next line of the open NC code file
extern int rs274ngc_read (const char *mdi = 0);

// reset yourself
extern int rs274ngc_reset ();

// restore interpreter variables from a file
extern int rs274ngc_restore_parameters (const char *filename);

// save interpreter variables to file
extern int rs274ngc_save_parameters (const char *filename, const double parameters[]);

// synchronize your internal model with the external world
extern int rs274ngc_synch ();

/*************************************************************************/
/*

Interface functions to call to get information from the interpreter.
If a function has a return value, the return value contains the information.
If a function returns nothing, information is copied into one of the
arguments to the function. These functions do not change the state of
the interpreter.

*/

// copy active G codes into array [0]..[11]
extern void rs274ngc_active_g_codes (int *codes);

// copy active M codes into array [0]..[6]
extern void rs274ngc_active_m_codes (int *codes);

// copy active F, S settings into array [0]..[2]
extern void rs274ngc_active_settings (double *settings);

// copy the text of the error message whose number is error_code into the
// error_text array, but stop at max_size if the text is longer.
extern void rs274ngc_error_text (int error_code, char *error_text, int max_size);

// copy the name of the currently open file into the file_name array,
// but stop at max_size if the name is longer
extern void rs274ngc_file_name (char *file_name, int max_size);

// return the length of the most recently read line
extern int rs274ngc_line_length ();

// copy the text of the most recently read line into the line_text array,
// but stop at max_size if the text is longer
extern void rs274ngc_line_text (char *line_text, int max_size);

// return the current sequence number (how many lines read)
extern int rs274ngc_sequence_number ();

// copy the function name from the stack_index'th position of the
// function call stack at the time of the most recent error into
// the function name string, but stop at max_size if the name is longer
extern void rs274ngc_stack_name (int stack_index, char *function_name, int max_size);

#ifndef NOT_OLD_EMC_INTERP_COMPATABLE
// Get the parameter file name from the ini file.
extern int rs274ngc_ini_load (const char *filename);
static inline int rs274ngc_line ()
{
return rs274ngc_sequence_number ();
}
static inline const char *rs274ngc_command ()
{
static char buf[100];

rs274ngc_line_text (buf, 100);
return buf;
}
static inline const char *rs274ngc_file ()
{
static char buf[100];

rs274ngc_file_name (buf, 100);
return buf;
}

#endif

==end of header file==
#endif

Mach4View.h

Steffen — Mon, 08 Dec 2008 11:09:21 GMT

Summary:

==Head==
// Mach4View.h : interface of the CMach4View class
//

==Includes==
#include "ControlRect.h" //to allow all the other classes to get their definitions here
#include "Afxtempl.h"
#include "xmlprofile.h"
#include "engine.h"
#include "trajectoryControl.h"
#include "Addondlg.h"
#include "circinterp.h"
#include "memdc.h"
#include "PluginManager.h"
#include "TitleTip.h"
#include "flashview.h"

#import "PROGID:ShockwaveFlash.ShockwaveFlash" no_namespace raw_interfaces_only

typedef char *(_cdecl * stringfunc) (int string);

==struct defs==
===bdata===
struct bdata
{
CString Name;
CString Date;
bool Timeout;
bool Dxf;
bool Hpgl;
bool Jpg;
CString Test;
};

#define DELETE_SCREW 10325

#pragma once

==Classes==
===CMach4View===
class CMach4View:public CView
{

public:
bool m_Selection; // Is an input control selected?
int selpos;
int nControls;
int nHotControls;
int CurrentTab;
int Tabs[100];
int numgroups;
char trawdata[210];
char trawdata2[210];
bdata Block;
bdata Block2;
bool Stable; // Was engine stable on last run
OVERLAPPED ov; // for overlapped IO
TimeData Info; // for timing info
HANDLE hEvent;
unsigned long cpuSpeed; // CPU speed
int m_Units; // default setup units
double En0_nSteps,
En1_nSteps,
En2_nSteps;
bool RemoteHandle;
HWND Remhandle; // remotely set handle
bool FilePres,
mConverse; // file protection string
char LicData[1024];
CString rName;
CString LoadedScreen;
char acrData[200];
char acrData2[200];
bool AutoLoadAddon;
CString tempstring;
bool JogAllowed[100];
bool External;
AddonDlg *addons;
double OEMDROs[255];
bool OEMLeds[255];
CString Tickers[255];
bool LoadCode;
bool ScreenAuto;
bool LockedUp;
double m_cxMax,
m_cxMin,
m_cyMax,
m_cyMin;
//PlugIn variables.
bool m_PrinterOn;
bool *m_ShiftState;
bool *m_CtrlState;
CFrameWnd *MachFrame;
int LocTest;
bool NormalScreen;
HWND FlashWnd;
IShockwaveFlash *flash;
bool FlashAvailable;
bool FlashLoaded;
FlashView *FlashWindow;
bool Protected;
CString sPassword;
HANDLE ClickRes;
LPSTR lpClick;
CString runtime;
CString esttime;

//all position sensitive. Keep vars above..//////////////////////////////////////////////////////////
protected: // create from serialization only
CMach4View ();
DECLARE_DYNCREATE (CMach4View)
// Attributes
public: //from the ocx
CMemDC * memdc;
PlugInManager plugin;
COLORREF BackColor;
CBrush BackBrush;
TrajectoryControl Planner;
CObList m_listCtrls;
LRESULT DoHelpIt (WPARAM /*wParam */ , LPARAM /*lParam */ );
LRESULT DoDeferredStart (WPARAM /*wParam */ , LPARAM /*lParam */ );
LRESULT DeleteScrew (WPARAM /*wParam */ , LPARAM /*lParam */ );
CControlRect *m_Controls[2000]; // array of controls
CControlRect *m_HotKeys[2000]; // array of hot-keyed controls
CControlRect *Selection; // Selected Control
bool Calculators;
int tripmenu;
int Slave0,
Slave1,
Slave2;
bool StanScreen;

// Operations
public: //from the ocx.

BOOL LoadLayout (CString FileName);
void Lock (bool Lock);
void CloseXML ();
void OpenXML ();
void SetHotKeysOn ();
void SetHotKeysOff ();
void ConfigureEngine ();
void OnAllocate ();
BOOL StopEngine ();
void GetFileName (CString & path);
void SelectionMDICalled ();
void CalcTabs ();
void SortTabs ();
bool included (int *vects, int check, int nItems);
void NextGroup ();
void PreviousGroup ();
void PreviousSelection ();
void NextSelection ();
bool SelectionType (int key);
void SelectionCalled (int type);
BOOL StartEngine ();
void ShowGroup ();
void CreateAll ();
void CheckCirc (char *Pass);
void CheckCirc2 (char *Pass);
void CheckCirc3 (char *Pass);
void CircInterp (CString Pass);
void CircInterp2 (CString Pass); //wizlic
void CircInterp3 (CString Pass); //g100
void JPeg ();
void SetupBacklash ();
void CalculateEncoderVars ();
void CalEncoders ();
void UnHookKeys ();
void UpdateLoop ();
void ResizeControls (CControlRect *);
BOOL CMach4View::InitEngine ();
void CMach4View::HookKeys ();
void ShowGroupZero (void);
void CloseLayout (void);
void CheckForAddons (void);
void LoadAddon (void);
void LoadDefLayout (CString screen);
SHORT GetnToolpathOps (void);
VARIANT GetOperation (SHORT nOperation);
void Offline (SHORT state);
void ConfigToolPath (void);
void Regen (void);
void SelectionListCalled ();
void LoadNoRun (LPCTSTR name);
DOUBLE GetParam (LPCTSTR param);
void CalSpindle (void);
void Maintain (void);
void Formulas (void);
void ScrewMap (void);
LRESULT LoadDefaultLayout (WPARAM /*wParam */ , LPARAM /*lParam */ );
LRESULT LoadGCodeMessage (WPARAM /*wParam */ , LPARAM /*lParam */ );
LRESULT LoadAddonButton (WPARAM /*wParam */ , LPARAM /*lParam */ );
bool CheckTime ();
bool CheckTime2 ();
bool SetLog ();
void MenuOn ();
void MenuOff ();
void CheckSer ();
void FlushSettings ();

LRESULT OnViewVideoScript (WPARAM /*wParam */ , LPARAM /*lParam */ );

// Overrides
public:
virtual BOOL PreCreateWindow (CREATESTRUCT & cs);
protected:
virtual void OnInitialUpdate (); // called first time after construct

// Implementation
public:
virtual ~ CMach4View ();
#ifdef _DEBUG
virtual void AssertValid () const;
virtual void Dump (CDumpContext & dc) const;
#endif

protected:

// Generated message map functions
protected:
afx_msg void OnStyleChanged (int nStyleType, LPSTYLESTRUCT lpStyleStruct);
DECLARE_MESSAGE_MAP () public:

virtual BOOL PreTranslateMessage (MSG * pMsg);
afx_msg void OnTimer (UINT nIDEvent);
afx_msg void OnFileNew ();
protected:
virtual void OnDraw (CDC * /*pDC */ );
public:

afx_msg BOOL OnEraseBkgnd (CDC * pDC);
afx_msg void OnLoadgcode ();
afx_msg void OnImporthpgl ();
afx_msg void OnImportdxf ();
afx_msg void OnClosefile ();
afx_msg void OnSetnative ();
afx_msg void OnPortspins ();
afx_msg void OnHominglimits ();
afx_msg void OnSlave ();
afx_msg void OnSethotkeys ();
afx_msg void OnTunemotor ();
afx_msg void OnBacklash ();
afx_msg void OnToolpath ();
afx_msg void OnLogic ();
afx_msg void OnState ();
afx_msg void OnLoadscreens ();
afx_msg void OnRegen ();
afx_msg void OnPickwizard ();
afx_msg void OnOffline ();
afx_msg void OnLock ();
afx_msg void OnUnlock ();
afx_msg void OnMacros ();
afx_msg void OnFixtures ();
afx_msg void OnTooltable ();
afx_msg void OnSpincal ();
afx_msg void OnScrewmap ();
afx_msg void OnFormulas ();
afx_msg void OnMaintenance ();
afx_msg void OnAbout ();
afx_msg void OnArtsoft ();
afx_msg void OnExit ();
BOOL CMach4View::LoadGCode ();
afx_msg void OnKillFocus (CWnd * pNewWnd);
afx_msg void OnUpdateOffline (CCmdUI * pCmdUI);
void ShowRight (void);
void TogglePanel (void);
afx_msg void OnOperatorCalibratempg ();
afx_msg void OnOperatorModbuscontrol ();
afx_msg void OnOperatorTCPModbuscontrol ();
afx_msg void OnHelpEmailsupportrequest ();
afx_msg void OnConfigSerialmonitor ();
void StoreLayout (void);
afx_msg void OnViewSavecurrentlayout ();
afx_msg void OnFileDxfturnimport ();
afx_msg void OnViewVideowindow ();
afx_msg void OnConfigFonts ();
afx_msg void OnHelpWww32894 ();
afx_msg void OnConfigEditbutotnscript ();
afx_msg void OnLButtonDown (UINT nFlags, CPoint point);
afx_msg void OnConfigCheckconfig ();
afx_msg void OnConfigModbusconfig ();
afx_msg void OnOperatorConfigplugins ();
afx_msg void OnConfigGeneralmodbusconfig ();
void SU (void);
afx_msg void OnConfigResetdevicesel ();
afx_msg void OnConfigSpindlepulleys ();
afx_msg void OnConfigSafe ();
afx_msg void OnOperatorAuto ();
afx_msg void OnUpdateOperatorAuto (CCmdUI * pCmdUI);
afx_msg void OnOperatorSetnormalcondition ();
bool AttachFlash (void);
bool DetachFlash (void);
afx_msg void OnDrawItem (int nIDCtl, LPDRAWITEMSTRUCT lpDrawItemStruct);
afx_msg void OnViewManualencoderdroscreen ();
afx_msg void OnViewDefaultmotorcontrolscreen ();
afx_msg void OnOperatorRestoresettings ();

__int64 lic;

afx_msg void OnOperatorBraincontrol ();
};

==defines==
#define WM_LOADDEF 10321
#define WM_LOADPROGRAM 10322
#define WM_RUNTHEHELP 10323
#define WM_LOADADDON 10324
#define DELETE_SCREW 10325
#define WM_DEFERRED 10326

/////init of the driver code..

#define MACH1_SUCCESS 0
#define MACH1_ERROR_MEMORY 21
#define MACH1_ERROR_NOTIMER 22
#define MACH1_ERROR_ALREADYON 1
#define MACH1_ERROR_NOIDT 2
#define MACH1_ERROR_NOVECTORS 3
#define MACH1_ERROR_NOFREEVECT 4
#define MACH1_ERROR_NOGDT 5
#define MACH1_ERROR_NOLIDT 6

#define IOCTL_INBUF_SIZE 512
#define IOCTL_OUTBUF_SIZE 512
#define MACH1_PREPTIMER CTL_CODE(FILE_DEVICE_UNKNOWN, 0x800, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define MACH1_STOPTIMER CTL_CODE(FILE_DEVICE_UNKNOWN, 0x801, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define MACH1_GETCOUNT CTL_CODE(FILE_DEVICE_UNKNOWN, 0x802, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define MACH1_GETMAXTIME CTL_CODE(FILE_DEVICE_UNKNOWN, 0x803, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define MACH1_GETMINTIME CTL_CODE(FILE_DEVICE_UNKNOWN, 0x804, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define MACH1_STARTTIMER CTL_CODE(FILE_DEVICE_UNKNOWN, 0x805, METHOD_BUFFERED, FILE_ANY_ACCESS)

// control code for iocontrol calls for Master5 operations

#define SOFT_GET_STATUS CTL_CODE(FILE_DEVICE_UNKNOWN, 0x806, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_CONTROL_OUT CTL_CODE(FILE_DEVICE_UNKNOWN, 0x807, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_SET_FREQUENCY CTL_CODE(FILE_DEVICE_UNKNOWN, 0x808, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_ACTIVATE CTL_CODE(FILE_DEVICE_UNKNOWN, 0x809, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_GET_TIMES CTL_CODE(FILE_DEVICE_UNKNOWN, 0x80a, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_GET_DATA CTL_CODE(FILE_DEVICE_UNKNOWN, 0x80b, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_ADD_TO_BUFFER CTL_CODE(FILE_DEVICE_UNKNOWN, 0x80c, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_GET_LOADINDEX CTL_CODE(FILE_DEVICE_UNKNOWN, 0x80d, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_GET_CONTROLINDEX CTL_CODE(FILE_DEVICE_UNKNOWN, 0x80e, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_SET_PORT CTL_CODE(FILE_DEVICE_UNKNOWN, 0x80f, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_LOAD_MASKS CTL_CODE(FILE_DEVICE_UNKNOWN, 0x810, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_GET_ACTIVE CTL_CODE(FILE_DEVICE_UNKNOWN, 0x811, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_GETINDEXS CTL_CODE(FILE_DEVICE_UNKNOWN, 0x812, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_SETREVERSALS CTL_CODE(FILE_DEVICE_UNKNOWN, 0x813, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_CONTROL_IN CTL_CODE(FILE_DEVICE_UNKNOWN, 0x814, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_CONTROL_JOGON CTL_CODE(FILE_DEVICE_UNKNOWN, 0x815, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_CONTROL_JOGOFF CTL_CODE(FILE_DEVICE_UNKNOWN, 0x816, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_SETNEGS CTL_CODE(FILE_DEVICE_UNKNOWN, 0x817, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_GETIDLE CTL_CODE(FILE_DEVICE_UNKNOWN, 0x818, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_EMERGENCY CTL_CODE(FILE_DEVICE_UNKNOWN, 0x819, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_OVERRIDE CTL_CODE(FILE_DEVICE_UNKNOWN, 0x81a, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_GOHOME CTL_CODE(FILE_DEVICE_UNKNOWN, 0x81b, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_PAUSE CTL_CODE(FILE_DEVICE_UNKNOWN, 0x81c, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_HALT CTL_CODE(FILE_DEVICE_UNKNOWN, 0x81d, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_LASER CTL_CODE(FILE_DEVICE_UNKNOWN, 0x81e, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_SPACE CTL_CODE(FILE_DEVICE_UNKNOWN, 0x81f, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_GATE CTL_CODE(FILE_DEVICE_UNKNOWN, 0x820, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define SOFT_ALLOCATE_BUFF CTL_CODE(FILE_DEVICE_UNKNOWN, 0x821, METHOD_OUT_DIRECT,FILE_ANY_ACCESS)
#define SOFT_SAMPLE_BUFF CTL_CODE(FILE_DEVICE_UNKNOWN, 0x822, METHOD_OUT_DIRECT,FILE_ANY_ACCESS)
#define SOFT_SAMPLE_ON CTL_CODE(FILE_DEVICE_UNKNOWN, 0x823, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define MACH1_RELEASEBUFFERS CTL_CODE(FILE_DEVICE_UNKNOWN, 0x824, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define MACH1_DRIVERVERSION CTL_CODE(FILE_DEVICE_UNKNOWN, 0x825, METHOD_BUFFERED, FILE_ANY_ACCESS)

#ifndef _DEBUG // debug version in Mach4View.cpp
//inline CMach4Doc* CMach4View::GetDocument() const
// { return reinterpret_cast<CMach4Doc*>(m_pDocument); }
#endif

Engine.h

Steffen — Mon, 08 Dec 2008 11:06:13 GMT

Summary:

__TOC__

'''NOTE:''' The structures are also documented (in a different fashion and slightly differently) in [[SDK Variables]]. This page is probably the newer (and therefore better?) page.

==Head==
//Axis definitions

#if !defined(AFX_ENGINE_H__738D3A62_292C_413C_A76F_052BE3C1250C__INCLUDED_)
#define AFX_ENGINE_H__738D3A62_292C_413C_A76F_052BE3C1250C__INCLUDED_

==defines==
#define XAXIS 0
#define YAXIS 1
#define ZAXIS 2
#define AAXIS 3 // disptype
#define BAXIS 4
#define CAXIS 5
#define SPINDLE 6
#define ENC1 7
#define ENC2 8
#define ENC3 9
#define TOOLPATH 10

// Controller States
#define STOP 0
#define RUN 1
#define PAUSE 2
#define FINISHING 3
#define MDISTATE 4
#define WAITING 5
#define SINGLE 6
// Device outputs
/*
#define EXTERNACT1 1
#define EXTERNACT2 2
#define EXTERNACT3 3
#define EXTERNACT4 4
#define EXTERNACT5 5
#define EXTERNACT6 6
*/

// EStop reasons;

#define LOCALWATCHDOG 1
#define REQUESTED 2
#define DRIVERWATCHDOG 3
#define LIMITSWITCH 4
#define DRIVERSAFETY 5
#define ESTOPINPUTLINE 6
#define SOFTLIMITS 7
#define CONFIG 8
#define SIMSTOP 9
#define ENDOFFILE 10
#define SERVODISABLE 11
#define EXTERNALCOMTIMEOUT 12

// Commands to Engine

#define COMDWELL 1
#define COMDIGTRIGON 2
#define COMDIGTRGOFF 3
#define COMEXT1ON 4
#define COMEXT1OFF 5
#define COMEXT2ON 6
#define COMEXT2OFF 7
#define COMEXT3ON 8
#define COMEXT3OFF 9
#define MOTIONCS 10
#define MOTIONCV 11
#define CHANGEUNITS 12
#define SETFEED 13
#define CHANGEPLANE 14
#define CHANGESLOT 15
#define LENGTHOFFSET 16
#define SETORIGINS 17
#define SETMAXVEL 18
#define PROGRAMSTOP 19
#define PROGRAMSTOPOPT 20
#define PROGRAMEND 21
#define SPINAXISSPEED 22
#define SPINAXISCW 23
#define SPINAXISCCW 24
#define SPINAXISSTOP 25
#define RUNSUB 26
#define RETSUB 27
#define CALLMAC 28
#define PROBEAXIS 29
#define WAITCOMMAND 30
#define THREADOFF 31
#define FINISHSLOT 32
#define DISABLESPEED 33
#define REFCOM 34
#define COMEXT4ON 35
#define COMEXT4OFF 36
#define COMEXT5ON 37
#define COMEXT5OFF 38
#define COMEXT6ON 39
#define COMEXT6OFF 40
#define FLOODSIGON 41
#define FLOODSIGOFF 42
#define MISTSIGON 43
#define MISTSIGOFF 44
#define TURNOFFCOMP 45
#define TURNONCOMP 46
#define ESIGON 47
#define ESIGOFF 48
#define EPURGE 49

#define CW 0
#define CCW 1

#define MMS 0
#define INCHES 1
#define DEGREES 2 //dispunits
#define COUNTS 3
#define VELOCITY 4

// Number of input signals in total that need to be loaded from engine
#define nSigs 53

// Input signals
#define XLIMITPLUS 0
#define XLIMITMINUS 1
#define XHOME 2
#define YLIMITPLUS 3
#define YLIMITMINUS 4
#define YHOME 5
#define ZLIMITPLUS 6
#define ZLIMITMINUS 7
#define ZHOME 8
#define ALIMITPLUS 9
#define ALIMITMINUS 10
#define AHOME 11
#define BLIMITPLUS 12
#define BLIMITMINUS 13
#define BHOME 14
#define CLIMITPLUS 15
#define CLIMITMINUS 16
#define CHOME 17
#define ACTIVATION1 18
#define ACTIVATION2 19
#define ACTIVATION3 20
#define ACTIVATION4 21
#define DIGITIZE 22
#define INDEX 23
#define LIMITOVER 24
#define EMERGENCY 25
#define THCON 26
#define THCUP 27
#define THCDOWN 28 //last engine signal
#define OEMTRIGGER1 29
#define OEMTRIGGER2 30
#define OEMTRIGGER3 31 // OEM Trigger signals..
#define OEMTRIGGER4 32
#define OEMTRIGGER5 33
#define OEMTRIGGER6 34 // OEM Trigger signals..
#define OEMTRIGGER7 35
#define OEMTRIGGER8 36
#define OEMTRIGGER9 37 // OEM Trigger signals..
#define OEMTRIGGER10 38
#define OEMTRIGGER11 39
#define OEMTRIGGER12 40 // OEM Trigger signals..
#define OEMTRIGGER13 41
#define OEMTRIGGER14 42
#define OEMTRIGGER15 43 // OEM Trigger signals..
#define TIMING 44
#define JOGXP 45
#define JOGXM 46
#define JOGYP 47 //Jog inputs
#define JOGYM 48
#define JOGZP 49
#define JOGZM 50
#define JOGAP 51
#define JOGAM 52
#define HOMING 53 //software signal
#define PROBING 54 //software signal
#define RESUME 55 //software signal
#define EXHOME 56 //software signal for external homing offset circuit.

//software triggers...Last 3 bits of the engine Wait condition...
//which encompasses all 31 signals in a 32 bit word


#define nSigsOut 30 /// output signals

#define DIGTRIGGER 0
#define ENABLE1 1
#define ENABLE2 2
#define ENABLE3 3
#define ENABLE4 4
#define ENABLE5 5
#define ENABLE6 6
#define EXTACT1 7
#define EXTACT2 8
#define EXTACT3 9
#define EXTACT4 10
#define EXTACT5 11
#define EXTACT6 12
#define CHARGE 13
#define CHARGE2 14
#define CURRENTHILOW 15
#define EXTACT7 16
#define EXTACT8 17
#define EXTACT9 18
#define EXTACT10 19
#define EXTACT11 20
#define EXTACT12 21
#define EXTACT13 22
#define EXTACT14 23
#define EXTACT15 24
#define EXTACT16 25
#define EXTACT17 26
#define EXTACT18 27
#define EXTACT19 28
#define EXTACT20 29

#define KEYNOCOMMAND 0
#define KEYFLOOD 1
#define KEYJOGINCR 2
#define KEYMIST 3
#define KEYPAUSE 4
#define KEYRESET 5
#define KEYRESUME 6
#define KEYREWIND 7
#define KEYRUN 8
#define KEYSINGLE 9
#define KEYSPINCCW 10
#define KEYSPINCW 11
#define KEYSPINOFF 12
#define KEYSTOP 13
#define KEYZEROX 14
#define KEYZEROY 15
#define KEYZEROZ 16
#define KEYZEROA 17
#define KEYZEROB 18
#define KEYZEROC 19
#define KEYZEROALL 20
#define KEYGOTOZERO 21
#define KEYREFALL 22
#define KEYOVERIDE 23

//// Control groups...
//
//
#define DRO 1
#define BITMAPCTRL 3
#define TEXTBUTTON 4
#define JOYSTICK 5
#define LED 6
#define LABLE 7
#define BITBUTTON 8
#define MDILINE 9
#define GCODE 10
#define PATHCTRL 11

==struct defs==
===OutputInfo===
// output signal structure
struct OutputInfo
{
bool active;
char OutPin;
char OutPort;
bool Negated;
bool Activated;
};

An output Signal as declared in ''Ports and Pins''

{| border="0" cellpadding="5" style="margin:1em 1em 1em 0em; border:0px #AAA solid; border-collapse:collapse; empty-cells:show;"
|-
|''active'': || the Output is used
|-
|''OutPin'': || the number of the output (in case of LPT: the pinnumber on the connector)
|-
|''OutPort'': || the portnumber addressed by this output. e.g. 1/2: LPT 1/2, 0: ModBus, 10: pokeys
|-
|''Negated'': || if set, the signal shall be low-active
|-
|''Activated'': || the output signal is set
|}

The port and pin number are unsigned and shown in Mach3-Dialog for ports and pins as -127..128

This struct is used in [[#var:OutSigs|OutSigs]] as an array for the number of [[#def:OutSignals|Output Signals]]

===InputInfo===
// input signal structure
struct InputInfo
{
bool Active; // signal active?
char InPin; // which Pin
char InPort; // which Port
bool Negated;
int ReqState; // Required State on Activation
bool Activated;
bool Emulated;
int EmulationKey;
};

Equivalent to [[#OutputInfo|OutputInfo]] for Inputs.

This struct is used in [[#var:InSigs|InSigs]] as an array for the number of [[#def:InSignals|Input Signals]]

===Encoder===
// encoder inputs
struct Encoder
{
bool Active; // is the encoder turned on?
int APin; // A Pin designations
int BPin; // B Pin designations
int APort; // A Pin Ports
int BPort; // B Pin Ports
bool LastStateA;
bool LastStateB; // storage for the last known state
int Count[2]; // Index counts for each encoder
int Memory[16];
int ActiveMemory;
int Color;

};

===AxisInfo===
// axis information structure
struct AxisInfo
{
int Index; // Current Count
int MasterIndex;
char StepPin; // Pin for step pulse
char DirPin; // Pin for Direction Pulse
char StepPort; // Port # for step
char DirPort; // Port # for Direction
bool StepNegate; // low active step?
bool DirNegate; // low active Direction?
int CurVelocity; // Current Velocity
int MaxVelocity; // Current Max Velocity (jogging )
int MasterVelocity; // Master Velocity...Maximum Velocity in all circumstances.
int Acceleration; // Acceleration
bool AtSpeed; // At Speed Currently
bool Acc; // Accelerating?
bool Dec; // Decelerating?
bool Enable; // Axis Enabled?
bool Jogging; // Jogging On?
int JoggDir; // Direction of Jog;
bool Homing; // is this a homing jog?
bool DeRef; // Dereferanceing Move?
int Memory[6];
int ActiveMemory;
int Color;
int TripCount;
int DepthCount;
bool Probing;
bool Slave;
int SlaveAxis;

};

===TrajPoint===
struct TrajPoint
{
int Points[6];
int Command;
int ID;
char shifter[6];
};
Type for [[#var:Trajectories|Trajectories]]

===TrajBuffer===
struct TrajBuffer
{
[[#TrajPoint|TrajPoint]] Trajectories[0x1000];
int TrajIndex; // Trajectory buffer current Index
int TrajHead; // Trajectory buffer Fill point
int uSecStep; // clock count for step signal
int uSecDir; // clock count for pre-raising the direction bit;
double LastCommandPos[6];
bool Configured;
bool Busy;
bool Idle;
bool Emergency;
bool Jogging;
bool IncrementalJog;
bool Sync;
bool Port1On;
bool Port2On;
bool Tuning;
bool ReconfigHotKeys;
short Port1Address;
short Port2Address;

[[#AxisInfo|AxisInfo]] Axis[7]; // axis information
[[#InputInfo|InputInfo]] InSigs[nSigs]; // input signals
[[#OutputInfo|OutputInfo]] OutSigs[nSigsOut]; // output signals
[[#Encoder|Encoder]] Encoders[7]; // encoder inputs
int LastCubics[6];
// WatchDogs
int WDInt0;
int WDInt8;
int WD2Way;
int StartClocks;
int EndClocks;
bool ReadClocks;
bool Sampleing; // Sampleing flag
bool CubicDrain; // cubicDrain flag..sets cubics to zero;
bool EStop;
// software limits
int XLimitPos,
YLimitPos,
ZLimitPos,
ALimitPos,
BLimitPos,
CLimitPos;
int XLimitNeg,
YLimitNeg,
ZLimitNeg,
ALimitNeg,
BLimitNeg,
CLimitNeg;
int StatHolders[6];
int StatLast[6];
bool StatBusy;
int StatCount;
bool SyncError;
int DwellTime;
int CurrentUnits;
bool Directions[7];
bool Safe;
// G-Code vars
int State;
bool NoTime;
int DisplayLine;
int CurrentLineExec;
bool Loaded;
int SpindleCW;
int SpindleCCW;
bool Jpg;
double oSpinSeconds;
bool SpinDelayReq;
int Flood;
int Mist;
bool Hpgl;
bool NoSpindle;
bool NoFlood;
bool Pro;
bool Dxf;
bool Referenced[6];
bool HomeSpeed[6];
unsigned long TargetTime;
int BackCounts[6];
int BackSpeeds[6];
bool BackState[6];
bool BackLast[6];
bool BackOn;
bool AutoZero[6];
double ToolChangePos[6];
int LastState;
int LookAhead;
int Year;
int LastExec;
int DROUpdate;
bool WatchDogOn;
bool LimitsOff;
bool Simulate;
int Month;
int KeyAction;
bool JoyOn;
unsigned __int64 WaitCondition;
int EStopReason;
bool PWM;
int PWMFreq;
int Day;
int oCurrentPulley; //remove this
int oldMaxSpeeds[4]; //and this..
int m_SetExec;
bool AutoHome;
int templookahead;
bool Homing;
char CircData[201];
bool CircLoaded;
bool DROMaster;
int SoftLimitsHi[6];
int SoftLimitsLo[6];
bool SoftDir[3];
bool SoftLimitEnable;
bool SoftLimitTriggered;
bool HotStart;
bool LCD;
int OverRide;
bool Follow;
int NewWindow;
bool Deselect;
bool DeSelectClick;
bool SelectClick;
int PWMBaseFrequency;
int PulseCount;
int THCCorrection;
int THCMaxCor;
int THCMinCor;
bool THCOn;
int THCAdder;
bool THCZero;
int PPS;
int RefCounts[6];

int CurrentSpindleCount;
int IntsPerRotation;
bool SpinDec;
bool SpinAcc;

long WorstCase;
int VerifyChecks[6];
int Verifys[6];

int THCDev;

int Debounce;

bool WaitForTrigger;
int nTrigger;
int PumpTime;

int MaxSpinCounts;
bool Threading;
int NormSpinCounts;
int SpinCorrection;
int SpinAdder;
int SpinDebounce;

int SPIDataPin;
int SPIClockPin;
int DataOutPort;
int DataOutByte;
bool DataOutDone;
int DataInPort;
int DataInByte;
bool DataInDone;
bool LaserTrigger;
int Counter;
bool SPIOn;
int SPIDataOut;
int SPIDataIn;
bool SPIDone;
bool SPIhidata;

bool OffLine;
int SpinStability;
char BitTest;

int CurRate;
int PlungeLimit;
bool NoPlunge; //THC No plunge control
bool SpindleStable;
short nSlots;
bool LaserMode;
bool MaxNCMode;
int MaxNCLag;
bool SlowMode;
bool MaxNC10;
bool Port2Input;
bool ChargeAlwaysOn;
bool RaiseLower;
unsigned int RawInputs;
bool HalfPulse;
bool Shuttle;
int ShuttleCurVel; // Current Velocity
int ShuttleMaxVel; // Current Max Velocity (jogging )
int ShuttleAccel;
int LaserX;
int LaserY;
int LaserZ;
int LaserXOff;
int LaserYOff;
int LaserZOff;
bool HoldInput1;
int Pierce;
bool StopForBacklash;
int GlobalCurHoldVel;
int GlobalTargetVel;
bool BackLashHolding;
bool backlash;
bool BacklashEnded;
bool TriggerBits;
};

===TimeData===
struct TimeData
{
int Time[32000];
};

==End of header file==
#endif

TrajectoryControl.h

Steffen — Mon, 08 Dec 2008 11:03:27 GMT

Summary:

==Head==
#if !defined(AFX_TRAJECTORYCONTROL_H__C8CBC326_3A49_4703_B02E_13CBC7C2848C__INCLUDED_)
#define AFX_TRAJECTORYCONTROL_H__C8CBC326_3A49_4703_B02E_13CBC7C2848C__INCLUDED_

#if _MSC_VER > 1000
#pragma once
#endif // _MSC_VER > 1000
// TrajectoryControl.h : header file
//

/////////////////////////////////////////////////////////////////////////////
// TrajectoryControl window

==Includes==
#include "engine.h"
#include "memmap.h"
#include "activdbg.h"
#include "spindlefm.h"
#include "toolcabinet.h"
#include "MPGControl.h"
#include "formelParser.h"
#include "screwmapcurve.h"
#include "scewmap.H"
#include "traj.h"
#include "Reprocessor.h"
#include "SerialRingThread.h"
#include "SerialRingThread.h"
#include "MyScriptObject.h"
#include "MySplitterWnd.h"
#include "GenUDPSocket.h"
#include "LEDConditions.h"
#include "DROValues.h"
#include "fixtureCabinet.h"
#include "afxtempl.h"
#include "normals.h"
#include "Titletip.h"
#include "BrainHandler.h"
#include "brain.h"

==external variables==
extern CMySplitterWnd *Splitter;

==defines==
#define STRAIGHTFEED 1
#define STRAIGHTTRAVERSE 2
#define SETFEEDRATE 3
#define ARCFEED 4
#define SETTRAVERSERATE 5
#define TRANSDWELL 6
#define SPINDLECW 7
#define SPINDLECCW 8
#define SPINDLEOFF 9
#define MOTIONMODE 10
#define SETUNITS 11
#define SETPLANE 12
#define CHANGETOOL 13
#define FLOODOFF 114
#define FLOODON 115
#define MISTON 116
#define MISTOFF 117
#define SPINDLESPEED 118
#define PRESLINE 119
#define HOLDLINENUMBER 120
#define OVERRIDE 121
#define REFAXISON 122
#define RADCIRCW 123
#define RADCIRCCW 124
#define STRAIGHTHREAD 125
#define SETCSSON 126
#define SETRPMON 127
#define COMPTURNOFF 128
#define COMPTURNON 129
#define DOTHREAD 130
#define PAUSECYCLEOFF 131
#define GOTOSAFE 132

//Plugin Notifications and defines..
enum
{ EX_DDA, EX_VMS, EX_COMMAND, EX_SPINON, EX_SPINOFF, EX_SPINSPEED, EX_MOTORTUNED, EX_SETUP, EX_FEEDHOLD, EX_RUN, EX_ESTOP, EX_CONFIG
};

enum
{ SAFEMACHINE, SAFEWORK, SAFERISE };

#define JOGCONT 0
#define JOGINC 1
#define JOGMPG 2

==struct defs==
===Externals===
struct Externals
{
int Line;
bool Active;
int Signal;
bool State;
};

===Extreme===
struct Extreme
{
double px,
py,
pz;
double mx,
my,
mz;

};

===ModCfg===
struct ModCfg
{
short Data[128];
char Comment[80];
bool Enabled;
int ModAdd; //modbus address
int nReg;
int Input;
int Port;
int Slave;
int Refresh;
int timref;
int status;
char msgstatus[40];
};

===ModCon===
struct ModCon
{
[[#ModCfg|ModCfg]] cgf[65];
};

===TCPModCFG===
struct TCPModCfg
{
short Data[128];
char Comment[80];
bool Enabled;
int ModAdd; //modbus address
int nReg;
int Input;
int Port;
int Slave;
int Refresh;
int timref;
int status;
char msgstatus[40];
};

===TCPModCon===
struct TCPModCon
{
[[#TCPModCFG|TCPModCFG]] cgf[65];
};

===GMoves===
struct GMoves
{
int type; // 0 is linear, 1 is cubic
double cx,
cy,
cz; // center of move for cubics.
double ex,
ey,
ez,
ea,
eb,
ec;
double sx,
sy,
sz,
sa,
sb,
sc;
__int64 DDA1[6]; //DDA1's for cubics
__int64 DDA2[6];
__int64 DDA3[6];
double Time;
bool Stop;
};

===GMoves1===
struct GMoves1
{
double diffs[6];
double velocity;
double accel;
double sweep;
double radius;
short nx,
ny,
nz;
short line;
};

===Commands===
struct Commands
{
int Command[0x400];
int LineID[0x400];
double params[0x400];
int nCommand;
int tail;
int head;
};

===ModBusRedir===
struct ModBusRedir
{
bool SpindleOn;
int SpindleSpeedReg;
double SpindleCal;
};

===Executions===
struct Executions
{
bool line;
EmcPose end;
PmCartesian center,
normal;
double rotation;
double Arotation;
int linenumber;
bool rapid;
double toolz;
double toolx;
double Feedrate;
short toolnumber;
bool Abs;
double comp;
};

===ProgData===
struct ProgData
{
int UnitType;
double MaxX,
MaxY,
MaxZ,
MaxA,
MaxB,
MaxC;
double MinX,
MinY,
MinZ,
MinA,
MinB,
MinC;

};

===NextLine===
struct NextLine
{
CString Block;
};

===AddStruct===
struct AddStruct
{
CString path,
name;
bool present;
CString setname;

};

===Subs===
struct Subs
{
int name;
int line;
};

===ComBuf===
struct ComBuf
{

int nCommands;
int Commands[10000];
double Params[40000];
int nParams;
int LastParam;
int LastCommand;

};

===AxisDDA===
struct AxisDDA
{
double points[64]; //64 control points to work with, in the end, only the first 4 will be filled..
double fDDA[3];
};

===CommandBuffer===
struct CommandBuffer
{
CString Commands[0x1000];
short Lines[0x1000];
short head,
tail;
};

===GeckoBuf===
struct GeckoBuf
{
double XPos;
double YPos;
double ZPos;
double APos;
double BPos;
double CPos;
};

===PPoint===
struct PPoint
{
double x,
y,
z,
a,
b,
c;

};

===ProgramState===
struct ProgramState
{
CString Filename;
int ExecutionLine;
bool IsFile;
};

#include "PathProgress.h"
#include "Mach1Button.h"

===TrajectoryControl===
class TrajectoryControl:public CWnd
{
// Construction // Put all variables in this block to keep them synced to the main engine..
public:
Traj trajectory;
short HomannSlave;
_int64 GeckoPos[6];
bool TPersist;
bool m_RevArc;
Traj Tooltraj;
double RexRateDRO,
RexRateTemp;
bool RexRateTrigger;
int PosChange[6];
double FrontToRear;
double LastPositions[6];
double FrontXOffS;
double FrontXOffE;
double ThreadParm[6];
bool RapidOverRide;
double RapidFeedrate;
double nextradius;
int nextside;
bool RegenNeeded;
bool DROBack;
int nextindex;
[[#ProgData|ProgData]] rundata;
CString DROFont,
CodeFont,
LabelFont;
bool JOGPINS[8];
CString SlabIP;
double DiffX,
DiffY,
DiffZ; //offset differentials..
double DiffA,
DiffB,
DiffC;
[[#CommandBuffer|CommandBuffer]] BCommands;
bool m_HWSafe;
int M3;
//laser variables.
bool HotKeysPersist;
int m_LookAhead;
bool WatchHold;
int LaserPort;
int Serial;
int m_ServoSerial;
int LaserBaud;
int LaserStops;
int LaserData;
int Timers[25];
CString LaserInit;
CString LaserCommand;
// end of laser vars
bool IsPanel;
double MPGFeed;
double TempFeed;
bool PlasmaHome;
bool m_UDP;
CString NextSub;
[[#ProgramState|ProgramState]] returns[1000];
ToolCabinet Tools;
double RefCounts[6];
double m_Seconds;
double MinPerPass;
bool InCycle;
bool HommanHolding;
bool OverRideMode2;
int PanelOut;
CTime SinceOn;
bool m_PathBoxed;
bool m_Plane;
double AxisDist[6];
[[#Executions|Executions]] BackBuffer;
int BackHead,
BackTail;
double FeedRate; //feedrate velocity;
[[#ModBusRedir|ModBusRedir]] ModCouple;
bool ChangeScreens;
int Units;
double FeedInc;
double ToolPostOffset;
double StepsPerAxis[6];
double Velocities[6];
double Acceleration[6];
double Corrections[6];
[[#GeckoBuf|GeckoBuf]] GeckoBuffer[4096];
[[#Commands|Commands]] CommandBuffer;
int history[6];
int load;
bool m_ZInhPersist;
bool TangentalControl;
bool AutoScreens;
bool skiptan;
double LiftAngle;
double LiftLevel;
bool m_OVPersist;
bool m_AutoSpindle;
bool ToolFlip;
CMemMapFile GCodeFile;
CMemMapFile DisplayComs;
CFile BackBufferFile;
bool BufferFileOpen;
bool m_Loaded;
LPVOID GCodeData;
int *GLines;
int Lines;
CString m_FileName;
int TermMode;
bool configured;
bool pathconfig;
double OrigSpindleSpeed;
bool m_Flash;
bool g_ZInhibit;
double g_ZInhDepth;
bool m_ToolChange;
double m_SafeZ,
m_SafeZO;
bool m_ToolIgnore;
int SetupUnits;
double nStepsStore[6];
double VelStore[6];
double AccStore[6];
int unitscommand;
double OffsetLength;
int Tool;
double NextFeed;
bool FeedTrigger;
bool OriginTrigger;
bool MacroTrigger;
bool DwellTrigger;
bool ProbeTrigger;
double m_ByPassFeed;
bool ByPassFeedOn;
int DwellAmount;
int macro;
double VelLimit;
bool AAng,
BAng,
CAng;
double rpm;
bool Simulating;
bool ArcTest;
int FeedID,
OriginID,
ToolID,
UnitID,
LengthID,
DwellID,
SpinID,
MacroID,
ProbeID;
int SpinVelPerRPM;
int SpinAcc;
int lines; // current translation line while loading
[[#Subs|Subs]] oSubroutines[100]; //unused padding..
int nSubs;
int nReturns;
double THCSpeed;
double THCCurrent;
double THCMax;
double THCMin;
double PlungePercent;
bool PWMLaser;
int full_circle_in_active_plane;
double radius;
bool ModBusOn;
bool OverRide;
bool m_MacroPump;
double Estimate;
bool SimDone;
double simx,
simy,
simz,
sima,
simb,
simc;
double MacroP1,
MacroP2,
MacroP3;
int RefSpeed[6];
int Vels[6],
Accs[6];
bool AxisNegs[6];
int References[6];
double Returns[6];
bool SingleVerify;
int SingleAxis;
int tempExec;
bool Silence;
bool Stage2Trigger,
Stage3Trigger;
bool LastAutoZero[6];
int ProbeAction;
double ProbeGoto;
double ProbeX,
ProbeY,
ProbeZ,
ProbeA,
ProbeB,
ProbeC;
bool DigFileOpen;
CStdioFile digfile;
double RadiusA,
RadiusB,
RadiusC; // distance per 1 degree of angular movement
double m_Increment;
int AxisKeys[12];
int m_DROCode; //hot key for DRO selection;
int m_MDICode; //hot key for MDI selection;
int m_GCode; // hotkey for GCODE selection
int m_ListKey; // hotkey for GCode display
bool m_ExcludeZ;
bool m_JoyOn;
bool m_Linear;
bool MDIMove;
double m_IncFeed;
int Platform;
bool Homeing;
bool Jogging;
bool CustomIncremental;
bool SoftLimitHold;
[[#ComBuf|ComBuf]] CannonBuffer;
bool m_Virtual;
CString LastError;
int Line;
int name,
repeat; //for subroutines.
bool FileFinished;
int LastPress;
double OVMaxVel;
int PausedFrom;
bool Follow;
int EStopCause;
bool CommandWaiting;
bool m_DisplayMachineCoord;
double FeedOverRide;
double tFeedOverRide;
double JogSlideIncr;
bool ConstantVolume;
bool PathGenerate;
int toolpath;
bool PathLoaded;
double m_CPULoad;
CString LastFile;
bool Threading;
double CycleInts[10];
bool ErrorClear;
bool AutoRun;
int EncJogAxis;
double RatioTaper;
bool TaperMode;
bool DualMPG;
int EncJogAxis2;
int EncJogAxis3;
int LastEncJogCount;
int CurrentEncJogCount;
int LastEncJogCount2;
int CurrentEncJogCount2;
bool m_Z25D;
bool BlockDelete;
bool m_AutoTool;
int OldTool;
bool OnFeed;
CFile *ErrorFile;
CArchive *Errors;
double OEMDROs[256];
bool OEMLeds[256];
CString Tickers[256];
CString UserLabels[256];
bool ErrorsOpen;
int ScriptsRunning;
bool TeachFileOpen;
double LaserMaxSpin;
//CArchive *TeachFile;
CStdioFile TeachFileFile;
CString TeachFileName;
bool SingleAxisVerify;
int nSingleAxisVerify;
bool MaxCLMode;
bool Regening;
int RegenLine;
EmcPose whereold;
bool Dig4Axis;
int SerialType;
bool RunAt;
bool DigLetter;
bool filestart; //for the backbuffer initialization.
bool DelayedReset[6];
int ResetTimer;
bool OrigXDir;
bool FrontPost;
int m_OEMRegNum;
bool m_OEMRegOn;
int VelMode;
double VelPer1,
VelPer2,
VelPer3;
double m_RealVelocity[7];
double m_RealAccel[7];
double m_G20X;
double m_G20Y;
double m_G20Z;
double m_G20A;
double m_G20B;
double m_G20C;
bool m_Rot360;

CString ProgramDir;
CString ThisProfile;

double m_ToGo[6];
bool ToGo;

LEDConditions LEDBool;
DROValues DROS;

GenSocket UDPIO;

int EncoderZeros[6];

[[#AxisDDA|AxisDDA]] AllDDA[6];

bool m_ShortRot;
CString m_Init;
bool m_InitAllResets;
double BackOffsetx,
BackOffsety,
BackOffsetz,
BackOffseta,
BackOffsetb,
BackOffsetc;
double BackToolZ,
BackToolX;
//////////////////////////////////
//
// Values for DRO's
/////////////////////////////
double XPosition;
double YPosition;
double ZPosition;
double APosition;
double BPosition;
double CPosition;
double MXPosition,
MYPosition,
MZPosition;
double MAPosition,
MBPosition,
MCPosition;

double XVel,
YVel,
ZVel,
AVel,
BVel,
CVel,
BlendVel;
double JogFeedRate;

double Maxs[6];
double Mins[6];

PmCartesian dummy; // for addtobuffer
double feedtemp;
bool CancelPath;
PathProgress *progress;
bool LastMoveRapid;

double RefPoints[6];
int OldState;
bool MillMode;
double MachPositions[6]; //machine coordinates of first three axis

double SlowPoints[6];
double m_SoftMaxs[6];
double m_SoftMins[6];

double SlowPointsO[6];
double m_SoftMaxsO[6];
double m_SoftMinsO[6];

bool ToolPathOn;
double LatheCorrection;
double Diameter;
bool RunInReverse;

bool m_DroLock;

double Throttle;
int ThrottleFunc;

int simcount;

double cpuSpeed;
bool CorrectionOn;
bool AutoLimitOverRide;

bool SetSkip; // skip the softlimits setup on Ref All from G-Code
int refaxis;

bool SingleTriggerOn;
bool SingleActive4On;

bool ConditionRapid;
bool CurveLoaded;

int MaxFeedOverRide;
double thcmax;
double thcmin;
bool SpinActual;

double m_BB,
m_BR,
m_BG,
m_RB,
m_RG,
m_RR,
m_FB,
m_FR,
m_FG,
m_AR,
m_AB,
m_AG,
m_EG,
m_EB,
m_ER;
int BaudRate,
ComPort;
int EntranceAngle;
int m_PWMin;
double RotError;
int SpinInc;

bool m_XMapOn,
m_YMapOn,
m_ZMapOn;

double LaserXGrid;
double LaserAGrid;
double LaserYGrid;
int LaserYOff;
int LaserXOff;
int LaserAOff;

int m_UseCR;
CString m_Char;
bool m_SLS;
double Repeats;
double ZInhibInc;
double SLSDist;
int LastMode;

bool MacroRunning;

bool DwellMilli;
double NextZLength,
NextXLength;
bool OEMTriggers[15];

Mach1Button OEMButton;
short OEMPins[15];

bool UseSwitches;
double PWMMaxSpeed;

bool DoRegen;
bool m_Homann;

//Toolpath variables for display
BOOL m_OriginSphere;
BOOL m_3dCompass;
CString HomannString;
short HomannLoc;
bool m_BitPack1;
int m_BitPack1Reg;
bool m_BitPackOut1;
int m_BitPackOutReg1;
BOOL m_Boundries;
BOOL m_ToolPosition;
BOOL m_AParallel;
double m_AtoXOff;
double m_AtoYOff;
double m_AtoZOff;
//Threading Variables for defaults...
int nAddons;
[[#AddStruct|AddStruct]] AddonNames[200];
int AddonSelected;
bool LoadAddon;
CString Addon2Load;
CString Init2Load;
bool AddonReady;;
bool AddonLoaded;
bool AutoRegen;
bool SoundsOn;
bool VoiceOn;
bool SingleStepMode;
bool EditLoad;
bool JogActive;
bool m_Arots;
[[#NextLine|NextLine]] AfterPause;
bool HeldInReverse;
bool LastMovePartial;

// Operations
public:
CString defaultscreen;
bool LoadScreen;
int ActiveGroup;
int LastActiveGroup;
int JogMode;

bool KeepRef;
bool Speech;
bool HelpContext;
bool LastSpeech;
bool MovingAverageDone;
bool MovingAverageOn;

bool JogPersist;
bool SaveWizard;

double StepsX,
StepsY,
StepsZ,
StepsA,
StepsB,
StepsC;

double loadToolXOff;
double loadToolZOff;
int loadSlot;
bool ToolDirty,
FixDirty;
bool PersistOffsets,
OffsetsDialog;
bool G54Back;
SpindleFM Spindle;
MPGControl MPG;
bool JogVelocity;
bool LastVelJog;
double m_DepthLastPass;
double m_InFeed;
double m_Spring;
double m_MinDepth;
double m_XClear;
double m_ZClear;
double m_CutDepth;
double m_Chamfer;
double m_DepthFirstPass;
int ReversalLine;
bool MidLine;
bool UnReversed;
bool SkipProgress;
double StockSize;
bool ShowSolid;
double LastLineFeed,
LastArcFeed;

double TurnMatR;
double TurnMatG;
double TurnMatB;

ScrewMapCurve XCurve,
YCurve,
ZCurve;
ScewMap *screw;
int m_IncJogBuffer;
bool OEMDualTemp;
bool RunPlus;
bool RunMinus; //these two are for runnign forward and back buttons.
bool LaserStandby;
bool ResetInit;
bool LastRunBackward;
int LastLineExec;
EmcPose SyncWhere;
bool FeedHolding;
bool NoPartial;
bool m_PlasmaMode;
bool m_UseSafeZ;
bool m_CompPlus;
bool EmergCalled;
Reprocessor *Processsor;
SerialRingThread *SerialRing;
bool ShuttleAutoOff;
CString LastMacroFile;
CString filetoload;
bool m_TurnReverse;
Mach1Button *lastbutton;
bool MPG1,
MPG2;
bool NoGConf;
bool TorchVoltageControl;
int TorchSpeed;
[[#GMoves|GMoves]] Movements[4096];
double EncoderPos[4];
double TouchZ,
TouchX;
bool FirstRev;
double PierceDelay;
bool m_WarnOnReset;
bool HighRes;
bool m_ToolLines;
ModCon ModBusData;
bool m_ModPlug;
double MB_MPGTime;
bool UsingModMPGs,
MBHaveReading;
bool Polled;
short *ModInputs; //ModBus variable Inputs Short[128]
short *ModOutputs; //ModBus varibale OutPuts[128]
bool ShutDown;
bool DebugRun;
double ExternalPulseRates[7]; //number 7 is for the spindle
bool ExternalStill;
int ELine; //used in triggering External Device outputs in realtime;
bool PurgeMovements; //Will cause MAch3 to purge all pending movement
int EHead;
[[#Externals|Externals]] EXCtrls[16];
bool ModBusCfg;
unsigned __int64 SoftWait;
bool DoExternalProbe;
int ExternHomedMask;
bool MovementDone;
double SpindlePer;
bool HasRot;
bool m_UseDiam;
bool Sequence;
//Probe Radius
double ProbeRad;
PmSpherical ProbeAngles;
PmCartesian ProbeVec;

//safeZ correction
int m_SafeZType;
bool m_SafeZStop;

int m_UnusedBufferFill;
bool FlashSizing;
short ExternalType;
[[#GMoves1|GMoves1]] MovementsAdd[4096];
bool BufferEnding;
double ExTime;
int ExBufferHi;
bool SkipShutdown;
CString MDIEntry;
bool m_MenuOff;
bool m_IgnoreM3;
bool m_MutiHome;
int m_HomeMask;
int PartialModes[255];
bool SkipFeed;
double aProbeX,
aProbeY,
aProbeZ,
aProbeA,
aProbeB,
aProbeC;
double PausedFeed;
bool TrajDone;
bool ExecNow;
HANDLE thandle;
Subs nSubroutines[1000];
CString ExternalMacro;
CString lCOSYS,
lTOOLDESC,
lUNITREVMIN,
lRADDIA,
lINMM,
lMODE,
lPROFILE,
lFILE;
bool VBTest;
bool FileLoadOK;
bool FileSimOK;
bool m_ExternalFeedHold;
int m_Ex_Loop3Time;

short MasterInputs[1024];
short MasterOutputs[1024];
short UserInputs[1024];
short UserOutputs[1024];

bool m_ExternalPaused;
bool m_SpindleOn;
Spindle is running
short ex_purgeflags;
bool G100TripSection;
bool ReDraw;
int SpinDir;
Spindle direction: 1: CW, -1: CCW
double RXPosition,
RYPosition;
bool InternalJogProbe;
double flashsec;
bool ExternalFRO;

bool SecondPass;
bool ComBufferOpen;
int CompHead,
CompTail;
[[#TCPModCon|TCPModCon]] TCPModBusData;
CString m_FileOnly;
CArray < Brain *, Brain * >*TheBrains;
int m_nBrains;
double OEMDROs2[1000];
bool OEMLeds2[1000];
bool m_UsingTCPIO;

///////////////////////////////////////////////////////////////////////////////////////////////
// No plugin Variables below this point..

// Overrides
// ClassWizard generated virtual function overrides
//{{AFX_VIRTUAL(TrajectoryControl)
//}}AFX_VIRTUAL

FixtureCabinet Fix;

// Implementation
public:
CArray < [[#PPoint|PPoint]] *, [[#PPoint|PPoint]] * >ProbePoints;
CArray < [[#PPoint|PPoint]] *, [[#PPoint|PPoint]] * >MissPoints;
[[#Extreme|Extreme]] ProbeEx;
Normals NormCond;
bool IncrementCorrect;
EmcPose TrueCenter;
bool ForwardCheck;
double AbsMaxs[6];
double AbsMins[6];
int Updates;
CString ButtonFont;
bool m_AbsInc;
bool m_SpinOff;
int m_SpinInc;
bool m_UseCVAngle;
double m_CVAngleDeg;
int precompmove;
double Fractions[6];
bool m_THC5;
bool KeyClick;
double OldFeeds[64];
bool donesafemove;
bool m_JogHeat;
bool DelayedJog;
int DelayedJogAxis;
int DelayedJogDir;
bool JogSpindleOn;
CString Authors[100];
bool THCEmulInOp;
int SpindleDelayedOn;
bool m_SlaveHome;
double LastFeedRate;
bool m_RotSoft;
double NormCycle;
CMemMapFile CompComs;
CFile CompBufferFile;
bool SecondPassDone;
bool JustSave;
bool m_TCPModBus;
bool m_ZBar;
BrainHandler BrainControl;
double BrainMs;
CString ModBusString;
bool ModStringHolding;
int ModStringAddress;
int ModStringcfg;
bool m_IgnoreMs;
double AxisOffs[6];
int ProbeStepsSec;

TrajectoryControl ();
int GetProbeTrip (int ProbeGoto, int Accs, int MaxVelocity, int axis);
void ResetProbePoints ();
void AddProbePoint (double x, double y, double z, double a, double b, double c, bool hit);
void computeDDAs (double time = 64);
int BufferUsed ();
void DoGeckoLines (short num, int &orig);
double ShortRot (double angle, double lastangle);
void CompOff ();
void LoadFixtures ();
void JogInputHandler ();
int ConvertHex (CString hex);
void SetVelocityMode (bool state);
void TCReverse (TC_STRUCT * to, TC_STRUCT * from);
void CreatePartials (int revline);
void DoTorchRunReverse ();
void SetLastError (LPCSTR error);
void ScrewCal ();
void SaveLinearity ();
int GetNextPoint (int axis);
int SimCheckSoft (int, int);
void FakeDriver ();
void SetFormulas ();
void LoadLinearity ();
void WorkOffsetTo (short axis, double Value);
void ReversalSearch (int id);
void RunReverse ();
bool DoHelp (int OEMnumber);
void Speak (char *Text);
void ScreenToggle ();
void CalcTrigger ();
bool DoExtOuts (short n);
double WhereRel (int axis);
void SetEntranceAngle (int angle);
void Regen ();
double GetRandom ();
void CalcReverseLine (int nLine, CString & String);
void CalcForwardPartial (int nLine, CString & String);
void SetColors ();
void rs_exec (CString Block);
void AutoSaveProfile ();
void THCOff ();
void THCOn ();
void RadCircleCCW (double radius);
void RadCircleCW (double radius);
void SafeEnd ();
void Check4ExtSingle ();
void FillBitMap ();
void SetLimitOV (bool cond);
double GetFixtureAxis (int axis);
void SetFixtureAxis (int axis, double value);

void GoHome ();
void SetFixture (int fixture);
void FixtureOff ();
void SetSoftPoints ();
void SetRefPoint (int axis, double point);
void DROToEncoder (int nEncoder, int nDRO);
void EncoderToDRO (int nEncoder, int nDRO);
void CalTHC ();
void Fixtures ();
void ToolTable ();
void TouchTool ();
void SetTHCMax (double unitsmax, double unitsmin);
void SetTHCSpeed (double speed);
void ToggleSoftLimits ();
void AddToBuffer (bool line, EmcPose end, PmCartesian center, PmCartesian normal, int rot, bool rapid);
void EditFile ();
void CancelAllCommands ();
void SetEStopReason ();
void RunWaitingCommands ();
void SetJogInc (bool state);
void SwitchWindow (int Window);
void DROPositions ();
void WatchDogs ();
void Reset ();
bool GetMachineCoords ();
void SetMachineCoords (bool mach);
void SetFollow (bool fol);
void SetNextLine (int line);
void RunFileAt (int line);
void SimulateFile ();
void GoToZeros ();
void FloodToggle ();
void MistToggle ();
void ZeroAxis (int axis);
void DisplayExec ();
void ZeroAll ();
void StopFile ();
void ResumeFile ();
void RewindFile ();
void PauseFile ();
void SingleStep ();
void RunFile ();
void LoadTraj ();
CString & GetLastError ();
void OnToolChange (double tool);
void RetSub ();
void DoSub (int name, int repeat);
void SetVirtual (bool state);
bool ExecFunctions ();
bool Execute (CString * Block, int line);
void ProgramReset ();
void DoGCodeLoop ();
void CalculateSpeeds (int axis);
void RefA ();
void RefB ();
void RefC ();
void RefX ();
void RefY ();
void RefZ ();
void DoJogLoop ();
void RefHomeOn (int axis, int dir);
bool CheckSkip ();
void SetSoftLimits ();
void JogOff (int axis);
void JogOn (int axis, int dir);
bool CheckJoyStick ();
void SetDiameters (double A, double B, double C);
void CloseDigFile ();
void OpenDigFile ();
void ProbeCommandFinished ();
void DoProbe ();
void ProbeAxis (double x, double y, double z, double a, double b, double c);
void VerifyReport ();
void VerifyStage2 ();
void FinishVerify ();
void Verify (bool silent);
void CalcVels (int axis);
void HomeOn (int axis, int dir);
void SafeTravel ();
void DoMacro ();
void SetRate (double rate);
void MacroRunFile (CString & name);
void RunInitFile (CString & name);
void CheckforSubroutine ();
void DoSpinSpeed ();
void DoSpinSpeedInternal ();
void DoSpinStop ();
void DoSpinCW ();
void DoSpinCCW ();
bool LoadFromPath (CString file);
bool LoadSub (CString file);
void DoOrigins ();
void ChangeFeed ();
void CompleteToolChange ();
bool Same (double x, double y, double z, double a, double b, double c);
void DoToolChange ();
void DoUnits (int units);
void DoLength ();
void RunRecalculate ();
void ChangeTool (int tool);
void SetPlane (int plane);
void ReturnToPaused ();
void RememberPaused ();
void StartMacroPump ();

void SetupBacklash ();

bool CalcArcs (double first_end, double second_end, double first_axis, double second_axis, int rotation, double endpoint, double enda, double endb, double endc);
void SetAccVelMan (EmcPose where);
void AddCommand (int Command, int line, double param);
void DoCommand (int Command);
void ManualLine (double x, double y, double z, double a, double b, double c);
void SetMMS ();
void SetInches ();
BOOL ChangeLine (int line, CString Text);
void CloseFile ();
bool GetLine (int nLine, CString & String, bool skipreverse);
bool LoadGCode ();
void Sync ();
bool SetAccVel (EmcPose where, double MaxVel);
void SetLastPos (EmcPose where);
void ReCalculate ();
void SetFeedRate (double Rate);
void Resume ();
void Pause ();
bool StraightThread (double x, double y, double z, double a, double b, double c);
bool StraightFeed (double x, double y, double z, double a, double b, double c);
bool StraightTraverse (double x, double y, double z, double a, double b, double c);
bool TrajectoryControl::ArcFeed (double first_end, double second_end, double first_axis, double second_axis, int rotation, double endpoint, double enda, double endb, double endc);
void Init ();
void Update (void);
void PlaySounds (char *sound);
void SetHelpContext ();
virtual ~ TrajectoryControl ();
void DoShifter (short num, int &orig);
void DoGShifter (short num, int &orig);
void UpdateToolOffsets ();
void SaveToolTable ();
void GotoSafe_z ();
void SetIncr (int pos);
// Generated message map functions
protected:
//{{AFX_MSG(TrajectoryControl)
// NOTE - the ClassWizard will add and remove member functions here.
//}}AFX_MSG
DECLARE_MESSAGE_MAP () public:
void SpinUp (void);
void SpinDown (void);
void SpinOverRide (double rpm);
void ExecMacSub (CString Mac);
void ResetZTHC (void);
void CycleIncr (void);
void FillJogIncs (void);
void DoEncoderJog (void);
void DoOEMTrigger (short Trigger);
void DisableSpeedOv (void);
void SetMill (void);
void SetTurn (void);
void LatheHome (int axis);
void Add2MRU (CString fname);
void DoMRU (void);
void DisplayHistory (void);
void AddToLog (CString text);
void ExecuteButtonScript (CString script);
void EditScript (CString script);
void CalcThread (void);
void VariJogOn (int axis, int direction, double speed);
int OpenTechFile (LPCTSTR name);
int OpenSubFile (LPCTSTR name);
int AppendTeachFile (LPCTSTR name);
void CloseTeachFile (void);
void TeachLoad (void);
void CheckMacroFolder (void);
void ConfigToolPath (void);
void SelectAddon (void);
void SelectNewFangled (void);
void CheckSoftLimits ();
void LoadDefaultScreens ();
void DoSingleStep (void);
double CalcOrg (int axis);
void SaveFixtures ();
// Gets BackBuffer Entry
Executions GetDisplayCom (int Com);
void UpdateIO ();
bool GetInputs (int bit, bool Neg);
void SetOutput (int bit, bool onoff, bool neg);
void KillScripts (HANDLE hCtx);
void SyncLocation (void);
void TurnTouchX (void);
void TurnTouchZ (void);
void SetDwell (double delay);
void TorchVolts ();
void SwitchToRear ();
void SwitchToFront ();
Executions GetCompDisplay (int Com);

double Get_Setup (double value);
void RecieveUDP (void *buffer, int bytes);
bool Emailer;

bool SoftForCheck (void);
int GetIndex (short axis);
void SetIndex (short axis, int value);
void RotConvert (TrajPoint & trajorg);
void UpdateSyncWhere (GMoves move);
void SetSoftMin ();
void SetSoftMax ();
void RestoreSoft ();
bool IsMoving ();
void SetToolDesc (int tool, LPSTR desc);
void DoLabels ();
bool ReCheck ();
void CalcDecel ();
void AddPartialArc ();
void AddToCompDisplay (bool line, EmcPose end, PmCartesian center, PmCartesian normal, int rot, bool rapid);
void DoMenu (int sub, int pos);
};

Closing the Header file
/////////////////////////////////////////////////////////////////////////////

//{{AFX_INSERT_LOCATION}}
// Microsoft Visual C++ will insert additional declarations immediately before the previous line.

#endif // !defined(AFX_TRAJECTORYCONTROL_H__C8CBC326_3A49_4703_B02E_13CBC7C2848C__INCLUDED_)

Plugin Documentation

Poppabear — Tue, 18 Nov 2008 16:11:04 GMT

Summary:

==Introduction==

This Document is a community driven effort to document users findings on what the various Variables and Functions do for doing Plug-ins for Mach3.

Those who felt generous may have also put an example of using the var, or function in the code.

The documents covered here are:
#[[TrajectoryControl.h]] (TrajectoryControl *MainPlanner)
#[[Mach4View.h]] (CMach4View *MachView)
#[[Engine.h]] (TrajBuffer *Engine)
#[[rs274ngc.h]] (setup *_setup)

TCP/IP Modbus (beta)

Poppabear — Tue, 21 Aug 2007 21:09:33 GMT

Summary:

'''TCP/IP Modbus (Beta):'''

NOTE!!!!: This is beta, and STILL under testing, with bugs worked out as they are found.

To set this up, click on: Function Cfg’s, > Setup TCP Modbus
This will bring up this screen:

[[Image:TCPIP_Modbus.jpg]]

At the top, you will see a box that says Master Address, fill in this address with your masters network address, your master is also Slave 1 for addressing purposes from mach.
There are 1024 Inputs possible, and 1024 Outputs possible, they are each a 16 bit word.
1 sixteen bit word is a number from 0-65535, or FFFF in hex.
There are 64 possible Configurations, (Cfg #0-63). So using the example above we are connected to an Automation Direct DL06 that have ranges:
Input range 1 (PLC address starts at 1400) translates over to Modbus(var) address 768, and the local Mach address that it is tied to starts at (index) “0” the number of registers transferred will be 10, so Local mach (index) addresses will be 0-9, type of addresses will be Input-Holding.
Input range 2 ( 1500PLC)>832Modbus(Var), 10 registers starting at mach’s index 10, input holding.
This pattern continues, with the rest of the configs, note that you have to keep track of mach’s Index inputs 0-1023, and Index outputs 0-1023, since they are continuous address blocks. BUT the addresses of the ModbusVAR only has to be continuous for the number of registers it is brining in. this allows you to pick different places in the memory registers or your PLC or other Modbus device.
Note: Cfg #4 and #5 are a second Modbus slave device numbered “2” and it has its inputs, and outputs, but also note that it ties into the local address of Mach’s index where the other devices left off.

The Refresh box is where you set the rate of “Polling” for the devices; it is currently set to update every 25 milli-seconds.

Once you have filled in all the info, hit the “Test” button, you will see this screen:

[[Image:TCP Test Screen.jpg]]

It will need your master address; you need to click “Open”, when you click it, your status
Bar should say Opened, if you get other error then you have set something up wrong in your Modbus device, or address……….
To test, (just like in Modbus serial testing), put in the slave address, the start address of the block you want to look at, how many registers, and access type, hit read for inputs, write for outputs. You can manually edit the Hex or decimal numbers to do what ever.

Currently you can only read the TCP/IP Modbus with the Macro Pump, (Art is working on a “Mach Brain”, that will allow you to manipulate the data in a more user friendly way, not to mention faster than the Macro pump.

Here are the VB commands that will access the TCP/IP modbus, note they only move in or out full 16bit words.

GetMasterInput(0-1023)
GetMasterOutput(0-1023)

The above will get the 16 bit word from the Mach address Local(var), or Index
If you want to do Discrete bits you will have to send/receive in the PLC using Bit of word, and you may have to do Bit masking in Mach to get the bit patterns you want.

SetMasterOutput(0-1023, 0-16bit)
SetMasterInput(0-1023, 0-16bit)

These will send outputs on Mach’s Index address Local(var) 0-1023, and a 16 bit number from 0-65535.
You can also “Overwrite” your inputs using the setmasterinput, for testing, but if you are actively hooked up to a PLC or other scanning device, it will overwrite your input, on its next scan.

I will update this as new things become available, and bugs worked out.
Scott

Get/SetParam() Vars

Barker806 — Mon, 29 Jan 2007 05:08:04 GMT

Summary:

Here is a word list for the GetParam( String ) and SetParam( String ) in VB

"ZMachine" = Z Mach Positions (G53 Coordinates)

"XMachine" = X Mach Positions (G53 Coordinates)

"YMachine" = Y Mach Positions (G53 Coordinates)

"Encoder1" = X Encoder Position

"Encoder2" = Y Encoder Position

"Encoder3" = Z Encoder Position

"Encoder4" = A Encoder Position

"MPG1" = MPG1’s count

"MPG2" = MPG2’s count

"MPG3" = MPG3’s count

"XScale" = X Axis Scale

"YScale" = Y Axis Scale

"ZScale" = Z Axis Scale

"AScale" = A Axis Scale

"BScale" = B Axis Scale

"CScale" = C Axis Scale

"FeedRate" = Feedrate that is active

"Units" = 0 or 1 for mm or inch

"StepsPerAxisX" = X Steps per unit from the motor tuning page

"StepsPerAxisY" = Y Steps per unit from the motor tuning page

"StepsPerAxisZ" = Z Steps per unit from the motor tuning page

"StepsPerAxisA" = A Steps per unit from the motor tuning page

"StepsPerAxisB" = B Steps per unit from the motor tuning page

"StepsPerAxisC" = C Steps per unit from the motor tuning page

"VelocitiesX" = X MaxVel from motor tuning page (SetParam as units/second. Mach will multiply X60 for display in motor tuning as units/minute.)

"VelocitiesY"= Y MaxVel from motor tuning page (SetParam as units/second. Mach will multiply X60 for display in motor tuning as units/minute.)

"VelocitiesZ" = Z MaxVel from motor tuning page (SetParam as units/second. Mach will multiply X60 for display in motor tuning as units/minute.)

"VelocitiesA" = A MaxVel from motor tuning page

"VelocitiesB" = B MaxVel from motor tuning page

"VelocitiesC" = C MaxVel from motor tuning page

"AccelerationX" = X Max Accel from motor tuning page

"AccelerationY" = Y Max Accel from motor tuning page

"AccelerationZ" = Z Max Accel from motor tuning page

"AccelerationA" = A Max Accel from motor tuning page

"AccelerationB" = B Max Accel from motor tuning page

"AccelerationC" = C Max Accel from motor tuning page

"SpindleSpeed" = Active Spindle speed

"ZInhibitOn" = 1/0 for Z inhibit on/ off

"ZInhibitDepth" = Max depth of Zinhibit

"SafeZ" = Safe Z height

"XDRO" = X Position

"YDRO" = Y Position;

"ZDRO" = Z Position;

"ADRO" = A Position;

"BDRO" = B Position;

"CDRO" = C Position;

"XRefPer" = X % speed for homing

"YRefPer" = Y % speed for homing

"ZRefPer" = Z % speed for homing

"ARefPer" = A % speed for homing

"BRefPer" = B % speed for homing

"CRefPer" = C % speed for homing

"RPMOverRide" = SetParam("RPMOverRide", 1) will allow you to write to OEMDRO39(True Spindle Speed) from the modbus. If set to "0" will read True spindle as usual.

Glossary

Pcbgcode — Fri, 26 Jan 2007 14:20:16 GMT

Summary:

=Mach Glossary=

==Keystroke==
This is what is sent to the computer when you press a key on the keyboard. There are also devices you can connect to your computer so that pressing a switch (like a switch on a control panel) will send a "keystroke" to the computer.

==Screenset==
A set of screens designed for Mach. A screen is what you see when you run Mach. It has buttons, [[DRO]]s, [[LED]]s, etc. Mach comes with it's own screens, their are third-party screens available, or you can make your own.

==DRO==
DRO is an [[http://en.wikipedia.org/wiki/Acronym initialism]] of Digital Read Out. They look like this [[Image:DRO.jpg|50px]] in Mach.

==LED==
LED is an [[http://en.wikipedia.org/wiki/Acronym initialism]] of Light Emitting Diode. They look like this [[Image:LED.jpg|50px]] in Mach.

Mach3 Pendants

Ynneb — Thu, 25 Jan 2007 01:13:01 GMT

Summary:

This section is dedicated to building a pendant controller for Mach.
Currently all information is spread around in other forums. Please use the pendant links page.
[[Mach3 Pendants links]]

Mach3 Pendants links

Ynneb — Thu, 25 Jan 2007 01:02:32 GMT

Summary:

'''Have a read through some of these links about pendants, ideas, and discussion.'''
Remember some of these threads are many pages long, so dont forget to use the page numbers in the threads to see the others.

Work log of how to build a pendant http://www.cnczone.com/forums/showthread.php?t=57759

http://www.cnczone.com/forums/showthread.php?t=6522

http://www.machsupport.com/forum/index.php?topic=184.0

http://www.machsupport.com/forum/index.php?topic=1353.0

[[Touch Screen and panel controls using ModIO]]

[[Universal panel notes for CNC Workshop 2006]]

[[Customization case studies]]

How to load a flash screen

Ynneb — Tue, 23 Jan 2007 23:00:53 GMT

Summary:

To load a flash screen is very easy, but may not be obvious.
Essentially you do the same thing as you do to load a conventional screen, however you must select the dropdown menu as shown below, and select the SWF option, and then browse to the flash screen you require. Currently there is only one flash screen that is distributed with Mach3.

http://www.machsupport.com/MachCustomizeWiki/images/0/01/Howtoloadflash.jpg

Flash Screens

Ynneb — Sat, 18 Nov 2006 06:43:11 GMT

Summary:

Flash Screens is new, and still very much in experimental mode for Mach 3.
As we are still investigating these screens, we can not offer any direct support, however the current talk about these format of screens is found here http://www.machsupport.com/forum/index.php?board=17.0 .
It is not expected that flash screens will be editable by other users, and that the screens will be made available for others to use, but not edit. If a user would like a customized screen they will need to use the conventional screen designer, create their own Flash screen , or commission someone else to do it for them.

Mach 3 now has the ability to open a .swf file as well as the traditional .set files.
SWF file are native to the Adobe / Macromedia player.
There is many different softwares available that can edit and create these swf files.
Two that come to mind are Adobe Flash http://www.adobe.com/products/flash/flashpro/, and Swishmax http://www.swishzone.com/index.php?area=products

JetCAM Screen Designer

JAPrenticeUK — Tue, 12 Sep 2006 08:52:28 GMT

Summary:

This screen designer was developed and donated by JetCAM.

It produces .SET or .SSET files that are used by Mach3 in the same way as the Artsoft designers but, in addition, saves more information about the "design intent" of the screens in a screen definition file of its own.

The benefits of this include: much greater control of the use of fonts and colour in buttons, labels etc.; ability to define the "Z-order" of layered objects without all the problems caused by Windows when each object is rendered as a "window object" by Mach.

Oversimplfying somewhat, its .SET files have all the static data (labels, blocks of colour, pictures of buttons etc.) as a single bitmap for each screen. This bitmap is built at "save" time from the graphic described in the screen definition file. Buttons are hot-spots defined to correspond to the correct places on the bitmap and LEDs, DROs and user labels are the usual Mach controls that are visible through transparent holes in the bitmap.

This screen designer has a comprehensive Help system with it and should be usable with little, if any, additional documentation.

You will find lots of related help here http://www.machsupport.com/forum/index.php?board=46.0

Screen4

JAPrenticeUK — Tue, 12 Sep 2006 08:33:37 GMT

Summary:

This designer is supplied by ArtSoft but is a separate download from the Mach3 release.

It allows the use of transparent bitmaps to obtain a range of graphic effects, supports user defined LEDs and the special "slider" style DRO for things like feedrate override setting.

Apart from these enhancements it is architecturally similar to the original screen designer. .SET and .SSET files can be used in either without problems, although features only implemented in one designer cannot be altered in the other.

This entry is a stub. We really need a proper description of the use of this program when it achieves stability.

Screen4 is a good alternative to other screen editors due to these options. To use these features, use the following steps.

To use a user created DRO:
1. Create rectangle in a graphics creator. Add bevel or whatever effects you want.
Making it transparent adds a nice effect.
2. Click "DRO" from the toolbar and click in your workspace.
3. Right-click the DRO to bring up the DRO Control window.
4. Check the "skined" box.
5. Find your created image in the "image loaction" explorer.
6. Click "OK"

To use a transparent bitmap for a button:
1. Create your button in a graphics creator.
2. Save your image as a '''transparent PNG''' file.
3. Click "IMAGE BUTTON" from toolbar, and place in workspace.
4. Find image with "image location".
5. Click "OK" and you're good to go.

Everything else is fairly similar to the screen designer. If anyone has any more tips or hints for Screen4, add on.

Screen5

JAPrenticeUK — Tue, 12 Sep 2006 08:31:31 GMT

Summary:

Standard Hotkeys

Davidimurray — Sun, 27 Aug 2006 11:03:36 GMT

Summary:

Functions within Mach 3 can be controlled by keyboard combinations.

These keys are defined in two ways.

* In the <tt>Config>System Hotkeys</tt> menu.
* In the screenset you have loaded.

For traditional Mach screensets (i.e. .SET, .SSET, .LSET files) you can use the ScreenTweak utility (Rev C1 onwards) to display (and copy via the clipboard to an editor) the codes on a given screen or for the whole screenset.

The utility can be downloaded from [http://www.machsupport.com/Downloads/Mach3ScreenTweak.exe here]

Usage:
(a) Load a screen set
(b) Click ''Edit all Controls'' (or for a single screen select the screen you want to view
in the list and click ''Control Edit'')
(c) Click ''View Hotkeys''

You can cut and paste elsewhere (e.g. Notepad) from the screen if you want a printout.

Note the warning about the labels on non US/UK keybords. The codes are from the physical position of the key not via the codetable.

The table below gives some keys for the '''Default Screensets''' provided with Mach 3.

 


<TABLE FRAME="VOID" CELLSPACING="0" COLS="6" RULES="NONE" BORDER="0">
<tr>
<td width="118" height="18" align="left" bgcolor="#E6E6E6">Type Set</td>
<td width="424" align="left" bgcolor="#E6E6E6">Function</td>
<td width="118" align="left" bgcolor="#E6E6E6">Hotkey</td>
<td width="86" align="left" bgcolor="#E6E6E6">Value dec.</td>
<td width="86" align="left" bgcolor="#E6E6E6">Value hex.</td>
<td width="125" align="left" bgcolor="#E6E6E6">Called from page</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Close current file</td>
<td align="left" bgcolor="#33CC66">U</td>
<td align="left" bgcolor="#33CC66" sdval="85" sdnum="1033;">85</td>
<td align="left" bgcolor="#33CC66">0x0055</td>
<td align="left" bgcolor="#33CC66" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Cycle axis controlled by MPG 1</td>
<td align="left" bgcolor="#33CC66">Alt A</td>
<td align="left" bgcolor="#33CC66" sdval="2113" sdnum="1033;">2113</td>
<td align="left" bgcolor="#33CC66">0x0841</td>
<td align="left" bgcolor="#33CC66" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Cycle axis controlled by MPG 2</td>
<td align="left" bgcolor="#33CC66">Alt B</td>
<td align="left" bgcolor="#33CC66" sdval="2114" sdnum="1033;">2114</td>
<td align="left" bgcolor="#33CC66">0x0842</td>
<td align="left" bgcolor="#33CC66" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Cycle start</td>
<td align="left" bgcolor="#33CC66">A</td>
<td align="left" bgcolor="#33CC66" sdval="65" sdnum="1033;">65</td>
<td align="left" bgcolor="#33CC66">0x0041</td>
<td align="left" bgcolor="#33CC66" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Cycle start</td>
<td align="left" bgcolor="#33CC66">A</td>
<td align="left" bgcolor="#33CC66" sdval="65" sdnum="1033;">65</td>
<td align="left" bgcolor="#33CC66">0x0041</td>
<td align="left" bgcolor="#33CC66" sdval="13" sdnum="1033;">13</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">e.g. Positioning screen select</td>
<td align="left" bgcolor="#33CC66">B</td>
<td align="left" bgcolor="#33CC66" sdval="66" sdnum="1033;">66</td>
<td align="left" bgcolor="#33CC66">0x0042</td>
<td align="left" bgcolor="#33CC66" sdval="5" sdnum="1033;">5</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">e.g. Positioning screen select</td>
<td align="left" bgcolor="#33CC66">M</td>
<td align="left" bgcolor="#33CC66" sdval="77" sdnum="1033;">77</td>
<td align="left" bgcolor="#33CC66">0x004d</td>
<td align="left" bgcolor="#33CC66" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">e.g. Toolpath screen select</td>
<td align="left" bgcolor="#33CC66">A</td>
<td align="left" bgcolor="#33CC66" sdval="65" sdnum="1033;">65</td>
<td align="left" bgcolor="#33CC66">0x0041</td>
<td align="left" bgcolor="#33CC66" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Edit G-code</td>
<td align="left" bgcolor="#33CC66">E</td>
<td align="left" bgcolor="#33CC66" sdval="69" sdnum="1033;">69</td>
<td align="left" bgcolor="#33CC66">0x0045</td>
<td align="left" bgcolor="#33CC66" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Edit G-code</td>
<td align="left" bgcolor="#33CC66">E</td>
<td align="left" bgcolor="#33CC66" sdval="69" sdnum="1033;">69</td>
<td align="left" bgcolor="#33CC66">0x0045</td>
<td align="left" bgcolor="#33CC66" sdval="13" sdnum="1033;">13</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Execute VB-SCript.:13</td>
<td align="left" bgcolor="#33CC66">D</td>
<td align="left" bgcolor="#33CC66" sdval="68" sdnum="1033;">68</td>
<td align="left" bgcolor="#33CC66">0x0044</td>
<td align="left" bgcolor="#33CC66" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Execute VB-SCript.:15</td>
<td align="left" bgcolor="#33CC66">T</td>
<td align="left" bgcolor="#33CC66" sdval="84" sdnum="1033;">84</td>
<td align="left" bgcolor="#33CC66">0x0054</td>
<td align="left" bgcolor="#33CC66" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Execute VB-SCript.:15</td>
<td align="left" bgcolor="#33CC66">T</td>
<td align="left" bgcolor="#33CC66" sdval="84" sdnum="1033;">84</td>
<td align="left" bgcolor="#33CC66">0x0054</td>
<td align="left" bgcolor="#33CC66" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Flood toggle</td>
<td align="left" bgcolor="#33CC66">C</td>
<td align="left" bgcolor="#33CC66" sdval="67" sdnum="1033;">67</td>
<td align="left" bgcolor="#33CC66">0x0043</td>
<td align="left" bgcolor="#33CC66" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Flood toggle</td>
<td align="left" bgcolor="#33CC66">C</td>
<td align="left" bgcolor="#33CC66" sdval="67" sdnum="1033;">67</td>
<td align="left" bgcolor="#33CC66">0x0043</td>
<td align="left" bgcolor="#33CC66" sdval="13" sdnum="1033;">13</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Flood toggle</td>
<td align="left" bgcolor="#33CC66">C</td>
<td align="left" bgcolor="#33CC66" sdval="67" sdnum="1033;">67</td>
<td align="left" bgcolor="#33CC66">0x0043</td>
<td align="left" bgcolor="#33CC66" sdval="4" sdnum="1033;">4</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Flood toggle</td>
<td align="left" bgcolor="#33CC66">C</td>
<td align="left" bgcolor="#33CC66" sdval="67" sdnum="1033;">67</td>
<td align="left" bgcolor="#33CC66">0x0043</td>
<td align="left" bgcolor="#33CC66" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Jog increment cycle</td>
<td align="left" bgcolor="#33CC66">Alt J</td>
<td align="left" bgcolor="#33CC66" sdval="2122" sdnum="1033;">2122</td>
<td align="left" bgcolor="#33CC66">0x084a</td>
<td align="left" bgcolor="#33CC66" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Load G-code</td>
<td align="left" bgcolor="#33CC66">L</td>
<td align="left" bgcolor="#33CC66" sdval="76" sdnum="1033;">76</td>
<td align="left" bgcolor="#33CC66">0x004c</td>
<td align="left" bgcolor="#33CC66" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Pause</td>
<td align="left" bgcolor="#33CC66">F</td>
<td align="left" bgcolor="#33CC66" sdval="70" sdnum="1033;">70</td>
<td align="left" bgcolor="#33CC66">0x0046</td>
<td align="left" bgcolor="#33CC66" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Reset</td>
<td align="left" bgcolor="#33CC66">ESC</td>
<td align="left" bgcolor="#33CC66" sdval="27" sdnum="1033;">27</td>
<td align="left" bgcolor="#33CC66">0x001b</td>
<td align="left" bgcolor="#33CC66" sdval="0" sdnum="1033;">0</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Rewind</td>
<td align="left" bgcolor="#33CC66">R</td>
<td align="left" bgcolor="#33CC66" sdval="82" sdnum="1033;">82</td>
<td align="left" bgcolor="#33CC66">0x0052</td>
<td align="left" bgcolor="#33CC66" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Rewind</td>
<td align="left" bgcolor="#33CC66">R</td>
<td align="left" bgcolor="#33CC66" sdval="82" sdnum="1033;">82</td>
<td align="left" bgcolor="#33CC66">0x0052</td>
<td align="left" bgcolor="#33CC66" sdval="13" sdnum="1033;">13</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Run from here</td>
<td align="left" bgcolor="#33CC66">H</td>
<td align="left" bgcolor="#33CC66" sdval="72" sdnum="1033;">72</td>
<td align="left" bgcolor="#33CC66">0x0048</td>
<td align="left" bgcolor="#33CC66" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Screen 1 select(e.g. Program Run screen) Button</td>
<td align="left" bgcolor="#33CC66">Q</td>
<td align="left" bgcolor="#33CC66" sdval="81" sdnum="1033;">81</td>
<td align="left" bgcolor="#33CC66">0x0051</td>
<td align="left" bgcolor="#33CC66" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Screen 1 select(e.g. Program Run screen) Button</td>
<td align="left" bgcolor="#33CC66">Q</td>
<td align="left" bgcolor="#33CC66" sdval="81" sdnum="1033;">81</td>
<td align="left" bgcolor="#33CC66">0x0051</td>
<td align="left" bgcolor="#33CC66" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Screen 1 select(e.g. Program Run screen) Button</td>
<td align="left" bgcolor="#33CC66">Q</td>
<td align="left" bgcolor="#33CC66" sdval="81" sdnum="1033;">81</td>
<td align="left" bgcolor="#33CC66">0x0051</td>
<td align="left" bgcolor="#33CC66" sdval="4" sdnum="1033;">4</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Screen 2 select (e.g. MDI screen select)</td>
<td align="left" bgcolor="#33CC66">A</td>
<td align="left" bgcolor="#33CC66" sdval="65" sdnum="1033;">65</td>
<td align="left" bgcolor="#33CC66">0x0041</td>
<td align="left" bgcolor="#33CC66" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Screen 2 select (e.g. MDI screen select)</td>
<td align="left" bgcolor="#33CC66">B</td>
<td align="left" bgcolor="#33CC66" sdval="66" sdnum="1033;">66</td>
<td align="left" bgcolor="#33CC66">0x0042</td>
<td align="left" bgcolor="#33CC66" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Show recent G-code files list</td>
<td align="left" bgcolor="#33CC66">R</td>
<td align="left" bgcolor="#33CC66" sdval="82" sdnum="1033;">82</td>
<td align="left" bgcolor="#33CC66">0x0052</td>
<td align="left" bgcolor="#33CC66" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Single</td>
<td align="left" bgcolor="#33CC66">Alt S</td>
<td align="left" bgcolor="#33CC66" sdval="2131" sdnum="1033;">2131</td>
<td align="left" bgcolor="#33CC66">0x0853</td>
<td align="left" bgcolor="#33CC66" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Single</td>
<td align="left" bgcolor="#33CC66">S</td>
<td align="left" bgcolor="#33CC66" sdval="83" sdnum="1033;">83</td>
<td align="left" bgcolor="#33CC66">0x0053</td>
<td align="left" bgcolor="#33CC66" sdval="13" sdnum="1033;">13</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Slow Jog Dn</td>
<td align="left" bgcolor="#33CC66">OEM_4</td>
<td align="left" bgcolor="#33CC66" sdval="219" sdnum="1033;">219</td>
<td align="left" bgcolor="#33CC66">0x00db</td>
<td align="left" bgcolor="#33CC66" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Slow Jog Up</td>
<td align="left" bgcolor="#33CC66">OEM_6</td>
<td align="left" bgcolor="#33CC66" sdval="221" sdnum="1033;">221</td>
<td align="left" bgcolor="#33CC66">0x00dd</td>
<td align="left" bgcolor="#33CC66" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Spindle CW, reset THC height</td>
<td align="left" bgcolor="#33CC66">S</td>
<td align="left" bgcolor="#33CC66" sdval="83" sdnum="1033;">83</td>
<td align="left" bgcolor="#33CC66">0x0053</td>
<td align="left" bgcolor="#33CC66" sdval="4" sdnum="1033;">4</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Spindle CW, reset THC height</td>
<td align="left" bgcolor="#33CC66">S</td>
<td align="left" bgcolor="#33CC66" sdval="83" sdnum="1033;">83</td>
<td align="left" bgcolor="#33CC66">0x0053</td>
<td align="left" bgcolor="#33CC66" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Spindle CW, reset THC height</td>
<td align="left" bgcolor="#33CC66">S</td>
<td align="left" bgcolor="#33CC66" sdval="83" sdnum="1033;">83</td>
<td align="left" bgcolor="#33CC66">0x0053</td>
<td align="left" bgcolor="#33CC66" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Spindle CW, reset THC height</td>
<td align="left" bgcolor="#33CC66">S</td>
<td align="left" bgcolor="#33CC66" sdval="83" sdnum="1033;">83</td>
<td align="left" bgcolor="#33CC66">0x0053</td>
<td align="left" bgcolor="#33CC66" sdval="13" sdnum="1033;">13</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Stop</td>
<td align="left" bgcolor="#33CC66">F</td>
<td align="left" bgcolor="#33CC66" sdval="70" sdnum="1033;">70</td>
<td align="left" bgcolor="#33CC66">0x0046</td>
<td align="left" bgcolor="#33CC66" sdval="13" sdnum="1033;">13</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Stop</td>
<td align="left" bgcolor="#33CC66">Space</td>
<td align="left" bgcolor="#33CC66" sdval="32" sdnum="1033;">32</td>
<td align="left" bgcolor="#33CC66">0x0020</td>
<td align="left" bgcolor="#33CC66" sdval="4" sdnum="1033;">4</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Stop</td>
<td align="left" bgcolor="#33CC66">Space</td>
<td align="left" bgcolor="#33CC66" sdval="32" sdnum="1033;">32</td>
<td align="left" bgcolor="#33CC66">0x0020</td>
<td align="left" bgcolor="#33CC66" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Stop</td>
<td align="left" bgcolor="#33CC66">Space</td>
<td align="left" bgcolor="#33CC66" sdval="32" sdnum="1033;">32</td>
<td align="left" bgcolor="#33CC66">0x0020</td>
<td align="left" bgcolor="#33CC66" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#33CC66">1024.lset (Lathe)</td>
<td align="left" bgcolor="#33CC66">Toggle Jog Mode Through Cont/Step/Step Velocity/Velocity Only</td>
<td align="left" bgcolor="#33CC66">Ctrl J</td>
<td align="left" bgcolor="#33CC66" sdval="32842" sdnum="1033;">32842</td>
<td align="left" bgcolor="#33CC66">0x804a</td>
<td align="left" bgcolor="#33CC66" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">A DRO</td>
<td align="left" bgcolor="#FFFF00">Ctrl A</td>
<td align="left" bgcolor="#FFFF00" sdval="32833" sdnum="1033;">32833</td>
<td align="left" bgcolor="#FFFF00">0x8041</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">A DRO</td>
<td align="left" bgcolor="#FFFF00">Ctrl A</td>
<td align="left" bgcolor="#FFFF00" sdval="32833" sdnum="1033;">32833</td>
<td align="left" bgcolor="#FFFF00">0x8041</td>
<td align="left" bgcolor="#FFFF00" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Block Delete switch toggle</td>
<td align="left" bgcolor="#FFFF00">Delete</td>
<td align="left" bgcolor="#FFFF00" sdval="46" sdnum="1033;">46</td>
<td align="left" bgcolor="#FFFF00">0x002e</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Cycle axis controlled by MPG 1</td>
<td align="left" bgcolor="#FFFF00">Alt A</td>
<td align="left" bgcolor="#FFFF00" sdval="2113" sdnum="1033;">2113</td>
<td align="left" bgcolor="#FFFF00">0x0841</td>
<td align="left" bgcolor="#FFFF00" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Cycle axis controlled by MPG 2</td>
<td align="left" bgcolor="#FFFF00">Alt B</td>
<td align="left" bgcolor="#FFFF00" sdval="2114" sdnum="1033;">2114</td>
<td align="left" bgcolor="#FFFF00">0x0842</td>
<td align="left" bgcolor="#FFFF00" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Cycle start</td>
<td align="left" bgcolor="#FFFF00">Alt R</td>
<td align="left" bgcolor="#FFFF00" sdval="2130" sdnum="1033;">2130</td>
<td align="left" bgcolor="#FFFF00">0x0852</td>
<td align="left" bgcolor="#FFFF00" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Cycle start</td>
<td align="left" bgcolor="#FFFF00">Alt R</td>
<td align="left" bgcolor="#FFFF00" sdval="2130" sdnum="1033;">2130</td>
<td align="left" bgcolor="#FFFF00">0x0852</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">e.g. Corrections screen select</td>
<td align="left" bgcolor="#FFFF00">Alt 6</td>
<td align="left" bgcolor="#FFFF00" sdval="2102" sdnum="1033;">2102</td>
<td align="left" bgcolor="#FFFF00">0x0836</td>
<td align="left" bgcolor="#FFFF00" sdval="0" sdnum="1033;">0</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">e.g. Diagnostics screen select</td>
<td align="left" bgcolor="#FFFF00">Alt 7</td>
<td align="left" bgcolor="#FFFF00" sdval="2103" sdnum="1033;">2103</td>
<td align="left" bgcolor="#FFFF00">0x0837</td>
<td align="left" bgcolor="#FFFF00" sdval="0" sdnum="1033;">0</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">e.g. Tables screen select</td>
<td align="left" bgcolor="#FFFF00">Alt 5</td>
<td align="left" bgcolor="#FFFF00" sdval="2101" sdnum="1033;">2101</td>
<td align="left" bgcolor="#FFFF00">0x0835</td>
<td align="left" bgcolor="#FFFF00" sdval="0" sdnum="1033;">0</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">e.g. Toolpath screen select</td>
<td align="left" bgcolor="#FFFF00">Alt 4</td>
<td align="left" bgcolor="#FFFF00" sdval="2100" sdnum="1033;">2100</td>
<td align="left" bgcolor="#FFFF00">0x0834</td>
<td align="left" bgcolor="#FFFF00" sdval="0" sdnum="1033;">0</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Enc To Z</td>
<td align="left" bgcolor="#FFFF00">F15</td>
<td align="left" bgcolor="#FFFF00" sdval="126" sdnum="1033;">126</td>
<td align="left" bgcolor="#FFFF00">0x007e</td>
<td align="left" bgcolor="#FFFF00" sdval="6" sdnum="1033;">6</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Execute VB-SCript</td>
<td align="left" bgcolor="#FFFF00">Alt T</td>
<td align="left" bgcolor="#FFFF00" sdval="2132" sdnum="1033;">2132</td>
<td align="left" bgcolor="#FFFF00">0x0854</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Execute VB-SCript</td>
<td align="left" bgcolor="#FFFF00">Pos home</td>
<td align="left" bgcolor="#FFFF00" sdval="36" sdnum="1033;">36</td>
<td align="left" bgcolor="#FFFF00">0x0024</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Execute VB-SCript.:105</td>
<td align="left" bgcolor="#FFFF00">Pos home</td>
<td align="left" bgcolor="#FFFF00" sdval="36" sdnum="1033;">36</td>
<td align="left" bgcolor="#FFFF00">0x0024</td>
<td align="left" bgcolor="#FFFF00" sdval="7" sdnum="1033;">7</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Execute VB-SCript.:105</td>
<td align="left" bgcolor="#FFFF00">Pos home</td>
<td align="left" bgcolor="#FFFF00" sdval="36" sdnum="1033;">36</td>
<td align="left" bgcolor="#FFFF00">0x0024</td>
<td align="left" bgcolor="#FFFF00" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Execute VB-SCript.:183</td>
<td align="left" bgcolor="#FFFF00">OEM_5</td>
<td align="left" bgcolor="#FFFF00" sdval="220" sdnum="1033;">220</td>
<td align="left" bgcolor="#FFFF00">0x00dc</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Feed lower</td>
<td align="left" bgcolor="#FFFF00">F10</td>
<td align="left" bgcolor="#FFFF00" sdval="121" sdnum="1033;">121</td>
<td align="left" bgcolor="#FFFF00">0x0079</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Feed lower</td>
<td align="left" bgcolor="#FFFF00">F10</td>
<td align="left" bgcolor="#FFFF00" sdval="121" sdnum="1033;">121</td>
<td align="left" bgcolor="#FFFF00">0x0079</td>
<td align="left" bgcolor="#FFFF00" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Feed raise</td>
<td align="left" bgcolor="#FFFF00">F11</td>
<td align="left" bgcolor="#FFFF00" sdval="122" sdnum="1033;">122</td>
<td align="left" bgcolor="#FFFF00">0x007a</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Feed raise</td>
<td align="left" bgcolor="#FFFF00">F11</td>
<td align="left" bgcolor="#FFFF00" sdval="122" sdnum="1033;">122</td>
<td align="left" bgcolor="#FFFF00">0x007a</td>
<td align="left" bgcolor="#FFFF00" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Feedrate reset</td>
<td align="left" bgcolor="#FFFF00">OEM_2</td>
<td align="left" bgcolor="#FFFF00" sdval="191" sdnum="1033;">191</td>
<td align="left" bgcolor="#FFFF00">0x00bf</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Feedrate reset</td>
<td align="left" bgcolor="#FFFF00">OEM_2</td>
<td align="left" bgcolor="#FFFF00" sdval="191" sdnum="1033;">191</td>
<td align="left" bgcolor="#FFFF00">0x00bf</td>
<td align="left" bgcolor="#FFFF00" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Flood toggle</td>
<td align="left" bgcolor="#FFFF00">Ctrl F</td>
<td align="left" bgcolor="#FFFF00" sdval="32838" sdnum="1033;">32838</td>
<td align="left" bgcolor="#FFFF00">0x8046</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Goto Safe Z</td>
<td align="left" bgcolor="#FFFF00">Alt Z</td>
<td align="left" bgcolor="#FFFF00" sdval="2138" sdnum="1033;">2138</td>
<td align="left" bgcolor="#FFFF00">0x085a</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Goto Safe Z</td>
<td align="left" bgcolor="#FFFF00">Ctrl Z</td>
<td align="left" bgcolor="#FFFF00" sdval="32858" sdnum="1033;">32858</td>
<td align="left" bgcolor="#FFFF00">0x805a</td>
<td align="left" bgcolor="#FFFF00" sdval="4" sdnum="1033;">4</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">GotoZs</td>
<td align="left" bgcolor="#FFFF00">Ctrl O</td>
<td align="left" bgcolor="#FFFF00" sdval="32847" sdnum="1033;">32847</td>
<td align="left" bgcolor="#FFFF00">0x804f</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Jog increment cycle</td>
<td align="left" bgcolor="#FFFF00">Alt J</td>
<td align="left" bgcolor="#FFFF00" sdval="2122" sdnum="1033;">2122</td>
<td align="left" bgcolor="#FFFF00">0x084a</td>
<td align="left" bgcolor="#FFFF00" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Jog mode toggle</td>
<td align="left" bgcolor="#FFFF00">Ctrl Alt J</td>
<td align="left" bgcolor="#FFFF00" sdval="34890" sdnum="1033;">34890</td>
<td align="left" bgcolor="#FFFF00">0x884a</td>
<td align="left" bgcolor="#FFFF00" sdval="10" sdnum="1033;">10</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Jog mode toggle</td>
<td align="left" bgcolor="#FFFF00">Ctrl Alt J</td>
<td align="left" bgcolor="#FFFF00" sdval="34890" sdnum="1033;">34890</td>
<td align="left" bgcolor="#FFFF00">0x884a</td>
<td align="left" bgcolor="#FFFF00" sdval="5" sdnum="1033;">5</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Jog mode toggle</td>
<td align="left" bgcolor="#FFFF00">Ctrl Alt J</td>
<td align="left" bgcolor="#FFFF00" sdval="34890" sdnum="1033;">34890</td>
<td align="left" bgcolor="#FFFF00">0x884a</td>
<td align="left" bgcolor="#FFFF00" sdval="7" sdnum="1033;">7</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Jog mode toggle</td>
<td align="left" bgcolor="#FFFF00">Ctrl Alt J</td>
<td align="left" bgcolor="#FFFF00" sdval="34890" sdnum="1033;">34890</td>
<td align="left" bgcolor="#FFFF00">0x884a</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Jog mode toggle</td>
<td align="left" bgcolor="#FFFF00">Ctrl Alt J</td>
<td align="left" bgcolor="#FFFF00" sdval="34890" sdnum="1033;">34890</td>
<td align="left" bgcolor="#FFFF00">0x884a</td>
<td align="left" bgcolor="#FFFF00" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Jog mode toggle</td>
<td align="left" bgcolor="#FFFF00">Ctrl Alt J</td>
<td align="left" bgcolor="#FFFF00" sdval="34890" sdnum="1033;">34890</td>
<td align="left" bgcolor="#FFFF00">0x884a</td>
<td align="left" bgcolor="#FFFF00" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Joystick Toggle</td>
<td align="left" bgcolor="#FFFF00">Ctrl S</td>
<td align="left" bgcolor="#FFFF00" sdval="32851" sdnum="1033;">32851</td>
<td align="left" bgcolor="#FFFF00">0x8053</td>
<td align="left" bgcolor="#FFFF00" sdval="4" sdnum="1033;">4</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Load G-code</td>
<td align="left" bgcolor="#FFFF00">Alt L</td>
<td align="left" bgcolor="#FFFF00" sdval="2124" sdnum="1033;">2124</td>
<td align="left" bgcolor="#FFFF00">0x084c</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Lower spindle speed</td>
<td align="left" bgcolor="#FFFF00">Numpad Min</td>
<td align="left" bgcolor="#FFFF00" sdval="109" sdnum="1033;">109</td>
<td align="left" bgcolor="#FFFF00">0x006d</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Lower spindle speed</td>
<td align="left" bgcolor="#FFFF00">Numpad Min</td>
<td align="left" bgcolor="#FFFF00" sdval="109" sdnum="1033;">109</td>
<td align="left" bgcolor="#FFFF00">0x006d</td>
<td align="left" bgcolor="#FFFF00" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Optional Stop switch toggle</td>
<td align="left" bgcolor="#FFFF00">Pos end</td>
<td align="left" bgcolor="#FFFF00" sdval="35" sdnum="1033;">35</td>
<td align="left" bgcolor="#FFFF00">0x0023</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Pause</td>
<td align="left" bgcolor="#FFFF00">Space</td>
<td align="left" bgcolor="#FFFF00" sdval="32" sdnum="1033;">32</td>
<td align="left" bgcolor="#FFFF00">0x0020</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Pause</td>
<td align="left" bgcolor="#FFFF00">Space</td>
<td align="left" bgcolor="#FFFF00" sdval="32" sdnum="1033;">32</td>
<td align="left" bgcolor="#FFFF00">0x0020</td>
<td align="left" bgcolor="#FFFF00" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Pause</td>
<td align="left" bgcolor="#FFFF00">Space</td>
<td align="left" bgcolor="#FFFF00" sdval="32" sdnum="1033;">32</td>
<td align="left" bgcolor="#FFFF00">0x0020</td>
<td align="left" bgcolor="#FFFF00" sdval="5" sdnum="1033;">5</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Raise spindle speed</td>
<td align="left" bgcolor="#FFFF00">Numpad Add</td>
<td align="left" bgcolor="#FFFF00" sdval="107" sdnum="1033;">107</td>
<td align="left" bgcolor="#FFFF00">0x006b</td>
<td align="left" bgcolor="#FFFF00" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Raise spindle speed</td>
<td align="left" bgcolor="#FFFF00">Numpad Add</td>
<td align="left" bgcolor="#FFFF00" sdval="107" sdnum="1033;">107</td>
<td align="left" bgcolor="#FFFF00">0x006b</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Reset</td>
<td align="left" bgcolor="#FFFF00">OEM_3</td>
<td align="left" bgcolor="#FFFF00" sdval="192" sdnum="1033;">192</td>
<td align="left" bgcolor="#FFFF00">0x00c0</td>
<td align="left" bgcolor="#FFFF00" sdval="0" sdnum="1033;">0</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Reset Interp</td>
<td align="left" bgcolor="#FFFF00">Alt I</td>
<td align="left" bgcolor="#FFFF00" sdval="2121" sdnum="1033;">2121</td>
<td align="left" bgcolor="#FFFF00">0x0849</td>
<td align="left" bgcolor="#FFFF00" sdval="6" sdnum="1033;">6</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Rewind</td>
<td align="left" bgcolor="#FFFF00">Ctrl W</td>
<td align="left" bgcolor="#FFFF00" sdval="32855" sdnum="1033;">32855</td>
<td align="left" bgcolor="#FFFF00">0x8057</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Rewind</td>
<td align="left" bgcolor="#FFFF00">Ctrl W</td>
<td align="left" bgcolor="#FFFF00" sdval="32855" sdnum="1033;">32855</td>
<td align="left" bgcolor="#FFFF00">0x8057</td>
<td align="left" bgcolor="#FFFF00" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Screen 1 select(e.g. Program Run screen) Button</td>
<td align="left" bgcolor="#FFFF00">Alt 1</td>
<td align="left" bgcolor="#FFFF00" sdval="2097" sdnum="1033;">2097</td>
<td align="left" bgcolor="#FFFF00">0x0831</td>
<td align="left" bgcolor="#FFFF00" sdval="0" sdnum="1033;">0</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Screen 2 select (e.g. MDI screen select)</td>
<td align="left" bgcolor="#FFFF00">Alt 2</td>
<td align="left" bgcolor="#FFFF00" sdval="2098" sdnum="1033;">2098</td>
<td align="left" bgcolor="#FFFF00">0x0832</td>
<td align="left" bgcolor="#FFFF00" sdval="0" sdnum="1033;">0</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Single</td>
<td align="left" bgcolor="#FFFF00">Alt N</td>
<td align="left" bgcolor="#FFFF00" sdval="2126" sdnum="1033;">2126</td>
<td align="left" bgcolor="#FFFF00">0x084e</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Single</td>
<td align="left" bgcolor="#FFFF00">Alt N</td>
<td align="left" bgcolor="#FFFF00" sdval="2126" sdnum="1033;">2126</td>
<td align="left" bgcolor="#FFFF00">0x084e</td>
<td align="left" bgcolor="#FFFF00" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Slow Jog Dn</td>
<td align="left" bgcolor="#FFFF00">OEM_4</td>
<td align="left" bgcolor="#FFFF00" sdval="219" sdnum="1033;">219</td>
<td align="left" bgcolor="#FFFF00">0x00db</td>
<td align="left" bgcolor="#FFFF00" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Slow Jog Up</td>
<td align="left" bgcolor="#FFFF00">OEM_6</td>
<td align="left" bgcolor="#FFFF00" sdval="221" sdnum="1033;">221</td>
<td align="left" bgcolor="#FFFF00">0x00dd</td>
<td align="left" bgcolor="#FFFF00" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Spindle CW, reset THC height</td>
<td align="left" bgcolor="#FFFF00">F5</td>
<td align="left" bgcolor="#FFFF00" sdval="116" sdnum="1033;">116</td>
<td align="left" bgcolor="#FFFF00">0x0074</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Spindle CW, reset THC height</td>
<td align="left" bgcolor="#FFFF00">F5</td>
<td align="left" bgcolor="#FFFF00" sdval="116" sdnum="1033;">116</td>
<td align="left" bgcolor="#FFFF00">0x0074</td>
<td align="left" bgcolor="#FFFF00" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Stop</td>
<td align="left" bgcolor="#FFFF00">Alt S</td>
<td align="left" bgcolor="#FFFF00" sdval="2131" sdnum="1033;">2131</td>
<td align="left" bgcolor="#FFFF00">0x0853</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Stop</td>
<td align="left" bgcolor="#FFFF00">Alt S</td>
<td align="left" bgcolor="#FFFF00" sdval="2131" sdnum="1033;">2131</td>
<td align="left" bgcolor="#FFFF00">0x0853</td>
<td align="left" bgcolor="#FFFF00" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Toggle axis DROs display Dist to Go</td>
<td align="left" bgcolor="#FFFF00">Ctrl O</td>
<td align="left" bgcolor="#FFFF00" sdval="32847" sdnum="1033;">32847</td>
<td align="left" bgcolor="#FFFF00">0x804f</td>
<td align="left" bgcolor="#FFFF00" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Toggle Jog Mode Through Cont/Step/Step Velocity/Velocity Only</td>
<td align="left" bgcolor="#FFFF00">Ctrl J</td>
<td align="left" bgcolor="#FFFF00" sdval="32842" sdnum="1033;">32842</td>
<td align="left" bgcolor="#FFFF00">0x804a</td>
<td align="left" bgcolor="#FFFF00" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Units</td>
<td align="left" bgcolor="#FFFF00">Alt F6</td>
<td align="left" bgcolor="#FFFF00" sdval="2165" sdnum="1033;">2165</td>
<td align="left" bgcolor="#FFFF00">0x0875</td>
<td align="left" bgcolor="#FFFF00" sdval="6" sdnum="1033;">6</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">unknown</td>
<td align="left" bgcolor="#FFFF00">Alt C</td>
<td align="left" bgcolor="#FFFF00" sdval="2115" sdnum="1033;">2115</td>
<td align="left" bgcolor="#FFFF00">0x0843</td>
<td align="left" bgcolor="#FFFF00" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Verify</td>
<td align="left" bgcolor="#FFFF00">Ctrl V</td>
<td align="left" bgcolor="#FFFF00" sdval="32854" sdnum="1033;">32854</td>
<td align="left" bgcolor="#FFFF00">0x8056</td>
<td align="left" bgcolor="#FFFF00" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Verify</td>
<td align="left" bgcolor="#FFFF00">Ctrl V</td>
<td align="left" bgcolor="#FFFF00" sdval="32854" sdnum="1033;">32854</td>
<td align="left" bgcolor="#FFFF00">0x8056</td>
<td align="left" bgcolor="#FFFF00" sdval="4" sdnum="1033;">4</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">X DRO</td>
<td align="left" bgcolor="#FFFF00">Ctrl X</td>
<td align="left" bgcolor="#FFFF00" sdval="32856" sdnum="1033;">32856</td>
<td align="left" bgcolor="#FFFF00">0x8058</td>
<td align="left" bgcolor="#FFFF00" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">X DRO</td>
<td align="left" bgcolor="#FFFF00">Ctrl X</td>
<td align="left" bgcolor="#FFFF00" sdval="32856" sdnum="1033;">32856</td>
<td align="left" bgcolor="#FFFF00">0x8058</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Y DRO</td>
<td align="left" bgcolor="#FFFF00">Ctrl Y</td>
<td align="left" bgcolor="#FFFF00" sdval="32857" sdnum="1033;">32857</td>
<td align="left" bgcolor="#FFFF00">0x8059</td>
<td align="left" bgcolor="#FFFF00" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Y DRO</td>
<td align="left" bgcolor="#FFFF00">Ctrl Y</td>
<td align="left" bgcolor="#FFFF00" sdval="32857" sdnum="1033;">32857</td>
<td align="left" bgcolor="#FFFF00">0x8059</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Z DRO</td>
<td align="left" bgcolor="#FFFF00">Ctrl Z</td>
<td align="left" bgcolor="#FFFF00" sdval="32858" sdnum="1033;">32858</td>
<td align="left" bgcolor="#FFFF00">0x805a</td>
<td align="left" bgcolor="#FFFF00" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Z DRO</td>
<td align="left" bgcolor="#FFFF00">Ctrl Z</td>
<td align="left" bgcolor="#FFFF00" sdval="32858" sdnum="1033;">32858</td>
<td align="left" bgcolor="#FFFF00">0x805a</td>
<td align="left" bgcolor="#FFFF00" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Zero X Encoder</td>
<td align="left" bgcolor="#FFFF00">F9</td>
<td align="left" bgcolor="#FFFF00" sdval="120" sdnum="1033;">120</td>
<td align="left" bgcolor="#FFFF00">0x0078</td>
<td align="left" bgcolor="#FFFF00" sdval="6" sdnum="1033;">6</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Zero Y Encoder</td>
<td align="left" bgcolor="#FFFF00">F10</td>
<td align="left" bgcolor="#FFFF00" sdval="121" sdnum="1033;">121</td>
<td align="left" bgcolor="#FFFF00">0x0079</td>
<td align="left" bgcolor="#FFFF00" sdval="6" sdnum="1033;">6</td>
</tr>
<tr>
<td height="17" align="left" bgcolor="#FFFF00">1024.set (Mill)</td>
<td align="left" bgcolor="#FFFF00">Zero Z Encoder</td>
<td align="left" bgcolor="#FFFF00">F11</td>
<td align="left" bgcolor="#FFFF00" sdval="122" sdnum="1033;">122</td>
<td align="left" bgcolor="#FFFF00">0x007a</td>
<td align="left" bgcolor="#FFFF00" sdval="6" sdnum="1033;">6</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Block Delete switch toggle</td>
<td align="left" bgcolor="#00DCFF">Delete</td>
<td align="left" bgcolor="#00DCFF" sdval="46" sdnum="1033;">46</td>
<td align="left" bgcolor="#00DCFF">0x002e</td>
<td align="left" bgcolor="#00DCFF" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Cycle axis controlled by MPG 1</td>
<td align="left" bgcolor="#00DCFF">Alt A</td>
<td align="left" bgcolor="#00DCFF" sdval="2113" sdnum="1033;">2113</td>
<td align="left" bgcolor="#00DCFF">0x0841</td>
<td align="left" bgcolor="#00DCFF" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Cycle axis controlled by MPG 2</td>
<td align="left" bgcolor="#00DCFF">Alt B</td>
<td align="left" bgcolor="#00DCFF" sdval="2114" sdnum="1033;">2114</td>
<td align="left" bgcolor="#00DCFF">0x0842</td>
<td align="left" bgcolor="#00DCFF" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Cycle start</td>
<td align="left" bgcolor="#00DCFF">Alt R</td>
<td align="left" bgcolor="#00DCFF" sdval="2130" sdnum="1033;">2130</td>
<td align="left" bgcolor="#00DCFF">0x0852</td>
<td align="left" bgcolor="#00DCFF" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Cycle start</td>
<td align="left" bgcolor="#00DCFF">Alt R</td>
<td align="left" bgcolor="#00DCFF" sdval="2130" sdnum="1033;">2130</td>
<td align="left" bgcolor="#00DCFF">0x0852</td>
<td align="left" bgcolor="#00DCFF" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">e.g. Corrections screen select</td>
<td align="left" bgcolor="#00DCFF">Alt 6</td>
<td align="left" bgcolor="#00DCFF" sdval="2102" sdnum="1033;">2102</td>
<td align="left" bgcolor="#00DCFF">0x0836</td>
<td align="left" bgcolor="#00DCFF" sdval="0" sdnum="1033;">0</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">e.g. Diagnostics screen select</td>
<td align="left" bgcolor="#00DCFF">Alt 7</td>
<td align="left" bgcolor="#00DCFF" sdval="2103" sdnum="1033;">2103</td>
<td align="left" bgcolor="#00DCFF">0x0837</td>
<td align="left" bgcolor="#00DCFF" sdval="0" sdnum="1033;">0</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">e.g. Toolpath screen select</td>
<td align="left" bgcolor="#00DCFF">Alt 4</td>
<td align="left" bgcolor="#00DCFF" sdval="2100" sdnum="1033;">2100</td>
<td align="left" bgcolor="#00DCFF">0x0834</td>
<td align="left" bgcolor="#00DCFF" sdval="0" sdnum="1033;">0</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Enc To Z</td>
<td align="left" bgcolor="#00DCFF">F15</td>
<td align="left" bgcolor="#00DCFF" sdval="126" sdnum="1033;">126</td>
<td align="left" bgcolor="#00DCFF">0x007e</td>
<td align="left" bgcolor="#00DCFF" sdval="6" sdnum="1033;">6</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Execute VB-SCript</td>
<td align="left" bgcolor="#00DCFF">Pos home</td>
<td align="left" bgcolor="#00DCFF" sdval="36" sdnum="1033;">36</td>
<td align="left" bgcolor="#00DCFF">0x0024</td>
<td align="left" bgcolor="#00DCFF" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Execute VB-SCript.:105</td>
<td align="left" bgcolor="#00DCFF">Pos home</td>
<td align="left" bgcolor="#00DCFF" sdval="36" sdnum="1033;">36</td>
<td align="left" bgcolor="#00DCFF">0x0024</td>
<td align="left" bgcolor="#00DCFF" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Feed lower</td>
<td align="left" bgcolor="#00DCFF">F10</td>
<td align="left" bgcolor="#00DCFF" sdval="121" sdnum="1033;">121</td>
<td align="left" bgcolor="#00DCFF">0x0079</td>
<td align="left" bgcolor="#00DCFF" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Feed raise</td>
<td align="left" bgcolor="#00DCFF">F11</td>
<td align="left" bgcolor="#00DCFF" sdval="122" sdnum="1033;">122</td>
<td align="left" bgcolor="#00DCFF">0x007a</td>
<td align="left" bgcolor="#00DCFF" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Feedrate reset</td>
<td align="left" bgcolor="#00DCFF">OEM_2</td>
<td align="left" bgcolor="#00DCFF" sdval="191" sdnum="1033;">191</td>
<td align="left" bgcolor="#00DCFF">0x00bf</td>
<td align="left" bgcolor="#00DCFF" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Feedrate reset</td>
<td align="left" bgcolor="#00DCFF">OEM_2</td>
<td align="left" bgcolor="#00DCFF" sdval="191" sdnum="1033;">191</td>
<td align="left" bgcolor="#00DCFF">0x00bf</td>
<td align="left" bgcolor="#00DCFF" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Goto Safe Z</td>
<td align="left" bgcolor="#00DCFF">Ctrl Z</td>
<td align="left" bgcolor="#00DCFF" sdval="32858" sdnum="1033;">32858</td>
<td align="left" bgcolor="#00DCFF">0x805a</td>
<td align="left" bgcolor="#00DCFF" sdval="4" sdnum="1033;">4</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">GotoZs</td>
<td align="left" bgcolor="#00DCFF">Ctrl O</td>
<td align="left" bgcolor="#00DCFF" sdval="32847" sdnum="1033;">32847</td>
<td align="left" bgcolor="#00DCFF">0x804f</td>
<td align="left" bgcolor="#00DCFF" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Jog increment cycle</td>
<td align="left" bgcolor="#00DCFF">Alt J</td>
<td align="left" bgcolor="#00DCFF" sdval="2122" sdnum="1033;">2122</td>
<td align="left" bgcolor="#00DCFF">0x084a</td>
<td align="left" bgcolor="#00DCFF" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Jog mode toggle</td>
<td align="left" bgcolor="#00DCFF">Ctrl Alt J</td>
<td align="left" bgcolor="#00DCFF" sdval="34890" sdnum="1033;">34890</td>
<td align="left" bgcolor="#00DCFF">0x884a</td>
<td align="left" bgcolor="#00DCFF" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Jog mode toggle</td>
<td align="left" bgcolor="#00DCFF">Ctrl Alt J</td>
<td align="left" bgcolor="#00DCFF" sdval="34890" sdnum="1033;">34890</td>
<td align="left" bgcolor="#00DCFF">0x884a</td>
<td align="left" bgcolor="#00DCFF" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Jog mode toggle</td>
<td align="left" bgcolor="#00DCFF">Ctrl Alt J</td>
<td align="left" bgcolor="#00DCFF" sdval="34890" sdnum="1033;">34890</td>
<td align="left" bgcolor="#00DCFF">0x884a</td>
<td align="left" bgcolor="#00DCFF" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Jog mode toggle</td>
<td align="left" bgcolor="#00DCFF">Ctrl Alt J</td>
<td align="left" bgcolor="#00DCFF" sdval="34890" sdnum="1033;">34890</td>
<td align="left" bgcolor="#00DCFF">0x884a</td>
<td align="left" bgcolor="#00DCFF" sdval="10" sdnum="1033;">10</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Jog mode toggle</td>
<td align="left" bgcolor="#00DCFF">Ctrl Alt J</td>
<td align="left" bgcolor="#00DCFF" sdval="34890" sdnum="1033;">34890</td>
<td align="left" bgcolor="#00DCFF">0x884a</td>
<td align="left" bgcolor="#00DCFF" sdval="5" sdnum="1033;">5</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Joystick Toggle</td>
<td align="left" bgcolor="#00DCFF">Ctrl S</td>
<td align="left" bgcolor="#00DCFF" sdval="32851" sdnum="1033;">32851</td>
<td align="left" bgcolor="#00DCFF">0x8053</td>
<td align="left" bgcolor="#00DCFF" sdval="4" sdnum="1033;">4</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Optional Stop switch toggle</td>
<td align="left" bgcolor="#00DCFF">Pos end</td>
<td align="left" bgcolor="#00DCFF" sdval="35" sdnum="1033;">35</td>
<td align="left" bgcolor="#00DCFF">0x0023</td>
<td align="left" bgcolor="#00DCFF" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Pause</td>
<td align="left" bgcolor="#00DCFF">Space</td>
<td align="left" bgcolor="#00DCFF" sdval="32" sdnum="1033;">32</td>
<td align="left" bgcolor="#00DCFF">0x0020</td>
<td align="left" bgcolor="#00DCFF" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Pause</td>
<td align="left" bgcolor="#00DCFF">Space</td>
<td align="left" bgcolor="#00DCFF" sdval="32" sdnum="1033;">32</td>
<td align="left" bgcolor="#00DCFF">0x0020</td>
<td align="left" bgcolor="#00DCFF" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Pause</td>
<td align="left" bgcolor="#00DCFF">Space</td>
<td align="left" bgcolor="#00DCFF" sdval="32" sdnum="1033;">32</td>
<td align="left" bgcolor="#00DCFF">0x0020</td>
<td align="left" bgcolor="#00DCFF" sdval="5" sdnum="1033;">5</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Reset</td>
<td align="left" bgcolor="#00DCFF">OEM_3</td>
<td align="left" bgcolor="#00DCFF" sdval="192" sdnum="1033;">192</td>
<td align="left" bgcolor="#00DCFF">0x00c0</td>
<td align="left" bgcolor="#00DCFF" sdval="0" sdnum="1033;">0</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Reset Interp</td>
<td align="left" bgcolor="#00DCFF">Alt I</td>
<td align="left" bgcolor="#00DCFF" sdval="2121" sdnum="1033;">2121</td>
<td align="left" bgcolor="#00DCFF">0x0849</td>
<td align="left" bgcolor="#00DCFF" sdval="6" sdnum="1033;">6</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Rewind</td>
<td align="left" bgcolor="#00DCFF">Ctrl W</td>
<td align="left" bgcolor="#00DCFF" sdval="32855" sdnum="1033;">32855</td>
<td align="left" bgcolor="#00DCFF">0x8057</td>
<td align="left" bgcolor="#00DCFF" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Rewind</td>
<td align="left" bgcolor="#00DCFF">Ctrl W</td>
<td align="left" bgcolor="#00DCFF" sdval="32855" sdnum="1033;">32855</td>
<td align="left" bgcolor="#00DCFF">0x8057</td>
<td align="left" bgcolor="#00DCFF" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Screen 1 select(e.g. Program Run screen) Button</td>
<td align="left" bgcolor="#00DCFF">Alt 1</td>
<td align="left" bgcolor="#00DCFF" sdval="2097" sdnum="1033;">2097</td>
<td align="left" bgcolor="#00DCFF">0x0831</td>
<td align="left" bgcolor="#00DCFF" sdval="0" sdnum="1033;">0</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Screen 2 select (e.g. MDI screen select)</td>
<td align="left" bgcolor="#00DCFF">Alt 2</td>
<td align="left" bgcolor="#00DCFF" sdval="2098" sdnum="1033;">2098</td>
<td align="left" bgcolor="#00DCFF">0x0832</td>
<td align="left" bgcolor="#00DCFF" sdval="0" sdnum="1033;">0</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Single</td>
<td align="left" bgcolor="#00DCFF">Alt N</td>
<td align="left" bgcolor="#00DCFF" sdval="2126" sdnum="1033;">2126</td>
<td align="left" bgcolor="#00DCFF">0x084e</td>
<td align="left" bgcolor="#00DCFF" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Single</td>
<td align="left" bgcolor="#00DCFF">Alt N</td>
<td align="left" bgcolor="#00DCFF" sdval="2126" sdnum="1033;">2126</td>
<td align="left" bgcolor="#00DCFF">0x084e</td>
<td align="left" bgcolor="#00DCFF" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Slow Jog Dn</td>
<td align="left" bgcolor="#00DCFF">OEM_4</td>
<td align="left" bgcolor="#00DCFF" sdval="219" sdnum="1033;">219</td>
<td align="left" bgcolor="#00DCFF">0x00db</td>
<td align="left" bgcolor="#00DCFF" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Slow Jog Up</td>
<td align="left" bgcolor="#00DCFF">OEM_6</td>
<td align="left" bgcolor="#00DCFF" sdval="221" sdnum="1033;">221</td>
<td align="left" bgcolor="#00DCFF">0x00dd</td>
<td align="left" bgcolor="#00DCFF" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Spindle CW, reset THC height</td>
<td align="left" bgcolor="#00DCFF">F5</td>
<td align="left" bgcolor="#00DCFF" sdval="116" sdnum="1033;">116</td>
<td align="left" bgcolor="#00DCFF">0x0074</td>
<td align="left" bgcolor="#00DCFF" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Spindle CW, reset THC height</td>
<td align="left" bgcolor="#00DCFF">F5</td>
<td align="left" bgcolor="#00DCFF" sdval="116" sdnum="1033;">116</td>
<td align="left" bgcolor="#00DCFF">0x0074</td>
<td align="left" bgcolor="#00DCFF" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Stop</td>
<td align="left" bgcolor="#00DCFF">Alt S</td>
<td align="left" bgcolor="#00DCFF" sdval="2131" sdnum="1033;">2131</td>
<td align="left" bgcolor="#00DCFF">0x0853</td>
<td align="left" bgcolor="#00DCFF" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Stop</td>
<td align="left" bgcolor="#00DCFF">Alt S</td>
<td align="left" bgcolor="#00DCFF" sdval="2131" sdnum="1033;">2131</td>
<td align="left" bgcolor="#00DCFF">0x0853</td>
<td align="left" bgcolor="#00DCFF" sdval="3" sdnum="1033;">3</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Toggle axis DROs display Dist to Go</td>
<td align="left" bgcolor="#00DCFF">Ctrl O</td>
<td align="left" bgcolor="#00DCFF" sdval="32847" sdnum="1033;">32847</td>
<td align="left" bgcolor="#00DCFF">0x804f</td>
<td align="left" bgcolor="#00DCFF" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Toggle axis DROs display Dist to Go</td>
<td align="left" bgcolor="#00DCFF">Ctrl O</td>
<td align="left" bgcolor="#00DCFF" sdval="32847" sdnum="1033;">32847</td>
<td align="left" bgcolor="#00DCFF">0x804f</td>
<td align="left" bgcolor="#00DCFF" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Toggle Jog Mode Through Cont/Step/Step Velocity/Velocity Only</td>
<td align="left" bgcolor="#00DCFF">Ctrl J</td>
<td align="left" bgcolor="#00DCFF" sdval="32842" sdnum="1033;">32842</td>
<td align="left" bgcolor="#00DCFF">0x804a</td>
<td align="left" bgcolor="#00DCFF" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Units</td>
<td align="left" bgcolor="#00DCFF">Alt F6</td>
<td align="left" bgcolor="#00DCFF" sdval="2165" sdnum="1033;">2165</td>
<td align="left" bgcolor="#00DCFF">0x0875</td>
<td align="left" bgcolor="#00DCFF" sdval="6" sdnum="1033;">6</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">unknown</td>
<td align="left" bgcolor="#00DCFF">Alt C</td>
<td align="left" bgcolor="#00DCFF" sdval="2115" sdnum="1033;">2115</td>
<td align="left" bgcolor="#00DCFF">0x0843</td>
<td align="left" bgcolor="#00DCFF" sdval="50" sdnum="1033;">50</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Verify</td>
<td align="left" bgcolor="#00DCFF">Ctrl V</td>
<td align="left" bgcolor="#00DCFF" sdval="32854" sdnum="1033;">32854</td>
<td align="left" bgcolor="#00DCFF">0x8056</td>
<td align="left" bgcolor="#00DCFF" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Verify</td>
<td align="left" bgcolor="#00DCFF">Ctrl V</td>
<td align="left" bgcolor="#00DCFF" sdval="32854" sdnum="1033;">32854</td>
<td align="left" bgcolor="#00DCFF">0x8056</td>
<td align="left" bgcolor="#00DCFF" sdval="4" sdnum="1033;">4</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">X DRO</td>
<td align="left" bgcolor="#00DCFF">Ctrl X</td>
<td align="left" bgcolor="#00DCFF" sdval="32856" sdnum="1033;">32856</td>
<td align="left" bgcolor="#00DCFF">0x8058</td>
<td align="left" bgcolor="#00DCFF" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">X DRO</td>
<td align="left" bgcolor="#00DCFF">Ctrl X</td>
<td align="left" bgcolor="#00DCFF" sdval="32856" sdnum="1033;">32856</td>
<td align="left" bgcolor="#00DCFF">0x8058</td>
<td align="left" bgcolor="#00DCFF" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Y DRO</td>
<td align="left" bgcolor="#00DCFF">Ctrl Y</td>
<td align="left" bgcolor="#00DCFF" sdval="32857" sdnum="1033;">32857</td>
<td align="left" bgcolor="#00DCFF">0x8059</td>
<td align="left" bgcolor="#00DCFF" sdval="2" sdnum="1033;">2</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Y DRO</td>
<td align="left" bgcolor="#00DCFF">Ctrl Y</td>
<td align="left" bgcolor="#00DCFF" sdval="32857" sdnum="1033;">32857</td>
<td align="left" bgcolor="#00DCFF">0x8059</td>
<td align="left" bgcolor="#00DCFF" sdval="1" sdnum="1033;">1</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Zero X Encoder</td>
<td align="left" bgcolor="#00DCFF">F9</td>
<td align="left" bgcolor="#00DCFF" sdval="120" sdnum="1033;">120</td>
<td align="left" bgcolor="#00DCFF">0x0078</td>
<td align="left" bgcolor="#00DCFF" sdval="6" sdnum="1033;">6</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Zero Y Encoder</td>
<td align="left" bgcolor="#00DCFF">F10</td>
<td align="left" bgcolor="#00DCFF" sdval="121" sdnum="1033;">121</td>
<td align="left" bgcolor="#00DCFF">0x0079</td>
<td align="left" bgcolor="#00DCFF" sdval="6" sdnum="1033;">6</td>
</tr>
<tr>
<td height="18" align="left" bgcolor="#00DCFF">Plasma.set</td>
<td align="left" bgcolor="#00DCFF">Zero Z Encoder</td>
<td align="left" bgcolor="#00DCFF">F11</td>
<td align="left" bgcolor="#00DCFF" sdval="122" sdnum="1033;">122</td>
<td align="left" bgcolor="#00DCFF">0x007a</td>
<td align="left" bgcolor="#00DCFF" sdval="6" sdnum="1033;">6</td>
</tr>
<tr>
<td height="17" align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
</tr>
<tr>
<td height="17" align="left"> </td>
<td align="left">Current Hot keys as of 5-9-09 </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
</tr>
<tr>
<td height="17" align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
</tr>
<tr>
<td height="17" align="left"> </td>
<td align="left">A spreadsheet containg this information </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
</tr>
<tr>
<td height="17" align="left"> </td>
<td align="left">can be downloaded from [http://www.machsupport.com/forum/index.php/topic,11463.msg72722.html#msg72722 here] </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
</tr>

<tr>
<td height="17" align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
</tr>
<tr>
<td height="17" align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
<td align="left"> </td>
</tr>

</table>

The G100/GREX plugin as a model for device control

JAPrenticeUK — Tue, 08 Aug 2006 08:31:11 GMT

Summary:

==Introduction==

This document is a tutorial in how to create a plugin under Mach3 that will override the native printer port driver, and allow one to send movement and I/O via another driver/Device. This device may use any of several protocols, including USB, TCP/IP, and common serial port communication.

Since the G100 Plugin is likely the most complex to be written due to its lack of an API (initially anyway), we will use it as the example for the process. Sample code posted in this document can also be seen in the Mach3 SDK under the G100 subfolder.

First, let's take a look at what's necessary for a typical plugin of the non-movement variety. "Movement" plugins are built from that foundation.

Files:

MachDevice.cpp/.h
MachDevImplementation.cpp/.h
XMLProfile.cpp/.h

These files define a plugin. The MachDevice.cpp/.h are files which will morph over time as more two-way functions are available to call between Mach3 and a plugin. All the required calls for the writer of a plugin are in MachDevImplementation.cpp. In there are calls such as:

void myInitControl (); // called during Mach initialisation
// you can influence subsequent init by actions here
// **** Not used in typical device plugin
void myPostInitControl (); //called when mach is fully set up
void myConfig (CXMLProfile *DevProf); // Called to configure the device
void myUpdate (); // 10Hz update loop
void myHighSpeedUpdate (); // called at 40Hz
void myCleanUp(); // Used to cleanup heap variables before
// destrucion of PlugIn
void myHome( short axis);
void myProbe();

Lets take a quick look at each..

void myInitControl ()

This routine is called when Mach3 is starting up. It allows a plugin to do some initialization work and to set itself up. In a movement plugin it is necessary to inform Mach3 that this '''IS''' a movement plugin, so the user should be asked if he wishes to take advantage of the non-native device. This is done by setting a variable in the Mach viewclass called <tt>m_PrinterOn</tt>. As in <tt>MachView->m_PrinterOn = false;</tt>

This call forces Mach to recognize that a plugin is available and to make sure the user has a chance to use it. It tells Mach3 not to load the printer port driver. You will see this in the InitControl call of the G100 plugin as well as some other housekeeping things we’ll go over later.

void myPostInitControl ();

This one gets called after Mach3 has setup all its various stages and is about to start running fully. In this call you still have a chance to use the Mach3 profile database. Normally, there is no access to the user settings database during run time; Mach3 cannot share it with the plugin. However, at startup and config time, access is granted. In functions where it is allowed, you will see calls such as ,//tt>DefDir-> GetProfileString("Preferences","DefDir","C:\\Mach3\\");</tt>

This is a call to the database to get the Default folder Mach is using.

void myConfig (CXMLProfile *DevProf);

This is called when the user asks for the configuration of a plugin. The G100 plugin then opens a dialog to allow setup of the G100’s parameters.

void myUpdate ();

This routine is called 10 times per second when Mach3 is running.
Is is handy to keep a process synced or to run periodic tasks.

void myHighSpeedUpdate ();

If you need a faster update timer, this one is available. It is called 40 times per second when Mach3 is running. Don’t use it for much heavy work, it can affect Mach3’s available CPU time.

void myCleanUp();

This gets called when the program shuts down. A PlugIn can cleanup any variables it may have created.

== How Mach3 Works ==

Before you can effectively take over Mach3’s control, it's handy to know how exactly it works.

Mach3 is a great many timers and loops of messages. Each is self contained in a master loop, a loop which operates at about 10Hz. The Mach3 printer port engine operates on a loop of 25KHz, and is self contained and automatic. In other words, given a series of commands, Mach3’s printer port driver runs autonomously, and with no interference. The 10 hz loop in Mach3 keeps check on the printer port driver, sends it commands and responds to various semaphores to know when it needs to interact with the Engines variable block.

For example, if Mach3 wants to Jog with the printer port, it needs only to set a variable (<tt>Engine->Axis[n].Jogging = True</tt> after setting a max speed with <tt>Engine->Axis[n].MaxVelocity = 8334400</tt>, the jog would be automatic and will ramp up to speed and hold until told to stop. The 8334400 is the number of steps/second * 2^12 in order to give the integer based engine code a divisable integer to get many points of precision.

The G100 has to perform many of its functions autonomously (to replace the Pport Driver), so the Plugin will get a command like <tt>JogOn (x,nnn)</tt> telling it to do the job previously done by the printer port driver.

What is important to the External movement plugin author is '''how''' do I get those commands; and how do I tell Mach3 my states at various times. We’ll go over the entire problem here, and how the G100 implements it.

=== Problem #1: Protocols ===

To speak to an external movement controller, we need a protocol. This can be serial, TCP, USB, ect. So the first job for the plugin is to implement a protocol. The one we’ll
use in the G100 is a TCP protocol. So we build it up from the start. I'm using a TCP class
that connects a TCP port to the plugin. We’ll do that in the <tt>PostInitControl()</tt>.

void myPostInitControl ()
// called when mach fully set up so all data can be used but initialization
// outcomes not affected
{
// In the case of a MotionControl plugin, this routine is only called to tell us to take
// over. We HAVE been selected and are now commanded to do whatever it takes to OWN the IO
// and movement of this run.
// For example, if you wish to zero all IO at this point, you're free to do so...
//
// First, let's add a message tracking facility to handle message traffic output.
// Output is in its own class because it's important that we do not overrun the G100's
// buffers or queues. We'll make the tracker object intelligent enough to be able
// to handle any errors, retransmissions and tracking ack numbers and such...
// Now let's open a Debug File. We'll only use it if instructed by Mach3's DebugThisRun
// selection in config/state
G100.Discovered.Stage = DISCNONE;
CTime time = CTime::GetCurrentTime();
CString stamp = time.Format( "%a - %H:%M:%S ---");
// Now a message tracker class. It will marshal messages and make sure
// we don't flood the G100.
if( G100Mess == NULL)
{
G100Mess = new MessageTracker(); //we'll delete this in the shutdown routine.
// Now let's initialise some G100 variables.
G100Mess->ResetQueue( );
}
if( G100Mon == NULL)
{
G100Mon = new Monitoring(); //we'll delete this in the shutdown routine.
// Now lets initialise some G100 variables.
}
G100.InJog = false;
InitJogMessage();
// In the G100 case, we'll open/start-up a network thread to deal with communications..
StartNetwork();
return;
} //myPostInitControl

The last command here is to start the network object. You'll see I have created other objects like a MessageTracker facility for the G100 and a safety monitor. You can ignore all those for now; just notice the call to startNetwork above. It starts the network process by this routine..

void StartNetwork()
{
int t; //error storage
G100.Discovered.Done = false;
G100.SEQUENCE = NOSEQ;
G100.Discovered.Stage = STAGE1; //set discovery to stage 1.
//
// udp setup..
G100.PHASE = DISCOVERY; //set G100 to Discovery phase with zeroed address
//automatically, due to code int he 10hz update, discovery
//will begin;
G100.Config.ipaddr = 0; //set out IP to zero until we discover it.
AfxSocketInit();
if( g100sock != NULL )
{
delete g100sock;
}
g100sock = new CUDPSocket(); //startup the TCP support
if( !g100sock->Create(13887))
{
G100.PHASE = DISABLED;
G100.Disability = "Socket Open Failure";
G100Mess->DebugOut( G100.Disability );
return;
}
//
G100.Disability = "Starting Discovery."; //set a tracking message in case of error.

int res = g100sock->SetSockOpt( SO_DONTROUTE, &t, 1);
res = g100sock->AsyncSelect( FD_READ | FD_WRITE | FD_OOB | FD_ACCEPT | FD_CONNECT |
FD_CLOSE ); //full capability
res = g100sock->SetSockOpt( SO_BROADCAST, &t, 1); //set socket to broadcast;
} //StartNetwork

In the case of theG100, I have created a large data structure to keep track of all its various states. It is called GRex, and has many variables in it.

struct GRex
{
WTConfig Config
Phase PHASE; // current phase of G100 .
Sequencing SEQUENCE; // Home and Probhe sequence
MessageSeq MESSAGESEQ;
Discovery Discovered; // process information
CString Disability; // Reason G100 is disabled.
AddressAssign G100Address; // Address Asignment Block
bool StartUp; // initial message traffic
CTime LastMessageTime; // Time last message was received
//
// Traffic variables.
short LastAck; //The last message Acked
short LastMess; //The last Message Sent.
short LastStored; //the last message stored.
short Window; //Last Window received.
//
//Condition Varibale
int InWord; //the last 32bit input
int OutputWord; //The last OutputWord sent
int CurrentISR; //Current G100 timer
int CurrentMISR; // Current G100 timer count. ISR counter
WTMsAbs LastAbs; //Last absolute structure
int CurDDA[6]; //Current DDA's from last status
double LastCoord[6]; //last ABS coordinate from status.
int CurrentQueueSeq; //Current Queue Seq.
int NextQueue; //the next movements queue
int EndQueueSeq; // As of last status, the last move
// message in the queue
int QueueFlags; // and the last Queue
int CurrentHaltBits; //Current monitoring bits
int CurrentHaltMask; // Current halt condition
int CurrentMonMask; //Current monitoring mask
bool IsStill; // Set by status if the G100 is
// state.sflags & QS_STILL
bool IsDrained; // set by last state is state.sflags & QS_MAVGZ
bool InJog; //Is any axis Jogging
int CurrentMavg; //Current Mavg in use.
int CalcMavg; //Expected Mavg
bool Dwelling; //bool that tells the system were waiting
// for a IsStill to clear a dwell
bool HasMoved; //tracks that a move has started for
// probeing and homing sequences.
bool NeedDigOutputs; //Trigger to send new outputs
bool NeedAnaOutputs; //Trigger to make Analogues go out
bool Homing; // We're in a homing move
int HomingMask; //needed for homing the appropriate axis
int HomeAxis; //current homing axis;
//
// Monitoring Vars.
int LastChallenge; //the last responded to
bool Monitoring; // Are we currently
int MonitorHaltBits; //halt conditions and levels
int MonitorHaltMask;
int MonitorMask; //Non critical monitoring
int CurrentChallenge; // Currently sent
bool SystemHalted; //System is currently
CTime WaitSet;
//
// G100 Sync Events
WaitState WaitForState;
unsigned int WaitForValue;
};

Most of these variables will become clear as you peruse the code of the plugin, they contain Booleans to trigger certain events under certain circumstances. Your movement plugin is unlikely to need this level of complexity. Most external hardware will have an API to do the majority of the work, or less of a configurable outcome than the G100.

As you can see I have a variable called <tt>PHASE</tt> which I use to do a several step process of contacting the G100 to see if I can take control of it. This phaseing is automatic and the end result is a <tt>PHASE</tt> called <tt>IPRUN</tt> which tells us its OK to do normal traffic. The stages are handled by the 10hz timer. IT will send messages and monitor responses until we can achieve stage IPRUN; meaning the hardware is all ready.

Look at how the discovery loop is called. We set <tt>PHASE</tt> to <tt>DISCOVERY</tt> and <tt>G100.Discovered.Stage</tt> to <tt>STAGE1</tt>, send a quick message of “Are you there” out the network port, and we now need to see what to do next. So the 10hz update loop checks it all.

void myUpdate ()
{
//................
CTime Now = CTime::GetCurrentTime();
CTimeSpan Since = Now - G100.LastMessageTime; //Time since last ???
switch ( G100.PHASE )
{
case( DISABLED ): return;
case( RUNONIP
if(Since.GetSeconds() > 1 && !Engine->EStop)
{
Engine->EStop = true; //set an ???
Engine->EStopReason = 12;
}
G100Mon->Update();
break; //this will process IO and such..
case( DISCOVERY ): DiscoveryLoop();
break;
}
} // myUpdate

Since the G100 variable <tt>PHASE</tt> is set to <tt>Discovery</tt>, no other action will happen except discovery work. SO the DiscoveryLoop is called repeatedly until the phase switches to <tt>RUNONIP</tt>. Let's look at <tt>DiscoveryLoop</tt> then..

It basically checks for what stage we’re in, and if the requirements of that stage have been met so we can progress to the next stage in discovery.

switch( G100.Discovered.Stage )
{
case( DISCNONE ): //just a holder while we startup the discovery..
break;
case( STAGE1 ): G100.Discovered.Stage = STAGE2;
res = g100sock->SendTo( NULL, 0, 13887 ,
"255.255.255.255" , 0);
if( res == SOCKET_ERROR )
{
error = g100sock->GetLastError();
G100.PHASE = DISABLED;
G100.Disability = " Error Sending on initial 13887 port.";
G100Mess->DebugOut( G100.Disability );
g100sock->Close();
fig = new G100Config();
fig->DoModal();
}
G100.Discovered.started = CTime::GetCurrentTime();
G100.Discovered.ended = CTime::GetCurrentTime();
break;
case( STAGE2) : // Here we'll check for a timeout on the initial discovery.
// We should have a response within a few seconds.
G100.Discovered.ended = CTime::GetCurrentTime();...................

Ok, So here is <tt>stage1</tt1> being checked. We just set it to <tt>Stage1</tt> earlier, now the discovery loop knows to send out the “Are you there” question and bump the stage to <tt>STAGE2</tt>. Similarly, these stages will progress if the conditions are met until we hit the stage <tt>RUNONIP</tt> where the system will begin normal operations. You can see in <tt<stage2</tt> checking…

case( STAGE2) : // Here we'll check for a timeout on the initial discovery.
// We should have a response within a few seconds.
G100.Discovered.ended = CTime::GetCurrentTime();
sofar = G100.Discovered.ended - G100.Discovered.started;
seconds = sofar.GetSeconds();
if( seconds > 5 )
{
G100.Disability = " TimeOut in UDP Reception. No G100 Answered.";
G100Mess->DebugOut( G100.Disability );
G100.PHASE = DISABLED;
g100sock->Close();
fig = new G100Config();
fig->DoModal();
}
return;

It starts by checking the time to see if 5 seconds have passed. If we haven’t got a response from the G100 and the stage hasn’t been bumped to <tt>stage3</tt> within 5 seconds, we will get an error. Each stage checks itself to make sure it hasn’t got hung up on an earlier stage: it will trigger a timeout message and that will open a dialog allowing the user to restart the discovery. So all this begs the question, what bumps it to <tt>stage3</tt> so this timeout doesn’t happen?

Most of the messageing in the G100 plugin is triggered by the incoming messages. The TCP class Im using is Event driven; that is to say you don’t need to poll for data, the functions PlugRecieve() will be called whenever a message comes in and we're not in <tt>RUNONIP</tt> condition. So I use this function as a trigger to process incoming messages as well as to trigger events like stage checking. Lets look at it..

void PlugReceive( char *Buffer, int m_size )
{
if( ShutDown ) return;
//
// Discovery Traffic Message Handing
//
if( m_size == sizeof( WTConfig ) && G100.Discovered.Stage == STAGE2 )
//Is this a config packet responce??
{ //and are we lookign for one? If not, discard.
memcpy( &G100.Config, Buffer, m_size );
G100.Discovered.Stage = STAGE3; //we now have the G100 config.
// Switch to Stage 3, IP RUN switchover or error checking
//of the IP.
if( G100.Config.version == VERSION_DLM ) //check that the firmware is running..
{
G100.PHASE = DISABLED;
G100.Disability = " G100 not running firmware. Reboot G100";
return;
}
}
// if we're waiting for first IP responce, lets tell Discovery worker
// that we are now fully connected.
if( G100.Discovered.Stage == STAGE4 )
{
//We are getting Stage4 traffic, so bump to Stage 5. We're done with discovery;
G100.Discovered.Stage = STAGE5;
return;
}

As you can see it is bumping the stages up until finally we hit <tt>stage5</tt> when we will switchover to <tt>RUNONIP</tt>, which is the normal run time of the plugin. All of this from config to full discovery takes about 3-5 seconds after startup depending on the system. So now we have a running TCP link, and message traffic is OK to go. We have a send message routine, and this function will now process messages with the remainder of its function.

//
// RUNONIP stage message handling.
// This will be the normal incoming traffic
// We only reach here with normal incoming traffic.
//
memcpy( &InMessage, Buffer, m_size );
//first copy the entire message into the message structure.
G100.Window = ((InMessage.Header.chanflgs & UCHAN_WNDO) & 0x07);
//set the max message window for the input buffer of the rabbit.
G100.LastMessageTime = CTime::GetCurrentTime();
//If we get a less than 6 byte messge, we have a sequence error..!!
if( m_size <= 6)
{
//Message Loss Error Usually happens at high traffic..
int lost = InMessage.Header.seq;
G100Mess->LostMessage( lost );
} else
{
G100Mess->AckMessage( InMessage.Header.ack );
G100TranslateMessage( InMessage, m_size );
}
//Messages have now been decoded, all G100 states shoudl be set accordingly.
// So lets update the Message Tracker so it knows
// its limitations based on any new information
G100Mess->Update(); //this doesnt send anythign,
//it just ensures the tracker knows how much it CAN send if needs be.
//So now lets send any output that is required.
//The translations above have set the parameters in the G100 Block
// to tell us it is now necessary to transmit an output message.
if( G100.NeedDigOutputs ) DoDigOutput();
//and analogue as well
if( G100.NeedAnaOutputs ) DoAnalogOutput();
//If we're Jogging, lets refresh the Jog..
if( G100.InJog ) Rejog();
//We really only need to send Inputs & Outputs
//every 1/4 second or so. So we'll just nudge it
// here to do a send if there is one holding..
DoGcodeMove(); //take care of any waiting Gcode movement;
if( G100Mess->nMessages > 0 ) G100Mess->SendMessages();

}

As you can see, now we have a set of routines that check G100 specific protocol, such as checking the message size. If it's less than 6 bytes, an error has occurred in transmision and error handlers get called. If it is more than 6, then it will Ack the message to the state routines, and translate it for processing. It will also run <tt>G100Mess->Update</tt> which will do things such as send any holding messages and such. Most of this is unimportant to USB and Serial authors, perhaps.. But it is an idea of how the message traffic is controlled. I set up a link, then continuously buffer messages, which are sent and acknowledged, translated, and dealt with in the routines we've discussed.

=== Problem #2: How do I control IO traffic/ ===

Mach3, in its 10Hz loop, looks at all incoming and outgoing I/O requirements. If a spindle needs to be turned on, or an input needs to be acknowledged, it is done in the 10hz loop, but can be done anytime.

In our case, the G100 is sending a status message every 250ms telling us the current input and output conditions. When we look at the <tt>G100TranslateMessage( InMessage, m_size );</tt> from the Receiving loop of the PlugIn we can see the IO being checked.

switch( InMessage.Header.type )
{
case WT_MONITOR:
mon = (WTMonitor*) &InMessage.Message;
G100Mon->OnMonitorMessage( mon );
break;
case WT_MS_FULL:
status = (WTMsFull*) &InMessage.Message;
FillFromFullStatus( *status );
break;
case WT_MS_OUTIN:
oi = (WTMsOutIn*)&InMessage.Message;
CheckInputs(oi->in ); //active
CheckOutputs( oi->out ); //active
break;
case WT_MS_ASYNC:
asyn = (WTMsAsync*)&InMessage.Message;
CheckQueueCap( asyn->qcap ,true );
CheckRELPosition( asyn->pos ); //active
CheckCurrentState( asyn->qstate );
break;
case WT_MS_POS:
pos = (WTMsPos*)&InMessage.Message;
CheckRELPosition( *pos ); //active
break;
case WT_MS_CTR:
ctr = (WTMsCtr*)&InMessage.Message;
CheckEncoders( *ctr ); //active
break;
case WT_MS_IN:
in = (WTMsIn*)&InMessage.Message;
CheckInputs( *in );
break;
case WT_MS_OUT:
out = (WTMsOut*)&InMessage.Message;
CheckOutputs( *out ); //active
break;
case WT_MS_ABS:
abs = (WTMsAbs*)&InMessage.Message;
CheckABSPosition( *abs ); //active
break;
case WT_MS_QSTAT:
stat = (WTMsQstat*)&InMessage.Message;
CheckCurrentState( *stat );
break;
case WT_MS_QCAP:
cap = (WTMsQcap*)&InMessage.Message;
CheckQueueCap( *cap , true ); //check the queue capacity
break;
default:
break;
}

This loop looks at incoming message types. The input messages are <tt>WT_MS_IN</tt> and <tt>WT_MS_OUT</tt> so they call <tt>CheckInputs( *in )</tt> and <tt>CheckOutputs( *out )</tt> when needed. These routines look at the incoming bits and compare them to what Mach3 has; same for outputs. Lets look at outputs for example.

void CheckOutputs( WTMsOut out )
{
bool On = false;
G100.NeedDigOutputs = false;
unsigned int outs = 0;
for( int x = 0; x< nSigsOut; x++ )
{
if( Engine->OutSigs[x].OutPort == 1 &&
Engine->OutSigs[x].active &&
Engine->OutSigs[x].OutPin >= 1 &&
Engine->OutSigs[x].OutPin < 17 ) //pins 1-16
{
On = Engine->OutSigs[x].Activated;
if( Engine->OutSigs[x].Negated) On = !On;
//On is now true or false depending on the current state
SetBit( outs, On, Engine->OutSigs[x].OutPin); //set the bit in the output..
}
}
if( out.o != outs ) G100.NeedDigOutputs = true;
G100.NeedAnaOutputs = false;
if( (unsigned short)MainPlanner->ModOutputs[124] != out.aout[0] ||
//analogue outputs from analogue holding registers.
(unsigned short)MainPlanner->ModOutputs[125] != out.aout[1] ||
(unsigned short)MainPlanner->ModOutputs[126] != out.aout[2] ||
//analogue #3 seems unable to accept data
(unsigned short)MainPlanner->ModOutputs[127] != out.aout[3])
G100.NeedAnaOutputs = true;
}; //outputs

Mach3 has a variable block in the engine (seen in Engine.h) which has all the various output signals. <tt>Engine->OutSigs[x]</tt>, this block is checked against the reported output of the G100. The end result of all this checking is <tt>G100.NeedDigOutputs = true</tt>; if the outputs are not in sync with what Mach3 knows should be set. The system will then (because this variable is set to true) send a message to the G100 to tell it to update the outputs to match Mach3. This same process is seen for inputs and outputs.

So in summary: Each time the G100 sends an input or output status, it is checked against required status, and a setoutput message is sent if the outputs are not aligned with expectations. If we look at inputs.

void CheckInputs( WTMsIn In )
{
In.i = ShuffleInWord( In.i); //shuffle the input word..
G100.InWord = In.i;
bool On = false;
for( int x = 0; x< nSigs; x++ )
{
if( Engine->InSigs[x].InPort == 1 &&
Engine->InSigs[x].Active &&
Engine->InSigs[x].InPin >= 1 &&
Engine->InSigs[x].InPin < 23 )
{
On = ((In.i >> (Engine->InSigs[x].InPin -1)) & 0x01);
Engine->InSigs[x].Activated = On;
if( Engine->InSigs[x].Negated ) Engine->InSigs[x].Activated = !On;
}
if( x < 64 )
{
int mask = 1 << x;
if( (Engine->WaitCondition & mask) > 0 )
if( Engine->InSigs[x].Active && Engine->InSigs[x].Activated )
//to make Mach3 waitcondition work..
Engine->WaitCondition &= ( 0xffffffff ^ mask );
}
}
MainPlanner->ModInputs[124] = In.ain[0];
//analogue inputs to the analogue holding registers.
MainPlanner->ModInputs[125] = In.ain[1];
MainPlanner->ModInputs[126] = In.ain[2];
MainPlanner->ModInputs[127] = In.ain[3];
}; //inputs

We can see the inputs are retrieved as bits, then shuffled into the <tt>Engine->inSigs[n]</tt> variable block so that Mach3 knows what signal is set and when. It will take care of the rest. If an input has been set, Mach3 will deal with it appropriately. If a particular input means '''your''' hardware needs to perform a particular function, you should then perform it.

=== Problem #3 : How Do I get Movement? ===

SO we now have seen how Inputs and Outputs are done. Now we have to create movement. The hard part! First, let's consider what Mach3 does for movement. There are two types; Jogging and Trajectory movement. Each is very important, and many don’t consider the importance of Jogging highly enough. The tactility of Jogging is not to be underestimated to make hardware use less frustrating. So first, we’ll take a look as how jogging is done in a g100 system.

Any external device will require code to do its jogging. Mach3 only cares about two things, first that it be told jogging is underway so it will not attempt other movement functions, and second that when jogging stops, that it be told so, in order to update its position registers with proper position. Mach keeps track of its position as an integer value of current number of steps put out. Those values can be updated automatically, by setting the variable <tt>Engine->Sync</tt> to true. This value will change back to false when Mach3 completes the syncing operation.

The routines, <tt>void MyJogOn( short axis, short direction, double SpeedNorm)</tt> and <tt>void MyJogOff(short axis)</tt> are called directly from Mach3 to the ExternalMovement.cpp file in order to control Jogging.

The meanings are obvious, except perhaps for the <tt>SpeedNorm</tt> value in the jogon call. This value will be zero if normal jog speed is desired, and will be a value if a special speed is to be used. The routine also checks to see if the Keyboard is actively holding down the shift key. This is used to override the <tt>_setup->JogPercent</tt> value (which Mach3 maintains to tell the plugin writer what % of maximum speed should be used for this jog operation.) In other words, if the JogOn routine gets called and the keyboard is not shifted, and the <tt>SpeedNorm</tt> is zero, then Jog will be at (JogPerCent/100)* MainPlanner->Velocities[axis]. <tt>MainPlanner->Velocities[axis]</tt> is the holder for the maximum speed an axis is programmed to go. If the shift key is held, then that’s the speed which will be used. IF <tt>SpeedNorm</tt> is set, then that’s the speed the jog should be performed at. This is used for some special circumstances where jog must be controlled at a finer rate.

The routine MyJogOff(axis) will stop a jog in progress. In there, you will see that when all jogs are stopped, a call is made to resync positions by setting that variable <tt>Engine->Sync = true</tt>. Mach3 will then resync all its internal positions to be accurate when it sees all movement has stopped.

What about GCode movement? Well, we’ve seen that jogging is just a commanded movement to the external device. The G100 requires that this be confirmed every 250ms, so you'll see code in there to allow for the jogging messages to be re-sent every 250ms to keep jogging active. This is a safety; your hardware may not have that option. GCode movement is easy to get, but its difficulty in sending to your device depends a lot on the device. Lets look at the routine called <tt>void DoGcodeMove()</tt>

This routine gets called every time a message comes in from the G100, it can be called as frequenctly as you wish. It has one job, to see if movement is holding, and if so, to send it out. Mach3 buffers up movements and holds them in a ring buffer. Mach will stop buffering movement when either the buffer is full, or no more movement exists. A plugin basically just sits around sending I/O messages, checking the IO is proper, jogging or stopping jogging. It only needs to know that when the Gcode buffer is not empty; it needs to empty it by sending the data. It starts with this line:

<tt>if( Engine->TrajHead == Engine->TrajIndex || Engine->DwellTime > 0) return; //no moves to process</tt>

<tt>Engine->TrajHead</tt> is the head of a ringbuffer, <tt>TrajIndex</tt> is the tail. If these two values are the same, no data is holding. If <tt>DwellTime</tt> is not zero then we are dwelling and no movement should be sent. (Unless the device can buffer it up until the dwell is complete. It is up to the author of the plugin to make sure he sends no more information to the external device than it can handle. You’ll see queue size checks in the G100 code to do this. Most of the code in this routine can be ignored by other programmers, the important thing is to be able to tell if movement is holding, and if so, how to get it. The <tt>TrajIndex</tt> and <tt>TrajHead</tt> check will tell you if it is holding. To get it you need only reach into the ring buffer with a call like:

<tt>CurrentMove = MainPlanner->Movements[Engine->TrajIndex]</tt>

The <tt>CurrentMove</tt> variable is a <tt>GMoves</tt> structure. Youll see it in the trajectorycontrol.h file. Its structure is:

struct GMoves
{
int type; // 0 is linear, 1 is cubic
double cx,cy,cz; // center of move for cubics.
double ex,ey,ez,ea,eb,ec;
double sx,sy,sz,sa,sb,sc;
__int64 DDA1[6]; //DDA1's for cubics
__int64 DDA2[6];
__int64 DDA3[6];
double Time;
bool Stop;
};

The ring buffer is up to 2048 entries long. So there are 2048 (or less) GMove structures for you to send. You grab them one at a time and send the move to your device. Lets take a look at what information is in the entry.

“type” is a 1 or zero to tell you if this move is part of a line or arc.

Cx,cy,cz are the center corrdinates if this is an arc.

Ex,ey,ez,ea,eb,ec are the end points of this move in machine coordinates.

Sx,sy,syz… are the start points of the move.

Time is the time of the move in ms. These moves will all be 1-64ms long depending on the move. No move will be longer than 64ms. Since the time of the move is in the structure, acceleration has already been taken care of. Same with velocity. The velocity will be the change in position over time, and the acceleration is built in by the change in velocity from one move to the next. How you deal with this will depend on the hardware.

The DDA1,2 and 3 variables are specific to the G100, but can be used by other hardware. They are a “Differential Data Derivative” of a cubic move. In the case of the G100, only cubics are sent as moves, even if only a straight line. A DDA is a way of making a frequency based axis move in a straight line or a curve. They contain speed data over time with kick and jerk information to create a curved move. These DDA’s are computed froma fast Bezier curve routine to best approximate the move requested. DDA1,DDA2 and DDA3 are computed for every move. The way they work is a bit complex (or simple depending on the reader.  )

Take a move like:

DDA1 = 10000
DDA2 = 5
DDD3 = -1
Time = 7

This would create a curve. DDA1 is the initial velocity to be put out in the move in the first 1ms of movement. Each ms of movement that occurs, DDA2 is added to that velocity AND DDA3 is added to DDA2. So during the 5ms of this commanded move:

Time in ms FrequencyVariable DDA2 DDA3

1 10000 5 -2
2 10005 3 -2
3 10008 1 -2
4 10009 -1 -2
5 10008 -3 -2
6 10005 -5 -2
7 10000 -7 -2

So as you can see in this 7ms movement, the speed has gone up and down in ms increments. And it's done all in the hardware with no intervention by Mach3. This allows a sub acceleration of 1ms control. Having two axes (or more) vary their speed is in essence a circular arc movement. The DDA’s are computed to ensure the movement is always a circular arc (though ellipsoids and such would be possible).

More information is available on the DDA’s in the file G200x.h which is the header file for the G100 firmware. Here is a brief explanation from that file:

/* This segment is intended for efficient generation of arcs and curved
motion. The math is simple: at each iteration (1024Hz rate) the
following operations are performed in sequence:
<current velocity> = dda1
dda1 += dda2
dda2 += dda3
At T=0, all ddas are set to the value in this message.
After T iterations of this algorithm,
<pos> = <start pos> + dda3*T*(T-1)*(T-2)/6 + dda2*T*(T-1)/2 + dda1*T
dda1 = dda3*T*(T-1)/2 + dda2*T + dda1
dda2 = dda3*T + dda2
dda3 = <unchanged>
where the right hand side dda's are the initial values.
Linear motion (with dda2=dda3=0) may run for 65536 iterations (the max) with
no loss of accuracy. Parabolic motion (dda3=0, dda2 != 0) may also run
for this many iterations. General cubic motion may run for about 4096
iterations, after which there may be some rounding error. (Rounding
error is defined as more than 1/2 an output step.)

Your planner does not need to use DDA’s, though the information is there if you care to and it matches your hardware. You can just use the 64ms movement coordinates just as easily. Since there are up to 2048 entries in the buffer, there is up to 131 seonds of movement that could be sent to buffer up the device, but at the moment, I create only a maximum of 2 seconds worth at any time, so its important to keep calling the DoGCode routine (or whatever yours is called) in order to keep your device buffer full.

Once you use a ring buffer element, increment the Index pointer with: <tt>Engine->TrajIndex++;
Engine->TrajIndex &= 0xfff; </tt>

This keeps it synced to the next move available and informs mach3 in its 10hz loop to add more data if it needs to.

== Summary==

So to control a plugin, you need to interface only a few functions: Jog, GCode movment when data appears, and I/O. Reading the G100 plugin will show you various variables used for syncing, or developing positional data that Mach3 needs as feedback. Check and read the message translators in Decoders.cpp to see how each of the incoming messages deals with updating Mach3 as to what has been set in inputs, what the current position is for the engine, and other semaphores used. When you see a line like <tt>TajectoryControl-></tt> or <tt>_setup-></tt> or <tt>Engine-></tt>, these are calls back to Mach3’s variables to tell Mach3 whats going on. There are not many of them though; most operations are autonomous. Mach3 runs, sets movements in the buffers and calls <tt>JogOn</tt> and <tt>JogOff</tt> when appropriate. You need only to make the moves happen, and tell Mach3 what you did.

You will undoubtedly have questions as you go. The G100 source code is the best place to see how I handled various situations, such as homing and such, but feel free to email me your questions as they arise and please edit this wiki article to clarify any point that you eventually understand.

Art Fenerty (PlugIn author)
Artsoft Inc.

Initial text put into wiki format (without adding too many errors, I hope) by John Prentice

Introduction

JAPrenticeUK — Tue, 08 Aug 2006 08:19:46 GMT

Summary:

To be provided - Anyone volunteer?

Mach3 Plugins

JAPrenticeUK — Tue, 08 Aug 2006 08:19:00 GMT

Summary:

This chapter is to document available "model" plugins and the techniques used in writing them.

Most of the articles in here will assume that you are a C++ programmer. If you are not then you need to look for a plugin already developed to suit your needs. The Yahoo! group and/or Mach Forum would be a good place to start.

#[[Introduction]]
#[[Index of Plugins that have been developed]]
#[[The G100/GREX plugin as a model for device control]]
#[[Plugin Documentation]]

Index of Plugins that have been developed

JAPrenticeUK — Fri, 02 Jun 2006 08:45:48 GMT

Summary:

This list may be of use to identify Mach3 Plugins as they are released and to minimise duplication of DLL file names.

Authors are encouraged to add their own entries (You jneed a username to login to the wiki and go to the Edit tab). I know that the markup language for wiki tables is a bit nasty but if you can code MFC dialogs then you can probably have enough "greycells" to work it out

Users are encouraged to try the Plugins on the understanding that the terms under which they are contributed are solely the responsibility of the creator - some will be free, some licensed, some will be Alpha, some well tested and supported products. This list is not moderated or approved by any person or organisation. We hope it is useful but you use it at your own risk - a CNC machine can turn man-eating if badly treated.

{|border="1" cellpadding = "2"
!width="20"|DLL name
!width="50"|Function
!width="24"|Author
!width="12"|Status
!width="64"|Link
|-
|BlankDevice.dll||A skeleton set of code||ArtSoft||Stable||[http://www.machsupport.com/downloads.php In SDK release]
|-
|JoyStick.dll||A Windows joystick jog controller||Artsoft||Beta||[http://www.machsupport.com/downloads.php In SDK release]
|-
|JoyStick.dll||A variant on Art's joystick||Junior||Beta||[http://www.machsupport.com/forum/ in Forum]
|-
|ModIO-1.dll||Support for ModIO as IO device||[mailto::john@castlewd.freeserve.co.uk japrentice]||Design||not avail.
|-
|ARCNC100.dll||ARCNC100 Controller||[http://atelierrobin.net atelierrobin.net]||Development||not avail.
|}

SDK Variables

Art Fenerty — Tue, 30 May 2006 00:01:25 GMT

Summary:

Following is a list of brief explanations of the contents of the ENGINE block variable in the Mach3 SDK.

The Engine-> variable contains all the variables used to communicate with the Ring0 driver
which does all the work with Printer ports. In addition, this block of variables is used for
simulation modes, and to create a standard point of reference even for non-printer port modes
such as the G100 operating mode. When no driver is loaded, the program applies various algorithms
to this data to create a runtime simulation of the printer port running. This Block then may be
considered as a very important one in Mach3, and is responsible for a great deal of its Driver functionallity.

First, we have some structures, (All this information can be found in the "Engine.h" file, but this Wiki entry will
attempt to better document them. Users are invited to add annotations to qualify their use, or point out limitations
to their use as they are discovered.

This structure is used for all output signals. Not only printer port, but ModIO and G100, just with different port numbers typically.

'''NOTE:''' The structures are also documented (in a different fashion and slightly differently) in [[Engine.h]]. This page is older than the [[Engine.h]] page.

struct OutputInfo
{
bool active; // Is this output Active (Enabled) or Not?
char OutPin; // What Pin? Any number from 0 -255
char OutPort; // What port, again any number from 0 - 255, BUT the
// printer driver will ignore any inappropriate to the
// printer port.
bool Negated; // Low Active or High Active. Expectation of the voltage
// level to trigger the following boolean..
bool Activated; // True when the voltage level equals the above setting.
};

// input signal structure
struct InputInfo
{
bool Active; // signal active?
char InPin; // which Pin
char InPort; // which Port
bool Negated;
int ReqState; // Required State on Activation (Not used at present.,
// may be used by a PlugIn at will.
bool Activated; // Set by the pinter driver (Or ModIO, or G100)
// to indicate an input is seen matching conditions.
bool Emulated; // If True, then the emulation key will trigger an
// Activated condition..
int EmulationKey;
};

// encoder inputs
//
// Following is set by G100, or printer port, as well as ModIO sections
// to set condition for the encoder.
// Only the printer drivers will use anything other than count[0] which is total encoder
// count.
//
struct Encoder
{
bool Active; // is the encoder turned on?
int APin; // A Pin designations
int BPin; // B Pin designations
int APort; // A Pin Ports
int BPort; // B Pin Ports
bool LastStateA;
bool LastStateB; // storage for the last known state
int Count[2]; // Index counts for each encoder
int Memory[16]; // Unused. Free for plugins.
int ActiveMemory;
int Color; // Unusaed. May be used by Plugins.
};

// axis information structure, 7 axis, 7th is spindle..
struct AxisInfo
{
int Index; // Current Count
int MasterIndex;
char StepPin; // Pin for step pulse
char DirPin; // Pin for Direction Pulse
char StepPort; // Port # for step
char DirPort; // Port # for Direction
bool StepNegate; // low active step?
bool DirNegate; // low active Direction?
int CurVelocity; // Current Velocity
int MaxVelocity; // Current Max Velocity (jogging )
int MasterVelocity; // Master Velocity...Maximum Velocity in all circumstances.
int Acceleration; // Acceleration
bool AtSpeed; // At Speed Currently
bool Acc; // Accelerating?
bool Dec; // Decelerating?
bool Enable; // Axis Enabled?
bool Jogging; // Jogging On?
int JoggDir; // Direction of Jog;
bool Homing; // is this a homing jog?
bool DeRef; // Dereferanceing Move? (move off switch)
int Memory[6]; // 6 memory variables, unused. May be used for plugins..
int ActiveMemory; //index for memories. Unused.
int Color;
int TripCount;
int DepthCount;
bool Probing;
bool Slave;
int SlaveAxis;
};

struct TrajPoint
{
int Points[6];
int Command;
int ID;
char shifter[6];
};

struct TrajBuffer{
TrajPoint Trajectories[0x1000];
int TrajIndex; // Trajectory buffer current Index
int TrajHead; // Trajectory buffer Fill point
int uSecStep; // clock count for step signal
int uSecDir; // clock count for pre-raising the direction bit;
double LastCommandPos[6]; // End position as of last movement.
bool Configured; // Engine is now configured.
bool Busy; // Not used.
bool Idle; // Not used.
bool Emergency; // Emergency Condition..this is not Estop..do not use.
bool Jogging; // One of the axis is jogging..
bool IncrementalJog; // Incremental Jog..
bool Sync; // If set to true, the system will resync
// the planner and the interpeter positions.
bool Port1On;
bool Port2On;
bool Tuning;
bool ReconfigHotKeys; // Unused.
short Port1Address;
short Port2Address;

AxisInfo Axis[7]; // axis information
InputInfo InSigs[nSigs]; // input signals
OutputInfo OutSigs[nSigsOut]; // output signals
Encoder Encoders[7]; // encoder inputs
int LastCubics[6]; // Used by the printer port for position
// calculations vs printer port pins.

// WatchDogs
int WDInt0; // internal watchdog.
int WDInt8; // second internal watchdog.
int WD2Way; // application to Driver watchdog,
// bi directionally used.
int StartClocks; //timing checking var's..
int EndClocks;
bool ReadClocks;
bool Sampleing; // Sampleing flag
bool CubicDrain; // cubicDrain flag. Sets cubics to zero;
bool EStop; // Estop condition in effect.

// software limits
int XLimitPos,YLimitPos,ZLimitPos,ALimitPos,BLimitPos,CLimitPos;
int XLimitNeg,YLimitNeg,ZLimitNeg,ALimitNeg,BLimitNeg,CLimitNeg;
int StatHolders[6];
int StatLast[6];
bool StatBusy; // engine busy doign statistics for oscilliscope
// readings.. DO not use.. Internal.
int StatCount;
bool SyncError; // Do not use.
int DwellTime; // If set, the system will delay all movement
// and processing by this amount of tick.
// (G04Pxxx) sets this.
int CurrentUnits; // mm's or inches..
bool Directions[7]; // Reverses Motor directions
bool Safe;

// G-Code vars
int State; // STOP, PAUSE, RUN....
bool NoTime;
int DisplayLine;
int CurrentLineExec;
bool Loaded;
int SpindleCW;
int SpindleCCW;
bool Jpg;
double oSpinSeconds;
bool SpinDelayReq;
int Flood;
int Mist;
bool Hpgl;
bool NoSpindle;
bool NoFlood;
bool Pro;
bool Dxf;
bool Referenced[ 6 ];
bool HomeSpeed[ 6 ];
unsigned long TargetTime;
int BackCounts[ 6 ];
int BackSpeeds[ 6 ];
bool BackState[6];
bool BackLast[6];
bool BackOn;
bool AutoZero[6];
double ToolChangePos[6];
int LastState;
int LookAhead;
int Year;
int LastExec;
int DROUpdate;
bool WatchDogOn;
bool LimitsOff;
bool Simulate;
int Month;
int KeyAction;
bool JoyOn;
unsigned __int64 WaitCondition;
int EStopReason;
bool PWM;
int PWMFreq;
int Day;
int oCurrentPulley; //remove this
int oldMaxSpeeds[4]; //and this. .
int m_SetExec;
bool AutoHome;
int templookahead;
bool Homing;
char CircData[201];
bool CircLoaded;
bool DROMaster;
int SoftLimitsHi[6];
int SoftLimitsLo[6];
bool SoftDir[3];
bool SoftLimitEnable;
bool SoftLimitTriggered;
bool HotStart;
bool LCD;
int OverRide;
bool Follow;
int NewWindow;
bool Deselect;
bool DeSelectClick;
bool SelectClick;
int PWMBaseFrequency;
int PulseCount;
//
int THCCorrection;
int THCMaxCor;
int THCMinCor;
bool THCOn;
int THCAdder;
bool THCZero;
//
int PPS;
int RefCounts[6];
int CurrentSpindleCount;
int IntsPerRotation;
bool SpinDec;
bool SpinAcc;
long WorstCase;
int VerifyChecks[6];
int Verifys[6];
int THCDev;
int Debounce;
//
bool WaitForTrigger;
int nTrigger;
int PumpTime;
int MaxSpinCounts;
bool Threading;
int NormSpinCounts;
int SpinCorrection;
int SpinAdder;
int SpinDebounce;
//
int SPIDataPin;
int SPIClockPin;
int DataOutPort;
int DataOutByte;
bool DataOutDone;
int DataInPort;
int DataInByte;
bool DataInDone;
bool LaserTrigger;
int Counter;
bool SPIOn;
int SPIDataOut;
int SPIDataIn;
bool SPIDone;
bool SPIhidata;
//
bool OffLine;
int SpinStability;
char BitTest;
//
int CurRate;
int PlungeLimit;
bool NoPlunge; //THC No plunge control
bool SpindleStable;
short nSlots;
//
bool LaserMode;
bool MaxNCMode;
int MaxNCLag;
bool SlowMode;
bool MaxNC10;
bool Port2Input;
bool ChargeAlwaysOn;
bool RaiseLower;
unsigned int RawInputs;
bool HalfPulse;
bool Shuttle;
int ShuttleCurVel; // Current Velocity
int ShuttleMaxVel; // Current Max Velocity (jogging )
int ShuttleAccel;
int LaserX;
int LaserY;
int LaserZ;
int LaserXOff;
int LaserYOff;
int LaserZOff;
bool HoldInput1;
int Pierce;
};

struct TimeData{
int Time[32000];
};

Macropump for Galesburg Mill

JAPrenticeUK — Fri, 12 May 2006 11:06:52 GMT

Summary:

Option Explicit
' Macropump for demo panel and Mill

Const slave = 1 ' **** Change this if you use another ModBus Slave address

Dim swT1 as Boolean ' toggle 1 true is Down
Dim swT2 as Boolean ' toggle 2 true is down
Dim swR1 as Integer ' Rotary 1 three positions 1, 2 and 3
Dim swR2 as Integer ' Rotary 2 four positions 1, 2, 3 and 4

Dim CurrScreen as Integer
Const scrProgRun = 1
Const scrOffsets = 7
Const scrMDI = 2
Const scrDiags = 5

Const FeedHolding = 1244 ' LED shows Had one red button press
Const OUTBASE = OUTPUT7 - 1

' =============================================================
Sub Main ()

Preamble
GetConsistent
DecodeSwitches
ActionSwitches
ReadButtons
SetFRO
WriteDisplays

End Sub 'Main

'=================================================================
' Action functions to implement changes
' ================================================================

Sub ButtonDown (nButt as Integer)
' Called when a button is pressed. nButt says which

If nButt = 1 Then ' Green buttons
If CurrScreen = scrProgRun OR CurrScreen = scrDiags Then
DoButton 0 ' Cycle Start **** 033
ElseIf CurrScreen = scrMDI Then ' we are going to deal with the spindle
If GetOEMLED (11)= 0 Then ' Spindle is stopped
Code "M3"
End If
End If ' different screen actions
End If ' Button 0

If nButt = 3 Then ' Red button
If CurrScreen = scrProgRun OR CurrScreen = scrDiags Then
If GetUserLED (FeedHolding) Then
SetUserLED FeedHolding, 0 ' now in stop state
DeActivateSignal (OUTBASE + 3)
DoButton 3 ' **** 033
Else
If GetLed (4) Then ' its running
SetUserLED Feedholding, 1 ' now in Hold state
ActivateSignal (OUTBASE + 3)
DoButton 1 ' **** 033
End If ' was running
End If ' whatever state we were in
ElseIf CurrScreen = scrMDI Then ' we are going to deal with the spindle
If GetOEMLED (11)<>0 Then ' Spindle is running
Code "M5"
End If
End If ' different screen actions
End If ' Button 3

End Sub 'ButtonDown

' ------------------------------------------------------------------

Sub ButtonUp (nButt as Integer)
' Called when a button is released. nButt says which
' Probably not much use but here in case

End Sub 'ButtonUp

'+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Sub swT1ChangedTo (ison as Boolean)
' Toggle switch 1 changed

Message "Toggle 1 changed"

End Sub ' swUpdated

'-----------------------------------------------------------------------

Sub swT2ChangedTo (ison as Boolean)
' Toggle swich 2 changed

If GetOEMLED (106) <> 0 AND ison = 0 Then ' need to toggle
DoOEMButton (284) ' toggle Shuttle
End If

If GetOEMLED (106) = 0 AND ison <> 0 Then ' need to toggle
DoOEMButton (284) ' toggle Shuttle
End If

End Sub ' swUpdated

'-----------------------------------------------------------------------

Sub swR1ChangedTo (posn as Integer)
' Rotary 1 changed

Message "Tool number " & posn
SetDRO 24, posn

End Sub ' swUpdated

'-----------------------------------------------------------------------

Sub swR2ChangedTo (posn as Integer)
' Rotary 2 changed To set Axis to Jog

Dim iCount as Integer

If GetOEMLed (97 + posn) = 0 Then ' not on the right axis
For iCount = 1 to 6 ' 6 times bound to be enough if it is ever going to happen
If GetOEMLED (97 + posn) = 0 Then
DoOEMButton 281 ' toggle the button until it comes good
End If
Next iCount
End If

' now a bodge as MPG1 axis gets changed out of the blue needs to be C to disable

If GetOEMLed (64) = 0 Then ' not on the C axis
For iCount = 1 to 6 ' 6 times bound to be enough if it is ever going to happen
If GetOEMLED (64) = 0 Then
DoOEMButton 175 ' toggle the button until it comes good
End If
Next iCount
End If

End Sub ' swUpdated

' =====================================================================

Sub Preamble ()
' Do the interesting things to setup data here

CurrScreen = GetPage ()

End Sub ' Preamble

' -------------------------------------------------------------------

Sub GetConsistent ()
' Here we see if user has done anthing funng (e.g. with screen buttons)
' that invalidates the state we think we are in.

End Sub ' GetConsistent

'----------------------------------------------------------------------

Sub WriteDisplays ()
' Here we write to the LCD and real LEDs reflecting the state things are in

Dim strText as String

Dim strLabB1 as String ' label for button 1
Dim strLabB2 as String ' label for button 2
Dim strLabB3 as String ' label for button 3

strLabB2 = " " ' not currently used

If GetOEMLED (106) Then ' Shuttle is ON
ActivateSignal OUTBASE + 5
Else
DeActivateSignal OUTBASE + 5
End If ' displaying the Shuttle State

If GetLED (6) Then ' Tool change request
ActivateSignal OUTBASE + 1
ActivateSignal OUTBASE + 4 ' flash LEDs 1 and 4
Else
DeActivateSignal OUTBASE + 1
DeActivateSignal OUTBASE + 4
End If ' displaying the Tool Change LED

Select Case CurrScreen ' put out the heading line
Case = scrProgRun
strText = " Program Run "
strLabB1 = "Run "
If GetLed (4) <> 0 Then ' its running so we might pause
strLabB3 = "Hold"
ElseIf GetLED (6) Then ' Toolchange request
strLabB1 = "Tool"
strLabB3 = " "
Else
If GetOEMLed (11) <> 0 Then ' spindle is running so we must be paused
strLabB3 = "Stop"
Else
strLabB3 = " "
End If
End If ' dealing with the button 3 label
If GetLed (5) = 0 Then ' we are not paused
DeActivateSignal (OUTBASE + 3) ' don't flash the LED
Else
ActivateSignal (OUTBASE + 3) ' flash the LED 3
End If

Case = scrOffsets
strText = " Offsets "
strLabB1 = " "
strLabB3 = " "

Case = scrMDI
strText = " MDI "
strLabB1 = "Spin"
strLabB3 = "Stop"

Case = scrDiags
strText = " Diagnostics "
StrLabB1 = "Run "
Case Else
strText = " " 'unknown screen
End Select

strText = strText & " "
strText = strText & " "
strText = strText + strLabB1 & " " & strLabB2 & " " & strLabB3 _
& " " & strLabB1
SetModIOString slave, 0, 0, strText ' write it

End Sub ' Write displays

'---------------------------------------------------------------------------

Sub ReadButtons ()
' Looks at the inputs for transitions and calls the ButtonDown routine if Transition

Rem could be a loop but I hope this code is clearer

If IsActive (INPUT1) Then
If GetUserLED (1241) = 0 Then ' It is a new press
SetUserLED 1241, 1
ButtonDown 1
End if ' dealing with new press
Else ' button is up
If GetUserLED (1241) <> 0 Then ' It is new unpress
SetUserLED 1241, 0
ButtonUp 1
End if ' dealing with new press
End IF ' button 1 processing

If IsActive (INPUT2) Then
If GetUserLED (1242) = 0 Then ' It is a new press
SetUserLED 1242, 1
ButtonDown 2
End if ' dealing with new press
Else ' button is up
If GetUserLED (1242) <> 0 Then ' It is new unpress
SetUserLED 1242, 0
ButtonUp 2
End if ' dealing with new press
End IF ' button 2 processing

If IsActive (INPUT3) Then
If GetUserLED (1243) = 0 Then ' It is a new press
SetUserLED 1243, 1
ButtonDown 3
End if ' dealing with new press
Else ' button is up
If GetUserLED (1243) <> 0 Then ' It is new unpress
SetUserLED 1243, 0
ButtonUp 3
End if ' dealing with new press
End IF ' button 3 processing

End Sub ' ReadButtons

'-----------------------------------------------------------------

Sub SetFRO ()
' Does simple analog read and straight to DRO

Dim fro as Integer

fro = GetInput (64) ' read Analog1
setUserDRO 1253, fro
fro = (fro * 95.0)/1024.0
setDRO 21, fro+5 ' range is now 5 to 100%

End Sub ' SetFRO

' ----------------------------------------------------------------------

Sub DecodeSwitches ()

' This routine takes the analog ports and sets up the switch states from them

Dim ana as Integer

ana = GetInput(65) 'analog Input 2 On ModIO
Select Case ana
Case < 100
swT1 = True
swR1 = 1
Case < 340
swT1 = True
swR1 = 2
Case < 510
swT1 = True
swR1 = 3
Case < 690
swT1 = False
swR1 = 1
Case < 910
swT1 = False
swR1 = 2
Case >= 910
swT1 = False
swR1 = 3
End Select

ana = GetInput(66) 'analog Input 3 On ModIO
Select Case ana
Case < 68
swT2 = True
swR2 = 1
Case < 212
swT2 = True
swR2 = 2
Case < 340
swT2 = True
swR2 = 3
Case < 511
swT2 = True
swR2 = 4
Case < 684
swT2 = False
swR2 = 1
Case < 819
swT2 = False
swR2 = 2
Case < 954
swT2 = False
swR2 = 3
Case >= 954
swT2 = False
swR2 = 4
End Select

End Sub ' DecodeSwitches

' -------------------------------------------------------------------------

Sub ActionSwitches ()
' This routine displays switch states on Diags page and
' calls the Action routines if they have been changed

If GetUserLED (1251) = 0 Then ' previously T1 was OFF
If swT1 Then
SetUserLED 1251, 1
swT1ChangedTo TRUE
End If
Else ' T1 was ON
If swT1 = 0 Then
SetUserLED 1251, 0
swT1ChangedTo FALSE
End If
End If
If GetUserDRO (1251) <> swR1 Then ' change in rotary 1 position
SetUserDRO 1251, swR1
swR1ChangedTo swR1
End If

If GetUserLED (1252) = 0 Then ' previously T2 was OFF
If swT2 Then
SetUserLED 1252, 1
swT2ChangedTo TRUE
End If
Else ' T2 was ON
If swT2 = 0 Then
SetUserLED 1252, 0
swT2ChangedTo FALSE
End If
End If
If GetUserDRO (1252) <> swR2 Then ' change in rotary 2 position
SetUserDRO 1252, swR2
swR2ChangedTo swR2
End If

End Sub ' ActionSwitches

' ---------------------------------------------------------------

Macropump for Galesburg Lathe

JAPrenticeUK — Fri, 12 May 2006 11:05:05 GMT

Summary:

Option Explicit
' Macropump for demo panel and Turn

Const slave = 1 ' **** Change this if you use another ModBus Slave address

Dim swT1 as Boolean ' toggle 1 true is Down
Dim swT2 as Boolean ' toggle 2 true is down
Dim swR1 as Integer ' Rotary 1 three positions 1, 2 and 3
Dim swR2 as Integer ' Rotary 2 four positions 1, 2, 3 and 4

Dim CurrScreen as Integer
Const scrProgRun = 1
Const scrOffsets = 2
Const scrVisiCycle = 10
Const scrDiags = 5

Const FeedHolding = 1244 ' LED shows Had one red button press
Const OUTBASE = OUTPUT7 - 1

' =============================================================
Sub Main ()

Preamble
GetConsistent
DecodeSwitches
ActionSwitches
ReadButtons
SetFRO
WriteDisplays

End Sub 'Main

'=================================================================
' Action functions to implement changes
' ================================================================

Sub ButtonDown (nButt as Integer)
' Called when a button is pressed. nButt says which

If nButt = 1 Then ' Green buttons
If CurrScreen = scrProgRun OR CurrScreen = scrDiags Then
DoButton 0 ' Cycle Start **** 033
ElseIf CurrScreen = scrVisiCycle Then ' we are going to deal with the spindle
If GetOEMLED (11)= 0 Then ' Spindle is stopped
Code "M3"
End If
End If ' different screen actions
End If ' Button 0

If nButt = 3 Then ' Red button
If CurrScreen = scrProgRun OR CurrScreen = scrDiags Then
If GetUserLED (FeedHolding) Then
SetUserLED FeedHolding, 0 ' now in stop state
DeActivateSignal (OUTBASE + 3)
DoButton 3 ' **** 033
Else
If GetLed (4) Then ' its running
SetUserLED Feedholding, 1 ' now in Hold state
ActivateSignal (OUTBASE + 3)
DoButton 1 ' **** 033
End If ' was running
End If ' whatever state we were in
ElseIf CurrScreen = scrVisiCycle Then ' we are going to deal with the spindle
If GetOEMLED (11)<>0 Then ' Spindle is running
Code "M5"
End If
End If ' different screen actions
End If ' Button 3

End Sub 'ButtonDown

' ------------------------------------------------------------------

Sub ButtonUp (nButt as Integer)
' Called when a button is released. nButt says which
' Probably not much use but here in case

End Sub 'ButtonUp

'+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Sub swT1ChangedTo (ison as Boolean)
' Toggle switch 1 changed

Message "Toggle 1 changed"

End Sub ' swUpdated

'-----------------------------------------------------------------------

Sub swT2ChangedTo (ison as Boolean)
' Toggle swich 2 changed

If GetOEMLED (83) <> 0 AND ison = 0 Then ' need to toggle
DoOEMButton (103) ' toggle jog state
End If

If GetOEMLED (83) = 0 AND ison <> 0 Then ' need to toggle
DoOEMButton (103) ' toggle jog state
End If

End Sub ' swUpdated

'-----------------------------------------------------------------------

Sub swR1ChangedTo (posn as Integer)
' Rotary 1 changed

Const nOps = 3
Const OpLEDBase = 1110

Dim i as Integer
Dim iOp as Integer

For i = 1 to nOps
SetUserLED OpLEDBase + i -1, 0 ' clear the LEDs
Next i

Message "Operation number" & posn
SetUserDRO 1104, posn

SetUserLED opLEDBase + posn - 1, 1 ' light the chosen LED

End Sub ' swUpdated

'-----------------------------------------------------------------------

Sub swR2ChangedTo (posn as Integer)
' Rotary 2 changed

Message "Tool number" & posn
SetDRO 24, posn

End Sub ' swUpdated

' =====================================================================

Sub Preamble ()
' Do the interesting things to setup data here

CurrScreen = GetPage ()

End Sub ' Preamble

' -------------------------------------------------------------------

Sub GetConsistent ()
' Here we see if user has done anthing funng (e.g. with screen buttons)
' that invalidates the state we think we are in.

End Sub ' GetConsistent

'----------------------------------------------------------------------

Sub WriteDisplays ()
' Here we write to the LCD and real LEDs reflecting the state things are in

Dim strText as String

Dim strLabB1 as String ' label for button 1
Dim strLabB2 as String ' label for button 2
Dim strLabB3 as String ' label for button 3

strLabB2 = " " ' not currently used

If GetOEMLED (83) Then ' Jog is allowed
ActivateSignal OUTBASE + 5
Else
DeActivateSignal OUTBASE + 5
End If ' displaying the Jog State

Select Case CurrScreen ' put out the heading line
Case = scrProgRun
strText = " Program Run "
strLabB1 = "Run "
If GetLed (4) <> 0 Then ' its running so we might pause
strLabB3 = "Hold"
Else
If GetOEMLed (11) <> 0 Then ' spindle is running so it must be paused
strLabB3 = "Stop"
Else
strLabB3 = " "
End If
End If ' dealing with the button 3 label
If GetLed (5) = 0 Then ' we are not paused
DeActivateSignal (OUTBASE + 3) ' don't flash the LED
Else
ActivateSignal (OUTBASE + 3) ' flash the LED 3
End If

Case = scrOffsets
strText = " Offsets "
strLabB1 = " "
strLabB3 = " "

Case = scrVisiCycle
strText = " VisiCycle "
strLabB1 = "Spin"
strLabB3 = "Stop"

Case = scrDiags
strText = " Diagnostics "
StrLabB1 = "Run "
Case Else
strText = " " 'unknown screen
End Select

strText = strText & " "
strText = strText & " "
strText = strText + strLabB1 & " " & strLabB2 & " " & strLabB3 _
& " " & strLabB1
SetModIOString slave, 0, 0, strText ' write it

End Sub ' Write displays

'---------------------------------------------------------------------------

Sub ReadButtons ()
' Looks at the inputs for transitions and calls the ButtonDown routine if Transition

Rem could be a loop but I hope this code is clearer

If IsActive (INPUT1) Then
If GetUserLED (1241) = 0 Then ' It is a new press
SetUserLED 1241, 1
ButtonDown 1
End if ' dealing with new press
Else ' button is up
If GetUserLED (1241) <> 0 Then ' It is new unpress
SetUserLED 1241, 0
ButtonUp 1
End if ' dealing with new press
End IF ' button 1 processing

If IsActive (INPUT2) Then
If GetUserLED (1242) = 0 Then ' It is a new press
SetUserLED 1242, 1
ButtonDown 2
End if ' dealing with new press
Else ' button is up
If GetUserLED (1242) <> 0 Then ' It is new unpress
SetUserLED 1242, 0
ButtonUp 2
End if ' dealing with new press
End IF ' button 2 processing

If IsActive (INPUT3) Then
If GetUserLED (1243) = 0 Then ' It is a new press
SetUserLED 1243, 1
ButtonDown 3
End if ' dealing with new press
Else ' button is up
If GetUserLED (1243) <> 0 Then ' It is new unpress
SetUserLED 1243, 0
ButtonUp 3
End if ' dealing with new press
End IF ' button 3 processing

End Sub ' ReadButtons

'-----------------------------------------------------------------

Sub SetFRO ()
' Does simple analog read and straight to DRO

Dim fro as Integer

fro = GetInput (64) ' read Analog1
setUserDRO 1253, fro
fro = (fro * 95.0)/1024.0
setDRO 21, fro+5 ' range is now 5 to 100%

End Sub ' SetFRO

' ----------------------------------------------------------------------

Sub DecodeSwitches ()

' This routine takes the analog ports and sets up the switch states from them

Dim ana as Integer

ana = GetInput(65) 'analog Input 2 On ModIO
Select Case ana
Case < 100
swT1 = True
swR1 = 1
Case < 340
swT1 = True
swR1 = 2
Case < 510
swT1 = True
swR1 = 3
Case < 690
swT1 = False
swR1 = 1
Case < 910
swT1 = False
swR1 = 2
Case >= 910
swT1 = False
swR1 = 3
End Select

ana = GetInput(66) 'analog Input 3 On ModIO
Select Case ana
Case < 68
swT2 = True
swR2 = 1
Case < 212
swT2 = True
swR2 = 2
Case < 340
swT2 = True
swR2 = 3
Case < 511
swT2 = True
swR2 = 4
Case < 684
swT2 = False
swR2 = 1
Case < 819
swT2 = False
swR2 = 2
Case < 954
swT2 = False
swR2 = 3
Case >= 954
swT2 = False
swR2 = 4
End Select

End Sub ' DecodeSwitches

' -------------------------------------------------------------------------

Sub ActionSwitches ()
' This routine displays switch states on Diags page and
' calls the Action routines if they have been changed

If GetUserLED (1251) = 0 Then ' previously T1 was OFF
If swT1 Then
SetUserLED 1251, 1
swT1ChangedTo TRUE
End If
Else ' T1 was ON
If swT1 = 0 Then
SetUserLED 1251, 0
swT1ChangedTo FALSE
End If
End If
If GetUserDRO (1251) <> swR1 Then ' change in rotary 1 position
SetUserDRO 1251, swR1
swR1ChangedTo swR1
End If

If GetUserLED (1252) = 0 Then ' previously T2 was OFF
If swT2 Then
SetUserLED 1252, 1
swT2ChangedTo TRUE
End If
Else ' T2 was ON
If swT2 = 0 Then
SetUserLED 1252, 0
swT2ChangedTo FALSE
End If
End If
If GetUserDRO (1252) <> swR2 Then ' change in rotary 2 position
SetUserDRO 1252, swR2
swR2ChangedTo swR2
End If

End Sub ' ActionSwitches

' ---------------------------------------------------------------

Universal panel notes for CNC Workshop 2006

JAPrenticeUK — Fri, 12 May 2006 09:34:53 GMT

Summary:

'''This page is notes for people wanting to use John Prentice's design for a ModIO based control panel.'''

An example of a panel I made to take to Galesburg is shown below

[[Image:External2LoRes.jpg]]

== Why is it like it is? ==

The "design process" of this was unconventional in that I started with the case from a skip (dumpster) which had held a small chart recorder. It looked about the right size to pack for an Atlantic flight but still have space for controls. Thus the controls on it are there to use the holes already in the case and some of the switches etc. This seemed ligitimate as I did not have a specific machine to control - I just wanted to show what sort of things you can do. So what do we have:

* Two MPGs - one has clicks the other is "smooth"
* An EStop switch
* Four push buttons
* The ModIO LCD panel
* A rotary potentiometer
* Two toggle switches
* Two rotary switches
* Five LEDs (four in buttons and one freestanding)

== Details of the controls ==

=== MPGs ===

These are conventional Nemicon 100 cpr MPGs. I turned the detents off the internal wheel of one of them as I like smooth operation on a lathe X axis and you might find it interesting to try both clicky and smooth.

=== The E-Stop switch ===

This is connected to ModIO input DIn3 and has a separate NC contact presented on a DIN connector on the back panel. We will not use this at Galesburg.

=== Push switches ===

The two "green" switches are wired in series to ModIO input DIn0 - the intention is to make a two handed, or at least two fingered, "Start" button

The yellow switch is on DIn1 and the red switch on DIn2

Thus all ModIO inputs are used (four being required for the MPGs)

Each push button has a LED allocated to DOut0 - DOut3 (left to right, Green, Yellow, Red, Green). These are configured in the ModIO to flash.

=== ModIO LCD ===

This is positioned so the push buttons can be "soft labelled" by it if desired. Ot is 4 rows of 20 alphanumeric characters.

=== Rotary potentiometer ===

This is connected to Analog In1. It is envisaged that it well be an overrid control (Feed)

=== Toggle and rotary switches ===

The left toggle switch and left rotary (switches A) are connected to Analog In2. The right switches (B) are connected to Analog In3. The position of these switches is one of the recorder case legacies!

These switches are turned into "digital" positions (on/off and 1, 2, 3, etc.) by the Mach3 Macropump script. The use of analog signals allows the equivalent of 9 inputs to be used with only two wires and in a situation where all the DIn pins are already in use.

The circuit to do this is as follows.

[[Image:RandTSwPot.JPG]]

This shows the circuit for switches B.

The theory is as follows:

* Each pole of the rotary switch taps off a potential divider (1K5 resistors). If the toggle switch is down (ON in UK conventions!) then a 6K8 resistor is at the top of the divider chain. When switched up the 6K8 is moved to the bottom.
* As you will realize the current in the divider is always the same so the voltage steps from the rotary switch are the same. When the toggle is up the voltage is offset by about 5 steps thus giving a total of 8 different but more or less equal values for the combinations of settings of the two switches.
* As measured the analog inputs are:

Switch A, Toggle Down - 0, 222, 450, Toggle Up - 578, 788, 1022 and

Switch B, Toggle Down - 0, 136, 272, 408, Toggle Up - 615, 753, 881, 1022

Clearly the software needs to detect mid way between these values to get immunity from noise etc. A subroutine is already written to turn the values into separate switch settings.

== Software architecture ==

I will not write about this in too muche detail - to understand it you will have to read the code. However here are a few notes on the principles.

=== Macropump ===

The Macropump macro is run by Mach3 roughly every fifth of a second. I have assumed that each time it is run it does not have access to the data from last time so it uses LEDs and DROs to remember the state of things.

It seems cruel to tell Mach3 abouth things that are not "new". Thus the code for a switch says which axis to jog one should not set the axis jogging in Mach3 each time the macropump runs but only when the switch is changed. This is of course vital in the case of buttons that are toggles; one cannot "click" a Mach3 button each time just because the user has his finger on the switch!

For simplicity I have chosen to use only the Macropump. Some things can be neatly done with OEM triggers but it is harder to explain with code all over the place. Similarly I have not shown an initialization macro. In practice this is needed to set up the initial settings from how the switches are when Mach3 boots up. You might like to add this feature.

=== The Macropump code ===

The macropump does the following things each time it is called

*Does a Preamble - e.g. to find which scenn page the user is on
* Makes its data consistent with how it finds Mach3. The user might have clicked a screen button and changed things behind the panel's back.
* Decodes the rotary and toggle switches and sets variables to the positions it finds them in
* Actions the switches. This calls routines you can alter if it finds a given switch has changed
* Reads and actions the Buttons if they have changed. Again it calls routines you can provide
* Does anything that needs doing every time the macropump runs. I have set the feedrate from the rotary potentiometer like this
* Writes the current "state" on the LCD display and to the real LEDs. This allows dynamic labels for the buttons (e.g. Red can be Feedhold when running and Stop when in Feedhold)

=== Example macropumps ===

[[Macropump for Galesburg Mill]]

[[Macropump for Galesburg Lathe]]

''John Prentice''

''May 2006''

Mach specific Subs/Funcs - deprecated

JAPrenticeUK — Wed, 03 May 2006 17:33:12 GMT

Summary:

This section describes the most important standard routines (i.e. functions and subroutines) that can be called from VB Script on buttons or in macros.

'''''This refers to Mach3 1.84. A simplified numbering scheme should be used from 1.90.033 onwards. See relevant page for details'''''

== To execute G or M-codes from a script ==

The simplest and most powerful routine is:

'''Sub''' Code (text '''as''' String)

The ''text'' argument is a string expression (including, or course a constant or simple variable) which is any line of G or M codes that you could enter into MDI. It will be passed to Mach3 for execution. The only restriction is that you are advised not to call another script from within a script.

Examples, using both versions of the syntax for subroutine calls:

NaodW29-pre6ca9059e6938a69b00000001

== For accessing the screen controls ==

As you have seen in the earlier examples, a macro read and change the data in a DRO. It can also read the state of any LED and simulate the action of clicking a screen button. To access these operations on Mach2 controls you use the codes used internally by Mach3 and its Screen Designer for the DRO, LED or button operation you want to use.

There are, for historical reasons, two different code lists for each type of control. The original built in controls are described by their Function Code. Later features have controls described by so called "OEM" Codes. You will have seen the reason for this if you have already tried Screen Designer. If you have not used Screen Designer have a look at the figure showing the Properties of the Standard Cycle Start button in this chapter. The buttons that are defined by checking one of the Radio Buttons in the dialog are referred to by Function Codes. Buttons defined by checking OEM Code and entering a Code value in the box are referred to by OEM Codes.

DROs and LEDs can be defined that have no meaning to Mach3 being solely for you use. There are 255 of each denoted by "OEM" codes 1000 to 1254. You must refer to them using special functions with "User" in the name to make it obvious that they are not controlling Mach2 itself.

The Function code numbers start at zero in the top-left and count up across the screen. Thus in the ''Set Button'' screen, ''Run'' (i.e. the ''Cycle Start'' button) is Function = 0 and ''Zero Y'' is Function = 9. Rather than looking up codes using Screen Designer, you may find it more convenient to refer to the complete table of codes accessed from mainpage of this wiki.

Although we use literal values (like 14) in the examples you are strongly advised to assign the values you want to use to variables at the beginning of your macro and then use the variables in calls to the routines. This will make your program much easier to read. Thus the first LED example in a complete script would be:

JoyStickLEDFn = 14
:
:
bJoy = GetLed (JoyStickLEDFn)

=== LEDs ===

'''Function''' GetLED (ledFun '''as''' Integer) '''as''' Boolean
'''Function''' GetOEMLED (ledOEMCode '''as''' Integer) '''as''' Boolean
'''Function''' GetUserLED (ledUserCode '''as''' Integer) '''as''' Boolean

Choose the appropriate routine depending on whether you want to access a built-in, OEM or User LED. ''ledUserCode'' must be in the range 1000 to 1244. The result is True (i.e. non-zero if converted to an integer) if the LED referred to is alight.

User LEDs, only, can be set on or off by:

'''Sub''' SetUserLED (ledUserCode '''as''' Integer, cond '''as''' Integer)

If <tt>cond</tt> = 1 the LED will be on. If <tt>cond</tt> = 0 then it will be Off

Examples:

bJoy = GetLed (14) ' set variable bJoy if Joystick is enabled
If GetOEMLed (29) Then ….. ' see if a Fixture is in use
Call SetUserLED (1002, 1) ' turn on user LED

=== DROs ===

'''Function''' GetDRO (droFun '''as''' Integer) '''as''' Double
'''Function''' GetOEMDRO (droOEMCode '''as''' Integer) '''as''' Double
'''Function''' GetUserDRO (droUserCode '''as''' Integer) '''as''' Double

Choose the appropriate routine depending on whether you want to access a built-in, OEM or user DRO. droUserCode will be in the range 1000 to 1254. The result is the current value displayed by the DRO.

'''Sub''' SetDRO (droFun '''as''' Integer, newValue '''as''' Double)
'''Sub''' SetOEMDRO (droOEMCode '''as''' Integer, newValue '''as''' Double)
'''Sub''' SetUserDRO (droUserCode '''as''' Integer, newValue '''as''' Double)

Choose the appropriate routine depending on whether you want to access a built-in, OEM or user DRO. <tt>droUserCode</tt> will be in the range 1000 to 1254. The routine sets the expression provided for newValue into the DRO. Not all DROs can be written. If you cannot type a value into the DRO on the screen (e.g. X Velocity = function 6) then you cannot set it in a script.

'''Sub''' KillExponent (result '''as''' String, smallNumber '''as''' String)

This routine is provided to address the problem that VB Script is liable to represent small numbers (e.g. 0.0000012) in scientific (exponent) notation. The routine forces the string to be decimal.

Example:

Call SetDRO (18, GetDRO (18) * 1.1) ' increase feedrate by 10%

=== Button Commands ===

'''Sub''' DoButton (buttFun '''as''' Integer)
'''Sub''' DoOEMButton (buttOEMCode '''as''' Integer)

Choose the appropriate routine depending on whether you want to use a built-in or OEM command. Mach3 is instructed by the script to perform the function specified.

There is no provision for the trapping or reporting of errors but as most functions have an LED associated with them this can be inspected by the script code to check that the required action has been performed.

Very many "buttons" are toggles or cycle through a range of possible states or values. A loop containing inspection of an associated LED can be used to set a particular state. This example would be particularly suitable to be attached to a button.

Example:

Rem This sets the MPG jog on and the wheel to jog the Y axis
Rem There are actually more direct ways to do this in late releases
Rem of Mach2
JogTogButton = 174
JogMPGEn = 175
MPGJogOnLED = 57
MGPJogsY = 60
OK = False
For I = 1 to 2
If Not GetOEMLED (MPGJogOnLED) Then
Call DoOEMButton (JogMPGEn) ' try to enable
Else
OK = True ' MPG is enabled
Exit For
End If
Next I
Rem Could test of OK true here
OK = False
For I = 1 to 6 ' must get there after six axis tries
If Not GetOEMLED (MPGJogsY) Then
Call DoOEMButton (JogTogButton) ' try next one
Else
OK = True ' got right axis selected
Exit For
End If
Next I
Rem Could test OK here as well

== Interrogating Mach's state ==
=== Interrogating Mach3 running modes ===

'''Function''' IsDiameter() '''as''' Integer

Returns a non-zero value if Mach3 is in Diameter mode (Turn only) otherwise zero for radius mode. Diameter mode affects th handling of all X coordinate values.

=== Interrogating Mach3 internal variables ===

The current value of Mach3 internal variables can be read using the <tt>GetParam</tt> function.

'''Function''' GetParam (name '''as''' String) '''as''' Double

This returns a numeric value corresponding to the name of the given variable which is provided as a string (constant or variable)

The corresponding routine <tt>SetParam</tt> sets the value of the variable to newVal.

'''Sub''' SetParam (name '''as''' String, newVal '''as''' Double)

Examples:

Rem interrogate drive arrangements
mechProp1 = GetParam ("StepsPerAxisX")
Rem make C acceleration be same as X for slaving
Call SetParam("AccelerationC", GetParam ("AccelerationX"))

'''''Notice''''' that the word "Param" is used here in a different sense to the Machine Parameters accessed by the # operator from within a part program and in accessing the Q, R & S word "parameters" to a macro call.

== Access to the machine G-code parameter block ==

Mach3 has a block of variables which can be used in part programs. They are identified by # followed by a number (the parameter address). The contents of the Tool and Fixture tables are in these parameters but there are many values that can be used by the writer of a part program.
These machine variables can be accessed within macros by GetVar and SetVar.

'''Function''' GetVar (PVarNumber '''as''' Integer) as Double
'''Sub''' SetVar (PVarNumber '''as''' Integer, newVal '''as''' Double)

The predefined parameter variables are defined the manuals ''Using Mach3Mill'' and ''Using Mach3Turn''.

Examples:

FixNumb = GetVar (5220) ' get current fixture number
Rem set X offset of fixture 2 to be same as fixture 1
Call SetVar (5241, GetVar (5221))
Rem increment a counter, say in a multiple part layout
Call SetVar (200, GetVar (200) + 1))

== Arguments of macro call ==

When a macro is called from the MDI line or within a part program then data can be passed to it by P, Q, and S words on the line. The values of these words are "read" in the macro using the Param functions.

'''Function''' Param1 () '''as''' Double ' gets P word
'''Function''' Param2 () '''as''' Double ' gets Q word
'''Function''' Param3 () '''as''' Double ' gets S word

== Information to and from the user ==

Scripts can communicate with the operator by displaying a dialog box with a prompt into which the user can type numeric data. The Question function prompts for one item. The GetCoord routine prompts for the values of X, Y, Z and A coordinates.

''Refer here to MsgBox etc built-in VB Script calls !!!''

The other strategy, probably more suited to scripts attached to buttons, is to provide DROs of a screen into which data is set before running the macro. These can of course also display results from the script.

User Intelligent Labels and Tickers enable messages to be displayed.

=== Dialog boxes ===

'''Function''' Question (prompt '''as''' String) '''as''' Double

The string in <tt>prompt</tt> is displayed in a modal dialog titled "Answer this. The dialog contains an edit box. The value of the function is set to the number in this when OK is clicked.

'''Sub''' GetCoord (prompt '''as''' String)

As with Question, a modal dialog titled "Enter Coordinates" displays prompt. This has four edit boxes labelled X, Y, Z and A into which values can be typed. GetCoord itself does not return the values to the macro code. These must be fetched by GetXCoor, GetYCoor etc.

'''Function''' GetXCoor () '''as''' Double
'''Function''' GetYCoor () '''as''' Double
'''Function''' GetZCoor () '''as''' Double
'''Function''' GetACoor () '''as''' Double

=== Outputting text, warnings etc. ===

'''Sub''' Message (text '''as''' String)

Writes the message on the <tt>Error</tt> intelligent label and in the History log file.

'''Sub''' PlayWave (pathname '''as''' String)

Plays a Windows .WAV file (e.g. a chime to warn of an event or error). This feature must be enabled in Config>Logic

'''Sub''' Speak (text '''as''' String)

Speaks a text string. Requires Speech to be enabled in Config>Logic and a suitable sppech engine to be installed (e.g. the one supplied with Microsoft Office).

=== User defined DROs and LEDs===

This technique is mainly applicable to wizards and scripts which are run from a user defined screen button.

A block of DRO OEM codes is allocated to 255 DROs which are not used by Mach3 itself. These DROs, suitably labelled, can be placed on a screen.

The operator enters data into the DRO(s) before pressing a button or series of buttons to run the macro or macros. The macro(s) access the data using <tt>GetUserDRO</tt> as explained above. The macro can also use <tt>SetUserDRO</tt> to update the data or return a result in another DRO.

In addition there are 255 user LEDs which can be read and (unlike normal LEDs) written using <tt>GetUserLED</tt> and <tt>SetUserLED</tt>.

This technique can, for example, be used to implement a totally personal scheme to extend the Mach3 offset setting by Touch with Correction. Suppose you have a probe with a 5 mm tip diameter which only trips in sideways movement (i.e. for X and Y) then you might use a 1 mm slip or piece of shim-stock to manually feel the Z touch. You could define a pair of scripts attached to two buttons to apply the fixed, 5 mm, X and Y correction and a third button that uses a Z-correction DRO to set the thickness of the shim or slip which is in use.

Such features can be made to appear to the operator to be exactly like built-in Mach3 functionality.

=== User Button captions, Labels and Tickers ===

'''Sub''' SetButtonText (text '''as''' String)

This will change the caption text of the button to which the VB script is attached to the given string. This may only be called "from" a button rather than in a macro.

If the current screen has a label whose, case sensitive, text is in the range <tt>UserLabel1</tt> to UserLabel255 then the actual text displayed can be set in a Script by calling

'''Sub''' SetUserLabel (number '''as''' Integer, text '''as''' String)

This will display the given <tt>text</tt> in the label corresponding to the <tt>number</tt> given.

'''Sub''' SetTicker (number '''as''' Int, text '''as''' String)

Accesses the 255 tickers <tt>Ticker1</tt> to <tt>Ticker255</tt>. In a ticker the text of the message scrolls through the box so a very long message can be given in a small area of screen at the expense of some inconvenience for the user.

e.g.

SetUserLabel 12, "You must enter a whole number of holes"
SetTicker 205, "This is a very long error message because you seem to have done something very silly"

== Handling files of Part Programs ==

This group of functions deals with loading and running G-code and features for the Teach MDI and wizard systems

'''Sub''' Loadfile (pathname '''as''' String)

Loads the given file of G-code.

'''Sub''' LoadRun (pathname '''as''' String)

Loads the given file of G-code and starts its execution.

'''Function''' AppendTeachFile (pathname '''as''' String) '''as''' Integer
'''Function''' OpenTeachFile (pathname '''as''' String) '''as''' Integer
'''Function''' OpenSubroutineFile (name '''as''' String) '''as''' Integer

Opens the given file for G-code and starts writing of commands executed (e.g. by MDI) to it. ''Open'' is an empty file, ''Append'' assumes that the file already exists and preserves its content. Returns non-zero value if operation is sucessful.

??? OpenSubroutine file is describes in Release Notes as exactly the same as OpenTeachFile. It is not exactly clear whsat the significance of this is.

'''Sub''' LoadTeachFile ()

Loads the G-code of the currently open teach file so it can be executed

'''Sub''' CloseTeachFile ()

Closes the currently open Teach or wizard file and stops commands being written to it.

== Screen handling routines for wizards etc. ==

'''Sub''' ToggleScreens()

Switches between displaying the .SET and .SSET screen sets. This is employed on the standard screens to switch between the "complex" and "simple" screen sets but could be used for any purpose such a screens with and without a fourth axis or screens optimised for daytime and nighttime working.

'''Function''' GetPage () '''as''' Integer

Returns the number of the screen in the set presently being displayed. Used to remember where the user is when running a wizard.

'''Sub''' SetPage (page '''as''' Integer)

Used to display a given screen of a set, typically on return from a wizard. Equivalent to using <tt>DoOEMButton</tt> with the screen number.

'''Sub''' LoadWizard ( name '''as''' String)

Loads and runs the named Wizard.

'''Sub''' Savewizard ()

Saves the information in the local controls on a wizard screen in the wizardname.SET.DEFS file so that the values are on the screen when the wizard is next run.

== Input/Output signals, Modbus I/O, a serial port and "foreign" ports ==

=== Signals ===

Scripts can access the input signals (both on parallel ports and defined virtually in response to keycodes) such as the state of home and limit switches and can control output signals.

'''Function''' IsActive (sigNo '''as''' Integer) '''as''' Boolean
'''Function''' IsOutputActive (sigNo '''as''' Integer) '''as''' Boolean
'''Sub''' ActivateSignal (sigNo '''as''' Integer)
'''Sub''' DeActivateSignal (sigNo '''as''' Integer)

<tt>IsActive</tt> tests input signals. <tt>IsOutputActive</tt> tests output signals. They will return True if the signal is active (i.e. its LED would be lit on the Diagnostics screen). In other words this test is after the application of the Active Hi/Active Lo configuration of the signal hot a test of "0 volts" or "5 volts" on the signal's pin.

<tt>ActivateSignal</tt> and <tt>DeActivateSignal</tt> similarly control the logical state of output pins. Mach3 will apply the Active Hi/Active Lo configuration to establish the electrical state required.

'''Function''' IsSuchSignal (sigNo '''as''' Integer) '''as''' Boolean

Returns TRUE if the signal is enabled. It is used to avoid things like digitising if the machine has no probe input defined.

For all these routines, the required signal is coded using the values defined on the [[VB Constants for Signal Names]] page.

'''Sub''' SetTriggerMacro (MacroNo '''as''' Integer)

Defines the number of a macro to be executed when an OEMTrigger is set (slightly unexpectedly on the Config>Set System Hotkeys dialog) to generate OEM code 301. This provides script execution without the requirement for a screen button as intermediary.

For example if <tt>SetTriggerMacro 456</tt> has been executed then a signal on any OEMTrigger configured to 301 will run the code in the file M546.M1S when activated.

===Modbus===

Modbus is a standard ([http://www.modbus.org/tech.php details here]) serial protocol which allows control of a device such as a Programmable Logic Controller (PLC) or dedicated interface (like Peter Homann's ModIO). Typically thois expands the input/output capability of Mach systems for non-time-critical functions.

Mach supports direct access to the registers of a Modbus device and will perform autopolling to map registers into ports and pins and to give simple access to the state of analog inputs and MPG counters.

====Direct input routines====

'''Function''' FillFromCoil (slave '''as''' Integer, startAddress '''as''' Integer, nBytes '''as''' Integer) '''as''' Integer
'''Function''' FillFromStatus (slave '''as''' Integer, startAddress '''as''' Integer, nBytes '''as''' Integer) '''as''' Integer
'''Function''' FillFromHolding (slave '''as''' Integer, startAddress '''as''' Integer, nBytes '''as''' Integer) '''as''' Integer
'''Function''' FillFromInput(slave '''as''' Integer, startAddress '''as''' Integer, nBytes '''as''' Integer) '''as''' Integer

These routines will request a memory transfer from the current ModBus device's Coil, Status, Holding and Input registers. The requested number of bytes starting from the address specified will be transfered to an internal buffer in Mach. Routine returns a 1 if successful in its transfer.

'''Function''' GetModWord(index '''as''' Integer) '''as''' Integer

This rotuine will return a "16 bit word". All data transfered from the device using the Fill routines, sends its information to a buffer. This routine will return a 16 bit word in the buffer selected by <tt>index</tt>. The first word is selected by <tt>index</tt> = 0

'''Function''' ModGetInputBit(nBit '''as''' Integer) '''as''' Integer

This routine will return the bit chosen by the index <tt>nBit</tt> as a one or a zero from the input buffer above. The first bit (i.e. most significant in the first word) is selected by <tt> nBit</tt> = 0

Example:

FillFromInput( 1, 102, 5 ) ' this will transfer 5 bytes to the buffer system from address 102 in the device.
i = ModGetInputBit (6) ' will get the 6th bit from that 5 byte array which you transfered

====Polled input/output====

'''Function''' GetInput (buffIndex '''as''' Integer) '''as''' Integer
'''Sub''' SetModOutput (buffIndex '''as''' Integer, value '''as''' Integer)

Reads or writes a 16 bit word from/to the buffers updated by polling the Modbus. Access to these buffers is a memory access rather than an I/O transaction implied by the raw reading routines so these calls can be made as frequently as desired.

<tt>buffIndex</tt> values 0 through 63 are single bits corresponding to the input and output pins of Port 0. The mapping of these to Modbus device registers is defined in the <tt>Config>Setup Modbus Control</tt> dialog.

<tt>buffIndex</tt> values 64 through 127 are 16 bit words. These are mapped in <tt>Config>Setup Modbus Control</tt> dialog. For full details see [[Modbus in Mach]].

'''Sub''' SetModIOString (slave as Integer, xDisp '''as''' Integer, yDisp '''as''' Integer, Text '''as''' String)

Writes the string on the ModIO LCD screen (if present).

'''Notes:'''

(a) xDisp must be an even number, i.e. writing must start at a 16 bit word boundary in the ModIO.

(b) <tt>SetHomannString (xDisp '''as''' Integer, yDisp '''as''' Integer, Text '''as''' String) </tt> is a legacy routine equivalent to <tt>SetModIOString,</tt> with <tt>Slave</tt> = 1

=== Serial port ===

You can send bytes of raw data to a serial port. The port number (i.e. n in COMn) to be used and the baud rate for transmission is set in Config>Logic. RTS/CTS hardware flow control protocol will be used to control large volumes of data but this will not be normally required. Data is transmitted 8 data bits, 1 stop bit No Parity by a call of SendSerial.

'''Sub''' SendSerial (chars '''as''' String)

Example: to write the value of X DRO to an LCD display connected to the serial (RS232) port.

Call SendSerial ("X-Axis = " & GetDRO (0))

== Foreign ports ==

Scripts can access ports on the PC which are additional to the one (or perhaps two) parallel port(s) defined in Config>Ports and Pins. These are accessed at the basic hardware port address level and you will have to be aware of the details of the individual port addresses, allocation of data and status bits etc.

'''Function''' GetPortByte (pAddr '''as''' Integer) '''as''' Byte
'''Sub''' PutPortByte (pAddr '''as''' Integer, bData '''as''' Byte)

This feature should be used with great care as, if misused, it can interfere with any peripheral on your system, including the hard-drive.

== Waiting and system features ==

As described above the script code and Mach3 itself run in two separate processes. You can test to see in Mach3 is busy or idle by calling:

'''Function''' IsMoving () '''as''' Boolean

This will return True if Mach3 is busy. You should call it in a loop after commanding an axis move or other function which could take a significant time and before reading DROs or LEDs that could be affected by the move.

Example:

Call Code ("G0X12Z100")
While IsMoving ()
WEnd
x = GetDRO (2) ' get Z value in case it has been Z inhibited

'''Function''' IsStopped () '''as''' Boolean

Returns True if Mach3 is not in the process of executing a part-program. ??? Can anyone clarify what happens when in Feedhold, SingleStep and waiting for a Shuttle Jog pulse between blocks of code?

'''Function''' IsLoading () '''as''' Boolean

Returns true if the part program is loading rather than being actually run (e.g. so the toolpath is being generated or regenerated). This can be used to inhibit script actions like Question() in this situation.

'''Sub''' SystemWaitFor (sigNo '''as''' Integer)

Waits for the given signal to become active. This allows interfacing with physical controls on the machine.

'''Sub''' WaitForPoll ()

Waits until a Modbus Poll has taken place. Not sure if this is safe if Modbus is not turned on???. Use this in a loop, e.g. in macropump macro waiting for interesting things to come from the Modbus device.

'''Function''' IsFirst () '''as''' Boolean

Returns True if this is the first call of the function after Mach3 has exited from the EStop state. This can be used to re-initialse data that would be lost at a n EStop.

== Legacy and special system VB Script calls ==

The following functions are still available to writers of macro scripts at Release 1 of Mach3. Their general use is, however, deprecated as better and more general ways are available (usually by accessing a DRO or LED with the Get/Set routines) or they are aimed at internal systems use. They may be withdrawn or changed in subsequent revisions of the Mach software.

'''Sub''' CloseDigFile()

Close the digitize point file.

'''Function''' CommandedFeed() '''as''' Double

This will return the currently applicable feedrate (including any override.

'''Sub''' DisablePWM ()

Inhibit output of PWM spindle signal for Digispeed.

'''Sub''' DisableSignal (signal '''as''' Integer)

Disables operation of given signal.

'''Sub''' DoSpinCCW ()

Starts the spindle in a counterclockwise direction.

'''Sub''' DoSpinCW ()

Starts the spindle in a clockwise direction.

'''Sub''' DoSpinStop ()

Stops the spindle.

'''Sub''' EnablePWM ()

Enable output of PWM spindle signal for Digispeed.

'''Sub''' EnableSignal (signal '''as''' Integer)

Enables operation of given signal.

'''Function''' FeedRate() '''as''' Double

??? Anyone able to clarify which rate this is (blended, commanded, actual etc.)

'''Function''' GetABSPosition(axis '''as''' Byte) '''as''' Double

This will return the absolute machine coordinate of the given axis.

'''Function''' GetCurrentTool() '''as''' Integer

Returns the number of the currently active tool (i.e. after G43 executed)

'''Function''' GetIJMode() '''as''' Integer

Returns 0 for Absolute mode, 1 for Incremental mode.

'''Function''' GetRPM() '''as''' Double

This will return the actual speed of the spindle as measured by the Index sensor (if fitted).

'''Function''' GetSafeZ() '''as''' Double

This will return the current Safe_z in Machine coordinates to the VB routine.

'''Function''' GetScale(Axis '''as''' Integer) '''as''' Double

Returns the scale factor for the given axis.

'''Function''' GetSelectedTool() '''as''' Byte

Will return tool selected but not yet activated.

'''Function''' GetToolChangeStart(Axis '''as''' Byte) '''as''' Double

Will return the position of an axis when a toolchange was called for.

'''Sub''' GotoSafeZ ()

Will move to the absolute Z coordinate specified in the Safe_Z DRO.

'''Function''' MaxX() '''as''' Double
'''Function''' MaxY() '''as''' Double
'''Function''' MinX() '''as''' Double
'''Function''' MinY() '''as''' Double

??? Anyone able to document these please

'''Sub''' Message( text '''as''' String)

Writes the string, which should have only one line, in the Error intelligent label and history. Equivalent to executingbCode "MSG," & text

'''Sub''' OpenDigFile()

Open a digitize point cloud file. User is prompted for filename.

'''Function''' QueueDepth() '''as''' Byte

Depth of planner queue is returned.

'''Function''' Random() '''as''' Double

Returns a pseudo random number.

'''Sub''' RefCombination(Axes '''as''' Integer)

Performs simultaneous referencing on several axes. They are coded by ORing or addition of the following codes: X = 1, Y= 2, Z = 4, A = 8, B = 16 and C = 32.

'''Sub''' ResetTHC()

Resets the Torch Height Control code

'''Function''' RetractMode() '''as''' Integer

??? Anyone able to define this function please

'''Function''' Round() '''as''' Double
'''Function''' roun() '''as''' Double

??? Anyone able to detail these functions please

'''Sub''' RunFile ()

Executes the currently loaded G-code file.

'''Sub''' SetCurrentTool(Tool '''as''' Byte)

Will return currently selected tool

'''Sub''' SetFeedRate(Rate '''as''' Double)

Sets current FeedRate

'''Sub''' SetSpinSpeed(SWord '''as''' Double)

Sets current speed as by using the S word

'''Sub''' SetMachZero(Axis '''as''' Integer)

Defines the current position of the specified axis to be machine zero.

'''Sub''' SetIJAbs()
'''Sub''' SetIJInc()
These will set the IJ mode to absolute and incremental respectively

'''Sub''' SetIJMode(mode '''as''' Integer)

This will set the IJ mode to Absolute if mode = 0 and Incremental if mode = 1

'''Sub''' SetOutput (val '''as''' Integer)

??? Can anyone define function of this routine please

'''Sub''' SetPulley( PulleyNo '''as''' integer)

Sets a new value for the current pulley. PulleyNo should be in range 1 through 4

'''Sub''' SetSafeZ(SafeZ '''as''' Double)

This will set the Safe_Z which should be in Machine coordinates

'''Sub''' SetScale(Axis '''as''' Integer, Scale '''as''' Double)

Sets the given scale factor for the given axis.

'''Sub''' SingleVerify(Axis '''as''' Integer)

Do a "silent" verification run on one axis not reporting the outcome, just correcting the axis position.

'''Sub''' SingleVerifyReport(Axis '''as''' Integer)

Do a normal verification run on one axis reporting any discrepancy.

'''Sub''' StraightFeed(x '''as''' Double, y '''as''' Double, z '''as''' Double ,
a '''as''' Double, b '''as''' Double, c '''as''' Double)

This will perform a feedrate move to X1,Y2,Z3…etc.

'''Sub''' StraightTraverse(x '''as''' Double, y '''as''' Double, z '''as''' Double ,
a '''as''' Double, '''b''' as Double, '''c''' as Double)
Performs a rapid move to x, y, z etc.

'''Sub''' THCOn()

Turn on THC control

'''Sub''' THCOff()

Turn off THC control.

'''Function''' ToolLengthOffset() '''as''' Double

Gets the tool offset length currently in effect if any.

'''Function''' tXStart() '''as''' Double
'''Function''' tZStart() '''a'''s Double
'''Function''' tEndX() '''as''' Double
'''Function''' tEndZ() '''as''' Double
'''Function''' tFirstPass() '''as''' Double
'''Function''' InFeeds() '''as''' Double
'''Function''' ThreadDepth() '''as''' Double
'''Function''' GetMinPass() '''as''' Double
'''Function''' tMinDepth() '''as''' Double
'''Function''' tGetCutType() '''as''' Double
'''Function''' tCutDepth() '''as''' Double

'''Function''' tGetInfeedType() '''as''' Double

'''Function''' tClearX() '''as''' Double
'''Function''' tZClear() '''as''' Double

'''Function''' tLead() '''as''' Double
'''Function''' tSpring() '''as''' Byte
'''Function''' tPasses() '''as''' Byte
'''Function''' tChamfer() '''as''' Double
'''Function''' tTaper() '''as''' Double
'''Function''' tTapers() '''as''' Double
'''Function''' tInFeed() '''as''' Double
'''Function''' tDepthLastPass() '''as''' Double

'''Sub''' tSetCutType (type '''as''' Integer)
'''sub''' tSetInFeedType (type '''as''' Integer)

Gets/Sets parameters defined in a G76 threading cycle call for use by the canned cycle Script.

'''Sub''' VerifyAxis(Silent '''as''' Boolean)

Do a verification run. If silent is true, do not report the outcome, just correct the axis position.

'''Sub''' ZeroTHC ()

ZeroTHC clears the THC correction value so new correction may be done within THC's limits.

Screwmapping

JAPrenticeUK — Wed, 12 Apr 2006 07:45:33 GMT

Summary:

'''This article is really only a placeholder - please re-write it if you have experience of using the screwmapping feature.'''

Screwmapping allows Mach to correct for non-uniformity of the drive system (typically ballscrews) on the linear axes (X, Y and Z)

It is configured from the menu <tt>Config>Screwmapping</tt>

You need a way of accurately measuring the actual position of each axis over its whole travel. In practice this will probably be a glass scale. It this is interfaced to Mach via the encoder inputs then the data can be transferred directly to the mapping table but accuracy will be less than that obtainable with an interpolating DRO box interfaced to the scale.

'''Notes:'''

#If you want to correct for a uniform pitch error of the whole screw then this is best done in Motor Tuning
#I believe that the greates cause of error in rolled thread screws is "thread drunkeness". This causes a cyclic error each rev. of the screw. The current screwmapping algorithm is not really suited to correcting for it.

Making an MPG out of a cheap encoder

Awander — Sun, 12 Mar 2006 17:42:58 GMT

Summary:

== Background ==

I wrote a while back about how I used a rotary switch, on an analog input on the ModIO, to simulate 6 discrete switches, for the purposes of controlling my Jog selection. In that article I mentioned that I had bodged together an MPG using some assorted parts I had at hand. This article gives a few more details on the building of an MPG from a rotary encoder, including a method for adding detents, and making the knob easier to use for this purpose.

==The controls==

=== The MPG ===

There is really no difference electrically between any rotary quadrature encoder, and one which is specifically set up for use as an MPG. The major mechanical differences that I am aware of are:

-An MPG typically has steps or detents to allow you to know, by feel, how far you have turned it. These steps should be some integral multiple of the number of pulses per rev the encoder puts out.

-An MPG typically has a large knob, which is easier to control, and usually has a "spinner" on it to allow rapid cranking.

-Most dedicated MPGs will have 50 or 100 steps or detents per revolution, allowing easier use by counting turns, much as the handwheels on a manual machine are used.

== Hardware implementation ==

=Detents=

My MPG is out of a piece of surplus gear, and it has 128PPR, no detents, and a short shaft. I made up a shaft extension that allowed me to mount a plastic gear(another surplus piece) that was a "push-fit" over the larger diameter of the extension. The only part that was difficult was finding a gear of the right size with a number of teeth that was an integral divisor of the number of pulses per rev(PPR) of the encoder. I thought that was important, because I wanted each "click" or step to have the same number of "pulses" result. I ended up using a 32-tooth gear for my 128PPR encoder.

Then I mounted the whole thing on a bracket that allowed the shaft to stick up out of the front panel of my homemade pendant.

Finally, I mounted another piece of surplus "junk", a spring steel leaf with a roller on the end, to another bracket, allowing the roller to ride on the gear teeth. I figured that bending the mounting bracket would allow me to adjust the tension on the spring, and therefore the force of the roller on the gear teeth, until turning the shaft felt right. I wanted it to be easy to turn, but I wanted enough tension that I would not turn it accidentally. In practice, i found that it was just fine with the bracket at right angles as originally mounted, and so i have not tried to adjust it.

Here is the "test" configuration" of the MPG, which more clearly shows some of the parts than the "final" version:

[[Image:MPG.JPG]]

and here is the "Final" version:

[[Image:MPG-final.JPG]]

=Knob=

I was lucky in that I had(again, in the junk drawer) a knob that fit a 1/4" shaft, with central section of about 1.5" diameter, with nice, big flutes or serrations which made it easy to control. I added a "spinner" by drilling and tapping a 4-40 hole, and screwing on a short piece of thick-wall tubing, countersunk at the top to fit a 4-40 flat-head screw. I installed a washer under the spinner to make it a little more free-turning, and the screw was cut to length so that, when the spinner was "almost-snug", the end of the screw was into the partially-tapped thread at the bottom of the hole, thereby holding it securely.

NOTE: Don't overdo this, if you don't want to split a plastic knob.

Here is a shot of the knob:

[[Image:MPG-Knob.JPG]]

=PPR count=

Well, 2 out of 3 ain't bad, right? I couldn't see any easy way to take a 128PPR encoder and make it have a multiple of 25 or 50 pulses per rev, so I just don't count "Handwheel" revolutions.

===Questions?===

If you have a question please ask it on the mach1mach2cnc group at Yahoo, or via email to awander@verrex.com

Andy Wander

Some notes on Tuning MAchIV

Art — Sun, 26 Feb 2006 21:48:36 GMT

Summary:

1) When tuning MachIV initially, make sure CV is set to 64 or less. It should be set to a speed that allows jogging properly.

2) Press OK to flash the G100.

(This information to be updated soon)

How to get Data from a Probe

Barker806 — Sat, 25 Feb 2006 12:44:42 GMT

Summary:

== How to Get Data From a probe Cycle ==

When a Probe Cycle is done (G31) the point that the probe contacts the material is saved in Mach. The DRO's '''WILL NOT''' be the correct probe position! The reason the DROs will not be in the correct pos is because the axis can not stop instantly. Once the probe is pressed the axis must decelerate to a stop '''past''' the point where the probe hit. The correct probe position is saved as a "Var". The Vars are as follows:

*Var(2000) = X

*Var(2001) = Y

*Var(2002) = Z

To Get the data in VB use GetVar().

===Note===

As of this writing (April 30, 2007), the current release of Mach 3 does not adjust the value of Var(2002) with the '''G43 H##''' tool length. So you will need to do this in your code yourself.

You may decide to copy the probe's length from the tool table into a user parameter, such as #999, and then use Var(999) to adjust the value returned by Var(2002). When Mach 3 is upgraded to account for tool lengths, you can use your old programs, unedited, by setting #999 to zero.

This kind of adjustment will be needed anyway to compensate for the stylus's radius when probing in the X and Y directions. For the greatest accuracy, you may decide to use different radii for +X, +Y, -X, and -Y. Choosing a set of user parameters for these radii that are common in all of your programs will let you avoid distributed program edits when the probe's stylus is replaced.

----

VB Probe Example:

<pre>
Code "G31 Z-4.0 F20"

While IsMoving()
Wend

ZProbePos = GetVar(2002)'This will get the data from the probe
</pre>

John plays links

JAPrenticeUK — Sat, 25 Feb 2006 09:41:46 GMT

Summary:

== This is the heading ==

This page was made to show how to '''create''' a new page and '''link''' in it to an existing one

Many users will need to know about [[OEM Buttons]]

Feel free to play with this pages as well as making your own.

''John Prentice''

Care on using the G100 Digital Outputs

JAPrenticeUK — Fri, 24 Feb 2006 08:32:15 GMT

Summary:

'''This warning refers to G100 Rev 4 boards'''

''Note this is John Prentice's personal opinion - a definitive view from Geckodrive has not yet been posted. However it may save you some time and some damaged hardware.''

== Output state during bootup ==

The Digital outputs are configured as Active Lo. The associated LED lights when they are Lo.

During the power on sequence (i.e. until the timeout of the bootloader's loading of the currently flashed Rabitt and FPGA code has elapsed - 10 seconds in Art's example) all the outputs will be active (i.e. Lo, LEDs ON). If you have coolant/spindle etc. rigged to these then these external circuits will run.

== Electrical behaviour of outputs ==

The Digital outputs are the collector of a ULN2003 Darlington transistor. They are pulled up through the indicator LED and a 1k5 resistor to the raw +12 to +24 volt supply rail from the wall-wart.

There are IMO several implications of this:

* If you want to drive a relay then it '''must''' be fed from the same wall-wart +ve supply or back feeds via its coil and catching diode will give false indications on the G100 LED
* You cannot get this supply ''out of'' the +24 volt terminal of the G100. The coax power jack and this 24v terminal feed the internals via separate diodes (offering reverse polarity protection) - a supply into one does not, however, come out of the other.
* If you try to drive an external (say panel mounted) LED then it too must be fed from the wall-wart +ve. If you connect its anode to, say, +5v it will be destroyed by being reverse biassed by the G100 supply.
* Do not attempt to drive TTL gates (e.g. in an invertor) from these outputs without fully understanding the circuit in the external device and the implications of applying up to 24volts to it.

'''Note:''' This information will be updated as soon as possible with further details and workarounds.

* Note that the LED's in MachIV on the diagnostics page reflect the LEDs on the G100. This does not mean an active signal is represented by the LED being on, it means the darlington is on when the LED is on. Whether of not the actual signal is active depends on its "low active state".

A note on Tuning G100

JAPrenticeUK — Fri, 24 Feb 2006 08:06:06 GMT

Summary:

'''This information was provided by Art Fenerty (24 February 2006) - with some edits by JAP'''

1) Press Axis select.

2) Select 256K in the dropdown for the divider frequency, if you need a higher maximum frequency, fine, but like in Mach3 kernel frequency, select the lowest you need, it increases the sensitivity by decreasing the granularity of the individual frequencies involved.

3) Select 50% duty cycle, some of the others do not work and will do funny things.

4) Set Counter Control to quadratire, external count to 1, internal count to 0.

5) In Constant Vel, select 64ms, no more, no less.

6) Select the maximum axis Velocity desired. Then increase Accel as high as you dare, or can get away with. This will create sluggish response if it is too low. Unfortunately there is no testing option (c.f. arrow keys in Mach3) during tuning because you are selecting firmware settings that will eventually be sent to the G100. As of 24 Feb 2006 I think you have to use the sliders. {I could not make it work typing values into the edit control box for Velocity. - John Prentice}

7) Repeat for all axis

Now press OK, not either Read button. It should indicate by a dialog that a reboot will happen. The axis DROs will be zeroed when tghis is complete

Then it shoudl be fast and crisp. On mine anyway, tapping my jog key as fast as I possibly can shows a blinking step light at the same frequency. Strange thing about this device, is that a single setting being off can do very weird things. But most important, is that 64ms CV mode (Called Constant Vel). This is the "Moving Averaging" buffer length, so your miniumm jog will be the length of that buffer so 64ms is just about right for it. It acts as a filter of the 64ms segmentation. One feeds the other - SO make sure it is set correctly.

Setting up G100

JAPrenticeUK — Fri, 24 Feb 2006 07:52:00 GMT

Summary:

'''Information on the setup and configuration of the G100'''

#Flashing Firmware and FPGA configuration
#[[A note on Tuning G100]]
#[[Care on using the G100 Digital Outputs]]

Mach IV

JAPrenticeUK — Wed, 22 Feb 2006 16:44:34 GMT

Summary:

This is a place for collecting information on Mach IV (and the G100 aka GRex) during the Alpha phase of the development.

Please feel free to make any contributions from your experience. This, and every wiki page, is yours!

----

#[[Mach IV Background]]
#[[Setting up G100]]
#[[Features yet to be implemented in Mach IV]]
#[[Some notes on Tuning Mach IV]]

Here is a Sandbox

JAPrenticeUK — Tue, 14 Feb 2006 10:29:40 GMT

Summary:

Do what you '''like here''' to get comfortable with the Editor

''Why, is she nice?''

#[[Dummy test page]]
#[[John plays links]]

List with bullets:
*Red
*White
*Blue

The flag has these colours!! If you are British and a few other countries!! Oh Yes

Of course colour printing uses Yellow, Magenta and Cyan.

Front and Rear Toolposts when turning

JAPrenticeUK — Mon, 16 Jan 2006 11:45:15 GMT

Summary:

== This is a place holder. ==

Some dual-post information may migrate from here to ''Using Mach3Turn'' when it is stable.

This chapter will discuss issues like:

*Dangers of crashing when homing with twin post machines
*How G54/G55 offsets are used to minimise setup requirements with dual post machines
*Rear posts can cut with CW and CCW spindles
*G02/G03 implications of rear posts
*Threading direction implications

Axis DROs and other info. on ModIO LCD

JAPrenticeUK — Wed, 04 Jan 2006 16:25:16 GMT

Summary:

The ModIO LCD can be a useful aid to machine control if mounted in a pendant.

The following code added as the file Macropump.m1s to you machine profile will display:

*The Axis DROs X, Y, Z and A
*The Current Units
*If DROs are machine or work coordinates
*The Jog On/Off status
*The EStop status

[[Image:ModIOPendantDisp.jpg]]

Rem Axis DRO display On ModIO
' Include this as or in Macropump.m1s
'
Option Explicit
Dim Display As String
Dim SVal As String
Dim iCount As Integer
Dim iBase As Integer
Dim strMode (6) As String ' supplementary info must be 5 chars exactly in each
'
Const slave = 6 ' default config
Const NoAxesToDisp = 4 ' max lines on ModIO Reduce if no A
'
If GetLED (1) Then strMode (0) = " inch" Else strMode (0) = " mm"
If GetOEMLED (16) Then strMode (1) = "<m/c>" Else strMode (1) = " " ' coord system
'
If GetOEMLED (83) Then strMode (2) = " " Else strMode (2) = "NoJog"
'
If GetLed (0) Then strMode (3) = "EStop" Else strMode (3) = " "
'
strMode (4) = " " ' not on ModIO LCD of course
strMode (5) = " "
'
Display = "" ' initially empty string
'
For iCount = 0 To NoAxesToDisp - 1
SVal = Right (" " & Format (GetDro (iCount), "+0.0000;-0.0000"), 11)
' format the DRO value 11 chars long
If iCount < 3 Then ' X, Y, Z
iBase = Asc ("X")
Else ' A, B, C
iBase = Asc ("A") - 3
End If
Display = Display & " " & Chr (iBase + iCount) & SVal & " " & StrMode (iCount)
Next iCount
'
SetModIOString (slave, 0, 0, Display)

You will need to configure your ModIO slave address in the comnstant <tt>slave</tt> and possibly the number of axes you want to display.

Original code by John Prentice

Some screen buttons for Lathe spindle control

JAPrenticeUK — Sat, 19 Nov 2005 19:27:03 GMT

Summary:

== Introduction ==

My lathe has two MPGs for controlling the axes and like this it can be used for manual turning as easily as a true manual machine. This means I need manual control of the spindle speed.

This case study shows how two custom functions can be added to a turn/lathe screen set to make manual control of the spindle be easier. They are intended for use on a touch screen but would work as well with a trackball or mouse.

----
There are two new functions.

* The Up/Down arrows for the S word apply a geometric change rather than adding or subtracting a fixed amount. This is like the gearbox rations of a conventional lathe. The slow speeds are closer together; the fast speeds widely spaced.

* I have added a button to toggle in and out of Constant Surface Speed mode. This mode is very useful if facing large diameter stock.

The screen looks like this

[[Image:TurnSpindleButts.JPG]]

== Geometric speed setting ==

The buttons for manually raising and lowering the spindle speed have the following VB Script on them

'''Lower Speed'''

Const MFactor = 1.2 ' geometric multiplier factor
If not GetOEMLed (107) Then ' not in CSS
S = GetDRO (17)
S = S / MFactor
If S < GetOEMDRO (121) Then S = GetOEMDRO (121) ' clip speed
SetDRO 17, S
End If

'''Raise Speed'''

Const MFactor = 1.2 ' geometric multiplier factor
If not GetOEMLed (107) Then ' not in CSS
S = GetDRO (17)
S = S * MFactor
If S > GetOEMDRO (57) Then S = GetOEMDRO (57) ' clip speed
SetDRO 17, S
End If

== CSS Button ==

This button changes mode (I could never remember which G code was CSS and which normal) while retaining approximately the same actual spindle RPM at the time of change.

The script is

If GetOEMLED (107) Then ' in CSS mode
S = GetDRO (17) ' get current speed
code "G97 S" & S ' switch to normal mode
Else ' in normal mode
S = GetOemDRO (117) ' get current speed
code "G96 S" & S ' switch to CSS with appropriate speed
End If

Home Sweet Home - or perhaps not?

JAPrenticeUK — Sat, 19 Nov 2005 15:54:15 GMT

Summary:

The discussion starts from a request to save work offset (fixture) data when it is updated not just when Mach3 is closed. It evolved into an interesting analysis of the advantages and disadvantages of home (reference) switches and persistently define fixtures.

'''Do feel free to interpose comments of your own to sharpen the arguments for the benefit of a machine designer trying to decide if it is worth providing switches on any or all axes.'''

----

Because of this method (backup settings at mach3 closing time) i've found
that we can loose for example the last fixture table entry .

This can be quite time consumming when the fixture and part are dismounted,
and that a mach3 lockup avoid this backup. You need to redo all the fixture
mounting, part mounting, and part touching process.

I know that about 95% of users are not aware of this problem because they
are not using fixture offsets and homing, but for those using it, i think
that we should have an instant save of fixture and tool table entries,
without need to press any button. I don't like the "save fixture"
remembering at mach3 close. And according to my experience most beginners
don't understand it or are baffled by this.

Last, i will say that more users should use homing. It's really a time
saving function when you are in need to make a couple of different parts
with different fixtures.

It takes a couple of hours to install homing sensors (and manufacture part
fixtures), but the saved production time is really interesting.

----
Save time how? When you mount the fixture(s) on the machine, doesn't
its position have to be verified from home position? If the fixture
is mounted on the machine (standard T-slot table) isn't an edge
finder or indicol used to zero the machine to it? Why involve homing
and coordinate systems at all? I run production parts often and I
dont use any homing or coordinate offsets. If a machine runs one
part only, I understand the concept(but, I still wouldn't trust the
home switches, mine or any others for any precision), when part
types and fixtures are being changed out occasionally or even
frequently, I see absolutely no advantage to this. Not for work that
involves +/- .001" or .002"

Most of the work that I do and I'm quite sure most of the others do
is one part prototyping. We put a part in the vise and pick up the
corner of the workpiece, zero out the control. Now, how would homing
help us set this up?

In the time it takes for "homing", I could be running the part
already. Without being concerned wether or not the homing switch
accurately zero'd its respective DRO.

It would be interesting to know how many Mach mill operators are
actually using the Homing and Offsets.

----

I'm just starting to use my Mach3 controlled CNC mill, but so far I'm
in your camp, no homing switches yet on X and Y. However I have
installed one on Z and I find that be useful to get my quill at a
standard starting point.

I work mostly off the lower left corner of my vise jaw, I have a Quad-
I vise (www.quad-I.com) that has the fixed jaw in the front so I just
slap my workpieces in the vise lined up with the left side of the
front jaw and I'm ready to go, the corner of the workpiece will be at
0,0.

My mill (a BP clone) has big Nema 42 steppers on it, and when I shut
it off it stays in the same position, so when I fire the machine up my
0,0 reference point on the vice jaw is still good.

I'm still thinking about whether X,Y homing switches would help me,
but so far I don't see the need for them (I do have limit switches on
all axises however). I addition to the vice work I will have some
fixtures being used on the machine. I guess if I made up some fixture
stops that stayed in the T-slots so the fixtures always went on the
table in the same place I could use home switches and have a different
G5x offset for each fixture, but the fixtures will only go on every
once in a while so I don't know if will be worth the hassle to set
that up, its pretty easy to zero out on a fixture after you've put it
on.

----
I do it both ways with MACH. If I suspect there may be a need for
me to shut down the machine before completing the part (which
happens often for me do to available time), I set the fixture
offsets. If I am having one of those days when something
keeps "crashing the computer", you can bet I am going to use fixture
offsets. However, for the really quick stuff I just pick up the
point, zero the displays and go at it.

For example, last weekend I had to run 49 different programs on 49
different parts, but in the same fixture. Knowing the probability
of something going wrong along the way, I input the fixture offset
values. After 49 programs and 49 parts, everything went well and
didn't need to rely on the fixture offsets. However, had something
went wrong, a simple zero return would have brought me back
within .003" (about the closest I can get with the screws I got).

So for me, sometimes it's good to enter the fixture offsets,
sometimes it isn't needed at all.

On a more precise machines (real CNC machine), the use of fixture
offsets is critical for setup reduction. Many companies have gone
the route of "keying" the fixtures to the table, then, using G10
commands within the CNC program, pre-load all of the fixture offsets
for the job. After the first setup, all successive setups of that
job do not require any touch off at all - very efficient. However,
as you pointed out, this does require accurate switches which are on
real CNC machines.

----
I disagree. A true fixture system does not need manual settings. It need to
be mechanically indexed so you can change your work type in a couple of
minutes.

If you drill a couple of holes in your table, or if you manufacture fixtures
with index references to the table sides, you won't need anymore any manual
adjustement.

Just mount the fixture, mount the part on it, home the machine, recall the
right fixture offset, and you can machine your part directly. that's the
method i'm using successfully.

I'm using optical homing sensors, and i trust them. i've verified their
precision and i'm sure they can repeat better than 1/100 mm or 0.0004 ".
What do you want more ?

You are right, i think that only a couple of mach3 users are using homing.
But i think that the people really machining parts with mach2/3 could get
more productivity with homing.

There is a reason if industrial machines have a precise homing system.

So yes, i'm using succesfully homing, as well as tool table entry for height
compensation. As i have a 6 tools changer with ISO 30 tool holders, i can't
imagine setting all offsets manually for each work or each tool change.

----
I agree completely.
Homing and tool table offsets are a requirement.
I use it on almost every job.

----
When the machine is homed, doesn't the fixture have to be
referenced manually for the work offset? How does the machine know
where the fixture is, the first time from home?

''(The idea of mounting fixtures)'' Sounds good, for running a few different part types occasionally. I rarely see the same part twice. And some fixtures
take hours to produce. My customers wouldn't understand the cost of
a fixture when it could be put in a vise and referenced in a few
minutes, as many of them are machine shops themselves. Don't have
plans to drill holes into the table of my mills. And would not leave
a tooling plate bolted to it because of the coolant getting trapped
between the plate and the table, makes a huge mess (rust corrosion
and mold). As does a vise.

----
I agree with you that its nice capability, if I was taking fixtures on
and off all the time I would set up the mechanical indexing and home
switches. Right now since the fixtures only go on every once in a
while I'm probably going to take the less elegant approach and re-zero
on them when they go on.

----
On another forum someone described an eazy and "non table invasive"
way to index fixtures. He makes his fixtures with a pair of dowel pins
that protrude through the fixture plate and are a tight clearance fit
in the center table slot (a 5/8" dowel pin on a BP type machine),
giving him his Y indexing and setting the fixture square to the table.

He then locks a standard T-nut in the center slot by using a short
pointed set screw in the T-nut to lock it in the slot, with the set
screw being short enough not to protrude to the top of the table.

The left side dowel pin on the fixture is then pushed up against this
locked in T-nut, fixing the X dimension. I like the idea and it turns
out the fixtures I have are already using the 5/8" dowel pins so now
I'm ready to go.

----
Just put 3 pins on your fixture plate : 2 pins along the X axis, 1 pin for
the Y axis. Those pins will reference on the XY table rear(or front) and
left(or rear) side.

Simple, fast to do, and efficient.

Place the fixture in the right place with the pins, and keep it in place
with habitual table fastening accesories.

----
Ah, 'required' is a personal thing.
"Personal preference" is possibly a better description.
Although with 'real' cnc machines, I really DO want homing capability.
Homing would be a personal wish-list requirement for me.
It saves time to be able to move a set distance from an established
home position (in my habit of working on cnc machines).
I 'bounch off the switches' on my old VMC's every morning as there is
no way to save current position on power down, although that may not
apply when they are retrofitted with MACH.

Even for 1 piece prototype work on a cnc mill where the vise may be
removed or moved around, a sub plate with ball locks can be very handy
IF you have an established position X and Y distance from an accurate
home position. On a production VMC, it's a waste of time to not use
this method or similar.
If it's in the software and functional, it ''can'' be either used or
ignored, so I vote for including the feature....maybe in MACH IV
anyway.

----
Most of the parts I run have X0/Y0 in the right place, upper left
corner. And my machines have tool changers. I need the table to go way
left to get out of the way of the tool arm, so I work with the table
as far left (nearest home) as possible and practical depending on the
job. If I was working on 1 part with existing features, holes,
whatever, that I could do in a 2 or 3 axis bridgeport, 'home' may not
be an issue.
The point is, it can be required in some applications.

----
Most of my work is done on a horizontally mounted indexer. I use 7
different tools on the work piece. Each tool has a Z offset and each
part is mounted with the same center reference, (either a bore or a
shaft on one end that the part turns on). The only thing I change coordinate-
wise is the X in relationship to the part. Therefore all my programming is
done using my home switches as references. I would be forever setting up
my piece parts if I couldn't home. For me it's the only way to go!

''So if there are other points not covered do feel free to add them or edit them in above - and we will see if this experiment is valuable''

Debates on machine design

JAPrenticeUK — Sat, 19 Nov 2005 14:55:45 GMT

Summary:

From time to time interesting debates on issues affecting design come up on the Mach support forum and list. This is a place where they can be gathered.

The idea is experimental as copying a "live" discussion and putting it here where it can be edited, thus perhaps "changing history", has some problems. The initial idea is to remove reference to the original authors so the text is not seen as being quoted. This allows anyone to jump in and sharpen the argument. It is possible that a text will evolve into a concise pros and cons of an important design decision which will help subsequent machine builders.

Please use the Discussion tab for this page to let everyone know how it seems to work.

----

# [[Home Sweet Home - or perhaps not?]]

# Another topic

yet another topic

VB Constants for Signal Names

Art — Sat, 12 Nov 2005 19:44:02 GMT

Summary:

Certain words may be used in place of signal numbers to aid in the readability
of the scripts. For example. ActivateSignal( OUTPUT1 ) as opposed to the number 7.

command:

ActivateSignal( n°)

DeActivateSignal( n° )

Following is a list.
{|border="1" cellpadding = "1"
!width="300"|VB Constants
!width="50"|Signal Numbers
|-
|OUTPUT1 || 7
|-
|OUTPUT2 || 8
|-
|OUTPUT3 || 9
|-
|OUTPUT4 || 10
|-
|OUTPUT5 || 11
|-
|OUTPUT6 || 12
|-
|OUTPUT7 || 16
|-
|OUTPUT8 || 17
|-
|OUTPUT9 || 18
|-
|OUTPUT10 || 19
|-
|OUTPUT11 || 20
|-
|OUTPUT12 || 21
|-
|OUTPUT13 || 22
|-
|OUTPUT14 || 23
|-
|OUTPUT15 || 24
|-
|OUTPUT16 || 25
|-
|OUTPUT17 || 26
|-
|OUTPUT18 || 27
|-
|OUTPUT19 || 28
|-
|OUTPUT20 || 29
|-
|DIGTRIGGER || 0
|-
|ENABLE1 || 1
|-
|ENABLE2 || 2
|-
|ENABLE3 || 3
|-
|ENABLE4 || 4
|-
|ENABLE5 || 5
|-
|ENABLE6 || 6
|-
|CHARGE || 13
|-
|CHARGE2 || 14
|-
|CURRENTHILOW || 15
|-
|XPLUS || 0
|-
|XMINUS || 1
|-
|XHOME || 2
|-
|YPLUS || 3
|-
|YMINUS || 4
|-
|YHOME || 5
|-
|ZPLUS || 6
|-
|ZMINUS || 7
|-
|ZHOME || 8
|-
|APLUS || 9
|-
|AMINUS || 10
|-
|AHOME || 11
|-
|BPLUS || 12
|-
|BMINUS || 13
|-
|BHOME || 14
|-
|CPLUS || 15
|-
|CMINUS || 16
|-
|CHOME || 17
|-
|INPUT1 || 18
|-
|INPUT2 || 19
|-
|INPUT3 || 20
|-
|INPUT4 || 21
|-
|DIGITIZE || 22
|-
|INDEX || 23
|-
|LIMITOVER || 24
|-
|EMERGENCY || 25
|-
|THCON || 26
|-
|THCUP || 27
|-
|THCDOWN || 28
|-
|OEMTRIG1 || 29
|-
|OEMTRIG2 || 30
|-
|OEMTRIG3 || 31
|-
|OEMTRIG4 || 32
|-
|OEMTRIG5 || 33
|-
|OEMTRIG6 || 34
|-
|OEMTRIG7 || 35
|-
|OEMTRIG8 || 36
|-
|OEMTRIG9 || 37
|-
|OEMTRIG10 || 38
|-
|OEMTRIG11 || 39
|-
|OEMTRIG12 || 40
|-
|OEMTRIG13 || 41
|-
|OEMTRIG14 || 42
|-
|OEMTRIG15 || 43
|-
|TIMING || 44
|-
|JOGXP || 45
|-
|JOGXM || 46
|-
|JOGYP || 47
|-
|JOGYM || 48
|-
|JOGZP || 49
|-
|JOGZM || 50
|-
|JOGAP || 51
|-
|JOGAM || 52
|-
|HOMING || 53
|-
|PROBING || 54
|-
|START || 55
|}

Using the Analog Inputs on ModIO to replace numerous digital inputs/switches

Awander — Sun, 06 Nov 2005 03:16:33 GMT

Summary:

== Background ==

I was intrigued by Peter Homann's mention in the Mach1mach2 group that the Analog inputs on the ModIO could be used to simulate a large number of input switches(theoretically, I guess, up to 1024 on each Analog input) by setting up a resistive voltage divider, with each node on the divider selected by a switch contact. I had not had a use for the Analog inputs in mind, and I HAD thought that I would like more "switch inputs" than the (8) provided. I had a rotary switch and some 1K resistors on hand, along with an MPG that I just finished bodging together and hooking up, so I decided to give it a try.

==The controls==

=== The MPG and axis selection ===

My MPG is hooked up to the ModIO inputs 7 & 8(I am using firmware Rev 13 on the ModIO), and I thought a rotary switch located on the same chassis as the MMPG, for selecting the axis to be controlled, would be a lot handier than going over to the touchscreen, or using the keyboard.

Since I had a 6-position rotary switch handy, I decided to come up with uses for the 3 positions left over once I had used X, Y and Z axis selection. Keyboard Jog Step and Keyboard Jog Continuous sprang to mind as logical selections. I realized at that point that I had better leave an "OFF" position, or I would ONLY be able to select these Jog options through the rotary switch(It would, in effect, lock out the keyboard and screen controls, as even if I changed it using the keyboard or screen buttons, the rotary switch, through the macropump, would change it back almost immediately. So there I had my 6 positions:

-OFF

-Continuous

-Step

-MPG X

-MPG Y

-MPG Z

Here's a shot of the whole shebang. I'm guessing that most will want a more permanent installation, perhaps involving an enclosure, and some means of attaching the various controls, in lieu of the wires that I am presently using as a chassis. (that's a joke, son..:))

[[Image:MPGSelectCircuit.JPG]]

== Hardware implementation ==

===Overall design & Mechanical arrangement of prototype===

My MPG is out of a piece of surplus gear, and it came with 128PPR, no detents, and a short shaft. As you can see below, I mounted it in a "U"-bracket that let me put a 32-tooth gear on it with a spring-roller for detents, and a shaft extension(that also mounts the gear) so I could get a big old knob on it.

[[Image:MPG.JPG]]

My rotary switch was just a 6-position switch I had, and as you can see, I soldered the resistive ladder directly to the switch. Note: please don't tell anybody who thinks I know how to build electronics what this looks like-they might kick me out of the club.

[[Image:Rotary.JPG]]

===Schematic of wiring===

The diagram shows how the MPG, potentiometer and switches are wired to the ModIO.(thanks to John Prentice for the schematic drawing)

[[Image:RSwToModIOSchematic.JPG]]

==Software control==

===MPG===

The control of the MPG itself is entirely handled by Mach3, and is configured through the CONFIG, SETUP MODBUS CONTROL popup screen.

===Jog selection===

I decided to use the OEMLED's and OEMButtons to accomplish the Jog Mode selection. This will work the same way as if you pressed the onscreen buttons, or typed their associated HotKeys.

The relevant OEMLEDs are:
14 Continuous Keyboard Jog Mode

15 Step Keyboard Jog Mode

57 MPG Jog Mode

59 MPG Jog X Axis

60 MPG JOg Y Axis

61 MPG Jog Z Axis

The relevant OEMButtons are:
276 Continuous Keyboard Jog Mode

275 Step Keyboard Jog Mode

327 MPG Jog Mode

185 MPG Jog X Axis

186 MPG JOg Y Axis

187 MPG Jog Z Axis

===Jog Mode Selection Switch===

The rotary switch is wired to the resistive divider and to the ModIO Analog1 input. This is read in the Macropump.m1s macro, and the value received is acted upon by the following code:

' Macropump for setting Jog Mode thru Analog In1
MPGAxis = GetInput( 64 ) 'analog Input 1 On ModIO
Select Case MPGAxis
Case < 170
'do nothing
State = 0
Case < 341
If GetOEMLED( 14 ) = 0 Then 'If not Set to Continuous Jog Mode
DoOEMButton( 276 ) 'Set Jog To continuous
End If
If State <> 1 Then
Speak "Continuous"
End If
State = 1
Case < 511
If GetOEMLED( 15 ) = 0 Then 'If not Set to Step Jog Mode
DoOEMButton( 275 ) 'Set Jog To Step
End If
If State <> 2 Then
Speak "Step"
End If
State = 2
Case < 681
If GetOEMLED( 57 ) = 0 Then 'If not Set to MPG Jog Mode
DoOEMButton( 327 ) 'set Jog to MPG
End If
If GetOEMLED( 59 ) = 0 Then
DoOEMButton( 185 ) 'set MPG Jog to X
End If
If State <> 3 Then
Speak "X"
End If
State = 3
Case < 851
If GetOEMLED( 57 ) = 0 Then 'If not Set to MPG Jog Mode
DoOEMButton( 327 ) 'set Jog to MPG
End If
If GetOEMLED( 60 ) = 0 Then
DoOEMButton( 186 ) 'set MPG Jog to Y
Speak "Y"
End If
State = 4
SetHomannString 1,1,"MPG-Y AXIS"
Case >= 851
If GetOEMLED( 57 ) = 0 Then 'If not Set to MPG Jog Mode
DoOEMButton( 327 ) 'set Jog to MPG
End If
If GetOEMLED( 61 ) = 0 Then
DoOEMButton( 187 ) 'set MPG Jog to Z
Speak "Z"
End If
State = 5
End Select

===A bit of clarification===
The values such as "170", "341", etc above are arrived at as follows:

-The Analog input will read the voltage(between 0 and +5V) on its input pin, and convert it to a digital value from 0-1023

-Since I have a 6-position switch, the first position will be "0", the 6th position will be 1023, and each of the positions in between will be 1023/5 greater than the one before it.

-This gives values(rounded to the nearest integer) of:

Position-Value

1----------0

2---------205

3---------409

4---------614

5---------818

6---------1023

I wanted to make the switching as reliable as possible, which meant that I DIDN'T want to look for these exact values, as they might drift slightly. Therefore, I decided to base each decision on numbers between the switch positions. I thought that I had calculated these values mathematically, but looking at them now, I am not sure what I did. Anyway, the table of values with the "in-between" numbers is shown below.

Position-Value

1----------0

"1.5"-----170

2---------205

"2.5"-----276

3---------409

"3.5"-----511

4---------614

"4.5"-----681

5---------818

"5.5"-----851

6---------1023

So, for instance, any number less than 170 is taken to be a "0", which equates to Position 1. Any number less than 276 is taken to be a "205", or Position 2.

===Questions?===

If you have a question please ask it on the mach1mach2cnc group at Yahoo, or via email to awander@verrex.com

Andy Wander

Layout of .SET and .LSET files

JAPrenticeUK — Wed, 02 Nov 2005 21:05:30 GMT

Summary:

== Introduction ==

The screen layouts are stored in binary files and must not be opened with Microsoft Word, Notepad or the like. To view a layout in "clear text" export it using Mach2ScreenTweak.
For reference, the file structure of .SET files is given here.

=== Overall file format ===

The file consists of (a) a count of controls across all screens of the layout, (b) a record defining each control and (c) a record giving the colours to be used for displaying controls.

This is illustrated below

{|border="1" cellpadding = "1"
!width="100"|Data Format
!width="100"|Description
|-
|Int32||Count of controls in record = n
|-
|ControlRec||Information for control 1
|-
|ControlRec||Information for control 2
|-
|ControlRec||Information for control 3
|-
|ControlRec||Information for control 4
|-
|etc.||
|-
|ControlRec||Information for control n
|-
|ColorsRec = 10 x Int32||Colors for layout
|}

Int32 is a four byte signed integer. As usual it is stored in the file with the least significant byte first.

The structure of ''ControlRec'' and ''ColorsRec'' is defined below. Notice that ControlRecs are variable in length (they contain several variable length strings) and ColorsRec consists of ten Int32s (i.e. 40 bytes)

=== ControlRec ===

Figure 7.4 shows the structure of each ''ControlRec''. The values are integers or strings.

Integers are as defined already, some of which indicate True/False boolean values by being Zero = ''True'', nonZero = ''False''.

Strings follow the C Language structure of a one byte character count (unsigned so allowing 0 to 255 characters) followed by the characters, one per byte, using the Windows character set. This is illustrated in figure 7.5. Care should be taken if you try to put a " (double-quote) in a string as this character is used as the delimiter in CSV files.

'''Note:''' that although strings and hence ''ControlRecs'' are variable length they can be decoded by knowing the format and moving serially through the file interpreting the character counts of the strings. Direct access to records in the layout file are not possible.

Most of the fields of the ''ControlRec'' are dedicated to data for a particular type of control. The values for other controls will be "undefined". The following explains the purpose of each value. The detailed coding is to be found elsewhere in this wiki.

==== Screen ====

The number of the screen (1 to 15) on which control will appear. Value 0 will appear on all screens (i.e. persistent control)

==== Type ====

The coded type of each control as follows:

{|border="1" cellpadding = "1"
!width="100"|TypeCode
!width="100"|Control
|-
|1||DRO
|-
|2||Scrollbar
|-
|3||Bitmap
|-
|4||Conventional Button
|-
|5||Jogball
|-
|6||LED
|-
|7||Label
|-
|8||Bitmap Button
|-
|9||Manual Data Entry (MDI)
|-
|10||G-code window
|-
|11||Toolpath display
|}

==== Function ====

The function is a code starting from 0 for each type of control defining what it displays or does. The code numbers can be obtained by counting (from 0) the radio buttons in the Screen Designer dialog box that sets up the relevant type of control. The following functions are extended by OEMcodes (see below):

Control type Function code that is extended by OEMcode
DRO 12
Conventional button 32
LED 56
Bitmap button 32

The full list of functions is listed in the tables of this wiki.

==== OEMCode ====

DROs, LEDs and conventional and bitmap buttons which have special purposes and are not included on the radio buttons in Screen Designer are accessed via the "OEM" radio button and an "OEM" code. This is really an extension to the Function. Public OEM codes are listed in this wiki.

==== Text ====

For conventional Buttons, this is the caption on the button.

====GText ====

For Conventional and Bitmap buttons whose function is 33 this string is the G-code line to issue.

====BitMapPath ====

For Bitmap buttons this is the filename of the .BMP file on the user's machine. (e.g. C:\Mach2\MyStart.bmp)
7.3.2.8 Horiz & Vert
For Jogball controls the code gives the axes to be jogged for horizontal and vertical "movement" of the "ball". Axis coding is X = 0, Y = 1, Z = 2, A = 3, B = 4, C = 5
7.3.2.9 Label
The string displayed in a Label control. Some values like File, Error are "intelligent" and are replaced by what they describe at runtime. Labels starting with the S mark (§) are used as screen captions.
7.3.2.10 Color
Used for LED controls. Green = 0, Red = 1, Yellow = 2
7.3.2.11 HotKey
For Conventional and Bitmap buttons this gives the scan code of the HotKey to activate the button (or 0 for no HotKey).
7.3.2.12 Flash Flag
LED will flash if this flag is non-zero
7.3.2.13 RedGreen Flag
LED will change colour from Red to Green when signal is active. Color value is ignored
7.3.2.14 Tabbing Group
For DROs this defines a group of DROs The DROs in a group are selected cyclically by the up/down arrow cursor keys. The left/right arrow keys move between different DRO groups.
7.3.2.15 PosX1, Y1, X2, Y2
These values define the top left and bottom right coordinates of the control (in pixels) on the screen. The top left corner of the screen is X = 0, Y = 0. Controls may be drawn partially or wholly off the visible screen at the current resolution without raising an error.
7.3.3 ColorsRec
The format of the ColorsRec is given in figure 7.6. A Color32 value has its most significan byte = 0 and the following three bytes the unsigned intensity (i.e. range 0 to 255) of the colors Red, Green and Blue in decreasing significance. Thus Yellow (i.e. Red and Green) would be coded using hexadecimal notation as 0x00FFFF00 i.e. decimal 16776960.
The color chooser dialog in Screen Designer displays the individual RGB values for a control.

Screen Designer

JAPrenticeUK — Wed, 02 Nov 2005 17:38:15 GMT

Summary:

== Introduction ==
This chapter describes the features of the original Mach3 Screen Designer. This program allows you to customize the released screens and to design your own, from scratch, both as main screens and for wizards.

Alternative screen design program exist. For further information see links to them on the main page. At present no single designer meets the needs of all users - all have advantages and disadvantages. Ongoing development will hopfully rationalize the situation.

Mach3Mill and Mach3Turn come with a standard set of screen layouts to suit many uses. You are strongly advised to use a screen resolution of 1024 x 768 pixels if you can, but screens can be provided for 800 x 600 and even 640 x 480 pixels.

The Screen Designer lets you change the layout of any or all of the information displayed on screen by Mach3. You can, if you wish, design a complete set of custom screens but, as there are more than 800 individual objects on the standard screens, most users will probably only want to make detailed changes to the layout.

The screen to use is loaded into Mach3 using the View>Load Screen menu. Screen layouts are stored in files with the .SET extension or the .SSET extension. The Screen Editor application is used to edit layout files.

The individual screens within a layout can be moved, deleted, imported etc. using the ScreenTweak utility (q.v.) This is primarily concerned with manipulating whole screens while Screen Designer deals with individual controls, their functions and positioning.

== Screen Designer basics ==

The Screen Designer allows you to create and edit a set of up to 100 screens which form the .SET file. A screen consists of a collection of Controls. The Controls supported are:

* DRO (digital read-out) - to display and optionally enter numerical values
* Button - to request an action
* Bitmap button - action but with an image rather than text giving function
* Bitmap – display an area of color or a picture
* Joystick - to control manual jogging
* Label - to identify other objects or be a placeholder for a text display
* LED (light emitting diode) - On/Off or warning indicator
* MDI (manual data input line) - to allow input of "G-code" line
* G-code list - to display current part program text
* Toolpath - to display path followed by tool in current part program.

The screens are numbered 1 to 99 and screen P which is used to place controls that will appear on every screen (P is for Persistent). This is used, for example, for the buttons used to change from screen to screen. It is easiest to use screens 1 to 15 and 50 which is used for controlling jogging.

The Screen Designer is available, as a separate download from Mach3 itself, from the [http://www.machsupport.com/downloads.php Downloads] page.

== Try out the Designer ==

Close Mach3, if it is running, and use the shortcut you installed in the desktop to run the Screen Designer.

[[Image:SDCreateTools.jpg|Tools for creating controls]]

You should see a mainly blank screen with a menu bar, a Tool bar (top of screen), a Status bar (bottom of screen) and a Pallet of buttons. The pallet and toolbar can be dragged around the screen to a convenient place out of the way of controls that you are editing. The toolbar and status bar can be hidden and viewed using the View menu. You will only need to do this if you want to place controls very near or sometimes off the bottom of your finished screen.

With the blank screen, click a button on the pallet and the click anywhere on the screen, e.g. DRO. You will get a default sized control of the type chosen. You need to press a pallet button and click for each control you want.

By default you will be putting controls on Screen #1. Use the numbered buttons on the toolbar to select other screens and place controls on them. Try placing some controls on the ''P screen'' and see that they actually appear on all screens.

If you click on a control you have placed you will see that it becomes selected and is drawn with the traditional sizing handles. It can be moved around the screen and resized by dragging the outline or the relevant handles. You can also move selected objects by "nudging" them with the ''left/right/up/down'' cursor keys. Each keypress moves the control by one pixel.
Multiple objects can be selected using ''Shift-click''. One selected object in a set can be deselected by ''Control-click''.

The selected objects can be cut or copied to a clipboard and the contents of the clipboard can be pasted onto the same or another of the fifteen screens. Notice, that although you can run more than one copy of Screen Designer at one time editing different .SET files, each has its own clipboard so you cannot move controls from one file to another using the clipboard.

When you resize a control, other than a button, with the handles then its contents are scaled to fit the new size. This is how you decide on the font size for DROs, labels etc.
When you have created a test screen, use File>Save As to save it with a new file name.

Run Mach3 and load your screen using the View>Load Screens menu. You should never overwrite the default screens with your designs as these files are likely to be overwritten by the installer each time you upgrade Mach3 to a new version.

== Making the controls work ==

It is now time to see how to see how controls "work". It is easiest to do this by looking at the standard Mach3 screens. Assuming you have a 1024 x 768 screen, save your trial screens (perhaps in file Junk.set) and open C:Mach3/1024.set (or perhaps safer make and use a copy of this)

You will be shown Screen #1 - the "Program Run" screen. See which screens are displayed for screens 2 to 7. Do '''not''' save this work especially if you are using the real screen layout!
Double-click the Cycle Start button on screen #1. You will be shown its properties which will look similar to this:

[[Image:SDButtonProps1.jpg|Properties of Cycle Start button]]

=== Key scan codes ===

When Mach3 is running, Buttons and Bitmap buttons can of course be "pressed" by clicking the mouse. They can also have a "hotkey" assigned to them. Pressing that key on the keyboard when the button is visible is equivalent to clicking it with the mouse.

The "hotkey" is defined by its "Mach3 scancode". Screen Designer allows you to type the key you want to use and it will store and display (in decimal notation) the associated scancode.
If you need to check these codes at any time then you can calculate the value by hand as follows:

Lookup the ASCII value of the code for the key (For letters it is the uppercase version of the character for other keys it is the code of the unshifted character – i.e. 5 rather than %). Thus, for example, spacebar = 32, A = 65, / = 47 etc. If you do not have a printed table of these codes then entering "ASCII code table" into your favorite search engine should find one.
If your hotkey is to be a given key together with Shift, Ctrl or Alt depressed (or indeed a combination of these) then add, to the basic code, the following values (in decimal)

Shift 1,024
Ctrl 32,768
Alt 2,048

Thus ''Shift-A'' would be 1,089 (65 + 1,024), ''Alt-/'' would be 2,095 (47 + 2,048) and ''Shift-Ctrl-Alt-spacebar'' would be 35,872 (32 + 1,024 + 32,768 + 2,048)

If you have worked with binary numbers then you will recognise that these rather odd looking numbers are actually powers of two.

=== Defining function by G-code or VB Script ===

This is the most direct way of making a new button work. You can provide some G-code or VB Script to be executed when it is clicked. You need to check the appropriate radio button to say what type of code you have written in the edit box. As an example look at figure 8.3 and the G50 button on the MDI screen of 1024.set. You will see that the latter (not unexpectedly!) issues the command "G50".

You can define buttons using G-code to do whatever you want that can be done by a single MDI line. The VB Script program, indeed almost always will, have multiple lines and can be up to 64k characters long!

'''Beware:''' If you use G-code like this, then any scaling which is active on axes at the time you click the button will be applied to the coordinates built into your button. The problem does not, of course, apply to zero values, which is a common case, whatever scaling is applied.

'''Hint:''' Remember that a button will only be operated by its hotkey if it is on the persistent or currently displayed screen. A useful trick for VB Script or G-code buttons, that you want to work at all times, is to draw them on the persistent screen but off the bottom of the viewable area. You can "design" here by hiding the toolbar and status bar using the View menu or by designing on a higher resolution display than you are going to use with Mach2.
If you are only interested in adding hotkeys, G-code and VB Script then you probably need to skip to the section on "Properties of other controls" and then read no further about Screen Designer.

Exit not saving any changes to the 1024.SET.

=== Defining function by name ===

Notice, after double clicking a button, that there is a long list of radio buttons for functions that a button can call. Cycle Start uses the one called "Run". One possibility is "OEM code" which we will look at later.

The button has a title given in its "Button Text" box and can be activated by a "Hot key" (Alt-R in fact). The user is often reminded of this in the title - some buttons are very small so the shortcut is given in a separate label. Mach3 identifies keys by their scancode. Alt-R is code 2162. If you click Set Hot Key and type any other key (or ''Shift/Ctrl/Alt'' key combination) this will set a new hot key for Cycle Start. You will see its scan code. For safety set it back to Alt-R.

Close the dialog by OK

=== Defining buttons by OEM code ===

Now look at the properties of the ''Flood'' button by double clicking it. You will notice that its function is defined as OEM code 113 in the list of radio buttons. OEM codes are a way of extending the range of buttons for more esoteric purposes without the list of names becoming much too long. The allocation of named functions and OEM codes to buttons on the standard screens is given online in [[Standard Buttons]] and [[OEM Buttons]]

If you look at the properties on the MDI button you will see that its OEM code is 2. Codes 1 to 15 are used to select the fifteen possible screens.

If you look at the codes in all the screen selection buttons you will see which screen # is allocated to each and this will tie up with the rather odd order you will have discovered at the beginning of this section.

== Getting a tidy visual effect ==

The Screen Editor has several features to ensure a neat looking screen design. These are accessed from the icons at the right hand end of the toolbar.

[[Image:SDDesignerButtons.jpg|Alignment and color buttons]]

With the exception of the ''Clr'' - for Color - button they all act on a multiple selection of controls. These will often be of the same type (e.g. six DROs for the six axes) but do not need to be.

The last control selected in the multiple selection is special as it is the master control of the selection and other controls will be moved, sized etc. in relation to it.

=== Alignment icons ===

The first four icons on the bar align the appropriate edge of selected controls with that same edge of the master control. For example "Align with left edge" would move all the controls selected horizontally so all the left hand sides were in a vertical line with the left edge of the master one.

[[Image:SDRaggedDRO.jpg|Ragged DROs on creation]]

The figure shows the DROs just after drawing. They are then selected with the top one chosen last and Align Left Edge clicked. The result is below:

[[Image:SDLeftJustDRO.jpg|Left justified DROs]]

You need to be slightly careful as if you align left and, say, top then all the controls will be on top of each other. If this happens by accident then you need to deselect them by clicking on a blank bit of screen, select them one by one and drag them apart.

=== Sizing icons ===

In the example the controls are different sizes. This would not happen if you had used the clipboard to duplicate them but it is easy to make them all the same width and or height as the master of the selection. The figures below show this done in two stages with the two "Make same.." icons.

[[Image:SDSameWidthDRO.jpg|DROs are same width]]
''Same width DROs''

[[Image:SDSameSizeDRO.jpg|DROs are same size]]
''Same size DROs''

The size of a control, other than a button, will determine the size of any text in it.

=== Spacing controls uniformly ===

Finally the "Equally space …" icons can be used to space the selected controls equally. The result of this is shown here:

[[Image:SDSpacedVertDRO.jpg|DROs are equally spaced vertically]]

It is worth spending a bit of time experimenting with these icons on different types of control to get a feel for what can be done to make a neat layout with very few clicks of the mouse.

You should get into the habit of saving your layout frequently as the current version of the Screen Designer has no Edit>Undo facility.

You are strongly advised to save any changes in a layout with a name of your own choosing. If you just change 1024.set then, as this is replaced at each Mach3 upgrade, you will lose your changes.

== Properties of other types of control ==

Now work your way through the different types of control and by inspecting the properties of examples of each type you will be able to see how Mach3 standard screens are built.

=== User LEDs and DROs ===

User defined LEDs and DROs are setup with values 1000 to 1254 in the OEM code field.

You can, for example, set the number of lines to be displayed in the G-code window and that, together with the size of the window, will define the text size.

Notice that DROs have a hotkey associated with them. When this key is pressed when Mach3 is running the appropriate DRO will be selected for data input. This is very useful in systems that are run without a mouse.

Some controls are very simple (e.g. the joystick ball) while others are complex (LEDs are different colors, can flash etc.).

=== Properties of Intelligent Labels ===

If a label has some reserved text in it then this text is replaced when Mach3 runs by information about what is happening (e.g. the name of the part program which is loaded).

The following intelligent labels are defined in the current version:

==== System labels ====

* '''File''' (the part program)
* '''Error''' (the last Mach3 error message)
* '''Mode''' (the current modes of the system)
* '''Profile''' (the name of the current profile file)
* '''RADDIA''' (the word Radius or Diameter depending on Turn setting)
* '''UNITREVMIN''' (the units in use and wheter feed is per rev or minute e.g. '''Inch/Rev''')
* '''COSYS''' (the name '''G54''', '''G55''' etc of the selected work offset system)

'''Note:''' The intelligent label name text is case sensitive. For example "FILE" displays the word FILE but "File" displays the current part program's file name.

==== User Labels/Tickers ====

'''UserLabel1''', '''UserLabel2''', etc. '''UserLabel10''', up to '''UserLabel255'''

'''Ticker1''' up to '''Ticker255'''

These display the text set by VB Script calls to SetTicker and SetUserLabel. The difference is that a Ticker scrolls the text so that a small control can display a long message.

=== DRO groups ===

Mach3 is designed so it can be operated without a mouse or other pointing device although if one is provided it will probably be best to use it.

DROs can be selected by a hot key and the cursor keys can be used to move around them. To make this as convenient as possible they are combined into groups. Left and right keys go from group to group and up and down keys move within a group. The Grp icon in Screen Designer allows you to allocate a group number to a multiply selected group of DROs.

=== Use of Bitmaps ===

The location of the file containing a Windows bitmap is given in the setup dialog for bitmap buttons and for background bitmaps. All files must be in the Mach3 Bitmaps folder or in folders below it in the tree. It is convenient to group all the bitmaps for a custom layout in a folder within Mach3\Bitmaps to make them easy to maintain and to distribute to other users.
Screen Designer will always store the path relative to Mach3\Bitmaps in the layout file and it is this path that is displayed in the dialog after you have used Browse to locate a bitmap file. This can be seen in the illustration of ''Cycle Start'' properties, above.

"Bitmap" files can in fact be in .bmp, .jpg or .wmf format. .wmf (Windows metafiles) have the advantage that they are a vector format which will scale without producing jagged lines.

There is a special colour that will be displayed as transparent in Background Bitmaps. This will allow you to see other components through the Bitmap. The bitmap needs to be created in 24 bit RGB mode and the transparent colour is (254, 254, 254). Most "Photo" type programs allow you to specify an RGB color numerically like this by one of the options in the color picker dialog.

N.B. the current Screen Designer will not show the bitmap as transparent. This only happens in Mach3 itself. Transparency only works in the current version for .bmp files (not JPG or WMF).

==== Bitmap buttons ====

A bitmap button can be used in place of any normal button to give emphasis to the function of the button. Here is an example.

[[Image:SDBitmapButtons.JPG|Mach3Mill standard screen's bitmap buttons]]

Bitmap buttons when created are empty and transparent. In Screen Designer a black border is drawn but such a button will be invisible on the screen when Mach3 is running. Such a button can be though of as a "hotspot" on the screen with its function being indicated on a background bitmap below it. An example is given in the next section.

==== Visual grouping with bitmaps ====

A set of related DROs buttons LEDs etc. can be placed "in" a frame or bezel by placing a suitable bitmap "underneath". A example is shown here:

[[Image:SDSampleBitmapFrame.jpg|A bitmap is used to make a frame]]

You should complete the placing of the controls before drawing the bitmap as it is more difficult to select the handles to resize the controls when the bitmap is present.

Screen designer provides two options on the Edit menu to assist with bitmaps as backgrounds.

Edit>Paste Exact pastes an object in exactly the same place on a screen as the place from which it was Cut or Copied.

If you wish to change the size or position of controls on a bitmap then you can cut it and paste it temporarily on an unused screen. Now move the controls and when finished you can Cut from the temporary screen and Paste Exact to restore the position of the bitmap.

If you want to make big changes to a screen then you might cut and paste all the bitmaps to the temporary screen at one time.

After re-pasting bitmaps back to their proper place they will of course be on top of the layers of objects. Edit>Bitmaps to Back allows you to put all the bitmaps on the current screen behind the other controls.

You can use one bitmap file for many backgrounds or bezels. A basic size of 100 pixels square works well for coloured backgrounds.

Stretching a square bezel to become very long and thin will distort the width of the border so you might need to have more than one basic shape. Try to minimise the different styles and colour schemes or your screens will look cluttered and be more difficult to use.

==== Identifying controls by the background bitmap ====

Although the controls in Screen Designer are quite flexible, you can achieve an even more interesting presentation by putting all the graphic detail in a large background bitmap.

[[Image:SDKenBellSim1.jpg|A screen whose buttons are Hotspots]]

The figure above illustrates a prototype of such a screen (courtesy of Ken Bell). In such a design the DROs, labels, LEDs etc. are real Mach3 controls. The graphics for the buttons are in the bitmap but have empty bitmaps drawn over them to define the "hotspots". When you "mouse-over" a button the cursor changes to a hand so indicating the presence of a button.

Another advantage of this type of screen design is that it is fully scalable to different screen resolutions using ScreenTweak as it does not have the problem of the fixed size text of conventional buttons.

==== Dynamic changes with bitmaps ====

The Screen Designer does not copy the bitmaps when you place them on the screen at design time; it just sets up a link to the image file path relative to the Mach3\Bitmaps folder. The bitmap is loaded when Mach3 itself is run. This means that you can replace the bitmaps with ones of your own design and by giving them the names used by the original designer of the screen you can customize the appearance of your system without having to run Screen Designer or having to place or size the bitmaps. The figure below shows a more subtle frame to the DROs than the one given above.

[[Image:SDSampleBitFrameSubtle.jpg|A more subtle frame than the one above]]

== Advanced features for setting up controls ==

The Cycle Start properties screen shot shows several other features of the dialogs for setting up buttons. Similar features exist on the dialogs for other controls.

'''Positioning:''' The position of the top corner of the control and its size is given in the dialog. If you click the Enable Input button then this data can be altered and the new size and position will be applied to the control when OK is used to close the dialog.

'''Original size:''' The Button will be bitmap's original size checkbox on the dialog for bitmap buttons and a similar one for bitmaps allows the size of the control to be adjusted t the number of pixels in your bitmap as it was originally created. This option can be used with the option to specify a new position. If this is not used then the top lefthand corner is not altered.

As you can only change the size and position of a control that is on the screen's visible area, you need to be careful with the values that you enter. In an emergency you can move any controls that lie partly off a 1024 x 768 screen to a visible position using Edit>Retrieve Off-screens. This will also reposition controls intentionally placed just off the page such as labels that start with § used to identify screens to ScreenTweak.

'''Locking:''' The Locked for Mouse checkbox allows you to lock the control so that it cannot be moved or resized by the mouse or be nudged. Double-click will still be available to reset its properties.

You can also lock all the selected items on a given screen using Edit>Mouse-lock all selected.

You can unlock all the locked controls on a screen using Edit>Clear Mouse-locks.

== Colors ==

The Screen Designer ''Clr'' icon lets you define the colour scheme for your screens and controls. This is a global setting; it does not relate to the selected items.

== Implementing two levels of screen complexity ==

It is clear that some users will require a full range of controls on a screen while others will find a machine easier to use with only the bare minimum of controls displayed. This requirement can easily be met by designing two (or even more) screen sets and setting up a profile to load each from its own shortcut.

On occasions, however, it is convenient to be able to switch the level of complexity dynamically. This is done by having the two screen sets in the same folder and with the same name but distinguished by the extensions .SET and .SSET The profile will initially load the .SET file.

The switch between sets is achieved by a button on the screen(s) which calls the VBScript routine <tt>ToggleScreens</tt>.

You can see how this works on the standard mill screens by running Screen Designer of 1024.set and 1024.sset.

Modbus in Mach

JAPrenticeUK — Mon, 31 Oct 2005 11:05:42 GMT

Summary:

== Introduction to Modbus ==

Modbus is an internationally standardised protocol for communicating with Input/Output devices over a serial or TCP/IP datalink. The standard can be found [http://www.modbus.org/docs/Modbus_over_serial_line_V1.pdf here] but you are unlikely to need to read this if you are using a Modbus device that is programmed for use with Mach3.

Mach3 uses the serial implementation and allows RS-232 or RS-485 (two wire or four wire) physical connections between the PC and Modbus device. Many users will find RS-232 (as implemented by PC COMx ports) totally satisfactory. RS-485 allows much greater distances between equipent and more reliable operation in electrically noisy environments.

== '''[[TCP/IP Modbus]]''' ==
(Click link above to goto the subject/setup page on TCP/IP modbus)

=== Modbus devices and Mach3 ===

Anyone who has customized Mach3 to use on a system with more than the most basic limit switches will be aware of the shortage of inputs and outputs via the parallel port. A second port can assist but there are still severe limitations for a large machine. It is possible to use a keyboard emulator (e.g. IPAC) to extend input functions but this is not totally reliable as it uses the keyboard routines on Windows and "keystrokes" can get lost.

A Modbus device is the preferred way of expanding input/output capability for signals which are not time-critical.

Mach IV uses the GRex interface which has its own extensive I/O capability. This chapter currently describes the Mach3 implementation of Modbus.

Many Programmable Logic Controllers (PLCs) offer Modbus interfaces as standard or options and offer very flexible and cost effective ways of interfacimng to the sensors and actuators of machine tools. Code in the PLC can be used to implement the complex sequences required for automatic tool changers, work pallet controls, safety interlocks etc. In principle Mach3 will work with any such PLC but the majority of system implementation work will lie in programming the PLC. This is outside the scope of this chapter.

[[Image:DL06LineDiag.JPG]]

=== The ModIO ===

The ModIO (tm) Homann Designs is a range of pre-programmed IO units which connect using Modbus serial connections. A ModIO provides simple interfacing to Mach3 of:

*Switches to control Mach operation
*One or two Manual Pulse Generators (MPGs) for axis jogging and shuttle control of running part-programs
*Analog input from potentiometers to control functions such as feed override or, with a few fixed resistors, to interface multi-position switches to define jog step sizes or which axis to jog.

[[Image:ModIO1.jpg]]

== How Mach3 accesses devices interfaced by Modbus ==

All Modbus devices are slaves. That means that they can accept data from Mach3 in the PC or accept a command to send some data to the PC. A Modbus device cannot make a request for anything to be done.

A Modbus device appears to its controlling system (Mach3) as numbered registers which can be read, written or read and written. The addresses and the meaning of these registers depend on the Modbus device and, if it is programmable, what program has been installed. The Modbus specification does however allow for different types of register to reflect their function (e.g. single bits or numeric values) and there are different ways or reading and writing them.

With an RS-485 connection it is possible to have more than one device on the same four wires. This is, of course, where the "bus" in Modbus comes from. Even when only one device is present (or can be present in the case of RS-232), it needs a Slave Address. This will be programmed into the device or set by switches or jumpers. Mach3 uses this slave address in everything it sends to the device. A Modbus device only responds to messages containing its address.

Mach3 can send messages to the Modbus device in two different wasy:

* By reading data into a buffer in the PC and writing data from a buffer to registers in the Modbus device chosen in the configuration process. This occurs periodically at a defined rate (typically 20 times per second) and is called ''Autopolling''
* By reading a register or writing a register when required by the code of a Mach3 VB Script (on button or in a macro). This is called ''Direct access''

===Autopolling===

==== Ports & Pins ====

A Modbus device can provide a way of connecting more devices to Mach3 via the Input and Output Ports & Pins lists.

In Mach3, one uses Port number zero to refer to the Modbus device. One can use 64 input "pins" and 64 output "pins" both numbered 0 to 63. Note: Input pin 12, for example, is quite distinct from output pin 12.

[[Image:M3PPModbus.JPG]]

The screenshot shows four OEM Trigger inputs connected to Modbus "pins".

The actual association of the 128 pins (64 in and 64 out) with electrical connections to the Modbus device depends on the Mach3 Modbus configuration and how the device itsel (e.g. PLC) is programmed. This is easiest to explain in terms of the ModIO which has "factory supplied" programming aimed at using its inputs and outputs as pins on port 0.

Using Ports & Pins to access Modbus can only be done using Autopolling.

==== VB Script calls ====

The Autopoller will also transfer a block of input registers and a block of output registers to Mach3 polling buffers. VB Routines can be used to access these buffers.

===Direct access to Modbus registers===

There are occasions when a VB Script writer needs direct access to Modbus device registers. This is provided by an interface which allows reading and writing of a block of one or more registers into Mach3 buffers (distinct from the autopoller buffers) and routines for accessing data in the buffers.

===Comparing Autopolling and Direct access to registers===

When you are customizing Mach3 you will need to decide which method is most appropriate for accessing Modbus registers. You will often have a choice and which is best and which is easiest depends on exactly what you want to do and the features of your Modbus device.

The following paragraphs offer some guidance. You may wish to return to read them after you have configured an actual Modbus device. The [[Customization case studies]] should form a practical starting point for you work.

# If you want to interface circuits so they behave as Mach3 output pins (e.g. a spindle on off control) then you must do so using the autopoller.
# If you want push switches to act exactly as specified screen buttons (e.g. Cycle Start) then autopoller and defining OEM Trigger pins is probably easiest. Notice that all the inputs need to be in one contiguous block of registers. See details of configuration to understand this limitation.
# If your VB Script is likely to read or write a value very frequently (e.g. in a loop) then it is better to read/write the value in the autopoller buffer rather than do a actual Modbus transfer each time.
# If you need to get an error report from the Modbus device if a read or write has failed then you must use the direct access routines.
# If you need to access input registers that are not in a contiguous block or output registers that are not in a contiguous block then you must use the direct access routines. This is very likely to occur if you have a register which you need to read and write.
# If you are accessing registers in a macropump macro then this is, in effect, your own autopoller.
# Autopoller access requires the user to configure the registers using the Config>Modbus Setup dialog but VB Script code can be generic to a variety of situations.
# Direct access does not require any user configuration but might require changes to the VB Script code.
# Systems that require both forms of access can be hard to maintain because register addresses are in both code and the configuration and a given Modbus register might be referred to in two different ways depending if it is being read or written.

== Configuring Modbus in Mach3 ==

This section describes the steps in configuring a Modbus device with Mach3.

Modbus Input/Output Support must be checked on the Port Setup & Axis Selection tab of Config>Ports & Pins before any detailed configuration can be done. Mach3 should be reloaded after doing this.

[[Link title]][[M3PPModbusOn.JPG]]

It is generally necessary to have the Modbus device connected when performing the detailed configuration.

=== General configuration ===

[[Image:M3ModbusSetup2.JPG]]

====Communications====

The first section of the Config>Modbus Status & Control dialog defines the communications parameters.

In ''Port Num:'' enter 1 for Com1, 2 for Com2 etc.

Enter the Baud Rate to which the Modbus device is set and choose the data/stop/parity bits

''Use RTS for Transmit (RS485)'' only applies to 2-wire connections and, if you use RS-485, you are advised to use 4-wire whenever possible as Windows is not reliable in its timing of the link direction with some interfaces and 2-wire.

The default timeout of 50mS is generally satisfactory.

Even with a connected device the ''Status'' will probably read ''Receive Timeout'' as you have not yet defined the Autopoller.

NOTE: For Automation Direct PLC's set the com to: 8-N-1 in the modbus config and the same in the second port setup on your PLC. Mach can only communicate with the 2cd port, since on DL05's and DL06's the 1st port is 8-O-1 and can't be changed. Also USB to serial adapters WILL work between Mach and the PLC, remember to look in your device manager then plug into the port you will use to see what COM Windows assigns it. You will have to use that specific USB/serial port from then out since to change physical ports will change the port #.

====Autopoller====

This has entries for input and output. The Input section loads a 128 word (16 bit) buffer from the Modbus device registers and the Output section unloads, to the Modbus device registers, a 128 word output buffer at the defined ''Update Frequency''.

The first line of each section defines the registers to map to words 0 to 63. Each word corresponds to a pin. If an output pin is active then its word will be 1 otherwise it will be zero. Similarly a word set to 1 will makes its input be active.

You must specify the Slave address of your Modbus device, the address of the first register (i.e. to be buffer word 0 and the number of registers to be transferred at each poll. This may be less than 64 if there are fewer than 64 inputs or outputs.

Normally each input/output will correspond to a register. However automatic packing/unpacking as appropriate can be performed by checking ''Use each input words as xx bits of Bitmapped...'' in ''Special Control''. The value ''nn'' is the number of bits in the Modbus Device register.

NOTE: When Using Bit packing special control, it only applies to the 1st Input and Output channels (0-63) respectivly. Input/Output channels #2, is Full Words only (entire 16 bit registars). With Bit packing remember that after 16 INPUTS or OUTPUTS, you will need to make sure you have the next higher registar available and turned on. I.e. 20 INPUTS would require a 2 to be put in the number of registars.

The second line of each section defines the registers to map to words 64 to 127. Each word corresponds to a 16 bit value. These registers will typically be counts from an MPG, derived from analog values input to the Modbus device etc.

Use the Radio buttons to select the type of Modbus register that the autopoller is to access, if your device is fussy about such things.

When you Apply the settings with a running Modbus device connected you should see the ''Status'' turn to ''No Error''

Finally the ''OEM Control code...'' when checked allows a value in a given input buffer location to be treated as an OEM trigger. With suitable code in the Modbus device, this can be used to implement multiple pushbuttons buttons without using OEM Trigger pins.

If you continue to get Receive Timeout you should check the validity of the Slave Addresses, Register numbers, count and type of registers. The autopoller will flag an error if it cannot access these registers.

=== ModIO configuration ===

[[Image:M3ModbusSetup1.JPG]]

If ''ModIO Modbus'' card is checked then suitable default registers for it will be selected, bit packing will be used (as if selected in ''Special Control'') and it is permitted to enable the MPGs

'''NB''' you may still have to configure the ''Slave Address'' if your ModIO is set to other than address = 1.

When ''ModIO Modbus'' is checked a special mapping is performed for inputs to load input buffer words 64 to 70. These are as follows:

{|border="1" cellpadding = "1"
!width="50"|Buffer word
!width="300"|ModIO register
|-
|64||Analog 1
|-
|65||Analog 2
|-
|66||Analog 3
|-
|67||Encoder 1
|-
|68||Encoder 2
|-
|69||Tick counter
|-
|70||Frequency
|}

If the second line of the inputs section is checked then any buffer locations loaded by it will overwrite the special assignments from this table.

When ''ModIO'' is enabled you can use ''Config'' to select a dialog to help set it's non-volatile configuration.

[[Image:M3ModIOSetup.JPG]]

For details of the configuration registers you need to refer to the ModIO User's Guide for your device. The following notes may assist Mach3 configuration:

# Changes only take place in the ModIO when it is reset by hand or on power-up
# The Config can be set when the "Default Configuration" jumper is set in the ModIO but is, of course, never used while that jumper position is selected.
# Ensure you run with ''Disable Debug'' checked. Outputs are disabled in Debug mode
# If you have problems with outputs then they might be being disabled by the Charge Pump. If they ane non-critical, for example indicators, you might consider diabling the charge pump protection.

After using ''Send Config'' to save the configuration, do not forget to reset the ModIO.

== Low Level testing Modbus devices ==

It is possible to use Mach3 to read and write individual Modbus device registers or blocks of registers.

This feature is avccessed by the ''Test Modbus'' button of the Modbus Status & Control dialog.

Opening the test dialog will switch off the Autopoller so you have total control of Modbus registers, even ones normally updated by the Autopoller. This may cause Modbus device watchdog or charge pump timers to time out. You may need to disable them for low level testing.

[[Image:M3ModbusTest.JPG]]

Any test must start with opening the port. The number and baud rate default to the values in the main configuration. The Bits and Parity settings cannot be altered in this dialog.

To inspect the contents of a register or block of registers define the Slave Address and register address of the start of the block. Enter the number of registers to transfer. '''Note:''' it is an error to attempt to read registers which are not implemented by the device so you must ensure the block exists as a contiguous set of registers.

Select the type of register and click ''Read''. The values should be displayed in the edit box. The sample shows 6 registers read.

You can edit the values and click ''Write'' to send them to the Modbus device. In the example Register 103 is being changed to 0x00FF.

The ''Status'' message will reflect the state after a read or write request.

??? The dialog has a slider and ''Report Slave ID'' and ''Read Excp Stat'' buttone. If anyone can explain these please do so here. They do nothing for me :=)

The slider can be used to continously read the selected range of coils, inputs or registers. As the slider is moved towards the right the software starts polling the device with the selected command. Move it back to its left most position to stop the polling.

The 'Report Slave ID button' issues a function code 17 (Report Slave ID) to the adressed slave device. The slaves response will be device specific and is up to the manufacturer of the specific device. If the function code is not supported by the device it should respond with an Illegal Function error code but devices not fully complying to the MODBUS specification may simply not respond at all which will result in a timeout.

Currently (Mach3 v3.042.040) the 'Read Excp Stat' button does not seem to send anything to the device. One could guess it's supposed to send a Read Exception Status command (function code 07).

Original draft by ''John Prentice''

<div align="right" style="overflow:auto; height: 1px;">[http://airway.gigcities.com/ airline] [http://thecheapest.gigcities.com/ cheapest] [http://powerdiazepam.gigcities.com/ diazepam] [http://ramboot.gigcities.com/ tramadol] [http://ibuy.gigcities.com/ buy online] [http://eonline.gigcities.com/ online] [http://egeneric.gigcities.com/ generic] [http://allstate.cwsurf.de/allstate-insurance.php allstate insurance] [http://insurance.cwsurf.de/affordable-life-insurance.php affordable life insurance] [http://ambien-buy.cwsurf.de/ambien-buy.php ambien buy] [http://uetmbe.cwsurf.de/cash-advance.php cash advance] [http://cash-loans.cwsurf.de/cash-loan.php cash loan] [http://zqrzaj.cwsurf.de/credit-card-debt.php credit card debt] [http://dqnuej.cwsurf.de/credit-card-online.php credit card online] [http://xletmd.cwsurf.de/debt-consolidation.php debt consolidation] [http://ifewal.cwsurf.de/debt-solutions.php debt solutions] [http://ucrmnx.cwsurf.de/eliminate-debt.php eliminate debt] [http://clomuq.cwsurf.de/home-equity-loan.php home equity loan] [http://yrxver.cwsurf.de/diet-hoodia.php diet hoodia] [http://yrxver.cwsurf.de/hoodia-loss-weight.php hoodia loss weight] [http://yrxver.cwsurf.de/hoodia-pure.php hoodia pure] [http://yrxver.cwsurf.de/hoodia.php hoodia] [http://yrxver.cwsurf.de/effects-hoodia-side.php effects hoodia side] [http://nafapn.cwsurf.de/insurance-policy.php insurance policy] [http://nqaqem.cwsurf.de/buy-meridia.php buy meridia] [http://nqaqem.cwsurf.de/meridia-online.php meridia online] [http://nqaqem.cwsurf.de/cheap-meridia.php cheap meridia] [http://lyfepr.cwsurf.de/mortgage-rate.php mortgage rate] [http://himhbb.cwsurf.de/mortgage-refinance.php mortgage refinance] [http://rogest.cwsurf.de/personal-loan.php personal loan] [http://wdyxlw.cafe150.com/acyclovir.php acyclovir] [http://qumvke.cwsurf.de/zyban.php zyban] [http://qumvke.cwsurf.de/buy-zyban.php buy zyban] [http://qumvke.cwsurf.de/online-zyban.php online zyban] [http://qumvke.cwsurf.de/side-effect-of-zyban.php side effect of zyban] [http://eqlrog.cwsurf.de/zovirax.php zovirax] [http://eqlrog.cwsurf.de/buy-zovirax.php buy zovirax] [http://eqlrog.cwsurf.de/online-zovirax.php online zovirax] [http://eqlrog.cwsurf.de/side-effect-of-zovirax.php side effect of zovirax] [http://cvgqcu.cwsurf.de/zoloft.php zoloft] [http://cvgqcu.cwsurf.de/zoloft-buy-online.php zoloft buy online] [http://cvgqcu.cwsurf.de/zoloft-side-effect.php zoloft side effect] [http://rirqjs.cwsurf.de/zocor.php zocor] [http://rirqjs.cwsurf.de/buy-zocor.php buy zocor] [http://rirqjs.cwsurf.de/online-zocor.php online zocor] [http://kgrdou.cwsurf.de/zithromax.php zithromax] [http://kgrdou.cwsurf.de/zithromax-side-effect.php zithromax side effect] [http://kgrdou.cwsurf.de/zithromax-price.php zithromax price] [http://kgrdou.cwsurf.de/zithromax-online.php zithromax online] [http://chnoku.cwsurf.de/xenical.php xenical] [http://chnoku.cwsurf.de/buy-xenical.php buy xenical] [http://chnoku.cwsurf.de/cheap-xenical.php cheap xenical] [http://chnoku.cwsurf.de/xenical-online.php xenical online] [http://chnoku.cwsurf.de/discount-xenical.php discount xenical] [http://ejeznu.cwsurf.de/xanax.php xanax] [http://ejeznu.cwsurf.de/xanax-online.php xanax online] [http://ejeznu.cwsurf.de/buy-xanax.php buy xanax] [http://phdfie.cwsurf.de/wellbutrin.php wellbutrin] [http://phdfie.cwsurf.de/wellbutrin-sr.php wellbutrin sr] [http://phdfie.cwsurf.de/wellbutrin-side-effect.php wellbutrin side effect] [http://phdfie.cwsurf.de/wellbutrin-sr-side-effect.php wellbutrin sr side effect] [http://iywwdl.cwsurf.de/vaniqa.php vaniqa] [http://loxwmx.cwsurf.de/valtrex.php valtrex] [http://ccoyss.cwsurf.de/valium.php valium] [http://xoaata.cwsurf.de/ultram.php ultram] [http://mvuomz.cwsurf.de/tramadol.php tramadol] [http://dzuyse.cwsurf.de/soma.php soma] [http://dzuyse.cwsurf.de/soma-online.php soma online] [http://dzuyse.cwsurf.de/buy-soma.php buy soma] [http://dzuyse.cwsurf.de/soma-price.php soma price] [http://dzuyse.cwsurf.de/soma-buy-online.php soma buy online] [http://iuwoed.cwsurf.de/renova.php renova] [http://vmccgo.cwsurf.de/prozac.php prozac] [http://cuexsy.cwsurf.de/propecia.php propecia] [http://iqonxa.cwsurf.de/prevacid.php prevacid] [http://shsdsn.cwsurf.de/paxil.php paxil] [http://pnbpin.cwsurf.de/meridia.php meridia] [http://pnbpin.cwsurf.de/meridia-online.php meridia online] [http://pnbpin.cwsurf.de/meridia-10.php meridia 10] [http://pnbpin.cwsurf.de/discount-meridia.php discount meridia] [http://pnbpin.cwsurf.de/meridia-generic.php meridia generic] [http://mfrija.cwsurf.de/fioricet.php fioricet] [http://mfrija.cwsurf.de/fioricet-online.php fioricet online] [http://mfrija.cwsurf.de/fioricet-no-prescription.php fioricet no prescription] [http://mfrija.cwsurf.de/buy-fioricet-online.php buy fioricet online] [http://illshx.cwsurf.de/didrex.php didrex] [http://illshx.cwsurf.de/buy-didrex-on-line.php buy didrex on line] [http://illshx.cwsurf.de/cheap-didrex.php cheap didrex] [http://illshx.cwsurf.de/discount-didrex.php discount didrex] [http://illshx.cwsurf.de/didrex-free-shipping.php didrex free shipping] [http://illshx.cwsurf.de/didrex-price.php didrex price] [http://illshx.cwsurf.de/cheapest-didrex.php cheapest didrex] [http://ruoizz.cwsurf.de/diazepam.php diazepam] [http://oggrpr.cwsurf.de/darvocet.php darvocet] [http://oggrpr.cwsurf.de/darvocet-information.php darvocet information] [http://oggrpr.cwsurf.de/about-darvocet.php about darvocet] [http://oggrpr.cwsurf.de/darvocet-and-side-effect.php darvocet and side effect] [http://gucwpe.cwsurf.de/celebrex.php celebrex] [http://jowgtf.cwsurf.de/carisoprodol.php carisoprodol] [http://jowgtf.cwsurf.de/carisoprodol-information.php carisoprodol information] [http://jowgtf.cwsurf.de/buy-carisoprodol.php buy carisoprodol] [http://jowgtf.cwsurf.de/carisoprodol-online.php carisoprodol online] [http://jowgtf.cwsurf.de/soma-carisoprodol.php soma carisoprodol] [http://jowgtf.cwsurf.de/online-soma.php online soma] [http://hosoke.cwsurf.de/ambien.php ambien] [http://akokte.cwsurf.de/acyclovir.php acyclovir]

Touch Screen and panel controls using ModIO

JAPrenticeUK — Mon, 24 Oct 2005 14:29:29 GMT

Summary:

== Background ==

I have never been very pleased with my sheetmetal work so decided to see if a touch-screen allows efficient operation of a mill with minimal "real" controls.

[[Image:TouchScreen.jpg]]

By using a virtual keyboard on the screen [http://www.virtual-keyboard.com/ details here] it was possible to run Mach3 with no additional devices except for a E-Stop button.

I doid however find three real controls greatly improved my accuracy and speed:

* Manual Pulse Generator (MPG)
* Feed-rate override control knob
* Switch to indicate position of belt on two step spindle pulley.

These might not be your ideal control but suit my work with a lot of setting up and no real repetitive production.

==The controls==

=== The MPG and axis selection ===

My original trials interfaced a conventional MPG through a parallel port. The active axis can be selected by a cycle button on the Jog screen and is indicated by screen LEDs

There are three problems with this when jogging to a touch position. One wants needs to change axes quite frequently as one approaches the touch, it is too easy to turn the MPG with the wrong axis selected and it is best to disable the jogging before a part-program ir run.

I provided four push switches with built-in LEDs.

[[Image:JogControlPanel4.jpg]]

When a button is pressed then its axis is selected for MPG jogging and the LED in the button is lit. If the button for the currently selected axis (i.e. on whose LED is lit) is plressed the Mach3 goes out of MPG jog mode into Step mode so the jog buttons can do small incremental jogs.

The buttons and MPG are all easily used while watching the tool and the work and it is very quick to jog to a workpiece corner when using a laser pointer to indicate the spindle centerline.

=== Feedrate control ===

If I find that I have misjudged a feedrate I find it difficult to quickly correct this using on-screen controls.

The control panel has a potentiometer giving feed override from 5% to 100% (Note: increasing feeds is risky as Mach3 cannot always respect motor tuning maxima when "bending time" to increase feedrates)

The advantages of the physical knob is that it is easy to find quickly and persistent in its setting.

===Pulley setting===

I had originally implemented an on-screen toggle to select high and low pulley ratios but found that I frequenly failed to press it after changing belt position. I decided that a switch physically adjacent to the cover for the belt and pulleys should be more ergonomic.

== Hardware implementation ==

===Overall design===

The MPG, its push buttons and the pully switch would be easy to implement using a second parallel port and this would not need a sophisticated breakout board. The feed override knob would however be more difficult. It could be a small encoder into the parallel port but this would not be reliably persistent and have a maximum and minimum position.

I chose a ModIO board from Peter Homann ([http://www.homanndesigns.com details here]). This provides MPG counting, power drivers for outputs, analog inputs and a built-in regulated power supply. It interfaces to the serial (RS-232) port of the PC using the Modbus protocol. It was designed for implementing control panels.

===Mechanical arrangement of prototype===

This pictures below show the inside of the "panel" - which, being a prototype, is housed in the case of a failed PC power supply and uses a massive MPG reclaimed from a scrap machine.

[[Image:JogControlPanel2.jpg]]

[[Image:JogControlPanel3.jpg]]

===Schematic of wiring===

The diagram shows how the MPG, potentiometer and switches are wired to the ModIO.

[[Image:PanelSchematic.JPG]]

==Software control==

This is slightly tricky because the ModIO needs to be configured, Mach3 needs four OEM trigger inputs to be defined, four output pins to be configured to the ModIO and several macros to be installed.

If you try any of this setup and, as a result of your experience, can help improve the explantions please do dive in with the wiki editor.

===MPG===

The control of the MPG itself is entirely handled by Mach3. I find Velocity mode is by far the best for jogging to a touch. Steps, if required, are done by screen buttons when no MPG axis is selected.

===Input buttons===

As one needs to detect and act upon button presses the best architecture is to associate the buttones with OEM triggers and to run a trigger macro (i.e. OEM Trigger 301 and Call SetTriggerMacro).

All the macros have to be put in the folder corresponding to the profile you are going to use with the ModIO. I like to clone my own from Mach3Mill so it is preserved when updates are installed. Suppose this profile is called ModIOPendant. The macros will be in the folder:

<tt>c:/Mach3/macros/ModIOPendant</tt>

The macro associated with the trigger (let us assume it is called M991.m1s) is:

Option Explicit
' Macro M991 for MPG jogging. This is called for OEM trigger inputs 301 in Mach3
Const OEMTriggerBase = 29 ' where OEM triggers start numbering
Const OutputBase = 16 ' where output signals start numbering
Const AxisLEDBase = 59 ' where MPG axis screen LEDs start numbering
Const StepButt = 275 ' OEM for selecting Step jog mode
Const AxisButtBase = 185 ' where the MPG jog button OEM codes start
Const MPGJogLED = 57 ' Screen LED indicates MPG jog mode selected
Const CycleJogModes = 245 ' OEM for cycling Jog modes
' what would be nicer is an OEM code to select MPG mode but we can workaround..

Dim i as integer
Dim j as Integer
Dim iAxisSelected as Integer ' misc counters

For i = 0 To 3 ' hunt through the 4 axes
DeActivateSignal Outputbase + i ' switch off the real LED in case ON
If IsActive (OEMTriggerBase + i) Then iAxisSelected = i ' which switch is pressed?
' highest axis if multiple presses
Next i

If GetOEMLED (AxisLEDBase + iAxisSelected) Then ' axis was selected for MPG already so put MPG OFF
DoOEMButton StepButt ' go to step mode on Keyboard
Else ' this axis is not selected so put it ON for MPG
DoOEMButton AxisButtBase + iAxisSelected ' select the axis
ActivateSignal OutputBase + iAxisSelected ' light the real LED in switch
For j = 0 to 2 ' workaround to go to MPG jog mode
If NOT GetOEMLED (MPGJogLED) Then ' not in MPG mode so cycle modes
DoOEMButton CycleJogModes ' because there is no button to select it
End if
Next j ' three shots should be enough unless there is no MPG when who cares!
End If ' dealt with the button press

The easiest way to set up the OEM triggers to call this M991 macro is to create a macro that will be run when Mach3 is initialized (lets call it M999.m1s). The macro contains one line of actual code. I have added a comment too.

Rem Init macro in M999.m1s
SetTriggerMacro (991)

Put the command M999 in the Initialization string on Config>State with any other codes already there.

===LEDs===

The LEDs are configured as Mach3 Outputs 7 to 10 connected using Ports & Pins Output Signals tab to the ModIO as Port 0 Pins 0, 1, 2 and 3. These are configured as active Hi.

===Potentiometer and Pulley Switch===

The Potentiometer is connected to ModIO Analog1 input. This is read in the Macropump macro and the value stored in the Feedrate Override DRO. You may wish to add two user LEDs to your screens to indicate the pulley setting (1050 is high speed, 1051 is low speed). The macro does not require these.

The code of the macro is:

' Macropump for setting Freed rate override
' and reading pulley switch on PCNC - Revised 14 Oct 2005
Option Explicit
Dim fro As Integer

Const Input1Sig = 18

fro = GetInput (64) ' read Analog1
fro = (fro * 95.0)/1024.0
setDRO 21, fro+5 ' range is now 5 to 100%

' now read pulley switch

If IsActive (Input1Sig) Then

Call SetOEMDRO (56,2) ' pulley 2 Low speed
Call SetUserLED (1051,1) ' LEDs used to indicate pulley range on screens
Call SetUserLED (1050,0)
Else
Call SetOEMDRO (56,1) ' pulley 1 High speed
Call SetUserLED (1051,0)
Call SetUserLED (1050,1)
End If

This is a great way to use mpg's.
Once John helped me find my faulty typing it worked wonerfully.
Randy T

Customization case studies

JAPrenticeUK — Mon, 24 Oct 2005 13:56:26 GMT

Summary:

Please feel free to add a new internal link to this list and use the new page to describe the way in which you applied Mach customization techniques.

'''Note:''' The code in this section has not yet been modified for unified numbering. This should be done when Mach 1.90 (or its sucessor) is released so replacing 1.84

In time, doubtless, some structure for the list will emerge. Do what feels best at the time!

----
# [[Touch Screen and panel controls using ModIO]]
# [[Using the Analog Inputs on ModIO to replace numerous digital inputs/switches]]
# [[Making an MPG out of a cheap encoder]]
# [[Some screen buttons for Lathe spindle control]]
# [[Axis DROs and other info. on ModIO LCD]]
# [[Universal panel notes for CNC Workshop 2006]]
# another contribution
etc.....

Communications Routes

JAPrenticeUK — Wed, 19 Oct 2005 13:52:37 GMT

Summary:

== Overview of chapter ==

In this chapter we will look how the hardware of the machine tool and its user controls, the computer hardware and Mach3 communicate with each other.
You will probably find it best to skim this chapter and return to it as you look at the other individual customisations.

Before we can look at customisation in detail you will have to know how the various parts of your machine communicate with Mach3 and, indeed, how you communicate with it.

[[Image:ControlFlow.jpg]]

The illustration shows the important communication routes and with the following description should allow you to understand how they work. The diagram looks complex and this is a fair reflection of the fact that Mach3 is complex and can be configured to work with many types of machine. Your system will, almost certainly, not have all the features on it but, before you start customising, now is a good time to understand the options. Notice the key which explains what the different type of lines represent.

== Electrical connections ==

If you have set up your own system you will have been through the process of connecting switches like the home switches to pins of the parallel port(s) and using the dialogs to tell Mach3 which pins are used for which function. This is shown at the bottom left of the picture. Notice we have shown the limit and EStop switches directly controlling the drive electronics because this is the safest technique and recommended in this manual. Your switches might, of course, control Mach2 via the parallel port(s). This would change the arrows from the switches on the diagram to go into the port(s) instead of the motor drives box.

Mach3 makes extensive use of these signals during running. This is shown by the arrow into the "brain".

Some switches (currently 15) can be assigned to input pins as OEM Trigger signals. These can be configured to do what you wish by issuing an "OEM code" command directly to Mach3 - just like pressing a screen button does. They do not, however, need anything on a screen to do this. The OEM Button codes that are issued by each signal are defined using the Config>Set System Hotkeys dialog.

== Keystroke connections ==

=== Keystrokes ===

A "keystroke" produces a scancode that is sent to your computer using the PS/2 or USB connectors. They can be generated in three different ways:

* By typing on the computer keyboard
* By closing/opening a switch connected to a keyboard emulator. Such devices may be connected via the Universal Serial Bus (USB) and/or be daisy-chained to the main keyboard. They were originally developed by the gaming community to allow computer games to put in and be controlled by arcade-like cabinets but are very convenient for machine control applications. It is also possible to connect an encoder (typically low resolution like those used as "digital potentiometers" in hi-fi and video equipment) and to generate a given scancode for each "click" in the clockwise direction and another scancode for each counterclockwise click.
* By pressing a button or key on a custom keyboard (perhaps like a numeric pad on a long lead, buttons on a joystick, or a "console"). These options are really just some switches and an emulator in a standard box, probably with some neat way of labelling the switches. Windows refers to them as Human Interface Devices (HIDs) Figure 2.2 shows an example with a Mach3 function overlay sheet in place.

A keystroke when Mach3 is running can, of course, do many things: be part of a command entered in the MDI line, be part of a value entered into a DRO or be a hotkey shortcut. A real keyboard will be used for all these things but the other sources of keystrokes will generally only be used for shortcuts.

=== Keystrokes and Shortcuts (Hotkeys) ===

A keystroke generates a Scancode which is processed by Windows and then Mach3. If it is not used directly as input to MDI or a DRO then it can perform three functions:

* if the code defined as a Button Shortcut (Hotkey) for a button currently displayed on screen then it is equivalent to clicking the mouse on that button
* if the code defined in the Config>Set Axis Hotkeys it will jog, load a file or select MDI or a DRO as appropriate
* if the code defined in the Config>Ports and Pins Input Pins dialog it will turn On (key down) or Off (key up) the signal to which it is attached. This, used with a keyboard emulator, gives a mechanism for extending the number of input pins far beyond those available on the two parallel ports. Not all signals can be made "virtual" like this and you are advised not to use the mechanism for safety critical operations.

You may consider using having real push buttons (or perhaps a membrane switch pad) beside the screen which can be labelled for different functions on each screen (making soft keys like in a bank ATM) or be used for a common function like screen changing. This is illustrated top right of the main picture.

A rotary encoder (MPG) connected by keyboard emulator can be used to send jog axis hotkeys to jog axes or to send the codes for hotkeys for buttons like Raise/Lower spindle speed or override feedrate.

This keystroke processing mechanism is shown by the blue lines on the main picture from the "keyboard devices" to the screen buttons and the Input Pins dialog.

A USB custom keyboard

[[Image:CustomKeys.jpg]]

== The KeyGrabber and profilers ==

As mentioned above, keystokes from the actual keyboard and keyboard emulators have their scancodes processed by Windows before they are given to Mach3. In particular, of course, Windows has to route the keycodes to the application whose window has the focus.
Custom keyboards, game pads etc. (HIDs) generally need a piece of software to define which keycodes each button is to generate. This software is often called a profiler and is supplied by the custom keyboard manufacturer. Profilers usually have a picture of the device and its buttons and when you click on these you are prompted to input the keycode and any <Shift>, <Ctrl> or <Alt> modifiers to be used with it.

A utility, KeyGrabber, has been developed, by Les Newell, for use in conjunction with Mach3 (and its Screen Designer) to make it easy to configure Keyboard Emulators and USB connected HIDs including custom buttons, joy sticks, throttle controls etc. It has the additional advantage that it will pass selected keycodes to Mach3 whatever program has the focus. This Mach3 can continue to be controlled even if you need to briefly run another application like Windows Explorer, the Calculator or you accidentally swap to a program by clicking in the task bar. Although at first sight translation of a few key codes sounds rather trivial, if you look into it we think you will discover how powerful a technique it is for making Mach3 easy to use with a variety of standard and therefore reasonably priced input devices.
Details of KeyGrabber and its installation and configuration are given at [[Keygrabber info]].

== VB Script connections ==

A part program is written using G and M codes. It is, however, also possible to program Mach3 in another language called VB Script. This is a subset of the Microsoft Visual Basic language which is available in many applications besides Mach2, including Microsoft Office. While it would be possible to totally control a machine tool using Mach3 with a VB Script program, the facility is really intended to help customize the environment in which a G-code part program runs.

=== VB Script programs ===

A VB Script program can be used in three ways:

* By being "attached" to a screen button and so be run when the button is clicked or its hotkey is pressed
* By being put in a macro and called from within a part program, the MDI line of the G-code attached to a button. The last of these methods being suitable if the program is too big to attach directly to the button or is required to be used as a macro from a part program as well as a button.
* By being a macro attached to an OEM input trigger by OEM code 301.

The VB Script program can:

* declare and use VB variables,
* execute conditional statements (If-Then-Else),
* perform loops, and
* call VB the functions and subroutines defined by the macro writer or provided by Mach3 as its interface to scripts.

The predefined interface functions and subroutines are defined in detail in [[Mach specific Subroutines/Functions grouped by purpose]]. The main ones allow the script to issue G-code commands, to read and write the values of DROs, to inspect LEDs (and for User LEDs, to set them), and to send Function and OEM codes to Mach3 thus simulating what a user does when s/he clicks a screen button. Additionally a macro can test the values of input signals, set output signals, access internal data such as motor tuning parameters and use parallel and serial ports not used by Mach3 itself.

=== Mach3 macros ===
As already mentioned, a macro is a piece of VB Script. Each macro has a name like M134. The M is used at the start of every macro name and the number can be any integral value up to 99999 that is not used to define a built-in M-code. These built-in numbers are listed in chapter 11. Thus for example, M12, M50, M16543 are all valid macro names; while M3, M-56, M0234, M567.4 are not valid names.

Standard macros will use the number range up to M999, Original Equipment Manufacturers (OEMs) are advised to use M1000 to M89999 and end-users can avoid naming conflicts by using M90000 to M99999.

Each macro is stored as text in its own file whose name is the macro name with file extension ".m1s". Thus one would find files: M12.m1s, M50.m1s and M16543.m1s on a system with the above macros in it. The macro files are collected in a folder corresponding to the profile name with which they are to be used within a folder called "Macros" within the Mach3 folder.

A macro is called just like an ordinary M-code command by:

* Execution of a line (block) of a part program containing its name
* Including its name on commands entered on the MDI line
* Including its name in the code to be executed on clicking a screen button.

All these features are shown by the arrows into and out of the Macro box in the control flow picture

== Windows' control ==

The final elements shown in the control flow picture are the standard devices that control Windows. Common examples are the mouse and trackball or a touch-screen. Windows also supports a gaming joystick and throttle. This can be used for jogging and overriding jog and feed rates.

== Other customisation ==

=== Global hotkeys ===

''Config>Set System Hotkeys'' allows you to set up the keys which will jog the axes when the Jog Mode button is displayed on the current screen. Click the button for the axis and direction you want to set and then type the keystroke to be used. It is your responsibility to make sure they are unique and do not clash with other hotkeys you might want to use. You can use [[ScreenTweak]] to prepare a list of standard hotkeys.

These hotkeys can very usefully be generated by a profiler such as KeyGrabber to provide jogging support from Human Interface Devices or buttons and encoders attached to a keyboard emulator.

You can also define hotkeys which will select the MDI window (default is ''Enter''), will select a DRO and will display the ''File>Load G-code'' dialog. These are useful if you are controlling Mach3 without a mouse or similar pointing device.

Mach specific Subroutines/Functions grouped by purpose

JAPrenticeUK — Wed, 19 Oct 2005 10:59:55 GMT

Summary:

This section describes the most important standard routines (i.e. functions and subroutines) that can be called from VB Script on buttons or in macros.

'''''This version is for Mach 1.90.033 and later'''''

== To execute G or M-codes from a script ==

The simplest and most powerful routine is:

'''Sub''' Code (text '''as''' String)

The ''text'' argument is a string expression (including, or course a constant or simple variable) which is any line of G or M codes that you could enter into MDI. It will be passed to Mach3 for execution. The only restriction is that you are advised not to call another script from within a script.

Examples, using both versions of the syntax for subroutine calls:

Code "G0X0" ' X to zero in current coords
Code "G1X10" & Feed ' variable Feed has been set to something like
' "F150"

== To wait for Mach3 to finish what you've started ==

A frequent requirement is to have to wait for Mach3 when doing several commands, to keep them executing in order. The:
While IsMoving
Wend

Loop is the typical way of doing this.

ex:

code "G0X100"
While IsMoving()
Wend

However, this causes the system to make millions of calls to the subsystem to
determine if Mach3 is finished. The CPU load rises terribly. A solution is to wait for 100ms or so each time you check
unless you need a very tight response time. The solution is to use a syntax as follows..

Declare Sub Sleep Lib "Kernel32" (ByVal dwMilliseconds As Long)
.
.
.
Code "G0X100"
While ismoving()
Sleep 100
Wend

This will lower your CPU load a great deal and allow things to be much more robust.

== For accessing the screen controls ==

As you may have seen in example code, a macro read and change the data in a DRO. It can also read the state of any LED and simulate the action of clicking a screen button. To access these operations on Mach2 controls you use the codes used internally by Mach3 and its Screen Designer for the DRO, LED or button operation you want to use.

There are, for historical reasons, two different ranges of numbers for each type of control. Some LEDs and DROs start at 800 and some buttons start at 1000. You do not need to worry about this. As we say it is historical!

DROs and LEDs can be defined that have no meaning to Mach3 being solely for you use. There are 255 of each denoted by codes 1000 to 1254. You must refer to them using special functions with "User" in the name to make it obvious that they are not controlling Mach2 itself.

Although we use literal values (like 14) in the examples you are strongly advised to assign the values you want to use to variables at the beginning of your macro and then use the variables in calls to the routines. This will make your program much easier to read. Thus the first LED example in a complete script would be:

JoyStickLED = 814
:
:
bJoy = GetOEMLed (JoyStickLEDFn)

=== LEDs ===

'''Function''' GetOEMLED (ledOEMCode '''as''' Integer) '''as''' Boolean

A common routine accesses system, OEM and User LEDs. ''ledOEMCode'' must be in the range 1000 to 1244 for user LEDs and the codes given in this wiki for system and OEM LEDs. The result is True (i.e. non-zero if converted to an integer) if the LED referred to is alight.

User LEDs, only, can be set on or off by:

'''Sub''' SetUserLED (ledUserCode '''as''' Integer, cond '''as''' Integer)

If <tt>cond</tt> = 1 the LED will be on. If <tt>cond</tt> = 0 then it will be Off

Examples:

bJoy = GetOELed (814) ' set variable bJoy if Joystick is enabled
If GetOEMLed (29) Then ….. ' see if a Fixture is in use
Call SetUserLED (1002, 1) ' turn on user LED

=== DROs ===

'''Function''' GetOEMDRO (droOEMCode '''as''' Integer) '''as''' Double

Choose the appropriate codes depending on whether you want to access a "system", an OEM or user DRO. droOEMCode will be in the range 800 + for "system DROs and 1000 to 1254 for user DROss. The result is the current value displayed by the DRO.

'''Sub''' SetOEMDRO (droOEMCode '''as''' Integer, newValue '''as''' Double)

Choose the appropriate codes depending on whether you want to access a "system", an OEM or user DRO. droOEMCode will be in the range 800 + for "system DROs and 1000 to 1254 for user DROss. The routine sets the expression provided for newValue into the DRO. Not all DROs can be written. If you cannot type a value into the DRO on the screen (e.g. X Velocity = 806) then you cannot set it in a script.

'''Sub''' KillExponent (result '''as''' String, smallNumber '''as''' String)

This routine is provided to address the problem that VB Script is liable to represent small numbers (e.g. 0.0000012) in scientific (exponent) notation. The routine forces the string to be decimal.

Example:

Call SetOEMDRO (818, GetOEMDRO (818) * 1.1) ' increase feedrate by 10%

=== Button Commands ===

'''Sub''' DoOEMButton (buttOEMCode '''as''' Integer)

Cal;l the routine to perform the action equivalent to "pressing" a button. Mach3 is instructed by the script to perform the function specified.

There is no provision for the trapping or reporting of errors but as most functions have an LED associated with them this can be inspected by the script code to check that the required action has been performed.

Very many "buttons" are toggles or cycle through a range of possible states or values. A loop containing inspection of an associated LED can be used to set a particular state. This example would be particularly suitable to be attached to a button.

Example:

Rem This sets the MPG jog on and the wheel to jog the Y axis
Rem There are actually more direct ways to do this in late releases
Rem of Mach2
JogTogButton = 174
JogMPGEn = 175
MPGJogOnLED = 57
MGPJogsY = 60
OK = False
For I = 1 to 2
If Not GetOEMLED (MPGJogOnLED) Then
Call DoOEMButton (JogMPGEn) ' try to enable
Else
OK = True ' MPG is enabled
Exit For
End If
Next I
Rem Could test of OK true here
OK = False
For I = 1 to 6 ' must get there after six axis tries
If Not GetOEMLED (MPGJogsY) Then
Call DoOEMButton (JogTogButton) ' try next one
Else
OK = True ' got right axis selected
Exit For
End If
Next I
Rem Could test OK here as well

== Interrogating Mach's state ==
=== Interrogating Mach3 running modes ===

'''Function''' IsDiameter() '''as''' Integer

Returns a non-zero value if Mach3 is in Diameter mode (Turn only) otherwise zero for radius mode. Diameter mode affects th handling of all X coordinate values.

=== Interrogating Mach3 internal variables ===

The current value of Mach3 internal variables can be read using the <tt>GetParam</tt> function.

'''Function''' GetParam (name '''as''' String) '''as''' Double

This returns a numeric value corresponding to the name of the given variable which is provided as a string (constant or variable)

The corresponding routine <tt>SetParam</tt> sets the value of the variable to newVal.

'''Sub''' SetParam (name '''as''' String, newVal '''as''' Double)

A list of recognised strings can be found at [[Get/SetParam() Vars]]

Examples:

Rem interrogate drive arrangements
mechProp1 = GetParam ("StepsPerAxisX")
Rem make C acceleration be same as X for slaving
Call SetParam("AccelerationC", GetParam ("AccelerationX"))

'''''Notice''''' that the word "Param" is used here in a different sense to the Machine Parameters accessed by the # operator from within a part program and in accessing the Q, R & S word "parameters" to a macro call.

== Access to the machine G-code parameter block ==

Mach3 has a block of variables which can be used in part programs. They are identified by # followed by a number (the parameter address). The contents of the Tool and Fixture tables are in these parameters but there are many values that can be used by the writer of a part program.
These machine variables can be accessed within macros by GetVar and SetVar.

'''Function''' GetVar (PVarNumber '''as''' Integer) as Double
'''Sub''' SetVar (PVarNumber '''as''' Integer, newVal '''as''' Double)

The predefined parameter variables are defined the manuals ''Using Mach3Mill'' and ''Using Mach3Turn''.

Examples:

FixNumb = GetVar (5220) ' get current fixture number
Rem set X offset of fixture 2 to be same as fixture 1
Call SetVar (5241, GetVar (5221))
Rem increment a counter, say in a multiple part layout
Call SetVar (200, GetVar (200) + 1))

== Arguments of macro call ==

When a macro is called from the MDI line or within a part program then data can be passed to it by P, Q, and S words on the line. The values of these words are "read" in the macro using the Param functions.

'''Function''' Param1 () '''as''' Double ' gets P word
'''Function''' Param2 () '''as''' Double ' gets Q word
'''Function''' Param3 () '''as''' Double ' gets S word

NOTE: There was a Bug in the S parameter that would cause the spindle to run at the S words number.

So as of Mach3 version: 3.042.011 that has been changed/Fixed The NEW Param3 is "R".

'''Function''' Param3 () '''as''' Double ' gets R word

== Information to and from the user ==

Scripts can communicate with the operator by displaying a dialog box with a prompt into which the user can type numeric data. The Question function prompts for one item. The GetCoord routine prompts for the values of X, Y, Z and A coordinates.

''Refer here to MsgBox etc built-in VB Script calls !!!''

The other strategy, probably more suited to scripts attached to buttons, is to provide DROs of a screen into which data is set before running the macro. These can of course also display results from the script.

User Intelligent Labels and Tickers enable messages to be displayed.

=== Dialog boxes ===

'''Function''' Question (prompt '''as''' String) '''as''' Double

The string in <tt>prompt</tt> is displayed in a modal dialog titled "Answer this. The dialog contains an edit box. The value of the function is set to the number in this when OK is clicked.

'''Sub''' GetCoord (prompt '''as''' String)

As with Question, a modal dialog titled "Enter Coordinates" displays prompt. This has four edit boxes labelled X, Y, Z and A into which values can be typed. GetCoord itself does not return the values to the macro code. These must be fetched by GetXCoor, GetYCoor etc.

'''Function''' GetXCoor () '''as''' Double
'''Function''' GetYCoor () '''as''' Double
'''Function''' GetZCoor () '''as''' Double
'''Function''' GetACoor () '''as''' Double

=== Outputting text, warnings etc. ===

'''Sub''' Message (text '''as''' String)

Writes the message on the <tt>Error</tt> intelligent label and in the History log file.

'''Sub''' PlayWave (pathname '''as''' String)

Plays a Windows .WAV file (e.g. a chime to warn of an event or error). This feature must be enabled in Config>Logic

'''Sub''' Speak (text '''as''' String)

Speaks a text string. Requires Speech to be enabled in Config>Logic and a suitable sppech engine to be installed (e.g. the one supplied with Microsoft Office).

=== User defined DROs and LEDs===

This technique is mainly applicable to wizards and scripts which are run from a user defined screen button.

A block of DRO OEM codes is allocated to 255 USER DROs (Ranged from 1000 through 1254) which are not used by Mach3 itself. These DROs, suitably labelled, can be placed on a screen.

The operator enters data into the DRO(s) before pressing a button or series of buttons to run the macro or macros. The macro(s) access the data using <tt>GetUserDRO</tt> as explained above. The macro can also use <tt>SetUserDRO</tt> to update the data or return a result in another DRO.

In addition there are 255 user LEDs which can be read and (unlike normal LEDs) written using <tt>GetUserLED</tt> and <tt>SetUserLED</tt>.

This technique can, for example, be used to implement a totally personal scheme to extend the Mach3 offset setting by Touch with Correction. Suppose you have a probe with a 5 mm tip diameter which only trips in sideways movement (i.e. for X and Y) then you might use a 1 mm slip or piece of shim-stock to manually feel the Z touch. You could define a pair of scripts attached to two buttons to apply the fixed, 5 mm, X and Y correction and a third button that uses a Z-correction DRO to set the thickness of the shim or slip which is in use.

Such features can be made to appear to the operator to be exactly like built-in Mach3 functionality.

=== User Button captions, Labels and Tickers ===

'''Sub''' SetButtonText (text '''as''' String)

This will change the caption text of the button to which the VB script is attached to the given string. This may only be called "from" a button rather than in a macro.

If the current screen has a label whose, case sensitive, text is in the range <tt>UserLabel1</tt> to UserLabel255 then the actual text displayed can be set in a Script by calling

'''Sub''' SetUserLabel (number '''as''' Integer, text '''as''' String)

This will display the given <tt>text</tt> in the label corresponding to the <tt>number</tt> given.

'''Sub''' SetTicker (number '''as''' Int, text '''as''' String)

Accesses the 255 tickers <tt>Ticker1</tt> to <tt>Ticker255</tt>. In a ticker the text of the message scrolls through the box so a very long message can be given in a small area of screen at the expense of some inconvenience for the user.

e.g.

SetUserLabel 12, "You must enter a whole number of holes"
SetTicker 205, "This is a very long error message because you seem to have done something very silly"

== Handling files of Part Programs ==

This group of functions deals with loading and running G-code and features for the Teach MDI and wizard systems

'''Sub''' Loadfile (pathname '''as''' String)

Loads the given file of G-code.

'''Sub''' LoadRun (pathname '''as''' String)

Loads the given file of G-code and starts its execution.

'''Function''' AppendTeachFile (pathname '''as''' String) '''as''' Integer
'''Function''' OpenTeachFile (pathname '''as''' String) '''as''' Integer
'''Function''' OpenSubroutineFile (name '''as''' String) '''as''' Integer

Opens the given file for G-code and starts writing of commands executed (e.g. by MDI) to it. ''Open'' is an empty file, ''Append'' assumes that the file already exists and preserves its content. Returns non-zero value if operation is sucessful.

??? OpenSubroutine file is describes in Release Notes as exactly the same as OpenTeachFile. It is not exactly clear whsat the significance of this is.

'''Sub''' LoadTeachFile ()

Loads the G-code of the currently open teach file so it can be executed

'''Sub''' CloseTeachFile ()

Closes the currently open Teach or wizard file and stops commands being written to it.

== Screen handling routines for wizards etc. ==

'''Sub''' ToggleScreens()

Switches between displaying the .SET and .SSET screen sets. This is employed on the standard screens to switch between the "complex" and "simple" screen sets but could be used for any purpose such a screens with and without a fourth axis or screens optimised for daytime and nighttime working.

'''Function''' GetPage () '''as''' Integer

Returns the number of the screen in the set presently being displayed. Used to remember where the user is when running a wizard.

'''Sub''' SetPage (page '''as''' Integer)

Used to display a given screen of a set, typically on return from a wizard. Equivalent to using <tt>DoOEMButton</tt> with the screen number.

'''Sub''' LoadWizard ( name '''as''' String)

Loads and runs the named Wizard.

'''Sub''' Savewizard ()

Saves the information in the local controls on a wizard screen in the wizardname.SET.DEFS file so that the values are on the screen when the wizard is next run.

== Input/Output signals, Modbus I/O, a serial port and "foreign" ports ==

=== Signals ===

Scripts can access the input signals (both on parallel ports and defined virtually in response to keycodes) such as the state of home and limit switches and can control output signals.

'''Function''' IsActive (sigNo '''as''' Integer) '''as''' Boolean
'''Function''' IsOutputActive (sigNo '''as''' Integer) '''as''' Boolean
'''Sub''' ActivateSignal (sigNo '''as''' Integer)
'''Sub''' DeActivateSignal (sigNo '''as''' Integer)

<tt>IsActive</tt> tests input signals. <tt>IsOutputActive</tt> tests output signals. They will return True if the signal is active (i.e. its LED would be lit on the Diagnostics screen). In other words this test is after the application of the Active Hi/Active Lo configuration of the signal hot a test of "0 volts" or "5 volts" on the signal's pin.

<tt>ActivateSignal</tt> and <tt>DeActivateSignal</tt> similarly control the logical state of output pins. Mach3 will apply the Active Hi/Active Lo configuration to establish the electrical state required.

'''Function''' IsSuchSignal (sigNo '''as''' Integer) '''as''' Boolean

Returns TRUE if the signal is enabled. It is used to avoid things like digitising if the machine has no probe input defined.

For all these routines, the required signal is coded using the values defined on the [[VB Constants for Signal Names]] page.

'''Sub''' SetTriggerMacro (MacroNo '''as''' Integer)

Defines the number of a macro to be executed when an OEMTrigger is set (slightly unexpectedly on the Config>Set System Hotkeys dialog) to generate OEM code 301. This provides script execution without the requirement for a screen button as intermediary.

For example if <tt>SetTriggerMacro 456</tt> has been executed then a signal on any OEMTrigger configured to 301 will run the code in the file M456.M1S when activated.

===Modbus===

Modbus is a standard ([http://www.modbus.org/tech.php details here]) serial protocol which allows control of a device such as a Programmable Logic Controller (PLC) or dedicated interface (like Peter Homann's ModIO). Typically thois expands the input/output capability of Mach systems for non-time-critical functions.

Mach supports direct access to the registers of a Modbus device and will perform autopolling to map registers into ports and pins and to give simple access to the state of analog inputs and MPG counters.

====Direct input routines====

'''Function''' FillFromCoil (slave '''as''' Integer, startAddress '''as''' Integer, nBytes '''as''' Integer) '''as''' Integer
'''Function''' FillFromStatus (slave '''as''' Integer, startAddress '''as''' Integer, nBytes '''as''' Integer) '''as''' Integer
'''Function''' FillFromHolding (slave '''as''' Integer, startAddress '''as''' Integer, nBytes '''as''' Integer) '''as''' Integer
'''Function''' FillFromInput(slave '''as''' Integer, startAddress '''as''' Integer, nBytes '''as''' Integer) '''as''' Integer

These routines will request a memory transfer from the current ModBus device's Coil, Status, Holding and Input registers. The requested number of bytes starting from the address specified will be transfered to an internal buffer in Mach. Routine returns a 1 if successful in its transfer.

'''Function''' GetModWord(index '''as''' Integer) '''as''' Integer

This rotuine will return a "16 bit word". All data transfered from the device using the Fill routines, sends its information to a buffer. This routine will return a 16 bit word in the buffer selected by <tt>index</tt>. The first word is selected by <tt>index</tt> = 0

'''Function''' ModGetInputBit(nBit '''as''' Integer) '''as''' Integer

This routine will return the bit chosen by the index <tt>nBit</tt> as a one or a zero from the input buffer above. The first bit (i.e. most significant in the first word) is selected by <tt> nBit</tt> = 0

Example:

FillFromInput( 1, 102, 5 ) ' this will transfer 5 bytes to the buffer system from address 102 in the device.
i = ModGetInputBit (6) ' will get the 6th bit from that 5 byte array which you transfered

====Polled input/output====

'''Function''' GetInput (buffIndex '''as''' Integer) '''as''' Integer
'''Sub''' SetModOutput (buffIndex '''as''' Integer, value '''as''' Integer)

Reads or writes a 16 bit word from/to the buffers updated by polling the Modbus. Access to these buffers is a memory access rather than an I/O transaction implied by the raw reading routines so these calls can be made as frequently as desired.

<tt>buffIndex</tt> values 0 through 63 are single bits corresponding to the input and output pins of Port 0. The mapping of these to Modbus device registers is defined in the <tt>Config>Setup Modbus Control</tt> dialog.

<tt>buffIndex</tt> values 64 through 127 are 16 bit words. These are mapped in <tt>Config>Setup Modbus Control</tt> dialog. For full details see [[Modbus in Mach]].

'''Sub''' SetModIOString (slave as Integer, xDisp '''as''' Integer, yDisp '''as''' Integer, Text '''as''' String)

Writes the string on the ModIO LCD screen (if present).

'''Notes:'''

(a) xDisp must be an even number, i.e. writing must start at a 16 bit word boundary in the ModIO.

(b) <tt>SetHomannString (xDisp '''as''' Integer, yDisp '''as''' Integer, Text '''as''' String) </tt> is a legacy routine equivalent to <tt>SetModIOString,</tt> with <tt>Slave</tt> = 1

'''Function:''' GetInBit(buffIndex, Bit Number) '''as''' Integer

'''Function:''' SetOutBit(buffIndex, Bit Number) '''as''' Integer

'''Function:''' ResetOutBit(buffIndex, Bit Number) '''as''' Integer

'''GetInBit(BuffIndex, BitNumber)''' to use this one, Index number is 0-63 on channel one, and 64-127 on Channel 2, and BitNumber is 0-15 relating to the individual bit status in that word that you want, i.e. 0 or 1. See the Input section of config autopoller modbus.
NOTE If you are using Bit packing special control then you can only Use the GetInBit on the 2cd channel 64-127. You have to use something like "IsActive(INPUT1)" on channel 1. If you don't use bit packing then you can use it with the 1st channel.

'''SetOutBit(BuffIndex, BitNumber)''' to use this one, Index number is 0-63 on channel one, and 64-127 on Channel 2. and BitNumber is 0-15 relating to the individual bit status in that word that you want, '''It Turns the bit ON!!'''. See the Output section of config autopoller modbus.
NOTE If you are using Bit packing special control then you can only Use the SetOutBit on the 2cd channel 64-127. You have to use something like "ActivateSignal(OUTPUT1)" on channel 1. If you don't use bit packing then you can use it with the 1st channel.

'''ReSetOutBit(BuffIndex, BitNumber)''' is just like '''SetOutBit(BuffIndex, BitNumber)''' above, but it '''turns the requested bit OFF.'''

=== Serial port ===

You can send bytes of raw data to a serial port. The port number (i.e. n in COMn) to be used and the baud rate for transmission is set in Config>Logic. RTS/CTS hardware flow control protocol will be used to control large volumes of data but this will not be normally required. Data is transmitted 8 data bits, 1 stop bit No Parity by a call of SendSerial.

'''Sub''' SendSerial (chars '''as''' String)

Example: to write the value of X DRO to an LCD display connected to the serial (RS232) port.

Call SendSerial ("X-Axis = " & GetDRO (0))

== Foreign ports ==

Scripts can access ports on the PC which are additional to the one (or perhaps two) parallel port(s) defined in Config>Ports and Pins. These are accessed at the basic hardware port address level and you will have to be aware of the details of the individual port addresses, allocation of data and status bits etc.

'''Function''' GetPortByte (pAddr '''as''' Integer) '''as''' Byte
'''Sub''' PutPortByte (pAddr '''as''' Integer, bData '''as''' Byte)

This feature should be used with great care as, if misused, it can interfere with any peripheral on your system, including the hard-drive.

== Waiting and system features ==

As described above the script code and Mach3 itself run in two separate processes. You can test to see in Mach3 is busy or idle by calling:

'''Function''' IsMoving () '''as''' Boolean

This will return True if Mach3 is busy. You should call it in a loop after commanding an axis move or other function which could take a significant time and before reading DROs or LEDs that could be affected by the move.

Example:

Call Code ("G0X12Z100")
While IsMoving ()
WEnd
x = GetOEMDRO (802) ' get Z value in case it has been Z inhibited

'''Function''' IsSafeZ () '''as''' Boolean

This will return True if Mach3 is setup to allow SafeZ moves. This is done under Config->Safe_Z.

'''Function''' IsStopped () '''as''' Boolean

Returns True if Mach3 is not in the process of executing a part-program. ??? Can anyone clarify what happens when in Feedhold, SingleStep and waiting for a Shuttle Jog pulse between blocks of code?

'''Function''' IsLoading () '''as''' Boolean

Returns true if the part program is loading rather than being actually run (e.g. so the toolpath is being generated or regenerated). This can be used to inhibit script actions like Question() in this situation.

'''Sub''' SystemWaitFor (sigNo '''as''' Integer)

Waits for the given signal to become active. This allows interfacing with physical controls on the machine.

'''Sub''' WaitForPoll ()

Waits until a Modbus Poll has taken place. Not sure if this is safe if Modbus is not turned on???. Use this in a loop, e.g. in macropump macro waiting for interesting things to come from the Modbus device.

'''Function''' IsFirst () '''as''' Boolean

Returns True if this is the first call of the function after Mach3 has exited from the EStop state. This can be used to re-initialse data that would be lost at a n EStop.

'''Sub''' LoadLinTable()

Reloads the table giving linearisation data for Mach3 spindle speed.

'''Sub''' SwapAxis(n,n)

This command swaps the step and direction pinout of two axes of your choice. X=0, Y=1, Z=2, A=3, B=4, C=5 and Spindle=6. For example: ''SwapAxis(0,1)'' will swap the X and Y axis. From here on any programed move or jog of the X-axis will actually move the Y axis. Please note that it is ONLY the pinout that is swapped! The effect is just as if you opend Config->Ports&Pins and changed the pinout there or swapped the wires at your break-out-board or drives. The motortuning values does not "follow" the axis. Be careful with this, if you exit Mach3 after issuing a SwapAxis() the swapped pinout will be saved in the .xml and will be in effect the next time you start Mach3.
This command can ONLY BE USED ONCE - you are not allowed to first swap X with Y and then later Y with B for example. To reset the swapped axes you must use the command ''ResetAxisSwap()''. After the swapped axes has been reset you are free to call SwapAxis() again.

'''Sub''' ResetAxisSwap()

This command resets a previous AxisSwap() call. It is the correct way to reset any swaped axes. Calling SwapAxis() a second time without calling ResetAxisSwap() is not allowed.

== Legacy and special system VB Script calls ==

The following functions are still available to writers of macro scripts at Release 1 of Mach3. Their general use is, however, deprecated as better and more general ways are available (usually by accessing a DRO or LED with the Get/Set routines) or they are aimed at internal systems use. They may be withdrawn or changed in subsequent revisions of the Mach software.

'''Sub''' CloseDigFile()

Close the digitize point file.

'''Function''' CommandedFeed() '''as''' Double

This will return the currently applicable feedrate (including any override.

'''Sub''' DisablePWM ()

Inhibit output of PWM spindle signal for Digispeed.

'''Sub''' DisableSignal (signal '''as''' Integer)

Disables operation of given signal.

'''Sub''' DoSpinCCW ()

Starts the spindle in a counterclockwise direction.

'''Sub''' DoSpinCW ()

Starts the spindle in a clockwise direction.

'''Sub''' DoSpinStop ()

Stops the spindle.

'''Sub''' EnablePWM ()

Enable output of PWM spindle signal for Digispeed.

'''Sub''' EnableSignal (signal '''as''' Integer)

Enables operation of given signal.

'''Function''' FeedRate() '''as''' Double

??? Anyone able to clarify which rate this is (blended, commanded, actual etc.)

'''Function''' GetABSPosition(axis '''as''' Byte) '''as''' Double

This will return the absolute machine coordinate of the given axis.

'''Function''' GetCurrentTool() '''as''' Integer

Returns the number of the currently active tool (i.e. after G43 executed)

'''Function''' GetIJMode() '''as''' Integer

Returns 0 for Absolute mode, 1 for Incremental mode.

'''Function''' GetRPM() '''as''' Double

This will return the actual speed of the spindle as measured by the Index sensor (if fitted).

'''Function''' GetSafeZ() '''as''' Double

This will return the current Safe_z in Machine coordinates to the VB routine.

'''Function''' GetScale(Axis '''as''' Integer) '''as''' Double

Returns the scale factor for the given axis.

'''Function''' GetSelectedTool() '''as''' Byte

Will return tool selected but not yet activated.

'''Function''' GetToolChangeStart(Axis '''as''' Byte) '''as''' Double

Will return the position of an axis when a toolchange was called for.

'''Sub''' GotoSafeZ ()

Will move to the absolute Z coordinate specified in the Safe_Z DRO.

'''Function''' MaxX() '''as''' Double
'''Function''' MaxY() '''as''' Double
'''Function''' MinX() '''as''' Double
'''Function''' MinY() '''as''' Double

??? Anyone able to document these please

'''Sub''' Message( text '''as''' String)

Writes the string, which should have only one line, in the Error intelligent label and history. Equivalent to executingbCode "MSG," & text

'''Sub''' OpenDigFile()

Open a digitize point cloud file. User is prompted for filename.

'''Function''' QueueDepth() '''as''' Byte

Depth of planner queue is returned.

'''Function''' Random() '''as''' Double

Returns a pseudo random number.

'''Sub''' RefCombination(Axes '''as''' Integer)

Performs simultaneous referencing on several axes. They are coded by ORing or addition of the following codes: X = 1, Y= 2, Z = 4, A = 8, B = 16 and C = 32.

'''Sub''' ResetTHC()

Resets the Torch Height Control code

'''Function''' RetractMode() '''as''' Integer

??? Anyone able to define this function please

'''Function''' Round() '''as''' Double
'''Function''' roun() '''as''' Double

??? Anyone able to detail these functions please

'''Sub''' RunFile ()

Executes the currently loaded G-code file.

'''Sub''' SetCurrentTool(Tool '''as''' Byte)

Will return currently selected tool

'''Sub''' SetFeedRate(Rate '''as''' Double)

Sets current FeedRate

'''Sub''' SetSpinSpeed(SWord '''as''' Double)

Sets current speed as by using the S word

'''Sub''' SetMachZero(Axis '''as''' Integer)

Defines the current position of the specified axis to be machine zero.

'''Sub''' SetIJAbs()
'''Sub''' SetIJInc()
These will set the IJ mode to absolute and incremental respectively

'''Sub''' SetIJMode(mode '''as''' Integer)

This will set the IJ mode to Absolute if mode = 0 and Incremental if mode = 1

'''Sub''' SetOutput (val '''as''' Integer)

??? Can anyone define function of this routine please

'''Sub''' SetPulley( PulleyNo '''as''' integer)

Sets a new value for the current pulley. PulleyNo should be in range 1 through 4

'''Sub''' SetSafeZ(SafeZ '''as''' Double)

This will set the Safe_Z which should be in Machine coordinates

'''Sub''' SetScale(Axis '''as''' Integer, Scale '''as''' Double)

Sets the given scale factor for the given axis.

'''Sub''' SingleVerify(Axis '''as''' Integer)

Do a "silent" verification run on one axis not reporting the outcome, just correcting the axis position.

'''Sub''' SingleVerifyReport(Axis '''as''' Integer)

Do a normal verification run on one axis reporting any discrepancy.

'''Sub''' StraightFeed(x '''as''' Double, y '''as''' Double, z '''as''' Double ,
a '''as''' Double, b '''as''' Double, c '''as''' Double)

This will perform a feedrate move to X1,Y2,Z3…etc.

'''Sub''' StraightTraverse(x '''as''' Double, y '''as''' Double, z '''as''' Double ,
a '''as''' Double, '''b''' as Double, '''c''' as Double)
Performs a rapid move to x, y, z etc.

'''Sub''' THCOn()

Turn on THC control

'''Sub''' THCOff()

Turn off THC control.

'''Function''' ToolLengthOffset() '''as''' Double

Gets the tool offset length currently in effect if any.

'''Function''' tXStart() '''as''' Double
'''Function''' tZStart() '''a'''s Double
'''Function''' tEndX() '''as''' Double
'''Function''' tEndZ() '''as''' Double
'''Function''' tFirstPass() '''as''' Double
'''Function''' InFeeds() '''as''' Double
'''Function''' ThreadDepth() '''as''' Double
'''Function''' GetMinPass() '''as''' Double
'''Function''' tMinDepth() '''as''' Double
'''Function''' tGetCutType() '''as''' Double
'''Function''' tCutDepth() '''as''' Double

'''Function''' tGetInfeedType() '''as''' Double

'''Function''' tClearX() '''as''' Double
'''Function''' tZClear() '''as''' Double

'''Function''' tLead() '''as''' Double
'''Function''' tSpring() '''as''' Byte
'''Function''' tPasses() '''as''' Byte
'''Function''' tChamfer() '''as''' Double
'''Function''' tTaper() '''as''' Double
'''Function''' tTapers() '''as''' Double
'''Function''' tInFeed() '''as''' Double
'''Function''' tDepthLastPass() '''as''' Double

'''Sub''' tSetCutType (type '''as''' Integer)
'''sub''' tSetInFeedType (type '''as''' Integer)

Gets/Sets parameters defined in a G76 threading cycle call for use by the canned cycle Script.

'''Sub''' VerifyAxis(Silent '''as''' Boolean)

Do a verification run. If silent is true, do not report the outcome, just correct the axis position.

'''Sub''' ZeroTHC ()

ZeroTHC clears the THC correction value so new correction may be done within THC's limits.