PI Connectors
Welcome to the
PI Connectors feedback page!
We created this forum to hear your ideas, feature suggestions and feedback on PI Connectors. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.
Please note that your ideas and comments posted here are visible to all other users.
- For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal (https://my.osisoft.com) instead of sharing them on this site.
- For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.
-
PI Connector for MQTT - support more generic JSON formats
While the existing support for Sparkplug MQTT format is helpful, this connector would be more useful if it also supported a more generic JSON format.
1 vote -
Redfish - Allow port selection from the DCM UI
When configuring the PI Connector for Redfish, it will default to port 443 for the target Redfish Server. Servers are commonly installed on custom ports. Currently, the port needs to be manually edited in in DataSource.config.json.
1 vote -
Distribute-Broadcast-To-Network broadcast for Discovery Tool and Connector
When running the discovery tool from a subnet with no BBMD to query BACnet devices on a separate subnet, it seems like the auto discovery tool is seen as a ‘foreign device’, so the devices do not respond correctly.
When analyzing a Wireshark trace, the discovery tool sends an ‘Original -Broadcast-NPDU’ Who-Is request to the BBMD on the other network, because it is seen as a foreign device, the request is not forwarded onto the sub-devices by the BBMD on this separate subnet. We can see that no I-am requests are sent back to the discovery tool.
As the discovery…
2 votes -
OPC UA: Set PI Tag Zero and Span Based on OPC UA Range
For OPC UA Analog Items, the OPC UA standard mandates an EURange property and an optional InstrumentRange property. These Range properties contain a Low and High field.The PI Connector for OPC UA should have an option to use either of these Ranges to set the Zero and Span of the PI tags it creates and the Maximum and Minimum AF Attribute Traits.
9 votes -
Auto discovery on a separate subnet (as foreign device)
When running the discovery tool from a subnet separate from the BBMD and BACnet devices, it seems like the auto discovery tool is seem as a ‘foreign device’, so the devices do not respond correctly. There is no BBMD on the subnet the connector is on.
When analyzing a Wireshark trace, the discovery tool sends an ‘Original -Broadcast-NPDU’ Who-Is request to the BBMD on the other network, because it is seen as a foreign device, the request is not forwarded onto the sub-devices by the BBMD on this separate subnet. We can see that no I-am requests are sent back…
1 vote -
New function for Ethernet/IP (“scanner”)
Add the function to able to act as (“scanner”).
At this moment the connect can only act as an adapter, that means that It can't collect data from other device that also are connector is an adapter.
https://www.odva.org/Technology-Standards/EtherNet-IP/Overview7 votes -
Customer is seeking WW connector to collect data from WW historian but with same naming convention of existing tags
Customer is seeking WW connector to collect data from WW historian but with same naming convention of existing tags.
Existing tags were reading from "FxBias interfaces" and in need to let them read from WW historian thru WW connector.
WW connector is reading names from WW historian and force the names as per WW historian.
can we rename WW connector created tags to be as per existing tags or not?
also about compression and exception settings, can we keep existing settings or we must follow WW connector settings only?
1 vote -
OMF Support PI Connector Relay
Keep the OMF support in PI Connector Relay, also add the new OMF Versions to it not just only OMF 1.0. Not just leave the OMF support to the PI WebAPI. In many customer scenarios, the PI Connector relay is a much more robust solution than PI WebAPI.
1 vote -
Develop PI Connector for AspenTech IP21 for the PI System and OCS
We have customers who are using AspenTech IP 21 and would like to have data replicated in both PI DataArchive and OCS in the future. Since the PI Interface is a bit outdated, a new PI Connector would make perfect sense (since there is already a PI Connector for WonderWare and Honeywell PHD). The PI Connector shall support both PI and OCS.
10 votes -
PI Connector for Beckhoff TwinCat
Develop a connector for Beckhoff TwinCat
4 votes -
PI Connector for Jason/GBP - Ford Connected Car
Develop a connector for Jason/GBP - Ford Connected Car
0 votes -
PI Connector for OSII EMS
Develop a connector for OSII EMS
0 votes -
PI Connector for SKF Vibration Monitoring
Develop a connector for SKF Vibration Monitoring
1 vote -
PI Connector for SPPS
Develop a connector for SPPS
0 votes -
PI Connector for Yokogawa Exaquantum Batch
Develop a connector for Yokogawa Exaquantum Batch
0 votes -
PI Connector for AMQP
Develop a connector for AMQP
0 votes -
PI Connector for Azure ML Web Service
Develop a connector for Azure ML Web Service
2 votes -
PI Connector for EDNA
Develop a connector for EDNA
1 vote -
PI Connector for Ex-passport ABB
Develop a connector for Ex-passport ABB
0 votes -
PI Connector for GE MARK 5 and MARK 6
Develop a connector for GE MARK 5 and MARK 6
0 votes
- Don't see your idea?