JACE hardware features

Alphabetically, JACE hardware license features listed here include dataRecovery, ibmj9j2me. maxheap, mstp, ndio, nrio, serial, and sunj2se.

dataRecovery

Starting in AX-3.6 for QNX-based JACE platforms, this feature licenses a station’s DataRecoveryService, sourced from the JACE’s platDataRecovery module. This service is required to support installed SRAM (Static RAM), whether integral “onboard SRAM” (such as for a JACE-6E or JACE-3E) or a different JACE model with an installed SRAM option card.

<feature name="dataRecovery" expiration="never"
parts="NPB-SRAM">

ibmj9j2me

Starting in AX-3.5 for QNX-based JACE platforms, this feature licenses the IBM J9 Java virtual machine (VM) to be able to run on the controller, if applicable. The “rev” attribute reflects the version number of the J9 VM, as found in its version.xml file. Note starting in AX-3.6, some JACE controllers run the (Oracle) Sun Hotspot VM instead, and so require another sunj2se feature.

<feature name="ibmj9j2me" expiration="never"
rev=”2.3” parts="VM-J9">

maxheap

This feature determines the maximum size of the Java heap for either a JACE-2 or JACE-6 series controller. In the absence of this feature, the maximum heap size is limited to 16 MB for a JACE-2, and 48 MB for a JACE-6. When this license feature is present, the maximum heap size is limited to 48 MB for a JACE-2 and 96 MB for a JACE-6. The feature may not be available on all JACE-2 controllers, earlier models were manufactured with 64 MB RAM chips. Verify the amount of physical memory in a JACE-2 before attempting to order the memory upgrade option.

<feature name="maxHeap" expiration="never"
parts="NPM-128">

mstp

This feature determines how many of the available serial ports may be used for BACnet MS/TP communications. Note that features bacnet and serial must also exist in the license file.

<feature name="mstp" expiration="never" port.limit="5"
parts="DR-MSTP-AX"/>
port.limit

port.limit="5" - This specifies the number of serial ports which may be used for MSTP communications. Typically this number matches the number of physical ports. Some JACE controller models have option card slots, if additional serial cards are added then the port limit may be less than the number of physical ports if the port activation has not been ordered as well.

ndio

This feature enables the NDIO (Niagara Direct Input Output) driver, required to configure and use a JACE controller's Ndio-type I/O modules. Not all JACE controllers support such I/O modules (which attach/chain directly to the controller, using 20-pin connectors); refer to specific JACE controller data sheets to confirm whether this is an available option. Note that in the ndio features line (below), a “device” equates to an “Ndio Board”, and that history and schedule limits have no practical application.

<feature name="ndio" expiration="never"
device.limit="none" history.limit="none" point.limit="none"
schedule.limit="none" parts="DR-NDIO"/>

Refer to the NiagaraAX NDIO Guide for related details.

nrio

This feature enables the NRIO (Niagara Remote Input Output) driver, required to configure and use a JACE controller's Nrio-type I/O modules and/or the onboard I/O of a JACE-x02 Express (M2M JACE) controller. Most QNX-based JACE controllers support NRIO modules (which communicate via RS-485). Refer to specific JACE controller data sheets to confirm whether this is an available option. Note that in the nrio features line (below), a “device” equates to an “Nrio16Module”, and that history and schedule limits have no practical application. See Driver Feature Attributes for related details.

<feature name="nrio" expiration="never"
device.limit="16" history.limit="none" point.limit="none"
schedule.limit="none" parts="DR-NRIO"/>

Refer to the NiagaraAX Nrio Guide for related details.

serial

This feature enables the use of JACE serial ports for various drivers, for example aapup or modbusAsync. Note that the JACE license needs this serial feature in addition to any specific driver feature. Only one serial feature line is needed, regardless of number of serial-based drivers. Note that in the case of a JACE used for BACnet MS/TP, it would require this serial feature and driver features bacnet and mstp.

<feature name="serial" expiration="never"
parts="AX-DEMO"/> 

sunj2se

Starting in AX-3.6 for some QNX-based JACE platforms, this feature licenses the (Oracle) Sun Hotspot Java virtual machine (VM) to be able to run on the controller, if applicable. The “rev” attribute reflects the version number of the Hotspot VM, as found in its version.xml file. Note some JACE controllers must run the IBM J9 VM instead, and so require a different ibmj9j2me license feature.

<feature name="sunj2se" expiration="never"
rev=”5” parts="VM-SUN">