Issue  To convert a 0 - 20 mA signal into an acceptable form to be used into a variety of controller types. Environment Sigma BAS Micronet X96 controllers X32 controllers IAC controllers Micronet controllers Cause Some controllers will not accept a 0 - 20 mA signals and therefore the signal must be converted. Resolution To achieve this conversion, please follow the instructions below. Install a 500 ohm 0.1% resistor in series with the 0 - 20mA signal. From across the resistor, take the signal to the controller . The Universal Input or Analogue Input should be set as a standard voltage input.

Issue The Remote Alarm Manager shuts down during use, or cannot be restarted. Environment Sigma BAS 2800+ Vista Micronet Remote Alarm Manager RAM Cause The Log.mdb file becomes too large, and uses excessive memory, this can cause the RAM Engine to shut down. Resolution The Log.mdb can record all system alarms, user actions and the actions that RAM is taking. This file will increase in size and has no restrictions on how big it can get. How fast it increases in size will depend on the logging requirements set in the configuration. This file needs to be managed, and this is achieved as follows: 1 - If the system is running without any problems, then this file should be deleted or renamed on a regular basis. To do this stop the RAM services and locate the Log.mdb record (For Sigma it is most likely located in Sigma\Data\Remote Alarm Manager), and delete / rename it. Restarting the RAM services will recreate a new file. 2 - Ensure that all logging is set to its most infrequent setting. The above screen shot shows the "Debugging" screen for the "GSM Modem" interface. In this instance, logging has been set to "Nothing", but there are four other options. 1 - Errors - Only errors are logged. 2 - Normal - Only low level information is recorded,. 3 - Detailed - More in depth information is stored. 4 - Verbose - All information is logged. If RAM is operating correctly, then choosing either Nothing or Errors, would be appropriate.

Issue Receive “Timeout while waiting for server to get ready” error when starting PCT Environment Project Configuration Tool, PCT Cause PCT can't reach DHCP-server from the virtual machine. Resolution To configure a portgroup or virtual switch to allow promiscuous mode: 1.Log into the ESXi/ESX host or vCenter Server using the vSphere Client. 2.Select the ESXi/ESX host in the inventory. 3.Click the Configuration tab. 4.In the Hardware section, click Networking. 5.Click Properties of the virtual switch for which you want to enable promiscuous mode. 6.Select the virtual switch or portgroup you wish to modify and click Edit. 7.Click the Security tab. 8.From the Promiscuous Mode dropdown menu, click Accept. Note: The setting on the portgroup overrides the virtual switch setting. For more information, see How promiscuous mode works at the virtual switch and portgroup levels (1002934).  

Issue Users or engineers may be unsure of how to access the best support for issues with Smart Connectors, especially where site specific Smart Connectors have been developed, or believe the issue is with the underlying framework. Product Line EcoStruxure Building Operation Environment SBO/EBO and general integration projects Cause Unlike SBO/EBO, which is a standard EcoBuilding product that falls under normal technical support, the Smart Connector (formerly known as Mongoose) was developed by Schneider Electric Buildings Labs. As such the necessary level of specific Smart Connector expertise is not found within the technical support teams Resolution If using a Smart Connector developed specifically for a project created by a separate Integration Team within Schneider EcoBuilding, then it is always best to go back to that team with your technical issues. In all other cases, the best place to raise any questions would be on the SmartConnector Developer Forum: Here, questions can be raised and speak directly to the Software Developers who originally created the Smart Connector Framework.

Issue Can I add the group bindings manually as the option to create group binding in the System Plug-in takes time and controllers are taken offline for the period of the process Environment Lonmaker Vista Cause This is  possible to do and works very well and effectively if you understand the process  Resolution Follow these steps to add TAG 0 system bindings and TAG 1 Xenta bindings to your new Xenta controller. In Lonmaker find the source of the TAG 0 binding buy finding any TAG 0 existing binding. Then right mouse click on the tag number and select Go to reference. This will take you to the source of the TAG 0 bindings. If a list of controllers appear then you are already at the source controller. Then Carry out a connection as normal in Lonmaker on that function block. Right click on the Virtual function block with the TAG 0 source and select the connect option. Select the TAG 0 option under the Hub tab then select the target tab and add the new Xenta controller to the system with the Add FB/SNs button. Then select the TAG 0 in the virtual function block of the new Xenta and click on the Add button. The select the OK button. This will add the TAG0 binding to the new Xenta device with the correct binding type. The next step is similar to the TAG 0 but for the TAG 1. You need to locate the TAG 1 Xenta group that you are adding the new Xenta controller into. Once you have located the TAG1 source use the same connection method as TAG0 but use the TAG1 in the virtual blocks. The final step is to download the added controller and the group master.

Issue Technical support contact information for Design 360 and Studio 360 Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Design 360 Studio 360 Cause Design 360 or Studio 360 has issues requiring technical support assistance which is not provided by PSS. Resolution Schneider Electric Employees should contact PSS who will provide you with your Branch Administrator and Technical Expert contact information. Partners may contact Smartware directly for any support of the tool at: Email: techsupport@smartwaretech.com Phone: (716) 213-2222

Issue Remote Alarm Manager - What TCP ports are used? Environment RAM TCP Ports Cause Customers RAM Console is unable to communicate with the RAM Engine. Customer cannot communicate with RAM webserver. Resolution Remote Alarm Manager uses TCP ports 8090 and 8091 between the RAM Console and RAM Engine. Remote Alarm Manager uses TCP port 80, but also recommends this to be changed to 781 - 785 as defined in the settings page.  

Issue Site backups, application files, etc need to be shared with Product Support to speed resolution. These files can be uploaded to the Box server. Environment Schneider Electric PSS-Rockford and PSS-Dallas Box server folder Cause Many email services have a limit on the size of attachments. In many cases, large files must be sent to Product Support so that the support engineer can investigate a reported issue. Resolution Use the following form to upload the files associated with your support ticket.  Please note that you must have an open support ticket with PSS- Rockford or PSS-Dallas before uploading a file.  Files uploaded without a reference to a support ticket will be deleted. You may upload additional files by clicking the appropriate link at the end of the "Success" message. Note: You might receive an error message despite your file still being sent

Issue The next generation extranet for Schneider Electric's Buildings Business is almost here: The Exchange. As a first phase deliverable, we are very excited to present The Exchange Download Center. All of the assets you once accessed through the Buildings Extranet are now available on a brand new platform. It's easy to search and fast to download. Stay tuned for more great features as we roll this into the all new extranet solution for Buildings. But first, we ask that you register for a new account on The Exchange.   Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment The Exchange Download Center Cause In the near future we will be rolling out a brand new Buildings web experience from the ground up. The first phase of this renovation is the Download Center, where you can find all the files you need to use Schneider Electric's Buildings products quickly and easily. Resolution Navigate to https://ecobuilding.schneider-electric.com * Use a modern browser for the best experience: Google Chrome, Mozilla Firefox, Microsoft Internet Explorer version 8 or later. If you receive the following error in Internet Explorer despite using version 8 or later, the browser is displaying the page in Compatibility View. Click here for more information on Compatibility View and how to disable it. The Download Center will not function properly in Compatibility View.   On the header bar, you will see the option in the top right corner for “Login / Register.” Click it.   If you are already registered, enter your email address and password. If this is your first time registering, click the link for “New to the Download Center? Register here!”   Answer whether or not you are a Schneider Electric employee using the radio buttons. If you are a Schneider Electric employee, enter your SESA ID and your desired password for The Exchange. Click to accept Schneider Electric’s Terms and Conditions and hit “Create Account” * The first time you register you must be connected to the Schneider Electric network, or connected via VPN. This is only required at registration. All future logins can be done externally. If you are not a Schneider Electric employee, enter your first name, last name, company name, location, business email address, and desired password for The Exchange. * It is important to use your business email address if you are a licensed partner. Your email address is used to validate your Partner status and assign the correct permissions to your user profile automatically.   An email is sent to your designated inbox with a link to click through and validate your email address. Once this is done, your login is created and you are ready to start using the Download Center. * If an error is displayed when trying to validate your authentication code, please try to log in. This happens when an email address has already been verified and oftentimes does not indicate an error with the registration.   Once logged in, you can search and download assets available to your user profile. If you attempt to download a file that you do not have access to, you will be given a chance to report if this is in error. Your username, email, and the asset you are trying to access are recorded. Please enter a message if any further description is required and hit “Submit.” A member of our team will get back to you promptly with a resolution. Web Site Support For any issue regarding The Exchange Download Center, please contact us at exchangesupport@schneider-electric.com.

Issue Both BACnet MS/TP and Modbus typically provide a robust and reliable communications channel allowing the Automation Server to effectively manage a large collection of equipment over extended distances. When the system does not come up operating as expected due to the communications integrity, considerable effort can be consumed troubleshooting or working-around the fault observations. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Other, TAC IA Series Environment Automation Server with BACnet MS/TP or Modbus RS485 networks connected to Port A or Port B. Cause The configuration of the RS485 network can create conditions that reduce the tolerance for EMI noise on the bus, electrical ground differences, transmission signal loss through the cable and/or component performance. Resolution A collection of application notes and Quick Start Best Practices Guides are available on the subject of BACnet MS/TP and Modbus RS485 network connections to the StruxureWare Automation Server.  These application notes and quick start guides provide recommendations in the areas of – BACnet MS/TP & Modbus RS485 Network Termination Network Biasing Options and Techniques Unit Load and associated Maximum Node Count Recommendations Isolated RS485 Interfaces and related Expanded Unit Load Cable Specifications and Suggested Cable Selections Cable Routing and Recommended Lengths The documents describe configurations of cable, network length, node counts and bias arrangements providing compliance with the EIA/TIA-485 Standard and TSB-89-A Guidelines with the objective of optimizing system tolerance for noise, grounding and transceiver component variations.  Most of the application notes and quick start guides target specific product families which include the Andover Continuum b3 Family, TAC I/A Series MNB Family, Legrand Power Meters and the Viconics VT7000 series sensors. There is also an application note and quick guide directed toward other “Generic” RS485 MS/TP and Modbus devices where the user is guided through a sequence of information collection steps to determine the appropriate recommendations.  The collection of application notes and guides are available on the Schneider Electric download center. The list of links below will take you to the applicable download page. AN01-RS485-Generic Application Note – General MS/TP & Modbus I/F to Automation Server Quick Guide-RS485-Generic Best Practices Guide - General MS/TP & Modbus AN02-RS485-B3 Application Note – Continuum B3 I/F to Automation Server Quick Guide-RS485-B3 Best Practices Guide - Continuum B3 I/F AN03-RS485-MNB Application Note – I/A Series MNB I/F to Automation Server Quick Guide-RS485-MNB Best Practices Guide – I/A Series MNB I/F AN04-RS485-Legrand Application Note – Legrand Meter I/F to Automation Server Quick Guide-RS485-Legrand Best Practices Guide – Legrand Meter I/F AN05-RS485-VT7000 Application Note – VT7000 Series I/F to Automation Server Quick Guide-RS485-VT7000 Best Practices Guide – VT7000 Series I/F Note:    If using the download center for the first time, you will need to register. See Register for The Exchange Download Center for more information. The Download Center requires the use of Internet Explorer (version 8 or higher), Google Chrome or Firefox browsers. Additional information is available in the Hardware Reference Guide Access the StruxureWare Building Operation Web Help. Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.

Issue Where can we find the LON xif files for SE72xx, SE73xx, SE76xx controllers? Environment SE7200 / SE7300 / SE76000 Cause xif files are needed for LON applications. Resolution All LON related files for these controllers are available for download on The Exchange Download Center:   XIF files and plug-ins Resource files (DRF kit)

Issue Printer Use with Emergin Software Emergin Software worked fine until I/NET 2000 was upgraded to I/NET Seven. Now the printer starts to print the Events and Alarms vertically instead of horizontally. Environment Emergin Software I/NET Seven upgraded from I/NET 2000 Cause Upgrade process requires that the COM port be added back again following the upgrade. Resolution Remove the COM Port from the Device Manager Reboot the PC so that it rediscovers it or re-adds it back again Restart I/NET Generate an Alarm and verify that it works correctly. If for some reason this does not work: Verify that you have the latest Emergin Build that is compatible with I/NET Seven, then try it again. You would have to go to the Emergin Website to get this information at www.emergin.com.

Issue I/NET to DVR interface communications port Environment TCP/IP Cause A firewall may prevent communication between a PC and the DVR Resolution Integral DVR communicates on port 18772.

Issue What is the proper way to enter data in ID Works and print a badge? Product Line OTHER, TAC INET Environment ID Works I/NET Seven Cause Enter data properly to avoid losing data or having to redo personnel entry. Resolution Log into the ID Works Program Default user name is lowercase admin Default password is lowercase admin Choose the badge project for the card you are going to print. If you do not see the Project in the window area, select the "More Projects" button to see the complete list of projects. Once you choose the project, a window will pop up for you to log into the ID Works Project. You have a choice on how to log in. You can either choose to check the box next to "Use Trusted Connection" or under the "INetThirdParty" Login ID the password is lower case passinetdb3p. Typically, select the “Trusted Connection” option. This is a view of the Sample project that is on the I/NET Seven CD under the "Support" file folder on the CD. Next fill in all the information listed on the Production Form including taking the photo. Now that you have filled in all the info and took the picture, it is time to print the badge. On the Bottom ICON Task Bar, the second ICON in going from left to right is the "Print ICON." Before you actually print the badge, make sure the Blank cards that are in the printer magazine are the correct ones. Once you verify that the correct blanks are in the printer, and then depress the Printer ICON with the mouse. Printing the badge will also save the information in the I/NET Seven system and the ID Works system. There is NO need to save the info first, and then print the badge. Now that you still have the information in the Production Form on the Screen, DO NOT choose the RED X on the Top ICON Task Bar to clear the page. If by accident you do choose the RED X, you will get the following pop up window. DO NOT CHOOSE the YES BUTTON, if you do, you WILL DELETE ALL THE INFORMATION AND PHOTO you just entered in the I/NET Seven System and the ID Works system. If you find yourself in this situation, you NEED TO CHOOSE the NO BUTTON, doing this choice WILL NOT DESTROY ANY DATA. In order to refresh the project, go to the Top Task Bar and choose the "FILE" option. In the drop down list choose the "Close Project" option. Then select a new Project for the next badge, this process will open a new clean Production Form to fill out.

Issue Inovonics Wireless Interface problem Environment FA7403 Cause Inovonics provides an interface to access wireless temperature sensors. The FA7403 receiver can be used to interface with Xenta equipment or Continuum equipment, however these interfaces use different protocols. Resolution The Xenta equipment requires a hexadecimal protocol which corresponds to the FA7403 receiver. The Continuum equipment requires an ASCII protocol which corresponds to the FA7403-ASC receiver. If you have the wrong receiver for the equipment you are trying to interface with then contact the Product Support Group for steps to reconfigure this device.  

Issue How to program a BioScrypt V-Pass-2 (Biometric) Reader in I/NET Seven. Product Line Other, TAC INET Environment I/NET Seven BioScrypt V-PASS (MV1200) Cause Assistance with configuring the BioScrypt V-PASS reader with I/NET Seven Access Control. Resolution Biometric Reader Setup Using the Bioscrypt V-pass-2 Reader The reader is: Bioscrypt V-Pass FingerPrint Reader VPASS-2 Note: The Programming software to load fingerprints on the PC comes with the reader. For the actual wiring and programming of this reader see the linked "BioScryptSetup.PDF" BioScript Setup Wiring (pigtail) Wiegand 1 - Wiegand Out Data 0 3 - Wiegand Out Data 1 6 - Wiegand GND Power using separate 24V DC Power Supply 11 - Pwr GND 13 - Pwr IN 15 - Earth Ground BioScrypt V-Pass Reader Wiegand Setup Install BioScrypt Software (VeriAdmin) on PC and setup to communicate with reader. Go to Configure > Unit Parameters Click on Wiegand Tab Check Predefined Format Pick "Standard 26 bit" Under On Success Check Alt Site Code & Enter Arbitrary Value (usually 3 digits) RECORD VALUE this is the Site Code Under Wiegand I/O Check Enable Input Check Enable Output Select Always Output (regardless of Input Source) Enroll Individual in VeriAdmin Enroll Individual RECORD ID – this is Individual Number NOTES: The index number is to assigned to ID number to record each individual finger (0-9 is for all 10 fingerprints). I/NET will only be sent the ID number in the Wiegand String. Schedule does not matter. You have selected Always Output (regardless of Input Source). One will do all the door scheduling in I/NET. Enroll Individual in I/NET Create new Tenant called “BioReaders” If site is using Wiegand Card and NOT Large Numbers (Dipswitch 7 OFF) Enter Site Code (recorded from above) as the Tenant ID When enrolling the individual in the new tenant, use the ID recorded from above as the Individual Number and Decimal Card Number.   If site is using Wiegand Cards and Large Numbers (Dipswitch 7 ON) or if using Idiscs (set Dipswitch 7 ON for only DPUs with BioScrypt, even if they have Idisc also) Leave default Tenant Code. Use 26BHEXCAL.xls and enter Site Code and Individual ID recorded from above and it will generate the HEX Card Number. When enrolling the individual, enter the Hex Card Number as generated. I/NET Door Configuration Make sure door is setup as Wiegand 26 Configuration as Implemented DPU 7920 Door 08 was setup as BioScrypt V-Pass MV1200 Door 09 was setup for Idisc Door Lock was wired to both relays in series (so both had to be energized to unlock the door). Door 08 (BioScrypt) was given a schedule of 24/7 and assigned to all individuals in new tenant. Door 09 (Idisc) had the original schedule assigned to site personnel. This schedule is the one that will deny access according to schedule. Other Configurations This can be used as a single reader for the door (with schedules in I/NET) or as implemented above with any combination of reader compatible with I/NET.

Issue Every time the computer reboots, LMGRD errors are shown at startup.   LMGRD encountered a problem and needed to close. lmgrd.exe - Application Error The instruction at "0x0012e854" referenced memory at "0xffffff91". The memory could not be "written". Product Line Other, Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Vista Server 5.0 FlexNet Licensing Remote Alarm Manager Sigma BAS2800+ Micronet Errors Cause There is a known issue with the new license server from Flexnet. The LMGRD.exe is actually crashing during shut down of the PC. Resolution This is nothing dangerous. What happens is that when you turn off the PC, something is happening with the license server during the shutdown phase. Since LMGRD runs as service, it can not display this error message during this shut down. The error message is shown the next time the PC is started. It will not affect anything since the error messages is queued from the last shutdown sequence, NOT during the startup. We think it has something to do with having a license server installed and not using only an entitlement license. In some situations, placing a customer license file from any project into the license folder along with the monthly demo license stops the LMGRD error. The license server may read the customer license, note that it is invalid, then use the monthly license. Flexnet is looking into this issue. Look for a fix in upcoming versions. On Sigma, BAS2800+, and Micronet systems where Remote Alarm Manager is installed, the TAC license server can be uninstalled as it is not used.

Issue The Echelon LonTalk PCC-10 PCMCIA Network Adapter Will not work with a Dell E6400 laptop Environment PCMCIA slot Cause Dell E6400 Chipset Resolution Go to the Dell website and upgrade your laptops chipset to the latest version from the dell drivers and downloads section. The file download is a self extracting file, follow the instruction provided and when you re-boot your computer your LonTalk PCC-1 PCMCIA Network Adapter should be fully functional. For further information see TPA-SACH-10-0008.00 - LON PCC-10 PCMCIA Card with Dell E6400 Laptop

Issue Integration to the Powerlogic PM800 power meter with the Xenta 500 \ Xenta 700 \ Xenta 900 and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Powerlogic PM800 Power Meter Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template. Please report any problems to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev file as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes.     To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.

Issue Integration to the Powerlogic CM4000 power meter with the Xenta 500 \ Xenta 700 \ Xenta 900 and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Powerlogic CM4000 Power Meter Cause Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support Services-Dallas has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template. Please report any problems to PSS Dallas at product.support@buildings.schneider-electric.com Resolution Please us the following .dev file as a starting point and a guide to the integration. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes.   To use these files in Xbuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on your harddrive. In Xbuilder, right click on the Modbus Master device and chose Add Device Browse to the needed .dev file and choose Open. Rename the newly added device to a unique name within the Modbus Master network.