Issue How can the TAC Xenta OP be used with a TAC Xenta 100-series controller? How does the OP identify which TAC Xenta 100 controller it's communicating with? Which OP mode should be used? Product Line TAC Vista Environment TAC Xenta OP TAC Xenta 101 TAC Xenta 102 TAC Xenta 121 TAC Xenta 122 Cause   The TAC Xenta OP panel allows access to input and output signals from a TAC Xenta 100-series controller. Identification of the specific controller is achieved via a Service Pin message. If connected directly to a TAC Xenta 100-series controller or a STR100-series device attached to it, the controller automatically sends a Service Pin message. If connected elsewhere on the network, you may need to manually press the Service Pin on the desired controller. For troubleshooting connectivity issues, refer to: “No Answer” on an OP when connecting to a Xenta 280/300/400 Resolution 1. Configure the TAC Xenta OP Plug in the TAC Xenta OP. Hold Back and Enter for 3 seconds to access the OP Service Menu. Scroll to Option 10: OP Mode. Set “Xenta 100” to ON using the + key. Press Enter. Set “Mode” to TAC using the + key. Press Enter twice to restart the OP. 2. Connect to a TAC Xenta 100-series Device Plug the OP into the OP jack on the TAC Xenta 100 controller or a connected STR100 device. When prompted “Press to access Xenta 100”, press Enter. At “Connecting to Xenta 100…”, wait or press the Service Pin on the controller. Press Down to proceed. 3. View and Modify Network Variables At the NV Index? prompt, use +/- to select the desired network variable index. Press Enter to view the signal. If the value is an input: Use +/- to modify the value. Press Enter to accept. If the signal is a bit-based application option: Press Enter to navigate between bits. Use + to change the bit value. Press Enter to confirm.

Issue The RUS.exe utility throws the following error when an attempt is made to activate a license for the first time on a host machine. Product Line Andover Continuum Environment Continuum Cyberstation Hasp Sentinal Continuum Virtual License Cause While it is not clear what causes this error, Product Support has occasionally run into cases where a change to the host machine configuration in some way taints the license fingerprint.  In such cases the license activation file (.v2c) is no longer applicable to the host machine, even though it was created produced from a license information file (.c2v) that was created on the same host. Resolution   There must be no configuration changes made to the host machines on which Continuum will be licenced from the time that the license information file (.c2v) is created until the time when the activation file (.v2c) is received and applied using the RUS.exe tool. This includes the following virtual machine settings... Memory allocation Processor Hard Disk Network Adapter This the following hardware on the physical machine that hosts the virtual machine. Hard drive Network Adapter Memory Processor In some cases when a Cloned host error is occurs upon applying the license activation file (.v2c) to the host machine, rebooting the virtual machine has cleared error.  In cases where rebooting the virtual machine does not resolve this issue, the virtual machine instance will have to be deleted and a new vm created on which the license software can then be installed.    A charge will apply in cases where it is necessary to generate a second activation file (.v2c).     

Issue Requirement to set the BACnet max master setting on a SE8000 series room controller Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Automation Server SE8000 BACnet MS/TP Cause The BACnet max master setting is not available to be set locally on the SE8000 room controller Resolution The max master setting of the SE8000 can be changed in EcoStruxure Building Operation Workstation.  Add the SE8000 to the EcoStruxure Server Open the SE8000 device properties On the Advanced tab, change the Maximum master property (which is a read/write property) to the required value. 

Issue Error "Initialization Failure" when starting I/NET on a PC that has just been upgraded Environment I/NET Seven I/NET Host Tool Cause Upgrading the version of I/NET on a PC requires that the database also be upgraded. Resolution Verify that the log in name that is used has Admin rights to I/NET Close I/NET and I/O Server, then start DB Create - log in Select the Upgrade Database radio button Force an upgrade on the database to reassign the passwords again Restart I/NET again and it should come up and give you the log in box, put your user name and password and it should start.

Issue Communicating to I/NET on a direct connect requires a cable that has to be connected from the PC to the controller. Product Line TAC INET Environment All versions of I/NET using Direct Connect to controllers. Cause Connecting to a controller from a PC if there are no Net Plus Routers for connectivity over the Ethernet. If a 7798C controller is being used then another programming cable needs to be used for the virtual HHC on that PC. Resolution To resolve this a cable part number CBL-072 connected to the PC and controller. To obtain the various part numbers for the cables, connecting to the iPortal and searching on %CBL% should bring up the required information. Maximum supported cable length is 25 feet (7.62 meters). ***See the comment below on the CBL-072*** Part number for the direct connect is CBL-072 The pin-out for this cable is shown below: Part number for the 7798C is CBL-082 The pin-out for this cable is shown below: Note: CBL072 is for direct connect between the computer and controller. CBL-082 is for programming with Virtual HHC. **********************************************************************  ***The CBL-072 looks to be no longer available From Schneider Electric (9/2017) *** You have two choices on the CBL-072: 1)            Build a new CBL-072 using the Pin-out above. 2)            Convert a CBL-082 into a CBL-072 (see steps below) To convert a CBL-082 into a CBL-072, cut the “Gray” wire connected to pin 5 on the D-Sub 9 connector at the PC end. Then remark the cable label to avoid future confusion on its use. ***********************************************************************

Issue How many Modbus TCP Clients can be connected to Vista via an Xenta 913? Product Information TAC Vista Environment Vista 5.1.X Xenta 913 5.1.X or later Xenta 511 5.1.5 or later Xenta 701 5.1.5 or later Xenta 711 5.1.5 or later Xenta 721 5.1.5 or later Xenta 731 5.1.5 or later Cause When planning a system it's important to know how many devices are required. Resolution A maximum of 40 Modbus TCP clients are supported when communicating via a Xenta 913, Xenta 511 or Xenta 700. Each TCP Client may have up to 100 Modbus devices (see page 4 in the datasheet).  

Issue When doing a conversion from TAC Vista with LNS Network, to EcoStruxure Building Operation, what system should handle the addressing of the devices? What does the Network property “Shared LNS and SBO network” mean? Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista Conversion Tool Cause In a TAC Vista system, running as LNS system, the network is marked as Protected in TAC Vista. This means that all addressing is handled via the LNS system. Resolution After a conversion from TAC Vista with LNS network, to EcoStruxure Building Operation, a flag is set in the Network properties, named “Shared LNS and SBO network” which means that the LonWorks network is shared between LNS and EcoStruxure BMS. LNS is used for network management, such as handling addresses and Lon bindings. LNS has the ownership of the network. EcoStruxure Building Operation is used for downloading application and configuration to the controllers. It does not write in the address table of the Lon device.  This flag should not be set manually.

Issue Cannot select data points of remote nodes to be references in a graphic on the monitor MPM Environment SmartStruxure Lite Multi-Purpose Manager MPM-VA MPM-UN MPM-GW Cause Feature not built-in Resolution When building dashboards on monitor MPMs, only local points can be used in the graphics. To be able to select points of remote MPMs, The Object_Copy script must be used. The script will copy points from the remote nodes to the monitor and make them local to that monitor MPM. This method can be used in ZigBee, Canbus and UDP networks. For example, to copy a point from each of the remote MPMs to the monitor, the script would have to be modified as follows object_list[1] = {tag = "zone1", source_device = "DEV200", source_point = "AV11", destination_device = "ME", destination_point = "AV1"} object_list[2] = {tag = "zone2", source_device = "DEV300", source_point = "AV22", destination_device = "ME", destination_point = "AV2"} object_list[3] = {tag = "zone3", source_device = "DEV400", source_point = "AV33", destination_device = "ME", destination_point = "AV3"}   Important notes: This script increase the monitor's CPU % usage and increases the traffic on the network. Therefore, depending on the size of the network, it is critical not to use more than a couple of points per remote MPM

Issue Configuration instructions for setting up a communications VX Log in the Xenta 5/7/9xx for communications troubleshooting. Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 VXI Cause Configuration instructions for setting up a communications log in the Xenta 5/7/9xx for communications troubleshooting. Obtaining the communications log for a Modbus or BACnet network is crucial in finding communications errors, or other unforeseen problems with integrating to third party devices. Resolution Step by step instructions for creating the communication log for troubleshooting or for data analysis: Log In to the Xenta 5/7/9xx controller and navigate to the Utilities Folder:   Click on the Target System Folder and choose VXI Web Shell Commands:   The command line should appear with VX populated in the command line:   Logging to file in the Xenta controller will first need to be enabled to by typing VX L 1 and press submit:   VXI Web Shell Commands should return a messing indicating logging has been enabled for 1 hour:   After logging has been enabled, the verbosity will need to be set in order to capture each layer of communications on the wire. In the command line type VX V 9 and press submit:   VXI Web Shell Commands should return a messing indicating the verbosity has been set to 9 and what messages you will see with this verbosity level :   Let the communications log run for 5-10 minutes. Create as many changes on the 3rd party wire as possible to get various data changes to and from the Xenta Server.   In the command line type VX O and press submit:   This command will output the communications log the Xenta Server has collected. Highlight this entire output log and copy, then paste it into notepad for archiving or emailing:   To set the communication logging back to default type "vx V 1" or power cycle the Xenta Controller. To stop the logging to file, type "vx L".   For TCP/IP logging you can only monitor one client at a time: Complete Steps 1- 8 above Enter "vx d" This will display a list of the TCP available devices Enter vx d # where # is the number corresponding to the deice you wish to monitor To view the log, follow steps 9 and 10 above

Issue Need for a custom report for the customer, client, user. How to create custom reports. Product Line TAC I/NET Environment I/NET Seven system with the need for Reporting Cause Reports which come with I/NET Seven software preloaded reports may not give the desired report needed or wanted Resolution Clients or Customers often come up with specific reports needed for their site. PSS does not support custom reports, make custom reports for clients, or assist in the development or production of custom reports. You can understand, the report's clients are endless and we simply would be covered up with requests and changes at every site worldwide. It is recommended to take a look at TCON301 (TAC INET Seven Database Connectivity and Reporting) beginning on page 4-1 which explains SevenReports. It is also suggested to look at and compare the different tables and what information they contain. Here you can get a better understanding of reports and take a canned report.  the reports which are available on the install CD and change to fit the needs of your client. This is the fastest and best approach to the manufacturing of custom reports.

Issue Depicting the differences between Bacnet points and Central IO points. Product Line EcoStruxure Building Operation Environment SmartStruxure 1.3 and lower Cause Explanation of difference in points Resolution Creating Central IO points When you create inputs and outputs in a non-BACnet SmartStruxure system, you simply create the inputs and outputs and then provide programming to control the Requested value. Trends, alarms and graphics would monitor the value property. In a BACnet SmartStruxure system, the inputs and outputs are created under the IO Module in the same way; however an additional point is created in the Application folder under the BACnet Interface Device. On the property page of that point is a field designating the “Associated Value”. You should browse to the appropriate CIO point and select it. At this point all monitoring, display and control of the object should be accomplished with the BACnet point. (It is also possible to make the link between the associated value and the IO value by using the binding tool.) There is no other binding necessary to make the link between the CIO point and the BACnet “proxy” that is created in the application folder. For SmartStruxure versions prior to 1.4 please see the attached document for some implications and proper method of operation for using the IO associated value property: PSS Building Operation Attachment 14040rev2.pdf For SmartStruxure 1.4 and above see Associate AS BACnet Interface IO points with points on the IO bus in SmartStruxure 1.4 and above.

Issue Existing documentation for showing damper feedback and provide damper calibration is applicable only for Continuum and the same steps will not work in SmartStruxure. Product Line EcoStruxure Building Operation Environment SmartStruxure i2866-V b3866-V Cause Damper feedback and calibration for these controllers do not work the same in SmartStruxure as they do in Continuum. Resolution The correct damper feedback can be shown, but will require a script program to correctly calculate this and then write this back to an Analog_Value. Unfortunately, it is not possible to bind directly to the "LCD State" attribute to be able to toggle this (and the damper calibration feature) from within a Script Program. For now, toggle this attribute of the Damper Output manually from "enabled" to "disabled" and back. This will set the damper to drive closed fully, then open fully, then to about 75%. After this is calibrated properly the "Override Value" attribute in the Damper Output will update with likely a very large and strange-looking number. To convert this to something usable, multiply this value by 100 to give a percentage open value. See Zip file with XML code and screenshots of the configuration with notes. Either import supplied XML file into b3866-v or create below objects: Create DamperOutput as a multistate output. Assign to channel 1. Create DamperPos AnalogValue. Create Script Program Damper_Position and input code as shown in image. This will be a looping program. Bind DamperOverrideValue to the OverrideValue attribute of the Damper Output and DamperPosition to the DamperPos AnalogValue we created earlier. See image for details. After the points and program is created and the damper calibrated, you should see the DamperPos AnalogValue update with a live representation of the current Damper Position.

Issue Continuum Cyberstation running on Windows 7 machine.  Cyberstation crashes unexpectedly.  Cyberstation crashes when an alarm come is reported. Product Line Andover Continuum Environment Continuum CyberStation WebClient Outlook Cause Event notification alarm delivery configured to send email alarms when Outlook is not installed on the workstation. Resolution Either remove the email option from the event notification, or install Outlook and set it up for alarm emailing. If enhanced alarm delivery is selected (Database Initialization> Server(Stand alone)> See check box for enhanced alarm delivery Ensure that recipient Cyberstations do not have page, log, forward options selected. Only use email if it is being used. Example: Ensure that if an object is selected in an event notification action (i.e display graphic) that the point that is being alarmed on has that object (graphic) selected. Related article:  https://community.se.com/t5/tkb/workflowpage/tkb-id/knowledge-base_public/article-id/6986 

Issue Multiple defects were identified in VisiSat 2.1 Build 196, affecting functionality, export reliability, character encoding, and memory management. These issues impacted integration with StruxureWare Building Operation and the handling of MicroNet engineering files. Product Line Satchwell MicroNet Environment Satchwell VisiSat 2.1 build 196 Cause Legacy limitations in character handling and export formatting Improper object disposal during export routines Encoding mismatches for non-ASCII characters Incomplete validation logic for interface exports Lack of error handling for blank point lists Resolution Service Pack 1 (Build 200) Fixes Included: ARCnet Debug Tool Property editor now functions correctly in the ARCnet debug Excel spreadsheet. (Defect 1633) Export Enhancements Point names now support up to 32 characters; descriptions up to 50 characters. (Defect 1706) MicroNet Interface Handling MicroNet Interfaces are no longer exportable/importable via StruxureWare WorkStation. All engineering must be completed in VisiSat before import. (Defect 1765) Point List Stability Blank point lists can now be saved without triggering errors. (Defect 1784) Memory Leak Fix Exporting to StruxureWare no longer causes memory leaks. (Defect 1808) Installation Instructions: Ensure VisiSat 2.1 Build 196 is installed. Download and apply Service Pack 1. Note: Control Panel may still display build as 2.1.196 after installation. Service Pack 2 (Build 201) Fixes Included: Character Encoding Correction Non-ASCII characters in import files are now correctly converted. (Defect 31467) Alarm and Trend Point Import Points with alarms and trends are now properly included in import files. Installation Instructions: Ensure Service Pack 1 is already installed. Shut down VisiSat and VisiSat-Server. Run VisiSat 2.1.196 Service Pack 2.exe . Extract to the VisiSat installation root (or extract elsewhere and move the Satchwell folder to C:\ ). When prompted to replace existing files, select "Yes to All". Restart VisiSat. After installation, build number updates to 2.1.201, but may still appear as 2.1.196 in Control Panel. Download Service Pack 2.

Issue Some issues which this article covers are: What rules or recommendations should be used with Indirect and Global Points? Why might a global point not change? Attempting to alter a global AO/DO points' value/state, by "Point Control" without "Manual Mode" being used, and the change does not take place. (Referred to as Global Output Retentive Feedback.) What scan rates should be used for global / indirect points? Product Line TAC INET Environment I/NET Software Cause Often within a system, a point's status or value within one controller has to be shared or used in other controllers connected to the system. An example could be an outside air temperature sensor connected to a controller. The value of the outside air temperature in that controller can be transmitted across the I/NET network to be used in algorithms in the other controllers. The I/NET software and firmware provides the mechanism to transmit and receive point data system wide. The outside air temperature point in this example would be called a "global point." The receiving points within the other controllers that reference and thereby mimic the global point's temperature value are called "indirect points." Resolution Each controller is capable of a total of 128 global and indirect points. Global points are used to share information from one controller to another. If a point is not a global point, the state or value of that point is available only to other points in the same controller. If a point is specified as global, you may use it to control an indirect point in another controller. Any internal or external point may be designated as a global point. When a point is defined as global, a corresponding indirect point must be set up in the additional controller(s) to receive the global point's data. The global point must be designated with the appropriate globalisation level. There are four (4) different levels of globalisation, as shown below: Local: This point provides information only to this controller. A global setting of "Local" indicates that this point is not a global point. LAN: This point may provide information to an indirect point in any device connected to this controller LAN. Link: This point may provide information to an indirect point in any device connected to this controller's Host LAN. This setting WILL NOT send global data across links headed by NetPlus Routers. System: This point may provide information to an indirect point in any device connected to the I/NET system including ETHERNET. This setting WILL send global data across links headed by NetPlus Routers. Global points "broadcast" or send their state/value to corresponding indirect points. The frequency of the broadcast depends on the point type. All global point types broadcast under the following conditions: The controller has been restarted, either by a power restore, the controller's red reset button has been pushed or the database, DCU0000.sav file, has been "Restored." A global point has been changed from "Automatic" to "Manual" or from "Manual" to "Automatic." This does not apply to the Test Mode. A global point changing to or recovering from the "old data" state due to either a communications failure, or an analogue input point falling outside or re-entering its sensor limits (defined within the 'Resident Points' editor). Global analogue points (AI, AO, GI, GO) broadcast whenever their value changes through a range greater than the specified "Broadcast change counts" parameter (defined within the 'Resident Points' editor). Global discrete points (DI, DA, DO, DM, DC) broadcast whenever their state changes. Global pulsed input points (PI) broadcast whenever their "Scans between broadcasts" parameter is exceeded (defined within the 'Resident Points' editor). When requested to by the associated indirect point. Indirect points "receive" their state/value from their corresponding global points. Indirect points must reside in a different controller from the global point, and they act as receptors for the value or status information broadcast from the global point. When entering an indirect point, you must specify the name or address of the associated global point. The frequency of the update from the global points depends on the following. Their associated global point broadcasting its status or value. In addition, an indirect point can request an update, at the indirect points scan rate, from their associated global point. This happens when: The indirect point is first entered. When the indirect point's controller is restored or reset (power restore, station restore or the red reset button is pressed). Whenever the local control LAN reconfigures. Whenever an AO or DO indirect point is put into "Manual Mode" or back into "Automatic Mode." When the indirect point has not seen a status/value change from its associated global point within 2 times the indirect point's scan interval it request an update from its associated global point. It then reports the update on its third scan interval. If the indirect point is unable to be updated from its global point (i.e. no communications) then the indirect point will report its last valid updated value/state and will flag the value/state as "Old Data." Direction of Point Data's Flow INPUT POINTS (AI, GI, DI and DA): The data flow is from the global input point broadcasting to the associated indirect point only. The flow is "one way" only, that is to say, if the associated indirect point should alter the state or value is not broadcast to their corresponding global point. GLOBAL INPUT --------------> LAN -------------> INDIRECT INPUT OUTPUT POINTS (AO, GO and DO): All output points (both global and indirect) broadcast their state or value changes to the other associated point(s). The flow is "two way," that is to say, a change to either the global or the associated indirect point will change their opposing point's value accordingly. GLOBAL OUTPUT <--------------> LAN <----------------> INDIRECT OUTPUT Click Here to view some recommendations / rules for Global and Indirect Points as well to view this complete article as one document.

Issue What was the repeater used on MicroSmart communication trunks? Environment DMS MicroSmart (all revisions) Cause Information on a discontinued product line Resolution The typical repeater installed was Model # RPTR-DMS-WW.  There are other model numbers for trunks installed with fiber. Click here to view the Repeater Installation Instructions (F-25846).

Issue Where can I find information on EWS? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled SmartConnector Cause Documentation required Resolution Documents can be downloaded from The Exchange Download Center - EcoStruxure Web Services EcoStruxure Web Services Specification can be found at: SmartConnector Server

Issue While opening a Menta file whose file name has changed, the following error appears:   tam32 Cannot open file: C:\$Projects\MentaFile.MTA  (File path of the offending file) Product Line TAC Vista Environment Menta Cause The cause of this error is typically due to manually renaming an .MTA through Windows instead of using the Menta "Save As" function, which causes corruption.  Resolution Right-click on the .MTA Menta file and select "Open with..." Open the file with a text editor, such as Notepad Scroll to the right on the second line to find the name of the file Menta is expecting with an .AUT extension.  The text will have extra spaces between each letter.  Caution: Do not make changes to the file in NotePad or save the file. Example: N E W M E N T A F I L E . A U T   Rename the file in Windows using the file name found in the text editor, but with a .MTA extension. Example: NewMentaFile.MTA   To avoid having to perform this correction, always use the Menta "Save As" function to rename .MTA files. 

Issue Does the Automation Server support network authentication via Radius Server (IEEE 802.1X)? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause AS supports network authentication via Radius Server (IEEE 802.1X)? Resolution RADIUS and IEEE 802.1X are not the same thing, although they can be used together. Remote Authentication Dial In User Service (RADIUS) is a networking protocol that provides centralized Authentication, Authorization, and Accounting (AAA) management for computers to connect and use a network service. RADIUS is a client/server protocol that runs in the application layer, using UDP as transport.   The RADIUS server is usually a background process running on a UNIX or Microsoft Windows server. RADIUS serves three functions: to authenticate users or devices before granting them access to a network, to authorize those users or devices for certain network services and to account for usage of those services.  IEEE 802.1X is an IEEE Standard for port-based Network Access Control (PNAC). It is part of the IEEE 802.1 group of networking protocols. It provides an authentication mechanism to devices wishing to attach to a LAN or WLAN. It is a mechanism used in (mostly) switches and wireless access-points to allow or block devices to access the network (or granularly allow access to parts of it).   For example, if you have a network port in a meeting room, you can enable 802.1x on the switch port and configure it in such a way that when an employee connects they have access to the entire network, but if a guest connects (with a temporary password) they can only reach the Internet and if a passer-by is tempted to try his luck, they cannot access anything at all. Does IEEE 802.1X also use RADIUS as it's underlying authentication mechanism? Yes and no. IEEE 802.1x uses Extensible Authentication Protocol (EAP), the drawing below shows that for wired 802.1x: EAP over LAN (EAPoL) is used between the Supplicant (software on a computer) and the Authenticator (switch). EAP is then usually tunneled over Radius between the Authenticator and the Authentication Server, but it can also be done over Diameter (the successor to Radius). For wireless, it is similar in the sense that there is also no Radius between the supplicant and the authenticator, only between the authenticator and the Authentication Server (to tunnel the EAP). From EBO 2022 the AS-P and AS-B can be configured as supplicants on a network protected by IEEE 802.1X security. See the IEEE 802.1X Security Webhelp topic for further details.   Note: MPx/RPx do not support 802.1x network authentication, see the SpaceLogic controllers MPx/RPx do not support 802.1x network authentication Knowledge Base article  for further details.    

Issue What is the A/D (Analog-to-Digital) resolution of the inputs and outputs on the Xenta product line? Product Line TAC Vista Environment Xenta 281/282/283 Xenta 301/302 Xenta 4xx I/O Modules Cause Project specifications often require precise information about input and output resolution to ensure compatibility and performance expectations are met. Resolution The input and output resolutions for the Xenta product line are as follows: Controller Thermistor Inputs Universal Inputs Analog Outputs Xenta 281 12-bit — 12-bit Xenta 282 12-bit — 12-bit Xenta 283 10-bit — 12-bit Xenta 301 12-bit — 12-bit Xenta 302 12-bit — 12-bit Xenta 421A / 422A — 12-bit — Xenta 451 / 452 12-bit 12-bit — Xenta 451A / 452A — 12-bit 8-bit Xenta 471 — 12-bit — Xenta 491 / 492 — — 12-bit