ASTM D6959-03
(Practice)Standard Practice for Data Exchange Format for Sewn Product Plotting Devices
Standard Practice for Data Exchange Format for Sewn Product Plotting Devices
SIGNIFICANCE AND USE
This practice provides a common format that allows a computer design system to generate data that an output device can accurately reproduce independent of the hardware manufacturer.
SCOPE
1.1 This practice describes a data format for transferring information from a sewn product computer aided design software program to a device that produces physical output, typically in the form of a printed or drawn image on paper.
1.2 This practice is based on a subset of the Hewlett Packard Graphics Language HPGL/2. Supported syntax and limitations are listed in . Unsupported syntax is listed in .
1.3 This practice only supports X-Y vector data and a limited set of additional functions. No provision is made to support bitmap/raster data used in applications like inkjet printing.
1.4 This practice supports a single system of units, an image fixed at 100 % scale and 1:1 aspect ratio. Scaling and custom unit systems are not supported.
1.5 This practice does not support curve interpolation or definitions. All curves are represented by discrete vectors (stroked) and are dependent on the resolution of the CAD software.
1.6 This practice requires that all coordinates are absolute, not relative, as defined in the HPGL/2 reference.
1.7 This practice only supports positive coordinates that are measured from a single X-Y origin point with coordinates 0,0.
1.8 This practice only supports fixed width fonts. Variable width fonts are not supported.
1.9 This practice intends to transfer a static image with no provision for editing.
1.10 This practice assumes monochromatic output. It does not support implied output colors.
1.11 This practice imposes no limits on the width or length of the plot data. Physical limitations imposed by the hardware and their effects on the output are the responsibility of the hardware manufacturer.
1.12 This practice does not support frame advance commands or any methods that insert multiple origin points or floating coordinate systems.
1.13 This practice limits the plot file to contain a single block of data demarked by a compatible header and terminator. Multiple blocks of data in a single file are not allowed.
1.14 The intended application of this practice is limited to the class of output devices found in the sewn product industries that produce apparel, textiles, upholstery, and others that use soft or semi-rigid materials.
This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory limitations prior to use.
General Information
Relations
Standards Content (Sample)
NOTICE: This standard has either been superseded and replaced by a new version or withdrawn.
Contact ASTM International (www.astm.org) for the latest information
Designation:D6959–03
Standard Practice for
Data Exchange Format for Sewn Product Plotting Devices
This standard is issued under the fixed designation D 6959; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. A
superscript epsilon (e) indicates an editorial change since the last revision or reapproval.
1. Scope that produce apparel, textiles, upholstery, and others that use
soft or semi-rigid materials.
1.1 This practice describes a data format for transferring
1.15 This standard does not purport to address all of the
information from a sewn product computer aided design
safety concerns, if any, associated with its use. It is the
software program to a device that produces physical output,
responsibility of the user of this standard to establish appro-
typically in the form of a printed or drawn image on paper.
priate safety and health practices and determine the applica-
1.2 ThispracticeisbasedonasubsetoftheHewlettPackard
bility of regulatory limitations prior to use.
Graphics Language HPGL/2. Supported syntax and limitations
are listed in 7.2. Unsupported syntax is listed in X1.1.
2. Referenced Documents
1.3 ThispracticeonlysupportsX-Yvectordataandalimited
2.1 ASTM Standards:
set of additional functions. No provision is made to support
D 6672 Practice for Formatting Cutting Data to Drive
bitmap/raster data used in applications like inkjet printing.
Numerically Controlled Fabric Cutting Machines
1.4 Thispracticesupportsasinglesystemofunits,animage
D 13.66 Terminology of Sewn Products
fixed at 100 % scale and 1:1 aspect ratio. Scaling and custom
unit systems are not supported.
3. Terminology
1.5 This practice does not support curve interpolation or
3.1 Definitions:
definitions. All curves are represented by discrete vectors
3.1.1 command, n—a two letter sequence, always written in
(stroked) and are dependent on the resolution of the CAD
capital letters, that governs interpretation of formatted data.
software.
Also known as a syntax command.
1.6 This practice requires that all coordinates are absolute,
3.1.2 data block, n—an organized group of commands and
not relative, as defined in the HPGL/2 reference.
parameters preceded by a header and followed by a terminator.
1.7 This practice only supports positive coordinates that are
3.1.3 header, n—a specific group of commands required at
measured from a single X-Y origin point with coordinates 0,0.
the beginning of a data block.
1.8 This practice only supports fixed width fonts. Variable
3.1.4 parameters, n—values that modify the action of a
width fonts are not supported.
command.
1.9 This practice intends to transfer a static image with no
3.1.5 plotfile,n—instructionsorganizedinformattedblocks
provision for editing.
of ASCII characters and stored in a computer file which are
1.10 This practice assumes monochromatic output. It does
used to control a plotter or printer.
not support implied output colors.
3.1.6 syntax command, n—see command.
1.11 This practice imposes no limits on the width or length
3.1.7 terminator, n—ASCIIcharacter(s)thatsignifytheend
of the plot data. Physical limitations imposed by the hardware
of an instruction (with any associated parameters ),or a data
and their effects on the output are the responsibility of the
block.
hardware manufacturer.
1.12 This practice does not support frame advance com-
4. Summary of Practice
mands or any methods that insert multiple origin points or
4.1 Plot data are organized to allow a parsing algorithm to
floating coordinate systems.
recognize adherence to theASTM format then are written as a
1.13 This practice limits the plot file to contain a single
data block into a computer file.
blockofdatademarkedbyacompatibleheaderandterminator.
4.1.1 A specific group of commands are required at the
Multiple blocks of data in a single file are not allowed.
beginning of the data block, called a header.
1.14 The intended application of this practice is limited to
4.2 Plot data follow a subset of the HPGL/2 ASCII lan-
theclassofoutputdevicesfoundinthesewnproductindustries
guage.
ThispracticeisunderthejurisdictionofASTMCommitteeD13onTextilesand
is the direct responsibility of Subcommittee D13.66 on Sewn Product Automation.
Current edition approved Dec. 1, 2003. Published February 2004. Annual Book of ASTM Standards, Vol 07.02.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959, United States.
D6959–03
4.2.1 The practice specifies syntactical and parametric con- 7.1.7 LT—Line Type,
straints to limit ambiguity.
7.1.8 PA—Plot Absolute,
4.2.2 Basic HPGL formatting is supported. Advanced
7.1.9 PD—Pen Down,
HPGL functions are beyond the scope of the practice.
7.1.10 PU—Pen Up,
7.1.11 SI—Absolute character Size, and
5. Significance and Use
7.1.12 SP—Select Pen.
5.1 This practice provides a common format that allows a
7.2 The following descriptions outline the implementation
computer design system to generate data that an output device
of HPGL/2 syntax commands allowed by this practice. Unless
can accurately reproduce independent of the hardware manu-
otherwise noted, usage exactly follows the specification de-
facturer.
scribed in the agreed HPGL/2 reference.
7.2.1 CO—Comments. Parameters between quotes are ig-
6. Plot File
nored by the output device. This practice requires four sequen-
6.1 Plot data are written in data blocks ofASCII characters,
tial CO commands containing specific text as header data.
one data block per computer file.
These must immediately follow the IN; and precede the PA;
6.2 Data blocks are made up of commands.
syntax at the beginning of the file and use the format that
6.2.1 Eachcommandisatwo-lettersequence(see7)always
follows. Information in brackets, [ ], are variable. Example:
written in CAPITAL letters.
CO “ASTMXXXXX-XX”; CO “Author: [Author Name]”;
6.2.2 An instruction and its associated ed parameters (if
CO “Creation Date: [DD-MM-YYYY]”; CO “Creation Time:
required)areterminatedbythesemi-colon(;)terminator.Other
[HH-MM on a 24 hour time scale]”;
terminators are not supported that is mnemonic, , or
7.2.2 DI—Absolute Direction. Specifies the direction char-
.
acters in a label are drawn. In this practice, DI syntax only
6.3 Some commands are followed by parameters.
affects usage of LB and SI. Default values are DI1,0. Example:
6.3.1 Parameters immediately follow the command with no
…DI1,0;.
separating space and come before the command terminator.
Result: defines label direction as horizontal, the default for
6.3.2 Multiple parameters are separated by a comma (,).
this practice.
Other separators are not supported that is blank space, etc.
Stringsofcoordinatesarenotallowed;thatis,PDX,Y,X,Y,X,Y.
7.2.3 DT—DefineLabelTerminator(headeronly).Indicates
6.4 Blocks of data that adhere to this practice begin and end the end of a text string associated with an LB command. This
in a specific way.
practice requires a single DT command near the end of the
6.4.1 Blocks begin with specific commands in a defined header immediately following the PA syntax. The required
order, commonly called a header, as follows (information in argumentsforDTareETX(decimal03)andmode1.Theseare
brackets, [ ], are variable):
the only allowed parameters. No other instances of DT are
IN; CO “ASTMXXXXX-XX”; CO “Author: [Author allowed. Example:
Name]”; CO “Creation Date: [DD-MM-YYYY]”; CO “Cre-
… PA;DTETX,1;…
ation Time: [HH-MM on a 24 hour time scale]”; PA;
Result: defines the label terminator as ETX (decimal 03).
DTETX,1; LM0; [All subsequent plot file data follow this
Mode “1” indicates that this character is not printed.
header]…
7.2.4 IN—Initialize (header only). Resets the configuration
6.4.2 Blocks are terminated with the ASCII file separator
of the output device to defaults and raises the logical pen,
character, FS (decimal 28).
equivalent to a PU; syntax command. Also indicates the
6.5 All coordinate data use the HPGL/2 default plotter-unit
beginning of a plot file conforming to this practice and is
system.
always the first syntax command in the header. No other
6.5.1 1 plotter-unit = 0.025 millimeter (mm)
instances of IN are allowed.
6.5.2 40 plotter-units=1mm
7.2.5 LB—Label. Prints the sub
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.