Issue BACnet Service does not start after enabling BACnet IP on a UNC station. The following error messages are seen in the UNC standard output. ERROR: Error initializing IP link layer. [IpLinkLayer.updateLocalAddress] java.lang.NoSuchMethodError: tridium/nre/Platform.getLocalHost()Ljava/net/InetAddress; ERROR: Cannot startService [Sys: BACnetService [12] BACnetService] java.lang.NullPointerException ERROR: Run error [BTrprt] java.lang.NullPointerException Product Line TAC IA Series Environment I/A Series UNC running at version r2.301.5xx prior to version r2.301.535 with BACnet 2.305.535a. Cause Most I/A Series R2 Niagara JAR files are backward compatible. Refer to Can jar files from Niagara R2 version 532 be used with a UNC running version 330? for details.  There were some changes to the BACnet service IP to support the new JACE-603/645 platforms. Because of these changes to the R2 core, the BACnet 2.305.535a JAR file is not backward compatible.  Resolution Upgrade the UNC to version r2.301.535. Refer to the Installation Instructions for upgrade procedure. 

Issue Can the Xenta 913 be used as a NPR in I/NET? Will the Xenta 913 transfer (via Connection Objects) from one I/NET link to another? Product Line TAC INET Environment I/NET Seven Xenta 913 Cause Although the Xenta 913 appears in the I/NET network configuration and parameters appears the same as a NPR not all functions are possible.  Refer to the resolution to below for supported communications: Resolution Even though the 913 has some basic NPR functionality to I/NET it does not function 100% as a NPR like the 527 or 731 does. The 913 will not pass any AMT information to a host, nor will it pass global indirect points from link to link. It is recommended to only use the 527 or 731 as an NPR to an I/NET system.   Click the picture above to open this image in PDF format. It should also be noted that provided the Xenta 913 is connected on the TCPIP network it is possible to create connection objects across I/NET links.  The Xenta must be part of the I/NET network, that is add the reference host to the Xenta 913 configuration then all links will be available to the device.

Issue Step by step instructions to configure the Lonworks Network Interfaces application to communicate over IP-852 to a Loytec L-IP router using the Echelon driver Product Line Field Devices, Other, TAC Vista Environment LNS Turbo Lonmaker turbo Lonworks Network Interfaces Loytec L-IP  Cause Instructional how to document steps through the necessary set-up to get a Loytec L-IP to communicate in a Vista system using the Echelon driver Resolution It is preferred to use Loytec's own driver rather than Echelon's driver, and also the Loytec driver is the only one supported in SmartStruxure, how ever it is possible to use Echelon's driver following the guide below. To learn more about the L-IP and understand the difference between two drivers, check this video: https://www.youtube.com/watch?v=cLNBv6tEDXg or Loytec L-IP 101 Note 1: The first steps would be to verify the IP addresses needed for both the computer and the Loytec L-IP router. In this example, we will be using 10.159.5.39 for the L-IP and 10.159.3.26 for the computer running LNS. The default IP address of the Loytec L-IP router is 192.168.1.254. In most cases the default IP needs to be changed to match the system network. Please reference the L-IP Users Manual page 20 for instructions on how to change the IP address of the device. Note 2: In our example there is only one L-IP, so it is configured as the configuration server. Remember: One L-IP within any Vista Server system has to be configured as the configuration server. Please reference page 52 of the L-IP users manual for instructions on how to set a L-IP as a configuration server. This document has the web instructions in step 12. Navigate to the windows control panel and open the Lonworks Interfaces application. In lonmaker 3.1 with LNS 3.1 the program will be lonworks IP channels: Within the Lonworks Interfaces application choose the IP-852 tab: Under network interface click the Add button: In the Network Interface Add window you will need to name your connection. In this example it is just simply named IP for the IP channel within LNS. The IP Address should be set to the local IP of the computer. The IP Port should be left at the default 1628 and Channel Timing should be LAN. Click OK: Back within the LonWorks Interfaces application you should now see the named IP network, the IP address, and the IP port number: Next, Click the Test button to test the communications from LonWorks Interfaces to the L-IP configuration server: Check the box to Set the Configuration Server Address and type in the IP address of you configurations server L-IP router. The default IP port used in network interfaces is 1628 so requesting a communication test from the L-IP requires the configuration server return port to be set to 1629. Then click the Start Test button: After clicking Start Test you will see a message verifying the test has started. If your test is successful you will see the following message: Your Lonworks Network Interfaces is now configured for a TCPIP connection and properly setup to communicate to a Loytec L-IP router configured as a configuration server. If you never receive a message showing a successful test, please proceed to step 9. Login to the L-IP web interface by opening a web browser and typing the IP address of the device. In our example it is http://10.159.5.39. This is the default web page within the L-IP web interface: Click the Config button: You will now be prompted to login to the controller. The default username is Administrator and the default password is admin Note: for new version of L-IP, its username is admin and password is loytec4u. Click on EIA-852 Server and make sure the Config server status is enabled and the Config server port is 1629. If any changes are necessary, a message will appear at the bottom of the web page to reboot the device for the changes to take effect. And if there are more than one LIP in this network, all the other LIPs apart from the first one need to choose disabled option for the Config server status. Click on EIA-852 Ch. List. In the channel list you should see your local L-IP device and IP address. The next step is to add the IP address of the HOST PC running the Lonworks Network Interfaces application. Click the Add Device button. Name your device. In this example it is named PC. Then type in the IP address and the port number of the HOST PC and click save. Click in the Recontact button and go back and repeat step 7. You should now see a successful test from your configuration server. If there are more than one LIP in the network, add all the other LIPs in this list. Now your Loytec L-IP router is communicating to the Lonworks Network Interfaces program. This will allow your LNS server to communicate on the IP channel connection within Lonmaker or NL220 and use this Loytec L-IP as its connection to the Lonworks network. Additional setup information is available here in the L-IP Users Manual.

Issue Attempting to map a 3rd party bacnet alarm and there is no way to navigate down to the object Click here to see the following snapshots illustrating the issue Environment SmartStruxure Windows XP SP3 Windows 7 Cause We currently do not support external alarming (that is a BACnet alarm in the AS or ES monitoring a property in some other device.) This is being considered for a future revision. Resolution If the 3rd party device does not support alarming they would have to create an SmartStruxure alarm to monitor it.    An alternative work around if the 3rd party device supports alarms (Ex. Veeder Root in this case) is to create a BACnet Value in the AS (or ES) and then binding it from the Veeder Root object to the local value, and configure alarming from there.

Issue I/NET uses a different "large number" hexadecimal format to represent individual cards.  To convert to a Continuum system, these must be decoded into Facility Codes and Card Numbers. Product Line Andover Continuum, TAC INET Environment I/NET Seven Security converted to Continuum Cause Different representations of individuals in the two systems. Resolution Download the "ZIP" file here conversion Excel spreadsheet. Press the "Clear Values" button to zero out the inputs. Select the correct format between the four options: 26-Bit Wiegand 32-Bit Wiegand Format (CSI) 35-Bit Wiegand Format 37-Bit Wiegand Format Enter the hexadecimal value and the Facility Code and Card Number will populate automatically.

Issue How can a schedule be added to a personnel records particular area? Environment Continuum 1.xx Cause Adding a schedule a one area in a personnel objects areas list. Resolution This link explains step by step how to add a schedule to a personnel objects area.

Issue In MNB-1000 (Plant Controller) firmware Revision 1.50E, the Spanning Tree Protocol is Disabled, by default. All previous versions were shipped with the Spanning Tree Protocol enabled. Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller), firmware Revision 1.50E, and later. Cause In some cases where multiple BACnet routers (eg, MNB-1000, UNC, ENC, etc) were installed on the same BACnet-IP internetwork, having the Spanning Tree Protocol enabled in the MNB-1000 would allow a "router loop". Resolution Be aware that in MNB-1000s with firmware Revision 1.50E and later, the Spanning Tree protocol is disabled, by default. Click here to see the Release Notes for firmware Revision 1.50E . It is always recommended the highest firmware version available for the MNB-1000 be used.  Many issues have been addressed for better functionality.

Issue How to Retrieve Log values from TAC Vista MSSQL Database Environment TAC Vista and MSSQL Database Cause Requires third party access to retrieve Log Values from TAC Vista MSSQL Database Resolution 1. Refer to the attached PDF document for the procedure 2. Note: You’re limited to retrieve only one log object at a time

Issue When was the AC256 product discontinued? Environment AC256 Cause Discontinuation notices only seem to go back to 2007, at which time the AC256 had been discontinued for quite some time. Unable to find any reference to this products discontinuation. Resolution The AC256 was discontinued in 1998. A reference to this can be found in the Andover Controls Network News from February 1998. On page 2 on the right hand column, there is reference to discontinued products as of May 1, 1998. You find the bulletin here.

Issue When using a USB to RS-232 adapter and an MN-CIM, cannot connect to MicroNet 2000 controllers. Receive an ERROR = -510. The problem has also been seen on laptops with an integral serial port. Environment Laptop computer running the MN-CI or MN-FLO-BAL software tools,  any version MN-CIM Controller interface Module Cause One cause of ERROR = -510 is that the serial port or USB to RS-232 adapter does not supply enough power to the "port-powered" MN-CIM. When the CI software is running, but not communicating on the U-LINK, it requires only 12 mA at 5 VDC. To communicate on the U-LINK, the MN-CIM requires 14 mA at 5 VDC from the DTR control line of the port.  Some computers have a mechanism to sense the increased current draw and shut down the DTR line. This loss of power causes the MN-CIM to reset, and after 3 attempts to communicate the MN-CI software issues the ERROR= -510 message. Resolution See Technical Bulletin 01-104 for information  on the Patton Electronics power supply adapter, model 3PMF9-BC.

Issue When trying to run Workplace Tech 4.0 for the first time, it may not start successfully, and an error message will be displayed: "Microsoft Visual C++ Runtime Library, Runtime Error!" Environment Workplace Tech version 4.0 Visio 2002, SR1 Windows XP Professional, Service Packs 1-3 Windows 2000 Professional, Service Pack 4 Cause The error is typically caused by not initializing Visio 2002 before running WPT 4.0 for the first time. Resolution See Technical Bulletin TB04-02, which details the issue and resolution.

Issue How to filter in a listview AlarmEvent based on the EventNotification Environment Continuum Cause Continuum pre 1.91 did not allow filter in a listview AlarmEvent, based on the EventNotification Resolution See Continuum CyberStation Release Notes Version 1.91(Downloadable here) Fixed Problems 4.007 Cannot filter an AlarmEvent table based on the EventNotification using the query wizard (21101) Find another way to filter or upgrade your version of Continuum.

Issue Satchwell AR Series 7 Rotary Actuator requires replacement Product Line Field Devices Environment Satchwell AR Series 7 Rotary Actuators installed on Air Dampers, Satchwell MB Series or MBF Series Rotary Shoe Valve Bodies. Actuator types :- ARE ARM ARX ARMS Cause Obsolescence of Satchwell AR Series 7 Rotary Actuators Resolution Replace Satchwell AR Series 7 Rotary Actuators with appropriate Schneider Electric MD Series Rotary Actuators and wire as follows :- Satchwell AR Series 7 Rotary Actuators installed on Air Dampers. ARE ARE Series 7 Wire Number 2 = MD20A-24 Wire Number 2 ARE Series 7 Wire Number 3 = MD20A-24 Wire Number 3 ARE Series 7 Wire Number 1 = MD20A-24 Wire Number 1 ARE Series 7 Wire Number 5 = MD20A-24 Wire Number 5 ARX ARX Series 7 Wire Number 3 = MD20B-24 Wire Number 3 ARX Series 7 Wire Number 2 = MD20B-24 Wire Number 2 ARX Series 7 Wire Number 1 = MD20B-24 Wire Number 1 ARM ARM Series 7 Wire Number 3 = MD20B-230 Wire Number 3 ARM Series 7 Wire Number 2 = MD20B-230 Wire Number 2 ARM Series 7 Wire Number 1 = MD20B-230 Wire Number 1 ARM Series 7 Wire EARTH = MD20B-230 NO EARTH REQUIRED ARMS ARMS Series 76021Term 3 (Open) = MD10SR-TS Blue G ARMS Series 7602 Term 2 (L1) = MD10SR-TS Not used *1 ARMS Series 7602 Term 1 (N) = MD10SR-TS Brown GO ARMS Series 7602 Wire EARTH = MD10SR-TS NO EARTH REQUIRED ARMS Series 7603 Wire Number 2 = MD10SR-T Blue G ARMS Series 7603 Wire Number 1 = MD10SR-T Brown GO ARMS Series 7604 Wire Number 2 = MD10SR-TS Blue G ARMS Series 7604 Wire Number 1 = MD10SR-TS Brown GO *1 Disconnect from the supply, label, and make safe at the supply and actuator.   N.B. Should the Satchwell AR Series 7 Actuator (not applicable to ARMS) include a wired Auxiliary Switch then the following Accessory should also be wired on the Schneider Electric MD Actuator as follows:- MD – S1 One independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switch AR COMMON Wire Number S1 = MD-S1 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S1 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S1 N/C contact Wire Number S2 MD – S2 Two independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switches AR COMMON Wire Number S1 = MD-S2 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S2 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S2 N/C contact Wire Number S2 AR COMMON Wire Number S4 = MD-S2 COMMON Wire Number S4 AR N/O contact Wire Number S6 = MD-S2 N/O contact Wire Number S6 AR N/C contact Wire Number S5 = MD-S2 N/C contact Wire Number S5   Satchwell AR Series 7 Rotary Actuators installed on Satchwell MB Series Screwed Rotary Shoe Valve Bodies. ARE ARE Series 7 Wire Number 2 = MD10A-24 Wire Number 2 ARE Series 7 Wire Number 3 = MD10A-24 Wire Number 3 ARE Series 7 Wire Number 1 = MD10A-24 Wire Number 1 ARE Series 7 Wire Number 5 = MD10A-24 Wire Number 5 ARX ARX Series 7 Wire Number 3 = MD10B-24 Wire Number 3 ARX Series 7 Wire Number 2 = MD10B-24 Wire Number 2 ARX Series 7 Wire Number 1 = MD10B-24 Wire Number 1 ARM ARM Series 7 Wire Number 3 = MD10B-230 Wire Number 3 ARM Series 7 Wire Number 2 = MD10B-230 Wire Number 2 ARM Series 7 Wire Number 1 = MD10B-230 Wire Number 1 ARM Series 7 Wire EARTH = MD10B-230 NO EARTH REQUIRED N.B. Should the Satchwell AR 7 Series Actuator include a wired Auxiliary Switch then the following Accessory should also be wired on the Schneider Electric MD Actuator as follows :- MD – S1 One independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switch AR COMMON Wire Number S1 = MD-S1 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S1 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S1 N/C contact Wire Number S2 MD – S2 Two independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switches AR COMMON Wire Number S1 = MD-S2 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S2 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S2 N/C contact Wire Number S2 AR COMMON Wire Number S4 = MD-S2 COMMON Wire Number S4 AR N/O contact Wire Number S6 = MD-S2 N/O contact Wire Number S6 AR N/C contact Wire Number S5 = MD-S2 N/C contact Wire Number S5   Satchwell AR Series 7 Rotary Actuators installed on Satchwell MBF Series Flanged Rotary Shoe Valve Bodies ARE ARE Series 7 Wire Number 2 = MD20A-24 Wire Number 2 ARE Series 7 Wire Number 3 = MD20A-24 Wire Number 3 ARE Series 7 Wire Number 1 = MD20A-24 Wire Number 1 ARE Series 7 Wire Number 5 = MD20A-24 Wire Number 5 ARX ARX Series 7 Wire Number 3 = MD20B-24 Wire Number 3 ARX Series 7 Wire Number 2 = MD20B-24 Wire Number 2 ARX Series 7 Wire Number 1 = MD20B-24 Wire Number 1 ARM ARM Series 7 Wire Number 3 = MD20B-230 Wire Number 3 ARM Series 7 Wire Number 2 = MD20B-230 Wire Number 2 ARM Series 7 Wire Number 1 = MD20B-230 Wire Number 1 ARM Series 7 Wire EARTH = MD20B-230 NO EARTH REQUIRED N.B. Should the Satchwell AR Series 7 Actuator include a wired Auxiliary Switch then the following Accessory should also be wired on the Schneider Electric MD Actuator as follows :- MD – S1 One independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switch AR COMMON Wire Number S1 = MD-S1 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S1 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S1 N/C contact Wire Number S2 MD – S2 Two independent SPDT 1 mA…3(0.5) A, 250 V AC Auxiliary Switches AR COMMON Wire Number S1 = MD-S2 COMMON Wire Number S1 AR N/O contact Wire Number S3 = MD-S2 N/O contact Wire Number S3 AR N/C contact Wire Number S2 = MD-S2 N/C contact Wire Number S2 AR COMMON Wire Number S4 = MD-S2 COMMON Wire Number S4 AR N/O contact Wire Number S6 = MD-S2 N/O contact Wire Number S6 AR N/C contact Wire Number S5 = MD-S2 N/C contact Wire Number S5   Product Information. For details of AR Series 7 ARM ARX ARE please see here For details of AR Series 7602 and 7603 please see here. For details of the MD10 SR Damper Actuator please see here. For details of MD10A please see here For details of MD10B please see here For details of MD20A please see here For details of MD20B please see here For details of MD-S1 please see here For details of MD-S2 please see here

Issue Satchwell CD2401 Proportional Controller-Actuator requires replacement. Product Line Field Devices Environment Stand alone discreet Satchwell CD2401 Proportional Controller-Actuator Cause Obsolescence of Satchwell CD2401 Proportional Controller-Actuator Resolution Replace Satchwell CD2401 Proportional Controller-Actuator with Schneider Electric Satchwell CZT5305 Proportional Controller, compatible Temperature Sensor and MD Series Actuator and Linkage Kit. Replace Satchwell CD2401 Proportional Controller-Actuator with Schneider Electric Satchwell CZT5305 Proportional Controller. Details of the Schneider Electric Satchwell CZT 5305 Proportional Controller may be viewed here. Replacement of Temperature Sensor It should be noted that although the existing Satchwell Temperature Sensor associated with the CD2401 Proportional Controller–Actuator is obsolete, it is compatible with the CZT Proportional Controller and may be retained. Should it be decide to install a replacement Temperature Sensor however, then the following may be considered. Room Temperature Sensor STR600 series details of which appear here. Duct Temperature Sensor STD660 details of which appear here. Immersion Temperature Sensor STP660 details of which appear here. NB In order to utilize the existing Pocket a Pocket Adaptor DWA0001 will also be required. Pocket Adaptor DWA0001 details of which appear here. OR Surface mounting Temperature Sensor STC600 details of which appearhere. Replacement of Actuator. Whilst the existing Satchwell MB Valve Body may also be retained, a new Schneider Electric Actuator and Linkage Kit will need to be installed on the MB Valve Body in order to permit control from the CZT Proportional Controller. Details of the Schneider Electric MD10A-24 Actuator may be viewed here. Details of the Schneider Electric LMD/AR-MB Linkage Kit may be viewed here.

Issue Significant changes and improvements were introduced with firmware revision 11.2P, including a streamlined "Flash clear" procedure. For Ethernet NIMs with firmware revisions prior to 11.2P, the procedure was documented in Technical Bulletin 99-56 (see below). The procedure in bulletin 99-56 was a revision of the procedure in the original NIM Networking and Configuration Practices manual, F-25955, which is no longer available. The current version of the manual, F-25955-4, applies only to NIMs with firmware  revisions 11.2P and 11.2T. Environment Ethernet NIM for network 8000; GCM-ETH-001 with firmware revision prior to 11.2P. Cause "Flash clear" procedure was changed in firmware revision 11.2P Resolution Follow the "Flash clear" procedure per Technical Bulletin 99-56.

Issue Personnel are not deleting properly using a stand alone database in 1.82 and above Environment Continuum 1.82 Continuum 1.9x SQL Express 2005 (Stand Alone) Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause There is a different mechanism used to delete personnel in SQL Express than was used in previous versions of Stand Alone databases (MSDE). The SQL agent is no longer available in SQL Express so a combination of batch files, SQL queries and Microsoft scheduler are used to accomplish this task. Resolution Several things to check: Ensure all controllers are online (a controller offline can cause deletions to not happen) A personnel listview with the deletepending attribute indicates True A controller was not deleted No areas were deleted Expiration date is not greater than 2031 Check the access distribution view for any errors At times for permission issues not all the components for deletion are configured by the Cyberstation installation and it's necessary to troubleshoot those components. Click here for a Word document describing these components to help troubleshoot.

Issue DC1100 / DC1400 Optimiser / Compensator Controller switched contact output compatibility with existing Boiler / Pump / Control Valve Actuator control circuits. Environment Stand alone Optimiser / Compensator Controller CMC1801 CMC1802 CMC1803 CMC1826 CMC3803 CSMC3804 CSMC3805 DC1100 DC1400 Contacts Output Cause DC1100 / DC1400 Optimiser / Compensator Controller is to be connected to existing Boiler / Pump / Control Valve Actuator control circuits previously connected to Satchwell CMC or CSMC Optimiser / Compensator Controller. Resolution IMPORTANT NOTE Satchwell CMC / CSMC Controller output contacts are VOLT FREE. S-E Satchwell DC1100 / DC1400 Controller output contacts are LIVE MAINS VOLTAGE. It may therefore be necessary to install Relays between the DC1100 / DC1400 outputs and any Plant Control Circuits / Control System Devices under control. For example, where a 24v Valve Actuator was originally controlled via volt free contact outputs of a CMC / CSMC Controller then the Actuator may now need to be controlled via live mains voltage contact outputs of a DC1400 Controller. A 230v coil Relay will therefore need to be connected to the Valve Open contact output of the DC1400 Controller while another 230v coil Relay is connected to the Valve Close contact output of the DC1400 Controller. The 24v power to drive the Valve Actuator Open and the 24v power to drive the Valve Actuator Close should then be connected to the Valve Actuator via the contacts of the appropriate Relays. Should the 24v power source originally have been provided by the CMC / CSMC Controller and no other 24v power source is available on the existing installation then this may be remedied by the installation of a S-E TR 230/24v Transformer. N. B. Normally a Satchwell CMC or CSMC Controller would be replaced by a S-E Satchwell DC1400 Controller in order that existing Satchwell Sensors may be retained for connection to the DC1400 Controller. In the event that a Satchwell CMC or CSMC Controller should be replaced by a S-E Satchwell DC1100 Controller then any existing Satchwell Sensors will also need to be replaced. DC1100 Overview details appear here. DC1100 Wiring and Commissioning details appear here. DC1400 Overview details appear here. DC1400 Wiring and Commissioning details appear here. TR Transformer details appear here

Issue What is the bCX and NCII required bandwidth? 10Mb, 100Mb Network Connections, GSM Modems. Environment Continuum Ethernet level controllers: ACX57xx, Netcontroller II and bCX1 Cause IT Departments often ask for the required IP Network bandwidth for the CX and bCX controllers; as it is not listed on the datasheets. Is there a bandwidth calculator available? Resolution The Network usage of a bCX/ CX/ ACX controller will vary constantly depending on what is happening on the system at the time. It will be affected by user commends, Graphics, Plain English programming, Access events, reloading or re-flashing controllers and time triggered events. The 2nd generation controllers network connection supports a 10Mb half duplex or 100Mb full duplex auto sensing permanent connection. Note: Older 1st generation controllers (CX9200, CX9400, CX9900 series) only support 10Mb half duplex. So a corresponding up to 10Mb or 100Mb connection would be ideal. GSM Modem or other packet based communication networks are unlikely to be able to provide the continuous data throughput required by Continuum. In terms of bandwidth an absolute minimum of 1Mb in both directions is recommended but this will depend on the specific site requirements you have, for example if there is a requirement to update graphic or alarm values within a specific time then a 10Mb connection would be more appropriate. The following Bandwidth Calculator can be used to determine the % network usage on a 10Mb network connection. This was created specifically for typical Access Control projects, so for HVAC applications the following should also be considered: data logging, PE programs passing data, IP based X Drivers. Fill in the appropriate values in Column D for the system: Bandwidth Calculator.

Issue Modbus devices such as power meters require the monitoring of values that are held in a 64-bit unsigned integer data format.  I/A Series G3 Modbus proxy points cannot be configured to directly support the 64 bit register format. Environment I/A Series G3, Modbus, Modicon, Schneider Electric PowerLogic PM800 Series Power Meters Cause Modbus devices such as power meters require the monitoring of values that are held in a 64-bit unsigned integer data format.  I/A Series G3 Modbus proxy points cannot be configured to directly support the 64 bit register format. Resolution As a workaround, the Modbus proxy points can be configured to poll the register as four integers and convert or combine the four integers to a single unsigned 64-bit value.  NOTE: that all four registers will need to be polled in a single message.  The following are two examples that can be used to read and convert unsigned 64-bit values.  The first example converts a Modicon power value with data type UINT64.  The second example converts a Schneider Electric PowerLogic P800 Series Power Meter with data type MOD10. Example 1 (Modicon UINT64):  The memory map below indicates the Total KWh+ value is presented in an unsigned 64-bit data format (four Modbus integers) starting at physical address 0500h. Create four Modbus Client Numeric Points under the Modbus Async Device Points container. This can be done by copying four objects or by using the Modbus Client Point Manager. Configure the points to read the integers that represent the value required. For example, the Modicon address 301280 (0500h) would be configured as follows. NumericPoint1 > Data Address (Address Format Hex, Address 500, Reg Type Holding, Data Type Integer) NumericPoint2 > Data Address (Address Format Hex, Address 501, Reg Type Holding, Data Type Integer) NumericPoint3 > Data Address (Address Format Hex, Address 502, Reg Type Holding, Data Type Integer) NumericPoint4 > Data Address (Address Format Hex, Address 503, Reg Type Holding, Data Type Integer) The values will attempt to poll and still will most likely be in fault as the value must be read in the same message request. This is where a Device Poll Config Entry will be required to configure the data to be read in a single message. The Device Poll Config Entry can be configured using the Learn Optimum Device Poll Config or by manually adding a Device Poll Config Entry to the Device Poll Config container. For this example, the Device Poll Config Entry would be setup with the start address of Hex 500, Data Type Holding Register, Consecutive Points To Poll 4 and Read Group Size 1. The consecutive points to poll may can be adjusted to read multiple UINT64 registers depending upon the maximum number of registers allowed by the Modbus device. Otherwise additional Device Poll Config Entry objects can be added and configured. Converting or combining the values can be performed in a couple of ways. The first is by using standard math logic (see image below). The inputs are multiplied by the correct binary multiplier and added together. The constants to use for each object are as follows. Multiply = 65536.0 Multiply1 = 4294967296.0 Multiply2 = 281474976710656.0   The second method is to use a program object and connect the four integers to the inputs. The same calculation as previous method is performed within the program.  The ModbusIntegersToUINT64 program object can be copied into a station database. Example 2 (PowerLogic P800 Series Power Meter MOD10):  The memory map below indicates the Energy (Real Out) value is presented in an unsigned 64-bit data format (four Modbus integers) starting at physical address 1708. Create four Modbus Client Numeric Points under the Modbus Async Device Points container. This can be done by copying four objects or by using the Modbus Client Point Manager. Configure the points to read the integers that represent the value required. For example, the address 1708 would be configured as follows. NumericPoint1 > Data Address (Address Format Decimal, Address 1708, Reg Type Holding, Data Type Integer) NumericPoint2 > Data Address (Address Format Decimal, Address 1709, Reg Type Holding, Data Type Integer) NumericPoint3 > Data Address (Address Format Decimal, Address 1710, Reg Type Holding, Data Type Integer) NumericPoint4 > Data Address (Address Format Decimal, Address 1711, Reg Type Holding, Data Type Integer) The values will attempt to poll and still will most likely be in fault as the value must be read in the same message request. This is where a Device Poll Config Entry will be required to configure the data to be read in a single message. The Device Poll Config Entry can be configured using the Learn Optimum Device Poll Config or by manually adding a Device Poll Config Entry to the Device Poll Config container. For this example, the Device Poll Config Entry would be setup with the start address of Decimal 1708, Data Type Holding Register, Consecutive Points To Poll 4 and Read Group Size 1. The consecutive points to poll may can be adjusted to read multiple MOD10 registers depending upon the maximum number of registers allowed by the Modbus device. Otherwise additional Device Poll Config Entry objects can be added and configured. Converting or combining the values can be performed in a couple of ways. The first is by using standard math logic (see image below). The inputs are multiplied by the correct binary multiplier and added together. The constants to use for each object are as follows. Multiply = 10000.0 Multiply1 = 100000000.0 Multiply2 = 1000000000000.0 The second method is to use a program object and connect the four integers to the inputs. The same calculation as previous method is performed within the program.  The ModbusIntegersToMOD10 program object can be copied into a station database.

Issue Checking operation of CSC. Product Line Field Devices Environment CSC5252 CSC5352 Cause The operation of the CSC compensator explanation. Resolution The operation of a compensator is to adjust the system flow temperature, in relation to changes in the outside air temperature. The system flow temperature can be further adjusted by the addition of a room temperature sensor, which will provide room influence. The CSC 5252/5352 controller is programmed with a complete set of "Default" settings, these settings will allow the controller to operate as soon as its powered up. Although the controller has a complete range of adjustable settings, accessed through the "Fine Tune Mode", for a basic installation the "Quick Set Mode" can be used. The screen shot below explains how to enter the Quick Set Mode and the settings available. Controller data sheet Controller User guide   Compensated Flow Temperature Set-point: The compensated flow temperature set-point is automatically adjusted based on a ratio for set-point adjustments against the outside temperature changes. A consistent ratio across the entire outside temperature range, may not provide suitable control. For example: with radiator type systems, radiators are less efficient at lower water flow temperatures and need to be provided with a higher temperature to compensate for this initially. The “Set compensator ratio 1”and the “Set Ratio 2” settings provide the ratio of the change to the flow temperature set-point for changes in the outside air temperature, the ratio used is based on the “Set Change-over Value”, with the compensated slope starting from the “Set Flow Origin”. The “Set Flow Temperature Set-up Value” and “Set Night Set Back Value” provide a constant adjustment of the flow temperature set-point to a given building control requirement. The default settings would give a resultant flow temperature as shown follows:     The CSC5352 Calculator presents these settings in a graphical and listed format, making it easier to visually confirm the effects any changes to these settings would make.