Building Automation Knowledge Base

Issue Upgrading a Xenta 102-AX to v 2.16 Product Line TAC Vista Environment Xenta 102-AX LonMaker NL220 Cause Firmware upgrade Resolution The following instructions will describe the firmware upgrade process for three different LNS environments: LonMaker 3.1, LonMaker Turbo 3.2, and NL220. The NXE, APB, and XIF files for upgrading the 102-AX are now available on The Exchange Download Center. Preparation   Always remember to make backups before beginning this process. Record the Neuron IDs for all Xenta 102-AXs that will be receiving the upgrade. If you do not record the Neuron IDs ahead of time, you will have to press the service pin on every controller being upgraded. A list of all Neuron IDs can be obtained in one of the following ways: Through TAC Vista Server Open TAC Vista Server Click on Reports > LonWorks Networks, Survey   This process will open a .txt document which lists all controller names and Neuron IDs in the Vista database. Through Echelon LNS Utilities Navigate to Start > Programs > Echelon LNS Utilities > LNS Report Generator Select the LNS Network   Hit Generate   This will generate a .csv file in the designated location with controller names and Neuron IDs. This can be viewed using Microsoft Excel. Through NL220 Choose either Subsystem or Channel view Depending on the view, right click either on the Subsystem or the Channel Select Print > Print list of nodes Select Export   Choose desired file format Hit OK If changes have been made to the configurations of the 102-AXs through any means other than the LNS plug-in (I/STAT, M/STAT, Vista Workstation) these parameters will first need to be uploaded to the LNS database. If this step is skipped, then any configurations made this way will be erased during the upgrade. In LonMaker 3.1 Right click on a device Select Resynch CPs... Repeat for each 102-AX In LonMaker Turbo 3.2 Right click on a device Select Commissioning > Resynch CPs... Repeat for each 102-AX In NL220 Right click on a device Select Copy configuration values in memory Repeat for each 102-AX Download the NXE and XIF files for version 2.16 from The Exchange Download Center. Please note that during the upgrade process, the 102-AX will not function properly. In a multiple LIP or router database the dummy database can be created on a notebook PC. This allows for a local FT10 connection to the Lon network after the router. The existing network topology is not needed on the dummy database in this case.   Performing the Upgrade in LonMaker 3.1 It is not possible to upgrade a 102-AX in an existing database. To upgrade a 102-AX, a temporary "dummy" database must be created. Launch LonMaker Select New Network Set the new network to be Online and Network Attached. Do not register any plug-ins. Add a generic device *Note: The network has to represent the topology of the physical connection to the FT-10 channel Check Commission Device box, hit Next.   Load XIF. Browse to the downloaded v2.16 XIF file (not the standard XIF, but the v2.16 downloaded from Exchange Online). Hit Next.   Specify channel. Hit Next.   Default Properties selections are okay. Hit Next.   Set the Neuron ID. If you recorded them in a report previously, manually enter the data here. If you planned to service pin the controller, select Service Pin. You will be prompted at the end of the process to service pin the device.   Check the box for Load Application Image. Browse to the v2.16 NXE downloaded from Exchange Online. Hit Next.   Set the desired state to Online. Set the Source of Configuration Property Values to Current values in device. This is an important step. If you do not set to current values in device, your previous configuration parameters will be erased. Press Finish to begin the download.   Allow approximately 50 seconds for the application image to finish loading. While you wait you will see this window.   To upgrade the next 102-AX, right click on the device and select Replace. Repeat these steps for each 102-AX in the system. Performing the Upgrade in LonMaker Turbo 3.2 It is not possible to upgrade a 102-AX in an existing database. To upgrade a 102-AX, a temporary "dummy" database must be created. Launch LonMaker Select New Network Set the new network to be Online and Network Attached. Do not register any plug-ins. Add a generic device Check Commission Device box, specify channel, hit Next.   Load XIF. Browse to the downloaded v2.16 XIF file (not the standard XIF, but the v2.16 downloaded from Exchange Online). Hit Next.   Default Properties selections are okay. Hit Next.   Set the Neuron ID. If you recorded them in a report previously, manually enter the data here. If you planned to service pin the controller, select Service Pin. You will be prompted at the end of the process to service pin the device.   Check the boxes for "Load application image" and "Update firmware in device to match application image." Browse to the v2.16 NXE downloaded from Exchange Online. Hit Next.   Set the desired state to Online. Set the Source of Configuration Property (CP) Values to "Application image file." Set the Device Specific CPs to "Preserve device values." This is an important step. If you do not preserve device values, your previous configuration parameters will be erased. Press Finish to begin the download.   Allow approximately 50 seconds for the application image to finish loading. While you wait you will see this window.   To upgrade the next 102-AX, right click on the device and select Commissioning > Replace. Repeat these steps for each 102-AX in the system. Performing the Upgrade in NL220 It is not possible to upgrade a 102-AX in an existing database. To upgrade a 102-AX, a temporary "dummy" database must be created. Launch NL220 Log in and create a New project. Do not register any plug-ins. In SmartChannel, set the new network to be Attached. Under the Device Templates tab, right-click and select New Device Template. Create the New Device Template from interface file. Browse to the downloaded v2.16 XIF file (not the standard XIF, but the v2.16 downloaded from Exchange Online). Hit OK.   On the Channel tab, right-click and select New node on Name the device and choose Create node from a device template. Select the newly created 2.16 device template. Uncheck Set all configurations to manufacturer's default.   Right-click on the new device and select Install (network > commission in newer versions). Set the Neuron ID. If you recorded them in a report previously, manually enter the data here. If you are going to service pin the controller, do it now.   Right-click the device and select Download program. Choose Upgrade system version. You will receive a warning stating that upgrading the system image can leave the device in a bad state and break communication. You should only use this option if you are sure of what you are doing. Confirm, Yes, you want to continue. Configuration download should be set to Keep current configuration on node.     Allow approximately 50 seconds for the application image to finish loading. To upgrade the next 102-AX, right click on the device and select Network > Replace. Repeat these steps for each 102-AX in the system.

Issue Unable to connect to a system that is using Server/Client Configuration. After promoting a stand alone PC to a remote client and clicking on the connect button, an error "No Entries in Database" comes up and the user cannot connect to any of the controllers on the system. After a restart of PC and an attempt to connect to the I/NET System, an error "No entries in database" is seen. Product Line TAC INET Environment I/NET Seven Windows 7, Windows XP, Windows Vista, Windows 10 Cause Some of the possible causes : After promoting a stand alone PC to a remote client the Reference Host information of both the server and the client must be updated with the IP addresses of each other. Bad communication or bad controller that is connecting the C-LAN to the Xenta 527 In some instances when running the I/NET IO Server as a service and after a restart of the PC hardware running a Windows 10 Operating System, it is has been seen to produce this "No entries in database" error.  At this stage the reason is currently unknown but the connection to the Xenta 527 is not made and the IO Server service needs to be restarted. Resolution Open I/O Server Hit the Modify button In the Reference Host Column, add the IP address of the server Repeat steps 1-3 on the server, adding the IP address of the remote client. Note: Should the Xenta 527 still not communicate to the controller: Verify that the C-LAN wire is connected properly There is communications between the controllers and the Xenta 527 If not, unplug the C-Lan connector, from all the controllers and bring them online one at a time to determine which one could be bad. Replace possible bad controller and the system should come online again. To correct the issue after a PC hardware restart, two options are available Restart the I/O Server service Change the run mode of the I/O Server to an application.  See Running I/NET Seven as a service on Windows for further information on options on how to achieve this. 

Issue Xenta Server (527/701/721/913) graphics, time schedules not working on the webpage. Xenta Server (511/555/527/913) can not create Menta object. Xenta Server (701 and 913) does not work with Xenta programmable controllers (Xenta 280/300/401). Which Xenta Server takes I/O modules and how many? Which Xenta Server works with I/NET, MicroNet, or ModBus. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server version after 5.1.5 (5.1.5 included) TAC XBuilder version after 5.1.5 (5.1.5 included) Vista, I/NET, LON, MicroNet, ModBus Cause Different Xenta Servers have different features. Using a different Xenta Server may result in missing features. Resolution Xenta Server 5.1.5 Major Features. Product LON I/NET MicroNet BACNet ModBus Web * I/O Modules Xenta Supp. ** Menta Supp. Xenta 511 X       X C   X   Xenta 527 X X     X C   X   Xenta 527-NPR   X       S       Xenta 555 X   X   X C   X   Xenta701 X       X ST 10   X Xenta 711 X       X C 10 X X Xenta 721 X       X ST 20 X X Xenta 731 X X X   X C 20 X X Xenta 913 *** X X   X X S       * S – Service. Means that the web interface is automatically generated in XBuilder and only contains values in value pages and is aimed for commissioning and service. NOTE: For Xenta 701 and Xenta 721, it is not possible to have any end-user web content, such as graphics, trend viewers, alarm viewers or value pages.  Xbuilder allows the user adding a Value Page in the Xbuilder project. It will not be displayed on the webpage though. T – Time Object Pages. Means that Time Object Pages can be added to the XBuilder project. These will only appear for Xenta Servers 701/721 in TAC Vista Workstation and can be used to control Xenta Server time charts from Vista Workstation C – Custom. Means that the web interface is totally configurable in XBuilder; navigation and all features for creating a full end-user web are available. ** Xenta Supp. – Xenta 280/300/401 support. Means that Xenta 280/300/401 can be installed on the LonWorks network beneath a Xenta Server and are fully supported by both the Xenta Server and TAC Vista on top of Xenta Server. *** The Xenta 913 also supports BacNet, M-Bus, and C-Bus. For Xenta Server 5.1.4 major features, please read Xenta Server 5.1.4 Major Features (Xenta 5XX/7XX/913 Capabilities with Graphics, Web Applications, and Migration to other systems).

Issue Is it possible to rename an ES after an AS has been created? Product Line EcoStruxure Building Operation Environment StruxureWare/EcoStruxure Building Operation 1.9 and lower Enterprise Server Automation Server Cause Not possible to rename the Enterprise Server or Automation Servers once attached as a multi-server system Resolution It is not possible in the earlier revisions 1.9 and lower to rename an ES or an AS once created under an ES. From EcoStruxure 2.0 and above this is possible;  Refer to WebHelp for additional details: Server Rename

Issue AMT has stopped receiving data AMT is not receiving data A new link added to a system, is not sending messages or transactions Product Line TAC INET Environment I/NET Cause AMT can stop receiving data for several reasons. Connection between Remote Client with I/O and SQL is broken AMT is Paused Communication to the device is not functioning AMT Masking is not set correctly Host Masking is not set correctly Point Masking is not set correctly Door Editor Masking is not Set The software has frozen I/NET has reached its maximum online event size and FIFO is not working (very rare) Other Resolution Connection between Remote Client with I/O and SQL PC is broken. Check that no other I/NET PCs are connected to the SQL database. This may include an instance of I/NET installed on the SQL PC Restart the I/Net Remote Client with I/O to re-establish the connection with the SQL Server Wait several minutes for data to update. If this fails, ensure that there are no firewalls or communication failures between the 2 PCs. If using I/NET v2.42 there have been instances where this version does not pass events to the SQL Server.  This is fixed in v2.43 or greater. AMT is paused Right-click anywhere in an open Alarm/Transaction/Message window The bottom choice is either "Pause" or "Resume" If it is "Resume" click on that and AMT function will be restored Communication to the device is not functioning Minimize AMT and open I/NET Connect to the controller Select Summary>Controller If you see values and get no error messages this is not the issue If you cannot see values or get a "No Entries in Database" error, determine why communication is down AMT Masking is not set correctly In AMT Select Edit>Configuration Note the current settings, take a screen shot and save it if possible For troubleshooting purposes, select all of the check boxes under "Messages/Alarm" Restart the I/O server In I/NET trigger a point to go into alarm or send a message Check AMT for successful delivery Host Masking is not set correctly (TCP/IP only) Right-click on the I/O server and select Configure Modify the Active Profile On the bottom of the screen click on "Host Masks" Select any NPR or 527 Note the current settings Check all boxes Click okay Repeat 4-7 for all NPR or 527 devices Restart the I/O server In I/NET trigger a point to go into alarm or send a message Check AMT for successful delivery Point Masking not set correctly Connect to a controller that you expect to receive messages from Select Edit>Controller>Resident I/O Modify a point you expect to receive messages from Ensure that the appropriate Mask bits are set Ensure that there is a priority set for both Messages and Alarms Click okay Go to the controller summary and attempt to trigger a message or alarm Door Editor Masking is not Set Connect to a controller that you expect to receive messages from Select Edit>Controller>Doors Modify a door you expect to receive messages from Ensure that the appropriate Mask bits are set Ensure that there is a priority set for both Transactions and Alarms Click okay Attempt to trigger a message or alarm The software has frozen Restart the I/O server If this does not work restart the computer I/NET has reached its maximum online event size and FIFO is not working (very rare) Right Click on the I/O server and select Archive Configuration Enable Archiving if it is not enabled Increase the size of the maximum online events Restart the I/O server Trigger an Alarm or Event in I/NET Verify AMT  Other troubleshooting steps Force a Lan to reconfigure by changing the station address of the Xenta 527, then changing it back If AMT still will not function Repeat the above processes using an Event window with no filter.  It is possible messages are being received, just not to the open Window Close all open AMT windows Select System>New>Event Window Click Okay This opens an Event Window which will display all data coming into AMT Repeat the above troubleshooting processes The Controller LAN is having communication issues Cycle power on one of the Controllers on the Controller Lan to force a Lan Reconfigure Other solutions for this issue have been documented in these articles: No door transactions coming into AMT: Quick Poll is not enabled.  Typically applies to older sites. Transactions not Updating AMT Window using direct connect: For Direct Connect systems No Transactions or controller Events in AMT: Reliable Tap AMT messages stop after re-installing I/NET: Applies to recently upgraded sites.

Issue How to order more NL credits in order to commission more devices. If the following message displays when opening a NL220 database, then more credits will need to be purchased soon. " BEWARE: less than 20 credits are available on this machine. If you need to install more than 20 device please order the amount of needed credits as soon as possible. Do you want to ask for new credits?" Product Line TAC IA Series, TAC Vista Environment NL220 LNS Cause There are two types of credits: Product specific credits like LonMaker and NL credits LNS credits   Echelon LNS LNS credits are assigned to the PC and when they reach zero, the LNS Server license goes into deficit mode. After 14 days the deficit mode will expire, at which time no LNS tools will be able to be used on that PC. To reverse the lockout, enough LNS credits must be ordered to cover the deficit and any additional nodes that need to be commissioned. Backing up, sharing, and restoring LNS databases can sometimes corrupt these LNS credits, which then prohibits you from launching any LNS plug-ins. For more help with corrupt LNS credits see Corrupted LNS Credits. Echelon LonMaker LonMaker credits are assigned to the PC. Both LNS and LonMaker credits are required, however when commissioning devices in LonMaker, LonMaker credits are consumed but LNS credits are not. Even though LNS credits are not consumed in LonMaker they are still necessary because certain LNS applications (i.e. TAC Vista System Plug-in) require them to operate. Newron NL220 Each time a node is commissioned in NL220 it requires a NL credit and a LNS credit. NL credits are assigned to the NL220 dongle and can be used on other PCs in "MOVED" mode. LNS credits are also necessary in NL220 to operate certain LNS applications such as the TAC Vista System Plug-in.   To order more Echelon LNS credits see Ordering more LNS credits. To order more Echelon LonMaker credits see Ordering more Echelon LonMaker credits. Resolution When working in NL220, it is wise to maintain a higher level of LNS credits than NL credits to help avoid locking out the LNS server license. To check the amount of NL credits remaining go to Start > All Programs > NL Suite > NLCreditsGenerator and look for Remaining NLCredits. The number of NL credits remaining can also be found at the bottom of the NL220 LonWorks Manager window with a project open. To check the amount of LNS credits remaining on a PC go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard and look for Credits Available. The number of LNS credits remaining can also be found at the bottom of the NL220 LonWorks Manager window with a project open.   To order more NL220 credits: Open the NLCreditsGenerator Utility that is installed with NL220. Go to Start > All Programs > NL Suite > NLCreditsGenerator > NLCreditsGenerator Utility. Enter the number of NL220 credits to be added  in the request area. Click Next. Click "Yes, this PC will be used for commissioning" Enter your name and contact details. Select "Copy to clipboard". Then either paste the information into notepad or in an email. Send the NL credit request to your local Schneider Electric Buildings Business order department  (NLCredits@buildings.schneider-electric.com). When you order has been processed by the local Schneider Electric Buildings Business order department you will receive an upgrade key. Open the NLCreditsGenerator Utility again. Go to Start > All Programs > NL Suite > NLCreditsGenerator > NLCreditsGenerator Utility. Click the Next button. Enter the key into the "Upgrade key" field of the credits generator. A message indicating you credits were added is then displayed.   Note: Once the request key has been generated, DO NOT commission or decommission any devices with the dongle until the upgrade key has been applied to the dongle. If devices are commissioned before then, the upgrade key will no longer be valid.

Issue The IC-GEN OPC server does not communicate with a third party OPC client across Ethernet. Environment Sigma IC-GEN OPC (all versions) Cause The IC-GEN OPC only supports a local IP address configured in the gateway.txt file. Resolution The IC-GEN OPC server can only be connected to third party OPC clients located on the same PC. For more information see Release Note, click here An example using an EIB I/O server, click here

Issue What is the required version of .NET framework and ASP.NET for TAC Vista software? Product Line TAC Vista Environment Vista 4.x.x Vista WebApps 4.x.x Vista 5.x.x Vista WebApps 5.x.x Cause Microsoft .NET framework is a core technology used by Vista software. ASP.NET is used by Vista Webapps for web presentation through Internet Information Services. With the many versions of .NET framework available from Microsoft it can be unclear which to install or ensure is available for Vista software. A new release of .NET framework is not necessarily supported by TAC Vista software until design changes have occurred in subsequent releases. Resolution Use this compatibility chart to ensure the proper version of .NET framework and ASP.net are installed: Vista Version .NET Framework Version ASP.NET Version 4.3.0 1.1 sp1 1.1 4.3.1 1.1 sp1 1.1 4.4.0 1.1 sp1 1.1 4.4.1 1.1 sp1 1.1 4.4.2 1.1 sp1 1.1 4.5.0 1.1 sp1 1.1 5.0.0 2.0 2.0 5.0.1 2.0 2.0 5.0.2 2.0 2.0 5.0.3 2.0 2.0  5.1.0 3.0 2.0 5.1.1 3.0 2.0  5.1.2 3.0 2.0 5.1.3 3.0 2.0 5.1.4 3.0 2.0 5.1.5 4.0 4.0 Note: A higher version of installation package might be present on the computer. To confirm the presence of the lower versions also being available review the C:\Windows\Microsoft.NET\Framework\ directory. The Microsoft.NET framework is available for install from Microsoft's website (http://www.microsoft.com/net/)

Issue Use of the Plain English programming environment and general Plain English programming is covered in the Training courses, what other techniques can be used to debug a program. Product Line Andover Continuum Environment Plain English Integrated Development Environment Cause Often additional techniques are required to debug Plain English, especially when attempting to analyze, modify or fault find other peoples code. Resolution Some techniques you can use for debugging your program and isolate problems are: Add in additional line labels to the program to isolate where the program is disabling or failing, if it disables you will be able to see the "CurrentLine" it has failed on and therefore know which line of code is causing the problem. Even if a program does not disable you can use the "Stop" keyword in the program it will act as a break in the code and you can look at the values of the various variables, that should tell you what value could be at 0. Use the Watch window to show the values of the various objects, when used with the above 2 techniques it allows you to accurately trace a program flow. Temporarily create local variables as actual points and comment them out from the assignment at the top of the program, this allows you to use the Watch window to see the points values. Revert them back to local objects when debugging is complete. Ensure none of the Program size limitations as defined in Plain English program limitations on number of characters in program and line labels are exceeded.    

Issue InfinityInput configured as counter does not count any pulses. Environment i2 devices B3 devices IOU modules Cause Here are two common reasons why the counter input may not be counting as expected: 1. No accumulation logic used with input. 2. Signal from the count source does not conform to specifications. Resolution 1. No accumulator logic used with input. The value of a counter input is reset to zero at every scan, in order to maintain the count value an accumulation strategy must be used, this can be accomplished via a conversion at the input or by using a PE program to accumulate the count in an InfinityNumeric object. a) Enter the following conversion in the counter input’s conversion field: Value + ElecValue Or b) Use the following logic in a PE program CountAccumulator = CountAccumulator + WaterMeterCount  (Where CountAccumulator is an InfinityNumeric object and WaterMeterCount is the name of the counter input)   2. The signal from the count source (Water meter, Power meter etc) does not have the minimum pulse width required by the input. For example, Infinet 2 devices (i.e. i2687) only support counter signal with a maximum frequency of 4 hertz and a minimum pulse width of 125 milliseconds. The DI8 IOU module has 2 channels that support counts of up to 10Khz with a pulse width as short as 50 microseconds. XPUi modules support counter inputs with a frequency up to 140 Hz and a minimum pulse width of 3.5 milliseconds. Refer to the manual for your count source (Meter) and verify the signal generated by it complies with the requirements of the Continuum hardware. For more information see the attached Infinity Technical Journal article. It describes several ways to reset the counter.   Note: Some meters will put out a pulse with a voltage equal to the supply voltage. In this case add a relay so the controller sees a dry contact per pulse.    

Issue Control HVAC or especially lighting based on the sunrise and sunset times for a given location on a given date, even though this functionality does not exist in Vista like it does in I/NET. Environment Menta Cause Menta/Vista time schedules have no built-in sunrise/sunset capability.  If this is required, it will need to be programmed into a Menta file. Resolution The attached Menta Macro calculates the sunrise and sunset for a given location. Click the picture to download.       Inputs - Menta Simple Blocks Month Date Hour Minute Configurable Parameters Year = Current year.  As Menta has no "Year" block, it must be calculated in the controller and should be set initially for the current year. DST = Does this location participate in Daylight Savings Time?  1=Yes, 0=No. TimeZone = Location's offset in hours from GMT Latitude = Location's latitude in degrees. North is a positive value, south is a negative value. Longitude = Location's longitude in degrees. West is a positive value, east is a negative value. Outputs - Available Data Current minutes past midnight Sunset minutes past midnight Sunset hour Sunset minutes Sunrise minutes past midnight Sunrise hour Sunrise minutes Output integer represents minutes until next transition.  Mimics a Menta time schedule.  Positive values count down minutes until sunrise.  Negative values count down minutes until sunset.

Issue Some issues which this article covers are: What rules or recommendations should be used with Indirect and Global Points? Why might a global point not change? Attempting to alter a global AO/DO points' value/state, by "Point Control" without "Manual Mode" being used, and the change does not take place. (Referred to as Global Output Retentive Feedback.) What scan rates should be used for global / indirect points? Product Line TAC INET Environment I/NET Software Cause Often within a system, a point's status or value within one controller has to be shared or used in other controllers connected to the system. An example could be an outside air temperature sensor connected to a controller. The value of the outside air temperature in that controller can be transmitted across the I/NET network to be used in algorithms in the other controllers. The I/NET software and firmware provides the mechanism to transmit and receive point data system wide. The outside air temperature point in this example would be called a "global point." The receiving points within the other controllers that reference and thereby mimic the global point's temperature value are called "indirect points." Resolution Each controller is capable of a total of 128 global and indirect points. Global points are used to share information from one controller to another. If a point is not a global point, the state or value of that point is available only to other points in the same controller. If a point is specified as global, you may use it to control an indirect point in another controller. Any internal or external point may be designated as a global point. When a point is defined as global, a corresponding indirect point must be set up in the additional controller(s) to receive the global point's data. The global point must be designated with the appropriate globalisation level. There are four (4) different levels of globalisation, as shown below: Local: This point provides information only to this controller. A global setting of "Local" indicates that this point is not a global point. LAN: This point may provide information to an indirect point in any device connected to this controller LAN. Link: This point may provide information to an indirect point in any device connected to this controller's Host LAN. This setting WILL NOT send global data across links headed by NetPlus Routers. System: This point may provide information to an indirect point in any device connected to the I/NET system including ETHERNET. This setting WILL send global data across links headed by NetPlus Routers. Global points "broadcast" or send their state/value to corresponding indirect points. The frequency of the broadcast depends on the point type. All global point types broadcast under the following conditions: The controller has been restarted, either by a power restore, the controller's red reset button has been pushed or the database, DCU0000.sav file, has been "Restored." A global point has been changed from "Automatic" to "Manual" or from "Manual" to "Automatic." This does not apply to the Test Mode. A global point changing to or recovering from the "old data" state due to either a communications failure, or an analogue input point falling outside or re-entering its sensor limits (defined within the 'Resident Points' editor). Global analogue points (AI, AO, GI, GO) broadcast whenever their value changes through a range greater than the specified "Broadcast change counts" parameter (defined within the 'Resident Points' editor). Global discrete points (DI, DA, DO, DM, DC) broadcast whenever their state changes. Global pulsed input points (PI) broadcast whenever their "Scans between broadcasts" parameter is exceeded (defined within the 'Resident Points' editor). When requested to by the associated indirect point. Indirect points "receive" their state/value from their corresponding global points. Indirect points must reside in a different controller from the global point, and they act as receptors for the value or status information broadcast from the global point. When entering an indirect point, you must specify the name or address of the associated global point. The frequency of the update from the global points depends on the following. Their associated global point broadcasting its status or value. In addition, an indirect point can request an update, at the indirect points scan rate, from their associated global point. This happens when: The indirect point is first entered. When the indirect point's controller is restored or reset (power restore, station restore or the red reset button is pressed). Whenever the local control LAN reconfigures. Whenever an AO or DO indirect point is put into "Manual Mode" or back into "Automatic Mode." When the indirect point has not seen a status/value change from its associated global point within 2 times the indirect point's scan interval it request an update from its associated global point. It then reports the update on its third scan interval. If the indirect point is unable to be updated from its global point (i.e. no communications) then the indirect point will report its last valid updated value/state and will flag the value/state as "Old Data." Direction of Point Data's Flow INPUT POINTS (AI, GI, DI and DA): The data flow is from the global input point broadcasting to the associated indirect point only. The flow is "one way" only, that is to say, if the associated indirect point should alter the state or value is not broadcast to their corresponding global point. GLOBAL INPUT --------------> LAN -------------> INDIRECT INPUT OUTPUT POINTS (AO, GO and DO): All output points (both global and indirect) broadcast their state or value changes to the other associated point(s). The flow is "two way," that is to say, a change to either the global or the associated indirect point will change their opposing point's value accordingly. GLOBAL OUTPUT <--------------> LAN <----------------> INDIRECT OUTPUT Click Here to view some recommendations / rules for Global and Indirect Points as well to view this complete article as one document.

Issue Satchwell CZU Mk2 Zonemaster Controller requires replacement. Product Line Field Devices Environment Stand alone Fan Coil Unit Temperature Controller. Satchwell CZU Mk 2 Zonemaster Controller. CZU 2201 CZU 2202 CZU 2203 Cause Obsolescence of Satchwell CZU Mk 2 Zonemaster Controller. Resolution Replacement of Satchwell CZU Mk 2 Zonemaster Controller with S-E Satchwell CZU Mk 4 Zonemaster Controller. The CZU 4201 may be used to replace the following CZU Mk 2 Controllers :- CZU 2201, CZU 2202, CZU 2203 N. B. CZU 2201 Controllers provided an additional -9 to +9 V d.c. output enabling connection to peripherals such as the Satchwell NSU 1401 Night Set-back Override Unit, TSU 1402 Two Step Auxiliary Unit and SSU 1403 Signal Selector Unit. CZU 2202 and CZU 2203 Controllers provided an additional -0.5 to +9 or -9 to +0.5 V d.c. output enabling connection to the Satchwell NSU 1401 Night Set-back Override Unit.  Additional outputs are not provided on the CZU 4201 Controller and in those applications where these are required then it will be necessary to consider an alternative Controller to the CZU 4201. Details of the CZU 4201 may be viewed here. A remote Satchwell Adjustable Room Temperature Sensor such as the DRT 3451, or a remote Satchwell Duct Temperature Sensor from the DDU range of Sensors may have been installed and connected to the Controller. Any existing remote Satchwell Temperature Sensors may be retained for connection to the CZU 4201. Should the remote Satchwell Adjustable Room Temperature Sensor require replacement then this may be replaced by an S E STR 612 Adjustable Room Temperature Sensor. Details of the STR 612 may be viewed here. Should the remote Satchwell Duct Temperature Sensor require replacement then this may be replaced by an S E STD 670 Duct Temperature Sensor. Details of the STD 670 may be viewed here

Issue Double clicking the BACnetNetwork used to open the BACnet Device Manager now it opens a BCP Device Manager that looks just like the BACnet Device Manager?  What is the BCP Device Manager? Environment I/A Series (Niagara) G3 Cause Installing Distech software to support their devices will result in the BCP Device Manager being installed for the BACnetNetwork. Resolution This is not an issue, just be sure to select the correct Device Manager for the devices you plan to work with.

Issue Need to purchase and replace the battery for the IAC-TS and IAC-600. Product Line Satchwell MicroNet Environment IAC-600 IAC-TS Cause The battery has failed and requires replacement. Resolution The battery is a lithium crystal SNAPHAT M4T28-BR12SH1 These are available from RS Components. The RS Components stock number is 189-1239. Manufacturer name: STMicroelectronics Manufacturer's part number: M4T28-BR12SH1 Specifications Category Detachable Lithium Power Source Maximum Operating Temperature 70°C Minimum Operating Temperature 0°C Mounting Through Hole Pin Count 4 Product Height 8mm Product Length 21.84mm Product Width 18.03mm Supplier Package SNAPHAT   Documentation M4T28-BR12SH M4T32-BR12SH TIMEKEEPER SNAPHAT (battery and crystal) Data Sheet.pdf Statement of conformity.pdf

Issue Resistance readings Environment Sensor Resistance Chart Type T Cause Resistance Resolution SENSOR CHARACTERISTICS   DRT DOT   DD 1401 DW 1202   DW 1204 DWS 1202   DO 2202 -40 to+40'c     DDT DWT   DR 2253 DWS 1301                 DST DOS                                                 Sontay Type SAT 1   Sontay Type SAT 2   Sontay Type SAT 3   Sontay Type SAT 4                               °C Ohms   °C Ohms   °C Ohms   °C Ohms                               -40 9711   0 2094   20 2708   -40 2317     -35 9604   1 2079   25 2592   -35 2246     -30 9465   2 2063   30 2474   -30 2163     -25 9288   3 2046   35 2346   -25 2067     -20 9067   4 2027   40 2216   -20 1962     -15 8796   5 2010   45 2086   -15 1849     -10 8472   6 1992   50 1950   -10 1733     -5 8093   7 1973   55 1818   -5 1617     0 7661   8 1953   56 1792   0 1504     5 7182   9 1934   57 1766   5 1397     10 6667   10 1911   58 1741   10 1298     15 6126   11 1892   59 1718   15 1208     20 5573   12 1872   60 1694   20 1128     25 5025   13 1851   61 1669   25 1057     30 4492   14 1830   62 1646   30 996     35 3987   15 1809   63 1622   35 942     40 3518   16 1787   64 1600   40 897     45 3089   17 1764   65 1578           50 2702   18 1740   66 1553           55 2358   19 1716   67 1530           60 2056   20 1690   68 1508           65 1792   21 1667   69 1484           70 1563   22 1644   70 1461           75 1364   23 1621   71 1439           80 1193   24 1596   72 1417           85 1047   25 1574   73 1396           90 921   26 1549   74 1375           95 815   27 1524   75 1353           100 722   28 1500   76 1333           105 643   29 1476   77 1312           110 575   30 1452   78 1293           115 517   31 1430   79 1276           120 466   32 1406   80 1258           125 423   33 1383   81 1240           130 386   34 1359   82 1222           135 353   35 1336   83 1205           140 324   36 1312   84 1188           145 300   37 1289   85 1171           150 278   38 1267   86 1154                 39 1243   87 1138                 40 1219   88 1122                 41 1198   89 1107                 42 1176   90 1089                 43 1155   91 1075                 44 1134   92 1061                 45 1113   93 1047                 46 1092   94 1033                 47 1072   95 1020                 48 1052   96 1004                 49 1033   97 991                 50 1013   98 978                       99 964                       100 950                                   Click here to download a pdf with this information.

Issue Access Control power supplies in UK are not available globally. Product Line Andover Continuum Environment Continuum ACX57 CX9702 PSU Power supply Continuum enclosures Cause Power supplies for access control systems (for powering of door locks/maglocks etc) should be purchased locally. Resolution All of the globally available enclosures are detailed in the Enclosure Family Datasheet. This includes ones suitable for Netcontrollers, ACX's, bCX's, i2 and VAV controllers. Power supplies for access control systems (for powering of door locks/maglocks etc) should be purchased locally to suit the site applications. Product Support Services does not keep records of the equipment that may have been purchased locally. e.g. in the UK a company called Dantech is used for Enclosures and power supplies, please contact them directly if PSU connection details are required. Dantech electronic engineering 3 Galliford Road Industrial Estate Heybridge Maldon Essex CM9 4XD Tel: +44(0)1621856850 NOTE: The Dantech PSUs often include FR contacts (Fire Relay) that need to be powered by 12Vdc to enable the supply.

Issue EL100DatabaseSetup.exe fails to execute correctly and will not build the EasyLobby database on the SQL server   Product Line Andover Continuum Environment SQL 2005 and SQL 2008 – All versions  Cause EasyLobby database creation via the .exe will not complete successfully due to a pathing issue with database file locations. Resolution Run the SQL script that is attached to this article via SQL Management tool. Make sure to double check the two lines near the top of the SQL script that specify the exact filepath(s) where the .mdf and .ldf files are to be created, as that could be unique on any given SQL Server. dbCreateSQLServer.zip Easy Lobby is available as a downloadable .doc: EasyLobby Schneider Electric Solution Guide. For all the add on products for Continuum, please visit this Exchange Extranet. For assistance with Add-On products, email COE.Support@buildings.schneider-electric.com Other add on software is Elevator Control, Reporting Modules for Continuum, Photo Album & Badge Printing App, Automatic Extended Log Archiver, Personnel Data Importer, Area Purge, Video Monitor, and Time Tracker. These products are available for a fee. PSS does not have pricing or availability for the programs. This can be found by contacting your sales representative for your region. Pricing is per machine rather than a site. Time Tracker for example,requires a software license and utilizes a software key, which is connected to the workstation’s printer port or USB dongle. A cookie is sent directly from the factory which updates the dongle used by the computer. Emailed instructions come with the cookie explaining how to install. Again, contact your sales representative to purchase a software license, software key, and activation code. EasyLobby Support: EasyLobby directly supports their software as well as the integration to Continuum. Please forward all EasyLobby support requests directly to them. support@easylobby.com (US) 001-781-455-8558  

Issue When upgrading a BCX Inf to BCX BACnet or vice versa , the BCX could lose any node count or X Drivers added using a post shipment factory *.upd cookies. The settings return if the controller is flashed back to the original model type. Product Line Andover Continuum Environment Continuum 1.xx 2.xx Windows Infinet  BACnet Node Count, X Driver, X-Driver Cause This is because the cookie upgrade to add the node count (or other features) will be sent out for the format it is intended for, i.e. if the controller was BACnet then the file will be sent as BACnet, and if the controller was Infinet then the cookie will be Infinet Resolution New controllers shipped from the factory can be flashed either way between a 4040 and 9640 and it will not affect the settings for Node count, X Drivers or other options. If a controller was to lose additional setting when it is convert from BACNet to Infinet or vice versa, there is a need to re-apply for the cookie upgrade file for the new model type. (it would of originally been ordered as additional options for the controller) To re-apply for the cookie, contact your local repairs department with the controller details i.e serial number, controller type, etc, this will enable them to find your order and reissue the upgrade in the version it has been changed to.

Issue Scheduled event reports exported to PDF are using the US date time format not the local systems date time format. Report settings   In the below example the Windows system, and Security Expert, were both setup for Australia regional settings with a date format of dd/mm/yyyy. The automatic scheduled reports exported to PDF were showing the US date format mm/dd/yyyy. Report export before   Product Line EcoStruxure Security Expert Environment Security Expert event reports Cause The local Windows system date settings for Welcome screen and New user accounts are incorrect. Resolution In Windows navigate to Control Panel\Region Click on Change date, time, or number formats. A new window (Region) will pop up. Click the Administrative tab Click Copy settings... Enable the following options if not enabled already. Under Copy your current settings to tick Welcome screen and system accounts and New user accounts as shown in the image below. This will copy the Current users format over to the Welcome screen and New user accounts sections. Date format settings After making the above changes the PDF reports generated now show the correct date format of dd/mm/yyyy. Report export after