3 backward compatibility, Table 4-1, Backward compatibility matrix – Artesyn System Management Interface Based on HPI-B (Centellis 2000 R3.0/4411) User's Guide (June 2014) User Manual
Page 42: Using hpi-b
 
Using HPI-B
System Management Interface Based on HPI-B (Centellis 2000 R3.0/4411) User’s Guide (6806800P20C)
42
4.3
Backward Compatibility
This section describes the various aspects that HPI-B user should make a note while migrating 
from HPI-B 02.01 based applications to HPI-B 03.02, or in using the HPI-B 02.01 applications 
with the HPI-B 03.02 daemon. The following points could impact existing HPI-B client 
applications.
Some management instruments and resources that were mandatory in SAIM-HPI-
B.01.01-ATCA are either made optional or removed in the latest specification.
Some of the RDR data has been modified to better describe the management instruments 
in this specification. This modification includes changing entity paths, sensor types, and 
control output types on various management instruments. HPI-B user applications 
compliant to HPI-B 02.01 specification will receive data as per the B03.02 xTCA mapping 
specification. These applications need to be modified to interpret the data correctly.
The symbolic names of all defined values are changed. A user program compiled with 
previous header files should still be usable with HPI library implementations that are built 
using the new symbols defined in this specification. We have taken care of this part by back 
porting the Xtca prefix to Atca Prefix.
Following table describes the backward compatibility:
 It is recommended for the user to note the differences in the specification and then modify 
the client applications suitably.
Table 4-1 Backward Compatibility matrix
HPI-B Daemon version
HPI-B Library version
Compatibility
B.03.02
B.02.01
Yes, functionality as B.03.02 daemon specs 
compliance. Refer to the backward 
compatibility notes in the Mapping 
specification.
B.02.01
B.03.02
Yes, Only B.02.01 functionality.