Tools with stimulus support¶

Below is an overview of all tools that support the stimulation of test variables using Start Stimulus test step and Stimulus test step.

Overview of the stimulus capabilities of the tools¶

By default, ecu.test converts the stimulus into a tool-compatible format and also automatically converts the trace files referenced in the DataFileSegment of an STI file into a tool-compatible format. All trace formats readable by ecu.test are supported. The following table lists the restrictions for tools/ports that, for various reasons, do not benefit from this automatic conversion.

In addition, input signal assignments and input signals for StopTriggers are supported for STI files by default, unless explicitly stated otherwise in the table.

Tool / Port	Notes and restrictions
A&D: iTest Port MODELACCESS - DEFAULT	Restrictions: Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
ASAM: XIL Port BUSACCESS - GENERIC	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the generic bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
ASAM: XIL Port BUSACCESS - MODEL BASED	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the model based bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
ASAM: XIL Port MODELACCESS - DEFAULT	Restrictions: Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
dSPACE: ControlDesk Port BUSACCESS - BUS_MANAGER	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the generic bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
dSPACE: ControlDesk Port BUSACCESS - GENERIC	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the generic bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
dSPACE: ControlDesk Port BUSACCESS - MODEL BASED	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the model based bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
dSPACE: ControlDesk Port MODELACCESS - DEFAULT	DataFileSegment: An absolute path must be provided Only MAT and MF4 can be referenced SignalValueSegment: A relative path must be provided
dSPACE: ControlDesk Port SERVICEACCESS - SERVICE_MANAGER	The stimulation of ServiceEvent signals takes place via the model access and is only possible if this also supports the stimulation. The restrictions/comments of the model access also apply to the generic ServiceManager access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
dSPACE: XIL API Port BUSACCESS - BUS_MANAGER	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the generic bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
dSPACE: XIL API Port BUSACCESS - GENERIC	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the generic bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
dSPACE: XIL API Port BUSACCESS - MODEL BASED	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the model based bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
dSPACE: XIL API Port MODELACCESS - DEFAULT	Restrictions: Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
dSPACE: XIL API Port SERVICEACCESS - SERVICE_MANAGER	The stimulation of ServiceEvent signals takes place via the model access and is only possible if this also supports the stimulation. The restrictions/comments of the model access also apply to the generic ServiceManager access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
ETAS: BOA Port BUSACCESS - CAN	This port supports all features described in Stimulation control.
ETAS: BOA Port BUSACCESS - CAN-FD	This port supports all features described in Stimulation control.
ETAS: COSYM-SIL Port MODELACCESS - DEFAULT	Restrictions: Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Hirain: TestBaseVCI Port BUSACCESS - CAN	This port supports all features described in Stimulation control.
Hirain: TestBaseVCI Port BUSACCESS - CAN-FD	This port supports all features described in Stimulation control.
HMS: Legacy Bus Interfaces (VCI V2) Port BUSACCESS - CAN	This port supports all features described in Stimulation control.
HMS: Legacy Bus Interfaces (VCI V2) Port BUSACCESS - FLX	This port supports all features described in Stimulation control.
HMS: VCI V4 Port BUSACCESS - CAN	This port supports all features described in Stimulation control.
HMS: VCI V4 Port BUSACCESS - CAN-FD	This port supports all features described in Stimulation control.
Intrepid Control Systems: neoVI Port BUSACCESS - CAN	This port supports all features described in Stimulation control.
Intrepid Control Systems: neoVI Port BUSACCESS - CAN-FD	This port supports all features described in Stimulation control.
IPG: CarMaker\|RealTimeMaker Port ENVSIM	Only the following segments are supported: Constant segment Ramp segment (with start and end value) Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
MAGNA: BluePiraT Port BUSACCESS - CAN	This port supports all features described in Stimulation control.
MAGNA: BluePiraT Port BUSACCESS - CAN-FD	This port supports all features described in Stimulation control.
MAGNA: BluePiraT Port BUSACCESS - FLX	This port supports all features described in Stimulation control.
Mathworks: MATLAB & Simulink Port BUSACCESS - GENERIC	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the generic bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Mathworks: MATLAB & Simulink Port MODELACCESS	Stimulation is supported only for signals in the Simulink model. Parameters cannot be stimulated. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test.
MicroNova: NovaCarts Port MODELACCESS - DEFAULT	Restrictions: Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Modelica Association: FMI Port BUSACCESS - CAN	A prerequisite for a bus signal to be stimulated is enabling cyclic writing of the signal group containing the signal to be stimulated.
Modelica Association: FMI Port BUSACCESS - GENERIC	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the generic bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Modelica Association: FMI Port MODELACCESS	Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test.
MOTEON: MTB Port MODELACCESS - DEFAULT	Restrictions: Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
NI: VeriStand Port MODELACCESS	Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test.
Opal-RT: RT-LAB Port BUSACCESS - GENERIC	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the generic bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
PEAK: PCAN-Basic, PCAN-FD Port BUSACCESS - CAN	This port supports all features described in Stimulation control.
PEAK: PCAN-Basic, PCAN-FD Port BUSACCESS - CAN-FD	This port supports all features described in Stimulation control.
SAE: PassThru Port BUSACCESS - CAN	This port supports all features described in Stimulation control.
SAE: PassThru Port BUSACCESS - CAN-FD	This port supports all features described in Stimulation control.
Speedgoat: SimulinkRealTimeXIL Port BUSACCESS - GENERIC	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the generic bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Speedgoat: SimulinkRealTimeXIL Port BUSACCESS - MODEL BASED	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the model based bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Speedgoat: SimulinkRealTimeXIL Port MODELACCESS - DEFAULT	Restrictions: Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Synopsys: Silver Port BUSACCESS - GENERIC	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the generic bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Synopsys: Silver Port MODELACCESS - DEFAULT	Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test.
Synopsys: SilverXIL Port BUSACCESS - GENERIC	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the generic bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Synopsys: SilverXIL Port BUSACCESS - MODEL BASED	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the model based bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Synopsys: SilverXIL Port MODELACCESS - DEFAULT	Restrictions: Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Synopsys: SilverXIL Port MODELACCESS - ESI	Restrictions: Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Technica: BTS Port BUSACCESS - CAN	This port supports all features described in Stimulation control.
Technica: BTS Port BUSACCESS - CAN-FD	This port supports all features described in Stimulation control.
Technica: BTS Port BUSACCESS - FLX	This port supports all features described in Stimulation control.
Technica: CM Port BUSACCESS - CAN	This port supports all features described in Stimulation control.
Technica: CM Port BUSACCESS - CAN-FD	This port supports all features described in Stimulation control.
Technica: CM Port BUSACCESS - FLX	This port supports all features described in Stimulation control.
TOSUN: libTSCAN API Port BUSACCESS - CAN	This port supports all features described in Stimulation control.
TOSUN: libTSCAN API Port BUSACCESS - CAN-FD	This port supports all features described in Stimulation control.
tracetronic: Ethernet Port BUSACCESS - CAPTURE-CAN(-FD)	This port supports all features described in Stimulation control.
tracetronic: Ethernet Port BUSACCESS - CAPTURE-FLX	This port supports all features described in Stimulation control.
tracetronic: Ethernet Port BUSACCESS - IEEE1722-CAN(-FD)	This port supports all features described in Stimulation control.
tracetronic: SocketCAN Port BUSACCESS - CAN	This port supports all features described in Stimulation control.
tracetronic: SocketCAN Port BUSACCESS - CAN-FD	This port supports all features described in Stimulation control.
Typhoon HIL: THCC Port MODELACCESS - DEFAULT	Restrictions: Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Vector: CANoe / CANalyzer Port BUSACCESS - GENERIC	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the generic bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Vector: CANoe / CANalyzer Port BUSACCESS - MODEL BASED	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the model based bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Vector: CANoe / CANalyzer Port MODELACCESS - XIL	Restrictions: Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Vector: SIL Kit Port BUSACCESS - CAN	This port supports all features described in Stimulation control.
Vector: SIL Kit Port BUSACCESS - CAN-FD	This port supports all features described in Stimulation control.
Vector: SIL Kit Port BUSACCESS - FLX	This port supports all features described in Stimulation control.
Vector: XL API Port BUSACCESS - CAN	This port supports all features described in Stimulation control.
Vector: XL API Port BUSACCESS - CAN-FD	This port supports all features described in Stimulation control.
Vector: XL API Port BUSACCESS - FLX	This port supports all features described in Stimulation control.
Vehinfo: LABCAR Port BUSACCESS - GENERIC	Stimulation of bus signals is performed via the model access and is only possible if this also supports stimulation. The restrictions/comments of the model access also apply to the generic bus access. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Vehinfo: LABCAR Port MODELACCESS - Default	The following LabCar-side restrictions apply: Up to version 3.7.9, only STI 1.0 can be used for stimulation. As of version 3.7.10, STI 2.0 is also supported. The SignalValueSegment is not supported. Only DAT and MAT files compatible with LabCar can be used as file reference. Only ‘forward’ and ‘linear’ interpolation methods are supported. It is mandatory to specify a stimulation task in the test bench configuration. Thereby the use of wildcards (* and ?) is not possible! The value for “duration” must not be +INF, but must be set to a concrete numeric value. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
Vehinfo: LABCAR Port MODELACCESS - SMF_Bosch	The following LabCar-side restrictions apply: Up to version 3.7.9, only STI 1.0 can be used for stimulation. As of version 3.7.10, STI 2.0 is also supported. The SignalValueSegment is not supported. Only DAT and MAT files compatible with LabCar can be used as file reference. Only ‘forward’ and ‘linear’ interpolation methods are supported. It is mandatory to specify a stimulation task in the test bench configuration. Thereby the use of wildcards (* and ?) is not possible! The value for “duration” must not be +INF, but must be set to a concrete numeric value. Restrictions: Stimulus input signals are not supported. Trace files being referenced by a DataFileSegment in an STI file are not converted automatically by ecu.test. It is up to the user to check whether the trace format being used is supported by the tool.
X2E: Xoraya Port BUSACCESS - CAN-OfflineLogging	This port supports all features described in Stimulation control.
X2E: Xoraya Port BUSACCESS - CAN-OnlineLogging	This port supports all features described in Stimulation control.
X2E: Xoraya Port BUSACCESS - FLX-OfflineLogging	This port supports all features described in Stimulation control.
X2E: Xoraya Port BUSACCESS - FLX-OnlineLogging	This port supports all features described in Stimulation control.
ZLG: zlgcan Port BUSACCESS - CAN	This port supports all features described in Stimulation control.
ZLG: zlgcan Port BUSACCESS - CAN-FD	This port supports all features described in Stimulation control.