WonderWare InBatch - change phase state logic when a phase end event occurs at the same time as phase start event
When a phase end event is received at the same time as a phase start event, the WWInBatch interface currently creates batches/event frames of zero duration despite there being phase state events under the phase event.
It would be helpful if the interface logic is updated so that either:
the phase end time is updated to the timestamp of the most current phase end event
or ignore phase end events that happen at the same time as phase start events.1 vote
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.1 vote
Make UserID and ReviewerID available from BatchQuestion table for PI Interface for Wonderware InBatch
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.1 vote
As a Batch Framework Interface user, I would like to filter my batch data by whitelisting. Currently the only option is blacklisting. This is inconvenient, for example, if data is only desired from a few units. Each time a new unit is added to the data source, the interface configuration must be updated.0 votes
Batch Framework Interfaces - [TIME] and [TIMESTAMP] placeholders should consider whether TS=LCL is configured (meaning the interface is processing incoming events as Local Time). Currently, values of these placeholders always show up as GMT timestamps.0 votes
- Don't see your idea?