Skip to content

Add an example using the script_command_interface #326

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

Merged
merged 3 commits into from
May 20, 2025

Conversation

urfeex
Copy link
Member

@urfeex urfeex commented May 19, 2025

This adds an example for using the script_command interface. It basically came out of testing #323 manually.

@urfeex urfeex requested a review from a team May 19, 2025 10:03
Copy link

codecov bot commented May 19, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (torque_control@7b01a7f). Learn more about missing BASE report.

Additional details and impacted files
@@                Coverage Diff                @@
##             torque_control     #326   +/-   ##
=================================================
  Coverage                  ?   82.68%           
=================================================
  Files                     ?        1           
  Lines                     ?      231           
  Branches                  ?        0           
=================================================
  Hits                      ?      191           
  Misses                    ?       40           
  Partials                  ?        0           
Flag Coverage Δ
start_ursim 82.68% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

// Keep running all commands in a loop until g_running is set to false
while (g_running)
{
run_cmd("Setting tool voltage to 24V",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should call start and stop force mode as well

Copy link
Member Author

@urfeex urfeex May 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As force mode needs quite a lot of arguments and might complain about singularities if the robot is in the wrong pose, I would rather skip it here. It's got its own example. But I can also add freedrive mode. I'll skip freedrive mode, as well, as that expects a special keepalive signal. That also has its own example.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make sense leaving it out then.

urfeex and others added 2 commits May 20, 2025 14:16
Co-authored-by: Mads Holm Peters <79145214+urmahp@users.noreply.github.com>
@urfeex urfeex requested a review from urmahp May 20, 2025 12:23
@urfeex urfeex merged commit 0d33b7d into UniversalRobots:torque_control May 20, 2025
7 of 22 checks passed
@urfeex urfeex deleted the script_command_example branch May 20, 2025 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants