Automation

The simulation graphical user interface (SGUI) in BikeSim, CarSim, and TruckSim lets you get the job done with minimal training, even with little experience in simulation.

But once you've gotten past the basics and need to run hundreds or thousands of simulated tests, you'll find that the SGUI and general simulation environment are also up to this task. And, as the number of users grows, their use of our software demands that we continue to improve the capabilities of running with other software and supporting the many methods of automation that are now in use.

Built-In Batch Control

The SGUI includes two screens that can be set up to make batches of runs. One offers a matrix approach, in which two lists of datasets are combined automatically to generate new runs. For example, a list of vehicles and a list of test conditions. The other screen is more general; drawing from the current database, make a list of run datasets, and update them with a single click. The list of runs can include built-in models (no extensions), models with extensions in Simulink, LabView, ASCET, etc., and a mixture of extension environments (e.g., several Simulink models). The batch control screen even works with real-time hardware-in-the-loop systems, allowing you to set up days of testing under completely automatic control.

Control through Windows COM

Starting in 2007 (CarSim 7), the SGUI acts as a powerful COM server (also known as ActiveX). Almost anything you might do interactively can be done by sending COM commands from any environment that supports COM. Examples are provided for using Excel, MATLAB, Python, and Visual Basic.

Older versions of the SGUI support Windows Dynamic Data Exchange (DDE), with basic automation capability.

Control through Text Files

The solvers for the math models obtain all inputs from simple text parameter files, called parsfiles. Simulation control is provided by a short text file (8 lines, typically with the name "simfile") that names the main input parsfile along with some standard output files. Normally, the parsfiles and simfile are generated by the SGUI when you click a run button. However, the format is so simple that they can be written by hand or by other software, to allow the math models to be run without involving the SGUI.

The parsfile format supports an "include" capability that allows references to data in other parsfiles. For example, the main parsfile could include a line "include myfile.par" that includes the contents of a file named myfile.par. You can replace that file with each run for sensitivity studies or other automated analyses.

Control by Events

The capability for describing complex test sequences with events blurs the distinction between one long run covering many conditions, and many short runs each covering a single condition. A sequence of tests can be defined as a single run, each segment treated as a separate event. For example, running a series of brake tests with a real-time HIL system might involve starting at zero speed, accelerating to 1 km/h above the brake test speed, coasting down, applying the brakes until the vehicle comes to rest, and then repeating. The repeat might involve a different speed, vehicle loading, surface condition, or other factor. Any number of these tests can be strung together using events to make a single (long) run.

Control by DOE and Optimization Software

The simple text input files used by the solvers in CarSim, TruckSim, and BikeSim provide an easy interface with most of the design, development and analysis software used by engineers. Design-of-experiments for optimizing chassis systems and components may be done using HyperStudy®, iSIGHT®, OPTIMUS® or any other DOE package. Since our products run much faster than real time, these optimization programs can be completed in record time.

General Information