Notifications

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

Invite a Co-worker

Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.

Send Invite Cancel

Related Forums

Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague

Label: "tac vista"

View in: "Building Automation Knowledge Base" | Community

2045 Posts | First Used: 2018-09-06

Building Automation Knowledge Base

Issue How to launch the Vista System Plug-In in Visio 2010. In earlier versions, it was located under the toolbar menu LonMaker > System Plug-Ins, but that menu item no longer exists. Product Line TAC Vista Environment LonMaker Turbo 3.2 Visio 2010 Add-Ins Cause Usual drop-down tool bar menu items do not exist in Visio 2010 as they did in earlier versions. Resolution System Plug-Ins can be found under the Add-Ins tab Add-Ins LonMaker Network Plugins. If the Add-Ins are missing, please see Visio will open but LonMaker menu is missing from the toolbar, the features are unavailable, or Error: "unable to launch visio with file lonworks.vst".

Issue TAC Vista will not dial out to an Xenta 901 network as expected e.g. when opening a graphic or selecting a remote controller in the folder view. Product Line TAC Vista Environment TAC Vista 4 TAC Vista 5 Cause The COM port and /or the Xenta 901 network are not correctly configured. Resolution Check that Vista is in Operating mode. See Opening a graphic will not cause TAC Vista to dial out to a Xenta 901 Network for details. Check that the COM port your modem is connected to is correctly configured in Vista. The port object in Vista will be of the type 'Communication Port - Modem'. Hopefully, it will have a meaningful name relating to the connected modem. In the properties for the port check that the Device Address refers to the correct physical COM port. The Device Address is of the form "server_name-COM_xx", where COM_01 will be the first port defined in Vista. If you have multiple COM ports or a USB/RS232 converter, this may not be the address you want. You can manually change this to the required port: for example COM_03. You can see which physical ports are available in Device Manager. In the properties for the port check that Traffic direction is set for outgoing traffic. Normally you will set this to "Incoming and outgoing traffic", but you might want "Only outgoing traffic" if you don't want to receive alarms or trend logs via this modem. Check that the port has been assigned to the Xenta 901 Network. In the properties for the Xenta 901 Network - Modem select the "Ports" tab. This displays a table listing all the communication ports this network will use. If the table is empty Vista will attempt to dial out on all ports not set as "Only incoming traffic". If you have multiple ports this is probably not what you want, so use the Add and Delete buttons to select only the ports that you want this network to use. In the properties for the Xenta 901 Network - Modem select the "Outgoing Traffic" tab. Check that the phone number shown is correct for the remote site. If Vista is dialing out through a PABX, prefix the phone number with "9,". The comma after the nine tells the modem to wait 1-5 seconds (adjustable via your modems command set) so that a dialing tone can be obtained from the PABX. If you are using the recommended US Robotics modem, the many default parameters for the comm port and the Xenta 901 Network - Modem should let Vista dial out without further modification.

Issue Cannot connect network variable point from a third party LON device to a graphic within an XBuilder project. XBuilder will not allow the drag and drop of LON network variable between the network pain and the system pain when you attempt to create connections. Product Line EcoStruxure Building Operation, TAC Vista Environment XBuilder Vista Lon Device .xif Cause XBuilder is very particular about the format of an .xif file and it will not allow certain characters in the function block name. Vista and LonMaker have far less limitations and these programs are able to parse these characters without causing problems. This explains why your values may show up in the LNS management tool and Vista Workstation. However, once you import the network into XBuilder you are unable to connect the SNVTs to your graphic. Resolution Replace the incorrect characters in the function block line of the .xif and reload the new .xif into your LonWorks Network. Please see LON device can communicate in Vista, but fails in a Xenta Server / XBuilder for more information about incorrect characters in an xif file. INCORRECT FUNCTION BLOCK EXAMPLE: File: MP580.XIF generated by NODEUTIL Revision 1.46, XIF Version 4.0 Copyright (c) 1997 by Echelon Corporation All Rights Reserved. Run on Fri Oct 31 16:30:28 2003 80:00:2A:52:00:03:04:03 2 15 1 618 0 8 8 4 4 11 11 0 0 0 0 3 0 16 0 0 1 65536 618 0 0 0 0 0 0 0 0 0 0 0 0 10000000 1 7 1 0 4 4 4 15 200 0 78125 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 5 8 5 12 14 15 * "&3.4@0,20000-MP580,8500-SCC,8610-DAC The problem is the three dashes between the object numbers and the object names in the self doc string. This is "allowed" in Vista and LonMaker in some sense. For example, Vista "replaces this "-" to a "/" but then XBuilder can't handle this situation properly. CORRECTED EXAMPLE: File: MP580.XIF generated by NODEUTIL Revision 1.46, XIF Version 4.0 Copyright (c) 1997 by Echelon Corporation All Rights Reserved. Run on Fri Oct 31 16:30:28 2003 80:00:2A:52:00:03:04:03 2 15 1 618 0 8 8 4 4 11 11 0 0 0 0 3 0 16 0 0 1 65536 618 0 0 0 0 0 0 0 0 0 0 0 0 10000000 1 7 1 0 4 4 4 15 200 0 78125 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 5 8 5 12 14 15 * "&3.4@0,20000MP580,8500SCC,8610DAC;Tracer MP580 The dashes 3 x (-)s have been removed from the function block name

Issue Get "No License available" error message when logging in to Vista webstation. The following errors have occurred. Please correct these errors and / or contact the system administrator. Product Line TAC Vista Environment Windows 2008 server 64-bit Vista 5.1.5 Vista 5.1.9 Evaluation License downloaded from extranet Cause Incorrectly formatted license setup Resolution Check the License Setup. Open License Setup and check the format used. The picture below shows that the license server is on the local PC (using the computer name), but this will not work. Instead, type the file path to the evaluation license (see below). Note: From Vista 5.1.8 and later the path should instead be C:\Program Files (x86)\Schneider Electric\License Server\taclic\licenses If this hasn't resolved the issue try the steps outlined in TAC Vista Webstation licenses are not released after closing the Webstation browser

Issue When opening a TGML graphic page you get an error and Vista Shuts Down. Product Line TAC Vista Environment Windows 7 Vista 5.1.X Cause The monitor is using the DIVI Digital Video Input. Resolution If Vista Crashes when you attempt to open a TGML graphic then change to the analog VGA output on your video card. Here is A DVI lead Here is a VGA lead Hardware acceleration on you video card can also cause a similar issue. Please see Vista Workstation is crashing/shutting down when graphics begin to load for more information on hardware acceleration issues.

Issue Upgrading the operating system (OS) to Windows 7 on an old PC. Product Line Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC INET, TAC Vista Environment Older PC's Windows 7 Cause Some older PC's are not suitable for upgrading to Windows 7. Resolution When considering upgrading to Windows 7 with an older PC, it must be first checked for suitability. Run the Windows 7 Upgrade Advisor before upgrading. To review the Schneider Electric Software and Firmware compatibility matrix please see Software and Firmware compatibility matrix for older versions of the traditional product lines.

Issue Check the current size of the SQL database associated with a Vista database to ensure that it hasn't become full. Product Line TAC Vista Environment SQL Cause The SQL database that installs automatically with Vista has limitations on the amount of data it can hold. Most often, this is plenty of space for many years of trending without issue. But if a site is very old or has many trend logs defined, it can out grow the SQL database. Limits are: Vista IV - Vista 5.0.0 MSDE: 2 GB Vista 5.0.1 - 5.1.6 SQL 2005 Express: 4 GB Vista 5.1.7 and newer SQL 2008 Express: 10 GB Resolution This procedure checks the log size from the Vista Workstation: In Vista Workstation, click on the Vista Server in the folder pane Right click on $Backup_LDB and select Properties Scroll to the bottom and make note of the Database Size property (shown in grey). This is the size of the database in MB. This procedure checks the file size on the hard drive. The assumption has been made that this is not a custom install, but the default SQL installed with Vista Server: Open Windows Explorer Navigate to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data Locate files: taclogdata.mdf taclogdata_log.ldf Note: If there are multiple instances of SQL installed on the PC, there may be MSSQL.1, MSSQL.2, MSSQL.3, etc. Find the SQL instance that contains the file names listed above. Highlight both files and look at the bottom of the window on the status bar. The combined size of these two files is shown. This can be used to determine is the SQL database is full and requires a purge. To purge a Vista IV SQL database, see How to create a new database or purge a full SQL (i.e. it has hit the limit of 2G) in Vista IV. To purge a Vista 5 SQL database, see Vista 5 full SQL database issue. If purging is not an option, then the SQL will need to be upgraded to a full version of SQL (not express). To see the different options, see Vista Database Sizing and SQL Server Selection.

Issue In the alarm window of TAC Workstation, there is a system alarm that is Physical device no defined/configured. After you acknowledge it, it will occur again. Product Line TAC Vista Environment TAC Vista workstation Xenta 280/300/401 Xenta server LOYTEC NIC-USB Cause The controller address cannot be verified correctly in TAC Workstation. For example, a TAC Xenta Group name or number is in conflict with another TAC Xenta Group’s. Resolution If multiple TAC Xenta Groups or Lonworks networks are created, you must verify the Lonworks network’s name or TAC Xenta Group name and number is unique. The TAC Xenta Group default number is 254. The different number must be given to the different TAC Xenta Group even though the TAC Xenta Groups are beneath the different Lonworks network. You can also reference to the articles System alarm message, Physical device not defined/configured and Physical device not defined/configured about this issue.

Issue When using the "Commission and Download" command in Vista Workstation the controller being downloaded is failing with a "Completion Event Failure" and has multiple "Waiting for unit to restart" error messages. Product Line TAC Vista Environment Vista Server/Workstation Classic Network Cause The controller being downloaded and presenting with this error message typically has been functioning and communicating on the network and an application update is being downloaded. The unit is busy responding to other communication (TAC network variables, Xenta group communication, etc) and can not devote full attention to the application download. By setting the neuron status to unconfigured, the controller can focus only on the application download. Resolution Right click on the Xenta programmable controller and select Advanced Operation > Neuron Unconfigured. Right click on the Xenta programmable controller and select Commission and Download. It is unnecessary to set the Neuron status back to Configured because this is part of the Commission and Download process. Similar steps are available for a LNS network and are discussed in "Completion event failure" and/or "Waiting for device to restart" errors when downloading a previously commissioned controller.

Issue The demo license used to access the OPC server configuration must be removed from the license Files folder in the new Flexnet License Server for the service to start. Upgrade to a Vista 5.1.8 will not allow access to the OPC Server Configuration. Product Line TAC Vista Environment Vista 5.1.8 using 3rd Party OPC where Vista is a client Cause Vista.OPCTool = Allows accessing the OPC Server for configuration Vista.Server.OPCClient license= Allows a connection to get the configured OPC points into Vista. Systems engineered to use 3rd Party OPC Server may only contain a Client license for connectivity, using the Demo for the initial configuration and servicing of the OPC Server. In Vista 5.1.8, the Flexnet License Software will not allow a Demo license to be present in conjunction with a Site License. This is corrected in Vista 5.1.9. More information can be found in License troubleshooting in Vista 5.1.8 or greater. Resolution Purchase the Vista.OPCTool to add to the existing Site License file. Best practice is to have a separate folder for your demo licenses, and reference the physical path to that folder. See below: WSDKHE9781;C:\Program Files (x86)\Schneider Electric\License Files Demo

Issue When creating a Modbus device template in XBuilder Device Editor which Modbus register data type should be used? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 701, 711, 721, 731, 913 XBuilder Modbus Register Bitmask Cause Lack of consistency between Modbus slave manufacturers there is a large number of data formats that can be selected. Each register format interprets the value differently based on byte order or purpose of the specific bits. Resolution Consult Modbus slave product documentation Use trial and error to find the correct register format. Perform communication logging to capture the raw data and compare with a known value to determine the format. As a tool to assist with these steps please consult the Definition of Modbus Registers.

Issue Which signal types can be connected to a UI on a Xenta I/O Modules? Product Line TAC Vista Environment Xenta 451A/452A, 421A/422A Cause UI is short for universal input, which means that these inputs are compatible with many different input types. Resolution Supported input signal types are: Thermistor: 1.8 KΩ at 25 °C or 10KΩ at 25 °C; Voltage: 0 to 10VDC; Current: 0 to 20mA; Digital Input. Refer to the following link about 1.8KΩ and 10KΩ thermistor compatibility: 1.8k Thermistor compatibility with Xenta controllers 10k Thermistor compatibility with Xenta controllers

Issue Are 8 byte unsigned integers (UI8) supported in Vista OPC client? Product Line TAC Vista Environment TAC Vista 5.1.X Vista OPC tool Cause Not all OPC data types (canonical data types) are supported by OPC server. UI8 variables show a question in OPC tool. If the Canonical Type column shows a question mark for the variable (or tag) then this means that Vista has been unable to identify or does not support the data type. Resolution If possible divide the OPC tag/variable into 2 x 4 byte registers. It could also be worth checking what the expected maximum value is for that register and seeing if that value will fit in a UI4 (unsigned integer 4 byte). An alternative solution, although the functionality must be checked by the engineer is to create the variable object manually and use the canonical type "string". To do this follow the steps below: Note the name of the OPC variable to be added to Vista in the OPC tool browser window. Under the OPC server object in Vista create a 'Value - String' and give it the same name as the OPC variable. Hold down shift and ctrl and right-click the string value - select properties. Locate the Property RA and fill in the name of the folder, variable name and the data type in the following format: folder name.variable name|data type Example of OPC naming convention including data type, in TAC Vista. Click on OK and the variable should start updating after refreshing the folder. More information on OPC data types can be found in What does the "| n" mean when viewing the properties of an OPC variable in Vista workstation?.

Issue Trying to download a Xenta programmable controller through System Plug-In fails. Errors shown are default LNS type errors shown as: (Subsystem: NS, #59). Click okay and the next error appears (Subsystem: NS, #64). Click okay and the next error appears (Subsystem: NS, #51). Product Line TAC Vista Environment TAC System Plug-In Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause The steps defined in this article only relate to the NS #59 error when it is received on an attempt to download a controller through the TAC Vista System Plug-In. It does not cover when this error is shown as a result of a commission attempt in an LNS environment. For the commissioning error, please see The new program interface does not match the previously defined program interface. (Subsystem: NS, #59). The cause of this particular set of errors is unknown at this time, but has been witnessed a number of times. Various troubleshooting techniques have resolved the issue. The best course of action is to try each of these methods in the order of least to most disruptive. As new techniques and procedures are discovered, they will be documented here. Resolution Remove the controller from the Vista database In the Vista System Plug-In, locate the offending controller in the right-hand TAC Pane Right click and delete the controller Update the Vista database Locate the controller in the left-hand LNS Pane Drag and drop it back into the TAC Pane Update the Vista database Attempt the download again. Remove the controller from the LNS database In LonMaker or NL220, locate the offending controller Right click and delete the controller In the Vista System Plug-In, locate the controller (which now has a red X over it) Right click and delete the controller Update the Vista database Add the controller back to the LNS database In the Vista System Plug-In, locate the controller in the left-hand LNS Pane Drag and drop it back into the TAC Pane Update the Vista database Attempt the download again Replace the controller Physically replace the controller This should be performed in conjunction with the steps listed above for removing the controller from the LNS database.

Issue When a Xenta 121-FC changes from heating to cooling the fan output turns off for 5-10 seconds. Product Line TAC Vista Environment 121-FC controller Cause The firmware version has been enhanced and this was a enhancement that has been implemented. Resolution Upgrade your 121-FC to version 1.25 (or above). Download the upgrade files from The Exchange Download Center: Xenta 121-FC Firmware Files (NXE/APB/XIF) See Downloading new NXE or APB files using Lonmaker for instructions on how to download the application to the controller using LonMaker.

Issue Periodically a computer with Vista 4.5 will start generating the message "Failed to Read Event From Event Log Database" when opening Vista Workstation. Error: "Event Receiver Failed - Could not retrieve any events from the event log". Product Line TAC Vista Environment Vista IV Vista Workstation Windows Server 2003 Windows XP Cause Vista IV uses 2 users, TACA and TACM (appended with an underscore followed by the PC name e.g. "TACA_PCname"), to manage its SQL connection. Certain Automatic IT security procedures will either remove these users or revoke their administrator privileges. Resolution Option 1 Reinstall Vista. This will be required if the users TACA and TACM no longer exist. Option 2 Modify User rights for accounts TACA and TACM. This is only possible if the local user accounts have not been deleted. To do this you will need to follow the following steps: Log in as an Administrator Go to the control panel and look for the program User Accounts (also called User Profiles) Find the User TACM Select Properties In the Group Membership tab, add the user TACM to the administrator group Option 3 Upgrade to Vista 5 For either Option 1 or Option 2, you will need to contact the site IT department to ensure that this issue will not come up again. Event Receiver Failed - Could not retrieve any events from the event log may also be of interest.

Issue Get error "Local TAC Vista server not started . Cannot reserve graphic object" when trying to edit a OGC graphic from TAC Vista Workstation. Can not start OGC editor from within TAC Vista Workstation Product Line TAC Vista Environment Windows Server 2008 Windows Server 2008R2 Windows 7 TAC Vista Server running as a Service Cause When using Windows 2008/7 the following legacy tools can not be used when TAC Vista Server runs as a service: TA Draw, TA Main, Database Generator, LIST.EXE, IPCL Editor, Test Client and UPGRFILE.EXE. For more restrictions for Windows 2008 and Windows 2007 see the release TPA-VSTA-11-0002.01 for TAC Vista 5.1.5. Resolution Run TAC Vista Server as an application. Refer to Registering/Unregistering TAC Vista Server as a Windows service for registering/unregistering Vista Server as a service.

Issue Vista reports fail to save to the server when they are being edited from a remote workstation. Product Line TAC Vista Environment Vista Microsoft Excel Cause When setting up remote workstations on a LAN or WAN, there are certain steps that must be taken. If the proper DCOM settings are not set up on every remote workstation as well as the computer that runs Vista server, there can be authority issues. Vista reports can be created but will not allow values or trends to be saved into the report. In some cases this has generated the error "The RPC Server is unavailable" as seen in Error: The RPC server is unavailable. Resolution On ALL remote workstations and the main server: Run DCOM Config 1.0.2.2.exe found in Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET. Either select Server-Workstation or Server-Workstation-Webstation. On the main server that will be used to run Vista Workstation: Run > dcomcnfg Expand Component Services Open Computers Right-click My Computer and choose properties Go to COM Security pane For Access Permissions and Launch and Activation Permissions choose to edit both Edit Limits... and Edit Default... Add users Anonymous and Everyone with Remote Access Go back to Component Services and open My Computer Open DCOM Config Browse for OPCEnum right-click and choose properties Go to Security pane Change the three options to Launch and Activation Permissions -Use Default Access Permissions -Use Default Configuration Permissions -Customize Choose Edit > add Anonymous and Everyone with Remote Access Go back to DCOM Config and browse for TACOS right-click and choose properties Go to Security pane Change the three options to Launch and Activation Permissions -User Default Access Permissions -User Default Configuration Permissions -Customize Choose Edit > add Anonymous and Everyone with Remote Access

Issue The TGML page is dynamic but looks static. Product Line EcoStruxure Building Operation, TAC Vista Environment Vista StruxureWare Interface Cause In the Release Note, page 30 says: It is possible to navigate to a TAC Vista Webstation TGML Graphic through a link in a SmartStruxure TGML Graphic. To achieve this connection a link object is created in the SmartStruxure TGML Graphic which is linked to a SmartStruxure hyperlink object that holds the TAC Vista Webstation TGML Graphic page address. Example of a hyperlink objects address in SmartStruxure that is linked to a TGML Graphic in TAC Vista: HTTP://ip_address/webstation/LoginPage.aspx?page=TgmlGraphicsPage.aspx?objectId=3074949137 Note: This will always require a login by a valid TAC Vista user, even if the TAC Vista Webstation auto login feature has been activated. Resolution The example link above is referring to a static page. For example, if the TGML page is dynamic, you will see the following in the copied link (see bold). HTTP://ip_address/webstation/LoginPage.aspx?page=TgmldynamicGraphicsPage.aspx?objectId=3074949137 You can also read the following in the release note: In order to determine the TAC Vista Webstation URL for a TAC Vista Webstation TGML Graphic the following TAC Vista Web Setting configuration must be in place: Optimized TGML Loading is deactivated Folders pane is set to Standard HTML With these settings it is possible to right-click a TGML object in the folders pane and select "Copy Shortcut." This will copy the TAC Vista Webstation URL to the clipboard and it can then be pasted into a SmartStruxure hyperlink object address field. After the shortcut has been pasted, it will have to be modified in order for the TAC Vista TGML Graphic to be displayed properly in SmartStruxure. The modification is marked with bold in the example below: Copied: HTTP://ip_address/webstation/TgmlGraphicsPage.aspx?objectId=3074949137 Modified: HTTP://ip_address/webstation/TgmlGraphicsPage.aspx?objectId=3074949137 If the link you copied was a dynamic TGML the link will look like: HTTP://ip_address/webstation/TgmldynamicGraphicsPage.aspx?objectId=3074949137 and should be modified as this HTTP://ip_address/webstation/LoginPage.aspx?page=TgmldynamicGraphicsPage.aspx?objectId=3074949137 Also reference the TAC Vista Webstation Graphics Links and SmartStruxure Integration tool on the Community.

Issue When Remote Alarm Manager attempts to initialise the GSM modem it fails during reset command. Modem will reset correctly if the same commands are sent from a terminal emulation program. Product Line Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Vista RAM Sigma Ram MicroNet RAM BAS RAM GSM Modem Cause The result codes from the modem are not returned in the format expected by Remote Alarm Manager Resolution The Mobile Equipment Errors setting (AT+CMEE) sets the format that error responses from the modem are returned in, the possible formats are: 0 disable result code and use ERROR instead 1 enable result code and use numeric values 2 enable result code and use verbose values The GSM driver in Remote Alarm Manager expects to see these results in numeric format. To Check and set the format do the following: Using a Terminal Emulation Program such as Hyperterminal connect to the modem Enter the command AT+CMEE? to show the current setting Enter AT+CMEE=1 Enter AT&W to store the current settings to non volatile memory. Disconnect Hyperterminal and test with Remote Alarm Manager.

To The Top!

Building Automation Knowledge Base

Related Forums

Intelligent Devices Forum

Launch Vista System Plug-In in LonMaker/Visio 2010

TAC Vista will not dial out to a Xenta 901 network

XBuilder will not allow a connection between a third party LON device and a graphic

Get "No License available" error message when logging in to Vista webstation

Vista crashes when attempting to open a TGML Graphic

Upgrading an older PC to Windows 7

Check the size of the SQL database for Vista trend logs and events

How to solve a system alarm that is Physical device not defined/configured?

Continuous "Waiting for unit to restart" when downloading application in Vista Classic network

Using Demo License to Configure 3rd party OPC Server in Vista 5.1.8

XBuilder Device Editor Modbus register formats

Which signal types can be connected to a UI on a Xenta I/O Modules?

Are 8 byte unsigned integers (UI8) supported in Vista OPC client?

NS Errors #59, #64, #51 in a row on download attempt through System Plug-In

Fan output turns off when set to continuous operation on a Xenta 121-FC

Failed to Read Event From Event Log Database - Vista IV

Get error "Local TAC Vista server not started . Cannot reserve graphic object" when trying to edit an OGC graphic from TAC Workstation

Vista reports can not be edited from a remote workstation

Navigating to a TAC Vista TGML Graphic from a SmartStruxure TGML Graphic through TAC Vista Webstation

GSM modem error in Remote Alarm Manager (RAM)

Building Automation Knowledge Base

Related Forums

This is a heading