• State Not Answered
  • Replies 4 replies
  • Subscribers 3 subscribers
  • Views 710 views
  • Users 0 members are here
Options
Related

Hi Everyone, At present, we are keen on exploring the potential to extend the PI System's functionality to enable remote monitoring of waveform and sub-second data from our Bently Nevada System 1 using the OPC UA Protocol. Please help with below detail

Lam Tran Huu

1) I concern is whether the PI System can seamlessly interface with the Bently Nevada System 1 through the OPC UA Protocol.

2) The core requirement for our project is to be able to capture and store waveform data with sub-second granularity. Does the PI System offer the necessary capabilities to effectively capture and store such high-frequency data for subsequent analysis?

3) To connect with the Bently Nevada OPC UA server and collect spectrum data, do I simply require a PI interface PC with the OPC UA Connector installed? Are there any additional components or considerations that we should be aware of to ensure successful data transmission to the PI server?

If any members have practical use cases or best practices related to remotely monitoring sub-second waveform data via the PI System and OPC UA Protocol, I would greatly appreciate your insights and recommendations. I have attached a Bently Nevada Document about OPC UA for reference.

 

Parents
  • 0

    The PI system supports sub-second timestamps. However, there is a limit to the precision. Depending on your use case it could be enough or not.

    KB Article:

    What is the precision of subsecond timestamps:

    In memory, sub-seconds are limited to a maximum of 2 bytes (16 bits). Therefore, one bit represents 1/(2 ^16) = 1/65536 seconds, or 15.2587890625 microseconds.

    When we scale down the bytes usage to 2 bytes we transform the sub-seconds portion to an unsigned integer first, do some rounding and then we transform it back to double. With PI 3's rounding technique, the error is distributed between 0 and 15.3 microseconds. This means that the PI Data Archive always stores a timestamp that is equal to or slightly higher than the passed timestamp.

     

     

    Personally, I don't really think that it makes a lot of sense to store that kind of super high frequency data in the PI System as a normal tag/PI Point.

Reply
  • 0

    The PI system supports sub-second timestamps. However, there is a limit to the precision. Depending on your use case it could be enough or not.

    KB Article:

    What is the precision of subsecond timestamps:

    In memory, sub-seconds are limited to a maximum of 2 bytes (16 bits). Therefore, one bit represents 1/(2 ^16) = 1/65536 seconds, or 15.2587890625 microseconds.

    When we scale down the bytes usage to 2 bytes we transform the sub-seconds portion to an unsigned integer first, do some rounding and then we transform it back to double. With PI 3's rounding technique, the error is distributed between 0 and 15.3 microseconds. This means that the PI Data Archive always stores a timestamp that is equal to or slightly higher than the passed timestamp.

     

     

    Personally, I don't really think that it makes a lot of sense to store that kind of super high frequency data in the PI System as a normal tag/PI Point.

Children
No Data