Page History

The number of address table entries to be allocated for the device. If not specified, the IzoT Interface Interpreter computes a number based on inspection of your application's interface. Target xif supports up to 4095 addresses, cpm-4200 and cpm-4000 targets support up to 254.

This option is not supported with ShortStack, where the number of addresses is an intrinsic property of the chosen Micro Server that cannot be changed with IML.

The number of alias table entries to be allocated for the device. If not specified, the IzoT Interface Interpreter computes a number based on inspection of your application's interface. Target xif supports up to 8191 aliases, cpm-4200 and cpm-4000 targets support up to 127 aliases.

This option is not supported with ShortStack, where the number of aliases is an intrinsic property of the chosen Micro Server that cannot be changed with IML.

The api This option selects API features as a combination of the following:

0 (the default) selects the basic API
1 adds local query and update functions
2 adds local utility functions.

This option is only available with ShortStack.

Enables authentication for the device. The default is False.

This option is only available with cpm-4000 and cpm-4200 targets.

The requested minimum buffer size for all input and output buffers. The IzoT Device Stack allocates a buffer size equal to or larger than the requested number if possible, or fails to initialize if it cannot allocate  the requested buffer size. If not specified, the IzoT Interface Interpreter allocates buffers according to the size of the largest datapoint (plus required protocol  overhead). If a Tag object is declared, the IzoT Interface Interpreter  ensures that the minimum buffer size is at least 255 bytes.
 
Your explicit minimum buffer size request triggers warning 32 if it fails to meet the size required by the largest datapoint (and an allowance for protocol overhead). This warning becomes an error with the strict option.

This option is supported with the xif target. The dynamic option accepts the number of dynamic blocks and datapoints to declare with the generated interface file. Both default to 0 (zero). The sum of dynamic and static datapoints cannot exceed 4096, and the number of dynamic blocks cannot exceed the number of dynamic datapoints.

Example:

//@IzoT Option dynamic(blocks=100, datapoints=1000)

This option accepts a Boolean True or False to enable or disable explicit addressing support. The default is False.

This enables source addressing information for incoming messages and explicit addressing for outgoing application messages. Enabling this option enlarges the required data frame.

This option is only available with ShortStack targets. 

This option accepts a Boolean True or False to enable or disable support for interoperable self-installation (ISI). The default is False.

This option is only available with ShortStack targets.

This option specifies a namespace for use with runtime interface selection. It accepts an identifier that must match this regular expression: [A-Za-z_][A-Za-z_0-9]*

This option is only available with ShortStack targets.

This option can be used to affect the generation of external names for datapoints, as reported in the interface file (XIF) and the device's self-identification data. Valid values are "v1" and "v2". The default value is "v2".

• namestyle "v1" yields names that are compatible with earlier releases of IzoT Interface Interpreter
• namestyle "v2" yields names that meet IzoT CT expectations, which results in a cleaner user interface when using automatically-generated datapoint names in a drawing

Example:

//@IzoT Option namestyle("v1")

This option accepts a Boolean True or False to enable or disable neutral output. The default is False.

In neutral mode, the tool produces neutral time, data and version information in the generated output. This is useful when comparing output generated from different versions, as is the case during automated regression testing.

This option can also be enabled with the IzoT Interface Interpreter command line option --neutral

The base name of the output files generated by the IzoT Interface Interpreter. The generated file names are basename.c and basename.h.

The default base name is IzoTDev so the default output file names are IzoTDev.c and IzoTDev.h (for cpm-4000 and cpm-4200), and ShortStackDev.c, ShortStackDev.h for ShortStack. 

The option has no effect with target xif.

Specifies the global property implementation policy as one of datapoint or file. 

The option is supported for ShortStack and XIF targets. 

Selects a ShortStack Micro Server.

Example: 

//@IzoT option server("microserver/standard/SS430_FT6050_SYS20000kHz")

The option is supported for ShortStack and XIF targets. 

Specifies the service pin held notification interval, 0 to 31 seconds. Defaults to The default is 0.

The option is supported with ShortStack targets. 

The target platform for the application, one of: cpm-4000, cpm-4200, shortstack-classic, or xif.

Example:

//@IzoT option target("shortstack-classic")

Most IML options require that the target is specified before the option can be selected. It is recommended to declare the target option at the start of the IML declarations. 

Some installations of IzoT Interface Interpreter set the default value of this option to the target that matches the installation, but it is generally best to always declare the target. This ensures portability of the IML instructions between different installations.

This option can also be set with the IzoT Interface Interpreter command line option --target.

Enables verbose IzoT Interface Interpreter output. The default is False. 

This option can also be selected with the IzoT Interface Interpreter command line option --verbose.