Building Automation Knowledge Base

Issue Transferring an I/NET Seven system from one PC to another Product Line TAC I/NET  Environment I/NET Seven Site Cause Customer needs to transfer I/NET between two computers Resolution Perform the following steps: Install I/NET Seven on the new PC. Using DBCreate.exe, create a backup of the I/NET database. Copy the backup to the new PC and restore it using DBCreate. If the database needs to be upgraded it will prompt you.  Proceed with the upgrade.  Copy the save files, graphic pages, archives, any custom reports, custom symbols, and custom BIN files (ICI bin files) to the new PC using the same directory path as the previous PC to guarantee that graphic links will still work. The following are default paths for these files assuming it was not an upgrade from I/NET 2000. If it was an upgrade from I/NET 2000 please consult TCON298 the Getting Started guide which includes I/NET 2000 paths. Default location for Archives: C:\Program Files\INET Seven\Arch\ Default location for BIN Files: C:\Program Files\INET Seven\Data\ Default location for Reports: C:\Program Files\INET Seven\Reports\ Default location for Save Files: C:\Program Files\INET Seven\Sav\ Default location for Bin Files: C:\Program Files\INET Seven\Data\ Default location for Graphics: C:\Program Files\INET Seven\ Take a screen capture or write down the active configuration profile in I/NET configuration and manually fill this information into I/NET configuration on the new PC and make it the active configuration profile. Transfer the communication medium to the new PC (serial cable or Ethernet cable) and if communicating via NPR’s set the IP address of the new PC to match that of the old PC and remove the old PC from the network to avoid IP address conflict. Start up I/NET, login, and edit the Host Computer->Network Configuration to verify that the PC is communicating with the controllers.

Issue TAC Vista and Peripheral Software Installation Outline Product Line TAC Vista Environment Microsoft Windows 2000/XP (Microsoft) LonMaker (Echelon) Microsoft Visio PCLTA-10/PCC-10/PCLTA-20/SLTA-10/PCNSI Adobe Acrobat  LNS  lmw31.exe lmw313U1.exe LNS3SP8.EXE LNSSP8U1.EXE HASP device driver h4_hinstall hdd32.exe Privilege Licenser 2.01 Aladdin Privilege Administrator 2.01 taclicense201.exe taclicense202.exe .NET Framework 1.1 TACVistaConfig1.2.0 .NET Framework 1.1 SP1 Microsoft SQL Server (MSDE)2000 SP4 MSXML 4.0 MDAC 2.8 Vista Server IV WorkStation TAC ToolPack 4.X   Cause The correct installation procedure for Vista IV and necessary peripheral software. Resolution Below is an outline that can be followed to install Vista in the proper order. Each "*" denotes a software package followed by the associated files/programs that are included. Depending on your specific application, some of the software may not be needed. For example, a Vista Classic network will not need LonMaker. Call Tech Support if you have any questions concerning the software needed for your application. *Microsoft Windows 2000/XP (Microsoft) *LonMaker (Echelon CD) LNS Utilities: Microsoft Visio, PCLTA-10/PCC-10/PCLTA-20/SLTA-10/PCNSI (only if using an Echelon LNS interface), Adobe Acrobat (if you don't already have it) *Update LonMaker to 3.13 and LNS to 3.08.05 (TAC Extranet) lmw31.exe, lmw313U1.exe, LNS3SP8.EXE, LNSSP8U1.EXE *HASP device driver utility (TAC Extranet) h4_hinstall - MUST Execute from a Command Prompt! or... hdd32.exe if using Windows Server 2003 *Privilege Licenser 2.01 - "taclicense201.exe" or 2.02 - "Privilege Windows XP crash hotfix" (TAC Extranet) *.NET Framework 1.1 (Microsoft) *TACVistaConfig1.2.0 (TAC Extranet) .NET Framework 1.1 SP1, Microsoft SQL Server (MSDE)2000 SP4, MSXML 4.0, MDAC 2.8 (Reboot) At this point you could be prompted to choose which type of Licensing to be used. Select which option is best for you, the Site License (Order Entry Department), 30 Day Demo (TAC Extranet), or Engineering dongle. This will write the appropriate license files to the Privilege License Server. *Vista Server 4.X with WorkStation (TAC Extranet) (Reboot) *TAC ToolPack 4.X (TAC Extranet) If you encounter any errors during the installation process, be sure to make a note of specific errors received so Technical Support can better troubleshoot your issue. A simple way to record errors are to capture a "screenshot" (Ctrl+PrintScnr). The screenshot can then be pasted (Ctrl+V) into Paint a text editor like wordpad for later reference. Note: Beginning 2012, PSS will no longer support the Privilege License System. The Tamfs26 Server will be retired along with TAC License Server software. It would be wise to inform the customer of this important information to plan for future upgrade in the event that their site license has issues.

Issue Time Zone Database shows +0 for all time zones when the platform date is in 2016. IA Series G3 version 3.6.407 IA Series G3 version 3.7.108 IA Series G3 version 3.8.41 Product Line TAC IA Series Environment IA Series G3 versions 3.6.407, 3.7.108, and 3.8.41 Cause This error appears when listing the contents of the Niagara Time Zone database where the Time Zone Database shows +0 for all time zones when the platform date is in 2016.  The issue is related to an error within the 3.8.41 baja and hx modules and only affects the display within the Platform view only.  The actual behavior and operation of the Time Zone remains accurate.  Prior IA Series G3 versions (e.g. 3.8.38, 3.7.106, and 3.6.406) or earlier will not exhibit this issue. Resolution Download and upgrade the baja and hx modules available in the latest consolidated patch files. baja 3.6.407.3 (or higher) and hx 3.6.407.1 (or higher) baja 3.7.108.3 (or higher) and hx 3.7.108.1 (or higher) baja 3.8.41.2 (or higher) and hx 3.8.41.1 (or higher) The consolidated patch files are available for download on the Buildings Download Center.  Login to the Schneider Electric Buildings Download Center and enter Consolidated_Patches in the search area (reference Latest consolidated patch files for I/A Series G3 maintenance builds with details).  Download and install the appropriate patch for the version.

Issue Viewing the routing tables on a PC using I/NET Seven Product Line TAC INET Environment I/NET Windows XP Cause Need to debug the I/NET routing table Resolution Viewing the I/NET Routing Table Select Start>Run Type "regedit" and press enter Browse to HKEY_LOCAL_MACHINE>SOFTWARE>CSI – Control Systems International>I/Net 2000>Configurations. If you are using 64 bit operation system, the path should be HKEY_LOCAL_MACHINE>SOFTWARE>WOW6432NODE>CSI – Control Systems International>I/Net 2000>Configurations Select the folder corresponding to the active configuration profile Double Click on the parameter "DebugTables"   Change the Value to "2"   Click OK Close the Registry Editor Restart the computer To view the Routing Tables, right click on the I/O Server and select "Show Tables"  

Issue Direct substitute for the obsolete CSI Lini-Temp sensors Product Line TAC INET Environment I/NET Cause Need a part number to replace a discontinued part Resolution Yes, there is a direct substitute for the 2-wire and 3-wire versions of the old Lini-Temp sensors. The company is ACI (Automation Components Inc.). For this substitute, use the ACI/592-10K Series sensors attached. Their website is located at http://www.workaci.com/. If you are not sure what ACI Product matches the old CSI product, their Customer Service or Sales Engineers are knowledgeable in the CSI Product line. They will be glad to help you with your selection.  

Issue Using an EP1501 as a controller and unable to add reader one. Product Line Access Expert Environment Access Expert Server 2012R2 and above Cause Using an EP1501 as a controller as well as a card reader controller. Resolution To resolve the issue, please follow the steps listed: Wire the RS-485 bus to reader port 1, Clock and Data Wire the reader being used on port 2 When programming the reader on the device, it needs to be added as Reader 1 The Door Address needs to be set as 0 as well

Issue What is the SubLAN and what is the C-LAN in regards to Ethernet and termination resistor information? Explanation of termination resistor, RS-485, baud rate, token passing, and polling method. Is the Host LAN above or below the Ethernet LAN? Product Line TAC INET Environment I/NET Seven Network with integration of the FOI or Fiber Optic Interface  Cause How the Fiber Optic Interface (FOI) fits into an I/NET site. Resolution When defining the network in I/NET, the chart below helps to explain which components communicate to others. This is a simple explanation on where the various I/NET components are located in an I/NET Seven Network. C-LAN & Sub-LAN and the integration of Fiber Optic or FOI. The FOI Spec sheet is available here, as well as TCON087. Click the image below to download as a PDF document.  

Issue Some Netcontrollers support 32 I/O Modules, others only 16, how to find out what the limit is when adding more modules to an existing system. Environment Continuum Netcontroller CX9900, CX9940, Netcontroller II CX9680, CX9940 16IO-T X Driver Cause When a site is being extended by adding extra IOU Modules, it needs to be determined if the Netcontroller will support these additional modules. Resolution If the controller is online to Cyberstation, Edit the controller and check the value of "Max IOU Modules" on the Options tab, this will show 16 or 32. If the controller is not online the following apply: All Netcontroller II (CX9680) controllers support 32 IOU Modules. All Netcontroller 1 CX9900 with 8Mb RAM support 32 IOU modules, Most CX9940 with 4Mb RAM support 32 modules the only exception was the 4M-16I/O-T (now obsolete) that supported 16 modules. To determine if the CX9940 is a 4M-16I/O-T, check that the Model on the right side of the unit is defined as CPU-4M also that there are no connectors for the RS485 fitted to the unit on Comm1 or Comm4 (you will see holes where the connectors are not fitted). The CX9940 16IO/T can support an X Driver on RS232 Comm1, but no other port. The 4M-16I/O-T and 8M-32I/OT Do not support any Infinet nodes and cannot be upgraded to support them as the required hardware is not fitted as the time of manufacture.

Issue When attempting LonWorks communications in WorkPlace Tech, the following error message is seen. "Failed to get communications type, using LonWorks as default" Environment WorkPlace Tech 5.7.x Echelon U10 USB LON Network Interface (part number ECH-75010) – TP/FT-10 Channel Cause WorkPlace Tech LonWorks communications is not properly initialised.   Resolution Re-initialise WorkPlace Tech LonWorks communications. In WorkPlace Tech, go to 'Tools' > 'Configure Communication'. Change the communications type to 'BACnet' and click 'OK'. Open up 'Configure Communication' again and change the communications type back to 'LonWorks'. This should re-initialise the LonWorks communications.

Issue How do I format a Comma Separated Variable file (CSV) to create personnel objects via import that will include area assignments and photos. Product Line Andover Continuum Environment CyberStation Cause Need way to mass create personnel objects. Resolution Typically personnel information is provided from Human Resources in a MS Excel file, the data can be saved as a CSV file and easily formatted for import into the Continuum system which will automatically create one personnel object per row using the information (LastName, FirstName etc) included in the file. Assigning areas during import is accomplished by specifying a personnel template (previously created using Continuum). Different areas can be assigned to different personnel objects as a template can be specified per row. When the personnel object is created via the CSV import, it will be assigned all the areas found in the specified template. Importing a photo for the personnel object is accomplished by specifying an image file in the PhotoFile column. Click Here for a sample CSV file.

Issue Network 8000 Ethernet networks experiencing the following symptoms should be upgraded: GCM panels reporting repeated off-line / on-line messages NIM lock-ups requiring power cycling to recover Loss of global data sharing with Network 8000 (RNET and SNET transmissions fail) Product Line TAC IA Series Environment Network 8000 GCM Ethernet NIM, part number GCM-ETH-001 Network 8000 GCM-86000 Series controller (GCM-86120, GCM-86110, LNC-100, SIM-CCN, SIM-MTECH, SIM-YORK, SIM-TRANE) 802.3U Ethernet (100 Mbps) or 802.3z gigabit Ethernet (1000 Mbps) backbone network Cause Ethernet NIM performance was enhanced in revision 11.2T. Resolution Upgrade all NIMs on the network to firmware revision 11.2T, with the single exception of any with revision 11.2P firmware. Click here to see Announcement 01-105 for more details. For details on the REVISED Flash clear procedure, see the NIM Networking and Configuration Guide, F-25955-4, Chapter 2, section titled "Special NIM Address Switch Functions". Click here to see the procedure. Please reference Verifying the current firmware revision of a Network 8000 GCM and if an upgrade kit is available regarding Network 8000 firmware, including current revisions and upgrade kit part numbers.

Issue Field Bus controller shows its version number as 0.000000. Learn controllers from comm port is very slow and fails when reloading the controller. Updating the firmware will not fix this problem. Product Line Andover Continuum Environment Cyberstation 1.74 above i2 controllers B3 controllers Cause There are many reasons that will cause the i2 and B3 controllers show their version number as 0.0000000 Wireless network enabled or Multi-Network card enabled on the machine. Database snatched from Flash RAM after power-cycle does not match to the Continuum Database Some controllers with special firmware (Such as B38XX-V with 4.501043) have points referenced by other controllers, this will make the source controller buffer to be full after more than 20 hours Unknown application software installed on the CyberStation PC B-Link fault will also cause this problem Resolution Exit Continuum CyberStation, then ensure only a single network card is enabled Fix the problem caused by database mismatching: Create a new database and bring the master controller online, Do learn from the commport and bring the field controllers online Click the "Reset" button on the Runtime tag after opening the controller editor. Do database initialization and connect the original database to see if the version number is correct or not. If not, skip to item 4. If yes, do SendToController and then BackUpToFlash Update the controllers to the latest version. Rebuild the CyberStation PC. Only have the Windows operating system and Continuum CyberStation installed. Skip over B-Link and connect Field bus to BCX1 comm2 directly to verify B-LINK has some fault, and then replace it with new one, if required

Issue When attempting to Discover devices on the Niagara Network getting the following message: java.net.socketException can't assign requested address. Environment G3 (Niagara) ENC Cause The address in the default gateway of the ENC is invalid. Resolution Under the station Platform open TCP/IP Configuration and enter the proper gateway address in the "IPv4 Gateway" field.

Issue Where can older versions of Cyberstation software be downloaded from? Product Line Andover Continuum Environment CyberStation Cause Older version of Cyberstation software archived to FTP site. Resolution Log on to FTP server ftp://ftp.andovercontrols.com/ Customer UserName: andoverrep Password : andoverrep   Older CyberStation versions are found in the CyberStation_Revisions directory.

Issue In WorkPlace Tech Tool, the Definition tab of a Custom Object, right click on any object to request Properties info. The response is an error "Exception happened finding Visio shape". What does this mean? Environment WorkPlace Tech Tool 5.7.x Cause There was an error in Visio. The custom object may have been copied from a newer version of Visio to an older version. There may have been an error when creating the custom object. Shapes may have been added to the custom object when opened directly in Visio instead of being opened in WPTech. Some other corruption to the drawing took place. Resolution Do a “Rebuild Application”, and then try opening the shape properties again.  If this does not work, try creating a new custom object, and then try copying the contents of the old custom object definition page into the new custom object definition page (while in WPTech).  Then delete the old custom object, and then try the shape properties in the newly created custom object.

Issue Opening an MTA file in Menta causes an "The device type is not supported" error message. Environment Menta 5.x.x XBuilder 5.x.x Cause The Menta file is for a Xenta 700 controller and cannot be opened in stand alone Menta which only supports the Xenta 280, 300, and 400 series of programmable controllers. Resolution Import the MTA file into an Xbuilder project's Menta Library in order to edit or view the MTA file.

Issue MFC errors when starting or running Cyberstation or Webclient Product Line Andover Continuum Environment Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Windows 10 Windows Server 2012 Cause Microsoft Function Class (MFC) errors are typically caused by missing, damaged or altered files that an application is looking for and is having problems using. Resolution There can be a number of reason why MFC errors are being received. Here are a few causes related to Cyberstation startup. Check the Continuum compatibility matrix. If you are using a version of Windows Operating System that has not been qualified for a specific version (i.e. Windows XP SP2 with 1.93) then this can cause MFC errors. Viruses and Malware can also affect MFC files. Be sure to run both types of scans on Cyberstation, but this should be done after the Cyberstation or Webclient PC has been installed. If these types of products are active during an install, they can flag some of the files that would normally get installed as suspect and cause problems with the operation of Cyberstation even if it appeared that the installation was successful. Removing Continuum, rebooting, running scans and then disabling the active scans at the time of the Cyberstation install will often resolve these issues. Windows XP, Vista and Windows7 have restore points that you can sometimes go back to in order to restore to a point earlier where the MFC errors were not happening. As a last resort, you may need to reformat the hard drive on the PC, reinstall the Windows Operating System including the appropriate service packs and hotfixes and then install Cyberstation or Webclient. Links to other MFC related articles: MFC errors on Continuum startup after moving a database to another PC MFC error on Continuum startup or Continuum won't start on HP PC Running a listview is giving a MFC error

Issue Continuum LAN controller going offline and logging error 0x00006c0f and 0x00006c10. Environment CX9900 CX9640 CX9702 CX9680 ACX5720 ACX5740 Cause The errors 0x00006c0f and 0x00006c10 are typically logged as a pair and indicate the controller has detected an issue with the physical layer of the network. The errors come from the PHY chip in the controller's network interface adapter. The Controller Error Log Tool gives the following text for the error codes: 34 W 12/12/2011 08:57:47.00  0x00006c0f 0x00002600 0x01901848 0x0000c540 0x00000000                                         buffer passed in was too small (LAN_ERR_BUFFER_TOO_SMALL_ERROR) 35 W 12/12/2011 08:57:47.00  0x00006c10 0x00002600 0x019018b0 0x0000c500 0x00000000                                         buffer passed in was invalid for free (LAN_ERR_ALLOCATION_ERROR) Resolution Make sure the ethernet cable is properly inserted at both ends, the ethernet cable may have to be replaced. Determine whether the problem is in the switch/router, move the controller to a different port on the switch/router. Switches/ports have many different ways to be configured and can affect the controllers connection status. If move to a different switch or hub corrects the issue, analyze the configuration of the ports. Although not a common failure, the issue could be in the controller's hardware, the controller may need to be replaced.

Issue When swiping card, the access is denied. The message shown in AMT is "Bad Card Read". Environment I/NET Cause There may be two causes for this message: The tenant code isn't correct when using Wiegand 26 format in the door parameter. The digit of card number exceeds the setting in the setting of card reader type. For example, the card format is Wiegand 35, but in the door parameter, the card reader length is set to 36 digits. Resolution For cause 1, enter the correct tenant code in the Tenant Editor. For cause 2, set the correct card reader type and digit.

Issue Before installing Access Expert on premise server software, the Mongo DB must be installed and the Mongo service started, this requires creation and editing of a configuration file where the data and log directories are specified. There have been many cases of YAML errors seen during V3 on premise installation when attempting to start the Mongo service. Product Line EcoStruxure Access Expert Environment V3 Mongo DB Cause The YAML parser that reads the "mongod.cfg" file is very sensitive to the format of the configuration file including some very strict rules about spaces, double quotes and back slashes. When editing the file, it helps to setup the text editor to display ALL characters which will show any hidden characters that might be causing a parsing error. Ex. In Notepad++: Select View>Show Symbol> Show All Characters Resolution Space is needed between key and value pair. Enclose paths in double quotes. Double back slash required in Windows systems.