Novanta ATI Axia80, Manual

Page: 124 / 131

Manual, F/T Sensor, Ethernet Axia
Document #9620-05-C-Ethernet Axia-02
Pinnacle Park • 1031 Goodworth Drive • Apex, NC 27539 • Tel:+1 919.772.0115 • Fax:+1 919.772.8259 •
www.ati-ia.com
C-89
Symptom: The sensor is
connected but not
streaming data.
Cause:
The user’s devices are not compatible with real time Ethernet or Telnet
communication; refer to
Section 4—Connecting Through Ethernet or
Section 8.1—Setting Up a Console Interface Through Telnet .
Solution:
Verify devices are compatible; refer to
Section 4—
Connecting Through Ethernet or Section 8.1—Setting Up
a Console Interface Through Telnet .
Cause: The sensor has had a hardware or software failure.
Solution:
Observe the Axia sensor LEDs; refer to
Section 8.5—
Example of Tool Transformation Functionality
Through Telnet
.
Cause: The user has not requested the sensor to start streaming.
Solution:
Send the proper command (via TCP, UDP, or Telnet) to
start the data stream. When using ATI’s NET F/T Java
®
Demo or F/T Data Viewer, click “Start Reading”.
Symptom: The actual data
output rate of
the sensor is
less than expected.
Cause: The user is communicating with the sensor via TCP, and the client (the
robot, PC, or PLC) is not requesting packets fast enough.
Solution: TCP is a request and response type of communication.
The request speed of the client is typically the limiting
factor. Try configuring the client to request packets faster
(more frequently).
Cause:
The user is using a data collection method such as RDT via an UDP
interface that is too fast for the user’s device to process; refer to
Section 12—UDP Interface Using RDT .
Solution:
Verify that the Ethernet network configuration is properly
set for the device; refer to
Section 13.7—Improving
Ethernet Throughput .
Symptom: The initial F/T
values are non-
zero and no
load is applied.
Solution:
Normal. Bias the sensor to bring all the F/T
values back to zero.