Add RWSClient::getIOSignals(). #63
Conversation
There was a problem hiding this comment.
The new function works as intended.
Do you also intend to expose the new function in the more user-friendly RWSInterface class? For example:
-
Implementing a
structfor an IO-signal list item according to the documentation, which contains:- name: IO-signal name
- type: Signal type {DO | DI | AO | AI | GI | GO}
- category: Signals list item
- lvalue: Signal value
- lstate: Signals state {simulated | not simulated}
-
Parsing the XML document into a vector of such IO-signal list items, similar to RWSInterface::getRAPIDModulesInfo(...).
If not, can you open an issue for that?
Can you also update the PR to be in sync with the base branch?
include/abb_librws/rws_client.h
Outdated
| @@ -357,6 +357,13 @@ class RWSClient : public POCOClient | |||
| */ | |||
| RWSResult getConfigurationInstances(const std::string topic, const std::string type); | |||
|
|
|||
| /** | |||
| * \brief A method for retrieving the all available IO signals on the controller. | |||
There was a problem hiding this comment.
| * \brief A method for retrieving the all available IO signals on the controller. | |
| * \brief A method for retrieving all available IO signals on the controller. |
|
I fixed the typo. I actually switched from |
|
Issue opened as #66. |
Getting a list of all signals is very useful if you're still getting to know the robot. I wanted this functionality for a ROS wrapper we've made at RoboHouse [1]. For now, it needs a forked
abb_librwswith this patch applied.I was kinda waiting for the other PRs to be merged first, but I suppose I might as well make make this one already.
[1] https://gitlab.com/robohouse/abb_io