STULZ_BMS_69B_0714_en

BMS 

Index 69B 

Edition 7.2014 

AIR CONDITIONING 

BUILDING MANAGEMENT SYSTEM 

TECHNICAL MANUAL

Contents 

1. Introduction.................................................................................................................5 

1.1 Overview and term definition.............................................................................................................5 

1.1.1 Building Management System BMS..........................................................................................5 

1.1.2 Data bus.....................................................................................................................................5 

1.1.3 Protocols....................................................................................................................................5 

1.1.4 Data points.................................................................................................................................5 

1.1.5 Data point lists...........................................................................................................................5 

1.1.6 Gateway.....................................................................................................................................6 

1.1.7 Controller...................................................................................................................................6 

2. Function principle of the Gateways...........................................................................7 

2.1 C7000AT and MIB7000......................................................................................................................7 

2.2 WIB8000............................................................................................................................................7 

2.3 Protocol converter..............................................................................................................................8 

3. Bus systems and protocols of Stulz units................................................................9 

3.1 IO bus................................................................................................................................................9 

3.2 Stulz bus..........................................................................................................................................10 

4. Supported BMS bus systems and protocols..........................................................11 

4.1 Modbus RTU....................................................................................................................................11 

4.2 SAIA.................................................................................................................................................12 

4.3 BACnet.............................................................................................................................................13 

4.4 LonWorks.........................................................................................................................................14 

4.5 HTTP / SNMP..................................................................................................................................15 

4.6 OTE..................................................................................................................................................15 

4.7 P90...................................................................................................................................................16 

4.8 SDC/Telecomptrol............................................................................................................................17 

5. Further connection modes.......................................................................................18 

5.1 Parallel operation of BMS and web interface...................................................................................18 

5.2 IOC with EBUS................................................................................................................................19 

5.3 C7000AT directly by BACnet MSTP.................................................................................................19 

5.4 Lon by MIB with LIB.........................................................................................................................20 

5.5 Lon by AT with LIB...........................................................................................................................20 

6. C7000AT board..........................................................................................................21 

6.1 Operational elements - (front)..........................................................................................................23 

6.2 Protocols..........................................................................................................................................23 

6.3 Adjustment by menus.......................................................................................................................24 

6.4 The BMS Connection.......................................................................................................................25 

7. MIB7000 board...........................................................................................................27 

7.1 Protocols..........................................................................................................................................28 

7.2 The Stulz-Bus...................................................................................................................................29 

7.2.1 C5000 controller.......................................................................................................................30 

7.2.2 C4000 controller.......................................................................................................................30 

7.2.3 C2020/C1010 controller...........................................................................................................30 

7.2.4 C7000 IOC with EBUS extension board..................................................................................31 

7.3 Start up............................................................................................................................................32 

7.3.1 Configuration of the MIB7000 Board........................................................................................32 

7.3.2 Wiring.......................................................................................................................................32 

7.3.3 Adjustments to build up the STULZ bus..................................................................................33 

7.4 The BMS Connection.......................................................................................................................36 

This manual refers to the software version C7000AT V4.09 resp. MIB 7000 v1.93. 

EN /07.2014/69B 3

8. Command Index........................................................................................................38 

8.1 System Commands..........................................................................................................................38 

8.2 IO-bus Commands (only for C7000AT)............................................................................................40 

8.3 STULZ - Bus Commands (only for MIB)..........................................................................................41 

8.4 BMS Commands..............................................................................................................................43 

9. Troubleshooting........................................................................................................47 

9.1 Wiring...............................................................................................................................................47 

9.2 STULZ Bus (only for MIB)................................................................................................................48 

9.3 BMS Connection..............................................................................................................................49 

10. Special functions - Sequencing (only for MIB).....................................................50 

10.1 Sequencing Commands.................................................................................................................50 

10.2 The Sequencing Function..............................................................................................................52 

10.3 Configuration..................................................................................................................................54 

A. Appendix...................................................................................................................55 

A1. Interfaces.........................................................................................................................................55 

A2. BMS - Timing...................................................................................................................................56 

B. Additional tools.........................................................................................................57 

4 EN /07.2014/69B

1. Introduction 

This manual helps you at the selection and start-up of a BMS. In the appendix you will find additional pages which 

explain the protocol you have ordered in detail. The protoccol description is useful especially for the commissioning. 

1.1 Overview and term definition 

1.1.1 Building Management System BMS 

A building management system serves to monitor and control air conditioning, ventilation or light control processes 

in buildings by PC and appropriate software. 

The software serves in the first place to communicate with the single control elements, to gather the responses of 

these components and to display these in an comprehensible form for the user. Moreover the software allows to send 

control commands (as e.g. modification of set values) by the user. 

The target of the application of such a technology is to minimize operating costs in modern buildings by monitoring 

building functions. 

1.1.2 Data bus 

A data bus provides the electrical transmission line between a BMS, the components connected to it and the components 

among each other. A data bus consists mostly of electric lines. Fibre optics or wireless connections are 

possible alternative solutions. 

1.1.3 Protocols 

For the communication between the BMS elements protocols are used. A protocol is the language by which the single 

elements communicate among each other, the medium of transmission are data busses. 

Each protocol consists of different data packages (a data package is a sequence of electric impulses on the lines, 

which correspond to the words of a language), a definition in which order these data packages are sent on the lines 

and the meaning of these. 

Just as for spoken languages many protocols exist, which have been designed each for a specific purpose of application. 

Examples for extensive protocols with a large complexity of commands are e.g. BACnet or Lon, which can be used 

for versatile tasks in the BMS scope, but which require on the other hand a relatively high effort of configuration. 

An example for a small, very specialized protocol, which require little effort of configuration, is e.g. the IO bus protocol 

from Stulz, which is used for the communication within the C7000 unit series. 

1.1.4 Data points 

The communication by means of protocols among the single elements serves to exchange data. All data in the Stulz 

controllers, which can be accessed, is represented as data points. Data points can either be read, written or read 

and written. Each data point features a value and an address, by which it can be addressed. Data point lists exist for 

a detailed description of all data points of the different controllers. 

1.1.5 Data point lists 

For all protocols which are supported by Stulz A/C units, by the help of which the BMS can access the single controllers, 

lists are provided. In these lists all data points are described by address, value range, unit etc.. 

You obtain the data point lists on request. 


See here some selected data points out of the data point list of the controller C7000IOC for the protocol 

Modbus (STULZ_udpl_149_modbus.pdf): 

There preset data point lists with a fixed set of data points and data point lists which are freely definable. 

1.1.6 Gateway 

As the controllers in the A/C units use a different protocol for the internal communication as uses the BMS, a protocol 

converter is required for the communication between controllers and the BMS. A protocol converter is also named 

a gateway. 

For the connection of Stulz controllers to a BMS the following gateways can be provided: 

C7000AT: for the connection of C7000IOC controllers 

MIB7000: 

for old controllers and C7000IOC via C7000AT 

WIB8000: for old controllers and C7000IOC via C7000AT, when HTTP or SNMP is required as protocol. 

Protocol converter: in combination with C7000AT or MIB7000, when a BMS protocol is required, which is not supported 

by AT respectively MIB. 

When a BMS connection is planned, it should be checked in the first step, whether the connection could run by a 

C7000AT. A C7000AT is present in most systems, as it also serves as graphical interface and terminal for the user 

directly at the A/C unit. 

1.1.7 Controller 

The controller contains all functions to control an A/C system. Depending on the A/C system type different controllers 

are used. In the C7000 IOC the Modbus protocol is already pre-installed so that a gateway is not necessary. 

Named "old controllers" are the Stulz controllers without the IO bus capability as: C1002, C1010, C2020, C4000, 

C5000 und C6000 bezeichnet. 


2. Function principle of the Gateways 

2.1 C7000AT and MIB7000 

The gateways C7000AT and MIB7000 are transparent for the BMS, i.e. the BMS sends its request to the global 

addresses resp. the CPU addresses of the controllers, as if these controllers were directly connected to the BMS. 

These requests are acknowledged by the gateway as substitute for the controller. C7000AT and MIB7000 buffer the 

controller data destined for the BMS and update these currently. This way requests by the BMS can be answered 

immediately, it is not necessary to wait for the communication between gateway and controller. 

2.2 WIB8000 

The WIB8000 represents a gateway, which provides an interface to TCP/IP 

networks by Ethernet. On the one hand the WIB8000 contains a web server, 

by which the A/C units can be administrated with the help of a web browser. 

On the other hand it contains a SNMP server, which provides data which 

can be used by a Network Management System. 


2.3 Protocol converter 

If A/C units shall be connected to a BMS, which is based on a protocol not provided by Stulz gateways, other protocol 

converters can be used as additional gateways. The connection between the protocol converter and Stulz A/C units 

equals the connection to a BMS from the point of view of the Stulz A/C units. 

The protocol converter is configured, so that it sequencially requests and buffers all desired data points from the 

controllers. Depending on the applicated protocol and configuration the protocol converter behaves differently towards 

the BMS. Some protocols allow to configure the protocol converter in such a way that it simulates several virtual 

servers towards the BMS, which all can be addressed by an individual address. This procedure corresponds to the 

request of controllers by C7000AT and MIB7000. 

Other protocols can only be configured in a way that the protocol converter represents itself as a single device, 

which provides all data points. See in the corresponding protocol converter manual which configuration alternatives 

are possible. 

Protocol 

converter 

Protocol converter configured as virtual server, the BMS can access single controller addresses. 

Protocol 

converter 

The protocol converter represents itself as one device towards the BMS, the assignment of data points to controllers 

can be found in the documentation. 


3. Bus systems and protocols of Stulz units 

The designations IOBus and Stulz-Bus/SDC actually do not describe a bus (here a serial, electrical transmission 

medium, RS485) but a combination of a bus and a protocol transmitted on it. As they are used as a unit, they are 

called IO bus and Stulz bus furthermore. 

3.1 IO bus 

The IO bus links units of the C7000 series. In an IO bus there can be 20 participants maximum, a participant being 

a C7000AT or C7000IOC. The combination of an AT and an IOC represents two participants for the IO bus. 

The C7000AT serves as graphical surface and as gateway for the BMS. The C7000AT can access all C7000IOCs in 

the bus. The C7000AT is, from a logical point of view, not linked closer to the IO controller, which is installed in the 

same A/C unit, as to all other controllers in the bus. 

The IO bus functions according to the MS/TP (Master-Slave/Token-Passing) principle, i.e. there exists always one 

unit which is the master. The master is authorized to send requests to other bus units, all other bus units are slaves 

and may only respond. After a certain time the master token is passed and the next unit becomes master. 

Each unit in an IO bus possesses an IO bus address which is unique within the bus in the range of 0 to 19. Furthermore 

each unit, which will be addressed by a BMS, needs a global address, which however is not used for the 

identification in the IO bus. It serves to identify single controllers across several busses. 

The value range for the global address depends of the applicated BMS protocol and extends for example from 1 to 

247 for Modbus RTU. 

The global addresses of the controllers in the IO bus are known to the C7000AT working as gateway, so that it can 

forward the corresponding BMS requests. 


3.2 Stulz bus 

The Stulz bus/SDC must be used, when there are old controllers such as C1002 till C6000 in the bus, or if the controllers 

will be accessed by a MIB or WIB. A Stulz bus consists of a bus master and up to 32 slave units. 

max. 

The Stulz bus is a Master-Slave-bus, in which there is one bus master, all other units in the bus are slaves. The 

complete bus communication is initiated by the master, all other bus units may only react to requests by the master. 

As the MIB the same as the WIB are bus masters, within a Stulz bus either a MIB or a WIB can be installed. This 

means, that old controllers can only be accessed by either a MIB or a WIB. 

In the Stulz bus the single controllers are identified by either their CPU address (old controllers) or the global address 

(C7000). C7000IOCs are transparently connected by the C7000AT for the bus master, i.e. the bus master addresses 

a C7000IOC address and the C7000AT forwards the request to the controller assigned to it. 

The bus master of a Stulz bus disposes of an address range assigned to the master for the administrated controllers. 

For a Modbus RTU BMS connection e.g. the address ranges are subdivided into the ranges 1...32, 33...64, and so 

forth, i.e. all controllers, which are connected to a bus master, must have global or CPU addresses of this range. 


4. Supported BMS bus systems and protocols 

Different bus systems and protocols are supported to connect Stulz A/C units to a BMS. C7000AT and MIB7000 

provide a serial RS232 or RS485 interface for the BMS connection. 

The following schemes display the preferred connection alternatives when the protocol is given. 

4.1 Modbus RTU 

developped by the Modicon company. 247 controllers can be addressed per each BMS port. 

max. 32 C7000AT 

as gateway 

IO bus 

max. 20 units 

incl. gateway 

C7000AT and C7000IOC 

IO bus 

max. 20 units 

incl. gateway 


IO bus 

max. 20 units 

incl. gateway 


max. 247 

C7000IOC 

The C7000AT can be directly connected to a BMS port as gateway between Modbus and IOBus. RS232 and RS485 

are provided by the C7000AT as transmission medium. With RS485 up to 32 C7000AT can be used as gateway. 

However, the maximum number of controllers addressed by the addresses 1 to 247 is 247. When RS232 is used for 

the connection between C7000AT and BMS, it is a 1:1 connection. Only one C7000AT can be linked as gateway 

and there are maximum 19 C7000IOCs in the IO bus. 

max. 8 MIB7000 

as gateway 

Stulz bus (SDC) 

RS485 max. 32 bus units 

IO bus 

max. 20 units 

incl. gateway 


max. 32 controllers per MIB 

incl. all controllers in the IO busses 

below the C7000AT 

IO bus 

max. 20 units 

incl. gateway 


If old controllers shall be linked to Modbus RTU, a MIB7000 is required as gateway. Maximum eight MIB7000 can be 

linked to a BMS by RS485 when Modbus RTU is used. Each MIB can address 32 controllers, for this a fixed address 

range is adjusted for each MIB. These ranges run from 1...32, 33...64 etc. 

By RS232 only one MIB7000 can be linked to a BMS as gateway. Maximum 32 controllers can be linked in this case. 


4.2 SAIA 

SAIA S-Bus has been developped by the company SAIA-Burgess Electronics AG. 255 controllers can be addressed 

per each BMS port. 

Three SAIA alternatives are supported, SAIA Break Mode, SAIA Parity Mode and SAIA Data Mode. 

max. 32 C7000AT 

as Ggateway 

IO bus 

max. 20 units 

incl. gateway 


IO bus 

max. 20 units 

incl. gateway 


IO bus 

max. 20 units 

incl. gateway 


max. 255 

C7000IOC 

The C7000AT can be directly connected to a BMS port by SAIA. RS232 and RS485 are provided by the C7000AT 

as transmission medium. With RS485 up to 32 C7000AT can be used as gateway. However, the maximum number 

of controllers with an address range of 0 to 254 is 255. 

When RS232 is used for the connection between C7000AT and BMS, it is a 1:1 connection. Only one C7000AT can 

be linked as gateway and there are maximum 19 C7000IOCs in the IO bus. 

You can find further information for the configuration and commissioning of the gateway and its connection to Stulz 

units in the separate appendix "Modbus RTU". 


4.3 BACnet 

BACnet means Building Automation and Control Networks and has been developped as company independent 

standard for the communication between the single units of the building automation. 

BACnet with C7000IOC controllers 

Protocol 

converter 

RS485 

interface depends on protocol. 

max. 32 C7000AT 

as gateway 

IO bus 

max. 20 units 

incl. gateway 


IO bus 

max. 20 units 

incl. gateway 


IO bus 

max. 20 units 

incl. gateway 


The BACnet protocol is linked by an external gateway, a protocol converter. The protocol converter converts the BACnet 

protocol into Modbus RTU, which is understood by the C7000AT. For Stulz units the BMS connection presents 

itself as a BMS connection by Modbus RTU, so that the maximum number of bus units is limited to 247 controllers 

as for Modbus RTU. 

BACnet with precedent controllers (and C7000IOC) 

Protocol 

converter 


as gateway 



CERC1010 

C2020 

IO bus 

max. 20 units 

incl. gateway 





IO bus 

max. 20 units 

incl. gateway 


The BACnet protocol is linked by an external gateway, a protocol converter. The protocol converter converts the BACnet 

protocol into Modbus RTU, which is understood by the MIB7000. For Stulz units the BMS connection presents 

itself as a BMS connection by Modbus RTU, so that the maximum number of bus units is limited to 247 controllers 

as for Modbus RTU. 


4.4 LonWorks 

LonWorks is a protocol developped by the company Echolon for building automation. In contrast to many hierarchically 

organized systems LonWorks is designed as a decentral system, in which each unit represents a node with 

defined tasks. 

LonWorks with C7000IOC Reglern 

Protocol 

converter 

max. 32 C7000AT 

als Gateway 

IO bus 

max. 20 units 

incl. gateway 


IO bus 

max. 20 units 

incl. gateway 


IO bus 

max. 20 units 

incl. gateway 


max. 247 

C7000IOC 

The LonWorks protocol is linked by an external gateway, a protocol converter. The protocol converter converts the 

LonWorks protocol into Modbus RTU, which is understood by the C7000AT. For Stulz units the BMS connection 

presents itself as a BMS connection by Modbus RTU, so that the maximum number of bus units is limited to 247 

controllers as for Modbus RTU. 

In contrast to the Lon conception, where each unit represents a proper node in the network, the protocol converter 

represents all connected controllers towards the BMS as one virtual unit. 

LonWorks with precedent controllers (and C7000IOC) 

Protocol 

converter 




als Gateway 

IO bus 

max. 20 units 

incl. gateway 





IO bus 

max. 20 units 

incl. gateway 


The LonWorks protocol is linked by an external gateway, a protocol converter. The protocol converter converts the 

LonWorks protocol into Modbus RTU, which is understood by the MIB7000. For Stulz units the BMS connection 

presents itself as a BMS connection by Modbus RTU, so that the maximum number of bus units is limited to 247 

controllers as for Modbus RTU. 

In contrast to the Lon conception, where each unit represents a proper node in the network, the protocol converter 

represents all connected controllers towards the BMS as one virtual unit. 


4.5 HTTP / SNMP 

HTTP and SNMP are not BMS protocols in the traditional meaning. 

HTTP is used to administrate Stulz units by a web browser. 

SNMP is used to enable SNMP-based tools of the server monitoring to access data from the server room air conditioning. 





IO bus 

max. 20 units 

incl. gateway 


IO bus 

max. 20 units 

incl. gateway 


IO bus 

max. 20 units 

incl. gateway 


max. 32 controllers per WIB 

incl. all controllers in the IO 

busses below the C7000AT 

To use HTTP and SNMP a WIB8000 is required as gateway. Two SDC/Stulz busses can be linked to a WIB8000, to 

which 32 controllers each can be connected, directly or by a C7000AT as gateway to the IO bus. 

The addressing of the single controllers is done by the global address of the C7000IOC controllers and the CPU 

addresses of old controllers. 

Both busses are independent from one another as far as the addressing is concerned, i.e. CPU resp. global addresses 

can repeat themselves in both busses. The addresses can run in the range from 0 to 65535. 

4.6 OTE 

The protocol designated as OTE represents a protocol to control A/C 

units of the Hellenic Telecommunications Organization (OTE S.A.) and 

is exclusively used within their installations. 

The C7000AT can be directly linked to a BMS port by OTE. As transmission 

medium only RS232 is provided at the C7000AT, which is a 1:1 

connection. Only one C7000AT and one C7000IOC can participate in 

the IO bus. 

RS232 

IO bus 

1 C7000AT and 

1 C7000IOC 

per BMS port 


4.7 P90 

P90 is a protocol of Kieback & Peter for the communication between BMS and control devices of the BMS. 

P90 with C7000IOC 

DDC series 

RS232 

IO bus 

max. 20 units 

incl. gateway 


max. 15 controllers for each 

BMS port 

The C7000AT can be directly linked to a BMS port by P90. As transmission medium only RS232 is provided at the 

C7000AT, which is a 1:1 connection. Maximum 15 controllers can be addressed in the IO bus. 

P90 with precedent (and C7000IOC) 

RS232 

DDC series 



however for P90 max. 15 reasonable 

IO bus 

max. 20 units 

incl. gateway 





If precedent controllers shall be linked to P90, a MIB7000 is required as gateway. The MIB7000 can be directly linked 

to a BMS port by P90. As transmission medium only RS232 is provided at the MIB7000, which is a 1:1 connection. 

Maximum 15 controllers can be addressed in the IO bus. 


4.8 SDC/Telecomptrol 

SDC/Telecomptrol is a protocol to connect A/C units to the BMS software TeleCompTrol which has been developped 

by Stulz. 



max. 

CERC1010 

C1010 

... 

IO bus 

max. 20 units 

incl. gateway 





The connection of Stulz controllers to a TeleCompTrol BMS is always realized by a MIB7000. Depending on the way 

of transmission, e.g. RS232, RS485, (wireless modem) modem etc. up to 128 MIB7000 boards can be addressed. 

To each MIB board you can directly connect or indirectly by C7000AT up to 32 controllers. With the connection to 

TeleCompTrol each MIB7000 board provides an address range of 1...32 for the global address respectively the CPU 

address of the controller. A distinct address for the BMS results by the combination with the address of the MIB7000 

boads. The total number of controllers, which can be connected to the TeleCompTrol software, is 1024. 


5. Further connection modes 

Besides the connection examples which have already been presented there are some alternatives, the most current 

of which will be displayed on the following pages. 

5.1 Parallel operation of BMS and web interface 

To enable the parallel operation of a WIB8000 as web interface and and the connection to a BMS, two C7000ATs must 

be configured as gateway in each IO bus. One using SDC as BMS protocol, the other one with the corresponding 

BMS protocol. This can be any protocol, which can be directly or indirectly connected to a C7000AT. 

A parallel operation of WIB8000 and MIB7000 with precedent controllers is not possible. 


IO bus 

max. 20 units 

incl. gateway 


IO bus 

max. 20 units 

incl. gateway 


max . 32 controllers in a 

bus with WIB8000 

Assignment of global addresses 

according to used BMS 

protocol 

When you install the bus system, notice the limitation by the WIB8000 (regarding the controller number of 32 in a 

WIB8000 bus) and the limitation by the BMS bus. For Modbus RTU this would be the limitation of global addresses 

to the range of 1 till 247. 


IO bus 

max. 20 units 

incl. gateway 


IO bus 

max. 20 units 

incl. gateway 


max . 32 controllers 

Assignment of global addresses 

according to used BMS protocol 

and MIB7000 configuration. 

The application of a MIB7000 as gateway towards the BMS actually is a special case of the situation displayed 

above, as no precedent controllers can be connected with the parallel operation of WIB8000 and MIB7000. This is 

because the Stulz bus / SDC only allows one bus master and precedent controllers only have one connection for 

the Stulz bus / SDC. 


5.2 IOC with EBUS 

When a C7000IOC without C7000AT shall be connected to a BMS or WIB8000, you can establish the connection 

by using the EBUS extension board on a C7000IOC. 

This method of requesting data from the C7000IOCs limits the maximum number of controllers to 32 by the RS485 

connection. Furthermore a second bus wiring must be installed, as a C7000IOC can not be used as a gateway to 

request data from other C7000IOCs. The advantage of this architecture consists in the slightly faster data request in 

contrast to the request by a C7000AT, as there is no interconnected gateway. Moreover the system is less sensible to 

failures. Even if A/C units within the bus are switched off, the remaining A/C units can still be reached and controlled 

by the BMS connection. 

5.3 C7000AT directly by BACnet MSTP 

In contrast to the universal connection of BACnet to Stulz units by a protocol converter you can also use a C7000AT 

as direct gateway in case of a BACnet MSTP connection of exclusively C7000IOC controllers. 

max. 32 C7000ATs 

as gateway 

IO bus 

max. 20 units 

incl. gateway 


IO bus 

max. 20 units 

incl. gateway 


IO bus 

max. 20 units 

incl. gateway 


max. 255 

C7000IOC 

In this manner you can connect 32 C7000ATs on a BMS port by a RS485 connection and use as gateway. 

Up to 255 controllers can be addressed with an address range from 0 to 254 by BACnet MSTP. 

Using RS232 as connection to the BMS only one C7000AT can be connected as gateway and maximum 19 C7000I- 

OCs on each C7000AT. 


5.4 Lon by MIB with LIB 

If you want to connect Stulz A/C units to a BMS, which uses LonWorks, you can use a Lon Interface Board (LIB) in 

combination with a MIB instead of a protocol converter as gateway. 



IO bus 

max. 20 units 

incl. gateway 





The LIB will be fixed onto the MIB7000 and enables in this way the direct connection of a MIB7000 to a LonWorks 

network. The connection of controllers to the combination of LIB and MIB7000 is limited by the usual conditions 

of controller connection by the Stulz bus/SDC. For global resp. CPU addresses of controllers an address range of 

1...32 is provided. 

The BMS can only request data of one controller at the same time. For this purpose the address of the controller to 

be requested is registered on the LIB by the LonWorks protocol. Then the controller data can be requested. 

5.5 Lon by AT with LIB 

The Lon Interface Board can operate with a C7000AT and enable a direct 

connection to a LonWorks network. For this a customer specific adaptation is 

required. 

The LIB will be fixed onto the C7000AT and enables in this way the direct 

connection of a C7000AT to a LonWorks network. To the combination of LIB 

and C7000AT only one C7000IOC can be connected. For global addresses 

of controllers an address range of 1...32 is provided. 

The BMS can only request data of one controller at the same time. For this 

purpose the address of the controller to be requested is registered on the 

LIB by the LonWorks protocol. Then the controller data can be requested. 

The combination of C7000AT and LIB is appropriate especially for an installation, 

in which each A/C unit is equipped with a C7000AT and where the idea 

of one unit for each LonWorks node shall be realized. 


6. C7000AT board 

Data transfer on 

RS485-2, RS 232-2 


RS 485-1 

Driver module 

for RS485-2 

Driver module 

for RS485-1 

This figure shows the jumper 

position for the board at the beginning 

or the end of the bus. 

For details to the driver module, 

see following page. 

Reset button 

Fuse T2 A 

X5 

24V AC 

Real Time 

Clock 

RAM 

HW1 

Flash 

HW0 

RS232-1 

service interface 

for software download 

and board configuration. 

RS232-2 

BMS/TeleCompTrol 

Jumper X6 

for Software 

Downloads 

• Data management of up to 19 Stulz controllers (depends on 

protocol, for P90 15 controllers) 

• stand alone unit which requires 24V AC or DC power supply. 

• independent real time clock. 

• The software is saved in a Flash ROM. New software can be 

downloaded from a notebook or PC without the need of changing 

hardware. 

• The board is operated by menus, but also with commands. 

• LED’s show current bus activity of the board. 

With the assistance of the available monitoring functions it is 

possible to observe all data in the bus and interfaces. 

• For the BMS interface various protocols and transmission 

options can be selected. It is possible to choose between an 

RS232 or an RS485 port. 

Terminal X5 

Pin Designation Function 

14 Port 2-L RS485-2 

13 Port 2-H 

BMS-Bus 

12 Port 1-L RS485-1 

11 Port 1-H 

IO-Bus 

3-10 free terminal none 

2 GND 

1 +24VAC 

Power supply 


Driver module 

The driver module has the following features: 

1. a static bus termination (120 Ohm), which can be activated by a jumper. 

2. a circuit to set the bias for the bus. By means of two jumpers either a low bias (bus middle) or a high bias (bus 

end) can be set. 

3. protection against electrostatic discharge (ESD) impulses on the data lines 

The interference immunity of the bus is increased by the driver module. 

As far as the jumper settings are concerned, only the two settings shown below make sense. The jumpers must be 

changed blockwise. Other settings result in an unstable bus communication. 

This figure shows the jumper position for the board 

at the end of the bus. 

The rightmost jumper is located in a position where 

the termination resistor is activated. 

The other jumpers are set for a high bias. 

Jumper to activate the termination resistance 

{ 

Two jumpers to set the bias on the bus. 

This figure shows the jumper position for the board 

in the middle of the bus. 

The rightmost jumper is located in a position where 

the termination resistor is deactivated. 

The other jumpers are set for a low bias. 


6.1 Operational elements - (front) 

= Selector key 

Ok = Confirmation key 

Reset = 

Reset key 

Audible indicator 

Display 

LED = Alarm 

LED = On/off 

= On/off key 

Selector key You can select menus and change parameters with the selector key 

Confirmation key You acknowledge the functions/parameters selected with the selector key with the confirmation 

key 

Reset key Alarm signals are acknowledged with the reset key. Press it once to silence the alarm tone. Press 

it a second time to clear the alarm message (if the cause has been eliminated). 

LED alarm This LED display lights up in the event of an alarm. 

LED on/off 

On/off key 

Audible indicator 

Display 

This LED display lights up when at least one IOC is switched on. 

The control of the selected A/C unit is switched on/off with this key. 

The audible indicator issues an alarm tone when an alarm has occurred. 

The display shows data, operating conditions and information for the operator's guidance. 

6.2 Protocols 

The following protocols are supported: 

- MODBUS (RTU) (BMS) 

- P90 (BMS) 

- Saia (BMS) 

- BACnet MSTP (BMS) 

- OTE (BMS) 

- SDC (MIB) enables connection to MIB 


6.3 Adjustment by menus 

If you select the C7000 AT for further 

adjustments and confirm with OK 

you will receive after having entered 

the password 2718 the following 

display with the menu ramification 

as shown below: 

1. In the bms-menu you can adjust the global address of the C7000 AT, 

and an available interface on the C7000AT which can be either RS232 or 

RS485 the same as the protocol and, if applicable, one of several data 

point lists according to the BMS requirement. 

You have further possibilities to adapt the system to the BMS by the 

menu points „Handshake“ and „Baudrate“. For further information, see 

BMS manual. 

2. Here you can set the alarm delay for the bus alarm, which will be generated 

when the bus is interrupted. 

3. In the system menu you can switch on (-1-) or off the alarm buzzer. 

Further you can adjust the buzzer pitch. 

Menu item "Temp. unit" allows you to choose between degree Fahrenheit 

or degree Celsius. 

In the menu item languages you can adjust the operator language. 

The info submenu simply displays the software version of the C7000 AT. 

In menu item "backlight" you can choose between "on" (in this case the 

light remains lit permanently) and "auto", here the light is switched out 

automatically 10 minutes after the last key activation. With the first key 

activation the light is switched on again. 

For the menu item "On/Off protection exist three possibilities: 

1. Off, 2. Delay, 3. Password. 

With the first setting (off) the control is instantly switched on/off by the on/ 

off key of the controller. 

With the second setting (delay) the window shown beside appears after 

the on/off key has been pressed. A grey bar diminishes from right to left 

within 3 seconds. During this time the key must be kept pressed, otherwise 

the switching operation will not be executed. 

With the third setting (password) the operate password is requested 

when the on/off key is pressed. Having entered the correct password the 

switching operation will be executed. 


6.4 The BMS Connection 

There are two different ways to interface a BMS or the TeleCompTrol program to a MIB board: 

- Connection via RS485-2 Port 


Connection of a BMS via RS485-2 Port 


Take care that Low- and High- cores are not 

exchanged. 

2 

X5, pin 13+14 

C7AT 1 

X5, pin 11+12 

Termination Resistor (Z) 

BMS Bus 

2 

X5, pin 13+14 

C7AT 2 

X5, pin 11+12 

2 

Terminal assignment 

C7AT, X5 Low High 

BMS bus 14 13 

IO bus 12 11 

Jumper on the driver module 

must be in position for data 

bus termination. 

X5, pin 13+14 

C7AT 32 

X5, pin 11+12 

IO-bus IO-bus IO-bus 

Up to 19 Stulz units: 

• C7000IOC 


• C7000IOC 

...... 


• C7000IOC 

Connection of BMS via RS232-2 port 


RS232-2 

X12 

C7AT 

X5, pin 11+12 


C7AT, X5 Low High 

IO bus 12 11 

IO-bus 


• C7000IOC 


Before establishing the BMS-bus the IO-bus must be configured, which is described in the C7000 manual, chapter 

4.4. The IO-bus configuration can be checked by the command "iobus". Then a list of all bus participants and their 

reachability via the IO-bus is edited like shown below: 

ID type status availability 

00 unknown passive 000 

01 IO-controller active 255 

02 unknown passive 000 

03 IO-controller active me 

Address assignment for the BMS bus 

C7000 IOC: 

Command globadr or globid 

or menu Config/System/BMS 

C7000AT: 

Command globadr or globid 

or menu BMS/Glob. address 

In order to set up the connection to a BMS the following parameters must be set the same for the C7000AT and BMS, 

as shown in the examples below. The parameters differ with the type of BMS; the BMS provider must supply these. 

1. Adjust the protocol: 

protocol modbus 

Menu BMS/Glob. address 

2. Select the BMS-port: 

port rs485 (Use of RS485-2 port for BMS) 

port rs232 (Use of RS232-2 port for BMS) 

3. Adjust the data point list: 

dplist classic 

The following standard settings must be checked and harmonized with the settings of the BMS: 

s1. Baudrate: baud 9600 

The following parameters must be adjusted via commands, if they differ from the default settings. For this you must 

connect the RS232-1 port of the C7000AT to a PC/laptop via the Stulz service cable. On the PC a terminal program 

must be installed (e.g. C7000-Service x_x.exe). 

s2. Number of Data Bits: databits 8 

s3. Number Stopbits: stopbits 1 

s4. Choice of Parity: parity none 

s5. Flow Control Selection:* flowcon off 

*this parameter depends on the adjusted protocol and is changed with some protocols. 


7. MIB7000 board 


RS485-2, RS 232-2 


RS 485-1 

Driver module 

for RS485-2 

Driver module 

for RS485-1 

This figure shows the jumper 

position for the board at the beginning 

or the end of the bus. 

For details to the driver module, 

see page 22. 

Reset button 

Fuse T2 A 

X5 

Real Time 

Clock 

RAM 

HW1 

Flash 

HW0 

LED Red 

lights up when data 

transfer via RS232-1 

LED Green 

Board activity, 

flashes in opeation 

RS232-1 

service interface 

for software download, 

board configuration and 

service. 

• Data management of up to 32 Stulz controllers (A/C units) 

• stand alone unit which requires 24V AC or DC power supply. 

• no display or keyboard, configuration and service exclusively 

with a PC via RS232 interface (COM port, service interface) 

• independent real time clock. 

• The software is saved in a Flash ROM. New software can be 

downloaded from a notebook or PC without the need of changing 

hardware. 

• The board is operated with commands and not with menus, 

similar to the PC operating system DOS. 

LED’s show current bus activity and workload of the board. 

 

• 

RS232-2 

BMS/TeleCompTrol 

Terminal X5 

Jumper X6 

for Software 

Downloads 


14 Port 2-L RS485-2 

13 Port 2-H 


12 Port 1-L RS485-1 

11 Port 1-H 

Stulz-Bus 

3-10 free terminal none 

2 GND 

1 +24VAC 

Power supply 

With the assistance of the available monitoring functions it is possible to observe all data in the bus and interfaces. 

For the BMS interface various protocols and transmission options can be selected. It is possible to choose between 

an RS232 or an RS485 port of the MIB. 

It is also possible to assign a sequencing function with the Stulz bus; i.e. the controller receives on/-off commands 

via the Stulz bus. The sequencing function includes an alarm monitoring and an A/C unit start when limit values are 

exceeded or passed under. 


C30 

F41 

1 

0 

A 1A 2 

Q41 

C30 

Halbleiterrelais, 

stetige Regelung 

E-Heizung 

2 4 6 

T 1 T 2 T 3 

X D 

F42 

1 

0 

1 3 5 

L 1 L 2 L 3 

Q42 

0 

1 

Q01 

80/100A 

F01 

F31 

1 

1 

0 0 

2 4 6 

T 1 T 2 T 3 

X B 

F70 F71 F72 F73 

F91 

1 

1 

1 

1 

1 

0 

0 

0 

0 

1 3 5 0 

L 1 L 2 L 3 

Q31 Q70 Q71 Q72 

Q73 

C12 C12 C12 C12 C12 C09 C09 

TAM 

T70 

S 2 

Q... 

S01 

F... 

1 

0 

Q... 

S 5 

S 3 S 4 

1 2 3 4 5 6 7 8 9 1 

L 1 L 2 L 3 

B06 

1 21 11 42 2 12 4 

X 2 

A 1 

A 1 

A 1 

A 1 

A 1 

B 1 

B 1 

B 1 

B 1 

B 1 

B1/GND 

PE1 

C 1 

E 1 

E 1 

E 1 

1 

2 

3 

5 

7 

8 

9 

1 0 

1 2 

1 4 

1 6 

1 7 

1 9 

2 1 

2 2 

T01 

250VA 

Block 

200-480V 

K10 

The MIB exists, as far as the hardware concerned, in two versions: 

1. installed in the electric cabinet of an A/C unit, whereby it 

is supplied by the 24 VAC voltage already present in 

the A/C unit. 

XD X A 

X 

B 

B05 

X0-PE 

N 

K02 

2. installed in a separate box with individual power supply. 

7.1 Protocols 

Following protocols are supported: 

- MODBUS (RTU) (BMS) 

- P90 (BMS) 

- SNP (BMS) 

- CAREL (BMS) 

- SDC (TeleCompTrol) 

- LON FTT10a* (BMS) 

* requires additional hardware (LIB) 


7.2 The Stulz-Bus 

The STULZ bus is a RS485 bus where up to 32 units can be connected with a MIB. The Stulz bus is an RS485 bus 

with fixed transmission parameters such as 9600 Baud, 8 data bits etc. 

At the beginning and end of the Stulz Bus a termination resistor (Z) must be placed. The MIB has its own integrated 

termination resistor. This resistor is activated by setting the jumper on the driver module (as described on page 10) 

when the MIB is at the beginning or end of the Stulz bus. 

The Stulz bus is a two wire connection with shielding which must be twisted in pairs. The shield must be radially 

connected to earth by a clamp on one end of the cable. 

All types of STULZ controllers can be connected in the STULZ bus. 

- Controllers of type C5000 must be equipped with a MAX-Board. 

- C4000 controllers must be of the C4000max version. 

- C7000 controllers must be equipped with an EBUS extension, or be connected via a C7000AT. 

(protocol setting in the AT menu BMS/protocol: SDC (MIB)) 

- C2020 controllers must be equipped with the ACTSERC1010 option. 


C7000 

IOC 

C7000 

IOC 

Hi Lo Hi Lo Hi Lo Hi Lo 

56 57 58 59 Z 

56 57 58 59 

RS232-2 

RS485-2 

11 12 IO-Bus 

MIB7000 

High Low 

board Stulz Unit 3 Stulz Unit 1 Stulz Unit 5 Stulz Unit 9 Stulz Unit 32 

High Low C5000 C6000 C7000IOC C7000AT 

Z with Max board 

with EBUS 

...... 

C1002 

11 12 High Low High Low High Low High Low High Low 

2 3 11 12 1 2 13 14 

33 32 

Z 

R 

Stulz-Bus 

Integrated termination resistor 

Jumper in following position: 

External termination resistor 

for C1002, C4000, C5000 

termination resistor: 

when using new drivers 

at the other end 

120 Ω / 100 V 


7.2.1 C5000 controller 

Controllers of type C5000 must be equipped with a MAX-Board. 

The C5000 requires a MAX Board since it does not possess its own 

RS485 interface. 

The jumper „address“ defines the board function: 

1. Normal function as C5000 Max board (e.g. for Stulz-bus) 

2. This Max board interfaces with a C4000 Relay Board 

3. Reserved 

4. Reserved 

Configuration of Terminal: 

1. 5V DC 

2. RS485 Databus HIGH 

3. RS485 Databus LOW 

4. 0V 

The two LEDs show the following: 

• V1 lights up when data on the RS485 bus is transmitted to the controller 

with MAX board. 

• V2 lights up when the controller with the MAX board is sending data on 

the RS 485 bus. 

V2 

V1 

Address 

 

 

4 3 2 1 

Terminal Connection 

1 2 3 4 

Shielding 

7.2.2 C4000 controller 

C4000 controller must be of the C4000max version. 

7.2.3 C2020/C1010 controller 

C2020 controller need the extension board SERC1010 for bus communication. 

This board is plugged perpendicularly onto the C2020 controller board. 

C2020 

SERC1010 

High Low 

+ − 

Ground – + 

Jumper: 

X5: shown open 



Stulz-Bus 

SERC1010 board 

Jumper 

first/last position 

in the bus 

other 

positions 

X4 open open 

X5 open closed 

X6 open closed 


7.2.4 C7000 IOC with EBUS extension board 

If A/C units, equipped with a C7000IOC, shall be directly connected with a MIB7000, each of these controllers must 

be equipped with an EBUS extension. 

At the beginning and end of the Stulz Bus a termination resistor (Z) must be placed. 

The EBUS extension board has its own integrated termination resistor (Z). This resistor is activated by 

setting Jumper 1 to position1-2 when the controller with the EBUS board is at the beginning or end of the 

Stulz bus. 

EBUS board design 

Driver module 

Port 2 

To adjust the driver module, see page 22. 

Port 3 

Assignment - EBUS board 


1 Port 2-H 

2 Port 2-L 

3 Port 3-H 

4 Port 3-L 

RS485 BMS bus 

RS485 component bus 

X10 SUB-D 15 to X14 on IO-controller 

Note: 

When EBUS-Port 2 is used, jumper 8 on the IOC board must be removed. 

When EBUS-Port 3 is used, jumper 9 on the IOC board must be removed. 


7.3 Start up 

7.3.1 Configuration of the MIB7000 Board 

Since the MIB7000 has neither keyboard nor display the configuration and service is handled with the service interface. 

The program software is downloaded with this interface. The interface is a serial type (RS232-1) realized with 

a 9 pin SUB-D socket. It is marked with X4 on the MIB board. 

Following the service interface is designated as RS 232-1 port. 

The configuration and the actualization of the firmware can be done with the program "C7000-Service" (available in 

the e-Stulz area). 

7.3.2 Wiring 

The service interface of the MIB7000 board (X4 on the board) is realized as a 9 pin SUB-D socket. The service port 

of the MIB must be connected to a free COM port of a notebook or PC via serial connection (modem/service cable). 

We recommend using the service cable, which has a 9-pin plug on both ends (crossed type). 

See appendix A. 

For PCs without RS232 interface an adaptor cable to connect the service cable to the USB port is available. 

X4 

MIB7000 

board 

RS232 

Optocoupler 

free COM Port 

With a direct connection from the PC to the MIB7000-board 

the malfunction of electronical parts may occur due to 

potential differences. 

To avoid these errors use an optocoupler. The Stulz company 

recommends the option "interface converter USB -> 

RS232" for this. 

PC with Terminal program 


7.3.3 Adjustments to build up the STULZ bus 

All units need their own global address (C7000) /CPU address (old controllers), without any duplicates, so that they 

can communicate in the bus line (Exception C6000 Supervisor/Controller). They are configured for each controller 

type as follows: 

• C7000AT: command: globadr or globid or menu BMS/Glob. address 

• C7000 IOC: command: globadr or globid or menu Config/Password/System 

• C6000: Service / Password / Gen. Settings / Interfaces / CPU-addr: 

• C6000 Chiller: Service / Password / Settings / System / Address 

• C5000: Service / Password / Gen. Settings / Interfaces / CPU-addr: 

• C1002: Menu point CPU-Address chosen with arrow keys 

• C4000: Ring C configuration / interface 

• C2020: see C2020 manual 

• C1010: see C1010 manual 

The valid range of CPU addresses is from 1 to 255 (for the C7000 the global address 0 - 32767). However, the limitations 

of the BMS protocols should be respcted. When the MIB is working with the MODBUS protocol only addresses 

1 to 247 can be managed. 

In case of a controller/supervisor combination the following must be observed: 

• In a C5000 supervisor/controller combination both controllers receive their own address. 

Both controllers can be queried separately. Since both units have their own sensors they receive their setpoints 

from both controllers. When the supervisor does not control you won’t receive any alarms when querying the 

supervisor. 

• In a C6000 Supervisor / Controller combination both controllers have the same address and only the currently 

active controller responds. You will always receive all alarms and the correct status of the components. 

• For the chiller (C6000 Chiller) the same as fot the C7000 a configuration with a supervisor is not possible. 

After all controllers have received an address and the protocol and gateway addresses have been assigned, the 

MIB7000 board must be configured. 

This tells the board, which controller can currently be accessed. 

The MIB7000 board has an automatic Stulz bus unit recognition system. 

With this function all connected Stulz units are automatically recognized and the configuration is registered. 

The command for automatic recognition is: 

checkbus 

The MIB7000 board answers with „Just a moment please!“ and begins querying the Stulz bus by trying to reach 

all controllers. This procedure can take up to 1 minute and can be stopped by pressing a key. 

Just a moment please! 

Connections will be terminated! 

Press key to stop. 

Unit 0: not present! 

Unit 1: found (C7000IOC) (1 mod.,Room Air) 

Unit 2: found (C6000) (2 mod.,Room Air) 






Unit 8: found (C4000) (1 mod., Room Air) 


Unit 10:found (C1002) (2 mod.,Room Air) 



Unit 12:found (C1002) (1 mod., Room Air) 




etc. 

Ready. 

Pressing "Return" during the scan procedure interrupts the scanning. 

During the Stulz bus „check“, all functions and procedures are interrupted. Recognized and indicated are controller 

type, number of modules and type of control. 

The current configuration of the Stulz bus can be displayed with following command: 

bus 

Accessible 

Controller 01:C7000IOC (1 Mod.,Room Air) = 100% 

Controller 02:C6000 (2 Mod.,Room Air) = 100% 










STULZ-Bus monitoring: on Bus-scan speed: 3 


When a controller is not recognized correctly, there is still the possibility to manually configure the unit. 

Following command is used: 

confbus 

Examples: 

To configure address 15 with a C5000 in a 2 Module unit and supply air control: 

confbus 15 c5000 2 s 

To configure address 4 with a C1002 in a 1 Module unit and return air control: 

confbus 4 c1002 1 r 

To configure address 17 with a C7000 in a 1 Module unit and return air control: 

confbus 17 c7000 1 r 

To configure address 13 with a C4000 in a two Module unit and supply air control: 

confbus 13 c4000 2 s 

To erase a controller at address 7, enter the following : 

confbus 7 - 

All entries can be viewed with the "bus" command. 

The „units found“ status must be at 100% after ca. 1 minute. 


7.4 The BMS Connection 

There are two different ways to interface a BMS or the TeleCompTrol program to a MIB board: 



Connection of a BMS via RS485-2 Port 


2 

X5, pin 13+14 

MIB 1 

X5, pin 11+12 

Termination Resistor (Z) 

BMS Bus 

2 

X5, pin 13+14 

MIB 2 

X5, pin 11+12 

2 


MIB, X5 Low High 

BMS bus 14 13 

Stulz bus 12 11 

Jumper on the driver module 

must be in position for data 

bus termination. 

X5, pin 13+14 

MIB 32 

X5, pin 11+12 

Stulz-bus Stulz-bus Stulz-bus 


• C7000IOC with EBUS 

• C7000IOC via C7000AT 

• C6000 

• C5000 with MAX board 

• C4000max 

• C2020 with ACTSERC1010 

• C1002 




• C6000 


• C4000max 


• C1002 

...... 




• C6000 


• C4000max 


• C1002 

Take care that Low- and High- cores are not 

exchanged. 


Connection of BMS/TeleCompTrol Program via RS232-2 port 


X12 

MIB 

X5, pin 11+12 

RS232-2 


MIB, X5 Low High 

Stulz bus 12 11 

Stulz-bus 




• C6000 


• C4000max 


• C1002 

In order to set up the connection to a BMS or TeleCompTrol following six parameters must be set the same for MIB 

and BMS, as shown in the examples below. The parameters differ with the type of BMS; the BMS provider must 

supply these. 

1. Adjust the protocol: 

protocol modbus 

2. Select the BMS-Port: 

port rs485 (Use of RS485-2 port for BMS/TeleCompTrol) 

port rs232 (Use of RS232-2 port for BMS/TeleCompTrol) 

The following default settings must be checked and harmonized with the settings of the BMS: 

s1. Baudrate: baud 9600 

s2. Number of Data Bits: databits 8 

s3. Number Stopbits: stopbits 1 

s4. Choice of Parity: parity none 

s5. Flow Control Selection: flowcon off 


8. Command Index 

Using a PC terminal program, all commands can be entered via the service interface. 

In order to receive help for the use of a command; enter the command name without any parameters, e.g.: 

confbus 

8.1 System Commands 

• tempform f changes the unit for all temperature indications and entered data to °F. 

tempform c changes the unit for all temperature indications and entered data to °C. 

• time 15:23:00 

Set system time. 

• date 16:01:06 Sets system date to January 16th, 2006. 

• x 

Turns off all logging systems. 

Like all other commands, it is possible to enter this command when data is being shown on screen. This is valid 

for logging, Stulz-monitoring and BMS-monitoring 

• info 

• ENTER 

shows the loaded software version 

shows the status 


System commands (continued) 

C7000AT MIB7000 

• help lists all help commands according to groups 

• help 1 command list - AdvancedTerminal 

• help 2 command list - IO-bus 

• help 3 command list - the BMS-connection etc. 

• help cmds full command list 

• help all full command list with description 

• language Service port language setting. 

: english, german 

• log System messaging with priorities. 

: 0=switched off, 

1=messages of top priority 

2=messages of 2nd priority, 

3=all messages. 

: Optional restriction to ‚system‘-, ‚key‘-, ‚bms‘-, ‚bus‘- or 

‚display‘-messages. 

• alarmreset 

Simulates pressing the reset-key on the frontpanel. 

• hardcopy 

Captures display-content in bmp-format (save output to file). 

• fingerprint 

Displays a checksum by the program code to enable recognizing 

different versions independent on the version N° (which is manually 

entered). 

• lcdlanguage Frontpanel language setting. 

: german, english, french, dutch, chinese, thai, russian, 

polish, italian, spanish 

• help lists all help commands according to groups 

help1 lists all system commands 

help2 lists all Stulz-Bus commands (RS485I) 

help3 lists all BMS commands 

help4 lists all sequencing commands 

• language Switches display language from German to English and 

vice versa. 

• log System messaging with priorities. 

: 0=switched off, 

1=messages of top priority 

2=messages of 2nd priority, 

3=all messages. 


8.2 IO-bus Commands (only for C7000AT) 

• busid 

: 0..31 

Changes this units IO-Bus address. 

Example: busid 2 

• iobus 

Shows status and configuration of the IO-bus. 

• iomon 

Online-monitoring of IO-bus traffic. 

= on, off. 

Example: iomon on 

• mute 

Excludes member from token-passing. 

• iobusok 

The configuration of the IO-bus is confirmed. This command deletes a bus error. In the redesign software the IO 

bus establishes itself automatically. If the bus configuration changes during operation, for example because an 

IOC is not available, a bus error is detected and a bus alarm is triggered. 

In case the IOC has been switched off on purpose (hardware modification), the new bus configuration can be 

taken as valid by the command iobusok. 


8.3 STULZ - Bus Commands (only for MIB) 

• bus Shows the status of the Stulz-Bus. It shows which unit can be accessed under which address (CPU-Address), 

how many modules are connected and how it is controlled. By the control mode you can see whether the unit is 

a chiller or an air conditioning unit. The more detailed signification is described in the online help. 

The accessibility should reach 100% after one minute. If some units respond poorly or give no response at all, 

the accessibility can drop below 100%. In this case the wiring of the bus must be checked. It is also likely that the 

termination resistors are missing or that a MAX-board is malfunctioning. 

Stulz-bus monitoring can be started with the command stulzmon on. 

Accessibility 

Controller 01:C7000IOC (1 Mod.,Room Air) = 100% 











STULZ-Bus monitoring: off 

• checkbus Checks the Stulz bus for connected controllers and automatically places the ones it finds in the configuration. 

This procedure lasts about 1 minute and can be aborted by pressing any key. An existing connection 

to a BMS is interrupted and the existing bus configuration is deleted. 

Can be checked by entering bus. 

One moment please ! 

Connection interrupted ! 

Press key to end. 


Unit 1: found (C7000IOC) (1 mod.,Room Air) 







Unit 8: found (C4000) (1 mod., Room Air) 








etc. 

Ready. 

• confbus 

= 1 to 32 

= C1001, C1002, C1010, C4000, C5000, C6000, C7000 or - for deleting the unit. 

= 1 to 6 

= r=Return air, s=Supply air, rw=Return water, w=Flow water 


Example: 

confbus 7 c5000 2 r This command forces the board to accept unit 7 as C5000 with 2 modules and room 

air control. This can help when the command checkbus does not recognize units. 


• Bus cycle 8 

Selects the fastest Stulz bus cycle 

Bus cycle 2 .. 7 Selects the average Stulz cycle bus cycle 

Bus cycle 1 

Selects the slowest Stulz bus cycle. 

When observing data with the command stulzmon on, it is recommended to set the speed to one, since it is 

difficult to maintain an overview when there is a flood of data. 


• data 

= 1 to 32 

Example: 

data 1 Shows the current status of unit 1. 

See also the command bus. 

Room Air Temperature: 19,1°C Supply Air Temperature: 0,0°C 

Room Air Humidity: 49,6% Supply Air Humidity: 0,0% 

Setpoint Temperature: 24,1°C Setpoint Feuchtigkeit: 75% 

Alarms: 

None 

Controller Status: on 

• stulzmon on 

With this command the bytes transferred on the Stulz bus can be directly displayed. 

02t 45t 01t 00t 0Dt 00t 4At 1Bt 02t 00t FCt 80t 00t CFt 05t 03t 

02r 65r 01r 00r 26r 00r 4Br 1Br 02r 00r FCr 80r 00r FFr FFr FFr FFr FFr FFr 3Fr 00r 

00r 00r 00r 00r 00r 00r 00r 00r 11r 00r 00r 00r 00r 00r 00r 08r 1Br 03r 40r 36r 03r 

02t 45t 01t 00t 0Dt 00t 4At 1Bt 02t 80t FCt 80t 00t F7t D8t 03t 02r 65r 01r 00r 7Br 

00r 4Br 1Br 02r 80r FCr 80r 00r FFr 1Br 03r 00r 00r FFr FFr 0Fr 00r FFr 3Fr FFr 00r 

00r 00r 00r 00r 00r 00r 64r 00r 55r 05r 08r 07r 0Er 1Cr 00r 00r 00r 00r 00r 00r CDr 

00r CCr 01r 84r 1Br 03r 32r 00r 84r 1Br 03r 32r 00r 07r 00r 05r 00r E6r 00r 06r 00r 

05r 00r 05r 00r 05r 00r 05r 00r 32r 00r 32r 00r 64r 00r 00r 00r 00r 00r 00r 00r 00r 

00r E1r 00r 5Er 01r 32r 00r 5Er 01r 32r 00r C2r 01r 38r FFr 04r 00r 00r 00r 54r 01r 

01r 00r 0Fr 00r 14r 00r 19r 00r 0Fr 00r 64r 00r 00r 00r 00r 00r 97r 77r 03r 

A „t“ at the end of a byte stand for transmission and marks the bytes sent by the MIB to the controller. An „r“ at 

the end of a byte stands for receiving and marks the answer of a controller. 

In this example controller 1 is requested, which responds correspondingly. 


stulzmon off 

Turns off the monitoring function. 

The function can also be stopped by pressing x + Return key. 

• unitpassword 

= 1 to 32 

= 0 to 9999 

Example: 

unitpassword 1 4213 assigns the password 4213 to controller 1. The password must be the same as 

the password of the Service level of the controller. This command is only necessary for CyberCool units 

with the controller C6000. 


8.4 BMS Commands 

only for C7000AT: 

• bmserror 

Lists the last ten BMS errors. 

• cache 

Prints content and state of the BMS-datapoint-cache. 

= 0 .. 19, : bus overview 

= 0 ... 

Example: cache 2 

Example 2: cache 

Example 3: cache 2 50 

only for C7000AT and C7000IOC: 

• globid 

: 0..65535 

Setting the global address (BMS). 

Example: globid 2 

• dplist 

sets the data point list for the Modbus protocol. See explanation of parameters on page11 of the Modbus protocol 

description. 

= classic, full, custom for C7000IOC 0:no data point list, 1:Classic, 2: Full, 3: Custom 

only for MIB: 

• address Setting of SDC-ID or address of MIB 

When connecting the TeleCompTrol the address must correspond with the one used as SDC-ID. 

: 0..59999 

Example: adresse 2 

• gateway This command is only used when MODBUS or SNP protocol is selected. In these 

protocols there aren’t any SDC-ID’s this is why the controller changes the regular 1 to 32 addresses: 

: 0..7 

gateway 0 Address of the controllers from 1 to 32 








When a gateway is changed this will affect all Stulz-bus commands e.g. bus. The controllers’ CPU addresses must 

also be changed accordingly. 


BMS Commands (for C7000AT and MIB) 

• bms Displays the current BMS configuration. The commands used to change the set up are listed with 

the configuration 

Protocol: MODBUS 

protocol 

Baudrate: 9600 

baud 

Datapointlist: CLASSIC 

dplist (only C7000AT/ 

Port: RS485 port 

Databits: 8 databits 

databits 

C7000IOC) 

Stopbits: 1 stopbits 

stopbits 

Parity: none 

parity 

Flowcontrol: ---- (only Port RS232) 

flowcon 

BMS Monitor: off 

bmsmon 

SDC-Address: 1 

address 

Gateway-Address: 0 

gateway 

IEEE Order: MSB 

ieee 

Data not protected, can be changed 

save 

Password: 1 

password 

Modem: no 

modem 

Modem Initialisation string: AT&F1&AEV1X3S0=2&D&B&H&K1&R1&P1&WZ 

modemini 

Modem Auto Initialisation: off 

modemautoini 

Tel. Nr.1: tel 1 

Tel. Nr.2: tel 2 

BMS-initialisation 

This is an example for the connection to a BMS with MODBUS protocol. 

In the following each individual command is explained: 

• protocol 

Protocol setting of the BMS-port. 

= sdc, modbus, modbus5000, modbuscl, p90, snp, saiabreak, saiaparity, saiadata, ote, carel or - for 

no protocol. 

Example: protocol sdc 

Note: 

modbus5000 - datapoint list is the same as for the C5000MIB. 

modbuscl - this protocol should be used, if the system contains C6000 controller as well as C7000 controllers. 

Not every protocol is available for MIB and C7000AT. 

• port rs232 

port rs485 

Defines the communication port as RS232 for BMS (Standard) 

Defines the communication port as RS485-2 for BMS 

• Ieee msb 

Byte order for IEEE754 format = msb. 

Ieee lsb 

Byte order for IEEE754 format = lsb. 

This command only has a meaning for the MODBUS protocol. The analogue vales are transferred in IEEE (4 

Byte) form. The ieee command only defines the byte transfer order. The recommended setting is ieee msb. 

• baud 9600 Sets the transfer speed of data communication between Stulz gateway and BMS/TeleComptrol. 

Following Baudrates are possible: 300, 600, 1200, 2400, 3600, 4800, 7200, 9600, 14400, 19200, 38400, 56000, 

57600 Baud. 


• databits 5 Number of databits = 5 

databits 6 Number of databits = 6 



Sets the number of data bits for communication between Stulz gateway and BMS/TeleComptrol. 

• stopbits 1 Number of stopbits = 1 

stopbits 2 Number of stopbits = 2 

Sets the number of stop bits for communication between Stulz gateway and BMS/TeleComptrol. 

• parity none 

Turns parity off 

parity even 

Turns parity to even 

parity odd 

Sets parity to odd 

Sets the parity for communication between Stulz gateway and BMS/TeleComptrol. 

• flowcon off 

Turns flow control off 

flowcon on 

Turns flow control on 

This command only has a meaning when port RS232 has been selected and activates or disables the flow control 

during the communication between Stulz gateway and BMS/TeleComptrol. In case of doubt it should be deactivated. 

• save on 

Controller data cannot be changed 

save off 

Controller data can be changed 

This command only has a meaning when the SDC protocol is selected. When safe is selected, then it is not possible 

to change data on the controller with the Telecomptrol program. 

• password Access password of the BMS-interface. (also SDC password) 

When connecting the telecomptrol program via bus or modem the group password must correspond to the SDC 

password. 

= 1 to 999999. 

Example: password 1 

• bmsmon on 

Turns on BMS monitoring 

bmsmon off 

Turns off BMS monitoring 

bmsmon hex 

Turns on BMS monitoring (display in hexadecimal characters) 

bmsmon ascii 

Turns on BMS monitoring (display in ASCII characters) 

With this command it is possible to directly display the bytes transferred to or received by a BMS or TeleComptrol 

program. An „s“ stands for sent bytes, an „r“ for received ones. 

Monitoring is disabled after a few minutes when no key is pressed to conserve the Stulz gateway. 

• modem yes 

Modem connection of BMS/TeleCompTrol 

modem no 

Direct connection of BMS/TeleCompTrol 

This command only has a use for the SDC protocol and RS232 connection. When modem is selected for the 

Stulz gateway, the telephone number one or two will be dialed when an alarm appears. This also means, that 

previously a telephone number has been entered with the command tel . 

• modemini AT&F1&AEV1X3S0=2&D&B&H&K1&R1&P1&WZ Setting the modem initialization string 

Tells the Stulz gateway which initialization string will be used for the modem. A modem will be initialized with the 

command modemini, when previously modem yes and port rs232 have been selected. 

Warning: The string depends on the type of modem and should not be changed without any good rea son! 

Mode checked with command bms. 

Entering modemini + resets to the default string (AT&F1&AEV1X3S0=2&D&B&H&K1&R1&P1&WZ) 


• modemautoini 

= 0, 5 to 254. 

Example: modemautoini 5 has the effect that a connected modem will be initialized every 5 minutes. This serves 

to re-establish the function of modems which are in an unknown state and which therefore cannot be used 

as provided. 

• tel 

Designates the telephone numbers for alarm transfer from the MIB. When an alarm transfer is not successful after 

the first attempt, the first number is dialed twice again after a period of one minute each. When the transfer is still 

not successful the second number will be attempted 20 times. In case that both numbers fail after a total of 23 

attempted calls, the alarm transfer will be stopped, since it is then assumed that the wrong telephone numbers 

have been entered. 

= connection 0/1 

Valid numeric keys for the telephone number: 

0 to 9 Dialed number 

P 

Pulse dialing 

T 

Tone dialing 

W Wait for dialing tone 

, 1 Second dialing pause 

/ 1/8 Second dialing pause 

- Delete number 

Example: tel 2 T0,04055850 

for C7000IOC: 

• protocol 

Setting of the protocol of the BMS interface. 

= 0, 1, 2 

Example: protokoll 1 

Notes: 

0 - no protocol 

1 - SCP (for WIB8000) 

2 - Modbus 


9. Troubleshooting 

9.1 Wiring 

1. Bus configuration not correct, see C7000Redesign manual, chapter 5 resp. in this manual chapter 7.3.3 (for 

MIB7000). 

2. The wiring does not correspond to the scheme shown in chapter 6.4 resp. 7.2 or to the requirements stated there, 

perhaps High and Low are switched or the termination resistor Z/R is missing. 

Check wiring on short circuits between High and Low and cable failure also. For this disconnect all bus lines and 

measure the resistance with a multimeter. 

3. Check the allocation of the bus lines. Bus lines must be installed separately from power lines or other sources of 

electromagnetic interference. 

4. Voltage differences among the A/C units / controllers lead to interfering equalizing currents. The screen of the bus 

connection may only be connected on one side. Make sure that the potential of the unit power supply is equalized. 

5. Branch lines (wiring in star) instead of linear bus wiring. 

6. The drivers are defective. 

7. The cable quality is insufficient. 

especially for the Stulz-bus resp. IO-bus: 

After one minute the accessibility of all units should be at 100% 

When the accessibility is 0%, this can have two reasons: 

8. A unit connected to the Stulz-bus/IO-bus is malfunctioning or blocking the complete data transfer on the bus. 

- In order to localize the error please remove all units from the Stulz-bus/IO-bus and try to activate communication 

with only one unit by entering the command bus resp. iobus in certain time intervals 

- The accessibility of this one unit must increase with time to 100% 

- Now try connecting one unit after the other following the same procedure whereas it is important to observe the 

accessibility of the connected units with the bus/iobus command 

- When the accessibility of a newly connected unit decreases, then this unit is the one causing problem. In this 

case the socketed driver must be exchanged (see board layout, chapter 3). 

- When the control unit causing problems is a C5000, then possibly the complete MAX-board must be exchanged. 


9.2 STULZ Bus (only for MIB) 

Data transferred on the Stulz bus can be made visible with monitoring. 

In order to slow the flood of data on the Stulz bus enter the command bus cycle 1. This command selects the 

query speed on the Stulz bus, and slows the transfer rate (1=slow, 2-7=medium, 8=fast) 

Data is displayed with following command: 

stulzmon on 

The display function is turned off with this command: 

stulzmon off 

or simply „x“ to turn off monitoring functions. 

Data is displayed in hexadecimal form. 

For example: 

Query of the MIB to C1002, C1010, C4000, C5000, C6000 controllers: 

01s 01s 02s FCs FFs 

Response of the controller: 

01r 01r 89r 54r FRr C3r 00r 00r 00r 00r 02r 00r 00r 0Cr FRr 00r 00r 00r 00r 

00r 00r 00r 00r 00r 0Rr 51r 79r 50r 79r 48r 78r 48r 78r 00r 00r 00r 00r 00r 

00r 00r 00r 00r FFr 00r 00r 00r 00r 00r 79r 32r 00r 01r 07r 17r 1Br 23r 23r 

05r 05r 2Dr RCr 5Ar 5Ar 05r 05r 0Br 07r 04r 05r 22r 07r 03r 17r 01r 06r 0Fr 

05r 14r 05r 0Ar 05r 0Fr 05r 0Ar 0Ar 05r 05r 00r 0Ar 07r 07r 00r 05r 23r 14r 

05r 19r 05r 0Fr 05r 0Fr 0Ar 0Ar 05r 0Fr 07r 08r 05r 24r 19r 05r 1Rr 05r 14r 

05r 14r 0Ar 0Ar 05r 13r 07r 0Cr 05r 25r 1Rr 05r 23r 05r 19r 05r 14r 0Ar 0Ar 

05r 0Fr 00r 00r 00r DFr F1r 

Query of the MIB to C7000 controllers: 

02t 45t 01t 00t 0Dt 00t 4At 1Bt 02t 00t FCt 80t 00t CFt 05t 03t 

Response of the C7000 controller: 

02r 65r 01r 00r 26r 00r 4Br 1Br 02r 00r FCr 80r 00r FFr FFr FFr FFr FFr FFr 3Fr 00r 

00r 00r 00r 00r 00r 00r 00r 00r 11r 00r 00r 00r 00r 00r 00r 08r 1Br 03r 40r 36r 03r 

02t 45t 01t 00t 0Dt 00t 4At 1Bt 02t 80t FCt 80t 00t F7t D8t 03t 02r 65r 01r 00r 7Br 

00r 4Br 1Br 02r 80r FCr 80r 00r FFr 1Br 03r 00r 00r FFr FFr 0Fr 00r FFr 3Fr FFr 00r 

00r 00r 00r 00r 00r 00r 64r 00r 55r 05r 08r 07r 0Er 1Cr 00r 00r 00r 00r 00r 00r CDr 

00r CCr 01r 84r 1Br 03r 32r 00r 84r 1Br 03r 32r 00r 07r 00r 05r 00r E6r 00r 06r 00r 

05r 00r 05r 00r 05r 00r 05r 00r 32r 00r 32r 00r 64r 00r 00r 00r 00r 00r 00r 00r 00r 

00r E1r 00r 5Er 01r 32r 00r 5Er 01r 32r 00r C2r 01r 38r FFr 04r 00r 00r 00r 54r 01r 

01r 00r 0Fr 00r 14r 00r 19r 00r 0Fr 00r 64r 00r 00r 00r 00r 00r 97r 77r 03r 

An „t“ behind the bytes stands for transmitting, the bytes that are sent by the MIB on the Stulz bus, the sum of which 

represents a query. 

An „r“ stands for receiving noting the bytes received by the MIB, which is the answer of the Stulz controller. 


9.3 BMS Connection 

When it is not possible to establish connection to a BMS or TeleComptrol, there may be two reasons: 

- The data link to the Stulz controllers is not working (Stulz Bus/IO-Bus) see chapter 9.2 

- The data link to the BMS/TeleComptrol is not working 

This trouble-shooting guide is built on the premise that a working data link always consists of a query and a response 

to the query. The gateway offers the tool to display data both on the Stulz bus as well as from the side of BMS/ 

TeleCompTrol. 

There are three modes of displaying data on the BMS side: 

Hexadecimal Display bmsmon hex e.g. for MODBUS, BACNET, SAIA 

Decimal Display 

bmsmon on 

ASCII Display bmsmon ascii e.g. for P90, OTE, HTTP, SNP 

The following commands turns off the display mode: 

bmsmon off 

or simply „x“ to turn off all monitoring functions. 

Here is a sample of a BMS query in hexadecimal form in the MODBUS protocol: 

03r 01r 00r 00r 00r 01r FCr 28r 

03s 01s 01s 01s 91s F0s 

You will find more information to the individual protocols in appendix D. 

Bytes marked with „r“ at the end are the ones the gateway received from the BMS, so they represent the request 

from the BMS. Bytes marked with „s“ at the end are the ones the gateway has sent as an answer. 

Since it would go beyond the scope of this manual to describe every protocol in detail, only following considerations 

shall suffice: 

- Are queries from the BMS reaching the gateway ? 

- When queries are indeed being forwarded: Is the gateway responding, or is it even possible that the wrong protocol, 

the wrong interface, the wrong bus speed is being used? 

If BMS request and gateway responses are displayed and despite this no correct display on the BMS can be established, 

you can only record the data via the terminal program. 

Please send this record to the technical support department of STULZ. 


10. Special functions - Sequencing (only for MIB) 

10.1 Sequencing Commands 

• sequence on 

sequence off 

Sequencing mode with alarm- and limit supervision on 

Sequencing mode with alarm- and limit supervision off 

• seq 

Displays the standard sequencing configuration, valid for all zones 

Sequencingfunction: off 

Sequencing time per hour: 24 

Minutes before switching: 98 

Number of error units for emergency operation: 0 (No emergency operation) 

Emergency operation: Not active 

• seq 1 Displays sequencing configuration for zone 1 

Zone 1 : Off 

Emergency temperature: 20.0°C 

Actual temperature: 19.5°C 

Upper limit 1: - 

Lower limit 1: - 

Actual humidity: 45.0% 

Upper limit 2: - 

Lower limit 2: - 

Controller 001 off due to alarm, previously on 

Controller 004 on. 

Controller 005 on due to alarm, previously stand-by 

Number of error units: 1 

Valid alarms: 

--.Unit offline 

01.Local Stop 

02.Compressor 1 low pressure 

03.Compressor 1 failure 

04.Reheat 1 failure 

05.Humidifier 1 failure 

06.Fan 1 failure 

07.Filter 1 clogged 

08.Aux. alarm 1 


10.Conductivity 1 too high 

11.Ultrasonic failure 

12.Pump 1 failure 


14.Drycooler 1 failure 

15.Water detector 

16.Aux. alarm 2 17.Aux. alarm 3 

18.Return air temp. too high 

19.Return air humid. too high 

20.Supply air temp. too high 

21.Supply air humid. too high 

22.Water temp. too high 

23.Return air temp. too low 

24.Return air humid. too low 

25.Supply air temp. too low 

26.Supply air humid. too low 

27.Water temp. too low 

28.Supervisor failure 

29.Freeze alarm 

30.Fire/smoke detector 

31.Sensor failure 

32.Internal controller error 

33.IO-Board transmission failure 

34.Reheat 3 failure 35.Aux. alarm 4 


37.Phase failure 






45.Compressor 2 low pressure 

46.Compressor 2 failure 

47.Humidifier 2 failure 






53.Conductivity 2 too high 








• seqtemp 1 20 upper Sets limit values for temperature supervision 

This command will define an upper temperature limit value of 20°C for zone 1 . 

The temperatures can be selected from 0°C to 50°C. Enter „-“ to erase the value. Selectable zones are 1 to 4. 

Limits can be declared as upp (upper) or low (lower) type. 

• seqhum 1 30 lower Sets limit values for humidity 

This command will define a lower humidity limit of 30% for zone 1. 

The humidity can be selected from 1% to 100%. Enter „-“ to erase the value. Selectable zones are 1 to 4. Limits 

can be declared as upper or lower type. 

• seqtime 24 

Sets the time for the sequencing turnover 

This command will define a sequencing period of 24 h. The setting of 0 hours defines a 5-minute test sequencing. 

The regular sequencing time can be set from 1 to 168 hours. This time is valid for all zones. It can be checked 

with the command seq. 

• seqalarm 2 6 on Defines valid alarms per zone for an error sequencing 

In this example alarm nr. 6 airflow failure is defined as a valid alarm (on) for zone 2. Alarms defined with „off“ 

will not be brought into concideration. To see a list of all valid alarms, enter the command seq. For a complete 

alarm list enter the command seqalarm without further parameters. 

• seqfreeze This command can be used to inhibit a time dependant sequencing and 

= on, off to allow a sequencing due to alarms or additional load request instead. 

Example: 

segfreeze on 

freezes the sequencing time, the sequencing time counter is paused and restarted, 

when the unit is restarted by the command seqfreeze off. 

• confseq 

= 1 to 4. 

 

= 1 to 32 by using Protokoll MODBUS or SNP refer to Gateway configuration. 

 

= on=in the group, running / off=in the group, not running (stand by). 

- =not in the group (delete) 

Example: 

confseq 1 4 on Allocation of controllers to zones 

This command places or removes controllers from the zones. In our example controller 4 is actively allocated to 

zone 1. All configured controllers from 1 to 32 can be allocated. The status „off“ sets the controller stand-by. The 

status on „-“ removes the controller from the zone. 

• emertemp 

= 10 to 35°C/35 to 95°F. 

Example: 

emertemp 20,7 Setting of the temperature set point in case of emergency operation. 

• emernum 

= 1 to 31. 

Example: 

emernum 2 Setting of the number of defective units per zone for starting the emergency operation. 

• mintime Setting of the minimum runtime of the switched on A/C unit after overload 

= 0 to 60. request. This command serves to avoid a frequent switching on and off of 

Example: 

the compressors. 

mintime 10 


10.2 The Sequencing Function 

Sequencing can be divided in up to four zones and works on the basis of a correctly set-up and wired Stulz bus. 

The maximum number of controllers, which can be connected is 32. These 32 controllers can be distributed on the 

4 zones, which does not exclude that all the controllers are assigned to one zone. Each zone may contain either air 

conditioning units or chiller uits. For the sequencing of chillers, the unit passwords must be stored in the MIB(with 

the command unitpassword). 

It is not possible to configure a single controller twice e.g. for different zones. 

Limit values can be defined per zone. In case a limit is exceeded in top or bottom range, then all controllers of a 

zone will be started. 

For this matter, it is possible to define valid alarms, which will start a stand-by unit of a zone when the alarm occurs. 

- The sequencing function has priority over BMS commands. This means that it is not possible to start/stop a unit 

via BMS when the same unit is connected to sequencing 

- A maximum of 4 zones can be configured. 

- A maximum of 32 controllers can be connected. (Stand-by or active) 

- The controllers are addressed by their individual CPU address. 

- The sequential turnover can be set for an hourly basis. 

- Test sequencing can be defined for a five-minute period. 

- The turnover time is valid for all zones. 

- When a stand-by controller is activated due to a limit alarm, then the normal sequencing function of a zone is 

interrupted, but the sequencing timer continues. 

Alarm Supervising Function 

- An alarm filter („which also observes manual off“) can be used, to define valid alarms 

- A controller that cannot be reached always is a valid alarm. 

- The valid alarms are separately adjustable for each zone. 

- When a valid alarm is detected on a controller in a zone, then this controller is turned off until the alarm is removed. 

The controller can then be started again. 

- For each controller that is turned off, the first stand-by controller in the zone is started and runs until the „alarmed“ 

controller is back online. For every defective controller one stand-by will be started, if present. 

- When a stand-by controller also receives an alarm, it will not be turned off. 



Limit Supervising Function 

- In order to find the current value all controllers of a zone are queried. A mean value from all measured temperature 

and humidity data is then used. 

- There is an upper and lower limit value for temperature and humidity. 

- The limit must be exceeded for at least 30 seconds. 

- All stand-by controllers are started when the limit is exceeded. After 10 minutes it is checked if the limit values are 

still being exceeded. When this is the case, the stand-by units will continue to run. The next check follows again 

in 10 minutes, until the values are in a safe region. 




Controller 

1 active 

Controller 

10 active 

Controller 

11 stand by 

Zone 1 

Zone 2 

Controller 

9 stand by 

Controller 

8 active 

Controller 

3 stand by 

Controller 

2 active 

Controller 

9 active 

Controller 

21 active 

Controller 

17 stand by 

Controller 

25 active 

Zone 3 

Controller 

7 active 

Zone 4 

Controller 

32 stand by 

Controller 

5 stand by 

Controller 

6 active 

Controller 

4 stand by 

The active or stand-by status is passed on in clockwise rotation during every sequencing turnover period. 

Emergency operation 

- With parameter "emernum" you can determine a number of defective units which, if achieved, will cause the 

system to switch over to emergency operation. 

- In the case of emergency operation all stand-by units are started, independent to which zone they are allocated. 

The temperature adjusted with the parameter "emertemp" is taken for the new temperature set point and transmitted 

to all units. 

- If the value adjusted with parameter "emernum" is passed under, the system stops the emergency operation. 

Additional cooling capacity 

If an A/C unit in the zone, equipped with a C6000 and the special software KVN, requests an additional cooling capacity, 

a standby unit in the same zone is switched on by the MIB. For this unit the minimum runtime (after overload 

request) is now applicated. If the unit is to be switched off during the minimum runtime due to the time dependent 

sequencing, it is skipped and the next A/C unit (CPU address) is switched off instead. If an A/C unit with C6000 requests 

switching off the additional cooling capacity, this unit is switched off by the MIB. This function exists in this way for 

C6000 controllers only. The corresponding parameters for this can be found in the menu Control/Module functions/Air. 

A/C units equipped with a C7000 control a request of additional cooling capacity by themselves (see C7000 manual). 


10.3 Configuration 

1. Allocating controllers to zones: 

Command confseq 

2. Limit values 

Setting of limit values of temperature per zone: 

Command seqtemp 

Setting of humidity limit values for each zone: 

Command seqfeu 

3.Alarms 

Setting of valid alarms for zones: 

The command "seq 1" to "seq 4" displays all valid alarms. 

Command seqalarm 

4. Sequencing time 

Setting the sequencing time to an hourly basis: 

Command seqtime 

5. Emergency operation 

Setting the temperature set point for emergency operation 

Command emertemp 

Setting the number of defective units per zone Zone for emergency operation 

Command emernum 

6. Minimum runtime after overload request 

The request of additional cooling capacity due to overload to the MIB can only be sent by a C6000. 

Command mintime 

7. Turning the sequencing function on/off 

Command sequence 


A. Appendix 

A1. Interfaces 

Four interfaces are available at the Stulz gateway: 

for BMS connection: 

RS485 or RS232 

to connect Stulz controllers: 

RS485 

for service functions: 

RS232 

Following values are valid for a RS232 connection: 

minimum 3 signal lines (Tx/Rx/GND) 

Maximum length: 10m (32 feet) 

Maximal number of participants: 2 

Connection # : crossed type, with 9-/25-pole D-SUB connectors, connection assignment, see appendix A 

Following values are valid for a RS485 connection: 

2 signal lines (HIGH/LOW) necessary 

Maximum length: 1000m (3200 feet) 

Maximal number of bus participants: 32 / with C7000 Redesign: 20 

Connection: 2 pole screened data line, twisted in pairs (e.g. Belden) 

Controllers wired in series, not in star, no ramification 

Data bus termination resistor (Z/R) at the beginning and end of bus 

# under restriction, as the connection of the BMS side is not known. 

Interfaces on Stulz Controllers 

Typ Board RS232-1 RS232-2 RS485-1 RS485-2 

Funktion Function Terminal Klemme Funktion Function Terminal Klemme Funktion Function Terminal Klemme Funktion Function Terminal Klemme 

C1002 Controller - - - - Stulz-Bus X10:32=Lo 

X10:33=Hi 

C1010 SERC1010 - - - - BMS-Bus 

C2020 SERC1010 - - - - BMS-Bus 

"+" = Hi 

"–" = Lo 

"+" = Hi 

"–" = Lo 

C4000 Max-Version - - - - Stulz-Bus P2:19=Hi 

P2:20=Lo 

C5000 

C6000 

C7000 

Redesign 

Max-Board - - - - Stulz-Bus 2=Hi 

3=Lo 

MIB-Board BMS-Port X6:1-9 - - Stulz-Bus X5:3=Lo 

X5:4=Hi 

Controller 

Service- 

Port 

X4:1-9 - - Stulz-Bus X5:11=Hi 

X5:12=Lo 

- - 

- - 

- - 

I/O-Bus 


P1:14=Hi 

P1:15=Lo 

- - 

I/O-Bus 

I/O-Board - - - - - - I/O-Bus 

MIB-Board 

MIB-Board 

IOC 

AT 

Service- 

Port 

Service- 

Port 

Service- 

Port 

Service- 

Port 

* with protocol "SDC/MIB": Stulz bus 

** with EBUS board 

X4:1-9 BMS-Port X12:1-9 Stulz-Bus X5:11=Hi 

X5:12=Lo 

X4:1-9 BMS-Port X12:1-9 Stulz-Bus X5:11=Hi 

X5:12=Lo 

X15:1-9 - - I/O-Bus 

X4:1-9 BMS-Port X12:1-9 I/O-Bus 



X1:1=Lo 

X1:2=Hi 

X5:13=Hi 

X5:14=Lo 

X1:31=Lo 

X1:32=Hi 

X5:13=Hi 

X5:14=Lo 

X5:13=Hi 

X5:14=Lo 

X1:56/58=Hi 

X1:57/59=Lo BMS-Bus** X1:1=Hi ** 

X1:2=Lo 

X5:11=Hi 

X5:12=Lo 

BMS-Bus* 

X5:13=Hi 

X5:14=Lo 


A2. BMS - Timing 

Adjustments at the customer side BMS 

BMS-Data 

BMS- 

Request 

No. 1 

BMS- 

Request 

No. 2 

t 

MIB7000- 

Data 

MIB- 

Response 

No. 1 

MIB- 

Response 

No. 2 

t1 t2 t3 

t 

t4 

t1: Non-response timeout: 4s 

t2: Response-time of MIB 

Value depends on number of requested data points and of the protocol 

t3: Time-delay: is omitted 

t4: respectively: n • t4: (with n: number of necessary requests) Total refresh 

rate for the complete unit image (refresh of all parameters and alarms) 


B. Additional tools 

Furthermore helpful for the start-up: 

1. PC / laptop 

2. Service cable (modem cable with SUB-D9 connector) 

The following software is necessary for the configuration and the start up 

and can be downloaded from the Stulz site (E-Stulz area): 

1. C7000-Service x_x.exe (x_x stands for the version N°) 

Service cable/modem cable 

Pin assignment: 

C7000AT Board 

MIB Board (X4 plug) 

PC or Notebook (COM-Port) 

9 pin SUB-D socket 9 pin SUB-D socket 

Pin Function Pin 

1 DCD 1 

2 RXD 2 

3 TXD 3 

4 DTR 4 

5 GND 5 

6 DSR 6 

7 RTS 7 

8 CTS 8 

9 RT free 

9 

To avoid a destruction of electronical parts by different earth potentials 

when Stulz boards are connected to a mains-operated PC, we 

recommend to use a galvanically isolated interface converter. 

The converter features a RS232 socket to connect the service cable 

for the C7000AT- or MIB board and a USB socket to connect the 

enclosed cable, which has to be plugged in the PC. 

RS232 - USB interface converter, 

galvanically isolated 

(option, no part of standard volume) 


STULZ Company Headquarters 

D 

STULZ GmbH 

Holsteiner Chaussee 283 . 22457 Hamburg 

Tel.: +49 (40) 55 85-0 . Fax: +49 (40) 55 85 352 . products@stulz.de 

STULZ Subsidiaries 

AUS 

AT 

BE 

CN 

E 

STULZ AUSTRALIA PTY. LTD. 

34 Bearing Road . Seven Hills NSW 21 47 

Tel.: +61 (2) 96 74 47 00 . Fax: +61 (2) 96 74 67 22 . sales@stulz.com.au 

STULZ Austria GmbH 

Lamezanstraße 9 . 1230 Wien 

Tel.: +43 (1) 615 99 81-0 . Fax: +43 (1) 616 02 30 . info@stulz.at 

STULZ Belgium BVBA 

Tervurenlaan 34 . 1040 Brussels 

Tel.: +32 (470) 29 20 20 . info@stulz.be 

Stulz Air Technology and Services Shanghai Co., Ltd. 

Room 5505, 1486 West Nanjing Road, JingAn . Shanghai 200040 . P.R. China 

Tel.: +86 (21) 3360 7133 . Fax: +86 (21) 3360 7138 . info@stulz.cn 

STULZ ESPAÑA S.A. 

Avenida de los Castillos 1034 . 28918 Leganés (Madrid) 

Tel.: +34 (91) 517 83 20 . Fax: +34 (91) 517 83 21 . info@stulz.es 

F STULZ FRANCE S. A. R. L. 

107, Chemin de Ronde . 78290 Croissy-sur-Seine 

Tel.: +33 (1) 34 80 47 70 . Fax: +33 (1) 34 80 47 79 . info@stulz.fr 

GB 

I 

IN 

STULZ U. K. LTD. 

First Quarter . Blenheim Rd. . Epsom . Surrey KT 19 9 QN 

Tel.: +44 (1372) 74 96 66 . Fax: +44 (1372) 73 94 44 . sales@stulz.co.uk 

STULZ S.p.A. 

Via Torricelli, 3 . 37067 Valeggio sul Mincio (VR) 

Tel.: +39 (045) 633 16 00 . Fax: +39 (045) 633 16 35 . info@stulz.it 

STULZ-CHSPL (INDIA) PVT. LTD. 

006, Jagruti Industrial Estate . Mogul Lane, Mahim . Mumbai - 400 016 

Tel.: +91 (22) 56 66 94 46 . Fax: +91 (22) 56 66 94 48 . info@stulz.in 

NL STULZ GROEP B. V. 

Postbus 75 . 1180 AB Amstelveen 

Tel.: +31 (20) 54 51 111 . Fax: +31 (20) 64 58 764 . stulz@stulz.nl 

NZ 

PL 

SG 

USA 

ZA 

STULZ New Zealand Ltd. 

Office 71, 300 Richmond Rd. . Grey Lynn . Auckland 

Tel.: +64 (9) 360 32 32 . Fax: +64 (9) 360 21 80 . sales@stulz.co.nz 

STULZ POLSKA SP. Z O.O. 

Budynek Mistral . Al. Jerozolimskie 162 . 02 – 342 Warszawa 

Tel.: +48 (22) 883 30 80 . Fax: +48 (22) 824 26 78 . info@stulz.pl 

STULZ Singapore Pte Ltd. 

33 Ubi Ave 3 #03-38 Vertex . Singapore 408868 

Tel.: +65 6749 2738 . Fax: +65 6749 2750 . andrew.peh@stulz.sg 

STULZ AIR TECHNOLOGY SYSTEMS (SATS) , INC. 

1572 Tilco Drive . Frederick, MD 21704 

Tel.: +1 (301) 620 20 33 . Fax: +1 (301) 662 54 87 . info@stulz-ats.com 

STULZ South Africa Pty. Ltd. 

Unit 18, Jan Smuts Business Park . Jet Park . Boksburg . Gauteng, South Africa 

Tel.: +27 (0) 11 397 2363 . Fax: +27 (0) 11 397 3945 . aftersales@stulz.co.za 

IT Cooling Solutions 

Close to you all over the world 

With specialist, competent partners in our subsidiaries and 

exclusive sales and service partners around the world. 

Our six production sites are in Europe, North America and Asia. 

For more information, please visit our website www.stulz.com.

STULZ_BMS_69B_0714_en

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?