Issue Modbus slaves are programmed according to device documentation, but either the wrong values are returned or error codes complaining about invalid address. Environment Xenta 913, Xenta 731, Xenta 511:B Cause The XBuilder Device Editor has two ways to address modbus registers. The improper usage of these methods can cause communication problems because the wrong register is polled. 1. Fixed Address Blocks This method combines the function code and register address to produce a single number format that serves multiple function codes. This is sometimes referred to as numerical notation. A poll of a holding register uses function 03 and an address from 00 00 to FF FF. When using Fixed Address Blocks a message of function code 03 and address 00 00 is displayed as 40001. Due to this combination it is limited to 9,999 addresses per function code. Type Function Code  Address  Coil Status  01  00001-9999  Input Status  02  10001-19999  Holding Register  03  40001-49999  Input Register  04  30001-39999 When the device editor is using Fixed Address Blocks then the numerical number is parsed from the Register in the following way. Register Function Code Address 1-9999 01 Register - 1 10001-19999 02 Register - 10001 30001-39999 04 Register - 30001 40001-49999 03 Register - 40001 2. Function Code Tables (Discrete Input, Coil, Input Register, Holding Register) This addressing format is closer to the actual protocol and keeps the function code separate from the register address. It also provides full use of the addresses from 0 to 65535. Table Function Code Discrete Input 02 Coil 01 Input Register 04 Holding Register 03   If the wrong format is used it can result in failure to communicate because the wrong register is used. For example polling register address 40010 on function code 03 when it should have been address 9 on function code 03. Resolution The documentation of the product being interfaced with is the best guide on the register addressing and the format they use. If the documentation does not directly specify the information then use the follow hints to guide your selection: Hints to use Function Code Tables Addresses that fall on zero (0, 10000, 30000, or 40001) Non binary data that is less then 30001 or greater then 40001. Devices states it is J-Bus. Register address is displayed in Hexadecimal format. Hints to use Fixed Address Blocks Any address register above 30000 or 40000, unless it claims to be a JBus device. If it is still unclear which addressing format to use then experiment with read only data and value pages in the Xenta Servers. Pick a point that you can easily confirm the value, add both address formats to a device template, and then confirm the proper format with a values page. Once you know how to read one point the rest of the product documentation is easier to work with.

Issue The device is applicationless, or is not associated with a program record. (Subsystem:  NS, #5) The target device does not have a valid application loaded. To correct this problem, right-click on the device and select the "Load" option. Then, if necessary, repeat this operation. The device was discovered to be applicationless, or not associated with a program. If you encounter this error, load the application into the device. For host-based nodes, ensure that the host application is running Product Line Other, TAC Vista Environment LNS LonMaker Vista NL220 Cause Interrupting a download can cause the download to fail and render the controller applicationless.  Also, a corrupt Menta file can sometimes successfully download, but cause the controller to go into an applicationless state. Resolution An application must be downloaded through Menta while directly connected to the controller through the RS-232 serial port.  A blank Menta file with just one PVR is sufficient to restore an application to the controller and allow it to be downloaded; however, downloading the actual Menta file is better because it can expose parsing errors in the Menta file that need to be fixed before downloading it through the System Plug-in again. In some cases, an attempt to direct download can not establish communications to the controller and "timeout". In this event, download a new .mot file to the system using the Download Wizard. Instructions are located in Instructions on how to download an .MOT file into a Xenta Programmable controller. If the Download Wizard  is not able to establish communications with the device, the program should first be cleared using a Xenta Hardware Reset Tool. You can make one by following the instructions located in Xenta Controller Will Not Download / How to Clear the Xenta Application. If the Xenta firmware is older than 3.61, the method to clear the Xenta application is to power cycle the controller 10 consecutive times.

Issue Displayed temperature on the ETR is offset from the actual temperature reading of the controller. Environment ETR Thermostat Cause Factory calibration is offset from actual temperature. Resolution Click here to download the Installation and Operating Instructions Temperature Display Adjustments Temperature display may be adjusted by adjusting the ZERO or OFFSET Potentiometer (P2) as shown on the diagram.  Adjust P2 until the LCD Display reading, matches your controllers temperature reading if necessary. Note that all LCD Displays, are factory calibrated using an NIST Certified Glass Thermometer.

Issue Step by step instructions to configure the Lonworks Network Interfaces application to communicate over IP-852 to a Loytec L-IP router using the Echelon driver Product Line Field Devices, Other, TAC Vista Environment LNS Turbo Lonmaker turbo Lonworks Network Interfaces Loytec L-IP  Cause Instructional how to document steps through the necessary set-up to get a Loytec L-IP to communicate in a Vista system using the Echelon driver Resolution It is preferred to use Loytec's own driver rather than Echelon's driver, and also the Loytec driver is the only one supported in SmartStruxure, how ever it is possible to use Echelon's driver following the guide below. To learn more about the L-IP and understand the difference between two drivers, check this video: https://www.youtube.com/watch?v=cLNBv6tEDXg or Loytec L-IP 101 Note 1: The first steps would be to verify the IP addresses needed for both the computer and the Loytec L-IP router. In this example, we will be using 10.159.5.39 for the L-IP and 10.159.3.26 for the computer running LNS. The default IP address of the Loytec L-IP router is 192.168.1.254. In most cases the default IP needs to be changed to match the system network. Please reference the L-IP Users Manual page 20 for instructions on how to change the IP address of the device. Note 2: In our example there is only one L-IP, so it is configured as the configuration server. Remember: One L-IP within any Vista Server system has to be configured as the configuration server. Please reference page 52 of the L-IP users manual for instructions on how to set a L-IP as a configuration server. This document has the web instructions in step 12. Navigate to the windows control panel and open the Lonworks Interfaces application. In lonmaker 3.1 with LNS 3.1 the program will be lonworks IP channels: Within the Lonworks Interfaces application choose the IP-852 tab: Under network interface click the Add button: In the Network Interface Add window you will need to name your connection. In this example it is just simply named IP for the IP channel within LNS. The IP Address should be set to the local IP of the computer. The IP Port should be left at the default 1628 and Channel Timing should be LAN. Click OK: Back within the LonWorks Interfaces application you should now see the named IP network, the IP address, and the IP port number: Next, Click the Test button to test the communications from LonWorks Interfaces to the L-IP configuration server: Check the box to Set the Configuration Server Address and type in the IP address of you configurations server L-IP router. The default IP port used in network interfaces is 1628 so requesting a communication test from the L-IP requires the configuration server return port to be set to 1629. Then click the Start Test button: After clicking Start Test you will see a message verifying the test has started. If your test is successful you will see the following message: Your Lonworks Network Interfaces is now configured for a TCPIP connection and properly setup to communicate to a Loytec L-IP router configured as a configuration server. If you never receive a message showing a successful test, please proceed to step 9. Login to the L-IP web interface by opening a web browser and typing the IP address of the device. In our example it is http://10.159.5.39. This is the default web page within the L-IP web interface: Click the Config button: You will now be prompted to login to the controller. The default username is Administrator and the default password is admin Note: for new version of L-IP, its username is admin and password is loytec4u. Click on EIA-852 Server and make sure the Config server status is enabled and the Config server port is 1629. If any changes are necessary, a message will appear at the bottom of the web page to reboot the device for the changes to take effect. And if there are more than one LIP in this network, all the other LIPs apart from the first one need to choose disabled option for the Config server status. Click on EIA-852 Ch. List. In the channel list you should see your local L-IP device and IP address. The next step is to add the IP address of the HOST PC running the Lonworks Network Interfaces application. Click the Add Device button. Name your device. In this example it is named PC. Then type in the IP address and the port number of the HOST PC and click save. Click in the Recontact button and go back and repeat step 7. You should now see a successful test from your configuration server. If there are more than one LIP in the network, add all the other LIPs in this list. Now your Loytec L-IP router is communicating to the Lonworks Network Interfaces program. This will allow your LNS server to communicate on the IP channel connection within Lonmaker or NL220 and use this Loytec L-IP as its connection to the Lonworks network. Additional setup information is available here in the L-IP Users Manual.

Issue Is one access vendors card with Wiegand 26 bit output the same as another vendors Wiegand 26 bit output? Environment Continuum 1.xx Access Control Cause Replacing access card reader. Resolution When replacing access readers follow the manufacturer’s installation instructions for that particular reader. Wiegand 26 bit output type is a standard so that output will be the same.

Issue Integration to the Veris H80xx Entercept power meter with the Xenta 5/7/9xx and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Veris H80xx Entercept Power Meter Cause Integration instruction and programming example for integration to the Veris Entercept power meter. Resolution Please use the following .dev files as a starting point and a guide to the integration of a 100 amp or 200 amp Veris Entercept meter. 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 the modbus mapping or this supporting document for data scaling changes. If mapping for larger amp meters is needed, please contact product support.   100 AMP .dev file 200 AMP .dev file   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 the harddrive. In Xbuilder, right click on the Modbus Master device and choose Add Device Browse to the needed .dev file and click Open. Rename the newly added device to a unique name within the Modbus Master network.   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 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.  

Issue Many customers do not have the luxury of having email or internet access in the field, but they do have SMS ready phones. The EAS system allows our customers to receive those same product announcements via SMS that are usually sent as emails and web posting. Environment Product Support Cause Subscribing to the early alert system allows you to immediately be notified via SMS of important product announcements, hotfix releases, and many other critical alerts. Resolution Please follow these steps: Send an email to product.support@buildings.schneider-electric.com with "EAS Subscription" in the subject line In the email body list the subscribers name, company information, and complete mobile phone number (including country code), and the product lines you would like to subscribe to. The product lines currently available for this service are: Andover Continuum Satchwell MicroNet Satchwell Sigma TAC Field Devices TAC I/A Series TAC I/Net TAC Vista

Issue Temperature inputs not reading the correct values Environment Cyberstation IOUs Controller Cause Bad input Bad controller Bad sensor Resolution Replace sensor with a 10k ohm resistor.  Temperature input should read roughly 77°F or 25°C.  If it does then the problem is with the sensor.  If it does not then the problem is either with the input board or that particular input itself.

Issue Cannot communicate to third party devices using the MODBus TCP XDriver or MODBus RTU XDriver. Environment CyberStation ACX5740 XDriver MODBus TCP Cause The MODBus TCP configuration point was not created Resolution Create the MODbus TCP configuration point following the guidelines in section 5.1.3 of the MODBus TCP guide

Issue Continuum Add-On Software products and support contacts Environment Continuum Continuum Reports Suite Continuum Archiver/Archivers Continuum Elevator Control Continuum Bioscrypt Integration Video Monitor For Third Party Video Systems Continuum Guard Tour Center of Excellence (COE) Cause Continuum Add-On Software products and support contacts information. Resolution Please forward Continuum Add-on Software support requests to COE.Support@buildings.schneider-electric.com The Reports Suite software can be downloaded here: https://ecobuilding.schneider-electric.com/search?documentUUID=e040ce9b-7114-4cbc-b9cc-bcde73a6d64e&title=Continuum%20Reports%20for%20CyberStation%20v1.81%20and%20v1.82%20Add-on%20Software Internal note: In bFO the Care Team to which PSS will De-Escalate case is the NAM_BLD_COE_ADV Care Team.

Issue Bacnet 3rd party controller will not respond to Find New Bacnet Devices (Who-Is/I-Am), so will not come online to Continuum Environment Bacnet MSTP Continuum Cause Some 3rd party bacnet devices can be setup as master or slave. If the bacnet 3rd party bacnet device is setup as a slave device, it will not respond to the mstp token, therefore will not respond to the Who-Is broadcast and will not be able to communicate on the mstp network. The BACnet MS/TP protocol does not allow a slave only device to respond to a "Who-Is" broadcast. Resolution Check 3rd party device documentation or contact 3rd party device vendor for Master/Slave settings and configure for Master to communicate on a MSTP network. Slave only devices cannot come online and will require a 3rd party interface to convert to a protocol that can be directly supported by Continuum.   Examples of BACnet MSTP Slaves that are known not to respond to a Continuum Who-Is request and so not come online are: - The Babel Buster 485XM from Control Solutions Inc is BTL listed as a BACnet Slave device , their PICs statement can be seen Here. - Wilo pumps Interface Modules: IF-Modul BACnet & IF-Modul Stratos BACnet, their PICs statement can be seen Here. Additional Note In SmartStruxure a "slave only" MSTP device can ba manually created. 

Issue What are the default passwords for a IAC Touchscreen Environment Satchnet IAC controllers Cause Access level Resolution Read only: -      1234 Read/Write: -   4321 Super User: -    1024 ACK Alarm: -  2513 It is worth noting that these passwords can be changed when programming. If you connect to the Touchscreen using VisiSat software you can identify the passwords under the properties of the Touchscreen.

Issue What are the default passwords for a MicroNet Touchscreen? Environment MicroNet Touchscreen controllers Cause Access level Resolution Read only: -      1234 Read/Write: -   4321 Super User: -    1024 ACK Alarm: -  2513 It is worth noting that these passwords can be changed when programming. If you connect to the Touchscreen using VisiSat software you can identify the passwords under the properties of the Touchscreen.

Issue Does I/NET Seven provide Time and Attendance functionality Environment I/NET Seven 2.xx and above Third Party Time and Attendance solution Cause Possible alternatives to Customers wanting to use or interface Time and Attendance solutions with I/NET. Resolution I/NET does not have a separate Time and Attendance ‘module’. There are three possible options which may provide a suitable alternative to your requirements: SevenReports: I/NET’s SevenReports provides a standard report called “Transactions Attendance”.  The report compares the time stamp for an individual and calculates the time within zones defined in I/NET.  I/NET doors must be configured with entry and exit readers and have defined Zones (i.e. Anti-pass back must be enabled).  It could be as simple as a single zone for the entire site or multiple zones if this is required. This report shows EACH transaction received, therefore if you badge multiple times on the entry or exit readers the system calculates the time difference from the last badge. This must be taken into account by any system when calculating the total time within the “Zone”. Automatic Report Generation (Export of SevenReports to CSV): Using the same report as mentioned above, I/NET is capable of automatically exporting this document to a CSV file. This can be scheduled to run as required for any third party system to use. Third Party Access to InetDb SQL database This option allows third party SQL connections to query the I/NET SQL Database (Read only access), utilizing a predefined login or the INetThirdParty login.  The third party software or application would query data from the InetDb SQL database. For further information and configuration of these features are all available in the same document, TCON301 – Database Connectivity and Reporting.

Issue Supported operating systems for BAS2800+ Environment BAS2800+ version 2.9 / 2.10 Cause BAS2800+ has been discontinued. Please refer to the Product Announcement 'Satchwell BAS2800+ Discontinuation' for details. Resolution As per Product Information Bulletin 04.04.02-2, BAS release 2.9/2.10 has been validated for running on the following Windows platforms:- Microsoft Windows NT 4.0 Microsoft Windows 2000 professional Microsoft Windows 2000 server Microsoft Windows XP professional Microsoft Windows 2003 server

Issue When using the above sensors in conjunction with a BAS or Sigma building management system, out of range values can occur. Environment BAS 2800+ Outstation Sigma Controller 0-10 volts Cause If is possible for the sensor to provide greater than the specified 10 Volts DC output, and this causes the Outstation / Controller to display a default value. Resolution To resolve this issue carry out the following; 1 - Connect a 10K ohm 0.1% resistor in series with the 0 – 10 volt signal as shown in the drawing below. 2 - Create a lookup table in Sigma or BAS 2800+ with the following values. Input                        Output 0                    –        0 83.335           –        100.000 100.000         –        100.000 3 - Allocate this table to the analogue input object, and download the (Point / Object) and table, to the (Outstation / Controller). The above configuration will allow the DC voltage to rise to 11.335 Volts before an out of range alarm would be generated.

Issue What is the difference between the NL220I and NL220M dongle. Product Line Other, TAC Vista Environment Newron NL220 Cause There are two types of NL220 dongles, (install) and M(maintenance).  Each type have their own specific functionality.  The correct dongle should be selected to avoid issues at a later time. Typically you use a NL220M for the site installation. This dongle is locked with the site NL220 installation, then use a NL220I dongle in conjunction with the NL220M to unlock the Engineering features. Credits are used and replaced on the NL220M dongle in this case. Resolution Newron NL220 functionality.   Administration (Engineering) mode will allow the following (NL220I): Creating a project Adding network infrastructure devices Adding LonWorks devices – application specific devices as well as programmable devices Installing and commissioning network infrastructure devices Installing and commissioning LonWorks devices Creating SNVT and tag bindings Configuring devices using the generic browser and device specific plug-ins Managing devices Deleting devices Replacing devices Maintenance mode will allow the following (NL220M): Configuring existing devices using the generic browser and device specific plug-ins Managing devices Replacing devices   Typically you use a NL220M for the site installation. This dongle is locked with the site NL220 installation, then use a NL220I dongle in conjunction with the NL220M to unlock the Engineering features. Credits are used and replaced on the NL220M dongle in this case.

Issue Upgrading Loytec L-IP to the latest firmware or checking current firmware version. Environment Loytec L-IP Vista Network Interface Cause UL 864 v.9 for Smoke Control requires at least version 5.04 firmware in all system L-IP's. Resolution Verifying L-IP Firmware Version via Console Connection To use the serial interface, the DB9 console connector of the L-IP can be connected to the RS-232 port of a PC. The L-IP-3ECTB and L-IP-33ECTB use a standard null-modem-cable must be used to connect the L-IP’s DB9console connector to the RS-232 port of the PC. The PC will communicate with the L-IP using a HyperTerminal program with the communication settings set to 38,400 bps / 8 data bits / no parity / 1 stop bit / no handshake. The L-IP displays the console menu shown in Figure 1 upon a successful HyperTerminal connection initiated by a “enter” keystroke or power cycle of the L-IP: LOYTEC electronics GmbH www.loytec.com L-IP Configuration Menu ======================= [1] Show device information [2] Serial firmware upgrade [3] System configuration [4] EIA-709 configuration [5] IP configuration [6] EIA-852 device configuration [7] EIA-852 server configuration [8] Reset configuration (factory defaults) [9] Device statistics [0] Reset device Please choose: Figure 1: L-IP main menu. Select Option 1 to Show device information  This menu item shows information about the L-IP and the current firmware version. The output should look like what is shown in Figure 2. Product information =================== Product code: L-IP-3ECT Firmware: L-IP Primary image Version: 5.0.5 Build date: Fri Mar 18 10:41:29 2005 Serial number: 002304-80000000E73C Free memory: 557K,57K System temp: 33.3C Supply volt: 12.0V Unique Node IDs =============== Port 1: 80 00 00 00 E7 3C EIA852: 80 00 00 00 F7 92 Figure 2: Device information. (For UL 864 v9: If the Firmware Version does not reflect a Version 5.0.4 or Version 5.0.5, you must update the firmware to an approved version in the next steps. If the L-IP contains an approved version, further action is not required.) L-IP Firmware Upgrade To download the firmware via the console connected the L-IP to the RS-232 port of a PC via its console interface as outlined above. Download the lswitch_lipxxx.zip located at www.loytec.com to the PC. Install the LOYTEC serial upgrade tool (LSU Tool) by double clicking LSU_2_0_1setup.exe. Double click on the lswitch_lip_xxx.dlc file. This will start the LSU Tool and load the firmware image referenced in the . lswitch_lip_xxx.dlc file. The start window of the LSU tool is shown in Figure 3. *note that the lswitch_lip_xxx.dlc file and the lswitch_lip_xxx.dl file must be stored in the same folder. Figure 3: LSU Serial Upgrade Tool in idle mode. If the L-IP is not connected to COM1 you can change the port to COM1, 2, 3, or 4. Press “Download” to start the download. A progress bar as shown in Figure 4 can be seen. Figure 4: Progress bar during firmware download. If the upgrade is successful the following window appears (Figure 5). Figure 5: Successful firmware upgrade. Exit the LSU Tool. Reconnect through HyperTerminal connection and  initiate the console by a “enter” keystroke or power cycle of the L-IP. At the console main menu, select option [1] Show device information, and press Enter. This will bring up the current device information as shown in Figure 2, for verification that the firmware version has updated successfully.

Issue Negative values presented to an IC3-SNP Integration Controller are displayed starting at 65535. Environment Sigma Integration Controllers IAC Controllers Unifact Controllers Cause The IC3-SNP Integration Controller calculates the negative value incorrectly. Resolution To overcome this issue it will be necessary to create a new Lookup table and to allocate it to the IC3-SNP Analogue Input object. 1 - In Sigma "System Manager" select "System Setup" and create a new lookup table, using the configuration shown below. 2 - Edit the Analogue Input object to include the new Lookup Table number, select to download the object. 3 - In Sigma "System Diagnostics" download the Lookup Table to the IC3-SNP. 4 - The lookup table shown above assumes that the value being presented is in whole numbers, i.e. a received value of 1 equals 1, but there are instances when the value received may have a *10 factor applied. In this case the lookup table is modified as shown below. Input         Output 0               0 32767       3276.7 32768      -3276.8 65535      -0.1

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.