Win32_1394ControllerDevice class
The Win32_1394ControllerDevice association WMI class relates the high-speed serial bus (IEEE 1394 Firewire) Controller and the CIM_LogicalDevice instance connected to it. This serial bus provides enhanced connectivity for a wide range of devices, including consumer audio or video components, storage peripherals, other computers, and portable devices. IEEE 1394 has been adopted by the consumer electronics industry and provides a Plug and Play-compatible expansion interface.
The following syntax is simplified from Managed Object Format (MOF) code and includes all of the inherited properties. Properties are listed in alphabetic order, not MOF order.
Syntax
[Dynamic, Provider("CIMWin32"), UUID("{8835CFC9-BAEF-11d2-85E5-0000F8102E5F}"), AMENDMENT]
class Win32_1394ControllerDevice : CIM_ControlledBy
{
uint32 NegotiatedDataWidth;
uint64 NegotiatedSpeed;
uint16 AccessState;
uint32 NumberOfHardResets;
uint32 NumberOfSoftResets;
Win32_1394Controller REF Antecedent;
CIM_LogicalDevice REF Dependent;
};
Members
The Win32_1394ControllerDevice class has these types of members:
Properties
The Win32_1394ControllerDevice class has these properties.
-
AccessState
-
-
Data type: uint16
-
Access type: Read-only
Indicates whether the controller is actively commanding or accessing the device. This information is necessary when a logical device can be commanded by, or accessed through, multiple controllers.
This property is inherited from CIM_ControlledBy.
-
-
Unknown (0)
-
Active (1)
-
Inactive (2)
Antecedent
-
Data type: Win32_1394Controller
-
Access type: Read-only
-
Qualifiers: key, Override ("Antecedent"), MappingStrings ("WMI|Win32_1394Controller")
The Win32_1394Controller antecedent reference represents the 1394 controller associated with this device.
Dependent
-
Data type: CIM_LogicalDevice
-
Access type: Read-only
-
Qualifiers: key, Override ("Dependent"), MappingStrings ("CIM|CIM_LogicalDevice")
The CIM_LogicalDevice dependent reference represents the CIM_LogicalDevice connected to the 1394 controller.
NegotiatedDataWidth
-
Data type: uint32
-
Access type: Read-only
-
Qualifiers: Units ("bits")
When several bus or connection-data widths are possible, this property defines the one in use between the devices. Data width is specified in bits. If data width is not negotiated, or if this information is not available or important to device management, the property should be set to 0 (zero).
This property is inherited from CIM_DeviceConnection.
NegotiatedSpeed
-
Data type: uint64
-
Access type: Read-only
-
Qualifiers: Units ("bits per second")
When several bus or connection speeds are possible, this property defines the one being used between the devices. Speed is specified in bits-per-second. If connection or bus speeds are not negotiated, or if this information is not available or important to device management, the property should be set to 0 (zero).
For more information about using uint64 values in scripts, see Scripting in WMI.
This property is inherited from CIM_DeviceConnection.
NumberOfHardResets
-
Data type: uint32
-
Access type: Read-only
Number of hard resets issued by the controller. A hard reset returns the device to its initialization or boot-up state. All internal device state information and data are lost.
This property is inherited from CIM_ControlledBy.
NumberOfSoftResets
-
Data type: uint32
-
Access type: Read-only
Number of soft resets issued by the controller. A soft reset does not completely clear current device state and data. Exact semantics are dependent on the device and on the protocols and mechanisms used to communicate to it.
This property is inherited from CIM_ControlledBy.
Remarks
The Win32_1394ControllerDevice class is derived from CIM_ControlledBy.
Examples
The following PowerShell code sample retrieves 1394 controller device information.
# Helper function to return AccessState
function get-WmiAccessState {
param ([uint16] $char)
# parse and return values
If ($char -le 2 -and $char -ge 0) {
switch ($char) {
0 {"00-Reserved"}
1 {"01-Reserved"}
2 {"02-Unknown"}
}
}
Else {
"$char - unknown value"
}
}
# Get 1394 Controller Device information from WMI
$1394Cont = Get-WMIObject Win32_1394ControllerDevice
# Display Details
"Win32_1394ControllerDevice WMI Information"
"=========================================="
foreach ($device in $1394Cont) {
"Device Characteristics - Device {0}" -f ++$i
"Access State : {0}" -f (Get-WmiAccessState($ch))
"Antecedent : {0}" -f $device.Antecedent
"Negotiated Data Width : {0}" -f $device.NegotiatedDataWidth
"Negotiated Speed : {0}" -f $device.NegotiatedSpeed
"Number of Hard Resets : {0}" -f $device.NumberofHardResets
"Number of Soft Resets : {0}" -f $device.NumberofSoftResets
}
The previous code sample returns the following information:
# Win32_1394ControllerDevice WMI Information
Device Characteristics -Device 1
Access State : 00-Reserved
Antecedent : \\UK0N055\root\CIMV2:Win32_1394Controller.DeviceID="PCI\\VEN_1217&DEV_00F7&SUBSYS_01CC1028
&REV_02\\4&2FE911E8&0&0CF0"
Negotiated Data Width :
Negotiated Speed :
Number of Hard Resets :
Number of Soft Resets :
Requirements
| Requirement | Value |
|---|---|
| Minimum supported client |
Windows Vista |
| Minimum supported server |
Windows Server 2008 |
| Namespace |
Root\CIMV2 |
| MOF |
|
| DLL |
|