i have been developing a driver using the same WMI interface. I use WMI method 19 for accessing additional battery data like temperature, etc. The data format seems to be based on the Smart Battery Data Specification, and the battery index starts with one (the zero index might be useful for detecting which data entries are valid, as they contain 0xffff for battery index zero, while unsupported data entries contain 0x0001).
Would it be possible to have a look at the bmof used to describe the extended WMI interface used by your driver? Because on my machine, WMI methods 20 and 21 are missing:
[WMI, Dynamic, Provider("WmiProv"), Locale("MS\0x409"), Description("Class used to control smart battery, Version 2.8"), guid("{79772EC5-04B1-4bfd-843C-61E7F77B6CC9}")]
class BatteryControl {
[key, read] string InstanceName;
[read] boolean Active;
Hi,
i have been developing a driver using the same WMI interface. I use WMI method 19 for accessing additional battery data like temperature, etc. The data format seems to be based on the Smart Battery Data Specification, and the battery index starts with one (the zero index might be useful for detecting which data entries are valid, as they contain 0xffff for battery index zero, while unsupported data entries contain 0x0001).
Would it be possible to have a look at the bmof used to describe the extended WMI interface used by your driver? Because on my machine, WMI methods 20 and 21 are missing:
[WMI, Dynamic, Provider("WmiProv"), Locale("MS\0x409"), Description("Class used to control smart battery, Version 2.8"), guid("{79772EC5-04B1-4bfd-843C-61E7F77B6CC9}")] class BatteryControl { [key, read] string InstanceName; [read] boolean Active;
[WmiMethodId(19), Implemented, read, write, Description("Get battery Information Interface.")] void GetBattInfoInterface([in] uint32 uBatteryInfoIndex, [in] uint32 uBatteryNo, [out] uint32 uReturn); };