Skip to content
简体中文

Changelog

  • Fix CANFD broadcast discovery at slave ID 0: use extended frames, accept validated replies routed from real slave IDs, and confirm each device by unicast. Preserve address filters, deduplication, and the default 126/127 unicast fallback.
  • Correct piezoresistive-array palm reads: a positive runtime count at register 4037 selects base address 4165, including a reported count of 36. A zero count or unavailable count registers selects the legacy 36-point buffer at 4200.

SDK 2.x public signatures and calling conventions remain unchanged. No application call changes are required.

  • Add on-demand hardware traceability code reads to Python Hand, C++ Hand, and the C ABI. Return the complete ASCII string without parsing configuration fields or performing Factory KEY authentication automatically.
  • Return an empty string for unsupported function/register responses and blank or all-0xFFFF data. Preserve transport, other device, and malformed-data errors. Missing codes do not prevent connection.
  • Fix the unintended removal in 2.3.3 by restoring per-joint protection-current writes at 201 + joint index and configuration readback at 201–221 across Python, C/C++, and the GUI. Register 200 remains write-only; register 116 remains retired. Preserve the C configuration structure size and later field offsets.
  • Add independent 21-joint position, velocity, current, and operating-state reads to Python State, C++ State, and the C ABI. Single-field reads count toward state-read statistics; separate calls are not atomic snapshots.
  • Include read and caller processing time in State, Touch, and Health subscription periods. Overruns start the next read immediately without catch-up polling.
  • Reject non-finite, negative, or greater-than-32767 mA protection-current inputs before sending a write. This is the protocol encoding range; device and application current limits still apply.
  • Reject malformed CANFD response lengths and preserve USB receive errors. Python motion demos bound cleanup waits and preserve the original communication error.

After upgrading from 2.3.3, applications can use set_joint_protect_current and the configuration snapshot field joint_protect_current_ma again. When upgrading from 2.3.1/2.3.2, replace set_global_protect_current with set_max_continuous_current; global current fields remain removed. Rebuild C/C++ applications with the 2.3.4 headers.

  • Apply the maximum continuous current to all joints through write-only register 200. Register 116 is retired; configuration snapshots no longer read current settings.
  • Breaking change: remove the global/per-joint protection-current setters and current fields from Python/C++ configuration snapshots. Rebuild C applications with the new header; former current slots are reserved and always zero.
  • Remove obsolete GUI protection-current controls. Contact-probe diagnostics require an explicit software current threshold.
  • Correct initial thumb limits to J16 base flexion 0–75° and J20 rotation 0–105°. Successful device readback continues to override defaults; public joint IDs and controller slot mappings are unchanged.
  • Align GUI labels, close-hand joint selection, timing targets, C API comments, and diagnostic examples with the documented thumb anatomy.
  • Add regression coverage for thumb defaults, device-limit readback, and GUI close-hand targets.
  • Windows discovery: Fix Modbus scanning after a probe timeout by waiting for the previous serial connection to be released before reopening the port.
  • Modbus recovery: Allow reconnection after a request timeout or caller cancellation invalidates the connection. Existing timeout values and protection against late responses are unchanged.
  • Control mode warning: Selecting whole-hand Position or Damping mode warns that existing controls may require explicit restoration of MIT mode.
  • Whole-hand control modes: Add explicit mode reads and writes to Python Motion, C++ Motion, and the C ABI for Position, Damping, and Mit. Supporting firmware is required.
  • Compatibility: Preserve existing controls and units. Connection and control calls do not implicitly probe or switch modes. Applications using older firmware can retain existing controls and hide or disable unsupported mode selection.
  • Error handling: Mode writes share exclusive control with motion, Servo, and dragging. They do not retry automatically or cache or assume a mode. Cancelling a wait after sending cannot withdraw the write.

Tune MIT Kp/Kd for each joint, load, and mechanical condition; Position-mode accuracy does not establish MIT tracking accuracy. See Motion and ServoSession for the new APIs and restrictions.

  • Connection and tactile layouts: Read runtime point counts for supported tactile arrays before connection returns. The initial layout is ready for snapshots and subscriptions without first calling hand.touch.point_counts(). Devices without arrays skip this read. Older firmware retains the existing fallback; point-count initialization failures fail the connection.
  • Python layout snapshots: Layout objects do not update automatically. After explicitly changing the layout or querying point counts again, obtain hand.touch.layout and its modules again.
  • Linux C/C++ distribution: Default portable packages still include libusb and libudev. The new download-lib.sh --system-deps option uses compatible system libraries. The download script preserves SDK and third-party licenses and does not install or replace system libraries. Python wheel distribution is unchanged.

Existing SDK 2.x control APIs and calling conventions are unchanged. See the developer guide.

  • Palm tactile reads: Fix pressure-array palm reads for UT1, UF2, UF3, UV1, and UV2, supporting both 36- and 71-point layouts. The actual point count depends on the device layout. Compatibility with older firmware is preserved.
  • RS485 recovery: Fix an issue where reads, writes, or connection closure could remain blocked after a request timeout or cancellation. Ordinary built-in Modbus RTU register requests wait at most 1000 ms.
  • Linux compatibility: x86_64 and aarch64 packages support glibc 2.31 or later, including Ubuntu 20.04.
  • After a built-in Modbus request times out or is cancelled, close the original Manager, create a new one, and reconnect. If a write result is unconfirmed, read the actual device state after reconnecting before deciding whether to resend. The request timeout rule does not apply to custom Modbus callbacks or CANFD; OTA data writes use dedicated timeouts.
  • Handle array lengths according to the actual device tactile layout. A 71-point palm heatmap requires matching spatial coordinates; do not reuse the 36-point coordinate map.

See the quickstart for installation and the developer guide for tactile layouts and connection recovery.