UltraScan DSP English Integration RevG

ULTRASCAN DSP
INTEGRATORS MANUAL
SOFTWARE REVISION Q
- for suitably qualified personnel only -
www.betalasermike.com
Manual Part Number: 92005 Manual Drawing Number: 0921-00248 English Revision G Copyright Apr 2009
UltraScan DSP Integrators Manual
Contents
Proprietary Statement ..................................................................................................................... 4
Introduction ..................................................................................................................................... 5
Document Description .................................................................................................................... 5
UltraScan DSP Revision ................................................................................................................ 5
Document Organization ................................................................................................................. 5
Intended Audience ......................................................................................................................... 5
Conventions ................................................................................................................................... 5
Definition of Terms ......................................................................................................................... 6
Serial Interface................................................................................................................................. 7
Technical Data ............................................................................................................................... 7
Communication Information ........................................................................................................... 8
DeviceNet Interface ....................................................................................................................... 17
Product Support ........................................................................................................................... 17
DeviceNet Objects ....................................................................................................................... 17
DeviceNet I/O Data ...................................................................................................................... 29
CANopen Interface ........................................................................................................................ 30
CANopen Data Dictionary Objects ............................................................................................... 33
Profibus Interface .......................................................................................................................... 64
Product Support ........................................................................................................................... 64
Profibus I/O Data ......................................................................................................................... 64
Profibus PKW Header .................................................................................................................. 64
FieldBus I/O Data........................................................................................................................... 72
Profibus ........................................................................................................................................ 72
DeviceNet .................................................................................................................................... 73
CANopen ..................................................................................................................................... 73
Definitions of Bit-Fields and Structures Used for Data Formats................................................... 73
Output Data Format ..................................................................................................................... 74
Input Data Formats ...................................................................................................................... 75
Appendix A: Waveform Information ............................................................................................ 83
Uncompressed Waveform Data ................................................................................................... 83
Compressed Waveform Data ....................................................................................................... 83
Waveform Collection Modes ........................................................................................................ 84
Waveform Collection Sequence ................................................................................................... 85
Appendix B: DeviceNet EDS File ................................................................................................. 87
Part Number: 92005 / Drawing Number 0921-00248 Page 2 of 212 Revision G (Apr 2009)
Appendix C: PROFIBUS GSD File ................................................................................................ 88

Appendix D: Gauge Calibration ................................................................................................... 90
Average Wall Calibration ............................................................................................................. 90
Fixed Sector-Based Wall Calibration ........................................................................................... 91
Adaptive Sector-Based Wall Calibration ...................................................................................... 93
OD Calibration ............................................................................................................................. 95
OD Offset Calibration ................................................................................................................... 96
Appendix E: High Speed Tolerance Checking ........................................................................... 97
Overview ...................................................................................................................................... 97
Modes .......................................................................................................................................... 97
Sensitivity Adjustment .................................................................................................................. 97
Error Indication ............................................................................................................................. 98
Examples ................................................................................................................................... 101
Troubleshooting ......................................................................................................................... 105
Appendix F: Waveform Processing Modes .............................................................................. 106
Center of Energy Mode .............................................................................................................. 106
Initial Energy Mode (Default)...................................................................................................... 107
Thin-Wall Tube Mode ................................................................................................................. 108
Total Wall Mode ......................................................................................................................... 109
Appendix G: Time-varying Gain (TVG) ...................................................................................... 110
Disabled Mode ........................................................................................................................... 110
Hardware-Based Automatic TVG Mode ..................................................................................... 110
Hardware-Based Manual TVG Mode ......................................................................................... 111
Software-Based Automatic TVG Mode ...................................................................................... 112
Software-Based Manual TVG Mode .......................................................................................... 112
Appendix H: UltraOPC Server .................................................................................................... 113
UltraOPC Server Tools and Files ............................................................................................... 114
Troubleshooting ......................................................................................................................... 119
Appendix I: Database Layout ..................................................................................................... 127
Standard Database Fields ......................................................................................................... 127
Database Packet Commands .................................................................................................... 195
Servicing and Returning Your Equipment ................................................................................ 211
Index ............................................................................................................................................. 212
Proprietary Statement
Manufacturer/Distributor
Beta LaserMike, 8001 Technology Blvd., Dayton, OH 45424, USA
About This Manual
This manual contains descriptions, drawings, and specifications for a Beta LaserMike product. Equipment or
products made prior to or subsequent to the publication date of this manual may have parts, features, options, or
configurations that are not covered by this manual. Specifications contained herein are subject to change by Beta
LaserMike without prior notice. Beta LaserMike is not responsible for errors or omissions that may be contained
herein or for incidental or consequential damages in connection with the furnishing or use of this information.
Comments or suggestions for possible improvements to the manual are appreciated. Please email us at
manualfeedback@betalasermike.com.
The information contained in this manual is the property of Beta LaserMike. The information disclosed in this
document is furnished in confidence and upon the condition that individual and corporate intellectual rights, whether
patented or not, will be respected. If this document is supplied on removable media (e.g. CD), an electronic copy
(stored on-site) and one printout is permitted. If this document is supplied in printed form, no part of this document
may be reproduced or scanned without the prior written consent of Beta LaserMike. This document may not be
distributed or circulated to third parties.
Limited Warranty
Beta LaserMike will correct by repair, or at Beta LaserMikes option, by replacement, F.O.B Beta LaserMikes plant,
any defect in workmanship or material in any equipment manufactured by Beta LaserMike which appears under
normal and proper use within twelve months from the date of shipment (eighteen months for OEMs), provided Beta
LaserMike is given reasonable opportunity to inspect the alleged defective equipment at the place of its use and
under conditions of its use.
EXCLUSIONS: This warranty does not cover products which have been modified, altered, or repaired by any other
party than Beta LaserMike or its authorized agents. Furthermore, any product which has been, or is suspected of
being damaged as a result of negligence, misuse, incorrect handling, servicing, or maintenance; or has been Note:
damaged as a result of excessive current/voltage or temperature; or has had its serial number(s), any other For information
markings, or parts thereof altered, defaced, or removed will also be excluded from this warranty.
about servicing
WARRANTY SERVICE AT CUSTOMER SITE: Warranty service performed at the customers facility will be free of and returning
charge for parts and labor; however, the customer will be liable for transportation and living expenses of personnel your equipment,
dispatched to effect such repair. A purchase order or other written confirmation of the acceptance of these charges, see the section
signed by an authorized individual, will be required prior to commencement of repairs. Additional charges may be at the end of this
assessed the customer if: 1) The equipment is not made available on a timely basis, 2) The equipment is found to manual.
be without fault, and/or 3) It is determined the equipment is not under warranty, whether by expiration of the
warranty or any act which voids the warranty.
OTHER THAN AS SET FORTH HEREIN, BETA LASERMIKE MAKES NO WARRANTIES, EXPRESSED OR
IMPLIED, OF MERCHANTABILITY AS TO THE EQUIPMENT MANUFACTURED BY IT, AND THERE ARE NO
EXPRESSED OR IMPLIED WARRANTIES WHICH EXTEND BEYOND THE DESCRIPTION ON THE FACE
THEREOF. Beta LaserMikes obligation to correct defects in such equipment by repair or replacement in
accordance with the foregoing provisions is in lieu of any other warranties, expressed or implied, and in no event
shall Beta LaserMike be liable for incidental or consequential damages. No service of Beta LaserMikes equipment
is permitted during the warranty period without the specific written consent of Beta LaserMike.
Introduction
Document Description
This document describes the various communication interfaces between a
control processor and the Beta LaserMike UltraScan DSP Ultrasonic Gauge.
UltraScan DSP Revision

This document describes the various communication interfaces as
implemented in Revision Q of the UltraScan DSP software. This document
may not be accurate for other earlier revisions of software and may only
represent a subset of the features implemented in subsequent versions.
Contact Beta LaserMike for a version of this handbook that corresponds to
your revision of the UltraScan DSP.
Document Organization
This document is divided into four major parts.
The first portion discusses the serial interface of the UltraScan DSP.
The second portion discusses the DeviceNet and CANopen interfaces
of the UltraScan DSP.
The third portion discusses the Profibus interface of the UltraScan
DSP.
The fourth section contains the appendices, which provide additional
useful information to an integrator.
Intended Audience
This document is intended for internal and external engineers who will be
integrating their own systems with the UltraScan DSP ultrasonic gauge.
Conventions
This document will use the following typestyle conventions:
Arial will be the normal font used.

Courier New will be used to indicate a command sent to the unit or
a response from the unit.
Hexadecimal numbers will be represented by a leading 0x all other
numbers are decimal.
All binary data is in little-endian format unless specified otherwise. With little-
endian data, if the data is contained in four bytes, byte 1 is the most-significant
byte and byte 4 is the least significant byte.
When appropriate, a value referred to in a table will contain the database cell
ID in this format: {ID}.
Definition of Terms
Char 2s complement signed 8-bit integer value
UChar unsigned 8-bit integer value
Short 2s complement signed 16-bit integer value
UShort unsigned 16-bit integer value
Long 2s complement signed 32-bit integer value
ULong unsigned 32-bit integer value
Float IEEE-754 32-bit floating point value
ETB ASCII character 0x17, representing the end of transmission
block (created by typing a Ctrl-w on the keyboard)
Serial Interface
The simplest interface to the UltraScan DSP is the RS-232 serial port
interface. The unit contains two serial ports, both of which can be used
independently or simultaneously to transmit commands to and receive data
from the gauge.
Technical Data
This section contains technical information about configuring the UltraScan
DSP serial ports.
Baud rate
The serial ports on the UltraScan DSP can be configured for several different
baud rates to suit your needs.
Port #1 can be configured for 4800 bps, 9600 bps, 19.2 kbps, and 38.4
kbps. The default is 38.4 kbps.
Port #2 can be configured for 1200 bps, 2400 bps, 4800 bps, and 9600
bps. The default is 9600 bps.
For both ports, the default configuration is for no parity, 8-bit
characters, 1 stop bit, and no flow control. Both ports can be
configured for 1 or 2 stop bits, 8 or 7-bit characters, even, odd or no
parity, hardware flow control (CTS input).
Checksum
All responses from the UltraScan DSP over the serial port will contain a
checksum suffix. This suffix will consists of a ETB character and 8-bit
checksum value.
A system communicating with the UltraScan DSP can terminate commands
with a checksum, if desired. The ETB character should separate the
instruction and the checksum. If the checksum is invalid, the UltraScan DSP
will not execute the request and will not send a response.
The checksum is calculated by adding the ASCII values of each character in
the response (including the *S1/) into an unsigned byte. The checksum value
is sent as two ASCII characters representing the checksum in hexadecimal.
If the checksum sent to the UltraScan DSP is incorrect (whether by sending an
invalid checksum, or by a faulty transmission causing the checksum not to
match), the UltraScan DSP will consider the message incomplete and no
response will be sent.
Metric vs. Imperial Units

The UltraScan DSP will communicate over the serial port in either metric or
imperial units. The database entry to change which method is used is
documented in Appendix I Database Layout of this document. Setting or
retrieving a database field which is unit-specific, the UltraScan DSP will
append a character to the end of the database field ID to indicate which units
type is currently in place -- I for imperial units and M for metric units.
Database Data Types

The UltraScan DSP database values are all stored in one of four different data
types:
Long a 32-bit Integer value
Float a IEEE-754 floating point value
Enum an integer-based value used to represent a non-integer
number
String a null-terminated, variable-length string
Communication Information
This section contains the required information for communicating with the
UltraScan DSP over a serial port.
Instruction Set
The UltraScan DSP has several instructions, which can be used to request
configuration and result data from, as well as set configuration data in the
UltraScan DSP.
The general format for interfacing with the UltraScan DSP via a serial port is:
<command character>S1/<database ID>[=value][checksum]
For example: =S1/103=20 would set database ID 103 to the value 20.
Each command is described in detail in its own sub-section.
Most commands will cause the UltraScan DSP to respond with a standard
reply message. The general format of the reply is:
*S1/<database ID><I|M>=<value><checksum>
Where an M or I indicates imperial or metric units, respectively when

appropriate, and represents the ETB character.
Set Value (=)
This command will set a value in the UltraScan DSP database. A set value
command will look like the following:
=S1/103=20
Where = is the set value command, 103 is the database ID, and 20 is the
value to set in database cell 20. The gauge will reply with the following:
*S1/103I=2059
Where * indicates a response from the UltraScan DSP, 103 is the database
ID, I represents imperial units, 20 is the requested value, and 59 is an
ETB and checksum.
Get Value (?)
This command will retrieve a value from the UltraScan DSP database. A get
value command will look like the following:
?S1/103
Where ? is the get value command and 103 is the database ID. The gauge
will reply with the following:
*S1/103I=2059
Where 103 indicates the database ID, I indicates imperial units, 20

represents the value stored in that database ID, and 59 is an ETB and
checksum.
Open Hot Link (!)
This command will setup a hot link, where the UltraScan DSP will send a
response over the serial port anytime the requested database cell changes.
This alleviates the need for a controller or monitoring system to poll the
UltraScan DSP to determine when a particular database value changes. The
response will only be sent over the serial port the request was sent over (i.e., if
a user sends an open hot link command over serial port 1, all responses will
be sent only over serial port 1).
An open hot link command will look like the following:
!S1/309
Where ! is the open hot link command and 309 is the database ID. The
gauge will reply with the current value of that database cell:
*S1/309=0e6
Where 309 is the database ID, 0 is the current value of the database cell,
and e6 is an ETB and checksum.
The UltraScan DSP will send a similar response message over the serial port
anytime the requested database cell value changes.
Open Timed Hot Link (!T)
This command performs the same function as the Open Hot Link command,
but allows the user to specify a time restriction. The UltraScan DSP will send
a response over the serial port anytime the requested data changes, but if an
update occurs faster than the requested time T, the gauge will not send the
data until time T has elapsed. The time T is configured in 10 ms
increments, so a value of 10 indicates 100 ms time.
For example, a time hot link is opened for a particular database cell with a
minimum update time of 1 second. A change occurs and the update is
transmitted over the serial port. 200 ms later, another update occurs. Since 1
second has not passed, the gauge will not transmit this new update. 500 ms
after this, another update occurs. Only 700 ms has passed, so this update is
not transmitted. After 1 second has passed, the last update that occurred is
now sent over the serial port.
An open timed hot link command will look like the following:
!30S1/309
Where ! is the open hot link command, 30 indicates a 300 ms time limit,
and 309 is the database ID. The gauge will reply with the following:
*S1/309=0e6
Where 309 is the database ID, 0 is the current value of the database cell,
and e6 is an ETB and checksum.
As with the Open Hot Link command, the response will only be sent over the
serial port the request was sent over (i.e., if a user sends an open hot link
command over serial port 1, all responses will be sent only over serial port 1).
Close Hot Link ())
This command will close an open hot link. A close hot link command will look
like the following:
)S1/309
Where ) is the close hot link command and 309 is the database ID. The
gauge will reply with the following:
*)S1/309-closed49
Where 309 is the database ID.
An alternative syntax allows the user to close all hot links with a single
command:
)ALL
The UltraScan DSP will respond to this command with the following:
*)ALL-closedd3
Suspend Hot Link (~)
This command will suspend an open hot link. A suspend hot link command
will look like the following:
~S1/309
Where ~ is the suspend hot link command and 309 is the database ID. The
gauge will reply with the following:
*~S1/309-suspendedef
An alternative syntax allows the user to suspend all hot links with a single
command:
~ALL
The UltraScan DSP will respond to this command with the following:
*~ALL-suspended59
Resume Hot Link (+)
This command will resume output of a suspended hot link. A resume hot link
command will look like the following:
+S1/309
Where + is the resume hot link command and 309 is the database ID. The
gauge will reply by restarting the normal hotlink output.
*S1/309=0e6
An alternative syntax allows the user to reusme all hot links with a single
command:
+ALL
The UltraScan DSP will respond by restarting the normal hotlink output for all
open hotlinks that are suspended.
Identify Serial Port
The Identify Serial Port command allows a host system to determine which
serial port they are communicating to the UltraScan DSP through. This
command is invoked by the following:
mS1/PORT
A reply from this command will look like this:
*mS1/PORT=1fd
Where 1 is the serial port on which this command was sent to the UltraScan
DSP.
Configure Output Broadcasting
The Configure Output Broadcasting command allows a host system to enable

or disable the automatic broadcasting of setup changes made by other host
systems connected to other I/O ports of the UltraScan DSP. This serial
command enables/disables broadcasting only on the serial port it is sent to.
The command is invoked by the following:
To enable broadcasting (the default mode after power-up or reset)
mS1/BCAST=1
The reply from this command will look like this:
*mS1/BCAST=125
To disable broadcasting
mS1/BCAST=0
The reply from this command will look like this:
*mS1/BCAST=024
Database Packets
When retrieving information from the database via the serial port connection, it
may take several database requests to pull all the required information.
Requesting a packet is a useful way to lessen the bandwidth usage.
Retrieving data in packets also ensures time-coincidence of the data.
A database packet consists of several database cells pre-grouped together
and requested with a single command.
A packet identifier can be used in any command, and can be identified by the
character P preceding the packet number.
The available packets and the format of the packet response are described in
Appendix I Database Layout.
Waveform Packets
Database packets {P20} through {P29} represent packets used to retrieve, via
the RS232 interface, waveform data and waveform information stored within
the UltraScan DSP. The waveform information is specific to the instance of
the waveform being retrieved and does not represent information that is
averaged.
Reference Appendix A for additional detail regarding waveform processing.
Reading waveform data read from the UltraScan DSP using packets {P28}
and/or {P29}, will generally require several reads to acquire an entire
waveform. Continue reading the waveform data packets until no data is
returned. Setting {985} will specify the waveform packet number to be
returned when {P28} or {P29} is subsequently read. Setting this cell, allows a
packet to be reread incase a corrupt packet was previously returned.
Waveform data packet {P28} is used to retrieve waveform data in a simple
run-length format for improved throughput (refer to Appendix A for details
describing compressed waveform data formats). The compressed data in
{P28} is also formatted into one or more UUENCODED strings before being
output to the RS232 interface to additionally enhance data throughput. The
first character of a UUECODED string, represents the number of valid data
bytes represented in the string. The character representing the length is
encoded as the length (up to a maximum of 45 data bytes encoded in one
UUENCODED string) + 0x20 (i.e. 0x21 represents a valid data length of one
decoded byte). The encoded data that follows the encoded length character is
combined into character quadruplets (3 data bytes encoded into 4
UUENCODED characters). The data bytes are decoded as follows:
data byte 1 = ((char 1 0x20) shifted left 2) or ((char 2 0x20) shifted right 4)
data byte 2 = ((char 2 0x20) shifted left 4) or ((char 3 0x20) shifted right 2)
data byte 3 = ((char 3 0x20) shifted left 6) or (char 4 0x20)
Data bytes 2 and 3 may not represent valid data and should be discarded
according to the valid data length specified in the first byte of the
UUENCODED string. If multiple UUENCODED strings are required to
represent all the data for a requested packet, subsequent strings will
immediately follow any previous strings and will begin with an encoded length
character.
External Database Synchronization

The UltraScan DSP provides a mechanism for an external host to synchronize
its database cell settings to that of the UltraScan DSP. The external host can
initiate the automatic output of the current settings within the UltraScan DSP
by writing to a specific database cell {218}.
The synchronization cell supports three different types of synchronization that
each represent a subset of the entire UltraScan DSP database: 1-General
(includes all configuration settings and statuses excludes measurement data
and tolerances), 2-Units (includes all configuration settings and measurement
values whose values must be converted when the system output units type
Metric vs. Imperial is changed), and 3-Resolution (includes all configuration
settings and measurement values whose values support a configurable
resolution).
Example:
=S1/218=2 Host initiates external
synchronization for Units
*S1/219=1299b Reply with 129 database cells to be
synchronized
*S1/218=230 Reply to external sync initiation
*S1/112=25.0bc First cell of synchronization
*S1/149=5.00c4 Second cell of synchronization
*S1/320=1.000017 Third cell of synchronization

*S1/2105=1.277778e-05c7
*S1/2106=69.2732 Last cell of synchronization
*S1/219=02f Status = synchronization complete
Communication Errors
If a serial message is not understood or cannot be successfully completed by
the UltraScan DSP, it will respond with an error message. All error messages
begin with the @ character. An example error message may look like this:
@S1/5=15
Where @ is the error response indicator, 5 is the database cell that was
used in the command which caused this error response, and 15 is the error
code.
Note that an incomplete command may be ignored by the UltraScan DSP

altogether, and not receive any response. A command sent with an incorrect
checksum is considered an incomplete command, and will therefore receive
no response.
The possible error codes are listed in the table below:
Error Code Error Description
14 Data name not available only device S supported
15 Read-only database cell
16 Syntax error
17 Device number out of range only device 1 supported
18 Database cell number out of range database cell/packet not defined
19 Command not implemented
DeviceNet Interface
The DeviceNet interface allows a customer to integrate the UltraScan DSP
gauge into the control loop via the industry standard DeviceNet protocol.
This section is written with the assumption that the reader is knowledgeable
about the DeviceNet communication protocol and terms associated with this.
For more information about DeviceNet in general, please contact the Open
DeviceNet Vendor Association (ODVA).
Product Support
The UltraScan DSP supports the standard DeviceNet predefined master/slave
connection set. The supported connection types are: explicit messaging,
polled I/O, bit-strobe I/O, cyclic I/O, and change-of-state (COS) I/O.
Currently, the bit-strobe I/O connection provides no useful service the gauge
will respond with 8 zeroed bytes.
DeviceNet objects and services have been provided to allow full access to all
data and control through a single explicit message connection, or through a
combination of explicit messaging and I/O data. The choice of connection
types for controlling and monitoring the gauge will depend on the required data
update rates and available CAN bandwidth. The use of cyclic or COS with an
appropriate production inhibit time is recommended for efficiency. On reliable
networks, ACK suppression may be used on cyclic or COS connections to
further reduce CAN bandwidth utilization.
As an extension to the DeviceNet standard, the UltraScan gauge can also
support additional explicit messaging connections for secondary PCs, PLCs,
data loggers, or indicators. These secondary connections have no effect on
the explicit message or I/O connections being used for the predefined
master/slave connection set. Please seek additional information from Beta
LaserMike should use of an additional explicit message connection be
required.
DeviceNet Objects
This section describes the DeviceNet objects that are implemented within the
UltraScan DSP.
Identity Object (DeviceNet Class = 1)

The Beta LaserMike implementation supports the standard identity object
class/instance attributes and services required for the pre-defined
master/slave connection set.
The following identity object instance attributes are supported:
Attribute Description
VENDOR_ID The vendor ID.
16-bit UINT This is the fixed value 732: Beta LaserMike
read-only
DEVICE_TYPE Always returns 0x0000 to indicate a generic device (no standard profile is
16-bit UINT applicable).
read-only
PRODUCT_CODE The vendor specific product code.
16-bit UINT This is the fixed value 4000: UltraScan DSP Gauge
read-only
The implementation revision. The major revision is the first byte, and the
4 minor revision is the second byte (as a 16-bit number, the revision is in big-
REVISION endian format contrary to all other DeviceNet values). The major revision
number will be changed whenever there is a significant change to the fit,
UINT:UINT form, or function of the product. Only values 1 through 127 are allowed.
read-only The minor revision number will be changed for big-fixes, minor functional
changes, build differences, etc. Only values 1 through 255 are allowed.
5
STATUS Currently only bit 0 is defined. Bit 0 is set to 1 when the gauge is assigned
to a master (part of the pre-defined master/slave connection set has been
16-bit WORD allocated).
read-only
6
The Beta LaserMike assigned gauge serial number. Serial numbers should
SERIAL_NUM
be unique across all products produced by Beta LaserMike.
32-bit UDINT
PRODUCT_NAME
The descriptive product name.
short string
read-only
In addition to the get attribute service, the identity object also supports the
reset service. The reset service only resets the DeviceNet protocol stack
within the gauge, and does not affect the gauges measurement functions.
DeviceNet Object (DeviceNet Class = 3)

The Beta LaserMike implementation supports the standard DeviceNet object
class/instance attributes and services required for the pre-defined
master/slave connection set.
The following DeviceNet object instance attributes are supported:
Attribute Description
1 The MAC ID used by the device, between 0 and 63, inclusive. Writing to this
value causes the gauge to store the new MAC ID and then reset the
MACID
DeviceNet stack using the new value (behavior defined in the DeviceNet
8-bit USINT specification). There is no guarantee that the gauge will be able to resume
communication using the new MAC ID (it may be in use by another gauge or
read/write
device).
2 The CAN baud rate code. 0=125k, 1=250k, 2=500k. As defined by the
DeviceNet specification, changing this value has no immediate effect. To
BAUD_RATE
make the new baud rate take effect, the gauge must be physically reset (after
8-bit USINT allowing a few seconds for the value to be stored to non-volatile memory),
the MAC ID must be updated, or the reset service issued to the identity
read/write
object.
BUS_OFF_INTERRUPT Set this value to 0 to hold the gauge CAN controller in reset when a bus-off
interrupt occurs. Set this value to 1 to cause the gauge to reset and restart
8-bit BOOL DeviceNet communication when a bus-off interrupt occurs
read/write
Reading this attribute returns the number of bus-off events detected by the
4
device since it was powered up. The counter never increments beyond 255.
BUS_OFF_COUNTER If the BUS_OFF_INTERRUPT attribute is set to 0, then this value will only
increment to 1, but since the devices CAN controller will be held in reset, it
8-bit-USINT
will not be possible to read the new value.
read/write
Writing any value to this attribute causes the attribute to reset to 0.
ALLOC_INFO
Returns the pre-defined master/slave connection set allocation bits and
8-bit BYTE and 8-bit currently assigned master as detailed in the DeviceNet specification.
USINT
read-only
Assembly Object (DeviceNet Class = 4)

Output Data
The output data is consumed by the gauge. It is produced by the DeviceNet

master and is supplied to the gauge over the polled connection or using the
explicit message connection set attribute or vendor specific get and set
services.
Note that if the master instantiates a COS/Cyclic connection that, as per the
DeviceNet specification, the masters output data is actually transmitted over
the polled connection, but with a different production trigger mechanism. This
is perhaps a detail with which most programmers need not be concerned, but
it highlights the point that the gauge can only sensibly use the same assembly
object instance for consuming the masters polled or COS/Cyclic output data.
All output data is consumed by DeviceNet assembly object instances. The
length and meaning of the output data depends on the assembly object to
which the data is directed. Currently each connection type is associated with
a fixed assembly object instance:
Connection Assembly Object Consumed Connection Path

Type Instance
Polled or
1 0x20,0x04,0x24,0x01,0x30,0x03
COS/Cyclic I/O
Bit-Strobe I/O 2 0x20,0x04,0x24,0x02,0x30,0x03
The consumed connection path attribute describes the connection as

consuming data to the assembly object, the relevant instance, and the
assembly object data attribute.
Please note that at the current time, the produced connection path is fixed.
However, future implementation may provide further assembly objects (e.g.
instances 3, 4, 5, 6, etc.) that consume additional data or data in alternate
formats. These assembly objects could be dynamically selected, and
therefore developers of master applications should consider checking the
instance number within the consumed connection path attribute to ensure that
they are sending data to the gauge in the format expected by the consuming
assembly object.
Input Data
Input data is produced by the gauge. It is supplied to the DeviceNet master

over one or more I/O connections and/or using the explicit message
connection get attribute service.
All input data is produced from DeviceNet assembly object instances. The
length and meaning of the input data depends on the assembly object used to
format the data. With the DeviceNet pre-defined master/slave connection set,
the gauge is able to simultaneously produce data from the polled, bit-strobe
and COS/Cyclic connections. Although it is possible to produce data from
different assembly object instances for the polled and COS/Cyclic
connections, no sensible benefit could be derived from such an arrangement.
Production for bit-strobe connections is usually from a different assembly
object instance as bit strobe connections are restricted to producing up to 8
bytes of input data.
Currently each connection type is associated with a fixed assembly object
instance:
Connection Assembly Object Consumed Connection Path

Type Instance
Polled or
1 0x20,0x04,0x24,0x01,0x30,0x03
COS/Cyclic I/O
Bit-Strobe I/O 2 0x20,0x04,0x24,0x02,0x30,0x03
The produced connection path attribute describes the connection as

producing data from the assembly object, the relevant instance, and the
assembly object data attribute.
Please note that at the current time, the produced connection path is fixed.
Future implementations may provide further assembly objects (e.g., instances
3, 4, 5, 6, etc.) that provide additional data or data in alternate formats. These
assembly objects could be dynamically selected, and therefore developers of
master applications should consider checking the instance number within the
produced connection path attribute to ensure that the data they are receiving
is from the expected assembly object.
Explicit Messaging
The DeviceNet Master may supply output data over the explicit message
connection by using the set attribute service specifying the assembly object
class ID (0x04), the relevant instance number, and the data attribute number
(0x03).
The DeviceNet master may obtain input data over the explicit message
connection by using the get attribute service specifying the assembly object
class ID (0x04), the relevant instance number, and the data attribute number
(0x03).
It is therefore possible to implement a master application that does not require
the use of I/O connection types.
An additional vendor specific service has been implemented for the assembly
object that allows the output data to be set and the input data to be obtained
using a single service in preference to performing a set attribute request
followed by a get attribute request. This service, code 0x40 (64 decimal),
should be directed at the relevant assembly object instance and data
attribute as would be used for the get attribute and set attribute request.
Use of this service allows more efficient communication with the gauge in
those specific applications where I/O data exchange isnt being used (for
example where a secondary PLC/PC/indicator is being used and the I/O data
facility is unavailable).
Connection Object (DeviceNet Class = 5)

The UltraScan DSP gauge fully implements the DeviceNet group 2 only, pre-
defined master/slave connection set.
The gauge fully supports concurrent explicit messaging, polled I/O, bit-strobe
I/O, and COS/Cyclic connections.
COS/Cyclic connections may be acknowledged or unacknowledged, and all
the associated production/consumption paths, path lengths, production
triggers, and initial communication characteristics are configured appropriately
as per the pre-defined master/slave connection set instantiation rules.
Please note the following points regarding the DeviceNet pre-defined
master/slave connection set specification:
1) COS/Cyclic connections are mutually exclusive (they are the same
connection but with a different production trigger mechanism).
2) The master can only produce output data over the polled connection,
but may do so using the polled, change-of-state or cyclic mechanisms
according to how the connection was instantiated.
3) When the polled connection and the COS/Cyclic connection are
instantiated at the same time, or the polled connection is instantiated
followed by the COS/Cyclic connection, then the master supplies
output data to the gauge using the polled connection, and the gauge
provides input data to the master using both the polled connection and
the COS/Cyclic connection. This behavior is defined in the DeviceNet
specification.
4) The bit-strobe connection provides 1 bit of output data from the master
to each slave. The UltraScan DSP makes no use of this bit, but will
respond with appropriate bit-strobe input data (each response is limited
to 8-bytes, as per the DeviceNet specification).
Normally, the master control computers DeviceNet drivers/library will take
care of establishing connections according to the parameters supplied. See
the DeviceNet specification for exact details regarding attributes of the
connection class and connection instances. However, it is worth mentioning
here that the UltraScan DSP implementation fully supports the following
connection instance attributes (where appropriate to the connection type):
1) Expected packet rates: to a 10 ms resolution
2) ACK retry limit for acknowledged COS/Cyclic connections
3) ACK timeout: for acknowledged COS/Cyclic connections, to a 10 ms
resolution
4) Production inhibit time: for COS connections, to a 10 ms resolution
5) Watchdog timeout action: including time out (I/O-only), auto-delete,
auto-reset (I/O-only), and deferred delete (explicit message only)
UltraScan Database Object (DeviceNet Class = 102)

The UltraScan database object class ID of 102 (0x66) is within the vendor
specific range of object class identifiers. This object provides various vendor
specific services in order to allow simple and efficient control and monitoring of
the UltraScan DSP gauge function.
It is possible to use this object to collect miscellaneous measurements, or set
miscellaneous parameters. Many values can be read or written in a single
request, and they need not be contiguous within the UltraScan DSP internal
database.
Please refer to Appendix I for details about individual database items.
UltraScan DSP Database Instances
It is possible to use metric or imperial units when setting or retrieving

UltraScan DSP database items. The units used depend on the object instance
encoded within the request:
Units Format Database Object Instance
Metric 1
Imperial 2
The units to use are therefore specified on a request-by-request basis, and are
independent of any units being used for I/O data communication or for service
requests through alternate explicit message connections (e.g., data loggers,
remote indicators, etc).
There are no services provided at the class level, and therefore attempts to
access object instance 0, the class-level instance, will fail with a service not
supported error.
Requests to access any instance greater than 2 will fail with an object does
not exist error.
UltraScan DSP Database Services
The UltraScan DSP Database object provides its own vendor-specific services
for access.
Enumeration Service (service code 64/0x40)
This service allows the internal UltraScan DSP database to be enumerated.

There is no requirement to enumerate the database Appendix I Database
Layout of this document provides details of the database item identifiers,
types, and access permissions, and it is possible to use this published
information directly with the other database services. The enumeration
service allows generic test programs to be written that have no prior
knowledge of the UltraScan DSP database.
The DeviceNet master provides exactly 3 bytes of services related data:
Type Description
UChar The maximum number of database items to enumerate
UShort The starting enumeration index
The gauge will provide an appropriate error response if there arent exactly
three service data bytes, or if the maximum number of items to enumerate is
excessive.
The gauge response data is an array of between 0 and the maximum number
of requested enumeration results. Each enumeration result has the following
form:
Type Description
UShort Database item identifier. This is the identifier to be used with other
database services
UChar Database item type:
0=long, 1=float, 2=string, 255=unknown
UChar Database item access bit-wise flags:
0x01 = Non-Volatile
0x02 = Read-Only
0x04 = Constant (not changed by the gauge)
Usually the DeviceNet master would begin with an enumeration index of 0,

and increase it by the number of items successfully enumerated in each
request. Enumeration is complete when the gauge responds with fewer
enumeration items than the maximum number requested by the DeviceNet
master. The gauge will respond with zero items if there are no more items to
enumerate.
Min/Max Service (service code 65/0x41)
This service allows determination of the valid range for a database long or
float, or the maximum size of a database string. There is no requirement to
use this service. Appendix I Database Layout of this document provides
details of database item ranges and other information. The min/max service
allows generic test programs to be written that have no prior knowledge of the
UltraScan DSP database.
The DeviceNet master must have explicit knowledge of the database item
types for each specific database item identifier, and deal with the response
data appropriately according to type.
The DeviceNet master provides an array of database item identifiers for which
the min/max range is required. At least one identifier must be provided, and
the total array size must be a multiple of two bytes (since each identifier is a
16-bit unsigned short).
Type Description
UShort The identifier of the database item for which min/max information is
required.
The gauge will provide an appropriate error response if there isnt at least one
identifier, the number of service data bytes isnt a multiple of two, there is
insufficient buffer space to generate a response for all requested identifiers, or
if there is no corresponding database item for any of the specified identifiers.
The gauge response data is an array of information, with the number of array
entries being equal to the number of database identifiers specified in the
request. Each item in the response array has the following form:
Type Description
Long or The minimum value for the database item. For a long database
Float item this is a 32-bit signed integer. For a float database item this is a
32-bit IEEE floating point value. For a string database item, this is
a 32-bit signed integer with the value 0.
Long of The maximum value for the database item. For a long database
Float item this is a 32-bit signed integer. For a float database item this is
a 32-bit IEEE floating point value. For a string database item this is
a 32-bit signed integer indicating the maximum string length of the
string (maximum number of non-null characters).
Get Longs/Floats Service (service code 66/0x42)
This service allows the current values of database longs and floats to be
obtained.
The DeviceNet master provides an array of database item identifiers for which
the current values are required. At least one identifier must be provided, and
the total array size must be a multiple of two bytes (since each identifier is a
16-bit unsigned short).
Type Description
UShort The identifier of the database item to be read
identifier, the number of service data bytes isnt a multiple of two, there is
insufficient buffer space to generate a response for all requested identifiers, or

one or more of the specified database items isnt a long or float type.
The gauge response data is an array of information, with the number of array
entries being equal to the number of database identifiers specified in the
request. Each item in the response array has the following form:
Type Description
Long or The current value for the database item. For a long database item
Float this is a 32-bit signed integer. For a float database item this is a 32-
bit IEEE floating point value.
Set Longs/Floats Service (service code 67/0x43)
This service allows the values of database longs and floats to be written.
types for each specific database item identifier, and format the request data
appropriately according to type.
The DeviceNet master provides an array of request structures. At least one
request structure must be provided, and the total array size must be a multiple
of six bytes.
Type Description
UShort The identifier of the database item to be written to
Long or The required value for the database item. For a long database item
Float this is a 32-bit signed integer. For a float database item this is a 32-
bit IEEE floating point value.
request structure, the number of service data bytes isnt a multiple of six, one
or more of the specified database items isnt a long or float type, or the
database item is read-only or constant.
Note: Items are processed in order one or more items may be successfully
processed before an error is generated upon detection of an invalid
identifier or value.
The gauge does not provide any service response data.
Get String Service (service code 68/0x44)
This service allows a database string to be obtained.

The DeviceNet master provides a single database string item identifier.
Type Description
UShort The identifier of the database string to be read
The gauge will provide an appropriate error response if there isnt exactly one
identifier, or if the database item specified isnt a string type.
The gauge response data is an array of characters containing the string data.
The gauge sends no null-terminator. The DeviceNet master must null
terminate the string if required.
Set String Service (service code 69/0x45)
This service allows a database string to be written.

types for each specific database item identifier.
The DeviceNet master provides a single database string item identifier and
zero or more characters containing the string data (no null terminator is
transmitted):
Type Description
UShort The identifier of the database string to be written
Char * N The string data (no null terminator)
The gauge will provide an appropriate error response if there isnt exactly one
identifier, the database item specified isnt a string type, or the database item
is read-only or constant.
The gauge does not provide any service response data.
DeviceNet I/O Data

See the FieldBus I/O chapter later in this document for a description of the
formats of the output and input page formats.
CANopen Interface
There are many ways to change the CAN settings:
through the DeviceNet DNET object
through the DeviceNet objects that provide access to the UltraScan
database
through the CANopen objects that provide access to the UltraScan
database
through the RS232 protocol that provides access to the UltraScan
database
After changing the CAN settings, wait at least 5 seconds for the new value to
be save to non-volatile memory, and then reset the gauge for the new setting
to become effective.
DeviceNet MACID / CANopen Node ID

The DeviceNet MACID or CANopen Node ID is configured using UltraScan
database item number 120. This is an integer record that may take a value
between 0 and 255. The default value is 63 (DeviceNet MACID 64).
Since DeviceNet and CANopen cannot be used simultaneously on the same
interface, the value of database item 120 allows selection between the two
CAN based protocols, as well as the MACID / Node ID to use for the required
protocol:
Database
Protocol MACID / Node ID
item 120
0 - 63 DeviceNet MACID = 0 - 63
64 - 128 None
129 - 255 CANopen Node ID = 1 - 127 (database item 120 value with bit 7 masked).
CAN / DeviceNet / CANopen Baud Rate

The CAN baud rate, for any CAN protocol, is configured using UltraScan
database item number 121. This is an integer record that may take a value
between 0 and 2. The default value is 0. The following table shows the
relevant values for different baud rates:
Database
CAN Baud Rate
item 121
0 125 k-bits per second
CAN / DeviceNet / CANopen Bus Off Interrupt Action

The CAN Bus-Off Interrupt (BOI) action, for any CAN protocol, is configured
using UltraScan database item number 122. This is an integer record that may
take a value between 0 and 1. The default value is 0. The following table
shows the relevant BOI values:
Database
BOI Action
item 122
Stay in bus-off state

0
The gauge will need to be reset for the CAN protocol to resume.
Reset the CAN protocol stack.

The relevant CAN protocol will be restarted. Note that it may endlessly
1
go bus-off and restart if there is a CAN baud rate mismatch, or if there
is a physical CAN network fault.
The UltraScan gauge supports the following CANopen protocols:

The NMT management protocol
The heartbeat producer protocol
The heartbeat consumer protocol
The nodeguard protocol (if the heartbeat protocol is unused)
The lifeguard protocol (if the heartbeat protocol is unused)
The SDO protocol (including large segmented transfers)
The PDO protocol
CANopen data dictionary objects have been provided to allow full access to all
data and control through an SDO connection. Up to 160 data bytes may be
communicated through a segmented SDO upload / download. Combined with
the availability of the IODATA formats, and multi-database item access
objects, an SDO connection can be used to efficiently exchange significant
amounts of information.
The UltraScan gauge supports the standard default SDO (data dictionary item
0x1200), as well as a single additional SDO (data dictionary item 0x1201). The
additional SDO allows a connection for a secondary PC, PLC, data logger, or
indicator. The additional SDO must be configured through the default SDO
before it may be used.
The UltraScan gauge supports 2 Rx PDOs and 32 Tx PDOs. The Rx PDOs
and the first four Tx PDOs are pre-configured for the following COBIDs:
RXPDO1 0x0200 + node ID TXPDO1 0x0180 + node ID
RXPDO2 0x0300 + node ID TXPDO2 0x0280 + node ID
TXPDO3 0x0380 + node ID
TXPDO4 0x0480 + node ID

The remaining Tx PDOs do not have a predefined COBID: these must be
configured using carefully selected COBIDs that are not used by other nodes
in the system.
Dynamic mapping is supported for all Tx and Rx PDOs, up to a limit of 8 data
dictionary items per PDO. After power-up none of the PDOs have any
assigned dynamic mappings. Each required PDO must be mapped to data
dictionary items by writing to the relevant PDO mapping sub-parameters as
defined in the CANopen specification. The gauge will reject attempts to set
PDO mappings if the number of mappings for the PDO is non-zero, or if an
attempt is made to map a data dictionary item that cannot be mapped. Tx
PDOs will not be transmitted unless the PDO has been successfully mapped.
Rx PDO data will not be consumed unless the PDO has been successfully
mapped.
All PDO transmission types are supported, with the exception of remote frame
requests:
Transmission Type 0 : acyclic synchronous
Transmission types 1 through 240 : cyclic synchronous
Transmission types 254 and 255 : asynchronous
The PDO inhibit time is supported for both acyclic synchronous and
asynchronous Tx PDO transmission types. For Rx PDOs the inhibit time is
used to reduce the rate at which Rx PDO data is consumed: providing a
mechanism to prevent the gauge become overloaded if the receive rate of the
Rx PDO data is too high and cannot be externally reduced. The PDO event
time is supported for both acyclic synchronous and asynchronous Tx PDO
transmission types: expiration of the event time triggers production from a Tx
PDO regardless of the inhibit time. Production for acyclic synchronous and
asynchronous Tx PDOs is also triggered by a change of the PDOs data, but
only if the inhibit time has expired.
CANopen Data Dictionary Objects
Objects 0x0001 - 0x0007 : Simple Data Types

The standard CANopen pre-defined data types at data dictionary entries
0x0001 through 0x0007 are available to be mapped into Rx PDOs as
mappings for the parts of any Rx PDO for which some content is not relevant
to the UltraScan gauge.
These items cannot be read, or mapped to Tx PDOs. They are purely for Rx
PDO mappings, and are as follows:
0x0001 BOOLEAN 1 byte (see note below)
0x0002 INTEGER8 1 byte
0x0003 INTEGER16 2 bytes
0x0004 INTEGER32 4 bytes
0x0005 UNSIGNED8 1 byte
0x0006 UNSIGNED16 2 bytes
0x0007 UNSIGNED32 4 bytes
Note that the UltraScan gauge does not support single bit quantities, and
therefore a BOOLEAN type consumes 8-bits of any Rx PDO into which it is
mapped.
Object 0x1000 : Device Type

Index 0x1000
Name Device type
Object type Variable
Sub-index 0x00
Name Device type
Data type UNSIGNED32
PDO mapping No
Access Read only
Value 0x00000000
The value 0x00000000 indicates the gauge does not follow a standardised
device profile.
Object 0x1001 : Error Register

Index 0x1001
Name Error register
Sub-index 0x00
Name Error register
Data type UNSIGNED8
PDO mapping Yes
Access Read only
Value 0x00 Gauge and communications OK.
0x01 NMT master guarding timeout or at least 1 Rx PDO event

timer has expired.
Object 0x1005 : Sync message COB-ID

Index 0x1005
Name Sync message COB-ID
Sub-index 0x00
Name Sync message COB-ID
PDO mapping No
Access Read + Write
Value Default value = 0x00000080.
The default value will usually be correct for most CANopen networks, but may
be set to any valid 11-bit CAN message ID for special network configurations.
Attempts to set a 29-bit CAN ID, or to set the sync producer bit will fail.
Object 0x1008 : Manufacturer Device Name

Index 0x1008
Name Manufacturer device name
Sub-index 0x00
Name Manufacturer device name
Data type Visible string
PDO mapping No
Access Read only
Value For example: "Ultrascan 1063"
Object 0x1009 : Hardware Version

Index 0x1009
Name Hardware version
Sub-index 0x00
Name Hardware version
PDO mapping No
Access Read only
Value For example: "Rev H, Thu Feb 05 08:10:05 2004"

Currently this string is the same as the software version (object 0x100A)
Object 0x100A : Software Version

Index 0x100A
Name Software version
Sub-index 0x00
Name Software version
PDO mapping No
Access Read only
Value For example: "Rev H, Thu Feb 05 08:10:05 2004"

Currently this string is the same as the hardware version (object 0x1009)
Object 0x100C : Guard Time

Index 0x100C
Name Guard time
Sub-index 0x00
Name Guard time
PDO mapping No
Access Read + Write

The guard time in milliseconds.
The node guarding and life guarding protocols are disabled if either the
heartbeat protocol is being used, or if the guard time is zero. If the heartbeat
protocol is not in use, then setting the guard time to a non-zero number of
milliseconds enables the node guarding protocol (the UltraScan will respond to
the node guard remote frames sent by the CANopen master). Both the guard
time and life-time factor must be non-zero to enable the life-guarding protocol.
Object 0x100D : Life Time Factor

Index 0x100C
Name Life time factor
Sub-index 0x00
Name Life time factor
Data type UNSIGNED8
PDO mapping No
Access Read + Write
The life time factor multiplied by the guard time gives the life time for the life
guarding protocol. This is the number of milliseconds during which at least one
node guarding remote frame must be received from the CANopen master. The
life guarding protocol is disabled if either the heartbeat protocol is being used,
the guard time is zero, or the life time factor is zero.
Object 0x1016 : Consumer Heartbeat Time

Index 0x1016
Name Consumer heartbeat time
Object type Array
Sub-index 0x00
Name Number of array entries
Data type UNSIGNED8
PDO mapping No
Access Read only
Value 1 (can consume heartbeats from 1 heartbeat producer).
Sub-index 0x01
Name Consumer heartbeat time 1
PDO mapping No
Access Read + Write
Value Default = 0x00000000

See description below for data bit usage.
Array entries from 1 upward are UNSIGNED32, and have the following format:
Bits 31-24 Bits 23-16 Bits 15-0
UNSIGNED8 UNSIGNED8 UNSIGNED16
Reserved (0) Producer node ID Heartbeat timeout value in milliseconds
Setting bits 15 through 0 to zero disables an array entry. When bits 15 through
0 are non-zero, then a heartbeat message is expected from the corresponding
producer node ID (using COB-ID 0x00000700 + producer node ID) within the
specified number of milliseconds.
Object 0x1017 : Producer Heartbeat Time

Index 0x1017
Name Producer heartbeat time
Sub-index 0x00
Name Producer heartbeat time
PDO mapping No
Access Read + Write
The heartbeat producer time in milliseconds.
Setting this value non-zero causes the gauge to use the heartbeat protocol
(disables the node guarding and life guarding protocols), and a heartbeat
message will be produced at the specified time intervals using COB-ID
0x00000700 + gauge node ID.
Object 0x1018 : Identity Object

Index 0x1018
Name Identity object
Object type Record
Sub-index 0x00
Name Number of entries
Data type UNSIGNED8
PDO mapping No
Access Read only
Value 4
Sub-index 0x01
Name CANopen vendor ID
PDO mapping No
Access Read only
Value 0x00000000
Sub-index 0x02
Name Manufacturers product code
PDO mapping No
Access Read only
Value 0x00000000
Sub-index 0x03
Name Revision number
PDO mapping No
Access Read only
Value 0x00010000
Sub-index 0x04
Name Serial number
PDO mapping No
Access Read only
Value The numeric representation of the gauges serial number.
Object 0x1200 - 0x127F : Server SDO Parameters

Index 0x1200 - 0x127F (shadowed at 0x5200 - 0x527F)
Name Server SDO parameters
Object type Record

0x1200 = default SDO
0x1201 = additional SDO
0x1202 - 0x127F = not supported
Sub-index 0x00
Data type UNSIGNED8
PDO mapping No
Access Read only
Value 2
Sub-index 0x01
Name COB-ID client (Tx) -> server (Rx)
Data type UNSIGNED32 (see COB-ID format below)
PDO mapping No
Access Read + Write
Value Default values:

default SDO (0x1200) = 0x00000600 + gauge node ID
additional SDOs (0x1201 - 0x127F) = 0x80000000 (disabled)
Sub-index 0x02
Name COB-ID server (Tx) -> client (Rx)
PDO mapping No
Access Read + Write

default SDO (0x1200) = 0x00000580 + gauge node ID
additional SDOs (0x1201 - 0x127F) = 0x80000000 (disabled)
Sub-index 0x80
Name SDO non-standard special features enable register

Beta LaserMike specific (see description below)
Data type UNSIGNED8
PDO mapping No
Access Read + Write
Value Default value = 0x00
The 32-bit values represent COB-IDs are formatted as shown below:

Bit 31 Bit 30 Bit 29 Bits 28 - 11 Bits 10 - 0
0/1 0 0 000000000000000000 11-bit identifier
0/1 0 1 29-bit identifier (not supported)
Note that for an SDO to be operational both COB-IDs (at sub-index 1 and sub-
index 2) must have bit 31 set to 0 for the SDO to be operational. Thus
additional SDOs must be configured before they may be used. The UltraScan
gauge does not currently support 29-bit COB-IDs.
The SDO non-standard special features enable register at sub-index 0x80

provides a mechanism for coping with certain CANopen clients that do not
properly support the SDO protocol specification. This 8-bit register value is
'hidden in that it is not included within the number of entries defined at sub-
index 0x00. The format of this 8-bit register is as follows:
Bit 0 If bit 0 is non-zero, then the SDO segmented download protocol is modified
such that the final segmented SDO download message contains the originally
requested data dictionary index and sub-index values. This is necessary for
use with Beckhoff TwinCAT systems that will reject a final message of a
segmented SDO download if that final message is properly CANopen
compliant.
Bits 1 - 7 Spare
Note that all of the SDO server objects are shadowed at 0x5200 through
0x527F. This allows the server SDO parameters to be accessed when using
systems such as Beckhoff TwinCAT which may otherwise prevent these
parameters from being accessed directly.
Object 0x1400 - 0x15FF : Receive PDO Comms Parameters

Index 0x1400 - 0x15FF (shadowed at 0x5400 - 0x55FF)
Name Receive PDO communications parameters
Object type Record

0x1400 (shadowed at 0x5400) Rx PDO1
etc (up to number of supported Rx PDOs)
Sub-index 0x00
Data type UNSIGNED8
PDO mapping No
Access Read only
Value 5
Sub-index 0x01
Name COB-ID
PDO mapping No
Access Read + Write

Rx PDO1 0x00000200 + gauge node ID
Any other supported Rx PDOs = 0x80000000 (disabled)
Sub-index 0x02
Name Transmission type (of remote PDO producer)
Data type UNSIGNED8
PDO mapping No
Access Read + Write
Value Default = 255
For Rx PDOs the following transmission types are supported:
0 Data is received asynchronously, but only used when the next

SYNC is received
1 - 240 Data is received every N SYNC cycles, but only used when the
next SYNC is received
254 - 255 Data is received asynchronously and used as soon

as it is received
Sub-index 0x03
Name PDO inhibit timer
PDO mapping No
Access Read + Write
Value Default = 0
For Rx PDOs this parameter is not normally used on CANopen nodes.

However, for the UltraScan gauge, this value can be set to the number
of 100 micro-second periods that must have elapsed since the PDO
was previously processed before any newly received PDO data will be
processed. This can be useful if it is not possible to reduce the
production rate of a PDO that would otherwise overload the UltraScan
gauge. For example, if a CANopen line-speed indicator is producing a
PDO every 10ms, but the UltraScan gauge must only process the PDO
once per second, then set this value to 10000).
Some CANopen masters (e.g. TwinCAT) may block attempts to

configure this parameter - use the shadow data dictionary object ID
range to overcome any such problems.
Sub-index 0x04
Name Reserved
Data type Reserved
PDO mapping No
Access None
Sub-index 0x05
Name PDO event timer
PDO mapping No
Access Read + Write

The event timer value in milliseconds.
The Rx PDO event time is used to time-out Rx PDOs.

NB: Some CANopen masters (e.g. TwinCAT) incorrectly set the event
timer for an Rx PDO to be the same as the event timer for the
corresponding asynchronous Tx PDO : this leads to erratic PDO
timeouts, and it may be necessary to take action to ensure that this
value is set to a larger value. Some CANopen masters (eg TwinCAT)
may block attempts to configure this parameter - use the shadow data
dictionary object ID range to overcome any such problems.
Object 0x1600 - 0x17FF : Receive PDO Mapping Parameters

Name Receive PDO mapping parameters
Object type Record

etc (up to number of supported Rx PDOs)
Sub-index 0x00
Name Number of mapped data dictionary objects for the PDO
Data type UNSIGNED8
PDO mapping No
Access Read + Write
Value Default = 0, maximum = 8

The receive PDO will not be processed if this parameter is set to zero
(since there are no mappings!). An attempt to set the number of
mappings to a non-zero value will fail if any of the mappings within the
intended range are not valid, or if the total mapped data size exceeds
64 bits (8 bytes).
Sub-index 0x01 through 0x08
Name PDO mapping for the Nth data dictionary object to be mapped
PDO mapping No
Access Read + Write (read only if sub-index 0x00 is non-zero)

Attempts to set a mapping will only succeed if the value written
specifies a data dictionary index and sub-index that may be mapped.
When mapping to data dictionary items it is important to use the correct
bit length - 32 bits for all UltraScan integer and floating point database
items. It is not possible to map UltraScan database strings to PDOs.
The individual mapping parameters at sub-index 0x01 upwards (as required)

may only be written when the number of mappings is zero. After assigning the
appropriate mappings, the number of mappings (at sub-index 0x00) should be
set to the required non-zero value. If the mappings must be dynamically
altered while the gauge is operational, then the number of mappings must be
set to zero before any re-mapping may take place.
A mapping parameter takes the following form:

Bits 31 - 16 Bits 15 - 8 Bits 7 - 0
Index Sub-index Object length (in bits!)
It is most likely that a receive PDO will be configured to consume line speed.
The following example shows how this may be affected in order to consume a
32-bit floating point line speed in meters per second (metric):
Bits 31 - 16 Bits 15 - 8 Bits 7 - 0
The UltraScan linespeed is data base For metric Database item 328 is a
item 328, and the data base items are access we floating point value, which is
accessed at data dictionary 0x2000 required sub- 32 bits.
upwards, therefore the required data index 2
dictionary item is 0x2000 + 328 =
0x2000 + 0x0148 = 0x2148
0x2148 0x02 0x20
So, for example, setting data dictionary index 0x1600 sub-index 1 to

0x21480220, and then setting data dictionary index 0x1600 sub-index 0 to 1
configures Rx PDO1 to accept a 4-byte value, and to place that value into the
line-speed entry of the UltraScan data base using metric units.
Object 0x1800 - 0x19FF : Transmit PDO Comms Parameters

Name Transmit PDO communications parameters
Object type Record

0x1800 (shadowed at 0x5800) Tx PDO1
0x1801 (shadowed at 0x5801) Tx PDO2
etc (up to number of supported Tx PDOs)
Sub-index 0x00
Data type UNSIGNED8
PDO mapping No
Access Read only
Value 5
Sub-index 0x01
Name COB-ID
PDO mapping No
Access Read + Write

Tx PDO1 0x00000180 + gauge node ID
All other supported Tx PDOs = 0x80000000 (disabled)
Sub-index 0x02
Name Transmission type
Data type UNSIGNED8
PDO mapping No
Access Read + Write
Value Default = 255
For Tx PDOs the following transmission types are supported:
0 Data is prepared asynchronously whenever the PDO

data content changes (provided the inhibit timer has
expired) or if the event timer has expired (regardless
of the inhibit timer), but only transmitted when the
next SYNC is received
1 - 240 Data is updated continuously, but only transmitted

every N SYNC cycles
254 - 255 Data is transmitted asynchronously when the PDO

data content changes (provided the inhibit timer has
expired), or if the event timer has expired (regardless
of the inhibit timer).
Sub-index 0x03
Name PDO inhibit timer
PDO mapping No
Access Read + Write
Value Default = 0
For Tx PDOs transmission types of 0 (acyclic synchronous) or 254/255

(asynchronous) this parameter specifies the minimum time in 100
micro-second periods that must have elapsed since the PDO was
previously transmitted before the PDO will be transmitted again as a
result of the PDO data content changing. Such PDOs will produce
regardless of the inhibit timer if the PDO event timer expires.
The Tx PDO inhibit time is ignored for transmission types 1 - 240

(cyclic).
Sub-index 0x04
Name Reserved
Data type Reserved
PDO mapping No
Access None
Sub-index 0x05
Name PDO event timer
PDO mapping No
Access Read + Write

The event timer value in milliseconds.
Expiration of a Tx PDO event timer is used to determine when a PDO

with transmission type 0 (acyclic synchronous) or 254 - 255
(asynchronous) should produce a new message, whether or not the
PDO data content has changed.
The Tx PDO event timer is ignored for transmission types 1 - 240

(cyclic).
Object 0x1A00 - 0x1BFF : Transmit PDO Mapping Parameters

Index 0x1A00 - 0x1BFF (shadowed at 0x5A00 - 0x5BFF)
Name Transmit PDO mapping parameters
Object type Record

0x1A00 (shadowed at 0x5A00) Tx PDO1
0x1A01 (shadowed at 0x5A01) Tx PDO2
etc (up to number of supported Tx PDOs)
Sub-index 0x00
Name Number of mapped data dictionary objects for the PDO
Data type UNSIGNED8
PDO mapping No
Access Read + Write
Value Default = 0, maximum = 8

The Tx PDO will not produce any CAN message if this parameter is set
to zero (since there are no mappings!).
Sub-index 0x01 through 0x08
Name PDO mapping for the Nth data dictionary object to be mapped
PDO mapping No
Access Read + Write (read only if sub-index 0x00 is non-zero)

Attempts to set a mapping will only succeed if the value written
specifies a data dictionary index and sub-index that may be mapped. It
is possible to request fewer data bytes (multiples of 8 bits) that the size
of the data dictionary item, but this only makes sense for items such as
gauge status, transducer status, etc, and floating point items should
always be accessed using 32-bit item lengths. It is not possible to map
UltraScan database strings to PDOs.
The individual mapping parameters at sub-index 0x01 upwards (as required)

may only be written when the number of mappings is zero. After assigning the
appropriate mappings, the number of mappings (at sub-index 0x00) should be
set to the required non-zero value. If the mappings must be dynamically
altered while the gauge is operational, then the number of mappings must be
set to zero before any re-mapping may take place.
A mapping parameter takes the following form:

Bits 31 - 16 Bits 15 - 8 Bits 7 - 0
It is most likely that a transmit PDO will be configured to produce wall

thickness information. The following example shows how this may be affected
in order to produce the layer 1 minimum wall thickness information in metric
units:
Bits 31 - 16 Bits 15 - 8 Bits 7 - 0
The UltraScan layer 1 minimum wall For metric Database item 523 is a
measurement is data base item 532, access we floating point value, which
and the data base items are accessed required sub- is 32 bits.
at data dictionary 0x2000 upwards, index 2
therefore the required data dictionary
item is
0x2000 + 532
= 0x2000 + 0x0214
= 0x2214
0x2214 0x02 0x20
Likewise for layer 1 minimum wall angle (database item 533) which is data
dictionary index 0x2215. So, for example, by setting data dictionary items in
the following order:
index 0x1A00 sub-index 1 to 0x22140220
index 0x1A00 sub-index 2 to 0x22150220
index 0x1A00 sub-index 0 to 1
Tx PDO1 is configured to produce the layer 1 minimum wall thickness and
minimum wall angle in metric units.
Object 0x2000 - 0x3FFF : UltraScan Database

This part of the manufacturer specific data dictionary area is used to access
the UltraScan database. This database is the area in which all readings,
status, and control reside. CANopen data dictionary object indices 0x2000
through 0x3FFF is used to provide access to single database items (other
object indices are available for reading/writing multiple database items).
The UltraScan database and associated item numbers are documented
elsewhere. To convert a UltraScan database item number into a CANopen
data dictionary index, add the constant 0x2000. Attempts to access data
dictionary indices for which there is no corresponding database item will result
in an no object error.
Index 0x2000 - 0x3FFF
Name UltraScan database items
Object type Record
Sub-index 0x00
Data type UNSIGNED8
PDO mapping No
Access Read only
Value 7
Sub-index 0x01
Name Database item type and flags
PDO mapping No
Access Read only
Value See table below
Sub-index 0x02
Name Database item value in metric units
Data type SIGNED32, FLOAT32, or Visible String
PDO mapping Yes (for SIGNED32 and FLOAT32 items only)
Access Read + Write (non-constant and not read-only items)

Read only (constant or read only database items)
Value Depends on database item.

NB: String values are the same when accessed through either sub-
index 0x02 (metric units) or sub-index 0x03 (imperial units)
Sub-index 0x03
Name Database item value in imperial units
Data type SIGNED32, FLOAT32, or Visible String
PDO mapping Yes (for SIGNED32 and FLOAT32 items only)
Access Read + Write (non-constant and not read-only items)

Read only (constant or read only database items)
Value Depends on database item.

NB: String values are the same when accessed through either sub-
index 0x02 (metric units) or sub-index 0x03 (imperial units)
Sub-index 0x04
Name Minimum value in metric units
Data type SIGNED32, FLOAT32
PDO mapping No
Access Read only
Value For 32-bit long or 32-bit float database items this value represents the
minimum value that the database item may take in metric units. For
string items this value always returns 0.
Sub-index 0x05
Name Minimum value in imperial units
Data type SIGNED32 or FLOAT32
PDO mapping No
Access Read only
minimum value that the database item may take in imperial units. For
string items this value always returns 0.
Sub-index 0x06
Name Maximum value in metric units
PDO mapping No
Access Read only
maximum value that the database item may take in metric units. For
string items this value returns the maximum string length.
Sub-index 0x07
Name Maximum value in imperial units
PDO mapping No
Access Read only
maximum value that the database item may take in imperial units. For
string items this value returns the maximum string length.
The 16-bit database item type and flags at sub-index 0x01 is encoded as
follows:
Bit 15 Reserved (0)
Bit 14 Reserved (0)
Bit 13 Reserved (0)
Bit 12 Reserved (0)
Bit 11 Reserved (0)
Bit 10 0 = database item is non-constant

1 = database item is constant
Bit 9 0 = database item is read + write

1 = database item is read only
Bit 8 0 = database item is volatile

1 = database item is non-volatile (retained when power is removed)
Bits 7 - 0 An 8-bit value with one of the following values:

0x00 = database item is a 32-bit long integer
0x01 = database item is a 32-bit floating point value
0x02 = database item is a string
0xFF = database item type is unknown
Object 0x4000 : UltraScan Database Multi Access

This part of the manufacturer specific data dictionary area is used to
simultaneously access multiple items within the UltraScan database. Multiple
access works by uploading a number of items (when reading or writing), and
then downloading the results (when reading) from the same data dictionary
index and sub-index at any subsequent time, provided that there is no
intervening asymmetric upload/download access.
Index 0x4000
Name UltraScan database multi item access
Object type Record
Sub-index 0x00
Data type UNSIGNED8
PDO mapping No
Access Read only
Value 7
Sub-index 0x01
Name Enumerate database items
Data type Upload: 16-bit item count (LSW) and 16-bit starting database index
(MSW) (NB: this is a database index, not a database ID - the IDs are
returned in the enumeration data response). Maximum item count = 40.
Download: enumeration data, 32-bits per database item enumerated, or
one 0xFFFFFFFF value if there are no more database items to be
enumerated.
PDO mapping No
Access Read + Write (asymmetric)
Value See table below
Sub-index 0x02
Name Read multiple database item values in metric units
Data type Upload: multiple 16-bit database item IDs (up to a maximum of 40 IDs).
Download: item values in metric units at the time the upload data was
received and processed. 4-bytes per database item requested,
SIGNED32 or FLOAT32, as appropriate for each requested database
item.
PDO mapping No
Value The database item values.
The request will fail if any of the requested database items do not exist
or cannot be read using this service (eg string values).
Sub-index 0x03
Name Read multiple database item values in imperial units
Download: item values in imperial units at the time the upload data was
received and processed. 4-bytes per database item requested,
SIGNED32 or FLOAT32, as appropriate for each requested database
item.
PDO mapping No
Value The database item values.
The request will fail if any of the requested database items do not exist
or cannot be read using this service (eg string values).
Sub-index 0x04
Name Write multiple database item values in metric units
Data type Upload: multiple 48-bit structures, one per item to be written. Each 48-
bit structure comprises a 16-bit database item ID followed by a 32-bit
metric value encoded as SIGNED32 or FLOAT32 as appropriate for the
database item. A maximum of 26 items may be simultaneously written
using this sub-index.
Download: not applicable.
PDO mapping No
Access Write only
Value Each item is processed in the order in which it appears within the
upload data, and the request is abandoned if an encountered database
item does not exist or cannot be written using this service (eg string
values). Thus if the request fails it is not possible to determine which of
the requested items were processed, and which were not - in practice
only valid database items would be written to, and this technicality can
be ignored.
Sub-index 0x05
Name Write multiple database item values in imperial units
Data type Upload: multiple 48-bit structures, one per item to be written. Each 48-
bit structure comprises a 16-bit database item ID followed by a 32-bit
imperial value encoded as SIGNED32 or FLOAT32 as appropriate for
the database item. A maximum of 26 items may be simultaneously
written using this sub-index.
Download: not applicable.
PDO mapping No
Access Write only
Value Each item is processed in the order in which it appears within the
upload data, and the request is abandoned if an encountered database
item does not exist or cannot be written using this service (e.g. string
values). Thus if the request fails it is not possible to determine which of
the requested items were processed, and which were not - in practice
only valid database items would be written to, and this technicality can
be ignored.
Sub-index 0x06
Name Multiple min/max values in metric units
Download: minimum and maximum item values in metric units. 8-bytes
per database item requested, 2*SIGNED32 or 2*FLOAT32, as
appropriate for each requested database item.
For string items the minimum value will be 0, and the maximum value
represents the maximum string length in bytes.
PDO mapping No
Value The request will fail if any of the requested database items do not exist.
Sub-index 0x07
Name Multiple min/max values in imperial units
Download: minimum and maximum item values in imperial units. 8-
bytes per database item requested, 2*SIGNED32 or 2*FLOAT32, as
appropriate for each requested database item.
For string items the minimum value will be 0, and the maximum value
represents the maximum string length in bytes.
PDO mapping No
Value The request will fail if any of the requested database items do not exist.
The 32-bit enumeration data returned for each enumerated database item
using sub-index 0x01 is encoded as follows:
Bit 31 Reserved (0)
Bit 30 Reserved (0)
Bit 29 Reserved (0)
Bit 28 Reserved (0)
Bit 27 Reserved (0)
Bit 26 0 = database item is non-constant

1 = database item is constant
Bit 25 0 = database item is read + write

1 = database item is read only
Bit 24 0 = database item is volatile

1 = database item is non-volatile (retained when power is removed)
Bits 23 - 16 An 8-bit value with one of the following values:

0x00 = database item is a 32-bit long integer
0x01 = database item is a 32-bit floating point value
0x02 = database item is a string
0xFF = database item type is unknown
Bits 15 - 0 A 16-bit unsigned number representing the database item ID. This ID is the
value that is used when accessing single database items using data
dictionary items 0x2000 through 0x3FFFF (by adding 0x2000), or when
accessing multiple database items when using this data dictionary index (in
which case database IDs are used unmodified).
Object 0x4001 : UltraScan Formatted IODATA Page Access

This part of the manufacturer specific data dictionary area is used to access
the UltraScan IODATA format pages. The access is asymmetric: the output
format data is uploaded first, and then the input format response data is
downloaded from the same data dictionary index and sub-index. Since the
uploaded output formatted data is very small (as little as two bytes), this is a
very efficient way of multiplexing large quantities of readings for various
transducers, layers, etc.
Index 0x4001
Name UltraScan formatted IODATA page access
Sub-index 0x00
Name UltraScan formatted IODATA page access
Data type Blocked data
PDO mapping No
Access Read (output data) + Write (input data)
Value IODATA
See the FieldBus I/O Data chapter later in this document for a description of
the formats of the output and input page formats. Note that it is necessary to
select the required input data format by writing at least the first two bytes of
the output data. The response is formulated at the time the output data is
written to this data dictionary item, and may be retrieved at any subsequent
time, provided that there is no intervening asymmetric upload/download
access.
Note that the metric/imperial selection is made via the first word of the data
content of the output data.
If it is required to set line speed using the output data, then the output data
must be 6-bytes in length. The UltraScan will limit processing of line speed
received via the output data to once per second (this has no effect on the
formulation of the response input data).
Profibus Interface
The Profibus interface allows a customer to integrate the UltraScan DSP
gauge into the control loop via the industry standard Profibus protocol.
This section is written with the assumption that the reader is knowledgeable
about the Profibus communication protocol and terms associated with this.
For more information about Profibus in general, please contact Profibus
International or Siemens Profibus Information Center.
Product Support
The UltraScan DSP supports Profibus DP using auto-baud rate detection up to
12 Mbps.
An appropriate GSD file containing all of the relevant configuration and
parameterization selection information is located in Appendix C of this
document.
The UltraScan DSP supports set slave address telegrams as documented in
the Profibus DP specification.
Profibus I/O Data

See the FieldBus I/O Data chapter later in this document for a description of
the formats of the output and input page formats.
Profibus PKW Header

The PKW header is used to communicate with the UltraScan DSP internal
database. The PKW request/response bytes appear in the Profibus I/O Data
before the UltraScan DSP I/O Data Format bytes. The meaning of the PKW
header bytes is the same for requests (from the master) and responses (from
the gauge).
The PKW header is used to get or set gauge settings, calibration information,
trigger waveform capture, etc.
The PKW header is exactly 8 bytes, and appears before the I/O data. The
PKW header format is the same for the output data (requests from the master)
and input data (responses from the gauge). All values are in little-endian
format.
Bit: 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Word 0: Response Code (should be 0 in requests) T U Command Code
Word 1: Command Qualifier
Word 2:
Command/Response Data
Word 3:
T: Toggle Bit
U: Units (0 =metric, 1=imperial)
The UltraScan DSP gauge processes the output data PWK request header
under the following circumstances:
1) The command code is different from the last command code processed
2) The units bit is different from the last units bit processed
3) The command qualifier is different from the last command qualifier
processed
4) The command code represents a read long or read float request.
This allows the master to continuously read a single database item
without needing to issue an intervening request.
A Profibus master should always keep the response code bits clear in the
input data PKW request header.
The UltraScan DSP gauge makes no direct use of the toggle bit, other than
to reflect the state of the toggle bit in the output data request PKW header
within the input data response PKW header. This is done whether or not the
UltraScan DSP gauge processed the command.
The units bit should be clear (0) for metric requests, and set (1) for imperial
requests. The state of the units bit within the PKW header affects only the
information exchanged through the PKW header; it has no effect on the
contents of the I/O data area, the units of which are controlled independently
through the I/O data header.
The command code is used to request a particular PKW service. The
available PKW command codes are detailed later in this document.
The command code qualifier is used to carry additional information relating to
the command. This includes enumeration indices, database item identifiers,
string segments, etc.
The command data is used by the master to send long, float or string
information. The gauge uses the command data to provide enumeration, limit,
value, and string data as appropriate according to the command code.
Detection of Matching PKW Response
After a master has initiated a PKW command by setting the PKW request
header appropriately, it must wait for a matching response from the UltraScan
DSP gauge.
A matching response is detected by comparing the command code, units, and
command qualifier within the PKW response header to those issued in the
PKW request header. Since the toggle bit is always reflected by the gauge, it
is also possible to include the toggle bit in the comparison.
The gauge will always respond with matching units, command code, and
command qualifier, even if the request is not valid.
The response code should be checked before any use is made of the
response data. A non-zero response code indicates that the request failed.
Currently, the gauge responds with a success response code and data of all
zeroes for unrecognized command codes.
Response Code Description
0 Success The command has been successfully processed.
1 Error The command referenced an unknown item
2 Error The command referenced an item of the incorrect type
Error A request to save a string cannot be performed because

3
no string data has previously been provided
Error A request could not be processed because there were

insufficient resources within the gauge (queues full, etc). The
command may succeed if retried but the master will need to
4
issue an intervening idle command. Otherwise, the gauge will
not act upon the unchanged command code and command
qualifier.
PKW Idle Command (Command Code 0)
The gauge responds with all zeroes in the response data and a success
response code. It is recommended that the idle command be issued before
starting Profibus communication, and during operation if no database items
need to be read or written.
PKW Enumeration Command (Command Code 1)
This command allows the UltraScan DSP database to be enumerated. A

single database item can be enumerated with each command/response
exchange; this makes it quite slow to enumerate the entire database. There is
no requirement to enumerate the database. Appendix I Database Layout of
this document provides details of database item identifiers, types, and access
permissions, and it is possible to use this published information directly with
the other database services. The enumeration service allows generic test
programs to be written that have no prior knowledge of the UltraScan DSP
database.
The Profibus master provides an incrementing enumeration index within the
command qualifier field. Usually this would begin with an enumeration index
of 0, and increment after each successful enumeration exchange.
Enumeration is complete when the response code is set to unknown item.
For a successful enumeration, the gauge sets the PKW response data as
follows:
Bit: 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Word 2: Database Item Identifier
Word 3: Database Item Access Flags Database Item Type

Database Item Identifier: identifier to be used with other database services
Database Item Type: 0=long, 1=float, 2=string, 255=unknown
Database Item Access Flags: 0x01=non volatile, 0x02=read-only,
0x04=constant (not changed by gauge)
PKW Get Min Value (Command Code 2)
This command allows determination of the minimum valid value for a database
long or float. This is not meaningful for a string database type. There is no
requirement for the use of this command. Appendix I Database Layout
provides details of database item ranges and other information. This
command allows generic test programs to be written that have no prior
The Profibus master must have explicit knowledge of the database item for
which minimum value information is being solicited, and deal with the
response data appropriately according to type.
The Profibus master specifies the database item identifier within the command
qualifier.
The gauge sets the PKW response data as follows:
Bit: 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Word 2:
Min Value for Database Item
Word 3:
For a long database item, this is a 32-bit signed integer. For a float database
item this is a 32-bit IEEE floating point value. For a string database item, this
is a 32-bit signed integer, and will always return 0.
PKW Get Max Value (Command Code 3)
This command allows determination of the maximum valid value for a

database long or float, and the maximum length for a string type. There is no
requirement for the use of this command. Appendix I Database Layout
provides details of database item ranges and other information. This
command allows generic test programs to be written that have no prior
The Profibus master must have explicit knowledge of the database item for
which maximum value information is being solicited, and deal with the
response data appropriately according to type.
qualifier.
The gauge sets the PKW response data as follows:
Bit: 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Word 2:
Max Value for Database Item
Word 3:
For a long database item, this is a 32-bit signed integer. For a float database
item this is a 32-bit IEEE floating point value. For a string database item, this
is a 32-bit signed integer, and will return the maximum length of the string.
PKW Read Long (Command Code 4)
This command allows an integer database item to be read.

qualifier. If the referenced database item is not an integer, then the response
code will be set to wrong type.
The gauge will ignore the contents of the PKW Request Data. The PKW
Response Data will contain the signed 32-bit value read from the database.
PKW Write Long (Command Code 5)
This command allows an integer database item to be written.

qualifier. If the referenced database item is not an integer, then the response
The contents of the PKW Request Data are treated as a signed 32-bit number
to be written in to the database, and the PKW Response Data will be all
zeroes.
PKW Read Float (Command Code 6)
This command allows a floating-point database item to be read.

qualifier. If the referenced database item is not floating point, then the
response code will be set to wrong type.
The gauge will ignore the contents of the PKW Request Data. The PKW
Response Data will contain the 32-bit floating-point value read from the
database.
PKW Write Float (Command Code 7)
This command allows a floating-point database item to be written.

qualifier. If the referenced database item is not floating point, then the
response code will be set to wrong type.
The contents of the PKW Request Data are treated as a 32-bit floating-point
number to be written in to the database, and the PKW Response Data will be
all zeroes.
PKW Load String (Command Code 8)
Since only four data bytes are available for communicating information within
the PKW header, it is necessary to load a string into a temporary buffer from
where it can be read four bytes at a time. The PKW Load String command
performs this function.
qualifier. If the referenced database item is not a string, then the response
The gauge sets the PKW response data to the length of the string. This length
indicates the number of non-null characters within the string. The Profibus
master can use this length to determine how many Read String Segment
requests must be issued, or to pre-allocate a buffer for receiving string data,
etc. It is also possible to detect the end of string when reading the string
segments, so the string length within the response data may be ignored if its
use is not required.
PKW Read String Segment (Command Code 9)
This command allows a Profibus master to read segments of a string that has
previously been loaded into a temporary buffer using the Load String
command. The string can be read 4 bytes at a time.
The Profibus master specifies a string segment number in the command
qualifier field. The string segment number starts at 0, then works up
incrementally 1, 2, 3, etc. It is not necessary to read the segments in any
particular order, although if the size of the string supplied in response to the
Load String command has not been retained then it is recommended that
segments be read in ascending order so that the operation can be terminated
when the null-terminator is detected.
The gauge always responds with 4 bytes in ascending order within the PKW
Response Data area. For a string segment number N, the returned characters
are from a starting index position N*4 within the temporary string buffer.
Attempts to read beyond the end of the temporary string buffer will return all
zero data.
The gauge always provides at least one null terminator byte after the string
data (assuming the master reads sufficient string segments). If the temporary
buffer has previously been used to load other strings, then non-null data may
follow the first null terminator byte. The Profibus master should detect and use
the first zero byte as a null terminator.
PKW Write String Segment (Command Code 10)
Since only four data bytes are available for communicating information within
the PKW header, it is necessary to build a string within a temporary buffer
from where it can be written into the database. The PKW Write String
Segment command performs this function.
The Profibus master specifies a string segment number in the command
qualifier field. The string segment number starts at 0, then works up
incrementally 1, 2, 3, etc. For a string segment N, the gauge then copies the
four supplied string bytes (possibly containing a null terminator) from the PKW
Request Header into the temporary buffer at index position N*4. It then adds a
null terminator to the temporary buffer at index position (N+1)*4. This
defensive technique means that the temporary buffer is always null
terminated, regardless of the order in which data is received from the master.
It is therefore not necessary for the master to supply a null terminator if the
string length is an exact multiple of four bytes. However, the technique
requires string segments to be written in ascending numerical order.
If the previous PKW command was not to write a string segment, then the
gauge inserts a null terminator at the start of the temporary buffer. Therefore,
all Write String Segment commands and the following Save String command
must be sent contiguously.
If the specified string segment N is valid, then the gauge reflects the supplied
PKW request header string data within the PKW Response Data. If the
specified string segment N is not valid, then the gauge sets all PKW Response
Data bytes to all zeroes.
PKW Save String (Command Code 11)
A string previously loaded into the temporary string buffer using the Write
String Segment command is written to the UltraScan DSP database using the
Save String command.
qualifier. If the referenced database item is not a string, then the response
The immediately preceding command must have been a Write String
Segment, otherwise a No String response code is generated. This is a
defensive mechanism to help prevent accidentally writing zero length or invalid
strings into the database.
The gauge sets the PKW Response Data to all zeroes.
FieldBus I/O Data

The UltraScan I/O data is based on a principal of formatted blocked output
request data and formatted blocked input response data. The output data
contains a metric/imperial selection flag, and a data format request, and
optionally a linespeed value. The input response contains a header record
that is common to all page formats, followed by the format specific data.
Profibus
For Profibus the IO data area is prefixed by a group of bytes to form a sub-
channel over which data requests and commands can be communicated. This
group of bytes is referred to as the PKW header, and is documented in a
separate section (see Profibus PKW Header).
The Profibus DP output data is 14 bytes in total, and is conceptually split into
two functions:
8 bytes: PKW Request header
6 bytes: Output I/O format data (common with other FieldBus interface
protocols)
The Profibus DP input data is 112 bytes in total, and is also conceptually split
into two functions:
8 bytes: PKW Response header
104 bytes: Input I/O format data (common with other FieldBus interface
protocols)
For Profibus, it is only practical to obtain the majority of measurements and

derived values through the data format part of the IO data. The PKW header is
primarily intended for setting values, issuing commands, and obtaining ad-hoc
data prior to a line start.
DeviceNet
For DeviceNet the software designer can use a variety of methods and
combinations for gathering readings, status, and derived data:
All necessary readings, status, and derived data obtained using the explicit
message connection to read directly from the database.
Readings obtained using an IO connection, status and derived data obtained

directly from the database using the explicit message connection.
Readings and derived data obtained using an IO connection, status obtained

using the explicit message connection.
All readings, status, and derived data obtained using an IO connection. Explicit
message connection used to read/write any information not included in the IO
message formats.
On very busy networks the software designer may need to consider the
relative priorities of explicit message fragments compared to IO fragments (IO
data always has a higher transmission priority on any DeviceNet network).
CANopen
For CANopen all gauge functionality is accessible through the SDO
connection. The pre-defined IODATA formats are available through SDO
connections, as is the ability to read or write large lists of database items using
the efficient segmented upload/download protocols.
It is also possible to use PDO mappings to obtain/set time critical readings in a
protocol efficient manner. The flexibility of CANopen PDO mapping, together
with large number of Tx PDOs available on the UltraScan, make it possible to
extract exactly the data required for a particular installation without the
overhead or complexity of using the IODATA formats over the SDO
connection.
Definitions of Bit-Fields and Structures Used for Data

Formats
In the following definitions, layer numbers are zero based (i.e., layer 1 is
represented by 0, etc). The symbol (*) indicates that although the number of
values is fixed, the actual number of values that are valid depends on the
number of operational transducers.
Request / response data format (all input and output data formats)
The following 16-bit little-endian word appears in the first two bytes of all
output and input data formats. It is written by the master within the output data
to select the required format of the input IO data.
Bit: 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0=Metric
Function: 0 0 Data format Data format specific information
1=Imperial
The gauge reflects this field exactly as written by the master, except that the
High Speed Tolerance bit is merged in. For invalid data format requests the
data format specific part of the returned input data will be all zero.
Bit: 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0=Metric
Function: 0 HST Data format Data format specific information
1=Imperial
HST: High Speed Tolerance status bit (0 = no HST errors detected, 1 = HST
error detected).
Transducer status (all input data formats)

The following 16-bit little-endian word appears in the first two bytes of all input
data formats. Its contents are the same as database identifier 309.
Bit: 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Transducer: 8 7 6 5 4 3 2 1
Function: % snr % snr % snr % snr % snr % snr % snr % snr

snr = Signal to noise ratio tolerance exceeded
% = Percentage good scans tolerance exceeded
Output Data Format

The following structure describes the output data format expected by the
gauge.
Request data format Bit field 2 bytes
Line Speed Float 4 bytes
6 bytes
The metric/imperial units selection for the line speed is determined by the
metric/imperial selection bit in the request data format bit field.
For DeviceNet and Profibus, it is possible to suppress the line speed by setting
all bits of the linespeed. In C this can be accomplished using a statement
similar to the following:
*(unsigned long *)&outdata.linespeed = 0xffffffff;
This will be necessary if it is desired to supply the line speed through a

different physical interface, through DeviceNet explicit messaging, or through
the Profibus PKW header.
For DeviceNet, the line speed is optional, and may be omitted if the DeviceNet
master is capable of sending variable length IO data.
Input Data Formats
Data format 0 : miscellaneous

This data format is used to select miscellaneous pages of information. The
data format specific information is used to determine a sub-format number
between 0 and 1023.
Data format 0 : miscellaneous, sub-format 0 - reserved

This data format returns all-zero data (except for transducer status bits).
Data format 1 : measurement data

The data format specific information is used as follows:
Bit: 9 8 7 6 5 4 3 2 1 0
Derived layer index Primary layer index

(sub-format 3 only)
0 = layer 1 0 = layer 1
Sub-format 1 = layer 2 1 = layer 2
0 = status 3 = layer 4 3 = layer 4
Function: 1 = gap to product outer
2 = derived product data 4 = layer 5 4 = layer 5
3 = derived layer data 5 = layer 6 5 = layer 6
The primary-layer specific information within sub-formats 0 through 3 is as

follows:
Primary layer specific measurement data (sub-formats 0 through 3)
Layer thickness(per transducer) 8 Floats (*) 32 bytes
Product OD (per transducer pair) 4 Floats (*) 16 bytes
Product ID (per transducer pair) 4 Floats (*) 16 bytes
64 bytes
The derived layer specific information within sub-format 3 is as follows:

Derived layer specific measurement data
Layer min wall thickness Float 4 bytes
Layer max wall thickness Float 4 bytes
Layer avg wall thickness Float 4 bytes
Layer min wall angle Float 4 bytes
Layer max wall angle Float 4 bytes
Layer X-Sect area Float 4 bytes
Layer X position Float 4 bytes
Layer Y position Float 4 bytes
Layer concentricity Float 4 bytes
36 bytes
Data format 1 : measurement data, sub-format 0 status

Response data format Bit field 2 bytes
Transducer status Bit field 2 bytes
Primary layer specific information Misc format 64 bytes
Gauge status S-Int 2 bytes
Water temperature Float 4 bytes
% Good (per transducer) 8 UChars (*) 8 bytes
% SNR (per transducer) 8 UChars (*) 8 bytes
% Gain (per transducer) 8 UChars (*) 8 bytes
Reserved 6 bytes
104 bytes
Data format 1 : measurement data, sub-format 1 gap to product outer

Gap to product outer (per transducer) 8 Floats (*) 32 bytes
Reserved 4 bytes
104 bytes
Data format 1 : measurement data, sub-format 2 derived product data

Product avg OD Float 4 bytes
Product avg ID Float 4 bytes
Product ovality Float 4 bytes
Product X position Float 4 bytes
Product Y position Float 4 bytes
Reserved 16 bytes
104 bytes
Data format 1 : measurement data, sub-format 3 derived layer data

Derived layer specific information Misc format 36 bytes
104 bytes
This data format is based on the concept of a primary layer and a derived
layer. The primary layer is used to request or indicate the layer to which the
wall thickness measurements relate. The derived layer is used to request or
indicate the layer to which the derived data relates. This allows wall thickness
measurements for one layer to be obtained at the same time as derived data
for another layer. This simplifies the writing of data gathering software that
collects primary wall thickness readings at a different rate to status, gap, per-
layer derived, and product derived information.
The following tables show examples of how a software system might solicit
data for a 3 layer product:
Derived Primary
Data Format Layer Layer
Index Index
1.1: Status - 0
1.2: Gap to product outer - 1
1.3: Derived product data - 2
1.4: Per layer derived data 0 0
etc etc etc

OR
Derived Primary
Data Format Layer Layer
Index Index
1.1: Status - 0
1.2: Gap to product outer - 1
1.1: Status - 2
1.3: Derived product data - 0
1.1: Status - 1
1.1: Status - 0
1.1: Status - 2
etc etc etc

ETC
In these schemes the product OD and ID are returned in every exchange,
whereas the thickness information for any particular layer are returned every
Nth exchange where N is the number of layers.
Note that the above schemes are easily modified to accommodate 1, 2, 3 and
4 layer products. Other schemes could be designed that collect the gap and
per-layer derived data at a much lower frequency than the gauge status and
derived product data. The actual data collection scheme employed must be
determined by the application designer based on the nature of the product
being measured and the desired data throughput rates.
Data format 2 : waveform data

The data format specific information is used as follows:
Bit: 9 8 7 6 5 4 3 2 1 0
Function: Waveform data packet number

The waveform data packet number is 512 to collect waveform header A, 513
to collect waveform header B, and between 0 and 511 to collect waveform
data. All waveform data packets have a common header. This common
header allows the waveform collection process to confirm that all waveform
data packets are related to the same waveform. Please see related Beta
LaserMike documentation for a more detailed description of waveform data.
Common waveform data format header:

Ping count ULong 4 bytes
Transducer index (0 based) Char 1 byte
Waveform type Char 1 byte
10 bytes
How to collect a consistent waveform:

1) Get waveform header A, and store the ping count, transducer index,
and waveform type.
2) Trigger a new waveform collection by writing to database item 984
(documented elsewhere).
3) Get waveform header A until the ping count, transducer index, or
waveform type differs from the last stored values (they will always be
different if we returned to this step after a waveform mis-match).
4) Store the new ping count, transducer index, waveform type, and the
contents of waveform header A.
5) Get waveform header B.
6) If the ping count, transducer index, or waveform type in header B are
different to those last stored, then go back to step 3 to begin collection
of the new waveform.
7) Store the contents of waveform header B.
8) Get waveform data packets starting from packet 0 (using the sub-
format for the packet number).
9) If the ping count, transducer index, or waveform type in any of the
waveform data packets are different to those last stored, then go back
to step 3 to begin collection of the new waveform.
10) If the number of data bytes within the waveform data packet is 0xFFFF
then this indicates that data collection within the gauge is still in
progress go back to step 8 to get the same packet again.
11) Store the waveform data from the data packet.
12) If the number of data bytes within the waveform data packet is 92, then
go back to step 8 to get the next data packet.
13) If the number of data bytes within the waveform data packet is less
than 92, then waveform data collection is complete. Return to step 2 to
trigger and collect the next waveform.
Data format 2 : waveform data, sub-format 512 waveform header A

Waveform data packet number 512 is used for waveform header A
Common waveform header Misc 10 bytes
Number of available waveforms UShort 2 bytes
Time stamp ULong 4 bytes
Window start delay ULong 4 bytes
Window samples ULong 4 bytes
Distance between samples ULong 4 bytes
Number of echoes Char 1 byte
Number of echo candidates Char 1 byte
Echo positions Ulong * 8 (*) 32 bytes
Echo candidate positions Ulong * 8 (*) 32 bytes
Signal to Noise Ratio Float 4 bytes
Gap Float 4 bytes
Reserved 2 bytes
104 bytes
Data format 2 : waveform data, sub-format 513 waveform header B

Waveform data packet number 513 is used for waveform header B sub-format
Initial gain Long 4 bytes
Time varying gain info (ULong+Long)*3 24 bytes
Ignore regions (ULong+Ulong)*4 32 bytes
Wall Float * 7 (*) 28 bytes
Reserved 6 bytes
104 bytes
Data format 2 : waveform data, sub-formats 0 through 511 waveform data

The waveform data is encoded using a simple run-length compression
technique. The data bytes may be signed or unsigned depending on the
waveform type. Please see relevant Beta LaserMike documentation for further
details.
Waveform data packet numbers 0 through 511 are used for waveform data:
Waveform data bytes in this packet UShort 2 bytes
Waveform data Char / UChar 92 bytes
104 bytes
Appendix A: Waveform Information

UltraScan DSP provides the capability to output the ultrasonic waveform data
captured and processed for the purposes of troubleshooting the UltraScan
DSP hardware, troubleshooting the ultrasonic gauge head connected to the
UltraScan DSP, troubleshooting the application, and/or manually overriding
the automatic setups of the UltraScan DSP. Interpretation of the waveforms
provided by the UltraScan DSP for the purposes described above, should be
reserved for personnel with the proper experience and/or training.
Uncompressed Waveform Data

The waveforms provided by the UltraScan DSP include raw, filtered, and
processed waveforms. Each byte of data represents the amplitude of a
single point of the entire waveform. The uncompressed waveform data can be
accessed via the RS232 serial interfaces using packet 29.
Raw Waveform Data

Each byte of raw waveform data is a signed value from 127 to 128. The raw
waveform data represents the data provided directly from the analog input and
A/D conversion hardware. If necessary, the data internal to the UltraScan
DSP will be scaled to represent an 8-bit signed value.
Filtered Waveform Data

Each byte of the filtered waveform data is a signed value from 127 to 128.
The filtered waveform data represents the raw data after it has been digitally
filtered based on the corresponding transducer type employed. If necessary,
the data internal to the UltraScan DSP will be scaled to represent an 8-bit
signed value.
Processed Waveform Data

Each byte of the processed waveform data is an unsigned value from 0 to 255.
The processed waveform data represents the final waveform state and is the
waveform from which any measurements are taken. If necessary, the data
internal to the UltraScan DSP will be scaled to represent an 8-bit unsigned
value.
Compressed Waveform Data

The UltraScan DSP can provide any of the above described uncompressed
waveform data in a compressed format. An increased throughput of data can
be achieved when transferring compressed waveform data over the I/O
interfaces of UltraScan DSP. The DeviceNet and ProfiBus interfaces currently
support only the Run-Length Encoded waveform data format. The

compressed waveform data can also be accessed via the RS232 serial
interfaces using packet {P28}.
Run-Length Encoding (RLE) Compression

The RLE compression implemented within UltraScan DSP is a byte wise run-
length encoding consisting of an 8-bit flag, an 8-bit run length, and an optional
8-bit data value. The compressed waveform data can be a mixture of
uncompressed data and data formatted according to the RLE scheme. The
flag value signifying the start of a run-length encoding is 0x80. All other data
shall be interpreted as uncompressed data. Following the flag will be the run-
length (N). If the run-length is less than 3, it represents the number of bytes of
the value 0x80 in the uncompressed data. If the run-length is greater than 2,
the byte following the run-length byte will represent the value repeated (N)
times in the uncompressed data.
Example compressed data (values in hex): 00010180100040800200

Equivalent uncompressed data (values in hex):
0001010000000000000000000000000000000040808000
Future Compression Formats

In the future, additional compression techniques may be employed to further
increase the throughput capabilities of the UltraScan DSP. All previously
defined compression techniques will be supported.
Waveform Collection Modes
Normal Mode
This is the default and normal mode of collection for the UltraScan DSP.
Waveforms are collected as requested by selecting the next waveform {984}.
Continuous/Stop Modes
In the continuous collection mode, the UltraScan DSP is continually capturing
and storing internally, waveforms for every ping initiated. The total number of
waveforms maintained within the UltraScan DSP is determined by the target
number of waveform sets configured {980} or the available RAM for storing
waveforms. The oldest waveforms are removed as new waveforms are
captured. The stop capture mode should be set before attempting to read the
waveform information and data from the UltraScan DSP to be certain the
waveform(s) being read are consistent.
Trigger-on-Error Mode
In the trigger-on-error mode, the UltraScan DSP is continually capturing ans
storing internally, waveforms for every ping initiated. The total number of
waveforms maintained within the UltraScan DSP is determined by the target
number of waveform sets configured {980} or the available RAM for storing
waveforms. The oldest waveforms are removed as new waveforms are
captured. The stop capture mode is automatically asserted by the UltraScan
DSP when the first waveform with a SNR confidence level ({290} through
{297}) is below the set threshold {298} or not enough echos are detected in the
waveform.
Waveform Collection Sequence

The following steps provide a guideline for the sequences of setup, monitoring,
accumulation, and output of waveform data within the UltraScan DSP.
Restrictions within the computing system collecting waveforms from the
UltraScan DSP may require that a more complex sequence of commands be
issued to facilitate the waveform information and data collection. In some
cases, a simplified sequence of commands can be issued depending on the
requirements of the collecting system.
1) Set {980} to specify the number of consecutive transducer pings to

capture waveform data for. By default or if {980} is not set, waveforms
for a single ping will be captured.
2) Set {981} to specify what waveform types (raw, filtered or processed)
are to be captured on each ping. By default or if {981} is not set, all
waveform types will be captured.
3) Set {982} to specify the target number of data points to be returned for
each waveform requested. The actual number of data points returned
may be less than the value requested and not be more than number
requested x 2 1. This setting can be used to improve the waveform
throughput rate of very long waveforms by setting the target number of
data points to an amount that can be practically displayed on a
computer screen. Long waveforms are decimated if their length is
greater than the target length set x 2. Setting the value to 0 specifies to
the UltraScan DSP that all data points of the waveform should be
returned. By default or if {982} is not set, the target number of data
points is set to 400.
4) Set {983} to clear any old waveforms from the internal capture buffer of
the UltraScan DSP.
5) Set {987} to specify the collection mode. See Waveform Collection
Modes above.
If the continuous collection mode is selected, the stop collection mode

must first be selected before proceeding. By default or if {987} is not
set, the normal collection mode is selected.
If the trigger on bad ping collection mode is selected, monitor {986} for
a non-zero value to know when a bad ping has been detected and
the corresponding waveform set has been captured.
6) Set {984} to select the next available captured waveform.
If the normal collection mode is selected, monitor {986} for a non-zero
value to know when a waveform is available before proceeding.
7) Read waveform information packets, as specified in the appropriate
protocol, to gather any required waveform-specific information.
8) Read waveform data packets to accumulate the compressed or
uncompressed waveform data for the captured ping. Repeat this step
until the all the data packets have been returned for the current
waveform selected.
9) Repeat from step 6.
Appendix B: DeviceNet EDS File

$ EDS File for the UltraScan DSP Gauge device
[File]
DescText = "EDS file for UltraScan DSP Ultrasonic ID/OD/Wall

Gauge.";
CreateDate = 10-11-2002;
CreateTime = 11:05:00;
ModDate = 10-11-2002;
ModTime = 11:05:00;
Revision = 1.0;
[Device]
VendCode = 0x2dc; $ Vendor Code
VendName = "Beta LaserMike Ltd";
ProdType = 0x0; $ Product Type
ProdTypeStr = "Generic Device";
ProdCode = 0xFA0; $ Product Code
MajRev = 0x1; $ Major Rev
MinRev = 0x1; $ Minor Rev
ProdName = "Beta LaserMike UltraScan DSP Gauge";
Catalog = "";
[IO_Info]
Default = 0x0001;
PollInfo = 0x000f, 1, 1;
StrobeInfo = 0x000f, 2, 0;
COSInfo = 0x000f, 1, 1;
CyclicInfo = 0x000f, 1, 1;
Input1 = 104,0,0x0D,"Input1", 6,"20 04 24 01 30 03","No Help";

Input2 = 8, 0,0x02,"Input2", 6,"20 04 24 02 30 03","No Help";
Output1 = 6, 0,0x0D,"Output1",6,"20 04 24 01 30 03","No Help";
[ParamClass]
MaxInst=0;
Descriptor=0x0;
CfgAssembly=0;
Appendix C: PROFIBUS GSD File
#Profibus_DP
Vendor_Name = "Beta LaserMike"
Model_Name = "UltraScan DSP"
OrderNumber = "USDSP"
Revision = "V1.1"
Ident_Number = 0xeeef
Protocol_Ident = 0
Station_Type = 0
Hardware_Release = "UltraScan DSP"
Software_Release = "Rev. D"
;
9.6_supp = 1
19.2_supp = 1
93.75_supp = 1
187.5_supp = 1
500_supp = 1
1.5M_supp = 1
3M_supp = 1
6M_supp = 1
12M_supp = 1
;
MaxTsdr_9.6 = 60
MaxTsdr_19.2 = 60
MaxTsdr_93.75 = 60
MaxTsdr_187.5 = 60
MaxTsdr_500 = 100
MaxTsdr_1.5M = 150
MaxTsdr_3M = 250
MaxTsdr_6M = 450
MaxTsdr_12M = 800
;
Min_Slave_Intervall = 1
;
Auto_Baud_supp = 1
Set_Slave_Add_supp = 1
Freeze_Mode_supp = 1
Sync_Mode_supp = 1
FMS_supp = 0
Fail_Safe = 0
;
Implementation_Type = "SPC3"
Slave_Family = 9
Periphery = "DPS"
;******* User-Parameter-Definition **********
; UserPrmData: Length and Preset:

User_Prm_Data_Len=4
User_Prm_Data=0x00,0x00,0x00,0x00
Max_User_Prm_Data_Len=4
Ext_User_Prm_Data_Const(0)=0x00,0x00,0x00,0x00
Max_Module = 1
Max_Input_Len = 112
Max_Output_Len = 14
Max_Diag_Data_Len = 11
;
Modular_Station = 0
;
Module = "UltraScan DSP Gauge" 0xC1,0xC6,0xF7,0x80
EndModule
Appendix D: Gauge Calibration

The process of calibrating the wall measurement and outer diameter (OD)
measurement is the same, regardless of which interface is used. The only
difference is that when using the serial interface, the gauge will respond with
information that needs to be polled for when using the DeviceNet or Profibus
interfaces.
When calibrating the UltraScan DSP, several values need to be written to and
read from the UltraScan DSP database. For the serial interface, this is
accomplished by using the Set Value command, referencing the appropriate
cell number. When using the DeviceNet interface, this is accomplished by
using the Set Integer/Float, Get Integer/Float, Set String and Get String
services on the appropriate instance of the Database Object. For Profibus,
database read and write operations are performed using the PKW header as
described in the Profibus section of this manual.
Any references to database cells in this appendix will be indicated like this:
{database ID}.
Average Wall Calibration

1) If using the DeviceNet or Profibus interface, set {329} to zero. This
allows the polling of this cell to detect a change. This is not necessary
when using the serial port interface.
2) Save the average wall. Do this by writing a random number to {322}.
This should be a different value than is currently in that database cell.
If using the serial interface, the UltraScan DSP will send the standard
reply.
3) The UltraScan DSP will update {329} to indicate the current state of
saving the average wall. If using the serial interface, the UltraScan
DSP will send a message indicating the change. If using DeviceNet or
Profibus, the user must poll this cell. This cell will indicate a value of
127 if it is in the process of saving the average wall, 130 if the
average wall is successfully saved, and 132 if the average wall is not
saved. The average wall save will fail if the transducer status {309} is
not zero. Correct the problem and restart the calibration.
4) If the product cooling rate compensation is to be employed, set the
material type for each layer {546, 646, 746, 846} as appropriate and
verify that it was set correctly.
material quench point temperature {111} and verify that it was set
correctly.

calibration line speed in {327}. If product cooling rate compensation is
undesirable or line speed is unavailable, set a line speed of 0. Verify
that this is set correctly.
8) Set the actual average wall for layer 1 that was measured offline {323}.
9) If using the serial interface, the UltraScan DSP will send a message
indicating a change to {329}. If using DeviceNet or Profibus, the user
should poll this cell. The cell will indicate a value of 133 if the wall
calibration for layer 1 was completed successfully, and a value of 135
if the wall calibration failed. A failure will occur if the average wall was
not saved. Restart the calibration sequence.
10) Repeat steps 7 through 10 for each layer as appropriate. For layers 2,
3, and 4, use cells {324}, {325}, and {326}, respectively.
Fixed Sector-Based Wall Calibration

Fixed sector-based wall thickness calibration is an available feature used to
compensate for an uneven circumferential product temperature or to
compensate for circumferential wall thickness changes that occur after
passing through the ultrasonic gauge head (perhaps introduced by product
wall sag).
Once the fixed sector-based wall thickness calibration compensation factors
have been calculated, subsequent average wall calibrations can be performed
without affecting the fixed sector-based wall thickness calibration
compensation factors employed (assuming changing product conditions do not
dictate that a new fixed sector-based wall calibration must be performed).
If the fixed sector-based wall calibration compensation factors need to be
removed, this can be accomplished by setting the sector calibration mode
{350} to Disabled. Using this method, the old compensation factors will be
maintained within the UltraScan DSP and can be made active again simply by
re-enabling the Fixed sector calibration mode. An alternative method can be
performed by directly setting each compensation factor cell to a value of 1.0
(cells {560} through {567} for layer 1, cells {660} through {667} for layer 2, cells
{760} through {767} for layer 3, cells {860} through {867} for layer 4).
1) Make sure the sector calibration mode {350} is set to Fixed.

3) Save the wall measurements. Do this by writing a random number to

{322}. This should be a different value than is currently in that
database cell. If using the serial interface, the UltraScan DSP will send
the standard reply.
saving the wall measurements. If using the serial interface, the
UltraScan DSP will send a message indicating the change. If using
DeviceNet or Profibus, the user must poll this cell. This cell will
indicate a value of 127 if it is in the process of saving the wall
measurements, 130 if the wall measurements were successfully
saved, and 132 if the wall measurements were not saved. The wall
save will fail if the transducer status {309} is not zero. Correct the
problem and restart the calibration.
5) The UltraScan DSP will also update cells {310},{311}, and {312} to
indicate the current system operating mode (static or reversing), the
current transducer angle (relevant only if operating in static mode), and
the number of relevant compensation factors to be calculated (will be
equal to 8 if operating in reversing mode or equal to the number of
tranducers if in static mode). These values can be used to setup a
HMI for entering the sector-based calibration values.
correctly.
9) As each of the offline measured setor wall thickness values are set in
the UltraScan DSP, the average layer speed of sound and sector-
based wall thickness compensation factors are updated. If necessary
for the HMI, setup hotlinks to receive updates as the values are
entered
10) Enter the number of offline measured sector wall thickness values
specified by database cell {312}. For a system operating in reversing
mode, cells {570}, {571}, {572}, {573}, {574}, {575}, {576}, and {577}
would be set for layer 1. For a system operating in static mode, cells
{570}, {571}, {572}, and {573} would be set for a 4 transducer system.
11) Poll or hotlink the number of wall thickness calibration compensation
factors specified by database cell {312}. For a system operating in
reversing mode, cells {560}, {561}, {562}, {563}, {564}, {565}, {566},
and {567} need to be read from the UltraScan DSP if they are to be
stored in a library file.
12) Repeat step 9 through 11 for each layer as appropriate. For layer 2,
use cells {670} through {676} to enter the measured wall thickness
values and cells {660} through {667} to read back the wall thickness
calibration compensation factors. For layer 3, use cells {770} through
{776} to enter the measured wall thickness values and cells {760}
through {767} to read back the wall thickness calibration compensation
factors. For layer 4, use cells {870} through {876} to enter the
measured wall thickness values and cells {860} through {867} to read
back the wall thickness calibration compensation factors.
Adaptive Sector-Based Wall Calibration

Adaptive Sector-based wall thickness calibration is an available feature used
to compensate for an uneven circumferential product temperature. The
uneven product temperature compensated for is due to an uneven product
wall thickness. Thicker walls will hold more potential energy in the form of
heat and will take more time to cool to the ambient water temperature than a
thinner wall. The uneven temperature can change the speed of sound at each
measurement point around the circumference of the product. Unlike the fixed
sector-based wall calibration described above the adaptive compensation will
provide more accurate measurements even if the product eccentricity changes
its directional orientation during production and from subsequent extrusion line
startups.
The adaptive sector-based wall calibration provides the most accuracy when
the wall concentricity is relatively low. Ideally, the concentricity of the product
should be such that the minimum wall and maximum wall product tolerances
are closely represented during the time of calibration. The adaptive sector-
based wall calibration compensation is not useful and is not necessary when
the product being measured has completely cooled to the ambient water
temperature. Under these conditions, the temperature profile around the
circumference of the pipe should be equal.
Once the adaptive sector-based wall thickness calibration compensation
factors have been calculated, subsequent average wall calibrations can be
performed to adjust the adaptive sector-based wall thickness calibration
compensation factors employed (assuming changing product conditions do not
dictate that a new adaptive sector-based wall calibration must be performed).
If the adaptive sector-based wall calibration compensation factors need to be
removed, this can be accomplished by setting the sector calibration mode
{350} to Disabled. Using this method, the old compensation factors will be
maintained within the UltraScan DSP and can be made active again simply by
re-enabling the Adaptive sector calibration mode. An alternative method can

be performed by directly setting the wall speed of sound slope {580, 680, 780,
and/or 880} to zero and by setting the wall speed of sound intercept {580, 680,
780, and/or 880} to the average speed of sound {500, 600, 700, and/or 800}.
1) Make sure the sector calibration mode {350} is set to Adaptive.
3) Save the individual wall measurements. Do this by writing a random
number to {322}. This should be a different value than is currently in
that database cell. If using the serial interface, the UltraScan DSP will
send the standard reply.
saving the wall measurements. If using the serial interface, the
UltraScan DSP will send a message indicating the change. If using
DeviceNet or Profibus, the user must poll this cell. This cell will
indicate a value of 127 if it is in the process of saving the wall
measurements, 130 if the wall measurements were successfully
saved, and 132 if the wall measurements were not saved. The wall
save will fail if the transducer status {309} is not zero. Correct the
problem and restart the calibration.
5) The UltraScan DSP will also update cells {310},{311}, and {312} to
indicate the current system operating mode (static or reversing), the
current transducer angle (relevant only if operating in static mode), and
the number of relevant compensation factors to be calculated (will be
equal to 8 if operating in reversing mode or equal to the number of
tranducers if in static mode). These values can be used to setup a
HMI for entering the sector-based calibration values.
correctly.
9) As each of the offline measured sector wall thickness values are set in
the UltraScan DSP, the average layer speed of sound, sector-based
wall thickness compensation factors, and adaptive sector-based wall
thickness compensation factors are updated. If necessary for the HMI,

setup hotlinks to receive updates as the values are entered.
10) Enter the number of offline measured sector wall thickness values
specified by database cell {312}. For a system operating in reversing
mode, cells {570}, {571}, {572}, {573}, {574}, {575}, {576}, and {577}
would be set for layer 1. For a system operating in static mode, cells
{570}, {571}, {572}, and {573} would be set for a 4 transducer system.
11) Poll or hotlink the adaptive sector-based wall thickness calibration
compensation factors (cells {580 and 581}). These cells need to be
read from the UltraScan DSP if they are to be stored in a library file.
12) Repeat step 9 through 11 for each layer as appropriate. For layer 2,
use cells {670} through {676} to enter the measured wall thickness
values and cells {680 and 681} to read back the wall thickness
calibration compensation factors. For layer 3, use cells {770} through
{776} to enter the measured wall thickness values and cells {780 and
781} to read back the wall thickness calibration compensation factors.
For layer 4, use cells {870} through {876} to enter the measured wall
thickness values and cells {880 and 881} to read back the wall
thickness calibration compensation factors.
OD Calibration
1) Place the small calibration pin into the gauge head. The transducer
gains should be below 30% for all configured transducers.
2) Clear the calibration status by changing {329} to a random number.
This should be different from the current value and not one of the
defined enumerations.
3) If using the serial port, wait for the UltraScan DSP to reply. If using
DeviceNet or Profibus, read back the value to ensure that it has been
cleared.
4) Set {320} to the size of the small calibration pin. Verify that this is set
correctly.
5) If using the serial interface, the UltraScan DSP will send a response
indicating a new value in {329}. If using DeviceNet or Profibus, the
user must poll this cell. The value will be set to 133 if the calibration
of the small pin was completed successfully. The value will be set to
135 if the small pin calibration failed.
6) Set {2105} with the gauge expansion coefficient. Aluminum 23 x 10-6
1/C or 12.77778 x 10-6 1/F, Stainless Steel 13 x 10-6 1/C or 7.22222
x 10-6 1/F, Delrin 122.4 x 10-6 1/C or 68 x 10-6 1/F.
OD Offset Calibration
OD offset calibration can be performed as a part of the wall thickness
calibration (see above). The OD offset calibration is used to account for
product shrinkage from the point of measurement to the end of the production
line or even after the product has been set aside to cool.
The uncompensated average OD measurement is saved by the UltraScan
DSP along with the individual wall measurements when the capture cell {322}
is set (see the wall calibration procedures above). The product diameter
measured at the gauge head can be read from cell {351} after the calibration
capture has completed successfully. The offline measured OD can be
combined with the product diameter measured at the gauge head to calculate
an OD offset value. The OD offset is applied so that the OD measurements
reported by the UltraScan DSP reflect the final product diameter instead of the
diameter measured at the gauge head. The OD offset should be calculated as
follows:
ODoffset = OfflineOD UncompensatedOD
The OD offset is subsequently applied by setting the OD offset cell {400} with
the value calculated above.
Appendix E: High Speed Tolerance Checking
Overview
High-Speed Tolerance Checking in the UltraScan DSP is intended to provide
customers with the ability to detect short-term wall thickness errors in their
product.
The theory is to compare a single scan or very small average of scans of wall
thickness with the running average or a nominal preset value and determine if
some tolerance has been exceeded.
Each layer is considered individually during the high-speed tolerance checking
and contain their own configuration values.
Modes
Two modes of high-speed tolerance checking are provided for the user
preset mode and relative wall mode.
Preset mode allows the user to preset a desired nominal wall value for the
product. A lower offset is subtracted from the nominal to determine the lower
thickness limit, and an upper offset is added to the nominal to determine the
upper thickness limit. If a single scan or small average is outside of these
tolerances, an error is triggered. This mode is like traditional tolerance
checking.
Measured wall mode is processed in the same manner as preset mode,
except the current individual wall thickness value for each transducer is used
as the nominal wall for that transducer. Since the individual walls are
averaged over some preset averaging duration, and the high-speed tolerance
checking is performed on single scans or a very small average of scans, this
mode allows slow changes in wall thickness to occur, but triggers on rapid
changes.
Sensitivity Adjustment
As would be expected in a form of tolerance checking, the standard
adjustment of an upper and lower wall thickness offset is available for the user
to configure. The offsets are layer-specific. There is an upper and lower
offset value for each layer of a multi-layer product. Besides this basic
configuration, there are a few other sensitivity adjustments that can be made
to the high-speed tolerance functionality.
Averaging Group Size

The averaging group size allows the user to adjust the number of scans to
average together to determine the current scans thickness. If this value is
set to one, single scan data will be compared against the nominal and offset.
For any other value, the set number of scans is averaged together. To ensure
that this average can only be a short-term average, the number of averaged
scans is limited to a maximum of ten. This configuration is global for all layers.
For example, if the group size is set to three, the current scan calculates a wall
of 2.0 mm, and the previous two scans calculate walls of 2.1 mm and 2.2 mm,
the value which will be compared against the tolerance limits is 2.1 mm.
Min Groups for Error Detection/Termination

The minimum groups for error detection setting allows the user to specify how
many consecutive out-of-tolerance groups are required before triggering a
high-speed tolerance error for a single transducer.
Similarly, the minimum groups for error termination setting allows the user to
specify how many consecutive in-tolerance groups are required to clear a
high-speed tolerance error for a single transducer.
Both of these configurations are global for all layers.
Error Indication
The UltraScan DSP contains database cells and packets which can be queried
to determine high-speed tolerance status. The information in the database
cells and packets is updated on a programmable update interval (see
description of database cell {376} and the Error Termination Packet below).
Most users interested in high-speed tolerance checking will want to hot-link the
appropriate cells and packets to receive fastest notification of status changes.
While the database cells can be polled via the serial interface or through either
fieldbus interface, hot-linking is only possible through the serial interface. The
information contained in the packets is only available though the serial
interface.
All-Layer Status
Database cell {375} contains the status information for all layers, indicating
which layers have transducers reporting oversize conditions, and which layers
have transducers reporting undersize conditions.
Bit: 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Layer: 4 3 2 1
RESERVED
Function: O U O U O U O U
U: Undersize error present in one or more transducers

O: Oversize error present in one or more transducers
This cell is useful for triggering an alarm, since it can be quickly checked for a
non-zero value and displays all layers at once.
Individual Layer Status

Each layer has its own database cell containing the high-speed tolerance
status information for each transducer. These database cells are numbered
{550}, {650}, {750}, and {850} for layers 1 through 4 respectively.
The format of these database cells is as follows:
3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1
Bit: 9 8 7 6 5 4 3 2 1 0
1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0
Transducer: 8 7 6 5 4 3 2 1
Function: O U O U O U O U O U O U O U O U
U: This transducer currently indicates an undersize error

O: This transducer currently indicates an oversize error
While a single layer may have transducers indicating both oversize and
undersize errors, a single transducer obviously cannot have both true in a
single layer.
Error Termination Packet

When an error has terminated on a particular layer, the data contained in the
corresponding error termination packet is updated. The error termination
packet only contains information about new errors. There is no historical
information stored in the UltraScan DSP.
An error termination will often only contain information about a single error. It
will contain information about multiple errors only if those errors all occurred
within a single update interval. The update interval is specified by the setting
in database cell {376} and defaults to a 600ms interval. The update interval
can be specified from 0.2 to 2 seconds in length.
The following information is contained in the error termination packet:
1) Packet Count This number is incremented each time the packet is
updated. This is useful for determining if receipt of an error packet was
missed. This counter starts at zero and rolls over at 9999.
2) Transducer Status This is a hex bit field in the same format as the
individual layer status database cells. This indicates which transducers
were in an error condition during any of the errors described in this
packet. For example, if two errors are described in which T1 and T2
were out of tolerance for one error and T5 was out of tolerance for the
second, the appropriate oversize and undersize bits would be set for all
three transducers.
3) Number of Errors in Packet This number lets the user know how
many errors terminated during this past update interval.
4) Max Size of Error This provides the maximum size that was
measured by an out-of-tolerance transducer during any of the errors
described in this packet. If there were no oversize errors, this value is
meaningless and should be zero.
5) Min Size of Error This provides the minimum size that was measured
by an out-of-tolerance transducer during any of the errors described in
this packet. If there were no undersize errors, this value is
meaningless and should be zero.
6) Num Oversize Errors This is the number of oversize errors which are
described in this packet. An oversize error is described as a condition
where one or more transducers are continually reporting oversize
errors. A single error may have multiple oversize errors.
7) Num Undersize Errors This is the number of undersize errors which
are described in this packet. An undersize error is described as a
condition where one or more transducers are continually reporting
undersize errors. A single error may have multiple undersize errors.
8) Error Length This is the length of product between the start of the
first error described in this packet and the end of the last error
described in this packet. If no line speed is provided to the UltraScan
DSP, this value will always be zero.
Examples
In order to help describe how the UltraScan DSP counts errors and updates
the appropriate database cells, the following six examples are provided. In
these examples, the solid vertical lines indicate 600 ms update cycles, and the
horizontal dotted lines show the upper and lower high-speed tolerance limits.
For simplicity, all examples show only one or two transducers. All other
transducers are assumed to be within tolerance. Transducer 1 is indicated by
a solid line, while transducer 2 (when present) is displayed with a dashed line.
Example #1
1 2 3 4 5 6
1) No update
2) Transducer status updated to indicate T1 out of tolerance
3) Error termination packet describing error
4) Transducer status updated to indicate no errors
5) No update
6) No update
Example #2
1 2 3 4 5 6
1) No update
2) Transducer status updated to indicate T1 and T2 out of tolerance
3) No update
4) Transducer status updated to indicate only T2 out of tolerance, Error
termination packet updated to describe T1/T2 error (1 error)
6) No update
Example #3
1 2 3 4 5 6
1) No update
2) Transducer status updated to indicate T1 out of tolerance, Error
termination packet updated to describe errors (2 errors)
4) No update
5) No update
6) No update
Example #4
1 2 3 4 5 6
1) No update
2) Transducer status updated to indicate T1 out of tolerance, Error
termination packet updated to describe errors (2 errors)
3) Error termination packet updated to describe error (1 error)
5) No update
6) No update
Example #5
1 2 3 4 5 6
1) No update
2) Transducer status updated to indicate T1 and T2 out of tolerance
3) Transducer status updated to indicate only T2 out of tolerance, Error
termination packet updated to describe error (1 error)
5) No update
6) No update
Example #6
1 2 3 4 5 6
1) Transducer status updated to indicate T2 out of tolerance

2) Transducer status updated to indicate T1 and T2 out of tolerance, Error
termination packet updated to describe error (1 error)
3) Transducer status updated to indicate only T2 out of tolerance
4) Error termination packet updated to describe error (1 error)
6) No update
Troubleshooting
If you are having problems using the UltraScan DSP High Speed Tolerance
Checking feature, please refer to the following table of common problems and
reasons.
Symptom Common Reasons
High-Speed Tolerance Status always in UltraScan DSP contains software version prior to rev D
tolerance
HST option not enabled in UltraScan DSP
HST mode set to OFF
Sensitivity set to low (too many groups required to trigger error)
Set to Measured Wall Mode instead of Preset Wall Mode
High-Speed Tolerance Status always Sensitivity set too high

out of tolerance
Set to Preset Wall Mode instead of Measured Wall Mode
One layer of multi layer product works Verify that all the layer-specific high-speed tolerance checking
correctly, second (or third or fourth) is options have been set correctly for all layers.
always out of tolerance
When a product has a wall thickness Increase the value for the minimum good scans before error
error correctly detected by the termination.
UltraScan DSP, several errors are
reported, instead of just one.
Appendix F: Waveform Processing Modes

The following sections describe the wavefrom processing modes selectable by
database cell {270}. The processing modes currently supported include the
center-of-energy, initial-energy, thin-wall tube, and total wall modes. The
initial-energy mode is the default processing mode.
Center of Energy Mode

The center of energy mode is a good general purpose method for determining
the measurement points on the waveforms. It takes the measurement points
at the peaks of the processed waveform (see figure below). This can offer a
more stable measurement in the presence of a moderate amount of signal
noise.
Points of
measure ment
Initial Energy Mode (Default)

The intial energy mode is also a good general purpose method for determining
the measurement points on the waveforms. It takes the measurement points
at the leading edge of the peaks of the processed waveform (see figure
below). This mode offers a more accurate and stable OD measurement when
the product position within the gauge fluctuates. This is the default mode of
processing. The initial energy mode should always be used when ultrasonic
OD measurements are required.
Points of
measurement
Thin-Wall Tube Mode

The thin-wall tube mode is used to measure very thin walled tubes typically
with thicknesses below 125 microns (0.005). Use database cell {1000} (the
echo #1 relative amplitude) to adjust the processed waveform fit to the
filtered waveform. The value sets the relative amplitude and polarity of the
first echo to the second. Typically the value of database cell is between 10%
and 60% with a default value of 20%.
Total Wall Mode

The total wall mode is used to measure multi-layered products as a single total
wall. Intermediate echoes are automatically ignored. The waveforms must be
void of any spurious noise for this mode to yield consistent and accurate
results. The user must keep in mind that the wall thickness calibration speed
of sound value is an average value of all the different materials that make up
the construction of the product. The relative proportions of the different
materials must be maintained as the wall thickness changes for the calibration
speed of sound to be accurate.
Use database cell S1/273 to define the number of waveform echoes to search
for. If the value of S1/273 is 2, then the DSP makes an effort to determine the
number of echoes automatically. In this mode, the the SNR threshold can be
used to control the echoes used in determining the total wall thickness of the
product. The DSP will add echoes until the SNR threshold is satisfied so
increasing the SNR threshold will typically add more echoes to the total wall
waveform. If the value of S1/273 is greater than 2, the DSP will find the
specified number echoes in the waveform and will use the first and last echoes
to determine the total wall thickeness.
Appendix G: Time-varying Gain (TVG)

The following sections describe the time-varying gain modes selectable by
database cell {250}. The time varying gain (TVG) feature of the UltraScan DSP
can be enabled to facilitate the measurement of products that are very difficult
to measure ultrasonically. These types of applications would include
applications where the relative echo amplitudes vary greatly from one to
another. In general, this feature should be disabled to preserve the fully
automatic nature of the UltraScan DSP acquisition and measurement of typical
products.
The TVG feature supports several different modes including:
Disabled
Hardware-based automatic TVG
Hardware-based manual TVG
Software-based automatic TVG
Software-based manual TVG
The hardware-based modes vary the gain setting of the analog input amplifier
hardware up or down. The hardware-based modes are only available if the
analog card hardware version number (see database cell {4101}) is 5 or greater.
The software-based modes simply apply mathematical scaling of the post-
digitized raw waveform data. The software-based modes are available for all
analog hardware versions.
The initial gain value of the waveform is determined by the most significant
overall amplitude of the raw waveform (including the affects of hardware-
based TVG if it is enabled). The TVG feature can be enabled to abruptly
change the amount of gain applied to the waveform relative to the initial gain
value.
Disabled Mode
When TVG is disabled, the initial gain is applied uniformly throughout the
entire waveform and no digital scaling is performed on the post-digitized data.
This is the default mode of operation.
Hardware-Based Automatic TVG Mode

In this mode, the DSP configures a single TVG point with a fixed TVG
threshold (25%), a fixed TVG gain delay (3x the selected transducer pulse
length after the first crossing of the TVG threshold) and a fixed TVG gain
adjustment (+18dB relative to the initial gain). These settings are applied
universally across all transducers. This mode should only be used for single
layer products where the first measurement echo is very strong relative to the
second. Typically this mode is useful for products and materials that are
highly attenuative to the ultrasound signal being transmitted though them.
Hardware-Based Manual TVG Mode

In this mode, the user must specify the TVG threshold, the TVG gain delay(s)
and the TVG gain adjustment(s). Up to three TVG points can be configured.
The settings for each TVG point are applied universally across all transducers.
TVG Threshold
The TVG threshold is configured as a percentage of the input range of the A/D
converter. The threshold is equally spaced above and below the zero point of
the raw waveform. At the first crossing of the TVG threshold (positive or
negative), the DSP begins the countdown of the first TVG delay. The default
TVG threshold is set at 10%. Care should be taken when setting thresholds
below 10% as the TVG feature could be inadvertently triggered on extraneous
noise. For applications where the first echo is very strong, the threshold can
be raised to 50% to avoid extraneous triggering. Care should also be taken to
not set the threshold too high or the TVG may not be triggered if the echoes
do not reach the threshold value. This setting applies to the hardware-based
manual TVG mode only.
TVG Gain Delay

The TVG gain delays are configured as a delay in samples from the first
crossing of the TVG threshold. All TVG gain delays must be positive values in
this mode. At the end of the first delay the first gain adjustment is applied. At
the end of the second delay the second gain adjustment is applied and the
same applies to the third delay.
TVG Gain Adjustment

The TVG gain adjustments are configured as relative hardware gain
adjustments in 3dB steps up or down from the initial gain. A setting of 0
represents no change from the initial gain. A setting of 1 represents an
increase of +3dB from the initial gain value. A setting of -1 represents a
decrease -3dB from the initial gain value.
A special condition exists when the desired gain adjustment would exceed the
capabilities of the analog amplifier. When this occurs, the initial gain is
reduced so that the desired gain adjustment results in the amplifier reaching
the full amplification available.
This setting applies to the hardware-based manual TVG mode only.
Software-Based Automatic TVG Mode

In this mode, the software scales the all digital values ahead of and after the
most significant point (positive or negative) in the waveform. A region around
(one transducer pulse duration before and one after) the most significant point
in the waveform is excluded from scaling. The second most significant point
outside the region of exclusion for the most significant point is used to
determine the scaling factor. The second most significant point and all others
outside the region of exclusion (both before and after) are scaled equally to
make the second most significant point equal in amplitude to that of the most
significant point. The amount of scaling is calculated dynamically for each
waveform and is independently calculated for each transducer.
Software-Based Manual TVG Mode

In this mode, the software scales the digital values either before or after the
most significant point (positive or negative) in the waveform. The user must
specify the TVG gain delay point. The direction of the scaling (before or after)
is determined by the sign of the gain delay specified. The amount of scaling is
calculated dynamically for each waveform and is independently calculated for
each transducer.
TVG Gain Delay

Only one gain delay can currently be configured in this mode. The delay
specified can be positive or negative. To specify scaling before the most
significant point, set a delay that is negative. To specify a scaling after the
most significant point, set a delay that is positive. The setting for this TVG
delay point is applied universally across all transducers.
Appendix H: UltraOPC Server

This section describes the UltraOPC server (also known as the SON server).
The UltraOPC server is a software program which runs in the background on a
Windows PC. The server uses a serial COM port to send and receive
message with the UltraScan DSP. The serial messages are converted into
measurement and setup information. This information is made available to
other applications through an OPC interface. Other programs, such as
UltraView, can then obtain the current measurement and setup information
through the industry standard OPC interface of the UltraOPC server. End
customers can also use the UltraOPC server to display measurement and
setup data in their own SCADA packages.
DataPro PC
UltraView
UltraOPC UltraScan
UltraComponents DSP
OPC Server
Interface Serial
Cable
SCADA Software
The full functionality of the UltraOPC server software is described in the online
help files. This document provides some supplemental information about the
server and is not intended to replace the online help files. This document
assumes that you are already familiar with the information found in the help
files. It is recommended that you read the help files before continuing.
Power Tool help file: SON.hlp
UltraOPC server help file: OSDKTLB.hlp
The UltraOPC server requires one of the following Windows operating

systems:
Windows NT 4.0 with Service Pack 5 or greater.
Windows 2000.
Windows XP
This server complies with the OLE for Process Control (OPC) v1.0a standard.
Any v1.0a-compliant OPC client application can access the UltraScan DSP
data through the I/O Server.
UltraOPC Server Tools and Files

There are several troubleshooting and setup tools for the UltraOPC server.
These tools and their related files are discussed in this section.
Power Tool Introduction

The UltraOPC Power Tool (also called the SON Power Tool) is the main
configuration utility for setting up and troubleshooting the UltraOPC server. To
start the Power Tool, select the Windows Start menu Programs SON
OPC Server SON Power Tool. If the I/O Driver Server Connection dialog
box appears, select Use Local Server.
CAUTION: When using the Power Tool, do not save configuration

changes to the UltraComponents.son or
UltraComponents.csv files. Do not change the setting for
the Default configuration file name or the Default path for
the configuration file. Modifying or changing these settings
could cause UltraView and DataPro to stop working!
Power Tool Help Topics

The Power Tool includes context sensitive help 1, which can be activated by
pressing the F1 key. For an overview of the Power Tool refer to the section
Overview: About the I/O Driver Power Tool. For an overview of the
troubleshooting tools refer to the section Tools for Troubleshooting the SON
I/O Driver. For an overview of the Power Tools user interface, read the topics
under the sections:
Understanding the PowerTools Graphic Interface
Viewing Statistics
To find these two sections:

1) From within the Power Tool, press F1 to open the help file
2) Press Help Topics in the tool bar
3) Select the Contents tab
1
The help files contain information for the FIX applications from Intellution. This information is not applicable
to the UltraView program.
4) Select either Using the Power Tool Understanding the

PowerTools Graphic Interface or Running the I/O Driver
Viewing Statistics
Power Tool Objects

The UltraOPC server consists of the several types of objects, which can be
seen, in the tree view of the Power Tool.
Each of these objects has both configuration and statistics properties. The
configuration properties are different for each object. Some of these settings
include software version (Driver Object); PC COM port and Baud Rate
(Channel Object), Reply Timeout, Retries, and Delay Time (Device Object);
and Command Type, Data Type and Parameter, (Datablock Object). To view
the configuration properties, click on one of the objects in the tree browser and
press the configuration button . The statistics provide timeout, and
retries for the driver and each channel, device, and datablock defined. To view
statistics properties, click on one of the objects and press the statistics button
. Refer to the Using the Power Tools Properties Viewer section for
more information about these two views. Each of the object shown above are
discussed in the following paragraphs.
Driver Object
Manages Channel Objects and the overall state of the UltraOPC server. The
software version can be seen from the Drivers Configuration View. You can
also view the server version from the About button on the ultrasonic Setup
page.
Channel Object
A channel is an UltraOPC servers communication path. Each channel has its
own serial port settings including COM port number, and baud rate. To
simultaneously change the serial settings for both the PC and the UltraScan
DSP, use the Communications Setup page in the
UltraView/UltraComponents. If you are using the UltraView/UltraComponents,
you must be logged in as service to access this page. To verify the channel
settings refer to the Cannot communicate with the UltraScan DSP entry in the
OPC Server/UltraScan Troubleshooting section of this manual.
Channel Configuration Properties
Communication's Setup Page
Device Object
As used in the UltraOPC server, the device object is used to group related
datablocks that share the same Reply Timeout, Retries, and Delay Time
settings.
Datablock Object
A datablock corresponds to a database cell in the UltraScan DSP. For
example, a datablock can be configured to read the S1/100 database cell. You
can view the datablock properties to ensure that the UltraOPC server and
UltraScan DSP are working properly: Below is a list of items that can indicate
problems.
A datablock whose Block Name is Datablock followed by a number.
This datablock can slow down communications between the UltraOPC
server and the UltraScan DSP which may result in intermittent No
Comms errors, slow data updates, or timeout errors in the calibration
wizard. The UltraView/UltraComponents software accessed this non-
existing datablock so it was created automatically by the UltraOPC
server. To correct this problem, replace the UltraComponents.son

configuration file with the right version of the file.
A datablock whose Timeouts or Retries continues to incrementing but
the Receives count does not change 2. This datablock can slow down
communications between the UltraOPC server and the UltraScan DSP
which may result in intermittent No Comms errors, slow data updates,
or timeout errors in the calibration wizard. The OPC server is not able
to read the database cell from the UltraScan DSP. To correct the
problem, download the correct software version into the UltraScan
DSP.
In addition to the statistics listed above, the OPC server supports a datascope
to help troubleshoot errors. Any objects that have the datascope enabled will
send messages to the datascope window. To display the datascope, click the
Datascope button from the Run-time toolbar. For additional information
about the Datascope, refer to the Datascope section of the help file.
UltraComponents.son and UltraComponents.csv configuration files

The UltraOPC server must be configured before it can be used to talk to the
UltraScan DSP. Two standard setup files, UltraComponents.son and
UltraComponents.cvs, have already been created and are required for the
UltraComponents and UltraView programs. The UltraComponents.csv file is a
text version of the configuration file and should be included as both a
reference and backup. For more information about the csv file refer to the
Using I/O Driver Report Files section of the help files. These two configuration
files should be used without modification in most customer applications. In the
Power Tool, the default configuration file name should be set to
"UltraComponents.son" and the default path set to "C:\Program Files\SON\".
For more information about these settings, refer to the Power Tools help topic
Setting Defaults for I/O Driver Configuration File Name and Path.
CAUTION: When using the Power Tool, do not modify or overwrite the OPC
configuration files, UltraComponents.son or
UltraComponents.csv. Doing so may prevent UltraView from
working!
UltraCommand.exe
UltraCommand.exe is a program developed by Beta LaserMike that sends
user entered serial commands to the UltraScan DSP and display the
2
To find a problem datablock, first check the statistics for the Drive Object. If the Timeouts or Retries are
incrementing, check the statistics for each Channel Object. Once the problem channel is identified, check the
statistics for each Device Object under this channel. In the same way, check each Device Object to narrow
down the problem.
response. Unlike a terminal program, this program can be used while

UltraView is running.
Troubleshooting
Problem/
Possible cause Action
Error message
Cannot Power is not being If the UltraScan DSP light is off, power is not being applied. If this is the case,
communicate with applied to the check the following:
the UltraScan DSP. UltraScan DSP.
Verify that the power supply is plugged in and turned on.
Verify that the cable is securely connected between the power

supply and the UltraScan DSP.
Verify that the power supply and power cable are good.
Verify that the power at the AC wall outlet is good.
If the light is still not on, call the Beta LaserMike Customer Service
Department.
The serial cable is Verify that the serial cable is securely connected to the PC and UltraScan
not connected DSP.
between the PC and
UltraScan DSP.
The serial cable is Verify the serial cable is securely connected to serial port 1 on the UltraScan
connected to the DSP.
wrong port on the
UltraScan DSP.
Problem/
Error message
The serial cable is If it is not already running, start the UltraView. If UltraView will not
not connected to the run, use the UltraOPC Power Tool (also called the SON Power
PC COM port Tool).
specified in
UltraView.
The PC serial port

settings do not match Press the Setup button then the Comm button
the settings in the
UltraScan DSP
The OPC Channel is

disabled
Verify that the serial cable is plugged into PC COM port specified for
the Primary setting.
Verify the following settings :
Baud Rate = "38400" 3
Data Bits = "8"
Parity = "None"
Stop Bits = 1
Flow = "None"
Start the Power Tool (SONDidw.exe) and verify the following:
Check the PC COM port selection
Check the baud rate and other serial port settings.
Check that the OPC Channel is enabled.
3
The default baud rate for serial port 2 on the UltraScan DSP is 9600.
Problem/
Error message
The serial cable is Ensure that UltraView and any other programs that use the UltraOPC
bad server (UltraCommand, UltraOPC Power Tool) are shut down.
The cable is not Check the serial communications as follows:

wired properly
1) Start HyperTerminal or another terminal program of your choice.
The PC COM port is HyperTerminal can be started by pressing the Windows Start button,
bad then selecting Programs, Accessories, Communications,
HyperTerminal.
2) Configure the serial port settings in the terminal program for 38400
baud, 8 data bits, no parity, 1 stop bit, and no flow control. Also set
the terminal program to append line feeds to incoming line ends. If
you are using HyperTerminal:
In the Connection Description window, set the Name: to

"UltraScan DSP" or any other name of your choice. Optionally,
select any icon of your choice.
Press OK
In the Connect To window, set Connect using: to the PC COM

that is connected to the UltraScan DSP.
Press OK
In the COM Properties window on the Port Settings tab, set the
following:
Bits per second: = "38400" 4
Data bits: = "8"
Parity: = "None"
Stop bits: = 1
Flow Control: = "None"
Press OK
Press the HyperTerminals Properties button
Select the Settings tab
Press the ASCII Setup button
Check the box next to Append line feeds to incoming line ends.
Press OK twice.
If the HyperTerminal says "Disconnected" in the bottom left of the

window, press the Call button
4
The default baud rate for serial port 2 on the UltraScan DSP is 9600.
Problem/ Possible cause Action

Error message
(continued) 3) Cycle power on the UltraScan DSP. During power up, the terminal
program should display messages from the UltraScan DSP similar
The serial cable is
to the text below. (The actual text from your UltraScan DSP may be
bad
different.)
The cable is not
Switch reads 0
wired properly
Starting power up initialization...
The PC COM port is
bad Main: init database...Max number of records in DB: 526
dbi: 525 total records
hli: 150 nodes, 4800 bytes
init database: done.
Main: starting init loop...
dbms: Starting dsp database sync...
dbms: Restoring from eeprom...
dbms: Restore complete
dbms: starting dsp value sync...
dbms: sync done [0000-1300]
initloop: done.
RS232-1:38400,8,n,1,nf
RS232-2:9600,8,n,1,nf
Starting power up initialization...
UltraScanDSP uC Application
Rev K, Thu Jul 08 08:23:01 2004

UltraScanDSP DSP Application
Rev K, Thu Jul 08 09:03:34 2004
Copyright (C) Beta LaserMike Inc. 1999-2004
*Power up initialization complete.
main: starting main loop...
If no characters appear in the terminal window:
Verify the serial cable is good and it is wired properly

Error message
(continued) Verify the PC COM port is good
The serial cable is If you still do not receive characters when the UltraScan DSP powers up,
bad contact Beta LaserMikes Customer Service Department.
The cable is not If the first several lines appear in the terminal window but unusual characters
wired properly follow, the UltraScan DSP may not be using the default serial port settings.
Look in the terminal window for the text RS232-1:. If this text is present, the
The PC COM port is
UltraScan DSP included its serial port settings in the power up message. The
bad
information that follows the colon isbaud rate, data bits, parity, stop bits, nf
for no flow control or nh for hardware flow control. If the values are different
then the default setting, change the terminal programs serial port settings to
match the UltraScan DSP settings. If you are using HyperTerminal, press the
Disconnect button and then the Properties button . On the Connect
To tab, press Configure. Change the serial port settings to match the
UltraScan DSP then press the OK button twice. Press the Call button .
After changing the terminals programs serial port settings, cycle power on
the UltraScan DSP. The first few characters may be unusual symbols. These
may be followed by the last part of the UltraScan DSPs power up message.
Type the following characters into the terminal program and the press the
Enter key: ?S1/100
Verify that the UltraScan DSP returned the microcontrollers software. The
text should look similar to the following:
*S1/100=Rev K, Thu Jul 08 08:23:01 2004 3b
If there was no reply from the UltraScan DSP, contact Beta LaserMikes
service department.
Shut down the terminal program.

Error message
The OPC server is Ensure that the terminal program is shut down.
not registered
1) Search for the file SONOpc.dll on your hard drive. Remember the
folder were this file is located.
2) Press the Windows Start button then select Run.
3) In the Open: combo box, type the text below, substitute the actual
folder name from step 1 in place of the folder name shown below.
regsvr32 C:\Program Files\Beta
LaserMike\UltraOPC\SONOpc.dll
4) A message should appear similar to the one show below.
5) See if UltraView will communicate with the UltraScan DSP.
Client for Microsoft Verify that the Client for Microsoft Networks is installed:
Networks is not
1) Right click on My Network Places on the PC desktop and select
installed on the PC
Properties.
2) In the pop up window, right click on Local Area Connection and

select Properties.
3) Verify that Client for Microsoft networks is in the list of

components. If it is not, press the Install button. Select Client and
press Add. Pick Microsoft and select Client for Microsoft
Networks and press OK.

Error message
Program locks The UltraOPC server has Close all programs that access the OPC server: UltraView
up when it starts crashed but is still running in (Ultraview.exe), Power Tool (SONDidw.exe), DataPro (DataPro.exe),
the background UltraCommand (UltraCommand.exe). Open the Windows Task
Manager (CTRL-Shift-ESC), select the Processes tab. Verify that
none of these programs are running. Note: it may take several
seconds for a program to finish closing and be removed from the
Windows Task Manager. If any of them are still running, select the
process and press the End Process button. Verify that
BetaOPCClient (BetaOPCClient.exe), SerComms, and TCOM
(TCOM.exe) are not running. If any of them are still running, select
the process and press the End Process button. Now verify that the
OPC server (SONDRV.EXE) is not running. If it is, select the process
and press the End Process button.
Open Windows Explorer and configure it to display hidden files and

The UltraOPC server has left
folders 5. Ensure that the OPC server (SONDRV.EXE) is not running
some corrupt hidden
(see previous step.) Search for the following wildcard files *SON_*.*.
temporary files that prevent
Verify that the following files are not on your computer. If the files are
the OPC server from starting
on your computer, delete them.
SON_BlockList
SON_ExceptionArea
SON_InputArea
SON_OutputArea
UltraOPCSON_BlockList
UltraOPCSON_ExceptionArea
UltraOPCSON_InputArea
UltraOPCSON_OutputArea
5
To show hidden files and folders in Windows 2000, open the Windows Explorer. From the drop down menu
select Tools Folder Options Select the View tab. Select the Show hidden files and folders.

Error message
Program locks The default configuration file Open Windows Explorer and find the folder where UltraOPC was
up when it starts has not been set or does not installedtypically C:\Program Files\SON or C:\Program Files\Beta
exist LaserMike\UltraOPC\. Verify that the file UltraComponents.son is in
this folder. Start the Power Tool. In the pull down menu, select
Options Setup. Select the Default Path tab. Verify that the
Default configuration file name is set to UltraComponents.son and
the Default path for the configuration file is set to the installation
folder for UltraOPC. An example is shown below. Your actual settings
may be different.
Appendix I: Database Layout
Standard Database Fields

The following fields are accessible via any protocol described in this manual. The database access ID is the value
located in the DB column.
DB Parameter Type Format W Values Units Description
100 Micro String RO Ex: Rev B, Mon Nov 11 13:50:18
Application 2002
software
revision
101 DSP Application String RO Ex: Rev B, Mon Nov 11 13:50:18
software 2002
revision
102 Serial number String RO
103 Identification Long RW On power up, set to 0. External
Number devices can set this to any value.
104 Options Long Hex RO 0 = Option not To enable or disable options, please
enabled contact Beta LaserMike.
1 = Option enabled
OD measurement. Bit: 4
High-Speed Tolerancing. Bit: 7
105 Library name Str RW
106 Erase EE Long RW Erase EE memory. Only write
executes the command.
107 Reset Long RW Only write executes the command.
Delays for three seconds then reset
initiates.

109 UltraScan DSP Long RO 0 = OK Indicates the most critical error
gauge status 4 = Microcontroller condition when multiple errors are
not communicating occurring.
with motor drive.
26 = Motor Drive
error.
50 = Bad SNR
51 = Bad % good
scans
52 = DSP not
communicating with
microcontroller.
110 Water Float #.12 RO C, F
temperature
111 Product Long # RW C, F Product temperature at quench point.
temperature at Used for line speed compensation.
quench point See the start of this document for
details about the calibration
sequence.
112 Water Float #.1 RW C, F Water temperature during calibration.
temperature at If line speed compensation is being
calibration used, this setting must be saved and
capture restored when switching recipes.
See the start of this document for
sequence.
113 Option/Serial Str RW This field is used to set a password
Number Entry protected field, such as Options or
Serial Number. Please contact Beta
LaserMike if you need more
information about this field
115 Reversing Long RO The reversing count cell increments
Count each time a reversing gauge
changes its direction of motion.

116 Custom FIR Str RW Max length of custom FIR filter string
Filter is 254 bytes. Setting to empty string
will clear the custom FIR filter. Filter
coefficients are comma or space
delimited 16-bit signed fixed point
decimal values. This string is stored
to non-volatile memory within the
DSP. Contact Beta LaserMike if a
custom filter is required.
120 CANbus MACID Long RW 0 to 63 - DeviceNet Default is 63 (DeviceNet MACID 63).
64 to 128 - None See DeviceNet MACID / CANopen
129 to 255 - Node ID.
CANopen
121 CANbus baud Enum RW 0=125k Default is 125k
rate 1=250k Applies to both DeviceNet and
2=500k CANopen protocols
122 CANbus bus-off Enum RW 0=Stay bus off Stay bus off(0) is the default
interrupt action 1=Reset stack Applies to both DeviceNet and
CANopen protocols
125 ProfiBus slave Long RW 1 to 126 Default is 70
address
126 ProfiBus Enum RW 0=Unlocked Unlocked is the default
address change 1=Locked
lockout
131 Serial port 1 Enum RW -26 = 4800 Default is 38400
baud rate -27 = 9600
-28 = 19200
-29 = 38400
132 Serial port 1 Long RW 7, 8 Default is 8 bits
data bits
133 Serial port 1 Enum RW 0 = None Default is None
parity 1 = Even
2 = Odd
134 Serial port 1 Long RW 1, 2 Default is 1
stop bits

flow control 1 = Software
2 = Hardware
141 Serial port 2 Enum RW -24 = 1200 Default is 9600
baud rate -25 = 2400
-26 = 4800
-27 = 9600
142 Serial port 2 Enum RW 7, 8 Default is 8
data bits
parity 1 = Even
2 = Odd
144 Serial port 2 Enum RW 1, 2 Default is 1
stop bits
flow control 1 = Software
2 = Hardware
148 Gauge model String RW Model name Maximum length: 80 characters
User Defined
149 Gauge diameter Float #.12 RW mm, in The gauge ID also referred to as
throat size.
The value of this data base cell is
included in packet(s) {P11}.
150 Number of Long RW 1 to 8
transducers

152 Transducer type Enum RW 0 = Default
1 = RSVD
2 = 0.5MHz
25mm
3 = 1MHz 25mm
4 = 2.25MHz
25mm
5 = 5MHz
6 = RSVD
7 = 10MHz 25mm
8 = 10MHz 6mm
9 = 20MHz 3mm
10 = 30MHz 6mm
11 = RSVD
12 = 10MHz 6mm
Seal-Tite
13 = 20MHz 3mm
Seal-Tite
153 Ping count Long RO 0 to Max long value This value is incremented each ping.
It is independent of the number of
transducers. After the count reaches
Max signed long (2,147,483,647),
the count starts over again at 0.
154 Ping rate Long RO pings/s This value is independent of the
number of transducers.
155 Die bolts - Long RW 4, 6
number
156 Die bolts Enum RW -54 = On
angled -55 = Off
157 Transducer Float #.123 RW -Pi to +Pi radians
angle
158 Product angle Float #.123 RW -Pi to +Pi radians
161 Number of Long RW 1 to 4 Number of layers to be measured
layers
162 Measurement Long RW 1 to 6 Number decimal places for
resolution measured values
163 Metric or Enum RW -15 = Metric

imperial -16 = Imperial
measurement
units
164 Averaging Enum RW -54 = On A running average is produced if the
mode, discrete -55 = Off discrete mode is disabled
165 Averaging units Enum RW -326 = Seconds Only Seconds and Pings are
-327 = Pings supported
-328 = Length
166 Static Mode Float #. RW 0.01 to 20.00 s, pings, m, ft Averaging duration for fixed gauges
Averaging - or - (seconds), or when reversing/rotating gauge is
duration #.12 1 to 2000 (pings) static.
0.01 to 20.00
(length)
167 Sampling Enum RW -8 = Auto Default is Auto. When manual mode
window mode -11 = Manual is set, sampling window presets are
-324 = Fixed employed. When the Fixed Duration
Duration mode is set, the sampling window
duration presets are used with the
start of the widow being determined
automatically.
168 Sampling Long RW 0 to Max long value Samples Set delay from ping to start of
window start waveform acquisition for transducer
preset 1 1
169 Sampling Long RW Min based on Samples Number of samples to acquire for
window duration transducer type to transducer 1
preset 1 458752000
preset 2 2
preset 2 458752000
preset 3 3
preset 3 458752000
preset 4 4
preset 4 458752000
preset 5 5
preset 5 458752000
preset 6 6
preset 6 458752000
preset 7 7
preset 7 458752000
preset 8 8
preset 8 458752000
184 Sampling Long RO Samples Delay from ping to start of waveform
window start acquisition for transducer 1
actual 1
185 Sampling Long RO Samples Number of samples acquired for

window duration transducer 1
actual 1
actual 2
actual 2
actual 3
actual 3
actual 4
actual 4
actual 5
actual 5
actual 6
actual 6
actual 7

actual 7
actual 8
actual 8
200 Waveform Enum RW -54 = On Enables and disables the waveform
filtering -55 = Off FIR filtering. This setting is stored to
the non-volatile memory within the
DSP.
201 Ignore delay 1 Long RW 0 to Max long Sample offset Relative sample offset from first echo
used for wall measurement to the
start of the ignore region. 0 disables
ignore region.
202 Ignore end 1 Long RW 1 to Max long Sample offset Relative sample offset from first echo
end of the ignore region.
ignore region.
ignore region.
207 Auto Ignore Enum RW -290 disabled Default value: -292 adaptive length
Mode -291 fixed length ignore.
ignore The setting of this cell determines
-292 adaptive the amount of time after each echo
length ignore to automatically ignore before
looking for the next echo.
A setting of -290 disables the
automatic ignore feature.
A setting of -291 enables a short
fixed length ignore period after each
echo. The length of the ignore
period is predefined based on the
transducer type selected.
A setting of -292 enables an adaptive
ignore period based on 5/8 of the
average time from one echo to the
next for all transducers.
218 Database Enum RW 0 RSVD This cell initiates an external
External Sync 1 General sync database synchronization process.
Command 2 Units sync The value written to this cell dictates
3 Resolution sync what subset of the entire database
will be output during the
synchronization process.
219 Database Long RO 0 to Max Long # of cells to This cell reports 0 when the
External Sync sync synhronization process is complete
Status or is not active. When the sync
process is active, this cell reports the
number of database cells remaining
to be synchronized.
220 Initial gain Long RW -100.00 to +100.00 % Set to 0 for auto gain. Negative
gains represent attenuated signals.
221 Initial gain Long RO -100 to 100 % Gain level set for transducer 1. The
transducer 1 value of this data base cell is
241 Extended Long RW 1 to 100 Sets length of extended averaging as
Averaging a count of the normal averaging.
Duration The extended average updates as
the normal average is completely
refreshed with new data. If in the
discrete averaging mode the
extended average is updated when a
new discrete average is calculated.
In the running average mode, the
extended average is updated at a
period defined by the length of the
running average.
250 Time varying Enum RW -55 = Off The hardware-based modes are
gain mode -314 = Hardware- available only for analog hardware
based Automatic with rev ID 4 or greater.
Mode
-315 = Hardware-
based Manual
Mode
-316 = Software-
based Automatic
Mode
-317 = Software-
based Manual
Mode
251 Time varying Long RW Positive values only Relative sample offset from threshold
gain delay 1 supported in crossing when in hardware-based
hardware-based manual TVG mode or offset from
manual TVG. peak waveform value (positive or
Positive or negative negative) when in software-based
values supported in manual TVG mode. 0 will disable
software-based this setting.
manual TVG
252 Time varying Float #.12 RW Gain adjustment from initial gain.
gain gain 1 Positive values increase the gain
relative to the initial gain in +3dB
steps per value. Negaitve values
attenuate the signal in 3dB steps
per value. If the value is set to 0,
then the waveform amplitude will not
be changed from what would result
from the initial gain. This setting is
only used for hardware-based
manual TVG mode.
hardware-based manual TVG mode. 0 will disable
manual TVG. this setting.
manual TVG mode.
hardware-based manual TVG mode. 0 will disable
manual TVG. this setting.
manual TVG mode.
260 Time varying Float #.12 RW 0-100% % This threshold is used for the manual
gain - threshold hardware based TVG mode only.
This determines the trigger point (as
a percentage of a full scale input) for
the subsequent TVG gain transitions.
The threshold is set to trigger on
both positive and negative going
echoes.
270 Waveform Enum RW -293 = Center of Default = -294 (Initial energy mode)
processing energy See Appendix F Waveform
mode -294 = Initial energy Processing Modes for more details.
-295 = Thin wall
tube
-303 = Total wall
272 Total Wall Long RW Defines the number of echoes to be
Echoes found in the total wall waveform
processing mode. If the value is set
to 2, the total wall mode tries to
determine this automatically. If the
value is greater than 2, the total wall
mode finds echoes as if it is
measuring a multi-layered product
but ignores any of the middle echoes
to determine a total wall
measurement.
273 Statistical Enum RW -55 = OFF Enables or disables the statistical
Filtering Mode -331 = Single layer measurement filtering mode.
mode
-332 = Dual layer
mode
274 Single Layer Float #.12 RW Min 0.05secs secs This setting is used for the single
statistical layer statistical filtering mode only. It
filtering mode represents the time from one carcass
pitch period pitch to the next to pass through the
gauge head at the transducer plane.
280 Gauge Enum RW -253 fixed at 0 Default: -253 (transducers have fixed
Transducer -254 fixed at 45 position with transducer 1 at 0).
Configuration -255 manual
-256 reversing
290 Signal to noise Long RO 0 to 100 % If the value is too low there is an
ratio transducer ambiguous signal in the UltraScan
1 DSP. If value is below threshold set
in {298} a transducer error will be
reported. The value of this data base
cell is included in packet(s) {P7}.
298 Signal to noise Long RW 0 to 100 % Signal to noise ratio values below
ratio lower this threshold will generate an error
reject tolerance status in {109} and {309}
Default value 50%. Nominal range
30 to 50% depending on application
requirements.
300 % good scans Long RO 0 to 100 % If value is below threshold set in
transducer 1 {308}, a transducer error will be

308 % good scans Long RW 0 to 100 % % good scans values below this
lower reject threshold will generate an error
tolerance status in {109} and {309}
Default value 50%.
309 Signal to noise Long Hex RO Transducer: 1 2 3 4 5 6 7 8
ratio and % Signal to noise ratio and % good
good scans scans tolerance status for all
tolerance status transducers. Bit field, 1 bit per sensor
for SNR and 1 bit per sensor for %
good scans.
0=OK, 1=out of tolerance
included in packet(s) {P0}, {P1}, {P2},
{P3}, {P4}, {P5}, {P10}, {P12}, {P13},
{P14}, {P15}, {P66}, {P67}, {P68},
{P69}, {P70}, {P71), {P72}, {P73}.
SNR out of reject tolerance. Bits: 0 2 4 6 8 10 12 14
Transducer % good scans out of
reject tolerance.
Bits:
Sector % good scans out of reject 16 17 18 19 20 21 22 23
tolerance. Bits:
Generatrix % good scans out of 24 25 26 27 28 29 30 31
reject tolerance.
Bits:
310 Operating Mode Enum RW -6 = Static Used with wall sector calibration.
during last wall -259 = Reversing This value should be saved and
calibration restored as a library setting
311 Transducer Float #.123 RW -Pi to Pi Radians Used with wall sector calibration to
Angle during represent the angular location of the
last wall transducers during static mode wall
calibration calibration. This value should be
saved and restored as a library
setting
312 Number of Long RW 0 to 8 Used with wall sector calibration to
Significant indicate the number of significant
Compensation compensation values per layer {560-
Values during 567, 660-667, 760-767, 860-867}
last wall calculated during last wall sector
calibration calibration. If this value is set to zero,
the sector compensation will be
disabled. This value should be saved
and restored as a library setting
313 Operating Mode Enum RO -6 = Static Used with wall sector calibration.
during last wall -259 = Reversing This cell indicates the operating
calibration mode during the last wall calibration
capture capture.
314 Transducer Float #.123 RO -Pi to Pi Radians Used with wall sector calibration.
Angle during This cell indicates the transducer
last wall angle during the last wall calibration
calibration capture when the system is in static
capture mode operation. If the gauge is a
fixed gauge, the angle will be
reported as 0. If the gauge is a
reversing gauge operating in
reversing mode, the angle will be
reported as 0.
315 Number of Long RO 1 to 8 Used with wall sector calibration.
Significant This cell indicates the number of
Compensation significant compensation values per
Values during layer {560-567, 660-667, 760-767,
last wall 860-867} to be calculated during the
calibration current calibration.
capture
316 Averaging count Long RW 10 to 500 Pings Number of pings per transducer
for wall averaged together for wall thickness
calibration calibration capture.
capture Default value: 10 pings per
transducer
317 Calibration Long RO Indicates the number of times since
capture count startup that the DSP has captured a
wall measurement for calibration
purposes.
320 OD cal pin Float Meas Res RW mm, in Only write executes the OD
calibration routine. The reply from
reads will return the cal pin size. See
Appendix D for details about the
calibration sequence.
322 Save average Long RW Only write executes the command.
wall See the start of this document for
sequence.
323 Layer 1 actual Float Meas Res RW mm, in Layer 1 average wall measured off-
average wall line for calibration purposes. See
327 Line speed for Float #.12 RW 0.00 disables line m/m, f/m Calibration line speed used for the
temperature speed temperature line speed/temperature
compensation compensation compensation algorithm.
setup algorithms See Appendix D for details about the
328 Line speed Float #.12 RW m/m, f/m Current line speed input. Used for
product cooling rate compensation.
See Appendix D for details about the
329 Calibration Long RW -127 = Saving See Appendix D for details about the
Status average wall calibration sequence.
-130 = Average wall
saved
-132 = Average wall
not saved
-133 = Calibrated
-135 = Not
calibrated
330 Gap 1 Float Meas Res RO mm, in Distance from transducer 1 to the
outer wall. The value of this data
base cell is included in packet(s)
{P9}.
{P9}.
{P9}.
{P9}.
{P9}.
{P9}.
{P9}.
{P9}.
340 X0 Float Meas Res RO mm, in Product position vector (X plane) =
center of the OD referenced from the
center of the gauge. Positive X plane
is 90 degrees from transducer 1 in
the direction of transducer 2. The
value of this data base cell is
included in packet(s) {P6}, {P11}.
341 Y0 Float Meas Res RO mm, in Product position vector (Y plane) =
center of the OD referenced from the
center of the gauge. Positive Y plane
is towards transducer 1. The value of
this data base cell is included in
packet(s) {P6}, {P11}.
342 X1 Float Meas Res RO mm, in Position vector for layer 1 (X plane) =
center of the layer 1 referenced from
the center of the OD. Positive X
plane is 90 degrees from transducer
1 in the direction of transducer 2.
included in packet(s) {P0}, {P12},
{P66}.
343 Y1 Float Meas Res RO mm, in Position vector for layer 1 (Y plane) =
the center of the OD. Positive Y
plane is towards transducer 1. The
{P66}.
the center of layer 1. Positive X
the center of layer 1. Positive Y
350 Sector Enum RW -290 = disabled Default = -291 (fixed sector
Calibration -291 = fixed calibration compensation)
mode -292 = adaptive See Fixed Sector-Based Wall
Calibration and Adaptive Sector-
Based Wall Calibration for more
details
351 Captured OD Float Meas Res RO mm, in Uncompensated OD measurement
captured during wall calibration
sequence. This value can be used
by a controller to calculate an OD
offset (see cell 400).
352 Captured Line Float #.12 RO m/m, ft/m Line speed captured during wall
Speed calibration. This line speed can be
used to setup the line
speed/temperature compensation
algorithm.
370 High Speed Enum RW -55 = Off Mode to use when performing high-
Tolerance Mode -216 = Measured speed tolerance checking
Wall
-217 = Preset Wall
371 High Speed Long RW 1-10 # scans Number of scans to average together
Tolerance for comparing against high-speed
Group Size tolerance values.
372 High Speed Long RW 1-500 # groups Number of consecutive out-of-
Tolerance Min tolerance groups required before
Groups for Error declaring a tolerance error.
Detection
373 High Speed Long RW 1-500 # groups Number of consecutive in-tolerance
Tolerance Min groups required before clearing a
Groups for Error tolerance error.
Termination
374 High Speed Long RW Any write to this location will reset all
Tolerance high-speed tolerance counters.
Count Reset
375 High Speed Hex RO Bit field indicates which layers are L1 L2 L3 L4
Tolerance indicating high-speed tolerance
Status errors, and whether error is over or
under tolerance, or both.
Undersize Error Bits: 0 2 4 6
Oversize Error Bits: 1 3 5 7
376 High Speed Float #.123 RW 0.2 to 2 Seconds Default 0.6 seconds
Tolerance Error
Packet output
rate
382 Motor Drive Enum RW -108 = Start rotation
Command -258 = Goto home
position
383 Motor Drive Hex Bitfield RO
Status
384 Motor Drive Long RO Refer to Ultra3000 Status value reported by AB
Extended Manual Ultra3000 motor drive and passed
Status directly through the UltraScan DSP
400 OD/ID offset Float Meas Res RW mm, in Default = 0.0

Offset value added to measured
value to compensate for OD/ID
shrinkage or expansion
401 OD/ID scaler Float #.1234 RW 0 to 106 Default = 1.0
Scaler value multiplied with
measured value to compensate for
OD/ID shrinkage or expansion
402 Calibration pin Float #.1234 RO mm, in OD measurement of calibration pin.
OD Measurement value only valid when
metal calibration pin is inserted in the
gauge.
403 Uncomensated Float Meas Res RO mm, in This cell represents the raw OD
OD Average average without OD/ID
compensation factors applied
404 OD preset Float Meas Res RW mm, in Nominal OD value used for tolerance
checking
405 OD individual Float Meas Res RW mm, in Tolerance check for individual axis
reject lower OD measurement
tolerance
warning lower OD measurement
tolerance
warning upper OD measurement
tolerance
reject upper OD measurement
tolerance
409 OD average Float Meas Res RW mm, in Tolerance check for average OD
reject lower measurement
tolerance
warning lower measurement
tolerance
warning upper measurement
tolerance
reject upper measurement
tolerance
413 OD individual 1 Float Meas Res RO mm, in Single axis OD measurement for a
transducer pair
transducer pair
transducer pair
transducer pair
421 OD min Float Meas Res RO mm, in Minimum value of all individual OD
measurements
422 OD min angle Float #.123 RO -Pi to Pi radians Angle from transducer 1 in the
direction of transducer 2
423 OD max Float Meas Res RO mm, in Maximum value of all individual OD
measurements
424 OD max angle Float #.123 RO -Pi to Pi radians Angle from transducer 1 in the
425 OD average Float Meas Res RO mm, in The value of this data base cell is
426 OD individual Long Hex RO 0 = OK OD Axis: 1 2 3 4
tolerance status 1 = Out of tolerance Bit field for up to 4 outer diameter
values. 4 bits per diameter
Under reject tolerance. Bits: 0 4 8 12
Under warning tolerance. Bits: 1 5 9 13
Over warning tolerance. Bits: 2 6 10 14
Over reject tolerance. Bits: 3 7 11 15
427 OD individual Long Hex RO 0 = OK Left: OD min/max. Right OD min/ avg

and average 1 = Out of tolerance Average: max
tolerance status Min/max tolerance checking is based
on min for under and max for over.
Four bits for OD min and max. Four
bits for OD average.
Under reject tolerance. Bits: 0 4
Under warning tolerance. Bits: 1 5
Over warning tolerance. Bits: 2 6
Over reject tolerance. Bits: 3 7
450 OD Ovality Float Meas Res RW mm, in
reject upper
tolerance
451 OD Ovality Float Meas Res RW mm, in
warning upper
tolerance
452 OD Ovality Float Meas Res RO mm, in The value of this data base cell is
and {P74}.
453 OD Ovality Long Hex RO 0 = OK
tolerance status 1 = Out of tolerance
Over warning tolerance. Bits: 2
Over reject tolerance. Bits: 3
500 Layer 1 speed Float #.123 RW 0.0001 to 30.000 in/micro-s,
of sound (metric) mm/us
#.1234
(imperial)
501 Layer 1 preset Float Meas Res RW mm, in Nominal wall thickness value used
wall for tolerance checking
502 Layer 1 Float Meas Res RW mm, in Tolerance check for individual
individual wall transducer wall thickness
tolerance
tolerance
tolerance
tolerance
506 Layer 1 average Float Meas Res RW mm, in Tolerance check for average wall
wall reject lower thickness measurement
tolerance
wall warning thickness measurement
lower tolerance
upper tolerance
wall reject upper thickness measurement
tolerance
510 Layer 1 wall Float Meas Res RO mm, in The wall thickness measured at
thickness 1 transducer #1.
532 Layer 1 min wall Float Meas Res RO mm, in The minimum value of all the
measured wall thicknesses. The
533 Layer 1 Float #.123 RO -Pi to Pi radians Angle from transducer 1 in the
predicted min direction of transducer 2. The value
wall angle of this data base cell is included in
534 Layer 1 max Float Meas Res RO mm, in The maximum value of all the
wall measured wall thicknesses. The
predicted max direction of transducer 2. The value
packet(s) {P12}.
536 Layer 1 average Float Meas Res RO mm, in The average wall thickness value for
wall all transducers configured. The
537 Layer 1 Long Hex RO 0 = OK Layer 1. Wall: 1 2 3 4 5 6 7 8
individual wall 1 = Out of tolerance Bit field for up to 8 wall thickness. 4
1-8 tolerance bits per wall
status
Under reject tolerance. Bits: 0 4 8 12 16 20 24 28
Under warning tolerance. Bits: 1 5 9 13 17 21 25 29
Over warning tolerance. Bits: 2 6 10 14 18 22 26 30
Over reject tolerance. Bits: 3 7 11 15 19 23 27 31
539 Layer 1-4 Long Hex RO 0 = OK Layer 1 min/max, avg, L1 L1 L2 L2 L3 L3 L4 L4
individual and 1 = Out of tolerance Layer 2 min/max, avg etc.: mn/ avg mn/ avg mn/ avg mn/ avg
average Bit field for up to 4 layers. 8 bits per mx mx mx mx
tolerance status layer. Min/max tolerance checking is
based on min for under and max for
over.
540 Concentricity Enum RW -97 = Difference/2 Difference/2 =

mode -110 = (MaxWall MinWall) / 2
%Eccentricity/2 %Eccentricity/2 =
-112 = ((Difference/2) / AvgWall) *
%Concentricity2 100%
-211 = Difference %Concentricity2 =
-212 = % ((AvgWall
Concentricity1 (Difference/2)) /
-215= %Eccentricity (AvgWall +
(Difference/2))) * 100%
Difference =
(MaxWall MinWall)
% Concentricity1 =
(MinWall / MaxWall) * 100%
%Eccentricity =
(Difference / AvgWall) *
100%
541 Layer 1 Float #. (%), Meas RW 0 to 100 for %, mm, in When the Concentricity Mode {540}
concentricity Res %Concentricity2, is set to 112 this setting is used as
warning (Difference %Eccentricity, the lower warning tolerance. When
tolerance Difference/2) %Eccentricity2, the Concentricity Mode {540} is set
Percent to 97, 110,211, 212, or 215,
0 to 9.9999 for this setting is used as the upper
Difference, warning tolerance.
Difference/2
reject tolerance (Difference %Eccentricity, the lower reject tolerance. When the
Difference/2) %Eccentricity2, Concentricity Mode {540} is set to
Percent 97, 110,211, 212, or 215, this
0 to 9.9999 for setting is used as the upper reject
Difference, tolerance.
Difference/2
543 Layer 1 Float #. (%), Meas RO 0 to 100 (% %, mm, in The value of this data base cell is
concentricity Res (Linear) Concentricity, % included in packet(s) {P5}, {P12}.
Eccentricity
0 to 9.9999 (Linear
eccentricity)
544 Layer 1-4 Long Hex RO 0 = OK Layer: 1 2 3 4
concentricity 1 = Out of tolerance Bit field for concentricity status for up
tolerance status to four layers. 2 bits per layer
Warning tolerance. Bits: 2 6 10 14 18 22 26 30
Reject tolerance. Bits: 3 7 11 15 19 23 27 31
545 Layer 1 wall Float Scientific RO mm^2, in^2 The value of this data base cell is
cross sectional included in packet(s) {P5}, {P12}.
area
546 Layer 1 Product Long RW 0 = PVC Product material type. Used for
material type 1 = LDPE product cooling rate compensation.
2 = HDPE See Appendix D for details about the
3 = PP calibration sequence.
4 = Nylon
5 = Urethane
6 = FEP
547 Layer 1 Float Scientific RO Microseconds This cell is updated as part of the
captured wall calibration capture sequence. It
average wall represents the average time between
time for layer 1echos for all transducers.
calibration
550 Layer 1 High Long Hex RO 0 = OK 1 2 3 4
Speed 1 = Out of tolerance Layer:
Tolerance Bit field for high speed tolerance
Status status for up to four layers. 2 bits per
layer
Undersize error bits: 0 4 8 12
Oversize error bits: 3 7 11 15
551 Layer 1 High Long RO Number of undersize errors detected

Speed in layer 1. This is reset by a write to
Tolerance cell 374.
Undersize
Count
552 Layer 1 High Long RO Number of oversize errors detected
Tolerance cell 374.
Oversize Count
553 Layer 1 High Float Meas. Res. RW mm, in Nominal wall thickness for high-
Speed speed tolerance checking in Preset
Tolerance Mode.
Nominal Wall
554 Layer 1 Upper Float Meas. Res. RW mm, in Value added to nominal wall (Preset
Wall Offset Mode) or current average wall
(Measured Wall Mode) to determine
upper wall thickness limit for high-
speed tolerance checking.
555 Layer 1 Lower Float Meas. Res. RW mm, in Value subtracted from nominal wall
Wall Offset (Preset Mode) or current average
wall (Measured Wall Mode) to
determine lower wall thickness limit
for high-speed tolerance checking.
560 Layer 1 Wall Float #.123 RW Default value of 1.0. The
Thickness (metric) transducer/sector compensation
Calibration #.1234 factor for layer 1 wall speed of
Compensation (imperial) sound. Used for wall sector or
Factor 1 transducer based calibration
compensation.
compensation.

compensation.
compensation.
compensation.
compensation.
compensation.
compensation.
570 Layer 1 Float Meas. Res. RW mm, in The offline measured layer 1 wall
Average thickness for transducer/sector
Measured Wall based calibration.
1 for sector or
transducer
based
calibration
2 for sector or
transducer
based
calibration
3 for sector or
transducer
based
calibration
4 for sector or
transducer
based
calibration
5 for sector or
transducer
based
calibration
6 for sector or
transducer
based
calibration
7 for sector or
transducer
based
calibration
8 for sector or
transducer
based
calibration
580 Layer 1 Float #.123 RW mm/s2, Layer 1 wall thickness calibration
Adaptive sector (metric) in/s2 factor used when system is operating
calibration slope #.1234 in adaptive sector calibration
(imperial) compensation mode. See Adaptive
Sector-Based Wall Calibration.
581 Layer 1 Float #.123 RW mm/s, in/s Layer 1 wall thickness calibration
Adaptive sector (metric) factor used when system is operating
calibration #.1234 in adaptive sector calibration
intercept (imperial) compensation mode. See Adaptive
#.1234
(imperial)
tolerance
tolerance
tolerance
tolerance
tolerance
lower tolerance
upper tolerance
tolerance
packet(s) {P13}.
636 Layer 2 average Float Meas Res RO mm, in The average value of all the
637 Layer 2 Long Hex RO 0=OK,1=out of Layer 2 Wall: 1 2 3 4 5 6 7 8
individual wall tolerance Bit field for up to 8 wall thickness. 4
status
Percent to 97, 110,211, 212, or 215,
Difference/2
Percent 97, 110,211, 212, or 215, this
Difference/2
Eccentricity
0 to 9.9999 (Linear
eccentricity)
area
4 = Nylon
5 = Urethane
6 = FEP
calibration
650 Layer 2 High Long Hex RO 0 = OK Layer: 1 2 3 4
Speed 1 = Out of tolerance Bit field for high speed tolerance
Tolerance status for up to four layers. 2 bits per
Status layer

Tolerance cell 374.
Undersize
Count
Tolerance cell 374.
Oversize Count
Tolerance Mode.
Nominal Wall
compensation.
compensation.

compensation.
compensation.
compensation.
compensation.
compensation.
compensation.
1 for sector or
transducer
based
calibration
2 for sector or
transducer
based
calibration
3 for sector or
transducer
based
calibration
4 for sector or
transducer
based
calibration
5 for sector or
transducer
based
calibration
6 for sector or
transducer
based
calibration
7 for sector or
transducer
based
calibration
8 for sector or
transducer
based
calibration
#.1234
(imperial)
tolerance
tolerance
tolerance
tolerance
tolerance
lower tolerance
upper tolerance
tolerance







packet(s) {P14}.
737 Layer 3 Long Hex RO 0=OK,1=out of Layer 3 Wall: 1 2 3 4 5 6 7 8
individual wall tolerance Bit field for up to 8 wall thickness. 4
1-8 tol. status bits per wall
Percent to 97, 110,211, 212, or 215,
Difference/2
Percent 97, 110,211, 212, or 215, this
Difference/2
Eccentricity
0 to 9.9999 (Linear
eccentricity)
cross sectional included in packet(s) {P5}.
area
4 = Nylon
5 = Urethane
6 = FEP
calibration
Status layer

Tolerance cell 374.
Undersize
Count
Tolerance cell 374.
Oversize Count
Tolerance Mode.
Nominal Wall
compensation.
compensation.

compensation.
compensation.
compensation.
compensation.
compensation.
compensation.
1 for sector or
transducer
based
calibration
2 for sector or
transducer
based
calibration
3 for sector or
transducer
based
calibration
4 for sector or
transducer
based
calibration
5 for sector or
transducer
based
calibration
6 for sector or
transducer
based
calibration
7 for sector or
transducer
based
calibration
8 for sector or
transducer
based
calibration
#.1234
(imperial)
tolerance
tolerance
tolerance
tolerance
tolerance
lower tolerance
upper tolerance
tolerance







packet(s) {P15}.
837 Layer 4 Long Hex RO 0 = OK Layer 4 Wall: 1 2 3 4 5 6 7 8
individual wall 1 = Out of tolerance Bit field for up to 8 wall thickness. 4
status
Percent to 97, 110,211, 212, or 215,
Difference/2
Percent 97, 110,211, 212, or 215, this
Difference/2
Eccentricity
0 to 9.9999 (Linear
eccentricity)
area
4 = Nylon
5 = Urethane
6 = FEP
calibration
Status layer

Tolerance cell 374.
Undersize
Count
Tolerance cell 374.
Oversize Count
Tolerance Mode.
Nominal Wall
compensation.
compensation.

compensation.
compensation.
compensation.
compensation.
compensation.
compensation.
1 for sector or
transducer
based
calibration
2 for sector or
transducer
based
calibration
3 for sector or
transducer
based
calibration
4 for sector or
transducer
based
calibration
5 for sector or
transducer
based
calibration
6 for sector or
transducer
based
calibration
7 for sector or
transducer
based
calibration
8 for sector or
transducer
based
calibration
903 Uncompensated Float Meas. Res. RW mm, in This cell represents the raw ID
ID average average without OD/ID
compensation factors applied
904 ID preset Float Meas Res RW mm, in Nominal ID value used for tolerance
checking
905 ID individual Float Meas Res RW mm, in Tolerance check for individual axis
reject lower ID measurement
tolerance
warning lower ID measurement
tolerance
warning upper ID measurement
tolerance
reject upper ID measurement
tolerance
909 ID average Float Meas Res RW mm, in Tolerance check for average ID
tolerance
tolerance
tolerance
tolerance
913 ID individual 1 Float Meas Res RO mm, in Single axis ID measurement for a
transducer pair
transducer pair
transducer pair
transducer pair
921 ID min Float Meas Res RO mm, in Minimum value of all individual ID
measurements
922 ID min angle Float #.123 RO -Pi to Pi radians Angle from transducer 1 in the
923 ID max Float Meas Res RO mm, in Maximum value of all individual ID
measurements
924 ID max angle Float #.123 RO -Pi to Pi radians Angle from transducer 1 in the
925 ID average Float Meas Res RO mm, in Average value of all individual ID
measurements.
{P76}.
926 ID individual Long Hex RO 0 = OK ID Axis: 1 2 3 4
tolerance status 1 = Out of tolerance Bit field for up to 4 inner diameter
values. 4 bits per diameter
Under reject tolerance. Bits: 0 4 8 12
Under warning tolerance. Bits: 1 5 9 13
Over warning tolerance. Bits: 2 6 10 14
Over reject tolerance. Bits: 3 7 11 15
927 ID individual Long Hex RO 0 = OK Left: ID min/max. Right ID average: Mn/ Avg
and average 1 = Out of tolerance Bit field for up to 4 outer diameter mx
tolerance status values. 4 bits per diameter. min/max
tolerance checking is based on min
for under and max for over.
Under reject tolerance. Bits: 0 4
Under warning tolerance. Bits: 1 5
Over warning tolerance. Bits: 2 6
Over reject tolerance. Bits: 3 7
950 ID Ovality upper Float Meas Res RW mm,in
reject limit
951 ID Ovality upper Float Meas Res RW mm,in
warning limit
952 ID Ovality Float Meas Res RO mm,in The value of this data base cell is
included in packet {P76}.
953 ID Ovality Long Hex RO 0 = OK
tolerance status 1 = Out of tolerance
980 Target number Long RW 1 to 100000 Specifies how many waveform sets
of waveform to capture in the waveform buffer. A
sets waveform set is one waveform of
each type selected by cell {981}. If
set to one, a single waveform is
captured. If this is set to two or more,
consecutive waveforms are
captured. See Appendix A for details
concerning waveform capture.
981 Waveform Long Hex RW 0 = Dont collect Transducer: 1 2 3 4 5 6 7 8
selection waveform Bit field for all 8 transducers. 4 bits
1 = Collect per sensor 1 bit for each waveform
waveform type. See Appendix A for details
concerning waveform capture.
Raw. Bits 0 4 8 12 16 20 24 28
Filtered. Bits 1 5 9 13 17 21 25 29
Processed. Bits 2 6 10 14 18 22 26 30
(Spare). Bits 3 7 11 15 19 23 27 31
982 Target number Long RW 0 to 8192 This is the target number of data
of waveform points that the UltraScan DSP will
data points return. It is possible that the actual
number of data points returned could
be different. Setting this value to zero
will return all data points. See
Appendix A for details concerning
waveform capture.
983 Clear waveform Long RW Note: Only write executes the
data command.
Clears all waveform data from the
capture buffer. Sets cells {985} and
{986} to 0. See Appendix A for
details concerning waveform
capture.
984 Next transducer Long RW Select next waveform to output. See
waveform data Appendix A for details concerning
waveform capture.
985 Waveform data Long RW Select waveform packet number to

packet to be be output. See Appendix A for
returned by details concerning waveform
{P29} capture.
986 Waveforms in Long RO Indicates the number of waveform
buffer stored in the waveform buffer. See
Appendix A for details concerning
waveform capture.
987 Waveform Enum RW 0 = Normal Waveform capture mode indicates

capture mode 1 = Continuous the condition that must be satisfied in
2 = Stop order to capture a waveform. See
3 = Trigger on bad Appendix A for details concerning
ping (Signal-to- waveform capture.
noise, wrong
number of peaks)
1000 Echo 1 relative Long RW -100 to 100 % Default = -20%
amplitude Typically set to values between -10
and -60%.
Sets echo #1 amplitude relative to
the amplitude of the second echo
(negative value indicates polarity
inversion).
This configuration is used when the
system is operating in the thin wall
tube waveform processing mode.
Used to optimize the echo #1
waveform fit when measuring thin
wall tubes.
See Appendix F Waveform
Processing for more information.
2101 Transducer to Float RW In, mm Calibrated distance between
Transducer transducers for measuring OD axis
distance for axis 1. See Appendix D for details
1 concerning OD calibration.

2105 Gauge Float #.123456 RW 1/C, 1/F Linear coefficient of expansion for
expansion gauge.
coefficient Aluminum = 23 x 10-6 1/C
12.77778 x 10-6
1/F
Stainless Steel = 13 x 10-6 1/C
7.22222 x 10-6 1/F
Delrin = 122.4 x 10-6 1/C
68 x 10-6 1/F.
See Appendix D for details
concerning OD calibration.
2106 OD calibration Float RW C, F Gauge temperature during OD
temperature calibration. Used to calculate gauge
expansion when water temperature
changes. See Appendix D for details
concerning OD calibration.
3342 Extended Float Meas Res RO mm, in Position vector for layer 1 (X plane) =
Average X center of the layer 1 referenced from
Position Layer 1 the center of the OD. Positive X
3343 Extended Float Meas Res RO mm, in Position vector for layer 1 (Y plane) =
Average Y center of the layer 1 referenced from
Position Layer 1 the center of the OD. Positive Y
plane is towards transducer 1.
3510 Extended Float Meas Res RO mm, in The wall thickness measured at
Average Layer transducer #1.
1 wall thickness The value of this data base cell is
1 included in packet {P67}.
3532 Extended Float Meas Res RO mm, in The minimum value of all the
Average Layer measured wall thicknesses. The
1 min wall value of this data base cell is
included in packet {P67 }.
3533 Extended Float #.123 RO -Pi to Pi radians Angle from transducer 1 in the
Average Layer direction of transducer 2. The value
1 predicted min of this data base cell is included in
wall angle packet {P67}.
3534 Extended Float Meas Res RO mm, in The maximum value of all the
Average Layer measured wall thicknesses. The
1 max wall value of this data base cell is
included in packet {P67 }.
3535 Extended Float #.123 RO -Pi to Pi radians Angle from transducer 1 in the
Average Layer direction of transducer 2. The value
1 predicted max of this data base cell is included in
wall angle packet {P67 }.
3536 Extended Float Meas Res RO mm, in The average wall thickness value for
Average Layer all transducers configured. The
1 average wall value of this data base cell is
3543 Extended Float #. (%), Meas RO 0 to 100 (% %, mm, in The value of this data base cell is
Average Layer Res (Linear) Concentricity, % included in packet {P67}.
1 concentricity Eccentricity
0 to 9.9999 (Linear
eccentricity)
4096 Micro Software Long RO Software version for the
Version number microcontroller represented as a
number. 1=A, 2=B,
4098 DSP Software Long RO Software version for the DSP
Version number represented as a number. 1=A, 2=B,

4100 FPGA Firmware Long RO Firmware version for the FPGA.
Version number
4101 Analog card Long RO Analog card hardware revision
hardware
version
4102 Processor card Long RO Processor card hardware revision
hardware
version
Database Packet Commands

The packet commands allow the user to retrieve a set of common data with a single command. Packet commands
are only available via the serial interface.
DB Parameter R/W Description
P0 Cross section OD, ID, RO *S1/P0I=hhhh,4.0000,3.0000,0.1234,3.141,1.1111,2.2222,0.1234,3.141,1.1111,2.2222,0.1234,3

average wall, min wall .141,1.1111,2.2222,0.1234,3.141,1.1111,2.2222cc
angle, inner circle position where: I imperial (M for metric)
hhhh transducer status in hex, {309}

4.0000 OD, {425}
3.0000 ID, {925}
0.1234 average wall (one for each layer), {536}, {636}, {736}, {836}
3.141 min wall angle, radians (one for each layer), {533}, {633}, {733}, {833}
1.1111 x position (one for each layer), {342}, {344}, {346}, {348}
2.2222 y position (one for each layer), {343}, {345}, {347}, {349}
ETB
cc check sum
carriage return
P1 Cross section Layer 1 RO *S1/P1I=hhhh,0.1234,0.1234,0.1234,0.1234,0.1234,0.1234,0.1234,0.1234cc
Individual walls where: I imperial (M for metric)

0.1234 individual wall measurements (one for each transducer), {510}, {511}, {512}, {513}, {514}, {515}, {516},
{517}
ETB
cc check sum
carriage return

{617}
ETB
cc check sum
carriage return


{717}
ETB
cc check sum
carriage return

{817}
ETB
cc check sum
carriage return
P5 Cross section ovality, min RO *S1/P5I=hhhh,0.0000,0.1234,5.6789e-12,100,0.1234,5.6789e-12,100,0.1234,5.6789e-12,10
wall, cross sectional area, 0,0.1234,5.6789e-12,100cc
concentricity
where: I imperial (M for metric)

0.0000 ovality, {452}
0.1234 min wall (one for each layer), {532}, {632}, {732}, {832}
5.6789e-12 cross sectional areas (one for each layer), {546}, {646}, {746}, {846}
100 concentricity (one for each layer), {543}, {643}, {743}, {843}
ETB
cc check sum
carriage return
P6 Gauge part position RO *S1/P6I=1.1111,2.2222cc
1.1111 x position, {340}

2.2222 y position, {341}
ETB
cc check sum
carriage return
P7 Gauge signal-to-noise, RO *S1/P7I=100,100,100,100,100,100,100,100,100,100,100,100,100,100,100,100cc

percent good scans where: I imperial (M for metric)
100 signal-to-noise (first) and percent good scans (second). (one for each transducer), {290}, {300}, {291},
{301}, {292}, {302}, {293}, {303}, {294}, {304}, {295}, {305}, {296}, {306}, {297}, {307}
ETB
cc check sum
carriage return
P8 Gauge gain RO *S1/P8I=100,100,100,100,100,100,100,100cc
100 gain (one for each transducer), {221}, {222}, {223}, {224}, {225}, {226}, {227}, {228}
ETB
cc check sum
carriage return
P9 Gauge gap RO *S1/P9I=1.234500,1.234500,1.234500,1.234500,1.234500,1.234500,1.234500,1.234500cc
1.234500 gap (one for each transducer), {330}, {331}, {332}, {333}, {334}, {335}, {336}, {337}
ETB
cc check sum
carriage return
P10 Cross section and RO *S1/P10I=hhhh,4.000000,0.000000,3.000000cc
UltraView/UltraComponents where: I imperial (M for metric)
OD, Ovality, ID
4.000000 OD, {425}
0.000000 ovality, {452}
3.000000 ID, {925}
ETB
cc check sum
carriage return
P11 UltraView/UltraComponents RO *S1/P11I=5.5,1.1111,2.2222cc
Position where: I imperial (M for metric)
5.5 Gauge size, {149}

1.1111 x position, {340}
2.2222 y position, {341}
ETB
cc check sum
carriage return
P12 Cross section Layer 1 RO *S1/P12I=hhhh,1.111111,2.222222,5.6789e-12,100,100,0.123400,0.123300,0.123200,3.140,

0.123500,0.123600,-0.002,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123
900,0.123900cc

1.111111 x position, {342}
2.222222 y position, {343}
5.6789e-12 cross sectional area, {546}
100 concentricity, {543}
100 predicted concentricity, {TBD}
0.123400 average wall, {536}
0.123300 min wall, {532}
0.123200 predicted min wall, {TBD}
3.140 predicted min wall angle, radians, {533}
0.123500 max wall, {534}
0.123600 predicted max wall, {TBD}
-0.002 predicted max wall angle, radians, {535}
0.123900 individual wall measurements (one for each transducer), {510}, {511}, {512}, {513}, {514}, {515},
{516}, {517}
ETB
cc check sum
carriage return

0.123500,0.123600,-0.002,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123
900,0.123900cc

1.111111 x position, {344}
2.222222 y position, {345}
0.123400 average wall, {636}
0.123300 min wall, {632}
0.123500 max wall, {634}
{617}
ETB
cc check sum
carriage return

0.123500,0.123600,-0.002,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123
900,0.123900cc

1.111111 x position, {346}
2.222222 y position, {347}
0.123400 average wall, {736}
0.123300 min wall, {732}
0.123500 max wall, {734}
{717}
ETB
cc check sum
carriage return

0.123500,0.123600,-0.002,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123
900,0.123900cc

1.111111 x position, {348}
2.222222 y position, {349}
0.123400 average wall, {836}
0.123300 min wall, {832}
0.123500 max wall, {834}
{816}, {817}
ETB
cc check sum
carriage return
P16 High Speed Tolerance RO *S1/P16I=9999,hhhhhhhh,hhhhhhhh,1234,1.111111,2.222222,123,123,3.333333,4.444444cc
Error Termination Packet where: I imperial (M for metric)
Layer 1
9999 packet count (increments each time packet is sent out)
hhhhhhhh transducer status indicating which transducers detected the error(s) described in this packet
hhhhhhhh reserved
1234 number of errors described in this packet
1.111111 max size of all oversize errors described in this packet
2.222222 min size of all undersize errors described in this packet
123 number of oversize errors described in this packet
123 number of undersize errors described in this packet
3.333333 length of product between start of first error and end of last error described in this packet
ETB
cc check sum
carriage return

Layer 2
hhhhhhhh reserved
ETB
cc check sum
carriage return
Layer 3
hhhhhhhh reserved
ETB
cc check sum
carriage return

Layer 4
hhhhhhhh reserved
ETB
cc check sum
carriage return
P20 Waveform header 1 Time RO *S1/P20I=2222,3333,1,hhhhhhh1,hhhhhhh2,hhhhhhh3,hhhhhhh4,hhhhhhh5,hhhhhhh6,hhhhhhh7,hhhhh
Stamp, Sampling Window, hh8cc
Echoes where: I imperial (M for metric)
2222 = ping count. (11 characters max) {153}

3333 = time stamp (11 characters max)
1 = transducer number. (2 characters)
hhhhhhh1,hhhhhhh2,hhhhhhh3 = sampling window. Samples from ping to sampling window start, sampling
window duration (in samples) and number of samples from one data point to the next. (27 characters max)
hhhhhhh4,hhhhhhh5,hhhhhhh6,hhhhhhh7,hhhhhhh8 = wall echo sample. Samples from ping to echo used for
the wall measurements. Used on processed waveform. (up to 5 echoes, 44 characters max)
ETB
cc check sum
carriage return
(Up to 108 characters.)
P21 Waveform header 2 Echo RO *S1/P21I=2222,hhhhhhh1,hhhhhhh2,hhhhhhh3,hhhhhhh4,hhhhhhh5,hhhhhhh6,hhhhhhh7,hhhhhhh8cc
Candidates where: I imperial (M for metric)

hhhhhhh1,hhhhhhh2, = candidate echo sample. Samples from ping to each echo candidate. Used on
processed waveform. (8 candidates, 71 characters max)
ETB
cc check sum
carriage return
P22 Waveform header 3 Gain RO *S1/P22I=2222,5555,hhhhhhhh,6666,...cc


5555,hhhhhhhh,6666, = gain data. Initial gain, relative sample where gain 1 is applied, gain 1, etc. Used on
raw, and filtered waveforms. (3 time varying gains, 46 characters max)
ETB
cc check sum
carriage return
P23 Waveform header 4 RO *S1/P23I=2222,hhhhhhhh,hhhhhhhh,...cc
Ignore Regions where: I imperial (M for metric)

hhhhhhhh,hhhhhhhh, = ignore regions. Relative sample of start of the ignore region, ignore duration (in
number of samples), etc. Used on processed waveform. (4 ignore regions, 71 characters max)
ETB
cc check sum
carriage return
P24 Waveform header 5 RO *S1/P24I=2222,777,0.1234,0.5678,...cc
Measurement Data where: I imperial (M for metric)

777,0.1234,0.5678, = measurement data. Signal-to-noise ratio, gap, layer 1, etc. (38 characters max)
ETB
cc check sum
carriage return
P28 Run length encoded RO *S1/P29I=2222,0,0,hhhh...cc
waveform data where: I imperial (M for metric)

0 = waveform type. Raw (0), filter (1), or processed (2).
0 = packet count.
hhhh = Run length encoded waveform data. Raw and Filtered waveforms are signed. Transformed is
unsigned.
ETB
cc check sum
carriage return
NOTE: Reading the waveform data will cause the waveform packet number {985} to automatically increment.
P29 Waveform data RO *S1/P29I=2222,0,0,hhhh...cc


0 = waveform type. Raw (0), filter (1), or processed (2).
0 = packet count.
hhhh = data point (in hex). Two characters per sample, no comma delimiter between samples. Raw and
Filtered waveforms are signed. Transformed is unsigned.
ETB
cc check sum
carriage return
NOTE: Reading the waveform data will cause the waveform packet number {985} to automatically increment.
P60 Sector Wall Calibration RO *S1/P60I=0.0000,0.0875,1.0000,1.0000,1.0000,1.0000,1.0000,1.0000,1.0000,1.0000cc
Compensation Factors - 0.0000 = Transducer angle during calibration {311}
Layer 1 0.0875 = Average speed of sound {500}
1.0000 = Wall thickness calibration compensation factors {560},{561},{562},{563},{564},{565},{566},{567}
ETB
cc check sum
carriage return

ETB
cc check sum
carriage return

ETB
cc check sum
carriage return

ETB
cc check sum
carriage return
P66 Cross section Layer 1 RO *S1/P66I=hhhh,1.111111,2.222222,100,0.123400,0.123300,3.140,0.123500,-0.002,

0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900cc

1.111111 x position, {342}
2.222222 y position, {343}
0.123400 average wall, {536}
0.123300 min wall, {532}
3.140 min wall angle, radians, {533}
0.123500 max wall, {534}
-0.002 max wall angle, radians, {535}
{516}, {517}
ETB
cc check sum
carriage return
P67 Extended Average Cross RO *S1/P67I=hhhh,1.111111,2.222222,100,0.123400,0.123300,3.140,0.123500,-0.002,

section Layer 1 0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900cc

1.111111 x position, {3342}
2.222222 y position, {3343}
0.123400 average wall, {3536}
0.123300 min wall, {3532}
0.123500 max wall, {3534}
0.123900 individual wall measurements (one for each transducer), {3510}, {3511}, {3512}, {3513}, {3514},
{3515}, {3516}, {3517}
ETB
cc check sum
carriage return
0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900cc

1.111111 x position, {344}
2.222222 y position, {345}
0.123400 average wall, {636}
0.123300 min wall, {632}
0.123500 max wall, {634}
{616}, {617}
ETB
cc check sum
carriage return

section Layer 2 0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900cc

1.111111 x position, {3344}
2.222222 y position, {3345}
0.123400 average wall, {3636}
0.123300 min wall, {3632}
0.123500 max wall, {3634}
{3615}, {3616}, {3617}
ETB
cc check sum
carriage return
0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900cc

1.111111 x position, {346}
2.222222 y position, {347}
0.123400 average wall, {736}
0.123300 min wall, {732}
0.123500 max wall, {734}
{716}, {717}
ETB
cc check sum
carriage return

section Layer 3 0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900cc

1.111111 x position, {3346}
2.222222 y position, {3347}
0.123400 average wall, {3736}
0.123300 min wall, {3732}
0.123500 max wall, {3734}
{3715}, {3716}, {3717}
ETB
cc check sum
carriage return
0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900cc

1.111111 x position, {348}
2.222222 y position, {349}
0.123400 average wall, {836}
0.123300 min wall, {832}
0.123500 max wall, {834}
{816}, {817}
ETB
cc check sum
carriage return

section Layer 4 0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900,0.123900cc

1.111111 x position, {3348}
2.222222 y position, {3349}
0.123400 average wall, {3836}
0.123300 min wall, {3832}
0.123500 max wall, {3834}
{3815}, {3816}, {3817}
ETB
cc check sum
carriage return
Servicing and Returning Your Equipment

Your instrument was carefully inspected electrically and
mechanically prior to shipment. It should be free of surface mars
and scratches, and it should be in perfect working order upon
receipt. If any indication of damage is found, file a claim with the
carrier immediately, prior to using the instrument. If no damage is
apparent, proceed by using this manual to install and setup this
instrument.
Save the shipping carton and packing material for future storing or
shipment of the instrument. If, at some future time, the instrument
must be returned to the factory for service, include a full description
of the instrument failure and the mode of operation the instrument
was in at the time of failure. Also include a contact person to
discuss the instrument failure.
When returning equipment for service, it is important to first obtain a
Return Material Authorization (RMA) number. The RMA number is
needed for proper handling of returned equipment.
To obtain an RMA, go to www.betalasermike.com
Select Service
Select Equipment Return / RMA from the drop-down menu.
Follow the instructions to obtain an RMA.
Ship the instrument in the original carton, or, if the original carton is
unavailable, ship in a carton providing sufficient protection. Send the
instrument to the Asia, Europe, or USA office (addresses listed in
the supplied Contacts/CE Compliance Manual), whichever is closest
to you or to the office indicated by your sales engineer. Place the
RMA number on the outside of the carton, and include a purchase
order number and any other information specific to your instrument.
Field warranty service is available, if the customer pays travel
expenses by advance purchase order. All service operations should
be performed by skilled electronics technicians, who have been
trained by Beta LaserMike.
Part No. 92005 / Drawing No. 0921-00248 Page 211 of 212 Revision G (Apr 2009)
Index
Adaptive Sector-Based Wall Calibration............. 93 DeviceNet Object ................................................19
Appendix A.......................................................... 83 DeviceNet Objects ..............................................17
Appendix B.......................................................... 87 External Database Synchronization....................15
Appendix C ......................................................... 88 FieldBus I/O Data................................................72
Appendix D ......................................................... 90 Fixed Sector-Based Wall Calibration ..................91
Appendix E.......................................................... 97 Gauge Calibration ...............................................90
Appendix F ........................................................ 106 High Speed Tolerance Checking ........................97
Appendix H ....................................................... 113 Identity Object .....................................................18
Appendix I ......................................................... 127 Initial Energy Mode (Default) ............................107
Assembly Object ................................................. 20 Introduction ...........................................................5
Average Wall Calibration .................................... 90 OD Calibration ....................................................95
Baud rate .............................................................. 7 OD Offset Calibration ..........................................96
CAN / DeviceNet / CANopen Baud Rate ............ 31 Power Tool ........................................................114
CAN / DeviceNet / CANopen Bus Off Interrupt PROFIBUS GSD File ..........................................88
Action .................................................................. 31 Profibus Interface ................................................64
CANopen Data Dictionary Objects ..................... 33 Profibus PKW Header .........................................64
CANopen Interface ............................................. 30 Serial Interface ......................................................7
Center of Energy Mode..................................... 106 Standard Database Fields ................................127
Checksum ............................................................. 7 Thin-Wall Tube Mode .......................................108
Compressed Waveform Data ............................. 83 Total Wall Mode ................................................109
Connection Object .............................................. 22 Troubleshooting ....................................... 105, 119
Database Data Types ........................................... 8 UltraOPC Server ...............................................113
Database Layout ............................................... 127 UltraScan Database Object ................................23
Database Packet Commands ........................... 195 Uncompressed Waveform Data..........................83
Database Packets............................................... 14 Waveform Collection Modes ...............................84
DeviceNet EDS File ............................................ 87 Waveform Collection Sequence .........................85
DeviceNet I/O Data ............................................. 29 Waveform Information ........................................83
DeviceNet Interface ............................................ 17 Waveform Packets ..............................................14
DeviceNet MACID / CANopen Node ID.............. 30 Waveform Processing Modes ...........................106
Part No. 92005 / Drawing No. 0921-00248 Page 212 of 212 Revision G (Apr 2009)

UltraScan DSP English Integration RevG

Uploaded by

Copyright:

Available Formats

You might also like

UltraScan DSP English Integration RevG

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

UltraScan DSP English Integration RevG

Uploaded by

Copyright:

Available Formats

ULTRASCAN DSP

- for suitably qualified personnel only -

Appendix C: PROFIBUS GSD File ................................................................................................ 88

Beta LaserMike, 8001 Technology Blvd., Dayton, OH 45424, USA

About This Manual

UltraScan DSP Revision

Arial will be the normal font used.

Metric vs. Imperial Units

Database Data Types

<command character>S1/<database ID>[=value][checksum]

Where an M or I indicates imperial or metric units, respectively when

Set Value (=)

Get Value (?)

Where 103 indicates the database ID, I indicates imperial units, 20

Open Hot Link (!)

Open Timed Hot Link (!T)

Close Hot Link ())

Where 309 is the database ID.

Suspend Hot Link (~)

Where 309 is the database ID.

Resume Hot Link (+)

Where 309 is the database ID.

Identify Serial Port

A reply from this command will look like this:

Configure Output Broadcasting

The Configure Output Broadcasting command allows a host system to enable

The reply from this command will look like this:

The reply from this command will look like this:

External Database Synchronization

Note that an incomplete command may be ignored by the UltraScan DSP

Error Code Error Description

14 Data name not available only device S supported

15 Read-only database cell

17 Device number out of range only device 1 supported

18 Database cell number out of range database cell/packet not defined

19 Command not implemented

Identity Object (DeviceNet Class = 1)

VENDOR_ID The vendor ID.

16-bit UINT This is the fixed value 732: Beta LaserMike

PRODUCT_CODE The vendor specific product code.

DeviceNet Object (DeviceNet Class = 3)

Assembly Object (DeviceNet Class = 4)

The output data is consumed by the gauge. It is produced by the DeviceNet

Connection Assembly Object Consumed Connection Path

Bit-Strobe I/O 2 0x20,0x04,0x24,0x02,0x30,0x03

The consumed connection path attribute describes the connection as

Input data is produced by the gauge. It is supplied to the DeviceNet master

Connection Assembly Object Consumed Connection Path

Bit-Strobe I/O 2 0x20,0x04,0x24,0x02,0x30,0x03

The produced connection path attribute describes the connection as

Connection Object (DeviceNet Class = 5)

UltraScan Database Object (DeviceNet Class = 102)

UltraScan DSP Database Instances

It is possible to use metric or imperial units when setting or retrieving

UltraScan DSP Database Services

Enumeration Service (service code 64/0x40)

This service allows the internal UltraScan DSP database to be enumerated.

UChar The maximum number of database items to enumerate

UShort The starting enumeration index