TOPS Trend Open Protocol Server

Transcription

1 Data Sheet Trend Open Protocol Server Description Trend Open Protocol Server () is a Windows based software application that runs on a PC to provide the communications between compatible devices (e.g. 963 v3.00 or greater) on the Trend IQ network and third party devices (e.g. BACnet devices). can be installed on the same PC as 963 or on a different PC provided the device can access the PC over IP. The licence to run also determines which third party networks is able to communicate with (e.g. BACnet) and potentially the number of points that can be accessed, depending on the driver option used. Features Provides communications with BACnet and TONN s. Enables the 963 to read values from, or write values to BACnet and TONN s Receive alarms from BACnet devices. Can be installed on same PC as 963 or a PC remote from the compatible device (963). Compatible with 963. Simple web based configuration. Trend mapping for points can be edited in. 963 can learn, view, and collect labels of all the devices (both online and offline) present in the database. Later, 963 can configure these devices. System tray icon has been added to provide access to features. FUNCTIONALITY learns the structure of the third party network (e.g. BACnet) and the devices on it. These devices and their values are then mapped to virtual Trend devices ( devices) inside. The devices are then grouped into Trend Lans, and made available to compatible devices (e.g. 963) using Trend addressing, making them appear to the compatible device as Trend devices. Values can then be displayed, and if appropriate adjusted from the compatible device in the normal way. Alarms from the third party network can be received by the compatible device. Learnt 3rd party devices learns system Mapping Mapped virtual Trend devices 3rd Party Devices compatible device Trend Open Protocol Server () Data Sheet TA Issue 8, 16-May Applies to

2 Data Sheet FUNCTIONALITY (continued) can operate in one of two modes: Standalone Bound Standalone mode: When operating in standalone mode connection to is via its vcnc. The device connected to the vcnc will have access to the 3rd party system(s) via the Lans and devices inside linked to the 3rd party devices. 963 vcnc Device Lan 22 Device CNC Device Lan 23 Internetwork Device vinc The diagram above shows operating in standalone mode. There are two Lans, Lan 22, and Lan 23 joined by an internetwork. Lan 22 is the Lan that contains and consists of itself, the vcnc inside, and a vinc. Lan 23 is a Lan of devices. The entire system is built inside. The 963 connects over Ethernet to the vcnc and is able to access all the devices on Lan 22 and 23. Note that the 963 has to have a separate connection to any IQ2 or 3 controllers which may be present Bound Mode: When operating in bound mode joins with the IQ network to which it is connected to form one large network including the Lans and devices. Connection to can be via any vcnc on the network although it is recommended that connection be made using the vcnc The device connected to the vcnc will have access to the 3rd party system(s) via the Lans and devices inside linked to the 3rd party devices, and all the devices on the Trend IQ network. When operating in this mode devices are able to receive data to, global to and data from IC comms messages from an IQ3/IQ4 controller and reply to data from IC comms with the correct value. This enables values to be transmitted between IQ3/IQ4 controllers, and the 3rd party devices using IC comms. Lan 20 Lan vinc Internetwork vcnc Lan 22 CNC Device Device Device Lan 23 Device In the diagram above the is operating in bound mode and forms an internetwork with other Trend devices on the Ethernet network forming an IQ system consisting of Lan 20, Lan 21, Lan 22, and Lan 23. Lans 20 and 21 are normal Lans consisting of IQ3/IQ4 controllers. Lan 22 is the Lan that contains and consists of two IQ3/IQ4 controllers, itself, and the vcnc inside. Lan 23 is a Lan of devices. The 963 connects over Ethernet to the vcnc and is able to access all the Lans. Configuration: configuration is carried out using a number of web pages that lead you through the configuration process. System Tray icon: The system tray icon provides access to features. Right click the icon for the following options like: License, Reset project, Start, Stop, configuration, and View License. is online is also displayed when is connected. Reset: can be reset to operate as a fresh installation. The reset will reset the config.bog file, navfile, histories and alarms. BACNET DRIVER The BACnet driver provides the ability for compatible devices to communicate with devices on a BACnet network. 963 is able to read values from, or write values to the BACnet devices, to receive alarms from those devices, and obtain BACnet Trends. Objects in the BACnet devices are mapped to Trend modules in the devices. BACnet analogue input objects map to Trend sensor modules. BACnet binary input objects map to Trend digital input modules. BACnet analogue output objects map to Trend analogue driver modules. BACnet schedule objects map to Trend time zone modules. Exception_Schedule Read/Write Exceptions (Cn) Weekly_Schedule Read/Write Normal Week Wn). Note: Supports only Boolean schedules. 2 Trend Open Protocol Server () Data Sheet TA Issue 8, 16-May Applies to 3.21.

3 Data Sheet BACNET DRIVER (continued) BACnet analogue value objects map to Trend knob modules. Low_Limit Read Bottom Range (B) High_Limit Read Top Range (T) BACnet binary value objects map to Trend switch modules. BACnet binary output objects map to Trend digital driver modules. BACnet Property Trend Parameter BACnet device objects maps to the Trend time module, and address module. Time Module Local_Time Read Hour (H) Local_Time Read Minute (N) Local_Date Read Day (D) Local_Date Read Month (M) Local_Date Read Year (Y) Local_Date Read Day of Week (W) Address Module Object_Name Read Identifier (D) Firmware_Version Read Version (C) BACnet Trend Log Objects map to the Trend plot modules. Buffer_Size Read Number of Records (N) Record_Count Read Record Count (R) Total_Record_ Read Total Record Count (C) Count Log_Buffer Read Log Values (Bn) Log_Interval Read Interval (I) Notification_ Threshold Read Notification Threshold (n) Records_Since_ Notification Last_Notify_Record Read Read Records Since Last Notification (r) Last notify Record (l) BACnet Multi State Input objects map to Trend sensor modules. BACnet Multi State Value objects map to Trend knob modules Low_Limit Read Bottom Range (B) High_Limit Read Top Range (T) BACnet Multi State Output objects map to Trend analogue driver modules. The mapping of BACnet points to Trend points can be edited as per the table below. BACnet Point Multi State Multi State Value Multi State Analogue Input Analogue Value Analogue Output Binary Input Binary Value Binary Output Possible Trend Mapping Switch/Digital Input/Digital Driver Switch/Digital Input/Digital Driver Digital Driver/Switch/Digital Input When a point is mapped to a sensor its properties are mapped as shown below. When a point is mapped to a knob its properties are mapped as shown below Low_Limit Read Bottom Range (B) High_Limit Read Top Range (T) When a point is mapped to an analogue driver its properties are mapped as shown below. When a point is mapped to an digital input its properties are mapped as shown below. When a point is mapped to an digital driver its properties are mapped as shown below. Trend Open Protocol Server () Data Sheet TA Issue 8, 16-May Applies to

4 Data Sheet BACNET DRIVER (continued) BACnet Alarms 963 can receive BACnet alarms from BACnet alarm notification classes that has subscribed to. The BACnet alarms are converted to Trend alarms by and passed to 963. Sensor HIGH, sensor LOW, sensor READ, driver SDGT, plot BBUF, digital input alarms are calculated using the EVENT TYPE property, and the TO Event state according to the table below. Other alarms are assigned alarm codes by 963 see the 963 Engineering Manual for details. BACnet Parameters Trend Alarm Sensor Digital Input Driver Plot HIGH LOW READ DI=1 DI=0 SDGT BBUF To Event State normal fault offnormal high-limit low-limit Event Type Property CHANGE_OF_STATE COMMAND_FAILURE OUT_OF_RANGE BUFFER_READY For details of BACnet capabilities with 963 see the 963 and Protocol Implementation Conformance Statement (TP201011). TONN DRIVER The TONN driver provides the ability for compatible devices to communicate with devices on a number of different 3rd party systems with which TONN can communicate. TONN is available with drivers for the following systems as standard: BACnet IP BACnet MSTP EIB/KNX IP ModbusRTU MasterModbusRTU Slave ModbusTCP Master ModbusTCP Slave MBus Serial MBus IP obix SNMP Additional drivers can also be purchased for the following systems: Flex Driver over RS-232 or RS-485 Micros Fidelio hotel room booking system Helvar serial driver American Automatrics PHP over RS-232 or RS-485 Protec fire panel serial. Global Cache American Automatrics PUP over RS-232 or RS-485 Horstmann serial Resol solar water heating controller serial The TONN communicates with the 3rd party systems and retrieves specified values. The TONN driver reads these values from the TONN and makes them available to compatible devices as Trend devices. Values can then be displayed, and if appropriate adjusted from the compatible device in the normal way. The driver does not support BBUF alarms on logs coming from TONNs. Use of the TONN driver requires a Trend Open Network Node (TONN) to be installed. This must be purchased separately. The TONN drivers should be used when there are a high number of 3rd party data points in the TONN that are required at the 963 as it is more cost effective. Alarms can be configured using alarm extension on the required points on the TONN and sending them to as an alarm recipient. Where the number of 3rd party data points is low, there is no need for provided there are enough modules in the IQ device. TONN can send the points to the IQ strategy modules which can be accessed from 963 in the normal way. Alarms and data logging can be configured on the Trend modules linked to the 3rd party point in the normal way. 4 Trend Open Protocol Server () Data Sheet TA Issue 8, 16-May Applies to 3.21.

5 Data Sheet COMPATIBILITY 3rd Party Systems: BACnet using BACnet driver, BACnet IP, BACnet MSTP, EIB/KNX IP, ModbusRTU, MasterModbusRTU Slave, ModbusTCP Master, ModbusTCP Slave, MBus Serial, MBus IP, obix, SNMP, Flex Driver over RS-232 or RS-485Micros Fidelio hotel room booking system, Global Cache, Horstmann serial, Helvar serial driver, American Automatrics PHP over RS-232 or RS- 485, American Automatrics PUP over RS-232 or RS-485, Resol solar water heating controller serial, and Protec fire panel serial and using TONN driver. Communications: It provides a single vcnc connection for use by compatible Trend devices. 963: 963 v3.00 or greater is compatible. TONN devices mapped via require 963 v3.30 or greater. Note that / TONN does not support BBUF alarms on logs coming from TONNs therefore 963 cannot use BBUF alarms to trigger data recording. Therefore, data recording must be performed at regular intervals. SET: SET is not a compatible device but if connected to a system to which is bound is displayed in the System View. TEM: is compatible with TEM V1 or greater. INSTALLATION A step-by-step installation program performs the installation of the software. After installation the software must be licensed, and configured to operate as required. See the Installation Instructions (TG201036) for more details. Trend Open Protocol Server () Data Sheet TA Issue 8, 16-May Applies to

6 Data Sheet ORDER CODES ORDER CODES /BAC/12DEV /TONN Software for communication with BACnet network, and with the ability to interact with 12 devices. Software for communication with Trend Open Network Node (TONN). USA SPECIFIC ORDER CODES /BAC/12DEV/USA /LOGIC1/500LOADS Software for communication with BACnet network, and with the ability to interact with 12 devices. Software for communication with Logic 1, and with the ability to interact with 500 loads. TREND OPEN PROTOCOL SERVER () UPGRADE ORDER CODES If more capacity is required it is necessary to also order the appropriate upgrade as well as appropriate entry level product using the codes below. E.g. to order for use with up to BACnet 60 devices it is necessary to order: /BAC/12DEV and /BAC/UP/60DEV Upgrade Order Codes /BAC/UP/60DEV /BAC/UP/240DEV Upgrade to 60 BACnet devices. Upgrade to 240 BACnet devices. USA Specific Upgrade Order Codes /BAC/UP/60DEV/USA /BAC/UP/240DEV/USA /LOGIC1/UP/750LOADS /LOGIC1/UP/1250LOADS Upgrade to 60 BACnet devices. Upgrade to 240 BACnet devices. Upgrade to 750 Logic 1 loads. Upgrade to 1250 Logic 1 loads. Note that the Logic 1 driver is only available in the USA. 6 Trend Open Protocol Server () Data Sheet TA Issue 8, 16-May Applies to 3.21.

7 Data Sheet SPECIFICATIONS SYSTEM REQUIREMENTS Before installing you should ensure that the PC meets the system requirements. The specifications below refer to a standard PC with mouse, keyboard, hard drive, CD drive, monitor, and sound capabilities (optional). Recommended The following specification provides a minimum environment for running effectively. For best results and demanding applications a system with greater CPU performance and more memory should be used. will run on the following operating systems. The PC must be of a suitable specification to run the required operating system. Windows 10 Home 32 bit Windows 10 Home 64 bit Windows 10 Pro 32 bit Windows 10 Pro 64 bit Windows 10 Enterprise 32 bit Windows 10 Enterprise 64 bit Windows 8 32 bit Windows 8 64 bit Windows 8 Pro 32 bit Windows 8 Pro 64 bit Windows 8 Enterprise 32 bit Windows 8 Enterprise 64 bit Windows bit Windows bit Windows 8.1 Pro 32 bit Windows 8.1 Pro 64 bit Windows 8.1 Enterprise 32 bit Windows 8.1 Enterprise 64 bit Windows 7 32 bit Windows 7 64 bit Windows Vista Business SP2 32 bit Windows Server 2008 SP2 32 bit Standard Windows Server 2008 SP2 32 bit Enterprise Windows Server 2008 SP2 64 bit Standard Windows Server 2008 SP2 64 bit Enterprise Windows Server 2008 R2 Windows Server 2003 SP2 32 bit Standard Windows Server 2003 SP2 32 bit Enterprise PERFORMANCE LIMITATIONS BACnet Driver For single driver installations, the maximum number of devices and points is limited by the licence details. For multiple driver installations, the maximum number of devices and or points will need to be lowered for the minimum specification machine. To achieve maximum capacities then machine performance must be increased by the minimum specification amount per driver used, or another machine should be used for that driver. In addition to this there are maximum limits for the following point types for a whole configuration. Plot modules 1000 Time zones 500 If there is a requirement to transfer information from a Trend system to a third party system using IC Comms the direct third party IC Comms features in the IQ3/IQ4 controllers should be used (i.e. a BACnet XP IQ3/IQ4 to a third party BACnet device). However in the case where this is not supported has limited IC Comms capabilities that enable the transfer of data between supported systems. In this case where is involved in transferring IC Comms data from IQ controllers through to a third party system the following limits should be observed. Directed IC Comms connections 25 or a single global to directed to a single Lan Any one of the above maxima when used in isolation is acceptable; however a reduction in performance will be experienced when combinations of maximums are used. Actual performance will need to be assessed by the user in each case. Improvement in performance can be achieved by increasing the specification of the machine, or if necessary running a further copy of on another machine. In addition to meeting the requirements for the operating system requires the following: 2 GHz or greater processor 1 GB or greater RAM. 40 GB or greater hard disk Ethernet network card For best results and demanding applications a system with greater CPU performance and more memory should be used. If and 963 are to be run on a single PC a dual core processor is recommended. Note: To optimise a PC for best performance the correct JAVA settings must be used. Note: can be used on 32-bit Windows with default heap settings for small to medium installations, though for more intensive use the Java heap settings2 should be increased up to a maximum of 25% of the physical memory in the PC or 800MB whichever the lower, performance may be significantly impacted by other applications running on the same machine. Too high a figure may result in not starting. For best results and larger installations install on 64-bit Windows and use higher Java heap settings2 again less than 25% of physical memory must be used. Note: v 3.21 is supported on IE 8, 9, 10, and 11 browsers. Trend Open Protocol Server () Data Sheet TA Issue 8, 16-May Applies to

8 Data Sheet CLIENTS Any configuration providing they are running TCP/IP networking protocol, have an Ethernet card, a web browser and have the JAVA runtime environment J2SE7.0 update 60 (32bit) or greater installed. The browser must have JAVA script enabled. Note: It is strongly recommended to have Java8 with latest update. Note: Popup blocking software must be disabled, or configured to allow popups from. Windows, Windows Vista, Windows 8, and Windows 8.1 are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. BACnet is a trademark of ASHRAE. Please send any comments about this or any other Trend technical publication to techpubs@trendcontrols.com 2016 Honeywell Technologies Sàrl, ECC Division. All rights reserved. Manufactured for and on behalf of the Environmental and Combustion Controls Division of Honeywell Technologies Sàrl, Z.A. La Pièce, 16, 1180 Rolle, Switzerland by its Authorized Representative, Trend Control Systems Limited. Trend Control Systems Limited reserves the right to revise this publication from time to time and make changes to the content hereof without obligation to notify any person of such revisions or changes. Trend Control Systems Limited Albery House, Springfield Road, Horsham, West Sussex, RH12 2PQ, UK. Tel:+44 (0) Fax:+44 (0) Trend Open Protocol Server () Data Sheet TA Issue 8, 16-May Applies to 3.21.