Skip to content

Driver to simulate multi-battery setups and test Windows power management

License

Notifications You must be signed in to change notification settings

forderud/BatterySimulator

Repository files navigation

Project Description
BatteryQuery Tool for querying battery parameters.
DevicePowerQuery Tool for enumerating connected devices and their power state and parameters.
PowerMonitor Sample code for handling power events and query system power state.
simbatt Mock driver to simulate multi-battery setups and test Windows power management. Based on the Microsoft Simulated Battery Driver Sample sample with modifications to ease multi-battery testing and failure handling without requiring physical battery packs.

Tutorial: Writing Battery Miniclass Drivers

image

How to test

It's recommended to test in a disposable virtual machine (VM) during development, since faulty drivers might crash or corrupt the computer. You can use the "checkpoint" feature to roll back the machine to a known good state in case of driver installations problems.

Prerequisites

Prerequisites for the host computer:

Prerequisites for the target computer:

  • Disable Secure Boot in UEFI/BIOS.
  • Enable test-signed drivers: bcdedit /set testsigning on
  • Enable kernel debugging: bcdedit /debug on (optional)

Test instruction

You can with the driver make Windows believe that it’s being powered by one or more battery packs – even if running from a AC-powered VM.

Steps:

  • Build solution in Visual Studio or download binaries from releases.
  • Copy BatteryQuery.exe, PowerMonitor.exe and the simbatt folder to the target machine.
  • Run INSTALL.bat with admin privileges to install the driver with two simulated batteries.
  • Run BatteryQuery.exe <N> <Charge>, where <N> is the simulated battery index and <Charge> is the new charge level, to modify the battery state. Example: BatteryQuery.exe 1 90 to set the charge level of the first battery to 90%.
  • Run PowerMonitor.exe to monitor power events broadcasted to all application.
  • Run UNINSTALL.bat with admin privileges to uninstall the driver and delete simulated batteries.

Examples

Simulate 6 battery-packs:
image

Battery status icons that can be simulated:

  • Critical level: image (7% or less)
  • Low level: image (10% or less)
  • Battery saver: image (20% or less)
  • Half full: image
  • On AC power: image

Notification when simulating low-battery conditions:
image

Alternative approach

It's also possible to make an Arduino board emulate a UPS battery. This leverages the in-built Windows hidbatt driver, so there's no need for installing additional drivers. The forderud/HIDPowerDevice project provides sample code for this.

Configuring Windows power management

Windows handling of low-battery situations can either be configured through the "Power Options" UI (run powercfg.cpl -> "Change plan settings" -> "Change advanced power settings"):
image image

... or using Powercfg:

:: Display current power configuration 
PowerCfg.exe /query

:: Select power scheme (in-built schemes: SCHEME_MIN, SCHEME_MAX or SCHEME_BALANCED)
set SCHEME=SCHEME_BALANCED

Power saving configuration:

:: Select power sheme
PowerCfg.exe /setactive %SCHEME%

:: Sleep after after 4min on DC and never sleep on AC
PowerCfg.exe /setdcvalueindex %SCHEME% SUB_SLEEP STANDBYIDLE 240
PowerCfg.exe /setacvalueindex %SCHEME% SUB_SLEEP STANDBYIDLE 0

:: Turn off display after 5min on DC and 10min on AC
PowerCfg.exe /setdcvalueindex %SCHEME% SUB_VIDEO VIDEOIDLE 300
PowerCfg.exe /setacvalueindex %SCHEME% SUB_VIDEO VIDEOIDLE 600

Drivers can expose both standard and custom power setting parameters as documented on Managing Device Performance States. These power settings can afterwards be configured using PowerCfg.

Power event configuration for AC & DC mode:

:: Low battery level (percentage)
PowerCfg.exe /setacvalueindex %SCHEME% SUB_BATTERY BATLEVELLOW 10
PowerCfg.exe /setdcvalueindex %SCHEME% SUB_BATTERY BATLEVELLOW 10

:: Low battery notification (0=off, 1=on)
PowerCfg.exe /setacvalueindex %SCHEME% SUB_BATTERY BATFLAGSLOW 0
PowerCfg.exe /setdcvalueindex %SCHEME% SUB_BATTERY BATFLAGSLOW 0
:: Delete Low battery notification rule
:: PowerCfg.exe /deletesetting SUB_BATTERY BATFLAGSLOW

:: Low battery action (0=do nothing, 1=sleep, 2=hibernate, 3=shut down)
PowerCfg.exe /setacvalueindex %SCHEME% SUB_BATTERY BATACTIONLOW 0
PowerCfg.exe /setdcvalueindex %SCHEME% SUB_BATTERY BATACTIONLOW 0
:: Delete Low battery action rule
:: PowerCfg.exe /deletesetting SUB_BATTERY BATACTIONLOW

:: Critical battery level (percentage)
PowerCfg.exe /setacvalueindex %SCHEME% SUB_BATTERY BATLEVELCRIT 5
PowerCfg.exe /setdcvalueindex %SCHEME% SUB_BATTERY BATLEVELCRIT 5

:: Critical battery notification (0=off, 1=on)
PowerCfg.exe /setacvalueindex %SCHEME% SUB_BATTERY BATFLAGSCRIT 0
PowerCfg.exe /setdcvalueindex %SCHEME% SUB_BATTERY BATFLAGSCRIT 0
:: Delete Critical battery notification rule
:: PowerCfg.exe /deletesetting SUB_BATTERY BATFLAGSCRIT

:: Critical battery action (0=do nothing, 1=sleep, 2=hibernate, 3=shut down)
PowerCfg.exe /setacvalueindex %SCHEME% SUB_BATTERY BATACTIONCRIT 0
PowerCfg.exe /setdcvalueindex %SCHEME% SUB_BATTERY BATACTIONCRIT 0
:: Delete Critical battery action rule
:: PowerCfg.exe /deletesetting SUB_BATTERY BATACTIONCRIT

CPU power configuration for AC & DC mode:

:: Minimum processor state (percentage)
PowerCfg.exe /setacvalueindex %SCHEME% SUB_PROCESSOR PROCTHROTTLEMIN 5
PowerCfg.exe /setdcvalueindex %SCHEME% SUB_PROCESSOR PROCTHROTTLEMIN 5

:: System cooling policy (0=passive, 1=active)
PowerCfg.exe /setacvalueindex %SCHEME% SUB_PROCESSOR SYSCOOLPOL 1
PowerCfg.exe /setdcvalueindex %SCHEME% SUB_PROCESSOR SYSCOOLPOL 0

:: Maximum processor state (percentage)
PowerCfg.exe /setacvalueindex %SCHEME% SUB_PROCESSOR PROCTHROTTLEMAX 100
PowerCfg.exe /setdcvalueindex %SCHEME% SUB_PROCESSOR PROCTHROTTLEMAX 100

There are also many other settings available. Use PowerCfg.exe /query to view all settings. See PowerSettings.ps1 for an example of API access and modification of power settings from a script.

Battery parameters

Battery parameters from the battery miniclass driver will automatically be exposed through the Win32_Battery WMI class, so there's no need for implementing a WMI provider yourself.

Per-battery parameters

Per-battery parameters can either be accessed through a WMI high-level or IOCTL low-level interface:

Windows power events and aggregated parameters

Windows applications receive WM_POWERBROADCAST events when the machine transitions between AC and battery power, as well as when suspening or resuming from low-power modes. Details about the power state and aggregated battery charge level can be retrieved by calling GetSystemPowerStatus.

The PowerMonitor project demonstrates how to handle power events and query system power state.
image