Kongberg PentaCut configuration with ArtiosCAD.

tjd 7 June 2004

The Kongsberg PentaCut requires some material setup information to allow the operator
to see what tools are required.

A counter Output should be set up which uses Output command file

OUT_KONGSBERG_PENTA. This command file adds the appropriate %MAT
information. This output must use the driver “KGB”.

Counter Line Type Physical tool Physical tool P# - PCIQ

(Example 1) (Example 2) approach
With Grain channel 2 2 1
Cross Grain channel 4 2 2
Crease End tool 3 3 3
Periphery 1 1 4
Chamfer 5 5 5
With Grain full depth 3 3 6
Cross Grain full depth 3 3 7
Name tool 2 2 8
Position hole tool 3 4 9
Mill tool 4 2 10

There are many ways the tools may be laid out.

In Example 1 there are separate tools for each crease channel, the Crease end tool and the
Chamfer and Periphery tool. The Crease end tool is shared with the With and Cross ‘full
depth’ slot tool as well as being used to profile cut the position hole. The area Mill tool
function is shared with the Cross Grain channel tool.

In Example 2, a single shot Position hole tool is used, as well as a separate crease end
tool. It is thus necessary to share a tool for the two crease channels.

There are two ways that the counter output lines may be mapped to the PentaCut tools.
The normal ArtiosCAD “Plotting style” approach or the “PCIQ compatible” approach.

ArtiosCAD “Plotting style”

In the ArtiosCAD “Plotting style” approach, a Counter output should be set up in the
normal way, with the Plotting Style providing the map to the tools as they are set up in
the PentaCut. The tool numbers used in the Plotting Style will be used in the output file
(*.MAP or *.ACM). A %MAT section will also provide the tool information which will
is displayed in GCWIN.

The plotting style setup for the two examples would be as shown above.
The Advanced page should use the command file OUT_KONGSBERG_PENTA
 “PCIQ compatible” approach.
The PentaCut was first introduced while PCIQ was our current software offering. The
way PCIQ supported the PentaCut was to output counter lines using P codes to select the
logical tools (based on tool function). These are then mapped by the %MAT section of
the *.MAP file to the physical tools in use on your counter cutter. This does not provide
an easy way of redirecting these line types to particular (physical) tools. If this type of
output is required (for compatibility reasons), it will be necessary to provide a tool
mapping somewhere else.

The plotting style used (CAM.ARTIOS.PENTA), is a simple map between the line
functions and the “logical tools”.
The remapping is provided as a series of numbers on the Advanced page.

Counter Line Type Physical tool Physical tool P# - PCIQ

(Example 1) (Example 2) approach
With Grain channel 2 2 1
Cross Grain channel 4 2 2
Crease End tool 3 3 3
Periphery 1 1 4
Chamfer 5 5 5
With Grain full depth 3 3 6
Cross Grain full depth 3 3 7
Name tool 2 2 8
Position hole tool 3 4 9
Mill tool 4 2 10

Suppose the physical tools for each of these operations is per Example 1 above, the
settings on the Advanced Page of the Output should look like:-

If a layout per Example 2 were employed, the numbers should be:-

2 2 3 1 5 3 3 2 4 2.
Advantages and disadvantages.

The advantages of the ArtiosCAD Plotting style approach is that when outputting, the
tool size selections are limited by the way the tools are defined. Where tools are used in
different places, only one may be entered, and the remaining fields simply show the
duplicate value.

With the PCIQ approach, the fields are ‘free’ and it is therefore possible to make a
mistake.
In the case where the With and Cross Grain tools are shared, they must ALL be set to the
same value. However, in this case, almost certainly once tool size will be used in all
cases since you must Multi-pass the tool. This can then be set in defaults, elimination
some of this effort and potential for error.