per the OPC DA 2.x spec, the OPC server will call us back for all points that have a changes; even those points where we are polling.
We have a switch to disable the callbacks for points that are not set to advise: /DC
Can we make that the default?!6 votes
The pitopi.ini file is used by the pitopi interface for collecting data from multiple sources and to save other miscellaneous settings such as 'histonly' flags. The configuration ini file uses sections to separate settings between instances with and the format is [PItoPI-<ID>] and this is not unique enough to distinguish settings between different instances that use the same instance ID but with a different point source. So when there are two instances with the same ID (regardless of the Point Source), any changes made to one instance will affect the other instance too.
Note: This was previously Enhancement 121629.6 votes
Add an option to encrypt trafic between interfaces/connectors and the PI Data Archive5 votes
My OPC server's items have the OPC server node name included in the itemID, for example: serverA.AB_1234.PV. I have redundant OPC servers and redundant interfaces (in failover) and would like the tags to refer to the correct OPC address including when the OPC servers fail over. Currently the workaround is to create two sets of tags, each pointing to one OPC server's itemIDs in their instrument tags and then merge the data with AF or a PE.5 votes
CA ISO Interface - Allow conversion of timestamp values (i.e. InstructionStart) from UTC to local time
Currently, the interface does not have any means to convert timestamp values (i.e. not the actual timestamps corresponding to values), such as InstructionStart, to account for timezone differences. Therefore, the timestamps have to be manually adjusted to account for timezone differences once it reaches the archives.
Having to manually adjust the timestamp causes issues further down the line, such as with PItoPI, and creates unnecessary overhead in AF to do said conversion.5 votes
The IEEE specification of the IEEE C37.118 protocol does not specify if analog data should be singed or unsigned for 16-bit integers. The currently the PI Interface for IEEE C37.118 represents these values as exclusively unsigned. Both types should be configurable in the interface5 votes
SNMP Interface to support using multiple types of encryption such as DES, 3DES, and AES-128 bit, AES-192 bit, and AES-256 bit.
SNMP Interface should support using multiple types of encryption such as DES, 3DES, and AES-128 bit, AES-192 bit, and AES-256 bit.5 votes
When run in delete mode for WWInBatch interface, it uses the data source as the system of record--any open batch in SQL will be deleted. However, as abandoned or done batches are open in WonderWare but closed in PI, the interface may delete batches in PI that are still open in the source. It would be helpful if the interface gave the option of using PI as the system of record regarding batch end times.5 votes
To enable us to move from PIBAGEN to EF Gen interface, we need 'merge consecutive' to work when running in PIBAGEN mode. Currently none of this functionality is working, and the following known issues is already found.
119695 - Merge consecutive at unit procedure level does not merge all consecutive unit procedures.
124407 - Unit Procedures may be improperly merged in PIBaGenCompatibility mode.
119363 - Consecutive subbatches can get merged incorrectly
Please make an updated version of the 'PI Event Frames Generator' where this important functionality is working.5 votes
The next version of EFGen will more closely mimic PIBaGen when running in PIBaGen compatibility mode.
PI APS is now not able to rename a PI Point name. If the item name is changed on the Datasource side we wish that APS rename the Pi Point.5 votes
When the PI RDBMS Interface gets a bad timestamp from the source RDB that it cannot coerce into a PI Timestamp, the actual bad timestamp received from the RDB should be logged as part of the error message.
This would coincide with the following error:
"pitm_settime() error - 15002. Using current time."5 votes
Currently there is no way to send corrected values to the OPC DA Server since they are triggered by snapshot. It would be useful if there was a way to alter the values that get sent in case there are substituted/replaced values.5 votes
Add a watchdog counter or something similar into the shared memory header. If the counter fails to update, initiate UFO.
If PIBufSS crashes, data loss can occur. implement something that allows UniInt to know that the Buffer Subsystem is not responding and initiate failover if available.
This was previously enhancement 119481.5 votes
AutoPointSync for OPC DA does not install or run correctly on 64bit servers. As most new servers are 64bit this would seem to be an essential capability.5 votes
SNMP: Throttle scan specific informational messages as the interface may fill up logs every scan frequency
This is for SNMP version 126.96.36.199, the following message is printed every scan frequency:
"Scan class <scan class number> for device <IP address> will be skipped due to previous pending requests"
And this needs to be throttled as the logs may be get filled up quickly with this type of messages.
Note: This was previously Enhancement 124938.5 votes
whenever the OPC server undergoes any restarts or configuration changes, the OPC interface will delete all old connections, groups, etc. and it will establish a new connection to the OPC server, loading all ItemID's etc (as if it is an automatic restart of the interface).
The reason for this enhancement request:
if OPC server is restarted or undergone configuration changes, all the handles and subscriptions for advise tags are not valid anymore. The interface would get the advise values in an inconsistent manor (values betwen the OPC server and the interface would show a mismatch)4 votes
Currently (as of PI to PI Interface AutoPointSync Connector Version 188.8.131.52), it's not possible to sync changes to "Point type". (See pg 5 of user manual).
Please make this possible in a future release.4 votes
Smart Connector foo DeltaV should let user configure some default attributes for tags created:
- User should be able to define what the default point security should be
- User should be able to decide if tags should be created as Poll or Advise4 votes
As a PI Admin, I may have already created a AF Element Hierarchy corresponding to my BES or MES source data. Therefore I have no need for the interface to create a new AF Elements and I would like to suppress this completely.4 votes
- Don't see your idea?