<< Click to Display Table of Contents >> Navigation: »No topics above this level« Variable names for PC devices |
The ADI line supports the following variables for a PC device:
Note: The "C" column indicates whether the variable returns a constant value.
Variable name |
Data format |
I/O |
C |
Devices |
Description |
aPci1Comment |
PP100/200: VT=string VL=33 PP300/400: VT=string VL=89 |
R |
ü |
PP100/200 4 PP300/400 |
Comment for the FPGA firmware for aPCI slot 1. By default, the comment contains the date and version of the firmware. |
aPci1DeviceId |
PP100/200: VT=string VL=7 PP300/400: VT=string VL=8 |
R |
ü |
PP100/200 3 PP300/400 |
Device ID of the aPCI module in Slot 1. Example: "5090" 2 |
aPci1Eeprom |
VT=u8 VN=256 |
R |
ü |
PP300/400 |
EEPROM data of the aPCI module in Slot 1. |
aPci1ModelNumber |
PP100/200: VT=string VL=19 PP300/400: VT=string VL=24 |
R |
ü |
PP100/200 3 PP300/400 |
Model number of the aPCI module in Slot 1. Example: "3IF786.9" 2 PP100/200 with Windows CE: Valid data is returned beginning with Windows CE 5.0 version 5.1 only (with boot loader version 2.3). An empty string is always returned in older Windows CE versions (with older bootloader versions). |
aPci1Size |
VT=u32 |
R |
ü |
PP100/200 4 PP300/400 |
Size of the FPGA firmware for aPCI Slot 1 in bytes. |
aPci1Status |
VT=u8 |
R |
ü |
PP100/200 3 PP300/400 |
Boot status for the FPGA firmware for aPCI slot 1. |
aPci1Variant |
VT=u8 |
R |
ü |
PP300/400 |
Variant of the aPCI module in Slot 1. 0 to 255. |
aPci1XmlHeader |
VT=string VL=256 |
R |
ü |
PP100/200 4 PP300/400 |
XML header for the FPGA firmware for aPCI slot 1. The XML header contains information about the firmware such as device ID, version, size, etc. |
aPci2Comment |
PP100/200: VT=string VL=33 PP300/400: VT=string VL=89 |
R |
ü |
PP100/200 4 PP300/400 |
Comment for the FPGA firmware for aPCI slot 2. By default, the comment contains the date and version of the firmware. |
aPci2DeviceId |
PP100/200: VT=string VL=7 PP300/400: VT=string VL=8 |
R |
ü |
PP100/200 3 PP300/400 |
Device ID of the aPCI module in Slot 2. Example: "5090" 2 |
aPci2Eeprom |
VT=u8 VN=256 |
R |
ü |
PP300/400 |
EEPROM data of the aPCI module in Slot 2. |
aPci2ModelNumber |
PP100/200: VT=string VL=19 PP300/400: VT=string VL=24 |
R |
ü |
PP100/200 3 PP300/400 |
Model number of the aPCI module in Slot 2. Example: "3IF786.9" 2 |
aPci2Size |
VT=u32 |
R |
ü |
PP100/200 4 PP300/400 |
Size of the FPGA firmware for aPCI Slot 2 in bytes. |
aPci2Status |
VT=u8 |
R |
ü |
PP100/200 3 PP300/400 |
Boot status for the FPGA firmware for aPCI slot 2. |
aPci2Variant |
VT=u8 |
R |
ü |
PP300/400 |
Variant of the aPCI module in Slot 2. 0 to 255. |
aPci2XmlHeader |
VT=string VL=256 |
R |
ü |
PP100/200 4 PP300/400 |
XML header for the FPGA firmware for aPCI slot 2. The XML header contains information about the firmware such as device ID, version, size, etc. |
BatteryVoltage |
VT=f32 |
R |
|
|
obsolete - replaced by BatVoltage |
BatState |
VT=i32 |
R |
|
APC510 APC511 APC620 16 APC810 APC820 APC910 PP300/400 15 PP500 PPC300 PPC700 16 PPC800 PPC900 |
CMOS battery state. 0 = Unknown 1 = Good 2 = Bad (missing, defective, dead) |
BatVoltage |
VT=f32 |
R |
|
APC510 APC511 APC620 APC910 PP500 27 PPC700 PPC900 |
CMOS battery voltage (Vbat) in volts. |
BiosBootInfo |
VT=i32 |
R |
ü |
APC510 APC511 PP500 27 |
BIOS Bootinfo. 0 = Booted from backup area 1 = Booted from normal (update) area |
BiosCoreVersion |
VT=string VL=80 |
R |
ü |
APC620 25 MP100/200 10 PP100/200 10 PP300/400 PPC300 PPC700 25 |
BIOS core version. Example: "4.0 Release 6.1" |
BiosDate |
VT=string VL=80 |
R |
ü |
APC510 APC511 APC620 APC810 APC820 APC910 APC2100 MP100/200 10 PP100/200 10 PP300/400 PP500 PPC300 PPC700 PPC800 PPC900 PPC2100 |
BIOS date. Example: "08/26/04" |
BiosVersion |
VT=string VL=80 |
R |
ü |
APC510 APC511 APC620 APC810 APC820 APC910 APC2100 MP100/200 PP100/200 PP300/400 PP500 PPC300 PPC700 PPC800 PPC900 PPC2100 |
BIOS version. Example: "1.10" |
BoardCenterTemperature |
VT=i8 |
R |
|
APC820 |
Temparature in the middle of the baseboard in degrees Celsius. |
BoardEth2Temperature |
VT=i8 |
R |
|
APC810 PPC800 |
Ambient temperature of ETH2 controller in degrees Celsius. |
BoardInTemperature |
VT=i8 |
R |
|
APC820 |
Temperature of the baseboard at air intake in degrees Celsius. |
BoardIoTemperature |
VT=i8 |
R |
|
APC620 APC810 MP100/200 PP100/200 PP300/400 PPC300 PPC700 PPC800 |
Temperature in the baseboard I/O area in degrees Celsius (positive values only). On the APC620 and PPC700, this temperature corresponds to the ambient temperature of the add-on drives. |
BoardOutTemperature |
VT=i8 |
R |
|
APC820 |
Temperature of the baseboard at air output in degrees degrees Celsius. |
BoardPowerTemperature |
VT=i8 |
R |
|
APC810 PPC800 |
Ambient temperature of power supply controller in degrees Celsius. |
BrOsVersion |
VT=string VL=80 |
R |
ü |
APC510 APC511 APC620 20 APC810 APC820 PP300/400 15 PP500 PPC300 19 PPC700 20 PPC800 |
B&R specific operating system version. Currently, only the version of the Windows CE image is supported. Example: "V1.0" |
CaseFan1Speed |
VT=u16 |
R |
|
APC620 APC810 APC820 PP300/400 PPC300 PPC700 PPC800 |
Speed of the first housing fan in rpm. |
CaseFan2Speed |
VT=u16 |
R |
|
APC620 APC810 APC820 PPC700 PPC800 |
Speed of the second housing fan in rpm. |
CaseFan3Speed |
VT=u16 |
R |
|
APC620 APC810 APC820 PPC700 PPC800 |
Speed of the third housing fan in rpm. |
CaseFan4Speed |
VT=u16 |
R |
|
APC620 APC810 PPC700 PPC800 |
Speed of the fourth housing fan in rpm. |
CmosProfile |
VT=u8 |
R |
|
APC810 APC820 PPC800 |
CMOS profile switch setting. |
CompatibilityId |
VT=u16 |
R |
ü |
All 18 28 |
PC compatibility ID. |
CpuBoardTemperature |
VT=i8 |
R |
|
APC620 12 13 APC810 APC820 PPC700 12 13 PPC800 |
CPU board temperature in degrees Celsius (positive values only). |
CpuBoardType |
VT=string VL=80 |
R |
ü |
APC510 APC511 APC620 APC810 APC820 APC910 APC2100 PP500 PPC700 PPC800 PPC900 PPC2100 |
CPU board type. Example: "E815", "E855", "X855" and "X945" on APC620 and PPC700 24 or "B945" on APC810, PPC800 and APC820. |
VT=i8 |
R |
|
APC620 APC810 APC820 APC910 30 APC2100 30 MP100/200 PP100/200 PP300/400 PPC300 PPC700 PPC800 21 PPC900 30 PPC2100 30 |
Internal CPU temperature in degrees Celsius (positive values only). APC620, PPC700, APC810, PPC800, APC820: The CPU temperature is read using WMI if ACPI (Advanced Configuration and Power Interface) is enabled in BIOS and WMI support is enabled with the WmiEnable variable. Temperature changes less than 4°C are not reported. If ACPI or WMI is disabled, the CPU temperature is read directly from the hardware monitor block (APC620, PPC700) or from the MTCX (APC810, PPC800, APC820). PPC800: When using CCAX CPU board, only supported if WmiEnable is enabled. APC910, PPC900, APC2100, PPC2100: Only supported if WmiEnable is enabled. |
|
CpuVoltage |
VT=f32 |
R |
|
APC620 PPC700 |
First CPU core voltage (VcoreA) in volts. |
CpuVoltage2 |
VT=f32 |
R |
|
APC620 12 13 PPC700 12 13 |
Second CPU core voltage (VcoreB) in volts. |
DcVoltage |
VT=f32 |
R |
|
APC620 PPC700 |
First DC voltage (+3.3 Vin) in volts. |
DcVoltage2 |
VT=f32 |
R |
|
APC620 12 13 PPC700 12 13 |
Second DC voltage (+5 Vin) in volts. |
DeviceId |
VT=u32 |
R |
ü |
All 18 28 |
PC device ID. |
VT=int32 |
R |
ü |
All |
Type of B&R PC: 0 = Unknown 4 = PP100/200 5 = MP100/200 6 = APC620 7 = PPC700 8 = PP300/400 9 = MP40 10 = PPC300 11 = MP50 12 = APC810 13 = PPC800 14 = APC820 15 = PP500 16 = APC510 17 = APC511 18 = APC910 19 = PPC900 20 = APC2100 21 = PPC2100 |
|
Drive1Temperature |
VT=i8 |
R |
|
APC620 APC810 PPC700 PPC800 |
Temperature of slide-in drive 1 in degrees Celsius (positive values only). |
Drive2Temperature |
VT=i8 |
R |
|
APC620 PPC700 25 31 APC810 |
Temperature of slide-in drive 2 in degrees Celsius (positive values only). |
Dvi1DisplayHResolution |
VT=u16 |
R |
|
APC510 APC511 APC620 7 APC810 APC820 APC910 APC2100 PPC700 7 PPC800 PP500 PPC900 PPC2100 |
Horizontal resolution of the first DVI display in pixels. |
Dvi1DisplayVResolution |
VT=u16 |
R |
|
APC510 APC511 APC620 7 APC810 APC820 APC910 APC2100 PPC700 7 PPC800 PP500 PPC900 PPC2100 |
Vertical resolution of the first DVI display in pixels. |
Dvi1FactoryData |
VT=u8 VN=256 |
R |
|
|
obsolete - replaced by Dvi1Settings |
VT=u8 VN=256 |
R |
|
APC510 APC511 APC620 7 APC810 APC820 APC910 APC2100 PPC700 7 PPC800 PP500 PPC900 PPC2100 |
Settings for the first DVI display. For B&R-internal use only! |
|
Dvi2DisplayHResolution |
VT=u16 |
R |
|
APC620 7 APC810 |
Horizontal resolution of the second DVI display in pixels. |
Dvi2DisplayVResolution |
VT=u16 |
R |
|
APC620 7 APC810 |
Vertical resolution of the second DVI display in pixels. |
Dvi2FactoryData |
VT=u8 VN=256 |
R |
|
|
obsolete - replaced by Dvi2Settings |
VT=u8 VN=256 |
R |
|
APC620 7 APC810 |
Settings for the second DVI display. For B&R-internal use only! |
|
Enable1State |
VT=u8 17 |
R |
|
MP40/50 |
Status of the first enable button. 0 = Button not pressed 1 = Button is in the panic position Only use this variable to check whether the button is working. |
Enable2State |
VT=u8 17 |
R |
|
MP40/50 |
Status of the second enable button. 0 = Button not pressed 1 = Button is in the panic position Only use this variable to check whether the button is working. |
Eth2Temperature |
VT=i8 |
R |
|
APC810 |
Temperature of ETH2 controller in degrees Celsius. |
FactoryData |
VT=u8 VN=256 |
R |
ü |
|
obsolete - replaced by FactorySettings |
VT=u8 VN=256 1 |
R |
ü |
All 10 18 28 |
PC factory settings. For B&R-internal use only! |
|
VT=string VL=8 11 |
R |
ü |
All 12 18 28 |
Version of factory settings Example: "1.02" 11 |
|
FactoryVersion |
VT=string VL=8 |
R |
ü |
|
obsolete - replaced by FactorySettingsVersion |
FanOnHours |
VT=u16 |
R |
|
APC620 APC810 APC820 PP300/400 PPC300 PPC700 PPC800 |
Number of operating hours for the PC's fans. |
FlashSize |
VT=u32 |
R |
|
MP40/50 18 |
Size of the flash memory of a MP40/50 in bytes. |
Fpga1Comment |
VT=string VL=33 |
R |
ü |
MP100/200 |
Comment for the FPGA1 firmware. By default, the comment contains the date and version of the firmware. |
Fpga1DeviceId |
VT=string VL=6 |
R |
ü |
MP100/200 10 |
Device ID of the onboard FPGA1. Example: "6504" 2 |
Fpga1Size |
VT=u32 |
R |
ü |
MP100/200 |
Size of the FPGA1 firmware in bytes. |
Fpga1Status |
VT=u8 |
R |
ü |
MP100/200 |
Boot status of the FPGA1 firmware. |
Fpga1XmlHeader |
VT=string VL=256 |
R |
ü |
MP100/200 |
XML header for the FPGA1 firmware. The XML header contains information about the firmware such as device ID, version, size, etc. |
FpgaComment |
VT=string VL=33 |
R |
ü |
MP100/200 PP100/200 4 |
Comment for the FPGA firmware. By default, the comment contains the date and version of the firmware. Example: "PowerPanel 10.03.2003 V10" |
FpgaDeviceId |
VT=string VL=6 |
R |
ü |
MP100/200 10 PP100/200 10 |
Device ID of the onboard FPGA1. Example: "5718" (or "5751" with BIOS version 1.04 or lower) on the PP100/200 2) |
FpgaSize |
VT=u32 |
R |
ü |
MP100/200 PP100/200 4 |
Size of the FPGA firmware in bytes. |
FpgaStatus |
VT=u8 |
R |
ü |
MP100/200 PP100/200 3 |
Boot status of the FPGA firmware. |
FpgaXmlHeader |
VT=string VL=256 |
R |
ü |
MP100/200 PP100/200 4 |
XML header for the FPGA firmware. The XML header contains information about the firmware such as device ID, version, size, etc. |
HandwheelPresent |
VT=boolean |
R |
ü |
MP40/50 |
"Electronic handwheel installed" indicator. 1 indicates that a handwheel is installed. |
HandwheelValue |
VT=u32 |
R/W |
|
MP40/50 PP500 32 |
Counter value of the electronic handwheel. Range of values: 0 to 65535 |
HardwareRevision |
VT=string VL=5 |
R |
ü |
APC510 APC511 APC620 APC810 APC820 APC910 APC2100 MP40/50 18 PP300/400 PP500 28 PPC300 PPC700 PPC800 PPC900 PPC2100 |
Hardware revision of the PC. |
IfSlotTemperature |
VT=i8 |
R |
|
APC820 PPC800 |
Temperature of the optional module in the IF slot in degrees Celsius. |
VT=f32 |
R |
|
APC510 APC511 APC910 PP500 27 PPC900 |
Input voltage (Vin) in volts. |
|
VT=boolean |
R/W |
|
MP40/50 |
Calibration mode of the joystick. Writing with 1 begins the calibration and 0 ends it. |
|
VT=boolean |
R |
|
MP40/50 |
"Joystick calibrated" identifier. 1 indicates that all joystick axes have been calibrated. When 0, the joystick must be calibrated (see also JoystickCalibrate). |
|
VT=u32 VN=3 |
R |
|
MP40/50 |
Calibrated values of the joystick position: [0] = X axis, [1] = Y axis, [2] = Z axis. Range of values: Is set during calibration (see also JoystickPosRange). The joystick must be calibrated (see also JoystickCalibrated). |
|
VT=u32 VN=3 |
R/W |
|
MP40/50 |
Specifies the range for the calibrated value = maximum (+/-) per axis direction: [0] = X axis, [1] = Y axis, [2] = Z axis. Range of values: 0 to 1023 per axis On an MP40/50, the value 15 is recommended; this is preset by default with JoystickCalibrate. |
|
VT=u32 VN=3 |
R |
|
MP40/50 |
Raw values of the joystick position: [0] = X axis, [1] = Y axis, [2] = Z axis. Range of values: 0 to 1023 per axis |
|
VT=u32 VN=3 |
R/W |
|
MP40/50 |
Raw values of the joystick position for the calibration: [0] = X axis, [1] = Y axis, [2] = Z axis. Range of values: 0 to 1023 per axis The values are preset with the current raw values when the calibration is started with JoystickCalibrate. |
|
VT=u32 VN=3 |
R/W |
|
MP40/50 |
Maximum raw values of the joystick position for the calibration: [0] = X axis, [1] = Y axis, [2] = Z axis. Range of values: 0 to 1023 per axis The values are initialized with the current raw values when the calibration is started with JoystickCalibrate, and maintained throughout the calibration. |
|
VT=u32 VN=3 |
R/W |
|
MP40/50 |
Minimum raw values of the joystick position for the calibration: [0] = X axis, [1] = Y axis, [2] = Z axis. Range of values: 0 to 1023 per axis The values are initialized with the current raw values when the calibration is started with JoystickCalibrate, and maintained throughout the calibration. |
|
JoystickPresent |
VT=boolean |
R |
ü |
MP40/50 |
"Joystick installed" identifier. 1 indicates that a joystick is installed. |
VT=string VL=11 |
R |
14 |
All 10 |
Creation date for the key configuration. Example: "2004-08-12" |
|
KeyCfgState |
VT=boolean |
R |
14 |
All |
Key configuration status: 0 = Invalid, 1 = Valid |
VT=string VL=89 |
R |
14 |
All 10 |
User information for the key configuration. |
|
VT=string VL=6 |
R |
14 |
All 10 |
Version of the key configuration. Example: "01.00" |
|
VT=u8 |
R/W |
|
All |
Number of active key layers: 0 to 3 |
|
VT=u8 |
R |
|
All |
0 = Shift 1 = Toggle 2 = One-shot |
|
LinkFpgaVersion |
VT=string VL=16 |
R |
ü |
APC510 APC511 APC620 5 7 APC810 PPC700 5 7 22 25 |
Version of the AP Link FPGA firmware. Example: "0.01" |
LinkPresent |
VT=boolean |
R |
ü |
APC620 5 7 APC810 PPC700 5 7 22 |
Indicates whether an AP link is present: 0 = Not provided 1 = Provided |
LinkType |
VT=string VL=5 |
R |
ü |
APC620 5 7 APC810 PPC700 5 7 22 25 |
Type of AP Link. Example: "SDLT" = SDL transmitter |
LockTime |
VT=u32 |
R/W |
|
APC510 APC511 APC620 6 APC810 APC820 APC910 APC2100 PP500 PPC700 6 PPC800 PPC900 PPC2100 |
Panel lock time in ms: 0 (no locking) to 65535 |
ModelNumber |
VT=string VL=41 |
R |
ü |
All 8 10 18 28 |
Model number of the PC. |
ModeNode |
VT=u8 |
R |
|
APC511 MP100/200 PP100/200 PP300/400 PP500 26 |
Mode/node switch setting. |
MtcxBootInfo |
VT=i32 |
R |
ü |
APC510 APC511 APC910 APC2100 PP500 27 PPC900 PPC2100 |
MTCX Firmware Bootinfo: 0 = Booted from low area 1 = Booted from high area |
MtcxFpgaVersion |
VT=string VL=16 |
R |
ü |
APC620 APC810 APC820 PP300/400 PPC300 PPC700 PPC800 |
Version of the MTCX (Maintenance Controller Extended) FPGA firmware. Example: "1.04" |
MtcxPx32Version |
VT=string VL=16 |
R |
ü |
APC620 APC810 APC820 PP300/400 PPC300 PPC700 PPC800 |
Version of the MTCX (Maintenance Controller Extended) PX32 firmware. Example: "1.19" |
MtcxVersion |
VT=string VL=16 |
R |
ü |
APC510 APC511 APC910 APC2100 PP500 26 PPC900 PPC2100 |
Version of the MTCX (Maintenance Controller Extended) firmware. Example: "00.20" |
MxcVersion |
VT=string VL=16 |
R |
ü |
MP100/200 PP100/200 |
Version of the MXC (Matrix Controller) firmware. Example: "02.00" |
OptimizedId |
VT=u8 |
R |
ü |
APC620 PPC700 |
Optimized ID. The optimized ID is set with the DIP switch on the baseboard and determines the BIOS profile to be used. Bits 0 - 5 define the BIOS profile; bits 6 and 7 are reserved. |
ParentCompatibilityId |
VT=u16 |
R |
ü |
APC510 APC511 APC620 23 APC810 APC820 APC910 APC2100 PP300/400 PP500 28 PPC300 PPC700 23 PPC800 PPC900 PPC2100 |
PC parent compatibility ID (FFFFh = no parent). Specifies the compatibility ID of the PC from which the current device was derived (e.g. for a custom variant of a standard device). |
ParentDeviceId |
VT=u32 |
R |
ü |
APC510 APC511 APC620 23 APC810 APC820 APC910 APC2100 PP300/400 PP500 28 PPC300 PPC700 23 PPC800 PPC900 PPC2100 |
PC parent device ID (FFFFFFFFh = no parent). Specifies the device ID of the PC from which the current device was derived (e.g. for a custom variant of a standard device). |
VT=boolean |
R/W |
|
MP40/50 |
Calibration mode of the override potentiometer. Writing with 1 begins the calibration and 0 ends it. |
|
VT=boolean |
R |
|
MP40/50 |
"Override potentiometer calibrated" identifier. 1 indicates that the override potentiometer is calibrated. When 0, the potentiometer must be calibrated (see also PotentiometerCalibrate). |
|
PotentiometerPresent |
VT=boolean |
R |
ü |
MP40/50 |
"Override potentiometer installed" identifier. 1 indicates that an override potentiometer is installed. |
VT=u32 |
R |
|
MP40/50 |
Calibrated value of the override potentiometer. Range of values: Is set during calibration (see also PotentiometerValueRange). The override potentiometer must be calibrated (see also PotentiometerCalibrated). |
|
VT=u32 |
R/W |
|
MP40/50 |
Specifies the range for the calibrated value = maximum value. Range of values: 0 to 127 On a MP40/50 the value 127 is recommended; this is preset by default with PotentiometerCalibrate. |
|
VT=u32 |
R |
|
MP40/50 |
Raw value of the override potentiometer. Range of values: 0 to 1023 |
|
VT=u32 |
R/W |
|
MP40/50 |
Maximum raw value of the override potentiometer for the calibration: Range of values: 0 to 1023 The value is initialized with the current raw value when the calibration is started with PotentiometerCalibrate, and maintained throughout the calibration. |
|
VT=u32 |
R/W |
|
MP40/50 |
Minimum raw value of the override potentiometer for calibration: Range of values: 0 to 1023 The value is initialized with the current raw value when the calibration is started with PotentiometerCalibrate, and maintained throughout the calibration. |
|
PowerOnCycles |
VT=u16 |
R |
ü |
APC510 APC511 APC620 APC810 APC820 APC910 APC2100 PP300/400 PP500 26 PPC300 PPC700 PPC800 PPC900 PPC2100 |
Number of power-ons for the PC. |
PowerOnHours |
VT=u16 |
R |
|
APC510 APC511 APC620 APC810 APC820 APC910 APC2100 MP40/50 17 PP300/400 PP500 27 PPC300 PPC700 PPC800 PPC900 PPC2100 |
Number of operating hours for the PC. |
PowerTemperature |
VT=i8 |
R |
|
APC620 APC810 APC820 PPC700 PPC800 |
Power supply temperature in degrees Celsius (positive values only). |
SerialNumber |
VT=string VL=12 |
R |
ü |
APC510 APC511 APC620 APC810 APC820 APC910 APC2100 MP40/50 18 PP300/400 PP500 28 PPC300 PPC700 PPC800 PPC900 PPC2100 |
Serial number of the PC. |
SmcVersion |
VT=string VL=16 |
R |
ü |
MP100/200 PP100/200 |
Version of the SMC (System Management Controller) firmware. Example: "d.4" |
StandbyVoltage |
VT=f32 |
R |
|
APC620 PPC700 |
Standby voltage (5 Vsb) in volts. |
Sys1Temperature |
VT=i8 |
R |
|
APC510 APC511 APC910 APC2100 PP500 PPC900 PPC2100 |
Temperature of Sensor 1 for the system unit in degrees Celsius. 29 |
Sys2Temperature |
VT=i8 |
R |
|
APC510 APC511 APC910 APC2100 PP500 PPC900 PPC2100 |
Temperature of Sensor 2 for the system unit in degrees Celsius. 29 |
Sys3Temperature |
VT=i8 |
R |
|
APC510 APC511 APC910 APC2100 PP500 PPC900 PPC2100 |
Temperature of Sensor 3 for the system unit in degrees Celsius. 29 |
Sys4Temperature |
VT=i8 |
R |
|
APC510 APC511 APC910 APC2100 PP500 PPC900 PPC2100 |
Temperature of Sensor 4 for the system unit in degrees Celsius. 29 |
VT=boolean |
R/W |
|
MP100/200 PP100/200 PP300/400 PPC300 |
Status of the User LED: 0 = Off, 1 = On On a B&R Mobile Panel, the User LED cannot be seen from outside. On a PPC300 or PP300/400, the User LED is operated as Power LED by default, until the first time UserLed is written. A switched on user LED is lit yellow, whereas a switched off user LED is lit green. The LED status setting only takes effect until the next time the system is started. After the system is started, the User LED is turned off. |
|
UserlogoComment |
VT=string VL=33 |
R |
ü |
MP100/200 PP100/200 4 PP300/400 PPC300 |
User logo comment. The comment generally contains the filename, date, and time of the bitmap being used. Example: "pp640.bmp 2003/08/21 15:03:52" |
UserlogoSize |
VT=u32 |
R |
ü |
MP100/200 PP100/200 4 PP300/400 PPC300 |
Size of the user logo in bytes. |
UserlogoVgaMode |
VT=u16 |
R |
ü |
|
obsolete - replaced by UserlogoVesaMode |
VT=u16 |
R |
ü |
MP100/200 PP100/200 4 PP300/400 PPC300 |
VESA mode used by the user logo. 0121h = 320 x 240 pixels (QVGA) 0101h = 640 x 480 pixels (VGA) 0103h = 800 x 600 pixels (SVGA) 0105h = 1024 x 768 pixels (XGA) Only on the PPC300 and PP300/400: 0125h = 1152 x 864 pixels (XGA+) 0107h = 1280 x 1024 pixels (SXGA) 0131h = 1600 x 1200 pixels (UXGA) |
|
UserSerialId |
VT=u32 |
R/W 9 |
|
All 10 18 |
User serial ID The user serial ID allows you to give the B&R device your own identification number. The user serial ID is permanently saved on the B&R device. With some devices, the PC must be restarted in order for a new user serial ID to take effect. On the PP100/200 and MP100/200, the user serial ID can only be configured from BIOS setup. |
VendorId |
VT=u32 |
R |
ü |
APC510 APC511 APC620 APC810 APC820 APC910 APC2100 MP40/50 18 PP300/400 PP500 28 PPC300 PPC700 PPC800 PPC900 PPC2100 |
Manufacturer ID of the PC (B&R = 0). |
VT=u32 |
R/W |
|
APC510 APC511 APC620 APC810 APC820 APC910 APC2100 PP300/400 PP500 PPC300 PPC700 PPC800 PPC900 PPC2100 |
Maximum watchdog time in ms. The watchdog is disabled once more when writing 0 to this variable. |
|
VT=u32 |
R/W |
|
APC510 APC511 APC620 APC810 APC820 APC910 APC2100 PP300/400 PP500 PPC300 PPC700 PPC800 PPC900 PPC2100 |
Minimum watchdog time in ms. The watchdog is disabled once more when writing 0 to this variable. |
|
VT=boolean |
R/W |
|
APC510 APC511 APC620 APC810 APC820 APC910 APC2100 PP300/400 PP500 PPC300 PPC700 PPC800 PPC900 PPC2100 |
Variable for acknowledging the watchdog. This variable always returns the value 0. The watchdog is acknowledged when this variable is written to. The written value is not evaluated. Before this variable is "removed" with PviUnlink or PviDelete, the watchdog must be disabled by writing 0 to the WatchdogMinTime or WatchdogMaxTime variable. |
|
VT=boolean |
R/W |
|
APC620 APC810 APC820 APC910 APC2100 PPC700 PPC800 PPC900 PPC2100 |
Specifies whether WMI is used: 0 = WMI not used 1 = WMI used WMI (Windows Management Instrumentation) is the Microsoft implementation of Web-Based Enterprise Management (WBEM), which builds upon the Common Information Model (CIM), a computer industry standard for defining device and application properties that system administrators and management programs can use to control devices and applications from various manufacturers or sources using the same method. WMI is not supported in Windows CE. With Windows 7 and higher, administrator rights are required: PVI Manager must be run as a service or with administrator rights! If WMI is enabled, ADI uses WMI functions whenever possible, for example to read the CPU temperature with the CpuTemperature variable. |
|
WriteProtect |
VT=boolean |
R |
|
MP100/200 10 PP100/200 10 |
Setting for the write-protect switch: 0 = Off, 1 = On |
1 |
Only 240 valid bytes are returned with ADI driver version 1.42 or lower on the APC620 and PPC700. The last 16 bytes are returned with 0s. |
2 |
An empty string is returned if no aPCI module or FPGA is present. |
3 |
Requires BIOS version 1.04 or higher on the PP100/200. |
4 |
Requires BIOS version 0.70 or higher on the PP100/200. |
5 |
Requires MTCX FPGA version 1.12 or higher on the APC620 and PPC700. |
6 |
Requires MTCX PX32 version 1.30 or higher on the APC620 and PPC700. |
7 |
Requires MTCX PX32 version 1.50 or higher on the APC620 and PPC700. |
8 |
Requires factory settings version 6 or higher on the PP100/200 and MP100/200. |
9 |
The user serial ID can only be read on the PP100/200 and MP100/200. |
10 |
Requires ADI driver version 2.00 or higher on the PP100/200 and MP100/200. |
11 |
VL=4 and version returns e.g. "6" on the PP100/200 and MP100/200. |
12 |
Requires ADI driver version 1.60 or higher on the APC620 and PPC700. |
13 |
Only available with the X855GME CPU board on APC720 and PPC700. |
14 |
The value can only be modified by updating the key configuration. |
15 |
Requires ADI driver version 1.20 or higher on the PP300/400. |
16 |
Requires ADI driver version 1.70, MTCX PX32 version 1.63 or higher, MTCX FPGA version 1.19 or higher, and a suitable hardware revision on the APC620 and PPC700. |
17 |
Requires ADI driver version 1.10 or higher on the MP40/50. |
18 |
Requires ADI driver version 1.20 or higher on the MP40/50. |
19 |
Requires ADI driver version 1.10 or higher on the PPC300. |
20 |
Requires ADI driver version 1.80 or higher on the APC620 and PPC700. |
21 |
To read the CPU temperature via WMI on a PPC800 with a CCAX CPU board (NM10 chipset) you need BIOS version 1.10 or higher. |
22 |
An AP link is not supported on PPC700 devices - the variables are also supported on PPC700 devices to ensure compatibility with old versions of the ADI line. |
23 |
Requires ADI driver version 1.90 or higher and MTCX PX32 version 1.67 or higher on APC620 and PPC700. |
24 |
ADI driver version 1.90 or lower on the APC620 and PPC700 returns "815E", "855GME" or "X855GME". |
25 |
No longer supported on APC620 and PPC700 with ADI driver version 2.00 or higher. |
26 |
Requires ADI driver version 1.1 or higher on the PP500. |
27 |
Requires ADI driver version 1.3 or higher on the PP500. |
28 |
Requires ADI driver version 1.3 or higher on the PP500. Older versions return data for the CPU board instead of the system unit. |
29 |
Optional temperature sensor: Depending on the system unit, a temperature may not be supported |
30 |
The temperature is only provided if WmiEnable is set to 1. |
31 |
A second slide-in is not supported on PPC700 devices - the variables are also supported on PPC700 devices to ensure compatibility with old versions of the ADI line. |
32 |
Requires ADI driver version 2.2 or higher on the PP500. |
The key configuration is created with the B&R Key Editor and contains the key code assignments for the keys of the B&R device, the operating mode of the key levels, the definitions of the key switches and special LEDs (key level, scroll/lock/shift etc.) and the panel lock time.
When creating the key configuration, a version (see the KeyCfgVersion variable) and user info (see the KeyCfgUserInfo variable) can be specified. The creation date that can be read with the KeyCfgBuildDate variable is set automatically by the B&R Key Editor when the key configuration is generated.
The keys on a B&R device can be operated on four different layers, which means each key can send up to four different key codes. The layer can be switched with special layer keys. These key layers are configured with the B&R Key Editor in the key configuration.
The key layers affect the Keys and KeyMatrix variables on all panel devices.
A key layer is only active in "Shift" mode as long as the corresponding layer key is pressed. The layer key must be pressed together with the desired key (corresponds to the function of a SHIFT key).
In "Toggle" mode, a key layer can be turned on or off using the layer key defined. That means each time this key is pressed, the level is toggled between the current level and the configured level.
In "One-shot" mode, pressing the level key only has an effect on the key pressed immediately afterwards. Once the action is complete, it switches back to the current level.
The panel locking time specifies how long input from keys or touch screens on other connected B&R panels is locked while input is being carried out on a particular panel. The panel lock time is usually set in the key configuration created in the B&R Key Editor.
The panel locking time is reset to the value configured in the key configuration when the system is restarted or when downloading a new key configuration.
These states can occur:
0 = Firmware not found
1 = Invalid firmware size (data destroyed)
2 = Module not found
3 = Cannot start boot mode
4 = Boot failed
5 = Boot OK
PP100/200 BIOS version 1.04 and higher:
6 = Old firmware (old version)
7 = Incorrect firmware (incorrect device ID or variant)
PP100/200 BIOS version 1.05 and higher:
8 = Boot disabled (in BIOS setup)
Only on PP300/400:
9 = Boot active
10 = Invalid firmware checksum
A user log can be displayed instead of the B&R logo when starting BIOS on the PPC300, PP100/200 PP300/400, and the MP100/200. The user log can be created from a Windows bitmap file using the B&R Windows USERLOGO.exe application and programmed onto the device using the ADI Control Center or the device-specific DOS Boot Logo Disk.
DVI data is intended for internal use at B&R.
The DVI channels are mapped as follows: The first DVI channel is used for the monitor / panel port. The second DVI channel is used for the optional Display / AP Link.
The watchdog can be used for the life sign monitoring of applications.
After setting the minimum and maximum time (WatchdogMinTime and WatchdogMaxTime variables), the watchdog is inactive and must be started by writing to the WatchdogToggle variable. After that happens, the WatchdogToggle variable must be written to periodically within the specified time to acknowledge watchdog.
Specify a long maximum time to keep the load needed to acknowledge the watchdog on the CPU to a minimum.
If the watchdog is acknowledged by writing to the WatchdogToggle variable before the specified minimum time has elapsed, or the maximum time is allowed to run out, and the WatchdogToggle variables hasn't been written to, the PC is reset.
Stop an active watchdog during a download (e.g. key configuration). Otherwise, a PC reset may occur if the specified watchdog time is shorter than the time required for longer flash access.
The watchdog is reactivated by writing the minimum and maximum times again. If the minimum and maximum times are set to 0, the watchdog can no longer be started, even with the WatchdogToggle variable.
Windows requires the system to be shut down properly. This doesn't happen if a reset occurs. This can lead to data loss which can leave the system or application "paralyzed".
Start the calibration by writing 1 to JoystickCalibrate. To calibrate, move the joystick from the center position to the extreme positions (e.g. by rotating the joystick in a full circle) and read the associated data using JoystickPosRaw. The raw values for the minimum and maximum position are then automatically saved as JoystickPosRawMin, JoystickPosRawMax and JoystickPosRawCenter. Using JoystickPosRange you can set the value range of the joystick.
Note: JoystickPosRawMin, JoystickPosRawMax, JoystickPosRawCenter and JoystickPosRange are set automatically during calibration and maintained, and therefore do not need to be set manually.
End the calibration by writing 0 to JoystickCalibrate.
When the calibration is complete, the joystick's calibrated values can be read using JoystickPos.
The calibration is permanently saved on the device, and is applied after the system is restarted (requires ADI driver version 1.21 or higher on MP40/50).
Start the calibration by writing 1 to PotentiometerCalibrate. To calibrate the potentiometer, turn it to the minimum and maximum position and read the corresponding raw values using PotentiometerValueRaw. The raw values for the minimum and maximum position are then maintained in PotentiometerValueRawMin and PotentiometerValueRawMax. Using PotentiometerValueRange you can set the value range of the potentiometer.
Note: PotentiometerValueRawMin, PotentiometerValueRawMax and PotentiometerValueRange are set automatically during calibration and maintained, and therefore do not need to be set manually.
End the calibration by writing 0 to PotentiometerCalibrate.
When the calibration is complete, the potentiometer's calibrated values can be read using PotentiometerValue.
The calibration is permanently saved on the device, and is applied after the system is restarted (requires ADI driver version 1.21 or higher on MP40/50).