Peddimat for Windows

Installation Guide

Version 1.3
Copyright (C) 2010 Peddinghaus Corp. All Rights Reserved # 2309109
2
TABLE OF CONTENTS PAGE

1. COMPUTER SYSTEM HARDWARE REQUIREMENTS 4

2. INSTALLATION 4

3. RUNNING PEDDIMAT 8

4. PART FILE COMPATIBILITY WITH DOS VERSIONS OF PEDDIMAT 9

5. COPE FILE COMPATIBILITY WITH DOS VERSIONS OF PEDDIMAT 9

6. FORMAT OF THE PEDD.CFG FILE 10

7. PEDDIMAT FOR WINDOWS DATA FILE STRUCTURE 12

8. COMMAND LINE PROCESSING 20

9. RS232 CABLE CONNECTION 21

10. COMPONENT REGISTRATION 23

3
1. Computer System Hardware Requirements:
Intel Pentium based IBM compatible personal computer,

64 MB system RAM,

Windows 95, 98, ME, NT, or 2000 operating system,

10 MB of available hard disk space,

VGA color display (super VGA recommended),

Mouse or other Windows compatible pointing device.

2. Installation

Peddimat is distributed on three diskettes, or a CD. If installing from the

diskette version, insert diskette #1. If from CD, insert the CD into your CD drive.
Run SETUP.EXE program contained on the setup disk. The screen shown
below will then appear:

Click the Yes button with your mouse, or press the enter key to continue.
To abort the installation, tab to the No button and press enter, or click it with your
mouse. The Peddimat installation program will now be copied to your computer.
If you‘re installing from floppies, after several seconds, you will receive the
prompt shown below:

4
 Insert diskette #2, and press enter or click the Ok button, after the
discette2 has finished, enter diskette #3 and click OK button again. After the
install program has been copied to your computer, you will see the following
message:

Press enter or click the Ok button to continue. In a few seconds, the

Peddimat install program screen will appear:

The default directory for Peddimat is C:\Program Files\Peddimat. If you

prefer another directory, change the path to your desired location.

5
Note:
The disk space values displayed on this screen may be different than
those shown in this example screen.

After selecting a directory, click the Install button. The install program will
now extract the Peddimat program files and associated support files, and install
them in the appropriate locations on your computer.

If an earlier version of Peddimat for Windows is present on your computer,

(indicated by the presence of the PEDWIN.INI file), a message similar to the one
shown below will be displayed:

This message indicates that the install program will use the original
Peddimat installation folder. Click the Ok button to continue, or select Cancel to
abort the installation.

After all program files and support files are installed on your computer, the
install program will confirm success of the installation with a screen similar to the
one shown below.
Keep in mind, that the path locations shown on this screen may be
different on your system.

6
 Depending on the status of your operating system, you may be prompted
to reboot your computer after the installation program completes. This may be
necessary to complete registration of support files that were in use during the
installation of Peddimat.

7
3. Running Peddimat

Double click the Peddimat icon which was created by the setup program,
or use the Windows Start-Programs-Peddinghaus-Peddimat program selection
procedure. The opening screen of Peddimat will appear as shown below:

To improve the usability of the Windows version of Peddimat, rather than

having a printed user’s manual, there is an extensive help system built into the
program. To invoke the help system, press the F1 key at any time or select help
from the pull down menu.

8
4. Part File Compatibility with Earlier Versions of Peddimat

If you are upgrading from an earlier version of Peddimat, you can use
existing part files with this new version.
If you use Peddimat for Windows to modify part files created with
Peddimat for DOS, those files will no longer be readable from the DOS version of
Peddimat.

5. Cope File Compatibility with Earlier Versions of Peddimat

Cope files created with the DOS version of Peddimat are fully compatible
with the Windows version, and vice versa.

9
6. Format of the PEDD.CFG file

The PEDD.CFG file is the basic configuration file for the Windows version
of Peddimat.
If you wish to relocate any of the Peddimat data files, or direct Peddimat to
look other directories for these files, it may be necessary to modify the
PEDD.CFG file. For this reason, the first four lines of a typical PEDD.CFG file
are shown below:

C:\PROGRA~1\PEDDIMAT\CFG\BPL.CFG
C:\PROGRA~1\PEDDIMAT\TXT\ENGLISH.TXT
C:\PROGRA~1\PEDDIMAT\SHP\AISC.SHP
C:\MISC\COPES\

2 1095 2445 3420 6135 0 0 1800 5445 7380 0 0 10140 0 5445 0 1800
8340 5445 9935
C:\PARTS\88B3.NC1
C:\PARTS\A43\88B3
C:\PARTS\A45\\BEAM
C:\PARTS\A47\T2

The first line defines the default machine configuration file.

The second line defines the default text file.

The third line defines the default shape file.

The fourth line defines the location of the .cop (cope) files. If this line is
left blank, the cope files will be located in the same folders as the part
files. You may also specify a different folder for macro copes than for
normal custom copes. An example is shown below:
@C:\MACROS\ C:\COPES\
In this example, C:\MACROS\ is used for the macro copes, and other
custom copes will be in C:\COPES\. If only the macro folder is specified,
normal custom copes will be located with the part files.

The fifth line defines the path and file name for the production report file.
This line is optional, and is blank by default.

If defined, the production report file is updated by

Peddimat whenever a machine program is generated using
either the Run-Single Part or Run-Multi Part menu selections

10
 in Peddimat. Each line of the production report file contains
the following data relating to the part program created:

Path of the Peddimat part file used to create the program

Name of the Peddimat part file used to create the program
Quantity of parts in the program
Time the program was created
Date the program was created

This is an ASCII format file, and can be read using any text
editor.

The sixth and seventh lines contain data concerning the window sizes
and locations for Peddimat.

The last four lines in the file are the recent file list for Peddimat. This list
contains the file names of the last four files that were opened by
Peddimat.

You can use one of the Windows text editors to make any necessary
changes to the default file locations. (Be sure to document any changes to make
updates in the future easier.)

11
7. Peddimat for Windows Data File Structure

This listing below is an example of a sample ASCII data file created by the
PEDDIMAT for Windows software. A file similar to the one below is created to
define individual piece parts. Using this file format, data from a third party
structural detailing package, or CAD system can be ported to the Peddimat
software system.

COPE
W12X50
B
1 3111.5 95.25 2063.75 158.75 0 0 0 30480 200 240 180 0 0 0 0 0 0
55
25400 53975.1010
25400 104775.1010
25400 155575.1010
25400 206375.1010
25400 257175.1010
762000053975.101
762000104775.101
762000155575.101
762000206375.101
762000257175.101
254000026987.301
254000077787.301
254000128587.301
254000179387.301
762000026987.301
762000077787.301
762000128587.301
762000179387.301
254000026987.201
254000077787.201
254000128587.201
254000179387.201
762000026987.201
762000077787.201
762000128587.201
762000179387.201
0 0.6000 CUSTOM,
25400 53975.1011
25400 104775.1011
25400 155575.1011
25400 206375.1011

12
25400 257175.1011
76200 53975.1011
76200 104775.1011
76200 155575.1011
76200 206375.1011
76200 257175.1011
25400 26987.3011
25400 77787.3011
25400 128587.3011
25400 179387.3011
76200 26987.3011
76200 77787.3011
76200 128587.3011
76200 179387.3011
25400 26987.2011
25400 77787.2011
25400 128587.2011
25400 179387.2011
76200 26987.2011
76200 77787.2011
76200 128587.2011
76200 179387.2011
0 0.6001 CUSTOM,

The first item on the list is the part number. It may be up to 40

characters long; the first 8 characters being used as the DOS file name.

The second item is the structural shape used. (up to 15 characters)

The third item is the shape type. The different types are defined as
below:

Beam = B
Angle = L
Channel = C
Plate = P
Tube = T

13
 The next 19 items are written to the file sequentially. Their meanings
are as described below:

(all dimensions in tenths of MM)

item 1 = quantity of parts needed

item 2 = depth of section (or near leg size)
item 3 = web thickness (near leg thickness)
item 4 = flange height (far leg size)
item 5 = flange thickness (far leg thickness)
item 6 = not used
item 7 = lead edge miter (degrees)
item 8 = trail edge miter (degrees)
item 9 = length of section
items 10-36 = tooling sizes
(Tools 1,2,3 - web, bottom flange, top flange)
(Tools 4,5,6 - web, bottom flange, top flange)
(Tools 7,8,9 - web, bottom flange, top flange)
Special tool types:
Obround tooling elements separate the length and width dimensions of the
tool with an X character. Square or rectangular tooling elements separate the
length and width dimensions with a – character. To specify a countersink tool,
the countersink depth dimension is followed by the S character.
Example:
Round: 300
Obround: 250X150
Rectangular: 250-150
Countersink: 120S

The next item in the file is an array containing the hole data. The first
item is the quantity of holes plus 1. The remaining string elements define the
machine operations.

All X and Gage dimensions are defined as metric values precise to one
thousandth of a millimeter.
The Gage dimension is defined by the 7 digits immediately to the left of
the decimal point. The default Gage dimension on the web of material is relative
to the top flange. The Gage dimension on the flange of material is relative to the
lower edge of the section. (Note exceptions shown below under Options.)
The X or length dimension is defined by the remaining digits to the left of
the decimal point.
The Surface of the material is specified by the first digit immediately to the
right of the decimal point.
Surfaces values are defined as follows:

0 = Character Marking

14
 1 = Web top side (or near leg of an angle).
2 = Bottom Flange
3 = Top Flange (or the far leg of an angle).
4 = Web bottom side
5 = program stop
6 = Burning/coping or free form marking

The Tool, is specified by the next two digits to the right of the decimal.
The Tool number corresponds to the tool diameters specified in the file header
as described above. Tool 0 specifies a layout mark.

The Option, if used, is specified by the next digit, and controls the
operation as defined below:

for holes:
0 = X location from the left end, Y from the datum side
1 = X location from the right end, Y from the datum side
2 = X location from the left end, Y from the non datum side
3 = X location from the right end, Y from the non datum side
for burning or free form marking:
0 = X location from the left end
1 = X location from the right end
for character marking:
0 = text normal orientation (reading left to right)
1 = text rotated 90 degrees (CCW)
2 = text rotated 180 degrees (CCW)
3 = text rotated 270 degrees (CCW)

The Burn type/file name is specified when the surface value is 6. The
burn name is to the right of the Option value
Burn variables, if used follow the burn type/file name string separated by
commas. There may be up to 5 cope variables.

Several examples of this data format are shown below:

xxxxxggggggg.stto cope,v0,v1,v2,v3,v4
EXAMPLE: 76200 76200.101

X-DIM Y-DIM SURFACE TOOL OPTION BURN

VARIABLES
76.2 76.2 1 1 0 NONE NONE

xxxxxxxggggggg.stto cope,v0,v1,v2,v3,v4
EXAMPLE: 2327200 103200.3

X-DIM Y-DIM SURFACE TOOL OPTION BURN

VARIABLES

15
2327.2 103.2 3 0 0 NONE NONE

xxxxxxxggggggg.stto cope,v0,v1,v2,v3,v4
EXAMPLE: 1524000 76200.6001 B,TB

LENGTH WIDTH SURFACE TOOL OPTION BURN

VARIABLES
152.4 76.2 6 0 1 B TB

When a marking operation is specified the tool value

specifies the ascii character desired. The standard character string
used for marking is shown below:

0123456789ABCDEFGH-JKLMN/PQRSTUVWXYZIO* .

Example: tool 1 would indicate marking the 0 character, which is

the first character in the marking string.

BURNING DATA FORMAT

The Burn name specifies a custom burn file or one of the 4 standard burn
types illustrated below:

B - block cope
N - notch cope
R - rat hole cope
FT - Flange thinning cope

When using one of the 4 standard burn types shown above, the X and Y
dimensions are used to specify the length and width of the cope respectively.
When using a custom burn file, as described below, the X and Y
dimensions are used to specify the location of the custom burn relative to the part
edges.
A custom burn file name can be up to 8 characters in length and has the
same restrictions as any DOS file name. (See details under CUSTOM BURN
FILES below.

The next item (VARIABLES), is used for several different things

depending upon which cope type was specified.
If a Block (B) or Rat Hole (R) was specified, this entry is used to specify
whether the cope is at the Top or Bottom flange. This would be done by using
"T", "B" or "TB" to select both flanges.

If a Notch (N) was specified, this parameter indicated the gage from the
top flange to the edge of the notch.

16
 If a Flange Thin (FT) was specified, this parameter indicates which
corners of the material are to be cut. These corners are specified by the
following abbreviations:

TU - top flange upper side

TL - top flange lower side
BU - bottom flange upper side
BL - bottom flange lower side

These abbreviations can be used in any combination. If all four corners are to be
cut, then this parameter should be left blank.

CUSTOM BURN FILES

Burns other than the four types described above are referred to as
custom copes.
Custom burns are used in both the Peddinghaus ABC coping machines
and in the FPB punching and burning machines.
The geometry for these custom burns are contained in a separate ASCII
file which can be then accessed by many different piece part files.
The DOS file name for these geometry files is taken from the first (TYPE)
parameter described above. This name is automatically given a .COP file
extension to indicate that it is a cope file. The file listed below is an example of a
typical cope file.

W 0 -1016
1016 0 1016
0 2032 1016
-2032 0 1016
0 -2032 1016
1016 0 0 N

The first item shown in line 1 above is the burn surface. The following
abbreviations are used to describe the coping surface:

W - web
T - top flange
B - bottom flange
TE45 - top flange 45 degree External bevel
TI45 - top flange 45 degree Internal bevel
BE45 - bottom flange 45 degree External bevel
BI45 - bottom flange 45 degree Internal bevel
TE30 - top flange 30 degree External bevel
TI30 - top flange 30 degree Internal bevel
BE30 - bottom flange 30 degree External bevel
BI30 - bottom flange 30 degree Internal bevel

17
 In this example, "W" is used, indicating the web of the material. The
center item in the top row is the incremental X-move to the point where the
burn is started. The right-most item in the top row is the incremental Y-move
to the point where the burn is started.

Each of the remaining lines in the file contain either 3 or 4 dimensions.

Lines with 3 dimensions:

Dimension 1: Incremental X from previous point
Dimension 2: Incremental Y from previous point
Dimension 3: Radius value used at X and Y point.
This value must always be positive,
and must be the smallest of the 3 dimensions in the line.

These 3 dimensions are used to produce a controlled corner round (G36)

in the Fagor CNC.

Lines with 4 dimensions:

Dimension 1: Incremental X from previous point
Dimension 2: Incremental Y from previous point
Dimension 3: Radius value of arc.
(Positive values produce an arc less than 180 degrees; Negative
values produce arcs larger than 180 degrees.
Dimension 4: Must be either 1 or -1.
value of -1 produces clockwise arcs.
value of 1 produces counterclockwise arcs.

On plate machines using these burn files, normally the dump table will
drop after completing each burn segment. To avoid dumping the table when it’s
not necessary, you can add an “N” character to the end of the cope line. This is
shown on the example on the previous page.

These 4 dimensions are used to produce arcs defined by two points and a
radius using G02 or G03 in the machines CNC control.

(all X, Y, and Radius values are in tenths of a millimeter)

The G02 and G03 routines are available only with Peddimat version 2.3 or
greater.

MARKING FILES

Similar files as those described above are used to control the Stylus
marker on machines so equipped. The format of the file is the same as the

18
custom burn files except that the file names must start with # to designate a
marking operation.

19
8. Command Line Processing

Automatic loading of part files:

To automatically load a part file when Peddimat is run, Peddimat can be
passed a command line parameter specifying a file name. The syntax for
passing a file name is shown below:

PEDDIMAT SAMPLE

In this example, SAMPLE is the name of the part file to be loaded. When
a file name is passed to Peddimat in this manner, Peddimat is run, and the
specified part file is loaded automatically.

Single part processing:

Machine programs for Individual parts can be generated by passing
Peddimat two command line parameters.
The first parameter is used to specify the part file name, and the second is
used to specify a CNC reference number. This reference number is used within
the CNC control to identify the part program.

PEDDIMAT PART 1

In this example, PART is the name of a Peddimat part file. The 1 following
the file name is the CNC reference number. If the desired part file is not
contained in the current directory, the full path must be specified at the command
line; for example:

PEDDIMAT C:\PART 1

Multiple part processing:

Multiple part programs can be produced automatically using a cut list or
mult file. From the command line, Peddimat can be passed a parameter which
specifies a mult file name. An example of this syntax is shown below:

PEDDIMAT SAMPLE.MLT

In this example, SAMPLE.MLT is the name of an ASCII file which

describes the desired multiple output. This ASCII file specifies a stocklength,
part program number, and list of parts to be used in the production of a machine
program. If this ASCII file is not located in the current directory, the full path
must be specified at the command line; for example:

20
 PEDDIMAT C:\MULTS\SAMPLE.MLT

An example of the required *.MLT file structure is shown below:

67056 1
3 PART1
2 PART2

The first line of the file contains the stocklength of the raw material
(millimeters) to be used in the mult. The second item on that line specifies the
NC reference number to be used for the finished program.
From the second line on, the file specifies quantity and part file names for
parts to be included in the mult. If the part files are not located in the current
directory, the full path must be specified.

For example:

67056 1
3 C:\L147\PART1
2 C:\L150\PART2

When processing mult files, PEDDIMAT uses the current machine

configuration file specified by the current PEDD.CFG file.
If the current part program output device is FILE, a disk file by the same
name as the mult file is created using a .NC file extension.

For example:

If C:\MULTS\SAMPLE.MLT is used as the .MLT file, a file

C:\MULTS\SAMPLE.NC would be created to hold the part program.

In situations where special options must be set, such as a crop cut, tooling
override, etc. Peddimat must be run in the normal manner.

9. RS232 Cable Connection

The required serial cable connection from the personal computer serial port
to the controller serial port is shown below:

21
22
10. Component Registration

In order for Peddimat (1.09.03 and later) to load and function properly, Fm20.dll
must be on the user’s system. If the following message is displayed when trying
to open Peddimat, Fm20.dll is missing.

The following steps explain what must be done to get Fm20.dll:

1. Go to http://msdn.microsoft.com/en-us/library/ms968493.aspx

2. Under the “Downloading the ActiveX Control Pad:” header, click on the
“SETUPPAD.exe” link

3. Choose to “Save” this file. Save the file on the desktop or another easy to
locate destination

4. Run “setuppad.exe” from the saved location

5. Click “Yes” to agree to the License Agreement

6. Click “Continue” to carry on with the installation

7. Click the button to start the installation

8. Click “Continue”

9. Click “OK” to finalize the installation program.

10. Fm20.dll is now on the system and Peddimat will load and function properly.

23