MxVDiff

The token charge for MxVDiff is 2 tokens.

MxTransIt

The token charge for access to all MxTransIt functions is 8 tokens.

MxVDev

The token charge for access to all MxVDev functions is 14 tokens. You can reduce the charge by using Read-Only or Edit-Only access. See Controlling Token Usage.

RapiCover Express

The token charge for RapiCover Express is 4 tokens.

Transforms

Charges can increase depending on which Transforms you use in your Test Harness. The token charge for each Transform is listed in the Toolbox in MxTransIt, except as listed below:

dSPACE: The token charge for the dSPACE Transform is: 15 tokens for the first instance, 0 tokens for subsequent instances.

Custom Transforms: The token charge for Custom Transforms is: 3 tokens for the first Transform, 0 tokens for subsequent instances.

MxVMC: The token charge for the VMC is: 0 tokens for the first instance, 6 tokens for each subsequent instance.

AUTOSAR VMC: Every instance of the VMC that uses code generated by the MxSuite from an ARXML file incurs a charge of 4 additional tokens.

Examples (14 tokens are required for MxVDev):

·1 AUTOSAR VMC costs: 14 + 0 + 4

·2 AUTOSAR VMCs cost: 14 + 6 + 0 + 4 + 4

·3 AUTOSAR VMCs cost: 14 + 6 + 6 + 0 + 4 + 4 + 4

Related Topic:

Controlling Token Usage