Building Automation Knowledge Base

Issue PIR Passive Infrared Sensor, Motion Detector with I/NET Environment Remote Arming Terminal(RAT) or OP5 site with PIR or Passive Infrared Sensor or Motion Detector Cause Site has an Intrusion Alarm System with OP5 arming terminal, the problem is that they want to disable messages from PIR (Passive Infrared Sensor detectors when the zones are disarmed. The goal is to only have alarms when zones are armed. One reason is that there are many PIR changes in the time when the building is occupied. They set the input of PIRs as an DA.   Resolution The best solution is to use an event sequence or sometimes referred to as an event definition. In other words there needs to be a relay which enables or disables the PIR. Some use the Shunt relay on the SCU(if the SCU is not double addressed) for this and it is on either one leg of the power or a contact on the PIR to enable-disable/arm-disarm the PIR.  

Issue Receive "Error 1606. Could not access network location\." when installing I/NET Seven Software with StruxureWare Building Operation Environment I/NET Seven SmartStruxure Solution 1.3 Cause When uninstalling / Installing I/NET with Building Operation software already installed the Enterprise Server and InetIoSrv service must be stopped.  In some situations when not installing the for site it may be best to set both the Enterprise Server and InetIoSrv services to manual avoiding this situation. Resolution To resolve this problem.  Stop the Building Operation Enterprise Server service, either from the Software Administrator application or from the Windows Services. It is also recommended to stop or remove the InetIoSrv service prior to any update of the I/NET Seven software.

Issue When attempting to build connection to a Filemaster the error "invalid I/NET seven operator" is given Environment I/NET Filemaster Equalized client Cause When building a connection to a remote database, you must use the credentials for the remote PC not the local PC. In this example, when creating the connection to a Filemaster from a Equalized client, you must use the I/NET log in credentials for the Filemaster. Resolution Change the I/NET user name and password to one that has full permissions on the Filemaster PC.  You may need to attempt to log into the filemaster PC to verify the username and password.

Issue Now the newest firmware version of Xenta server is 5.1.8, and the hardware version is 3. If a new Xenta server in an old project is needed to replace an old Xenta server with old version, it is not compatible with the old TAC Vista or I/NET software version of the project. So downgrade of the firmware is needed. Environment TAC Xenta 500/700/900 TAC Vista Cause Controller with new firmware is not compatible with the old TAC Vista or I/NET software. Resolution The controller with hardware 3 can be downgraded, but with only three versions: 5.1.6 SP1, 5.1.7 SP2 (or SP3 for X700) and 5.1.8 SP1. If any firmware other than these three versions is downloaded to the Xenta server, there will be no warning and it will be "bricked". Refer to TPA-VSTA-12-0029.00.

Issue In Chinese OS, values under Xenta server on graphics in Webstation show offline. But in Workstation, it is fine. Environment Xenta 5/7/9 Vista Graphics Webstation Cause In Chinese OS, the characters contain space will show odd symbols. If the path of the value contains space, it will be fine in Workstation, but offline in Webstation. Resolution The solution of this issue is to avoid space in the path of the value. Use underline instead of space to separate characters. For these path that can’t avoid space(for example, the Public signal and Time schedule under Xenta server), create dummy variables to connect to them, and use these variables in graphics.

Issue What is an acceptable induced voltage on to I/Net signal terminals Environment I/net SCU Cause If you have 10V which is induced on to an input cable. And The installer ran 24Vac alongside signal wires in a multicore cable with a common screen. And  have a plan to eliminate the induced voltage by reducing the number of pairs carrying voltage and using other cables Resolution Of the input signal types, the Thermistor type is considered the most vulnerable to the pickup of stray voltage from sources in the local area. This is because the AI input is a high input impedance (as it is with all voltage measurement modes of operation), AND the signal source is also very high impedance (the 10K thermistor itself). With one side of the circuit grounded, this presents the 10K ohm impedance of the signal wire as a prime candidate for inducing AC voltage noise from and local adjacent AC voltage sources AND especially any such run in the same cable. There is no “acceptable limit” definition on such AC pickup. Acceptability is directly related to the system application and/or customer tolerance for fluctuations of temperature readings. In the room temperature range, a thermistor signal changes by only ~ 54mv for each degree C. Without filtering, this 54mv/C sensitivity would produce constant variation form small induced noise levels. We provide both hardware and software filtering on the analog signals that allows rejection of AC noise seen on the input terminal, BUT you still want to minimize the level of the noise pickup as seen on the analog inputs. In the I/NET controllers the hardware filter provides a 94/95 % reduction of the 50/60 hz AC noise level presented to the controller. The controller firmware follows with implementation of  deglitching and averaging filters that further reduce the effect of noise on the AI point value.  We also have a input filter technique specifically targeted at reducing the impact from AC line induced noise. That filter works on the principle of making the AI readings at a scan rate of 1.5 times the AC line frequency. This is the purpose of making the AC line frequency a configuration item (50 or 60 hz) in the CLAN controllers. On the SubLAN, this is scan rate is fixed at 25ms (1.5 times 60hz) which make the line frequency filter not as effective for 50hz, but still very helpful.   As the analog inputs are scanned, we capture a reading on the negative or positive cycle of the induced noise and then we average that with a reading taken from the opposing cycle of the induced AC noise as seen 25ms (or 20ms) away from the previous sample. The average of the positive and negative cycle of the induced noise creates a near complete cancelation of the induced error – for a sinusoidal wave noise signal. This technique does a great job of producing a notch filter centered on the AC line frequency and reducing/filtering the impact from such line frequency noise.   This combination of several filters allows you to see AC line induced noise on the analog input terminal, and still maintain a stable temperature reading in many cases.  Note -- If the AC noise is non-sinusoidal, due to anomalies in the noise transfer or originating from an AC source other than the sine wave AC power line, then the affectivity of the noise reduction will be reduced and signal reading impact will be larger. The 10V of induced voltage you describe is very large (huge) and far beyond anything I have seen, but then I have never seen 24VAC wired in the same cable with thermistor signals.  Separation of the 24VAC as you describe below is needed. Your described past tolerance for  5V is also above what I would expect to accept.   However, it is possible that the AC line frequency filter has been making such high noise level appear acceptable on the temperature reading display.   For possible work-around use, the high impedance of the thermistor source makes the addition of a capacitor on the AI terminal to ground very effective in reducing the applied voltage from AC noise pickup. Here a capacitor value in the range from 2 to possibly 100 micro-farads can sometimes be useful to reduce or work-around an installation wiring problem. The capacitor should be of the “Low Leakage” type.  Leakage in the capacitor would be exhibited as a small reduction in the DC voltage and associated increase in the temperature reading.  The higher the micro-farad capacitance value, the more reduction in noise you will achieve, but it is easier to obtain low leakage capacitors in the smaller capacitance values.  If polarized electrolytic capacitors are used, be sure to position the negative terminal toward ground.

Issue MR-VAV-AX output 3 set to an AO instead of a DO Environment MR-VAV-AX Cause This is correct. The output will always be labeled as an AO even thought the function of the output will be a DO Resolution If a DO is required for additional programming needs, create an internal DO point and use either a calculation or event sequence to control the new internal point.

Issue The UNC and Enterprise server, as well as many other Schneider-Electric Buildings products, use a TIME protocol server to provide clock synchronization. The address of that Time Protocol Server no longer works. NOTE: The nist.gov sites will no longer be providing TIME protocol services over TCP port 37 as of March 1, 2013. Product Line Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Schneider Electric Buildings products that rely on the use of TCP TIME protocol servers for time synchronization. This includes the I/A Series R2 UNC & ES and the I/A Series G3 ENC & ENS as well as other IP ethernet based products. Cause Many server sites are discontinuing support for the TCP TIME protocol because it is so bandwidth intensive. NOTE: The nist.gov sites will no longer be providing TIME protocol services over TCP port 37 as of March 1, 2013. The site http://tf.nist.gov/tf-cgi/servers.cgi lists most of the currently available TIME protocol servers as well as the status of the entire TIME protocol system. Resolution If the product supports the use of the NTP time sync protocol, switch to the use of that protocol. If the device only supports the TIME protocol, consult the web site http://tf.nist.gov/tf-cgi/servers.cgi for currently available sites.

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 Services for assistance. Issue When many trend logs are linked to the same time object for emailing via a Receiver Group, some of the trend logs may not be sent. Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause The Xenta Server cannot send more than approx. 50-60 simultaneous emails before some are lost.  The limit appears to be dependent on the size of attached trend logs and the number of addresses in the Receiver Group list. Resolution For a single email address, split the trend logs into groups of no more than 40.  Link the logs in each group to a different time object and stagger the times at which they are sent.  If the Receiver Group definition contains multiple email addresses, reduce the number of trend logs in each group accordingly.

Issue Prior to XBuilder 5.1.1, it was not possible to change the type of an Xenta Server in an XBuilder project once it had been created.  Sometimes there is a need to move the project to a different type of Xenta Server without losing all the links and bindings within the project. Environment Xenta Server XBuilder 5.1.0 or earlier Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause In XBuilder 5.1.0 or earlier, it is not possible to edit the Xenta Server type in the network pane of the XBuilder project Resolution Upgrading to Vista/XBuilder 5.1.1 or later will allow you to easily change the device type directly from XBuilder.  Note that this must be done from an XBuilder project that is saved to the computer. If the project is in a Vista database start by opening the XBuilder project, clicking on File > Save as and then save it to the computer. Then, close XBuilder, reopen XBuilder and open up the saved copy of the XBuilder project from the PC. In the XBuilder Project menu select 'Change Target type...'.  Choose your preferred target device from the drop-down list.   If it is not possible to upgrade, the following instructions allow an XBuilder project to be transferred to a different type of Xenta Server without losing graphic bindings or bindings between objects on the System pane and the Network pane.  The one proviso is that the target Xenta Server's hardware must be able to support any network defined in the source project and have the same or better Menta and User graphic capabilities.   There are many different combinations of Server types and BMS platforms that these instructions could apply to in general.   The example given here transfers an Xenta 555 project to an Xenta 731.  The Xenta 555 has a Lonworks network and a Modbus network and is part of a Vista database.   Creating the Xenta 731 in the Vista database: Open the Vista database containing the Xenta 555 project. Right-click on the 555 and select Edit from the dropdown menu. The XBuilder project opens.  Keep this open for the following steps. In the Vista database create a new Xenta 731.  The name is not important but it should be similar but not identical to the 555 it will replace. Transferring the Lonworks network to the Xenta 731: In Vista, drag and drop the LON network from the 555 to the 731. Right-click on the 731 and select Edit from the dropdown menu. The 731 project opens in a new instance of XBuilder.  Rename the default folder in the system pane to the same name as the top level folder in the 555 project. In the 731 project right-click on the LON object in the Network pane.  Select 'Refresh network from TAC Vista'. Transferring the Modbus network to the Xenta 731: In the 555 project, right-click a Modbus device and select 'Edit Device template' When the device editor opens, select File | Save as.. Save the file in the default location with the default name. Repeat steps 2 to 3 for all Modbus devices in the network. In the 731 project recreate the Modbus network using the templates just saved.     Transferring the System objects to the Xenta 731: In the 555 project, right-click an object below the top level folder and select 'Copy'. Move focus to the 731 project, right-click on the top level folder and select 'Paste'. Repeat steps 1 and 2 for each object and folder below the top level in the 555 project.  Selecting a folder also selects all the objects and folders beneath it.  Although it is possible to copy the top level folder in the 555 project, it is not possible to paste it into the 731 project. Graphics bindings are retained and the reference paths are automatically updated with the new network tree i.e. 'TAC_Xenta_555' is replaced with 'TAC_Xenta_731'. Some object bindings will be broken e.g. Time objects.  These must be rebound manually. When all objects have been copied across and rebound if necessary, close the 555 project. Deleting the Xenta 555 and downloading the project to the Xenta 731: In the Vista database, delete the Xenta 555. Generate the 731 project.  There will be a warning message offering to copy the original TGML files to the new default location.  Select 'Yes'. The 731 project should now generate without errors. Download the project to the Xenta 731.   If the 555 only contains a Modbus network, a similar methodology will also work with standalone 555 and 731 projects.  

Issue Used the script to make an automatic backup and after the first one, it doubled on the next one. Is this what is expected from the backup? Product Line TAC INET Environment All versions of I/Net Cause What does an automatic backup really do to a database? Resolution The Automatic backup is a script that will backup the database whenever it is executed. It creates a generic database the first time but does not append it. Each time after that a backup is created and time stamped that it was executed. If it changed in size, then it would have been due to events occurring during the time that has elapsed.

Issue Unable to install the SQL Server with I/NET. Error shows: The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine "machinename" error:2147942405(0x80070005). Environment I/NET Seven Cause Some security settings have been changed under DCOM. If local launch and local activation properties are set to 'Not Defined,' the installation will fail. Resolution Open Administrative Tools > Local Security Policies Find Local Policies > Security Options > 'DCOM: Machine Launch Restriction in Security Descriptor Definition Language(SDDL)' Set the System user 'Local Launch' and 'Local Activation' to ALLOW.

Issue Cannot get changed I/NET point or controller name to update in StruxureWare Building Operation Environment SmartStruxure I/NET integration Cause There is a designed feature for integrated I/NET objects within Building Operation.  Once an object is imported into SmartStruxure, it can be re-named and given description with more options than on the I/NET controller.  For this reason, when changing a point or controller name through the I/NET interface, it will not be updated in SmartStruxure.  All name changes should be done through the Building Operation Workstation interface. Resolution If you wish the StruxureWare Building Operation names to match the changed I/NET name, you have 2 options. Change the name manually in Building Operation Delete the point and re-upload the controller, or delete the controller and re-discover it NOTE: Do not change point names in SmartStruxure until after all converted graphics have been imported.  The import process requires the SmartStruxure name and I/NET name to match.

Issue I/NET alarms not coming into StruxureWare Building Operation as Alarms, but are showing up in Event Window Environment SmartStruxure StruxureWare Building Operation Cause In order for an event to register as an Alarm in SmartStruxure, there must be a SmartStruxure object in the Enterprise Server Resolution Ensure all Controllers generating desired alarms are visible in the I/NET interface. If they are not, use the device discovery feature to import them. Ensure all Controllers are up to date.  Right click upload any that are not. For alarms that originate from a Host or NPR, you will need to add these to the I/NET interface System Folder.  Right click on the I/NET Interface/System folder and add either a host or link as applicable.  Set the correct host or link number in the properties window.

Issue Is there a way to activate a function which requires a cause note, action note to be added to every I/NET alarm? Environment I/NET SmartStruxure Alarm User Action Cause Need to document user actions in SmartStruxure when an I/NET alarm changes state. Resolution Create a Change of State alarm and bind it to the I/NET alarm object in SmartStruxure. Create a Change of State alarm. On the User Action page of the alarm configuration attach a Cause Note Group, Action Note Group or Checklist. Bind the alarm object to the Alarm attribute of the I/NET Value.

Issue After logging on to I/NET, an error comes up saying "Verifying Database. The database file "RptASample" has changed. Proceeding to fix up the report." Environment I/NET upgraded version 2.4X Cause The table structure that was saved with the report is different than the current database table structure. Resolution There is no resolution as there is nothing wrong with the report. Click on the OK button and the report will be generated. The original report's structure is different and Crystal Reports recognizes it then alters or realigns them to work in the new format.

Issue Text in I/NET is showing up as gibberish, but the text in the SQL database looks OK Environment I/NET Cause If you upgrade I/NET and the SQL database but do not use DBcreate, the text in I/NET can become gibberish. Resolution Restore/upgrade the database with the help of DBcreate (follows I/NET )

Issue Changing an I/NET DI to a DA does not show up in StruxureWare Building Operation Workstation Environment I/NET SmartStruxure Integration Cause After integrating I/NET to SmartStruxure the designed intent is to allow all point name changes and alarming to be done in SmartStruxure workstation.  If you delete a point and re-create it using the same point address, point name but a different point type, the change will not show up in SmartStruxure. Resolution To successfully change an I/NET point from DI to DA: Delete the Point using the I/NET Resident I/O Editor Re-create the Point using the I/NET Resident I/O Editor using the new point extension DA. YOU MUST change the point name in some way. Perform a Station Save Open Building Operation Workstation Right Click on the Controller and select Update.

Issue Contact info for Schneider Electric Buildings Business Order Entry in the UK Environment Purchasing UK Price and Delivery information Cause For all questions from end users, pricing and delivery information. Resolution UK CCC in Telford: Phone 0870 608 8608 Email OrderEntry.UK@Schneider-Electric.com

Issue When using User Defined PIN in the individual, it can’t take effect. Environment I/NET Cause Large card number should be used if User defined PIN is needed. Resolution User-defined PINs are supported when all of the following requirements are met: The door controller’s firmware is version 2.30 or later. DIP switch 7 at the door controller is ON or the Card Translation option is enabled in the Door Extension editor The individual is directly assigned a large key/card number (i.e., a key/card translation table is not being used to translate the user’s key/card number).