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.

Issue Integration to the Cummins ModLon 2 gateway 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 Cummins ModLon 2 Gateway 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 files 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. One generator: .dev file Two generators: .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 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 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 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 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 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.

Issue Cisco switches reporting connected Sigma devices using more than one MAC Address which appear to be transmitted from the Sigma device connected to the port.  The error alarm reported "%PORT_SECURITY-2-PSECURE_VIOLATION: Security violation occurred, caused by MAC address 0050.b401.1e46 on port FastEthernet1/0/35" Environment All ARM7 Sigma Ethernet devices Cisco Catalyst 3550 Series Switches Cisco Catalyst 3560 Series Switches Cisco Catalyst 3560-E Series Switches Cisco Catalyst 3750-E Series Switches   Cause Sigma controllers broadcasting high number of Sigma globals (typically 40 per second). Upgrading BAS2800+ systems to Sigma can result in higher levels of Sigma global data than seen previously. Cisco switch set to 10Mb half duplex which mistakes the source MAC address of the Sigma global from a controller on one port with that of a controller on another port. Cisco switch has Layer 2 Security feature enabled, see Click Here High collision rates may also be seen at the switch. Resolution Identify those Sigma objects that are broadcasting global data at high rates and suppress the rate of change of the Sigma object. This can be achieved by: Running Wire Shark Ethernet trace program to record the Sigma broadcast Ethernet packs per Ethernet sub-LAN. Email each of the saved capture files (per LAN) to your local product support for a global analysis report. If possible then increase the connection speed of the Cisco ports. New firmware for the ARM processors has been created to addresses the issue. You can find the firmware and release note on the Exchange