Any further questions?
Join our discordOur documentation is currently incomplete and undergoing active development. If you have any questions or feedback, please visit this forum thread.
The Electrics sensor returns the full electrics.values table from the host vehicle. Those entries are produced by the vehicle Electrics
system — the in-simulation signal bus that connects controllers, powertrain logic, lights, and driver inputs. The same values drive hydros
, props
, gauges, and co-simulation interfaces.
The sensor is non-positional and updated every simulation step. It has no separate mount pose; it mirrors whatever the vehicle’s electrics application currently publishes.
The sensor is available to use from
Python API
. It has no extensions.tech_sensors.create* / get*Readings Lua API.
This sensor does not use extensions.tech_sensors.create*. Request it through a tech client (BeamNGpy, ROS, or similar) with a vehicle SensorRequest containing {type = 'Electrics'}.
{type = 'Electrics'}
Args:
None.
Returns: response(table):
Signal names and units are documented on the Electrics application page.
Was this article helpful?