Skip to content
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

Setting an anlog output without specifying a domain doesn't work #215

Open
1 task done
fmauch opened this issue Oct 8, 2024 · 0 comments
Open
1 task done

Setting an anlog output without specifying a domain doesn't work #215

fmauch opened this issue Oct 8, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@fmauch
Copy link
Collaborator

fmauch commented Oct 8, 2024

Affected Client Library version(s)

all

What combination of platform is the Client Library running on.

Linux without realtime patch

How did you install the Client Library

Build the library from source

Which robot platform is the library connected to.

URSim in docker

Robot SW / URSim version(s)

irrelevant

How are you using the Client Library

Headless without using the teach pendant, Through the robot teach pendant using External Control URCap

Issue details

Setting an analog output through sendStandardAnalogOutput without specifying an output domain doesn't work as expected.

Since the RTDEWriter always caches a full package with all recipe entries to avoid allocations for each sending operation, it will store the last set output domain and send that with each sent package. Since the RTDE protocol doesn't contain an option to "leave as configured on the TP" this can't be done with that method.

However, it might be worthwhile looking into whether we can change the communication on the client library's side. Since we create a new package to be sent from the cached package in each send operation the reasoning for keeping a cached package around might not hold up anyway. That might require some refactoring in our RTDEClient structure which is why I will not put that on the top priority list.

Relevant log output

No response

Accept Public visibility

  • I agree to make this context public
@fmauch fmauch added the bug Something isn't working label Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant