PocketParameterData: Difference between revisions

From SDK
Jump to navigation Jump to search
No edit summary
Line 37: Line 37:
===.DoRamping===
===.DoRamping===
'''R/W - bool - If true ramp entry to pockets (always zig-zag)
'''R/W - bool - If true ramp entry to pockets (always zig-zag)


===.DoRasterClearance===
===.DoRasterClearance===
Line 46: Line 43:
'''Returns:''' (bool) if true we will do peck drilling
'''Returns:''' (bool) if true we will do peck drilling


===.Name===
R/W - string - The name for the toolpath


===.ProfilePassType===
R/W - integer - type of profile pass to perform . Valid values are ...
::PocketParameterData.PROFILE_NONE
::PocketParameterData.PROFILE_FIRST
::PocketParameterData.PROFILE_LAST


===.Name===
'''Interaction:''' Read and Write


'''Returns:''' (string) The name for the toolpath
'''Returns:''' (string) The name for the toolpath
Line 61: Line 62:


'''Returns:''' (double) distance above surface to retract to when peck drilling
'''Returns:''' (double) distance above surface to retract to when peck drilling


===.ProjectToolpath===
===.ProjectToolpath===
Line 69: Line 67:


'''Returns:''' (bool) If true and used with Aspire, toolpath is projected onto model surface after calculation
'''Returns:''' (bool) If true and used with Aspire, toolpath is projected onto model surface after calculation





Revision as of 21:03, 3 August 2021

Back.jpg

This object is used to hold the settings for a pocketing toolpath and also the clearance tool section of a flat bottomed v carving toolpath.

Constructor

ProfileParameterData() - Constructor

Create a new object ready to have its parameters set

For Example:

local pocket_data = PocketParameterData()() 

Properties

.Allowance

R/W - double - allowance to leave on pocket sides when calculating toolpath

.AllowanceFormula

R/W - string -Formula for allowance to leave on pocket sides when calculating toolpath

.CutDepth

R/W - double -Final cutting depth below start depth

.CutDepthFormula

R/W - string -Formula for cutting depth below start depth

.CutDirection

R/W - integer - Cutting direction for toolpath. Valid values are ...

ProfileParameterData.CLIMB_DIRECTION
ProfileParameterData.CONVENTIONAL_DIRECTION

Note: Direction constants use ProfileParameterData. NOT PocketParameterData.

.DoRamping

R/W - bool - If true ramp entry to pockets (always zig-zag)

.DoRasterClearance

R/W - bool - if true doing raster area clearance, else offset

Returns: (bool) if true we will do peck drilling

.Name

R/W - string - The name for the toolpath

.ProfilePassType

R/W - integer - type of profile pass to perform . Valid values are ...

PocketParameterData.PROFILE_NONE
PocketParameterData.PROFILE_FIRST
PocketParameterData.PROFILE_LAST


Returns: (string) The name for the toolpath



.PeckRetractGap

Interaction: Read and Write

Returns: (double) distance above surface to retract to when peck drilling

.ProjectToolpath

Interaction: Read and Write

Returns: (bool) If true and used with Aspire, toolpath is projected onto model surface after calculation


.StartDepth

Interaction: Read and Write

Returns: (double) Start depth for toolpath below material surface



.StartDepthFormula

Interaction: Interaction: Read and Write Returns: (string) Formula for start depth for toolpath below material surface

For Example:

    -- Create  object used to pass drilling options
    local drill_data = DrillParameterData() -- start depth for toolpath
    drill_data.StartDepth = start_depth                -- cut depth for toolpath this is depth below start depth
    drill_data.CutDepth = cut_depth                    -- if true perform peck drilling
    drill_data.DoPeckDrill = retract_gap > 0.0      -- distance to retract above surface when peck drilling
    drill_data.PeckRetractGap = retract_gap        -- if true in Aspire, project toolpath onto composite model
    drill_data.ProjectToolpath = false 
   
   
Back.jpg

References

Please Note: The base material for the contents found in this WiKi was sourced from Vectric Lua Interface for Gadgets, version 2.05, published September 12, 2018. by Vectric Ltd. Most current document from Vertric can be downloaded at Vertric Developer Information