MiniProf

Technical Reference
 Author
Jens Christian Rodi Hansen

Reviewers
Jane Nielsen
Jens Skouboe Poulsen
MiniProf for Windows
Editor
Technical Reference Jens Christian Rodi Hansen

Layout
Version 2.4 Jens Christian Rodi Hansen
Copyright° c 1997-2008
Greenwood Engineering A/S
First Edition, January 2008

Greenwood Engineering A/S

H. J. Holst Vej 3-5C
DK-2605 Brøndby, Denmark

www.greenwood.dk
Copyright notice
MiniProf for Windows Version 2.4 Copyright°
c 1997-2008, Greenwood Engineering A/S. All
rights reserved.

License Agreement
1. License. This agreement grants any owner of MiniProf measurement equipment a
license to use the software, MiniProf for Windows, for performing measurements and
for analyzing the measurements and results. In addition, the software may be used on
any number of computers for post-processing measurements without charge.

2. Restrictions. The software contains trade secrets and in order to protect them the software
may not be decompiled, reverse engineered, disassembled, or otherwise reduced to a
human perceivable form. Furthermore it is not allowable to modify, adapt, translate,
rent, lease, resell for profit, distribute or create derivative works based upon the software
or any part thereof.

Disclaimer of Warrenty
THIS SOFTWARE AND ACCOMPANYING WRITTEN MATERIALS ARE PROVIDED
“AS IS” WITHOUT WARRANTY OF ANY KIND. FURTHERMORE, GREENWOOD
ENGINEERING A/S (GE) DOES NOT WARRANT, GUARANTEE OR MAKE ANY
REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF USE, OF THE
SOFTWARE OR WRITTEN MATERIALS IN TERMS OF CORRECTNESS, ACCURACY,
RELIABILITY, CURRENTNESS ETC. THE ENTIRE RISK AS TO THE RESULTS AND
PERFORMANCE OF THE SOFTWARE IS ASSUMED BY YOU. IF THE SOFTWARE
OR WRITTEN MATERIALS ARE DEFECTIVE YOU, AND NOT GE OR ITS DEALERS,
DISTRIBUTORS, AGENTS, OR EMPLOYEES, ASSUME THE ENTIRE COST OF ALL
NECESSARY SERVICING, REPAIR OR CORRECTION.

NEITHER GE NOR ANYONE ELSE WHO HAS BEEN INVOLVED IN THE CREATION,
PRODUCTION OR DELIVERY OF THIS PRODUCT SHALL BE LIABLE FOR ANY
DIRECT, INDIRECT, CONSEQUENTIAL OR INCIDENTAL DAMAGES (INCLUDING
DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS
OF BUSINESS INFORMATION, AND THE LIKE) ARISING OUT OF THE USE OR
INABILITY TO USE THE SOFTWARE EVEN IF GE HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
 C ONTENTS

Contents i

List of Figures iii

List of Tables v

Introduction 1

Measurement file formats 3

2.1 Single measurement file format . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1.1 Header format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1.2 Data format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2 Multiple measurement file format . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3 Field identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.4 Compressed format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Result file formats 13

3.1 Single result file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1.1 Header format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1.2 Data format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2 Multiple result file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.3 Compressed format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Reference file format 17

4.1 The file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Multilingual support 21
5.1 Translating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Index 23

Contents i
ii Contents
 L IST OF F IGURES

2.1 Example of an old header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2.2 Example of a new header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3 Example of the measurement data . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.4 Example of a multiple measurement file . . . . . . . . . . . . . . . . . . . . . . 6

3.1 Example of a header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3.2 Example of the result data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.3 Example of a multiple result file . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.1 Example of a MPT reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

List of Figures iii

iv List of Figures
 L IST OF TABLES

2.1 Column definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.2 Fields from the core software . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 Fields from standard calculations . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.4 Fields from Wheel Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.5 Fields from Rail Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.6 Fields from Brake Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.1 MPT elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.2 MPT modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

List of Tables v
vi List of Tables
 C HAPTER 1

I NTRODUCTION

The Technical Reference to MiniProf for Windows is intended as a help for the advanced user.
Its main purpose is to document the more technical elements related to the software. This is
done to enable a larger integration with other applications and to make it possible to extend
the software’s functionality by adding and altering the configurations.

This reference includes file-format descriptions for measurement-files, result-files and reference-
files generated and used by the MiniProf software. It also includes a small description on how
to get the software translated to other languages.

Chapter 1: Introduction 1
2 Chapter 1: Introduction
 C HAPTER 2

M EASUREMENT FILE FORMATS

Measurements made with the MiniProf software can be stored in two different formats,
depending on the equipment used and the measurements made. The main difference between
these formats is the number of profiles that a single file contains. Each format is described in
the following sections.

2.1 Single measurement file format

The single measurement file contains information and measurement data for one single profile.
It is an ASCII formatted text file divided into two parts: a header with information about the
measurement and the data with the actual measured points. At least one empty line divides
the two parts. Please note that the header can be left entirely out of a measurement file. The
file is in that case initiated with one or more empty lines.

2.1.1 Header format

The format of the header depends greatly on the version of the program which has written
the file. There are basically two different formats: the old and the new. The old format, used
by the Dos software versions prior to MP35, writes a number of lines like shown in Figure 2.1
below.

MINIPROF 130 221 1996 7 223090011

Stock : :
Car No. : :
Axle No. : :
Wheel ID : :
Flange dia..: 1249.592 mm
Taperline...: 1188.179 mm
Offset Y....: -44.360 mm
31.98 30.71 10.74 (Sd/Sh/qR)

Figure 2.1: Example of an old header

Chapter 2: Measurement file formats 3

This is only an example of how the header could look. The only almost certain thing about
the old header is, that there is a line with the text MINIPROF.... It may not be the first line,
but is should almost certainly be present.

As a part of the latest version of the Dos based software MP35, a new and more generalized
format for the header was defined. This is also the native format used in MiniProf for Windows
version 2, though this software also supports partial extraction of the information from old
headers, mainly to give a greater level of backward compatibility.

The new format splits each header-line into two parts divided by an equal sign. The left part
is called the field-name and the right part is called the field-value. This formatting is also very
similar to the configuration files used by windows (known as ini-files). Figure 2.2 below shows
an example of how the old header would look in the new format.

MPTypeNo=130
MPSerNo=221
Date=1996/7/2
Filename=23090011
Stock=
CarNo=
AxleNo=
WheelID=
FlangeDia=1249.592
Taperline=1188.179
OffsetY=-44.360
Sd=31.98
Sh=30.71
qR=10.74

Figure 2.2: Example of a new header

The field-name and field-value can contain any character, except the equal sign and characters
with ASCII codes below 32. Field names must be at least 1 character long and they should be
unique. Field values can be any length, including empty. See the later section on field identifiers
for a list of standard identifiers as they are defined and used in MiniProf for Windows.

2.1.2 Data format

In the data part of the measurement file each line represents one measured point. The contents
of these lines vary depending on the version of the program that wrote the data. The ColumnDef
field holds the column definition used to identify which columns contain what. The field contains
a comma seperated string of characters, one for each column, as described in the table below.

4 Chapter 2: Measurement file formats

 TABLE 2.1: C OLUMN DEFINITION

X X coordinate for the point

Y Y coordinate for the point
T Angle of the tangent in the point
C Inverse curvature in the point
N Number of raw points gone into this point

If the ColumnDef field is not present in the header, which is the case for older measurement
files, assume two columns with X and Y coordinates.

0.71 18.03 1.489

0.73 18.23 1.489
0.74 18.38 1.379
..
..

Figure 2.3: Example of the measurement data

There is no way to tell how many points are present in the data part, without reading through
all the data. Even when a field in the header indicates the number of points, it should not be
used as an exact measure.

2.2 Multiple measurement file format

When measuring multiple profiles related to each other (for instance measuring a switch), it is
not ideal to get the measurements stored in multiple files, but instead in one single file, keeping
all the information together. The multiple measurement files are also known as TwinHead files,
because the format was designed for use with the TwinHead equipment. Actually the format
turned out to be very useful for other purposes, such as switch measurements.

A multiple measurement file places the data from a number of single measurement files into a
single file. To do this, the file is divided into a number of major sections, each initiated with a
label encapsulated by square brackets. See the example below in Figure 2.4.

Chapter 2: Measurement file formats 5

 [FileInfo]
Filename=MP_35.EXE
ProgramVer=1.35
..

[Profile1Info]
MPTypeNo=130
MPSerNo=221
Date=1996/7/2
Filename=23090011
..

[Profile1Points]
0.71 18.03 1.489
0.73 18.23 1.489
..

[Profile2Info]
..

[Profile2Points]
..

Figure 2.4: Example of a multiple measurement file

The FileInfo section contains information, which is global for the entire file. The sections named
Profile1Info and Profile1Points contains the header and data for the first profile formatted as
described for single measurement files. All headers, including the file header, use the new header
format.

There is no way to determine the number of profiles stored in a file, without reading through
and interpreting the entire file. It is not even possible to start from the tail of the file to find
the last section, using it to find the number of profiles, because there is no guarantee of order
in which the sections are placed.

2.3 Field identifiers

The field id is used as the key for accessing information from the profile header. Below follows a
list of all the standard identifiers. All identifiers marked with a star (*) are considered reserved
to the MiniProf software and should not be used for other purposes.

Though field identifiers used to store results from calculations can be changed in MiniProf for
Windows, their standard id’s have been included in the list.

6 Chapter 2: Measurement file formats

 TABLE 2.2: F IELDS FROM THE CORE SOFTWARE

ProgramName Name of the program that made the measurement

ProgramVer Version of the program that made the measurement
Date Date of the measurement formatted as dd/mm/yyyy
Time Time of the measurement formatted as hh:mm:ss
*Chars Character set used for storing text in header fields. Valid values
are: Dos and Win
*ColumnDef Column definition. This sets the interpretation of the columns of
profile data
*MPTypeNo Type number of the instrument that made the measurement. This
is used to determine the profile type
*MPSerNo Serial number of the instrument that made the measurement
*MPCalDate Date of last calibration for the instrument that made the
measurement
*MPCalTime Time of last calibration for the instrument that made the
measurement
*XYPoints Number of points in the profile
*Xoffset Profile horizontal displacement in millimeters
*Yoffset Profile vertical displacement in millimeters
*RefPoint1 Reference point 1
*RefPoint2 Reference point 2
*RefPoint3 Reference point 3
*RefPoint4 Reference point 4
*RefPoint5 Reference point 5
*RefPoint6 Reference point 6
*RefPoint7 Reference point 7
*RefPoint8 Reference point 8
*RefPoint9 Reference point 9
*ReferenceProfile Name of a reference profile which is associated with a measured
profile
*PostopsBeforeAdjust Script operations defined by a reference performed post
measurement and before instrument specific profile adjustments
are made
*PostopsAfterAdjust Script operations defined by a reference performed post
measurement and after instrument specific profile adjustments are
made

Chapter 2: Measurement file formats 7

 *PostopsScriptCombine Script operations defined by a measurement performed post
measurement when multiple script based measurements are stored
together
*PostopsFieldsUsed Defines the fields used by a post-ops script
AlignDX Horizontal displacement applied at the last alignment
AlignDY Vertical displacement applied at the last alignment
AlignDV Rotation applied at the last alignment
AlignOX X-origin of rotation for last alignment
AlignOY Y-origin of rotation for last alignment
AlignRX Horizontal scale factor applied at the last alignment
AlignRY Vertical scale factor applied at the last alignment
AlignSX X-origin of scaling for last alignment
AlignSY Y-origin of scaling for last alignment
ReferenceName Set by the MPT reference loader, using the MPT reference name
ReferenceMode Set by the MPT reference loader, using the MPT reference mode
MPDN Same as ReferenceName, but could also be set by other loaders
(import filters) using the mathematical profile definition
MPDC Number parts in the mathematical profile definition
MPD[i] Part i of the mathematical profile definition
DiameterFlange Flange diameter of the wheel in millimeters
DiameterTaperline Taperline diameter of the wheel in millimeters
Gauge Rail gauge in millimeters
Temperature Instrument temperature
SwitchOffsetX The horizontal displacement of the measurement head relative to
the instrument base
SwitchOffsetY The vertical displacement of the measurement head relative to
the instrument base

TABLE 2.3: F IELDS FROM STANDARD CALCULATIONS

Sd Result from Wheel wear

Sh Result from Wheel wear
qR Result from Wheel wear
FlangeR Result from Wheel flange radius
W1 Result from Rail wear
W2 Result from Rail wear

8 Chapter 2: Measurement file formats

 W3 Result from Rail wear
CrownR Result from Rail crown radius
HeadW Result from Rail head width
DiscWear Result from Brake wear
DiscThickness Result from Brake wear
Position Result from Brake wear
DiscWear Result from Brake wear (No reference)
DiscThickness Result from Brake wear (No reference)
Position Result from Brake wear (No reference)
Length Result from Length
MinimumResidual Result from Maximum residuals
MaximumResidual Result from Maximum residuals
AverageResidual Result from Maximum residuals
AreaGained Result from Area
AreaLost Result from Area
AreaTotal Result from Area

TABLE 2.4: F IELDS FROM W HEEL E XTENSION

FlangeWidth Result from Wheel flange width

FlangeWidthTram Result from Wheel flange width (Tram)
FlangeBackWear Result from Wheel flange back wear
FlangeBackWearFla Result from Wheel flange back wear (Tram)
FlangeAngle Result from Wheel flange angle
FlangeAngleMax Result from Wheel flange angle maximum
FlangeAngleMaxPos Result from Wheel flange angle maximum
TaperlineAngle Result from Wheel taperline angle
dSd Result from Wheel wear difference
dSh Result from Wheel wear difference
dqR Result from Wheel wear difference
DiameterDiffA1 Result from Wheel diameter difference
DiameterDiffA2 Result from Wheel diameter difference
DiameterDiffC1 Result from Wheel diameter difference
DiameterDiffC2 Result from Wheel diameter difference

Chapter 2: Measurement file formats 9

 Hollowing Result from Wheel hollowing
HollowingPos Result from Wheel hollowing
ThreadWear Result from Wheel thread wear
ThreadWearMax Result from Wheel thread wear maximum
ThreadWearPos Result from Wheel thread wear maximum
VolumeLoss Result from Wheel volume loss
WeightLoss Result from Wheel volume loss
DiameterFlange Result from Wheel diameter from tyre
DiameterTaperline Result from Wheel diameter from tyre
GaugeFlange Result from Wheel gauge flange
LeadingVal1 Result from Wheel gauge flange
LeadingVal2 Result from Wheel gauge flange
GaugeBack Result from TwinHead Wheel gauge
GaugeTaperline Result from TwinHead Wheel gauge
GaugeFlange Result from TwinHead Wheel gauge
GaugeAR Result from TwinHead Wheel gauge (AR)

TABLE 2.5: F IELDS FROM R AIL E XTENSION

RailAngle Result from Railhead angle

RailGaugeAngle Result from Rail gauge angle
RailGaugeAngleMax Result from Rail gauge angle maximum
RailGaugeAngleMaxPos Result from Rail gauge angle maximum
RailHeight Result from Rail height
AreaRailhead Result from Railhead area
AreaReference Result from Railhead area
AreaRatio Result from Railhead area
W1 Result from Grooved rail wear
W2 Result from Grooved rail wear
W4 Result from Grooved rail wear
CrownRadius Result from Grooved rail geometry
GaugeTopRadius Result from Grooved rail geometry
GaugeBottomRadius Result from Grooved rail geometry
CheckTopRadius Result from Grooved rail geometry

10 Chapter 2: Measurement file formats

 CheckBottomRadius Result from Grooved rail geometry
GrooveWidth Result from Grooved rail geometry
GrooveHeight Result from Grooved rail geometry
Gauge Result from TwinHead rail gauge

TABLE 2.6: F IELDS FROM B RAKE E XTENSION

VolumeLoss Result from Brake volume loss

WeightLoss Result from Brake volume loss
DiscWidthMin Result from TwinHead brake width
DiscWidthMax Result from TwinHead brake width

2.4 Compressed format

Measurement files can be stored in a compressed binary format with MiniProf for Windows
Version 2.2 or later. This compression will typically reduce the file size with about 50 percent.
The exact format of these files will, for the moment, remain confidential.

Chapter 2: Measurement file formats 11

12 Chapter 2: Measurement file formats
 C HAPTER 3

R ESULT FILE FORMATS

Results files created with the MiniProf for Windows software can be stored in two different
formats, depending on the number of results contained in the file. Each format is described in
the following sections.

3.1 Single result file format

The single result file contains information and result data for one single result. It is an ASCII
formatted text file divided into two parts: a header with information about the result and the
data with the actual result points. At least one empty line divides the two parts. Please note
that the header can be left entirely out of a result file. The file is in that case initiated with
one or more empty lines.

3.1.1 Header format

The header is formatted similar to the header of a measurement file. This format splits each
header-line into two parts divided by an equal sign. The left part is called the field-name and
the right part is called the field-value. This formatting is also very similar to the configuration
files used by windows (known as ini-files). Figure 3.1 below shows an example of how a result
header could look.

Chapter 3: Result file formats 13

 ColumnDef=X1,X2,Y1
ColumnX1Name=Tangent angle
ColumnX1Flag=
ColumnX1Form=%.*f◦
ColumnX1Unit=deg
ColumnX2Name=Profile distance
ColumnX2Flag=
ColumnX2Form=%.*f
ColumnX2Unit=mm
ColumnY1Name=Curvature
ColumnY1Flag=/50,Sqr,Abs,Inv
ColumnY1Form=%.*f
ColumnY1Unit=mm
XYPoints=804
Chars=Win

Figure 3.1: Example of a header

The field-name and field-value can contain any character, except the equal sign and characters
with ASCII codes below 32. Field names must be at least 1 character long and they should be
unique. Field values can be any length, including empty.

3.1.2 Data format

In the data part of the result file, each line represents one point. The contents of these lines
vary depending on the type of result stored. The ColumnDef field in the header defines the
sequence of the columns. Use the column descriptions (ColumnX... and ColumnY...) to locate
the columns of interest.

-92.5968 0.0000 12.3643

-92.2969 0.1377 12.3643
-91.7937 0.4001 12.4301
-91.2931 0.6589 12.6490
..
..

Figure 3.2: Example of the result data

There is no way to tell how many points are present in the data part, without reading through
all the data. Even when a field in the header indicates the number of points, it should not be
used as an exact measure.

14 Chapter 3: Result file formats

3.2 Multiple result file format

A result file can, just as measurements files, contain multiple results. To do this, the file is
divided into a number of major sections, each initiated with a label encapsulated by square
brackets. See the example below in Figure 3.3.

[FileInfo]
ProgramName=MiniProf for Windows
ProgramVer=2.1.12
..

[Result1Info]
ColumnDef=X1,X2,Y1
ColumnX1Name=Tangent angle
ColumnX1Flag=
ColumnX1Form=%.*f◦
ColumnX1Unit=deg
..

[Result1Points]
-90.1494 0.0000 12.3643
-89.8679 0.1377 12.3643
..

[Result2Info]
..

[Result2Points]
..

Figure 3.3: Example of a multiple result file

The FileInfo section contains information, which is global for the entire file. The sections named
Result1Info and Result1Points contains the header and data for the first result formatted as
described for single result files.

There is no way to determine the number results stored in a file, without reading through and
interpreting the entire file. It is not even possible to start from the tail of the file to find the
last section, using it to find the number of results, because there is no guarantee of order in
which the sections are placed.

Chapter 3: Result file formats 15

3.3 Compressed format

Result files can be stored in a compressed binary format with MiniProf for Windows Version
2.2 or later. This compression will typically reduce the file size with about 50 percent. The
exact format of these files will, for the moment, remain confidential.

16 Chapter 3: Result file formats

 C HAPTER 4

R EFERENCE FILE FORMAT

The MPT format was developed in order to make it possible to use mathematical defined
reference profiles in the MiniProf software. Reference profiles can be specified much more
precisely in this way, and the inaccuracy on calculations will at the same time be minimized.

MPT files was originally designed from a subset of the commands used in DXF files, which
easily can be generated by AutoCAD and other CAD applications. More elements have been
added now, making it even more usable than the DXF format. The MiniProf software can
import DXF and export the profile to a MPT reference, but if elements like the polynomium
is required (which is not available in the DXF format) the MPT have to be written manually.

4.1 The file format

MPT files use a very simple text-based format, in which files are read line by line and empty
lines are ignored. The contents of a single line can be classified entirely by the first character.
The table below describes the format for the elements in the individually lines.

All numbers are represented as floating point with a precision of seven decimals. The period
sign is used to separate the integer part from the fraction part. All coordinates are stated in
millimeters and angles for arcs and ellipsis are given in degrees in the interval -360◦ to 360◦ .

TABLE 4.1: MPT ELEMENTS

;[text] Enters a comment in the file. The text is optional.

*name Sets the reference profile name, used for later identification.
#mode Sets the reference profile mode. This defines the type of the
reference profile, both how the software loads it and for which
calculations it can be used. See the Table 4.2 below for further
information on the available mode numbers.
@fieldid=fieldval Inserts a field into the profile header when loaded. Header fields
can be used to embed additional information with a reference
profile. This is specially usefull for adding calculation parameters,
warning and failure levels to the reference.
L x1 y1 x2 y2 Places a line from (x1 ,y1 ) to (x2 ,y2 ).

Chapter 4: Reference file format 17

 A xc yc r v2 v1 Places an arc in (xc ,yc ) with the radius r, starting in v1 and
ending in v2 .

E xc yc ra rb v2 v1 v0 Places an ellipsis in (xc ,yc ) with the major axis ra and miror axis
rb , starting in v1 and ending in v2 . The ellipsis major axis is
rotated v0 relative to the coordinate system.

P x1 x2 x0 k0 k1 k2 ... kn Places a nth degree polynomium from x1 to x2 .

y[x1 ..x2 ] = kn · xn + kn−1 · xn−1 + ... + k2 · x2 + k1 · x + k0
The points are shifted horizontally by x0 .

Note: The format code ‘P’ have been given a new meaning in MiniProf for Windows
Version 2.2 and above. Previously the code denoted a point, which was a redundant type.
If a reference is formed by a series of points, it is not really a mathematical precise definition,
and it should be stored in the measurement file format instead. If, for some reason, points
are needed in a region of a profile, define these using lines.

TABLE 4.2: MPT MODES

100 Asymmetrical wheel profile

18 Chapter 4: Reference file format

 200 Asymmetrical rail profile
201 Symmetrical rail profile
300 Asymmetrical brake profile

The reference can be defined either asymmetrical or symmetrical. For asymmetrical references
all parts of the references must be defined. By symmetrical references however only the left or
right part needs to be defined. The software will automatically generate the remaining part of
the reference by mirroring along a vertical line, which goes through the coordinate (0,0).

To complete this description, Figure 4.1 below shows an example of an MPT reference file. The
file defines a symmetrical rail profile reference named UIC60.

;Rail reference profile UIC60.

;Greenwood Engineering A/S
*UIC60
#201
;
A 0.00000 -300.00000 300.00000 87.994238 90.00000
A 7.70000 -80.134791 80.00000 76.77651 87.994238
A 23.02625 -14.911283 13.00000 2.695142 76.77651
L 36.01187 -14.3 37.060422 -35.271027
A 34.064165 -35.42084 3.00000 289.983107 2.862405
L 35.089394 -38.24022 16.5 -45.0

Figure 4.1: Example of a MPT reference

Chapter 4: Reference file format 19

20 Chapter 4: Reference file format
 C HAPTER 5

M ULTILINGUAL SUPPORT

The MiniProf for Windows software has been designed to support multiple languages. The
following sections describe how to get the software translated and how to install a new language.

5.1 Translating

All the text which needs to be translated is located in an Excel file found on the CDROM in the
language folder. Use Microsoft Excel to edit the contents of the files. There are some essential
things, which must be considered during the translation.

1) Each line in the files is used separately by the software. Therefore, do not break a line
into two or more lines. Also do not insert new lines or delete any of the existing.

2) Some of the lines include the ‘|’ character, which must be preserved. It divides the line
into two parts, where the first gives a short description for some function and the last is
a longer description for the same function.

3) All the text used in menus and on buttons uses the ‘&’ character to indicate which letter
will be highlighted with an underscore. Place this character carefully and make sure that
all items in one submenu have a unique highlighted letter.

4) Some of the text includes formatting codes, which should be preserved. The codes are
all encapsulated by curly brackets (‘{’ and ‘}’). As an example, the text “Press the
{b1}Cancel{b0} button” will be displayed as “Press the Cancel button”, making the
word Cancel appear bold.

When the translation is complete, mail the translated files to us, preferable as e-mail. The
addresses can be found in the back of this manual. We will then generate the language files,
verify that they work, and return them as fast as possible.

Note: Please contact Greenwood Engineering before starting a translation. Some

languages are currently not supported and some may already be in the process of
translation.

Chapter 5: Multilingual support 21

22 Chapter 5: Multilingual support
 I NDEX

C The file format . . . . . . . .

Result file formats . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 17
. 11
Compressed format . . . . . . . . . . . . . . . . . . . . . . . 15
Compressed format . . . . . . . . . . . . . . . . . . . . . 11, 15 Multiple result file format . . . . . . . . . . . . . . . . . . 14
Single result file format . . . . . . . . . . . . . . . . . . . . 13

D S
Data format . . . . . . . . . . . . . . . . . . . . . . . . . . . 4, 14
Single measurement file format . . . . . . . . . . . . . . . . .3
Data format . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Header format . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Single result file format . . . . . . . . . . . . . . . . . . . . . 13
F Data format . . . . . . . . . . . .
Header format . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 14
. 13
Field identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

T
H The file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Translating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Header format . . . . . . . . . . . . . . . . . . . . . . . . . . 3, 13

I
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

M
Measurement file formats . . . . . . . . . . . . . . . . . . . . .1
Compressed format . . . . . . . . . . . . . . . . . . . . . . . 11
Field identifiers . . . . . . . . . . . . . . . . . . . . . . . . . .6
Multiple measurement file format . . . . . . . . . . . . .5
Single measurement file format . . . . . . . . . . . . . . .3
Multilingual support . . . . . . . . . . . . . . . . . . . . . . . 19
Translating . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Multiple measurement file format . . . . . . . . . . . . . . .5
Multiple result file format . . . . . . . . . . . . . . . . . . . . 14

R
Reference file format . . . . . . . . . . . . . . . . . . . . . . . 16

Index 23