Building Automation Knowledge Base

Issue DVR incorporated with I/NET Seven and Pelco Integral or Digital Sentry Product Line Pelco, TAC INET Environment I/Net Seven Pelco Integral or Digital Sentry DVR CCTV Cause Send back a Integral DVR and it comes back as a Digital Sentry or confusion revisions of I/NET Seven and Pelco Integral of Digital Sentry Resolution This chart to clarifies which versions of I/NET Seven are compatible with which Pelco DVRs: For the latest products (after 2.31 revision) please visit Software and Firmware compatibility matrix for older versions of the traditional product lines which has the most recent Pelco compatibility.

Issue A Macro comes installed in the default directories with Menta.  This macro will create a PWM signal that can be used for a variety of purposes in Menta.  It will not, however, drive most industry-standard PWM hardwired actuators.  For information on this, see Pulse Width Modulated (PWM) outputs in Menta. Product Line TAC Vista Environment Menta PWM actuator Cause Creating an a pulse width modulated output. Resolution Go to Program Files > TAC Menta > Library > Macro Block Library > Miscellaneous > Function > PWM.aut and PWM.doc These two files will give you a PWM function for Menta and an explanation. In simulation mode it will appear that the PWM increments at very crude levels but when the application is downloaded the processor actually runs at less than 1 second increments. Download this application to a controller and connect up a transducer and vary the control signal to be comfortable with the performance. Use a PVR block to generate a manually controlled signal.

Issue What if an NPR 2000 goes away and never comes back even after cycling power to it? Product Line TAC INET Environment I/NET site Cause Cold starting an NPR 2000 is a common troubleshooting technique to clear up a number of communication problems that may arise. Resolution If said NPR stops communicating and doesn't come back no matter what, you should cold start it and do a software restore. (See that procedure in How to cold start an NPR 2000.)

Issue What do the HVAC, SEC, and INT options on the Continuum Security Key provide access to? Product Line Andover Continuum Environment Continuum Security Key Continuum Cyberstation Cause Unsure as to what restrictions these various Security Key Options place on the activity that can be performed and what can be viewed within Continuum. Resolution HVAC - Provides access to HVAC specific objects such as viewing BACnet controllers, creating BACnet objects and polling for new BACnet Devices. SEC - Provides access to viewing and creating Security specific objects such as Door, Area, and Personnel objects. INT - Provides access to all of the above. This key will be able to view/create both HVAC and Security related objects. Any Workstation with a SEC key will not be able to view any BACnet Devices or objects in the database and any with an HVAC key will not be able to view Security related objects in the database. For more information see Different options on the CyberStation security key.

Issue How is the time synchronized between the Automation Server and Xenta Programmable Controllers? If the time synchronization is offline, what can be done to correct this? Product Line EcoStruxure Building Operation Environment Automation Server Building Operation Workstation Cause Time Synchronization occurs between the Automation Server and the Xenta Programmable controllers during two events: When the Xenta programmable controller is commissioned. Periodically the time is synchronized (default 10 minutes, but configurable). For the time synchronization to work properly it is critical to ensure that the time zone of the automation server is correct and the date/time of the automation server is correct. Resolution Walk through these steps to troubleshoot the synchronization of the Automation Server and Xenta controllers.   Check that all Xenta devices are at software revision 3.74 or higher Check the local time of the Xenta programmable controller by accessing the properties of the programmable controller and using the "Xenta" property tab group. The local time is listed there. Check the time zone of the automation server. By default the "Factory time zone" needs to be changed for proper operation. Check the server time of the Automation Server in the Basic property tab of the Automation Server. Check Time Synchronization Interval setting of the LonWorks Network object under the advanced tab in the Xenta General section. Default is 10 minutes. Either wait for the interval to elapse or manually commission the controller to synchronize the time and check the local time of the controller to ensure it completed properly.   Note: Keep in mind that the time displayed time in Workstation reflects the time zone of the local machine. If you are logging into an Automation Server in a different time zone, the alarms and events will be displayed in your local time, not the time of the Automation Server's time zone. For more information on Time settings and Synchronization see Time Synchronization of the ES and AS.

Issue Personnel distribution shows error 5310 Product Line Andover Continuum Environment Cyberstation Cause Error 5310 (0x14BE hex) indicates a duplicate card number. Resolution Take a LAN capture of the distribution using Using WireShark to analyse communications on an Ethernet network and send it to PSS for analysis, a PSS engineer will decode the packet to extract the card number and card type that is being rejected as duplicate. Armed with the card number and type find the offending record in the DB and eliminate the duplication.

Issue Configuring the Xenta 102-AX to accept a 4-20mA CO₂ sensor input on Universal Input 3. A negative value is required on the CO₂ offset value, but it is not possible to enter a negative value. Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta 102-AX 4-20mA output CO₂ sensor Cause The Xenta 102-AX universal inputs are designed to work with a 0-5V input. The best option is to always buy a CO₂ sensor that is compatible. However, if 4-20mA CO₂ sensors have already been purchased and installed, they can be made to work. Resolution In this example, a 4-20mA CO₂ sensor with a 0-2000ppm range is assumed. In the Xenta 102-AX Plug-In > Hardware Configuration Tab, set Input 3 Selection to CO₂ Sensor Wire a 250Ω resistor across U3 and M. This converts the 4-20mA signal to 1-5V. In Vista Workstation, navigate to the 102-AX > UnivIn3_Sense. Open SCPToffsetCO2. This value needs to be -500, but negative values cannot be entered. To get around this: Change Value to 0 Change Scaling > Offset to 500. This alters the display of the offset value. Click OK. Open SCPToffsetCO2 a second time. The value is still 0, but it is being displayed as 500, due to the scaling offset. Change the value to 0 (because of the offset, 0 represents -500). Click OK Open SCPTgain. Set multiplier to 2444 Set divisor to 1000 Click OK. This value comes from 2000 (range of sensor) + 500 (offset) / 1023 Note: An input of 0V (a sensor that has not been wired yet) will result in an nvoCO2sensor value of 65535 (invalid). Also see Using a 0-10 volt CO2 sensor with a Xenta 102-AX to configure the Xenta 102-AX to accept a 0-10 volt CO₂ sensor input on Universal Input 3.

Issue Edit > Host Computer > Software Restore results in pop-up error "No entries in data base" Product Line TAC INET Environment I/NET Seven host Cause The network configuration does not have any entries saved in the database. Resolution Go to Edit > Host Computer > Network Configuration In the Link Summary window, find the correct Link. If the Cnf column has a plus sign (+) in it, then this link is not saved. If the correct link is not shown, reference Error: "No Entries in Database" for more information. Highlight the correct link and press "Save" With the correct link highlighted, click "Penetrate" Any controller with a + in the Cnf column has not been saved. Click "Save All" Hit "Close" on the Station Summary and "Close" on the Link Summary. There are now entries in your database. The software restores should now show the correct options. For instructions on performing a software restore, see How to upgrade bin and SAV files in I/NET controllers

Issue Getting error "Unable to find an object in the database.Root\FolderName\OldAreaName" when creating new Personnel, in Personnel Manager. Following a change to Area names, the Personnel Profiles no longer contain these changed Areas. Product Line Andover Continuum Environment Continuum 1.81 and above Cause Do not rename Areas without removing/replacing them from the Personnel Profile. Resolution Always remove Areas from Personnel Profiles before changing the Area name, then replace Area If you simply rename the Area without removing that Area from the Personnel Profile, then the Personnel Profile will either get corrupted or the changed Areas will get removed from the Personnel Profile. If the Personnel Profile is corrupted then it needs deleting. Delete from Personnel Manager, if the corruption is such that it cannot be deleted from Personnel Manager, see Cannot delete personnel profiles Once the Personnel Profile deleted, recreate as required.

Issue A multi-port router can be represented in a LonMaker drawing using several LonMaker Basic Shapes routers if the internal structure of the L-IP is understood. Alternatively, Loytec provides a stencil library of their routers that can be used. Product Line TAC Vista Environment LonMaker Visio Loytec L-IP routers L-IP-3ECT, L-IP-1ECT, L-IP-33, L-IP-3333, LS-13333, LS-11333, LS-13300 LS-33300, LS-33, LS-13, LS-11 Cause The LonMaker Basic Shapes router only represents a single port router (near side/far side). To represent the 2, 3, or 4 port L-IP routers requires multiple basic routers with different channel types, or one of the device templates from the Loytec Shapes stencil library. Resolution Download the latest Loytec Shapes 5.0 stencil library here. Extract the contents of the .zip file Move the LoytecShapes.vss files to C:\LonWorks\LonMaker\Visio Note: This is assuming that LonMaker is installed at the default location on the C: drive Start LonMaker Go to File > Stencils > LoytecShapes Select the router part number that matches the physical device. The appropriate channels for the router will be added along with the shape. Each port can now be commissioned separately. See also How to Configure Lonworks Network Interfaces to Communicate on the IP to a Loytec L-IP Router using the Echelon driver for more information. 

Issue Stand-alone Vista 5 applications and Licensing Product Line TAC Vista Environment LMGRD Menta Save Menta View Demo Vista 5.x Cause No license found lc_checkout Failed: Network connect to THIS_HOST failed. The license file indicates THIS_HOST, and the server is not running on this host. Resolution Running Menta, Xbuilder or any of the Vista Applications as a "stand-alone" application i.e. no Vista Server/Workstation, requires a download of the License Server from Exchange Online. Navigate to Product Zone > TAC Vista > Vista Software > TAC Vista 5.0.X > Downloads. Ensure the version matches (5.0X) the version of Vista installed. For instruction set for licensing a Vista Software Entitlement: See How to Host a Vista Site License. Ensure the license is placed in C:\Program Files\TAC(Schneider Electric)\License Files folder. Launch the licensed Vista software of your choice, typically Menta or Xbuilder. When prompted, select "Use a License Server" option. Specify the Computer name that the server exists on, typically the Local Computer Name, or "localhost". To assist in troubleshooting additional Licensing problems: See [Video] Vista 5 Macrovision/Flexnet Licensing: Lmtools diagnostic utility overview See License troubleshooting in Vista 5.1.8 or greater See TAC Vista 5.0 to 5.1.7 license does not work after installation

Issue What is the maximum character length a value (object) name can have? What is the maximum character length an alarm name can have? What is the maximum character limitation on the Description? What is the maximum character limitation on the Alarm and Reset messages? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation (all versions to 1.3 SP1  (1.3.0.10100))  Cause Require an understanding of what character limits are applied within Building Operation Workstation Resolution There is no documented limitation, the following numbers are those that have been tested: An object and alarm name: 1900 character limit. An object and alarm Description:  No found limit here, either in entry or saving. An Alarm message and Reset message - no found limit here, either in entry or saving. It is important to note these are limitations on StruxureWare objects only, when the actual object is also represented in another device, like a BACnet or LON device, then there may be restrictions at that device. A b3 is an example of this where you can make the object name with 1900 characters but the BACnet name will be limited to 32. Also refer to StruxureWare Building Operation object names limitation on what characters are allowed to be used.

Issue The controller installation guides detail how to display the values in Water Column (WC), but how can this be displayed in metric units? Product Line Andover Continuum Environment Infinet controllers (i2865 & i2865-V, i2866 & i2866-V , i2885, i2885-V, i2850 &i2853 ) BACnet controllers (b3865 & b3865-V, b3866 & b3866-V , b3885, b3885-V, b3850 & b3853) Cause A conversion to metric units (Pascals) is needed. Resolution i28xx type of Infinet Controller has 0-2" WC (Water Column) range which corresponds to 0-2V so the input value can be read directly in WC. The 850 has a single airflow sensor on channel 8 The 853 has two airflow sensors on inputs 7 and 8 For 865, 866, and 885 the airflow sensor is on Input 7 Always use input type Voltage Set the units to Pascals The following conversion can be used on the conversion line: ElecValue * 500 The i28xx-V type of Infinet Controller has 0-1" WC (Water Column) range. For 865-V, 866-V and 885-V, the airflow sensor is on Input 7 Always use input type Voltage Set the units to Pascals The following conversion can be used on the conversion line: ElecValue * 250  For controlling the Damper motor output Create an Infinity Output point of type Triac on Channel 1 It can then be opened/closed like any other Triac output with the use of On, -On or Off commands. Also see Setting up the override value to show the damper feedback on an i2/B3 866-V for details on reading the damper feedback on the i2/b3886-V.

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

Issue When using the Modbus TCP/IP XDriver will the data type used by a 3rd party system be supported. Product Line Andover Continuum Environment Modbus TCP X-Driver Cause Not every possible format of data is included in the Modbus IP X Driver. Resolution The following data formats are supported in version ModbusTCPIP_2ndGen200018.xdr: Unsigned Integer 16 bit Signed Integer 16 bit Reverse Floating Point 32 bit Floating point 32 bit Long Integer Unsigned 32 bit Long Integer Unsigned Swapped 32 bit If the products used have a different data format then this would require a new development of the X Driver, please see Will Continuum communicate with a third party system? for contact details. Also ensure that the X Driver point type created (Numeric, Input, Output) is supported by the function code used. Check out the X Driver manual for the list of point types supported by each function code. For example Function code 3 can be used with Numerics and Outputs, but not Inputs.

Issue Options are needed for truncating large amounts of extended log data, but with the ability to report on that data Product Line Andover Continuum Environment Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause Extended logs data can cause the Continuumdb to get large and needs to be truncated with the ability to continue to report from the old data Resolution Set up automatic truncation of extended logs (See the Check Purge Interval section in Stand Alone Continuum using SQL Server 2005 Express is not purging the ExtendedLog table) Ex. Year, 180 days Make a copy of the Continuum database on the existing server. In this scenario you would have ContinuumDB and ArchiveDB. Use one of the Cybers via Workstation Initialization) to temporarily switch to the ArchiveDB for reporting purposes and then switch back. Purchase the Extended Log Archiver uses a separate db for the archived data and truncates data from the Continuumdb automatically. For more information email COE@Buildings.Schneider-Electric.com

Issue A Deny Entry Tenant Message is given instead of a valid card read. Product Line TAC INET Environment I/NET Seven AMT Cause The Deny Entry Tenant message is delivered when the credential read is not known to the controller for any of the following reasons: The door being read is not part of the individuals tenant. The SLI does not have the correct database Card Translation is incorrectly enabled/disabled in the door editor There is a hardware error with the Card reader. Resolution General Steps: Determine if the issue only happens to a single individual or a group or all cards. Select Access>Tenant. Verify that the door has been added to the correct tenant(s) Select Edit>Individuals and browse to the card(or a test card) in question. Verify that the card has the been added to the door correctly. Follow the directions in How to force a download of card data to force a download. If this fixes the issue, go to the "SLI does not have the correct database section" In AMT, select window options and add the message column to the window Find a Deny entry tenant message and see if the message column matches up with Hex card number for the badge that was read. If all you get is a scrambled number, There is probably a hardware error. Verify Card Translation is Enabled (this section assumes you are using large card number format) Select Access>Doors Modify the door in question Check the box next to "Card Translation". If this option is not available you will need to flip Dip switch 7 on the SCU Compare this setting to a few other doors on the system. Thy should all have the same setting Hardware Error The easiest way to prove a hardware error is to plug a spare card reader directly into the DPU or SCU. If the problem is immediately solved replace the field reader. If not, try unplugging other readers on the controller and see if the problem goes away for that reader. It is possible that the controllers power supply is no sufficient to power the reader. Use an external power supply instead. Various known fixes for SLI database Errors: Take the SLI to it's boot state and restore bin file and database files from the Server If you are using I/NET 2.15-2.21, upgrade to 2.31 Insufficient memory: The SLI will allocate memory for all possible individuals in a tenant regardless if they are used or not. For example, if the site has only 500 cards, but the tenant is set to 32000 individuals, this will use the same controller memory as a site with 25000 individuals.  Reducing the number of individuals allocated in the tenant has been shown to clear up Denied Entry Tenant messages. System traffic: In I/NET 2.31 and above, the filemaster or server will indicate when badge data is being downloaded on a status bar in the bottom right hand corner of the screen. If this indicator is constantly showing downloads, it is due to poor system communication causing constant polling of the database.  Follow these steps to fix this issue. Turn Automatic DPU restore off on all links and wait for the download messages to stop. (this is done by selecting Edit>Host Computer>Network Configuration, then modifying each link) Wait for the automatic downloads already requested to finish. Re-enable Automatic DPU restore on each link, one at a time. Wait for the system to finish individual downloads before moving on. When you find a link that take an excessive amount of time (compared to others) to finish downloading, troubleshoot that links controller LAN wire.

Issue When alarm is triggered in the controller sometime the alarm will immediately be displayed on the Alarm View as expected, you trigger the same point alarm a few times and some times there is a delay of up to a minute or two before the alarm shows up on the Alarm View. Looking at a list view of the alarms you can see the difference between the time stamp and the time of log Product Line Andover Continuum Environment CyberStation All controllers Cause The controller has been taught about CyberStation whose network ID has been since changed. Resolution Use a PE program to find out from the controller's perspective what it has been taught. If the controller contains entries in its table that it should not have, then reload the controller to remove them. See Visibility into a controller's list of peer controllers and Cyberstations following a teach for a sample PE program.

Issue If using TAC Informer (Product development within Australia / New Zealand region), product has no further support and now longer works with I/NET Seven 2.40 or higher.  Receive either of the following errors: * I/Net Alarms     'Alarms' I/Net connect failed - I/O Server create failed OR * I/Net Alarms     'Alarms' failed to start - I/O Server create failed Alternatives with sending SMS alarms with I/NET Emailing alarm solutions for I/NET  Product Line TAC INET Environment I/NET Seven 2.4x or above TAC Informer (Pager TAP) - Product sold within Australia / New Zealand region. Cause Application developed by Australia (support for this product ended in 2005) now does not work with I/NET 2.40 or above. There are a few alternatives and possible workarounds, but this product is no longer supported. Resolution There are couple of alternatives: Currently the TAC Informer software will work with 2.31 or lower, so you can use these versions of I/NET Seven software. It may be possible that loading the I/NET 2000 compatibility files from the I/NET Seven CD may allow connection to the current INetIoSrv.exe file. The steps for this are as follows: Copy DbSrv2K.exe and INetIoSrv2K.exe from the CD “Support \ INET2000_Backward_Compatibility” directory into I/Net Seven's Program Files directory. From a DOS command and from the C:\Program Files\Inet Seven\ folder; Register both programs from the command line: DbSrv2K /regserver INetIoSrv2K /regserver Note: If you need to unregister these files use the following syntax: /unregserver  Alternatively it is recommended to use the email feature within Xenta 527 Web Server (Refer to Troubleshooting sending emails from a Xenta Server) which can then be configured with a third party mobile message service provided by Redcoal (www.redcoal.net).  They provide a set of simple Desktop applications which allow SMS to be sent via desktop application or via email.  Click Here for further information.  Customer will require to setup an account and charges do apply. Note: This provider only operates in Australia.  Third alternative is to use a solution provided by a company called NotePage, product name is PageGate - Refer to PageGate I/NET Seven Programming Instructions for further information.  Benjamin Roswall has developed a tool which is available on the community: TAC INET Notifier.  The program will look for alarm events in the SQL database, and process then according to the settings. The program has its own alarms list, and if the service is stopped, it will save the alarm list so that only new alarm events are processed when the program comes back online. For emails you just need to know your SMTP server configuration, and for SMS it uses the SysManSMS program that has a SMTP to SMS feature. Also, the program can write to a text file, and SysManSMS can then look for this text file. Please note Schneider Electric do not endorse this product but provide this option as a workable solution. All support issues related to these products should be directed to the developers / providers of the respective software.

Issue Can the AS, work independently or together without an ES? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site, any version Cause Are bindings or other communication between two AS possible if there is no ES?  Resolution The AS, is designed to work independently or in conjunction with others, or in conjunction with an ES.  Points, Bindings, Schedules, etc. can be setup on the AS using the Workstation. With the ES service stopped, the Points, Bindings, etc. on the AS continue to reflect the values on themselves or if the Bindings interlink between multiple AS.  For multiple AS configuration check the AS are listed in the Communication tab of each other. From your workstation highlight the AS and the tabs shown are List View, Device Discovery, Date & Time, Communication, and Properties. Under Communication the other AS devices should be listed as well as the ES. For information on a Automation Server alone at a site and licensing requirements, see License requirements for AS alone at a site