Applies to IPA, all ACR7xxxx and ACR9xxx products, and the discontinued Aries-CE.
There are several reasons your HMI or GUI may not be able to access the ACR language user parameters P0 - P4095.
First, user parameters P0 - P4095 do not exist by default in any of the ACR language products. These user parameters must be dimensioned in memory at the time your main configuration is done, typically via the ACR-View configuration wizard. If these are not dimensioned in memory then they do not exist in that particular project and cannot be accessed in that particular controller.
Second, these are 64 bit floating point user parameters. Many HMI drivers (like Interact Xpress and InteractX) only support 32 bit data types so you may be able to access smaller values and then get bad responses if the values are larger. We recommend using P39168 - P39423 which are 32 bit float data type or P38912-P39167 which are long data type and have the added advantage of being non-volatile in most of the ACR controllers.
Finally, your HMI driver or GUI may be doing direct memory access via the binary host protocol that the ACR language supports (PEEK and POKE functions). The recommended procedure for this is out-lined in the ACR Programmer's Guide in the Binary Host Interface chapter. ACR Programmer Guide
The address for a particular parameter should be requested before attempting to PEEK or POKE information. If the address is returned as zero then the particular parameter or local array is not dimensioned. Also, the actual address locations of specific parameter groups (such as the user parameters P0 - P4095) may vary from product to product or revision to revision so hard coding these addresses can lead to problems.
For example, the P0 - P4095 parameters reside in different memory locations between the ACR9xx0 controllers, Aries-CE drive/controllers, and IPA drive/controllers.
Interact Xpress HMI Interact X HMI Red Lion HMI
IPA04-HC IPA15-HC AR-04CE AR-08CE AR-13CE ACR9000 ACR9030 ACR9040 ACR9600 ACR9630 ACR9640
glh 4/2017
