Getting started

Installation

Use Python 3.11 or newer with a graphical desktop. In an activated virtual environment, install the published application:

python -m pip install conducted-emission-mpylab

The README describes virtual-environment creation and activation on macOS, Linux, and Windows. As an alternative, pipx can manage an isolated application environment:

pipx install conducted-emission-mpylab

Both methods install conducted-emission and conducted-emission-info on the active environment’s PATH.

Check the installation

conducted-emission-info
conducted-emission-info --json
conducted-emission-info --help

These diagnostic commands show versions, package location, dependencies, and example-configuration availability without opening instruments. The example files are not installed with the application wheel. To obtain them, keep the application environment activated and clone the repository using Git:

git clone https://gitlab.hrz.tu-chemnitz.de/chair-of-electromagnetic-theory-and-compatibility-at-tu-dresden/mpylab/conducted-emission.git
cd conducted-emission
conducted-emission

The GUI starts without beginning a measurement. Its entry point launches the window; --json and the documented --help belong to the separate conducted-emission-info command.

The application menu provides About Conducted Emission… with the installed version, documentation and project links, and Quit with the platform’s standard shortcut. On macOS these actions appear in the native application menu. Quit follows the normal window-close path: settings are saved and active measurement workers are asked to stop. If a worker is still stopping, the window stays open. Existing settings remain in their previous location.

Try a dummy scan

  1. In DOT-File: select conf/conducted_emission_dummy.dot from the cloned repository. In Search Paths: use ['.', 'conf'] when starting from that repository root, or a Python list containing the absolute path to its conf directory. Keep the logical names rec, lisn, and eut.

  2. Set start frequency to 150 kHz, stop to 300 kHz, and a linear step of 150 kHz. Select only LISN path N for this short example.

  3. Inspect the selected limit profile and detector. Choose a writable Output Directory: and enter a DUT description.

  4. Choose Start Measurement. The graph uses a dummy receiver and dummy LISN, so no physical instruments are accessed. Results appear in the plots and CSV files in the chosen output directory. Dummy levels may vary.

The example is a software exercise and does not establish real-device compliance. For actual measurements, select the applicable limit profile and reviewed hardware graph, correction data, detector, and frequency settings.

Results and stopping

Use Pause Measurement or Stop Measurement to control an active scan. A stopped scan retains completed data and is logged as stopped. CSV results distinguish passed, failed, and not-evaluated points. The reference in conducted_emission_mpylab documentation explains final-scan assessment, limit selection, partial results, and device-error handling.