In most cases, a kitControl conversion object takes an input value and makes it available on the object’s output as a different data type. Prior to AX-3.6, you typically use them as a “go-between” to allow linking between different data types.

For example, you use a conversion object to allow a link between a:

Starting in AX-3.6, in most cases you no longer need conversion components. Instead, you simply link directly between component slots of different data types, and a “conversion link” is automatically made. Sometimes, further editing of such a link is also possible. For complete details, see the Engineering Notes II document NiagaraAX Conversion Links. Also starting in AX-3.6, all of the “Status value to simple value” components in kitControl were extended with optional properties. See the Status value to simple value section for details.

Also, a NumericUnitConverter is available. It is unique in that it does not change the data type (both input and output are StatusNumeric), but changes the actual numeric value, based upon unit conversions going from the configured “In Facets” to “Out Facets.” To produce a valid output, you must configure both facets to be under the same category (such as temperature or power, as examples). Otherwise, the NumericUnitConverter has a fault status.