Generex CS141 - Page 54

Version: 2020-09-04
54
Copyright of the European Union is effective (Copyright EU) (c) 2019 GENEREX Systems GmbH, Hamburg, Germany, All rights reserved
TEL +49(40)22692910 - EMAIL generex@generex.de - WEB www.generex.de (This and all other product datasheets are available for download.)
In case of the SNMP agent suddenly dies, these options are available:
No action the recovery service will not bother the SNMP agent with something like restarting.
Restart the recovery service will restart the SNMP agent if it does not answer.
Delay [Min] time delay until the Recovery service will restart the agent.
Note:
In some cases, SNMP v1 queries may cause a hung up of the SNMP agent. Although not officially supported, the CS141 can work with
the appropriate SNMP v.1 queries. The agent recovery service ensures that the agent is automatically restarted in case of doubt.
BACNET
With firmware release 1.88, the official BACnet standard is supported. Your will find this menu only ofter running an update to at least
this firmware version.
Some facts about BACnet
Where is BACnet from?
In 1987, the American Society of Heating Refrigeration and AirConditioning Engineering - known as ASHRAE - founded the standard
project committee SPC2 135P - members of this committee included companies like Andover Controls, Honeywell, Johnson Controls,
Trane and many others. The thankless task of this convened committee was to define a communication protocol for the monitoring,
regulation and energy management of buildings. However, in December 1995 and after some back and forth as well as several
submitted designs a solution was found: BACnet was adopted as the ASHRAE / ANSI standard by the American National Standards
Institute. Just three years later, the standard was initially adopted by Europe as DIN V ENV 1805-1. BACnet has become one of the
most widely used standard in America and thanks to its flexibility, extensive building management, automation can be implemented and
easily expanded by new devices.
The future of BACnet: BACnet over IP
With BACnet over IP, BACnet goes on:
Existing IT infrastructures can be used, which significantly reduces costs for implementation. Ultimately, you only need a few BACnet-
compatible network infrastructure devices like routers and switches with today's standard RJ45 ports.
Requirements
BACnet over IP is based on existing TCP / IP structures, but extends these by a lot of functions that are required in building automation.
It is important that a BACnet device only works if the corresponding infrastructure supports routing the BACnet extendet protocol - for
example, routers and switches must also be able to handle BACnet over IP. Alternativly, BACnet-compatible routers must be installed to
connect BACnet segments with each via common network hardware.
For the exact configuration of the existing BACnet infrastructure, please contact your local system administrator.
Required ports to use BACnet over IP
BACnet uses the UDP protocol and usually these standard ports:
- 47808 or 47809
Note:
Unlike e.g. Modbus, the standard ports do not follow standards in port binding. Due to this fact, BACnet does not specify any port that
must be used for devices:
You can set up any port for your BACnet system that fits to your IT infrastructure. However, more modern BACnet port objects require
support in the areas 47808 - 47823 (0xBAC0 - 0xBACF) and for the dynamic port areas 49152 - 65535
Please refer to your local system administrator for the correct port settings.