TUM-Aries-Lab / motor-module

74%

LAST BUILD ON BRANCH main

branch: SELECT

CHANGE BRANCH

x

Sync Branches

• No branch selected
• CAD-files-added
• CAN_implementation
• HNam05-patch-1
• HNam05-patch-2
• HNam05-patch-3
• Hannes
• IMU_Motor
• NGierden-Claude-Integration
• No-max-angle-limitations
• PDF-files-Motor+Jetson
• Test
• add_typehints
• audit-guard-and-faults
• bring-up-the-can-interface
• dependency-updates
• docs-claude-md-refresh
• enable-mit-mode-actually-enables
• fix-erpm-limits
• fix-motor-spec-default
• fix-pipeline
• fix-readme-badges
• grouping_constants
• main
• make-can-init-executable
• make-the-sudoers-script-executable
• new_main_test
• no_hardware
• release-prep-0.0.8
• remove_high_pitch_noise
• revert-zero-velocity-semantics
• safer-mit-kd-defaults
• sakshi_ak80_code_fixing
• sakshi_frequency_test
• sakshi_modular_multi_motor_can_system
• sakshi_pid_controller
• sakshi_tasks_part_1
• test_hardware
• update_fault_codes
• update_make_app
• v1_1_cleanup
• velocity-limit-audit
• verify-set-velocity-uses-profile-kd

Build # 35759845564

Build Type

push

github

Committed by NGierden

Commit Message

Make can_init.sh executable too

Same latent trap: mode 100644 while its own header says to run it as
./can_init.sh, which fails as "command not found" rather than as a permission
problem. All four shell scripts here are now 100755.

Nothing depends on it -- it is a bench tool that raises can0 and then pings
motors 003 and 004 to see them answer. Its bring-up half is superseded by
ensure_can_interface; the detection half is still the quickest way to ask
whether both motors are alive.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Coverage Stats

1563 of 2118 relevant lines covered (73.8%)

0.74 hits per line