Dear Matti,

Thank you for your reply.

Please could you help me with the following code?
— start code
private void testAlarms(NodeDevice nodeDevice) {
try {
TCDHelpOffNormalAlarmTypeNode alarm = nodeManagerEu82_1.createInstance( //
TCDHelpOffNormalAlarmTypeNode.class, //
“TCDHelpOffNormalAlarmType”, //
new NodeId(nodeManagerEu82_1.getNamespaceIndex(),
“TCDHelpOffNormalAlarmType_” + nodeDevice.getDevice().getFmId())); //

System.err.println(“— alarm: ” + alarm.getNodeId());
System.err.println(“— alarm: ” + alarm);

TCDHelpOffNormalAlarmTypeNode retriveAlarm = nodeManagerEu82_1.getNode( //
new NodeId(nodeManagerEu82_1.getNamespaceIndex(),
“TCDHelpOffNormalAlarmType_” + nodeDevice.getDevice().getFmId()), //
TCDHelpOffNormalAlarmTypeNode.class);

System.err.println(“— check alarm ” + alarm.equals(retriveAlarm));
} catch (Exception e) {
e.printStackTrace();
}
}
— end code

The method nodeManagerEu82_1.getNode throws exception:
— start log
27/12/2022 14:02:34 [connectionThread] ERROR c.p.g.s.p.o.m.e.OPCUAEuromap82_1Module – — alarm: ns=4;s=TCDHelpOffNormalAlarmType_1
27/12/2022 14:02:34 [connectionThread] ERROR c.p.g.s.p.o.m.e.OPCUAEuromap82_1Module – — alarm: NodeId=ns=4;s=TCDHelpOffNormalAlarmType_1, NodeClass=Object, BrowseName=4:TCDHelpOffNormalAlarmType; Type={NodeId=ns=4;i=1009, NodeClass=ObjectType, BrowseName=4:TCDHelpOffNormalAlarmType, IsAbstract=false}
27/12/2022 14:02:34 [connectionThread] ERROR java.lang.Throwable – com.prosysopc.ua.StatusException: nodeId=ns=4;s=TCDHelpOffNormalAlarmType_1 StatusCode=Bad_NodeIdUnknown (0x80340000) “The node id refers to a node that does not exist in the server address space.” Diagnostics=Diagnostic Info:
nodeId=ns=4;s=TCDHelpOffNormalAlarmType_1
— end log

Best regards,
Francesco

Hi everyone,
Thank you for your support.

If there is no problem I would continue writing in this thread.

My goal is to send the TCDHelpOffNormalAlarmTypeNode alarm (subtype of OffNormalAlarmTypeNode) and then check it with UAExpert.

My server code does the following:
1 Create an instance of the TCDHelpOffNormalAlarmTypeNode alarm.
2 Set the alarm source.
3 Send the alarm.

I listened for events with UAExpert:

Question: in the Events tab I see the alarm, but why I don’t see anything in the Alarms tab?

See pictures:
link 1
link 2

Thank you,

Hello,

Please I need your help to set mandatory attributes of TCDHelpOffNormalAlarmType (see Consideration fields)
——————————————————————————–
Hierarchy:
BaseEventType (OPC UA part 5)
This EventType is defined in OPC 10000-3.
|
ConditionType (OPC UA part 9)
The ConditionType inherits all Properties of the BaseEventType. Their semantic is defined in 10000-5.
|
AcknowledgeableConditionType (OPC UA part 9)
The AcknowledgeableConditionType inherits all Properties of the ConditionType.
|
AlarmConditionType (OPC UA part 9)
The AlarmConditionType that extends the AcknowledgeableConditionType by introducing an ActiveState, SuppressedState and ShelvingState. It also adds the ability to set a delay time, re-alarm time, Alarm groups and audible Alarm settings.
|
DiscreteAlarmType
The DiscreteAlarmType is used to classify Types into Alarm Conditions where the input for the Alarm may take on only a certain number of possible values (e.g. True/False, running/stopped/terminating).
|
OffNormalAlarmType (OPC UA part 9)
The OffNormalAlarmType is a specialization of the DiscreteAlarmType intended to represent a discrete Condition that is considered to be not normal.
|
HelpOffNormalAlarmType (EUROMAP 83)
The HelpOffNormalAlarmType can be used by devices, to inform the client about a Condition that is considered to be not normal. It is a subtype of the OffNormalAlarmType defined in OPC UA Part 9 and adds the Property Helptext to give some additional information to the operator.
|
TCDHelpOffNormalAlarmType (EUROMAP 82.1)
For alarms (alarms, warnings, information) of the TCD the TCDHelpOffNormalAlarmType as defined in Table 21 shall be used, if the alarm facet is supported. A machine which connects to a TCD via OPC 40082-1 shall subscribe this event

——————————————————————————–
BaseEventType properties (mandatory):

—
– BrowseName: EventId.
– Description: is generated by the Server to uniquely identify a particular Event Notification.
– Considerations: managed by Prosys SDK: EventId increments when i send the alarm (method: com.prosysopc.ua.types.opcua.server.BaseEventTypeNode.triggerEvent(null)).

—
– BrowseName: EventType.
– Description: describes the specific type of Event.
– Considerations: managed by Prosys SDK: the value of EventType is already set (TCDHelpOffNormalAlarmTypeNode’s NodeId – EUROMAP 82.1).

—
– BrowseName: SourceNode.
– Description: identifies the Node that the Event originated from.
– Considerations: SourceNode could be the NodeId of a TCD instance / MonitoredParameterType if this is out of tolerance

—
– BrowseName: SourceName.
– Description: provides a description of the source of the Event.
– Considerations: this could be the string-part of the DisplayName of the Event source

—
– BrowseName: Time.
– Description: Time provides the time the Event occurred. This value is set as close to the event generator as possible.
– Considerations: none.

—
– BrowseName: ReceiveTime.
– Description: provides the time the OPC UA Server received the Event from the underlying device of another Server.
– Considerations: none.

—
– BrowseName: Message.
– Description: provides a human-readable and localizable text description of the Event.
– Considerations: none.

—
– BrowseName: Severity.
– Description: is an indication of the urgency of the Event. This is also commonly called “priority”.
– Considerations: EUROMAP 82.1: For the Severity Property (included in BaseEventType) the following classes shall be used:
667-1000 Messages of high urgency
334-666 Messages of medium urgency
1-333 Messages of low urgency

——————————————————————————–
ConditionType properties (mandatory):
—
– BrowseName: ConditionClassId.
– Description: specifies in which domain this Condition is used. It is the NodeId of the corresponding subtype of BaseConditionClassType.
– Considerations: HELP. the value is null. What should i set?

—
– BrowseName: ConditionClassName.
– Description: provides the DisplayName of the of the ConditionClassType provided in the ConditionClassId.
– Considerations:HELP. the value is null. What should i set?

—
– BrowseName: ConditionName.
– Description: identifies the Condition instance that the Event originated from. It can be used together with the SourceName in a user display to distinguish between different Condition instances. If a ConditionSource has only one instance of a ConditionType, and the Server has no instance name, the Server shall supply the ConditionType browse name.
– Considerations: HELP. the value is null. Please can you give me an example?

—
– BrowseName: BranchId.
– Description: is NULL for all Event Notifications that relate to the current state of the Condition instance. If BranchId is not NULL, it identifies a previous state of this Condition instance that still needs attention by an Operator.
– Considerations: HELP. the value is null. Please can you give me an example?

—
– BrowseName: Retain.
– Description: when True describes a Condition (or ConditionBranch) as being in a state that is interesting for a Client wishing to synchronize its state with the Server’s state. The logic to determine how this flag is set is Server specific. Typically, all Active Alarms would have the Retain flag set; however, it is also possible for inactive Alarms to have their Retain flag set to TRUE.
– Considerations: if null the command Acknowledge of OPC UA CLIENT is not available.

—
– BrowseName: EnabledState.
– Description: indicates whether the Condition is enabled.
– Considerations: none.

—
– BrowseName: Quality
– Description: reveals the status of process values or other resources that this Condition instance is based upon.
– Considerations: HELP. the value is already set (GOOD (0x00000000) “The operation succeeded.”). When should i update it?

—
– BrowseName: LastSeverity
– Description: provides the previous severity of the ConditionBranch.
– Considerations: HELP. the value is null. Please can you give me an example?

—
– BrowseName: Comment
– Description: contains the last comment provided for a certain state (ConditionBranch).
– Considerations: HELP. the value is null. Please can you give me an example?

—
– BrowseName: ClientUserId
– Description: is related to the Comment field and contains the identity of the user who inserted the most recent Comment.
– Considerations: none.

—
– BrowseName: Disable
– Description: Method is used to change a Condition instance to the Disabled state.
– Considerations: none.

—
– BrowseName: Enable
– Description: Method is used to change a Condition instance to the enabled state.
– Considerations: none.

—
– BrowseName: AddComment
– Description: Method is used to apply a comment to a specific state of a Condition instance.
– Considerations: none.

——————————————————————————–
AcknowledgeableConditionType properties (mandatory):

—
– BrowseName: AckedState
– Description: when False indicates that the Condition instance requires acknowledgement for the reported Condition state.
– Considerations: none.

—
– BrowseName: Acknowledge
– Description: Method is used to acknowledge an Event Notification for a Condition instance state where AckedState is False.
– Considerations: none.

——————————————————————————–
AlarmConditionType properties (mandatory):

—
– BrowseName: ActiveState.
– Description: when set to True indicates that the situation the Condition is representing currently exists.
– Considerations: none.

—
– BrowseName: InputNode.
– Description: Property provides the NodeId of the Variable the Value of which is used as primary input in the calculation of the Alarm state.
– Considerations: none.

—
– BrowseName: SuppressedOrShelved
– Description: When an Alarm has any or all of the SuppressedState, OutOfServiceState or ShelvingState set to True, the SuppressedOrShelved property shall be set True and this Alarm is then typically not displayed by the Client.
– Considerations: none.

——————————————————————————–
DiscreteAlarmType properties (mandatory):

none.

——————————————————————————–
OffNormalAlarmType properties (mandatory):

—
– BrowseName: NormalState
– Description: The NormalState Property is a Property that points to a Variable which has a value that corresponds to one of the possible values of the Variable pointed to by the InputNode Property where the NormalState Property Variable value is the value that is considered to be the normal state of the Variable pointed to by the InputNode Property.
– Considerations: none.

——————————————————————————–
HelpOffNormalAlarmType properties (mandatory):
– BrowseName: HelpText
– Description: Servers can use the Property HelpText also in other server specific alarms which are not derived from OffNormalAlarmType
– Considerations: none.

——————————————————————————–
TCDHelpOffNormalAlarmType

—
– BrowseName: DeviceMappingNumber
– Description: The value of DeviceMappingNumber corresponds to the value given in the instance of the OperationType (see 9.1) for assigning the alarm to a device.
– Considerations: none.

—
– BrowseName: SourceNode
– Description: For unique identification of the alarm event, the SourceNode (included in BaseEventType) of the device needs to be sent for every alarm message. The SourceNode includes the namespace number and the Identifier from the object instance of TCD_InterfaceType (for general events) or the NodeId of a child element (e.g. a variable
of MonitoredParameterType if this is out of tolerance).
– Considerations: none.

—
– BrowseName: Severity
– Description: For the Severity Property (included in BaseEventType) the following classes shall be used: Table 22 – Severity Classes…
– Considerations: none.

Thanks,
Francesco

Dear Bjarne,

Thank you very much for your help.

I answer your question:
“First I would like to ask that are setting these due to “a real need” or more like that you are curious what their values could be?”

Right now I’m trying to handle the event TCDHelpOffNormalAlarmType triggered by TCD instances / monitored variables.

Also, I’m studying Alarms&Conditions to understand how the alarm event types defined in the OPC UA standard work because later I’ll have to handle alarms from machines that don’t implement UA Companion Specifications.

——————————————————————————–

I have another question regarding the Event View of the UAExpert client:

Can you please explain how the Event View page tabs work?

– Events tab: should the client only display events triggered after the client connection? Or should the server send the events triggered before the client connection?

– Alarms: should the server send to it the alarms triggered before the client connection? (as for the Events tab).

– Event History: should the client view the events stored in the server’s event history?

Thanks,
Francesco

Dear Bjarne,

I started using the OPC UA Browser client. Now I can check the differences between two clients. Thanks.

——————————————————————————–

Question: I noticed that if I don’t add my TCDHelpOffNormalAlarmTypeNode instance to the OPC UA tree (UaNode.addComponent() method), the client fails to execute the methods (Acknwoledge, Confirm, Active, …). Error: Bad_NodeIdUnknown.

I thought it wasn’t mandatory to add the alarms nodes to the OPC UA tree.

Is this behavior correct?

Question 2: I tried adding the myAlarm node to the MyHistorian event handler (SampleConsoleServer project). But it’s not working. Please can you send me an example?

Thanks,
Francesco

Dear Bjarne,

I answer your question:
“So I guess a better question would be that is adding them to the address space a problem for you?”
Thanks you for the explanation. For me it is not a problem to add the nodes. I prefer to use high level API (NodeManagerListener + Codegen classes).

Thanks,
Francesco