Skip to main content

Standalone node interfaces

The ROS 1 and ROS 2 standalone nodes share endpoint, calibration, publishing, recovery, and diagnostic configuration. ROS wrench output is always N and N·m.

Parameters

NameTypeDefaultDescription
sensor_ipstring192.168.1.1Sensor IPv4 address or host
sensor_portint49152RDT UDP port
http_portint80Sensor HTTP configuration port
use_sensor_calibrationbooltrueDiscover calibration from the sensor over HTTP
frame_idstringnetft_linkWrench header frame
wrench_topicstring/netft/wrenchPublished wrench topic
bias_servicestring/netft/biasSoftware-bias service
counts_per_forceint1000000Counts per newton for a manual override
counts_per_torqueint1000000Counts per newton-meter for a manual override
publish_rateint0Maximum publish rate; zero publishes every accepted sample
receive_timeoutdouble0.1Maximum seconds without a valid record
configuration_connect_timeoutdouble0.5HTTP connection timeout
configuration_timeoutint1Total HTTP configuration timeout
reconnect_initial_delaydouble0.25Initial reconnect delay
reconnect_max_delayint5Maximum reconnect delay
diagnostics_rateint1Diagnostics publication rate
expected_rdt_rateint2000Expected RDT receive rate
rate_tolerancedouble0.2Allowed fractional receive-rate deviation
publish_on_errorboolfalsePublish standalone samples with serious device status

Interfaces

NameCategoryTypeDescription
/netft/wrenchtopicgeometry_msgs/WrenchStampedStandalone SI wrench output
/netft/biasservicestd_srvs/TriggerStandalone software bias

ROS 2 uses SensorDataQoS for wrench data and reliable diagnostics. ROS 1 uses a wrench publisher queue of 10. The message timestamp is the local ROS clock immediately after a complete RDT record is accepted.