Issue Unable to create new OGC graphic pages in Xbuilder 5.0.2 or later.  The edit option has been grayed out and I cannot open the OGC graphic editor. Environment XBuilder TGML Graphics Editor Vista Cause In Xbuilder 5.0.2 the system was changed to support UTF-8 character encoding. Since OGC Graphics pages cannot support this change all new graphic pages added to XBuilder will be forced to be TGML pages which support the UTF-8 character encoding.  Resolution OGC graphics created in earlier versions of XBuilder will still display properly when those projects are upgraded to newer versions of XBuilder but they can no longer be edited. If changes need to be made to these files you can follow one of the two options listed below:  #1. In order to make changes to these graphics the files must first be upgraded to TGML graphics. This is done by opening the OGC graphics with the TGML editor and the graphics will be automatically updated. #2. It is possible for 2 versions of XBuilder to reside on one PC. You can download the 5.0.2 version of XBuilder and use this version of the tool to make the necessary changes. Once the changes are made you will save the project and open the edited project in the newer version of XBuilder.  

Issue The factory uses the number of field failure returns to evaluate product quality.  The analysis of returned product has the potential to produce extensive information about how the product is performing and also reveal areas for improvement. Environment All controllers in following product lines:  MNB, MNL, Niagara, Network 8000, Micronet 2000. Cause Lately, many of the returned controllers, after factory-testing, have resulted in "no fault found", and a high percentage of these controllers have little to no explanation of the failure witnessed in the field. This makes it difficult to investigate the returned product further. Resolution Include the following information with all controller returns: A detailed description of the reason for return The name of the site from where the controller was removed The name and contact information of the field technician who determined the unit was defective The field technician will only be contacted if absolutely necessary. Write the above information on a "returned goods" identification tag (part number F-24802) and attach a tag to each returned controller.  The tags are available via the Publication Zone through iPortal at no charge. For more information on returning product to the factory, review the following technical product advisories: TPA-PSSG-09-0003.00  Return Process Improvement TPA-RKFD-10-0005.00  Return Process Improvements

Issue Data not showing up in the consumption report. Environment All versions of I/Net. Cause The points that are trending data are not matching up with the new host, therefore it is not collecting any data. Resolution After restoring the database, open up the trends editor and create or match the trends on the new Host PC.

Issue Are there any pressure sensors in the Schneider Electric portfolio that uses the 4-20mA signal? Environment Pressure sensor Cause Cannot find any 4-20mA pressure sensors in the current portfolio Resolution No pressure sensor in the current portfolio is using the 4-20mA signal

Issue Spare parts for V221 Environment 0804375005 Recond kit 221/223-65  0804376005 Recond kit 221/223-80  0804377005 Recond kit 221/223-100  0804538005 Recond Kit 221/223-125  0804627005 Recond kit 221/223-150 V221: DN65 7212154000 DN80 7212158000 DN100 7212162000 DN125 7212166000 DN150 7212170000 Cause Reconditioning kits for the V221 valves Resolution The following reconditioning kits are available until the end of 2012, after that they will be obsolete: 0804375005 Recond kit 221/223-65  0804376005 Recond kit 221/223-80  0804377005 Recond kit 221/223-100  0804538005 Recond Kit 221/223-125  0804627005 Recond kit 221/223-150

Issue What I/A Series G3 object can be used to retrigger a write a value to a Modbus controller? Environment I/A Series G3, Modbus Cause Various Modbus controllers require the rewrite of values to maintain use of remote values versus local values.  This fallback mechanism allows the local Modbus controller to maintain control in the event of a BMS controller failure or loss of communications. Resolution The I/A Series G3 Modbus driver utilizes Modbus preset components to perform the rewrite function.  Presets allow writing preset values to the target addressed data items upon right-click action (command). If required, the “Write” action of any preset container can be linked into other control logic. For example, the “Trigger” slot of a TriggerSchedule can be linked into a ModbusClientPresetRegisters container component for periodic writes of child registers defined under the parent.  The same is also true using a periodic trigger object found in kitControl.  Preset components can be found in the modbusAsync palette and modbusTcp palette in the “Presets” folder. Note: Modbus client preset components are not proxy points or proxy extensions.  Modbus client preset components are not polled and do not read data from the device.  Modbus client preset components are only used to write data to the device. Presets exist for both Modbus coils and holding registers. Reference the I/A Series G3 Modbus Guide (About Modbus preset components) included with G3 documentation for more details.

Issue 3rd party BACnet device can send a reinitialize device request to an EBO server. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause EBO servers support the "ReinitializeDevice-B" Bacnet device management service. This allows BACnet clients, such as BACnet browsers or operator WorkStations, to initiate ReinitializeDevice requests, i.e. Warm Start or Cold Start. Resolution EBO currently does not support passwords for the ReInitializeDevice service. It is possible to create a whitelist for the EBO server and exclude a 3rd party BACnet device from that list, but this will block all communication with the 3rd party BACnet device.

Issue Can bCX comm1 power a port-powered RS232-to-RS485 converter?. Environment bCX Cause Need to connect Modbus RTU devices on RS485 bus to Xdriver on bCX comm1. Resolution This has been done successfully according to posts on the Exchange commnuity. It is not a configuration that Product Support Services supports as it is not tested and there are many different devices on the market - some of whch may work and some which may not. 

Issue What is the difference between the MNL-V3RV3 and the MNL-V3RV3-A? Environment  MNL-V3RV3 MNL-V3RV3-A Cause MNL-V3RV3-A is a new part number, and it isn't clear how it differs from the existing  MNL-V3RV3. Resolution The MNL-V3RV3-A meets the requirements of the Buy American Act (BAA).

Issue Can certain Analog Input values be read with up to 3 decimal places in WorkPlace Tech? Environment WorkPlace Tech MNL series MNB series MicroNet 2000 Network 8000 Cause The MNL, MNB, MicroNet 2000 and Network 8000 controllers have the capability of working with values from -163.83 to 16,383 and never use more than 2 digits after the decimal place. This is something that all of the controllers have used for many years. This is documented on page 25 of WorkPlace Tech Tool 4.0 Engineering Guide (F-27254). Resolution In certain applications where it is necessary to read very small values beyond 2 decimals, a work around has been used.  The technique should only be used by those who fully understand the concept and its implementation.  The technique to overcome this is to set the output scaling factors of the Analog Input object (in WorkPlace Tech) to values at a factor of 10 or 100 (or other suitable number) thus giving the resolution and therefore (no loss of) accuracy that is required.  This requires scaling the value down by the same factor at the head-end (or wherever) to get the proper and accurate reading.  Multiply the scale properties by a factor then divide by the same factor for display or logic calculations. Example:  A pressure transmitter that reads a pressure range of -.25 to .25 in. wc at 4 to 20 mA, the Analog Input properties needed for such a transmitter would be as in this table: Input Low Value:     4 mA Scaled Low Value:  -.25 inwc Input high Value:     20 mA Scaled High Value: .25 inwc There is an issue with a device that has such small sampled values.  The controllers can only register at most 2 digits after the decimal.  Therefore the controller can be fooled by setting the properties such that the controller thinks that it has a device transmitter attached that reads pressures from -25 to 25 In. WC.  This is a factor of 100 and all values would be 100 times larger than the true reading.  This of course needs to be accounted for in any calculations and GUIs.  The properties for this would be as in this table. Input Low Value:      4 mA Scaled Low Value:  -25 inwc Input high Value:     20 mA Scaled High Value: 25 inwc In using this technique, remember to factor the number when displaying it or using it with other logic.  Since the controller can use negative numbers no smaller than -163.83, no properties can be entered smaller than that value.  In the table below the same transmitter is used but a factor of 1000 is used for the properties.  This can not work due to the scaled low value being less than -163.83. Input Low Value:     4mA Scaled Low Value: -250 inwc Input high Value:     20 mA Scaled High Value: 250 inwc The workaround is well proven and sufficient to satisfy needs.

Issue Infinity Schedule Standard days and exception days clarification Environment Infinity Cause Information on schedule Standard days and Exception days Resolution Schedule Standard days and exception days clarification When editing standard or creating exception days/range of dates it is important to understand what is really taking place here in order to avoid any issues. Standard days are recurring days from week to week. You can alter the week to week days if you want the same schedule week after week and also have multiple events on each day if desired. Exception days have a higher priority than standard days and once you assign an exception day or range of dates to a schedule you will be overwriting the standard day for the day/dates that your assigning to. For example... if you have a standard day of 8am-5pm and assign an exception day of 9pm - 10pm to one of the standard days, what will happen is that the date the exception is added to will have one event for that day of 9pm - 10pm. If you still wanted the 8am-5pm event as well, you would need to add that to the same exception list  

Issue Valve Linkage Kits for Hazardous Location Gear Train Actuators that mount on TAC Globe Valves: VB-7XXX & VB-9XXX. Environment Valve Linkage VB-7XXX VB-9XXX Cause Part number for Valve Linkage Kits. Resolution Linkages are AV-291, AV-293, AV-295, AV-296 Reference literature # F-27441.

Issue Can not discover the proxy points for an UNC under the ObixNetwork of a Niagara G3 ENS.  Nothing shows up when a Discover is performed. Environment Niagara G3 Cause Obix Thread Pool count set too low in ENS Resolution Increase Obix Thread Pool count in the ENS ObixNetwork Property Sheet. Expand Drivers in the ENS Right-click on the ObixNetwork and select Property Sheet Expand the Thread Pool property Increase the number of threads

Issue Email notifications fail to send from the I/A Series R2 Enterprise Server. The error message displayed is: datax:nohandler for: notification Product Line TAC IA Series Environment I/A Series R2 Enterprise Server Cause The NotificationService in the Enterprise Server station has its archiveMode property set to archive_disabled . This is the default configuration and prevents notifications from being processed. Resolution Update the Enterprise Server station configuration: Open the NotificationService settings in the Enterprise Server station. Change the archiveMode property from archive_disabled to archive_local . Save and restart the service if required. This change enables notifications to process correctly.

Issue When using STR101 to STR-107 connected to a TAC Xenta 121-FC, the LED Mode indicator will be default allocated to the Y1 output on the TAC Xenta 121-FC, which is the only analog output on the TAC Xenta 121-FC device. Environment TAC Xenta 120-FC STR-101 STR-102 STR-103 STR-104 STR-105 STR-106 STR-107 Cause When using any of STR-101 to STR-107 connected to a TAC Xenta 121-FC, the LED Mode indicator will be default allocated to the Y1 output on the TAC Xenta 121-FC device, which is the only analog output on the TAC Xenta 121-FC device. Resolution In ZBuilder, it is possible to move the Status LED from the default location at Y1 to K1-4. In this case you also need to have an external power supply with 5 Volt DC for the LED indicator. It is also possible to use 24 Volt AC power supply for the LED indicator, however this will make an incorrect temperature reading of about 0.5 degree C. In this case, add a 5 kΩ resistance (4.7 - 5,1 kΩ) ¼W in one of three possible positions: Between G and KC1 Between K1 and LED 16 Between Mx 15 and M. The resistor must be placed outside the STR device.

Issue What is the BACnet address and BACnet object ID for the Xenta 913? Environment TAC Xenta 913 Cause The Xenta 913 does not have those features since it's not a BACnet device. Resolution The Xenta 913 is a gateway that translates the BACnet objects so that they can be read by for example Lonworks devices. It is not a native BACnet device itself, hence it doesn't have a BACnet address or a BACnet object ID.  

Issue Access control site where doors are typically held opened during business hours don't want annoying alarms during the day, specifically the site wants door ajar alarms sent only from 5:00 PM (17:00) to 8:00 AM (08:00) Environment CyberStation Cause Configure a separate Event Notification with recipient time range specified in 'From Time' to 'To Time' columns. Resolution When configured as above the alarms associated with the notification object will be logged in the database but not displayed in the Alarm Viewer during business hours.

Issue Does Niagara G3 support or use the Service Location Protocol (SLP)? Environment Niagara G3 Cause Query made by an end customer Resolution No.  Niagara G3 is not aware of or uses the Service Location Protocol (SLP).

Issue Can Network 8000 Microflo or CVV-80000 series controllers be integrated using the Niagara R2 GCM driver? Product Line TAC IA Series Environment Niagara R2 Network 8000 controllers connected via GCM-84000 GCS bus communication Cause Clarification needed on architectural compatibility and integration method between Network 8000 controllers and Niagara R2 using the GCM driver. Resolution Yes, integration is supported. The Network 8000 controllers connect to the GCS bus of a GCM-84000 controller. The GCM database contains VVBOX blocks, which interact with Microflo controllers. These VVBOX blocks can be read and written using GcmGeneric objects within a Niagara R2 UNC station. Key Notes: Ensure proper configuration of VVBOX blocks in the GCM database. Use GcmGeneric objects for data exchange between Niagara R2 and Network 8000 controllers.

Issue The UNC-520-2 in an R2 system displays an “Authentication mismatch” error for an MNL-800 controller. How can this error be corrected? Product Line TAC IA Series Environment I/A Series R2 MNL-800 Controllers Cause The Authenticate property in the LonWorksService does not match the setting in the MNL-800 shadow object. One is set to True, and the other is set to False. Authentication is rarely used due to high overhead, so it is generally recommended to disable it. Resolution  Verify Authentication Settings In LonWorksService properties → Netmgmt tab In DynamicDevice shadow object → Engineering tab In MNL shadow object → General and Engineering tabs Disable Authentication In WorkPlace Pro: Open the station LonWorksService Highlight affected shadow objects From the menu, select Commands → disAuth → Yes Note: An error may appear even if the action succeeds Recommission and Rebind Recommission each Lon device (reset if commissioning fails) Rebind all affected bindings Recommendation: Set Authenticate = False in both LonWorksService and MNL-800 shadow object properties.