Issue It is recommended to save often when working with Menta. Product Line TAC Vista Environment Menta Cause We have experienced lockups of Menta when we conduct very long programming sessions. Resolution Save often. When you take a break, shut down Menta and then restart it when you return. This will help you to avoid losing time should Menta freeze up which is known to happen. It is good practice to let Vista DB folder structure be the file cabinet. When a change is required, export the application from Vista, make the changes, then re-import to Vista and download the controller. This will keep your field environment in synchronization with the operator interface.

Issue Transferring a Vista Database from one computer to another. Error when attempting to start TAC Vista Server: Insufficient object database authority to start the TAC Vista server Product Line TAC Vista Environment Vista Database Cause The database files are stored on the hard drive of the server computer. To move it to a new PC, it can be as easy as copying and pasting the database folder. While it is still recommended that you use the Vista backup function when moving databases, it is also possible to directly copy the files. It is not uncommon to burn a CD containing these files due to storage media size constraints, and the request has a permanent backup of the database. The user should be cautious when copying those files from the CD to the PC since by default these files will be flagged as "READ ONLY". This will result in an error when you start Vista Server similar to the error shown below. Resolution When copying the database files, they should be selected and the READ ONLY flag removed in the properties screen. Alternatively, zipping the files before copying them to the CD will avoid this issue as when they are unzipped on the new PC, they will not be flagged as "READ ONLY".  

Issue How to generate an alarm in TAC Vista, if some event happens in Modbus units. Generating alarms in Vista from Modbus devices. Product Line TAC Vista Environment TAC Vista 5.x Xenta Servers Xenta 511, 527, 701, 711, 721, 731 (since Vista 5.1.5), 913 Cause It is possible to see alarms generated in Modbus devices in TAC Vista but these will not automatically create an alarm that appears in the alarm pane. Resolution Create a change of state object that is connected to the alarm signal from the Modbus device. If the Modbus device goes offline the value will remain at its last polled value. In this case, there may be no alarm generated so you can also monitor the online option in the Modbus device template to give an alarm that the Modbus device is offline.

Issue How does Xenta Server poll Modbus registers? Does it poll all registers that are specified in the device template or only the active points (such as a value displayed on an open graphic in Vista or on a web page in Xenta Server)? Product Line TAC Vista Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 Cause Understanding how the communication will appear on the wire (whether it is Modbus TCP/IP or RS-485) can help with everything from setup to troubleshooting. Resolution The Xenta Server will constantly poll all registers specified in the device template They do not have to be defined in any value pages or graphics. Just by being defined in the device template, the Xenta Server will poll them constantly. The order of the polling will be in the order they have been defined in the template. The cycle time will depend on how many registers are defined and the response time from the device being polled.  To see the polling time and response time a log can be taken of the Xenta server communications, the process for setting up these logs refer to the following article: Setting up a Modbus, M-Bus or BACnet communications log in a Xenta 5/7/9xx

Issue After an upgrade to EBO version 3 the  "Alarm State Sort Order" in EBO Webstation is not following the  "Alarm State Sort Order" set in Workstation for certain Alarm Views. Workstation:   Webstation: Product Line EcoStruxure Building Operation Environment Building Operation Webstation version 3.0 and later Cause This issue is only seen on Alarm views upgraded from a version earlier than 1.9 to EBO 3.0 or later The problem is that in EBO version 1.9 Webstation did not follow the sort order for Workstation, back then the sort order in the alarm view in Workstation and Webstation was separated. And the default sort order in Webstation was "Triggered time" when upgrading to version 3 the upgrade does not change the sort order for Webstation. So after the upgrade the sort order in the alarm view is "Triggered time" and it will not follow the sort order from Workstation.    Resolution In EBO Webstation version 3 click on the "Filter" button in the Alarm view. Click on "Sort" and remove "Triggered time", click OK In Workstation open the Alarm view and right-click, Open Alarm view settings and click on "Reset standard layout to standard default"  

Issue When trying to upgrade a SmartX server from 3.0.x.x to any hotfix build, you get the following errors: Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Device Administrator Cause This is an issue within 7z. The path becomes too long on the unzipping of it. In 3.1 and onwards, only the GUID is used as the folder name. In 3.0, its is the file name + GUID which causes the path to become too long. Resolution Rename the firmware file so that it is shorter in length.

Issue Some Modbus registers contain separate bits to stand for different values. Sometimes additional bits need to be added to the device template in Vista. Product Line TAC Vista Environment TAC Vista Xenta Controllers Modbus Cause This kind of application is required for some projects.  Resolution Create a new device template. Fill the name, full address and other information of the register. In the BitMask column, fill the Start and Stop bit of the register. For example, if only the 2 nd to the 5 th bits are needed, then fill “1” in the Start bit while “4” in the Stop bit. Then only the bits needed are added into the device template. The bit numbers to read are different than the start and stop BitMask numbers due to the fact that the first bit in a register is bit number 0.

Issue There are no minimum current or wetting currents shown on the datasheets. Product Line EcoStruxure Buildings Operation Environment DO-FA-12 and DO-FA-12-H IP-IO Form A, B and C relay contacts Cause The relay outputs are not working since the minimum or wetting current was not maintained and the contacts of the relays have filmed up giving incorrect control. Resolution There are several relays used across this range of controllers and to ensure good low current operation, the minimum or wetting current should be 1milliamp at 5volts or greater. Wetting current is the minimum electric current needing to flow through a contact to break through the surface film resistance of a contact. It is typically far below the contact's nominal maximum current rating. It should also be noted that these controllers may be monitoring third party devices through their status or fault relays. An example of this would be an IP-IO monitoring a VFD for status. The IP-IO inputs will supply 3milliamp at 24volts. To ensure good lifetime operation of this output from the VFD, ensure this is within the VFDs range of minimum or wetting current.

Issue Some links in graphics are unresponsive on Advanced Display when running EBO 1.9.4. Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display V2 Building Operation Advanced Display V3 EcoStruxure Building Operation v. 1.9.4 Cause The links that are unresponsive are trying to open the target in a floating window. This is not supported on Advanced Display with WebStation when using EBO v. 1.9.4. More specifically the graphics script function is not supported under the conditions mentioned above. invoke("Link", "OpenInFloatingWindow"); Resolution Use alternative arguments other than "OpenInFloatingWindow" such as "OpenInNewWindow". See the WebHelp Section Invoke Function for more information about the Invoke function.

Issue Accessing WebPinpoint graphics from a web browser causes one of the following errors…   Failed CreateDNWACServer. Cause:Object reference not set to an instance of an object. URL:HTTP://eceheatsrvr/DNWACServerFactory DNWACServerFactory /WACServerFactory.soap   Failed creating remote objects. DotNet framework is missing.      Product Line Andover Continuum Environment Continuum webClient Server MicroSoft Windows XP MicroSoft Windows Vista MicroSoft Windows 7 MicroSoft Windows 10 MicroSoft Windows Server 2003 MicroSoft Windows Server 2008 Cause User Account Control redirects files to a different folder than expected by WebClient. User permissions are interfering with the WebClient. A variety of other configuration issues may cause this problem. Resolution User Account Controls Redirection The WebClient installation guide goes into detail about why MicroSoft Windows includes User Account Controls redirection. Follow the procedure outlined below.   Give "Everyone" permissions to the C:\Program Files\Continuum and C:\Program Files\Continuum\DNWACServerFactory folders In Windows Control Panel > User Accounts and Family Safety > User Accounts, select an Administrator user on the PC and select User Account Control Settings. Move the slider all the way to the bottom to Never Notify and select Ok. Follow the instructions in the webClient Installation guide section called "Configuring Graphics for webClient: Windows Server 2008, Windows Vista and Windows 7". Site may be setting User Account Control with group policy and setting it upon reboot of the PC to a setting other than Never notify. A batch file may be used to turn User Account Control off before launching WebClient. A Google search for doing this would be needed and is beyond the scope of this article. Each host that will be running a web browser WebClient session should have also have User Account Control settings set to minimum.       Web.config has not been correctly modified   Using Windows Notepad as an Admin user, modify the web.config file which is located in the c:\program files\continuum\dnwacserverfactory folder. Delete the text and replace with the text below, replacing WORKSTATION1 with the host name of the host computer.  This must be done on all hosts which will run WebClient browser sessions. <configuration> <system.runtime.remoting> <application> <service> <wellknown mode="Singleton" type="DNWACServerProxy.WACServerFactory, DNWACServerProxy" objectUri="WACServerFactory.soap" /> </service> <channels> <channel ref="http" machineName="WORKSTATION1"> </channel> </channels> </application> </system.runtime.remoting> <system.webServer> <security> <requestFiltering allowDoubleEscaping="True"/> </security> <directoryBrowse enabled="true" /> </system.webServer> </configuration>     Allow Double Escaping   If for some reason editing this file is still not working. Try the following: In Start >Control Panel > System and Security > Administrative Tools > IIS Manager (Not IIS6) Expand the tree on the left for the webserver name. ie. Webclient1 Expand Sites Expand Default Web Site Click DNWACServerFactory Double Click Request Filtering In the right-hand column select Edit Feature Settings Check Allow Double Escaping and click OK Click on the Default web site and in the far right column click Restart     Test Authentication pass-through for SOAP errors   In IIS Manager; Expand Server> Sites> Default Web Site Left-click on the DNWACServerFactory, on the far right column Select the Basic Settings link Click the Test Settings button. If Authentication pass-through is showing red follow this procedure Click Close Click Connect As> Add a windows user and password that will be used for WebClient Click the Test Settings button Authentication pass through again and it should now show green Perform a local reboot on the WebClient server Test Webclient Graphics     Make sure that the browser PCs are logged in as a Local Administrator for the WebPinpoint and ActiveX installation   Internet Explorer>Tools>Internet Options>Security>(select Zone i.e. TrustedSites)>Custom Level button Make sure that 'Download signed Activex controls' and 'Download unsigned Activex controls is set to prompt or Enable, since the default setting on many web browsers is Disabled.       Add the Webclient PC as a trusted site to the browser PCs   In some configurations, you may need to add the IIS computer into Internet Explorer as a trusted site for each browser. In Internet Explorer: Select Tools > Internet Options > Security > Click Trusted sites > Click Sites Type in http://yourservername/WebClient and click Add (Ex. http://tacweb/WebClient) Deselect the checkbox for Require server verification (https:) for all sites in this zone.  Click OK and then OK again Close Internet Explorer and retry accessing WebPinpoint     Be sure to configure the application pool for 32-bit applications on 64-bit operating systems.   On 64-bit Operating Systems perform the following steps: Open IIS Manager. Expand the computer name in the left-hand pane and click on Application Pools in the system tree view. Select DefaultAppPool and click Advanced Settings. In the Advanced Settings dialog box, change the Enable 32-bit Applications option to True. ** When using 1.94 SP1 and above, check the application pools .net version selected and make sure that the Identity is set to "Network Service" Name                           .Net Version ASP NET v4.0 4.0 ASP NET v4.0 Classic  4.0 Classic .NET AppPool  2.0 Default AppPool   2.0 WebClient 4.0       DNS issues   Even when you may not be seeing red x’s in Pinpoint View>Options>Web locations and you are able to browse to pin files though IE, WebPinpoint may be giving you a graphic URL error. Try entering using the IP of the WebClient server in place of its DNS name for Pinpoint View>Options>Web locations. Also try using the WebClient Servers IP address in places of the its DNS name and also for accessing WebClient through the browser. For example http://10.159.100.125/WebClient       WebPinpoint fails to register the DNWACClientProxy.dll and tlb files when installed.   On the from the client (web browser) host, perform the steps below:  Close WebClient browser if it is running. Open command line in Administrator mode. Run the batch file C:\Programs Files (x86)\WebClientPinpoint\WPPRegistrationClient.bat     Other items to check:   Disable Windows Defender Turn off all 3 firewalls Shut off SPS software protection service when installing. Run Internet Explorer as an Administrator to make sure the ActiveX controls are being installed

Issue Updating an exposed property in Webstation doesn't change the exposed attribute. An example is an ellipse having the Fill color attribute exposed, but when updating the exposed property the ellipse does not change color. Right click the graphic in the tree view and choose Properties. Click the Exposed tab Update the property (1) and click OK (2) The fill color of the ellipse does not change This works fine in Workstation. Product Line EcoStruxure Building Operation Environment Building Operation Webstation Cause The Expose object has a property called Public. This value should be True if the exposed property should be visible and editable from Webstation or Workstation. The cause of this problem is that the value is true instead of True. TGML is case sensitive. Workstation is more forgiving, so the color is updated when doing the same procedure in Workstation. Resolution Update the value of the Public property in the Expose object from true to True. If there are many objects to be checked, a search and replace can be undertaken in the Source view.

Issue Attempting to set the Retain Level attribute of a Value object results in the following error: Saving Changes Invalid data 'Prohibit to retain both Value and priority properties at same time: (point name) Invalid data Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation 3.1 Cause Prior to EBO 3.1, it was possible to set retention levels on both the Value attribute and individual members of the Priority Stack. Starting with 3.1, that is not allowed and will give this error if you attempt to change the retain level setting of a Value that already has it set on a Priority, or vice versa. For systems configured in EBO 3.0 or prior that are upgraded to 3.1, the now invalid double-retention will be resolved automatically during the upgrade by retaining the Priority Stack retention level and setting the Value attribute Retain Level to No. Resolution Only set the retain level on one attribute of an object. The best attribute to retain is the Value. Setting Retain Level to Cold Start or Warm Start on the Value will also retain the full priority stack on a power failure or restart. Check the retain levels of each member of the priority array and ensure all are set to "No" and then set the Retain Level of the Value attribute to "Cold Start" or "Warm Start." To clear the retain level of individual priorities: Open point's Property window Click the Command tab Click the gear icon next to a Priority level, most likely starting with Priority 16. Check the checkbox for Retain level and set to No. To set the retain level on the Value attribute: Open point's Property window Click the gear icon next to the value Check the checkbox for Retain level and choose the desired level.

Issue Is it currently supported in EcoStruxure Building Operation to make EWS requests with users managed by Active Directory (Windows user)? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause The EcoStruxure Building Operation software provides two methods to log on to the system, as a Windows user or as an EcoStruxure Building Operation user. Windows User A Windows user account is mapped to a Windows Active Directory user account group. Log On as an EcoStruxure Building Operation User When logging on as an EcoStruxure Building Operation user, you authenticate yourself with an EcoStruxure Building Operation account user name and password Resolution EWS only supports login to SBO domains (with Challenge Response, RFC7616) and NOT Windows domains added into SBO. It is not possible for an EWS request to authenticate using a Windows user only an EcoStruxure Building Operation user.

Issue Not possible to download an application(.mta file) to a Xenta 401, Xenta 301/302, Xenta 281/282 The download process looks fine until the file transfer should start. Then it just hangs and nothing happens. Product Line TAC Vista Environment Xenta 401 Xenta 301/302 Xenta 281/282  Cause The problem is that a file transfer is already running for something else (trend logs or alarms) and only one file transfer can run at a time for each LON network. Resolution Shut all graphics pages and try again. Restart the Vista Server and try again. If that doesn't help, restart the Xenta's to stop the ongoing file transfers If that doesn't help, ensure you are running TAC Vista 5.1.9 and  Start the TAC Vista server communication log, let it run for 10 minutes and send that to your local technical support for investigation. To start the communication log: open the Log tab in the TAC Vista server, open "Comm.Log", Set the Physical layer to "Active" The log will be saved in the $Log folder in the Vista database and called PL_"network name"

Issue In a TAC Xenta group, there must be one TAC Xenta which is the master, which TAC Xenta device in the group is most suitable to be the master in the group? Product Line TAC Vista Environment TAC Xenta 401 TAC Xenta 301/302 TAC Xenta 281/282 Cause TAC Xenta group master devices have additional communication responsibilities to the Vista Server -- reporting online/offline status of their group members. Resolution During network planning, choose the master device to be the group member with the: least amount of SNVTs least TACNV least amount of I/O modules least memory used least communication least processing load If adding controllers in an ad-hoc manner, the first controller commissioned must be the group Master to enable communication with any other controllers. If the group master is offline, the whole group will be offline. Remember that when a controller is added to a group all controllers in that group need to have the application and parameters downloaded. If the Master Device is changed after the group is set up you will also need to download every controller, Download the new Master first so that as you download the rest of the controllers they will come online after the download.

Issue Is SP-MNR2 compatible with SP-C-WEB and SP-ACX? The documentation only refers to "controller" and not SP-C/SP-C-WEB/SP-ACX specifically. Product Line Security Expert Environment Security Expert Security Purpose COMMS Expander (SP-MNR2) Security Expert WEB Controller (SP-C-WEB) Security Expert ACX PCB Controller (SP-ACX) Security Expert Controller (SP-C) Cause Compatibility information needed to make a correct solution design. Resolution The SP-MNR2 is compatible and will work with both the SP-C-WEB and the SP-ACX, as well as the SP-C, with no issues.

Issue Empty Legacy Code and Error converting PE code seen in Continuum Conversion Tool Many objects shown as "Partially converted" Product Line EcoStruxure Building Operation Environment Continuum Conversion Tool Infinet i2 BACnet B3 PE programs and functions Cause The Continuum dump file converts, but numerous errors are seen as below PE programs and functions are empty in line with the error Empty Legacy Code and Error converting PE code Resolution Create a new Continuum text dump by highlighting the b3 or Infinet controllers only (rather than the Network Controller (bCX, NC2 etc)) and create a text dump. This is achieved by right clicking on the highlighted devices, choosing "Send To" then "Text File...". Use this new text file in the Continuum Conversion Tool. If this converts correctly then there is an issue in the Net Controller configuration. Alternatively check the Net Controller configuration, specifically the "CommPort", in this example; the first 'CommPort' line should not exist and is the problem, once removed, the conversion then proceeds correctly. 'TYPE         : DEVICE                              : NAME    : TEMPLATE : DEFAULTMODE : BAUD           : ALIAS CommPort : SiteName\ControllerName : 6780       : False          : Printer                : Baud9600    : CommPort : SiteName\ControllerName : comm1   : False          : Infinet                 : Baud19200  : comm1 CommPort : SiteName\ControllerName : comm16 : False          : LON                    : Baud19200  : comm16 CommPort : SiteName\ControllerName : comm2   : False          : NotConfigured    : Baud9600   : comm2 CommPort : SiteName\ControllerName : comm3   : False          : AutoSet               : Baud9600   : comm3 CommPort : SiteName\ControllerName : comm4   : False          : NotConfigured    : Baud9600   : comm4

Issue Direct Connect to Xenta 527-NPR Product Line TAC INET Environment I/NET Xenta 527 Xenta 527-NPR Cause Newer versions of Xenta 527-NPR with 5.1.0 and 5.1.1 revisions are unable to be directly connected to the system. Resolution Using the FTP connection through IE (Internet Explorer) to connect to the device. Log on using the root username and password Now go to sys/system/hwconfig.cfg Copy out the hwconfig.cfg file and open it with Notepad Modify the part that says serial_A_function="7" and change it to "5" Save this and now copy it back in again. Restart the device Start I/NET and the direct connect through the NPR to the system should be working now. Warning: Reloading the system program (such as performing upgrades) will remove this change.

Issue When attempting to open WorkPlace Tech Editor or Monitor an error is displayed stating: A supported version of Visio must be installed for WorkPlace Tech Editor or Monitor to function properly. Product Line EcoStruxure Building Operation Environment Building Operation Workstation WorkPlace Tech Editor and Monitor Cause This message is displayed if WPTE requests Visio be started and Windows is unable to comply. Resolution Confirm the version of Visio loaded is a supported version. If it is then set Visio.exe and SE.WorkStation.IA.wptEd.exe to "run as administrator" and retry. To set a program to always run as Administrator, locate the executable file then right click it and select properties. From the Compatibility tab check "Run this program as an administrator" and then click OK Find the SE.WorkStation.IA.WptEd.exe for the EBO version being used and perform the same process as in step 2+3. See the path below

Issue Users are finding it difficult to locate the settings for Password Expiry on EBO Accounts Product Line EcoStruxure Building Operation Environment EcoStruxure 1.7.1 and later Cause When the standard Administrators User Group is examined (of which the admin account is a member), the Password Expiry, Change Password and Auto Logoff settings cannot be altered.  Everything is greyed out.   Even if a new User Group is created,  while Passwords Change permissions and Automatic Logoff settings can now be adjusted, the Password Expiry is still not available. Resolution For Password Expiry settings select: Control Panel / Security Settings / Password Policy.    All Password options including Password Expiry can be adjusted here and will apply to all users rather than a single User or Group