Notifications

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Building Automation Knowledge Base

Issue What are the limitations of using ID Works with I/NET Seven? Can a "begin time" or an "end time" be assigned to a temporary card from ID Works (Card Access Control Data Entry)? Can an individual’s record be made a "DPU Resident" from ID Works? (I/NET Seven 1.0x) What is the format of the CardID entry in the ID Works system? Can assign PIN numbers be used with an ID Works system? Product Line TAC INET Environment I/NET Seven ID Works - For details of what version of Datacard ID Works Software integrates correctly with I/NET Seven refer to Datacard ID Works Software versions for integrating with I/NET Seven. Cause I/NET Seven provides support for Datacard ID Works identification software. I/NET Seven provides a database view specifically designed for use with ID Works. This view contains tenant and individual data used by the ID Works Video Badging application. It allows you to add individuals, assign key/cards, edit individual parameters, or even delete individuals. The limitations described below are imposed anytime that you use ID Works to modify your I/NET Seven access control system. Resolution The limitations described below are imposed anytime that you use ID Works to modify your I/NET Seven access control system. ID Works does not allow you to add or modify multiple cards for a single individual. ID Works does not allow you to remove a card from an individual without deleting the individual record in I/NET Seven. You cannot disable an individual’s card without disabling the individual in the I/NET Seven. You cannot create a new group or a new tenant from within ID Works. You cannot assign a begin time or an end time to a temporary card from ID Works – only dates can be entered. I/NET Seven will use a default time of 00:00 (Midnight) on the dates specified. If you need to change this default time, it requires you to go into I/NET Seven > Access > Individuals editor. You cannot make an individual’s record be DPU resident from ID Works. You cannot assign a decimal card number to an individual from within ID Works. The format for this entry has to be a hexadecimal number. You cannot set and individual’s APB scheme (i.e., hard, soft, or graced antipassback) from within ID Works. You cannot assign a PIN to an individual from within ID Works. These can be access via the I/NET individual editor. For further information refer to TCON301 Chapter 5.

Issue From time to time TAC Vista Server stops communicating with LonWorks devices and needs to be restarted. Product Line TAC Vista Environment TAC Vista Server LonWorks Cause There can be various reasons for this. One of the reasons can be, that one or more devices is flooding TAC Vista Server with communication, and the communication finally stops. Among other things, this can be due to one or more TAC Xenta's suffering from the rare memory fault issue described in TAC Xenta 401 - Rare Memory Fault Issue - TPA-MALI-09-0011.01, or that the system program in the TAC Xenta device has become corrupt. To identify the issue, make a communications log as described in Start TAC Vista Communications Log, and open the log with the "TAC Vista Comm. Log Decoder". Filter on "C1" messages, and check if there's extensive communication from one or more devices. If that's the case, you have identified that file transfer loop is the issue. Resolution The first thing to try, is to update the system program in the Xenta. Follow article Download an .MOT file into a Xenta Programmable controller for instructions on how to do that. If that doesn't work, replace the Xenta device(s) causing the massive file transfer.

Issue Renaming a Vista Server. Product Line TAC Vista Environment Vista Server Cause The Vista Server name will default to the PC name where the database is created. To rename the server to any desired name of fewer than 40 characters. This can be customer-appropriate or more generic than an individual's PC name; follow the steps below. Resolution Shut down Vista Server Open Vista Server setup and navigate to the Vista Database tab. Enter the desired server name in the text field "Rename Vista Server to" Click OK Restart Vista Server. Within a few seconds, the server's name shown at the top of the window will be updated to reflect the new name. It will also show up in the folder view of the Vista Workstation. Note: Changing the Vista Server name after graphics have been created and bound will break the binding path for all points. To fix up the binding paths for all graphics at once, use Change References, as shown in Change all bind paths for all bindings on a TGML or OGC graphic at once.

Issue How can I determine what version of SQL I/NET is using? What version of SQL is installed on the I/NET PC? Product Line TAC INET Environment I/NET Seven 2.10 and above For previous versions of I/NET refer to How to determine the SQL version you are running with I/Net Seven. Cause To find out what version of SQL is installed and used by I/NET Seven site PC. Resolution A new feature was introduced in I/NET Seven Revision 2.10 that allows you to view both the I/NET revision and SQL revision installed. To view this all I/NET applications and the IO Server must be shutdown before performing the following steps: Start DBCreate >Start> All Programs> INet>DBCreate Login screen is shown, select either Windows login or enter the SQL Server Authentication details and click OK Right-click on the Title area shown in red below: After Right-clicking, select from the menu options About... The About DBCreate screen will then be shown and you can see both the I/NET Seven Version and SQL Versions as shown and highlight below: For I/NET Revisions prior to 2.10 then refer to How to determine the SQL version you are running with I/Net Seven on how to view what version of SQL is installed.

Issue DBCreate database restore fails with error message: "The backed-up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database. [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE is terminating abnormally." Product Line TAC INET Environment I/NET Seven SQL Server 2000 all editions and SQL 2005 all editions Cause It is not possible to restore a SQL Database which was backed up using SQL 2005 back into a SQL 2000 database. Resolution The simplest method to rectify this problem would be to uninstall I/NET and SQL (Refer to Procedure for uninstalling I/NET Seven on a stand-alone host on how to do this) and then re-install I/NET using SQL 2005. The second method would be to upgrade the installed MSDE Default instance to SQL 2005 Express. There is a published white paper from Microsoft on this and is attached here: MSDEtoSQLExpress.doc. Refer to the steps on page 11 to 14. The SQLExpress installation file is available on the I/NET CD under the folder SQLExpress\.SQLEXPR32.EXE. After performing these steps its advisable to run up DBCreate and upgrade the SQL database.

Issue Which licenses are required when TAC Vista is used in a virtual environment? Environment TAC Vista Cause Running a TAC Vista system in a virtual environment. Resolution No special end user licenses are necessary. License requirements are the same as if run in regular environment. Also, please see: Problems installing Vista on virtual PC and Running Vista software on an emulated environment for more details on the subject of running TAC Vista in a virtual environment.

Issue In order to make page links between different I/NET graphic folders work fine, the same folder structure needs to be created manually in EcoStruxure / SmartStruxure. Refer to Converting I/NET graphics to TGML using the "Create Source Tree" option to realize this. Product Line EcoStruxure Building Operation, TAC INET Environment EcoStruxure / SmartStruxure 1.4 or higher I/NET Cause The I/NET graphic folder structure will not be created automatically before SmartStruxure 1.4.0. Resolution Starting in version 1.4.0, there was a new feature called Data import for I/NET graphic. Using this feature, all the converted I/NET graphic folders structure can be imported at one time without any need for manual work. Here are the steps to make it work: Convert the I/NET graphics according to Converting I/NET graphics to TGML using the "Create Source Tree" option, but do not create the folder structure manually in EcoStruxure / SmartStruxure. Create the default Inet Graphics folder by right clicking on I/NET Interface-->New. Right click on Data Import and choose the root folder of all of the I/NET graphics. Click OK. Data importer will check all the file names and bindings. If any error happens, check and fix it before importing again. (Currently apostrophe is not supported in SmartStruxure. Change the name and relative link and do it again. It may be fixed in later version) Check whether all the bindings and links work fine. Important: Currently this feature doesn't support export/import in SmartStruxure. It will fail to import if any sub folders are contained under INET interface. This may be fixed in later version. The workaround is to still create the whole structure according to Converting I/NET graphics to TGML using the "Create Source Tree" option.

Issue Have Cyberstations and BCXs and/or 3rd party devices on different subnets Product Line Andover Continuum Environment Cyberstations BCX 40xx 3rd Party MSTP/IP BACnet Cause Unable to communicate with B3 devices or get B3 point values. Resolution Review LAN configuration. Each separate subnet requires a single BBMD for communication. See BACnet documentation on line via Cyberstation or "Introducing BACnet" document in Cyberstation. See Simple BBMD setup.

Issue Regional settings might differ when TAC Vista server runs as a service. Product Line TAC Vista Environment TAC Vista Server set to run as a service Cause If TAC Vista Server is configured to run as Windows service it might have different regional settings. This is because the TAC Vista server service needs to be configured to use a specific user account (See Registering/Unregistering TAC Vista Server as a Windows service). One common symptom would be that the date and Time stamp might have another format. Resolution To make sure that TAC Vista server is using the correct regional settings: Log on to the system once using the credential that TAC Vista server is configured to use Check the regional settings for this account.

Issue The TAC Xenta operator panel will not display controllers on the network even though it has the correct StruxureWare Domain ID entered and is set to manual mode. Product Line EcoStruxure Building Operation Environment TAC Xenta Operator Panel StruxureWare Cause StruxureWare Building Operation sets its LonWorks Domain ID to a decimal value. The TAC Xenta Operator Panel needs the hexadecimal value in order to operate properly. The decimal value must be converted to hexadecimal. Resolution In order to locate the domain ID of a LonWorks Network, see How to locate and change the LonWorks domain ID. Converting a decimal value to hexadecimal using a calculator Open the calculator on your computer. If Windows go to Start > All Programs > Accessories > Calculator. In the View menu, select Programmer. Enter in the decimal value of the domain ID. Select the Hex button on the left side of the calculator. The domain ID has been converted to hexadecimal. In the example, the domain ID 0B should be entered into the operator panel and set to manual mode.

Issue Need help with programming Need help to make graphic Installation questions Forum Environment BMS Security Video Cause A great way of getting help with various application programming and graphic making is to spread knowledge between all the great technician out there. A forum exist for this and people worldwide that works with SE Solution share their knowledge here. Resolution Please enter the forum by the link below. http://community.se.com/welcome

Issue Created a BACnet digital output under the BACnet Interface in the Automation Server but the Out of service property indicates 'True' and get the error 'Property value out of range' when attempting to set the out of service to false. Product Line EcoStruxure Building Operation Environment WorkStation Automation Server - AS BACnet Interface Cause BACnet output must be associated with an IO Bus output. Resolution See Associate AS BACnet Interface IO points with points on the IO bus in SmartStruxure 1.4 and above for instructions on setting the associated value.

Issue What are the differences between the IAC 400 and the IAC 420 controllers? Product Line Field Devices, Other, Satchwell MicroNet, Satchwell Sigma Environment IAC 400 IAC 420 Cause The IAC 400 controller is obsolete and its replacement is the IAC420. Resolution Hardware differences; The IAC 400 has 3 Temperature, 2 Analogue and 1 Digital input, where as the IAC 420 has 6 Universal inputs. Communications differences; The IAC 400 controller uses terminal 3 to earth the communications cable screening, on the IAC 420 the screening must be connected to a good earth and not terminal 3. Tables and offsets; Because the IAC 420 has different inputs that tables and offsets are changed, please review IAC Controllers - Tables and Offsets. IAC 400 Wiring details. For the full data sheet please click HERE. IAC 420 Wiring details. For the full data sheet please click HERE.

Issue When installing the TAC Vista OPC server it doesn't show up as a Windows service like it should. Product Line TAC Vista Environment TAC Vista OPC Server Cause A valid license for the TAC Vista OPC server must be installed before installing The OPC server. Resolution Uninstall the OPC software Install a valid license for the TAC Vista OPC server. Reinstall the OPC software For more OPC Server issues please see Vista OPC Server Installation and Known Issues.

Issue When a MPM is replaced on a BACnet IP network, a "Duplicate network identifier" alarm is generated Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment MPM Automation Server Cause If the BACnet name and instance number in the new controller is not exactly the same as the original MPM, the Automation Server will consider that an additional device has been installed and an alarm will be triggered stating that the new device has the same BACnet ID as an existing device. Resolution Steps to replacing a MPM to prevent the Duplicate ID alarm being triggered: When replacing the original MPM, note the BACnet name and Instance ID. Install the new MPM and enter the same BACnet name and Instance ID. Refer to BACnet device can't be discovered due to duplicate name for more information about duplicate BACnet names.

Issue Update to available documentation. Product Line EcoStruxure Building Operation, Satchwell MicroNet Environment Windows 7 32/64 bit Cause Clarification of supported communication protocols and devices. Resolution Computer running Windows 7 32bit or 64bit. Visio software installed must be 32 bit version. VisiSat runs as a 32 bit application. SNP Via computers RS232 communications port. Via RS232 provided by USB to RS232 converter. Via RS232 provided by PCMCIA card to RS232 converter. Via RS232 provided by Express card to RS232 converter. IP tunneling through Xenta 555/731 AS/AS-P LAN network. Remote site connection. NCP Via computers RS232 communications port. Via RS232 provided by USB to RS232 converter. Via RS232 provided by PCMCIA card to RS232 converter. Via RS232 provided by Express card to RS232 converter. IP tunneling through LAN network. Remote site connection. ARCnet Via computers RS232 communications port connected through null modem lead to an MicroNet Interface Unit. (MN50-MI-ARC). Via PCI120U-485 PCI card (This card was made by Contemporary controls but is no longer). The card was replaced by the USB22 Series. (USB 2.0 to ARCNET adapters) These USB22 adapters do not work with VisiSat. IP tunneling through LAN network. Remote site connection. LON Not supported with Windows 7 64bit or 32bit. The latest documentation for VisiSat can be downloaded, see Download latest VisiSat Data Sheets, Engineering Guides, Installation and User Guides, and Release Notes.

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 What are the limitations of Building Operation Web Services? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Version 1.3 Cause Due to the XML response rate (XML file information send to Building Operation), it has some limitations. Resolution General Guide in the Technical Reference Guide: The limit for the whole XML response is 100 kb, which includes manually created values. The limit for a string value is 10 kb, which includes manually created values. The maximum number of values created in the Web Server interface is 200. The recommended limit for XML elements in the Web Service interface is 100 The recommended number of Web Service interfaces in an Automation Server XML elements at a polling rate of 60 seconds. is 2. Additional Information: Maximum number of Web Services in an Automation Server Also refer to Architectural Guidelines for your respective version in use.

Issue Vista locks up randomly and displays application crashes. Investigating the Windows Event log shows the following errors pointing to tacldv32.dll. For more information on Windows Event Log, see Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes. Faulting application tacos.exe, version 0.1.0.0, faulting module tacldv32.dll, version 1.0.0.1, fault address 0x00007310 Product Line TAC Vista Environment Vista Server LNS Communication Port Large LNS network, or many smaller LNS networks Orion Stack Cause The DLL file, tacldv32.dll, is responsible for managing communications through an LNS communication port. If that is being overwhelmed with information from too many devices on the port, this DLL will crash. If the number of networks is only one and the database size is reasonable then the problem can be caused by a corrupted and non functioning LNS database.See Also Echelon LNS Utilities LNS Database Validator. Resolution If the number of networks is high then LNS communication must be managed by an Orion Stack, or NIC-852. This does not utilize tacldv32.dll and will stop the application crashes. If the number of networks is low, but the size of the networks is quite large, then it is also advisable to allow the Orion Stack to manage communication and will prevent the application crashes. If the number of networks is low and they are not very sizeable, then ensure that LNS database is working properly independently of Vista Server. If it has problems, investigate the LNS problems further, looking for any errors that can be searched on other articles. *Note that if you receive the tacldv32.dll error and are currently using an Orion Stack or NIC-852. There is a problem with the Orion Stack or NIC-852 installation or configuration. Hovering the mouse over the Communication Port objects in the TAC Vista Workstation should produce a pop-up window stating "Loytec Port". If it says "LNS Port", there will still be a need for using tacldv32.dll resource.

Issue Various issues have been observed regarding the use of the I/A Series R2 WorkPlace Pro or I/A Series G3 Graphics access. The following is a partial list of known issues caused by the Ethernet firewall built into the Trend Micro Internet Security Suite software: When attempting to install an R2 UNC license using the Admin Tool, the error "Unable to install license" is displayed. When attempting to connect to a UNC from the WorkPlace Pro tree, a "Cannot connect" error occurs. When attempting to access G3 graphics using the web browser, the user is unable to log into the station serving the graphics. When attempting to access R2 graphics using the web browser, the user is unable to display the graphics pages. When attempting to paste a .gif file to a UNC's remote library, WorkPlace Pro stops responding and must be closed with Windows Task Manager. When attempting to open a local station on the computer, using WorkPlace Pro, the Windows hourglass is displayed and the station never opens. This list will be updated as additional issues are encountered. Environment Computer running "Trend Micro Internet Security Suite" I/A Series R2 (Niagara) WorkPlace Pro software or attempting to use the computer to view I/A Series G3 (Niagara) graphics. Cause The I/A Series R2 software requires bi-directional communications over Ethernet port 80 unless the software has been user-configured to use a different Ethernet port. The Trend Micro Internet Security Software Suite has a built-in firewall that blocks incoming access to Ethernet port 80. The Trend Micro software does not allow this port to be unblocked because it considers web access to a "workstation class" computer as a security risk. Resolution The best solution to this issue is to use a different Internet Security software package on the computer that does not block the use of Ethernet port 80. One approach is to use the "Server" version of Trend Micro Internet Security instead of the "Workstation" version. Since port 80 is typically used on server systems as the IIS (Internet Information Services) access port, the Server version of the software does not block that port. The alternate solution is to configure the I/A Series R2/G3 (Niagara) software to use a different Ethernet port for HTTP communications and Web services. This change would need to be made in the R2 or G3 software installed on the computer as well as in every UNC or ENC being accessed from this computer. See New installation of the I/A Series (Niagara) R2 WorkPlace Pro software cannot connect to existing UNC for more information.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

ID Works Limitations when configured with I/NET Seven

TAC Vista Server stops communicating with LonWorks devices

Rename a Vista Server

DbCreate now displays the revision level and description of SQL in the Help About box

I/NET DBCreate database restore fail

TAC Vista end user licenses in virtual environment.

Import all converted I/NET graphic folders into EcoStruxure at one time

Cannot see B3 Controllers

Regional settings might differ when TAC Vista server runs as a service

Xenta Operator Panel will not recognize Xenta controllers in a SmartStruxure network

BMS Application assistance

BACnet output point under the BACnet Interface of Automation Server indicates out of service

Differences between IAC 400 and IAC 420 controllers

After installing TAC Vista OPC server it does not show up as a Windows service

Duplicate ID alarm when replacing a MPM on BACnet IP

Supported communications options when running VisiSat software on Windows 7

Techniques to debug Plain English programs

StruxureWare for Building Operation Web Services Limitations

Vista lock-up caused by tacldv32.dll crash

"Trend Micro" Internet Security Suite causes communications issues with I/A Series R2/G3 (Niagara) software

Building Automation Knowledge Base

Related Forums

This is a heading