Issue Configuring and monitoring the Xenta 102-AX is traditionally done through the LNS Xenta 102-AX Plug-In, but how can it be done in a Vista Classic Network where no LNS plug-ins are available? Environment Vista 5 Classic Network TGML Xenta 102-AX Vista Workstation ONLY -- This plug-in is not compatible with Webstation or XBuilder graphics at this time. Cause LNS Plug-ins are not available in a Vista Classic Network. Resolution All of the values that are written to by the LNS Plug-In are public and available through the Vista front end. So if only one or two signals need to be set for each box, this can be accomplished by locating them in the Vista network and writing the desired values to them.  This does require some fairly intimate knowledge of the Xenta 102-AX and Plug-In. The alternative is: Download the Xenta 102-AX TGML Plug-in by clicking the image below.  Unzip the contents to the hard drive. Open the TGML file. Select File > Save As > Vista Database Object Navigate to the first Xenta 102-AX in the network. Drill down into the 102-AX on the same level with Node_Object and VAV_Controller modules. Give the plug-in graphic a name and save. Right click on the Graphic object in Vista Workstation and select Copy Navigate to the next Xenta 102-AX and select Paste Shortcut. Since all bindings are automatically populated with relative bindings, copying and pasting shortcuts will automatically display data for the associated Xenta 102-AX. Repeat Step 8 for all Xenta 102-AXs in the network.

Issue Can multiple Modbus devices be mapped to the same IP address when communicating over TCP/IP? Product Line Satchwell BAS & Sigma Environment Sigma IC3 Modbus Cause This configuration is not documented in the official release notes, leading to uncertainty about its feasibility and implementation. Resolution Yes, multiple Modbus devices can be mapped to the same IP address using appropriate configuration in the gateway.txt file. This setup is particularly useful when simulating multiple Modbus devices using tools like ModSim or when interfacing with a gateway that multiplexes device IDs. Example Configuration ; gateway.txt entries 1,1,3,1,1,0x0001,0,0,1 ;Modsim1 40001 2,1,3,2,1,0x0001,0,0,1 ;Modsim1 40002 3,2,3,1,1,0x0001,0,0,1 ;Modsim2 40001 4,2,3,2,1,0x0001,0,0,1 ;Modsim2 40002 5,3,3,1,1,0x0001,0,0,1 ;Modsim3 40001 6,3,3,2,1,0x0001,0,0,1 ;Modsim3 40002 7,4,3,1,1,0x0001,0,0,1 ;Modsim4 40001 8,4,3,2,1,0x0001,0,0,1 ;Modsim4 40002 ; IP_ADDRESS_TABLE 1,10.158.72.254 2,10.158.72.254 3,10.158.72.254 4,10.158.72.254 Each entry maps a unique Modbus device number to the same IP address ( 10.158.72.254 ) but differentiates them using the device ID and register offset. Important Notes Single Gateway Limitation: IC3 Modbus can only be mapped to a single IP gateway or PC application. No Dual Mapping: It is not possible to map to two applications running on the same PC simultaneously.

Issue Performing an automatic learn or manually commissioning i2/b3 device results in the error "Unknown model number" ACCTrace shows a model number zero Product Line Andover Continuum Environment CyberStation CX/bCX I2/B3 Cause This error can be caused by communication issues. Resolution Verify field bus is properly terminated if required. Follow standard Infinet/MSTP troubleshooting techniques to solve any communication problems inducing the unknown model error.

Issue Receive an error, "Invalid Device " when trying to download an application to an I/A Series LonMark controller with Workplace Tech. Product Line TAC IA Series Environment I/A Series LonMark (MNL-5Rxx, MNL-10Rxx, MNL-20Rxx, MNL-11RFx, MNL-13RFx, MNL-V1RVx, MNL-V2RVx, MNL-V3Rvx) Workplace Tech Cause Typically, this situation occurs when a user runs the Hardware Wizard in Workplace Tech and then downloads a controller without recompiling the application. Resolution See Technical Bulletin TB06-01 for detailed information and a solution.

Issue Key for the standard Door Control Graphic Product Line Andover Continuum Environment Door Control Graphic PinPoint Cause Require a key for the standard Door Control Graphic Resolution

Issue Previously the BACnet Device Id of the controller would default to the devices serial number, this is no longer possible due to the maximum BACnet Device Id being 4,194,303. Serial numbers greater than 800xxx can give an error 'Device Node id is out of range' (1 to 4,194,303) Environment Continuum BACnet Controllers Cause Concern about what the default BACnet Id will be set to a value higher than what is supported or to a value that has already been set to a previous controller. Will this conflict with existing controllers on a site when adding new controllers when all are using the default BACnet Device Id? Resolution There is an internal calculation done that uses the Serial number as a seed to then calculate the BACnet Device Id so that it falls within the 4,194,303 max. This calculated value will be unique to every other Continuum BACnet Devices default BACnet Device Id so you should be fine when newer controllers are being added to existing sites. If you want to ensure there are no address conflicts though you may want to set the value yourself when commissioning the controllers through creating the Device object manually and setting the BACnet Device Id at that time or if the device is already configured delete it from the BACnet side and then edit it from the Infinity side and enter a new and unique device id, then perform a find BACnet devices to bring the device back on the BACnet side with its new device id.

Issue Need to protect Continuum Workstations from Virus and Malware threats. Product Line Andover Continuum Environment Continuum Workstation Cause There are many Anti Virus applications on the market, how to choose which one to use on a Continuum Workstation machine. Resolution We do not qualify any specific Anti Virus applications or definitions for use with Continuum software. You can use whatever Anti Virus you want on the machine Continuum is installed on as long as Continuum was installed when that Anti Virus was disabled as this can hinder files from being copied, dll's from being registered, and registry entries from being created / modified. If there are conflicts with Continuum and the specific Anti Virus application being used, you may need to add the Continuum folder and / or the Continuum processes to the exclusion lists. For details on specific environments that have been qualified with Continuum see Software and Firmware compatibility matrix for older versions of the traditional product lines.

Issue The alarms in the UNCs stop archiving to the Enterprise Server database. The process was working before and nothing was changed. Product Line TAC IA Series Environment I/A Series R2 using the Cloudscape database Cause The size of the Cloudscape database has grown too large. This may cause issues with the system. Resolution Reduce the size of the Cloudscape database by deleting older alarms and logs. Refer to this document for details on how you can delete old alarms and logs. For details on the CloudscapeAdmin utility mentioned in the document, refer to How to remove data for all logs prior to a specific date in a Niagara R2 Enterprise Server.   Switch to using a SQL database instead of the default Cloudscape database if there is a requirement to keep old alarms and logs for a longer period.   There isn't a known limit where the size of the Cloudscape database can grow before the possibility of problems starting to occur. It is different for each site. As a guideline, it is recommended that SQL database be used if the size of the Cloudscape database has to be greater than 2GB.

Issue Configuring a SetPoint in EcoStruxure Building Operation so that the set value of the SetPoint is retained after a Warm or a Cold Start rather than defaulting to zero. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Cause The value retention configuration is not held in the initial properties page of the Analogue Value when used as a SetPoint. Resolution Navigate to the actual value within the properties page of the Analogue Value. On the right hand side of the GUI there is a Configure button. Pressing on this button then takes the user to a sub menu where the Retain level option can be enabled. Once enabled it is then possible to decide whether the SetPoint needs to retain its value under a Warm Start or a Cold Start condition.

Issue In an SCU1284 with a dual address what is the addressing scheme for the "DO's"? Environment I/NET site with Access Control Cause Addressing issue with SCU1284 Resolution In the Dual Address mode of the SCU1284 the "DO's" addressing scheme is as follows First four relays are associated with the first address DOxx00 thru DOxx03. The Last four relays are associated with the second address DOyy00 thru DOyy03

Issue Connection lines will not connect to some objects on the drawing, but will on other objects. The "Snap and Glue" feature was verified per Connecting lines in WorkPlace Tech stay red even when snapped to an object. Product Line TAC IA Series Environment WorkPlace Tech 5.x Windows XP SP3 Visio 2003 Visio 2007 Cause Objects are on the "back" layer. Resolution Select objects or complete drawing Right click Select Shape > "Bring to Front"

Issue How to setup user photos so they are shown when accessing through a Door. Product Line EcoStruxure Security Expert Environment Security Expert Server Cause Unsure how to add photos to users and have them displayed when that user is accessing through Doors. Resolution There is an option for User photos in Security Expert and the Photo Id option is included with the base Security Expert license. With this "Photo ID" feature enabled you will see the Photo tab on the User object and will then be able to add photos to your users.   1. You can associate a photo to your users in the Photo tab of Users | Users.   2. In Monitoring | Setup | Status Page Editor, you can set the Style to Display User Image. Doing this will show the users photo with the access event.

Issue The STR-150 Wall Module with Display is not compatible with Xenta 100 controllers that are earlier than SW-version 1.2. The space temperature (nvoSpaceTemp) is displaying an invalid or default value (either 621.81 degrees Fahrenheit or 327.67 degrees Celsius). In newer versions of Vista the value will display "Invalid Value". Product Line TAC Vista Environment STR-150 Xenta 101-VF Xenta 102-ES Xenta 103-A Xenta 104-A Cause Software for Xenta 100 series controllers previous to version 1.2 is not compatible the STR-150 wall module. Resolution The STR-150 is only compatible with Xenta 100 series controllers that are software version 1.2 or later. If a wall module with display is required for a Xenta 100 controller with software that is older than version 1.2 there are two possible solutions: An identical Xenta controller can be purchased with the latest software version to replace the old controller. An STR-350 stat can be used and connected to the Xenta controller via SNVT bindings.

Issue A new computer has been configured as an InVue Client computer.  In Viewer, when displaying a typical graphic screen, the dynamic values for each OCX is replaced with the words "Access is Denied". What causes this message and how can it be corrected? Environment InVue Wonderware for Intelligent Buildings (WIB) Cause Primarily a Windows permissions issue or incomplete communications setup. Resolution Try each of the following to correct the problem: Make sure DCOM is enabled (Start -> Run -> dcomcnfg) and running on both the client and server computers. Use "telnet" command to see if port 135 is open and available for DCOM. Use dcomcnfg.exe to modify its settings: On Default Properties tab, verify that "Enable Distributed COM" is checked, default authentication level is "Connect" and Default impersonation level is "Identify" On Default Security tab, Default Launch Permissions - click Edit ... button, verify that the Administrators group is shown and has "Allow Launch" permission" On Default Security tab, Default Configuration Permissions - click Edit ... button, verify that the Administrators group is shown and has "Full Control" permission" Windows login account for the client pc must exist on the server as well -- same username and password -- administrative privileges mandatory Ensure wwuser.exe (factorysuite/common folder) reflects the local computer name and administrative user account Re-do the DDE Shares as outlined in Tech Bulletin 02-26 on the client computer. Turn off any firewall and disable/remove anti-virus / anti-spam program or service.

Issue Bindings on every I/NET point in a converted graphic show the Server 1 instead of the correct server name Environment StuxureWare Building Operation Workstation I/NET 2.42 or higher Cause The INET Interface path parameter set in the Export INET Graphics to TGML converter does not revert to default after each conversion.   If the parameter is set to: /Server 1/INET Interface All binds will use that path even if the Server is named 'Building 1' Resolution OPTION 1 - Reconvert Graphics Change the INET Interface path to reflect the correct location. The most common is: ~/INET Interface The '~' symbol points the remainder of the path to the Server that the user is logged into during the import. If the user is not logged into the correct server, this may cause errors. INET Interface is the default name of the I/Net Interface but can be changed. For a site where the I/NET interface is named 'INET' and the Server is name 'Enterprise Server' the INET interface path could be set to: /Enterprise Server/INET OR ~/INET Option 2 - Change Server Name If every path on the I/NET interface references the incorrect server name: Change the Server Name to match the bindings Verify that the bindings now function with the matching Server Name Change the Server Name back to the desired name. The bindings should follow the name change.

Issue What are the currency units 1-10? Environment StruxureWare Building Operation site Cause When adding a unit to a value, you have the choice of Currency units. Currency units 1 through 10 are not defined. Resolution Using Workstation units, Currency1…Currency10 BACnet specific and to be used in BACnet devices rather than in the StruxureWare Building Operation system. These currency units have absolutely nothing to do with money (US dollar $, GBP £, Euro €, etc.) Currency units (1-10), are to be able to translate BACnet units using StruxureWare Building Units. Basically, if a site encounters a BACnet device which is using one of those units, Building Operation needs to be able to convert it to something displayable in Building Operation. The main reason they are there is so Building Operation can comply with the “BACnet workstation” requirements. In most cases the customers need for setting a currency unit to a value could be solved by simply adding the label containing the currency symbol after another label stating the value itself into a graphic.

Issue Alarm Forward and Log settings with enhanced alarm logging causes unnecessary network traffic Product Line Andover Continuum Environment Continuum Workstation Cause There has been some confusion about whether to select forwarding and logging on the recipient editor located within the eventnotification editor. Resolution In 1.5 and later versions of Continuum, a new alarm engine was introduced. To use the new alarming engine, select the enhanced alarming check box located in the database initialization editor. The enhanced alarming feature will perform both the forwarding and logging of an alarm. If the enhanced alarming feature IS SELECTED, then the forwarding and logging of a specific PC will not need to be checked ***. If enhanced alarming IS NOT SELECTED, then you will need to specify a forwarding and logging workstation. **IMPORTANT: Intrinsic alarms of type Controller Status, Fault Status and Logon Status still need their corresponding Event Enrollment object configured for logging and/or forwarding as before. If enhanced alarming, forwarding and logging are selected, there will be no duplication of alarms, but will cause unnecessary traffic on the network. If all three are selected and are on a very busy network, you may experience workstations appearing as offline. This can be intermittent depending on the amount of network traffic generated on your site. To check the settings of your enhanced alarming features, open up the database initialization editor and select either the server or stand alone button to view your settings. If your setting is not selected and you want to use the new alarming engine then select the feature. Make sure you restart ALL workstations when you change this feature. In 1.7 and later versions of continuum there is also an enhanced alarm delivery selection. This selection uses Microsoft's Messaging Queuing Service to deliver alarms. This feature allows multiple workstations to share the load of delivery of alarms to the recipients of an eventnotification. Thus reducing the work load of just one workstation to handle the delivery. The enhanced alarm delivery feature, will be best utilized when working with multiple workstations.

Issue Even though "Clear when enabled" is configured on a trend log, the trend data is not cleared when the log activation is triggered. Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Trend Logs Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause The property "Clear when enabled" only affects the trend data when the trend log goes from disabled to enabled. This is not the same as the activation method of the trend log. Activation method changes the Status from Stopped to Started etc. Resolution To activate the "Clear when enabled" setting configured on the trend log: Select the Trend log, right-click on it and select Activation, then select "Disable trend log". Select the Trend log, right-click on it and select Activation, then select "Enable trend log". See the following online help topics for further information on Activation: Trend Log Activation Actions Menu - Activation Submenu

Issue When using Conversion Coefficient slope m = 1.0, the return to normal (RTN) Alarm Limit on an AI point appears to have a built-in offset. Environment I/NET Seven - Analog Inputs (AI), all revisions. Cause There is a built-in hysteresis of 3 counts on the return-to-normal settings for both the low and high limit setting of an analog input (AI) point.  When using a conversion coefficient slope (M) of 1, this provides a 1:1 scale between counts and engineering units which could provide undesired results.  So this built-in hysteresis needs to be considered when using a slope (M) of one or higher on analog input alarm points.    Resolution Consider using a conversion coefficient slope (M) of 0.1.  Alternatively if this is not possible, creating an internal AI point (using a m = 0.1) or a DA and applying a calculation to reflect the points value or alarm state as required as a workaround.

Issue Difficulty integrating Eaton Series 2000 Xpert Power Meter with Niagara R2 using Modbus RTU due to unclear documentation on register map differences between IP and RTU protocols. Product Line TAC IA Series Environment I/A Series UNC Eaton Series 2000 Xpert Power Meter Cause The Eaton documentation does not clearly differentiate between Modbus register maps for TCP/IP and RS-485 RTU, leading to confusion during integration. Resolution Locate RS-485 Map: The Modbus RTU RS-485 register map is found under Eaton IQ-250/260 meter documentation, not under Series 2000. Access Embedded Utility: Use the embedded setup and monitoring software on the Eaton Power Meter. Click the Help button to upload the Modbus map as an Excel spreadsheet. Note: This map represents the TCP/IP Modbus register map, not RS-485. Connection Details: Access via a standard internet browser using Ethernet cable. Default IP address: 192.168.1.1. Register Calculation: Convert Eaton’s decimal register number to standard 5-digit Modbus register by adding 40000. Example: Register #1000 → 40000 + 1000 = 41000 (Volts Phase A - Neutral).