Functions | |
| int | TEST_2_tools_cycle () |
| Informs that a cycle is using two tools at same time such as Balanced Roughing and Balanced Finishing. | |
| int | TEST_cancel_transformation () |
| test if TRANSFO (TRANSLATION,...) is cancelled. In this case, it does not precede a call. Useful in EDM when the translation performs a movement. | |
| int | TEST_change_cycle () |
| cycle change at OPERATION_BEGIN ? CONST_NO for sub-cycles other than the first one. When you program, you can select multiple geometries, the first one is this cycle, and the others are sub-cycles. CONST_NO for 2nd OPERATION_BEGIN call in blocks call. When the cycle changes, you will get CONST_YES Important change : Until version 6.10, this function returned CONST_YES for a sub program call. <>To know if a cycle is a sub program call, use ICALL(TEST_internal_spm_call) | |
| int | TEST_change_plane () |
| plane change ? (different number) OPERATION_BEGIN : CONST_YES if new plane number. OPERATION_END, SPECIFIC_END : CONST_YES only at the end of plane use (only once, even with techno cycles) CONST_YES on OPERATION_END between subprograms calls in ABC rotation. CONST_YES in case of operations in same plane but with different origins (ie : G55 -> G56) | |
| int | TEST_change_primary () |
| change primary angle It is used for 4-axis and 5-axis Milling machines, when you edit the Machine - Work Holding Device - Rotary Axis , you can find the rotation models such as: BA, CB, CA, etc. The first letter of the model is primary, In TurnMill, the primary is C angle. CONST_YES for change primary angle | |
| int | TEST_change_secondary () |
| change secondary angle It is used for 5-axis Milling machines, when you edit the Machine - Work Holding Device - Rotary Axis , you can find the rotation models such as: BA, CB, CA, etc. The second letter of the model is secondary, In TurnMill, you may find in Machine - Kinematics by channel - Second rotary axis, Type A or Type B is the secondary ; CONST_YES for change secondary angle | |
| int | TEST_change_tool () |
| tool change ? (different number) OPERATION_BEGIN : CONST_YES if new tool number. OPERATION_END, SPECIFIC_END : CONST_YES only when tool completes (only once, even with techno cycles) CONST_YES also on last cycle | |
| int | TEST_change_tool_indexing () |
| change tool index in spindle you can activate the Invert by selecting the geometry. CONST_YES for change tool index in spindle, for example ,activate the Invert or cancel the invert. This option has changed from the previous cycle. | |
| int | TEST_change_tool_pocket () |
| tool poste or index change ? It points to the tool and recognizes the tool change even if there are multiple tools on one tool number. For example, if a machine tool number is equipped with a tool holder with multiple pockets, one tool number corresponds to multiple tools | |
| int | TEST_change_tool_pocket_turret () |
| tool poste or index change according to current trl ? | |
| int | TEST_change_tool_turret () |
| tool change according to current trl ? (different number) | |
| int | TEST_conical_thread () |
| conical or circular threading detected at OPERATION_BEGIN In turning cycle, threading for conical, Profile thread, | |
| int | TEST_corner_next () |
| EDM link with following element ? | |
| int | TEST_corner_prev () |
| EDM link with previous element ? | |
| int | TEST_cycle_end () |
| end of last sub_cycle of current cycle, on OPERATION_END CONST_NO for sub-cycles other than the last one. CONST_YES for other cases | |
| int | TEST_cycle_fictive () |
| Blocks output info deactivated by PPG (OPERATION_BEGIN call to prepare tool before SPG writing) (blocks deactivated for multi-holes processing) | |
| int | TEST_cycle_spindle () |
| Informs at OPERATION_BEGIN, whether a subprogram call has to be prepared. This means that the machining toolpath will not be called immediately afterwards; a subprogram call will be made. Operation Copy to get subprogram,. | |
| int | TEST_cycle_turret () |
| CONST_YES if some cycles are affect to the current program. | |
| int | TEST_exist_channel (int canal) |
| cycle present on canal in operations list ? | |
| int | TEST_exist_milling () |
| milling cycle present in operations list ? In TurnMill, all cycles are turning, you well get CONST_NO; CONST_YES: One or more Milling cycle is present. in Milling, always get CONST_YES | |
| int | TEST_exist_parting () |
| parting cycle present in operations list ? | |
| int | TEST_exist_rework_spindle () |
| cycle exists on reworking spindle ? Usually applied to MillTurn and SwissTurn, when it has parting or has no parting, the starting or ending block is different. detected at OutputEndChannel ; OutputStartChannel | |
| int | TEST_exist_start_plane () |
| machining present on starting plane | |
| int | TEST_exist_turret (int Itrl, int Btrl0) |
| cycle present on turret numtrl in operations list ? | |
| int | TEST_exist_turret2 () |
| ORDO. | |
| int | TEST_first_evol () |
| first evolution point of sub-cycle ? (POINT) | |
| int | TEST_first_hole () |
| first hole ? (DRILLING,...) When you use a canned cycle, one or more holes are selected in a cycle, find the first hole. you can use it in PROCEDURE CycleDrillingCommonBegin | |
| int | TEST_first_roughing () |
| first roughing (in case of pocket) ? | |
| int | TEST_first_tool_edm () |
| first edm tool ? (OPERATION_BEGIN) | |
| int | TEST_first_tool_milling () |
| first milling tool ? (OPERATION_BEGIN) A milling tool is used in multiple cycles, it will help you find the first cycle to use the milling tool. | |
| int | TEST_first_tool_turning () |
| first turning tool ? (OPERATION_BEGIN) | |
| int | TEST_first_turret_tool () |
| first tool on current trl ? (OPERATION_BEGIN) In the specified turret, it can find the first cycle of this TURRET. | |
| int | TEST_hole_cycle () |
| turning or milling hole cycle type ? (or broaching) | |
| int | TEST_internal_spm_call () |
| Informs at OPERATION_BEGIN and OPERATION_END if it's beetween sub-program calls (decomposed or not) CONST_NO on first OPERATION_BEGIN and last OPERATION_END some retracts or init can be omitted in this case. | |
| int | TEST_last_cycle (int Btrl) |
| last operation according to channel ? In Milling only CONST_NO is working It is more used for Operation_End | |
| int | TEST_last_evol () |
| last evolution point of sub-cycle ? (POINT) | |
| int | TEST_last_hole () |
| last hole ? (DRILLING,...) only with rotating tools | |
| int | TEST_last_rapg80 () |
| last retraction in this sub-cycle ? ( CYCLE_DRILLING_CANCEL) When multiple holes are selected in a cycle, it finds the last one. It is used for OutputDrillingCancel | |
| int | TEST_last_return () |
| last return point of sub-cycle ? (RET_...) | |
| int | TEST_last_tool () |
| last tool according to channel ? | |
| int | TEST_latest_cycle (int Bnext, int Bcanal, int Bchuck, int Btrl) |
| last cycle according to turret, chuck, channel ? ignoring techno cycles | |
| int | TEST_leadin_arc () |
| leadin/leadout arc ? (CRCL in particular case) for procedures APPROACH_PLANE, RETURN_PLANE, ... approach : READ_PATH_point : point destination (apres arc entree) READ_PATH_point_start : point intermediaire (depart arc entree) retour : READ_PATH_point : point destination (point de retour) READ_PATH_point_inter : point intermediaire (fin arc sortie) caracteristiques arc : READ_PATH_center, READ_PATH_radius, READ_PATH_direction, .. V5.9 : this function is available on CRCL procedure. | |
| int | TEST_machine_pattern () |
| patterns table defined in MCG file or not ? | |
| int | TEST_milling_cycle () |
| milling cycle ? In Turnmill, determine if it is a milling cycle. It is commonly used in Operation_Begin | |
| int | TEST_modif_plane () |
| change primary angle or secondary angle there must be an angle change to be considered a plane change. Note: The default plane of GO2cam is empty, and the first cycle is the change from empty to having a plane, which is also a plane change. | |
| int | TEST_MTE_activated () |
| working with MTE or not ? | |
| int | TEST_MTE_call () |
| MTE simulation is running ? | |
| int | TEST_multax () |
| READ_PATH_point_5axis must be used if return is yes return : CONST_YES CONST_NO. | |
| int | TEST_NCcontrol_activated () |
| CONST_YES if informations for NC check have to be output. | |
| int | TEST_new_main_pattern (int Idsync) |
| main code pattern is not the same taht current one ? | |
| int | TEST_next_approach_point (double *Pt) |
| approaches same point on following sub-cycle ? (useful in return to avoid wire_cutting) | |
| int | TEST_part_in_chuck (int Ichuck) |
| part is in chuck , used at start | |
| int | TEST_part_return () |
| returning cycle present in operations list ? In turning, you can do part manipulation, CONST_YES: In the machining tree, there is either part rework or part return CONST_NO: In the machining tree, there is no part rework or part return | |
| int | TEST_part_return_next () |
| RETOURN_PIECE or REPRISE_PIECE techno cycle immediately follows. (allows retraction at OPERATION_END) | |
| int | TEST_parting_cycle () |
| Used in turning to know if cycle is PARTING. | |
| int | TEST_parting_rework_cycle () |
| Used in turning to know if cycle is PARTING and next cycle is REWORK you can find it in FUNCTION IsPartingReworkOperation. | |
| int | TEST_path_edm_conic () |
| test if EDM toolpath with constant taper and conical radius | |
| int | TEST_path_edm_iso () |
| test if EDM toolpath with constant taper and radius of ISO type | |
| int | TEST_path_edm_taper () |
| test if EDM toolpath with constant taper and conical radius | |
| int | TEST_path_in_inch () |
| test if toolpath movment are in INCH or not | |
| int | TEST_path_modified () |
| Test if the initial toolpath has been modified. The modification can be a techno user function, or a point generated by collision management. This test is mainly useful for toolpath macros, if you want to replace movements by a NC cycle. (the GO2cam cycles are automatically decomposed when the toolpath is modified). | |
| int | TEST_paxis3_invers () |
| PAX3 coordinates in opposite to GO2cam plane ? (WRITE_NC_init_plane inverse normal vector of plane ?) | |
| int | TEST_paxis3_orthognal () |
| PAX3 coordinates in opposite to GO2cam plane ? (WRITE_NC_init_plane changes normal vector of plane ?) | |
| int | TEST_paxis3_recalculate () |
| PAX3 coordinates affected by plane recalculation ? | |
| int | TEST_plane_fictiv () |
| detect if plane is not created by GO2cam (sub-routines) | |
| int | TEST_point_evol () |
| evolution point of sub-cycle ? (POINT) | |
| int | TEST_pplane_recalculate () |
| plane coordinates affected by plane recalculation ? | |
| int | TEST_probing_cycle () |
| probe cycle ? | |
| int | TEST_rapg80_down () |
| CycleDrillingCancel to move lower pilot hole ? accessible on previous hole in V4.4 CONST_YES After jumping, the next hole becomes low. OR a hole at high elevations to a hole at low elevations. | |
| int | TEST_rapg80_jump () |
| CycleDrillingCancel used to jump obstacles ? ( CONST_YES on the 2 points ) accessible on previous hole in V4.4 return : CONST_YES CONST_NO. | |
| int | TEST_rapg80_up () |
| CycleDrillingCancel to climb higher pilot hole ? accessible on previous hole in V4.4 return : CONST_YES CONST_NO. | |
| int | TEST_secondary_move () |
| Test if secondary is moving or not on toolpath with multax treatment return : CONST_YES CONST_NO. | |
| int | TEST_select_integer_tec (int Btyp, int Bclef, int Ival) |
| select tool, machine, DPP file structure index to access lit_xTEC, ldppxxx, edppxxx data. (CONST_YES if OK) | |
| int | TEST_select_spm (int Indice) |
| select nth SPG sub-cycle, to access starting and ending points (useful for EDM). | |
| int | TEST_select_string_tec (int Btyp, int Bclef, const std::string &Sval) |
| select tool, machine, DPP file structure index to access lit_xTEC, ldppxxx, edppxxx data. (CONST_YES if OK) You can find it in PROCEDURE Origin | |
| int | TEST_select_tec (int Btyp, int Indice) |
| select tool, machine, DPP file structure index to access lit_xTEC, ldppxxx, edppxxx data. (CONST_YES if OK) | |
| int | TEST_spm_call () |
| Informs at OPERATION_BEGIN, whether a subprogram call has to be prepared. This means that the machining toolpath will not be called immediately afterwards; a subprogram call will be made. The tool call, thus, remains outside the subprogram. Operation Copy to get subprogram, TEST_cycle_spindle can also be used. | |
| int | TEST_stock_change () |
| stock change, only available with dental application | |
| int | TEST_stock_pocket () |
| pocket present in stock profile ? Used for roughing cycles in turning. Some machines cannot carry out canned roughing if there is a pocket in the stock ( NUM ) | |
| int | TEST_synchro_pattern (int Idsync) |
| a pattern is defined on synchro or not ? | |
| int | TEST_tangent_next () |
| element tangent to following one ? | |
| int | TEST_tangent_prev () |
| element tangent to previous one ? | |
| int | TEST_text_nc_cycle () |
| techno cycle with NC blocs ? in this case, only nc bloks need to be output | |
| int | TEST_tool_end () |
| tool job is finish ? (end of last cycle with this tool) The same tool processes multiple cycles, at the same time, the cycles are continuous. It will find the last of these consecutive cycles. OPERATION_END, SPECIFIC_END : | |
| int | TEST_tool_pocket_opposite () |
| is turning tool opposite used ? (OKUMA MULTUS,...) | |
| int | TEST_tool_turret_B180 () |
| is tool selected with B180 position for turret on Baxis | |
| int | TEST_tool_type (int Btyp, int Bout) |
| particular type tool ? useful in turning with Rotary Tool for following type of tool | |
| int | TEST_toolpath_modif () |
| CONST_YES, when you use Contouring,Zrepeat Facing, ZREPEAT POCKET, TAPER CUTTING;. | |
| int | TEST_turn_cycle_b () |
| to know if turning cycle is using Baxis. In GO2cam Baxis Turning you can only find it in continuous B turning | |
| int | TEST_turn_cycle_c () |
| to know if turning cycle is using Caxis (and not spindle rotation). In GO2cam Caxis Turning you can only find it in eccentric turning | |
| int | TEST_turn_cycle_y () |
| to know if turning cycle is using Yaxis. In GO2cam Yaxis Turning you can only find it in Parting or eccentric turning | |
| int | TEST_turning_cycle () |
| In Turnmill or SwissMill, let you know if it's a turning cycle. It is commonly used in Operation_Begin. | |
| int | TEST_type_cycle (int Btyp, int Bcyc) |
| particular type cycle ? useful in turning with RT for following type of cycle useful in milling for controlling facing tools | |
| int | TEST_wire_thread () |
| presence of ENFILE_FIL techno function on sub-cycle ? | |
| int | TYPE_next_cycle (int Bnext, int Bcanal, int Bchuck, int Btrl) |
| type opf next cycle according to turret, chuck, channel ? CONST_NO if last cycle or CONST_PARTING, CONST_CYC_TECHNO, ... | |
Tests
| int TEST_2_tools_cycle | ( | ) |
Informs that a cycle is using two tools at same time
such as Balanced Roughing and Balanced Finishing.
| int TEST_cancel_transformation | ( | ) |
test if TRANSFO (TRANSLATION,...) is cancelled.
In this case, it does not precede a call.
Useful in EDM when the translation performs a movement.
| int TEST_change_cycle | ( | ) |
cycle change at OPERATION_BEGIN ?
CONST_NO for sub-cycles other than the first one.
When you program, you can select multiple geometries,
the first one is this cycle, and the others are sub-cycles.
CONST_NO for 2nd OPERATION_BEGIN call in blocks call.
When the cycle changes, you will get CONST_YES
Important change : Until version 6.10, this function returned CONST_YES for a sub program call. <>To know if a cycle is a sub program call, use ICALL(TEST_internal_spm_call)
| int TEST_change_plane | ( | ) |
plane change ? (different number)
OPERATION_BEGIN :
CONST_YES if new plane number.
OPERATION_END, SPECIFIC_END :
CONST_YES only at the end of plane use
(only once, even with techno cycles)
CONST_YES on OPERATION_END between subprograms calls in ABC rotation.
CONST_YES in case of operations in same plane but with different origins (ie : G55 -> G56)
| int TEST_change_primary | ( | ) |
change primary angle
It is used for 4-axis and 5-axis Milling machines,
when you edit the Machine - Work Holding Device - Rotary Axis ,
you can find the rotation models such as: BA, CB, CA, etc.
The first letter of the model is primary,
In TurnMill, the primary is C angle.
CONST_YES for change primary angle
| int TEST_change_secondary | ( | ) |
change secondary angle
It is used for 5-axis Milling machines,
when you edit the Machine - Work Holding Device - Rotary Axis ,
you can find the rotation models such as: BA, CB, CA, etc.
The second letter of the model is secondary,
In TurnMill, you may find in Machine - Kinematics by channel - Second rotary axis,
Type A or Type B is the secondary ;
CONST_YES for change secondary angle
| int TEST_change_tool | ( | ) |
tool change ? (different number)
OPERATION_BEGIN :
CONST_YES if new tool number.
OPERATION_END, SPECIFIC_END :
CONST_YES only when tool completes
(only once, even with techno cycles)
CONST_YES also on last cycle
| int TEST_change_tool_indexing | ( | ) |
change tool index in spindle
you can activate the Invert by selecting the geometry.
CONST_YES for change tool index in spindle,
for example ,activate the Invert or cancel the invert.
This option has changed from the previous cycle.
| int TEST_change_tool_pocket | ( | ) |
tool poste or index change ?
It points to the tool and recognizes the tool change
even if there are multiple tools on one tool number.
For example, if a machine tool number is equipped with a tool holder with multiple pockets,
one tool number corresponds to multiple tools
| int TEST_change_tool_pocket_turret | ( | ) |
tool poste or index change according to current trl ?
| int TEST_change_tool_turret | ( | ) |
tool change according to current trl ? (different number)
| int TEST_conical_thread | ( | ) |
conical or circular threading detected at OPERATION_BEGIN
In turning cycle, threading for conical, Profile thread,
| int TEST_corner_next | ( | ) |
EDM link with following element ?
| int TEST_corner_prev | ( | ) |
EDM link with previous element ?
| int TEST_cycle_end | ( | ) |
end of last sub_cycle of current cycle, on OPERATION_END
CONST_NO for sub-cycles other than the last one.
CONST_YES for other cases
| int TEST_cycle_fictive | ( | ) |
Blocks output info deactivated by PPG
(OPERATION_BEGIN call to prepare tool before
SPG writing)
(blocks deactivated for multi-holes processing)
| int TEST_cycle_spindle | ( | ) |
Informs at OPERATION_BEGIN, whether a subprogram call
has to be prepared.
This means that the machining toolpath will not be called
immediately afterwards; a subprogram call will be made.
Operation Copy to get subprogram,.
| int TEST_cycle_turret | ( | ) |
CONST_YES if some cycles are affect to the current program.
| int TEST_exist_channel | ( | int | canal | ) |
cycle present on canal in operations list ?
| int TEST_exist_milling | ( | ) |
milling cycle present in operations list ?
In TurnMill, all cycles are turning, you well get CONST_NO;
CONST_YES: One or more Milling cycle is present.
in Milling, always get CONST_YES
| int TEST_exist_parting | ( | ) |
parting cycle present in operations list ?
| int TEST_exist_rework_spindle | ( | ) |
cycle exists on reworking spindle ?
Usually applied to MillTurn and SwissTurn,
when it has parting or has no parting,
the starting or ending block is different.
detected at OutputEndChannel ; OutputStartChannel
| int TEST_exist_start_plane | ( | ) |
machining present on starting plane
| int TEST_exist_turret | ( | int | Itrl, |
| int | Btrl0 ) |
cycle present on turret numtrl in operations list ?
| [in] | Itrl | turret number (1...n) |
| [in] | Btrl0 | cycles on turret 0 (all turrets) allowed |
| int TEST_exist_turret2 | ( | ) |
| int TEST_first_evol | ( | ) |
first evolution point of sub-cycle ? (POINT)
| int TEST_first_hole | ( | ) |
first hole ? (DRILLING,...)
When you use a canned cycle, one or more holes are selected in a cycle,
find the first hole.
you can use it in PROCEDURE CycleDrillingCommonBegin
| int TEST_first_roughing | ( | ) |
first roughing (in case of pocket) ?
| int TEST_first_tool_edm | ( | ) |
first edm tool ? (OPERATION_BEGIN)
| int TEST_first_tool_milling | ( | ) |
first milling tool ? (OPERATION_BEGIN)
A milling tool is used in multiple cycles,
it will help you find the first cycle to use the milling tool.
| int TEST_first_tool_turning | ( | ) |
first turning tool ? (OPERATION_BEGIN)
| int TEST_first_turret_tool | ( | ) |
first tool on current trl ? (OPERATION_BEGIN)
In the specified turret, it can find the first cycle of this TURRET.
| int TEST_hole_cycle | ( | ) |
turning or milling hole cycle type ? (or broaching)
| int TEST_internal_spm_call | ( | ) |
Informs at OPERATION_BEGIN and OPERATION_END
if it's beetween sub-program calls (decomposed or not)
CONST_NO on first OPERATION_BEGIN and last OPERATION_END
some retracts or init can be omitted in this case.
| int TEST_last_cycle | ( | int | Btrl | ) |
last operation according to channel ?
In Milling only CONST_NO is working
It is more used for Operation_End
| [in] | Btrl | CONST_YES: Automatically finds the last cycle of each channel. CONST_NO: Automatically finds the last cycle of the machining tree. |
| int TEST_last_evol | ( | ) |
last evolution point of sub-cycle ? (POINT)
| int TEST_last_hole | ( | ) |
last hole ? (DRILLING,...) only with rotating tools
| int TEST_last_rapg80 | ( | ) |
last retraction in this sub-cycle ? ( CYCLE_DRILLING_CANCEL)
When multiple holes are selected in a cycle,
it finds the last one.
It is used for OutputDrillingCancel
| int TEST_last_return | ( | ) |
last return point of sub-cycle ? (RET_...)
| int TEST_last_tool | ( | ) |
| int TEST_latest_cycle | ( | int | Bnext, |
| int | Bcanal, | ||
| int | Bchuck, | ||
| int | Btrl ) |
last cycle according to turret, chuck, channel ? ignoring techno cycles
| [in] | Bnext | only last sub-cycle is valid CONST_YES or CONST_NO |
| [in] | Bcanal | only cycle on current channel CONST_YES or CONST_NO |
| [in] | Bchuck | only cycle on current chuck CONST_YES or CONST_NO |
| [in] | Btrl | only cycle on current turret CONST_YES or CONST_NO |
| int TEST_leadin_arc | ( | ) |
leadin/leadout arc ? (CRCL in particular case)
for procedures APPROACH_PLANE, RETURN_PLANE, ...
approach :
READ_PATH_point : point destination (apres arc entree)
READ_PATH_point_start : point intermediaire (depart arc entree)
retour :
READ_PATH_point : point destination (point de retour)
READ_PATH_point_inter : point intermediaire (fin arc sortie)
caracteristiques arc :
READ_PATH_center, READ_PATH_radius, READ_PATH_direction, ..
V5.9 : this function is available on CRCL procedure.
| int TEST_machine_pattern | ( | ) |
patterns table defined in MCG file or not ?
| int TEST_milling_cycle | ( | ) |
milling cycle ?
In Turnmill, determine if it is a milling cycle.
It is commonly used in Operation_Begin
| int TEST_modif_plane | ( | ) |
change primary angle or secondary angle
there must be an angle change to be considered a plane change.
Note: The default plane of GO2cam is empty, and the first cycle is the change
from empty to having a plane, which is also a plane change.
| int TEST_MTE_activated | ( | ) |
| int TEST_MTE_call | ( | ) |
| int TEST_multax | ( | ) |
READ_PATH_point_5axis must be used if return is yes
return : CONST_YES CONST_NO.
| int TEST_NCcontrol_activated | ( | ) |
CONST_YES if informations for NC check have to be output.
| int TEST_new_main_pattern | ( | int | Idsync | ) |
main code pattern is not the same taht current one ?
| [in] | Idsync | synchro index (1,...) or 0 |
| int TEST_next_approach_point | ( | double * | Pt | ) |
approaches same point on following sub-cycle ?
(useful in return to avoid wire_cutting)
| [in] | Pt | point courant |
| int TEST_part_in_chuck | ( | int | Ichuck | ) |
part is in chuck , used at start
| [in] | Ichuck | 1 or 2:chuck number |
| int TEST_part_return | ( | ) |
returning cycle present in operations list ?
In turning, you can do part manipulation,
CONST_YES: In the machining tree, there is either part rework or part return
CONST_NO: In the machining tree, there is no part rework or part return
| int TEST_part_return_next | ( | ) |
RETOURN_PIECE or REPRISE_PIECE techno cycle
immediately follows. (allows retraction at OPERATION_END)
| int TEST_parting_cycle | ( | ) |
Used in turning
to know if cycle is PARTING.
| int TEST_parting_rework_cycle | ( | ) |
Used in turning
to know if cycle is PARTING and next cycle is REWORK
you can find it in FUNCTION IsPartingReworkOperation.
| int TEST_path_edm_conic | ( | ) |
test if EDM toolpath with constant taper and conical radius
| int TEST_path_edm_iso | ( | ) |
test if EDM toolpath with constant taper and radius of ISO type
| int TEST_path_edm_taper | ( | ) |
test if EDM toolpath with constant taper and conical radius
| int TEST_path_in_inch | ( | ) |
test if toolpath movment are in INCH or not
| int TEST_path_modified | ( | ) |
Test if the initial toolpath has been modified.
The modification can be a techno user function,
or a point generated by collision management.
This test is mainly useful for toolpath macros,
if you want to replace movements by a NC cycle.
(the GO2cam cycles are automatically decomposed
when the toolpath is modified).
| int TEST_paxis3_invers | ( | ) |
PAX3 coordinates in opposite to GO2cam plane ?
(WRITE_NC_init_plane inverse normal vector of plane ?)
| int TEST_paxis3_orthognal | ( | ) |
PAX3 coordinates in opposite to GO2cam plane ?
(WRITE_NC_init_plane changes normal vector of plane ?)
| int TEST_paxis3_recalculate | ( | ) |
PAX3 coordinates affected by plane recalculation ?
| int TEST_plane_fictiv | ( | ) |
detect if plane is not created by GO2cam (sub-routines)
| int TEST_point_evol | ( | ) |
evolution point of sub-cycle ? (POINT)
| int TEST_pplane_recalculate | ( | ) |
plane coordinates affected by plane recalculation ?
| int TEST_probing_cycle | ( | ) |
| int TEST_rapg80_down | ( | ) |
CycleDrillingCancel to move lower pilot hole ?
accessible on previous hole in V4.4
CONST_YES After jumping, the next hole becomes low.
OR a hole at high elevations to a hole at low elevations.
| int TEST_rapg80_jump | ( | ) |
CycleDrillingCancel used to jump obstacles ?
( CONST_YES on the 2 points )
accessible on previous hole in V4.4
return : CONST_YES CONST_NO.
| int TEST_rapg80_up | ( | ) |
CycleDrillingCancel to climb higher pilot hole ?
accessible on previous hole in V4.4
return : CONST_YES CONST_NO.
| int TEST_secondary_move | ( | ) |
Test if secondary is moving or not on toolpath with multax treatment
return : CONST_YES CONST_NO.
| int TEST_select_integer_tec | ( | int | Btyp, |
| int | Bclef, | ||
| int | Ival ) |
select tool, machine, DPP file structure index to access
lit_xTEC, ldppxxx, edppxxx data. (CONST_YES if OK)
| [in] | Btyp | TEC_PPCOM_FORMAT DPP comments' format TEC_PPCYCLE DPP cycle comments TEC_PPCOD_FEED DPP feeds codes TEC_PPCOD_SPEED DPP speeds codes TEC_PPCOD_ARRO codes arrosage DPP TEC_PPCOD_GAMME DPP spindle speed range code TEC_PPPLAN DPP planes processing |
| [in] | Bclef | integer key (GPP_INTEGER_PLANE_NO,...) |
| [in] | Ival | value searched for Bclef |
| int TEST_select_spm | ( | int | Indice | ) |
select nth SPG sub-cycle,
to access starting and ending points (useful for EDM).
| [in] | Indice | 0 for not taking 1...n into account in 1..der to select a particular sub-cycle. |
| int TEST_select_string_tec | ( | int | Btyp, |
| int | Bclef, | ||
| const std::string & | Sval ) |
select tool, machine, DPP file structure index to access
lit_xTEC, ldppxxx, edppxxx data. (CONST_YES if OK)
You can find it in PROCEDURE Origin
| [in] | Btyp | TEC_PPCLEF (it is point to GPP - Keys) |
| [in] | Bclef | reference string key (GPP_STRING_KEY,...) |
| [in] | Sval | string searched for Bclef |
| int TEST_select_tec | ( | int | Btyp, |
| int | Indice ) |
select tool, machine, DPP file structure index to access
lit_xTEC, ldppxxx, edppxxx data. (CONST_YES if OK)
| [in] | Btyp | TEC_ATTACHE tool holder TEC_TOURELLE machine turret TEC_OUTFIX machine fixed tool TEC_JAUGE machine gauge TEC_PUNTOLE sheet metal TEC_PPCLEF DPP address letter TEC_PPCYCLE DPP cycle processing TEC_PPAUX_G DPP G group TEC_PPAUX_M DPP M group TEC_PPCOD_FEED DPP feeds codes TEC_PPCOD_SPEED DPP speeds codes TEC_PPCOD_GAMME DPP spindle speed range code TEC_PPCOM_FORMAT DPP comments' format TEC_PPCOM_ENTETE DPP header comments TEC_PPCOM_DEBUT DPP start comments TEC_PPCOM_CYCLE DPP cycle comments TEC_PPCOM_OUTIL DPP tool comments TEC_PPCOD_ARRO DPP coolant codes TEC_PPPLAN DPP planes processing TEC_PPCOM_LISOUT tools list header comments TEC_PPCOL_LISOUT tools list columns definition |
| [in] | Indice | element's index (0,...) except turret (1,...) |
| int TEST_spm_call | ( | ) |
Informs at OPERATION_BEGIN, whether a subprogram call
has to be prepared.
This means that the machining toolpath will not be called
immediately afterwards; a subprogram call will be made.
The tool call, thus, remains outside the subprogram.
Operation Copy to get subprogram,
TEST_cycle_spindle can also be used.
| int TEST_stock_change | ( | ) |
stock change, only available with dental application
| int TEST_stock_pocket | ( | ) |
pocket present in stock profile ?
Used for roughing cycles in turning.
Some machines cannot carry out canned roughing
if there is a pocket in the stock ( NUM )
| int TEST_synchro_pattern | ( | int | Idsync | ) |
a pattern is defined on synchro or not ?
| [in] | Idsync | synchro index (1,...) or 0 If Idsync is null, test if there is one synchro with pattern in opelist |
| int TEST_tangent_next | ( | ) |
element tangent to following one ?
| int TEST_tangent_prev | ( | ) |
element tangent to previous one ?
| int TEST_text_nc_cycle | ( | ) |
techno cycle with NC blocs ?
in this case, only nc bloks need to be output
| int TEST_tool_end | ( | ) |
tool job is finish ? (end of last cycle with this tool)
The same tool processes multiple cycles,
at the same time, the cycles are continuous.
It will find the last of these consecutive cycles.
OPERATION_END, SPECIFIC_END :
| int TEST_tool_pocket_opposite | ( | ) |
is turning tool opposite used ? (OKUMA MULTUS,...)
| int TEST_tool_turret_B180 | ( | ) |
is tool selected with B180 position for turret on Baxis
| int TEST_tool_type | ( | int | Btyp, |
| int | Bout ) |
particular type tool ?
useful in turning with Rotary Tool for following type of tool
| [in] | Btyp | CONST_TURNING CONST_CYCLE_MILLING CONST_EDM_CYCLE |
| [in] | Bout | read BOOLEAN_TOOL_TYPE |
| int TEST_toolpath_modif | ( | ) |
CONST_YES, when you use Contouring,Zrepeat Facing, ZREPEAT POCKET, TAPER CUTTING;.
| int TEST_turn_cycle_b | ( | ) |
to know if turning cycle is using Baxis.
In GO2cam Baxis Turning you can only find it in continuous B turning
| int TEST_turn_cycle_c | ( | ) |
to know if turning cycle is using Caxis (and not spindle rotation).
In GO2cam Caxis Turning you can only find it in eccentric turning
| int TEST_turn_cycle_y | ( | ) |
to know if turning cycle is using Yaxis.
In GO2cam Yaxis Turning you can only find it in Parting or eccentric turning
| int TEST_turning_cycle | ( | ) |
In Turnmill or SwissMill, let you know if it's a turning cycle.
It is commonly used in Operation_Begin.
| int TEST_type_cycle | ( | int | Btyp, |
| int | Bcyc ) |
particular type cycle ?
useful in turning with RT for following type of cycle
useful in milling for controlling facing tools
| [in] | Btyp | CONST_TURNING CONST_CYCLE_MILLING CONST_CYCLE_3D_MILLING CONST_EDM_CYCLE |
| [in] | Bcyc | READ_PART_cycle_no |
| int TEST_wire_thread | ( | ) |
presence of ENFILE_FIL techno function on sub-cycle ?
| int TYPE_next_cycle | ( | int | Bnext, |
| int | Bcanal, | ||
| int | Bchuck, | ||
| int | Btrl ) |
type opf next cycle according to turret, chuck, channel ? CONST_NO if last cycle or CONST_PARTING, CONST_CYC_TECHNO, ...
| [in] | Bnext | if CONST_NO, function will return typ current cycle if not last sub-cycle |
| [in] | Bcanal | only cycle on current channel CONST_YES or CONST_NO |
| [in] | Bchuck | only cycle on current chuck CONST_YES or CONST_NO |
| [in] | Btrl | only cycle on current turret CONST_YES or CONST_NO |