OPC Alarm Parameters are not collected at IoT hub

Question

OPC Alarm Parameters are not collected at IoT hub

HI,
We have installed "Prosys OPC Simulation Server" on edge device and configured 6 tags for data collection (F101A, F101B,P101A, P101B,T101A,T101B) and Prosys simulation software , by default, as an In built tag (MyLevel) on which alarms are gnereated. We are able fetch the alarm tag associated parameters ( like severity , AckedState, Message, AcivityState) on client (Prosys UA Browser). However we are not able to read those parameters on IoT hub.

Enclosed is PublishedNode.json file and Log file that collects the raw data on IOT Hub from OPC server. Log file is collected from Functions -> monitor -> systemLogs

You may observe from the log file that all tags (F101A,...) are collected periodically, only myLevel.ActiviteState is collected , while other associated parameters like myLevel.message, mylevel. Severity, myLevel.SourceName are not collected

126672-publishednodesjson.txt
126673-log.txt
Thanks

QuantumCache 20,366 Reputation points Moderator

2021-08-26T23:43:37.143+00:00

Hello @HCL-AZURE-Cloud-Connected-ECOSystems

We are able to fetch the alarm tag associated parameters ( like severity , AckedState, Message, AcivityState) on client (Prosys UA Browser).
What is the procedure or method followed to read the message on the client-side?

However we are not able to read those parameters on IoT hub.
could you please confirm on the data sent to the IoT Hub contains the required information which is read by the client?

Any documentation which you have followed or any architectural workflow would be helpful to understand this issue better.

IoT Edge-->IoTHub-->Azure Functions-->Prosys UA Browser ?is this the right architectural flow?
HCL-AZURE-Cloud-Connected-ECOSystems 46 Reputation points

2021-08-27T08:37:52.65+00:00

We are able to fetch the alarm tag associated parameters ( like severity , AckedState, Message, AcivityState) on client (Prosys UA Browser).
What is the procedure or method followed to read the message on the client-side?
--> Prosys UA Broser is OPC Client Tool and after connecting to server , the data view and Event View tabs in that tool can be used to view the data and alarm parameters . we are able to read the alarm parameters in Data View and Event view tab in UA browser

could you please confirm on the data sent to the IoT Hub contains the required information which is read by the client?
Any documentation which you have followed or any architectural workflow would be helpful to understand this issue better.
IoT Edge-->IoTHub-->Azure Functions-->Prosys UA Browser ?is this the right architectural flow?
--> the flow is Prosys UA Simulation server (on linux box)-> OPC Publisher (on linux box) -> Azure Functions (on cloud) -> IoT Edge(on cloud)
r
Let me know if you able to simulate the issue
QuantumCache 20,366 Reputation points Moderator

2021-08-27T14:48:41.667+00:00

Hello @HCL-AZURE-Cloud-Connected-ECOSystems ,

I wanted to understand if this issue is really with Azure IoT Hub or with Prosys UA Browser OPC Client Tool/
Could you please include the screenshots of the Prosys UA Broser OPC Client Tool, where the data is viewed and the issue area?

--> the flow is Prosys UA Simulation server (on linux box)-> OPC Publisher (on linux box) -> Azure Functions (on cloud) -> IoT Edge(on cloud)

You may want to mention the place of 'Azure IoT Hub' in the above flow?
HCL-AZURE-Cloud-Connected-ECOSystems 46 Reputation points

2021-08-31T13:29:11.977+00:00

Hi,
Here are screen shots from Prosys UA browser installed in same linux machine as the Prosys simulation server .
Alarm.jpg is from Event view page that displays the alarms are rows
Alarm1.jpg is from data view page that shows individual parameters. Note the NodeID in this same as one configured in json file
Thanks
QuantumCache 20,366 Reputation points Moderator

2021-08-31T18:52:25.283+00:00

Looks like this issue is more related to OPC UA Server -->OPC UA Browser. Something is broken between these two, right?
HCL-AZURE-Cloud-Connected-ECOSystems 46 Reputation points

2021-09-01T05:00:38.707+00:00

Hi,
Everything is fine between simulation server and UA browser - that is reason I posted the images (alarm.jpg and alarm1.jpg)
The alarm values are collected on UA Browser
Need to check if OPC Publisher is collecting those alarm values
Thanks

Accepted answer

0 additional answers

Your answer

QuantumCache 20,366 Reputation points Moderator

2021-08-26T23:43:37.143+00:00

Hello @HCL-AZURE-Cloud-Connected-ECOSystems

We are able to fetch the alarm tag associated parameters ( like severity , AckedState, Message, AcivityState) on client (Prosys UA Browser).
What is the procedure or method followed to read the message on the client-side?

However we are not able to read those parameters on IoT hub.
could you please confirm on the data sent to the IoT Hub contains the required information which is read by the client?

Any documentation which you have followed or any architectural workflow would be helpful to understand this issue better.

IoT Edge-->IoTHub-->Azure Functions-->Prosys UA Browser ?is this the right architectural flow?
HCL-AZURE-Cloud-Connected-ECOSystems 46 Reputation points

2021-08-27T08:37:52.65+00:00

We are able to fetch the alarm tag associated parameters ( like severity , AckedState, Message, AcivityState) on client (Prosys UA Browser).
What is the procedure or method followed to read the message on the client-side?
--> Prosys UA Broser is OPC Client Tool and after connecting to server , the data view and Event View tabs in that tool can be used to view the data and alarm parameters . we are able to read the alarm parameters in Data View and Event view tab in UA browser

could you please confirm on the data sent to the IoT Hub contains the required information which is read by the client?
Any documentation which you have followed or any architectural workflow would be helpful to understand this issue better.
IoT Edge-->IoTHub-->Azure Functions-->Prosys UA Browser ?is this the right architectural flow?
--> the flow is Prosys UA Simulation server (on linux box)-> OPC Publisher (on linux box) -> Azure Functions (on cloud) -> IoT Edge(on cloud)
r
Let me know if you able to simulate the issue
QuantumCache 20,366 Reputation points Moderator

2021-08-27T14:48:41.667+00:00

Hello @HCL-AZURE-Cloud-Connected-ECOSystems ,

I wanted to understand if this issue is really with Azure IoT Hub or with Prosys UA Browser OPC Client Tool/
Could you please include the screenshots of the Prosys UA Broser OPC Client Tool, where the data is viewed and the issue area?

--> the flow is Prosys UA Simulation server (on linux box)-> OPC Publisher (on linux box) -> Azure Functions (on cloud) -> IoT Edge(on cloud)

You may want to mention the place of 'Azure IoT Hub' in the above flow?
HCL-AZURE-Cloud-Connected-ECOSystems 46 Reputation points

2021-08-31T13:29:11.977+00:00

Hi,
Here are screen shots from Prosys UA browser installed in same linux machine as the Prosys simulation server .
Alarm.jpg is from Event view page that displays the alarms are rows
Alarm1.jpg is from data view page that shows individual parameters. Note the NodeID in this same as one configured in json file
Thanks
QuantumCache 20,366 Reputation points Moderator

2021-08-31T18:52:25.283+00:00

Looks like this issue is more related to OPC UA Server -->OPC UA Browser. Something is broken between these two, right?
HCL-AZURE-Cloud-Connected-ECOSystems 46 Reputation points

2021-09-01T05:00:38.707+00:00

Hi,
Everything is fine between simulation server and UA browser - that is reason I posted the images (alarm.jpg and alarm1.jpg)
The alarm values are collected on UA Browser
Need to check if OPC Publisher is collecting those alarm values
Thanks

Answer 1

QuantumCache 20,366 Moderator

Hello @HCL-AZURE-Cloud-Connected-ECOSystems , Thanks for posting this query on this forum.

Below is the response from Microsoft's Product team, I hope this helps with your initial query.

Alarms and Events are currently not supported.
Please refer to this Github page for any future updates: Azure Industrial IoT Platform

Please comment in the below section for further help in this matter. Happy to help!

Share via

OPC Alarm Parameters are not collected at IoT hub

0 additional answers

Your answer