Building Automation Knowledge Base

Issue What is the replacement for the Drayton Autotherm? Environment Drayton Autotherm Cause The Drayton TA/L1 actuator is obsolete, and no like for like actuators are available, this makes the Autotherm controller unusable. Resolution The TA/L1 actuator provides positional feedback to the Autotherm controller, and actuators providing feedback are very few, and providing the correct feedback is not possible. The Autotherm controller provides considerable functionality, and in our current  ranges of controllers, these cannot be matched. To upload the Autotherm data sheet, please click HERE.     The most appropriate replacement controller is CSC5352. This device will provide a compensated heating system with a timed start, the output relay can be used to enable the hot water system. Please click HERE to upload the data sheet. If separate time periods are required for the heating system and how water system, then the DC1100/1400 should be considered. Please click HERE to upload the data sheet. Please note that in both of the above options, new sensors will be required and possibly actuators too.

Issue How to display custom text and properties of an alarm in the email notification. Product Line EcoStruxure Building Operation Environment Email Notification Substitution Codes Cause There may be certain situations where a specific property of the monitored value needs to listed in the alarm email that is sent out. For example when an alarm is triggered, the value at the time the alarm state changed my need to be documented in the notification email. These are called substitution codes. Resolution The properties of the Email Notification can be set to customize the message that is sent out when an alarm changes states. As seen in the properties window of the Email Notification above, the "Subject" and "Text" can be changed to say whatever is desired. There are special codes that can also be entered into these fields to pull actual properties from the value that went into alarm. Below is a table that lists all of the Codes for the different value properties. This same information can also be found on the EcoStruxure Building Operation WebHelp. Substitution Codes for Notifications Code Description @(AcknowledgedBy) Writes the user that acknowledged the alarm. @(AcknowledgeTime) Writes the time the alarm was acknowledged. @(AckRequired) Writes an indicator if the BACnet alarm requires acknowledgement. @(AlarmState) Writes the present state of the alarm. @(AlarmText) Writes the alarm messages that is added to the alarm. @(AssignedID) Writes the unique ID of the user the alarm is assigned to. @(​AssignedState) Writes the current assigned state the alarm is in. The possible values are Unassigned, Assigned, and Accepted. @(​AssignedTo) Writes the name of the user or group that the alarm is assigned to. @(​AssignedToDomain) Writes the domain of the user or group that the alarm is assigned to. @(BACnetEventType) Writes the BACnet event type for this alarm. @(BACnetNotificationType) Writes whether the BACnet notification was an alarm or event. @(BasicEvaluationState) Writes if the alarm is active or not. @(Category) Writes the category name of the alarm. @(CommandValue) Writes the value which was commanded for a BACnet command failure alarm. @(ConfirmedNotification) Writes an indication whether a BACnet notification was issued as a confirmed or unconfirmed BACnet message. @(Count) Writes the number of times the alarm has toggled between the alarm and reset states. @(Deadband) Writes the value of the deadband used for limit checking for BACnet out of range alarms. @(DeviceName) Writes the name of the I/NET device that generated the event. @(​DisabledCause) Writes the cause of the alarm being disabled. An alarm can be disabled by User, Shunt variable, and System. If the alarm isn't configured correctly it can be disabled by System. @(ErrorLimit) Writes the difference limit that was exceeded for BACnet floating limit alarms. @(EvaluationState) Writes the present evaluation state of the alarm. For example, Upper limit alarm is displayed when the monitored value reaches the upper alarm limit. @(EventFromState) Writes the event state of the object prior to the occurrence of the alarm condition for BACnet alarms. @(CWSid) Writes the EcoStruxure Web Service identification of the alarm on the external system. @(CWSSourceId) Writes the EcoStruxure Web Service identification of the external object that generated the alarm. @(ExceededLimit) Writes the value of the limit that was exceeded for BACnet out of range alarms. @(ExceedingValue) Writes the value that exceeded a limit for BACnet out of range alarms. @(FeedbackValue) Writes the value that differs from the commanded value for a BACnet command failure alarm. @(FirstName) Writes the first name of the individual whose key/card was used at the I/NET door point. @(Hidden) Writes the visible status of an object. False is displayed when the object is shown. @(IndivNdx) Writes the individual number of the individual whose key/card was used at the I/NET door point. @(LastName) Writes the last name of the individual whose key/card was used at the I/NET door point. @(Logging) Writes whether the alarm should be logged or not. @(MessageText) Writes the text of an I/NET action or dispatch message, if there is one. @(MonitoredObject->DESCR) Writes the description property of the monitored object. @(MonitoredObject->NAME) Writes the name property of the monitored object. @(MonitoredObject->NOTE1) Writes the note 1 property of the monitored object. @(MonitoredObject->NOTE2) Writes the note 2 property of the monitored object. @(MonitoredObject->LabelText) Writes the label text of the monitored object. This requires that a MonitoredVariable is configured. @(MonitoredValue) Writes the value depending on the alarm states selected under 'Notify on transition to'. @(​MonitoredVariable) Writes the path of the monitored variable. @(NewMode) Writes the new mode of the monitored object for a BACnet change of value alarm. @(NewState) Writes the new state of the monitored object for a BACnet change of state or change of life safety alarm. @(NewValue) Writes the new value of the monitored property for a BACnet change of value alarm. @(NotificationClass) Writes the distribution information of an alarm notification within a BACnet system. @(OperationExpected) Writes the next operation requested by the monitored object for a BACnet change of life safety alarm. @(OriginalAlarmText) Writes the alarm text from the matched alarm. This substitution code is only available for Alarm Decorators. @(PossibleOperatorActions) Writes the possible actions one can perform on the record, given permissions. @(PreviousAlarmState) Writes the previous alarm state. @(Priority) Writes the current priority level of the alarm state. @(ProcessId) Writes the process identifier configured by the notification for a BACnet alarm. @(ReferencedBitString) Writes the new value of the monitored bitstring property for a BACnet change of bitstring alarm. @ (Report) Writes the name of the report connected to the notification. @(SEQNO) Writes the sequence number of the record. @(SetpointValue) Writes the value of the setpoint when the alarm condition occurred for a BACnet floating limit alarm. @(​Source) Writes the path of the source object. @(SourceName) Writes the name of the source object that generated the alarm. @(SourceObject->DESCR) Writes the description property of the source object. @(SourceObject->NAME) Writes the name property of the source object. @(SourceObject->NOTE1) Writes the note 1 property of the monitored object. @(SourceObject->NOTE2) Writes the note 2 object of the monitored object. @(​SourceServer) Writes the path to the server where the source object is located. @(StatusFlags) Writes the status flag of the object. @(SystemAlarmId) Writes the alarm ID generated by the system. @(TenantNdx) Writes the tenant number of the individual whose key/card was used at the I/NET door point. @(TimeStamp) Writes the time and date when the event was generated. @(TriggeredTimestamp) Writes the time and date of the last state transfer from normal state to alarm state. @(TYPE) Writes the record type.

Issue How to set the IP address of a Xenta 5/7/9xx through serial communication. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause If the IP address of a Xenta 5/7/9xx is not known initially, then no configuration can be done through the IP interface. The IP address must be set through serial communication. Resolution IP setup for a Xenta server (Xenta 5/7/9xx) through serial communication for step-by-step instructions for this process.

Issue Registering/Unregistering TAC Vista Server as a Windows service will allow the server to start automatically and run in the background of the PC (it won't show up on the Windows taskbar). This is not the same as having it run on Startup (for information on that, please see Configuring Vista Server to run on Startup). Product Line TAC Vista Environment Vista Server Microsoft Windows -- All versions Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Reference Chapter 16.3 of the TAC Vista Technical Manual "Running TAC Vista Server as a Service in Microsoft Windows XP" for more information. When you log out of Microsoft Windows or restart the computer, all running processes, for example, Vista Server, are shut down. These processes are not resumed at log on or at restart. You have to start Vista Server manually again. To get Vista Server to remain running at log off and automatically start up when the computer restarts, you can run Vista Server as a service. Running a program as a service means that it runs in the background, but it is not visible on the Windows task bar. Before you start Vista Server as a service, you must first install and configure your Vista Servers and your network and have everything running satisfactorily. It is not advisable to start Vista Server as a service until you have completed all the settings (including security and authority) and the TAC Vista system is running well. Resolution Register Vista Server to run as a Windows service Go to Start > Run Register the service by typing: Tacos.exe /service When you register TAC Vista Server as a Windows service, it will default to run under the "Local system" account.  This is not supported by TAC Vista Server. Right-click on My Computer and select Manage. Browse to Computer Management (local) > Services and Applications > Services Find TACOS, right-click and select Properties On the Log On tab, specify "This account:" with admin authority.  It is ideal to use a domain account with local administration authority if your system is a member of a domain. At this point, if you would like to start the service, highlight TACOS in the Services window and select Start the service. If you choose to run Vista Server as a service in a multi-computer network, we recommended that you run every Vista Server as a service. Change from running as a service to running as interactive Go to Start > Run Unregister the service by typing: Tacos.exe /unregserver You must then register the server back to interactive by typing: Tacos.exe /regserver Helpful Utility This utility will read in the current run mode of the Vista Server and allow you to switch between running as a service and an application. It also lets you set the user to run the service under. Click the image to the right to go to a Community post containing the utility .exe file. Accessing Vista Server Menus and Dialog Boxes Once the service has started, it is not possible to use the Vista Server menus and dialog boxes. To be able to use these, you have to unregister the service and start Vista Server in the normal way. LonTalk Adapter from Loytec When TAC Vista is running as a service and you are using a LonTalk adapter from Loytec, you must ensure that the program LConfig is also running as a service. You do this when you configure the network interface card. TAC Vista Tools and Microsoft Windows Vista Some of the tools installed in the installation folder of TAC Vista cannot run if TAC Vista is running as a service in Windows Vista. These are TAMIAN, CIPCL, SYSDOC, TADRAW, and DBGEN. Related Articles: Unable to save periodic report to network drive when Vista is running as a service Regional settings might differ when TAC Vista server runs as a service Dependencies for Vista Server running as a service Upgrading Vista while running Server as a service

Issue Modbus RTU Serial Device (RS485 - Slave) address greater than 247 Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (AS, AS-P, AS-B)  Modbus RTU Master RS485 Network Cause Third party Modbus device has an address range between 248 and 255. Resolution For Modbus master/slave RS485 networks, the third party device must be in the range of 1 to 247, this is the Modbus RTU standard. This would apply not only to EBO but to other Modbus master/slave networks.   The KB article Modbus basics explains this amongst other Modbus topics.   If the third party Modbus slave device cannot be changed to an address to within this range, then contact with the product vendor may be required.   For TCP devices see the KB article Modbus TCP Device (Slave) address greater than 247.  

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Recovering non-functioning Jace 8000 caused by image corruption Product Line TAC IA Series Environment Jace 8000 Cause Improper management of the files on the Micro SD card of the Jace 8000, power brownouts, and other issues have been known to cause corruption of the installed "Golden Image" of the Jace Resolution Download and review the Product Announcement to determine which image should be used on your Jace based on the software to be installed and the Micro SD card version: PADV-IA-22-0001, JACE 8000 Hardware Changes Soon To Be In Effect Note item 8 in the FAQ for information about the correct image for use in version 4.0 Micro SD card.   Download and select the image and tools for completing the process detailed in the video: I/A Series Niagara JACE 8000 Images and Raw Copy Utility - Installation Software   

Issue When swiping a card in front of the reader, there should be a beep indicating that the reader has read the card. There is no beep. Product Line EcoStruxure Security Expert, Andover Continuum, TAC I/NET Environment Access Control HID Reader Cause There are 3 possible reasons for this issue: The beeper is disabled through a default configuration when the card is shipped The beeper has failed The Reader and Card represent incompatible technologies such as an 125Khz Prox Reader trying to read a 13.56MHz IClass Card Resolution Ensure Reader and Card both support a common technology (125Khz/13.56Mhz etc..) Short the Beeper wire (yellow) and the GND wire (Black) with the reader powered On If there is a beep, that indicates that the beeper can work but is disabled. Ask the manufacturer to send a configuration card to enable the beeper (use 3 seconds after reader power is on) If shorting the beeper produces no sound, the beeper has failed. Send the reader to repair and replace it with a new one.

Issue Automation Server Classic support for hosting MPX or RPC Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Classic, AS-P, AS-B Building Operation SmartX MPX, MPC, MPV field controller Building Operation SmartX RPC field controller Cause The original Automation Server (Classic) can be set up to fully host (host server) and configure both MPX and RPC devices, but the Architectural Guidelines do not specify how many devices can be fully hosted. Resolution Full hosting of MPX, RPC is only supported and tested on AS-P, AS-B and Enterprise Server. This is confirmed in the MPX and RPC Specification Sheet. "MP-C/MP-V/RPC can either be used as a standalone BACnet/IP field controller or as part of an EcoStruxure BMS with a SmartX AS-P or AS-B server or an Enterprise Server as the parent server." MPX, RPC can be simply be BACnet hosted on an Automation Server Classic, but the use as parent or host server is not supported or tested.

Issue Controller loses data following power failure or mains noise (from transients or spikes). Product Line Andover Continuum Environment All CX, ACX, i2, bCX, b3 controllers Cause Controllers are exposed to operating conditions outside their operating envelope and tested limits. This can cause them to reset, go offline or lose data. In extreme circumstances, poor installation can take controllers outside their operating envelope and cause damage requiring a repair. Resolution If a controller is setup on a bench with a clean power supply and the correct grounding, you will be able to turn off/ on the power and the controller will warm start every time. This test will confirm the controller is operating correctly, not faulty and that the software settings are correctly set for warm starting. Also that the RAM backup battery is connected and operating. If site resets, lockups, loss of memory or other corruption are seen on a site, then here are some of the installation issues to consider: Grounding - All controllers require a clean low impedance earth to sink all of the noise and emission energy a controller may be exposed to. The noise protection circuitry within a controller is designed to dissipate this energy down to earth, if this path is not low impedance the energy can cause a controller to reset or even be damaged permanently. Shared Ground - The earth cable to the Controller should not be shared with any other equipment that is a high inductive or capacitive load, these can generate noise spikes back into the controller. This includes motors (pumps/ fans etc) lighting circuits (capacitive loads), inverters (high frequency noise). Induced emissions - The controller should not be installed near any equipment that may induce excessive radiated emissions into the unit, the radiated emissions from Motors, inverters, radio & microwave equipment, lighting circuits, power wiring can all produce radiated emissions that could exceed the specified limits of the Controllers. By fitting the controllers into earthed metal enclosures you can minimize the external emissions by effectively creating a Faraday cage protecting the controllers circuitry. Power feed - The power requirements for every controller is defined in its datasheet with the defined tolerance, taking the power levels outside these limits can cause incorrect operation. Power spikes - Surges or spikes in power feeds or connection I/O cabling can cause controllers to reset, lose data or even become damaged. Fitting varistors to the power supplies and across any output loads can minimize the impact on the controller, See What Varistors should be used?. Shared Supply - The power feed to a controller should never be shared with other equipment that can generate electrical noise. Never use the same supply to power both controllers and field equipment like valve/ damper actuators in BMS systems or magnetic door locks in Access control, both actuators and the solenoids in Mag locks can generate large back EMF pulses into the controllers that can cause resets or even damage.. Fitting power filters or an external UPS on the controller can protect it from spikes on power up/ down, it is however always best to remove the noise spikes at source, so fit filters the generators, motors, contactors etc. It is also possible for the above issues to cause Infinet networks to Reconfig as well as other networking problems. Note: All controllers are approved and tested to the defined limits for FCC and CE induced and radiated emissions as detailed in the datasheets, for a controller to fail, restart or lose data it must be exposed to levels exceeding these specifications. They are not however power equipment and cannot be exposed to the noise levels power and industrial controls equipment is designed to withstand.

Issue How can the true/false output from a Boolean object (i.e. Tstat) be changed to a numeric 0 or 100 in Niagara G3? Environment Niagara G3 Cause Represent a boolean on/off value with a numeric that can be used to drive other logic. Resolution Open the kitControl palette under the Util folder Use an object called NumericSwitch Link the output of the Boolean object into the InSwitch property of the NumericSwitch In the properties of the NumericSwitch object, set the "in true" value to 100 and "in false" value to 0 (or vice versa if reverse acting). The output of the NumericSwitch will be a numeric type.

Issue Two related issues are covered in this article While attempting to activate a customer or demo license, the activation process stops at around 80%. When clicking the "Diagnostics" tab in the License Administrator it crashes with a "System.DllNotFoundException" error. System.DllNotFoundException: Unable to load DLL (Tac.Nsp.Archive.Licensing.Client.dll) Product Line EcoStruxure Building Operation Environment First detected in Windows 10 First detected with Microsoft Visual C++ Redistributable 2012 (VC++ 2012) License Administrator Cause There can be two reasons why this happens If the activation process stops at around 80%, but the License Administrator does not crash when the "Diagnostics" tab is selected, the license system needs to be completely reset. If the activation process stops at around 80%, and the License Administrator crashes when the "Diagnostics" tab is selected, Microsoft Visual C++ components need to be repaired. Refer to solutions below depending on the issue detected. Resolution Solution 1: Resetting the license system The process to reset the license server system is covered in Resetting the License Server. In some cases, a deeper reset can be required. For that, a tool called "SBO License Server Reset" can be downloaded from the Community. Solution 2: Repairing Microsoft Visual C++ components Method 1 In Control Panel, click Uninstall a program in the Programs group. In the programs list, locate Microsoft Visual C++ 2012 Redistributable (X64) - 11.0.61030 or Microsoft Visual C++ 2012 Redistributable (X86) - 11.0.61030, depending on your system architecture. Right-click the entry name, and then click Change. In the Modify Setup dialog box, click Repair. After the repair process is completed, restart the computer if you are prompted to do this. Method 2 Run the Modify Setup repair functionality for Microsoft Visual C++ Redistributable by starting the installer. VC++ installers In the Modify Setup dialog box, click Repair. After the repair process is completed, restart the computer if you are prompted to do this.

Issue OPC Server with third party and alternatives Product Line Andover Continuum, TAC INET Environment System requiring third party connectivity Cause OPC Server to communicate between hardware and the iBMS (intelligent Building Management System). Resolution The OPC server is a software program that converts hardware communication protocol into the OPC protocol. The OPC client software is any program that needs to connect to the hardware. The OPC client uses the OPC server to get data from or send commands to the hardware. OPC Client Servers are used to communicate between BACnet IP interfaces and iBMS (intelligent Building Management System) programs such as TAC I/NET or Andover Continuum. There is also no Continuum OPC Client software to use for a direct OPC link. The best way to integrate from 3rd party EIB or OPC protocols is using BACnet IP on Continuum; there are third party interfaces and gateways that will convert to BACnet/IP and others that go from OPC Client/ Server to BACnet/IP. I/NET OPC For I/NET a great solution is to install a Xenta 913 controller which gives the capability to go with Modbus or BACnet/IP to third party solutions. The I/NET to Xenta 913 allows communication with Continuum BCX, StruxureWare AS-B, and other 3rd Party solutions. Continuum OPC Standard 3rd party gateways are established to communicate between the protocols such as BACnet and Modbus. Andover Continuum has an OPC Server available here. The hardware requirements are Windows NT 4.0 or Win2K. If wanting to run on XP or newer operating systems, please be aware that no testing has not been done with these OS. For more info on the OPC and XDriver, please see OPC Server Integration. Only one instance of the OPC server on a computer. Each system would need a separate PC with license key to connect to the individual systems and host controllers. The Andover Controls OPC server must be running a separate 3rd Party OPC client computer and cannot be on the same computer as CyberStation. From there it is configured to retrieve point values from a the suggested dedicated Infinity (CX) Controller. It is suggested to install a OPC gateway Infinity Controller since this controller will constantly be busy with OPC traffic. Therefore it is the separate third party vendor computer which requires the ACC OPC Server security key, not Cyberstation security key. Both USB and parallel port keys are available. If no choice is available for OS, one alternative is to check on 3rd party OPC servers like Kepware and Matrikon. Note: For Continuum, determine which one of your controllers will become the “Primary Controller” The Server requires that you designate one external Andover Controls Infinity or Continuum controller located on the same network as its “Primary Controller.” This controller must have had the network taught to it prior to selection. (This is done through the “Teach” function in the workstation.) The Server gets its information about the network through this controller. This suggested single controller is designated as the interface through which all point access is obtained. Controller Type Select the type of network where the controller is located. For a NetController, b4920, CX9702 or upgraded Infinity controllers that can be connected to a Continuum network you would select “Continuum”. For older Infinity controllers, select Infinity. Works with any IP level controller. There is no limit on the quantity, but rather it depends on how you tune.

Issue The discontinuation of the SVT controller due to component obsolescence. Product Line Field Devices Environment SVT Optimiser 4201 4251 Cause What replacements are available for the SVT 4201 / 4251 controllers? Resolution Important Note - The replacement controller mentioned in this article is no longer available, and therefore a replacement for the SVT 4201 / 4251 is not available. The SVT controller range has been discontinued due to component obsolescence. The SVT controller was a basic optimiser that performed the start calculation using only an internal temperature sensor. There are no exact replacements for this controller available. What is available? The Schneider Electric DC1400 Optimiser / Compensator is the recommended replacement, but this is not a direct replacement. Differences in the controllers. The SVT controller provides only an optimum start, the DC1400 provides optimum start and stop. The SVT controller uses only a room temperature sensor for the start calculation, the DC1400 uses only a room temperature sensor and an outside temperature sensor for the start/stop calculations. The SVT controller has a dedicated "Boost" relay, which allows overriding of a CSC compensator, and control valve. This is an internal function with the DC1400 optimiser/compensator. The DC1400 has many other built in functions.   Controller wiring - Modifications will be required. SVT general wiring connections. Relay R1 is the main plant relay and relay R2 is the boost relay. To see the full controller details, please click SVT Optimiser DS2001 0210.pdf DC1400 general wiring details.   To see the full controller details, please click DC1400 DS2044A.pdf Controller Sensors As already indicated, the SVT controller uses only a space temperature detector, and this sensor is NOT suitable to use with the DC1400. The DC1400 controller will, as a minimum, require a room temperature sensor and an outside temperature sensor, meaning that extra wiring for the outside temperature sensor, and the sensor itself, will need to be installed. For details on suitable sensors, please refer to What sensors does the DC1400 optimiser/compensator require?

Issue After downloading a hotfix for Device Administrator, it is not possible to install a new database onto an Automation Server **. **Note, for this article "Automation Server" will be used as a general term. This applies to all Smart-X controllers (Automation Server, AS-P, and AS-B). Product Line EcoStruxure Building Operation Environment AS, AS-P, AS-B  SBO Device Administrator Cause When the Device Administrator hotfix is downloaded to the machine, it replaces the "Full-Installer" version that was already installed. The new hotfix version does not include the necessary firmware to push down onto the Automation Server. This can be misleading because Device Administrator still indicates the base firmware version is present, as shown below. Resolution A full installer (such as 1.8.1.87 or 1.9.1.95) of Device Administrator must first be installed on the machine and used to install the base firmware onto the Automation Server. Then the hotfix version may be downloaded to the PC and used to apply the hotfix to the Automation Server.  **Note - In some instances a hotfix can be a full installer, which will allow for the download of a new database. Such hotfixes will be released either as a full installer or as a maintenance build. The release notes for the particular hotfixes will indicate their full installer build. 

Issue The Automatic Logoff feature is available in version 1.4 and higher. Starting in version 1.5, there is a default automatic logoff time of 10 minutes in both Workstation and WebStation for the Administrators user group. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation WebStation Cause To prevent unauthorized users access to the system the automatic logoff feature has been added to SBO/EBO. The default Administrators group is set to automatically log off of both Workstation and Webstation after 10 minutes of being idle. This setting cannot be changed for the Administrators group. Resolution The automatic logoff function makes it possible to decide when a user is automatically logged off after a specified time of inactivity. Inactivity means that no user initiated activity is ongoing, that is, no action has been made using the mouse or the keyboard. However, if a user has initiated a big operation in Workstation, for example an import or a large copy and paste, the user is still considered to be active as long as the process is ongoing in Workstation. This is to prevent loss of data. The automatic logoff function is used for security reasons and it also prevents that a Workstation user occupies a license when inactive. The automatic logoff time is set at User Group level and is always defined by the group that has the longest automatic logoff time. For example, if a user belongs to two groups, one group has an automatic logoff time of 5 minutes and the other group has an automatic logoff time of 15 minutes, the user is automatically logged off after 15 minutes. If a user belongs to a group that does not have the automatic logoff function enabled the user will never be logged off. Note: When a user is logged off by the automatic logoff function all settings that are not saved are lost.   Creating a new user group so the Automatic logoff time can be adjusted Starting in version 1.5, in order to change the duration of time before the automatic logoff occurs or turn it off a new User Account Group must be created. Follow the steps below. Go to the Control Panel in Workstation. Click on Account management. Click Add under the User Account Groups section. Name the new User Account Group. Click Next. Select the Users to add to the new group and then click the right arrow to move them to the "Selected User Accounts" window. Click Next. In the same method as step 4, select the Workspace to add to the new group and move it over to the "Available Workspaces" window. Click Next Set the group policies for the new group taking note of the Automatic logoff time which can be set to "Never" if desired. Click Create.   Changing the Automatic logoff time of an existing user group In the System Tree under System > Domains > Local > Groups, select the user group and click on the "Policies" tab. Here the Automatic logoff time can be changed and then click the save button on the tab at the top of the window.

Issue Reference of I/NET Guide Product Line TAC INET Environment I/NET Seven Cause Combination of various TCON documents showing most common used functions for easy reference.  Note that this document is not maintained.  Please refer to documentation available on Exchange Resolution Download the INET Pocket Reference Guide PDF

Issue Replace Invensys Actuator Model MA5-419-500-0-3 Environment Damper Control Actuator site Cause Replacement Specifications for Obsolete Invensys MA5-419-500 which is a Two Position Damper Actuator, SR, 240V, 50 Hz, 60 lb-in, w/SPDT Aux. Switch Resolution The closest replacement would be the MD5B-24(-S)/-230(-S) On/Off or 3-point 24 V AC/230 V AC Damper Actuator 5 Nm (45 in-lb). Note: This is a Rockford, Illinois offering, which we would not normally have offered this in Europe in the past. There is a range of Non-Spring Return Damper Actuators detailed in Pages 54 and 55 of the below Schneider Electric Catalogue. Similarly there is a range of Spring Return Damper Actuators detailed in Pages 56 through 58 of the below Schneider Electric Catalogue. Damper Actuator Accessories are shown on Page 59 of the below Schneider Electric Catalogue. Schneider Electric HVAC Valve and Actuator Catalogue  

Issue What is the procedure for upgrading the I/A Series G3 software in an I/A Series ENC? Product Line TAC IA Series Environment I/A Series G3 Workbench software on computer (both the old version and new version need to be installed on the computer) I/A Series G3 ENC-520 or ENC-410 Cause Need to upgrade the software that is installed in the ENC. Resolution With the old version of Workbench running on the computer, backup the station running in the ENC.  All required graphic files, etc., stored in the ENC should also be backed up.  Note the station folder name for use in step 5, below. Verify that the license in the ENC is compatible with the new release to be installed. If not, use the License Manager (under the Platform) to install an updated license. If the correct version of the license is not currently available, it must be obtained and installed prior to beginning step 6, below. If the new release of the I/A Series G3 software has not already been installed on the computer, install it now. Verify that the Workbench computer has a license that is version compatible with the new release of the I/A Series software to be installed.  If the license is not version compatible, acquire a new license for the Workbench computer before continuing. Copy the entire named station folder (used in step 1) from the old release Stations folder to the new release Stations folder.  See NOTE below regarding the installation of a version downgrade. Run the "Install Platform Daemon" command from the Windows Start Menu folder for the new version of the software. Open the Workbench in the new version of the I/A Series G3 software and connect to the platform of the ENC to be upgraded. From the Platform menu, open the License Manager and verify that the ENC license has been updated to allow use with the new version of the I/A Series G3 software. Right-Click on the ENC platform in the Workbench tree and select Commissioning Wizard. Complete the commissioning process as documented in the Niagara AX Install and Startup Guide . On the first screen, select the operations to be performed.  The required minimum operations will normally be checked and shown in grey.  The "Install a station..." option needs to be checked if not already checked. Click [Next] to begin the commissioning process.  Continue through the various steps, as required.   When prompted, select the station copied in step 5. When prompted, verify that all required modules are available and are selected for installation. Allow the commissioning process to complete, following the prompts as required. The upgrade is now complete.  Start the station as required. NOTE: Do not use the process to directly downgrade the version of software installed in an ENC.  You must use the Platform "Distribution File Installer" to install the appropriate clean distribution (from the cleanDist folder under the software version to be installed.  Typically, only one clean distribution file will be available to be installed.  Select that file then click the [-> Install] button to downgrade the ENC software.  This process needs to be done as noted in step 5, above, after backing up the station but before beginning the commissioning of the device with the older I/A Series G3 software version.

Issue Tips for Configuring HID OSDP Reader LED Colors Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert OSDP Reader Cause Additional tips for configuring OSDP Reader LED Colors Resolution The Configuring LED Colors section of AN-254 Configuring OSDP Readers in Security Expert  details the basic steps for LED configuration. This article details some additional areas of the HID reader setup and Security Expert configuration that may be useful when configuring the LED colors.   Note: The steps in this article are specific to an HID Signo RP10 Reader BLE and may not apply to other HID reader models or other brands of OSDP readers.   Upgrade the Reader firmware to the latest version. Earlier versions of the reader firmware would not correctly allow LED control. The Bluetooth option allows the configuration of the reader using the HID Reader Manager App. For detailed information see HID Reader Manager App Information Note: To use the HID Reader Manager App to configure a reader, the Security Technician or Security Installer needs to create and register an account with HID. The Reader Manager Administrator for your organization or company needs to enroll this new account using the Reader Manager Service and issue an invitation code and key authorization for this and other readers. The Security Technician can then verify the key authorization has been received in the HID Reader Manager app. Detailed instructions for all of this are included in the HID Reader Manager App Information URL listed above.   HID Reader Manager App Firmware snapshots       In the HID Reader Manager App, change the Reader Options for LED color to "Host Controlled" in 2 places. The reader must be controlled by the Security Expert controller. Credential Reader AV LED Idle Color Ensure that the firmware for the following hardware is upgraded to these versions or greater in order for LED Color Output to work. Security Expert 4.3.308.46 SP-C 2.08.1234 MRDM2 1.2.590 In Security Expert the Outputs to control the LEDs need to be manually created. Programming> Outputs> Add A pop-up asking to Invert Output will display, select 'No' when prompted Output 3 (GreenLED Port 1) Output 4 (Red LED Port 1) Output 6 (Green LED Port 2) Output 7 (Red LED Port 2)   Name the Outputs whatever is appropriate Example:  GreenLEDPortON RedLEDPortOff LED Colors The default LEDs are Blue when Idle and Green when active. As an example, the LED colors will be changed to Red when Idle and Green when Active. Color Options:   Set the colors for both Red(idle) and Green(active) in the Security Expert Output Command Window for the newly created outputs RedLEDPortOff   GreenLEDPortOn Update the modules and wait for about 15 seconds before activating the output to test. Just saving the updated command setting doesn't work, the module must be updated.   Activate the GreenLEDPort1 - the color should change to what the output was set to in the command. In this case, green. Deactivate goes back to Off (idle) Red. GreenLEDPort1 = On State RedLEDPort1 = Off State   Note: The Off state if left at the default of Blue can't be used with the On state of custom(non-default). Both Outputs must be specified in the command window for the colors to work together.   Example: If the OFF state is left at the default of blue and the color of the ON state is set in the command window and Activated, the LED color will change to what it is set to(green), but when deactivating the Off(idle) output it will not turn blue.

Issue How to recover the AD v3 password if lost / forgotten? How is a factory reset done on an Advanced Display version 3 (AD v3)? Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display V3 Cause If losing the kiosk password for AD v3, it is not possible to get a recovery password. If the kiosk password is lost for the AD v3 a factory reset must be done on the tablet to be able to get out from the kiosk mode. Resolution The following video will show the steps to perform a factory reset on an AD v3: