XFOX762.tlk Driver Reference
Foxboro 762C/762CSA/743CB Micro Controllers Driver
This driver requires that you have TAS-HMITalk 8.04 installed.
XFOX762 driver allows you to communicate with the FOXBORO 762C
and 762CSA SINGLE STATION MICRO Controllers and the 743CB FIELD
STATION MICRO Controllers. This driver has been developed
according to the Foxboro Instruction Book MI 018-888.
RECOMMENDATIONS:
- Use pins 24 and 25 in the back of the controller to connect to the
RS485 serial port of the controller. Check this with your controller's
manual to see if this pins have not changed from previous versions
of the controller.
- Use an RS-232/485 converter to connect the controller to your PC.
- Set the RTS signal to ON while transmitting and receiving.
- Make sure that the controller station address, baudrate, parity, databits
and stop bits are correctly configured in the driver.
Loop Controllers
FOXBORO 762C Single Station Micro Controllers
FOXBORO 762CSA Single Station Micro Controllers
FOXBORO 742C Field Station Micro Controllers
Read Current Set Point, Measurement, Output, Status and Alarm Values
Read Controller Inputs #1 to #4
Write Current Set Point, Measurement, Output, Status or Alarm Values
Read Controller Memory As Bytes
Read Controller Memory As Bits
Read Controller Memory As Words
Write Controller Memory As Bytes
Write Controller Memory As Bits
Write Controller Memory As Words
Read Current Computer Variables, Controller Outputs and I/O Settings
Read Current Set Point, Measurement, Output, Status or Alarm Values From The Secondary Controller
Write Current Set Point or Secondary Controller Output
COMMAND DESCRIPTION:
Reads the current values for the set point, measurement, and
output, plus additional controller status and alarm information.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Analog Input
HMITalk1.DriverNumPoints = 1-19
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 11
RETURNS:
- HMITalk1.PointValue(0) = Primary controller set point.
- HMITalk1.PointValue(1) = Primary controller measured value.
- HMITalk1.PointValue(2) = Primary controller output.
- HMITalk1.PointValue(3) = FLAG BYTE/Bit 0: User interface entered indicator:
0 = not entered
1 = entered subsequent to last host acknowledgment
- HMITalk1.PointValue(4) = FLAG BYTE/Bit 1: Primary A/M setting
0 = MANUAL
1 = AUTO
- HMITalk1.PointValue(5) = FLAG BYTE/Bit 2: W/P setting
0 = PANEL
1 = WORKSTATION
- HMITalk1.PointValue(6) = FLAG BYTE/Bit 3: Primary R/L setting
0 = LOCAL
1 = REMOTE
- HMITalk1.PointValue(7) = FLAG BYTE/Bit 4:
1 = CONTROLLER OUTPUT LIMITED HIGH
- HMITalk1.PointValue(8) = FLAG BYTE/Bit 5:
1 = CONTROLLER OUTPUT LIMITED LOW
- HMITalk1.PointValue(9) = FLAG BYTE/Bit 6: Ctrl Bypass State
0 = Bypass not active
1 = Bypass active
- HMITalk1.PointValue(10) = FLAG BYTE/Bit 7: Alarm indicator
0 = No alarms
1 = Alarm present (See ALARM BYTE)
- HMITalk1.PointValue(11) = ALARM BYTE/Bit 0: (Only valid if BIT 1 = 1)
0 = ALARM 4 is LEVEL 2 alarm
1 = ALARM 4 is LEVEL 1 alarm
- HMITalk1.PointValue(12) = ALARM BYTE/Bit 1:
0 = No ALARM 4 exists
1 = ALARM 4 exists
- HMITalk1.PointValue(13) = ALARM BYTE/Bit 2: (Only valid if BIT 3 = 1)
0 = ALARM 3 is LEVEL 2 alarm
1 = ALARM 3 is LEVEL 1 alarm
- HMITalk1.PointValue(14) = ALARM BYTE/Bit 3:
0 = No ALARM 3 exists
1 = ALARM 3 exists
- HMITalk1.PointValue(15) = ALARM BYTE/Bit 4: (Only valid if BIT 5 = 1)
0 = ALARM 2 is LEVEL 2 alarm
1 = ALARM 2 is LEVEL 1 alarm
- HMITalk1.PointValue(16) = ALARM BYTE/Bit 5:
0 = No ALARM 2 exists
1 = ALARM 2 exists
- HMITalk1.PointValue(17) = ALARM BYTE/Bit 6: (Only valid if BIT 7 = 1)
0 = ALARM 1 is LEVEL 2 alarm
1 = ALARM 1 is LEVEL 1 alarm
- HMITalk1.PointValue(18) = ALARM BYTE/Bit 7:
0 = No ALARM 1 exists
1 = ALARM 1 exists
COMMAND DESCRIPTION:
Reads analog inputs #1 to #4 current values.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Analog Input
HMITalk1.DriverNumPoints = 1-4
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 32
HMITalk1.DriverP2 = 512
HMITalk1.DriverP3 = -40
COMMAND DESCRIPTION:
Writes the setpoint value or the primary controller output, as
well as to change the status of some flags like A/M, R/L and to
acknowledge alarms in the controller.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Analog Output
HMITalk1.DriverNumPoints = 1
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 12
HMITalk1.DriverP2 = Defines the STATUS BYTE (here it acts like a sub-command).
This command is used to change the setpoint value or the
primary controller output, as well as to change the status
of some flags like A/M, R/L and to acknowledge alarms in
the controller.
There is no command which allows you to change the setpoint or output
only, without in turn having to indicate some other related data.
Thus, it is necessary to specify in all cases the STATUS
BYTE through HMITalk1.DriverP2.
According to the value provided in HMITalk1.DriverP2, the current Analog Output value may
or may not be used. The Analog Output value is only used and sent to the
controller in those cases where the STATUS BYTE BIT0 is 1.
At that point, BIT5 decides if what is to be changed is the
setpoint or the output. The Analog Output value must be taken to internal
controller format like in the case of the WRITE COMMAND.
If BIT0 is 0, the Analog Output value is not sent and the command is used
to change some operation flag or to be notified of the alarm
status.
STATUS BYTE:
- Bit 0: Change Indicator
0 = No new output or setpoint
1 = New output or setpoint is being specified via
bits 4, 5 & 6 if incremental, or value if
absolute.
- Bit 1: A/M Setting:
0 = MANUAL
1 = AUTO
- Bit 2: User interface acknowledgement:
0 = No acknowledgement.
1 = Acknowledgement.
- Bit 3: R/L Setting:
(R/L is ignored if the controller is configured
for LOCAL only).
0 = LOCAL
1 = REMOTE
- Bit 4: Size of step change:
0 = SMALL STEP
1 = LARGE STEP
- Bit 5: Output Vs setpoint or W/P:
0 = Select panel if Bit 0 = 0
1 = Select workstation if Bit 0 = 0
0 = Change output if Bit 0 = 1
1 = Change setpoint if Bit 0 = 1
- Bit 6: Direction of change:
0 = Increment the setting.
1 = Decrement the setting.
- Bit 7: Alarm acknowledge:
0 = No acknowledge.
1 = acknowledge all current alarms.
Examples:
- P2 = 01h ==> Set MANUAL, LOCAL, WORKSTATION modes and
without alarm acknowledgement,sending the
Analog Output value as the new controller output.
(Appropriate scaling is 0, 1, 0, 40)
- P2 = 20h ==> Set MANUAL, LOCAL, WORKSTATION modes and
without alarm acknowledgement.
- P2 = 21h ==> Set MANUAL, LOCAL, WORKSTATION modes and
without alarm acknowledgement,sending the
Analog Output value as the new setpoint.
(Appropriate scaling is 0, 1, 0, 40)
- P2 = 22h ==> Set AUTOMATIC, LOCAL, WORKSTATION modes and
without alarm acknowledgement.
- P2 = 23h ==> Set AUTOMATIC, LOCAL, WORKSTATION modes and
without alarm acknowledgement, but sending
the Analog Output value as the new setpoint.
(Appropriate scaling is 0, 1, 0, 40)
- P2 = A2h ==> Set AUTOMATIC, LOCAL, WORKSTATION mode and
with alarm acknowledgement. (Note that in
the previous commands, 80h is added to any
previous command for alarm acknowledgement).
NOTE:
R/L is ignored if the controller is configured for LOCAL only.
COMMAND DESCRIPTION:
Writes the setpoint value in the controller.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Analog Output
HMITalk1.DriverNumPoints = 1
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 12
HMITalk1.DriverP2 = 35
COMMAND DESCRIPTION:
Writes the output current value in the controller.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Analog Output
HMITalk1.DriverNumPoints = 1
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 12
HMITalk1.DriverP2 = 1
COMMAND DESCRIPTION:
Sets the controller in manual or auto mode.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Digital Output
HMITalk1.DriverNumPoints = 1
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 12
WHERE:
- HMITalk1.PointValue(0) = 0 sets manual mode
- HMITalk1.PointValue(0) = 1 sets auto mode
COMMAND DESCRIPTION:
Sets the controller in manual mode.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Analog Output
HMITalk1.DriverNumPoints = 1
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 12
HMITalk1.DriverP2 = 32
COMMAND DESCRIPTION:
Sets the controller in auto mode.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Analog Output
HMITalk1.DriverNumPoints = 1
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 12
HMITalk1.DriverP2 = 34
COMMAND DESCRIPTION:
Writes the setpoint value in the controller.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Analog Output
HMITalk1.DriverNumPoints = 1
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 12
HMITalk1.DriverP2 = 35
COMMAND DESCRIPTION:
This command allows you to read bytes from the controller memory.
The controller's memory map information is included in
Appendix B of the Controller Manual.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Analog Input
HMITalk1.DriverNumPoints = 1-250
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 14
HMITalk1.DriverP2 = Initial memory address pointed
HMITalk1.DriverP3 = Conversion Factor
COMMAND DESCRIPTION:
This command allows you to read bytes of the controller memory as bits.
The controller's memory map information is included in
Appendix B of the Controller Manual.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Digital Input
HMITalk1.DriverNumPoints = 1-250
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 14
HMITalk1.DriverP2 = Initial memory address pointed
COMMAND DESCRIPTION:
Reads consecutive words from the controller memory.
It is a non-standard function which is very useful to read
parameters whose values are formed by 2 bytes.
In the case of packages, be careful to note that all the
data required are word-type, otherwise wrong results will
be obtained.
The controller's memory map information is included in
Appendix B of the Controller Manual.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Analog Input
HMITalk1.DriverNumPoints = 1-125
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 32
HMITalk1.DriverP2 = Initial memory address pointed
HMITalk1.DriverP3 = Conversion Factor
COMMAND DESCRIPTION:
This command allows you to write bytes of the controller memory.
The controller's memory map information is included in
Appendix B of the Controller Manual.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Analog Output
HMITalk1.DriverNumPoints = 1-125
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 13
HMITalk1.DriverP2 = Initial memory address pointed
HMITalk1.DriverP3 = Conversion Factor
COMMAND DESCRIPTION:
Writes the controller memory byte as bits.
The controller's memory map information is included in
Appendix B of the Controller Manual.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Digital Output
HMITalk1.DriverNumPoints = 1-8
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 13
HMITalk1.DriverP2 = Memory address pointed
COMMAND DESCRIPTION:
Writes consecutive words to the controller memory.
It is a non-standard function which is very useful to write
parameters whose values are formed by 2 bytes.
In the case of packages, be careful to note that all destination
parameters are word-type, otherwise wrong results will
be obtained.
The controller's memory map information is included in
Appendix B of the Controller Manual.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Analog Output
HMITalk1.DriverNumPoints = 1-125
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 33
HMITalk1.DriverP2 = Initial memory address pointed
HMITalk1.DriverP3 = Conversion Factor
COMMAND DESCRIPTION:
This command allows you to read a consecutive parameters as bytes.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Analog Input
HMITalk1.DriverNumPoints = 1-125
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 15
HMITalk1.DriverP2 = Parameter number to be read
HMITalk1.DriverP3 = Conversion Factor
COMMAND DESCRIPTION:
This command allows you to read a consecutive parameters as bits.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Digital Input
HMITalk1.DriverNumPoints = 1-250
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 15
HMITalk1.DriverP2 = Parameter number to be read
COMMAND DESCRIPTION:
This command allows you to write a consecutive parameters as bytes.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Analog Output
HMITalk1.DriverNumPoints = 1-83
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 16
HMITalk1.DriverP2 = Parameter number to be written
HMITalk1.DriverP3 = Conversion Factor
COMMAND DESCRIPTION:
Writes the parameter as bits.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Digital Output
HMITalk1.DriverNumPoints = 1-16
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 16
HMITalk1.DriverP2 = Parameter number to be written
COMMAND DESCRIPTION:
It allows you to read the value of the computed variables A, B, C,
D, E and F, the OUT1 and OUT2 controller outputs, setting of
CI1 and CI2 input, and setting of CO1 and CO2 output.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Analog Input
HMITalk1.DriverNumPoints = 1-12
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 17
RETURNS:
- HMITalk1.PointValue(0) = Value of the computed variable A
- HMITalk1.PointValue(1) = Value of the computed variable B
- HMITalk1.PointValue(2) = Value of the computed variable C
- HMITalk1.PointValue(3) = Value of the computed variable D
- HMITalk1.PointValue(4) = Value of the computed variable E
- HMITalk1.PointValue(5) = Value of the computed variable F
- HMITalk1.PointValue(6) = Value of the OUT1 output
- HMITalk1.PointValue(7) = Valor of the OUT2 output
- HMITalk1.PointValue(8) = Status of CI1 (0=OPEN, 1=CLOSED)
- HMITalk1.PointValue(9) = Status of CI2 (0=OPEN, 1=CLOSED)
- HMITalk1.PointValue(10) = Status of CO1 (0=OPEN, 1=CLOSED)
- HMITalk1.PointValue(11) = Status of CO2 (0=OPEN, 1=CLOSED)
COMMAND DESCRIPTION:
Reads the current values for the set point, measurement, and
output, plus additional controller status and alarm information
from the secondary controller. Since the secondary controller
works as REMOTE-ONLY, the R/L flag status will always indicate
REMOTE. Besides, except for the M/A status of the secondary
controller, all other data transmitted in the FLAG BYTE and in
ALARM BYTE will match those transmitted by the primary
controller poll command.
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Analog Input
HMITalk1.DriverNumPoints = 1-19
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 18
RETURNS:
- HMITalk1.PointValue(0) = Secondary controller setpoint
- HMITalk1.PointValue(1) = Secondary controller measured value
- HMITalk1.PointValue(2) = Secondary controller output
- HMITalk1.PointValue(3) = FLAG BYTE/Bit 0: User interface entered indicator:
0 = not entered
1 = entered subsequent to last host acknowledgment
- HMITalk1.PointValue(4) = FLAG BYTE/Bit 1: Primary A/M setting
0 = MANUAL
1 = AUTO
- HMITalk1.PointValue(5) = FLAG BYTE/Bit 2: W/P setting
0 = PANEL
1 = WORKSTATION
- HMITalk1.PointValue(6) = FLAG BYTE/Bit 3: Secondary R/L setting
0 = LOCAL
1 = REMOTE
- HMITalk1.PointValue(7) = FLAG BYTE/Bit 4:
1 = CONTROLLER OUTPUT LIMITED HIGH
- HMITalk1.PointValue(8) = FLAG BYTE/Bit 5:
1 = CONTROLLER OUTPUT LIMITED LOW
- HMITalk1.PointValue(9) = FLAG BYTE/Bit 6: Ctrl Bypass State
0 = Bypass not active
1 = Bypass active
- HMITalk1.PointValue(10) = FLAG BYTE/Bit 7: Alarm indicator
0 = No alarms
1 = Alarm present (See ALARM BYTE)
- HMITalk1.PointValue(11) = ALARM BYTE/Bit 0: (Only valid if BIT 1 = 1)
0 = ALARM 4 is LEVEL 2 alarm
1 = ALARM 4 is LEVEL 1 alarm
- HMITalk1.PointValue(12) = ALARM BYTE/Bit 1:
0 = No ALARM 4 exists
1 = ALARM 4 exists
- HMITalk1.PointValue(13) = ALARM BYTE/Bit 2: (Only valid if BIT 3 = 1)
0 = ALARM 3 is LEVEL 2 alarm
1 = ALARM 3 is LEVEL 1 alarm
- HMITalk1.PointValue(14) = ALARM BYTE/Bit 3:
0 = No ALARM 3 exists
1 = ALARM 3 exists
- HMITalk1.PointValue(15) = ALARM BYTE/Bit 4: (Only valid if BIT 5 = 1)
0 = ALARM 2 is LEVEL 2 alarm
1 = ALARM 2 is LEVEL 1 alarm
- HMITalk1.PointValue(16) = ALARM BYTE/Bit 5:
0 = No ALARM 2 exists
1 = ALARM 2 exists
- HMITalk1.PointValue(17) = ALARM BYTE/Bit 6: (Only valid if BIT 7 = 1)
0 = ALARM 1 is LEVEL 2 alarm
1 = ALARM 1 is LEVEL 1 alarm
- HMITalk1.PointValue(18) = ALARM BYTE/Bit 7:
0 = No ALARM 1 exists
1 = ALARM 1 exists
COMMAND DESCRIPTION:
This command is used to change the value of the setpoint or
secondary controller output. It is similar to the command used
for the primary controller although it has some restrictions
(for example, it cannot modify the LOCAL/REMOTE status since
the secondary controller is always in REMOTE mode).
PROPERTY SETTINGS REQUIRED:
HMITalk1.DriverDataType = Analog Output
HMITalk1.DriverNumPoints = 1
HMITalk1.DriverP0 = Controller Address (0-99).
HMITalk1.DriverP1 = 19
HMITalk1.DriverP2 = Defines the STATUS BYTE (here it acts like a sub-command).
This command is used to change the setpoint value or the
primary controller output, as well as to change the status
of some flags like A/M, R/L and to acknowledge alarms in
the controller.
There is no command which allows you to change the setpoint or output
only, without in turn having to indicate some other related data.
Thus, it is necessary to specify in all cases the STATUS
BYTE through HMITalk1.DriverP2.
According to the value provided in HMITalk1.DriverP2, the current Analog Output value may
or may not be used. The Analog Output value is only used and sent to the
controller in those cases where the STATUS BYTE BIT0 is 1.
At that point, BIT5 decides if what is to be changed is the
setpoint or the output. The Analog Output value must be taken to internal
controller format like in the case of the WRITE COMMAND.
If BIT0 is 0, the Analog Output value is not sent and the command is used
to change some operation flag or to be notified of the alarm status.
STATUS BYTE:
- Bit 0: Change Indicator
0 = No new output or setpoint
1 = New output or setpoint is being specified via
bits 4, 5 & 6 if incremental, or value if
absolute.
- Bit 1: A/M Setting:
0 = MANUAL
1 = AUTO
- Bit 2: User interface acknowledgement:
0 = No acknowledgement.
1 = Acknowledgement.
- Bit 3: Reserved.
- Bit 4: Size of step change:
0 = SMALL STEP
1 = LARGE STEP
- Bit 5: Output Vs setpoint or W/P:
0 = Select panel if Bit 0 = 0
1 = Select workstation if Bit 0 = 0
0 = Change output if Bit 0 = 1
1 = Change setpoint if Bit 0 = 1
- Bit 6: Direction of change:
0 = Increment the setting.
1 = Decrement the setting.
- Bit 7: Alarm acknowledge:
0 = No acknowledge.
1 = acknowledge all current alarms.
Examples:
- P2 = 01h ==> Set MANUAL, LOCAL, WORKSTATION modes and
without alarm acknowledgement,sending the
Analog Output value as the new controller output.
(Appropriate scaling is 0, 1, 0, 40)
- P2 = 20h ==> Set MANUAL, LOCAL, WORKSTATION modes and
without alarm acknowledgement.
- P2 = 21h ==> Set MANUAL, LOCAL, WORKSTATION modes and
without alarm acknowledgement,sending the
Analog Output value as the new setpoint.
(Appropriate scaling is 0, 1, 0, 40)
- P2 = 22h ==> Set AUTOMATIC, LOCAL, WORKSTATION modes and
without alarm acknowledgement.
- P2 = 23h ==> Set AUTOMATIC, LOCAL, WORKSTATION modes and
without alarm acknowledgement, but sending
the Analog Output value as the new setpoint.
(Appropriate scaling is 0, 1, 0, 40)
- P2 = A2h ==> Set AUTOMATIC, LOCAL, WORKSTATION mode and
with alarm acknowledgement. (Note that in
the previous commands, 80h is added to any
previous command for alarm acknowledgement).
[1005] DRIVER (Internal): Invalid driver stage
[1300] PROTOCOL (Timeout): No answer
[1410] PROTOCOL (Format): Invalid device id in response
[2147] CONFIG (NumValues): Only one value can be read or written
[2181] CONFIG (NumValues): Too many values (max=12)
[2185] CONFIG (NumValues): Too many values (max=125)
[2189] CONFIG (NumValues): Too many values (max=16)
[2193] CONFIG (NumValues): Too many values (max=19)
[2203] CONFIG (NumValues): Too many values (max=250)
[2235] CONFIG (NumValues): Too many values (max=8)
[2239] CONFIG (NumValues): Too many values (max=83)
[3018] CONFIG (P0): Invalid device address (0-99)
[3508] CONFIG (P1): Invalid command
[8073] CONFIG (Remote): Controller is in PANEL mode
[8183] CONFIG (Remote): Index requested too small
[8191] CONFIG (Remote): Invalid command byte
[8194] CONFIG (Remote): Invalid data
[8220] CONFIG (Remote): No data given with command
[8225] CONFIG (Remote): No permission for download
[8339] CONFIG (Remote): Transmission error
[8367] CONFIG (Remote): Wrong number of data bytes
This driver requires that you have TAS-HMITalk 8.04 installed.
Driver Source Code Last Update: 04/09/2007 19:23:46
Driver Reference Last Update: 10/30/2008 17:37:55
© 1990-2008, CPKSoft Engineering. All rights reserved.