@BrandonRiley-j2x support.industry.siemens.com/cs/document/109818073/s7-1500-opc-ua-server-self-diagnostics?dti=0&lc=en-WW I would use the timestamps as the basis as there are a few ways. I assume you mean for the OPC Server side because the client side is quite easy to evaluate. Clock Bytes or Timestamps: You can use either clock bytes or timestamps as a basis. Clock bytes are easy to work with, and there’s a checkbox for them in the OPC server. However, consider using more strategic OPC UA timestamps for better alarm functionality. Client Timestamps: The client can also add timestamps (like DTL, DATE, and TIME) to the OPC Server system. It evaluates these timestamps internally. TIA Portal v18 or higher: If you’re using TIA Portal v18, Siemens introduced an internal “loopback" for the server without having to make a client setup. This lets the server see its own diagnostics data. You can query something like the timestamp updates and other details from the client on the server's namespace. I modified that app note link above for this purpose, and it worked well. In either of the cases, for the client this is easy and included in a timestamp, but from the server, it's going to require a call to code. Best of luck with your endeavors.
Where would you go about setting up a heartbeat connection
@BrandonRiley-j2x
support.industry.siemens.com/cs/document/109818073/s7-1500-opc-ua-server-self-diagnostics?dti=0&lc=en-WW
I would use the timestamps as the basis as there are a few ways. I assume you mean for the OPC Server side because the client side is quite easy to evaluate.
Clock Bytes or Timestamps: You can use either clock bytes or timestamps as a basis. Clock bytes are easy to work with, and there’s a checkbox for them in the OPC server. However, consider using more strategic OPC UA timestamps for better alarm functionality.
Client Timestamps: The client can also add timestamps (like DTL, DATE, and TIME) to the OPC Server system. It evaluates these timestamps internally.
TIA Portal v18 or higher: If you’re using TIA Portal v18, Siemens introduced an internal “loopback" for the server without having to make a client setup. This lets the server see its own diagnostics data. You can query something like the timestamp updates and other details from the client on the server's namespace. I modified that app note link above for this purpose, and it worked well.
In either of the cases, for the client this is easy and included in a timestamp, but from the server, it's going to require a call to code.
Best of luck with your endeavors.
Thank you. Very good explanation. Short and clear.