Each driver is enabled by a feature line (element) in the license file. Most of the drivers utilize the same attributes within that feature. For simplicity, these common attributes are discussed first, and any unique attribute specific to a particular driver or service will be discussed in that Driver types section.
<feature name="driver name" expiration="expiration date" device.limit="none" history.limit="none" point.limit="none" schedule.limit="none" parts="AX-DEMO">
The various "limit type" attribute values can be either "none" or a numerical (limit) value, for example device.limit=32. Note that a limit value of none means unlimited, whereas a limit value of 0 means none allowed. Although most drivers include all the attributes shown in the feature line above, some attributes may
not apply to a specific driver, with the exceptions of point.limit and device.limit attributes, which typically do apply to any driver.For example, none of the Modbus-related drivers have any history or schedule
import/export capability, due to the simplicity of the Modbus protocol. Therefore, "history.limit" and "schedule.limit" attributes have no importance in the feature line of those drivers.
Feature name of the driver, often the same as the actual module (.jar file) name, for example bacnet, lonworks, etc.
Each driver has an expiration date which is typically the same as the expiration property of the license feature. In some cases such as beta testing agreements, individual drivers may be set to expire where the main license file is non-expiring.
This attribute designates a license limit on the number of devices which may be added to this specific driver network in the station database. Above this limit, any added device component (and all its child components) will be in fault.
This limit has no impact on the actual physical limitation of a field bus. For example just because the lonworks feature is set to device.limit="none", this does not mean that you can exceed the normal limit of 64 devices per segment.
This attribute limits the number of NiagaraAX histories that can be imported from remote histories (logs or trends) into the station's history space, and/or exported from station histories to appear as histories in remote devices. Above this limit, any added history import descriptor (or history export descriptor) will be in fault, and the associated import/export will not be successful.
This attribute designates the maximum number of proxy points that may be added to the station database for a particular driver. Above this limit, any added proxy point will be in fault.
This attribute limits the maximum number of NiagaraAX schedules that can be imported from remote schedules into the station’s database, and/or exported from station schedules to appear as schedules in remote devices. Above this limit, any added schedule import descriptor (or schedule export descriptor) will be in fault, and the associated import/export will not be successful.