Vehicle Signal Logger
The Vehicle Signal Logger (VSL) is a World Editor tool for selecting vehicle properties and writing them to a CSV file while the simulation runs. It reuses the same signal catalogue as the Co-Simulation Editor (kinematics, driver, wheels, electrics, powertrain, and attached sensors), but is logging-only: there is no UDP coupling and no inbound “from” message.
The Vehicle Signal Logger lets you pick individual signals, save/load that selection as a config CSV, and control sampling from the World Editor (or BeamNGpy).
Vehicle Signal Logger with Scene Vehicles and Available Signals windows
Opening the editor
- Open the World Editor.
- In the mode bar, select Vehicle Signal Logger (chart icon). If this icon is not visible, click on the 3 bars icon and select All.
- A Scene Vehicles window lists every vehicle currently in the scene.
Scene Vehicles window
Each row is one loaded vehicle. Actions on the selected vehicle:
Switching vehicle while logging is blocked. Changing vehicle clears the previous signal selection cache and reloads vehicle-side signal metadata.
Available Signals window
Use the code icon on a vehicle row to open <vehicle> [available signals].
Categories
Checkboxes at the top filter which groups appear in the list:
Selections survive category toggles and reloads within the same vehicle session.
Selecting signals
Logging settings
At the bottom of the signals window:
vsl_signals_log.csv or a path under the user folder).0.0001 s).If you include sensor signals while those sensors are still in Edit mode in the ADAS editor, VSL automatically promotes the needed sensor instances to Live before logging starts so the vehicle controllers exist.
Configuration CSV vs output CSV
VSL uses two different CSV formats:
Configuration CSV (Save / Load in the editor)
Written by Save configuration. Columns:
type, groupName, name, description, dataType, filename, frequencySteps
Row kinds:
groupName + name, plus description and type).filename, frequencySteps).This file is a reusable selection contract. It is not the timed log.
Output CSV (runtime log)
Written while logging is active. It contains a timestamp and one column per selected signal, sampled at the configured stride. Stop logging to flush and unload the vehicle-side logger.
Typical workflow
- Spawn or load the vehicle(s) you care about.
- Optionally attach IMU / GPS / Ideal RADAR / Roads sensors with the ADAS Sensor Configuration Editor.
- Open Vehicle Signal Logger, select the vehicle, open the signals window.
- Enable the needed categories, filter if useful, and tick the signals to log.
- Set the log filename and sampling period.
- Optionally Save configuration so the selection can be reused.
- Press Start logging, run the scenario, then Stop logging.
BeamNGpy
The same vehicle-side logger is available from BeamNGpy as vehicle.logging. For methods, parameters, and usage details, see the
BeamNGpy documentation
.
Editor Save configuration CSVs can be passed into that API as the signal selection (configuration CSV, not an output log). See Configuration CSV vs output CSV .
Limitations
- Currently the VSL does not support logging multiple vehicles simultaneously.
Related tools
- ADAS Sensor Configuration Editor — attach sensors whose channels can appear under the Sensors group.
- Co-Simulation Editor — same signal catalogue, used for tight UDP coupling with third-party software.
Was this article helpful?
