CORRIGO E VENTILATION VARIABLES FOR EXOLINE AND MODBUS 3.6 MANU

Chapter 1 Corrigo with EXOline, Modbus and BACnet communication 5
Baudrate
150, 300, 600, 1200, 2400, 4800, 9600
BACnet communication
Corrigo is capable of communication via the BACnet-AAC (Advanced Application Controller)
protocol, using either IP or MS/TP data link formats. A B-AAC unit is a device that may be intended
for a specific application, but which supports some degree of programmability allows the user to do
more – such as generate alarms, definine schedules, synchronize clocks, etc.
In order to connect a Corrigo running a ventilation application to a BAS (Building Automation
System) via BACnet/IP, a third generation Corrigo with a TCP/IP port is required. To connect to a
BAS via BACnet MS/TP, a third generation Corrigo with an RS485 communication port is required.
With the default install path entered upon software installation, BACnet objects lists will be located
in the following directory:
C:\Program Files\EXO\SLib\Corrigo\VentilationProgram3_6\BACnet
The lists can also be found in E tool
©
, under the menu “Help”.
BACnet type
The BACnet type of signals:
10XXX = Read and write binary
20XXX = Read binary
30XXX = Read and write analogue
40XXX = Read analogue
30XXX = Read and write multistate
40XXX = Read multistate
(Where XXX = Modbus address)
NOTE: In the variable lists contained in this manual, the following abbrevations are used:
AV = Analogue Value
BV = Binary Value
MSV = Multistate Value
BACnet object names are the same as for EXOL type objects, but are shortened by removing the
preamble “Cor_” (e.g.: “VentSettings.Cor_OverHeatFastStop” becomes
“VentSettings.OverHeatFastStop”, etc.).
BACnet/IP configuration
Upon delivery, the BACnet/IP protocol is disabled as a default. To enable BACnet communication,
simply change the setting “Not active” to “Active”. The protocol will now be available for use:
TCP/IP 
BACnet/IP
communication
Active 