Manual Gocator 2100 2300 2400 2800 Series PDF
Manual Gocator 2100 2300 2400 2800 Series PDF
USER MANUAL
Gocator 2100, 2300, 2400, 2500 Series; Gocator 2880
Firmware version: 5.3.x.xx
Document revision: B
Copyright
Copyright © 2019 by LMI Technologies, Inc. All rights reserved.
Proprietary
This document, submitted in confidence, contains proprietary information which shall not be
reproduced or transferred to other documents or disclosed to others or used for manufacturing or any
other purpose without prior written permission of LMI Technologies Inc.
This product is designated for use solely as a component and as such it does not comply with the
standards relating to laser products specified in U.S. FDA CFR Title 21 Part 1040.
Contact Information
LMI Technologies, Inc.
9200 Glenlyon Parkway
Burnaby BC V5J 5J8
Canada
Telephone: +1 604-636-1011
Fax: +1 604-516-8368
www.lmi3D.com
Connection Settings 780 Using the Mountains Map Transfer Tool 811
This documentation describes how to connect, configure, and use a Gocator. It also contains reference
information on the device's protocols and job files, as well as an overview of the development kits you
can use with Gocator. Finally, the documentation describes the Gocator emulator and accelerator
applications.
B series Gocator sensors are only supported by firmware version 4.3 or later.
C revision Gocator sensors are only supported by firmware version 4.5 SR1 or later. These
sensors are compatible with SDK applications built with version 4.x of the SDK. The sensors are
also compatible with jobs created on sensors running firmware 4.x.
Notational Conventions
This documentation uses the following notational conventions:
The following sections describe the safe use and maintenance of Gocator sensors.
Laser Safety
Gocator sensors contain semiconductor lasers that emit visible or invisible light and are designated as
Class 2, 2M, Class 3R, or Class 3B, depending on the laser option. For more information on the laser
classes used in these sensors, Laser Classes on the next page.
Gocator sensors are referred to as components, indicating that they are sold only to qualified customers
for incorporation into their own equipment. These sensors do not incorporate safety items that the
customer may be required to provide in their own equipment (e.g., remote interlocks, key control; refer
to the references below for detailed information). As such, these sensors do not fully comply with the
standards relating to laser products specified in IEC 60825-1 and FDA CFR Title 21 Part 1040.
Use of controls or adjustments or performance of procedures other than those specified herein
may result in hazardous radiation exposure.
References
1. International standard IEC 60825-1 (2001-08) consolidated edition, Safety of laser products – Part 1:
Equipment classification, requirements and user's guide.
2. Technical report 60825-10, Safety of laser products – Part 10. Application guidelines and explanatory
notes to IEC 60825-1.
3. Laser Notice No. 50, FDA and CDRH (https://www.fda.gov/Radiation-Emit-
tingProducts/ElectronicProductRadiationControlProgram/default.htm)
l The user’s blink reflex can terminate exposure (in under 0.25 seconds).
l Diffuse reflections are safe if viewed for less than 10 seconds at a minimum distance of 13 cm.
l Use a clearly visible indicator to show that a laser is in use, such as “Laser in operation.”
For more information, see Precautions and Responsibilities on the next page.
*LMI Class 3B laser components do not incorporate these laser safety items. These items must be added and completed by customers
in their system design. For more information, see Class 3B Responsibilities below.
Class 3B Responsibilities
LMI Technologies has filed reports with the FDA to assist customers in achieving certification of laser
products. These reports can be referenced by an accession number, provided upon request. Detailed
descriptions of the safety items that must be added to the system design are listed below.
Remote Interlock
A remote interlock connection must be present in Class 3B laser systems. This permits remote switches
to be attached in serial with the keylock switch on the controls. The deactivation of any remote switches
must prevent power from being supplied to any lasers.
Key Control
A key operated master control to the lasers is required that prevents any power from being supplied to
the lasers while in the OFF position. The key can be removed in the OFF position but the switch must not
allow the key to be removed from the lock while in the ON position.
Beam Attenuators
A permanently attached method of preventing human access to laser radiation other than switches,
power connectors or key control must be employed.
Emission Indicator
It is required that the controls that operate the sensors incorporate a visible or audible indicator when
power is applied and the lasers are operating. If the distance between the sensor and controls is more
than 2 meters, or mounting of sensors intervenes with observation of these indicators, then a second
power-on indicator should be mounted at some readily-observable position. When mounting the
warning indicators, it is important not to mount them in a location that would require human exposure
to the laser emissions. User must ensure that the emission indicator, if supplied by OEM, is visible when
viewed through protective eyewear.
Warning Signs
Laser warning signs must be located in the vicinity of the sensor such that they will be readily observed.
The laser beam is considered dangerous if the operator is closer to the source than the NOHD.
The following tables provide the NOHD values for each sensor model and laser class, assuming
continuous operation of the laser. As a configurable device, a sensor lets you set the laser exposure
(laser on-time) independently of the frame period (total cycle time for data acquisition). Continuous
operation of the laser means that the laser exposure is configured to be identical to the frame period,
which is also referred to as 100% duty cycle. However, in many applications the laser exposure can be
smaller than the frame period (less than 100% duty cycle), thereby reducing the NOHD. The tables
therefore show the worst-case NOHD.
2440A
3R 660 3340 1330
21x0D/23x0D (except 2x80D)
a With exposure time < 10 seconds. For longer exposure times, consult IEC 60825.
The following table provides NOHD values for older hardware version sensors.
2130A to C, 2330A to C
3R 660 900 358
2140A to C, 2340A to C
2150A to C, 2350A to C 3B 660 5759 2292
Customers are advised to obtain the information booklet Regulations for the Administration and
Enforcement of the Radiation Control for Health and Safety Act of 1968: HHS Publication FDA 88-8035.
Electrical Safety
Failure to follow the guidelines described in this section may result in electrical shock or
equipment damage.
For a description of the connector pins, see Gocator I/O Connector on page 897.
Heat Warning
If a sensor is not adequately heat-sunk, the housing may get hot enough to cause injury.
The Master network controllers are similarly rated for operation between 0–50° C.
The sensor must be heat-sunk through the frame it is mounted to. When a sensor is properly heat
sunk, the difference between ambient temperature and the temperature reported in the sensor's
health channel is less than 15° C.
Sensors are high-accuracy devices, and the temperature of all of its components must therefore
be in equilibrium. When the sensor is powered up, a warm-up time of at least one hour is required
to reach a consistent spread of temperature in the sensor.
The following sections provide system and hardware overviews, in addition to installation and setup
procedures.
2000 X
2100 & 2300 C X X X
2100 & 2300 D X X X X
2400 A X X X X
1. More powerful sensor controller, allowing Gocator-based solutions to run faster than before, at a
lower overall temperature.
2. Twice the sensitivity of previous generations and effectively lower laser classifications (from 3B to 3R
in some cases, and from 3R to 2 in many cases). This lets you scan darker targets at higher speeds
without the safety considerations of class 3B lasers.
3. The A and B versions of Gocator 2100 and 2300 sensors can run the latest versions of firmware, but
they do not support the new tools and PROFINET output protocol available in these versions. You
can however use these features if you accelerate the sensors using GoMax or the PC-based Gocator
accelerator. For more information on the accelerator, see Gocator Acceleration on page 527.
4. You can however use these tools if you accelerate the sensors using GoMax or the PC-based Gocator
accelerator. For more information on the accelerator, see Gocator Acceleration on page 527. For a
complete list of tools not available on non-accelerated A revision sensors, see below.
The following tools are not available on non-accelerated revision A G2 sensors:
Surface Extend
Gocator Sensor
Item Description
Gocator Cordsets
Gocator sensors use two types of cordsets: the Power & Ethernet cordset and the I/O cordset.
The Power & Ethernet cordset provides power, laser safety interlock to the sensor. It is also used for
sensor communication via 1000 Mbit/s Ethernet with a standard RJ45 connector. The Master version of
the Power & Ethernet cordset provides direct connection between the sensor and a Master network
controller, excluding Master 100 (for more information, see Master Network Controllers on page 903).
See Gocator I/O Connector on page 897 and Gocator Power/LAN Connector on page 895 for pinout
details.
See Accessories on page 921 for cordset lengths and part numbers. Contact LMI for information on
creating cordsets with customized lengths and connector orientations.
Master 100
The Master 100 is used by sensors for standalone system setup (that is, a single sensor).
Item Description
Master Ethernet Port Connects to the RJ45 connector labeled Ethernet on the Power/LAN to Master cordset.
Master Power Port Connects to the RJ45 connector labeled Power/Sync on the Power/LAN to Master
cordset. Provides power and laser safety to the sensor.
Sensor I/O Port Connects to the I/O cordset.
Master Host Port Connects to the host PC's Ethernet port.
Power Accepts power (+48 V).
Power Switch Toggles sensor power.
Safety Switch Toggles safety signal provided to the sensors [O= off, I= on]. This switch must be set to
on in order to scan with laser-based sensors.
Trigger Signals a digital input trigger to the sensor.
Encoder Accepts encoder A, B and Z signals.
Digital Output Provides digital output.
Item Description
Sensor Ports Master connection for sensors (no specific order required).
Ground Connection Earth ground connection point.
Power and Safety Power and safety connections. Safety input must be high in order to scan with laser-
based sensors.
Encoder Accepts encoder signal.
Input Accepts digital input.
For pinout details for Master 400 or 800, see Master 400/800 on page 905.
For pinout details for Master 1200 or 2400, see Master 1200/2400 on page 918.
Master 2410
Item Description
Sensor Ports Master connection for sensors (no specific order required).
Power and Safety Power and safety connections. Safety input must be high in order to scan with laser-
based sensors.
Encoder Accepts encoder signal.
Input Accepts digital input.
DIP Switches Configures the Master (for example, allowing the device to work with faster encoders).
For information on configuring Master 810 and 2410 using the DIP switches, see
Configuring Master 810 on page 44.
Disks are typically used with systems containing a single sensor and can be ordered from LMI
Technologies. When choosing a disk for your application, select the largest disk that fits entirely within
the required field of view. See Accessories on page 921 for disk part numbers.
For dual- and multi-sensor systems, where sensor laser planes are roughly coplanar, bars are required to
match the length of the system by following the guidelines illustrated below. (LMI Technologies does not
manufacture or sell bars.)
For multi-sensor systems in a ring layout, use a polygon-shaped alignment target. The number of corners
in the target should correspond with the number of sensors in the system. Sensors should be positioned
so that each sensor can scan a corner and surrounding surface.
System Overview
Gocator sensors can be installed and used in a variety of scenarios. Sensors can be connected as
standalone devices, dual-sensor systems, or multi-sensor systems.
Standalone System
Standalone systems are typically used when only a single sensor is required. The device can be
connected to a computer's Ethernet port for setup and can also be connected to devices such as
encoders, photocells, or PLCs.
A Master network controller (excluding Master 100) must be used to connect two sensors in a dual-
sensor system. Power and Ethernet to Master cordsets are used to connect sensors to the Master.
Master networking hardware does not support digital, serial, or analog output.
Mounting
Sensors should be mounted using a model-dependent number of screws. Some models also provide the
option to mount using bolts in through-body holes. Refer to the dimension drawings of the sensors in
Specifications on page 847 for the appropriate screw diameter, pitch, and length, and bolt hole diameter.
Proper care should be taken in order to ensure that the internal threads are not damaged from
cross-threading or improper insertion of screws.
Sensors should not be installed near objects that might occlude a camera's view of the projected light.
(Gocator 2880 is an exception, as it is specifically designed to compensate for occlusions.)
Sensors should not be installed near surfaces that might create unanticipated laser reflections.
Gocator sensors are high-accuracy devices. The temperature of all of its components must be
in equilibrium. When the sensor is powered up, a warm-up time of at least one hour is required
to reach a consistent spread of temperature within the sensor.
Orientations
The examples below illustrate the possible mounting orientations for standalone and dual-sensor
systems.
Standalone Orientations
Side-by-side for wide-area measurement (Wide) Main must be on the left side (when
looking into the connector)
of the Buddy (Wide)
In the table below, part numbers do not include the length indicator.
Number of
Outer Number of
Cable Type Cordset Part Numbers Static (mm) Dynamic (mm) Ticks
Diameter Ticks (U-shape)
(90° Tick Tock)
Power and
Ethernet to
30858, 30877,
Master 8.89 45 140 > 2,000,000
Standard 30861, 30880
Power and
Ethernet
Power and
Ethernet to
301165, 301173,
Master 8.5 34 40 > 2,000,000 > 7,000,000
High Flex 301176, 301171
Power and
Ethernet
The following illustrations show the test setups used to determine the number of bends.
Gocator
Gocator sensors should be grounded to the earth/chassis through their housings and through the
grounding shield of the Power I/O cordset. Sensors have been designed to provide adequate grounding
through their mounting screws. Always check grounding with a multi-meter to ensure electrical
continuity between the mounting frame and the sensor's connectors.
The frame or electrical cabinet that the sensor is mounted to must be connected to earth ground.
When using the rack mount brackets, you must connect the frame or electrical cabinet to which
the Master is mounted to earth ground.
You must check electrical continuity between the mounting frame and RJ45 connectors on the
front using a multi-meter.
If you are mounting Master 810 or 2410 using the provided DIN rail mount adapters, you must ground
the Master directly; for more information, see Grounding When Using a DIN Rail (Master 810/2410)
below.
You can use any of the ground holes shown below. However, LMI recommends using the holes
indicated on the housing by a ground symbol.
Older revisions of Master 810 and 2410 network controllers use a different configuration for the DIN rail
clip holes.
2. Locate the DIN rail mounting holes on the back of the Master (see below).
Master 810:
Current revision
Older revision
Master 2410:
Current revision
Older revision
Ensure that there is enough clearance around the Master for cabling.
Master 810 supports up to a maximum incoming encoder quadrature frequency of 6.5 MHz.
This section describes how to set the DIP switches on Master 810 to do the following:
l Set the divider so that the quadrature frequency of the connected encoder is compatible with the
Master.
In the formula, use the quadrature frequency of the encoder (for more information, see Encoder
Quadrature Frequency on the next page) and a divider from the following table so that the Output
Quadrature Frequency is no more than 300 kHz.
2 ON OFF OFF
4 OFF ON OFF
8 ON ON OFF
16 OFF OFF ON
32 ON OFF ON
64 OFF ON ON
128 ON ON ON
The divider works on debounced encoder signals. For more information, see Setting the
Debounce Period below.
You must use a quadrature frequency when determining which divider to use (see Setting the Divider on
the previous page). Consult the datasheet of the encoder you are using to determine its quadrature
frequency.
Some encoders may be specified in terms of encoder signal frequency (or period). In this case,
convert the signal frequency to quadrature frequency by multiplying the signal frequency by 4.
short debounce ON
Layout
The Gocator 2375 sensor is designed to cover a scan width of up to 4.2 m by using 8 sensors mounted
in parallel.
The diagram above shows the clearance distance and measurement range required in a typical setup.
Use the specification estimator (Gocator-2375_Specification_Estimator.xlsx) to calculate the X and Z
resolution of the sensors with different combinations of clearance distance and measurement range.
System Setup
A typical Gocator 2375 system is set up as a multi-sensor system. The sensors are powered using a
Master network controller (excluding Master 100).
1. Connect the Power and Ethernet to Master cordset to the Power/LAN connector on the sensor.
2. Connect the RJ45 jack labeled Power to an unused port on the Master.
3. Connect the RJ45 jack labeled Ethernet to an unused port on the switch.
See Master 400/800 on page 905 and Master 1200/2400 on page 918 for more information on how to
install a Master.
Software Configuration
Each sensor is shipped with a default IP address of 192.168.1.10. Before you add a sensor to a multi-
sensor system, its firmware version must match that of the other sensors, and its IP address must be
unique.
b. Make sure that there is no other sensor in the network with the IP address 192.168.1.10.
APPNOTE_Gocator_4.x_Multi_Sensor_Guide.zip
Explains how to use the SDK to create a multi-sensor system, and multiplex their timing.
Gocator-2000-2300_appnote_multi-sensor-alignment-calibration.zip
Explains how to use the SDK to perform alignment calibration of a multi-sensor system.
You can find the app notes under the How-to category in LMI's online Gocator resources.
DHCP is not recommended for sensors. If you choose to use DHCP, the DHCP server should try
to preserve IP addresses. Ideally, you should use static IP address assignment (by MAC address)
to do this.
Client Setup
To connect to a sensor from a client PC, you must ensure the client's network card is properly
configured.
Setting Default
DHCP Disabled
IP Address 192.168.1.10
Subnet Mask 255.255.255.0
Gateway 0.0.0.0
All sensors are configured to 192.168.1.10 as the default IP address. For a dual-sensor system, the
Main and Buddy sensors must be assigned unique addresses before they can be used on the same
network. Before proceeding, connect the Main and Buddy sensors one at a time (to avoid an
address conflict) and use the steps in See Running a Dual-Sensor System on page 53 to assign each
sensor a unique address.
See Troubleshooting on page 846 if you experience any problems while attempting to establish a
connection to the sensor.
The following describes how to set up a sensor system for operations. After you have completed the
setup, you can perform a scan to verify basic sensor operation.
Master 400/800/1200/2400
Master 810/2410
Master 400/800/1200/2400
Master 810/2410
Ports used
Port Data Packet Protocol Description
3189 TCP Flash security policy server (only in Gocator 4.7 and earlier releases)
For more information on how the different protocols use these ports, see the appropriate section in
Protocols on page 647.
Next Steps
After you complete the steps in this section, the sensor system is ready to be configured for an
application using the software interface. The interface is explained in the following sections:
The following sections provide an overview of how Gocator acquires and produces data, detects and
measures parts, and controls devices such as PLCs. Some of these concepts are important for
understanding how you should mount sensors and configure settings such as active area.
You can use the Accelerator to speed up processing of data. For more information, see Gocator
Acceleration on page 527.
3D Acquisition
After a sensor system has been set up and is running, it is ready to start capturing 3D data.
The sensor's camera views the laser line on the target from an angle and captures the reflection of the
laser light off the target. The camera captures a single 3D profile—a slice, in a sense—for each camera
exposure. The reflected laser light falls on the camera at different positions, depending on the distance
of the target from the sensor. The sensor’s laser emitter, its camera, and the target form a triangle. The
sensor uses the known distance between the laser emitter and the camera, and two known angles—one
of which depends on the position of the laser light on the camera—to calculate the distance from the
sensor to the target. This translates to the height of the target. This method of calculating distance is
called laser triangulation.
Gocator sensors are always pre-calibrated to deliver 3D data in engineering units throughout
their measurement range.
Clearance distance – The minimum distance from the sensor that a target can be scanned and
measured. A target closer than this distance will result in invalid data.
Measurement range – The vertical distance, starting at the end of the clearance distance, in which
targets can be scanned and measured. Targets beyond the measurement range will result in invalid data.
Field of view – The width on the X axis along the measurement range. At the far end of the
measurement range, the field of view is wider, but the X resolution and Z resolution are lower. At the
near end, the field of view is narrower, but the X resolution is higher. When resolution is critical, if
possible, place the target closer to the near end. (For more information on the relation between target
distance and resolution, see Z Resolution on page 61.)
X Resolution
X resolution is the horizontal distance between each measurement point along the laser line. This
specification is based on the number of camera columns used to cover the field of view (FOV) at a
particular measurement range.
Because the FOV is trapezoidal (shown in red, below), the distance between points is closer at the near
range than at the far range. This is reflected in the Gocator data sheet as the two numbers quoted for X
resolution.
X Resolution is important for understanding how accurately width on a target can be measured.
When the sensor runs in Profile mode and Uniform Spacing is enabled, the 3D data is
resampled to an X interval that is different from the raw camera resolution. For more
information, see Resampled Data and Point Cloud Data on page 68.
Like X resolution, Z resolution is better closer to the sensor. This is reflected in the Gocator datasheets as
the two numbers quoted for Z resolution.
Z Linearity
Z linearity is the difference between the actual distance to the target and the measured distance to the
target, throughout the measurement range. Z linearity gives an indication of the sensor's ability to
measure absolute distance.
Coordinate Systems
Range data is reported in one of three coordinate systems, which generally depends on the alignment
state of the sensor.
l System coordinates: Used on aligned sensors. Applies to either standalone or multi-sensor sys-
tems.
l Part and section coordinates: Data can optionally be reported using a coordinate system relative
to the part itself.
These coordinate systems are described below.
For most Gocator 2100, 2300, 2400, and 2800 sensors, X and Y increase as illustrated below,
relative to the connectors. For Gocator 2320, 2410, and 2420, one or both of these axes
increase relative to the laser and camera; for more information, see the coordinate system
orientations illustrated in the specification drawings of these sensors in Sensors on page 847.
Sensor Coordinates
Unaligned sensors use sensor coordinates: The measurement range (MR) is along the Z axis. The sensor’s
field of view (FOV) is along the X axis. Most importantly, the origin is at the center of the measurement
range and field of view.
The mounting direction, relative to the direction of travel, can be set using either the Normal or Reverse
layout. For more information, see Layout on page 101.
System Coordinates
Aligning sensors adjusts the coordinate system in relation to sensor coordinates, resulting in system
coordinates (for more information on sensor coordinates, see Sensor Coordinates on the previous page).
For more information on aligning sensors, see Alignment on page 143.
The adjustments resulting from alignment are called transformations (offsets along the axes and
rotations around the axes). Transformations are displayed in the Sensor panel on the Scan page. For
more information on transformations in the web interface, see Transformations on page 133.
System coordinates are aligned so that the system X axis is parallel to the alignment target surface. The
system Z origin is set to the base of the alignment target object. In both cases, alignment determines the
offsets in X and Z.
Alignment is used with a single sensor to compensate for mounting misalignment and to set a zero
reference, such as a conveyor belt surface.
Additionally, in multi-sensor systems, alignment sets a common coordinate system. That is, scan data
and measurements from the sensors are expressed in a unified coordinate system.
Alignment can also determine offsets along the Y axis. This allows setting up a staggered layout in multi-
sensor systems. This is especially useful in side-by-side mounting scenarios, as it provides full coverage
for models with a small scan area.
As with sensor coordinates, in system coordinates, Y position increases as the object moves forward
(increasing encoder position).
Alignment also determines the Y Angle (angle on the X–Z plane, around the Y axis) needed to align sensor
data. This is also sometimes called roll correction.
Similarly, tilt can be determined around the X and the Z axis, which compensates for the angle in height
measurements. These are sometimes called pitch correction and yaw correction, respectively. Rotation
around the X axis often used for specular mounting.
X angle is positive when rotating from positive Y to positive Z. Z angle is positive when rotating from
positive X to positive Y.
When applying the transformations, the object is first rotated around X, then Y, and then Z, and then the
offsets are applied.
Part data can be expressed in aligned system coordinates or unaligned sensor coordinates. But part data
can also be represented in part coordinates: data and measurement results are in a coordinate system
that places the X and Y origins at the center of the part. The Z origin is at the surface surrounding the
alignment target (if the sensor or system has been aligned) or in the center of the center of the
measurement range (if the sensor or system has not been aligned).
The Frame of Reference setting, in the Part Detection panel on the Scan page, controls
whether part data is recorded using sensor/system coordinates or part coordinates.
For more information, see the Profile Bounding Box tool or the Surface Bounding Box tool, and the
Script tool.
The size of the spacing interval is set under the Spacing tab in the Sensor panel on Scan page.
Resampling to uniform spacing reduces the complexity for downstream algorithms to process the profile
data from the sensor, but places a higher processing load on the sensor's CPU.
When uniform spacing is not enabled, no processing is required on the sensor. This frees up processing
resources in the sensor, but usually requires more complicated processing on the client side. Ranges in
this case are reported in (X, Z) coordinate pairs.
Most built-in measurement tools in the Gocator in Profile mode operate on profiles with uniform
spacing. A limited number of tools can operate on profiles without uniform spacing. For more
information on the profile tools, see Profile Measurement on page 225.
A drawback of uniform spacing is that if sensors are angled to scan the sides of a target, data on the
"verticals" is lost because points falling in the same "bin" are combined. When Uniform Spacing is
disabled, however, all points are preserved on the sides. In this case, the data can be processed by the
subset of tools that work on profiles without uniform spacing. Alternatively, the data can be processed
externally using the SDK.
l Surface generation
l Part detection
l Sectioning
Surface Generation
Laser profile sensors create a single profile with each exposure. These sensors can combine a series of
profiles gathered as a target moves under the sensor to generate a height map, or surface, of the entire
target.
Part Detection
After a sensor has generated data by combining single exposures into larger pieces of data, the firmware
can isolate discrete parts on the generated surface into separate scans representing parts.
Part detection is useful when measurements on individual parts are needed and for robotic pick and
place applications.
Sectioning
In Surface mode, the sensor can also extract a profile from a surface or part using a line you define on
that surface or part. The resulting profile is called a “section.” A section can have any orientation on the
surface, but its profile is parallel to the Z axis.
You can use most of Gocator's profile measurement tools on a section, letting you perform
measurements that are not possible with surface measurement tools.
Part Matching
The sensor can match scanned parts to the edges of a model based on a previously scanned part (see
Using Edge Detection on page 182) or to the dimensions of a fitted bounding box or ellipse that
encapsulate the model (see Using Bounding Box and Ellipse on page 191). When parts match, the sensor
can rotate scans so that they are all oriented in the same way. This allows measurement tools to be
applied consistently to parts, regardless of the orientation of the part you are trying to match.
Gocator provides several measurement tools, each of which provides a set of individual measurements,
giving you dozens of measurements ideal for a wide variety of applications to choose from. The
configured measurements start returning pass/fail decisions, as well as the actual measured values,
which are then sent over the enabled output channels to control devices such as PLCs, which can in turn
control ejection or sorting mechanisms. (For more information on measurements and configuring
measurements, see Measurement and Processing on page 201. For more information on output
channels, see Output and Digital Tracking on page 82.)
You can create custom tools that run your own algorithms. For more information, see GDK on
page 823.
A part's position can vary on a transport system. To compensate for this variation, Gocator can anchor a
measurement to the positional measurement (X, Y, or Z) or Z angle of an easily detectable feature, such
as the edge of a part.
The calculated offset between the two ensures that the anchored measurement will always be properly
positioned on different parts.
Tool Chaining
Gocator’s measurement and processing tools can be linked together: one tool uses another tool’s output
as input. This gives you a great deal of control and flexibility when it comes to implementing your
application.
The following table lists the available outputs from Gocator’s tools:
Measurement Single 64-bit value SDK, PLC protocols Rendered on tool's input Not supported as input,
data positional and Z angle
measurements can be
used by some tools for
anchoring
Geometric Structured data Cannot be output via Rendered on tool's input Tools that accept the
Features values: for protocols data specific features
example, point or
line
Tool Data Binary data SDK Rendered separately Tools that accept the
structure: Profile, specific data type
Surface, or Generic
The following sections describe these types of output and how you use them as input.
Anchoring Measurements
Tools can use the positional measurements (X, Y, or Z) of other tools as anchors to compensate for
minor shifts of parts: anchored tools are “locked” to the positional measurements of the anchoring tool’s
measurements. Some tools can also use a Z Angle measurement as an anchor. Typically, you will use
measurements from more easily found features on a target—such as an edge or a hole—as anchors to
accurately place other positional and dimensional measurements. This can help improve repeatability
and accuracy in the anchored tools. Note that anchoring measurements are used to calculate the offsets
of the anchored tools: the results from these measurements are not used as part of the anchored tool's
measurements.
When combined with the matching and rotation capabilities of part matching, anchoring accounts for
most sources of variation in part position and orientation and, consequently, avoids many measurement
errors. For more information on anchoring, see Measurement Anchoring on page 216.
Gocator’s “Feature” tools (such as Feature Dimension and Feature Intersect) use geometric features as
inputs. For example, because the point geometric feature representing the center of a hole has X, Y, and
Z components, you can perform dimensional measurements between it and another geometric feature,
such as another hole or an edge. The Feature Create tool takes one or more geometric features as input
and generates new geometric features (for example, creating a line from two point geometric features).
Center Point geometric feature of a Surface Hole tool enabled on Features tab
Geometric features are distinct from the “feature points” used by certain tools to determine which data
point in a region should be used in a measurement, for example, the maximum versus the minimum on
the Z axis of a data point in a region of interest:
Tool Data
Some measurement and processing tools can output more complex data, which can be used as input by
other tools or SDK applications. The following types of data are available: Profile, Surface, and Generic.
Profile and Surface tool data are identical in nature to the data produced by a sensor scan, except that
they are the processed result from a tool. This kind of data can be used as input in compatible tools.
Examples of this kind of this kind of data are the Stitched Surface output from the Surface Stitch tool, or
the Filtered Surface output from the Surface Filter tool. Another important kind of data is the
Transformed Surface produced by the Surface Transform tool, which transforms (shifting or rotating on
the X, Y, and Z axes) the sensor's scan data; the Surface Transform tool supports a full 6 degrees of
freedom. For more information, see Transform on page 464.
Both Profile and Surface tool data can be visualized in the data viewer, not as an overlay, however, but as
independent data. The following is the output of the Surface Filter tool . Note that the first drop-down is
set to Tool, to tell the sensor to display the tool data output, rather than the sensor output:
You enable tool data input on a tool’s Parameters tab, using the Stream drop-down:
Generic tool data can’t be visualized. It can however be accessed from GDK tools or SDK applications you
create. Examples of Generic tool data are the Segments Array data produced by the Surface
Segmentation tool, or the Output Measurement data produced by the Surface Flatness. For more
information on the SDK, see GoSDK on page 813. Generic tool data is enabled in the same way as Profile
and Surface tool data, from the tool’s Data tab.
You may need to switch the first data viewer drop-down to “Tool” to view Profile or Surface tool data:
l Ethernet (which provides industry-standard protocols such as Modbus, EtherNet/IP, and ASCII, in
addition to the Gocator protocol)
l Digital
l Analog
l Serial interfaces
An important concept is digital output tracking. Production lines can place an ejection or sorting
mechanism at different distances from where the sensor scans the target. For this reason, Gocator lets
you schedule a delayed decision over the digital interfaces. Because the conveyor system on a typical
production line will use an encoder or have a known, constant speed, targets can effectively be “tracked”
or "tagged." Gocator will know when a defective part has traveled far enough and trigger a PLC to
activate an ejection/sorting mechanism at the correct moment. For more information on digital output
tracking, see Digital Output on page 514.
Browser Compatibility
LMI recommends Chrome, Firefox, or Edge for use with the Gocator web interface.
Internet Explorer 11 is supported with limitations; for more information, see below.
It is possible to remove the time limit that causes this issue, but you must modify the computer’s
registry. To do so, follow Microsoft's instructions at https://support.microsoft.com/en-
us/help/3099259/update-to-add-a-setting-to-disable-500-msec-time-limit-for-webgl-frame.
1. In upper right corner, click the settings icon ( ), and choose Internet options.
2. In the dialog that opens, click the Advanced tab, and scroll down to the Security section.
4. Click OK and then restart your computer for the changes to take effect.
1 Manage page Contains settings for sensor system layout, network, motion and
alignment, handling jobs, and sensor maintenance. See Management and
Maintenance on page 98.
2 Scan page Contains settings for scan mode, trigger source, detailed sensor
configuration, and performing alignment. See Scan Setup and Alignment on
page 121.
3 Model page Lets you set up sections and part matching. See Models on page 181
4 Measure page Contains built-in measurement tools and their settings. See Measurement
and Processing on page 201.
5 Output page Contains settings for configuring output protocols used to communicate
measurements to external devices. See Output on page 509.
6 Dashboard page Provides monitoring of measurement statistics and sensor health. See
Dashboard on page 523.
7 CPU Load and Speed Provides important sensor performance metrics. See Metrics Area on
page 95.
8 Toolbar Controls sensor operation, manages jobs, and filters and replays
recorded data. See Toolbar on the next page.
9 Configuration area Provides controls to configure scan and measurement tool settings.
10 Data viewer Displays sensor data, tool setup controls, and measurements. See Data
Viewer on page 165 for its use when the Scan page is active and on page
202 for its use when the Measure page is active.
11 Status bar Displays log messages from the sensor (errors, warnings, and other
information) and frame information, and lets you switch the interface
language. For more information, see Status Bar on page 95.
Toolbar
The toolbar is used for performing operations such as managing jobs, working with replay data, and
starting and stopping the sensor.
Element Description
Most of the settings that can be changed in the sensor's web interface, such as the ones in the Manage,
Measure, and Output pages, are temporary until saved in a job file. Each sensor can have multiple job
files. If there is a job file that is designated as the default, it will be loaded automatically when the sensor
is reset.
When you change sensor settings using the sensor web interface in the emulator, some changes are
saved automatically, while other changes are temporary until you save them manually. The following
table lists the types of information that can be saved in a sensor.
Job Most of the settings that can be changed in the sensor's web interface, such as the ones in
the Manage, Measure, and Output pages, are temporary until saved in a job file. Each
sensor can have multiple job files. If there is a job file that is designated as the default, it
will be loaded automatically when the sensor is reset.
Alignment Alignment can either be fixed or dynamic, as controlled by the Alignment Reference
setting in Motion and Alignment in the Manage page.
Alignment is saved automatically at the end of the alignment procedure when
Alignment Reference is set to Fixed . When Alignment Reference is set to
Dynamic, however, you must manually save the job to save alignment.
Network Address Network address changes are saved when you click the Save button in Networking on
the Manage page. The sensor must be reset before changes take effect.
The job drop-down list in the toolbar shows the jobs stored in the sensor. The job that is currently active
is listed at the top. The job name will be marked with "[unsaved]" to indicate any unsaved changes.
To create a job:
1. Choose [New] in the job drop-down list and type a name for the job.
To save a job:
The job is saved to sensor storage. Saving a job automatically sets it as the default, that is, the job
loaded when then sensor is restarted.
The job is activated. If there are any unsaved changes in the current job, you will be asked whether you want
to discard those changes.
You can perform other job management tasks—such as downloading job files from a sensor to a
computer, uploading job files to a sensor from a computer, and so on—in the Jobs panel in the Manage
page. See Jobs on page 112 for more information.
1. Toggle Replay mode off by setting the slider to the left in the Toolbar.
Newly recorded data is appended to existing replay data unless the sensor job has been modified.
To replay data:
1. Toggle Replay mode on by setting the slider to the right in the Toolbar.
The slider's background turns blue and a Replay Mode Enabled message is displayed.
2. Use the Replay slider or the Step Forward, Step Back, or Play buttons to review data.
The Step Forward and Step Back buttons move the current replay location forward and backward by a
single frame, respectively.
The Play button advances the replay location continuously, animating the playback until the end of the
replay data.
The Stop button (replaces the Play button while playing) can be used to pause the replay at a particular
location.
The Replay slider (or Replay Position box) can be used to go to a specific replay frame.
3. Use the Replay Slider, Step Forward, Step Back, or Play button to simulate measurements.
Step or play through recorded data to execute the measurement tools on the recording.
Individual measurement values can be viewed directly in the data viewer. Statistics on the
measurements that have been simulated can be viewed in the Dashboard page; for more information
on the dashboard, see Dashboard on page 523.
Recording Filtering
Replay data is often used for troubleshooting. But replay data can contain thousands of frames, which
makes finding a specific frame to troubleshoot difficult. Recording filtering lets you choose which frames
the sensor records, based on one or more conditions, which makes it easier to find problems.
Any Condition The sensor records a frame when any condition is true.
All Conditions The sensor only records a frame if all conditions are true.
Conditions
Setting Description
Any Measurement The sensor records a frame when any measurement is in the state you select.
The following states are supported:
l pass
l fail or invalid
l fail and valid
l valid
l invalid
Single Measurement The sensor records a frame if the measurement with the ID you specify in ID is in the
state you select. This setting supports the same states as the Any Measurement
setting (see above).
Any Data At/Above Threshold : The sensor records a frame if the number of valid points in
the frame is above the value you specify in Range Count Threshold .
Below Threshold : The sensor records a frame if the number of valid points is below
the threshold you specify.
In Surface mode, the number of valid points in the surface is compared to the
threshold, not any sections that may be defined.
3. In the Recording Filtering dialog, choose how the sensor treats conditions:
For information on the available settings, see How a sensor treats conditions on the previous page.
4. Configure the conditions that will cause the sensor to record a frame:
For information on the available settings, see Conditions on the previous page.
5. Click the "x" button or outside of the Recording Filtering dialog to close the dialog.
The recording filter icon turns green to show that recording filters have been set.
When you run the sensor, it only records the frames that satisfy the conditions you have set.
Data can also be exported from a sensor to a client computer in order to process the data using third-
party tools.
You can only upload replay data to the same sensor model that was used to create the data.
Replay data is not loaded or saved when you load or save jobs.
l Upload and merge: Uploads the replay data and merges the data's associated job with the current
job. Specifically, the settings on the Scan page are overwritten, but all other settings of the current
job are preserved, including any measurements or models.
If you have unsaved changes in the current job, the firmware asks whether you want to discard the
changes.
4. If you clicked Discard, navigate to the replay data to upload from the client computer and click OK.
The replay data is loaded, and a new unsaved, untitled job is created.
Replay data can be exported using the CSV format. If you have enabled Acquire Intensity in the Scan
Mode panel on the Scan page, the exported CSV file includes intensity data.
Surface intensity data cannot be exported to the CSV format. It can only be exported separately
as a bitmap.
4. (Optional) Convert exported data to another format using the CSV Converter Tool. For information on
this tool, see CSV Converter Tool on page 837.
The decision values in the exported data depend on the current state of the job, not the state
during recording. For example, if you record data when a measurment returns a pass decision,
change the measurement's settings so that a fail decision is returned, and then export to CSV,
you will see a fail decision in the exported data.
Recorded intensity data can be exported to a bitmap (.BMP format). Acquire Intensity must be
checked in the Scan Mode panel while data was being recorded in order to export intensity data.
l Switch to Replay mode and click the Export button and select Intensity data as BMP.
The CPU bar in the Metrics panel (at the top of the interface) displays how much of the CPU is being
utilized. A warning symbol ( ) will appear next to the CPU bar if the sensor drops data because the CPU
is over-loaded.
CPU at 100%
The Speed bar displays the frame rate of the sensor. A warning symbol ( ) will appear next to it if
triggers (external input or encoder) are dropped because the external rate exceeds the maximum frame
rate.
Open the log for details on the warning. For more information on logs, see Log on the next page.
Data Viewer
The data viewer is displayed in both the Scan and the Measure pages, but displays different
information depending on which page is active.
When the Scan page is active, the data viewer displays sensor data and can be used to adjust the active
area and other settings. Depending on the selected operation mode (page 122), the data viewer can
display video images, profiles, sections, or surfaces. For details, see Data Viewer on page 165.
When the Measure page is active, the data viewer displays sensor data onto which representations of
measurement tools and their measurements are superimposed. For details, see Data Viewer on
page 202.
Status Bar
The status bar lets you do the following:
1. Click on the Log open button at the bottom of the web interface.
Frame Information
The area to the right of the status bar displays useful frame information, both when the sensor is
running and when viewing recorded data.
This information is especially useful when you have enabled recording filtering. If you look at a recording
playback, when you have enabled recording filtering, some frames can be excluded, resulting in variable
"gaps" in the data.
Frame Index: Displays the index in the data buffer of the current frame. The value resets to 0 when the
sensor is restarted or when recording is enabled.
Master Time: Displays the recording time of the current frame, with respect to when the sensor was
started.
Encoder Index: Displays the encoder value at the time of the last encoder Z index pulse. Note this is not
the same as the encoder value at the time the frame was captured.
Timestamp: Displays the timestamp the current frame, in microseconds from when the sensor was
started.
l Click the frame information area to switch to the next available type of information.
When this mode is enabled, the data viewer and measurement results are not refreshed after each
setting change. Also, when Quick Edit is enabled, in Replay mode, stepping through frames or playing
back scan data does not change the displayed frame.
When a sensor is running, Quick Edit mode is ignored: all changes to settings are reflected
immediately in the data viewer.
Interface Language
The language button on the right side of the status bar at the bottom of the interface lets you change
the language of the interface.
The interface reloads on the page you were working in, displaying the page using the language you chose.
The sensor state is preserved.
Element Description
4 Motion and Alignment Contains settings to configure the encoder. See Motion and
Alignment on page 110.
5 Jobs Lets you manage jobs stored on the sensor. See Jobs on
page 112.
Sensor System
The following sections describe the Sensor System category on the Manage page. This category
provides sensor information and the autostart setting. It also lets you choose which sensors to add to a
dual- or multi-sensor system.
Although some sensor models have much wider fields of view, the trade-off is that their resolution is
much lower: finer features on targets are below their resolution and therefore can't be measured.
Models with smaller fields of view—which limit the maximum size of targets that can be scanned—have
vastly finer resolutions. When you combine multiple sensors with a smaller field of view, you obtain a
wider overall field of view with the finer resolution of those models.
The sensors lets you easily and quickly set up dual- and multi-sensor systems from the web interface.
Setting up these systems involves two steps:
1. Assigning one or more additional sensors, called Buddy sensors, to the Main sensor. For more inform-
ation, see Buddy Assignment on the next page.
Buddy Assignment
In a dual- or multi-sensor system, the Main sensor controls a second sensor, called the Buddy sensor,
after the Buddy sensor is assigned to the Main sensor. You configure both sensors through the Main
sensor's interface.
Main and Buddy sensors must be assigned unique IP addresses before they can be used on the
same network. Before proceeding, connect the Main and Buddy sensors one at a time (to avoid an
address conflict) and use the steps described in Running a Dual-Sensor System (page 30) to assign
each sensor a unique address.
When a sensor is acting as a Buddy, it is not discoverable and its web interface is not accessible.
A sensor can only be assigned as a Buddy if its firmware and model number match the
firmware and model number of the Main sensor.
2. In the Visible Sensors list, click the "plus" icon next to the sensor you want to add as a Buddy.
The sensor you added to the system appears in a Buddies list.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 100
After you have assigned the desired number of Buddy sensors, you must specify system's layout. For
more information, see Layout below.
To remove a Buddy, click the "minus" icon next to the sensor you want to remove. To remove all
Buddies, click Remove All Buddies.
Disabling the setting is not recommended. Disabling the overheat protection feature could lead
to premature laser failure if the sensor operates outside the specified temperature range.
Sensor Autostart
With the Autostart setting enabled, scanning and measurements begin automatically when the sensor
is powered on. Autostart must be enabled if the sensor will be used without being connected to a
computer.
To enable/disable Autostart:
Layout
The following sections describe the Layout category on the Manage page. This category lets you
configure dual- and multi-sensor systems.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 101
Mounting orientations must be specified for a dual- or multi-sensor system. This information allows the
alignment procedure to determine the correct system-wide coordinates for laser profiling and
measurements. For more information on sensor and system coordinates, see Coordinate Systems on
page 63.
Dual- and multi-sensor layouts are only displayed when a Buddy sensor has been assigned.
For multi-sensor layouts with sensors angled around the Y axis, to get "side" data, you must
uncheck Uniform Spacing before scanning. The Y offset, X angle, and Z angle transformations
cannot be non-zero when Uniform Spacing is unchecked. Therefore, when aligning a sensor
using a bar alignment target with Uniform Spacing unchecked, set the Degrees of Freedom
setting to X, Z, Y Angle, which prevents these transformations from being non-zero.
Supported Layouts
Layout Type Example
Normal
The sensor operates as an isolated device.
Reverse
The sensor operates as an isolated device,
but in a reverse orientation. You can use
this layout to change the handedness of the
data.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 102
Layout Type Example
Wide
Sensors are mounted in Left (Main) and
Right (Buddy) positions. This allows for a
larger combined field of view. Sensors may
be angled around the Y axis to avoid
occlusions.
Reverse
Sensors are mounted in a left-right layout
as with the Wide layout, but the Buddy
sensor is mounted such that it is rotated
180 degrees around the Z axis to prevent
occlusion along the Y axis.
Sensors should be shifted along the Y axis
so that the laser lines align.
Opposite
Sensors are mounted in Top (Main) and
Bottom (Buddy) positions for a larger
combined measurement range and the
ability to perform Top/Bottom differential
measurements.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 103
Layout Type Example
Grid
For systems composed of three or more
sensors. Sensors can be mounted in a 2-
dimensional grid using the settings in the
Layout Grid area below. Side-by-side and
top-bottom configurations are supported,
as well as combinations of these and
reversed orientations.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 104
Layout Type Example
2. Under Layout Types, choose Normal or Reverse layout by clicking one of the layout buttons.
Before you can select a dual-sensor layout, you must assign a second sensor as the Buddy
sensor. For more information, see Dual- and Multi-sensor Systems on page 99.
2. Under Layout Types, choose a layout by clicking one of the layout buttons.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 105
See the table above for information on layouts.
Before you can select a multi-sensor layout, you must assign two or more additional sensors as
Buddy sensors. For more information, see Dual- and Multi-sensor Systems on page 99.
2. Under Layout Grid, click the "plus" icon to the right to add the desired number of columns in the grid.
The Main sensor is automatically assigned to the first cell. You can however assign the Main sensor to
any cell.
3. Choose a sensor from the drop-down in each cell you want to populate.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 106
The following shows the layout of a four-sensor Wide system:
The following shows the layout of a four-sensor system, with two sensors on the top and two sensors on
the bottom:
4. (Optional) For each sensor mounted in a reversed orientation in relation to the Main sensor (rotated
180 degrees around the Z axis to avoid occlusions), check the Reversed option.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 107
You must assign all Buddy sensors to a cell in the layout grid. Otherwise, the system will not run.
You can configure dual- and multi-sensor systems so that there is a slight delay between the exposures
of sensors or groups of sensors to eliminate laser interference, using the Device Exposure
Multiplexing setting. For more information, see Device Exposure Multiplexing below.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 108
To enable/disable exposure multiplexing:
3. (Optional) If the system contains more than two sensors, assign the sensors to different banks.
Networking
The Networking category on the Manage page provides network settings. Settings must be configured
to match the network to which the sensors are connected.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 109
To configure the network settings:
2. In the Networking category, specify the Type, IP, Subnet Mask, and Gateway settings.
The sensor can be configured to use DHCP or assigned a static IP address by selecting the appropriate
option in the Type drop-down.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 110
Alignment Reference
The Alignment Reference setting can have one of two values: Fixed or Dynamic.
Setting Description
Fixed A single, global alignment is used for all jobs. This is typically used when the sensor
mounting is constant over time and between scans, for example, when the sensor is
mounted in a permanent position over a conveyor belt.
Dynamic A separate alignment is used for each job. This is typically used when the sensor’s position
relative to the object scanned is always changing, for example, when the sensor is mounted
on a robot arm moving to different scanning locations.
1. Go to the Manage page and click on the Motion and Alignment category.
2. In the Alignment section, choose Fixed or Dynamic in the Alignment Reference drop-down.
Encoder Resolution
You can manually enter the encoder resolution in the Resolution setting , or it can be automatically set
by performing an alignment with Type set to Moving. Establishing the correct encoder resolution is
required for correct scaling of the scan of the target object in the direction of travel.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 111
Encoder resolution is expressed in millimeters per tick, where one tick corresponds to one of the four
encoder quadrature signals (A+ / A- / B+ / B-).
Encoders are normally specified in pulses per revolution, where each pulse is made up of the
four quadrature signals (A+ / A- / B+ / B-). Because the sensor reads each of the four quadrature
signals, you should choose an encoder accordingly, given the resolution required for your
application.
1. Go to the Manage page and click on the Motion and Alignment category.
Travel Speed
The Travel Speed setting is used to correctly scale scans in the direction of travel in systems that lack an
encoder but have a conveyor system that is controlled to move at constant speed. Establishing the
correct travel speed is required for correct scaling of the scan in the direction of travel.
1. Go to the Manage page and click on the Motion and Alignment category.
Travel speed can also be set automatically by performing an alignment with Type set to Moving (see
Aligning Sensors on page 144).
Jobs
The Jobs category on the Manage page lets you manage the jobs stored on a sensor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 112
Element Description
Jobs list Displays the jobs that are currently saved in the sensor's flash storage.
Save button Saves current settings to the job using the name in the Name field.
Load button Loads the job that is selected in the job list. Reloading the current job discards any unsaved changes.
Delete button Deletes the job that is selected in the job list.
Set as Default Sets the selected job as the default to be loaded when the sensor starts. When the default job is
button selected, this button is used to clear the default.
Jobs can be loaded (currently activated in sensor memory) and set as default independently. For
example, Job1 could be loaded, while Job2 is set as the default. Default jobs load automatically when a
sensor is power cycled or reset.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 113
To save a job:
Security
You can prevent unauthorized access to a sensor by setting passwords. Each sensor has two accounts:
Administrator and Technician.
By default, no passwords are set. When you start a sensor, you are prompted for a password only if a
password has been set.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 114
Account Types
Account Description
Administrator The Administrator account has privileges to use the toolbar (loading and saving jobs, recording and
viewing replay data), to view all pages and edit all settings, and to perform setup procedures such as
sensor alignment.
Technician The Technician account has privileges to use the toolbar (loading and saving jobs, recording and
viewing replay data), to view the Dashboard page, and to start or stop the sensor.
2. In the Administrator section, enter the Administrator account password and password confirmation.
2. In the Technician section, enter the Technician account password and password confirmation.
If the administrator or technician password is lost, the sensor can be recovered using a special software
tool. See Sensor Discovery Tool on page 836 for more information.
Maintenance
The Maintenance category in the Manage page is used to do the following:
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 115
Sensor Backups and Factory Reset
You can create sensor backups, restore from a backup, and restore to factory defaults in the
Maintenance category.
Backup files contain all of the information stored on a sensor, including jobs and alignment.
An Administrator should create a backup file in the unlikely event that a sensor fails and a
replacement sensor is needed. If this happens, the new sensor can be restored with the backup
file.
To create a backup:
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 116
To restore from a backup:
1. Go to the Manage page and click on the Maintenance category.
Firmware Upgrade
LMI recommends routinely updating firmware to ensure that sensors always have the latest features
and fixes.
In order for the Main and Buddy sensors to work together, they must be use the same firmware
version. This can be achieved by upgrading through the Main sensor or by upgrading each sensor
individually.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 117
3. Download the latest firmware.
If a new version of the firmware is available, follow the instructions to download it to the client
computer.
If the client computer is not connected to the Internet, firmware can be downloaded and transferred to
the client computer by using another computer to download the firmware from LMI's website:
http://www.lmi3D.com/support/downloads.
3. Locate the firmware file in the File dialog and then click open.
Support
The Support category in the Manage page is used to do the following:
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 118
Support Files
You can download a support file from a sensor and save it on your computer. You can then use the
support file to create a scenario in the emulator (for more information on the emulator, see Gocator
Emulator on page 534). LMI's support staff may also request a support file to help in troubleshooting.
2. In Filename, type the name you want to use for the support file.
When you create a scenario from a support file in the emulator, the filename you provide here is displayed
in the emulator's scenario list.
Support files end with the .gs extension, but you do not need to type the extension in Filename.
Manual Access
You can access the Gocator manuals from within the Web interface.
You may need to configure your browser to allow pop-ups to open or download the manual.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 119
l Open HTML: Opens the HTML version of the manual in your default browser.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 120
Scan Setup and Alignment
The following sections describe the steps to configure sensors for data acquisition using the Scan page.
Setup and alignment should be performed before adding and configuring measurements or outputs.
Element Description
1 Scan Mode panel Contains settings for the current scan mode and other options. See Scan Modes on the
next page.
2 Trigger panel Contains trigger source and trigger-related settings. See Triggers on page 123.
3 Sensor panel Contains settings for an individual sensor, such as active area or exposure. See Sensor on
page 129.
5 Surface Generation Contains settings for surface generation. See Surface Generation on page 154.
panel
6 Part Detection Used to set the part detection logic for sorting data into discrete objects. See Part
panel Detection on page 158.
7 Filters panel Contains settings for post-processing of the profiles. See Filters on page 151.
8 Data Viewer Displays sensor data and adjusts regions of interest. Depending on the current operation
mode, the data viewer can display video images or scan data. See Data Viewer on
page 165.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 121
The following table provides quick references for specific goals that you can achieve from the panels in
the Scan page.
Goal Reference
Select a trigger source that is appropriate for the application. Triggers (page 123)
Ensure that camera exposure is appropriate for scan data acquisition. Exposure (page 134)
Find the right balance between data quality, speed, and CPU utilization. Active Area (page 129)
Exposure (page 134)
Job File Structure (page 551)
Align scan data to a common reference and so that values can be correctly scaled Aligning Sensors (page 144)
along the different axes.
Set up the part detection logic to create discrete objects from scan data. Part Detection (page 158)
Specify smoothing, gap-filling, and resampling parameters to remove effects of Filters (page 151)
occlusions.
Scan Modes
The sensor web interface supports a video mode and one or more data acquisition modes. The scan
mode can be selected in the Scan Mode panel.
Video Outputs video images from the sensor. This mode is useful for configuring exposure
time and troubleshooting stray light or ambient light problems.
Profile Outputs profiles and performs profile measurements.
Video images are processed internally to produce laser profiles and cross-sectional
measurements.
Surface Outputs 3D point clouds and performs surface measurements. The sensor uses various
methods to generate a surface (see Surface Generation on page 154). Part detection
can be enabled on a surface to identify discrete parts (Part Detection on page 158).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 122
Mode and Option Description
Uniform Spacing When this option is enabled, data points are resampled to a uniform spacing
(Resampled Data and Point Cloud Data on page 68 for more information). Set the size
of the spacing in the Spacing tab (see Spacing Interval on page 139).
When the option is disabled, the sensor outputs unprocessed range data. The sensor
reports data points in (x, z) coordinate pairs. Post-processing is disabled. Only a subset
of the measurement tools is available.
Disable this option to extract ranges from the sensor at the highest possible rate.
If you are using a layout in which sensors are angled around the Y
axis in order to capture "side" data, you must uncheck Uniform
Spacing. However, currently, only a limited set of built-in
measurement tools are able to perform measurements on the
resulting data. If more complex measurements are required, data
can be processed using an SDK-based application instead.
Acquire Intensity When this option is enabled, an intensity value will be produced for each data point.
Triggers
A trigger is an event that causes a sensor to take a single image. Triggers are configured in the Trigger
panel on the Scan page.
When a trigger is processed, the laser is strobed and the camera exposes to produce an image. The
resulting image is processed inside the sensor to yield a profile (range/distance information). The data
can then be used for measurement.
The sensor can be triggered by one of the sources described in the table below.
If the sensor is connected to a Master 400 or higher, encoder and digital (external) input signals
over the IO cordset are ignored. The sensor instead receives these signals from the Master; for
encoder and digital input pinouts on Masters, see the section corresponding to your Master in
Master Network Controllers on page 903.
If the sensor is connected to a Master 100 (or no Master is used), the sensor receives signals
over the IO cordset. For information on connecting encoder and digital input signals to a sensor
in these cases, see Encoder Input on page 900 and Digital Input on page 899, respectively.
Time Sensors have an internal clock that can be used to generate fixed-frequency triggers. The
external input can be used to enable or disable the time triggers.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 123
Trigger Source Description
Encoder An encoder can be connected to provide triggers in response to motion. Three encoder triggering
behaviors are supported. These behaviors are set using the Behavior setting.
Track Backward
A scan is triggered when the target object moves forward. If the target object moves backward, it
must move forward by at least the distance that the target travelled backward (this distance
backward is "tracked"), plus one encoder spacing, to trigger the next scan.
Ignore Backward
A scan is triggered only when the target object moves forward. If the target object moves
backward, it must move forward by at least the distance of one encoder spacing to trigger the
next scan.
Bi-directional
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 124
Trigger Source Description
When triggers are received at a frequency higher than the maximum frame rate, some triggers
may not be accepted. The Trigger Drops Indicator in the Dashboard can be used to check for
this condition.
The external input can be used to enable or disable the encoder triggers.
For information on the maximum encoder rate, see Maximum Encoder Rate on page 129.
To verify that the sensor is receiving encoder signals, check whether Encoder
Value is changing in the Motion and Alignment category on the Manage page,
or in the dashboard.
External Input A digital input can provide triggers in response to external events (e.g., photocell). The external
input triggers on the rising edge of the signal.
When triggers are received at a frequency higher than the maximum frame rate, some triggers
may not be accepted. The Trigger Drops Indicator in the Dashboard page can be used to check
for this condition.
For information on the maximum input trigger rate, see Maximum Input Trigger Rate on page 129.
Software A network command can be used to send a software trigger. See Protocols on page 647 for more
information.
Depending on the setup and measurement tools used, the CPU utilization may exceed 100%, which
reduces the overall acquisition speed.
For examples of typical real-world scenarios, see Trigger Examples on the next page. For information on
the settings used with each trigger source, see Trigger Settings on page 127.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 125
Trigger Examples
Example: Encoder + Conveyor
Encoder triggering is used to perform profile
measurements at a uniform spacing.
The speed of the conveyor can vary while the
object is being measured; an encoder ensures
that the trigger spacing is consistent,
independent of conveyor speed.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 126
Example: Software Trigger + Robot Arm
Software triggering can be used to produce a
snapshot for profile measurement.
A software trigger can be used in systems that
use external software to control the activities
of system components.
Trigger Settings
The trigger source is selected using the Trigger panel in the Scan page.
After specifying a trigger source, the Trigger panel shows the parameters that can be configured.
Source All Selects the trigger source (Time, Encoder, External Input, or
Software).
Frame Rate Time Controls the frame rate. Select Max Speed from the drop-
down to lock to the maximum frame rate. Fractional values are
supported. For example, 0.1 can be entered to run at 1 frame
every 10 seconds.
Gate on External Input Time, Encoder External input can be used to enable or disable data acquisition
in a sensor. When this option is enabled, the sensor will
respond to time or encoder triggers only when the external
input is asserted.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 127
Parameter Trigger Source Description
Behavior Encoder Specifies how the sensor is triggered when the target moves.
Can be Track Backward, Ignore Backward, or Bi-Directional. See
Triggers on page 123 for more information on these behaviors.
Spacing Encoder, External Input Specifies the distance between triggers (mm). Internally the
sensor rounds the spacing to a multiple of the encoder
resolution.
Reversal Distance Encoder When encoder triggering is set to Bi-Directional , use this
setting to ignore jitter or vibrations in your transport system by
specifying what distance the target must travel before a
direction change is triggered. One of the following:
Auto: The distance is automatically set by multiplying the value
in Spacing by 3.
Custom: Set the distance (in millimeters). Various functions in
the sensor depend on this value to explicitly determine the
point where direction change is triggered. Set this value larger
than the maximum vibrations you see in your transport
system.
Units External Input, Software Specifies whether the trigger delay, output delay, and output
scheduled command operate in the time or the encoder
domain.
The unit is implicitly set to microseconds with Time trigger
source. The unit is implicitly set to millimeters with Encoder
trigger source.
Trigger Delay External Input Controls the amount of time or the distance the sensor waits
before producing a frame after the external input is activated.
This is used to compensate for the positional difference
between the source of the external input trigger (e.g.,
photocells) and the sensor.
Trigger delay is only supported in single exposure mode; for
details, see Exposure on page 134.
Depending on the surface generation settings, some trigger options may not be available.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 128
3. Select the trigger source from the drop-down.
When using a standalone sensor or a sensor connected to a Master 100, the maximum trigger rate is 32
kHz. This rate is limited by the fall time of the signal, which depends on the Vin and duty cycles. To
achieve the maximum trigger rate, the Vin and duty cycles must be adjusted as follows:
3.3 V 34 kHz
5V 34 kHz
10 V 22 kHz
For sensors connected through a Master 400 or higher, with the encoder signal supplied to the Master,
the maximum rate is about 300 kHz.
Sensor
The following sections describe the settings that are configured in the Sensor panel on the Scan page.
Active Area
Active area refers to the region within the sensor's maximum field of view that is used for data
acquisition.
By default, the active area covers the sensor's entire field of view. By reducing the active area, the sensor
can operate at higher speeds. You can also reduce the active area to exclude areas that are affected by
ambient light.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 129
Active area is specified in sensor coordinates, rather than in system coordinates. As a result, if the sensor
is already alignment calibrated, press the Acquire button to display uncalibrated data before configuring
the active area.See Coordinate Systems on page 63 for more information on sensor and system
coordinates.
Active area is set in the Active Area tab on the Sensor panel.
3. Expand the Sensor panel by clicking on the panel header or the button.
6. Click Select.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 130
7. Click Acquire to see a scan while setting the active area.
Acquiring a scan while setting the active area can help you determine where to size and place the
active area.
10. Save the job in the Toolbar by clicking the Save button .
Scanning devices are usually more accurate at the near end of their measurement range. If your
application requires a measurement range that is small compared to the maximum measurement
range of the sensor, mount the sensor so that the active area can be defined at the near end of the
measurement range.
Tracking Window
A sensor can follow a relatively flat target as it moves up and down beneath the sensor, using a
“tracking window.” When you define a tracking window, the sensor effectively reduces the active area
to match the size of the tracking window, which results in a faster scan rate. The reduced area moves to
track the laser line within the area defined in the Active Area tab. A tracking window is typically used in
road or web scanning applications where the target is a continuous surface.
You must balance the gain in speed due to the reduced area of the tracking window and the impact it
has on the sensor’s tracking ability: a smaller window gives the tracking function less data to predict
where the profile is moving.
The sensor adjusts the position of the tracking window to center the area on the average height of the
entire visible laser profile. A laser line remains tracked as long as the percentage of detected laser points
exceeds the user-defined search threshold. When the sensor loses track of the laser line, the sensor
searches for the laser line using the full defined active area.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 131
You should adjust the lighting and the active area to remove all background objects, such as the
conveyor belt surface.
On Gocator 2342 sensors, the Bridge Value tool's Window and StdDev measurements can force
the tracking engine to switch to search mode in some situations. For more information, see
Bridge Value on page 237.
The tracking window is defined in the Active Area tab, beneath the settings for the active area.
10. Save the job in the Toolbar by clicking the Save button .
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 132
Transformations
The transformation settings determine how data is converted from sensor coordinates to system
coordinates (for an overview on coordinate systems, see Coordinate Systems on page 63). Typically,
transformations are set when you align a sensor. However, you can also manually set values using the
Transformations section of the Active Area tab on the Sensor panel.
Parameter Description
X Offset Specifies the shift along the X axis. With Normal orientation, a positive value shifts the data to the
right. With Reverse orientation, a positive value shifts the data to the left.
Z Offset Specifies the shift along the Z axis. A positive value shifts the data toward the sensor.
When applying the transformations, the object is first rotated around X, then Y, and then Z, and then the
offsets are applied.
Artifacts may appear in scan data when Angle Z or Angle X is set to a non-zero value if
encoder trigger spacing is set too high (resulting in a low sampling rate).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 133
2. Choose a mode other than Video mode in the Scan Mode panel.
If Video mode is selected, you will not be able to change the settings.
8. Check that the transformation settings are applied correctly after the sensor is restarted.
Exposure
Exposure determines the duration of camera and light-source on-time. Longer exposures can be helpful
to detect light on dark or distant surfaces, but increasing exposure time decreases the maximum speed.
Different target surfaces may require different exposures for optimal results. Sensors provide three
exposure modes for the flexibility needed to scan different types of target surfaces.
Single Uses a single exposure for all objects. Used when the surface is uniform and is the same for
all targets.
Dynamic Automatically adjusts the exposure after each frame. Used when the target surface varies
between scans.
Multiple Uses multiple exposures to create a single profile. Used when the target surface has a varying
reflectance within a single profile (e.g., white and black).
For more information on the different types of exposure options, see the sections below.
Video mode lets you see how the light appears on the camera and identify any stray light or ambient
light problems. When exposure is tuned correctly, the projected light should be clearly visible along
the entire length of the viewer. If it is too dim, increase the exposure value; if it is too bright decrease
exposure value.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 134
Under-exposure: Over-exposure:
Laser line is not detected. Laser line is too bright.
Increase the exposure value. Decrease the exposure value.
When the sensor is in Multiple exposure mode, select which exposure to view using the drop-down box
next to "View" in the data viewer. This drop-down is only visible in Video scan mode when the Multiple
option is selected in the Exposure section in the Sensor panel.
Single Exposure
The sensor uses a fixed exposure in every scan. Single exposure is used when the target surface is
uniform and is the same for all targets.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 135
3. Expand the Sensor panel by clicking on the panel header or the button.
7. Edit the exposure setting by using the slider or by manually entering a value.
You can automatically tune the exposure by pressing the Auto Set button, which causes the sensor to turn
on and tune the exposure time.
Dynamic Exposure
The sensor automatically uses past profile information to adjust the exposure for subsequent exposures
to yield the best profile. This is used when the target surface changes from exposure to exposure (that is,
from scan to scan).
You can tune settings that control the exposure that is chosen by dynamic exposure in the
Material tab.
2. Expand the Sensor panel by clicking on the panel header or the button.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 136
Exposure is configured separately for each sensor.
Multiple Exposure
The sensor combines data from multiple exposures to create a single laser profile . Multiple exposures
can be used to increase the ability to detect light and dark materials that are in the field of view
simultaneously.
Up to five exposures can be defined with each set to a different exposure level. For each exposure, the
sensor will perform a complete scan at the current frame rate making the effective frame rate slower.
For example, if two exposures are selected, then the speed will be half of the single exposure frame rate.
The sensor will perform a complete multi-exposure scan for each external input or encoder trigger.
The resulting profile is a composite created by combing data collected with different exposures. The
sensor will choose profile data that is available from the lowest-numbered exposure step. It is
recommended to use a larger exposure for higher-numbered steps.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 137
If you have enabled intensity in the Scan Mode tab, you can use the Intensity setting to choose which
of the exposures the sensor uses for acquiring intensity data. This lets you choose the exposure that
produces the best image for intensity data.
2. Expand the Sensor panel by clicking on the panel header or the button.
7. Set the exposure level for each exposure to make the sensor's camera less or more sensitive, as required.
8. If Acquire Intensity is enabled in Scan Mode, select the exposure that is used to capture the intensity
output.
Spacing
The Spacing tab lets you configure settings related to spacing (sub-sampling and spacing interval).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 138
Sub-Sampling
Sub-sampling reduces the number of camera columns or rows that are used for laser profiling, reducing
the resolution. Reducing the resolution can increase speed or reduce CPU usage while maintaining the
sensor's field of view. Sub-sampling can be set independently for the X axis and Z axis.
The X sub-sampling setting is used to decrease the profile's X resolution to decrease sensor CPU usage.
The X setting works by reducing the number of image columns used for laser profiling.
The 1/4 sub-sampling setting is not available on Gocator 2100 series sensors.
The Z sub-sampling setting is used to decrease the profile's Z resolution to increase speed. The Z setting
works by reducing the number of image rows used for laser profiling.
Sub-sampling values are expressed as fractions in the Web interface. For example, an X sub-sampling
value of 1/2 indicates that every second camera column will be used for laser profiling.
The CPU Load bar at the top of the interface displays how much the CPU is being used.
Both the X and the Z sub-sampling settings must be decreased to increase speed.
To configure X or Z sub-sampling:
2. Expand the Sensor panel by clicking on the panel header or the button.
Spacing Interval
Spacing interval is the spacing between data points in resampled data. (In Profile mode, resampled data
is only produced if the Uniform Spacing option in the Scan Mode panel is checked.) A larger interval
creates profiles with lower X resolution, reduces CPU usage, and potentially increases the maximum
frame rate. A larger interval also reduces the data output rate. For more information on resampled data,
see Resampled Data and Point Cloud Data on page 68.
The Uniform Spacing option must be checked in the Scan Mode panel for the Spacing Interval
option to be displayed.
You can set the spacing interval either to one of three presets or set a custom value.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 139
To configure the spacing interval:
3. Expand the Sensor panel by clicking on the panel header or the button.
Speed: Uses the lowest X resolution within the active area as the spacing interval. This setting minimizes
CPU usage and data output rate, but the profile has the lowest X resolution (i.e., least detail).
Balanced: Uses the X resolution at the middle of the active area as the spacing interval. This setting
balances CPU load, data output rate, and X resolution.
Resolution: Uses the highest X resolution within the active area as the spacing interval. This setting
maximizes resolution but has higher CPU load and has the highest data output rate (i.e., greatest detail).
Advanced
The Advanced tab contains settings to configure material characteristics, camera gain, and dynamic
exposure.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 140
To configure advanced settings:
3. Expand the Sensor panel by clicking on the panel header or the button.
4. If you are configuring a dual- or multi-sensor system, click the button corresponding to the sensor you
want to configure.
The button is labeled Top, Bottom, Top-Left, or Top-Right, depending on the system.
Settings can be configured separately for each sensor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 141
Material
Data acquisition can be configured to suit different types of target materials. This helps maximize the
number of useful profile points produced. For many targets, changing the setting is not necessary, but it
can make a great difference with others.
For 2380 sensors (revision B or later), use the Sensitivity Compensation setting (not shown above) to
make the sensitivity of the sensor compatible with revision A sensors. This setting is enabled by default.
You can select preset material types in the Materials setting under the Advanced tab. The Diffuse
material option is suitable for most materials.
Setting Description
Spot Threshold The minimum increase in intensity level between neighbouring pixels for a pixel to be
considered the start of a potential spot.
This setting is important for filtering false spots generated by sunlight reflection.
Spot Width Max The maximum number of pixels a spot is allowed to span.
This setting can be used to filter out data caused by background light if the unwanted
light is wider than the laser and does not merge into the laser itself. A lower Spot
Width Max setting reduces the chance of false detection, but limits the ability to
detect features/surfaces that elongate the spot.
Various settings can affect how the Material settings behave. See Spots and Dropouts on page 170 for
more information.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 142
Setting Description
Camera Gain
Analog camera gain can be used when the application is severely exposure limited,
yet dynamic range is not a critical factor.
Digital camera gain can be used when the application is severely exposure limited, yet
dynamic range is not a critical factor.
Dynamic Exposure
Sensitivity controls the exposure that dynamic exposure converges to. The lower the
value, the lower the exposure the sensor will settle on.
The trade-off is between the number of underexposed spots and the possibility of
over-exposing.
Threshold is the minimum number of spots for dynamic exposure to consider the
profile point that make up the spot valid. If the number of spots is below this
threshold, the algorithm will walk over the allowed exposure range slowly to find the
correct exposure. Because this is slow, the Threshold value typically should be kept as
low as possible, so this slow search is not used.
These settings let you set tune how dynamic exposure settles on an exposure for a
scan. For more information on Dynamic Exposure, see Dynamic Exposure on page 136.
Alignment
Alignment procedures are required to compensate for sensor mounting inaccuracies or to set a Z
(height) reference plane. The alignment procedure also sets a common coordinate system for multi-
sensor systems, and determines the encoder resolution (if present) and the speed of the transport
system. (In many systems, the reference surface is a conveyor belt.)
Sensors are pre-calibrated and ready to deliver data in engineering units (mm) out of the box.
Alignment procedures do not affect sensor calibration.
A sensor can be in one of two alignment states: Unaligned and Aligned. An indicator on the Alignment
panel display UNALIGNED or ALIGNED, depending on the sensor's state.
Alignment State
State Explanation
Unaligned The sensor or sensor system is not aligned. Data points are reported in sensor
coordinates.
Aligned The sensor is aligned using the alignment procedure (described below) or by manually
modifying the values under Transformation in the Sensor tab on the Scan page (for
more information, see Transformations on page 133). Data points are reported in
system coordinates.
Once the alignment procedure has completed, the derived transformation values are displayed under
Transformations in the Sensor panel.
Alignment Types
Sensors support two types of alignment: stationary or moving.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 143
Type Description
Stationary Stationary is used when the alignment target does not move. This type of
alignment can only compensate for mounting inaccuracies in the laser plane (Z
offsets, and optionally X offsets and Y angle rotation). It is typically used when the
sensor will run in Profile mode.
Moving Moving is used when the alignment target moves beneath the sensor. This type
allows for Y offset and Z angle alignment, in addition to X and Z offset and Y angle
alignment. It is typically used when a sensor will run in Surface mode.
Aligning Sensors
Alignment is configured and performed using the Alignment panel.
With certain types of alignment, a Degrees of Freedom setting lets you choose the axes on which
offsets and rotations are calculated. If the setting is not available, only X and Z offsets, and Y angle
rotation, are calculated. That is, alignment is only performed within the profile plane. When the Degrees
of Freedom setting is available, it provides options that let you perform alignment outside the profile
plane. For more information, see the procedure on performing moving alignment.
1. Choose an alignment reference in the Manage page if you have not already done so.
For more information, see Alignment Reference on page 111.
3. Choose a mode other than Video mode in the Scan Mode panel.
4. Expand the Alignment panel by clicking on the panel header or the button.
5. Ensure that all sensors have a clear view of the target surface.
Remove any irregular objects from the sensor's field of view that might interfere with alignment. If
using a bar for a dual- or multi-sensor top-down or bottom-up system, ensure that the lasers illuminate
a reference hole on the bar.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 144
Press the Clear Alignment button to remove an existing alignment.
Configure the characteristics of the target (bar dimensions and reference hole layout). For details
on alignment targets, see Alignment Targets on page 30.
Degrees of Freedom: In stationary bar alignment, only one option is provided, namely, X, Z, Y
Angle. This setting aligns X and Z offsets, as well as rotation around the Y axis.
Height: The thickness of the bar in the Z direction. The alignment is performed to determine the
average Z height of the bar's top surface. This height value is used to offset the coordinate system
so that the bottom of the calibration bar becomes the Z origin.
Width: The width of the bar in the Y direction.
l Polygon: Use this to align a ring layout setup using a polygon-shaped alignment target. Polygon
target alignment is typically used when you need to scan 360 degrees around a target.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 145
To perform polygon target alignment, you must set the X and Z coordinates of each corner of the
alignment target. The coordinates are relative to the target itself, and you typically set them such
that the X and Z origins are at the center of the target.
To properly configure the X and Z values of each corner of the alignment target (and assign
sensors to the corners), you must view the sensors and alignment target so that Y increases toward
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 146
you. To determine how to view the sensors and target, refer to the coordinate system orientation
information for your sensor model in Sensors on page 847. (If any sensors are defined as Reversed
in the layout grid, use only the non-reversed sensors to determine how to view the sensors; for
more information, see Layout on page 101.)
For each corner, define the X and Z coordinates and assign the sensor that is viewing that corner,
proceeding in a clockwise order. You can start with any corner.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 147
You are not required to assign a sensor to every corner.
Alignment uses the exposure defined for single exposure mode, regardless of the
current exposure mode.
l If the system does not use an encoder, configure travel speed. See Travel Speed on page 112 for
more information.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 148
2. In the Alignment panel, select Moving as the Type.
Configure the characteristics of the target (bar dimensions and reference hole layout); for details
on alignment bars, see Alignment Targets on page 30.
Degrees of Freedom: In moving bar alignment, three options are available, which are
combinations of different types of alignments. X, Y, and Z compensate for offsets on the X, Y, and Z
axes, respectively. Y Angle and Z Angle compensate for rotation around the Y and Z axes,
respectively. Compensating for X angle rotation is currently only possible by manually setting the
rotation in the Transformations panel.
On sensors aligned using Z angle or X angle, and to a lesser extent Y offset, CPU
usage increases when scanning, which reduces the maximum scan speed.
Artifacts may appear in scan data on sensors aligned using Z angle or X angle if
encoder trigger spacing is set too high (resulting in a low sampling rate).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 149
When aligning using X, Y, Z, Y Angle or X, Y, Z, Y Angle, Z Angle, you can improve
alignment accuracy by reducing the motion speed of the target. Repeat alignment
at lower speeds and observe the transformation values in the Sensor panel to
achieve maximum accuracy.
Alignment uses the exposure defined for single exposure mode, regardless of the
current exposure mode.
When using an alignment bar, there can be at most one hole in each sensor's field of view.
Encoder Calibration
For systems that use an encoder, encoder calibration can be performed while aligning sensors. The table
below summarizes the differences between performing alignment with and without encoder calibration.
Target Type Calibration disk or calibration bar Flat surface or calibration bar
Target/Sensor Motion Linear motion Stationary
Calibrates Tilt Yes Yes
Calibrates Z axis Offset Yes Yes
Calibrates X axis Offset Yes Yes (Calibration bar required)
Calibrates Encoder Yes No
Calibrates Travel Speed Yes No
See Coordinate Systems on page 63 for definitions of coordinate axes. See Alignment Targets on page 30
for descriptions of calibration disks and bars.
See Aligning Sensors on page 144 for the procedure to perform alignment. After alignment, the
coordinate system for laser profiles will change from sensor coordinates to system coordinates.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 150
Clearing Alignment
Alignment can be cleared to revert the sensor to sensor coordinates.
To clear alignment:
2. Expand the Alignment panel by clicking on the panel header or the button.
Filters
Filters are used to post-process scan data along the X or Y axis to remove noise or clean it up before it is
output or is used by measurement tools.
In some situations, such as when Uniform Spacing is disabled or when a sensor does not support
filters, the filters panel is not displayed.
Filter Description
Gap Filling Fills in missing data caused by occlusions using information from the nearest neighbors.
Gap filling also fills gaps where no data is detected, which can be due to the surface
reflectivity, for example dark or specular surface areas, or to actual gaps in the surface.
Median Substitutes the value of a data point with the median within a specified window around
the data point.
Filters are applied in the order displayed in the table above. The filters are configured in the Filters panel
on the Scan page.
Gap Filling
Gap filling works by filling in missing data points using either the lowest values from the nearest
neighbors or linear interpolation between neighboring values (depending on the Z difference between
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 151
neighboring values), in a specified X or Y window. The sensor can fill gaps along both the X axis and the Y
axis. X gap filling works by filling in the gaps within the same profile. Y gap filling works by filling in gaps in
the direction of travel at each X location.
If both X and Y gap filling are enabled, missing data is filled along the X and Y axes at the same time, using
the available neighboring data.
In Profile mode, Gap Filling is limited to the X axis. (The Y setting is not available.)
3. Expand the Filters panel by clicking on the panel header or the button.
Median
The Median filter substitutes the value of a data point with the median calculated within a specified
window around the data point.
Missing data points will not be filled with the median value calculated from data points in the
neighbourhood.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 152
To configure X or Y median:
3. Expand the Filters panel by clicking on the panel header or the button.
Smoothing
Smoothing works by substituting a data point value with the average value of that data point and its
nearest neighbors within a specified window. Smoothing can be applied along the X axis or the Y axis. X
smoothing works by calculating a moving average across samples within the same profile. Y smoothing
works by calculating a moving average in the direction of travel at each X location.
If both X and Y smoothing are enabled, the data is smoothed along X axis first, then along the Y axis.
Missing data points will not be filled with the mean value calculated from data points in the
neighbourhood.
To configure X or Y smoothing:
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 153
2. Choose a mode other than Video in the Scan Mode panel.
Otherwise, you will not be able to configure smoothing.
3. Expand the Filters panel by clicking on the panel header or the button.
Decimation
Decimation reduces the number of data points along the X or Y axis by choosing data points at the end
of a specified window around the data point. For example, by setting X to .2, only points every .2
millimeters will be used.
To configure X or Y decimation:
3. Expand the Filters panel by clicking on the panel header or the button.
Surface Generation
The sensor can generate a surface by combining a series of profiles gathered along the direction of
travel.
The sensor uses different methods to generate the data, depending on the needs of the application.
Data generation is configured in the Surface Generation panel on the Scan page.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 154
The types in the table below correspond to the Type setting in the panel.
When Type is set to Continuous, part detection is automatically enabled. When Type is set to
any of the other settings, part detection can be enabled and disabled in the Part Detection
panel. For descriptions of the settings that control part detection logic, Part Detection on
page 158.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 155
are available under Start Trigger:
o Sequential: Continuously
generates back-to-back fixed
length surfaces.
o External Input: A pulse on the
digital input triggers the
generation of a single surface of
fixed length.
o Software: Allows starting fixed
length surfaces on command
from PLC or PC.
For more information on
connecting external input to a
sensor, see Digital Input on
page 899.
You can optionally enable part
detection to process the surface
after it has been generated, but the
generation itself does not depend
on the detection logic. To do this,
check Enabled in the Part
Detection panel.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 156
sensor, see Digital Input on
page 899.
You can optionally enable part
detection to process the surface
after it has been generated, but the
generation itself does not depend
on the detection logic. To do this,
check Enabled in the Part
Detection panel.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 157
You can optionally enable part
detection to process the surface
after it has been generated, but the
generation itself does not depend
on the detection logic. To do this,
check Enabled in the Part
Detection panel.
1. Go to the Scan page and choose Surface in the Scan Mode panel.
If this mode is not selected, you will not be able to configure surface generation.
2. Expand the Surface Generation panel by clicking on the panel header or the button.
3. Choose an option from the Type drop-down and any additional settings.
See the types and their settings described above.
Part Detection
In Surface mode, a sensor can analyze scan data to identify discrete objects. Surface measurements can
then be performed on each object. Part detection is configured using the Part Detection panel on the
Scan page.
Part detection must be manually enabled when Type is set to Fixed Length, Variable Length, or
Rotational in the Surface Generation panel. When Type is set to Continuous, part detection is
always enabled.
Part detection can be performed when Source in the Trigger panel is set to Time or Encoder. To use
the Time trigger source, the travel speed must be calibrated. To use the Encoder trigger source, the
encoder resolution must be calibrated. See Aligning Sensors on page 144 for more information.
Multiple parts can pass through the laser at the same time and will be individually tracked. Parts can be
separated along the laser line (X axis), in the direction of travel (Y axis), or by gated external input.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 158
The following settings can be tuned to improve the accuracy and reliability of part detection.
Setting Description
Height Threshold Determines the profile height threshold for part detection. The setting for Threshold
Direction determines if parts should be detected above or below the threshold. Above is
typically used to prevent the belt surface from being detected as a part when scanning
objects on a conveyor.
In an Opposite layout, the threshold is applied to the difference between the top and the
bottom profile. A target thinner than the threshold value is ignored, including places where
only one of either top or bottom is detected.
To separate parts by gated external input, set the Height Threshold to the active area Z
offset (i.e., minimum Z position of the current active area), set Source to Time or Encoder
and check the Gate on External Input checkbox in the Trigger panel (page 123).
Include one-sided data The option is only displayed with dual-sensor systems in Opposite layout, or multi-sensor
systems in Grid layout with at least one sensor in the Bottom row. When the option is
disabled, data points from a sensor are excluded if the points directly opposite from the
other sensor are missing (due to occlusions, drop-outs, and so on). When the option is
enabled, data points are included even if data points from the other sensor are missing.
The following image shows surface data from a dual-sensor system in which the sensors
are mounted facing each other. In this case, Include one-sided data is disabled.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 159
Setting Description
The data on the upper left is missing, due to the shape of the target: getting data from this
area is difficult or impossible, due to occlusions or simply because this part of the upper
surface is beyond the top sensor's measurement range. Data is missing on the left of the
lower surface, even though the target is flat in this area.
In the following image, Include one-sided data is enabled. The result is that data from
the lower left is included in the scan data, better representing the actual target. (The same
situation is occurring on the right side of the surfaces.)
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 160
Setting Description
Threshold Direction Determines if parts should be detected above or below the height threshold.
Gap Width Determines the minimum separation between objects on the X axis. If parts are closer than
the gap interval, they will be merged into a single part.
Gap Length Determines the minimum separation between objects on the Y axis. If parts are closer than
the gap interval, they will be merged into a single part.
Padding Width Determines the amount of extra data on the X axis from the surface surrounding the
detected part that will be included. This is mostly useful when processing part data with
third-party software such as HexSight, Halcon, etc.
Padding Length Determines the amount of extra data on the Y axis from the surface surrounding the
detected part that will be included. This is mostly useful when processing part data with
third-party software such as HexSight, Halcon, etc.
Min Area Determines the minimum area for a detected part. Set this value to a reasonable minimum
in order to filter out small objects or noise.
Max Part Length Determines the maximum length of the part object. When the object exceeds the
maximum length, it is automatically separated into two parts. This is useful to break a long
object into multiple sections and perform measurements on each section.
Sensor
When Frame of Reference is set to Sensor, the sensor's frame of reference is used. The
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 161
Setting Description
way the sensor's frame of reference is defined changes depending on the surface
generation Type setting ( and Surface Generation on page 154 for more information):
l When parts are segmented from a continuous surface (the surface generation Type
setting is set to Continuous), measurement values are relative to a Y origin at the
center of the part (the same as for Part frame of reference; see below).
l When parts are segmented from other types of surfaces (the surface generation Type
setting is set to Fixed Length, Variable Length, or Rotational ), measurement
values are relative to a Y origin at the center of the surface from which the part is
segmented.
The Surface Bounding Box GlobalX and GlobalY measurements (see Bounding Box on page
312) are exceptions: regardless of the Frame of Reference setting, these measurements
produce the Sensor frame of reference values of the Part frame of reference origin (which
is the bounding box center), except for GlobalY when parts are segmented from
continuous surfaces. In this case the GlobalY value is the Y value relative to the encoder
zero position. These values can be used to locate Part frame of reference measurements in
a world space.
Part
When Frame of Reference is set to Part, all measurements except Bounding Box X and Y
are relative to the center of the bounding box of the part. For Bounding Box X and Y, the
measurement values are always relative to the sensor frame of reference (see Bounding
Box on page 312).
Status Provides details on the status of the part detection engine. For more information, see Part
Detection Status.
Edge Filtering See Edge Filtering on page 164.
1. Go to the Scan page and choose Surface in the Scan Mode panel.
If this mode is not selected, you will not be able to configure part detection.
2. Expand the Part Detection panel by clicking on the panel header or the button.
3. If necessary, check the Enabled option.
When Surface Generation is set to Continuous, part detection is always enabled.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 162
The following part detection status information is available:
Tracking State Part detection state for largest currently tracking part. One
of the following:
l Not In Part
l In Part, Min area not achieved
l In Part, Min area achieved
l In Gap, Min area not achieved
l In Gap, Min area achieved
Parts Being Tracked The number of parts the engine is currently tracking.
Part Center X The center of the partial part, midway between the
minimum X and maximum X detected for the part.
Part Length The length of the part. In cases of backtracking, the number
decreases.
Total Parts Accepted The number of parts that meet the part detection criteria.
Due to Max Part Length The number of parts accepted because they have reached
Max Part Length. If too many parts are being accepted,
increase Max Part Length.
Total Parts Rejected The number of parts that fail to meet the part detection
criteria.
Due to Min Area The number of parts rejected because they are below Min
Area. If too many parts are being rejected, reduce Min Area.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 163
Edge Filtering
Part scans sometimes contain noise around the edges of the target. This noise is usually caused by the
sensor’s light being reflected off almost vertical sides, rounded corners, etc. Edge filtering helps reduce
edge noise in order to produce more accurate and repeatable volume and area measurements, as well as
to improve positioning of relative measurement regions. Optionally, the Preserve Interior Feature
setting can be used to limit filtering to the outside edges of the target.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 164
To configure edge filtering:
1. Go to the Scan page and choose Surface in the Scan Mode panel.
If this mode is not selected, you will not be able to configure part detection.
2. Expand the Part Detection panel by clicking on the panel header or the button and enable part
detection if necessary.
Part detection can be enabled and disabled when Type in the Surface Generation panel is set to Fixed
Length, Variable Length, or Rotational. Part detection is automatically enabled when Type is set to
Continuous.
Data Viewer
The data viewer can display video images, profiles, sections, surfaces, height maps, and intensity images.
It is also used to configure the active area (Active Area on page 129) and measurement tools (see
Measurement and Processing on page 201). The data viewer changes depending on the current
operation mode and the panel that has been selected.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 165
For more information on the kinds of data displayed in Surface mode, see Surface Mode on page 173.
When the sensor displays profiles, a safety goggle mode button ( ) is available above the data viewer.
Enabling this mode changes some colors to ensure that profiles are visible in the data viewer when
wearing laser safety goggles. The option is also available in Surface mode when a section is displayed.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 166
When multiple exposures have been defined, you can use the Multiple Exposures button ( ) to toggle
between showing a single-color profile made up of data from all exposures, and a profile in which the
source exposure of the data points is identified by a different color.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 167
Video Mode
In Video mode, the data viewer displays images directly from the sensor's camera or cameras. In a dual-
or multi-sensor system, camera images from any camera can be displayed.
In this mode, you can configure the data viewer to display exposure, spot, and dropout information that
can be useful in properly setting up the system for scanning.
Exposure Information
In Video mode, you can display exposure-related information. This information can help you correctly
adjust the exposure settings.
Exposures
If you have set Exposure Mode to Multiple, and have set more than one exposure, a drop-down at the
top of the data viewer lists the available exposures. Choosing an exposure changes the view of the data
viewer to that exposure.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 168
For details on setting exposure in the Exposure tab in the Sensor panel, see Exposure on page 134.
1. Go to the Scan page and choose Video mode in the Scan Mode panel.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 169
The Exposure setting uses the following colors:
To display an overlay:
1. Go to the Scan page and choose Video mode in the Scan Mode panel.
In the image below, the white and gray squares represent the laser line as it appears on the camera
sensor. Spots (which represent the center of the laser line on the camera sensor for each column) are
displayed as red "x" symbols. Dropouts (where no spot is detected on the camera sensor in a given
column) are depicted at the upper edge of the data viewer as yellow dots.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 170
To show data dropouts:
1. Go to the Scan page and choose Video mode in the Scan Mode panel.
2. check the Show Dropouts option at the top of the data viewer.
Profile Mode
When the sensor is in Profile scan mode, the data viewer displays profile plots.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 171
In a dual-sensor system, profiles from individual sensors or from a combined view can be displayed.
Similarly, in a multi-sensor system, profiles from individual sensors or from combined views can be
displayed.
When in the Scan page, selecting a panel (e.g., Sensor or Alignment panel) automatically sets the
display to the most appropriate display view.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 172
To manually select the display view in the Scan page:
In the Measure page, the view of the display is set to the profile source of the selected measurement
tool.
Surface Mode
When the sensor is in Surface scan mode, the data viewer can display height maps, sections, and
intensity images. You can select the data to display from the first drop-down.
Surface Displays surface data received from the sensor's scan engine.
Profile Displays the last collected profile. (Only available in 2D view. Only displays data on physical
sensors: in the emulator, no data is displayed.)
Section If any sections have been defined, displays the section selected in the Sections drop-down.
(Only available in 2D view.)
Tool Displays data from tools capable of producing "tool data" output (such as Surface Stitch or
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 173
Data Type Option or
Description
Button
Surface Track). When you select Tool , a second drop-down is displayed next to the first,
which lets you choose among the available data.
For more information on tool data output, see Tool Data on page 78.
Uniform button Overlays a uniform shaded surface on the 3D model. (Only available in 3D view.)
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 174
2D viewer with intensity overlay
Choosing the Profile view option will switch the data viewer out of the 3D viewer and display a profile.
Clicking the 3D button toggles between the 2D and 3D viewer. The 3D model is overlaid with the
information that corresponds to the selected View option.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 175
3D viewer with uniform overlay 3D viewer with uniform overlay
In 3D mode, you can choose how the data viewer renders the model:
Point Cloud (default) Renders 3D models using point clouds. Useful in scan data that contains noise around edges,
and shows hidden structure.
In a multi--sensor system, data from individual sensors or from a combined view can be selected. While
in the Scan page, selecting a panel (e.g., Sensor or Part Detection panel) will automatically set the
display to the most appropriate display type and display view.
To manually select the display type and the display view in the Scan page:
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 176
To change the scaling of the height map:
l To automatically set the scale based on a user-selected sub-region of the heightmap, choose Auto
- Region in the Range drop-down and adjust the yellow region box in the data viewer to the desired
location and size.
l To manually set the scale, choose the Manual in the Range drop-down and enter the minimum
and maximum height to which the colors will be mapped.
Sections
When the sensor is in Surface scan mode, the data viewer can display sections (profiles extracted from
surfaces).
In a multi-sensor system, profiles from individual sensors or from a combined view can be displayed.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 177
When in the Scan page, selecting a panel (e.g., Sensor or Alignment panel) automatically sets the
display to the most appropriate display view.
3. Just above the data viewer, choose Section in the View drop-down.
The view from an individual sensor or the combined view of two sensors can be selected from the drop-
down list at the top of the data viewer.
Top: View from a single sensor, from the top sensor in an opposite-layout dual-sensor system, or the
combined view of sensors that have been aligned to use a common coordinate system.
Bottom: View from the bottom sensor in an opposite-layout dual-sensor system.
Left: View from the left sensor in a dual-sensor system.
Right: View from the right sensor in a dual-sensor system.
Left & Right: Views from both sensors, displayed at the same time in the data viewer, using the
coordinate systems of each sensor.
3. Just above the data viewer, choose Section in the View drop-down.
The view from an individual sensor or the combined view of two sensors can be selected from the drop-
down list at the top of the data viewer.
Top: View from a single sensor, from the top sensor in an opposite-layout dual-sensor system, or the
combined view of sensors that have been aligned to use a common coordinate system.
Bottom: View from the bottom sensor in an opposite-layout dual-sensor system.
Left: View from the left sensor in a dual-sensor system.
Right: View from the right sensor in a dual-sensor system.
Left & Right: Views from both sensors, displayed at the same time in the data viewer, using the
coordinate systems of each sensor.
In the Measure page, the view of the display is set to the profile source of the selected measurement
tool.
Region Definition
Regions, such as an active area or a measurement region, can be graphically set up using the data viewer.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 178
When the Scan page is active, the data viewer can be used to graphically configure the active area. The
Active Area setting can also be configured manually by entering values into its fields and is found in the
Sensor panel (see Sensor on page 129).
2. Drag the rectangle to move it, and use the handles on the rectangle's border to resize it.
Intensity Output
Sensors can produce intensity images that measure the amount of light reflected by an object. An 8-bit
intensity value is output for each range value along the laser line . A sensor applies the same coordinate
system and resampling logic as the ranges to the intensity values.
To be able to display intensity data, you must enabled Acquire Intensity in the Scan Mode
panel.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 179
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 180
Models
The following sections describe how to set up part matching using a model, a bounding box, or an ellipse.
It also describes how to configure sections.
Element Description
1 Part Matching Contains settings for configuring models and for part matching.
panel
2 Sections panel Contains settings for configuring sections, which let you extract profiles from surfaces.
3 Data Viewer Displays sensor data and lets you add and remove model edge points.
Part Matching
The sensor can match scanned parts to the edges of a model based on a previously scanned part (see
Using Edge Detection on page 182) or to the dimensions of a fitted bounding box or ellipse that
encapsulate the model (see Using Bounding Box and Ellipse on page 191). When parts match, the sensor
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 181
can rotate scans so that they are all oriented in the same way. This allows measurement tools to be
applied consistently to parts, regardless of the orientation of the part you are trying to match.
When the match quality between a model and a part reaches a minimum value (a percentage), or the
bounding box or ellipse that encapsulates the part is between minimum and maximum dimension
values, the part is "accepted" and any measurements that are added in the Measure page will return
valid values, as long as the target is in range, etc. If the part is "rejected," any measurements added in the
Measure page will return an Invalid value. For more information on measurements and decision values,
Measurement and Processing on page 201.
In the data viewer, a model is represented as a yellow outline. The target is represented as a blue outline.
If the part match quality above a minimum user-defined level, any measurements configured on the
Measure page are applied.
When you create a model, the sensor runs an edge detection algorithm on either the heightmap or
intensity image of a scanned part. The resulting model is made up of the detected edge points. The scan
used to create the model should be of a reference (or "golden") part to which all other parts will be
compared.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 182
After the model has been created, you optionally modify the model by adjusting the sensitivity (how
many edge points are detected), or selectively remove edge points from the model, to improve
matching.
Once you have finished modifying the model, you can also modify target sensitivity, which controls how
many edge points are detected on the subsequently scanned targets that will be compared to the
model; the same edge detection algorithm used for creating models is used to compare a model to a
part.
Typically, setting up edge detection to perform part matching involves the following steps:
1. Scan a reference part (you can also use replay data that you have previously saved).
2. Create a model based on the scan (using either heightmap or intensity data).
3. Adjust the model (edge detection algorithm sensitivity and selective removal of edge points).
4. Scan another part typical of the parts that would need to match the model.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 183
Model Editing tab on Part Matching panel
The following settings are used to configure part matching using edge detection.
Setting Description
Match Algorithm Determines which algorithm the sensor will use to attempt a match. Set this to
Edge for edge detection.
Image Type Determines what kind of data the sensor will use to detect edges and therefore
for part matching. Choose this setting based on the kinds of features that will be
used for part matching:
Heightmap : Surface elevation information of the scanned part will be used to
determine edges. This setting is most commonly used.
Intensity: Intensity data (how light or dark areas of a scanned part are) will be
used to determine edges. Use this setting if the main distinguishing marks are
printed text or patterns on the parts. The Acquire Intensity option must be
checked in the Scan Mode panel on the Scan page for this option to be
available.
Z Angle Corrects the orientation of the model to accurately match typical orientation and
simplify measurements.
Target Sensitivity (Target Controls the threshold at which an edge point is detected on the target's
Matching tab) heightmap or intensity image. (The "target" is any part that is matched to the
model and which will subsequently be measured if the match is accepted.)
Setting Target Sensitivity higher results in more edge points. Setting it lower
results in fewer edge points and results in higher performance. Use this setting
to exclude noise from the detected edges and to make sure distinguishing
features are properly detected.
The level of this setting should generally be similar to the level of Model
Sensitivity.
Model Sensitivity Controls the threshold at which an edge point is detected on the heightmap or
(Model Editing tab) intensity image used to create the model. Setting Model Sensitivity higher
results in more edge points. Setting it lower results in fewer edge points and
results in higher performance. Use this setting to exclude noise from the
detected edges and to make sure distinguishing features are properly detected.
The level of this setting should generally be similar to the level of Target
Sensitivity.
Changing this setting causes the edge detection algorithm to run again at the
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 184
Setting Description
new threshold. If you have edited edge points manually (removing them
selectively), those changes will be lost. See Using Edge Detection on page 182 for
more information.
Edge Points The Edit button lets you selectively remove edge point that are detected by the
(Model Editing tab) edge detection algorithm at the current Model Sensitivity setting. See Using
Edge Detection on page 182 for more information.
Acceptance Criteria Determines the minimum quality level of the match as a percentage value.
To run part matching, simply make sure that the Enabled option is checked on the Part Matching
panel when the sensor is running. Any measurements that are added and configured on the Measure
page will be applied to parts if a part match is accepted, regardless of the part's orientation (a
successfully matched part is rotated to match orientation of the model), returning a value and decision
(as long as the part is in range, etc.). If a part match is rejected, measurements will return an Invalid
value.
Creating a Model
Gocator creates a model by running an edge detection algorithm on the heightmap or intensity image of
a scan. The algorithm is run when a model is first created and whenever the Model Sensitivity setting is
changed.
To create a model:
1. Go to the Scan page.
a. In the Scan Mode panel, choose Surface.
You must choose Surface in order to scan a part. Furthermore, the Model page is only displayed in
Surface mode.
b. If you want to use intensity data to create the model, make sure Acquire Intensity is checked.
c. In the Part Detection panel, choose Part for the Frame of Reference.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 185
Part matching is only available when Part has been selected.
l Locate some previously recorded replay data and load it. See Recording, Playback, and Measurement Sim-
ulation on page 88 and Downloading, Uploading, and Exporting Replay Data on page 92 for more inform-
ation on replay data.
After adding the model, the sensor will show that the match quality is 100%, because it is in
effect comparing the model to the scan that was used to create the model. This value can
be ignored.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 186
7. If you need to correct the orientation of the model, provide a value in the Z Angle field.
Correcting the Z angle is useful if the orientation of the model is not close to the typical angle of target parts
on the production line.
To rename a model:
1. In the Models list, double-click on a model name.
First, you can control the overall number of edge points that are detected by the edge detection
algorithm by raising and lowering the edge detection threshold (the Model Sensitivity setting).
Modifying Model Sensitivity causes the edge detection algorithm to run again.
Second, you can fine-tune the model's edge points by selectively removing edge points that are detected
by the edge detection algorithm. This could be useful, for example, if an edge on the target parts
frequently presents minor variations such as flashing (excess material caused by leakage during
molding): the edge points that make up the model can be edited to exclude that region. Editing the
model can allow parts to match it more easily.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 187
Edge points along top of model not removed.
Part is rejected. (Min set to 85%.)
Removing edge points does not cause the edge detection algorithm to run again.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 188
2. Click the Model Editing tab.
3. Adjust the Model Sensitivity slider to exclude noise and to properly detect the distinguishing features that
will match parts.
You can also set the sensitivity value manually in the provided text box.
3. On the toolbar above the data viewer, make sure the Select tool is active.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 189
4. Click in the data viewer and hold the mouse button while moving the pointer over the edge points you want
to remove.
Points within the circular Select tool are removed from the model. Removed edge points turn red in the data
viewer.
You can zoom in to see individual edge points by using the mouse wheel or by using the Zoom mode ( ).
5. If you have removed too many edge points, use Ctrl + Click in the data viewer to add the edge points back.
6. When you have finished editing the model, click Save in the Model Editing tab.
Much in the same way that you can adjust a model's sensitivity, you can adjust the target sensitivity, that
is, the threshold at which edge points are detected on the heightmaps or intensity images of parts that
you want to match to the model. Adjusting the target sensitivity is useful to exclude noise, improving
part matching.
2. Adjust the Target Sensitivity setting to exclude noise in order to properly detect the distinguishing features
that will allow parts to match.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 190
You can also set the sensitivity value manually in the provided text box.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 191
In the data viewer, a bounding box or ellipse is displayed with a blue outline. If a part fits in the bounding
box or ellipse, any measurements configured on the Measure page are applied.
Typically, setting up a bounding box or an ellipse to perform part matching involves the following steps:
1. Scan a reference part (you can also use replay data that you have previously saved).
2. Set the characteristics of the bounding box (width and length) or ellipse (major and minor axes).
The following settings are used to configure part matching using a bounding box or ellipse.
Setting Description
Match Algorithm Determines which algorithm the sensor will use to attempt a match. Set this to
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 192
Setting Description
You must choose Surface in order to scan a part. Furthermore, the Model page is only displayed in
Surface mode.
Intensity data is not used when part matching using a bounding box or an ellipse, but you can enable the
Acquire Intensity option if you need intensity data for other reasons.
b. In the Part Detection panel, choose Part for the Frame of Reference.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 193
Part matching is only available when Part has been selected.
l Locate some previously recorded replay data and load it. See Recording, Playback, and Measurement Sim-
ulation on page 88 and Downloading, Uploading, and Exporting Replay Data on page 92 for more inform-
ation on replay data.
4. Set Min and Max of both of the dimensions of the selected match algorithm shape, taking into account
expected acceptable variations.
l If you chose Bounding Box for the match algorithm, select Width and then Length in Match Result, set-
ting the minimum and maximum values acceptable for each dimension.
l If you chose Ellipse for the match algorithm, select Minor and then Major in Match Result, setting the
minimum and maximum values acceptable for each dimension.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 194
Using Part Matching to Accept or Reject a Part
Part matching results only determine whether a measurement is applied to a part. Whether the
measurement returns a pass or fail value—its decision—depends on whether the measurement's value
is between the Min and Max values set for the measurement. This decision, in addition to the actual
value, can in turn be used to control a PLC for example. The part matching "decision" itself is not passed
to the Gocator output, but you can simulate this by setting up a measurement that will always pass if it is
applied.
For example, you could set up a Position Z measurement, choosing Max Z as the feature type, and
setting the Min and Max values to the measurement range of the sensor. This way, as long as a part
matches and the target is in range, etc., the measurement will pass. This measurement decision, which is
passed to the Gocator's output, could in turn be used to control a PLC.
Sections
In Surface mode, the sensor can also extract a profile from a surface or part using a line you define on
that surface or part. The resulting profile is called a “section.” A section can have any orientation on the
surface, but its profile is parallel to the Z axis.
You can't create sections from the Models page on surface data that is produced by other tools,
such as Surface Stitch. You can however create sections on any kind of surface data using the
Surface Section tool; for more information, see Section on page 419.
You can use most profile measurement tools on a section: you can't use tools that work with
unresampled data. Using sections and the profile measurements, you can therefore use measurements
that are not otherwise possible in Surface mode, for example:
On the Output page, in Surface mode, you can output both surface measurements and section-based
profile measurements at the same time. The sensor can also output the surfaces and section profiles
themselves at the same time.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 195
Part in data viewer (3D view)
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 196
Circle Radius measurement running on profile extracted
from surface using defined section
You can configure the sampling distance between points along the section. Reducing the sampling
distance reduces the resolution of the profile, but increases the sensor’s performance and results in less
data being sent over the output.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 197
Maximum spacing interval: lowest profile resolution,
lower sensor CPU usage and data output
Using a higher spacing interval can produce different measurement results compared to using
a smaller spacing interval. You should therefore compare results using different spacing
intervals before using sections in production.
The sections you add to a surface are directional, and their start and end points are defined using X and Y
coordinates. The start point always corresponds to the leftmost point on the extracted profile, whereas
the end point always corresponds to the rightmost point on the extracted profile, no matter the
orientation of the section on the surface.
Creating a Section
Before you create a section, you should first scan a target in Surface mode to create a surface on which
you can create the section. You can use either live data or recorded data.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 198
After creating a section, the following settings are available:
Setting Description
Spacing Interval Determines the space between the points of the extracted profile.
Auto: The highest resolution, calculated using the X and Y resolution of the scan.
Custom: Lets you set the spacing interval by using a slider or setting the value
manually.
Section Lets you manually set the X and Y coordinates of the start and end points of the
section.
Setting the coordinates manually is useful if you need to create a section that is
perfectly horizontal or vertical. For example, to create a horizontal section, copy the
Y value of either the start or end point to the other point's Y field.
You can reverse the start and end points by clicking the button.
To reset the start and end points to their initial values, click the button.
To create a section:
1. On the Scan page, in the Scan Mode panel, click Surface.
4. Move the section and adjust the start and end points of the section to extract the desired profile.
You can move or adjust the section graphically in the data viewer, or you can manually adjust the X and
Y coordinates of the section.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 199
After you create a section, the profile measurement tools become available in the Tools panel on the
Measure page. If you have created more than one section, you must select it in the tool. For more
information on profile measurement tools, see Profile Measurement on page 225.
The sensor also adds a Section option to the View drop-down above the data viewer, which lets you
view an extracted profile, as well as a section selector drop-down for cases where multiple sections are
defined.
Sections are also added to the Stream drop-down in Profile and Feature tools.
If parts are not consistently oriented in the same way from scan to scan, you can use part matching to
correct their rotation, if the entire part is visible in the scan. Parts will then be consistently oriented, and
sections will fall on the same area on each part. You can also use anchoring to ensure that
measurements are consistently placed on a part.
Deleting a Section
When you delete a section, the sensor removes any associated measurements. After you remove the last
section, the sensor no longer displays profile measurement tools in the Tools panel.
To delete a section:
1. On the Scan page, in the Scan Mode panel, click Surface.
2. On the Model page, in the Section panel, click the button of the section you want to delete.
You may need to click the button to expand the panel.
If you have associated a measurement tool to the section by setting the tool's Stream setting to the section,
the sensor asks if you want to delete all of the associated measurement tools.
The sensor deletes the section on the surface.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 200
Measurement and Processing
The following sections describe Gocator's measurement and processing tools.
The content of the Tools panel in the Measure page depends on the current scan mode. In Profile
mode, the Measure page displays tools for profile measurement. In Surface mode, the Measure page
displays tools for surface measurement. If you have defined a section in Surface mode, profile tools are
also displayed. In Video mode, tools are not available.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 201
Element Description
1 Tools panel Used to add, manage, and configure tools and measurements (see Tools Panel on the
next page) and to choose anchors (Measurement Anchoring on page 216).
2 Data Viewer Displays video and scan data, sets up tools, and displays result calipers related to the
selected measurement.
Parts are displayed using a height map, which is a top-down view of the XY plane,
where color represents height.
3 Feature Area Configurable region of interest from which feature points are detected. These feature
points are used to calculate the measurements. The number of feature areas
displayed depends on which measurement tool is currently selected.
Data Viewer
When the Measure page is active, the data viewer can be used to graphically configure measurement
regions. Measurement regions can also be configured manually in measurements by entering values into
the provided fields (see Regions on page 206).
For information on controls in the data viewer, see Data Viewer Controls on page 165.
For instructions on how to set up measurement regions graphically, see Region Definition on page 178.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 202
Tools Panel
The Tools panel lets you add, configure, and manage measurement tools. Tools contain related
measurements. For example, the Dimension tool provides Height, Width, and other measurements.
Some settings apply to tools, and therefore to all measurements; these settings are found in the
Parameters tab below the list of tools. Other settings apply to specific measurements, and are found in
a Parameters tab below the list of measurements; not all measurements have parameters.
See Profile Measurement on page 225 and Surface Measurement on page 301 for information on the
measurement tools and their settings.
Tool names in the user interface include the scan mode, but not in the manual. So for example, you
will see "Profile Area" or "Surface Bounding Box" in the user interface, but simply "Area" or
"Bounding Box" in the manual.
4. In the Tools panel, select the tool you want to add from the drop-down list of tools.
6. (Optional) If you are running a dual-sensor system, choose the sensor that will provide data to the
measurement tool in Source.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 203
For more information on sources, see Source on the next page.
7. (Optional) If the measurement is a profile measurement running on a section, and you have created
more than one section, choose the section that will provide data to the measurement in Stream.
For more information on streams, see Stream below.
Stream
It's possible for more than one type of data to be available for a tool as input. You use the Stream drop-
down in a tool to choose which type. If only one type of data is available for a tool, the Stream drop-
down may not be displayed.
For example, many tools can produce processed surface data (such as the Stitched Surface output from
the Surface Stitch tool, or the Corrected Surface output from the Surface Vibration Correction tool).
When you have added one of these tools, the tool's data output is listed in the Stream drop-down, as
well as the data that comes directly from the sensor's scanning engine. Surface data coming directly
from the sensor's scan engine is always called "Surface" in the Stream drop-down. Profile data coming
directly from the sensor's scan engine is always called "Profile/Merged" in the Stream drop-down. For
data that comes from another tool, the convention is {Tool name}/{Data output name}:
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 204
Sections are also listed in the Stream setting.
To choose a stream:
The scan mode must be set to the type of measurement you need to configure.
Otherwise, the wrong tools, or no tools, will be listed on the Measure page.
3. If it is not already selected, click the Parameter tab in the tool configuration area.
Source
For dual- or multi-sensor systems, you must specify which sensor, or combination of sensors, provides
data for a measurement tool.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 205
The Source setting applies to all of a tool's measurements.
Depending on the layout you have selected, the Source drop-down will display one of the following (or a
combination). For more information on layouts, see Layout on page 101.
Setting Description
In a dual-sensor system, refers to the Main sensor in Opposite layout, or to the combined
data from both the Main and Buddy sensors.
In a multi-sensor system, refers to the combined data from all sensors in the top row of the
layout grid.
In a multi-sensor system, refers to the combined data from all sensors in the bottom row of
the layout grid.
Top & Bottom In a dual-sensor system, refers to the combined data from the Main and Buddy sensor.
In a multi-sensor system, refers to the combined data from all sensors in the top and bottom
row of the layout grid.
The scan mode must be set to the type of measurement you need to configure.
Otherwise, the wrong tools, or no tools, will be listed on the Measure page.
3. If it is not already selected, click on the Parameter tab in the tool configuration area.
Regions
Many measurement tools use user-defined regions to limit the area in which measurements occur or to
help in the identification of a feature (Feature Points on page 209), a fit line (Fit Lines on page 213), or left
or right side of the Panel tool ( see Panel on page 279). Unlike reducing the active area, reducing the
measurement region does not increase the maximum frame rate of the sensor.
You can disable regions entirely and cause the measurement tool uses the entire active area by
unchecking the checkbox next to the Regions setting.
All tools provide region settings under the upper Parameters tab. This region applies to all of a tool's
measurements.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 206
Region settings are often found within expandable feature sections in the tool's panel.
In 2D mode, the tool region defaults to the center of the current data view, not the global field of
view. In 3D mode, the region defaults to the global field of view.
Use the region reset button ( ) to set the size of a region to its default. This is useful after
zooming in or out in the data viewer.
To configure regions:
The scan mode must be set to the type of measurement you need to configure.
Otherwise, the wrong tools, or no tools, will be listed on the Measure page.
The measurement region of some tools can be rotated by setting the region's Z Angle to better
accommodate features that are on an angle on a target. By rotating the measurement region, data not
related to the feature can often be excluded, improving accuracy of measurements.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 207
To rotate measurement regions:
1. Determine the length and width of the region that will be required once it is rotated.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 208
The region rotates clockwise around the Z axis relative to the X axis.
Once the region has been rotated, you cannot modify it in the data viewer using the mouse. You can
however modify its dimensions and its location manually by changing the region's values in the Region
setting.
Feature Points
Dimensional and positional measurements detect feature points found within the defined measurement
region and then compare measurement values taken at the selected point with minimum and maximum
thresholds to produce a decision. Feature points are selected in one or more Feature dropdowns in a
tool and are used for all of the tool's measurements.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 209
Point Type Examples
Max Z
Min Z
Min X
Max X
Average
Corner
Top Corner
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 210
Point Type Examples
Bottom Corner
Left Corner
Right Corner
Rising Edge
Falling Edge
Any Edge
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 211
Point Type Examples
Median
Geometric Features
Most Surface tools, and many Profile tools, can output features that Feature tools can take as input to
produce measurements. These features are called geometric features. Feature tools use these entities to
produce measurements based on more complex geometry. (For more information on Feature tools, see
Feature Measurement on page 484.)
Gocator’s measurement tools can currently generate the following kinds of geometric features:
Lines: A straight line that is infinitely long. Useful for locating the orientation of an enclosure or part, or
to intersect with another line to form a reference point that can be consumed by a Feature tool.
Planes: A plane extracted from a surface. Can be used for point-to-plane distance or line-plane
intersection measurements.
The following tables list the tools that can generate geometric features. (Tools that can't generate
geometric features are excluded.)
Bounding Box X
Countersunk Hole X
Edge X X
Ellipse X X
Hole X
Opening X
Plane X
Position X
Segmentation X
Sphere X X
Stud X
Volume
The Circle geometric feature currently cannot be used by any of the built-in Feature tools.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 212
Geometric features generated by Profile tools
Tool Point Line
Area X
Bounding Box X
Circle X
Intersect X X
Line X X
Position X
The Feature Intersect tool can also produce an intersect point. Script tools do not currently take
geometric features as input.
Fit Lines
Some measurements involve estimating lines in order to measure angles or intersection points. A fit line
can be calculated using data from either one or two fit areas.
A line can be defined using one or two areas. Two areas can be used to bypass discontinuity in a line
segment.
Decisions
Results from a measurement can be compared against minimum and maximum thresholds to generate
pass / fail decisions. The decision state is pass if a measurement value is between the minimum and
maximum threshold. In the data viewer and next to the measurement, these values are displayed in
green. Otherwise, the decision state is fail. In the user interface, these values are displayed in red.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 213
Value (14.785) within decision thresholds (Min: 14, Max: 15). Decision: Pass
Value (1604.250) outside decision thresholds (Min: 1500, Max: 1600). Decision: Fail
Along with measurement values, decisions can be sent to external programs and devices. In particular,
decisions are often used with digital outputs to trigger an external event in response to a measurement.
See Output on page 509 for more information on transmitting values and decisions.
To configure decisions:
The scan mode must be set to the type of measurement you need to configure.
Otherwise, the wrong tools, or no tools, will be listed on the Measure page.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 214
4. Click on the Output tab.
For some measurements, only the Output tab is displayed.
Filters
Filters can be applied to measurement values before they are output from the Gocator sensors.
All measurements provide filter settings under the Output tab. The following settings are available.
Filter Description
Scale and Offset The Scale and Offset settings are applied to a measurement value according to the following
formula:
Scale and Offset can be used to transform the output without the need to write a script. For
example, to convert the measurement value from millimeters to thousands of an inch, set
Scale to 39.37. To convert from radius to diameter, set Scale to 2.
Hold Last Valid Holds the last valid value when the measurement is invalid.
Smoothing Averages the valid measurements in the number of preceding frames specified in Samples.
Use this to reduce the impact of random noise on a measurement's output.
If Hold Last Valid is enabled, the smoothing filter uses the last valid measurement value
until a valid value is encountered.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 215
Filter Description
Preserve Invalid When enabled, smoothing is only applied to valid measurements and not to invalid results:
invalid results are not modified and are sent to output as is.
When disabled, smoothing is applied to both valid and invalid results. (This setting is only
visible when Smoothing is enabled.)
If Hold Last Valid is enabled, results will always be valid, in which case this setting does
nothing.
The scan mode must be set to the type of measurement you need to configure.
Otherwise, the wrong tools, or no tools, will be listed on the Measure page.
5. Expand the Filters panel by clicking on the panel header or the button.
Measurement Anchoring
When parts that a sensor is scanning move on a transport mechanism such as a conveyor, their position
typically changes from part to part in one or both of the following ways:
For cases where movement from part to part is more drastic, you can use part matching to
compensate. However, in order for part matching to work properly, the entire part typically
must be visible in the field of view.
For example, the following image shows a surface scan of a PCB. A Surface Dimension height
measurement returns the height of a surface-mount capacitor relative to a nearby surface (the F1
region).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 216
In the following scan, the part has shifted, but the measurement regions remain where they were
originally configured, in relation to the sensor or system coordinate system, so the measurement
returned is incorrect:
When you set a tool's anchor source, an offset is calculated between the anchored tool and the anchor
source. This offset is used for each frame of scanned data: the anchored tool's measurement region is
placed in relation to the anchor source, at the calculated offset.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 217
In the following image, after the Surface Dimension tool is anchored to the X and Y measurements from
a Surface Hole tool (placed over the hole to the lower left), Gocator compensates for the shift—mostly
along the Y axis in this case—and returns a correct measurement, despite the shift.
You can combine the positional anchors (X, Y, or Z measurements) with an angle anchor (a Z Angle
measurement) for optimum measurement placement. For example, in the following scan, the part has
not only shifted on the XY plane but also rotated around the Z axis. Anchoring the Surface Dimension
tool to the Z Angle measurement of a Surface Edge tool (placed on the lower edge in this case)
compensates for the rotation, and the anchored tool returns a correct measurement.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 218
If Z Angle anchoring is used with both X and Y anchoring, the X and Y anchors should come from
the same tool.
If Z Angle anchoring is used without X or Y anchoring, the tool's measurement region rotates
around its center. If only one of X or Y is used ,the region is rotated around its center and then
shifted by the X or Y offset.
Several anchors can be created to run in parallel. For example, you could anchor the measurements of
one tool relative to the left edge of a target, and anchor the measurements of another tool relative to
the right edge of a target.
You can combine positional anchors (X, Y, or Z) with angle anchors (Z Angle) for optimum measurement
placement.
In Surface mode
a. Select a Surface Generation type (Surface Generation on page 154) and adjust Part Detection
settings (see Part Detection on page 158) if applicable.
b. Start the sensor, scan the target, and then stop the sensor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 219
3. Adjust the anchoring tool's settings and measurement region, and choose a feature type (if applicable).
You can adjust the measurement region graphically in the data viewer or manually by expanding the
Regions area.
The position and size of the anchoring tool’s measurement regions define the zone within which
movement will be tracked.
If you intend to use angle anchoring and the part in the initial scan is rotated too much,
you may need to rotate the anchoring tool's region to accomodate this rotation. For
more information on region rotation, see Regions on page 206.
5. Adjust the tool and measurement settings, as well as the measurement regions, on a scan of the
representative target.
If the sensor is running, the anchored tool’s measurement regions are shown in white to indicate the
regions are locked to the anchor. The measurement regions of anchored tools cannot be adjusted.
The anchored tool’s measurement regions are now tracked and will move with the target’s position and
angle under the sensor, as long as the anchoring measurement produces a valid measurement value.
If the anchoring measurement is invalid, for example, if part moves outside its measurement region,
the anchored tool will not show the measurement regions at all and an “Invalid-Anchor” message will be
displayed in the tool panel.
8. Verify that the anchored tool works correctly on other scans of targets in which the part has moved
slightly.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 220
To remove an anchor from a tool:
To enable a measurement:
4. In the measurements list, check the box of the measurement you want to enable.
The measurement will be enabled and selected. The Output tab, which contains output settings will be
displayed below the measurements list. For some measurements, a Parameters tab, which contains
measurement-specific parameters, will also be displayed.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 221
To disable a measurement:
4. In the measurement list, uncheck the box of the measurement you want to disable.
The measurement will be disabled and the Output tab (and the Parameters tab if it was available) will
be hidden.
l Measurement: In a tool's measurement list, double-click the measurement name you want to
change.
Changing a Measurement ID
The measurement ID is used to uniquely identify a measurement in the Gocator protocol or in the SDK.
The value must be unique among all measurements.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 222
To select a measurement, it must be enabled. See Enabling and Disabling Measurements on page 221
for instructions on how to enable a measurement.
Duplicating a Tool
You can quickly create a copy of a previously added tool in Gocator. All settings of the original are
copied. This is useful, for example, when you need almost identical tools with only minor variations, such
as different Min and Max values.
To duplicate a tool:
1. Go to the Scan page by clicking on the Scan icon.
2. Choose Profile or Surface mode in the Scan Mode panel.
If one of these modes is not selected, tools will not be available in the Measure panel.
3. Go to the Measure page by clicking on the Measure icon.
4. In the tool list, click the Duplicate button ( ) of the tool you want to duplicate.
A copy of the tool appears below the original.
Removing a Tool
Removing a tool removes all of its associated measurements.
To remove a tool:
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 223
3. Go to the Measure page by clicking on the Measure icon.
4. In the tool list, click on the Duplicate button ( ) of the tool you want to duplicate.
A copy of the tool appears below the original.
Reordering Tools
When you add or duplicate a tool, the tool is added to the bottom of the list in the Tools panel. You can
reorder tools in the web interface to organize tools more logically. For example, you could group tools
that output geometric features with the tools that use them. Or you could group tools you use as
anchors with the tools that use those anchors.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 224
Profile Measurement
This section describes the profile measurement tools available in Gocator sensors.
When Gocator is in Surface mode and you have defined a section, a Stream option displays in Profile
tools. Choosing a section in the Stream option lets you apply profile measurements to the section.
A subset of the Profile tools is available when Uniform Spacing is disabled, that is, when tools are
applied to point cloud data.
For more information on the Uniform Spacing setting and resampled data, see Resampled Data and
Point Cloud Data on page 68.
Profile measurement tools can be used on sections. For more information on sections, see Sections on
page 195.
Advanced Height
The Advanced Height tool provides highly accurate and repeatable master (template) comparison and
step height measurements (up to 16 in a tool instance).
All instances of the Advanced Height tool share the same template file set in File. For this
reason, you must be careful when editing or removing template files shared by another
instance of the tool.
Height measurements can be made relative to a reference line. Reference line sets the measurement
direction (perpendicular to the reference line). A separate base line can also be set so that height
measurements are between the base line and a profile feature, rather than the reference line (which in
this case is used for angle correction).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 225
Measurement Panel
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 226
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement
Height {n}
Will be Invalid if the appropriate number of height regions has not been set in Height Region.
Master Correction X
Master Correction Z
The amount of correction applied to the profile with respect to the master.
Data
Type Description
Parameters
Parameter Description
Reference Line Toggles a set of settings related to the reference line. For
more information, see Reference Line on page 229.
Height Region Sets the number of height region measurements the tools
returns. For each height region, the tool displays an Edit
Height Region checkbox that you use to edit the height
region's location and size. The tool also displays a Feature
drop-down that lets you select the type of feature for that
height region.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 227
Parameter Description
Base Height Use base height to "set" the Z axis: when enabled height
values are offset from the base. This is useful if you need to
measure between two features, rather than between a
feature and the reference line.
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Master Comparison
When you check the Master option, the tool displays several additional settings and disables
measurement anchoring from other tools.
Master Parameters
Parameter Description
Display Master Overlays the master profile, in white, on the current profile.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 228
X Correction
When you check the Master option and enable X Correction, the tool displays several additional
settings.
X Correction Parameters
Parameter Description
Edit Edge Region Enables an edge region section letting you configure the
region. You can also edit this region in the data viewer.
Edge Direction Determines the direction of the edge. One of the following:
Falling or Rising.
Count Direction Indicates how edges are counted. One of the following: Left
to Right or Right to Left.
Reference Line
When you check the Master option and enable Reference Line, the tool displays several additional
settings. The reference line is used to set the measurement direction (perpendicular to the reference
line).
Edit Line Region Enables settings that let you edit the size and position of
the line's region.
Fitting Method Indicates the fitting method the tool uses. One of the
following: Simple or Robust.
Anchoring
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 229
Area
The Area tool determines the cross-sectional area within a region.
Areas are positive in regions where the profile is above the X axis. In contrast, areas are negative in
regions where the profile is below the X axis.
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 230
Measurements, Features, and Settings
Measurements
Measurement Illustration
Area
Centroid X
Centroid Z
Features
Type Description
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 231
For more information on geometric features, see Geometric Features on page 212.
Parameters
Parameter Description
Stream The data that the tool will apply measurements to.
Type Object area type is for convex shapes above the baseline.
Regions below the baseline are ignored.
Baseline Baseline is the fit line that represents the line above which
(Object clearance type) or below which (Clearance area type)
the cross-sectional area is measured.
Region The region to which the tool's measurements will apply. For
more information, see Regions on page 206.
Line When Baseline (see above) is set to Line, set this to one of
the following:
All Data: The tool uses all of the data in the active area.
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 232
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 233
Bounding Box
The Bounding Box tool provides measurements related to the smallest box that contains the profile (for
example, X position, Z position, width, etc.).
The bounding box provides the absolute position from which the Position centroids tools are
referenced.
When you use measurement tools on parts or sections, the coordinates returned are relative to
the part or section. You can use the values returned by the Bounding Box tool's "Global" (see
below) measurements as an offset in a Gocator script to convert the positional (X, Y, or Z)
measurements of other measurement tools to sensor or system coordinates (depending on
whether the sensor is aligned). For more information on Gocator scripts, see Scripts on
page 504.
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 234
Measurements, Features, and Settings
Measurements
Measurement Illustration
Width
Height
Global X*
Determines the X position of the center of the bounding
box that contains the profile relative to the surface from
which the profile is extracted.
Global Y*
Determines the Y position of the center of the bounding
box that contains the profile relative to the surface from
which the profile is extracted.
Global Angle*
Determines the angle around Z of the section used to create
the profile, relative to the surface from which it is extracted,
where a line parallel to the X axis is 0 degrees.
*The Global X, Global Y, and Global Angle measurements are intended to be used with profiles
extracted from a surface using a section.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 235
When used with profiles not generated from a section, the Global X measurement returns the
same value as the X measurement, and the Global Y and Global Angle measurements return
0.000.
Features
Type Description
Parameters
Parameter Description
Stream The data that the tool will apply measurements to.
Region The region to which the tool's measurements will apply. For
more information, see Regions on page 206.
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 236
Bridge Value
The Bridge Value tool calculates the "bridge value" and angle of a scanned surface. A bridge value is a
single, processed range that is an average of a laser line profile that has been filtered to exclude user-
definable portions of highs and lows in the profile. The resulting value represents a "roughness
calculation." A bridge value is typically used to measure road roughness, but can be used to measure the
roughness of any target.
The tool provides two additional measurements (Window and StdDev) that can help determine whether
the scanned data is valid; for more information, see Measurements on the next page.
The Bridge value tool is only available when Uniform Spacing (in the Scan Mode panel on the
Scan page) is unchecked, as the tool only works with unresampled data. For more information,
see Resampled Data and Point Cloud Data on page 68.
Profile point heights in the white area are included in the calculation of the average. Profile point heights
in the grey area are excluded. By adjusting the Window and Skip parameters, you can exclude profile
point heights that correspond to unwanted features on the target. In road roughness applications, for
example, you could exclude rocks (profile points higher than the road surface), cracks or tining valleys
(profile points lower than the road surface), and so on, to get an accurate representation of the tire-to-
road interface.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 237
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement Illustration
Bridge Value
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 238
Measurement Illustration
Angle
Window
StdDev
Parameters
Parameter Description
Stream The data that the tool will apply measurements to.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 239
Parameter Description
The Skip setting basically sets the upper limit of the profile
point heights in the histogram to be used in the average.
Normalize Tilt Fits a line to the profile and shears the points in the Z
direction by the angle between the fitted line and the X
axis. The Window and Skip settings are applied to the
histogram of the transformed data.
Region The region to which the tool's measurements will apply. For
more information, see Regions on page 206.
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 240
the noise instead of switching to search mode to find the actual profile. As a result, the Bridge Value tool
receives bad data and returns incorrect or invalid measurements.
On Gocator 2342 sensors, the Bridge Value tool’s Window and StdDev measurements can be used as
metrics to determine how valid the Bridge Value measurement is. The Window and StdDev
measurements force an enabled tracking window to switch to search mode when either measurement
returns a fail decision or an invalid value. The measurements’ Min and Max decision settings should be
set to define a range that reflect the expected target roughness so that the tracking window does not
switch to search mode: For example, the Window measurement should correspond to the height of the
area resulting from excluding highs and lows from the profile with the Window and Skip settings.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 241
Circle
The Circle tool provides measurements that find the best-fitted circle to a profile and measure various
characteristics of the circle.
The tool may be unable to fit a circle to the profile when attempting the fit on a small number of
relatively collinear data points.
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement Illustration
Radius
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 242
Measurement Illustration
Standard Deviation
Min Error
Max Error
Min Error X
Min Error Z
Max Error X
Max Error Z
Features
Type Description
Parameters
Parameter Description
Stream The data that the tool will apply measurements to.
Region The region to which the tool's measurements will apply. For
more information, see Regions on page 206.
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 243
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 244
Circle Radii
This tool is not supported on A and B revision Gocator 2100 and 2300 sensors. However, it is
supported on any accelerated sensors (PC or GoMax), including these models, and will appear
in emulator scenarios created using these sensors.
The Profile Circle Radii tool lets you measure radii and diameters at specified angle steps, given a
specified center point. The tool draws rays from the center point and returns radii or diameter
measurements for each ray.
For example, in the following scan of an exhaust pipe by a four-sensor system, the tool is showing a
radius measurement at 70 degrees that indicates a dent in the pipe. The tool also provides settings to
compensate for missing data and for rough surfaces or noise.
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 245
Measurements, Features, and Settings
Measurements
Measurement Illustration
Radius at {angle}
Diameter at {angle}
Data
Type Description
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For
more information, see Source on page 205.
If this option is not checked, the tool uses data from the entire active area.
Region The region to which the tool's measurements will apply. For more information, see Regions
on page 206.
Center Selection The source for the point geometric feature the tool uses as a center point. One of the
following:
Bounding Box – Uses the center of the bounding box that encloses the scan data selected
in Source. If Use Region is enabled, the tool places a bounding box only around the data
in the region. If Use Region is disabled, the tool places a bounding box around all scan
data; this will include any outliers in the bounding box, which could produce an undesired
center point.
Feature Input – A point geometric feature provided by another tool, such as the center
point from a Circle tool.
Center The point geometric feature coming from another tool that the Circle Radii tool uses as the
center point from which rays are drawn to search for data points. The parameter is only
available when Center Selection is set to Feature Input.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 246
Parameter Description
The tool searches for a data point at each angle step and returns the radius from the
center point or the diameter.
Tolerance If no data point is found at the angle step, the tool searches within the specified number
of degrees to each side of the step to find a data point. Useful to compensate for gaps in
the data.
The graphic above shows how the tool searches to each side of the angle step until it finds
a data point (circled and in yellow).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 247
Parameter Description
Averaging The number of data points to each side of the point the tool uses to average. Use this to
compensate for noise or rough surfaces.
The graphic above shows how the tool averages the data point at the angle step with the
number of data points specified in Averaging to each side of the angle step, replacing the
original data point with the average (circled and in yellow).
Filters The filters that are applied to measurement values before they are output. For more
information, see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement
tool sends a pass or fail decision to the output. For more information, see Decisions on
page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 248
Closed Area
The Closed Area tool determines the cross-sectional area within a region using point cloud data from a
dual- or multi-sensor system.
The tool is intended for use with roughly circular shaped profiles, or profiles that do not contain
excessive concavity. The tool renders a polygon corresponding to the profile in the data viewer. Use this
polygon to decide whether the tool can correctly calculate an acceptable representation of the profile.
Minor gaps in the profile are permitted; the size of these gaps is configurable.
When the tool is used in conjunction with a script tool, you can calculate the volume of a target; for more
information on the Script tool, see Script on page 299.
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement Illustration
Closed Area
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 249
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For more
information, see Source on page 205.
For this tool, you should set this parameter to Top and Bottom.
If this option is not checked, the tool uses data from the entire active area.
Region The region to which the tool's measurements will apply. For more information, see Regions on
page 206.
Use Max Gap Indicates whether the tool uses the Max Gap setting (see below).
Max Gap The maximum gap allowed between any two profile points on the contour of the target, in
millimeters. In the following illustration of a profile, if the gap were greater than the value set in
Max Gap, the tool would return an invalid value.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 250
Parameter Description
Sample Spacing The angle interval around the center of the profile the tool uses to calculate area. Enabling this
setting and setting a value can increase the tool's performance.
In the following image, the spacing is set to 1 degree. The polygon calculated from the profile
points, which is then used to calculate the area, is simplified, increasing performance but
reducing accuracy.
In the following image, Sampling Spacing is set to 0. Accuracy is increased, but performance is
reduced.
If you set the value to 0, the tool uses the smallest angle permitted internally by the sampling
engine.
Filters The filters that are applied to measurement values before they are output. For more
information, see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement tool
sends a pass or fail decision to the output. For more information, see Decisions on page 213.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 251
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 252
Dimension
The Dimension tool provides Width, Height, Distance, Center X, and Center Z measurements.
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement Illustration
Width
Height
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 253
Measurement Illustration
Distance
Center X
Center Z
Parameters
Parameter Description
Stream The data that the tool will apply measurements to.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 254
Parameter Description
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 255
Edge
The Profile Edge tool finds an edge on a profile, searching from left to right. The tool's settings help fit
the edge point when multiple potential edges are in the region of interest. After the tool locates an edge,
the position (X and Z) of the center of the step and the step height can be returned as measurements.
The tool can also generate a point geometric feature corresponding to the center of the step that
Feature tools can take as input for measurement. For more information on Feature tools, see Feature
Measurement on page 484.
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 256
Measurements, Features, and Settings
Measurements
Measurement
These measurements return the X and Z position of the edge point, respectively. The edge point is located half-way
between the upper and lower data points of the step.
Step Height
Features
Type Description
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For more
information, see Source on page 205.
Selection Type Determines which step the tool uses when there are multiple steps in the profile. An edge point
is placed the chosen step. Steps must satisfy the tool's Step Threshold and Step Direction
settings.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 257
Parameter Description
Step Threshold The minimum step accepted as an edge candidate. Steps on the profile are treated as absolute
values when compared to this setting.
In the following profile, with Step Threshold set to 1.7 (and Selection Type set to Last), the tool
accepts the step to the right, with a step of -1.873 mm, because it is above the step threshold.
In the following, when Step Threshold is increased to 1.9, the tool excludes the falling step to the
right, because it is no longer above the step threshold, and instead uses the step to the left.
Step Direction Determines whether the expected step rises or falls, moving left to right, along the profile. Either
Rising, Falling, or Rising or Falling.
Step Smoothing The size of the (moving) window along the profile used to calculate an average for each data point
on the profile. The setting is useful for averaging out noise.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 258
Parameter Description
Step Width The distance, along a path profile, separating the points the tool uses to find steps on a profile.
In the following, a step width of 5.5 mm causes the tool to consider profile points that distance
apart as steps. Consequently, the curved portion of the profile is not used to measure the step.
The setting is useful when you must detect a slope as an edge, rather than a sharply defined
edge: setting Step Width to a value greater than the width of the edge ensures that the tool
measures the height difference between the flat regions on either side of the edge. As a result,
the height of the step is accurately measured, and the edge is correctly located.
Setting Step Width wider than necessary can reduce the precision of edge
location.
Max Gap Fills in regions of missing data caused by an occlusion near the desired edge. Use this setting
when continuity on the target is expected. When Max Gap is set to a non-zero value, the tool
holds and extends the last data point on the low side next to an edge across a gap of null points,
up to the distance specified in Max Gap.
The tool uses data points "filled in" by Max Gap before data points filled in by Null Fill Value (see
below).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 259
Parameter Description
Include Null Edges Indicates whether null points (points where no height value is available, due to dropouts or
regions outside of the measurement range) are filled with the value in Null Fill Value as a general
“background level.”
To find an edges next null points, you must use either this option and an
appropriate value in Null Fill Value or Max Gap. Otherwise, only edges within
areas of contiguous data will be detected.
Null Fill Value The height value (in mm) used to replace null points when Include Null Edges is enabled.
If both Null Fill Value and Max Gap fill in null points at the same position, the tool uses the value
extended by Max Gap, regardless of the value of Null Fill Value.
Show Detail When disabled, reduces what is indicated in the data viewer.
Filters The filters that are applied to measurement values before they are output. For more information,
see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement tool
sends a pass or fail decision to the output. For more information, see Decisions on page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 260
Groove
The Groove tool provides measurements of V-shape, U-shape, or open-shape grooves.
The Groove tool uses a complex feature-locating algorithm to find a groove and then return
measurements. See "Groove Algorithm" in the Gocator Measurement Tool Technical Manual for a
detailed explanation of the algorithm. The behavior of the algorithm can be adjusted by changing the
parameters in the measurement panel.
The Groove tool lets you add multiple measurements of the same type to receive measurements and set
decisions for multiple grooves. Multiple measurements are added by using the drop-down above the list
of measurements and clicking on the Add button.
For example, if a target has three grooves, by adding two measurements, choosing Index From The
Left in the Select Type setting of those measurements, and providing values of 0 and 2 in the Index
setting of the measurements, respectively, the Groove tool will return measurements and decisions for
the first and third grooves.
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 261
Measurements, Features, and Settings
Measurements
Measurement Illustration
Width
Depth
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 262
Measurement Illustration
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For
more information, see Source on page 205.
Stream The data that the tool will apply measurements to.
This setting is only displayed when data from another tool is available as input for this tool.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 263
Parameter Description
Min Width Minimum width for a groove to be considered valid. The width is the distance between the
groove corners.
Max Width Maximum width of a groove to be considered valid. If set to 0, the maximum is set to the
width of the measurement area.
Region The measurement region defines the region in which to search for the groove. For a stable
measurement, the measurement region should be large enough to cover some data on the
left and right sides of the groove.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 264
Parameter Description
(Groove X and Groove Z Bottom - Groove bottom. For a U-shape and open-shape groove, the X position is at the
measurements only) centroid of the groove. For a V-shape groove, the X position is at the intersection of lines fitted
to the left and right sides of the groove. See algorithm section below for more details.
Select Type Specifies how a groove is selected when there are multiple grooves within the measurement
area.
Index from The Left - 0-based groove index, counting from left to right
Index from the Right - 0-based groove index, counting from right to left.
Filters The filters that are applied to measurement values before they are output. For more
information, see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement tool
sends a pass or fail decision to the output. For more information, see Decisions on page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 265
Intersect
The Intersect tool determines intersect points and angles.
The Intersect tool's measurements require two fit lines, one of which is a reference line set to the X axis (z
= 0), the Z axis (x = 0), or a user-defined line.
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement Illustration
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 266
Measurement Illustration
Angle
Features
Type Description
Parameters
Parameter Description
Stream The data that the tool will apply measurements to.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 267
Parameter Description
Line You can use one or two fit areas for the fit line. To set the
region (or regions) of the fit line, adjust it graphically in the
data viewer, or expand the feature using the expand
button ( ) and enter the values in the fields. For more
information on regions, see Regions on page 206.
Ref Line Used to define the reference line when Line is selected in
the Reference Type parameter. To set the region (or regions)
of the reference line, adjust it graphically in the data viewer,
or expand the feature using the expand button ( ) and
enter the values in the fields. For more information on
regions, see Regions on page 206.
0 – 180
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 268
Line
The Line tool fits a line to the profile and measures the deviations from the best-fitted line. The sensor
compares the measurement value with the values in Min and Max to yield a decision. For more
information on decisions, see Decisions on page 213.
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 269
Measurements, Features, and Settings
Measurements
Measurement Illustration
Standard Deviation
Min Error
Max Error
Percentile
Finds the best-fitted line and measures the range (in Z) that
covers a percentage of points around the line.
Offset
Angle
Min Error X
Min Error Z
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 270
Measurement Illustration
Max Error X
Max Error Z
Features
Type Description
Parameters
Parameter Description
Stream The data that the tool will apply measurements to.
Region The region to which the tool's measurements will apply. For
more information, see Regions on page 206.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 271
Parameter Description
Fitting Regions Determines which data Gocator uses to fit the line over the
profile.
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 272
Line Advanced
This tool is not supported on A and B revision Gocator 2100 and 2300 sensors. However, it is
supported on any accelerated sensors (PC or GoMax), including these models, and will appear
in emulator scenarios created using these sensors.
Like the Profile Line tool, the Profile Line Advanced tool fits a line to a profile and measures the
deviations from the best-fitted line. Additionally, this version of the tool provides two “roughness
parameter” measurements: Ra and Rz. Note that the region-related parameters have been reorganized
to make the tool easier to use. The sensor compares the measurement value with the values in Min and
Max to yield a decision. For more information on decisions, see Decisions on page 213.
If you do not need the roughness parameters, LMI currently recommends using the Profile Line
tool (see Line on page 269).
Set Fitting Method to Simple to cause the tool to behave like the older Profile Line tool.
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 273
Measurements, Features, and Settings
Measurements
Measurement Illustration
Standard Deviation
Min Error
Max Error
Percentile
Finds the best-fitted line and measures the range (in Z) that
covers a percentage of points around the line.
Offset
Angle
Min Error X
Min Error Z
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 274
Measurement Illustration
Max Error X
Max Error Z
Ra
Rz
Returns the average maximum height of the profile data.
Features
Type Description
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For more
information, see Source on page 205.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 275
Parameter Description
Region Whether the fitting and measurement regions are combined or separate (or not used). One of the
following:
None
The tool uses the entire profile to fit the line and perform measurements.
The tool uses a single, user-defined region to fit the line and in which it performs measurements.
In the following image,
The tool uses one or two regions to fit the line, and a single, separate region in which it performs
measurements.
In the following image, the tools uses a single region to the left to fit the line, and performs
measurements in the measurement region to the right:
In the following image, the uses two regions to the left to fit the line, and performs
measurements in the measurement region to the right:
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 276
Parameter Description
Stream The data that the tool will apply measurements to.
This setting is only displayed when data from another tool is available as input for this tool.
Region These settings contain parameters to define the position and size of the fitting and
Measurement Region
Fitting Method Determines how the tool fits the line to the data. One of the following:
Simple
Uses a less accurate but faster line-fitting method. Use this setting to cause the tool to behave
like Profile Line.
Robust
An iterative line-fitting method that removes points and attempts to fit a line until only one-third
of the original profile data points is left. More accurate but takes longer.
Outlier Percentile Indicates the number of outlier points to be removed overall during line fitting. Adjust this value
based on how much noise is present in the profile.
Measurement The specified percentage of points around the best-fitted line that the Percentile measurement
Percentage uses.
(Percentile measurement
only)
Filters The filters that are applied to measurement values before they are output. For more information,
see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement tool
sends a pass or fail decision to the output. For more information, see Decisions on page 213.
Anchoring
Anchor Description
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 277
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 278
Panel
The Panel tool provides Gap and Flush measurements.
The Panel tool uses a complex feature-locating algorithm to find the gap or calculate flushness and
return measurements. The behavior of the algorithm can be adjusted by changing the parameters in the
measurement panel. See "Gap and Flush Algorithm" in the Gocator Measurement Tool Technical Manual
for a detailed explanation of the algorithm.
You must make sure that there are enough data points to define the edge in the profile, by
properly settng up exposure, etc. If not, the algorithm will not function.
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 279
Measurements
Measurement Illustration
Gap
Flush
Left Gap X
Left Gap Z
Left Flush X
Left Flush Z
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 280
Measurement Illustration
Right Gap X
Right Gap Z
Right Flush X
Right Flush Z
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For
more information, see Source on page 205.
Stream The data that the tool will apply measurements to.
This setting is only displayed when data from another tool is available as input for this
tool.
Reference SideDirection Defines the side used to calculate the measurement axis (see below) rounded corner.
Max Gap Width The maximum width of the gap. Allows the tool to filter gaps greater than the expected
width. This can be used to single out the correct gap when there are multiple gaps in the
field of view.
Measurement Axis Defines the direction that the gap is calculated, in relation to the reference side (see
Surface: In the direction of the fitted surface line of the reference surface.
Absolute When enabled, returns an absolute value rather than a signed value.
Filters The filters that are applied to measurement values before they are output. For more
information, see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement
tool sends a pass or fail decision to the output. For more information, see Decisions on
page 213.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 281
Left/Right SideEdge Parameters
Parameter Description
Max Void Width The maximum allowed width of missing data caused by occlusion or data dropout.
Min Depth Defines the minimum depth before an opening could be considered to have a potential
edge. The depth is the perpendicular distance from the fitted surface line.
Surface Width The width of the surface area in which data is used to form the fitted surface line. This
value should be as large as the surface allows.
Surface Offset The distance between the edge region and the surface region.
Setting a small value allows the edge within a tighter region to be detected. However, the
measurement repeatability could be affected if the data from the edge are considered as
part of the surface region (or vice versa). A rule of thumb is to set Surface Offset equal to
Nominal Radius.
Nominal Radius The radius of the curve edge that the tool uses to locate the edge region.
Edge Angle A point on the best fit circle to be used to calculate the feature point. The selected point
is on the circumference at the specified angle from the start of the edge region.
The angle is measured from the axis perpendicular to the fitted surface line.
Edge Type Defines the type of feature point to use for the edge (Corner or Tangent).
A tangent edge point is the point selected based on the defined Edge Angle. A corner
edge point is the intersect point between the fitted surface line and a edge line formed
by interpolating the points at and after the tangent within the edge region.
Region The region to which the tool's measurements will apply. For more information, see Regions
on page 206.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 282
Position
The Position tool finds the X or Z axis position of a feature point. The feature type must be specified and
is one of the following: Max Z, Min Z, Max X, Min X, Corner, Average (the mean X and Z of the data
points), Rising Edge, Falling Edge, Any Edge, Top Corner, Bottom Corner, Left Corner, Right Corner, or
Median (median X and Z of the data points).
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement Illustration
Features
Type Description
Parameters
Parameter Description
Stream The data that the tool will apply measurements to.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 283
Parameter Description
Feature The feature the tool uses for its measurements. One of the
following:
l Max Z
l Min Z
l Max X
l Min X
l Corner
l Average
l Rising Edge
l Falling Edge
l Any Edge
l Top Corner
l Bottom Corner
l Left Corner
l Right Corner
l Median
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 284
Round Corner
The Round Corner tool measures corners with a radius, returning the position of the edge of the corner
and the angle of adjacent surface with respect to the X axis.
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
The Round Corner tool uses a complex feature-locating algorithm to find the edge and return
measurements. The behavior of the algorithm can be adjusted by changing the parameters in the
measurement panel. See "Gap and Flush Algorithm" in the Gocator Measurement Tool Technical Manual
for a detailed explanation of the algorithm.
You must make sure that there are enough data points to define the edge (proper exposure,
etc.). If not, the algorithm will not function.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 285
Measurements
Measurement Illustration
Angle
Features
Type Description
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 286
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For
more information, see Source on page 205.
Stream The data that the tool will apply measurements to.
This setting is only displayed when data from another tool is available as input for this
tool.
Reference Direction Defines the side used to calculate the rounded corner.
Max Gap Width The maximum width of the gap. Allows the tool to filter gaps greater than the expected
width. This can be used to single out the correct gap when there are multiple gaps in the
field of view.
Filters The filters that are applied to measurement values before they are output. For more
information, see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement
tool sends a pass or fail decision to the output. For more information, see Decisions on
page 213.
Edge Parameters
Parameter Description
Max Void Width The maximum allowed width of missing data caused by occlusion or data dropout.
Min Depth Defines the minimum depth before an opening could be considered to have a potential
edge. The depth is the perpendicular distance from the fitted surface line.
Surface Width The width of the surface area in which data is used to form the fitted surface line. This
value should be as large as the surface allows.
Surface Offset The distance between the edge region and the surface region.
Setting a small value allows the edge within a tighter region to be detected. However, the
measurement repeatability could be affected if the data from the edge are considered as
part of the surface region (or vice versa). A rule of thumb is to set Surface Offset equal to
Nominal Radius.
Nominal Radius The radius of the curve edge that the tool uses to locate the edge region.
Edge Angle A point on the best fit circle to be used to calculate the feature point. The selected point
is on the circumference at the specified angle from the start of the edge region.
The angle is measured from the axis perpendicular to the fitted surface line.
Edge Type Defines the type of feature point to use for the edge (Corner or Tangent).
A tangent edge point is the point selected based on the defined Edge Angle. A corner
edge point is the intersect point between the fitted surface line and a edge line formed
by interpolating the points at and after the tangent within the edge region.
Region The region to which the tool's measurements will apply. For more information, see Regions
on page 206.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 287
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 288
Strip
The Strip tool measures the width of a strip.
The Strip tool uses a complex feature-locating algorithm to find a strip and then return measurements.
See "Strip Algorithm" in the Gocator Measurement Tool Technical Manual for a detailed explanation of
the algorithm. The behavior of the algorithm can be adjusted by changing the parameters in the
measurement panel.
The Strip tool lets you add multiple measurements of the same type to receive measurements and set
decisions for multiple strips. Multiple measurements are added by using the drop-down above the list of
measurements and clicking on the Add button.
For example, if a target has three strips, by adding two measurements, choosing Index From The Left
in the Select Type setting, and providing values of 1 and 3 in the Index of field of the measurements,
respectively, the Strip tool will return measurements and decisions for the first and third strip.
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 289
Measurements
Measurement Illustration
Width
Height
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For more
information, see Source on page 205.
Stream The data that the tool will apply measurements to.
This setting is only displayed when data from another tool is available as input for this tool.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 290
Parameter Description
When Base Type is set to Flat, both strip (raised area) and base support regions are needed.
When set to None, only a point that deviates from a smooth strip support region is needed to
find a rising or falling edge.
Left Edge Specifies the features that will be considered as the strip's left and right edges. You can select
Data end - First valid profile data point in the measurement region.
Void - Gap in the data that is larger than the maximum void threshold. Gaps connected to the
measurement region's boundary are not considered as a void.
See "Strip Start and Terminate Conditions" in the Gocator Measurement Tool Technical Manual for
the definitions of these conditions.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 291
Parameter Description
The strip may be tilted with respect to the sensor's coordinate X axis. This can be caused by
conveyor vibration. If the Tilt option is enabled, the tool will report the width and height
measurements following the tilt angle of the strip.
Support Width Specifies the width of the region around the edges from which the data is used to calculate the
step change. See "Strip Step Edge Definitions" in the Gocator Measurement Tool Technical Manual
on how this parameter is used by different base types.
Transition Width Specifies the nominal width needed to make the transition from the base to the strip. See "Strip
Step Edge Definitions" in the Gocator Measurement Tool Technical Manual on how this parameter is
used by different base types.
Min Width Specifies the minimum width for a strip to be considered valid.
Min Height Specifies the minimum deviation from the strip base. See "Strip Step Edge Definitions" in the
Gocator Measurement Tool Technical Manual on how this parameter is used for different base
types.
Max Void Width The maximum width of missing data allowed for the data to be considered as part of a strip
when Void is selected in the Left or Right parameter. This value must be smaller than the edge
Support Width.
When occlusion and exposure causes data drops, users should use the gap filling function to fill
the gaps. See Gap Filling on page 151 for information.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 292
Parameter Description
Region The measurement region defines the region in which to search for the strip. If possible, the
region should be made large enough to cover the base on the left and right sides of the strip.
Location Specifies the strip position from which the measurements are performed.
Select Type Specifies how a strip is selected when there are multiple strips within the measurement area.
Filters The filters that are applied to measurement values before they are output. For more
information, see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement tool
sends a pass or fail decision to the output. For more information, see Decisions on page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 293
Template Matching
This tool is not supported on A and B revision Gocator 2100 and 2300 sensors. However, it is
supported on any accelerated sensors (PC or GoMax), including these models, and will appear
in emulator scenarios created using these sensors.
The Profile Template Matching tool lets you align a profile to a "master" template profile you create in
the tool (a "golden template"), compensating for movement of the target from frame to frame. As a
result, you can perform measurements over on a "stabilized" profile.
The tool returns measurements that represent differences between the profile and the master, letting
you perform simple defect detection and location from within the tool.
The tool also outputs an aligned profile that other Profile measurement tools can use as input (via their
Stream parameter). Finally, the tool produces a "difference" profile on which you can similarly perform
measurements.
The sensor compares the measurement value with the values in Min and Max to yield a decision. For
more information on decisions, see Decisions on page 213.
In the data viewer, the profiles are rendered using different colors:
The master profile is rendered in white. The aligned profile is rendered in blue. The current profile is rendered in red.
Note that in the image above, the tool is performing only a rough alignment to ensure that the different
profiles are clearly visible. Typically, the blue aligned profile will be on top of the white master profile.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 294
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
l Transform X
l Transform Z
l Transform Y Angle
Master Compare must be enabled for the following measurements; otherwise, they return Invalid
values:
Measurements
Measurement
Transform X
Transform Z
The distance the profile has shifted on the X and Z axis after alignment to the master, respectively.
Transform Y Angle
The maximum height difference between the profile and the master.
The X and Z positions of the maximum height difference between the profile and the master.
Standard Deviation
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 295
Measurement
Difference Average
The average difference on the Z axis between the profile and the master.
Difference Sum
The sum of the differences on the Z axis between the profile and the master.
Variance
Returns the variance of a difference profile calculated by subtracting the current profile from the master.
Matching Score
Returns a value between 0 and 1 that is the is the percentile of standard deviation of a difference profile (calculated by
subtracting the current profile from the master) from the tolerance.
Data
Type Description
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For more
information, see Source on page 205.
Stream The data that the tool will apply measurements to.
This setting is only displayed when data from another tool is available as input for this tool.
File A list of templates available to the tool. The template containing the profile the tool uses as a
master profile for alignment and comparisons. Use the Operation parameter to add and remove
templates to this list.
Operation Provides operations related to profile template files (masters). One of the following:
Save – Saves the current profile to a template file in the local file system and adds it to the list in
File. Multiple templates can be available. Files are persistent.
(This parameter switches to “Normal” after the tool performs one of the file operations.)
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 296
Parameter Description
Use Region Indicates whether the tool uses a user-defined region to perform matching. (The tool uses only the
data profile and master data in this region to perform matching.)
If this option is not checked, the tool performs matching using data from the entire active area.
Match Region Size and position of the region in which the matching (alignment) is performed..
Master comparison measurements however are applied to the entire profile (current profile and
master). For example, in the following image, the tool limits matching to the data in the match
region. But the measurement (Max Height Difference in this case) is calculated on the data
outside the region.
(The dashed lines are added to illustrate the hidden aligned profile and master.)
Coarse Align When enabled, shows the X Shift Window parameter. Use this setting by itself if you expect
targets will only move along the X and Z axes (that is, you don’t expect rotation). Otherwise, when
combined with Fine Align, it provides a good initial start position for fine alignment.
X Shift Window The maximum distance on the X axis the tool can move the current profile in order to align it.
Should be set to the maximum amount the part is expected to shift left or right. (Enabled using
the Coarse Align parameter.)
Fine Align When enabled, lets you set the Max Iteration and Match Window parameters for fine alignment.
This alignment method is more accurate than coarse alignment but takes more time to run.
Max Iteration The maximum number of iterations the tool uses to perform fine alignment of the profile to the
master.
Match Window The region in which points are evaluated for a match. It there’s a larger difference between the
current profile and the master than the match window size, it would ignore the point.
Master Compare Causes the tool to compare the current profile to the master profile and return results in some of
the tool’s measurements. (See list above.)
When disabled, the measurements that compare the profile to the master return invalid values.
Difference Profile Defines the size of the window the tool uses to smooth out noise in the Difference Profile data
Median Size output.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 297
Parameter Description
Filters The filters that are applied to measurement values before they are output. For more information,
see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement tool
sends a pass or fail decision to the output. For more information, see Decisions on page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 298
Script
A Script measurement can be used to program a custom measurement using a simplified C-based
syntax. A script measurement can produce multiple measurement values and decisions for the output.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 299
4. Click the Save button to save the script code.
If there is a mistake in the script syntax, the result will be shown as a "Invalid" with a red border in the
data viewer when you run the sensor.
Outputs from multiple measurement tools can be used as inputs to the script. A typical script would
take results from other measurement tools using the value and decision function, and output the result
using the output function. Stamp information, such as time and encoder stamps, are available in the
script, whereas the actual profile3D point cloud data is not. (The script engine is not powerful enough to
process the data itself.) Only one script can be created.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 300
Surface Measurement
Surface measurement involves capturing a sequence of laser profiles, optionally identifying discrete
objects, and measuring properties of the surface or the objects, such as the volume of the object or the
height at a certain position of the object. All volumetric tools have the ability to operate either on the
entire surface or the full object, or within a region of interest at a certain position in relation to the
surface or an object.
Multiple measurements can be performed on the entire surface or each discrete object, limited only by
the available CPU resources.
The frame of reference for the coordinate system of the detected object can be set to Sensor or Part in
the Part Detection panel (Part Detection on page 158). This setting determines what coordinate system
the region of interest for a measurement is positioned in, as well as the coordinate reference used to
output measurement values.
For example, if you need to measure the average height in a certain location relative to the sensor's field
of view regardless of the objects passing under the sensor, the frame of reference should be set to
Sensor. This is typical in applications where a wide web of material is continuously scanned, such as
paper, rubber, fabrics, etc. If on the other hand you need to measure the average height in a certain
location of a scanned object, the frame of reference should be set to Part. This is typical in applications
where discrete objects pass under the sensor and specific locations on the objects need to be inspected.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 301
Arithmetic
This tool is not supported on A and B revision Gocator 2100 and 2300 sensors. However, it is
supported on any accelerated sensors (PC or GoMax), including these models, and will appear
in emulator scenarios created using these sensors.
The Surface Arithmetic tool lets you perform various operations on a pair of surfaces. For example, you
can use the tool to perform dynamic masking from frame to frame. The tool performs bitwise
operations (AND or OR) on the corresponding data points in the source surfaces, and also combines
height and intensity data with add, subtract, average, and mask operations.
2D View
Tool Setup
Settings
Parameters
Parameter Description
Stream The data that the tool will apply measurements to.
This setting is only displayed when data from another tool is available as input for this tool.
If you switch from one type of data to another (for example, from section profile data to
surface data), currently set input features will become invalid, and you will need to choose
features of the correct data type.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 302
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For
more information, see Source on page 205.
Can only accept Surface scan data (that is, cannot accept data from other tools).
Secondary Source The data output of another tool, for example, of a Surface Filter tool.
If this option is not checked, the tool uses data from the entire active area.
Region The region to which the tool's measurements will apply. For more information, see Regions
on page 206.
Use Intensity If enabled, the tool uses intensity data instead of heightmap data. Only available if Acquire
Intensity is enabled on the Scan page during the scan; for more information, see .
Add – Adds the height values of the corresponding data points in the two sources.
Subtract – Subtracts the height values of the corresponding data points in the two sources.
Average – Averages the height values of the corresponding data points in the two sources.
Logic Performs bitwise-operations on the source and secondary source surface data. One of the
following: And or Or. When Operator is set to Average, this parameter is unavailable.
Data
Type Description
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 303
Ball Bar
This tool is not supported on A and B revision Gocator 2100 and 2300 sensors. However, it is
supported on any accelerated sensors (PC or GoMax), including these models, and will appear
in emulator scenarios created using these sensors.
The Surface Ball Bar tool returns measurements useful for calibrating systems using a ball bar,
particularly systems that include a robot.
2D View 3D View
Measurement Panel
Measurements
Measurement
Distance 3D
The direct distance between the centers of the spheres fitted to the balls.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 304
Measurement
Position X1 / Y1 / Z1
Position X2 / Y2 / Z2
These measurements return the X, Y, and Z positions of the centers of the spheres fitted to the balls.
Normal X / Y / Z
These measurements return the X, Y, and Z components of the normal vector of the surface surrounding the calibration
target.
Ix / Iy / Iz
Jx / Jy / Jz
Kx / Ky / Kz
These measurements return the X, Y, and Z components of the I, J, and K unit vectors defining the coordinate system
orientation.
Tx / Ty / Tz
These measurements return the X, Y, and Z components of the translation vector defining the coordinate system origin
location.
Parameters
Parameter Description
Origin Ball Determines which ball is used as the origin. The Bottom of
View option selects the ball at the bottom of the data
viewer in the Gocator web interface.
Use Nominal Distance When enabled, displays Nominal Distance and Distance
Tolerance settings. Set these to reflect the distance
between the balls of the ball bar (refer to the specifications
of the ball bar) and the tolerance you need. This can be
useful to ensure invalid results due to false or inaccurate
detection are rejected.
Use Nominal Radius When enabled, displays Nominal Radius settings. Set these
to reflect the radius of the balls of the ball bar (refer to the
specifications of the ball bar) and the tolerance you need.
This can be useful to ensure invalid results due to false or
inaccurate detection are rejected.
Zero Plane Parameters Enables advanced zero plane settings. For UR integration,
you should leave the settings at their default. These
parameters allow ensuring the plane detection is accurate
and robust to variations.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 305
Parameter Description
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Barcode
This tool is not supported on A and B revision Gocator 2100 and 2300 sensors. However, it is
supported on any accelerated sensors (PC or GoMax), including these models, and will appear
in emulator scenarios created using these sensors.
The Barcode tool lets you decode data encoded in 1D (linear) and 2D barcodes from surface data
(intensity data or heightmap data) without the need for 2D vision cameras or barcode readers. The tool
also supports dot-peened types (Datamatrix and QR code). For a complete list of the types the tool
supports, see "Type" in Parameters on page 308.
When configuring the tool, make sure you switch the data viewer to the appropriate type of
visualization for the barcode: for intensity-based barcodes (such as printed barcodes), switch
the data viewer to intensity mode using the Intensity button ( ); for height-based barcodes
(such as dot peen codes), switch the data viewer to heightmap mode using the Heightmap
button ( ).
The tool returns whether it has found the barcode and whether it is valid, as well as the X, Y, and Z
position of the barcode's lower left corner.
You can use the String Encoding tool to extract the string and pass it as output to a PLC; for more
information, see String Encoding on page 441. The extracted string is also available via the SDK; for
information on the SDK, see GoSDK on page 813 and the SDK reference documentation.
2D View 3D View
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 306
Measurement Panel
The decoded data is also displayed in the log; for more information on the log, see Log on page 96.
The tool provides two "learn" functions that can speed up the process of determining appropriate
settings. (For more information, see Mode below.)
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 307
Measurements, Features, and Settings
Measurements
Measurement Illustration
Found
Data
Type Description
Location Image The image the tool uses to find the a dot-peen barcode.
(When Type is set to a printed barcode, that is, a type other
than a dot-peen code, this image is the same as the decode
image.)
Decode Image The image the tool uses as part of the dot peen decode
algorithm. Use this to adjust the image (for example, using
one of the filter tools) and to diagnose issues.
Dot peen decode Image A binarized image the tool runs the dot peen decode
algorithm on. The points of the code should appear clearly
in the image to ensure proper decoding. Use this to adjust
the image (for example, using one of the filter tools) and to
diagnose issues.
Parameters
Parameter Description
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 308
Parameter Description
If this option is not checked, the tool uses data from the
entire active area.
Region The region to which the tool's measurements will apply. For
more information, see Regions on page 206.
Data The data the tool uses to detect a bar code. One of the
following:
l Intensity
l Heightmap
Type The type of barcode the tool expects. One of the following:
l Any: Detects any type of barcode.
l 1D Barcode (All): Detects any type of 1D (linear) barcode.
l EAN-8
l EAN-13
l ISBN-10
l ISBN-13
l UPC-A
l UPC-E
l Code-39
l Code-128
l Interleave 2 of 5
l PDF417
l Data Matrix
l Data Matrix dot peened
l QR Code
l QR Code dot peened
Mirrored Reverses the scan. Use this if the scan is mirrored. Only
useful with 2D barcodes.
Light on dark / Raised If you are scanning light-on-dark barcodes or raised barcodes,
enable this option.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 309
Parameter Description
Threshold Mode Sets the threshold mode the tool uses. Any data points
below the threshold are ignored and considered part of the
"background"; data points not excluded are considered part
of the barcode. Useful for cases where the surrounding
surface is similar to the intensity or height of the barcode
itself.
Subsampling ratio Downsamples the image. Can make the tool run faster. (A
value of at least 2 is usually necessary.)
Use validation Enables validation of the decoded string, using the string in
Validation for the comparison.
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 310
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 311
Bounding Box
The Bounding Box tool provides measurements related to the smallest box that contains the part (for
example, X position, Y position, width, length, etc.).
A bounding box can be vertical or rotated. A vertical bounding box provides the absolute position from
which the Position centroids tools are referenced.
The vertical bounding box X and Y correspond to the part frame of reference origin. For this reason
all X and Y measurements (except Bounding Box Global X and Global Y) are referenced to this point
when Frame of Reference on the Part Detection panel is set to Part. See Part Detection on
page 158 for more information.
2D View 3D View
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 312
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement Illustration
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 313
Measurement Illustration
Width
Length
Height
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 314
Measurement Illustration
Z Angle
Determines the rotation around the Z axis and the angle of
the longer side of the bounding box relative to the X axis.
Global X*
Determines the X position of the center of the bounding
box that contains the part on the surface from which the part
was extracted.
Global Y*
Determines the Y position of the center of the bounding
box that contains the part on the surface from which the part
was extracted.
Global Z Angle*
Determines the rotation of the longer side of the bounding
box around the Z axis on the surface from which the part was
extracted.
*These measurements are mostly useful with parts extracted from a surface. For more
information on parts, see Part Detection on page 158.
Features
Type Description
Parameters
Parameter Description
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 315
Parameter Description
Asymmetry Detection Resolves the orientation of an object over 360 degrees. The
possible values are:
0 – None
Region The region to which the tool's measurements will apply. For
more information, see Regions on page 206.
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 316
Circular Edge
The Circular Edge tool fits a circle to a circular edge in the scan data, using either height map or intensity
data. The edge can be the outer edge of a disc-like feature or the inner edge of a hole. The tool can
optionally work with partial data, as little as 1/4 of a circle, letting it work with rounded corners.
The tool lets you measure the position and radius of the circular feature and determine its roundness
error. The feature is expected to be relatively round and not, for example, ovoid. In the following images,
the outer edge of a circular feature is measured. The same tool could just as easily measure the
characteristics of one of the holes at the top.
2D View 3D View
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 317
Measurement Panel
The tool uses one of four standard methods to calculate roundness. The choice of method affects the
other measurements.
Some of the tool parameters are hidden unless Show Advanced Parameters is checked.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 318
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Rectangular calipers (dark blue) placed along circular path (dark blue), constrained by the region
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 319
The circular path can optionally be partial, and starts at a defined orientation around the Z axis. The
circular path can be as short as 1/4 of a circle, letting it work with rounded corners. Calipers extend
vertically to fill the entire region of interest.
Internally, the tool extracts profiles from the data within each caliper, running from the end of the caliper
closest to the center of the tool's region of interest to the end farthest from the center. The tool then
searches for steps in each profile that meet the criteria set by the tool’s settings, such as minimum
height, direction (whether it is rising or falling), and so on.
The tool places an edge point on each selected step. The tool then uses the edge points in all the calipers
to fit a circle: the various characteristics of the fitted circle are then returned as measurements.
Measurements
Measurement Illustration
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 320
Measurement Illustration
Radius
Roundness
Features
Type Description
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 321
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For more
information, see Source on page 205.
Region The region to which the tool's measurements will apply. For more information, see Regions on
page 206. The region also constrains the circular path along which the tool places the calipers.
Caliper Count The number of calipers the tool places along the circular path. Using a higher number of calipers
increases the amount of data available to the tool, but also increases the amount of time the tool
takes to run.
Choose a balance between the runtime of the tool and the number of calipers needed to get
enough edge points to properly fit the circle to the scan data.
Caliper Length Caliper Length is the length of the calipers (extending perpendicular to a tangent on the circular
Caliper Width caliper path, centered on the path). The length of the calipers determines the length of the
extracted profiles the tool examines for steps. Longer calipers increase the amount of data the tool
must analyze and therefore the time the tool takes to run; longer calipers can also include
unwanted steps when the tool searches for the edge.
Caliper Width is the width of the calipers (extending parallel to a tangent on the circular path).
A wider caliper increases the time the tool takes to run. It does however increase the number of
edge points, which may help the tool fit the circle.
Edge Source Specifies the type of data the tool uses. Either Height or Intensity.
Use intensity data as the edge source when contrast differences on a flat area of a target, which
would not be detected using height map data, are distinct, letting the tool use the detected edge to
fit the circle.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 322
Parameter Description
Step Direction Determines whether the expected step in the data rises or falls, or moves from valid to null or null to
valid. Note that this setting depends on the Edge Search Direction setting for its interpretation of
what "rises" and "falls." One of the following:
Edge Search Specifies the search direction along the calipers. Either Inward (toward the center of the region of
Direction interest) or Outward.
Edge Selection Type Determines which step the tool uses on each of the profiles internally extracted from the calipers
when there are multiple steps. An edge point is placed on each chosen step, and is used to fit the
circle. Steps must pass the criteria of the tool's settings, such as threshold and outlier exclusion.
Best: Selects the greatest step in the search direction on each profile.
First: Selects the first step in the search direction on each profile.
Last: Selects the last step in the search direction on each profile.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 323
Parameter Description
Outlier Fraction The percentage of outlier points to exclude. Setting this to a small value can help the tool fit the
circle better to the edge.
Outlier Fraction set to a low value: rejected outlier edge points are red.
Show Advanced When enabled, displays advanced settings. Note that most of these settings are applied even when
Parameters they are hidden. For information on these settings, see Advanced Parameters on the next page.
Show Detail When disabled, hides the calipers and caliper path, as well as the edge points.
Filters The filters that are applied to measurement values before they are output. For more information,
see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement tool sends a
pass or fail decision to the output. For more information, see Decisions on page 213.
The following parameters are hidden when Show Advanced Parameters is unchecked. All
advanced parameters, except Reference Plane, are applied when they are hidden. Mask
regions are not rendered, even though they are applied.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 324
Advanced Parameters
Parameter Description
Angle Start Angle Start is the starting angle, around the Z axis on the XY plane, for the circular path along
Angle Span which calipers are placed. Setting this to 0 aligns the start angle with the positive direction of the X
axis.
Angle Span is the length of the circular path along which calipers are placed.
You can use these settings together to set a partial path and exclude part of the data. In the
following image, the dark blue path starts to the right of the notch and ends to the left of it.
Path Spacing Sets the spacing between paths in the calipers used to extract the profiles that determine the edge.
A higher number of paths results in a higher number of edge points, which makes the fitting of the
edge line more accurate. However, a higher number of edge points results in a greater tool
execution time.
When Path Spacing is set to 0, the resolution of the scan data is used as the basis for spacing.
Path Width The size of the windows perpendicular to the path used to calculate an average for each data point
on a path profile. Useful to average out noise along the path caused by reflections, and so on.
If Path Width is set to 0, no averaging is performed (only the data point under the path is used).
For averaging along the path, use Step Smoothing (see below).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 325
Parameter Description
Absolute Threshold When Use Intensity is disabled, the setting specifies the minimum height difference between points
on a path profile for that step to be considered for an edge point.
The setting can be used to exclude smaller steps on a part that should not be considered for an
edge, or to exclude height differences caused by noise. When used in conjunction with Relative
Threshold, Absolute Threshold is typically set to a small value, greater than the general surface
roughness.
When Use Intensity is enabled, the setting specifies the minimum difference in intensity. (Acquire
Intensity must enabled in the Scan Mode panel.)
Use Relative When this option is enabled, the Relative Threshold field is displayed.
Threshold
The tool calculates a relative threshold by scaling the greatest height or intensity difference found
on the path profiles by the percentage in Relative Threshold. This lets you configure the tool
without knowing the actual step height in advance, and is useful for edges with varying step height.
For a height or intensity difference to be considered a valid step, both Absolute Threshold and
Relative Threshold must pass.
Step Smoothing The size of the windows along the path used to calculate an average for each data point on a path
profile. The setting is useful for averaging out noise.
If Step Smoothing is set to 0, no averaging is performed (only the data point under the path is
used).
For averaging perpendicular to the path, use Path Width (see above).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 326
Parameter Description
Step Width The distance, along a path profile, separating the points used to find steps on a path profile.
The setting is useful when you must detect a slope as an edge, rather than a sharply defined edge:
setting Step Width to a value greater than the width of the edge ensures that the tool measures the
height difference between the flat regions on either side of the edge. As a result, the height of the
step is accurately measured, and the edge is correctly located.
Setting Step Width wider than necessary can reduce the precision of edge
location.
Max Gap Fills in regions of missing data caused by an occlusion near the desired edge. Use this setting when
continuity on the target is expected. When Max Gap is set to a non-zero value, the tool holds and
extends the last data point on the low side next to an edge across a gap of null points, up to the
distance specified in Max Gap.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 327
Parameter Description
Include Null Edges Indicates whether null points (points where no height or intensity value is available, due to dropouts
or regions outside of the measurement range) are filled with the value in Null Fill Value as a general
“background level.” If Use Intensity (see above) is enabled, the intensity value in Intensity Null Fill
Value is also used.
A typical example is a discrete part produced by part detection of an object sitting on a flat
background. The background is not visible in the part, so the tool assumes that any null region are
at the background level.
To find edges along a region of null points, you must use either this option and an
appropriate value in Null Fill Value (and Intensity Null Fill Value if Use Intensity
is enabled) or Max Gap. Otherwise, only edges within areas of contiguous data will
be detected.
Null Fill Value The height value (in mm) used to replace null points not filled by Max Gap when Include Null Edges
is enabled.
Intensity Null Fill The intensity value (0-255) used to replace null points when Include Null Edges and Use Intensity
Value are enabled.
Mask Regions Lets you enable up to five regions that you can use to mask data you want the tool to ignore.
You can resize and reposition the mask regions using the mouse in the data viewer, or by
configuring values manually in the Mask Region sections the tool displays in the tool settings for
each region. You can only set the rotation of the mask regions manually by modifying the region's Z
angle parameter.
By default, when you add multiple mask regions, they are initially placed in the same position, one
on top of the other.
Reference Plane Uses the output of a Surface Plane tool as a reference plane. Useful to correct the scan data if the
target is slightly tilted.
When Show Advanced Parameters is unchecked and Reference Plane is set to a plane, the plane is
ignored.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 328
Parameter Description
Fit Type The method the tool uses to calculate the roundness of the feature. One of the following:
Minimum Zone Circle (MZC): If you choose this method, set the circle the tool uses with the Which
Circle parameter.
Maximum Inscribed Circle (MIC): Typically used to measure the inner edge of a circular feature,
such as a hole.
Minimum Circumscribed Circle (MCC): Typically used to measure the outer edge of a circular
feature.
If you load a job that contains an instance of the Circular Edge tool created using an earlier firmware
version, an additional parameter (LSC FIt Method) is displayed. It provides two options:
Least Square Method: This algorithm provides more accurate fit results than Iterative
Approximation on partial circle data. The execution time is also better on average, so this method
should be chosen in general.
Iterative Approximation: Legacy algorithm for compatibility with 5.2 SR2 and earlier.
Which Circle Tells the tool which circle (Inner or Outer) to use when Minimum Zone Circle is the fit method in Fit
Type.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 329
Countersunk Hole
The Countersunk Hole tool locates a countersunk circular opening within a region of interest on the
surface and provides measurements to evaluate characteristics of countersunk holes, including the
position (X, Y, and Z) of the center of the hole, outside radius of the hole, hole bevel angle, and the depth
of the hole. The countersunk hole can be on a surface at an angle to the sensor. The tool also supports
measuring holes drilled at an angle relative to the surrounding surface.
2D View 3D View
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 330
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 331
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement Illustration
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 332
Measurement Illustration
Outer Radius
Depth
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 333
Measurement Illustration
Bevel Radius
Bevel Angle
Cone
Counterbore
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 334
Measurement Illustration
X Angle
Cone
Y Angle
Counterbore
Counterbore Depth
Determines the depth of a counterbore.
Axis Tilt
Measures the tilt of the axis of the hole relative to the surface
surrounding the hole.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 335
Measurement Illustration
Axis Orientation
Measures the angle of the axis of the hole around the normal of the
surface surrounding the hole, relative to the X axis.
Features
Type Description
Center Point The center point of the countersunk hole. The Z position of
the center point is at the Z position of the surrounding
surface.
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's
measurements. For more information, see Source on page 205.
0 – Cone
1 – Counterbore
Nominal Bevel Angle The expected bevel angle of the countersunk hole.
Nominal Outer Radius The expected outer radius of the countersunk hole.
Nominal Inner Radius The expected inner radius of the countersunk hole.
Bevel Radius Offset The offset, relative to the surface that the countersunk hole is on, at which the
bevel radius will be measured.
Partial Detection Enable if only part of the hole is within the measurement region. If disabled, the
hole must be completely in the region of interest for results to be valid.
Plane Fit Range Excludes data beyond the specified distance from the plane surrounding the
hole. You can use this setting to exclude surfaces close to the countersunk hole
that step down from the plane surrounding the hole that could make
measurement of the hole less reliable.
Region The region to which the tool's measurements will apply. For more information,
see Regions on page 206.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 336
Parameter Description
Curved Surface Whether the surface that the countersunk hole is on is curved. When this
setting is enabled, specify the orientation of the curvature in degrees in
the Curve Orientation setting.
Curve Orientation The orientation of the curvature in degrees. Only visible when Curved Surface is
enabled.
Reference Regions The tool uses the reference regions to calculate the Z position of the hole. It is
typically used in cases where the surface around the hole is not flat.
When this option is set to Autoset, the algorithm automatically determines the
reference region. When the option is not set to Autoset, you must manually
specify one or two reference regions. The location of the reference region is
relative to the detected center of the hole and positioned on the nominal
surface plane.
When Reference Region is disabled, the tool measures the hole's Z position
using all the data in the measurement region, except for a bounding
rectangular region around the hole.
Tilt Correction Tilt of the target with respect to the alignment plane.
Custom: You must enter the X and Y angles manually in the X Angle and Y Angle
parameters (see below).
X Angle The X and Y angles you must specify when Tilt Correction is set to Custom.
Y Angle You can use the Surface Plane tool's X Angle and Y Angle measurements to get
the angle of the surrounding surface, and then copy those measurement's
values to the X Angle and Y Angle parameters of this tool.
Filters The filters that are applied to measurement values before they are output. For
more information, see Filters on page 215.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 337
Parameter Description
Decision The Max and Min settings define the range that determines whether the
measurement tool sends a pass or fail decision to the output. For more
information, see Decisions on page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Curvature
This tool is not supported on A and B revision Gocator 2100 and 2300 sensors. However, it is
supported on any accelerated sensors (PC or GoMax), including these models, and will appear
in emulator scenarios created using these sensors.
The Surface Curvature tool removes curvature from curved surfaces while preserving surface features or
defects, using a configurable polynomial order (the tool performs a 2D polynomial fit on X and Y to
process surfaces). You can then use the tool's output apply measurements to the "flattened" surface.
The tool does not support rotational scans (that is, polar "unwrapping").
In the following images, a curved surface (top) is flattened out (bottom), preserving the surface detail.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 338
The original, curved scan of a target.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 339
In the following image, a Surface Dimension tool's height measurement runs on the "flattened" output
(the Surface Curvature tool's Difference Surface output) to determine the height of one of the raised
areas:
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement
Processing Time
Data
Type Description
Fit Surface The fitted polynomial the tool uses to flatten the original
surface.
Difference Surface The “flattened” surface: this is the original surface with the
fitted polynomial removed.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 340
Parameters
Parameter Description
Stream The data that the tool will apply measurements to.
Polynomial Order Selects the order (or degree) of the polynomial to be fit to
the surface. A higher order results in a better fit but
increases processing time.
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Advanced Parameters
Parameter Description
Sampling Step The step in data points in both directions with which the surface is sampled. Choosing a
higher sampling step reduces the processing time the tool requires, but reduces fit accuracy.
Useful if the surface being processed has a large number of data points.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 341
Parameter Description
Exclude Features Lets you exclude features or surface details from the polynomial fit. This can allow you to get a
better fit on the surrounding surface.
Checking this option enables the Negative area, Positive area, and Iterative Steps
parameters. (See below.)
For example, in the following scan data, we would like to accurately measure the circular divots
and the small hole near the center of the data on the curved surface.
If the large feature to the left is not excluded for the polynomial fit, the fitted surface will and
therefore the measurements on the smaller features will be inaccurate. In the following
"flattened" scan data, without excluding the larger feature, the smaller features would be
difficult to accurately measure:
When the larger feature is excluded from the polynomial fitting, the surrounding surface and
the smaller features are more properly "flattened."
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 342
Parameter Description
Iterative Steps The number of times the tool repeats the feature exclusion calculation (see Exclude Features,
above).
Negative area These settings exclude the specified percentage of a histogram of the height values of the
Positive area scan data from the botom up (Negative area) and from the top down (Positive area),
respectively.
Number of Regions Lets you specify and configure one or more regions that the tool will process. Use this
parameter to limit the tool to specific areas on the target.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 343
Dimension
The Dimension tool returns various dimensional measurements of a part. You must specify two feature
types (see below).
2D View 3D View
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 344
Measurements
Measurement Illustration
Width
Length
Height
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 345
Measurement Illustration
Distance
Plane Distance
Center X
Center Y
Center Z
Parameters
Parameter Description
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 346
Parameter Description
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Direction Filter
This tool is not supported on A and B revision Gocator 2100 and 2300 sensors. However, it is
supported on any accelerated sensors (PC or GoMax), including these models, and will appear
in emulator scenarios created using these sensors.
The Surface Direction Filter helps exclude unwanted data points based on their “orientation” (relative to
surrounding data points) in 3D space, for example, data points resulting from reflections. The tool can
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 347
provide better results than median or height based filters. The tool lets you define up to 16 regions, and
for each region, configure the characteristics of the data points to exclude.
For example, in the following scan data, noise (in pink) appears to the right of three surface mount
components on a PCB. In this case, the "direction" (specifically, the polar angle) of the noise is roughly 75
to 85 degrees, relative to Z.
In the following scan data, the tool has removed the noise.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 348
Surface after direction filtering.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 349
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement
Processing Time
Data
Type Description
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 350
Parameters
Parameter Description
Stream The data that the tool will apply measurements to.
If you switch from one type of data to another (for example, from
section profile data to surface data), currently set input features will
become invalid, and you will need to choose features of the correct
data type.
Source The sensor, or combination of sensors, that provides data for the
tool's measurements. For more information, see Source on page 205.
Region Count The number of regions the tool applies filtering to.
Region {n} Lets you configure the size and position of region {n}.
Filters The filters that are applied to measurement values before they are
output. For more information, see Filters on page 215.
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision to the
output. For more information, see Decisions on page 213.
The following illustrates the angle parameters that control which data points are excluded in scan data
(see Region Filtering Parameters on the next page):
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 351
The number of neighboring points shown above is for illustrative purposes only.
Region {n} Max Z Angle the XY projection of the normal of the surface surrounding a data
point, where 0 degrees is defined as positive X and positive rotation
is clockwise around the Z axis.
Region {n} Min Polar Angle The minimum and maximum acceptable angles of the normal of the
Region {n} Max Polar Angle surface surrounding a data point with respect to the Z axis.
Region {n} Smooth Size A mean filter applied to the surface data before calculating the
normals in order to avoid abrupt normal changes due to noise.
Region {n} Noise Removal Eliminates noise that can be introduced by the tool's normal
calculation.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 352
For more information on anchoring, see Measurement Anchoring on page 216.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 353
Edge
The Edge tool fits a line to a straight edge in the scan data, using either height map or intensity data. The
tool's settings help fit the line when multiple potential edges are in the region of interest. After the tool
locates an edge, the position (X, Y, and Z) of the center of the edge line in the region of interest. The tool
also returns its angle around the Z axis, the step height between the upper and lower surfaces adjacent
to the edge, minimum and maximum error points to either side of the line, and a point count.
You can use the Z Angle measurement of the edge line with some tools to perform angle anchoring,
compensating for minor part rotations around the Z axis, greatly increasing repeatability between part
scans; for more information see Measurement Anchoring on page 216.
The minimum and maximum errors are useful for calculating a straightness value (using a script tool, for
example; for more information, see Script on page 483).
The tool can also generate edge line and center point geometric features that Feature tools can take as
input for measurement. For more information on Feature tools, see Feature Measurement on page 484.
2D View 3D View
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 354
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 355
Paths and Path Profiles
To fit an edge line to the scan data, the Surface Edge tool overlays evenly spaced, parallel paths (light
blue lines in the interface; see below) in the defined region of interest.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 356
For each path, a profile is generated internally from the height map’s data points that fall under or,
optionally, near the path. The tool then examines each path profile for steps (changes in height) that
meet the criteria set by the tool’s settings, such as minimum height, direction (whether it is rising or
falling), and so on.
For the step on each path profile that matches the settings, the tool places an edge point between the
upper and lower area (light blue diamonds in the interface). The tool then fits a line to those edge points
(yellow line in the interface). You can choose the orientation of the paths around the Z axis to
accommodate different edge orientations.
Measurements
Measurement Illustration
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 357
Measurement Illustration
Z Angle
Step Height
Min Error
Max Error
Point Count
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 358
Features
Type Description
Center Point The intersection point of the fitted edge line and a line
through the center of the region at the path angle.
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For more
information, see Source on page 205.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 359
Parameter Description
Use Intensity (This setting is only available when Acquire Intensity is enabled in the Scan Mode panel; for
more information, see Scan Modes on page 122.)
Uses intensity data rather than height data to find an edge. Useful when color differences on a
flat area of a target, which would not be detected using height map data, are distinct, letting you
use the detected "line" as an anchor source or perform geometric feature measurements.
Use Intensity enabled (intensity view): Surface Edge tool finds the edge using intensity data.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 360
Parameter Description
Use Intensity disabled (heightmap view of the same area): Surface Edge tool unable to find edge using
height data.
Number of Regions The number of regions the tool will use to fit the line. You must configure each region (see Region
{n} below).
Using multiple regions allows you to fit a line to an edge that is not straight along its entire
length or that is not continuous.
Region {n} The region or regions the tool uses to fit a line. For more information, see Regions on page 206.
The Search Direction setting applies to all of the regions.
You can configure the Z Angle of each region independently to accommodate the particularities
of the feature or target (for example, to exclude unwanted scan data next to one of the regions
in the fitting of the line to the edge).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 361
Parameter Description
Search Direction The search direction for steps, specified as an orientation around the Z axis, relative to the
X axis. Can be 0, 90, 180, or 270 degrees. Choose a value that is roughly perpendicular to the
edge on the target.
Fixed Angle When this option is enabled, the value in Fixed Angle Value replaces the value the Z Angle
measurement returns.
Useful when the angle of the feature is known and noise in the scan data could otherwise cause
the measurement to return an incorrect angle.
Fixed Angle Value The value the tool uses to locate the edge and returns for the Z Angle measurement. You must
enable Fixed Angle to set this value.
Path Spacing Sets the spacing between paths in the measurement region used to extract the profiles that
determine the edge. A higher number of paths results in a higher number of edge points, which
makes the fitting of the edge line more accurate. However, a higher number of edge points
results in a greater tool execution time.
When Path Spacing is set to 0, the resolution of the scan data is used as the basis for spacing.
No paths are displayed in the data viewer in this case.
Path Width The size of the windows perpendicular to the path used to calculate an average for each data
point on a path profile. Useful to average out noise along the path caused by reflections, and so
on.
If Path Width is set to 0, no averaging is performed (only the data point under the path is used).
For averaging along the path, use Step Smoothing (see below).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 362
Parameter Description
Outlier Fraction The percentage of outlier points to exclude. Setting this to a small value can help the tool fit the
line better to the edge.
Outlier Fraction set to a low value: rejected outlier edge points are dark blue.
Selection Type Determines which step the tool uses on each path profile when there are multiple steps in the
profile. An edge point is placed on each chosen step. Steps must pass the criteria of the tool's
Absolute Threshold, Step Direction, and Relative Threshold settings.
Step Direction Determines whether the expected step rises or falls along the path. Either Rising, Falling, or
Rising or Falling.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 363
Parameter Description
Absolute Threshold When Use Intensity is disabled, the setting specifies the minimum height difference between
points on a path profile for that step to be considered for an edge point.
The setting can be used to exclude smaller steps on a part that should not be considered for an
edge, or to exclude height differences caused by noise. When used in conjunction with Relative
Threshold, Absolute Threshold is typically set to a small value, greater than the general surface
roughness.
In the image below, when Absolute Threshold is left at the default of 0, all steps are included as
possible candidates for an edge, and will be used to fit an edge line. The resulting edge line is
angled upward to the left.
When Absolute Threshold is set to 3 with the same data (see image below), steps going from the
yellow to pink regions (roughly 1.37 mm) and from the blue to yellow regions (roughly 2 mm) are
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 364
Parameter Description
excluded. Only steps from the blue to pink regions (roughly 3 mm) are included.
When Use Intensity is enabled, the setting specifies the minimum difference in intensity.
(Acquire Intensity must enabled in the Scan Mode panel.)
Use Relative Threshold When this option is enabled, the Relative Threshold field is displayed.
The tool calculates a relative threshold by scaling the greatest height or intensity difference
found on the path profiles by the percentage in Relative Threshold. This lets you configure the
tool without knowing the actual step height in advance, and is useful for edges with varying step
height.
For a height or intensity difference to be considered a valid step, both Absolute Threshold and
Relative Threshold must pass.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 365
Parameter Description
Step Smoothing The size of the windows along the path used to calculate an average for each data point on a
path profile. The setting is useful for averaging out noise.
If Step Smoothing is set to 0, no averaging is performed (only the data point under the path is
used).
For averaging perpendicular to the path, use Path Width (see above).
Step Width The distance, along a path profile, separating the points used to find steps on a path profile.
The setting is useful when you must detect a slope as an edge, rather than a sharply defined
edge: setting Step Width to a value greater than the width of the edge ensures that the tool
measures the height difference between the flat regions on either side of the edge. As a result,
the height of the step is accurately measured, and the edge is correctly located.
Setting Step Width wider than necessary can reduce the precision of edge
location.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 366
Parameter Description
Max Gap Fills in regions of missing data caused by an occlusion near the desired edge. Use this setting
when continuity on the target is expected. When Max Gap is set to a non-zero value, the tool
holds and extends the last data point on the low side next to an edge across a gap of null
points, up to the distance specified in Max Gap.
Include Null Edges Indicates whether null points (points where no height or intensity value is available, due to
dropouts or regions outside of the measurement range) are filled with the value in Null Fill Value
as a general “background level.” If Use Intensity (see above) is enabled, the intensity value in
Intensity Null Fill Value is also used.
A typical example is a discrete part produced by part detection of an object sitting on a flat
background. The background is not visible in the part, so the tool assumes that any null region
are at the background level.
To find edges along a region of null points, you must use either this option
and an appropriate value in Null Fill Value (and Intensity Null Fill Value if Use
Intensity is enabled) or Max Gap. Otherwise, only edges within areas of
contiguous data will be detected.
Null Fill Value The height value (in mm) used to replace null points not filled by Max Gap when Include Null
Edges is enabled.
Intensity Null Fill Value The intensity value (0-255) used to replace null points when Include Null Edges and Use
Intensity are enabled.
Show Detail When disabled, hides the light blue path lines and edge points.
Filters The filters that are applied to measurement values before they are output. For more information,
see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement tool
sends a pass or fail decision to the output. For more information, see Decisions on page 213.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 367
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 368
Ellipse
The Ellipse tool provides measurements for the major and minor axis lengths of an ellipse roughly
aligned to the part's shape in the XY plane, and also for the ratio of the major and minor axis lengths and
for the orientation angle of the ellipse. The tool is typically used to find the general orientation of a part,
for example, potatoes on a conveyor that are longer in one dimension than the other.
Note that the ellipse fit is not the minimum area ellipse around the data. (Technically, it is the ellipse with
matching moments as the data.) For surfaces with no holes, this results in an ellipse approximately the
same size and orientation of the part. But for surfaces with holes, the resulting ellipse can be larger than
the part.
3D View
2D View
Measurement Panel
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 369
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement Illustration
Major
Minor
Ratio
Z Angle
Features
Type Description
Major Axis A line representing the major axis of the fitted ellipse.
Minor Axis A line representing the minor axis of the fitted ellipse.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 370
Parameters
Parameter Description
Asymmetry Detection Resolves the orientation of an object over 360 degrees. The
possible values are:
0 – None
Region The region to which the tool's measurements will apply. For
more information, see Regions on page 206.
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 371
Extend
This tool is not supported on A and B revision Gocator 2100 and 2300 sensors. However, it is
supported on any accelerated sensors (PC or GoMax), including these models, and will appear
in emulator scenarios created using these sensors.
The Extend tool creates a new surface by appending part of the previous frame's data to the current
frame's data. The tool outputs the new surface data, which can be used as input by other tools. The tool
is especially useful when scans are performed using fixed length surface generation, where parts might
be split between two frames. (For more information on surface generation, see Surface Generation on
page 154.)
Data is only appended in one direction. Partial objects in the resulting surface output from the tool must
be filtered out using downstream tools, for example, excluding them based on the expected area.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 372
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Data
Type Description
Extended Surface Data containing an extended surface, available for use as input in the Stream drop-down in
other tools.
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For
more information, see Source on page 205.
Direction Determines whether the previous frame's data is appended above or below the current
frame's data.
One of the following. Note that these settings depend on whether the trigger source has been
set to Encoder (see Trigger Settings on page 127).
l Auto: Choose this when Encoder is selected as the trigger source, in which case the tool
will know the direction of travel relative to encoder increase / decrease.
l Forward: Choose this when the trigger source is not set to Encoder and the direction of
motion is the same as the increase of the encoder.
l Backward: Choose this option when the trigger source is not set to Encoder and the
direction of motion is the opposite of the increase of the encoder.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 373
Parameter Description
Overlap Length The amount, in millimeters, of the previous frame's data to append to the current frame's
data. The combination will be output as tool data. Choose the overlap length to accommodate
the size of your scan targets.
l Lock: Lets you lock the current processing and outputs of the tool. Useful when you need
to add another tool that will use this tool's output (for example, a Surface Section tool). If
you do not lock the tool, as soon as you add the other tool, the output is cleared, which
means you must re-execute the combined output again to configure the additional tool.
Be sure to unlock the tool after you have configured any other tools.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 374
Filter
This tool is not supported on A and B revision Gocator 2100 and 2300 sensors. However, it is
supported on any accelerated sensors (PC or GoMax), including these models, and will appear
in emulator scenarios created using these sensors.
The Filter tool provides several common vision processing filters that you can apply to surface data, as
well as a two "cropping" filters that output a subset of the surface data, letting you pre-process scan data
to get more repeatable measurements. You can enable up to seven of the filters at once, in any order.
Filters in the tool are chained together. Any Surface or Feature tool can use the resulting filtered surface
data as input, via the tool's Stream drop-down.
The Filter tool provides no measurements or decisions, as its only purpose is to output processed
surface data.
Tool Setup
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 375
Settings and Available Filters
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For
more information, see Source on page 205.
Can only accept Surface scan data (that is, cannot accept data from other tools).
Region The region whose data the tool will apply filters to. Only data within the region is output to
other tools.
Use Intensity If enabled, the tool uses intensity data instead of heightmap data. Only available if Acquire
Intensity is enabled on the Scan page during the scan; for more information, see Scan
Modes on page 122.
Kernel Units Specifies whether filters use data points (pts) or millimeters (mm).
Number of Filters Specifies the number of filters you want to chain together. You can specify up to seven
filters.
Filter Type For each filter, specifies the type of filter. For more information on the available filters, see
Filters below.
Level The kernel size used by the Median filter. High is a 5x5 square kernel. Low is a 3x3 square
kernel.
Threshold The threshold that the filter uses. (Not available on all filters.)
Symmetry One of the following: Symmetrical, Horizontal, or Vertical. (Not available on all filters.)
Kernel Size The kernel size that the filter uses. (Not available on all filters.)
Filters
Name Description
Erode Applies an erosion filter. Lets you specify the direction of the erosion; one of the following:
l Horizontal
l Vertical
l Symmetrical
Dilation Applies a dilation filter. Lets you specify the direction of the dilation; one of the following:
l Horizontal
l Vertical
l Symmetrical
Morph Gradient Applies a morphological gradient. The difference between dilation and erosion.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 376
Name Description
Lets you specify the direction of the filter; one of the following:
l Horizontal
l Vertical
l Symmetrical
Laplacian Applies a Laplacian filter. Useful for detecting areas of distinct edges. Uses the following
kernel:
Binarize Sets height values to a fixed value for each point that is present in the data. Can be used
with a region Z offset to threshold points above/below a Z value.
Percentile Limits the scan data to points between the values you set in High Percentile and Low
Percentile, which are displayed when you choose this option.
Relative Threshold Crops scan data based on user-specified minimum and a maximum heights. Use Reference
Region to set the heights relative to a reference region.
Mask With Input Uses the surface input into the tool as a mask on the data. Any points in the filtered data
will be set to null if the input surface is null at the same location.
For example, the Gaussian filter can extend data along the edges, adding data in areas
that contain null values. This filter would remove data that the Gaussian filter introduces,
preserving the null values.
This filter should follow any filter that introduces this kind of unwanted data.
Data
Type Description
Filtered Surface The filtered data, available for use as input in the Stream
drop-down in other tools.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 377
For more information on anchoring, see Measurement Anchoring on page 216.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 378
Flatness
This tool is not supported on A and B revision Gocator 2100 and 2300 sensors. However, it is
supported on any accelerated sensors (PC or GoMax), including these models, and will appear
in emulator scenarios created using these sensors.
The Flatness tool returns various measurements related to the flatness of one or more regions on the
surface of your target. The tool is ideal for general fit and finish inspection.
The tool lets you set a grid over a specific region, or more flexibly with multiple individual regions
manually. In each case, "local" minimum and maximum heights, as well as flatness indicators (maximum -
minimum), are returned (for grid cells or individual regions, depending on the tool's settings). In addition,
"global" minimum, maximum, and flatness measurements, that combine data from all flatness
measurement areas, can also be returned. The tool measures the maximum and minimum distances
from a different best-fit plane for each local measurement, and from another plane fit to all data for the
"global" measurements.
You can control how many data points the tool uses in its calculations to account for noise or smooth
data, or otherwise exclude unwanted data.
When you configure the tool to use a grid that contains more than 15 cells, only the first 15 local
measurements (which correspond to the first 15 cells of the grid) are displayed in the web
interface. Flatness results for cells beyond 15 are however available in the tool data.
2D View 3D View
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 379
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement
Global Max
Global Min
Global Flatness
The maximum distance, minimum distance, and flatness (maximum - minimum) calculated using the valid data from all
the cells in the grid (when Region Mode is set to Grid Pattern), or all the individual regions (when Region Mode is set to
Flexible).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 380
Measurement
The maximum distance, minimum distance, and flatness (maximum - minimum) calculated using the valid data points
from a specific grid cell (when Region Mode is set to Grid Pattern), or an individual regions (when Region Mode is set to
Flexible).
Clicking a local measurement in the list of measurements selects corresponding the cell or region in the data viewer.
When a local measurement is selected, changing the value of Grid Cell to Display has no effect.
Data
Type Description
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For more
information, see Source on page 205.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 381
Parameter Description
Region Mode Determines how flatness measurement areas are set up on the target. One of the following:
Grid Pattern: The tool determines flatness in a grid you define on the target. This option enables
settings that let you set a region that will contain the grid, as well as the width and length of the
grid cells.
Flexible: The tool determines flatness in one or more (up to 15) regions that you define
individually on the target.
Cell Width (X) These settings determine the size of the cells in the grid.
Region {n} When Region Mode is set to Flexible, for each region, the tool displays a region definition.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 382
Parameter Description
Global Flatness Mode Chooses which points the tool uses to calculate global flatness. One of the following:
All Points: The tool uses all points in the measurement area (all flexible regions or the grid
pattern in the region).
Single Average Point: The tool uses an average of the points in the measurement area. When you
choose this option, the global measurements require at least four data points to calculate the
plane and statistics. This means that if you set Region Mode to Flexible, you must choose a
minimum of four regions; if you set Region Mode to Grid Pattern, the size of the grid and the cells
must result in at least four cells.
Data Filtering Lets you filter scan data before the tool performs its calculations.
Percentile - Limits the data to points between the values you set in High Percentile and Low
Percentile, which are displayed when you choose this option.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 383
Parameter Description
Grid Cell to Display When the Global Flatness measurement is selected, displays data points in the specified cell.
(used with Grid Pattern Display Points in Region must be enabled for this to work. (When a local measurement is
Unit Lets you choose which units the tool uses for measurement results. One of the following:
l um (micrometers)
l mm (millimeters)
Filters The filters that are applied to measurement values before they are output. For more information,
see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement tool
sends a pass or fail decision to the output. For more information, see Decisions on page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 384
Hole
The Hole tool measures a circular opening within a region
of interest on the surface and returns its position and
radius.
The tool does not search for or detect the
feature. The tool expects that the feature,
conforming reasonably well to the defined
parameters, is present and that it is on a
sufficiently uniform background.
3D View
2D View
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 385
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 386
Measurements, Features, and Settings
Measurements
Measurement Illustration
Radius
Features
Type Description
Center Point The center point of the hole. The Z position of the center
point is at the Z position of the surrounding surface.
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For more
information, see Source on page 205.
Radius Tolerance The maximum variation from the nominal radius (+/- from the nominal radius).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 387
Parameter Description
Partial Detection Enable if only part of the hole is within the measurement region. If disabled, the hole must be
completely in the region of interest for results to be valid.
Depth Limit Data below this limit (relative to the surface) is excluded from the hole calculations.
Region The region to which the tool's measurements will apply. For more information, see Regions on
page 206.
Reference Region The tool uses the reference regions to calculate the Z position of the hole. It is typically used in
cases where the surface around the hole is not flat.
When this option is set to Autoset, the algorithm automatically determines the reference region.
When the option is not set to Autoset, you must manually specify one or two reference regions.
The location of the reference region is relative to the detected center of the hole and positioned
on the nominal surface plane.
When Reference Region is disabled, the tool measures the hole's Z position using all the data in
the measurement region, except for a bounding rectangular region around the hole.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 388
Parameter Description
Tilt Correction Tilt of the target with respect to the alignment plane.
Autoset: The tool automatically detects the tilt. The measurement region to cover more areas on
the surface plane than other planes.
Custom: You must enter the X and Y angles manually in the X Angle and Y Angle parameters (see
below).
X Angle The X and Y angles you must specify when Tilt Correction is set to Custom.
Y Angle You can use the Surface Plane tool's X Angle and Y Angle measurements to get the angle of the
surrounding surface, and then copy those measurement's values to the X Angle and Y Angle
parameters of this tool. For more information, see Plane.
Filters The filters that are applied to measurement values before they are output. For more information,
see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement tool
sends a pass or fail decision to the output. For more information, see Decisions on page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Measurement Region
The center of the hole must be inside the measurement region, even if the Partial Detection option is
enabled.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 389
Mask
The Surface Mask tool lets you extract up to 16 regions of data from a surface. Each region’s size,
position, and shape (circular, elliptical, polygonal, and rectangular) can be individually configured, and
regions can overlap. The tool can also exclude inner data of circular and elliptical regions, letting you
extract rings of surface data.
The resulting surface can then be further processed or measured by other tools.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 390
A circle region box containing a partial ring (cyan)
The image below shows the extracted data. The extracted surface data can then be further processed by
other tools, or measurements can be applied to the surface data.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 391
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 392
Circle Diameter is non-zero. Note that the "length" of the partial region extends from the start angle. In
the following illustration, the start angle (θ) is 135 degrees relative to positive X, and the region extends
270 degrees (δ) clockwise around Z.
Note that the angles defining a partial circular/elliptical region are relative to the region, and not the
sensor's coordinate system. So a region rotated 30 degrees rotates the start angle and angle range by 30
degrees.
When you set a region type to Ellipse, instead of the inner circle diameter, you must set the major and
minor axes of the inner ellipse.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 393
Measurements and Settings
Measurements
Measurement
Processing Time
Data
Type Description
Parameters
Parameter Description
Stream The data that the tool will apply measurements to.
This setting is only displayed when data from another tool is available as input for this tool.
If you switch from one type of data to another (for example, from section profile data to
surface data), currently set input features will become invalid, and you will need to choose
features of the correct data type.
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For
more information, see Source on page 205.
Number of Regions The number of regions the tool uses to extract surface data. You can define up to 16 regions.
When you specify more than one region, the regions are initially stacked on top of one
another, in the same location.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 394
Parameter Description
Region Type {n} For each region, the type. Regions can overlap. One of the following. (For more information on
the settings you use with the Circle and Ellipse types, see Working with Circular and Elliptical
Regions on page 392.
Circle
Extracts a circular region from the surface data, constrained by a square region.
Set the region's inner circle (inner cyan circle below) using the Inner Circle Diameter
parameter to extract annular data.
Use the Sector Start Angle and Sector Angle Range settings to extract a partial circular or
elliptical region.
Ellipse
Extracts an elliptical region from the surface data, constrained by a square or rectangular
region.
Set the region's inner ellipse (inner cyan ellipse below) using the Inner Ellipse Major Axis and
Inner Ellipse Minor Axis parameters to extract annular data.
Use the Sector Start Angle and Sector Angle Range settings to extract a partial circular or
elliptical region.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 395
Parameter Description
Polygon
Extracts a polygonal region with the number of vertices specified in Vertex Count. You can
define the shape of the polygon using a mouse in the data viewer, dragging and dropping the
vertex points.
Note that you can't adjust the height of a polygon region: it occupies the entire vertical space
available:
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 396
Parameter Description
Rectangle
Inner Circle Diameter Defines the diameter of the inner circle when Region Type {n} is set to Circle.
Set this parameter to a value greater than 0 to extract a ring of data. Set this parameter to 0 to
extract a circle of data.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 397
Parameter Description
Inner Ellipse Major Axis Defines the major and minor axes of the inner ellipse, respectively, when Region Type {n} is
Set this parameter to a value greater than 0 to extract a ring of data. Set this parameter to 0 to
extract an elliptical disk of data.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 398
Parameter Description
Sector Start Angle Use these parameters together to extract a partial ring of data. Sector Start Angle controls
Sector Angle Range the starting angle of the data, whereas Sector Angle Range controls the length of the arc.
Note that the angles and ranges in these parameters are measured clockwise around Z, where
0 degrees is along the positive X axis.
These settings are only displayed when a region's type is set to Circle or Ellipse.
For example, in the first image below, Sector Start Angle is set to 135, and Sector Angle
Range is set to 270. The resulting extracted partial ring (or annular data) is shown below that.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 399
Parameter Description
Filters The filters that are applied to measurement values before they are output. For more
information, see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement tool
sends a pass or fail decision to the output. For more information, see Decisions on page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
OCR
This tool requires a GoMax-accelerated sensor.
For more information on GoMax, see the GoMax user manual.
The Surface OCR (optical character recognition) tool lets you extract a string of text from surfaces, using
either heightmap or intensity scan data. The tool is font-independent and already trained. The tool
therefore lets you implement OCR without the need for a separate 2D camera system.
You can use the String Encoding tool to extract the string and pass it as output to a PLC; for more
information, see String Encoding on page 441. The extracted string is also available via the SDK; for
information on the SDK, see GoSDK on page 813 and the SDK reference documentation.
The tool does not support multi-line character recognition, and the text must be rotated so that it is
human-readable from left to right along the X axis.
When configuring the tool, use the Diagnostic Image data output, on the Output tab, to help set
the thresholding parameters correctly.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 400
2D View 3D View
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement
Time
Found
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 401
Data
Type Description
Diagnostic Image The data the tool uses to perform optical character
recognition.
Output String A string containing the recognized text. (This data is not
currently visualized in the data viewer.)
Parameters
Parameter Description
Stream The data that the tool will apply measurements to.
This setting is only displayed when data from another tool is available as input for this tool.
If you switch from one type of data to another (for example, from section profile data to
surface data), currently set input features will become invalid, and you will need to choose
features of the correct data type.
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For
more information, see Source on page 205.
Data Type The type of data the tool uses (Heightmap or Intensity).
If this option is not checked, the tool uses data from the entire active area.
Region The region in which the tool performs OCR. For more information, see Regions on page 206.
Threshold Mode Determines the threshold the tool uses to identify characters relative to the background
data. One of the following:
Default – The default used by tesseract with OTSU adaptive thresholding method. Use this
mode if the scan data has been pre-processed to remove any tilt of the surface on which you
want to perform OCR, for example using Surface Transform; for more information, see
Transform on page 464.
Local Threshold – The tool varies the threshold for each pixel based on the minimum and
maximum values within a moving window over the region, using the specified window size
and multiplier (see below). This method can compensate for intensity and height gradients.
Manual Threshold – The tool uses a single, fixed threshold for the entire region (see Manual
Threshold below).
Local Threshold Window The window size the tool uses for local thresholding. The window size should generally be
Size larger than the size of the characters being detected.
Threshold Multiplier The multiplier the tool uses for local thresholding. Typically set to a value close to 1.
Manual Threshold The manual threshold the tool uses, expressed as a percentage, converted to a 0-255 range,
relative to minimum and maximum values within the region.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 402
Parameter Description
Mode Limits the characters the tool will recognize. Choose the mode based on the expected types
of characters in the target. One of the following:
Whitelist – Only attempts to recognize the characters in the Whitelist parameter that this
option displays.
Blacklist – Will not attempt to recognize characters in the Blacklist parameter that this
option displays.
Whitelist The whitelist or blacklist of characters that the tool will attempt to recognize or ignore,
Blacklist respectively. These parameters are case sensitive. The list of characters is a simple string of
characters.
Invert Swaps intensity values in the data the tool uses to perform OCR. Use this if you need to
perform OCR on light text on a dark background. (The OCR library the tool uses expects dark
text on a light background.)
For heightmap data, the tool swaps the "high" and "low" values. For example, in the second
image below, the height values used for the text and the surrounding surface (the highest
and lowest values in the heightmap legend to the right) are swapped when compared to the
first, non-inverted data.
Expected Text The string the tool compares the extracted text to. The parameter is case-sensitive and does
not support wild cards or truncation.
Filters The filters that are applied to measurement values before they are output. For more
information, see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement tool
sends a pass or fail decision to the output. For more information, see Decisions on page 213.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 403
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 404
Opening
The Opening tool locates rounded, rectangular,
and rounded corner openings. The opening can
be on a surface at an angle to the sensor.
The tool does not search for or
detect the feature. The tool expects
that the feature, conforming
reasonably well to the defined
parameters, is present and that it is
on a sufficiently uniform
background.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 405
3D View
2D View
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 406
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 407
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement Illustration
Width
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 408
Measurement Illustration
Length
Angle
Features
Type Description
Center Point The center point of the opening. The Z position of the
center point is at the Z position of the surrounding surface.
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For more
information, see Source on page 205.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 409
Parameter Description
Nominal Angle Nominal angle of the opening. The default orientation is the length of the opening along the X
axis.
The diagram above illustrates the case where the surface is not tilted. When the surface is tilted,
the orientation is defined with respect to the normal of the surface, not with respect to the X-Y
plane
Nominal Radius Nominal radius of the opening ends. If the opening type is set to rectangular, the radius setting is
disabled. The opening has an oval shape if the radius is equal to ½ of the width. The opening is a
rounded rectangle when the radius is less than ½ of the width.
Width Tolerance The maximum variation from the nominal width (+/- from the nominal value).
Length Tolerance The maximum variation from the nominal length (+/- from the nominal value).
Angle Tolerance The maximum variation from the nominal orientation (+/- from the nominal value).
Partial Detection Enable if only part of the opening is within the measurement region. If disabled, the opening
must be completely in the region of interest for results to be valid.
Depth Limit Data below this limit (relative to the surface) is excluded from the opening calculations.
Region The region to which the tool's measurements will apply. For more information, see Regions on
page 206.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 410
Parameter Description
Reference Regions The tool uses the reference regions to calculate the Z position of the opening. Reference regions
are relative to the center location of the feature. This option is typically used in cases where the
surface around the opening is not flat.
When the Reference Regions setting is disabled, the tool measures the opening's Z position using
the all data in the measurement region, except for a bounding rectangular region around the
opening.
With one or more reference regions, the algorithm calculates the Z positions as the average values
of the data within the regions.
When you place the reference region manually, all of the data is used, whether the data is inside
or outside the opening. You should place the reference region carefully.
Tilt Correction Tilt of the target with respect to the alignment plane.
Autoset: The tool automatically detects the tilt. The measurement region to cover more areas on
the surface plane than other planes.
Custom: You must enter the X and Y angles manually in the X Angle and Y Angle parameters (see
below).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 411
Parameter Description
X Angle The X and Y angles you must specify when Tilt Correction is set to Custom.
Y Angle You can use the Surface Plane tool's X Angle and Y Angle measurements to get the angle of the
surrounding surface, and then copy those measurement's values to the X Angle and Y Angle
parameters of this tool. For more information, see Plane.
Filters The filters that are applied to measurement values before they are output. For more information,
see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement tool sends
a pass or fail decision to the output. For more information, see Decisions on page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Measurement Region
The center and the two sides and ends of the opening must be within the measurement region, even if
Partial Detection is enabled.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 412
Plane
The Plane tool provides measurements that report a plane's position and orientation (X Angle, Y Angle, Z
Offset, Normal, Distance), as well as the maximum and average deviations from the plane.
The Z offset reported is the Z position at zero position on the X axis and the Y axis.
The results of the Angle X and Angle Y measurements can be used to manually customize the tilt angle in
the Hole, Opening, and Stud tools.
3D View
2D View
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 413
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 414
Measurements, Features, and Settings
Measurements
Measurement Illustration
Angle X
Angle Y
Offset Z
Standard Deviation
Min Error
Max Error
X Normal
Y Normal
Z Normal
Distance
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 415
Features
Type Description
Parameters
Parameter Description
Regions The region to which the tool's measurements will apply. For
more information, see Regions on page 206.
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 416
Position
The Position tool reports the X, Y, or Z position of a part. The feature type must be specified and is one
of the following: Average (the mean X, Y, and Z of the data points), Median (median X, Y, and Z of the
data points), Centroid (the centroid of the data considered as a volume with respect to the z = 0 plane),
Min X, Max X, Min Y, Max Y, Min Z, or Max Z.
2D View 3D View
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 417
Measurements, Features, and Settingss
Measurements
Measurement Illustration
Features
Type Description
Parameters
Parameter Description
Feature The feature the tool uses for its measurements. One of the
following:
l Average
l Median
l Centroid
l Max X
l Min X
l Max Y
l Min Y
l Max Z
l Min Z
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 418
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Section
The Surface Section tool lets you define a line on a surface (a "section") from which the tool extracts a
profile. You can apply any Profile tool to the resulting profile (see Profile Measurement on page 225).
Note that a section can have any XY orientation on the surface, but its profile is parallel to the Z axis.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 419
A section over a row of components
Note that profiles extracted from surfaces start at the point defined as the X/Y Start of the section.
Profiles are always displayed horizontally, with X increasing to the right. The origin of extracted profiles is
the beginning of the section, and not relative to the surface from which they are extracted.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 420
The Surface Section tool provides functionality similar to sections you can define on the Models page
(see Models on page 181). However, the Surface Section tool has a few advantages.
One advantage of the Surface Section tool is that you can anchor the tool to some other easily
identifiable feature on the scan target, which "shifts" the section in relation to that feature: this increases
repeatability.
Another advantage is that unlike sectioning generated from the Model page, the Surface Section can
take any surface as input, such as a combined surface (using Surface Extend or Stitch), a transformed
surface (using Surface Transformation), a filtered / corrected (Surface Filter and Surface Vibration
Correction), and so on.
Finally, the Surface Section tool provides measurements useful for calculating the global X/Y coordinates
of the resulting profile, using a Script tool Script (page 483). Even if you don't use anchors or the
measurements, LMI recommends using the Surface Section tool over model-based sections.
2D View 3D View
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 421
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement
X Start
Y Start
These measurements return the X and Y position of the start of the section, respectively.
X End
Y End
These measurements return the X and Y position of the end of the section, respectively.
Z Angle
Data
Type Description
Profile The profile the tool extracts from the surface. Available to
profile tools for profile measurement.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 422
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements.
For more information, see Source on page 205.
Section Contains the coordinates of the two points that define the section.
Point
X, Y, Z
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 423
Parameter Description
Averaging Width The width, in millimeters, of a window in which averaging of data points occurs. Use
this to compensate for noise around the section.
When set to 0, only data points directly under that section are used in the profile.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 424
Parameter Description
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 425
Parameter Description
Show Detail Determines whether data points (in red) are displayed under the section in the data
viewer. If this setting is disabled (as shown below), only the yellow line representing
the defined section is displayed.
Filters The filters that are applied to measurement values before they are output. For more
information, see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the
measurement tool sends a pass or fail decision to the output. For more information,
see Decisions on page 213.
Anchoring
Anchor Description
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 426
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 427
Segmentation
This tool is not supported on A and B revision Gocator 2100 and 2300 sensors. However, it is
supported on any accelerated sensors (PC or GoMax), including these models, and will appear
in emulator scenarios created using these sensors.
The Segmentation tool separates surface data into "segments," based on the tool's parameters.
Segments can be touching and overlapping to a certain degree. The Segmentation tool is especially
useful in the food industry, for example to identify food items that are too small or too big, or items that
are damaged.
The tool displays the area of each segment in the data view, but does not output them as
measurements.
The Segmentation tool can also be used as a second stage of processing after part detection. For
example, part detection could be used to detect a tray (containing parts), and the Segmentation tool
could then separate the parts within the tray.
To reduce processing time, consider using the decimation filter. For more information on this
filter, see Filters on page 151.
2D View 3D View
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 428
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 429
Measurements, Data, and Settings
Measurements
Measurement
Count
Returns the number of found segments identified, based on the tool's parameters.
Min Dimension
Max Dimension
The minimum and maximum dimensions among all of the identified segments.
Mean Width
Mean Length
Min Area
Max Area
The minimum and maximum area among all of the identified segments.
Sum Area
Mean Area
Min Height
Max Height
The minimum and maximum heights among all of the identified segments.
Mean Height
X Center {n}
Y Center {n}
The X and Y positions of the center of a part segmented from the surface.
The Number of Part Outputs setting determines the number of measurements listed in the Measurements tab.
Length {n}
Width {n}
The length and width of a part segmented from the surface. These are always the major and minor axis of a part,
respectively.
The Number of Part Outputs setting determines the number of measurements listed in the Measurements tab.
Features
Type Description
Center Point {n} The point representing the center of a segmented part.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 430
Data
Type Description
Diagnostics Surface Surface data you can use to evaluate the impact of the tool's
kern size and iteration settings, which the tool uses to
separate potential segments.
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For
more information, see Source on page 205.
Use region Indicates whether the tool uses the user-defined region.
If this option is not checked, the tool uses data from the entire active area.
Part Area Min The minimum and maximum areas in square millimeters for a part of the scan data to be
Part Aspect Min The minimum and maximum aspect ratios (minimum axis length in mm) / (maximum axis
Part Aspect Max length in mm) of the best fit ellipse to the segment contour points for a segment to qualify
to be added to the list of found segments.
Background Filter Kern Size These settings perform background cleanup. The greater each of these values is, the more
Background Filter Iterations the background surface for the segment search will be adjusted. You must find a balance
that removes noise adequately without degrading the segment find quality.
Part Edge Filter Kern Size Use this value to clean up overlapping edges and find segments when noise is present in
the scan data.
Part Edge Filter Threshold Controls the separation of the parts, increasing the gap between the parts so that they can
be detected more easily.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 431
Parameter Description
Use Margins When enabled, discards parts that are too close to the edge of the scanning area or the
region, based on the left, right, top, and bottom values.
In the following, a part is close to the edge of the XY scan area; the right margin is set to 0, so
the part is not discarded. (Total part count is 9.)
In the following, the right margin has been set to 10 mm. Because the center point of the
part is now within the margin, the tool discards the part. (Total part count is reduced to 8.)
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 432
Parameter Description
Ordering Orders the measurements, features, and surface data of the individual parts output by the
tool. Choose one of the following:
l Area - Large to small
l Area - Small to large
l Position - X increasing
l Position - X decreasing
l Position - Y increasing
l Position - Y decreasing
l Position - Z increasing
l Position - Z decreasing
Show Details Toggles whether the tool displays the index and area of each individual part.
Number of Part Outputs Determines the number of parts the tool outputs as measurements, features (center points
of parts), and surface data. Currently limited to 200 parts.
Filters The filters that are applied to measurement values before they are output. For more
information, see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement tool
sends a pass or fail decision to the output. For more information, see Decisions on page 213.
Anchoring
Anchor Description
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 433
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 434
Sphere
The Sphere tool lets you compute characteristics of a scanned sphere by specifying a region to inspect.
For example, you can use the tool to align a robot-mounted sensor to a ball-bar as shown in the images
below.
For the tool to work properly, the tool's region typically must be enabled and set, and properly
placed. For more information, see the table of parameters below.
2D View 3D View
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 435
Measurements, Features, and Settings
Measurements
Measurement Illustration
Center X
Center Y
Center Z
Radius
StandardDeviation
Features
Type Description
Center The center of the circle encompassing the widest part of the
fitted sphere.
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For more
information, see Source on page 205.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 436
Parameter Description
Region The region to which the tool's measurements will apply. For more information, see Regions on
page 206.
In order for the tool to correctly fit a sphere to the scan data, you must set the region so that it only
contains data from the sphere on the target.
Filters The filters that are applied to measurement values before they are output. For more information,
see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement tool sends a
pass or fail decision to the output. For more information, see Decisions on page 213.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 437
Stitch
This tool is not supported on A and B revision Gocator 2100 and 2300 sensors. However, it is
supported on any accelerated sensors (PC or GoMax), including these models, and will appear
in emulator scenarios created using these sensors.
The Stitch tool lets you combine up to 6 frames of scans into a single Surface scan. This lets you get a
much larger scan volume with fewer sensors (either in a single sensor system or a multi-sensor system).
For each scan, you can specify not only X, Y, and Z offsets (translations), but also X, Y, and Z angles
(rotations), defining its relationship with the others. This means that when the sensor system is mounted
to a robot, or if you are using, for example, an X-Y table, you can get a complete scan with fewer sensors.
The resulting combined scan can then be used as input by any other Surface or Feature tool from its
Stream drop-down.
You cannot define sections on the combined scan; for more information on sections, see Sections on
page 195.
Seams are often seen in combined data in stitching performed in anything other than along the
Y axis.
The tool returns one measurement, which simply indicates the number of scans successfully added to
the combined scan data.
In the following, the tool has combined the frames into a single surface.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 438
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement
Captured
Indicates the number of scans successfully added to the combined surface scan.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 439
Only one of the following data types will contain data, depending on whether Uniform Spacing
is enabled. For more information, see Scan Modes on page 122.
Data
Type Description
Stitched Surface The stitched surface scan, available for use as input in the
Stream drop-down in other tools. Contains uniform data
only and is empty if Uniform Spacing is disabled.
Stitched Raw Surface The stitched surface scan, available for use as input in the
Stream drop-down in other tools. Contains point cloud data
only and is empty if Uniform Spacing is enabled.
Parameters
Parameter Description
Surface Count The number of scans to combine into a single surface. For
each, a "Surface Parameters" section is added. The tool
accepts setting the number of scans to one: in this case it,
behaves like a transform tool.
Enforce Frame Order Restricts the stitching for specific frame indexes, starting at
the frame indicated in Start Frame Index. If unchecked, an
Operation drop-down is displayed (see below).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 440
Parameter Description
Reset On Start Clears buffers for the stitched surface when the sensor is
started. Useful for situations where the sensor is started
and stopped frequently (to capture a small number of
frames), rather than starting the sensor and letting it run
for a long period. Enable this parameter to prevent data
from a previous capture session being stitched with data
from the current capture session.
Surface Parameters {n} For each scan to be added to the combined surface scan, a
Surface Parameters checkbox is added. To configure the
parameters of the individual surfaces, check the box and
configure the settings. Unchecking the checkbox does not
disable the scan or its settings. The following settings are
available:
l Data Source
l X, Y, and Z Offset
l X, Y, and Z Angle
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
String Encoding
This tool is not supported on A and B revision Gocator 2100 and 2300 sensors. However, it is
supported on any accelerated sensors (PC or GoMax), including these models, and will appear
in emulator scenarios created using these sensors.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 441
The String Encoding tool is only available from the drop-down in the Tools panel after a tool
capable of providing compatible input, such as Surface Barcode or Surface OCR, has been
added.
The String Encoding tool takes the string output from a Surface Barcode or Surface OCR tool and
converts the characters to measurements that can be sent to PLCs. Measurements contain either a
single value for each character, or a four-character string. You can set the endianness of the four-
character string, letting you use the tool with any PLC.
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement
Measurement {n}
A decimal representation of either a single character or a four-character string, depending on the value of the Encoding
parameter. In both cases, values are displayed with a decimal point, and three places after the decimal point. The
number of measurements is set by the Number of Measurements parameter.
The last character is always a null terminator (\0). If the string passed to the tool is longer than the number of
measurements will accommodate, the last character is truncated and replaced with \0.
Parameters
Parameter Description
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 442
Parameter Description
Stream The data that the tool will apply measurements to.
Byte Order Selects the byte order the tool uses to encode strings in the
measurements. One of the following: Big Endian or Little
Endian.
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 443
Stud
The Stud tool measures the location and radius of a
stud.
The tool does not search for or detect the
feature. The tool expects that the feature,
conforming reasonably well to the defined
parameters, is present and that it is on a
sufficiently uniform background.
3D View
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 444
2D View
Measurement Panel
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 445
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement Illustration
Tip X
Tip Y
Tip Z
Base X
Base Y
Base Z
Radius
Features
Type Description
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's measurements. For
more information, see Source on page 205.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 446
Parameter Description
Base Height The height above the base surface that will be ignored when the (truncated) cone is fit to
the stud data.
Tip Height The height from the top of the surface that will be ignored when the (truncated) cone is fit
to the stud data.
Region The region to which the tool's measurements will apply. For more information, see Regions
on page 206.
Reference Regions The tool uses the reference regions to calculate the base plane of the stud. Reference
regions are relative to the base of the stud.
Tilt Correction Tilt of the target with respect to the alignment plane.
Autoset: The tool automatically detects the tilt. The measurement region to cover more
areas on the surface plane than other planes.
Custom: You must enter the X and Y angles manually in the X Angle and Y Angle
parameters (see below).
X Angle The X and Y angles you must specify when Tilt Correction is set to Custom.
Y Angle You can use the Surface Plane tool's X Angle and Y Angle measurements to get the angle of
the surrounding surface, and then copy those measurement's values to the X Angle and Y
Angle parameters of this tool. For more information, see Plane.
Radius Offset The distance from the tip of the stud from which the radius is measured.
Filters The filters that are applied to measurement values before they are output. For more
information, see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the measurement tool
sends a pass or fail decision to the output. For more information, see Decisions on page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Measurement Region
The tip and the side of the stud must be within the measurement region.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 447
Track
This tool is not supported on A and B revision Gocator 2100 and 2300 sensors. However, it is
supported on any accelerated sensors (PC or GoMax), including these models, and will appear
in emulator scenarios created using these sensors.
The Track tool lets you perform quality control and inspection along a path you define on representative
scan data. The Track tool is especially useful for inspecting materials such as glue / sealant beads. The
tool returns width and height measurements of the material, as well as OK and NG ("no good") counts,
which let you monitor material overflow and breaks. A major advantage of the tool is that it removes the
need to configure individual tools for each location along the path. You can use point and line geometric
features to anchor the tool (for more information on geometric features, see Geometric Features on
page 212).
Gocator sensors have a limited amount of space for storing path files. For this reason, when
working with large datasets, we recommend that you run the Track tool on a PC through the
Gocator accelerator. For more information on the accelerator, see Gocator Acceleration on
page 527.
2D View 3D View
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 448
Measurement Panel
You define the path along which the tool performs its internal measurements using a separate, PC-based
utility (the "track editor"). The following shows the relationship between the Track tool and the track
editor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 449
For more information on the track editor, see Using the Track Editor on page 461
All instances of the Track tool share the same path file set in File (ending in .user). For this
reason, you must be careful when editing or removing path files shared by another instance of
the tool.
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Key Concepts
The following are important concepts for using both the track editor (see Using the Track Editor on
page 461) and the Track tool itself:
Track: The material being measured, for example glue or sealant. The material can sit on a flat area on
the target, or sit in a groove where the material touches one or both sides.
Path: The ideal centerline of the track. You define the path in the track editor. You can define more than
one path for use on scanned targets, but the Track tool returns the combined results for all paths. For
more information on the track editor, see Using the Track Editor on page 461.
Ruler: A ruler is one of the areas perpendicular to the path you define. You define the size and spacing
of the rulers in the track editor. The Track tool extracts a profile from the surface data beneath a ruler
and performs internal measurements based on the values you choose in the Track tool's parameters.
Ruler profiles: The profiles extracted from the surface data under a ruler. The tool's internal
measurements, which are configured using the tool's settings, are applied to these profiles.
Segment: One portion of the path, between points created by clicking on an image of scan data in the
track editor. You can choose to configure rulers in segments independently, or choose to configure them
in a batch mode.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 450
Track tool in data viewer, showing a track (lighter grey), path (dark blue line), rulers running
perpendicular to the track (white lines centered on light blue dots).
Dots of other colors provide additional information (see below).
When you enable Show Measurement Results, the Track tool displays dots on the rulers to provide
the following information (see also the images below):
l Light blue dots: The data points in the ruler profile. When you enable Show Path and Rulers, the
tool displays a white line centered on these dots to indicate the location of the ruler.
l Dark blue dotes: The detected sides of the track. These represent the width of the track under that
ruler.
l Green dots: Center points on rulers that pass the criteria set in the tool. These count toward the "OK
Count" measurement.
l Red dots: Center points on rulers that fail at least one of the criteria set in the tool. These count
toward the "NG Count" measurement.
l Orange dots: The peak (highest) point on the ruler. If the center point (green or red) is the same as
the peak point, the tool only shows the center point.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 451
Three "OK" rulers, indicated by green center points. In the bottom two, the peak point (orange)
is slightly to the left of the center point (green).
Track Location
The tool attempts to locate the track using the profile data it extracts under each ruler, and does this by
first locating the "peak" (the highest point on the ruler profile, based on certain criteria) and then locating
the side points representing the "sides" of the track.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 452
Peak Detection
The tool determines the peak point on a ruler profile by moving two windows—one to each side of the
point being examined—and comparing the average height in those windows with the height of the point
being examined. (The size of these windows is specified in Center Window Size.) If the height of the
point being examined is greater than both the left and right average height by the value specified in
Center Threshold, that point is considered a candidate peak point. The tool uses the candidate point
with the highest average height over both windows as the peak point.
Side Detection
After the tool has located the peak point, it locates the sides of the track starting from the peak point.
You can choose between two methods for side detection: Maximum Gradient and Height Threshold.
Maximum Gradient:
Use this side detection method when the slope of the two sides show a clear drop-off. The following
settings define the area in which the tool searches for a maximum gradient, which will determine the
edge of the track.
Max Track Width The maximum width of the track over the ruler profile the tool searches for edge
points. The tool uses this value to limit where the edge of the track might be
detected. Set this to slightly larger than Side Window Size.
Height Threshold:
Use this side detection method when the slope of two sides is very gradual. The tool finds the left and
right edges by averaging the height of small fixed-size windows moving away from the peak point. Edge
points are the left-most and right-most window locations where the average height is below a minimum
height threshold.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 453
Center Point Detection
The Track tool calculates the center point as the mid point between the left and right side points. This
means that the center point may be different from the peak point.
3. In the Surface Track tool, choose Create from the Operation drop-down.
The tool creates a file (for example, SurfaceTrack-0000.user) containing scan data in "C:/LMI/Surface
Track". You will use the track editor to add path data to this file.
5. After you have finished editing the track data in the track editor, in the Surface Track tool, choose Load in
the Operation drop-down to load the path data you just created.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 454
For information on the tool's measurements and settings, see the below.
Measurements
Measurement Illustration
OK Count
Returns the number of rulers along the path that pass all of
the criteria set in the tool's parameters.
NG Count
Returns the number of rulers along the track path that fail
the criteria set in the tool's parameters. (They are "no good.")
Width Min
Width Max
Width Avg
Height Min
Height Max
Height Avg
Area Min
Area Max
Area Avg
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 455
Data
Type Description
Output Measurement Data containing the results from each ruler, namely:
l track ID
l segment ID
l track width
l track height
l track offset
l X position of the center point
l Y position of the center point
A sample included in the SDK package shows how you can use this
output data in an application.
Profiles List Diagnostics Surface Surface data created by combining the extracted profiles. Use for
diagnostics.
Main Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's
measurements. For more information, see Source on page 205.
Point Feature Point and line geometric features (produced by another tool) that you can select as
Line Feature anchors for translation and rotation transformations, respectively. Currently, you must
select both in order for anchoring to work. For more information on geometric
features, see Geometric Features on page 212.
File The CSV file that contains scan and path data. You add path data to the file using the
track editor. For more information on the track editor, see Using the Track Editor on
page 461.
Operation Provides operations related to the CSV scan / path data file. One of the following:
l Normal: Selected by the tool after you perform another file operation.
l Create: Creates a new CSV file for use with the track editor.
l Save: Saves changes made in the scan data, as well as the geometric features
used as anchors in the Point Feature and Line Feature settings, to the file
selected in File.
Interpolation Enables linear interpolation on the profile extracted from the rulers to achieve sub-
pixel accuracy in the width and height measurements.
Height Filter When Height Filter is enabled, use the Threshold Low and Threshold High settings
Threshold High to set a range to filter out noise or exclude other undesired data along the ruler
profiles.
Threshold Low
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 456
Parameter Description
Median Filter When Median Filter is enabled, specify the window the tool will use to smooth the
Window Size height values of the points in the ruler profiles in the Window Size setting.
Center Window Size The size of the left and right windows the tool moves along the ruler profile to detect
whether the point centered between the two is the highest point along a ruler (the
center point).
Set this to roughly 50% of the typical width of the track as a starting point.
Center Threshold The center point is determined by moving two side-by-side windows (left and right,
Center Window Size setting) over each ruler profile. At each point, the height value
between the two windows is compared to the average height of the left and right
windows.
If the center point height is greater, by the amount set in Center Threshold, than the
average height in both the left and right windows, that point is considered a
candidate center point. The candidate center point with the highest average height
over both windows is used as the center point.
Side Detection Method The method the tool uses to detect the two sides of the track. One of the following:
Maximum Gradient or Height Threshold. For more information on side detection
method settings, see Track on page 448.
Height Mode Determines how height values are interpreted in the tool's Nominal Height setting
and what the returned height measurements represent. One of the following:
Absolute Height - Height values are interpreted globally (the entire scan data).
Step Height - Height values are relative to the surrounding area of the track.
Show Path and Rulers Displays the path and rulers (as defined in the track editor) on the scan data.
Show Measurement Result Shows dots on each ruler representing the results of the internal measurements on
the profile extracted from the surface data under the ruler. For more information, see
Key Concepts on page 450.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 457
Parameter Description
In the following, the distance between the blue dots indicating the width of the track
under the ruler to the right (white vertical line) is greater than the width tolerance;
this is indicated by the red center point dot, and counts as a NG measurement. The
widths of the track under the two rulers to the left are within tolerance; this is
indicated by green center points, and count as OK measurements. The track is lighter
grey than the surrounding surface.
Nominal Height The expected height of the track. The expected height is the absolute height in the
scan data, not relative to the surrounding area. This setting applies to the peak point,
not the center point.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 458
Parameter Description
Height Tolerance The tolerance applied to the nominal height. This setting applies to the peak point,
not the center point.
In the following, the red center points indicate that the height at that point is outside
of the height tolerance. Green points indicate heights within tolerance. The track is
lighter grey than the surrounding surface.
Nominal Area The expected cross-sectional area under the rulers on the track.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 459
Parameter Description
Offset Tolerance The maximum allowed distance between the center (highest) point on a ruler and the
path. This setting applies to the center point.
In the following, the top and bottom center points (green) are at an acceptable
distance from the blue path. The red center points fail because they are too far from
the path. The track is lighter grey than the surrounding surface.
Filters The filters that are applied to measurement values before they are output. For more
information, see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the
measurement tool sends a pass or fail decision to the output. For more information,
see Decisions on page 213.
Anchoring
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 460
Using the Track Editor
You use the track editor to configure "path" and "ruler" information on a frame of scan data from a
sensor. The Track tool uses this information to inspect targets along the defined path.
In the track editor, you can define one or more paths, and configure rulers along these paths.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 461
Closeup of the track editor window, showing a track of material on a surface (yellow on green),
a path (blue segments; red segment for the currently selected segment),
path points (green dots), and rulers (white rectangles).
The following assumes that you have already scanned a representative target and created a
CSV file from within the Track tool. For more information, see the first steps of To configure the
Track tool: on page 454.
l PC: Choose this option if you are using the Track tool through the accelerator. The track editor will
retrieve the path data file from local (PC) storage and save changes there. (Choose the same if you
are using the emulator).
l Sensor: Choose this option if you are not using the accelerator. The track editor will retrieve the path
data file from the sensor at the IP address specified in the IP field. Because sensors have a limited
amount of space to store path data, only use this option for simple paths.
2. Click Load Tracks, navigate to "C:\LMI\SurfaceTrack" (if you have chosen PC as the source), and choose the
.user file you created using the Surface Track tool.
The track editor loads the data. If paths have been previously defined, they are also loaded.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 462
3. Do one or more of the following:
l Move the slider to the left or right to zoom in or out in the editor's viewer.
l Move the data in the track editor's window using the scrollbars or the mouse wheel.
l Set MinH and MaxH and then reload the track data to assign a narrower height range to the height
map colors. This may help make the track clearer in the editor.
After you have loaded the data, you must add a path and configure its rulers.
To add a path:
1. In the track editor, click on the middle of the track somewhere in the scan data, move the mouse pointer to
another location and click again.
A red segment between the first two green path points appears in the editor window.
You can move path points using the mouse at any time to adjust the path. You can also delete the last point
by clicking Delete Last. To delete all path points, click Delete All.
2. Continue clicking along the track to add more path points, building up the path.
When adding points on corners, add more points to follow the track more precisely.
3. Continue clicking until you complete the path along the track.
You cannot close the path: simply click close to the starting path point when you have finished.
5. (Optional) You can add other paths if necessary by clicking somewhere in the scan data after you have
saved the track data.
After you have finished adding a path, you must configure the rulers on the path (the dimensions and
the spacing of the rulers). You can choose to apply dimensions/spacing to all rulers in all segments at the
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 463
same time by checking Batch Setting. The settings also apply to all paths if you have defined more than
one path.
Otherwise, you must move through the individual path segments by clicking the spinner control in the
Segment field and set the ruler dimensions for each segment. If you have defined multiple paths, you
will have to click through the paths too, using the Track spinner.
The following table lists the ruler settings available in the track editor:
Length The dimension of the ruler perpendicular to the path. Be sure to use a value
large enough to cover the track from one side to another and to include enough
surface on each side of the track (the surface to which the material is applied) for
the Track tool to properly detect the track.
Space The space between rulers on the path. Because you will typically place path
points closer together around corners, you may need to use smaller spacing
around corners.
Transform
The Surface Transform tool generates a new surface based on the coordinate system of geometric
features the tool uses as input. The tool can take a zero-plane, line, and origin point to define this new
coordinate system. You can then apply the built-in measurement tools or GDK tools to this new surface
data. This could let you, for example, get the height of a feature relative to a slightly tilted or warped
adjacent or surrounding reference surface, rather than the absolute height in the original scan volume
relative to the sensor. The result is increased repeatability of your measurements.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 464
2D View 3D View
Measurement Panel
In Combinations of geometric feature inputs and results on page 467, the following geometric features
are used by a Surface Transform tool in various combinations (a plane, a line, and a point).
A Surface Plane tool, with the region set to a small left-facing angled surface
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 465
A Surface Edge tool, with the region set to the left edge of a raised surface (upper left of data viewer).
A Surface Position tool (maximum Z), with the region set to the raised point near the top of the data viewer.
Furthermore, in the sections below, two types of data are shown: the original (input) scan data and the
transformed data. When the tool displays the original data, it overlays indicators of the new,
transformed coordinate system on the data.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 466
A Surface Transform tool using all three types of geometric feature inputs.
The data viewer is set to display the input surface data with an overlay of the transformed coordinate system.
X, Y, and Z axes
The transformed axes are represented above by the red, green, and blue lines intersecting on the surface
data above. Note how these are rotated with respect to the original coordinate system (the background
grid, axes, and values along the axes).
Origin
The new origin is represented by the dark blue dot at the intersection of the transformed axes.
Plane
The bounding box that indicates where the transformed data is in relation to the original coordinate
system.
To switch between the original and transformed data, choose Surface or Tool in the first drop-
down above the data viewer, respectively.
Plane
Matches the input plane. Parallel to the old X axis. Old origin projected to plane.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 467
Original data with overlay
Transformed data
Line
The new plane contains the line. The intersection of the new Matches the line. Old origin projected onto the
plane and the old plane is perpendicular to the input line. line.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 468
Original data with overlay
Transformed data
The direction of the X axis depends on the tool generating the line that Surface Transform takes as input.
You may need to adjust the direction using the Add Fixed Transform settings.
Point
Through the input point, parallel to old Z=0 plane. Parallel to the old axis. The input point.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 469
Original data with overlay
Transformed data
Plane + Line
Matches the input plane. Line projected onto the plane. Old origin projected onto the projected line.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 470
Original data with overlay
Transformed data
Plane + Point
Matches the input plane. Parallel to the old X axis. At the input point, projected onto the plane.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 471
Original data with overlay
Transformed data
Line + Point
The new plane contains the line. The intersection of the Matches the line. The input point projected onto
new plane and the old plane is perpendicular to the input the line.
line.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 472
Original data with overlay
Transformed data
Matches the input plane. The input line projected onto the plane. The input point projected onto the input
line.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 473
Original data with overlay
Transformed data
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Scaling Modes
Line profile sensors have independent X and Y resolution settings: the former is set using the Spacing
setting (for more information, see Spacing on page 138), whereas the Y resolution is set using the
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 474
Spacing Interval setting in the Trigger panel (for more information, see Trigger Settings on page 127).
In many applications, the X resolution can be as much as 3-5 times higher than the Y resolution. Rotating
scan data around Z greater than 45 degrees (for example, with the Transform tool) when there is a large
difference between X and Y resolutions can result in significant data quality reduction. To avoid data
quality reduction, choose one of the scaling modes that the tool offers (see below).
Measurements
Measurement
The amount of time required for tool execution. Used for diagnostic purposes.
Data
Type Description
Transformed Surface The transformed surface. Available via the Stream drop-
down in other tools.
Parameters
Parameter Description
Source The sensor, or combination of sensors, that provides data for the tool's
measurements. For more information, see Source on page 205.
Input Plane The plane the tool uses to transform the surface scan data.
Input Line The line the tool uses to transform the surface scan data.
Input Point The point the tool uses to transform the surface scan data.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 475
Parameter Description
Scaling Mode Determines whether the tool scales the X or Y resolution so that they are the
same (a 1:1 ratio), or leaves the X and Y resolutions as the original. One of the
following.
l Optimal (uniform)
Brings the X/Y resolution ratio to 1:1 while preserving the pixel area. Best for
random rotation around Z. Provides a balance between the highest and
lowest possible resolutions, requiring an average amount of memory and
processing time compared to the High Oriented (uniform) or Low Oriented
(uniform) options.
l High Oriented (uniform)
Keeps the original X and Y resolution of the scan. Use this option only when
you expect little or no Z rotation. Otherwise, with X/Y resolution ratios that
are not 1:1, large rotation around Z results in severe data quality reduction
Add Fixed Transform When enabled, displays X, Y, and Z offset and angle fields you can use to set
additional transformations, which are applied after any transformations supplied
by the input geometric features.
Setting a fixed transformation can be useful if the geometric features the tool
uses results in data rotated to an unusual orientation; you could, for example,
rotate the data 90 or 180 degrees so that it is in the "expected" orientation, or
shift it so that it's easier to work with.
Use Region When this setting is enabled, the tool only outputs the surface contained in the
defined region.
Filters The filters that are applied to measurement values before they are output. For
more information, see Filters on page 215.
Decision The Max and Min settings define the range that determines whether the
measurement tool sends a pass or fail decision to the output. For more
information, see Decisions on page 213.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 476
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 477
Vibration Correction
This tool is not supported on A and B revision Gocator 2100 and 2300 sensors. However, it is
supported on any accelerated sensors (PC or GoMax), including these models, and will appear
in emulator scenarios created using these sensors.
The Vibration Correction tool analyzes variation in surface data to remove high frequency noise in the
data. The tool is useful for improving repeatability and accuracy of measurements when subtle
vibrations in your transport system introduce height variations. The tool's intended use is to send
corrected surface data to other tools.
The Vibration Correction tool requires at least 64 lines of data in the surface data it receives as
input to be able to output corrected surface data.
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 478
Data and Settings
Data
Type Description
Corrected Surface Surface data corrected for vibration, available for use as
input in the Stream drop-down in other tools.
Parameters
Parameter Description
Correct region only If enabled, only the area under the region is corrected for
vibration in the output surface data. This setting can be
useful if vibration regularly occurs in a specific area of the
scan data.
Use Region When enabled, lets you set a region and optionally choose
to apply vibration correction only to that region (using
Correct region only).
Region The region whose data the tool will use to calculate the
vibration correction.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 479
Volume
The Volume tool determines the volume, area, and thickness of a part.
2D View 3D View
Measurement Panel
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 480
Measurements
Measurement Illustration
Volume
Area
Measures area in the XY plane.
Thickness
Measures thickness (height) of a part.
Parameters
Parameter Description
Region The region to which the tool's measurements will apply. For
more information, see Regions on page 206.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 481
Parameter Description
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Anchoring
Anchor Description
A measurement must be enabled in the other tool for it to be available as an anchor. The anchor
measurement should also be properly configured before using it as an anchor.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 482
Script
A Script measurement can be used to program a custom measurement using a simplified C-based
syntax. A script measurement can produce multiple measurement values and decisions for the output.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 483
Feature Measurement
The following sections describe Gocator's Feature tools.
Feature tools produce measurements based on more complex geometry, letting you implement
applications more quickly by reducing dependence on writing scripts to accomplish these kinds of
measurements. Feature tools take geometric features generated by other tools as input and perform
measurements on those features.
The Circle geometric feature currently cannot be used by any of the built-in Feature tools.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 484
Create
The Feature Create tool lets you generate geometric features from other geometric features (ones
generated by other tools). For example, you can create a line from two points, or create a plane from a
point and a line. The tool can generate points, lines, circles, or planes. You can also extract measurement
values from the geometric features generated by other tools; you can use these values as decisions or
use them as anchors in other tools. The advantage of the Feature Create tool is that it means you need
to rely less on Script tools or SDK/GDK applications to perform complex geometric operations.
For example, in the following, a Feature Create tool takes the hole geometric features output by two
Surface Hole tools to generate a line geometric feature (near-vertical yellow line between the cyan hole
center points).
You could perform measurements on the resulting line (X, Y, and Z positional measurements on the line's
center point, and, more importantly, angle measurements on the line). You could also use the line's
Z angle as an anchor in other tool's in order to increase repeatability.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 485
Measurement Panel
The following sections describe the output types available in the Output drop-down, the inputs required
by each output, and the resulting output.
The resulting output is a line geometric feature connecting the two points.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 486
A line between the center point of a hole and the corner of the chip.
(The corner is the intersect point resulting from the Feature Intersect tool,
taking the left vertical and lower horizontal line edges of the chip as input.)
The X, Y, and Z measurements return the midpoint of the line. The X, Y, and Z Angle measurements
return the angle of the line.
For both of these types of line output, the X, Y, and Z measurements return the position of the point.
For perpendicular line output, the X, Y, and Z angle measurements return the angles of the line.
For parallel line output, the Z angle measurement returns the angle of the line; the X and Y angle
measurements both return 180.000.
In the following, the tool generates a roughly vertical line (yellow) perpendicular to the input line (cyan
line along the left edge of the large integrated circuit), passing through the input point (cyan dot at the
center of the hole).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 487
In the following, the tool generates a roughly horizontal line (yellow) parallel to the input line (cyan line
along the bottom edge of the large integrated circuit), passing through the input point (cyan dot at the
center of the hole).
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 488
Projected Line on Plane
Creates a line projected onto a plane.
The X, Y, and Z measurements return the center of the circle. The X, Y, and Z Angle measurements return
a 0.000 value.
Circle generated from the center points of the two holes and the corner of the chip (cyan points).
(The corner is the intersect point resulting from the Feature Intersect tool,
taking the left vertical and lower horizontal line edges of the chip as input.)
The X, Y, and Z measurements return the midpoint. The X, Y, and Z Angle measurements return the angle
of the line.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 489
A line generated at the intersection of two planes. The Z angle is indicated.
The X, Y, and Z measurements return the position of the intersect point. The X, Y, and Z Angle
measurements return 0.000 values.
A point generated at the intersection of two planes. The Y position is indicated here.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 490
Point from Line and Circle
Creates a point from a line and a circle (their intersection).
Point or Line
The Point and Line types of output take a point or a line geometric feature as input, respectively.
These outputs are useful if the tool takes features generated by another Feature Create tool as input, on
which you want to perform measurements in the second Feature Create tool. Also, this can be useful if
you have developed GDK tools that only generate geometric features (no measurements): you can use
this tool to extract those measurements.
For point output, the X, Y, and Z measurements return the X, Y, and Z position of the point; the angle
measurements all produce 0.000 as values.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 491
For line output, the X, Y, and Z measurements return the midpoint of the line. The Z Angle measurement
returns the angle of the line around the Z axis. The X angle is always 0.000, and the Y angle is always
180.000.
See Adding and Configuring a Measurement Tool on page 203 for instructions on how to add
measurement tools.
Measurements
Measurement Illustration
X, Y, Z
Note that even when enabled on the Features tab, not all features are generated. (For example, with
Line selected as the output type, only a line geometric feature can be generated: point, circle, and plane
features are not generated.)
Features
Type Description
Parameters
Parameter Description
Show Detail Toggles the display of the input geometric features in the
data viewer.
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 492
Dimension
The Feature Dimension tool provides dimensional measurements from a point geometric feature to a
reference point, line, or plane geometric feature.
Some examples:
l Obtaining the length of a stud by measuring the distance between its tip and base.
The sensor compares the measurement value with the values in Min and Max to yield a decision. For
more information on decisions, see Decisions on page 213.
See Adding and Configuring a Measurement Tool on page 203 for instructions on how to add
measurement tools.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 493
2D View 3D View
Measurement Panel
In the following measurement descriptions, the first geometric feature is set in the Point drop-
down. The second geometric feature is set in the Reference Feature drop-down.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 494
Measurements
Measurement Illustration
Width
Length
Height
Distance
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 495
Measurement Illustration
Plane Distance
Parameters
Parameter Description
Stream The data that the tool will apply measurements to.
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 496
Intersect
The Feature Intersect tool returns the intersection of a line geometric features and a reference line or
plane geometric feature. For line-line intersections, the lines are projected onto the Z = reference Z line
plane for features extracted from a surface, and the intersection of the lines projected onto the Y = 0
plane for features extracted from a profile. The angle measurement between the two lines is also
returned. The lines the tool takes as input are generated by other tools, such as Surface Edge or Surface
Ellipse.
The Feature Intersect tool saves you from having to write complicated calculations in script tools to find
intersect point between lines. Previously, calculating the intercept point of two lines was difficult and
prone to bugs, involving finding lines in indirect ways.
The Feature Intersect tool's positional measurements are particularly useful as anchor sources. For
example, you can easily find a corner point on a part from two edges (produced by two Surface Edge
tools) and using the X and Y positions as anchor sources.
When you use these positional anchors in combination with a Z Angle anchor from tools such as Surface
Edge, you can achieve extremely robust, repeatable measurements.
This tool's Angle measurement cannot be used as an angle anchor source. Only Z Angle
measurements can be used as angle anchor sources.
The Feature Intersect tool can also generate a point geometric feature representing the point of
intersection of the lines that the Feature Dimension tool can use in measurements.
The sensor compares the measurement value with the values in Min and Max to yield a decision. For
more information on decisions, see Decisions on page 213.
See Adding and Configuring a Measurement Tool on page 203 for instructions on how to add
measurement tools.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 497
2D View 3D View
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 498
Measurement Panel
Measurements
Measurement Illustration
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 499
Measurement Illustration
Angle
Features
Type Description
Parameters
Parameter Description
Stream The data that the tool will apply measurements to.
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 500
Robot Pose
This tool is not supported on A and B revision Gocator 2100 and 2300 sensors. However, it is
supported on any accelerated sensors (PC or GoMax), including these models, and will appear
in emulator scenarios created using these sensors.
The Feature Robot Pose tool takes geometric features as input and outputs positional and rotational
values. You can use these values in a robot system to control the robot.
In the following images, the Robot Pose tool has returned positional (X, Y, and Z) and rotational (roll,
pitch, and yaw) information on a part.
2D View 3D View
Measurement Panel
l A Plane geometric feature to determine roll and pitch (rotation around the X and Y axes)
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 501
Including a Line geometric feature lets the tool also return yaw (Z rotational information). For example,
to get pose information for the part shown below, you could first configure a Surface Bounding Box tool
and a Surface Plane tool.
Bounding Box tool. The tool is configured to rotate to accommodate the orientation of the part.
With both tools, you must enable the required feature outputs on the Feature tabs:
Enabled geometric features in Features tabs of Bounding Box and Plane tools, respectively.
Then select the features as input (the first three parameters) in the Robot Pose tool:
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 502
For information on adding, managing, and removing tools and measurements, as well as detailed
descriptions of settings common to most tools, see Tools Panel on page 203.
Measurements
Measurement Illustration
X, Y, Z
Data
Type Description
Matrix Data containing a matrix representing the same pose as the tool's measurements. It can be
deserialized into a GoRobotMatrix structure using the GoRobot library.
Parameters
Parameter Description
Point The Point geometric feature the tool extracts the X, Y, and Z
measurements from. This input is required.
Plane The Plane geometric feature the tool extracts the Roll and
Pitch measurements from. This input is required.
Z Angle Line The Line geometric feature the tool extracts the Yaw
measurement from.
This input is optional. If you omit it, the X and Y axes will be
parallel to the sensor's X and Y axes.
Decision The Max and Min settings define the range that determines
whether the measurement tool sends a pass or fail decision
to the output. For more information, see Decisions on
page 213.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 503
Scripts
Scripts use outputs from other measurement tools to produce custom measurements.
Similar to other measurement tools, a script measurement can output multiple measurement values and
decisions. Scripts are added, configured, and removed much like other measurement tools; for more
information on this, see Script under Profile Measurement on page 225 or Surface Measurement on
page 301.
Scripts use a simplified C-based syntax. The following elements of the C language are supported:
Supported Elements
Elements Supported
Data Types char, int, unsigned int, float, double, long long (64-bit integer).
Arithmetic and Logical Standard C arithmetic operators, except ternary operator (i.e., "condition? trueValue:
Operator falseValue"). Explicit casting (e.g., int a = (int) a_float) is not supported.
Function Declarations Standard C function declarations with argument passed by values. Pointers are not
supported.
l Measurement
l Output
l Memory
l Runtime variable
l Stamp
l Math
Measurement Functions
Function Description
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 504
Function Description
0 - Measurement is invalid
1 - Measurement is valid
double Measurement_Value (int id) Gets the value of a measurement by its ID.
Parameters:
id - Measurement ID
Returns:
Value of the measurement
0 – if measurement does not exist
1 – if measurement exists
int Measurement_Decision (int id) Gets the decision of a measurement by its ID.
Parameters:
ID - Measurement ID
Returns:
Decision of the measurement
0 – if measurement decision is false
1 – If measurement decision is true
int Measurement_Id (char* toolName, char* Gets the measurement ID by the measurement name.
measurementName) Parameters:
toolName – Tool name
measurementName – Measurement name
Returns:
-1 – measurement does not exist
Other value – Measurement ID
Output Functions
Function Description
void Output_Set (double value, int decision) Sets the output value and decision on Output index 0. Only the last
output value / decision in a script run is kept and passed to the Gocator
output. To output an invalid value, the constant INVALID_VALUE can be
used (e.g., Output_SetAt(0, INVALID_VALUE, 0))
Parameters:
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 505
Function Description
void Output_SetAt(unsigned int index, Sets the output value and decision at the specified output index. To
double value, int decision) output an invalid value, the constant INVALID_VALUE can be used (e.g.,
Output_SetAt(0, INVALID_VALUE, 0))
Parameters:
index – Script output index
value – value output by the script
decision – decision value output by the script. Can only be 0 or 1
void Output_SetId(int id, double value, int Sets the output value and decision at the specified script output ID. To
decision) output an invalid value, the constant INVALID_VALUE can be used (e.g.,
Output_SetId(0, INVALID_VALUE, 0))
Parameters:
id – Script output ID
Memory Functions
Function Description
void Memory_Set64s (int id, long long Stores a 64-bit signed integer in persistent memory.
value) Parameters:
id - ID of the value
value - Value to store
long long Memory_Get64s (int id) Loads a 64-bit signed integer from persistent memory.
Parameters:
id - ID of the value
Returns:
value - Value stored in persistent memory
void Memory_Set64u (int id, unsigned long Stores a 64-bit unsigned integer in the persistent memory
long value) Parameters:
id - ID of the value
value - Value to store
unsigned long long Memory_Get64u (int id) Loads a 64-bit unsigned integer from persistent memory.
Parameters:
id - ID of the value
Returns:
value - Value stored in persistent memory
void Memory_Set64f (int id, double value) Stores a 64-bit double into persistent memory.
Parameters:
id - ID of the value
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 506
Function Description
double Memory_Get64f (int id) Loads a 64-bit double from persistent memory. All persistent memory
values are set to 0 when the sensor starts.
Parameters:
id - ID of the value
Returns:
value - Value stored in persistent memory
int Memory_Exists (int id) Tests for the existence of a value by ID.
Parameters:
id – Value ID
Returns:
0 – value does not exist
1 – value exists
int RuntimeVariable_Count() Returns the number of runtime variables that can be accessed.
Returns:
The count of runtime variables.
int RuntimeVariable_Get32s(int id) Returns the value of the runtime variable at the given index.
Parameters:
Id – ID of the runtime variable
Returns:
Runtime variable value
Stamp Functions
Function Description
long long Stamp_Frame() Gets the frame number of the last frame.
long long Stamp_Time() Gets the time stamp of the last frame.
long long Stamp_Encoder() Gets the encoder position of the last frame when the image data was
scanned/taken.
long long Stamp_EncoderZ() Gets the encoder position at the time of the last index pulse of the last
frame.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 507
Function Description
unsigned int Stamp_Inputs() Gets the digital input state of the last frame. Returns a bit field
representing digital input states.
Math Functions
Function Description
float pow (float x, float y) Calculates the exponential value. x is the base, y is the exponent
int id = 1;
Memory_Set64s(0, Volume);
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 508
Output
The following sections describe the Output page.
Up to two outputs can have scheduling enabled with ASCII as the Serial output protocol. When
Selcom is the current Serial output protocol, only one other output can have scheduling enabled.
Category Description
1 Ethernet Used to select the data sources that will transmit data via Ethernet. See Ethernet
Output on the next page.
2 Digital Output 1 Used to select the data sources that will be combined to produce a digital
output pulse on Output 1. See Digital Output on page 514.
3 Digital Output 2 Used to select the data sources that will be combined to produce a digital
output pulse on Output 2. See Digital Output on page 514.
4 Analog Panel Used to convert a measurement value or decision into an analog output signal.
See Analog Output on page 517.
5 Serial Panel Used to select the measurements that will be transmitted via RS-485 serial
output. See Serial Output on page 520.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 509
Ethernet Output
A sensor uses TCP messages (Gocator protocol) to receive commands from client computers, and to
send video, laser profile, intensity, and measurement results to client computers. The sensor can also
receive commands from and send measurement results to a PLC using ASCII, Modbus TCP, PROFINET, or
EtherNet/IP protocol. See Protocols on page 647 for the specification of these protocols.
The specific protocols used with Ethernet output are selected and configured within the panel.
All of the tasks that can be accomplished with the Gocator's web interface (creating jobs, performing
alignment, sending data and health information, and software triggering, etc.) can be accomplished
programmatically by sending Gocator protocol control commands.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 510
To receive commands and send results using Modbus TCP messages:
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 511
To receive commands and send results using EtherNet/IP messages:
7. Click the Download EDS File button to download an EDS file for use with your IDE.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 512
PROFINET is not supported on A and B revision Gocator 2100 and 2300 sensors.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 513
To receive commands and send results using ASCII messages:
Digital Output
Gocator sensors can convert measurement decisions or software commands to digital output pulses,
which can then be used to output to a PLC or to control external devices, such as indicator lights or air
ejectors.
Digital outputs cannot be used when taking scans using the Snapshot button, which takes a
single scan and is typically used to test measurement tool settings. Digital outputs can only be
used when a sensor is running, taking a continuous series of scans.
A digital output can act as a measurement valid signal to allow external devices to synchronize to the
timing at which measurement results are output. In this mode, the sensor outputs a digital pulse when a
measurement result is ready.
A digital output can also act as a strobe signal to allow external devices to synchronize to the timing at
which the sensor exposes. In this mode, the sensor outputs a digital pulse when the sensor exposes.
Each sensor supports two digital output channels. See Gocator Power/LAN Connector on page 895 for
information on wiring digital outputs to external devices.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 514
Trigger conditions and pulse width are then configured within the panel.
4. In Configuration, set Assert On and select the measurements that should be combined to determine
the output.
If multiple measurement decisions are selected and Assert On is set to Pass, the output is activated
when all selected measurements pass.
If Assert On is set to Fail, the output is activated when any one of the selected measurements fails.
7. Check the Scheduled option if the output needs to be scheduled; otherwise, leave it unchecked for
immediate output.
A scheduled output becomes active after the delay from the start of Gocator exposure. A scheduled
output can be used to track the decisions for multiple objects as these objects travel from the sensor to
the eject gates.
The Delay setting specifies the distance from the sensor to the eject gates.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 515
An immediate output becomes active as soon as measurement results are available. The output
activates after the sensor finishes processing the data. As a result, the time between the start of sensor
exposure and output activates can vary and is dependent on the processing latency. The latency is
reported in the dashboard and in the health messages.
9. If you want to invert the output signal, check Invert Output Signal.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 516
Scheduled output becomes active at a specific target time or position, given by the Scheduled Digital
Output command. Commands that schedule an event in the past will be ignored. An encoder value is in
the future if the value will be reached by moving in the forward direction (the direction that encoder
calibration was performed in).
Analog Output
Gocator sensors can convert a measurement result or software request to an analog output.Each sensor
supports one analog output channel.
See Analog Output on page 902 for information on wiring analog output to an external device.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 517
To output measurement value or decision:
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 518
activates after the Gocator finishes processing the data. As a result, the time between the start of
Gocator exposure and output activates depends on the processing latency. The latency is reported in
the dashboard and in the health messages.
8. Specify a delay.
The delay specifies the time or spatial location between the start of Gocator exposure and the output
becomes active. The delay should be larger than the time needed to process the data inside the
Gocator. It should be set to a value that is larger than the processing latency reported in the dashboard
and in the health messages.
The unit of the delay is configured in the trigger panel. See Triggers on page 123 for details.
8. Specify a delay.
The delay specifies the time or spatial location between the start of Gocator exposure and the output
becomes active. The delay should be larger than the time needed to process the data inside the
Gocator. It should be set to a value that is larger than the processing latency reported in the dashboard
and in the health messages.
The unit of the delay is configured in the trigger panel. See Triggers on page 123 for details.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 519
The analog output takes about 75 us to reach 90% of the target value for a maximum change, then
another ~40 us to settle completely.
Serial Output
Gocator's web interface can be used to select measurements to be transmitted via RS-485 serial output.
Each sensor has one serial output channel.
Two protocols are supported: ASCII Protocol and Selcom Serial Protocol.
Gocator 2500 series sensors do not support the Selcom Serial Protocol.
The ASCII protocol outputs data asynchronously using a single serial port. For information on the ASCII
Protocol parameters and data formats, see ASCII Protocol on page 780.
The Selcom Serial Protocol outputs synchronized serial data using two serial ports. For information on
the Selcom serial protocol and data formats, see Selcom Protocol on page 791.
For information on wiring serial output to an external device, see Serial Output on page 901.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 520
To configure ASCII output:
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 521
To configure Selcom output:
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 522
Dashboard
The following sections describe the Dashboard page.
Element Description
1 System Displays sensor state and health information. See State and Health Information
below.
2 Tool Stats Displays measurement and tool performance statistics. See Statistics on
page 525.
Laser Safety Whether Laser Safety is enabled. With laser-based sensors, laser safety must be
enabled in order to scan.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 523
Name Description
Storage Usage Sensor flash storage utilization (MB used / MB total available).
Processing Latency Last delay from camera exposure start to when the results are ready for output.
Processing Latency Peak Peak delay from camera exposure start to when the results are ready for output.
Alignment State Whether the sensor or sensor system has been aligned.
Over Temperature State Whether the internal temperature of the sensor is over a predetermined level.
Over Temperature Duration The amount of time that the internal temperature of the sensor has been over a
predetermined level. (Some models only.)
Scan Count* Number of scans performed since sensor state last changed to Running.
Trigger Drop** Count of camera frames dropped due to excessive trigger speed.
Ethernet Output Drop** Count of frame drops due to slow Ethernet link.
Analog Output Drop** Count of analog output drops because last output has not been completed.
Serial Output Drop** Count of serial output drops because last output has not been completed.
Digital Output 1 Drop** Count of digital output drops because last output has not been completed.
Digital Output 2 Drop** Count of digital output drops because last output has not been completed.
Valid Spot Count Count of valid spots detected in the last frame.
Max Spot Count* Maximum number of spots detected since sensor was started.
Camera Search Count Count of camera frames where laser tracking is lost. Only applicable when tracking
window is enabled.
* When the sensor is accelerated, the indicator's value is reported from the accelerating PC.
** When the sensor is accelerated, the indicator's value is the sum of the values reported from the
sensor and the accelerating PC.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 524
Statistics
In the Tool Stats pane, you can examine measurement and tool statistics in two tabs: Measurements
and Performance.
Measurements
The Measurements tab displays statistics for each measurement enabled in the Measure page,
grouped by the tool that contains the measurement.
Measurement Statistics
Name Description
ID The measurement ID as set in the measurement's ID field on the Measure page.
Avg The average of all measurement values collected since the sensor was started.
Std The standard deviation of all measurement values collected since the sensor was
started.
Performance
The Performance tab displays performance statistics (execution time) for each tool added in the
Measure page.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 525
Performance Statistics
Name Description
Avg (%) The average percentage the CPU the tool uses.
Gocator Line Profile Sensors: User Manual Gocator Web Interface • 526
Gocator Acceleration
Gocator sensors are all-in-one devices, combining scanning, measurement, and control capabilities in a
single housing. However, to achieve higher scan rates and measurement performance in very high
density data scenarios, you may wish to use one of two acceleration methods.
For information on the ports acceleration uses (for example, in order to ensure ports are not blocked
over your network), see Required Ports on page 56.
The web interface of an accelerated sensor is identical to the interface of an unaccelerated sensor. The
Ethernet-based output protocols (Gocator, EtherNet/IP, ASCII, and Modbus) are also identical to those
found on an unaccelerated sensor, and are fully supported.
Accelerators support digital, analog, and serial output from sensors. However, because output
must be passed to the accelerator and then back to the sensor, network latency will have an
impact on performance.
Benefits
Accelerated sensors provide several benefits.
Acceleration is completely transparent: because the output protocols of an accelerated sensor are
identical to those of an unaccelerated sensor, SDK and PLC applications require no changes whatsoever
for controlling accelerated sensors and receiving health information and data.
Measurement latency is reduced on accelerated sensors, which results in shorter cycle times. This means
a sensor can scan more targets in a given time period.
The memory of accelerated sensors is limited only by the memory of the accelerating device. Accelerated
sensors can therefore handle large 3D point clouds more effectively.
l For information on which indicators are affected in the Dashboard in the web interface, see State and
Health Information on page 523.
l For information on which indicators accessed through the Gocator protocol are affected, see Health
Results on page 704.
Hardware Acceleration: GoMax
The GoMax Smart Vision Accelerator is a dedicated, small form factor device that can accelerate one or
more sensors. Using GoMax to accelerate a sensor system rather than a PC greatly simplifies
implementation and maintenance, providing a plug-and-play experience. And GoMax better handles
continuous 3D data streams over Ethernet. Finally, GoMax automatically recovers from temporary
power losses or system disconnects.
Software-Based Acceleration
You can implement acceleration capabilities in client applications that you create using the Gocator SDK.
You can also use the provided standalone utility (GoAccelerator.exe) that you can use to instantly
accelerate systems.
The firmware version of the sensor you want to accelerate must match the version of the
SDK used to build an accelerator-based application (or the version of the GoAccelerator utility).
PC
Graphics Card
The acceleration of line profile sensors does not currently make use of a computer's graphics card.
Recommendations
The following are general recommendations:
l Run only the accelerator application on the PC: third-party applications can consume system
resources in unpredictable ways and at random times.
l Limit background Windows processes such as drive optimization (defragmentation) or virus scans, or
schedule them so that they don't interfere with scanning sessions.
l Ensure that sufficient overhead in the system's resources is available. You can review the PC's
resources with the Windows Task Manager and Resource Monitor applications. We recommend that
you leave at least 20% network bandwidth, CPU, memory and disk utilization at all times.
l To verify system stability and robustness, perform long-term testing over multiple days.
Installation
To get the necessary packages, go to http://lmi3d.com/support, choose your product from the Product
Downloads section, and download it from the Download Center.
l For the SDK libraries and DLL for integrating acceleration into a client application, download the
14400-X.X.X.X_SOFTWARE_GO_SDK.zip.
3. If a Windows Security alert asks whether you want to allow GoAccelerator.exe to communicate on networks,
make sure Public and Private are checked, and then click Allow Access.
If you do not see the sensor, you may need to wait a few seconds and then click the Refresh button ( ).
In multi-sensor systems, only the Main sensor is listed.
5. (Optional) In the IP drop-down, choose an IP or choose Any to let the application choose.
6. (Optional) Set Web Port to a port for use with the accelerated sensor's URL.
8. Click Start.
The sensor system is now accelerated. An icon appears next to the accelerated sensor in the Sensors list to
indicate this.
9. To open the accelerated sensor's web interface, in the Accelerator application, click the link next to URL.
When a sensor is accelerated, a "rocket" icon appears in the metrics area.
If you restart an accelerated sensor, the sensor will continue to be accelerated when it restarts.
2. Click Stop.
// construct accelerator
if ((status = GoAccelerator_Construct(&accelerator, kNULL)) != kOK)
{
printf("Error: GoAccelerator_Construct:%d\n", status);
return;
}
// start accelerator
if ((status = GoAccelerator_Start(accelerator)) != kOK)
{
printf("Error: GoAccelerator_Start:%d\n", status);
return;
}
printf ("GoAccelerator_Start completed\n");
if ((status = GoAccelerator_Attach(accelerator, sensor)) != kOK)
{
printf("Error: GoAccelerator_Attach:%d\n", status);
return;
}
After, the SDK application can control an accelerated sensor in the same way as an unaccelerated sensor.
Estimated Performance
The following table lists the running time of various measurement tools, with and without GoMax, as
well as the performance increase factor when running with GoMax.
Note that although sensor models and job file configurations will affect running times, the performance
increase factor for tools should be consistent across models and configurations.
The emulator is a stand-alone application that lets you run a "virtual" sensor, encapsulated in a
"scenario." When running a scenario, you can test jobs, evaluate data, and even learn more about new
features, rather than take a physical device off the production line to do this. You can also use a scenario
to familiarize yourself with the overall interface if you are new to Gocator.
System Requirements
The following are the system requirements for the software:
PC
Limitations
In most ways, a scenario behaves like a real sensor, especially when visualizing data, setting up models
and part matching, and adding and configuring measurement tools. The following are some of the
limitations:
l Changes to job files in the emulator are not persistent (they are lost when you close or restart the
emulator). However, you can keep a modified job by first saving it and then downloading it from the
Jobs list on the Manage page to a client computer. The job file can then be loaded into the emulator
at a later time or even onto a physical sensor for final testing.
l Performing alignment in the emulator has no effect and will never complete.
For information on uploading and downloading jobs between the emulator and a computer, and
performing other job file management tasks, see Downloading and Uploading Jobs on page 546.
You can also create scenarios yourself by downloading a support file from a physical sensor and then
adding it to the emulator.
Support files can contain jobs, letting you configure systems and add measurements in an emulated
sensor. Support files can also contain replay data, letting you test measurements and some
configurations on real data. Dual-sensor systems are supported.
2. In Filename, type the name you want to use for the support file.
When you create a scenario from a support file in the emulator, the filename you provide here is displayed
in the emulator's scenario list.
Support files end with the .gs extension, but you do not need to type the extension in Filename.
To run the emulator, unzip the package and double-click the GoEmulator link in the unzipped Emulator
and Accelerator subfolder.
You can change the language of the emulator's interface from the launch screen. To change the
language, choose a language option from the top drop-down:
To add a scenario:
1. Launch the emulator if it isn't running already.
2. Click the Add button and choose a previously saved support file (.gs extension) in the Choose File to
Upload dialog.
Running a Scenario
After you have added a virtual sensor by uploading a support file to the emulator, you can run it from
the Available Scenarios list on the emulator launch screen. You can also run any of the scenarios
included in the installation.
To remove a scenario:
2. In the Available Scenarios list, scroll to the scenario you want to remove.
If you try to uncheck Replay Protection, you must confirm that you want to disable it.
3. In the command prompt, type GoEmulator.exe /browser (or .\GoEmulator.exe /browser for
PowerShell).
After the emulator application starts, the emulator also launches in your default browser.
The job drop-down list in the toolbar shows the jobs available in the emulator. The job that is currently
active is listed at the top. The job name will be marked with "[unsaved]" to indicate any unsaved changes.
To create a job:
To save a job:
The job is activated. If there are any unsaved changes in the current job, you will be asked whether you want
to discard those changes.
To replay data:
1. Toggle Replay mode on by setting the slider to the right in the Toolbar.
The slider's background turns blue.
To change the mode, you must uncheck Replay Protection.
3. Use the Replay Slider, Step Forward, Step Back, or Play button to simulate measurements.
Step or play through recorded data to execute the measurement tools on the recording.
Individual measurement values can be viewed directly in the data viewer. Statistics on the
measurements that have been simulated can be viewed in the Dashboard page; for more information
on the dashboard, see Dashboard on page 523.
Data can also be exported from the emulator to a client computer in order to process the data using
third-party tools.
You can only upload replay data to the same sensor model that was used to create the data.
l Upload and merge: Uploads the replay data and merges the data's associated job with the current
job. Specifically, the settings on the Scan page are overwritten, but all other settings of the current
job are preserved, including any measurements or models.
If you have unsaved changes in the current job, the firmware asks whether you want to discard the
changes.
4. If you clicked Discard, navigate to the replay data to upload from the client computer and click OK.
The replay data is loaded, and a new unsaved, untitled job is created.
Replay data can be exported using the CSV format. If you have enabled Acquire Intensity in the Scan
Mode panel on the Scan page, the exported CSV file includes intensity data.
Surface intensity data cannot be exported to the CSV format. It can only be exported separately
as a bitmap.
4. (Optional) Convert exported data to another format using the CSV Converter Tool. For information on
this tool, see CSV Converter Tool on page 837.
The decision values in the exported data depend on the current state of the job, not the state
during recording. For example, if you record data when a measurment returns a pass decision,
change the measurement's settings so that a fail decision is returned, and then export to CSV,
you will see a fail decision in the exported data.
Recorded intensity data can be exported to a bitmap (.BMP format). Acquire Intensity must be
checked in the Scan Mode panel while data was being recorded in order to export intensity data.
l Switch to Replay mode and click the Export button and select Intensity data as BMP.
Element Description
Jobs list Displays the jobs that are currently saved in the emulator.
Save button Saves current settings to the job using the name in the Name field. Changes to job files are not
persistent in the emulator. To keep changes, first save changes in the job file, and then download the
job file to a client computer. See the procedures below for instructions.
Load button Loads the job that is selected in the job list. Reloading the current job discards any unsaved changes.
Delete button Deletes the job that is selected in the job list.
Set as Default Setting a different job as the default is not persistent in the emulator. The job set as default when the
button support file (used to create a virtual sensor) was downloaded is used as the default whenever the
emulator is started.
Changes to job files in the emulator are not persistent (they are lost when you close or restart
the emulator). However, you can keep modified jobs by first saving them and then downloading
them to a client computer.
To save a job:
Other settings on the Scan page related to the post-processing of data can be modified to test their
influence on scan data, without modifying or clearing the data, for example edge filtering (page 164), and
filters on the X axis (page 151). Note that modifying the Y filters causes the buffer to be cleared.
For information on creating models and setting up part matching, see Models on page 181. For
information on adding and configuring measurement tools, see Measurement and Processing on
page 201.
For example, when you reduce the active area, in the Active Area tab on the Sensor panel, the
maximum frame rate displayed on the Trigger panel is updated to reflect the increased speed that
would be available in a physical sensor. (See Active Area on page 129 for more information on active
area.)
Similarly, you can adjust exposure on the Exposure tab on the Sensor panel to see how this affects the
maximum frame rate. (See Exposure on page 134 for more information on exposure.)
To adjust active area in the emulator, Replay Protection must be turned off. See Using Replay
Protection on page 540 for more information.
Protocol Output
The emulator simulates output for all of Gocator's Ethernet-based protocols, with the exception of
PROFINET.
l Gocator
l ASCII
l Modbus
l EtherNet/IP
Clients (such as PLCs) can connect to the emulator to access the simulated output and use the protocols
as they would with a physical sensor.
The emulator allows connections to emulated sensors on localhost (127.0.0.1). You can also allow
connections to emulated sensors on your computer's network card; for more information, see Remote
Operation below.
Remote Operation
You can specify the IP address of one of your computer's network cards to allow clients to connect
remotely to an emulated sensor using the /ip command line parameter. When the /ip parameter is not
used, emulated sensors are only available on the local machine (that is, 127.0.0.1 or localhost).
Clients can only connect to emulated sensors, not to the emulator's launch page.
You may need to contact your network administrator to allow connections to the computer
running the emulated sensor.
3. In the command prompt, type GoEmulator.exe /ip, followed by a valid IPV4 address on your network.
5. Provide the IP address you used with the /ip parameter, followed by port number 3191, to users who want
to connect to the emulated sensor, for example:
192.168.1.42:3191
Live Files
Various "live" files stored on a sensor represent the sensor's active settings and transformations
(represented together as "job" files), the active replay data (if any), and the sensor log.
By changing the live job file, you can change how the sensor behaves. For example, to make settings and
transformations active, write to or copy to the _live.job file. You can also save active settings or
transformations to a client computer, or to a file on the sensor, by reading from or copying these files,
respectively.
The live files are stored in volatile storage. Only user-created job files are stored in non-volatile
storage.
Live Files
Name Read/Write Description
_live.job Read/Write The active job. This file contains a Configuration component containing the
current settings. If Alignment Reference in the active job is set to Dynamic, it
also contains a Transform component containing transformations.
For more information on job files (live and user-created), accessing their
components, and their structure, see Job File Structure on the next page.
_live.cfg Read/Write A standalone representation of the Configuration component contained in _
live.job. Used primarily for backwards compatibility.
_live.tfm Read/Write If Alignment Reference of the active job is set to Dynamic:
A copy of the Transform component in _live.job. Used primarily for backwards
compatibility.
If Alignment Reference of the active job is set to Fixed:
The transformations that are used for all jobs whose Alignment Reference
setting is set to Fixed.
_live.log Read A sensor log containing various messages. For more information on the log
file, see Log File below.
_live.rec Read/Write The active replay simulation data.
ExtendedId.xml Read Sensor identification.
Log File
The log file contains log messages generated by the sensor. The root element is Log.
The arguments are all sent as strings and should be applied in order to the format specifiers found in the
content.
Job files, which are stored in a sensor's internal storage, control system behavior when a sensor is
running. Job files contain the settings and potentially the transformations and models associated with
the job (if Alignment Reference is set to Dynamic).
l A special job file called "_live.job." This job file contains the active settings and potentially the trans-
formations and models associated with the job. It is stored in volatile storage.
Configuration config.xml The job's configurations. This component is always present. For more
Gocator Line Profile Sensors: User Manual Sensor Device Files • 551
Component Path Description
Part model <name>.mdl One or more part model files. Part models are created using models
and part matching . For more information, see Part Models on
page 644.
Elements in the components contain three types of values: settings, constraints, and properties. Settings
are input values that can be edited. Constraints are read-only limits that define the valid values for
settings. Properties are read-only values that provide supplemental information related to sensor setup.
When a job file is received from a sensor, it will contain settings, constraints, and properties. When a job
file is sent to a sensor, any constraints or properties in the file will be ignored.
Changing the value of a setting can affect multiple constraints and properties. After you upload a job file,
you can download the job file again to access the updated values of the constraints and properties.
If Alignment Reference is set to Fixed, the active job file (_live.job) will not contain
transformations. To access transformations in this case, you must access them via _live.tfm.
The following sections correspond to the XML structure used in job file components.
Configuration
The Configuration component of a job file contains settings that control how a sensor behaves.
You can access the Configuration component of the active job as an XML file, either using path notation,
via "_live.job/config.xml", or directly via "_live.cfg".
You can access the Configuration component in user-created job files in non-volatile storage, for
example, "productionRun01.job/config.xml". You can only access configurations in user-created job files
using path notation.
See the following sections for the elements contained in this component.
All sensors share a common job file structure and settings for all features are included in job files,
regardless of the model.
If a setting in a job file is not used by a sensor, the setting's used property is set to 0.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 552
Configuration Child Elements
Element Type Description
Setup Section For a description of the Setup elements, see Setup below.
Replay Section Contains settings related to recording filtering (see Replay on page 576).
Streams Section Read-only collection of available data streams (see Streams/Stream
(Read-only) on page 577).
ToolOptions Section List of available tool types and their information. See ToolOptions on
page 578 for details.
Tools Collection Collection of sections. Each section is an instance of a tool and is named
by the type of the tool it describes. For more information, see the
sections for each tool under Tools on page 580.
Outputs Section For a description of the Output elements, see Output on page 636.
Setup
The Setup element contains settings related to system and sensor setup.
TemperatureSafetyEnabled Bool Enables laser temperature safety control. Only applies to certain
laser-based sensors.
TemperatureSafetyEnabled.used Bool Whether or not this property is used.
ScanMode 32s The default scan mode.
ScanMode options String (CSV) List of available scan modes.
OcclusionReductionEnabled Bool Enables occlusion reduction.
OcclusionReductionEnabled.used Bool Whether or not property is used.
OcclusionReductionEnabled.value Bool Actual value used if not configurable.
OcclusionReductionAlg 32s The Algorithim to use for occlusion reduction:
0 – Standard
1 – High Quality
Gocator Line Profile Sensors: User Manual Sensor Device Files • 553
Element Type Description
Devices Collection A collection of two Device sections (with roles main and buddy). See
Devices / Device on page 562.
SurfaceGeneration Section See SurfaceGeneration on page 569.
SurfaceSections Section See SurfaceSections on page 570.
BackgroundSuppression
The BackgroundSuppression element contains settings related to background suppression.
Filters
The Filters element contains settings related to post-processing profiles before they are output or used
by measurement tools.
XSmoothing
Gocator Line Profile Sensors: User Manual Sensor Device Files • 554
Element Type Description
YSmoothing
XGapFilling
YGapFilling
XMedian
Gocator Line Profile Sensors: User Manual Sensor Device Files • 555
Element Type Description
YMedian
XDecimation
YDecimation
XSlope
Gocator Line Profile Sensors: User Manual Sensor Device Files • 556
Element Type Description
YSlope
Trigger
The Trigger element contains settings related to trigger source, speed, and encoder resolution.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 557
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 558
Element Type Description
Layout
X 64f X start (mm).
Gocator Line Profile Sensors: User Manual Sensor Device Files • 559
Element Type Description
Grid Elements
Element Type Description
Alignment
The Alignment element contains settings related to alignment and encoder calibration.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 560
Element Type Description
Disk
Bar
HoleCount.used Bool Whether the hole count with be used in the bar alignment proceudure.
Plate
Gocator Line Profile Sensors: User Manual Sensor Device Files • 561
Polygon
Polygon/Corner
X 64f X Position
Y 64f Y Position
Devices List of 32u List of devices this corner is assigned to.
Devices.options List of 32u List of valid options for this field.
Devices / Device
Gocator Line Profile Sensors: User Manual Sensor Device Files • 562
Element Type Description
PatternSequenceIndex 32u The index of the pattern sequence to display. Choose the pattern
that produces the best data.
The indices represent Phase Pattern Sequences, followed by Stripe
Pattern Sequences in reverse order. The lower indices are the higher
frequency phase code patterns, and the higher indices are the lower
frequency binary patterns.
Index 1 [Phase Pattern Sequence Image 5]: Highest frequency
sinusoid.
Index 2 [Phase Pattern Sequence Image 4]
[...]
Index 5 [Phase Pattern Sequence Image 1]: Lowest frequency
sinusoid.
Index 6 [Stripe Pattern Sequence Image 7]: Highest bar count.
Index 7 [Stripe Pattern Sequence Image 6]
[...]
Index 12 [Stripe Pattern Sequence Image 1]: Lowest bar count)
Index 13 [Reference Image 1]
PatternSequenceIndex.used Bool Whether or not the pattern sequence index should be displayed
PatternSequenceIndex.used Bool Whether or not the pattern sequence index should be displayed.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 563
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 564
Region3D Child Elements
Element Type Description
X 64f X start (mm).
Gocator Line Profile Sensors: User Manual Sensor Device Files • 565
Tracking Child Elements
Element Type Description
SpotThreshold.readonly Bool Whether or not property can be modified. If set, the value
should be considered read-only by the client. Only has
meaning if “used” is also set.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 566
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 567
Element Type Description
SurfaceEncoding.readonly Bool Whether or not property can be modified. If set, the value
should be considered read-only by the client. Only has
meaning if “used” is also set.
ContrastThreshold.value 32s Value in use by the sensor, useful for determining value
when used is false.
ContrastThreshold.readonly Bool Whether or not property can be modified. If set, the value
should be considered read-only by the client. Only has
meaning if “used” is also set.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 568
IndependentExposures Child Elements
Element Type Description
Tracheid settings are only supported by Gocator 200 series multi-point sensors.
SurfaceGeneration
The SurfaceGeneration element contains settings related to surface generation.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 569
FixedLength
ExternalInputIndex 32s Index of external input when Source (above) is set to 1 – Digital Input
and connected to a Master.
0 – first digital input
1 – second digital input
2 – third digital input
3 – fourth digital input
VariableLength
Rotational
SurfaceSections
Gocator Line Profile Sensors: User Manual Sensor Device Files • 570
Element Type Description
@yMin 64f The minimum valid Y value to be used for section definition.
@yMax 64f The maximum valid Y value to be used for section definition.
Section Collection A series of Section elements.
ProfileGeneration
The ProfileGeneration element contains settings related to profile generation.
FixedLength
Gocator Line Profile Sensors: User Manual Sensor Device Files • 571
Element Type Description
1 – Digital input
2 – Software triggered
ExternalInputIndex 32s Index of external input when Source (above) is set to 1 – Digital Input
and connected to a Master.
0 – first digital input
1 – second digital input
2 – third digital input
3 – fourth digital input
VariableLength
Rotational
PartDetection
Gocator Line Profile Sensors: User Manual Sensor Device Files • 572
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 573
Element Type Description
EdgeFiltering
PartMatching
The PartMatching element contains settings related to part matching.
Edge
ModelName String Name of the part model to use. Does not include the .mdl extension.
Acceptance/Quality/Min 64f Minimum quality value for a match.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 574
BoundingBox
Ellipse
Gocator Line Profile Sensors: User Manual Sensor Device Files • 575
Element Type Description
Replay
Contains settings related to recording filtering.
RecordingFiltering
ConditionCombineType 32s 0 – Any: If any enabled condition is satisfied, the current frame is
recorded.
1 – All: All enabled conditions must be satisfied for the current frame
to be recorded.
Conditions/AnyMeasurement
Conditions/AnyMeasurement Elements
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 576
Conditions/AnyData
Conditions/AnyData Elements
Element Type Description
RangeCountThreshold 32u The threshold for the number of range points that are valid.
Conditions/Measurement
Conditions/Measurement Elements
Element Type Description
Streams/Stream (Read-only)
Streams/Stream Child Elements
Element Type Description
Step 32s The data step of the stream being described. Possible values are:
1 – Video
2 – Range
3 – Surface
4 – Section
Gocator Line Profile Sensors: User Manual Sensor Device Files • 577
Element Type Description
16 – Uniform Surface
ColorEncoding 32s The color encoding type. Only appears for Video stream steps (1).
0 – None
1 – Bayer BGGR
2 – Bayer GBRG
3 – Bayer RGGB
4 – Bayer GRBG
Capability 32s The capability of the data stream source. Possible values are:
0 – Full
1 – Diagnostic only
2 - Virtual
ToolOptions
The ToolOptions element contains a list of available tool types, their measurements, and settings for
related information.
<Tool Names> Collection A collection of tool name elements. An element for each
tool type is present.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 578
Element Type Description
MeasurementOptions
FeatureOptions
<Feature Names> Collection A collection of feature name elements. An element for each
measurement is present.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 579
StreamOptions
@step 32s The data step of the stream being described. Possible values
are:
1 – Video
2 – Range
3 – Surface
4 – Section
@ids CSV A list representing the available IDs associated with the
given step.
Tools
The Tools element contains measurement tools. The following sections describe each tool and its
available measurements.
@options String (CSV) A list of the tools available in the currently selected scan
mode.
Profile Types
The following types are used by various measurement tools.
ProfileFeature
An element of type ProfileFeature defines the settings for detecting a feature within an area of interest.
Type 32s Determine how the feature is detected within the area:
0 – Max Z
1 – Min Z
2 – Max X
3 – Min X
4 – Corner
5 – Average
6 – Rising Edge
7 – Falling Edge
8 – Any Edge
9 – Top Corner
10 – Bottom Corner
11 – Left Corner
12 – Right Corner
Gocator Line Profile Sensors: User Manual Sensor Device Files • 580
Element Type Description
13 – Median
ProfileLine
An element of type ProfileLine defines measurement areas used to calculate a line.
Regions (Collection) The regions used to calculate a line. Contains one or two Region
elements of type ProfileRegion2D, with RegionEnabled fields for each.
ProfileRegion2d
An element of type ProfileRegion2d defines a rectangular area of interest.
Surface Types
The following types are used by the various measurement tools.
Region3D
An element of type Region3D defines a rectangular area of interest in 3D.
SurfaceFeature
An element of type SurfaceFeature defines the settings for detecting a feature within an area of interest.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 581
SurfaceFeature Child Elements
Element Type Description
Type 32s Setting to determine how the feature is detected within the area:
0 – Average (formerly Centroid 2d)
1 – Centroid (formerly Centroid 3d)
2 – X Max
3 – X Min
4 – Y Max
5 – Y Min
6 – Z Max
7 – Z Min
8 – Median
SurfaceRegion2d
An element of type SurfaceRegion2d defines a rectangular area of interest on the X-Y plane.
Parameter Types
The following types are used by internal and custom (user-created) GDK-based tools.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 582
GDK Parameter Child Elements
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 583
Element Type Description
ProfileArea
A ProfileArea element defines settings for a profile area tool and one or more of its measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 584
Element Type Description
1 – Video
2 – Range
3 – Surface
4 – Section
Gocator Line Profile Sensors: User Manual Sensor Device Files • 585
Element Type Description
1 – Enable
ProfileBoundingBox
A ProfileBoundingBox element defines settings for a profile bounding box tool and one or more of its
measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 586
Element Type Description
measurement
Measurements\Z Bounding Box tool Z measurement.
measurement
Measurements\Width Bounding Box tool Width measurement.
measurement
Measurements\Height Bounding Box tool Height measurement.
measurement
Measurements\GlobalX Bounding Box tool GlobalX measurement
measurement
Measurements\GlobalY Bounding Box tool GlobalY measurement
measurement
Measurements\GlobalAngle Bounding Box tool GlobalAngle measurement
measurement
Gocator Line Profile Sensors: User Manual Sensor Device Files • 587
ProfileBridgeValue
A ProfileBridgeValue element defines settings for a profile bridge value tool and one or more of its
measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 588
Element Type Description
ProfileCircle
A ProfileCircle element defines settings for a profile circle tool and one or more of its measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 589
ProfileCircle Child Elements
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 590
Circle Tool Measurement
Element Type Description
ProfileDimension
A ProfileDimension element defines settings for a profile dimension tool and one or more of its
measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 591
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 592
Element Type Description
1 – Enable
ProfileGroove
A ProfileGroove element defines settings for a profile groove tool and one or more of its measurements.
The profile groove tool is dynamic, meaning that it can contain multiple measurements of the same type
in the Measurements element.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 593
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 594
Element Type Description
ProfileIntersect
A ProfileIntersect element defines settings for a profile intersect tool and one or more of its
measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 595
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 596
Element Type Description
ProfileLine
A ProfileLine element defines settings for a profile line tool and one or more of its measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 597
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 598
ProfilePanel
A ProfilePanel element defines settings for a profile panel tool and one or more of its measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 599
Element Type Description
ProfilePanelEdge
Element Type Description
Gap/Flush Measurement
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 600
Element Type Description
1 – Enable
ProfilePosition
A ProfilePosition element defines settings for a profile position tool and one or more of its
measurements.
ProfilePosition Child Elements
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 601
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 602
ProfileRoundCorner
A ProfileRoundCorner element defines settings for a profile round corner tool and one or more of its
measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 603
ProfilePanelEdge
Element Type Description
ProfileStrip
A ProfileStrip element defines settings for a profile strip tool and one or more of its measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 604
The profile strip tool is dynamic, meaning that it can contain multiple measurements of the same type in
the Measurements element.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 605
Element Type Description
0 – Disabled
1 – Enabled
Gocator Line Profile Sensors: User Manual Sensor Device Files • 606
Element Type Description
Script
A Script element defines settings for a script measurement.
Output
Element Type Description
SurfaceBoundingBox
A SurfaceBoundingBox element defines settings for a surface bounding box tool and one or more of its
measurements.
SurfaceBoundingBox Child Elements
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 607
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 608
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 609
SurfaceCsHole
A SurfaceCsHole element defines settings for a surface countersunk hole tool and one or more of its
measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 610
Element Type Description
0 – Disable
1 – Enable
Gocator Line Profile Sensors: User Manual Sensor Device Files • 611
Element Type Description
SurfaceDimension
A SurfaceDimension element defines settings for a surface dimension tool and one or more of its
measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 612
SurfaceDimension Child Elements
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 613
Element Type Description
measurement
Measurements\Width Dimension tool Width measurement
measurement
Gocator Line Profile Sensors: User Manual Sensor Device Files • 614
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 615
Element Type Description
0 – Rising
1 – Falling
2 – Rising or Falling
Gocator Line Profile Sensors: User Manual Sensor Device Files • 616
Edge Measurement Child Elements
Element Type Description
SurfaceEllipse
A SurfaceEllipse element defines settings for a surface ellipse tool and one or more of its measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 617
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 618
Element Type Description
SurfaceHole
A SurfaceHole element defines settings for a surface hole tool and one or more of its measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 619
Element Type Description
DepthLimit 64f The depth limit relative to the surface. Data below this
limit is ignored.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 620
Element Type Description
SurfaceOpening
A SurfaceOpening element defines settings for a surface opening tool and one or more of its
measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 621
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 622
Element Type Description
DepthLimit 64f The depth limit relative to the surface. Data below this
limit is ignored.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 623
Element Type Description
SurfacePlane
A SurfacePlane element defines settings for a surface plane tool and one or more of its measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 624
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 625
Element Type Description
0 – Disable
1 – Enable
SurfacePosition
A SurfacePosition element defines settings for a surface position tool and one or more of its
measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 626
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 627
Element Type Description
SurfaceStud
A SurfaceStud element defines settings for a surface stud tool and one or more of its measurements.
SurfaceStud Child Elements
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 628
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 629
Element Type Description
1 – Enable
SurfaceVolume
A SurfaceVolume element defines settings for a surface volume tool and one or more of its
measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 630
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 631
Element Type Description
1 – Enable
Gocator Line Profile Sensors: User Manual Sensor Device Files • 632
Element Type Description
anchoring.
Anchor\Z.options String (CSV) The Z measurements (IDs) available for
anchoring.
Parameters\RefPoint GdkParamGeometricFeature Reference point feature.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 633
(Width measurement only)
Gocator Line Profile Sensors: User Manual Sensor Device Files • 634
Element Type Description
@type=Z
Measurements\Measurement Intersect Measurement Angle measurement.
@type=Angle
Features\IntersectPoint GDK Feature Intersect point feature.
Custom
A Custom element defines settings for a user-created GDK-based tool and one or more of its
measurements.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 635
Element Type Description
Output
The Output element contains the following sub-elements: Ethernet, Serial, Analog, Digital0, and Digital1.
Each of these sub-elements defines the output settings for a different type of output.
For all sub-elements, the source identifiers used for measurement outputs correspond to the
measurement identifiers defined in each tool's Measurements element. For example, in the following
XML, in the options attribute of the Measurements element, 2 and 3 are the identifiers of measurements
that are enabled and available for output. The value of the Measurements element (that is, 2) means
that only the measurement with id 2 (Profile Dimension Width) will be sent to output.
<ProfileDimension> ...
<Measurements>
<Width id="2"> ...
<Height id="3"> ...
<Output>
<Ethernet> ...
<Measurements options="2,3">2</Measurements>
Ethernet
The Ethernet element defines settings for Ethernet output.
In the Ethernet element, the source identifiers used for video, range, profile, and surface output, as well
as range, profile, and surface intensity outputs, correspond to the sensor that provides the data. For
example, in the XML below, the options attribute of the Profiles element shows that only two sources are
available (see the table below for the meanings of these values). The value in this element—0—indicates
that only data from that source will be sent to output.
<Output>
Gocator Line Profile Sensors: User Manual Sensor Device Files • 636
<Ethernet>
...
<Ranges options=""/>
<Profiles options="0,1">0</Profiles>
<Surfaces options=""/>
...
Gocator Line Profile Sensors: User Manual Sensor Device Files • 637
Element Type Description
0 – Top
1 – Bottom
2 – Top left
3 – Top right
RangeIntensities.options 32s (CSV) List of available range intensity sources (see above).
ProfileIntensities 32s (CSV) Selected profile intensity sources.
0 – Top
1 – Bottom
2 – Top left
3 – Top right
ProfileIntensities.options 32s (CSV) List of available profile intensity sources (see above).
SurfaceIntensities 32s (CSV) Selected surface intensity sources.
SurfaceIntensities.options 32s (CSV) List of available surface intensity sources (see above).
SurfaceSectionIntensities 32s (CSV) Selected surface section intensity sources
SurfaceSectionIntensities.options 32s (CSV) List of available surface section intensity sources.
Tracheids 32s (CSV) Selected tracheid sources.
Tracheids.options 32s (CSV) List of available tracheid sources.
Measurements 32u (CSV) Selected measurement sources.
Measurements.options 32u (CSV) List of available measurement sources.
Events 32u (CSV) Selected events
Events.Options 32u (CSV) CSV list of possible event options:
0 – Exposure Begins
Gocator Line Profile Sensors: User Manual Sensor Device Files • 638
Element Type Description
1 – Exposure Ends
Ascii
EIP
Gocator Line Profile Sensors: User Manual Sensor Device Files • 639
Modbus
Profinet
PROFINET is not supported on A and B revision Gocator 2100 and 2300 sensors.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 640
Element Type Description
Delay 64f Output delay (µs or mm, depending on delay domain defined below).
DelayDomain 32s Output delay domain:
0 – Time (µs)
1 – Encoder (mm)
Analog
The Analog element defines settings for analog output.
The range of valid measurement values [DataScaleMin, DataScaleMax] is scaled linearly to the specified
current range [CurrentMin, CurrentMax].
Gocator Line Profile Sensors: User Manual Sensor Device Files • 641
Element Type Description
0 – Time (µs)
1 – Encoder (mm)
The delay specifies the time or position at which the analog output activates. Upon activation, there
is an additional delay before the analog output settles at the correct value.
Serial
The Serial element defines settings for Serial output.
Gocator 2500 series sensors do not support the Selcom Serial Protocol.
Selcom
Gocator Line Profile Sensors: User Manual Sensor Device Files • 642
Ascii
Transform
The transformation component contains information about the physical system setup that is used to:
l Transform data from sensor coordinate system to another coordinate system (e.g., world)
l Define the travel offset (Y offset) between sensors for staggered operation
You can access the Transform component of the active job as an XML file, either using path notation, via
"_live.job/transform.xml", or directly via "_live.tfm".
You can access the Transform component in user-created job files in non-volatile storage, for example,
"productionRun01.job/transform.xml". You can only access transformations in user-created job files
using path notation.
See the following sections for the elements contained in this component.
Transformation Example:
Gocator Line Profile Sensors: User Manual Sensor Device Files • 643
</Device>
<Device id="1">
<X>0</X>
<Y>0.0</Y>
<Z>123.4966803469</Z>
<XAngle>5.7478302588</XAngle>
<YAngle>3.7078302555</XAngle>
<ZAngle>2.7078302556</XAngle>
</Device>
</Devices>
</Transform>
The Transform element contains the alignment record for both the Main and the Buddy sensor.
Device
A Device element defines the transformation for a sensor. There is one entry element per sensor,
identified by a unique role attribute (0 for main and 1 for buddy):
The rotation (counter-clockwise in the X-Z plane) is performed before the translation.
Part Models
Part models represent models created using the part matching feature.
Gocator Line Profile Sensors: User Manual Sensor Device Files • 644
You can access a model in the active job using path notation. For example, to access a model called
scan.mdl, use "_live.job/scan.mdl".
You can access part models in user-created job files in non-volatile storage, for example,
"productionRun01.job/model1.mdl". You can only access part models in user-created job files using path
notation.
Part models contain the following subcomponents. You can access the subcomponents using path
notation, for example, "productionRun01.job/myModel.mdl/config.xml".
The edge points file exists only when the model contains the source data for the edge points.
Edge Points
Edge Points Data
Field Type Offset Description
id 16s 0 Sender ID
-1 – Part matching
source 8s 2 Source
0 – Model
1 – Target
Gocator Line Profile Sensors: User Manual Sensor Device Files • 645
Field Type Offset Description
Configuration
Configuration Child Elements
Element Type Description
Gocator Line Profile Sensors: User Manual Sensor Device Files • 646
Integrations
Several integration tools are provided in the Tools package available from the Downloads center, in the
Software subsection for your sensor model and Gocator software release.
l LabVIEW integration (for more information, see the LabVIEW application guide at https://-
downloads.lmi3d.com/interfacing-gocator-labview-4x-guide).
l EtherNet/IP files
Protocols
Gocator supports protocols for communicating with sensors over Ethernet (TCP/IP) and serial output.
For a protocol to output data, it must be enabled and configured in the active job.
If you switch jobs or make changes to a job using the SDK or a protocol (from a PLC), the switch
or changes are not automatically displayed in the web interface: you must refresh the browser
to see these.
Gocator 2500 series sensors do not support the Selcom Serial Protocol.
Gocator Protocol
This section describes the TCP and UDP commands and data formats used by a client computer to
communicate with Gocator sensors using the Gocator protocol. It also describes the connection types
(Discovery, Control, Upgrade, Data, and Health), and data types. The protocol enables the client to:
l Send commands to run sensors, provide software triggers, read/write files, etc.
l Upgrade firmware.
The Gocator 4.x/5.x firmware uses mm, mm2, mm3, and degrees as standard units. In all
protocols, values are scaled by 1000, as values in the protocols are represented as integers.
This results in effective units of mm/1000, mm2/1000, mm3/1000, and deg/1000 in the
protocols.
To use the protocol, it must be enabled and configured in the active job.
Sensors send UDP broadcasts over the network over the Internal Discovery channel (port 2016)
at regular intervals during operation to perform peer discovery.
The Gocator SDK provides open source C language libraries that implement the network
commands and data formats defined in this section. For more information, see GoSDK on
page 813.
For information on configuring the protocol using the web interface, see Ethernet Output on page 510.
For information on job file structures (for example, if you wish to create job files programmatically), see
Job File Structure on page 551.
Data Types
The table below defines the data types and associated type identifiers used in this section.
All values except for IP addresses are transmitted in little endian format (least significant byte first)
unless stated otherwise. The bytes in an IP address "a.b.c.d" will always be transmitted in the order a, b,
c, d (big endian).
Data Types
Type Description Null Value
Commands
The following sections describe the commands available on the Discovery (page 649), Control (page
652), and Upgrade (page 690) channels.
When a client sends a command over the Control or Upgrade channel, the sensor sends a reply whose
identifier is the same as the command's identifier. The identifiers are listed in the tables of each of the
commands.
Status Codes
Each reply on the Discovery, Control, and Upgrade channels contains a status field containing a status
code indicating the result of the command. The following status codes are defined:
Status Codes
Label Value Description
OK 1 Command succeeded.
Item Not Found -999 A required item (e.g., file) was not found.
Discovery Commands
Sensors ship with the following default network configuration:
Setting Default
DHCP 0 (disabled)
IP Address 192.168.1.10
255.255.255.255 3220
When a sensor accepts a discovery command, it will send a UDP broadcast response:
The use of UDP broadcasts for discovery enables a client computer to locate a sensor when the senor
and client are configured for different subnets. All you need to know is the serial number of the sensor in
order to locate it on an IP network.
Get Address
The Get Address command is used to discover sensors across subnets.
Command
Field Type Offset Description
Reply
Field Type Offset Description
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 64s 16 Operation status. For a list of status codes, see Commands on
page 649.
Get Info
The Get Info command is used to retrieve sensor information.
Command
Field Type Offset Description
status 64s 16 Operation status. For a list of status codes, see Commands on
page 649.
attrCount 16u 32 Byte count of the attributes (begins after this field and ends
before propertyCount).
id 32u 34 Serial number.
version 32u 38 Version as a 4-byte integer (encoded in little-endian).
uptime 64u 42 Sensor uptime (microseconds).
ipNegotiation byte 50 IP negotiation type:
0 – Static
1 – DHCP
Property
Field Type Description
Control Commands
A client sends control commands for most operations over the Control TCP channel (port 3190).
States
A sensor system can be in one of three states: Conflict, Ready, or Running. The client sends the Start and
Stop control commands to change the system's current state to Running and Ready, respectively. The
sensor can also be configured to boot in either the Ready or Running state, by enabling or disabling
autostart, respectively, using the Set Auto Start Enabled command.
In the Ready state, a sensor can be configured. In the Running state, a sensor responds to input signals,
performs measurements, drives its outputs, and sends data messages to the client.
The state of the sensor can be retrieved using the Get States or Get System Info command.
The Conflict state indicates that a sensor has been configured with a Buddy sensor but the Buddy sensor
is not present on the network. The sensor will not accept some commands until the Set Buddy
command is used to remove the configured Buddy.
Progressive Reply
Some commands send replies progressively, as multiple messages. This allows the sensor to stream data
without buffering it first, and allows the client to obtain progress information on the stream.
A progressive reply begins with an initial, standard reply message. If the status field of the reply indicates
success, the reply is followed by a series of “continue” reply messages.
A continue reply message contains a block of data of variable size, as well as status and progress
information. The series of continue messages is ended by either an error, or a continue message
containing 0 bytes of data.
Protocol Version
The Protocol Version command returns the protocol version of the connected sensor.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Get Address
The Get Address command is used to get a sensor address.
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Set Address
The Set Address command modifies the network configuration of a sensor. On receiving the command,
the sensor will perform a reset. You should wait 30 seconds before re-connecting to the sensor.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Every sensor contains factory backup firmware. If a firmware upgrade command fails (e.g., power is
interrupted), the factory backup firmware will be loaded when the sensor is reset or power cycled. In this
case, the sensors will fall back to the factory default IP address. To avoid IP address conflicts in a multi-
sensor system, connect to one sensor at a time and re-attempt the firmware upgrade.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Local Info
Field Type Offset Description
Remote Info
Field Type Offset Description
Errors:
0 – Unbuddiable (General Error)
-100 – Already buddied
-99 – Invalid State (e.g. running)
-98 – Version Mismatch
-97 – Model Mismatch
modelDisplayName[32] char 92 Remote user-friendly model display name that can be used
Buddy Info
Field Type Offset Description
Errors:
0 – Unbuddiable (General Error)
-100 – Already buddied
-99 – Invalid State (e.g. running)
-98 – Version Mismatch
-97 – Model Mismatch
-95 – Device Missing
-92 – Standalone Sensor
-91 – Restricted Sensor Mismatch
This version of the Get System Info command is deprecated. Use Get System Info (v2) instead.
The Get System Info command reports information for sensors that are visible in the system.
Firmware version refers to the version of the sensor's firmware installed on each individual sensor. The
client can upgrade the sensor's firmware by sending the Start Upgrade command (see Start Upgrade on
page 690). Firmware upgrade files are available from the downloads section under the support tab on
the LMI web site. For more information on getting the latest firmware, see Firmware Upgrade on
page 117.
Every sensor contains factory backup firmware. If a firmware upgrade command fails (e.g., power is
interrupted), the factory backup firmware will be loaded when the sensor is reset or power cycled. In this
case, the sensors will fall back to the factory default IP address. To avoid IP address conflicts in a multi-
sensor system, connect to one sensor at a time and re-attempt the firmware upgrade.
Command
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Sensor Info
Field Type Offset Description
Get States
The Get States command returns various system states.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
cableLength 32u 66 Cable length (maximum Is 60.0 meters, default is 5.0 meters)
Log In/Out
The Log In/Out command is used to log in or out of a sensor.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Change Password
The Change Password command is used to change log-in credentials for a user.
Command
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Assign Buddies
The Assign Buddies command is used to set the list of buddies assigned to the system.
This command can be used to both add and remove buddies by changing the list of buddies. A serial
number of 0 can be used to add device slots that are not assigned a physical sensor. Collections
associated with the devices (e.g. <Device> element in the configuration) grow or shrink accordingly.
Items are added to or removed from the end of these collections. For example: the system starts with 2
devices, [A, B]. A new list [A, B, C] is sent. The configuration for A and B are preserved, and a new record is
created for C. If now the system changes back to [A, B], the record for C is deleted. Adding or removing
items in the middle of the list has the same behaviour. Example: the system starts with 3 devices, [A, B,
C]. A new list [A, C] is sent. The configuration for B is now used for C, and the configuration for C is
deleted. To ensure consistency when adding and removing devices, add only to the end of the list and
remove using the Remove Buddies command.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Remove Buddies
The Remove Buddies command is used to remove one or more buddies using 0-based buddy indices.
Use this command to remove a buddy devices along with its associated configuration resources. If the
system starts with 3 devices: [A, B, C], and this command is called to remove B, the configuration items
for A and C remain unchanged.
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Set Buddy
The Set Buddy command is used to assign or unassign a Buddy sensor.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
List Files
The List Files command returns a list of the files in the sensor's file system.
Command
Field Type Offset Description
extension[64] char 6 Specifies the extension used to filter the list of files (does not
include the "."). If an empty string is used, then no filtering is
performed.
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Copy File
The Copy File command copies a file from a source to a destination within the connected sensor (a .job
file, a component of a job file, or another type of file; for more information, see Job File Structure on
page 551).
To make a job active (to load it), copy a saved job to "_live.job".
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Read File
Downloads a file from the connected sensor (a .job file, a component of a job file, or another type of file;
for more information, see Job File Structure on page 551).
To read the configuration of the live configuration only, pass "_live.job/config.xml" in the name field.
Command
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Write File
The Write File command uploads a file to the connected sensor (a .job file, a component of a job file, or
another type of file; for more information, see Job File Structure on page 551).
To make a job file live, write to "_live.job". Except for writing to the live file, the file is permanently stored
on the sensor.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Delete File
The Delete File command removes a file from the connected sensor (a .job file, a component of a job file,
or another type of file; for more information, see Job File Structure on page 551).
Command
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
Reply
Field Type Offset Description
Command
Field Type Offset Description
Reply
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
name[64] char 10 The file name (null-terminated) of the job the sensor loads
when it powers up.
Command
Field Type Offset Description
fileName[64] char 6 File name (null-terminated) of the job the sensor loads when it
powers up.
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
changed 8u 74 Whether or not the currently loaded job has been changed (1:
yes; 0: no).
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Clear Alignment
The Clear Alignment command clears sensor alignment.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Get Timestamp
The Get Timestamp command retrieves the sensor's timestamp, in clock ticks. All devices in a system are
synchronized with the system clock; this value can be used for diagnostic purposes, or used to
synchronize the start time of the system.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Get Encoder
This command retrieves the current system encoder value.
Command
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Reset Encoder
The Reset Encoder command is used to reset the current encoder value.
The encoder value can be reset only when the encoder is connected directly to a sensor. When
the encoder is connected to the master, the value cannot be reset via this command.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Start
The Start command starts the sensor system (system enters the Running state). For more information
on states, see Control Commands on page 652.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
target 64s 6 Target scheduled start value (in ticks or µs, depending on the
trigger type).
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Stop
The Stop command stops the sensor system (system enters the Ready state). For more information on
states, see Control Commands on page 652.
Command
Field Type Type Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
enable 8u 10 0: disabled
1: enabled
Command
Field Type Offset Description
enable 8u 6 0: disabled
1: enabled
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
Reply
Field Type Offset Description
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Start Alignment
The Start Alignment command is used to start the alignment procedure on a sensor.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
opId 32u 10 Operation ID. Use this ID to correlate the command/reply on the
Command channel with the correct Alignment Result message
on the Data channel. A unique ID is returned each time the client
uses this command.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
opId 32u 10 Operation ID. Use this ID to correlate the command/reply on the
Command channel with the correct Exposure Calibration
Result message on the Data channel. A unique ID is returned
each time the client uses this command.
Software Trigger
The Software Trigger command causes the sensor to take a snapshot while in software mode and in the
Running state.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
target 64s 8 Specifies the time (clock ticks) when or position (µm) at which the
digital output event should happen.
The target value is ignored if ScheduleEnabled is set to false.
(Scheduled is unchecked in Digital in the Output panel.) The
output will be triggered immediately.
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
target 64s 8 Specifies the time (clock ticks) or position (encoder ticks) of when
the event should happen.
The target value is ignored if ScheduleEnabled is set to false.
(Scheduled is unchecked in Analog in the Output panel.) The
output will be triggered immediately.
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
The analog output takes about 75 us to reach 90% of the target value for a maximum change,
then roughly another 40 us to settle completely.
Ping
The Ping command can be used to test the control connection. This command has no effect on sensors.
Command
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
If a non-zero value is specified for timeout, the client must send another ping command before
the timeout elapses; otherwise the server would close the connection. The timer is reset and
updated with every command.
Reset
The Reset command reboots the Main sensor and any Buddy sensors. All sensors will automatically reset
3 seconds after the reply to this command is transmitted.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Backup
The Backup command creates a backup of all files stored on the connected sensor and downloads the
backup to the client.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
The sensor must be reset or power-cycled before the restore operation can be completed.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Restore Factory
The Restore Factory command restores the connected sensor to factory default settings.
Note that the sensor must be reset or power-cycled before the factory restore operation can be
completed.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
A reply status of -996 means that the current configuration (mode, sensor type, etc.) does not
support simulation.
A reply status of -992 means that the simulation buffer is empty. Note that the buffer can be
valid even if the simulation buffer is actually empty due to optimization choices. This scenario
means that the simulation buffer would be valid if data were recorded.
Seek Playback
The Seek Playback command seeks to any position in the current playback dataset. The frame is then
sent.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Step Playback
The Step Playback command advances playback by one frame.
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
When the system is running in the Replay mode, this command advances replay data (playback) by
one frame. This command returns an error if no live playback data set is loaded. You can use the
Copy File command to load a replay data set to _live.rec.
Playback Position
The Playback Position command retrieves the current playback position.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
Reply
Field Type Offset Description
Clear Log
The Clear Log command clears the sensor's log.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Simulate Unaligned
The Simulate Unaligned command simulates data before alignment transformation.
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Acquire
The Acquire command acquires a new scan.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
The command returns after the scan has been captured and transmitted.
Acquire Unaligned
The Acquire Unaligned command acquires a new scan without performing alignment transformation.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Create Model
The Create Model command creates a new part model from the active simulation scan.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Detect Edges
The Detect Edges command detects and updates the edge points of a part model.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Add Tool
The Add Tool command adds a tool to the live job.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Add Measurement
The Add Measurement command adds a measurement to a tool instance.
Command
Field Type Offset Description
toolIndex 32u 6 Index of the tool instance the new measurement is added to.
typeName[64] char 10 Type name of the measurement (for example, X).
name[64] char 74 User-specified name of the measurement instance.
Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
This command can only be used with dynamic tools (tools with a dynamic list of measurements).
The maximum number of instances for a given measurement type can be found in the
ToolOptions node. For dynamic tools, the maximum count is greater than one, while for static
tools it is one.
This command returns an initial reply, followed by a series of "continue" replies if the initial reply's status
field indicates success. The continue replies contain the actual data, and have 0x5000 as their identifier.
Command
Field Type Offset Description
Initial Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Continue Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
This command returns an initial reply, followed by a series of "continue" replies if the initial reply's status
field indicates success. The continue replies contain the actual data, and have 0x5000 as their identifier.
Command
Field Type Offset Description
Initial Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Continue Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
All recorded range or profile data is exported to the CSV stream. Only the current surface scan,
as determined by the playback position, is exported to the CSV stream.
This command returns an initial reply, followed by a series of "continue" replies if the initial reply's status
field indicates success. The continue replies contain the actual data, and have 0x5000 as their identifier.
Command
Field Type Offset Description
Initial Reply
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Get Flag
The Get Flag command returns the given flag value as a string.
Command
Field Type Offset Description
Reply
Field Type Offset Description
valueLength 32u 10 The length of the string representing the flag's value.
value[valueLength] Char 14 The value of the flag.
Set Flag
The Set Flag command sets the string value for the given flag name.
Command
Field Type Offset Description
status 32s 6 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
Reply
Field Type Offset Description
Command
Field Type Offset Description
Reply
Field Type Offset Description
Get Runtime Variables
The Get Runtime Variables command gets the runtime variables for the given index and length.
Reply
Field Type Offset Description
Upgrade Commands
A client sends firmware upgrade commands over the Upgrade TCP channel (port 3192).
The Control channel (port 3190) and the Upgrade channel can be connected simultaneously. For more
information on Control commands, see Control Commands on page 652.
After connecting to a sensor, you can use the Protocol Version command to retrieve the protocol
version. Protocol version refers to the version of the Gocator Protocol supported by the connected
sensor (the sensor to which a command connection is established), and consists of major and minor
parts. The minor part is updated when backward-compatible additions are made to the protocol. The
major part is updated when breaking changes are made to the protocol.
Start Upgrade
The Start Upgrade command begins a firmware upgrade for the sensors in a system. All sensors
automatically reset 3 seconds after the upgrade process is complete.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 64s 16 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 64s 16 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 64s 16 Reply status. For a list of status codes, see Commands on
page 649.
Command
Field Type Offset Description
Reply
Field Type Offset Description
status 64s 16 Reply status. For a list of status codes, see Commands on
page 649.
Results
The following sections describe the results (data and health) that a sensor sends.
Data Results
A client can receive data messages from a sensor by connecting to the Data TCP channel (port 3196).
The Data channel and the Health channel (port 3194) can be connected at the same time. The sensor
accepts multiple connections on each port. For more information on the Health channel, see Health
Results on page 704.
Messages that are received on the Data and Health channels use a common structure, called Gocator
Data Protocol (GDP). Each message consists of a 6-byte header, containing size and control fields,
followed by a variable-length, message-specific content section. The structure of the GDP message is
defined below.
Gocator Data Protocol
Field Type Offset Description
Messages are always sent in groups. The Last Message flag in the control field is used to indicate the final
message in a group. If there is only one message per group, this bit will be set in each message.
reserved 8u 13 Reserved.
stamps[C] Stamp 14 Array of stamps (see below).
Stamp
Field Type Offset Description
serialNumber 32u 40 Sensor serial number. (In a dual-sensor system, the serial
number of the main sensor.)
Video
1 – 8-bit greyscale
2 – 8-bit color filter
3 – 8-bits-per-channel color (B, G, R, X)
source 8u 19 Source
0 – Top
1 – Bottom
2 – Top Left
3 – Top Right
streamStep 32s 28 Data stream step number. For video, values are:
0 – video stream step
8 – tool data stream step
streamStepId 32s 32 Data stream step identifier within the stream step.
Source 8u 32 Source
0 – Top
1 – Bottom
2 – Top Left
3 – Top Right
reserved[2] 8u 38 Reserved.
Uniform Profile
source 8u 32 Source
0 – Top
1 – Bottom
2 – Top Left
3 – Top Right
reserved[3] 8u 37 Reserved.
streamStep 32s 40 Data stream step number. For a profile, values are:
2 – profile stream step
streamStepId 32s 44 Data stream step identifier within the stream step.
Profile Intensity
source 8u 24 Source
0 – Top
1 – Bottom
2 – Top Left
3 – Top Right
reserved[2] 8u 30 Reserved.
streamStep 32s 32 Data stream step number. For video, values are:
2 – profile stream step
8 – tool data stream step
streamStepId 32s 36 Data stream step identifier within the stream step.
Uniform Surface
source 8u 40 Source
0 – Top
1 – Bottom
2 – Top Left
3 – Top Right
reserved[7] 8u 45 Reserved.
streamStep 32s 52 Data stream step number. For a surface, values are:
3 – surface stream step
8 – tool data stream step
streamStepId 32s 56 Data stream step identifier within the stream step.
Surface Intensity
source 8u 32 Source
0 – Top
1 – Bottom
2 – Top Left
3 – Top Right
reserved[3] 8u 37
streamStep 32s 40 Data stream step number. For surface, values are:
3 – surface stream step
8 – tool data stream step
streamStepId 32s 44 Data stream step identifier within the stream step.
Surface Section
The pose can be used to transform the section data into the surface frame of reference, via a
rotation and then a translation.
Measurement
reserved[2] 8u 10 Reserved.
reserved[3] 8u 5 Reserved.
Alignment Result
Event
Feature Point
id 16u 6 Feature Id
Point.x 64s 8 X Coordinate of Point (Scaled by 10^6)
Point.y 64s 16 Y Coordinate of Point (Scaled by 10^6)
Point.z 64s 24 Z Coordinate of Point (Scaled by 10^6)
id 16u 6 Feature Id
Point.x 64s 8 X Coordinate of Point (Scaled by 10^6)
Point.y 64s 16 Y Coordinate of Point (Scaled by 10^6)
Point.z 64s 24 Z Coordinate of Point (Scaled by 10^6)
Direction.x 64s 32 X Component of Direction Vector (Scaled by 10^6)
Direction.y 64s 40 Y Component of Direction Vector (Scaled by 10^6)
Direction.z 64s 48 Z Component of Direction Vector (Scaled by 10^6)
Feature Plane
id 16u 6 Feature Id
Normal.x 64s 8 X Component of Normal Vector (Scaled by 10^6)
Normal.y 64s 16 Y Component of Normal Vector (Scaled by 10^6)
Normal.z 64s 24 Z Component of Normal Vector (Scaled by 10^6)
originDistance 64s 32 Distance to Origin (Scaled by 10^6)
Feature Circle
id 16u 6 Feature Id
Point.x 64s 8 X Coordinate of Point (Scaled by 10^6)
Point.y 64s 16 Y Coordinate of Point (Scaled by 10^6)
Point.z 64s 24 Z Coordinate of Point (Scaled by 10^6)
Normal.x 64s 32 X Component of Normal Vector (Scaled by 10^6)
Normal.y 64s 40 Y Component of Normal Vector (Scaled by 10^6)
Normal.z 64s 48 Z Component of Normal Vector (Scaled by 10^6)
radius 64s 56 Radius of Circle (Scaled by 10^6)
Health Results
A client can receive health messages from a sensor by connecting to the Health TCP channel (port 3194).
The Data channel (port 3196) and the Health channel can be connected at the same time. The sensor
accepts multiple connections on each port. For more information on the Data channel, see Data Results
on page 692.
Messages that are received on the Data and Health channels use a common structure, called Gocator
Data Protocol (GDP). Each message consists of a 6-byte header, containing size and control fields,
followed by a variable-length, message-specific content section. The structure of the GDP message is
defined below.
Gocator Data Protocol
Field Type Offset Description
Messages are always sent in groups. The Last Message flag in the control field is used to indicate the final
message in a group. If there is only one message per group, this bit will be set in each message.
A Health Result contains a single data block for health indicators. Each indicator reports the current
status of some aspect of the sensor system, such as CPU usage or network throughput.
Health Result
Field Type Offset Description
The indicators block contains a 2-dimensional array of indicator data. Each row in the array has the
following format:
Indicator Format
Field Type Offset Description
When a sensor is accelerated, some health indicators report values from the PC that is
accelerating the sensor, or a combination of both. In the table below, values are reported from
the sensor unless otherwise indicated.
Indicator identifiers
Indicator ID Instance Value
Digital Inputs* 2024 - Current digital input status (one bit per input).
Event Count 2102 - Total number of events triggered.
Camera Search Count 2217 - Number of search states. (Only important when
tracking is enabled.)
profile/surface.
Max Spot Count* 20004 - Maximum number of spots that can be found.
Cast Start State* 20007 The state of the second digital input. (NOTE: Only
available on XLine capable licensed devices)
Point Count 20015 - Number of points found in last resampled
Profile/Surface.
Max Point Count 20016 - Maximum number of points that can be found.
Laser Overheat Duration* 20021 - The length of time in which the laser overheating
state occurred.
Only available on certain 3B laser devices.
FireSync Version 20600 - The FireSync version used by the Gocator build.
The low-level firmware version used by the
sensor.
Last Processing Latency 21001 - Last delay from camera exposure to availability
of all results.
Ethernet Rate 21004 - The average number of bytes per second being
transmitted.
Digital Output Pass 21006 Output Index Number of pass digital output pulse.
Digital Output Fail 21007 Output Index Number of fail digital output pulse.
Output Drops** 21011 Number of dropped output data. The sum of all
output drops (analog, digital, serial, host server,
and ASCII server).
Controlled Trigger Drops 21017 Trigger drops from the Controlled Triggering
System (Grouped with “Trigger Drops” indicator)
Surface Processing Time 21018 Processing Time of Frame on 35XX/32XX
(microseconds)
Max Frame Rate 21019 Max Configurable frame rate given above
Processing Time (scaled by 1x10-6)
Last Log Id 21300 ID of the last available log entry. It is inclusive: for
example, if first = 3 and last = 5, the available log
IDs are 3, 4, 5. If no log is available, the last ID is
less than the first ID.
Z-Index Drop Count 22000 - The number of dropped surfaces due to a lack of
z-encoder pulse during rotational part detection.
Tool Run Time 22004 Tool Index The most recent time taken to execute the tool.
Part Total Emitted 22006 - Total number of parts emitted by profile part
detection.
Part Length Limit 22007 - Number of parts emitted due to reaching the
length limit.
Part Min Area Drops 22008 - Number of parts dropped due to being smaller
than the minimum area.
Part Backtrack Drops 22009 - Number of parts dropped due to backtracking.
Parts Currently Active 22010 - Number of parts currently being tracked.
Part Length 22011 - Length of largest active part.
Part Start Y 22012 - Start Y position of the largest active part.
Part Tracking State 22013 - Tracking state of the largest active part.
Part Capacity Exceeded 22014 - Part detection part or run capacity has been
exceeded.
Part X Position 22015 - Center X position of the largest active part.
Tool Runtime Minimum 22016 - Minimum time spent for tool to process a
sample
Tool Runtime Maximum 22017 - Maximum time spent for tool to process a
sample
Tool Runtime Average 22018 - Average time for tool to process a sample
Tool Runtime Percent 22019 - Average percentage of total time spent running
Average this tool
Bar Alignment Status 22020 - Status of the buffered bar alignment when
aligning:
1 – buffer leveling in progress
2 – buffer searching in progress
3 – buffer scanning in progress
4 – buffer padding in progress
5 – buffering complete; processing alignment on
buffered data
11 – alignment leveling in progress
12 – alignment searching in progress
13 – alignment fitting in progress
14 – alignment complete
15 – alignment completed but failed
16 – alignment cancelled
* When the sensor is accelerated, the indicator's value is reported from the accelerating PC.
** When the sensor is accelerated, the indicator's value is the sum of the values reported from the
sensor and the accelerating PC.
Modbus embeds a Modbus frame into a TCP frame in a simple manner. This is a connection-oriented
transaction, and every query expects a response.
This section describes the Modbus TCP commands and data formats. Modbus TCP communication lets
the client:
l Switch jobs.
The Gocator 4.x/5.x firmware uses mm, mm2, mm3, and degrees as standard units. In all
protocols, values are scaled by 1000, as values in the protocols are represented as integers.
This results in effective units of mm/1000, mm2/1000, mm3/1000, and deg/1000 in the
protocols.
If buffering is enabled with the Modbus protocol, the PLC must read the Buffer Advance output register
(see State on page 714) to advance the queue before reading the measurement results.
Concepts
A PLC sends a command to start each sensor. The PLC then periodically queries each sensor for its latest
measurement results. In Modbus terminology, the PLC is a Modbus Client. Each sensor is a Modbus
Server which serves the results to the PLC.
The Modbus protocol uses TCP for connection and messaging. The PLC makes a TCP connection to the
sensor on port 502. Control and data messages are communicated on this TCP connection. Up to eight
clients can be connected to the sensor simultaneously. A connection closes after 10 minutes of
inactivity.
Messages
All Modbus TCP messages consist of an MBAP header (Modbus Application Protocol), a function code,
and a data payload.
Transaction ID 2 Used for transaction pairing. The Modbus Client sets the value and
the Server (the sensor) copies the value into its responses.
Length 2 Byte count of the rest of the message, including the Unit identifier
and data fields.
Unit ID 1 Used for intra-system routing purpose. The Modbus Client sets the
value and the Server (the sensor) copies the value into its
responses.
Modbus Application Protocol Specification describes the standard function codes in detail. Gocator
supports the following function codes:
4 Read Input Registers 16 Read multiple data values from the sensor.
The data payload contains the registers that can be accessed by Modbus TCP messages. If a message
accesses registers that are invalid, a reply with an exception is returned. Modbus Application Protocol
Specification defines the exceptions and describes the data payload format for each function code.
The sensor data includes 16-bit, 32-bit, and 64-bit data. All data are sent in big endian format, with the
32-bit and 64-bit data spread out into two and four consecutive registers.
0 32-bit Word 1 31 .. 16
1 32-bit Word 0 15 .. 0
0 64-bit Word 3 63 .. 48
1 64-bit Word 2 47 .. 32
2 64-bit Word 1 31 .. 16
3 64-bit Word 0 15 .. 0
Registers
Modbus registers are 16 bits wide and are either control registers or output registers.
The output registers report the sensor states, stamps, and measurement values and decisions. You can
read multiple output registers using a single Read Holding Registers or a single Read Input Registers
command. Likewise, you can control the state of the sensor using a single Write Multiple Register
command.
1000 - 1998 Measurements & RO 333 measurement and decision pairs. See
Decisions Measurement Registers on page 716 for detailed
descriptions.
Control Registers
Control registers are used to operate the sensor. Register 0 stores the command to be executed.
Subsequent registers contain parameters for the commands if applicable. The sensor executes a
command when the value in register 0 is changed. To set the parameters before a command is executed,
you should set up the parameters and the command using a single Multiple Write register command.
The 16-bit values used for Command Register are described below.
2 Align (stationary target) Starts the stationary alignment process. State register 301 will be set to
1 (busy). When the alignment process is complete, the register is set
back to zero.
3 Align (moving target) Starts moving alignment process and also calibrate encoder
resolution. State register 301 will be set to 1 (busy). When the
alignment process is complete, the register is set back to zero.
7 Software trigger Software trigger the sensor to capture one frame. The sensor must
already be running, in trigger mode “Software”. Otherwise, software
trigger has no effect.
Output Registers
Output registers are used to output states, stamps, and measurement results. Each register address
holds a 16-bit data value.
State
State registers report the current sensor state.
301 Modbus Command in 16u 1 when the sensor is busy performing the last
Progress command, 0 when done. Registers 302 and 311-371
below are only valid when there is no command in
progress.
303 Encoder Position High 64u Current encoder position (64-bit value, requiring
four 16-bit registers)
304 Encoder
305 Encoder
307 Time High 64s Uptime timestamp (64-bit value, requiring four 16-
bit registers)
308 Time
309 Time
311 Job File Name Length 16u Number of characters in the current job file name.
(Valid when register 301 = 0.)
312 – 371 Live Job Name 16u Name of currently loaded job file. Does not include
the extension. Each 16-bit register contains a single
character. (Valid when register 301 = 0.)
375 Runtime Variable 0 High 32s Runtime variable value stored in two register
locations.
376 Runtime Variable 0 Low
... ... ... ...
381 Runtime Variable 3 High 32s Runtime variable value stored in two register
locations.
382 Runtime Variable 3 Low
Stamp
Stamps contain trigger timing information used for synchronizing a PLC's actions. A PLC can also use this
information to match up data from multiple sensors.
In Profile mode, the stamps are updated after each profile is processed. In Surface mode, the stamps
are updated after each surface has been processed.
976 Buffer Advance Register 16u If buffering is enabled, this address must be read
by the PLC Modbus client first to advance the
buffer. After the buffer advance read operation,
the Modbus client can read the updated
Measurements & Decisions in addresses 1000-1059.
980 zPosition High 64u Encoder position at time of last index pulse. 64-bit
value, requiring four 16-bit registers.
981 zPosition
982 zPosition
983 zPosition Low
984 Exposure High 32u Laser exposure (µs) of the last frame. Stored in two
register locations.
988 Encoder Position High 64u Encoder position of the last frame when the image
data was scanned/taken. 64-bit value, requiring
four 16-bit registers.
992 Time High 64u Time stamp in microseconds of the last frame. 64-
bit value, requiring four 16-bit registers.
993 Time
994 Time
995 Time Low
996 Frame Index High 64u The frame number of the last frame. 64-bit value,
requiring four 16-bit registers.
Measurement Registers
Measurement results are reported in pairs of values and decisions. Measurement values are 32 bits wide
and decisions are 8 bits wide.
In Profile mode, the measurement results are updated after each profile is processed. In Surface mode,
the measurement results are updated after each discrete part has been processed.
1005 Decision 1
1008 Decision 2
l Switch jobs.
Note that in firmware version 5.2, the identity information was updated as follows:
This update may require a change on a device attempting to connect to a sensor via EtherNet/IP. A
compatible EDS file can be downloaded from the web interface. If the existing EDS must be maintained,
the device can be configured to disable electronic keying, ignoring the product code and version
numbers.
To use the EtherNet/IP protocol, it must be enabled and configured in the active job. For information on
configuring the protocol using the Web interface, see Ethernet Output on page 510.
The Gocator 4.x/5.x firmware uses mm, mm2, mm3, and degrees as standard units. In all
protocols, values are scaled by 1000, as values in the protocols are represented as integers.
This results in effective units of mm/1000, mm2/1000, mm3/1000, and deg/1000 in the
protocols.
Sensors support unconnected or connected explicit messaging (with TCP), as well as implicit (or I/O)
messaging. For information on explicit messaging assemblies and objects, see Explicit Messaging below.
For information on implicit messaging assemblies and objects, see Implicit Messaging on page 725.
Explicit Messaging
To EtherNet/IP-enabled devices on the network, the sensor information is seen as a collection of objects,
which have attributes that can be queried.
Sensors support all required objects for explicit messaging, such as the Identity object, TCP/IP object, and
Ethernet Link object. In addition, an Assembly object is used for sending sensor and sample data and
receiving commands. The Assembly object contains four assemblies: the command assembly (32 bytes),
The PLC sends a command to start a sensor. The PLC then periodically queries the attributes of the
assembly objects for its latest measurement results. In EtherNet/IP terminology, the PLC is a scanner
and the sensor is an adapter.
For detailed information on setting up explicit messaging using Allen-Bradley PLCs, see
https://downloads.lmi3d.com/setting-ethernetip-explicit-messaging-allen-bradley-plcs.
The following sections describe the explicit messaging assemblies and objects.
4 Physical Link Structure (See See 5.3.3.2.4 of CIP Specification Volume 2: Get
Object description) Path size (UINT)
Path (Padded EPATH)
All assembly object instances are static. Data in a data byte array in an assembly object are stored in the
big endian format.
Command Assembly
The command assembly object is used to start, stop, and align the sensor, and also to switch jobs on the
sensor.
Command Assembly
Information Value
Class 0x4
Instance 0x310
Attribute Number 3
Length 32 bytes
Attributes 1 and 2 are not implemented, as they are not required for the static assembly object.
Command Definitions
Value Name Description
0 Stop running Stop the sensor. No action if the sensor is already stopped
1 Start Running Start the sensor. No action if the sensor is already started.
2 Stationary Alignment Start the stationary alignment process. Byte 1 of the sensor state
assembly will be set to 1 (busy) until the alignment process is complete,
then back to zero.
3 Moving Alignment Start the moving alignment process. Byte 1 of the sensor state assembly
will be set to 1 (busy) until the alignment process is complete, then back
to zero.
5 Load Job Load the job. Set bytes 1-31 to the file name (one character per byte. File
name must be null-terminated. The job name and extension are case-
sensitive. If the extension “.job” is missing, it is automatically appended to
the file name.
7 Software trigger Sends a software trigger to the sensor to capture one frame. The sensor
must already be running, and its trigger mode must be set to “Software”.
Otherwise, software trigger has no effect.
Class 0x04
Instance 0x311
Attribute Number 3
Length 64 bytes
Attribute 3
Attribute Name Type Value Description Access
3 Command Byte See below Runtime variable configuration information. See Get
Array below for more details.
0-3 Runtime 32s Stores the intended value of the Runtime Variable at index 0.
Variable 0
4-7 Runtime 32s Stores the intended value of the Runtime Variable at index 1.
Variable 1
8-11 Runtime 32s Stores the intended value of the Runtime Variable at index 2.
Variable 2
12-15 Runtime 32s Stores the intended value of the Runtime Variable at index 3.
Variable 3
16-63 Reserved
Class 0x04
Instance 0x320
Attribute Number 3
Attributes 1 and 2 are not implemented, as they are not required for the static assembly object.
Attribute 3
Attribute Name Type Value Description Access
3 Command Byte See below Sensor state information. See below for more Get
Array details.
1 - Aligned
The value is only valid when byte1 is set to 0.
20-83 Current Job Name of currently loaded job, including the ".job"
Filename extension. Each byte contains a single character. Valid when
byte 1 = 0.
Class 0x04
Instance 0x321
Attribute Number 3
Attribute 3
Attribute Name Type Value Description Access
3 Command Byte See below Sample state information. See below for more Get
Array details.
2-9 Z Index Position 64u Encoder position at time of last index pulse of
the last frame.
18-25 Encoder Position 64u Encoder position of the last frame when the
image data was scanned/taken.
34-41 Frame Counter 64u The frame number of the last frame.
... ...
Measurement results are reported in pairs of values and decisions. Measurement values are 32 bits wide
and decisions are 8 bits wide.
The measurement ID defines the byte position of each pair within the state information. The position of
the first word can be calculated as (80 + 5 * ID). For example, a measurement with ID set to 4 can be
read from byte 100 (high word) to 103 (low word) and the decision at 104.
Implicit Messaging
Implicit messaging uses UDP and is faster than explicit messaging, and is ideal for time-critical
applications. However, implicit messaging is layered on top of UDP. UDP is connectionless and data
delivery is not guaranteed. For this reason, implicit messaging is only suitable for applications where
occasional data loss is acceptable.
For detailed information on setting up implicit messaging using Allen-Bradley PLCs, see
http://lmi3d.com/sites/default/files/APPNOTE_Implicit_Messaging_with_Allen-Bradley_PLCs.pdf.
All assembly object instances are static. Data in a data byte array in an assembly object are stored in the
big endian format.
Class 0x04
Instance 0x64
Attribute Number 3
Length 32 bytes
1-31 Reserved (except for If you are setting the runtime variables, use
configuring runtime bytes 4-19 to define the values of each of the
variables and loading job four runtime variables in little endian format.
file)
If you are loading job file, use bytes 1-31 for
the filename, one character per byte. The job
name and extension are case-sensitive. The
filename must be null terminated and must
end with ".job".
Class 0x04
Instance 0x322
Attribute Number 3
state Bit 0:
1 – Explicit or Implicit Command in progress
0 – No Explicit or Implicit command is in
progress
Bit 1
1 – Aligned
0 – Not aligned
… …
119 Decision 63 8u Measurement decision is a bit mask where:
Bit 0:
1 – Pass
0 – Fail
Bits [1-7]:
0 – Measurement value OK
1 – Invalid Value
2 – Invalid Anchor
(0x80000000 if invalid)
… …
372-375 Measurement 63 32s Measurement value in µm.
(0x80000000 if invalid)
Implicit messaging has advantages and disadvantages. Implicit messaging uses UDP and is faster than
explicit messaging and is ideal for time-critical applications. Since implicit messaging is layered on top of
UDP, it is connectionless and data delivery is not guaranteed. For this reason, implicit messaging is only
suitable for applications where occasional data loss is acceptable. Two connection types are available for
implicit communication: a Monitor Data connection or a Monitor Data and Control Data connection.
Explicit messaging is more suitable for deterministic and verified communication transfer where no
losses are acceptable. Add-On Profile (AOP) is not available for the Gocator, and it is not possible to use
the EDS file for automatic configuration.
For these reasons, LMI recommends in most application using a closed ethernet subnet (i.e., network
switch, PLC, Gocator(s), and setup PC only) to minimize losses and collisions and cyclical implicit
messaging over the EtherNet/IP protocol unless a specific control command such as job loading and/or
transfer verification is required.
Requirements Details
Gocator Firmware 5.2 and higher
Gocator Series G1, G2, and G3 sensors.
Required Files GocatorEip.eds
LMI.ico
Gocator_EthernetIP.ACD
Other Allen-Bradley L16ER-BB1B PLC
Allen-Bradley Studio 5000 programming tool V21.11 or newer
D-Link Unmanaged Industrial Gigabit Ethernet Switch DGS-108
Note: The Ethernet card to which the Gocator is connected should be added as a module to the
Backplane. Verify that the IP Address is on the correct subnet. Note the IP address should be that of the
PLC’s Ethernet modules, not that of the Gocator’s.
Little Endian Byte Order: The least significant byte (the "little end") of the data is placed at the byte with
the lowest address. The rest of the data is placed in order of increasing significance in the next three
bytes in memory.
Most Allen-Bradley PLCs default to Little Endian addressing formats, but you should verify this when
configuring the PLC.
5. Set the Trigger Override dropdown to the type of implicit messaging you are using.
For cyclic messaging, set Trigger Override to Force Cyclic.
For change of state messaging, set Trigger Override to Force Change of State.
When you set up the PLC to communicate with a Gocator using change of state implicit messaging, an event
task must be created on the PLC to rapidly check whether the sensor is running; if the frame count
1. If you haven’t already done so, download the EDS file from the Gocator sensor.
For more information, see To download the EDS file: on the previous page.
2. In Studio 5000, under the Tools menu, click EDS Hardware Installation Tool.
7. Click Next.
9. Verify that the tool automatically selects the LMI logo from the unzipped folder.
The .ico file contained in the zip folder you downloaded previously contains the logo.
10. If the tool does not automatically select the LMI logo, navigate to the file, select it, and then click Next.
1. Click the Who Active button to the right of the Path field.
2. Click Refresh in RSLinx the Who Active dialog to update your available devices.
4. If you do not see the Go Online option at this point, make sure that RSLinx has been started and is running
in the background on your setup PC.
Device discovery will not complete if RSLinx is not running.
7. In Studio 5000, verify that the path is updated to the IP address of your controller.
12. In the New Module dialog, in the Name field, give the new IO device a unique name.
When the Gocator is in Implicit Messaging mode, data will be streamed and stored in the Gocator1:I tag
when both the PLC is in Run mode and the Gocator is started. The tag address header is formatted as
devicename:I and/or devicename:O for inputs and outputs, respectively.
For the data format, see Implicit Messaging Output Assembly on page 726.
The EDS file now contains detailed tag descriptions as shown below that can be used directly in the PLC
program.
b. Confirm that frames are properly stored in the stored array, without any repetition or dropped frames.
In this case, the Gocator frame count is stored in a user-defined array.
In PLC programming, the standard practice is to use bits instead of sending a value representing that
command, for example, start/stop bits. When using values, the PLC needs to add more code to convert it
to bits and vice versa.
Since the Gocator does not allow parallel commands, a priority scheme is needed to handle multiple
command bits being set at the same time. Only the bit with the highest priority will be accepted as the
command.
For information on the command assembly structure, see Implicit Messaging Command Assembly on
page 725.
It’s important to understand that because the Gocator is driven internally by its own clock, and because
users can configure the Gocator for any frame rate—independently of the RPI request configured on the
PLC—Cyclic implicit messaging can cause unnecessary data loss if the two clocks are not synchronized.
Using Change of State implicit messaging instead can overcome this issue. For instructions on how to set
up Change of State implicit messaging, see Setting Up Change of State Implicit Messaging.
The data block used to send control messages to the Gocator should have been set properly up in
Setting Up Implicit Messaging on the PLC on page 731. It will appear in the Gocator Module-Defined data
types as shown below:
1. Make sure that you have downloaded your PLC program to the controller and that your controller is in Run
mode.
For information on downloading the the PLC program to the controller, see Install EDS File on page 731.
This process can be repeated to stop the sensor, clear alignment, start moving alignment, start stationary
alignment, or issue a software trigger by typing the proper integer value into the Command byte of the
1. Make sure that you have downloaded your PLC program to the controller and that your controller is in Run
mode.
For information on downloading the the PLC program to the controller, see Install EDS File on page 731.
4. If 1.job is the name of the job file to be loaded on the sensor and it is not currently running, type each of the
five characters making up the filename into the first five characters of the Reserved bytes of the Command
assembly.
The ASCII character inputs here are case sensitive and the extension, .job, must be included. All non-
jobname characters must be null or empty values. Changing the display option from Decimal (which is the
default) to ASCII can make this easier.
6. Go to a web browser and type in the sensor IP address to the URL bar
This process can be repeated to load runtime variables by typing the proper integer value into the
Command byte of the Output assembly after preloading the runtime variable values into four successive
bytes starting at byte 4 of the Reserved bytes. For additional commands and control options, Implicit
Messaging Command Assembly on page 725, or refer to the provided sample Studio 5000 job file.
2. Right-click in the middle of the screen and choose New Tag from the context menu.
5. Right-click in the middle of the screen again and choose New Tag from the context menu.
7. In the ladder, navigate to the Input/Output function blocks and click MSG to add a Message function block.
You may need to add a new rung to allow this.
8. Once the new MSG function block has been added, click the tag dropdown and select the MSG tag you
created earlier.
14. In the Message Path Browser dialog, choose the EtherNet/IP Network node.
This will route communication messages to the EtherNet/IP network.
16. In Path, type the IP address of the Gocator to complete the path.
Double-check that the network, port, and IP address are separated by commas in the form
“networkname,port,IPaddress”.
18. In the Controller Organizer, verify that the serial number is updated in the RetrievedSN tag by going to the
Controller Tags node.
To obtain a measurement result, use the procedure described above but change the messaging block
class to 4, the instance to 801, and the attribute to 3. The data storage location for this attribute will
have to be the proper type and length; for more information, see Sensor State Assembly on page 722.
You will now have to create ladder logic to copy the correct bits in the raw data stream into Controller
Tags holding the individual results. This can be done with the Bit Field Distribute (BTD) block. For
l Start a sensor
l Stop a sensor
l Align a sensor
l Clear sensor alignment
l Set a sensor’s runtime variables
l Load a job on a sensor
l Trigger a sensor
LMI recommends following the steps in To read the sensor's serial number: on page 755 to verify
the communication path and message block before attempting to control a sensor.
2. Right-click in the middle of the screen and select New Tag from the context menu.
This creates a block to store parameters for sending data to the Gocator.
5. Right-click in the middle of the screen again and choose New Tag from the context menu.
If you will only be starting or stopping the sensor, leave Style at the default setting of Decimal.
9. In the ladder, navigate to the Input/Output function blocks and click MSG to add a Message function block.
You may need to add a new rung to allow this.
10. Once the new MSG function block has been added, click the tag dropdown and select the MSG tag you
created earlier.
11. Click the grey box to open the Configuration Dialog box
12. In the Message Configuration dialog, choose the Set Attribute Single function from the Service Type
drop-down.
This will auto populate the Service Code hex character.
14. Select the SINT[32] tag you created to store the command assembly from the Destination Element
dropdown
18. Add the ethernet port that is physically connected to the Gocator.
This will add the specific port address to your communication path.
1. Make sure that you have downloaded your PLC program to the controller and that your controller is in Run
Mode.
5. Go to a web browser and type in the sensor IP address to the URL bar. This should load the web GUI
1. Make sure that you have downloaded your PLC program to the controller and that your controller is in Run
Mode
4. If 1.job is the job file to be loaded on the sensor and it is not currently running, type each of the five
characters making up the filename into Command[1] through Command[5] of the Command assembly.
The ASCII character inputs here are case sensitive and the extension, .job, must be included. All non-
jobname characters must be null or empty values. If the style was changed to ASCII as the default during the
tag creation, this will be done already, and the alphanumeric characters can be directly typed into the value
column of the bytes.
6. Go to a web browser and type in the sensor IP address to the URL bar.
7. Once the web GUI loads, verify that the job was loaded on the Gocator by looking at the job name box.
PROFINET is not supported on A and B revision Gocator 2100 and 2300 sensors.
This section describes the PROFINET modules that let a controller do the following:
l Switch jobs.
l Align and run sensors.
l Receive sensor states, stamps, and measurement results.
l Set and retrieve runtime variables.
To use the PROFINET protocol, it must be enabled and configured in the active job. For information on
configuring the protocol using the Web interface, see Ethernet Output on page 510.
The Gocator 4.x/5.x firmware uses mm, mm2, mm3, and degrees as standard units. In all
protocols, values are scaled by 1000, as values in the protocols are represented as integers.
This results in effective units of mm/1000, mm2/1000, mm3/1000, and deg/1000 in the
protocols.
Control Module
The client sends the Control module to the sensor. The length of the Control module is 256 bytes.
Unused space is for future expansion.
Command Definitions
Value Name Description
7 Software trigger Software trigger the sensor to capture one frame. The sensor must
already be running, in trigger mode “Software”. Otherwise, software
trigger has no effect.
Data
Byte Index Name Description
Type
0-3 Runtime 32s Stores the intended value of the Runtime Variable at index 0.
Variable 0
4-7 Runtime 32s Stores the intended value of the Runtime Variable at index 1.
Variable 1
8-11 Runtime 32s Stores the intended value of the Runtime Variable at index 2.
Variable 2
12-15 Runtime 32s Stores the intended value of the Runtime Variable at index 3.
Variable 3
State Module
The length of the State module is 116 bytes. The sensor sends the module to the client. The runtime
variables are received from the sensor in big endian format. The extra unused space is for future
expansion.
Data
Byte Index Name Description
Type
20-83 Current job Name of currently loaded job, including extension. Each byte contains a
filename single character. Max 64 bytes.
(valid when byte 1 = 0)
Stamp Module
The length of the Stamp module is 45 bytes. The sensor sends the module to the client. The extra
unused space is for future expansion.
Data
Byte Index Name Description
Type
Measurements Module
The length of the Measurement module is 800 bytes. The sensor sends the module to the client. The
measurements and decisions are sent in big endian format only. Each measurement plus decision takes
5 bytes so this module can hold a maximum of 800/5 = 160 measurements + decisions.
Data
Byte Index Name Description
Type
1 – Invalid Value
2 – Invalid Anchor
5-8 Measurement 1
9 Decision 1
... ...
795-798 Measurement
159
799 Decision 159
The byte mapping of each measurement/decision pair depends on its ID as specified in the
measurement interface. Each measurement will begin at byte (0 + 5*ID). For example, a
measurement with ID set to 4 can be read from bytes 20 (high byte) to 23 (low byte) and the
decision at 24.
ASCII Protocol
This section describes the ASCII protocol.
The ASCII protocol is available over either serial output or Ethernet output. Over serial output,
communication is asynchronous (measurement results are automatically sent on the Data channel when
the sensor is in the running state and results become available). Over Ethernet, communication can be
asynchronous or can use polling. For more information on polling commands, see Polling Operation
Commands (Ethernet Only) on the next page.
The protocol communicates using ASCII strings. The output result format from the sensor is user-
configurable.
To use the ASCII protocol, it must be enabled and configured in the active job.
The Gocator 4.x/5.x firmware uses mm, mm2, mm3, and degrees as standard units. In all
protocols, values are scaled by 1000, as values in the protocols are represented as integers.
This results in effective units of mm/1000, mm2/1000, mm3/1000, and deg/1000 in the
protocols.
For information on configuring the protocol with the Web interface (when using the protocol over
Ethernet), see Ethernet Output on page 510.
For information on configuring the protocol with the Web interface (when using the protocol over Serial),
see Serial Output on page 520.
Connection Settings
Ethernet Communication
With Ethernet ASCII output, you can set the connection port numbers of the three channels used for
communication (Control, Data, and Health):
Channels can share the same port or operate on individual ports. The following port numbers are
reserved for sensor internal use: 2016, 2017, 2018, and 2019. Each port can accept multiple
connections, up to a total of 16 connections for all ports.
Serial Communication
Over serial, ASCII communication uses the following connection settings:
Start Bits 1
Stop Bits 1
Parity None
Data Bits 8
Format ASCII
Delimiter CR
Up to 16 users can connect to the sensor for ASCII interfacing at a time. Any additional connections will
remove the oldest connected user.
Under asynchronous operation, measurement results are automatically sent on the Data channel when
the sensor is in the running state and results become available. The result is sent on all connected data
channels.
The Health channel is used to receive health indicators (see Health Channel on page 788).
<COMMAND><DELIMITER><PARAMETER><TERMINATION>
If a command has more than one parameter, each parameter is separated by the delimiter. Similarly, the
reply has the following format:
<STATUS><DELIMITER><OPTIONAL RESULTS><DELIMITER>
The status can either be "OK" or "ERROR". The optional results can be relevant data for the command if
successful, or a text based error message if the operation failed. If there is more than one data item,
each item is separated by the delimiter.
The delimiter and termination characters are configured in the Special Character settings.
Special Characters
The ASCII Protocol has three special characters.
Special Characters
Special Character Explanation
Delimiter Separates input arguments in commands and replies, or data items in results. Default value is
",".
Terminator Terminates both commands and result output. Default value is "%r%n".
The values of the special characters are defined in the Special Character settings. In addition to normal
ASCII characters, the special characters can also contain the following format values.
%t Tab
%n New line
%r Carriage return
Command Channel
The following sections list the actions available on the command channel.
Optional parameters are shown in italic. The placeholder for data is surrounded by brackets (<>). In the
examples, the delimiter is set to ','.
Formats
Message Format
The start target (optional) is the time or encoder position at which the sensor will be
started. The time and encoder target value should be set by adding a delay to the time
or encoder position returned by the Stamp command. The delay should be set such
that it covers the command response time of the Start command.
Examples:
Command: Start
Reply: OK
Command: Start,1000000
Reply: OK
Command: Start
Reply: ERROR, Could not start the sensor
Stop
The stop command stops the sensor system (causes it to enter the Ready state). This command is valid
when the system is in the Ready or Running state.
Formats
Message Format
Command Stop
Examples:
Command: Stop
Reply: OK
Trigger
The Trigger command triggers a single frame capture. This command is only valid if the sensor is
configured in the Software trigger mode and the sensor is in the Running state.
Formats
Message Format
Command Trigger
Examples:
LoadJob
The Load Job command switches the active sensor configuration.
Formats
Message Format
Examples:
Command: LoadJob,test.job
Reply: OK,test.job loaded successfully
Command: LoadJob
Reply: OK,test.job
Command: LoadJob,wrongname.job
Reply: ERROR, failed to load wrongname.job
Stamp
The Stamp command retrieves the current time, encoder, and/or the last frame count.
Formats
Message Format
Command Stamp,time,encoder,frame
If no parameters are given, time, encoder, and frame will be returned. There could be
more than one selection.
Examples:
Command: Stamp
Reply: OK,Time,9226989840,Encoder,0,Frame,6
Command: Stamp,frame
Reply: OK,6
Clear Alignment
The Clear Alignment command clears the alignment record generated by the alignment process.
Command ClearAlignment
Examples:
Command: ClearAlignment
Reply: OK
Moving Alignment
The Moving Alignment command performs an alignment based on the settings in the sensor's live job
file. A reply to the command is sent when the alignment has completed or failed. The command is timed
out if there has been no progress after one minute.
Formats
Message Format
Command MovingAlignment
Examples:
Command: MovingAlignment
Reply: OK
Command: MovingAlignment
Reply: ERROR, ALIGNMENT FAILED
Stationary Alignment
The Stationary Alignment command performs an alignment based on the settings in the sensor's live job
file. A reply to the command is sent when the alignment has completed or failed. The command is timed
out if there has been no progress after one minute.
Formats
Message Format
Command StationaryAlignment
Examples:
Command: StationaryAlignment
Reply: OK
Command: StationaryAlignment
Reply: ERROR,ALIGNMENT FAILED
Formats
Message Format
Command setvars,index,length,data
Reply OK or ERROR
Examples:
Command: setvars,0,4,1,2,3,4
Reply: OK
Formats
Message Format
Command setvars,index,length
Reply OK,data
Examples:
Command: getvars,0,4
Reply: OK,1,2,3,4
Data Channel
The following sections list the actions available on the data channel.
Optional parameters are shown in italic. The placeholder for data is surrounded by brackets (<>). In the
examples, the delimiter is set to ','.
Result
The Result command retrieves measurement values and decisions.
Formats
Message Format
Reply If no arguments are specified, the custom format data string is used.
OK, <custom data string> ERROR, <Error Message>
Examples:
Result,0,1
OK,M00,00,V151290,D0,M01,01,V18520,D0
Result,2
Result
OK,1420266101,151290,0
Value
The Value command retrieves measurement values.
Formats
Message Format
Reply If no arguments are specified, the custom format data string is used.
OK, <custom data string> ERROR, <Error Message>
If arguments are specified,
OK, <data string in standard format, except that the decisions are not sent> ERROR,
<Error Message>
Examples:
Value,0,1
OK,M00,00,V151290,M01,01,V18520
Value,2
Value
Decision
The Decision command retrieves measurement decisions.
Formats
Message Format
Reply If no arguments are specified, the custom format data string is used.
OK, <custom data string> ERROR, <Error Message>
If arguments are specified,
OK, <data string in standard format, except that the values are not sent> ERROR, <Error
Message>
Examples:
Decision,0,1
OK,M00,00,D0,M01,01,D0
Decision,2
Decision
OK,1420266101, 0
Health Channel
The following sections list the actions available on the health channel.
Optional parameters are shown in italic. The placeholder for data is surrounded by brackets (<>). In the
examples, the delimiter is set to ','.
Formats
Message Format
Reply OK, <health indicator of first ID>, <health indicator of second ID>
ERROR, <Error Message>
Examples:
health,2002,2017
OK,46,1674
Health
ERROR,Insufficient parameters.
M tn , in , V vn , D d1 CR
Bit 0:
1 – Pass
0 – Fail
Bits 1-7:
0 – Measurement value OK
1 – Invalid value
2 - Invalid anchor
Result Placeholders
Format Value Name Explanation
%encoder Encoder Position Encoder position of the last frame when the image data was
scanned/taken.
%value[Measurement Value Measurement value of the specified measurement ID. The ID must
ID] correspond to an existing measurement.
C language printf-style formatting is also supported: for example, %sprintf[%09d, %value[0]]. This allows
fixed length formatting for easier input parsing in PLC and robot controller logic.
Gocator 2500 series sensors do not support the Selcom Serial Protocol.
To use the Selcom protocol, it must be enabled and configured in the active job.
For information on configuring the protocol using the Web interface, see Serial Output on page 520.
Units for data scales use the standard units (mm, mm2, mm3, and degrees).
Serial Communication
Data communication is synchronous using two unidirectional (output only) RS-485 serial channels: data
(Serial_Out0) and clock (Serial_Out1). See Serial Output on page 901 for cable pinout information.
Measurement results are sent on the serial output (data) in asynchronous mode. Measurement values
and decisions can be transmitted to an RS-485 receiver, but job handling and control operations must be
performed through the sensor's web interface or through communications on the Ethernet output.
Connection Settings
The Selcom protocol uses the following connection settings:
Data Bits 16
Format Binary
Message Format
The data channel is valid on the rising edge of the clock and data is output with the most significant bit
first, followed by control bits for a total of 16 bits of information per frame. The time between the start
of the camera exposure and the delivery of the corresponding range data is fixed to a deterministic
value.
The sensor can output data using one of four formats, illustrated below, where:
The included GenTL driver allows GenICam-compliant third-party software applications such as Halcon
and Common Vision Blox to acquire and process 3D data and intensity generated from the sensor.
l Video
l Profile (with Uniform Spacing disabled). In this mode, the raw profiles are resampled and accu-
mulated into a surface.
To use these third-party software applications, you must configure a system variable so the
software can access the GenTL driver. For instructions, see To configure system variables to use
the driver in Windows 7, below.
After downloading the package and unzipping the file to a location you will remember, you will find the
driver in the GenTL\x86 or GenTL\x64 subfolder under Integration > GenTL (you can move the
GenTL folder to a more convenient location).
5. In the Environment Variables dialog, under the System variables list, click New.
The GenTL driver packs the output, intensity, and stamps (e.g., time stamp, encoder index, etc.) into
either a 16-bit RGB image or a 16-bit grey scale image. You can select the format in the Go2GenTL.xml
setting file.
The width and height of the 16-bit RGB or grey scale image is calculated from the maximum number of
columns and rows needed to accommodate the sensor's field of view and the maximum part length.
Channel Details
Red Height map information. The width and height of the image represent the dimensions
in the X and Y axis. Together with the pixel value, each red pixel presents a 3D point in
the real-world coordinates.
The following formula can be used to calculate the real-world coordinates (X, Y, Z) from
pixel coordinates (Px, Py, Pz):
X = X offset + Px * X resolution
Y = Y offset + Py * Y resolution
Z = Z offset + Pz * Z resolution
Refer to the blue channel on how to retrieve the offset and resolution values. If Pz is 0
if the data is invalid. The Z offset is fixed to -32768 * Z resolution. Z is zero if Pz is 32768.
Green Intensity information. Same as the red channel, the width and height of the image
represent the dimension in the X and the Y axis. Together with the pixel value, each
blue pixel represents an intensity value in the real-world coordinates.
The following formula can be used to calculate the real-world coordinates (X, Y, Z) from
pixel coordinates (Px, Py, Pz):
X = X offset + Px * X resolution
Y = Y offset + Py * Y resolution
Z = 16-bit intensity value
The intensity value is 0 if the intensity image is not available. Gocator outputs 8-bit
intensity values. The values stored in the 16-bit RGB image is multiplied by 256. To
obtain the original values, divide the intensity values by 256.
Refer to the blue channel on how to retrieve the offset and resolution values.
Blue Stamp information. Stamps are 64-bit auxiliary information related to the height map
and intensity content. The next table explains how the stamps are packed into the blue
pixel channel
The following table shows how the stamp information is packed into the blue channel. A stamp is a 64-
bit value packed into four consecutive 16-bit blue pixels, with the first byte position storing the most
significant byte.
0 0..3 Version
7 28..31 X resolution(nm)
Rows Details
0 .. (max part height - 1) Height map information. The width and height of the image represent the dimensions
in the X and Y axis. Together with the pixel value, each pixel presents a 3D point in the
real-world coordinates.
The following formula can be used to calculate the real-world coordinates (X, Y, Z) from
pixel coordinates (Px, Py, Pz):
X = X offset + Px * X resolution
Y = Y offset + Py * Y resolution
Z = Z offset + Pz * Z resolution
Refer to the blue channel on how to retrieve the offset and resolution values. If Pz is 0
if the data is invalid. The Z offset is fixed to -32768 * Z Resolution. Z is zero if Pz is
32768.
(max part height) .. 2* (max Intensity information. The width and height of the image represent the dimension in
part height) the X and the Y axis. Together with the pixel value, each blue pixel represents an
If intensity is enabled intensity value in the real-world coordinates.
The following formula can be used to calculate the real-world coordinates (X, Y, Z) from
pixel coordinates (Px, Py, Pz): The following formula assumes Py is relative to the first
row of the intensity information, not the first row of the whole 16-bit grey scale image.
X = X offset + Px * X resolution
Y = Y offset + Py * Y resolution
Z = 16-bit intensity value
This intensity value is 0 if the intensity image is not available. Gocator outputs 8-bit
intensity values. The values stored in the 16-bit Grey scale image is multiplied by 256.
To obtain the original values, divide the intensity values by 256.
Refer to the stamps on how to retrieve the offset and resolution values.
The last row of the 16-bit Stamp information. Stamps are 64-bit auxiliary information related to the height map
grey scale image and intensity content. The next table explains how the stamps are packed into the blue
pixel channel
The following table shows how the stamp information is packed into the last row. A stamp is a 64-bit
value packed into four consecutive 16-bit pixels, with the first byte position storing the most significant
byte.
0 0..3 Version
7 28..31 X resolution(nm)
Registers
GenTL registers are multiples of 32 bits. The registers are used to control the operation of the GenTL
driver, send commands to the sensors, or to report the current sensor information.
260 WidthReg RO 4 Specify the width of the returned images. The part
height map is truncated if it is wider than the
specified width.
specified configuration.
XML Settings File
The settings file, Go2GenTL.xml, resides in the same directory as the Gocator GenTL driver. Users can set
the resample mode and output format by changing the setting in this file.
When resampling mode is enabled, the GenTL driver will resample the
height map so that the pixel spacing is the same in the X and Y axis. The
default value is 1.
DataFormat 32u Settings to choose 16-bit RGB or 16-bit grey scale image output:
0 – 16-bit RGB Image
1 – 16-bit grey scale Image
The default value is 0.
The current GenTL driver does not support scanning in profile mode.
For information on setting up the GenTL driver, see GenICam GenTL Driver on page 793.
This section describes how to configure Halcon to acquire data from the 4.x firmware. You should be
familiar with the sensor's Surface mode. Before continuing, make sure Halcon is installed.
Setting Up Halcon
Before using Halcon with a sensor, you must set up Halcon.
To set up Halcon:
1. Connect a sensor to the PC running Halcon.
You will need a Master hub to connect the sensor to the PC. For more information, see Installation on
page 35 and Network Setup on page 49.
3. On the Scan page, click the Surface icon to switch to Surface mode.
4. (Optional) If you need intensity data, check the Acquire Intensity option.
7. On the Output page, enable the required surface under Data and choose Gocator in Protocol.
10. In Halcon, in the Assistants menu, click Open New Image Acquisition.
11. In the dialog that opens, in the Source tab, check the Image Acquisition Interface option and choose
GenICamTL in the drop-down.
The driver uses the Gocator protocol discovery messages to search for available Gocator
sensors. Discovery messages can be blocked by a PC’s firewall. You should therefore turn
off the firewall and try again if the sensor can't be detected.
14. In the sensor's web interface, click the Snapshot button to trigger the output of a surface.
Halcon Procedures
The Halcon example code contains internal procedures that you can use to decompose the RGB image
and to control registers that the GenTL driver opens.
You can import the procedures into your own code by selecting File > Insert Program > Insert Procedures
and then choosing the example code Continuous_Acq.hdev under the Examples/Halcon directory.
The Go2GenTL.xml file for Gocator 4.x has more fields than the Gocator 3.x version. Make sure
you are using the correct version.
Halcon Procedures
Procedures Description
Go2GenTL_ The GenTL driver packs the height map, intensity and stamp information into a 16-bit RGB image.
ParseData The function is used to extract data from the RGB image.
For details on how the information is packed in the data, see the sections under GenICam GenTL
Driver on page 793.
The function accepts the image acquired from grab_image_async, and returns the height map,
intensity and stamps.
Parameters (Input)
Image: RGB Image acquired by using grab_image_async.
Parameters (Output)
HeightMap : The height map image.
Intensity: The intensity image.
FrameCount: The number of frames.
Timestamp : The timestamp.
Encoder: The encoder position.
EncoderIndex: The last index of the encoder.
Inputs: The digital input states.
xOffset: The X offset in millimeters.
xResolution: The X resolution in millimeters.
yOffset: The Y offset in millimeters.
yResolution: The Y resolition in millimeters.
zOffset: The Z offset in millimeters.
zResolution: The Z resolution in millimeters.
Width: The width (number of columns) of the image that contains the part. The part width
can be less than the image width requested by the user.
Height: The height or length (number of rows) of the image that contains the part. The
part length can be less than the image height requested by the user.
HasIntensity: Specifies if the intensity image is available. The intensity image is available if
Acquire Intensity is enabled in the sensor's web interface.
Each output is returned as decimal value.
Example
Go2GenTL_ParseData(Image, HeightMap, Intensity, frameCount,
timestamp, encoderPosition, encoderIndex, inputs, xOffset,
xResolution, yOffset, yResolution, zOffset, zResolution, width,
height, hasIntensity)
Go2GenTL_ Returns the resample mode.
ResampleMode
Parameters (Input)
AcqHandle: Acquisition handle created by open_framegrabber.
Parameters (Output)
ResampleMode:
No - Resample is disabled.
Yes - Resample is enabled.
When resampling is enabled, the GenTL driver resamples the height map so that the pixel
spacing is the same on the X and Y axis.
Example
Go2GenTL_ResampleMode (AcqHandle, ResampleMode)
To set the resample mode, you must directly modify Go2GenTL.xml, which is
in the same directory as the sensor GenTL driver (Go2GenTL.cti).
Parameters (Output)
ConfigFile: The name of the job file. The file name includes the extension .job.
Example
Go2GenTL_ConfigFileName (AcqHandle, ConfigFile)
Go2GenTL_ Sets the sensor live configuration.
SetConfigFileNa
Parameters (Input)
me
AcqHandle: Acquisition handle created by open_framegrabber.
ConfigFile: The name of the job file. The file name should include the extension .job.
Example
Go2GenTL_SetConfigFileName (AcqHandle, 'test2.cfg')
Go2GenTL_ Returns the current encoder value. When this function is called, the GenTL driver retrieves the
Encoder latest encoder value from the sensor. The value is returned as a two-element tuple. The first
element is the least significant 32-bit value, and the second element is the most significant 32-bit
value.
Parameters (Input)
AcqHandle: Acquisition handle created by open_framegrabber.
Parameters (Output)
EncoderValue: The current encoder value.
Example
Go2GenTL_Encoder(AcqHandle, EncoderValue)
Go2GenTL_ Returns the size of the image returned by the GenTL driver.
ImageSize
Parameters (Input)
AcqHandle: Acquisition handle created by open_framegrabber.
Parameters (Output)
Width: The width of the image.
Height: The height of the image.
Example
Go2GenTL_ImageSize(AcqHandle, Width, Height)
To set the image size, you must directly modify Go2GenTL.xml, which is in
the same directory as the sensor GenTL driver (Go2GenTL.cti).
Go2GenTL_ Returns the real-world coordinates (X, Y, Z) of the part given the row and column position in the
CoordinateXYZ height map.
The values of the offset and resolution input parameters can be retrieved using Go2GenTL_
ParseData.
Parameters (Input)
HeightMap : The height map image.
Row: The row in the height map.
Column: The column in the height map.
xOffset: The X offset in millimeters.
Parameters (Output)
coordinateXYZ: The real-world coordinates.
Go2GenTL_ Returns the current exposure.
Exposure
Parameters (Input)
AcqHandle: Acquisition handle created by open_framegrabber.
Parameters (Output)
Exposure: The current exposure value (in µs). The value is returned as an integer.
Decimals are truncated.
Example
Go2GenTL_Exposure(AcqHandle, exposure)
Go2GenTL_ Sets the current exposure.
SetExposure
Parameters (Input)
AcqHandle: Acquisition handle created by open_framegrabber.
Exposure: The current exposure value (in µs), as an integer.
Example
Go2GenTL_SetExposure(AcqHandle, exposure)
set_ Generic Halcon function to set parameters on the scanner. Can be used to set scanner specific
framegrabber_ settings. For a complete list of settings that can be changed, see the SDK interface files. In the
param generic form:
set_framegrabber_param( AcqHandle, ‘Name’, ‘Value’)
Parameters (Input)
AcqHandle: Acquisition handle created by open_framegrabber.
Name: The name of the parameter to set on the scanner.
Value: The parameter value to set on the scanner.
Examples
To set the format of the image buffer to 16-bit packed:
set_framegrabber_param( AcqHandle, ‘PixelFormat’, ‘RGB16Packed’)
2. In the dialog that opens, in the Code Generation tab, set Acquisition Mode to Asynchronous Acquisition.
3. Under Acquisition, click Insert Code to generate the code that will open the acquisition device.
To handle cases when the grab_image function times out while waiting for data, add a
try-catch statement around the grab_image function code.
To configure a sensor:
1. In the web interface, go to the Output tab.
3. In the Data area of the panel, make sure a source for Surface data is checked under Surfaces.
By default, a source for Surface data is already selected.
4. (Optional) If you want to transfer intensity data, check a source for intensity data under Surface Intensities.
Element Description
2 Receiving timeout The number of seconds the transfer tool will wait to receive data from the sensor before
timing out.
3 MountainsMap After the data transfers from the sensor to the tool, you can edit it directly in the transfer
component tool.
4 Status bar Indicates whether the tool is connected to a sensor, and so on.
5 Show/hide log file Toggles display of the log file. Useful for diagnosing connection and scan issues.
6 Hide command bar Toggles display of the command bar at the top of the tool.
7 Use accelerator Attempts to accelerate the sensor chosen in the sensor selector drop-down.
In order for the tool to accelerate the sensor, the sensor's firmware must
match the Gocator SDK version indicated on the tool's title bar. If these
versions do not match, the tool will not be able to accelerate the sensor.
In this case, you can accelerate the sensor using the standalone
accelerator application or an SDK-based application.
8 Snapshot button Causes the connected sensor to take a snapshot. The data is then transferred to the tool. If
the tool does not receive the data before the delay specified in Receiving timeout, the
transfer fails.
GoSDK
The Gocator Software Development Kit (GoSDK) includes open-source software libraries and
documentation that can be used to programmatically access and control Gocator sensors. To get the
latest version of the Gocator SDK package, go to http://lmi3d.com/support, choose your product from
the Product Downloads section, and download it from the Download Center.
For information on the ports the SDK uses (for example, in order to ensure ports are not blocked over
your network), see Required Ports on page 56.
If you switch jobs or make changes to a job using the SDK or a protocol (from a PLC), the switch
or changes are not automatically displayed in the web interface: you must refresh the browser
to see these.
You can download the Gocator SDK from within the Web interface.
Applications compiled using SDK version 4.x are compatible with sensors running firware 5.x.
Applications compiled using SDK version 3.x are not compatible with sensors running firmware 4.x. In
this case, you must rewrite the application with the SDK version corresponding to the sensor firmware in
use.
14400-x.x.x.xx_SOFTWARE_GO_SDK\GO_SDK\doc\GoSdk\Gocator_2x00\GoSdk.html
Examples
Examples showing how to perform various operations are provided, each one targeting a specific area.
For Visual Studio, the examples can be found in solution files specific to different versions of Visual
Studio. For example, GoSdk-2017.sln is for use with Visual Studio 2017. A make file for Linux systems is
also provided.
To compile the examples in Visual Studio, you may be need to retarget the solution to the
installed Windows SDK version. You can do this through the Retarget solution option in the
solution context menu.
To run the GoSDK examples, make sure the required DLLs are copied beside the executable. In most
cases only GoSDK.dll and kApi.dll are required, but with .NET and the accelerator additional DLLs are
needed. Please refer to the SDK samples to see which DLLs are required.
Header Files
Header files are referenced with GoSdk as the source directory, for example: #include
<GoSdk/GoSdk.h>. The SDK header files also reference files from the kApi directory.
Functional Hierarchy of Classes
This section describes the functional hierarchy of the classes in the Gocator SDK ("GoSDK"). In the
following diagram, classes higher in the hierarchy often provide resources for classes lower in the
hierarchy, and for this reason should be instantiated earlier in a client application.
Refer to the How To Use The Open Source SDK To Fully Control A Gocator Multi-sensor System how-to guide
in http://lmi3d.com/sites/default/files/APPNOTE_Gocator_4.x_Multi_Sensor_Guide.zip for details on
how to control and operate a multi-sensor system using the SDK.
All objects that are explicitly created by the user or passed via callbacks should be destroyed by
using the GoDestroy function.
GoSensor
GoSensor represents a physical sensor. If the physical sensor is the Main sensor in a dual-sensor setup, it
can be used to configure settings that are common to both sensors.
GoSetup
The GoSetup class represents a device's configuration. The class provides functions to get or set all of the
settings available in the web interface.
GoSetup is included inside GoSensor. It encapsulates scanning parameters, such as exposure, resolution,
spacing interval, etc. For parameters that are independently controlled for Main and Buddy sensors,
functions accept a role parameter.
GoLayout
The GoLayout class represents layout-related sensor configuration.
GoTransform
The GoTransform class represents a sensor transformation and provides functions to get and set
transformation information, as well as encoder-related information.
GoOutput
The GoOutput class represents output configuration and provides functions to get the specific types of
output (Analog, Digital, Ethernet, and Serial). Classes corresponding to the specific types of output
(GoAnalog, GoDigital, GoEthernet, and GoSerial) are available to configure these outputs.
Data Types
The following sections describe the types used by the SDK and the kApi library.
Value Types
GoSDK is built on a set of basic data structures, utilities, and functions, which are contained in the kApi
library.
The following basic value types are used by the kApi library.
Output Types
The following output types are available in the SDK.
GoBoundingBoxMatchMsg Represents a message containing bounding box based part matching results.
GoDataMsg Represents a base message sourced from the data channel. See GoDataSet Type
below for more information.
Refer to the GoSdkSamples sample code for examples of acquiring data using these data types.
See Setup and Locations on page 814 for more information on the code samples.
GoDataSet Type
Data are passed to the data handler in a GoDataSet object. The GoDataSet object is a container that can
contain any type of data, including scan data (profiles, sections, or surfaces), measurements, and results
from various operations. Data inside the GoDataSet object are represented as messages.
The following illustrates the content of a GoDataSet object of a profile mode setup with two
measurements. The content when using a surface mode setup is identical, except that a GoSurfaceMsg is
sent instead of a GoProfileMsg.
All objects that are explicitly created by the user or passed via callbacks should be destroyed by
using the GoDestroy function.
Measurement Decisions
Decision Description
1 The measurement value is between the maximum and minimum decision values. This
is a pass decision.
0 The measurement value is outside the maximum and minimum. This is a fail decision.
-1 The measurement is invalid (for example, the target is not within range). Provides the
reason for the failure.
-2 The tool containing the measurement is anchored and has received invalid
measurement data from one of its anchors. Provides the reason for the failure.
Refer to the SetupMeasurement example for details on how to add and configure tools and
measurements. Refer to the ReceiveMeasurement example for details on how to receive measurement
decisions and values.
You should check a decision against <=0 for failure or invalid measurement.
Operation Workflow
Applications created using the SDK typically use the following programming sequence
Sensors must be connected before the system can enable the data channel.
All GoSDK data functions are named Go<Object>_<Function>, for example, GoSensor_Connect.
For property access functions, the convention is Go<Object>_<Property Name> for reading the
property and Go<Object>_Set<Property Name> for writing it, for example, GoMeasurement_
DecisionMax and GoMeasurement_SetDecisionMax, respectively.
Refer to the Discover example for details on iterating through all sensors. Refer to other examples for
details on how to get a sensor handle directly from IP address.
Connect Sensors
Sensors are connected by calling GoSensor_Connect. You must first get the sensor object by using
GoSystem_SensorAt, GoSystem_FindSensorById, or GoSystem_FindSensorByIpAddress.
Configure Sensors
Some configuration is performed using the GoSensor object, such as managing jobs, uploading and
downloading files, scheduling outputs, setting alignment reference, etc. Most configuration is however
performed through the GoSetup object, for example, setting scan mode, exposure, exposure mode,
active area, speed, alignment, filtering, subsampling, etc. Surface generation is configured through the
GoSurfaceGeneration object and part detection settings are configured through the GoPartDetection
object.
See Functional Hierarchy of Classes on page 814 for information on the different objects used for
configuring a sensor. Sensors must be connected before they can be configured.
Refer to the Configure example for details on how to change settings and to switch, save, or load jobs.
Refer to the BackupRestore example for details on how to back up and restore settings.
Perform Operations
Operations are started by calling GoSystem_Start, GoSystem_StartAlignment, and GoSystem_
StartExposureAutoSet.
Refer to the StationaryAlignment and MovingAlignment examples for details on how to perform
alignment operations. Refer to the ReceiveRange, ReceiveProfile, and ReceiveWholePart examples for
details on how to acquire data.
#include <GoSdk/GoSdk.h>
void main()
{
kIpAddress ipAddress;
Power loss during flash memory write operation will also cause sensors to enter rescue mode.
GoSensor_ChangePassword Changes the password associated with the specified user account.
System created using the SDK should be designed in a way that parameters are set up to be appropriate
for various application scenarios. Parameter changes not listed above will not invoke flash memory write
operations when the changes are not saved to a file using the GoSensor_CopyFile function. Fixed
alignment should be used as a means to attach previously conducted alignment results to a job file,
eliminating the need to perform a new alignment.
The Gocator Development Kit (GDK) is a framework for developing and testing custom Gocator tools
containing your own algorithms, and then deploying them to Gocator sensors.
Custom tools created with the GDK act much like native Gocator data output tools (providing
measurements, geometric features, data and generic outputs) with support for multiple input
parameters), running at native speeds and taking advantage of features such as anchoring. The
GDK supports all data types, and tools created with the GDK use the same data visualization as native
tools.
Benefits
When you use the GDK to create custom measurement tools, you have complete control over how and
where your custom measurement tools can be used, which protects your intellectual property.
You can also easily troubleshoot and modify your tools on-site, letting you respond quickly to your
customers' urgent issues.
Supported Sensors
The GDK is available for free for the following Gocator sensors:
Typical Workflow
The following is the typical workflow for creating and deploying custom measurement tools:
l Develop and build tools using the GDK project files and libraries in Microsoft Visual Studio, targeting
Win32.
You can access full installation and setup instructions, as well as the complete class reference
documentation, by double-clicking the Guide shortcut under the root directory.
Required Tools
The GDK requires Microsoft Visual Studio 2017, as well as various other tools provided in the
GDK Prerequisites package (14525_x.x.x.x_SOFTWARE_GDK_Prerequisites.zip). This package is
available in LMI's Downloads Center (see above for download location).
l Win32/x64 for debugging code and emulating a sensor to test tools (on a PC)
l Arm7 for building for Gocator 2300C and 2400 series sensors
l C64x for Gocator 1300, 2300A, 2300B, 3210, and 3506 series sensors
The Win32 target supports Debug and Release builds. The Arm7 and C64x targets (sensors) only the
support Release builds.
Tool Registration
For a tool to be available to a user in the sensor web interface, you must add it to the project assembly in
Asm.c.
#include <GdkSampleApp/Asm.h>
#include <GdkSampleApp/TestProfileSelect.h>
#include <GdkSampleApp/TestSurfaceSelect.h>
#include <GdkSampleApp/TestSurfaceConfiguration.h>
#include <GdkSampleApp/TestSurfaceGraphics.h>
#include <Gdk/GdkLib.h>
#include <GoSensor/Version.h>
#include <GoSensorAppLib/GsaDef.h>
#include <GoSensorAppLib/GsaAsm.h>
You can add multiple tools in a GDK project. As seen above, TestProfileSelect,
TestSurfaceSelect, TestSurfaceConfiguration, etc. will be available for users from the drop-
down menu in the Tools panel in sensor's web interface.
kCheck(GdkToolInfo_SetTypeName(toolInfo, TEST_PROFILE_SELECT_TOOL_NAME));
kCheck(GdkToolInfo_SetLabel(toolInfo, TEST_PROFILE_SELECT_TOOL_LABEL));
kCheck(GdkToolInfo_SetSourceType(toolInfo, GDK_DATA_TYPE_UNIFORM_PROFILE));
...
The function <Tool Name>_VDescribe describes the tool and its basic configuration. This function is
called during sensor start-up. For more information on entry functions, see Entry Functions below.
Make sure the VDescribe function for each tool is properly formed. Significant issues with this
function (for example, overwriting memory) could prevent the sensor from starting.
You should use the emulator to debug tools before deploying tools to sensors.
Entry Functions
The following table describes the main entry functions.
Function Description
VDescribe Defines the tool's name, data types, acceptable source options, configuration
parameters, and at least one measurement.
VStart Called when the sensor starts running (that is, the user clicks the Run button). The
function gets parameters from GtTool. You typically allocate memory in this function.
VProcess Called every time data is received while the sensor is running.
The TestSurfaceConfiguration example shows how to create and modify parameters based on
other user settings.
For full descriptions of these functions, see the GDK class reference documentation (see Installation and
Class Reference on page 824 for information on installing the documentation).
Parameter Configurations
Each tool has two levels of parameters: tool parameters and measurement parameters.
A tool can contain multiple measurements. In the image above, the Groove tool contains four
measurements: X, Z, Width, and Depth. Each tool has one set of tool parameters and each measurement
in a tool has one set of measurement parameters.
The following table lists the functions that provide advanced or interactive control for setting up tool
and measurement parameters:
Function Description
VNewToolConfig Advanced method for setting default values of tool parameters based on the current
sensor configuration (for example, active area). Called when a new tool is added in the
interface.
VNewMeasurementConfig Advanced method for setting default values of measurement parameters based on the
current sensor configurations (for example, active area). Called when measurements in
a tool is are added in the interface.
VUpdateConfig Advanced method for updating the configuration based on parameters set by users.
For full descriptions of these functions, see the GDK class reference documentation (see Installation and
Class Reference on page 824 for information on installing the documentation).
Graphics Visualization
The GdkGraphic function supports points and lines.
Point graphics
To create graphics:
1. Use GdkGraphic_Construct to create a graphic object.
3. Add the points and lines to the graphic object using GdkGraphic_AddPointSet and GdkGraphic_
AddLineSet.
kTest(GdkGraphic_Construct(&graphic, kObject_Alloc(tool)));
kTest(GdkGraphic_AddPointSet(graphic, pointSet));
The GDK example TestSurfaceGraphics shows how to use the graphics functions.
2. In the output directory, rename the DLL with the same name as your project to GdkApp.dll.
For example, if your project is called MyGDKTools, the resulting DLL should be called MyGDKTools.dll. You
rename this DLL to GdkApp.dll.
The output directories are as follows:
Release: win32
Debug: win32d
VDescribe however is called when the DLL loads, before the debugger can attach to the
kFramework.exe process. To debug VDescribe, we recommend testing the function calls by putting
them in VInit.
For information on building targets for testing in the emulator, see the GDK class reference
documentation.
Tips
The following sections provide useful information for creating custom measurement tools.
By default, if declared parameters are missing from the configuration, a job file or a recording will fail to
load.
There are two ways to provide backward compatibility with older parameter sets.
Configuration Versioning
Over the lifetime of a tool, you may need to make changes to its interface (for example, changing or
removing parameters). The user-defined aspects of a tool interface—its parameters and
By default, a tool has just one version (GdkToolInfo_FirstVersion), but more versions may be
added using GdkToolInfo_AddVersion. Whenever the interface of a tool has changed, a new version
can be registered so that the new interface can be correctly parsed by the framework.
When the configuration of a tool instance is saved, the version used at the time is also saved. This saved
version is used by the framework to parse the configuration. If a version is not defined by the firmware
implementation, then that tool instance will not be active.
During run-time, you can query the version of the configuration of a tool instance by using
GdkToolCfg_Version. You can then interpret the parameters depending on the version the
configuration is saved in.
kCheck(GdkToolInfo_SetSourceType(info, GDK_DATA_TYPE_UNIFORM_PROFILE));
kCheck(GdkToolInfo_AddSourceOption(info, GDK_DATA_SOURCE_TOP));
kCheck(GdkExampleTool_DescribeV0(info));
kCheck(GdkExampleTool_DescribeV1(info));
return kOK;
}
return kOK;
}
// Auto-version
return kOK;
}
Version
You can define the version number of your tools in Asm.x.h.
The GdkToolInput_Find and GdkInputItem_Info functions are used to extract the item and info
objects. These objects can then be used to retrieve the input data and information (for example, offset
and resolution) associated to the input. The following are some examples:
offsetRegion = obj->region;
offsetRegion.x += anchor->x;
offsetRegion.z += anchor->z;
In the code above, we first retrieve the tool’s region settings (before anchoring is applied), and then
adjust the region based on the results from the anchored source in VProcess. If the anchored source
fails, the tools will not be invoked.
For more information on anchoring, see Measurement Anchoring in the Gocator user manual.
Part Matching
When part matching is enabled, the tool receives translated and corrected surface data. If part matching
fails for the current scan (for example, the quality score is too low), the tools will not be invoked.
For more information on part matching, see Part Matching in the user manual.
For example, to read and write a file to a sensor's storage, you could use the following:
Print Output
In the emulator, you can send output to Visual Studio or to programs such as DebugView by using the
OutputDebugString function.
kVarArgList argList;
kVarArgList_Start_(argList, format);
{
status = kStrPrintvf(debugLine, 256, format, argList);
}
kVarArgList_End_(argList);
OutputDebugStringA(debugLine);
return status;
}
OutputDebugString is NOT supported on sensor targets. Use #ifdef to comment out the code
when compiling against sensor targets.
The following sections describe some of the tools provided with a Gocator sensor, as well as the
CSV format that a sensor can export. For information on the integrations available with a sensor, see
Integrations on page 647.
l Sensor Discovery Tool: Used to find sensors on a network. See Sensor Discovery Tool below.
l CSV Converter Tool: Used to convert CSV data exported from a sensor to several formats. See CSV
Converter Tool on the next page.
After downloading the utility package [14405-x.x.x.x_SOFTWARE_GO_Utilities.zip], unzip the file and run
the Sensor Discovery Tool [Tools > Discovery > kDiscovery.exe].
Any sensors that are discovered on the network will be displayed in the Devices list.
The Sensor Discovery tool uses UDP broadcast messages to reach sensors on different subnets.
This enables the Sensor Discovery tool to locate and re-configure sensors even when the sensor IP
address or subnet configuration is unknown.
For information on the CSV file format that the sensor exports, see the next section.
To get the utility package (), go to http://lmi3d.com/support, choose your product from the Product
Downloads section, and download it from the Download Center.
After downloading the tool package, unzip the file and run the Gocator CSV Converter tool [Tools
> CSV Converter > kCsvConverter.exe].
Output formats
Format Description
16-bit BMP Heightmap with 16bit height values in a 5-5-5 RGB image.
Not intended for visualization.
STL ASCII Mesh in standard STL text format (can become very large).
With some formats, one or more of the following options are available:
Output options
Option Description
Keep Aspect Ratio Resamples the X and Y axes to obtain the proper aspect
ratio.
The GenTL format is a 48-bit RGB or grey scale PNG. Height map, intensity and stamp
information are stored as defined in the GenTL Driver section (GenICam GenTL Driver on
page 793). You can load the exported data into image processing software to provide simulation
data for developing applications using the GenTL driver.
2. (Optional) If intensity information is required, check the Intensity box and select the intensity bitmap.
Intensity information is only used when converting to ASCII or GenTL format. If intensity is not selected,
the ASCII format will only contain the point coordinates (XYZ).
3. If a dual-sensor system was used, choose the source sensor next to Image.
6. Click Convert.
The converter converts the input files.
The converted file will be in the same directory as the input file. It will also have the same name as the
input file but with a different file extension. The converted file name is displayed in the Output File
field.
An exported CSV file contains a series of "sections." Each section begins with a row containing the name
of the section, and ends with a row containing the string "End." An empty line separates each section.
Each section usually contains one or more subsections. Each subsection has a header row containing a
list of field names, followed by one or more rows of data. There is usually no empty line between the
subsections.
Example:
Info
CSV Version,Sensor Count,Trigger Mode,...
2,1,0,32000.00000,...
End
DeviceInfo
ID,Model,Version,...
13434,311320-2M-01,4.8.2.29,...
End
Ranges
...
End
Usually all available data in the recording buffer is exported. The exceptions are Surface and
SurfacePointCloud. For these sections, only the currently selected frame is exported.
Info
This section contains basic system information. It has one header row and one value row. The fields are
described below:
Trigger Delay Output delay (µs or mm, depending on delay domain defined above).
Operation Mode The scan mode.
XResolution System X resolution (mm).
YResolution System Y resolution (mm).
ZResolution System Z resolution (mm).
Yspeed Y Speed (mm/s).
Layout Sensor orientation:
0 – Normal (single-sensor system) / Wide (dual-sensor system)
1 – Opposite
2 – Reverse
3 – Grid
DeviceInfo
This section contains information about each device in the system. There is one header row, and one
value row per device.
DeviceInfo Fields
Field Description
RecordingFilter
This section lists the filters used during recording. Unlike the other sections, it contains multiple sub-
sections within, separated by spaces (but not the “End” keyword).
Example:
RecordingFilter
Section1 Param 1, Section1 Param2
value, value
Section2 Param 1
value
Section3 Param1, Section3 Param2
value
End
Each section will be described by a separate table below. They appear in the same order as documented.
RecordingFilter Fields
Field Description
Type Measurement
Enabled Whether or not is enabled: Yes/No
Result Accepted result type: Pass/Fail/Invalid/Valid
Selection ID First measurement ID
Ranges
This section describes single-point range data. It has two sub-sections: attributes and data.
The data section has one or more rows of data per frame (for example, range and intensity).
Profile
This section describes uniform (or resampled) profile data, which is produced when the sensor is in
The data section has one or more rows of data per frame (for example, range and intensity).
RawProfile
This section describes point cloud profile data (or unresampled / raw data), which is produced when the
sensor is in Profile mode and uniform spacing is disabled. It has two sub-sections: attributes and data.
The data section has one or more rows of data per frame (for example, range and intensity).
Part
This section describes uniform (or resampled) surface data, which is produced when the sensor is in
Surface mode and uniform spacing is enabled.
Only the data for the frame currently selected in the UI is exported when you export part data to
a CSV file.
The data section contains the data of a single surface scan. Each data row corresponds to one Y position.
The first row contains the X values, and the first column contains the Y values. The region inside contains
the range values (mm) for the corresponding row and column.
Review the guidance in this chapter if you are experiencing difficulty with a sensor system.
If the problem that you are experiencing is not described in this section, see Return Policy on page 924.
Mechanical/Environmental
The sensor is warm.
l It is normal for a sensor to be warm when powered on. A sensor is typically 15° C warmer than the ambient
temperature.
Connection
When attempting to connect to the sensor with a web browser, the sensor is not found (page does not
load).
l Verify that the sensor is powered on and connected to the client computer network. The Power Indicator LED
should illuminate when the sensor is powered.
l Check that the client computer's network settings are properly configured.
l Use the Sensor Recovery tool to verify that the sensor has the correct network settings. See Sensor Discovery
Tool on page 836 for more information.
l Use the Sensor Recovery tool. See Sensor Discovery Tool on page 836 for steps to reset the password.
The sensor emits laser light, but the Range Indicator LED does not illuminate and/or points are not
displayed in the Data Viewer.
l Verify that the measurement target is within the sensor's field of view and measurement range. See Spe-
cifications on page 847 to review the measurement specifications for your sensor model.
l Check that the exposure time is set to a reasonable level. See Exposure on page 134 for more information on
configuring exposure time.
Performance
The sensor CPU level is near 100%.
l Consider reducing the speed. If you are using a time or encoder trigger source, see Triggers on page 123 for
information on reducing the speed. If you are using an external input or software trigger, consider reducing
the rate at which you apply triggers.
l Consider reducing the resolution.
See Spacing on page 138 for more information on configuring resolution.
l Review the measurements that you have programmed and eliminate any unnecessary measurements.
The following sections describe the specifications of Gocator sensors and connectors, as well as Master
hubs.
Sensors
The following sections provide the specifications of Gocator sensors.
The following models are not typically industry-specific and can be used for various applications.
Data Points / 640 / 1280 640 / 1280 640 / 1280 640 / 1280 640 /1280 640 /1280 640 / 1280
Profile
Resolution Z (mm) 0.0018 - 0.0030 0.006 - 0.014 0.013 - 0.037 0.019 - 0.060 0.055 - 0.200 0.175 - 0.925 0.092 - 0.488
Resolution X (mm)
(Profile Data
Interval)
2100 series 0.028 - 0.042 0.088 - 0.150 0.19 - 0.34 0.3 - 0.6 0.55 - 1.10 0.510 - 1.580 0.75 - 2.20
2300 series 0.014 - 0.021 0.044 - 0.075 0.095 - 0.170 0.150 - 0.300 0.275 - 0.550 0.255 - 0.790 0.375 - 1.100
Field of View (FOV) 18 - 26 47 - 85 96 - 194 158 - 365 308 - 687 324 - 1010 390 - 1260
(mm)
Input Voltage +24 to +48 VDC (13 W); Ripple +/- 10%
(Power)
The following diagram illustrates some of the terms used in the table above.
Optical models, laser classes, and packages can be customized. Contact LMI for more details.
Gocator 2300 series sensors provide 1280 data points per profile. Gocator 2100 series sensors provide
640 data points per profile; additionally, Gocator 2100 series sensors do not support the tracking
window capability (for more information, see Tracking Window on page 131).
Specifications stated are based on standard laser classes. Linearity Z, Resolution Z, and Repeatability Z
may vary for other laser classes.
Linearity Z is the worst case difference in average height measured, compared to the actual position over
the measurement range.
Resolution Z is the maximum variability of height measurements across multiple frames, with 95%
confidence.
Resolution X is the distance between data points along the laser line.
Repeatability Z is measured with a flat target at the middle of the measurement range. It is the 95%
confidence variation of the average height over 4096 frames. Height values are averaged over the full
FOV.
Mechanical dimensions, CD/FOV/MR, and the envelope for each sensor model are illustrated on the
following pages.
In the following drawings, the physical height dimensions of measurement ranges are reversed
compared to the logical height values returned by sensors. For an illustration of the orientation
of coordinate systems in relation to physical sensors, see the sections below for each sensor
model.
Envelope
Dimensions
Envelope
Envelope
Class 3B
Class 2 & 3R
Clearance 19 60 75 183
Distance (CD) (mm)
Measurement 6 25 80 210
Range (MR) (mm)
2M (blue, 405 nm) 2M (blue, 405 nm 3R, 3B (red, 660 nm) 2, 3B (red, 660 nm)
The following diagram illustrates some of the terms used in the table above.
Optical models, laser classes, and packages can be customized. Contact LMI for more details.
All specification measurements are performed on LMI’s standard calibration target (a diffuse, painted
white surface).
Linearity Z is the worst case difference in average height measured, compared to the actual position over
the measurement range.
Resolution Z is the maximum variability of height measurements across multiple frames, with 95%
confidence.
Resolution X is the distance between data points along the laser line.
Repeatability Z is measured with a flat target at the middle of the measurement range. It is the 95%
confidence variation of the average height over 4096 frames. Height values are averaged over the full
FOV.
Scan Rate 200 Hz, up to 5 kHz. (Gocator 2400 series sensors provide up to 2x scan rate for
equivalent window size as 2300 series sensors.)
Interface Gigabit Ethernet
Inputs Differential Encoder, Laser Safety Enable, Trigger
Outputs 2x Digital output, RS-485 Serial (115 kBaud), 1x Analog Output (4 - 20 mA)
Housing Gasketed aluminum enclosure, IP67
Input Voltage (Power) +24 to +48 VDC (9 W); Ripple +/- 10%
Operating Temp. 0 to 50° C
Storage Temp. -30 to 70° C
Mechanical dimensions, CD/FOV/MR, and the envelope for each sensor model are illustrated on the
following pages.
Envelope
Envelope
Measurement 6 6 25
Range (MR) (mm)
The following diagram illustrates some of the terms used in the table above.
Unlike other Gocator line profile sensors, the clearance distance for Gocator 2500 sensors is
measured from the lowest point of the sensor's housing, not the laser window.
Specifications stated are based on standard laser classes. Linearity Z and Repeatability Z may vary for
other laser classes.
Linearity Z is the worst case difference in average height measured, compared to the actual position over
the measurement range.
Resolution X is the distance between data points along the laser line.
Repeatability Z is measured with a flat target at the middle of the measurement range. It is the 95%
confidence variation of the average height over 4096 frames. Height values are averaged over the full
FOV.
Scan Rate 2.4 kHz (2510 full field of view) / 1.6 kHz (2520 full field of view) to 10 kHz
Mechanical dimensions, CD/FOV/MR, and the envelope for each sensor model are illustrated on the
following pages.
Envelope
Estimated Performance
This section provides estimated measurement tool performance.
PC
l Intel i7 5960X
l 16 GB RAM
l Windows 8.1 Pro
Graphics Card
MODEL 2880
Linearity Z 0.04
(+/- % of MR)
Clearance 350
Distance (CD) (mm)
Measurement 800
Range (MR) (mm)
Optical models, laser classes, and packages can be customized. Contact LMI for more details.
Specifications stated are based on standard laser classes. Resolution Z and Linearity Z may vary for other
laser classes.
Mechanical dimensions, CD/FOV/MR, and the envelope for each sensor model are illustrated on the
following pages.
This connector is rated IP67 only when a cable is connected or when a protective cap is used.
This section defines the electrical specifications for Power/LAN Connector pins, organized by function.
Power
Apply positive voltage to DC_24-48V.
Power requirements
Function Pins Min Max
DC_24-48V A 24 V 48 V
GND_24-48VDC L 0V 0V
Safety_in+ J 24 V 48 V
Safety_in- G 0V 0V
Confirm the wiring of Safety_in- before starting the sensor. Wiring DC_24-48V into Safety_in- may
damage the sensor.
This connector is rated IP67 only when a cable is connected or when a protective cap is used.
This section defines the electrical specifications for I/O connector pins, organized by function.
Grounding Shield
The grounding shield should be mounted to the earth ground.
Digital outputs cannot be used when taking scans using the Snapshot button, which takes a
single scan and is typically used to test measurement tool settings. Digital outputs can only be
used when a sensor is running, taking a continuous series of scans.
Out_1 (Collector – Pin N and Emitter – Pin O) and Out_2 (Collector – Pin S and Emitter – Pin T) are
independent and therefore V+ and GND are not required to be the same.
Out_1 N, O 40 mA 70 V 20 µs
Out_2 S, T 40 mA 70 V 20 µs
Inverting Outputs
To invert an output, connect a resistor between ground and Out_1- or Out_2- and connect Out_1+ or
Out_2+ to the supply voltage. Take the output at Out_1- or Out_2-. For resistor selection, see above.
Digital Input
Every sensor has a single optically isolated input. To use this input without an external resistor, supply
3.3 - 24 V to the positive pin and GND to the negative.
If the supplied voltage is greater than 24 V, connect an external resistor in series to the positive. The
resistor value should be R = [(Vin-1.2V)/10mA]-680.
Active Low
To assert the signal, the digital input voltage should be set to draw a current of 3 mA to 40 mA from the
positive pin. The current that passes through the positive pin is I = (Vin – 1.2 – Vdata) / 680. To reduce
noise sensitivity, we recommend leaving a 20% margin for current variation (i.e., uses a digital input
voltage that draws 4mA to 25mA).
Function Pins Min Voltage Max Voltage Min Current Max Current Min Pulse Width
Trigger_in D, H 3.3 V 24 V 3 mA 40 mA 20 µs
Encoder Input
Encoder input is provided by an external encoder and consists of three RS-485 signals. These signals are
connected to Encoder_A, Encoder_B, and Encoder_Z.
Gocator only supports differential RS485 signalling. Both + and - signals must be connected.
Encoders are normally specified in pulses per revolution, where each pulse is made up of the
four quadrature signals (A+ / A- / B+ / B-). Because the sensor reads each of the four quadrature
signals, you should choose an encoder accordingly, given the resolution required for your
application.
Serial Output
Serial RS-485 output is connected to Serial_out as shown below.
Function Pins
Serial_out B, C
Function Pins
Serial_out (data) B, C
Serial_out2 (clock) E, G
Analog_out P, F 4 – 20 mA
To configure for voltage output, connect a 500 Ohm ¼ Watt resistor between Analog_out+ and Analog_
out- and measure the voltage across the resistor. To reduce the noise in the output, we recommend
using an RC filter as shown below.
For information on maximum external input trigger rates, see Maximum Input Trigger Rate on page 129.
Master 100
The Master 100 accepts connections for power, safety, and encoder, and provides digital output.
Connect the Master Power port to the Gocator's Power/LAN connector using the Gocator Power/LAN to
Master cordset. Connect power RJ45 end of the cordset to the Master Power port. The Ethernet RJ45
end of the cordset can be connected directly to the Ethernet switch, or connect to the Master Ethernet
port. If the Master Ethernet port is used, connect the Master Host port to the Ethernet switch with a
CAT5e Ethernet cable.
To use encoder and digital output, wire the Master's Gocator Sensor I/O port to the Gocator IO
connector using the Gocator I/O cordset.
Encoder_A- 2 Brown/Black
Encoder_Z- 4 Green/Black
Trigger_in+ 5 Grey
Trigger_in- 6 Pink
Out_1- 7 Blue
Out_1+ 8 Red
Encoder_B+ 11 Black
Encoder_B- 12 Violet
The rest of the wires in the I/O cordset are not used.
Encoder_Z+ 3
Encoder_Z- 4
Encoder_A+ 5
Encoder_A- 6
Encoder_B+ 7
Encoder_B- 8
Encoder_GND 9
Encoder_5V 10
The Phoenix connectors on Master 400/800/1200/2400 are not compatible with the connectors
on Master 810/2410. For this reason, if you are switching models in your network, you must
rewire the connections to the Master.
+48VDC 1
+48VDC 2
GND (24-48VDC) 3
GND (24-48VDC) 4
Safety Control+ 5
Safety Control– 6
The power supply must be isolated from AC ground. This means that AC ground and DC ground
are not connected.
The Safety Control requires a voltage differential of 24 VDC to 48 VDC across the pin to enable the
laser.
Input 1 1
Input 1 GND 2
Reserved 3
Reserved 4
Reserved 5
Reserved 6
Reserved 7
Reserved 8
Reserved 9
Reserved 10
Reserved 11
Reserved 12
Reserved 13
Reserved 14
Reserved 15
Reserved 16
The Input connector does not need to be wired up for proper operation.
Encoder_A+ 1
Encoder_A- 2
Encoder_B+ 3
Encoder_B- 4
Encoder_Z+ 5
Encoder_Z- 6
GND 7
+5VDC 8
The power supply must be isolated from AC ground. This means that AC ground and DC ground
are not connected.
The Power Draw specification is based on a Master with no sensors attached. Every sensor has
its own power requirements that need to be considered when calculating total system power
requirements..
Total Power Master 810 / 2410 input power + (sensor input power x number of sensors)
Capacity Master 810: up to 8 sensors
10-pin Phoenix
Master 2410: 0.9
Notes
3. Supports open collector, pull-up resistor, line driver, push-pull, and TTL.
Master 810 and 2410 can be mounted to DIN rails using the provided adapters (for more information,
see Installing DIN Rail Clips: Master 810 or 2410 on page 42). The units are also provided with removable
adapters for 1U rack mounting; the mounting holes for this option are compatible with older Master
models (400/800/1200/2400).
The Phoenix connectors on Master 400/800/1200/2400 are not compatible with the connectors
on Master 810/2410. For this reason, if you are switching models in your network, you must
rewire the connections to the Master.
Master 2410 can currently be used with encoders with a maximum quadrature frequency of 300 kHz.
Power In+ 1
Power In+ 2
Power In- 3
Power In- 4
Safety Control+ 5
Safety Control– 6
The power supply must be isolated from AC ground. This means that AC ground and DC ground
are not connected.
On earlier revisions of Master 810 and Master 2410, the inputs are labeled 0-3.
Input 1 Pin 1 1
Input 1 Pin 2 2
Reserved 3
Reserved 4
Reserved 5
Reserved 6
Reserved 7
Reserved 8
The Input connector does not need to be wired up for proper operation.
Encoder_A_Pin_1 1
Encoder_A_Pin_2 2
Encoder_A_Pin_3 3
Encoder_B_Pin_1 4
Encoder_B_Pin_2 5
Encoder_B_Pin_3 6
Encoder_Z_Pin_1 7
Encoder_Z_Pin_2 8
Encoder_Z_Pin_3 9
The power supply must be isolated from AC ground. This means that AC ground and DC ground
are not connected.
24 VDC power supply is only supported if all connected sensors support an input voltage of 24
VDC.
The Power Draw specification is based on a Master with no sensors attached. Every sensor has
its own power requirements that need to be considered when calculating total system power
requirements..
The 5-volt encoder input supports up to 12 volts for compatibility with earlier Master network
controllers. However, we strongly recommend connecting 12-volt output encoders to the
appropriate 12-volt input to attain maximum tolerance.
Single-Ended 5 VDC
Single-Ended 12 VDC
Differential 12 VDC
Input
Master 810 and 2410 support the following types of input: Differential, Single-Ended High, and Single-
Ended Low.
Differential
Older revisions of Master 810 and 2410 network controllers use a different configuration for the DIN rail
clip holes.
For information on installing DIN rail clips, see Installing DIN Rail Clips: Master 810 or 2410 on page 42.
Older revisions of Master 810 and 2410 network controllers use a different configuration for the DIN rail
clip holes.
For information on installing DIN rail clips, see Installing DIN Rail Clips: Master 810 or 2410 on page 42.
The Phoenix connectors on Master 400/800/1200/2400 are not compatible with the connectors
on Master 810/2410. For this reason, if you are switching models in your network, you must
rewire the connections to the Master.
+48VDC 1
+48VDC 2
GND (24-48VDC) 3
GND (24-48VDC) 4
Safety Control+ 5
Safety Control– 6
The power supply must be isolated from AC ground. This means that AC ground and DC ground
are not connected.
The Safety Control requires a voltage differential of 24 VDC to 48 VDC across the pin to enable the
laser.
Input 1 1
Input 1 GND 2
Reserved 3
Reserved 4
Reserved 5
Reserved 6
Reserved 7
Reserved 8
Reserved 9
Reserved 10
Reserved 11
Reserved 12
The Input connector does not need to be wired up for proper operation.
Encoder_A+ 1
Encoder_A- 2
Encoder_B+ 3
Encoder_B- 4
Encoder_Z+ 5
Encoder_Z- 6
GND 7
+5VDC 8
The power supply must be isolated from AC ground. This means that AC ground and DC ground
are not connected.
The Power Draw specification is based on a Master with no sensors attached. Every sensor has
its own power requirements that need to be considered when calculating total system power
requirements..
Masters
Description Part Number
Cordsets
Description Part Number
Cordsets - 90-degree
Description Part Number
10m Power and Ethernet to Master cordset, 90-deg, 2x RJ45 ends 30877-10m
15m Power and Ethernet to Master cordset, 90-deg, 2x RJ45 ends 30877-15m
20m Power and Ethernet to Master cordset, 90-deg, 2x RJ45 ends 30877-20m
25m Power and Ethernet to Master cordset, 90-deg, 2x RJ45 ends 30877-25m
90-degree cordsets are not stocked. Lead times for delivery may be longer.
Custom cordset lengths and connector orientations are available upon request. Prices depend on length
and orientation requested. For standard cordsets, the maximum cable length is 60 m.
5m Power and Ethernet cordset, 90-deg, 1x open wire end, 1x RJ45 end 301171-5m
10m Power and Ethernet cordset, 90-deg, 1x open wire end, 1x RJ45 end 301171-10m
10m Power and Ethernet to Master cordset, 90-deg, 2x RJ45 ends 301173-10m
Calibration Disks
Return Policy
Before returning the product for repair (warranty or non-warranty) a Return Material Authorization
(RMA) number must be obtained from LMI. Please call LMI to obtain this RMA number.
Carefully package the sensor in its original shipping materials (or equivalent) and ship the sensor prepaid
to your designated LMI location. Please ensure that the RMA number is clearly written on the outside of
the package. Inside the return shipment, include the address you wish the shipment returned to, the
name, email and telephone number of a technical contact (should we need to discuss this repair), and
details of the nature of the malfunction. For non-warranty repairs, a purchase order for the repair
charges must accompany the returning sensor.
LMI Technologies Inc. is not responsible for damages to a sensor that are the result of improper
packaging or damage during transit by the courier.
Pico-C
Website:
http://code.google.com/p/picoc/
License:
http://www.opensource.org/licenses/bsd-license.php
Redistribution and use in source and binary forms, with or without modification, are permitted provided
that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and
the following disclaimer in the documentation and/or other materials provided with the distribution.
* Neither the name of the Zik Saleeba nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Website:
http://www.chiark.greenend.org.uk/~sgtatham/putty/licence.html
License:
Portions copyright Robert de Bath, Joris van Rantwijk, Delian Delchev, Andreas Schultz, Jeroen Massar,
Wez Furlong, Nicolas Barry, Justin Bradford, Ben Harris, Malcolm Smith, Ahmad Khalifa, Markus Kuhn,
Colin Watson, and CORE SDI S.A.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
associated documentation files (the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the
following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial
portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL SIMON TATHAM BE LIABLE FOR
ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
CodeMirror
Website:
http://codemirror.net
License:
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
associated documentation files (the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the
following conditions:
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANT ABILITY,FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE
OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
jQuery
Website:
http://jquery.com/
License:
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
associated documentation files (the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the
following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial
portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE
OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Three.js
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
associated documentation files (the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
The above copyright notice and this permission notice shall be included in all copies or substantial
portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE
OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
jQuery.CopyEvents
Website:
http://brandonaaron.net
License:
jQuery.history
License:
Modified by Lincoln Cooper to add Safari support and only call the callback once during initialization for
msie when no initial hash supplied. API rewrite by Lauris Bukis-Haberkorns
jQuery.mouseWheel
Website:
http://brandonaaron.net
License:
jQuery.scaling
Website:
http://eric.garside.name
License:
jQuery.scrollFollow
Website:
http://kitchen.net-perspective.com/
License:
Website:
sourceforge.net/projects/opener
License:
For help with a component or product, please submit an online support ticket using LMI's Help Desk at
http://support.lmi3d.com/newticket.php.
If you are unable to use the Help Desk or prefer to contact LMI by phone or email, use the contact
information below.
Response times for phone or email support requests are longer than requests submitted
through the Help Desk.
North America
Email [email protected]
Europe
Email [email protected]
LMI Technologies (Head Office) LMI Technologies GmbH LMI (Shanghai) Trading Co., Ltd.
Burnaby, Canada Berlin, Germany Shanghai, China
+1 604 636 1011 +49 (0)3328 9360 0 +86 21 5441 0711
LMI Technologies has sales offices and distributors worldwide. All contact information is listed at
lmi3D.com/contact/locations.