Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Heartbeat not working in newer versions of OPC Publisher #1133

Closed
ajithkumars opened this issue Apr 29, 2021 · 9 comments
Closed

Heartbeat not working in newer versions of OPC Publisher #1133

ajithkumars opened this issue Apr 29, 2021 · 9 comments
Assignees
Labels
bug Something isn't working

Comments

@ajithkumars
Copy link

We are currently using full Industrial IOT deployment version 2.7.183. And this bug/issue concerns opc publisher.
Heartbeat does not work as we expect it to work, i.e, static values are not read in every hearbeat interval.
We tested different versions to be sure:
2.5: Works
2.6: Works
2.7: Does not work
2.7.183: Does not work
2.7.206: Does not work (latest version)

Steps to reproduce the behavior:

  1. Deploy Industrial IOT (2.7.183)
  2. Add an edge device.
  3. Add opc publisher with heartbeat interval set (also has a opc server it can read from)
  4. Depoy different versions of the pulisher itself to check it works differently

Expected behavior
When heartbeat interval for example 10 seconds is set, publisher should retrieve even static data (data that does not change)
every 10 seconds and send to IoTHub.

Edge running on

  • OS: Ubuntu 20.04 Desktop (Running on VM)
@hansgschossmann hansgschossmann added the bug Something isn't working label May 4, 2021
@koepalex koepalex self-assigned this Aug 19, 2021
@koepalex
Copy link
Contributor

Could you please share some more details? I've just tested it with iot-edge-opc-plc with 60 nodes and it worked.

@ajithkumars
Copy link
Author

Which version did you test ?

@koepalex
Copy link
Contributor

2.8.0 (LTS)

@ajithkumars
Copy link
Author

ajithkumars commented Aug 20, 2021

Right, as mentioned in the issue all those versions that were tested were older. So, its great that it is fixed in the new version (if it is)

@koepalex
Copy link
Contributor

Just for my understanding. I just tested standalone (because you mentioned 2.5 and this is only available for standalone). Your testing of 2.6/2.7 was in standalone or orchestrated mode (as part of Industrial IoT Platform) ?

@ajithkumars
Copy link
Author

ajithkumars commented Aug 20, 2021

It has been a while now, but I think as described it was evaluated as a part of the orchestrated mode.

@koepalex
Copy link
Contributor

I've tested also 2.8 in orchestrated mode and it works now.

@ajithkumars
Copy link
Author

Thank you, I will look into it.

@koepalex
Copy link
Contributor

I will close the issue because it worked in 2.8 release, please reopen if necessary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants