All code that is added to this field will be written to the PlatformConfigApp configuration header file without any changes. This can be used to add custom defines or constants.

Note: This field must contain valid code in the configured target language.

Note: See the Imt.Base API Documentation for more details.

Callback (A)

When this checkbox is checked, the code generator will add a Custom assert handler to the callback folder (see Source Code Paths). This allows the developer to define custom assert handling.

See the Imt.Base API Documentation for more details.

Custom Defines (A)

All code that is added to this field will be written to the DiagnosticsConfigApp configuration header file without any changes. This can be used to add custom defines or constants.

This field must contain valid code in the configured target language.

See the Imt.Base API Documentation for more details.

Custom Implementation (A)

Use Runtime Statistics

When this checkbox is checked, the code generator will add a FreeRunningTimer and StatisticsCalibration file to the Statistics folder (See Source Code Paths). This allows the developer to add the required user code to use the Statistics Feature of the DATAFLOW runtime.

In addition, the project generator will add a Statistics configuration to the generated IDE project.

Use Small Event Buffer

Custom Idle Callback (A)

When this checkbox is checked, a Idle Callback is generated to the Callbacks folder (see Source Code Paths). This allows the developer to implement a custom behaviour when the Runtime has no work to do.

For more information see the DATAFLOW Runtime API Documentation.

Custom Event Pool Capacity Callback (A)

When this checkbox is checked, an Event Capacity Callback is generated to the Callbacks folder (see Source Code Paths). This allows the developer to discard events when the event pool reaches a high water mark.

For more information see the DATAFLOW Runtime API Documentation.

Tick Length (A)

Event Pool Size

This field defines the number of events allocated in the static event pool.

This value must be defined based on the developed application and can not be automatically determined.

Event Size (A)

This field defines the number of bytes allocated for each event in the event pool.

Note: This value can be automatically generated from the model when the checkbox is set. To set a manual value, uncheck the checkbox.

The automated value is defined by the largest protocol size in the generated model.

Small Event Pool Size

This field defines the number of events allocated in the static small event pool.

This value must be defined based on the developed application and can not be automatically determined.

Small Event Threshold (A)

This value defines the threshold for events to be added to the small event pool. All events above this threshold will use the regular event pool.

Note: This value can be automatically generated from the model when the checkbox is set. To set a manual value, uncheck the checkbox.

The automated value is defined by the smallest protocol size in the generated model.

Executable Pool Size (A)

This field defines the maximal number of active parts (executables) the application can use.

Note: This value can be automatically generated from the model when the checkbox is set. To set a manual value, uncheck the checkbox.

The automated value is defined by the number of active parts in the generated model.

Timer Pool Size (A)

This field defines the maximal number of timers the application can use.

Note: This value can be automatically generated from the model when the checkbox is set. To set a manual value, uncheck the checkbox.

The automated value is defined by the number of timers in the generated model.

Buffer Pool Size (A)

This field defines the maximal number of buffers the application can use.

Note: This value can be automatically generated from the model when the checkbox is set. To set a manual value, uncheck the checkbox.

The automated value is defined by the number of buffers in the generated model.

Default Stack Size (A)

This value defines the default stack size allocated for an active part. An individual stack size can be defined for each active part in the model. This value is only used for runtime that do not use a single stack (RTOS Runtime).

This value must be defined based on the developed application and can not be automatically determined.

This value defines the number of remote frames in the frame pool. The required number of frames must be adjusted to the user code. Each remoting stack used requires 2 frames (one for send, one for received) per layer. A typical value for one active part with send and receive on 3 layers (physical, framing, CRC) would be 6.

Note: See Imt.Base API Documentation for more details.

The field defines the maximal size for a remote object sent over the serial connection.

Note: This value can be automatically generated from the model when the checkbox is set. To set a manual value, uncheck the checkbox.

The automated value is defined by the largest protocol size that has the 'Is Remote Object' property checked.

This field defines the maximal number of remote objects that can be registred.

Note: This value can be automatically generated from the model when the checkbox is set. To set a manual value, uncheck the checkbox.

The automated value is defined by the sum of protocols that have the 'Is Remote Object' property checked.