Name Description Size Coverage
CMakeLists.txt 2011 -
doc -
opcuaattributecache.cpp ! \class OpcUaAttributeCache \inqmlmodule QtOpcUa \brief Flexible attribute value cache providing signals. \deprecated [6.9] \internal This class is just for internal use in the declarative backend and not exposed to users. It caches node attribute values and provides access. Main purpose is to let \l OpcUaAttributeValue provide separate value change signals for each attribute. \sa OpcUaAttributeValue 1674 -
opcuaattributecache_p.h 1201 -
opcuaattributeoperand.cpp ! \qmltype AttributeOperand \inqmlmodule QtOpcUa \brief The OPC UA AttributeOperand type. \since QtOpcUa 5.13 \deprecated [6.9] The AttributeOperand is defined in OPC UA 1.05 part 4, 7.7.4.4. It has the same purpose as \l SimpleAttributeOperand but has more configurable options. 5691 -
opcuaattributeoperand_p.h 2657 -
opcuaattributevalue.cpp ! \class OpcUaAttributeValue \inqmlmodule QtOpcUa \brief Stores an attribute value and provides a changed signal. \internal \deprecated [6.9] This class is just for internal use in the declarative backend and not exposed to users. When setting the value it will emit a changed signal if the value has changed. \sa OpcUaAttributeCache 1258 -
opcuaattributevalue_p.h 1050 -
opcuaconnection.cpp ! \qmltype Connection \inqmlmodule QtOpcUa \brief Connects to a server. \since QtOpcUa 5.12 \deprecated [6.9] The main API uses backends to make connections. You have to set the backend before any connection attempt. \code import QtOpcUa as QtOpcUa QtOpcUa.Connection { backend: "open62541" } Component.onCompleted: { connection.connectToEndpoint("opc.tcp://127.0.0.1:43344"); } \endcode 18579 -
opcuaconnection_p.h 3965 -
opcuadatachangefilter.cpp 2219 -
opcuadatachangefilter_p.h 2237 -
opcuaelementoperand.cpp ! \qmltype ElementOperand \inqmlmodule QtOpcUa \brief The OPC UA ElementOperand type. \since QtOpcUa 5.13 \deprecated [6.9] The ElementOperand is defined in OPC UA 1.05 part 4, 7.7.4.2. It is used to identify another element in the filter by its index (the first element has the index 0). This is required to create complex filters, for example to reference the two operands of the AND operation in ((Severity > 500) AND (Message == "TestString")). The first step is to create content filter elements for the two conditions (Severity > 500) and (Message == "TestString"). A third content filter element is required to create an AND combination of the two conditions. It consists of the AND operator and two element operands with the indices of the two conditions created before: \code import QtOpcUa as QtOpcUa QtOpcUa.EventFilter { select : [ ... ] where: [ QtOpcUa.FilterElement { operator: QtOpcUa.FilterElement.GreaterThan firstOperand: QtOpcUa.SimpleAttributeOperand { browsePath: [ QtOpcUa.NodeId { identifier: "Severity" ns: "http://opcfoundation.org/UA/" } ] } secondOperand: QtOpcUa.LiteralOperand { value: 500 type: QtOpcUa.Constants.UInt16 } } QtOpcUa.FilterElement { operator: QtOpcUa.FilterElement.Equals firstOperand: QtOpcUa.SimpleAttributeOperand { browsePath: [ QtOpcUa.NodeId { identifier: "Message" ns: "http://opcfoundation.org/UA/" } ] } secondOperand: QtOpcUa.LiteralOperand { value: "TestString" type: QtOpcUa.Constants.String } } QtOpcUa.FilterElement { operator: QtOpcUa.FilterElement.And firstOperand: QtOpcUa.ElementOperand { index: 0 } secondOperand: QtOpcUa.ElementOperand { index: 1 } } ] } \endcode 3436 -
opcuaelementoperand_p.h 1187 -
opcuaendpointdiscovery.cpp ! \qmltype EndpointDiscovery \inqmlmodule QtOpcUa \brief Provides information about available endpoints on a server. \since QtOpcUa 5.13 \deprecated [6.9] Allows to fetch and access information about available endpoints on a server. \snippet ../../src/declarative_opcua/doc/snippets/basic/basic.qml Basic discovery 7179 -
opcuaendpointdiscovery_p.h 2433 -
opcuaeventfilter.cpp ! \qmltype EventFilter \inqmlmodule QtOpcUa \brief Defines an EventFilter for a monitored item. \since QtOpcUa 5.13 \deprecated [6.9] An event filter is required for monitoring events on the server. It consists of \c select clauses and a \c where clause. The \c select clauses are used to specify the data the user wants to receive when an event occurs. It consists of \l {SimpleAttributeOperand} simple attribute operands which select attributes of child nodes of an event type, for example the value attribute of the "Message" property of BaseEventType. The \c where clause is used to restrict the reported events by matching against certain criteria. Several operators and four different operand types allow filtering based on the values of the attributes of the child nodes of an event type. The select clause consists of an array of \l SimpleAttributeOperand. The where clause consists of an array of \l SimpleAttributeOperand, \l LiteralOperand, \l ElementOperand or \l AttributeOperand. The following EventFilter tells the server to report the value of the "Message" field for events that have a "Severity" field with value >= 500: \code import QtOpcUa as QtOpcUa QtOpcUa.Node { ... eventFilter: QtOpcUa.EventFilter { select: [ QtOpcUa.SimpleAttributeOperand { browsePath: [ QtOpcUa.NodeId { identifier: "Severity" ns: "http://opcfoundation.org/UA/" } ] }, QtOpcUa.SimpleAttributeOperand { browsePath: [ QtOpcUa.NodeId { identifier: "Message" ns: "http://opcfoundation.org/UA/" } ] } ] where: [ QtOpcUa.FilterElement { operator: QtOpcUa.FilterElement.GreaterThanOrEqual firstOperand: QtOpcUa.SimpleAttributeOperand { browsePath: [ QtOpcUa.NodeId { identifier: "Severity" ns: "http://opcfoundation.org/UA/" } ] } secondOperand: QtOpcUa.LiteralOperand { value: 700 type: QtOpcUa.Constants.UInt16 } } ] } } \endcode For a more complex example with two conditions, see \l QOpcUaElementOperand. \sa FilterElement 7847 -
opcuaeventfilter_p.h 2774 -
opcuafilterelement.cpp ! \qmltype FilterElement \inqmlmodule QtOpcUa \brief The OPC UA ContentFilterElement. \since QtOpcUa 5.13 \deprecated [6.9] A content filter element contains an operator and operands. There are four different operator types which contain literal values, references to attributes of nodes or to other content filter elements. A combination of one or more content filter elements makes a content filter which is used by the server to filter data for the criteria defined by the content filter elements. For example, the \c where clause of an event filter is a content filter which is used to decide if a notification is generated for an event. \code QtOpcUa.FilterElement { operator: QtOpcUa.FilterElement.GreaterThanOrEqual firstOperand: QtOpcUa.SimpleAttributeOperand { ... } secondOperand: QtOpcUa.LiteralOperand { ... } } \endcode \sa EventFilter 3900 -
opcuafilterelement_p.h 2330 -
opcuaforeign.cpp ! \qmltype Constants \inqmlmodule QtOpcUa \brief Provides access to OPC UA enumerations. \since QtOpcUa 5.12 \deprecated [6.9] This type provides access to enumerations from the \l QOpcUa namespace for use in QML. 1635 -
opcuaforeign_p.h 1365 -
opcualiteraloperand.cpp ! \qmltype LiteralOperand \inqmlmodule QtOpcUa \brief The OPC UA LiteralOperand type. \since QtOpcUa 5.13 \deprecated [6.9] The LiteralOperand is defined in OPC UA 1.05 part 4, 7.7.4.3. It contains a literal value that is to be used as operand for filters. Setting the type should be done to match the expected types on the server. Otherwise the type will be guessed and may lead to errors because it does not match on the server. \code import QtOpcUa as QtOpcUa QtOpcUa.LiteralOperand { value: 43.21 type: QtOpcUa.Constants.Double } \endcode 1862 -
opcualiteraloperand_p.h 1351 -
opcuamethodargument.cpp ! \qmltype MethodArgument \inqmlmodule QtOpcUa \brief Arguments for OpcUa method calls. \since QtOpcUa 5.13 \deprecated [6.9] When calling methods which require arguments, this type is used. This example shows how to call a method with two double arguments. \code QtOpcUa.MethodNode { ... inputArguments: [ QtOpcUa.MethodArgument { value: 3 type: QtOpcUa.Constants.Double }, QtOpcUa.MethodArgument { value: 4 type: QtOpcUa.Constants.Double } ] } \endcode 1672 -
opcuamethodargument_p.h 1228 -
opcuamethodnode.cpp ! \qmltype MethodNode \inqmlmodule QtOpcUa \brief Calls a method on the server. \since QtOpcUa 5.12 \inherits Node \deprecated [6.9] This QML element supports calling method nodes on a server. The target object node ID has to be specified by the \l objectNodeId property. \code import QtOpcUa as QtOpcUa QtOpcUa.MethodNode { nodeId : QtOpcUa.NodeId { identifier: "s=Example.Method" ns: "Example Namespace" } objectNodeId : QtOpcUa.NodeId { identifier: "s=Example.Object" ns: "Example Namespace" } connection: myConnection } \endcode The actual function call can be triggered by a signal. \code Button { text: "Start" onClicked: myNode.callMethod } \endcode or by JavaScript \code myNode.callMethod() \endcode 7291 -
opcuamethodnode_p.h 2608 -
opcuanode.cpp ! \qmltype Node \inqmlmodule QtOpcUa \brief Represents a node on a server. \since QtOpcUa 5.12 \deprecated [6.9] \code import QtOpcUa as QtOpcUa QtOpcUa.Node { nodeId : QtOpcUa.NodeId { identifier: "s=Example.Method" ns: "Example Namespace" } connection: myConnection } \endcode 18089 -
opcuanode_p.h 5342 -
opcuanodeid.cpp ! \qmltype NodeId \inqmlmodule QtOpcUa \brief Specifies a node by an identifier. \since QtOpcUa 5.12 \deprecated [6.9] \code import QtOpcUa as QtOpcUa QtOpcUa.NodeId { identifier: "s=Example.Node" ns: "Example Namespace" } \endcode 2104 -
opcuanodeid_p.h 1136 -
opcuanodeidtype.cpp ! \qmltype OpcUaNodeIdType \inqmlmodule QtOpcUa \brief Common base class for all node IDs. \deprecated [6.9] \internal This base class provides common functions for node ID related classes. It is not supposed to be used from QML directly. \sa NodeId, RelativeNodeId 1820 -
opcuanodeidtype_p.h These functions are not exposed to QML intentionally. The reason is that some derived QML types have to prohibit access to some of these functions. Exposing is done selectively in the derived classes. 1697 -
opcuaoperandbase.cpp 688 -
opcuaoperandbase_p.h 874 -
opcuapathresolver.cpp ! \class OpcUaPathResolver \inqmlmodule QtOpcUa \internal \brief This class resolves relative nodes. \deprecated [6.9] This class is used to resolve relative node IDs. It will emit \c resolvedNode with the result and delete itself afterwards. In case of errors the resolved node is empty and the error message is set. This class is capable of resolving cascaded relative nodes by recursively instantiating further resolvers. The maximum recursion depth is 50. \sa RelativeNodeId, Node 6841 -
opcuapathresolver_p.h 1747 -
opcuareaditem.cpp ! \qmltype ReadItem \inqmlmodule QtOpcUa \brief Specifies an item to be read from the server. \since QtOpcUa 5.13 \deprecated [6.9] This type is used to specify items to be read from the server using the function \l Connection::readNodeAttributes. 2582 -
opcuareaditem_p.h 1855 -
opcuareadresult.cpp ! \qmltype ReadResult \inqmlmodule QtOpcUa \brief Contains result data after reading from the server. \since QtOpcUa 5.13 \deprecated [6.9] This type is used to pass the read data after reading from the server using the function \l Connection::readNodeAttributes. 3793 -
opcuareadresult_p.h 1895 -
opcuarelativenodeid.cpp ! \qmltype RelativeNodeId \inqmlmodule QtOpcUa \brief Specifies a relative node by a start node and a path. \since QtOpcUa 5.12 \deprecated [6.9] Proceeding from the given start node, the server tries to match the content of the path property to any existing nodes on the server. Only if the path fully matches to exactly one single target node, it will be used. Partial or multiple matches can not be handled and are treated as error. \code import QtOpcUa as QtOpcUa QtOpcUa.RelativeNodeId { startNode: QtOpcUa.RelativeNodeId { identifier: "s=Example.Node" ns: "Example Namespace" } path: [ QtOpcUa.RelativeNodePath { ns: "Test Namespace" browseName: "SomeName" } ... ] } } \endcode \sa NodeId, Node 3954 -
opcuarelativenodeid_p.h 2009 -
opcuarelativenodepath.cpp ! \qmltype RelativeNodePath \inqmlmodule QtOpcUa \brief Specifies a relative node path element. \since QtOpcUa 5.12 \deprecated [6.9] \code import QtOpcUa as QtOpcUa QtOpcUa.RelativeNodePath { ns: "Test Namespace" browseName: "SomeName" } \endcode \sa Node, NodeId, RelativeNodeId 4469 -
opcuarelativenodepath_p.h 2419 -
opcuaserverdiscovery.cpp ! \qmltype ServerDiscovery \inqmlmodule QtOpcUa \brief Provides information about available servers. \since QtOpcUa 5.13 \deprecated [6.9] Allows to fetch and access information about servers known to a server or discovery server. \snippet ../../src/declarative_opcua/doc/snippets/basic/basic.qml Basic discovery 7614 -
opcuaserverdiscovery_p.h 2157 -
opcuasimpleattributeoperand.cpp ! \qmltype SimpleAttributeOperand \inqmlmodule QtOpcUa \brief The OPC UA SimpleAttributeOperand type. \since QtOpcUa 5.13 \deprecated [6.9] The SimpleAttributeOperand is specified in OPC UA 1.05 part 4, 7.7.4.5. It is used when a node attribute is required as operand. For example, the following simple attribute operand represents the value of the "Severity" field of the base event type: \code import QtOpcUa as QtOpcUa QtOpcUa.SimpleAttributeOperand { identifier: "Severity" ns: "http://opcfoundation.org/UA/" } \endcode 6070 -
opcuasimpleattributeoperand_p.h 2466 -
opcuastatus.cpp ! \qmltype Status \inqmlmodule QtOpcUa \brief Status code of an OPC UA function. \since QtOpcUa 5.13 \deprecated [6.9] This QML element contains information about the result status of an OPC UA action. The most common use case is to check if a call was successful \code if (methodNode.resultCode.isGood) { // do something } \endcode 53017 -
opcuastatus_p.h 12334 -
opcuavaluenode.cpp ! \qmltype ValueNode \inqmlmodule QtOpcUa \brief Represents a value node from a server. \inherits Node \since QtOpcUa 5.12 \deprecated [6.9] \code import QtOpcUa as QtOpcUa QtOpcUa.ValueNode { nodeId: QtOpcUa.NodeId { ns: "Test Namespace" identifier: "s=TestName" } connection: myConnection } \endcode A subscription will be created on the server in order to track value changes on the server. \sa NodeId, Connection, Node 9434 -
opcuavaluenode_p.h 2644 -
opcuawriteitem.cpp ! \qmltype WriteItem \inqmlmodule QtOpcUa \brief Specifies an item to be written to the server. \since QtOpcUa 5.13 \deprecated [6.9] This type is used to specify items to be written to the server using the function \l Connection::writeNodeAttributes. 5270 -
opcuawriteitem_p.h 2799 -
opcuawriteresult.cpp ! \qmltype WriteResult \inqmlmodule QtOpcUa \brief Contains result data after writing to the server. \since QtOpcUa 5.13 \deprecated [6.9] This type is used to pass the results after writing to the server using the function \l Connection::writeNodeAttributes. \sa WriteItem 2907 -
opcuawriteresult_p.h 1602 -
universalnode.cpp 12678 -
universalnode_p.h 3609 -