Honeywell C-Bus communication protocol

Supported device types and versions
Communication line configuration
Communication station configuration
I/O tag configuration
Installation of KMFB02CB driver (obsolete)
Literature
Changes and modifications
Document revisions

Supported device types and versions

This protocol supports communication with Honeywell devices based on the C-Bus communication bus.

It supports Honeywell devices, series EXCEL (XL20, XL50, 500,....). Communication has also been tested against LION Controller CLLIONLC01.

Communication line configuration

Following physical communication interfaces can be used:

ISA card KMFB02 (Incos a.s. Zilina) with firmware by Ipesoft s.r.o. (stored in EPROM). The communication is performed using baud rates 4800 Bd, 9600 Bd, or 19200 Bd. The card requires the driver KMFB02CB.SYS installed in Windows NT/2000.
Parameters:

Communication line category: Honeywell C-Bus.
Line parameters (C-Bus tab).
Device ID – is C-Bus Id which is assigned to the KMFB02 card. It must be an unused number in the range of 1 to 30, reserved for KMFB02 in the C-Bus network.
Baud rate – is a baud rate of C-Bus. Supported baud rates: 4800, 9600, and 19200 Bd.

Communication computer KPX02 with firmware by Ipesoft s.r.o.
D2000 KOM process on a computer equipped with an RS-485 interface (tested on a Techbase NPE X500 M3 industrial computer based on Raspberry PI)
D2000 KOM process communicating via Moxa N-Port with an RS-485 interface (this combination may not meet protocol timing requirements)
Parameters:

Communication line category:: Serial (communication via serial port), SerialOverUDP Device Redundant (communication via a serial server in UDP mode)

Communication line protocol parameters

Configuration line dialog box - tab Protocol parameters.
They influence some of the optional protocol parameters. The following line parameters can be set:

Table 1

Keyword	Full name	Description	Unit	Default value

Keyword	Full name	Description	Unit	Default value
DID	Device ID	This parameter is not used for the Honeywell C-Bus line. For other line types, it has a similar meaning as the "Device ID" parameter on the Honeywell C-Bus line: it is the C-Bus Id assigned to the D2000 KOM process. It must be an unused number between 1 and 30 reserved for the D2000 KOM process on the C-Bus network.	1-30	30
BR	Baud Rate	This parameter is not used for the Honeywell C-Bus line. For other line types, it has a similar meaning as the "Baud Rate" parameter on the Honeywell C-Bus line: it is the C-Bus baud rate, supported baud rates are 4800, 9600, and 19200 Bd. Note: for Line Mode = Direct and a Serial line, the parameter must match the communication speed configured on the line.	baud	9600
LM	Line Mode	Mode of communication with C-Bus: ISA card - uses ISA card KMFB02 (obsolete) KPX02 - use of KPX02 communication computer Direct - direct communication via RS-485 serial interface	ISA card KPX02 Direct	Direct
KL	KOM Latency	The parameter allows "tuning" of time parameters. A positive value decreases the wait before sending a message, a negative value increases the wait. Reducing the wait can compensate for the slowness of the communication computer.	0.1 ms	0
DI	Debug Input	Debugging messages for input data. The parameter is a bitmask, meaning of individual bits is as follows: 1.bit - debugging of received data - priority task handling RS-485 interface (for Line Mode = Direct) 2.bit - debugging of received packets with correct CRC - priority task handling RS-485 interface (for Line Mode = Direct) 3.bit - debugging of received packets with correct CRC - line service task 4.bit - debugging of received values - line service task 5.bit - debugging of analyzed packets - line service task	-	0
DI	Debug Output	Debugging messages for output data. The parameter is a bitmask, meaning of individual bits is as follows: 1.bit - debugging of sent data - priority task serving RS-485 interface (for Line Mode = Direct) 2.bit - debugging of special packets - priority task serving RS-485 interface (for Line Mode = Direct) 3.bit - debugging of sent data - line service task 4.bit - debugging of composed requests - line service task 5.bit - debugging of reading the list of points - line service task	-	0