Skip to main content
CUSTOMER SUPPORT
Product Manuals
6-axis Force/Torque Sensors

Smart 6-axis Force Torque Sensor, AFT200-D80-EC

Download PDF

Smart 6-axis Force Torque Sensor, AFT200-D80-EC

Rev. 2026.09.15

FOREWORD​

Thank you for purchasing our Force Torque sensor. This manual contains the information necessary for the correct use of the AIDIN ROBOTICS AFT200-D80 sensor. Please carefully read this manual when using this software. Please note that the basic performance of the product will not be exhibited when the robot system is used out of conditions. This manual describes possible dangers and consequences using Force Torque sensor. Be sure to comply with safety precautions written in this manual to use safety and correctly.

NOTICE​

This manual Do NOT allow copy, reproduction or share without authorization of AIDIN ROBOTICS. Please notify us any errors in this manual or the provided instructions.

MANUFACTURER​

AIDIN ROBOTICS

SAFETY PRECAUTIONS​

Installation of Force Torque sensor MUST be performed by qualified personnel in accordance with national and local codes. Please carefully read this manual when using this software.

WARNING & CAUTION​

🚫 This symbol indicates that a danger of possible serious injury or death exists if the associated instructions are not followed properly.

⚠️ This symbol indicates that a danger of possible harm to people or physical damage to equipment and facilities exists if the associated instructions are not followed properly.

✅ AFT200-D80-EC sensor from AIDIN ROBOTICS meets CE-certified “A Class”

1. Introduction​

1.1 Smart 6-axis Force Torque Sensor, AFT200-D80​

1.2 Key features​

  • Smart 6-axis force/torque sensor
  • All-in-one sensor (No additional amplifier)
  • Digital output communications (EtherCAT)
  • Easy installation and data collection
  • Grippers, robot hands, collaborative robot, industrial robot

1.3 Specs.​

IndexUnitValue
Operating voltageVDC12
Max. safe excitation voltageVDC24
Nominal force rangeN200
Nominal torque rangeNm15
Limit force (Fxyz)N300
Limit torqueNm22.5
Force ResolutionN0.15
Torque ResolutionNm0.015
Force Noise-free resolution (STD)N0.4
Torque Noise-free resolution (STD)Nm0.025
Maximum sample rateHz1,000
DimensionsmmD80 x H21.5
IP ratingIP65
Operating temperature10-50℃

1.4 Flyer​

2. Installation Guide​

2.1 Basic Components​

  • AFT200-D80 x 1 EA
  • 1.5m Cable x 1 EA

2.2 Mounting​

  • M5 bolt 5.2Nm required for tightening
  • Performance cannot be guaranteed and A/S not possible when disassembling internal/external bolts

  • Sensor tightening order

  • CAUTION OF CABLE CUTTING AND EXCESS PULLING
  • Secure the sensor line with the robot so that it does not pull as it moves
    • Do not fix it to the robot using cable ties, etc., or use cable ties to fix it in a bundle shape like other wires
    • We recommend that you use Velcro to fix it with the robot, and please use Velcro to fix it when fixing it in a bundle form with other lines

💡 Performance CANNOT be guaranteed if not followed to the tightening torque guide.

💡 If the sensor line is not fixed to the robot, the output signal may have a noise due to the pulled by robot

💡 Please check More detail setup guide as follow:

2.3 AXIS & Drawings​

Drawing File :

💡

Port Location Notice

  • EtherCAT Type model has two ports: IN and OUT.
  • Ethernet Type model has one port, located on the left side.
  • CAN Type model has one port, located on the right side. STEP File:
  • 📎 AFT200-D80-EC_배포용.zip

2.3 Wiring​

The EtherCAT device are provided with a POE injector and a 12-24V AC/DC power supply. The sensor is complying with 802.3af Mode A protocol, but the power is being delivered by only one unused pair of the Cat5e ethernet cable. Make sure DO NOT apply the over voltage to the sensor cable. The user should connect the sensor cable to the “POE” marked port of the injector. Other POE Injectors compatible with the 802.3af Mode A can be used with 12-24V supply voltage.

2.3.1 Pin out​

  • Use POE Connector to connect Power & EtherNET signal

Cable wires colorEtherCAT Signal
1Green/WhiteTX+
2GreenTX-
3Orange/WhiteRX+
4Blue12V
5Blue/WhiteNC
6OrangeRX-
7Brown/WhiteNC
8BrownGND

2.5 EtherCAT interface​

The AFT200-D80-EC model support the RUN state where the sensor is providing the force/torque measurements. Also the IMU measurements can be activated by using activating signal to AFT200-D80-EC sensor. To activate the IMU signal or biasing the sensor signal, please follow the instructor in section 2.6. The EtherCAT interface is used to give the users the following capabilities: • Read the Product Number, Serial Number, etc. • Read Force/Torque Data → Force [N] = Force output/100-300, Torque = Torque output/500-50 • Read IMU data → Acceleration [m/s^2]= (Acceleration value – 32767)/1000 → gyroscope [ ˚/s] = (gyroscope value – 32767)/16.4

2.5.1 PDO interface The PDO interface exchanges data in real time with the F/T sensor. The PDO mapping used is given in the following:

2.5.1.1 RxPDO1: Object 0x1600 Digital Output

Name TypeIndexSubindexSizeBit SizeAccess
Digital Output0x70000x00BOOL1RO
BIAS_ON0x70000x01BOOL1RO
ACC_ON0x70000x02BOOL1RO
GYRO_ON0x70000x03BOOL1RO
NC0x70000x04BOOL1RO

2.5.1.2 TxPDO1: Object 0x1A00 Digital Output

Name TypeIndexSubindexSizeBit SizeAccess
Status0x60000x00SINT8RO
Force x0x60000x01REAL32RO
Force y0x60000x02REAL32RO
Force z0x60000x03REAL32RO
Torque x0x60000x04REAL32RO
Torque y0x60000x05REAL32RO
Torque z0x60000x06REAL32RO
Out of Range0x60000x07REAL32RO
Out of Range status0x60000x08REAL32RO
Acceleration x0x60000x09REAL32RO
Acceleration y0x60000x0aREAL32RO
Acceleration z0x60000x0bREAL32RO
Angular Rate x0x60000x0cREAL32RO
Angular Rate y0x60000x0dREAL32RO
Angular Rate z0x60000x0eREAL32RO
Temperature0x60000x0fREAL32RO

2.5.2 SDO interface The SDO data configures the sensor and reads the manufacturing and calibration data. This section lists dictionary objects specific to the EtherCAT F/T sensor application; it does not list objects that are a required part of the EtherCAT standard. These dictionary objects can also be found in the ESI file on the website

ObjectNameTypeDescription
0x20000StatusRO
0x60000Sensor DataROUsed to read the Force/Torque data, IMU etc.
from the sensor
0x70000Digital OutputRO

💡 To stabilize the sensor signal, it is recommended to have a running time of about **30 minutes.

* P**lease leave the sensor data on for at least 10 minutes before using it

💡 The first 10 minutes of sensor output data can cause data to flow.

2.6 Force/Torque Out of Range​

The sensor can operate up to its nominal capacity, while a single axis load. On Nominal capacity reading is incorrect and invalid. The nominal capacity of composite loading is The following diagram illustrates a complex loading scenario. The sensor cannot operate outside the normal operating area

The following graph shows the range of payloads and tool lengths that can be used with AFT200-D80-EC sensor for applications requiring high or moderate precision.

F/T load is outside the sensor’s detection capability. TxPDO1[0x6000, Index: 0x08] shows the value type and TxPDO1[0x6000, Index: 0x09] shows the status.

• The total percentage of the calibrated range used by Fxy and Tz axes is greater than 105%. Refer to the following Fxy, Tz equation.

Fx2+Fy2/FxyRange+∣Tz∣/TzRange>105%\sqrt{{F_x}^2+{F_y}^2}/{F_{xy}Range} +|{T_z}|/{T_{z}Range} >105 \%

• The total percentage of the calibrated range used by Fz and Txy axes is greater than 105%. Refer to the following Fz, Txy equation.

Tx2+Ty2/TxyRange+∣Fz∣/FzRange>105%\sqrt{{T_x}^2+{T_y}^2}/{T_{xy}Range} +|{F_z}|/{F_{z}Range} >105 \%

3. SOFTWARE​

3.1 Testing the EtherCAT in Windows application ( TwinCAT3 )

  • 📎 EtherCAT_manual.pdf 3.1.1 ESI(EtherCAT Slave Information) XML file for EtherCAT
    • XML file name : AFT200-D80-EC.xml
  • 📎 AFT200_D80_EC.xml
    • Download the XML file and paste it to the installed directory of TwinCAT. “C:/TwinCAT/3.1/Config/Io/EtherCAT” 3.1.2. Sequence of Testing
    1. Create a TwinCAT project using Visual Studio.
  1. Connect a LAN cable to EtherCAT Master (Ethernet adapter).
  2. Turn on AFT sensor.
  3. Scan the device.
  4. Activate the TwinCAT in free-run mode
  5. Observe the output values of PDO (Process Data Object) and SDO (Service Data Object)

3.2 Testing the EtherCAT in Linux application ( SOEM ) 3.2.1 clone the SOEM source code from the following page

git clone https://github.com/OpenEtherCATsociety/SOEM
  1. Follow the installation steps according to the SOEM webpage
  • mkdir build
  • cd build
  • cmake ..
  • make
  1. Copy the following code and paste to the simpletest.c code
/** \file
* \brief Example code for Simple Open EtherCAT master
*
* Usage : simple_test [ifname1]
* ifname is NIC interface, f.e. eth0
*
* This is a minimal test.
*
* (c)Arthur Ketels 2010 - 2011
*/

#include <stdio.h>
#include <string.h>
#include <inttypes.h>

#include "ethercat.h"

#define EC_TIMEOUTMON 500

char IOmap[4096];
OSAL_THREAD_HANDLE thread1;
int expectedWKC;
boolean needlf;
volatile int wkc;
boolean inOP;
uint8 currentgroup = 0;
boolean forceByteAlignment = FALSE;

void simpletest(char *ifname)
{
int i, j, oloop, iloop, chk;
needlf = FALSE;
inOP = FALSE;

printf("Starting simple test\n");

/* initialise SOEM, bind socket to ifname */
if (ec_init(ifname))
{
printf("ec_init on %s succeeded.\n",ifname);
/* find and auto-config slaves */

if ( ec_config_init(FALSE) > 0 )
{
printf("%d slaves found and configured.\n",ec_slavecount);

if (forceByteAlignment)
{
ec_config_map_aligned(&IOmap);
}
else
{
ec_config_map(&IOmap);
}

ec_configdc();

printf("Slaves mapped, state to SAFE_OP.\n");
/* wait for all slaves to reach SAFE_OP state */
ec_statecheck(0, EC_STATE_SAFE_OP, EC_TIMEOUTSTATE * 4);

oloop = ec_slave[0].Obytes;
if ((oloop == 0) && (ec_slave[0].Obits > 0)) oloop = 1;
if (oloop > 8) oloop = 8;
iloop = ec_slave[0].Ibytes;
if ((iloop == 0) && (ec_slave[0].Ibits > 0)) iloop = 1;
if (iloop > 8) iloop = 8;

printf("segments : %d : %d %d %d %d\n",ec_group[0].nsegments ,ec_group[0].IOsegment[0],ec_group[0].IOsegment[1],ec_group[0].IOsegment[2],ec_group[0].IOsegment[3]);

printf("Request operational state for all slaves\n");
expectedWKC = (ec_group[0].outputsWKC * 2) + ec_group[0].inputsWKC;
printf("Calculated workcounter %d\n", expectedWKC);
ec_slave[0].state = EC_STATE_OPERATIONAL;
/* send one valid process data to make outputs in slaves happy*/
ec_send_processdata();
ec_receive_processdata(EC_TIMEOUTRET);
/* request OP state for all slaves */
ec_writestate(0);
chk = 200;
/* wait for all slaves to reach OP state */
do
{
ec_send_processdata();
ec_receive_processdata(EC_TIMEOUTRET);
ec_statecheck(0, EC_STATE_OPERATIONAL, 50000);
}
while (chk-- && (ec_slave[0].state != EC_STATE_OPERATIONAL));
if (ec_slave[0].state == EC_STATE_OPERATIONAL )
{
printf("Operational state reached for all slaves.\n");
inOP = TRUE;
/* cyclic loop */
for(i = 1; i <= 10000; i++)
{
ec_send_processdata();
wkc = ec_receive_processdata(EC_TIMEOUTRET);

if(wkc >= expectedWKC)
{
printf("Processdata cycle %4d, WKC %d , O:", i, wkc);

for(j = 0 ; j < oloop; j++)
{
printf(" %2.2x", *(ec_slave[0].outputs + j));
}

printf(" I:");
//Test
int Fx= *(ec_slave[0].inputs+1)*256+*(ec_slave[0].inputs);
int Fy= *(ec_slave[0].inputs+5)*256+*(ec_slave[0].inputs+4);
int Fz= *(ec_slave[0].inputs+9)*256+*(ec_slave[0].inputs+8);
int Tx= *(ec_slave[0].inputs+13)*256+*(ec_slave[0].inputs+12);
int Ty= *(ec_slave[0].inputs+17)*256+*(ec_slave[0].inputs+16);
int Tz= *(ec_slave[0].inputs+21)*256+*(ec_slave[0].inputs+20);
int Ax= *(ec_slave[0].inputs+25)*256+*(ec_slave[0].inputs+24);
int Ay= *(ec_slave[0].inputs+29)*256+*(ec_slave[0].inputs+28);
int Az= *(ec_slave[0].inputs+33)*256+*(ec_slave[0].inputs+32);

printf(" Fx: %d, Fy: %d,Fz: %d,Tx: %d,Ty: %d,Tz: %d,Ax: %d,Ay: %d,Az: %d, ", Fx, Fy,Fz,Tx,Ty,Tz,Ax,Ay,Az);
printf(" T:%"PRId64"\n",ec_DCtime);
needlf = TRUE;
}
osal_usleep(5000);

}
inOP = FALSE;
}
else
{
printf("Not all slaves reached operational state.\n");
ec_readstate();
for(i = 1; i<=ec_slavecount ; i++)
{
if(ec_slave[i].state != EC_STATE_OPERATIONAL)
{
printf("Slave %d State=0x%2.2x StatusCode=0x%4.4x : %s\n",
i, ec_slave[i].state, ec_slave[i].ALstatuscode, ec_ALstatuscode2string(ec_slave[i].ALstatuscode));
}
}
}
printf("\nRequest init state for all slaves\n");
ec_slave[0].state = EC_STATE_INIT;
/* request INIT state for all slaves */
ec_writestate(0);
}
else
{
printf("No slaves found!\n");
}
printf("End simple test, close socket\n");
/* stop SOEM, close socket */
ec_close();
}
else
{
printf("No socket connection on %s\nExecute as root\n",ifname);
}
}

OSAL_THREAD_FUNC ecatcheck( void *ptr )
{
int slave;
(void)ptr; /* Not used */

while(1)
{
if( inOP && ((wkc < expectedWKC) || ec_group[currentgroup].docheckstate))
{
if (needlf)
{
needlf = FALSE;
printf("\n");
}
/* one ore more slaves are not responding */
ec_group[currentgroup].docheckstate = FALSE;
ec_readstate();
for (slave = 1; slave <= ec_slavecount; slave++)
{
if ((ec_slave[slave].group == currentgroup) && (ec_slave[slave].state != EC_STATE_OPERATIONAL))
{
ec_group[currentgroup].docheckstate = TRUE;
if (ec_slave[slave].state == (EC_STATE_SAFE_OP + EC_STATE_ERROR))
{
printf("ERROR : slave %d is in SAFE_OP + ERROR, attempting ack.\n", slave);
ec_slave[slave].state = (EC_STATE_SAFE_OP + EC_STATE_ACK);
ec_writestate(slave);
}
else if(ec_slave[slave].state == EC_STATE_SAFE_OP)
{
printf("WARNING : slave %d is in SAFE_OP, change to OPERATIONAL.\n", slave);
ec_slave[slave].state = EC_STATE_OPERATIONAL;
ec_writestate(slave);
}
else if(ec_slave[slave].state > EC_STATE_NONE)
{
if (ec_reconfig_slave(slave, EC_TIMEOUTMON))
{
ec_slave[slave].islost = FALSE;
printf("MESSAGE : slave %d reconfigured\n",slave);
}
}
else if(!ec_slave[slave].islost)
{
/* re-check state */
ec_statecheck(slave, EC_STATE_OPERATIONAL, EC_TIMEOUTRET);
if (ec_slave[slave].state == EC_STATE_NONE)
{
ec_slave[slave].islost = TRUE;
printf("ERROR : slave %d lost\n",slave);
}
}
}
if (ec_slave[slave].islost)
{
if(ec_slave[slave].state == EC_STATE_NONE)
{
if (ec_recover_slave(slave, EC_TIMEOUTMON))
{
ec_slave[slave].islost = FALSE;
printf("MESSAGE : slave %d recovered\n",slave);
}
}
else
{
ec_slave[slave].islost = FALSE;
printf("MESSAGE : slave %d found\n",slave);
}
}
}
if(!ec_group[currentgroup].docheckstate)
printf("OK : all slaves resumed OPERATIONAL.\n");
}
osal_usleep(10000);
}
}

int main(int argc, char *argv[])
{
printf("SOEM (Simple Open EtherCAT Master)\nSimple test\n");

if (argc > 1)
{
/* create thread to handle slave error handling in OP */
// pthread_create( &thread1, NULL, (void *) &ecatcheck, (void*) &ctime);
osal_thread_create(&thread1, 128000, &ecatcheck, (void*) &ctime);
/* start cyclic part */
simpletest(argv[1]);
}
else
{
ec_adaptert * adapter = NULL;
printf("Usage: simple_test ifname1\nifname = eth0 for example\n");

printf ("\nAvailable adapters:\n");
adapter = ec_find_adapters ();
while (adapter != NULL)
{
printf (" - %s (%s)\n", adapter->name, adapter->desc);
adapter = adapter->next;
}
ec_free_adapters(adapter);
}

printf("End program\n");
return (0);
}
  1. do make in build folder
  2. then run the simpletest program as follow
SOEM/build/test/linux/simple_test
sudo ./simple_test -(port)

Q & A​

(내용 준비 중)


Revision History​

DateDescription
2026.09.15Initial release (Current version)
Can't find what you're looking for?Try our FAQs first. Still need help? Contact us and our team will get back to you.