New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
maxon EPOS4 Cia402Driver homing fails #236
Comments
This is the relevant exchange of SDOs that happens after I call the /init service.
It looks like the Master is asking for the supported drive modes and is not happy with 0x225. |
Things I have tried so far that did not fix the problem:
|
@leonce-m this is a problem I have also encountered with certain drives. It seems to be an issue with the homing sequence (from ROS1) that does not pick up that homing has already happened when you use a mode such as 35/37 (homing in actual position). For now I have set init to not actually fail in that case homing thinks it has failed (kind of workaround). Therefore, you can actually control the device in position mode etc. |
@ipa-cmh I was able to bypass this issue by essentially skipping the default homing mode execution similar to how it's done with homing mode 0. It's kind of a hack but it works for now. I needed homing to succeed because otherwise the ros2_control Cia402System would get stuck when calling the /init service and not accept control commands.
|
When I finish running the launch file,and cansend can0 702#00, the terminal responds as follows:[device_container_node-1] Found rpdo mapped object: index=6040 subindex=0 response: terminal responds as follows master: defaults:
rpdo: cob_id: 0x344 diagnostics: |
Describe the bug
When calling the /init service with homing mode 37 I get an error, but I'm still able to switch to position mode and control the motor.
Logs
Setup:
Additional context
bus.yml
The text was updated successfully, but these errors were encountered: