|
EventCookie | RegisterCallback (std::function< void()> handler) |
| Registers a callback for the method node. More...
|
|
void | UnregisterCallback (EventCookie eventCookie) |
| Unregisters a callback for the method node. More...
|
|
void | AddArgument (const Cvb::String &Name, OpcUa::ArgumentType inOutType, const Cvb::String &defaultValue) |
| Adds an argument of type 'Cvb::String' to the method node. See class description for details. More...
|
|
void | AddArgument (const Cvb::String &Name, OpcUa::ArgumentType inOutType, double defaultValue) |
| Adds an argument of type 'double' to the method node. See class description for details. More...
|
|
void | AddArgument (const Cvb::String &Name, OpcUa::ArgumentType inOutType, std::int64_t defaultValue) |
| Adds an argument of type 'std::int64_t' to the method node. See class description for details. More...
|
|
std::vector< OpcUa::MethodNodeArgument > | InputArguments () |
| Returns all registered input arguments. See class description for details. More...
|
|
std::vector< OpcUa::MethodNodeArgument > | OutputArguments () |
| Returns all registered output arguments. See class description for details. More...
|
|
void | Call () const |
| Starts execution of the given method node on the server. See class description for details.
|
|
void * | Handle () const noexcept |
| Returns C-API style handle to BaseNode Object. More...
|
|
OpcUa::NodeIDPtr | NodeID () const |
| Returns the OPCUA NodeID of an OPCUA BaseNode object. More...
|
|
String | BrowseName () const |
| Returns the browse name of an OPCUA BaseNode object. More...
|
|
std::vector< NodeIDPtr > | Browse (const BrowseFilter &filter) const |
| "Browse" all referenced BaseNodes of this BaseNode. More...
|
|
String | DisplayName () const |
| Returns the humanreadable name of a node. More...
|
|
OpcUa::NodeClass | NodeClass () const |
| Returns the NodeClass of an OPCUA BaseNode object. More...
|
|
OpcUa::ConnectionStatus | ConnectionStatus () const |
| Returns the ConnectionStatus of an OPCUA BaseNode object. More...
|
|
OpcUa::Access | Access () const |
| Returns the Access right to an OPCUA BaseNode object. More...
|
|
String | Description () const |
| Returns the description OPCUA BaseNode object. More...
|
|
void | AddReference (const OpcUa::BaseNode &destination, const ReferenceType reference, ReferenceDirection direction) const |
| Adds a Reference to the OPCUA node. More...
|
|
std::int64_t | GetAttributeAsInt (AttributeID attributeID) const |
| Return specific Information about a Opcua::BaseNode. More...
|
|
void | SetAttributeAsInt (AttributeID attributeID, std::int64_t value) |
| Set specific Information about a Opcua::BaseNode. More...
|
|
double | GetAttributeAsFloat (AttributeID attributeID) const |
| Return specific Information about a Opcua::BaseNode. More...
|
|
void | SetAttributeAsFloat (AttributeID attributeID, double value) |
| Set specific Information about a Opcua::BaseNode. More...
|
|
String | GetAttributeAsString (AttributeID attributeID) const |
| Return specific Information about a Opcua::BaseNode. More...
|
|
void | SetAttributeAsString (AttributeID attributeID, const String &value) |
| Set specific Information about a Opcua::BaseNode. More...
|
|
An OPCUA method node object to call remote procedures.
It provides an interface for calling functions/methods on the OPCUA server.
- Note
- MethodNodes (may) have input and output arguments. The generals step are ...
- On the server side: MethodNode is created and added to the server
- On the server side: The desired amount of arguments are added via MethodNode::AddArgment (for input and output). This "defines" the argments.
- On the server side: A callback is set. This is later called by the client via MethodNode::Call.
- On the client side: The client application retrieves the MethodNode and retrieves the argments via MethodNode::InputArguments
- On the client side: The client application sets the input arguments to the desired value and then calls MethodNode::Call.
- On the server side: The callback is triggered.
- The server application (inside the callback) retrieves the input arguments (MethodNode::InputArguments) and does whatever the callback is supposed to do.
- The server application (still inside the callback) set the output arguments (MethodNode::OutputArguments).
- The client application retrieves the output arguments.
-
For details also refer to the OPCUA specification Part 5:
https://opcfoundation.org/developer-tools/specifications-unified-architecture/part-5-information-model/