BlueM.Sim application

BlueM.Sim | Download | Application | Theory | Development

This page is an aid to the application of BlueM.

Record

• A record consists of several text files. Mandatory for each simulation are ALL- (general information) and the SYS file - (System Plan). Furthermore, files for a description of the system elements should be in the required manner. All files must have the same file name (name = record), only the file extensions differ. (The name of the record shall consist of not more than 32 characters! See Bug 13)
• It is possible to make a record using TALSIM, after creating these can be exported and used for BlueM. These are minor modifications to the export files. See TALSIM Export.

See also Input files

Simulation

BlueM.Win Screenshot

Release 0.9.1

For individual simulations, it is easiest to use the BlueM.Win package.

• Download the prebuilt package BlueM.Win.zip and unzip.
• Start the file BlueM.Win.exe
• Select a record
• Start simulation
• After successful simulation, view the simulation result in BlueM.Wave.

For bluem.dll from another application address, the BlueM.DLLAdapter can be used.

Release 0.9

BlueM.exe Screenshot

• In the simplest case the compiled EXE file (BlueM.exe) is in the same directory as the data to be simulated. In this case, simply launch the EXE at the request of the record name. Then the simulation starts.
• You can specify the name of the data directly as a parameter to pass to BlueM.exe

<dos>C:\Arbeitsverzeichnis>"Pfad\zu\BlueM.exe" Datensatzname</dos>

• To prevent the window from closing immediately when the simulation is finished or an error has occurred, a shortcut to BlueM.exe can be created. In the properties of the shortcut enter the following "target" :

cmd.exe /K "Pfad\zu\BlueM.exe"

Under "Start in" the working directory must be specified, i.e., the directory in which the record is located.

Results

• Depending on the setting BlueM creates result files. By default, the WEL-file.

See also output files

Errors / warnings

• In some cases, the blue model for a global program termination gives an ERROR-Constant back. (In case a $FEHL.TMP file is generated, there is also the ERROR constant in the left column).
• Warnings (eg, Buffer overflows) are written during the simulation in the file $WARN.TMP .