Novanta ATI Axia130, Руководство пользователя

Страница: 90 / 95

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-90
Symptom: The values do not
match expected
values, for example:
the F/T values are
fluctuating but
are higher than a
known applied load.
Cause:
The user may be viewing gage data instead of F/T data.
Solution:
Gage data is not a 1:1 correlation to F/T axis data.
To view F/T data, refer to
Section 8.4—Query
Commands: “S” or “C” .
Cause: It is normal to see an offset in the data, even when unloaded.
Solution:
Use the bias command to zero/tare the data.
Cause: The sensor outputs data in counts. Counts must be divided by the
Counts per Force (CpF) or Counts per Torque (CpT) in order to
convert them to Calibration units (such as N and Nm).
Solution:
Verify if a user or user’s software is scaling the F/T values
to convert into units. Use the CpF and CpT to convert the
raw F/T values into units; for these count values, refer to:
•
ATI webpage: Section 6.2—Snapshot Page (rundata.htm)
•
Console via Telnet: Section 8.3—Console “CAL” | “SET”
Command Fields and Values
•
TCP: Section 10.5—Read Calibration Info Response
• XML:
Section 11.2—Calibration Information
(netftcalapi.xml)
Cause:
If the raw F/T values are already converted into units and the values
are high or nonsensical, verify that the sensor is not in one of these
conditions: saturation, gage out of range, or F/T out of range. Check
the status code of the sensor; refer to
Section 5.5—Status Code .
Solution: If the values exceed the ATI sensor’s calibration range
per the ATI manual in
Table 2.1 , the reported values are
incorrect. For more information, refer to
Section 2.1:
Measurement Range & Overload Limits in the Frequently
Asked Questions (FAQ) ATI document .