the ability to disable the timezone adjustment.

currently we are calculating daily kpis on our global pi server. with PItoPI we are sharing it to the site pi-servers.
so the daily kpi for e.g. 1st januar 2019 00:00AM sould alwas have that timestamp. Because if the forward it to e.g. britain, it has the timestamp 31st decemper 2019 11:00PM (adjusted -1h to austrian time)

plz make it possible to disable it via Location2.

For a PI tag with a specific scan class, if no new value is collected by the PI Interface after a period of time (for example 2x the scan class) , the interface will add automaticaly the value "No Data". It will avoid the usage of a dedicated analyze for this, in the PI Server. And like that, the PI user will be aware of the issue, by using any PI Visualization tool.

Hi all,
 
i got to know this standard:
Standards – SiLA Rapid Integration
This standard is a really good approach to connect various types of lab equipment. Over it it is possible to fetch for example the RPM of a mixing device, temperature of a heater etc.
For my understanding, this screams loudly for a time series recorder with analytic options.
 
Thanks for your support
Thorsten

Currently the ODBC connection is configured with a SQL date time parameter when retrieving the TS parameter (snapshot time stamp).
Due to the fact lots of sources system having more precision in their time stamps, it makes it hard to compair source time stamp to the pi time stamp (precision and rounding issue in SQL).
I request to add support for sql datetime2 into the ODBC connection, or an option to read the time from the snapshot in seconds since 1.1.1970

/fd parameter is only used while performing real-time scan. If scan rate is set to a higher value such as a day, the user would need to wait for the first scan (after a day) to get future data. This should be done at interface startup. For use case see notes for Case # 895278.

I would like the ability for the PI Interface for OPC DA to retry writing data when it receives a CONNECTEADVISELIMIT error. Certain OPC servers return a CONNECTEADVISELIMIT error when write requests are received in quick succession, and having a setting to retry writing the data would be better than the current method of performing a restart of the service. The issue is exacerbated when the network is unstable.

Add the YouTube help videos that exist on the OSIsoft Learning channel to the "Help" section of ICU. For example, the UFL designer YouTube videos would appear alongside the corresponding documentation that should be accessible from ICU > Help > Interface Manual...

The PI Interface for Quindar SCADA should have an option to log all values and timestamps from the data source (Prior to any processing by UniInt) for a specified PI point.

I have a scan-based output point writing multiple PI values to the relational database as described here:
https://livelibrary.osisoft.com/LiveLibrary/content/en/int-rdbms-v4/GUID-1A194D2B-388B-4FD7-8B82-D85EDDBBC572

I would like to perform history recovery for such an output point, but this is currently not possible because the output point is scan-based:
https://techsupport.osisoft.com/Troubleshooting/KB/KB01139/

Since event-driven tags can have only one source tags, I cannot recover historical data from multiple PI tags with only one output tag.

There are some performance counters that are Date and Time based.

PI PerfMon tags have to be configured as Float32 or Int32 and at PI AF it has to be converted by using PI Analysis or Formulas. Would be easier to configure, maintenance and to build reports if there is a direct way.

For the SNMP Interface, the suggestion would be to have the interface output a .txt file that includes the SNMP devices that have lost connection with the interface. This could be useful when there is a high volume of SNMP devices that connect to the interface.

The health point names for the Read_Only 1.6.8.1 SNMP Interface have a different naming convention than the health points for Read-Write SNMP Interface 1.5.1.306. In order to keep monitoring consistent across version upgrades, the suggestion is to keep naming convention of the health points the same across versions.

PI EMDVB interface stops because of time difference between SQL and PI servers:

"Error, SQL Server is ahead of PI Server more than 30 seconds, please adjust clocks. "

That means we should adjust the (SQL server) DCS clock. However 30 seconds seems a short time to me.

I would like the PI Interface for EMDVB to have the ability to define the source system Time/TimeZone offset.

Currently if you attempt to create a service for a UniInt interface without a service ID you get an error message "Unknown Error" (see attached screenshot)

Generally review and improve error messages to be meaningful but also allow the creation of services without service IDs if the user wishes.

Currently UserID (DoneByUserID) and ReviewerID (CheckByUserID) cannot be read from the BatchQuestion table when using PI Interface for Wonderware InBatch. These fields are important to know who answered the question and who confirmed/checked the question.

I have been working with a customer who works with oil rigs and satellite networks and they requested that more external resources be available for how to efficiently operate PItoPI in a high latency environment. Currently there is only one internal document that may be out of date.

In the PI Interface of UFL we would like the option to suppress the message: "exception attributes corrected through the SDK read" for values of excmax larger then 9hrs.

Can you remove the restriction to use only an IP address in the BACnet Network Discovery Tool?  The interface will correctly load and poll tags to a network device referenced by name instead of IP, however the Discovery Tool has the limitation of being IP only.