Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: i2rt-robotics/i2rt
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: VectorRobotics/i2rt
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: main
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 4 commits
  • 3 files changed
  • 1 contributor

Commits on Apr 3, 2026

  1. feat: add limit_gripper_force parameter to get_yam_robot function

    Introduced a new parameter, limit_gripper_force, to the get_yam_robot function, allowing for dynamic control of the gripper force during robot operation. Updated the function call to utilize this parameter instead of a hardcoded value.
    alexlin2 committed Apr 3, 2026
    Configuration menu
    Copy the full SHA
    6dfb317 View commit details
    Browse the repository at this point in the history

Commits on Apr 4, 2026

  1. refactor: simplify gripper force torque mapping in GripperForceLimiter

    Replaced the partial function for gripper force torque mapping with a direct reference to the mapping function. This change enhances code clarity and maintains the same functionality in the compute_target_gripper_torque method.
    alexlin2 committed Apr 4, 2026
    Configuration menu
    Copy the full SHA
    32af33d View commit details
    Browse the repository at this point in the history

Commits on Apr 9, 2026

  1. feat: implement consecutive communication failure handling in DMChain…

    …CanInterface
    
    Added a mechanism to track and handle consecutive communication failures for motors in the DMChainCanInterface. Introduced a new constant MAX_CONSECUTIVE_COMM_FAILURES and updated error handling to log warnings and abort operations after reaching the failure threshold. Enhanced the get_yam_robot function to include an optional parameter for gripper calibration control.
    alexlin2 committed Apr 9, 2026
    Configuration menu
    Copy the full SHA
    a78ee19 View commit details
    Browse the repository at this point in the history
  2. fix: increase MAX_CONSECUTIVE_COMM_FAILURES threshold in DMChainCanIn…

    …terface
    
    Updated the MAX_CONSECUTIVE_COMM_FAILURES constant from 10 to 250 to allow for more consecutive communication failures before aborting motor operations. This change aims to improve system resilience in the face of intermittent communication issues.
    alexlin2 committed Apr 9, 2026
    Configuration menu
    Copy the full SHA
    5dba44b View commit details
    Browse the repository at this point in the history
Loading