AVEVA™ PI System™ Feedback Portal

Welcome to our new feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Add a new idea Subscribe
Status Declined
Product PI Interfaces
Categories PI Interfaces for Modbus
Created by Clint Ramsey
Created on Aug 18, 2022

RELATED IDEAS

Modify the Modbus Interface to accept 32-bit Unsigned Ints from the PLC

provide a data type to accept a 4 byte unsigned integer from the PLC.  At this point, it would be stored in a 64-bit float in PI DA.
  • ADMIN RESPONSE
    Aug 18, 2022
    Thank you for your feedback. We do not plan to add native support for 32-bit Unsigned Integers to PI Interface for Modbus Ethernet PLC. Please check out the workaround provided in the comments below.
  • Attach files
  • Mario Amrhein
    Reply
    |     Mar 29, 2023

    Same here: our Powermeter device disallows to ask for a single register when the actual datatype is 2 registers long (e.g. INT32U). So the workaround doesn't work in any case.

  • Guest
    Reply
    |     Aug 18, 2022
    I was just working with a customer to read uint32 tags from the Modbus interface. We were successful in using Clint's workaround from PISquare here: https://pisquare.osisoft.com/message/78622-re-pi-modbuse-4-byte-unsigned-integer-uint32#comment-78622 Briefly, the workaround involves reading the first 16-bits and last 16-bits as separate uint16 tags (modbus interface data type 11). Then using Performance Equations or Analytics to combine the values with the following formula: float64 = highPoint*65536 + lowPoint. Hopefully this helps others. Native support would be great!
  • Guest
    Reply
    |     Aug 18, 2022
    This only works if you can read the 2 x 16bit registers separately, I have a device that disallows reads from the second word of the 32bit unsigned int, currently I can use a 703 read and hope I never see the sign bit tripped. I'd prefer native support for 32 bit unsigned intergers as am about to roll out a heap of PV inverters which the majority of registers are 32UINT and as above they refuse to allow 2 16bit reads.