Building Automation Knowledge Base

Issue What are the IO wiring requirements for the IO Modules? Product Line EcoStruxure Building Operation Environment Analogue, Digital, Input, Output Cables UI-16, DI-16, AO-8-x, AO-8-V-x UI-8, DO b3 Inputs Cause The existing documentation does not specify the exact cable types to be used. Resolution Different types of sensors can be used that come from different legacy systems, so cable types specified for the legacy systems will be appropriate for the same sensor type being connected to an Automation Server I/O module. If you are using Xenta sensors with the 1.8K Ohm thermistors you should use the wiring rules as per the Xenta documentation. Of if you use Continuum 10K Ohm sensors, use the Continuum IO wiring rules etc. Some suitable cables for most Analogue and Digital input, also analogue output applications are: 18 AWG (16 x 30) 0.823 mm2 - single pair screened e.g. Belden 8760 22 AWG (7 x 30) 0.325mm2 - single pair screened e.g. Belden 8761 The maximum distances that these cable can be run are dependent on the input requirements, for Temperature inputs this will depend on the temperature range and accuracy required. For examples of of these cable distances see links below: Continuum 10K Ohm sensors (also applicable for b3 controller inputs). Xenta 1.8K Ohm sensors For digital outputs cable should be used with appropriate size (current rating) to the loads being switched. It is recommended to use screened cables and also ensure correct connections for analogue inputs as detailed in How to wire an Analog input to an IO Module.

Issue Using BACnet IP to add a SmartStruxure Lite MPM to a StruxureWare Building Operation Enterprise Server or Automation Server Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment StruxureWare Workstation Cause SmartStruxure Lite systems may desire an Enterprise Level Solution to bring multiple sites into one system. Resolution Configure the SmartStruxure Lite MPM for BACnet IP as shown in MPM BACnet Integration. Ensure that the BACnet Network ID is Unique to the system and does not match the Network ID in use by the Enterprise Server Save the BACnet Configuration Be sure to Right Click on the Root Object of the MPM and save the database. Open StruxureWare for Building Operation Workstation Right Click on the Server Object and add a BACnet Interface Ensure that the BACnet interface has a unique BACnet Network ID which does not match the Network ID used by the MPM Expand the BACnet Interface Click on the Server Object and select the Device Discovery Tab Select BACnet Devices NOTE: There have been instances of Skype causing interference with this process. Please completely close Skype if you are using it and unable to discover any devices. ALSO NOTE: There may be 2 instances of the MPM shown. If so, use the MPM that is part of the Enterprise Server BACnet Network Drag the MPM to the BACnet Interface/IP Network object in the Enterprise Server System Tree Right Click on the Device and Upload it If any devices are connected to the MPM such as a Zigbee Wireless State or Enocean switch, these will be discovered in the BACnet Network configured in the MPM Add these devices to the Enterprise Server by dragging and dropping them to the BACnet Interface/IP Network object Right Click and upload all devices.

Issue Registering/Unregistering TAC Vista Server as a Windows service will allow the server to start automatically and run in the background of the PC (it won't show up on the Windows taskbar). This is not the same as having it run on Startup (for information on that, please see Configuring Vista Server to run on Startup). Product Line TAC Vista Environment Vista Server Microsoft Windows -- All versions Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Reference Chapter 16.3 of the TAC Vista Technical Manual "Running TAC Vista Server as a Service in Microsoft Windows XP" for more information. When you log out of Microsoft Windows or restart the computer, all running processes, for example, Vista Server, are shut down. These processes are not resumed at log on or at restart. You have to start Vista Server manually again. To get Vista Server to remain running at log off and automatically start up when the computer restarts, you can run Vista Server as a service. Running a program as a service means that it runs in the background, but it is not visible on the Windows task bar. Before you start Vista Server as a service, you must first install and configure your Vista Servers and your network and have everything running satisfactorily. It is not advisable to start Vista Server as a service until you have completed all the settings (including security and authority) and the TAC Vista system is running well. Resolution Register Vista Server to run as a Windows service Go to Start > Run Register the service by typing: Tacos.exe /service When you register TAC Vista Server as a Windows service, it will default to run under the "Local system" account.  This is not supported by TAC Vista Server. Right-click on My Computer and select Manage. Browse to Computer Management (local) > Services and Applications > Services Find TACOS, right-click and select Properties On the Log On tab, specify "This account:" with admin authority.  It is ideal to use a domain account with local administration authority if your system is a member of a domain. At this point, if you would like to start the service, highlight TACOS in the Services window and select Start the service. If you choose to run Vista Server as a service in a multi-computer network, we recommended that you run every Vista Server as a service. Change from running as a service to running as interactive Go to Start > Run Unregister the service by typing: Tacos.exe /unregserver You must then register the server back to interactive by typing: Tacos.exe /regserver Helpful Utility This utility will read in the current run mode of the Vista Server and allow you to switch between running as a service and an application. It also lets you set the user to run the service under. Click the image to the right to go to a Community post containing the utility .exe file. Accessing Vista Server Menus and Dialog Boxes Once the service has started, it is not possible to use the Vista Server menus and dialog boxes. To be able to use these, you have to unregister the service and start Vista Server in the normal way. LonTalk Adapter from Loytec When TAC Vista is running as a service and you are using a LonTalk adapter from Loytec, you must ensure that the program LConfig is also running as a service. You do this when you configure the network interface card. TAC Vista Tools and Microsoft Windows Vista Some of the tools installed in the installation folder of TAC Vista cannot run if TAC Vista is running as a service in Windows Vista. These are TAMIAN, CIPCL, SYSDOC, TADRAW, and DBGEN. Related Articles: Unable to save periodic report to network drive when Vista is running as a service Regional settings might differ when TAC Vista server runs as a service Dependencies for Vista Server running as a service Upgrading Vista while running Server as a service

Issue Netcontroller will not come online in Continuum although the unit can be pinged. Product Line Andover Continuum Environment Continuum 2nd generation controllers (NC2 (CX9680), ACX57, CX9702, bCX4040, bCX9640) 1st generation addendum Cause Even though a unit can be pinged, that does not mean the unit will come online within Continuum, as the "ping" is a very low level communication Resolution Check all settings are correct (IP address, ACCNetID, Subnet Mask, Default Router(Gateway Address)) Check the correct network ports are open, see Router required open port numbers to run a Continuum system Check the site fits within the compatibility matrix, see Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation Check there is only a single Network Card enabled on the CyberStation  For a second generation NetController (NC2, ACX57, CX9702, bCX) Check the web page can be accessed, if it can then double check the network settings. Connect a temporary single user Continuum laptop to the controller directly, manually reset the IP address and bring the controller online (using 169.254.1 Subnet). If this operates correctly then controller fault is eliminated. If the controller is not faulty then the network and/or the Continuum installations will need to be checked. Addendum for first generation controllers: Attach to the controller via hyperterminal to determine it's perspective and to verify the IP address, ACCNetID, Subnet Mask, Default Router. You can also verify if the netcontroller lists the Workstation as a controller indicating it can see the workstation. If not, perform a teach from the Workstation.

Issue Does the entire SBO system need to be upgraded to 1.5.0.171xx, 1.6.2.12xxx or 1.7.2.111xx before upgrading to 1.9.1 if the network includes LON devices? Can SBO be upgraded directly to 1.9.1 from 1.5.X, 1.6.X or 1.7.X? Product Line EcoStruxure Building Operation Environment SBO Workstation 1.5.0/1.6.1/1.7.1 SBO ES 1.5.0/1.6.1/1.7.1 SBO AS 1.5.0/1.6.1/1.7.1 SBO AS-P 1.7.1 Cause In systems that have SBO servers that already are hosting LON devices based on LonWorks imported device templates (.XIF) or resource kits (.DRF), the servers need to be prepared before an upgrade from versions 1.5/1.6/1.7 to version 1.9.1. Even servers where device templates (.XIF) or resource kits (.DRF) are just imported, and no devices or network variables are created yet, the servers have to be prepared before the upgrade. Resolution Please see section 9.2.3 of SBO 1.9.1 Release Notes. Although it says "Steps to upgrade a 1.6.2/1.7.2 multi-server system" you don't have to upgrade the AS or ES etc, even if they run 1.6.1/1.7.1, it's only SBO Workstation that need to be hotfixed. Links to the different Workstation hotfixes can be found Server with LonWorks devices - TPA-SBO-17-0002.00 - Links to hot fixes. If there are no LON devices in the system, you may upgrade directly to 1.9.1 from 1.5.X/1.6.X/1.7.X

Issue When trying to open a report, you get an error message like below: Msg=DDL creation failed ex=Error creating DropDownddlTopCount The request failed with HTTP status 503: Service Unavailable Ex=ButtonRunReport The request failed with HTTP status 503: Service Unavailable   Product Line EcoStruxure Building Operation Environment Reports server Cause Cause 1: The Report Server Service is not started To check if this is the cause, open the report manager. If you get the error below, continue to resolution 1.   Cause 2: The Report Server Service takes too long to generate the report and thus times out The root cause should also be investigated. It can be a slow network connection, fragmented SQL database, antivirus software or memory limitation that is slowing the request to compile a report down. Resolution Resolution 1 Open "Reporting Services Configuration Manager" Start the server   Resolution 2 Increase the timeout for the report service Open Report Manager Click "Site Settings" Change the Report Timeout. Default is 1800 which is 30 seconds.   Check that the memory usage for the SQL server is not limited (Microsoft's How to: Set a Fixed Amount of Memory (SQL Server Management Studio)) Open SQL Management Studio Open the properties for the SQL Server Click "Memory" and check that the value is default (2147483647)   Reindex and defragment the SQL database e.g. using SBO Reports Agent Config.

Issue Perform a complete 2.43 I/NET install on a clean workstation with integration with StruxureWare Building Operation 1.3.x or higher. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET 2.43 StruxureWare Building Operation 1.3 Cause Before starting the upgrade, please ensure the following: I/NET system installed is performing well Communications – reliable Alarms - Routing masks configured Application sequences - tuned Points - enabled and calibrated Devices - online Database - backed up If not, then these issues should be resolved before proceeding. SmartStruxure Solution will add functionality, but will not resolve existing performance issues. Verify architecture: All controllers, workstations, & the I/NET database can remain including: (for a complete list, see I/Net Controllers which are supported with StruxureWare Building Operation) All LAN Controllers All Sub-LAN Controllers HVAC and Security applications Replace all TAPS with dial-up connections with LAN connections: Xenta 527 Xenta 527-web NetPlusRouter 2000 (discontinued but supported) Verify I/NET system size is supported by the version of StruxureWare Building Operation to be installed Upgrade TAC I/NET software and firmware: I/NET Seven v2.43+ on a workstation v2.42 compatible controller firmware versions Note: All I/NET controllers will require this update For more information on version, compatibility see Compatible versions of I/NET and StruxureWare Building Operation software. Resolution Click here for a video summary of the integration process after all installations have been completed. Perform a complete I/NET install of build 23xx on a virgin machine Install I/NET build 23xx from CD Run "setup.exe" Enter the I/NET Subkey information Verify SQL database gets installed Run Dbcreate NOTE: If running I/NET Seven on 64-Bit Operation system, the path to the INET Seven folder is: C:\Program Files(x86)\INET Seven\ Make I/O Server runs as a Service Refer to the article Running INET Seven as a service on Windows Set I/O server to "Maintain" Set "Host" Mask" for your specified controllers --------->recommend reboot to ensure Inet7Iosrv is running as a service at this time<------- Ensure you have a current License file CD or provided by Order Entry Verify that you see the "StruxureWare_License_File.asr" (current name of file changes with each release of license file) Save the file to a folder on the workstation in License Tool Folder Perform an install of StruxureWare Building Operation License  Select build of interest ex 1.3.0.xx Locate and click the Licensing Tool folder Click on the StruxureWare.License.Administrator-1.3.0.xx.exe After the loading process completes, click “next” on the Welcome to the StruxureWare screen Click the “I agree” button at the License Agreement screen Uncheck the License Server component and Click the “Next” button at the Choose components screen Click “Install” at the License Server Configuration screen Once the install completes, click the “next” button Click “Finish” at the Completing the StruxureWare 1.3 screen Verify the License Administrator by selecting Start=>All programs=>Schneider Electric=>StruxureWare 1.3=> StruxureWare License Administrator Verify License Administrator editor appears To load the License File select the “Licenses” tab Select the Add License drop down=>Add License from File Point to your License file and click “open” After License Load click the close button Verify the License file gets loaded and Status is Valid Click “Ok” Perform a complete install of Device Administrator Select Device Administrator.exe in build of interest On Welcome screen select Next Agree to End User License On Choose Components leave default and select Next After install select Next Finish the Device Administrator installation Perform a complete install of ES Select build of interest ex 1.3.0.xx Locate and click the WinES folder Click on the StruxureWare.Enterprise.Server-1.3.0.xx.exe After the loading process completes, click “next” on the Welcome to the StruxureWare screen Click the “I agree” button at the License Agreement screen Click the “Next” button at the Choose components screen Verify database location and Click the “Next” button at the Choose install Location for database Click the “Next” button at the Enterprise Server Configuration screen Click “Install” at the License Server Configuration screen Once install completes, click the “next” button Click “Finish” at the Completing the StruxureWare 1.3 screen Verify the Server is running by selecting Start=>All programs=>Schneider Electric=>StruxureWare 1.3=> StruxureWare Software Administrator Reboot PC to sync the services After reboot verify that the ES and I/O Server is running as a service. The ES is hardcoded when an I/NET interface is present; I/NET service is automatically started first. That is why when the system is restarted it always comes up in the correct order.   Perform a complete install of .Net Framework 4.0 "Microsoft .NET Framework 4 (Web Installer)"' Verify .net Framework 4.0 is not installed (look if listed in add/remove programs) Go to http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17851 Verify you are attempting to download "Microsoft .NET Framework 4 (Web Installer)" Verify download .exe is "dotNetFx40_Full_setup.exe" Click the "download" button Verify .net downloads successfully Perform a complete install of Workstation Select build of interest ex 1.3.0.xx Locate and click the NspClients folder Click on the StruxureWare.Workstation-1.3.0.xx.exe After the loading process completes, click “next” on the Welcome to the StruxureWare screen Click the “I agree” button at the License Agreement screen Click the “Next” button at the Choose components screen Verify Installation type and Click the “Next” button at the Workstation Installation Type Screen Click “Install” at the License Server Configuration screen Once the install completes, click the “next” button Click “Finish” at the Completing the StruxureWare 1.3 screen Verify the Workstation is running by selecting Start=>All programs=>Schneider Electric=>StruxureWare 1.3=> StruxureWare Workstation Verify "Building Operation workstation" screen appears Select either Windows or Other User, enter user name and password and select "log on" (for assistance, view Workstation Log on failure due to unidentified port) Select either the Administration or Engineering view Verify Workstation System tree screen appear Verify that Device Discovery + I/NET Devices shows all Links and controllers Select and Right-click on top of tree "Server 1" Object - example: "Server 1" within the System Tree Pane Click New => Interface Verify "Create Object" window appears Within the "name the object" select "I/NET Interface" Create a name - example: "I/NET Interface" Click "create Select Server 1 Select "Device Discovery" tab Click drop-down using the "Select device type" Select "I/NET devices" Verify Links and controllers appear in List view Verify that Drag and Drop and Upload (Get Configuration) works correctly Select Server 1 Select "Device Discovery" tab Click drop-down using the "Select device type" Select "Inet devices" Verify Links appear in list view Select desired Link and expand Link Verify DCU's appear within the Link Select the DCU within I/NET devices - example: "DCU 9551- DCU - 7728-x " Drag and drop the selected DCU into "I/NET Interface" Verify the DCU dragged successfully. Select the created DCU - example: "I/NET DCU (1)" within the System Tree Pane Click the "Properties" tab Go to the "Configuration" window within the "Properties" tab Verify the "Link Number"(LL) and 'Station Number"(SS) info Click the Actions => Upload" or right click=>Upload Select the "List View" tab Verify all of the Points objects for the DCU controller appears and is online. Verify that you can drag and drop and perform an Upload (Get Configuration) all point types and controllers Select Server 1 Select "Device Discovery" tab Click drop-down using the "Select device type" Select "Inet devices" Verify Links and controllers appear in list view Select desired Link/s and expand Link Verify controllers appear within the Link Select multiple controllers of different point types within I/NET devices Drag and drop the selected controllers into "I/NET Interface" Verify the controllers dragged successfully. Select "I/NET Interface" select the List view tab Select multiple controllers types within List view Click the Actions => Upload" or right click=>Upload Verify all of the Points objects for the DCU controller appears Perform an Update firmware (DCU Download) to a downloadable DCU type from StruxureWare Building Operation. Verify the Binary file for the selected DCU at the following location: C:\INET Seven Data\Data Copy the Binary file Rename the existing Binary file and make sure the file updates. Within StruxureWare, Right-click on the specified DCU Click the "Update firmware" Verify the Software Restore Editor appears. Locate the Link, Site and or station of the DCU Select the Software and Database options Verify software directory is C:\INET Seven Data\Data and Run in Dial Retry Mode is checked. Click "download" Verify the Software Restore Editor appears and starts the download. Verify the "Binary date" on the Software Restore editor matches the date of the updated Binary file. Verify the restore completes. Click Close. Validate that the Rev shown in the Summary Configuration view is the expected number. Perform a Backup (DCU Save) Verify that a current .SAV file exists for the DCU at the following location. C:\INET Seven Data\Sav Within StruxureWare, Right-click or select the specified DCU Click the "Backup" or Actions=> Backup Verify the status editor appear. Verify .SAV file date updates at the following location. C:\INET Seven Data\Sav Perform a Restore (DCU Restore) Verify that a current .SAV file exists for the DCU at the following location. C:\INET Seven Data\Sav Modify the .SAV file name to reflect as being old) Log into the Host Tool and locate your DCU Go to the point summary for the DCU and select "zoom" Delete 2 of the points Click yes to confirm Click close and save the DCU. Within StruxureWare, Verify the dirty flag appears in the DCU Select the DCU and Click the Actions => "Upload" or right click=>Upload Select the "List View" tab Verify the 2 Points objects are deleted from the DCU Go into C:\INET Seven Data\Sav and Modify the current .sav file name to reflect delete. Modify the former "old" .sav file name back to the original XXXX.sav Within NSP, Right-click on select the specified DCU Click the "Restore" Verify the Software Restore Editor appears and starts the download. Select "INET Interface" select the List view tab Verify the previously deleted points objects appear. Force a State change to a Point object using (StruxureWare) Make sure the screen is in split mode or split-screen.. (INET / StruxureWare) Using INET, Select your Discrete Alarm (DA) point type object from Controller Summary Make sure the Point value = off and Test is "on". Within StruxureWare, select the same Discrete Alarm (DA) point Right-click (Discrete Alarm (DA) point) =>properties Scroll down to Values Change the Value of the point to "on" by clicking the drop-down and selecting "1". (Value will vary upon Setup) Click ok Verify the state changes on the (Discrete Alarm (DA) point) object. Force a value change to a Point object using (StruxureWare) Make sure the screen is in split mode or split-screen.. (INET / StruxureWare) Using I/NET, Select your Analog Input (AI) point type object from Controller Summary Turn Test is "on" Within StruxureWare, select the same Analog Input (AI) point object Right-click Analog Input (AI) point type object =>properties Scroll down to Values Change the control value by entering a numeric value. Click ok Verify the value changes on the Analog Input (AI) point type object. Create a Global Point scenario between 2 points Setup a DLA configuration for 2 Discrete Output (DO) points Using I/NET, Go to DCU/Discrete Output (DO) point in Control Summary click "control" Verify the point control editor appear Make sure both Point values = off Go to StruxureWare, Locate the 2 Discrete Output (DO) points Change the view to Engineering. Locate and drag both Discrete Output (DO) points and drag them into the watch window Within INET, change the control state of the point to "on" by clicking the drop down and selecting "1". (Value will vary upon Setup) Verify both points change to the "on' status Within StruxureWare, change the control state of the point to "off" by clicking the drop down and selecting "0". (Value will vary upon Setup) Verify the that both point objects update and reflect the same state value in both StruxureWare and INET. StruxureWare Building Operation Commands Using I/NET, select Summary=> Controller Verify a "controller summary" window appears. select the first point type for the specified controller and select the "control" button Using StruxureWare, right click=>commands on the same point type as in I/NET Expand "Commands" Verify "manual," "Automatic," "Acknowledge," "Test On," "Test Off," "Point Control," "Alarm Configuration" appears per specific point types select "Point Control" Verify "point control" editor appears as in I/NET select "Download" Verify "value" = updates in the "point control", Controller Summary and Properties(Basic) in StruxureWare. select "Manual" within the Commands (if applicable) Verify "manual = True" for property name Test within properties (Basic)... (note this is only if it was False previously) Verify the information updates in the "point control", Controller Summary and Properties(Basic) in StruxureWare. Create an Alarm Event (if applicable) Verify "UnAcknowledge = True" for property name Test within properties (Basic)... (note this is only if it was False previously) Verify the information updates in the "point control", Controller Summary and Properties(Basic) in StruxureWare. select "Acknowledge" within the Commands Verify "UnAcknowledge = False" for property name Test within properties (Basic)... (note this is only if it was True previously) Verify the information updates in the "point control", Controller Summary and Properties(Basic) in StruxureWare. select "Automatic" within the Commands Verify "Manual = False" for property name Test within properties (Basic).. (note this is only if it was True previously) Verify the information updates in the "point control", Controller Summary and Properties(Basic) in StruxureWare. select "Test On" within the Commands Verify "Test = True" for property name Test within properties (Basic).. (note this is only if it was False previously) Verify the information updates in the "point control", Controller Summary and Properties(Basic) in StruxureWare. select "Test Off" within the Commands Verify "Test = True" for property name Test within properties (Basic).. (note this is only if it was True previously) Verify the information updates in the "point control", Controller Summary and Properties(Basic) in StruxureWare. Select "Alarm Configuration" within the Commands (if applicable) Verify an Alarm Configuration editor appears containing Alarm/Messaging Complete steps 2-30 until all point types are verified. StruxureWare Building Operation EDITS Using INET, select Summary=> Controller Verify a "controller summary" window appears. select the first point type for the specified controller and select the "zoom" button Using StruxureWare, right click=>edit on the same point type as in I/NET Expand "Edits" Verify "Point Configuration", "Calculation", "Event", "Trend Configuration","Runtime", "Time Schedule", "Temperature Control", "Demand control", "Consumption", "Door", "Elevator","Alarm Inhibit","Unitary Control" appears per specific point types select "Point Configuration" Verify a Point Configuration editor appears containing the point info Within I/NET Verify that Point Configuration editor appears for the specified Point type Complete steps 4-9 until all point types are verified. StruxureWare Building Operation Point Extension Using I/NET, select Summary=> Controller => from the main menu. Verify Controller Summary page appears Select "Zoom" Within in StruxureWare, Select the DCU select the specified point (LL.SS.PP.BB xx) Click on the "properties" tab =>Extensions tab Verify correlating point extensions appear and are checked. Verify point extensions can not be updated in StruxureWare. Go into I/NET (Resident I/O) Locate the specified point (LL.SS.PP.BB xx) Verify that correlating point extensions in I/NET matches to the extensions in StruxureWare. Visit two extension editors (C, EV, RT, CN, AI, TS, TC, TR, or DC). Add or modify an entry Repeat for all Points types Verify that correlating point extensions in INET updates and matches to the extensions in StruxureWare. Force a value change to a Point object using the Point Control (HOST Tool) dialog (StruxureWare Building Operation) Make sure the screen is in split mode or split-screen.. (I/NET / StruxureWare) Using I/NET, Select your Analog Input (AI) point type object. click "control" Verify the point control editor appear containing the value. Within StruxureWare, Load/Configure DCU right click=>edits on the same point type as in I/NET Expand "Edits" select "Point Configuration" Verify a Point Configuration editor appears containing the point info Change the control value by entering a numeric value. Click the “Download” button Verify the value changes in (I/NET and StruxureWare) Force a State change to a Point object using the Point Control (HOST Tool) dialog (StruxureWare Building Operation) Make sure the screen is in split mode or split-screen.. (I/NET / StruxureWare) Using I/NET, Select your Discrete Alarm (DA) point type object. (video alarm) Make sure the Point value = off click "control" Verify the point control editor appear Within StruxureWare, select the same Discrete Alarm (DA) point Right-click (Discrete Alarm (DA) point) =>Commands=>point control Verify the point control editor appear Change the control state of the point to "on" by clicking the drop-down and selecting "1". (1 or 0 Values will vary according to setup) click ok Verify the state changes on the (Discrete Alarm (DA) point) object in both (I/NET / StruxureWare) StruxureWare Building Operation Time Schedule Update the ES Server to reflect your time zone by going to Tools=>Control Panel (Date and Time) Please see Time Synchronization of the ES and AS for more information.  Save your time zone Right click on Server1 => New=> Schedule Verify the Create Object editor appears Select "Digital Schedule" and click the "Create" button Verify the Digital Schedule object appears in the system tree Within "Digital Schedule" select "New schedule event" icon or Select the time period of choice Verify the "Schedule Event Properties" appear Create a schedule by selecting a Day of week and a Time and click the ok button.(Set the time to a future desired time) Save the schedule select "Digital Schedule" and right click=>"edit bindings" Manually Bind the Digital Schedule(Value) to Digital Point object(Control Value) Save and exit bindings. Switch your view to engineering view and drag your Digital Point object into the watch window. Verify the Digital Point object is set to "off" Take a look a the calendar and verify the time block is an "on" status Verify that when the start time is met, the Digital Point object updates to an "on" status I/NET Verify when the end time is met, the Digital Point object updates to an "off" status in I/NET. Create a Program Script in StruxureWare Building Operation (Digital) 1. Right-click on Server1 => New=> Program 2. Verify the Create Object editor appears 3. Select "Script Program" and click the "Create" button 4. Verify the Script Program object appears in the system tree 5. select "Script Program" and right click=>edit " 6. Verify the script editor opens up 7. Copy and paste the following script into the script program: Numeric Input pt1 Numeric Output DV1 if pt1 is True then turn on DV1 Else turn off DV1 Endif   Save the Script and minimize the script editor Verify no errors appear within the "check" box. Within the system tree, right-click on the "Script Program"=>edit bindings Manually Bind the DV1 Output to a Digital Point object (PVControl) Save the Script Program and exit binding. Switch your view to engineering view and drag your Digital Point object into the watch window. Verify the Digital Point object is set to "off" Select the Script Program and click on the "Input" tab Force the Numeric Input pt1 value to on or 1. Verify that your Digital Point object update to an on status. Verify that you can Convert an I/NET Graphic page using INET Conversion Tool (.gpg to .tgml) Within I/NET, Select "System=>New Graphic Page" Verify I/NET Seven Graphic Page appear Select "I/Net" from the main menu Select "Points" from the I/NET menu Choose a section of the page and left-click on the mouse. Verify the Point selection editor appears. Select a Point Object type and click OK Verify the Graphic appear Right-click on a graphic object and select properties Verify the "Point Object Drawing Styles Editor appear" Within the Editor locate Digital Point Style=> Icon plus value Within the Editor locate and fill in the applicable Options. ie……Display option Click Ok. Repeat steps 3 - 14 until all "……Point Style" on that Point object are used. Save the created graphic within I/NET, File=>Save As Verify the graphic file saves as .gpg file Within StruxureWare, Select "I/NET Interface and Actions=> "Convert graphics" Verify Export INET Graphics to StruxureWare Editor will appear Verify Source: c:\Program Files\INET Seven is populated Verify Look in a subfolder, Over-write existing files and Log conversion boxes are checked. Select the graphic page/s to be converted Verify Destination: c:\INET Seven Data is populated Click "Convert" button Verify the conversion completes Verify the graphic is converted from .gpg to .TGML format at the destination location. Verify that you can view the converted I/NET Graphic object in StruxureWare Building Operation Create a .sav file of the controller which you are converting. Within StruxureWare, Right-click Server 1=> New=> Folder Rename object as "INET Graphic" Verify the "INET Graphic" object appears in the system tree Right-click on "INET Graphic"=> Graphic Verify the Graphic "create object" editor appears. Click the "Next" button Verify the "Basic Settings" appears. Locate the converted files by clicking on the [...] symbol at the end file line. Point to the Graphic *.tgml to be opened Select the specified cell "Graphics Viewer" tab and select open Verify the Graphic file object appears Click "create" to process the Graphic object. Click on the Graphic object Verify the Graphic object/s appears in StruxureWare. Verify that the graphic object points can be controlled using the graphic property editor Double click on the graphic page Verify page editor appear Update the control state or value from the page editor Verify the Graphic updates in both StruxureWare and I/NET Verify that you can edit and save the .tgml (StruxureWare Graphic Editor) Launch the StruxureWare Graphic Editor Click on file=>open=>file Locate and select your .tgml file Click "open" and verify the .tgml graphic appears Update the graphics and click the save icon. Verify the graphic saves correctly close the Graphic Editor Right-click on "INET Graphic"=> properties Verify the Graphic "create object" editor appears. Click "Next" button Verify the "Basic Settings" appears. Locate the converted files by clicking on the [...] symbol at the end file line. Point to the Graphic *.tgml to be opened Select the specified cell "Graphics Viewer" tab and select open Verify the Graphic file object appears Click "create" to process the Graphic object. Verify the updated Graphic object appears in StruxureWare. Verify the creation and operation of all Display Windows Types - Verify that all these windows update with live data ***Ensure that the Host Masking and Message Masking is set*** Using I/NET, select Summary=> Controller => from the main menu. Verify AMT is running Verify a "controller summary" window appears. Select your Discrete Alarm (DA) point type object. (video alarm) Verify the Point Object is "off" Using StruxureWare, Select your Discrete Alarm (DA) point type object. (video alarm) Right-click on the point type object and select Properties (Value) Change the control state of the point to "on" or 1 Change view to engineering Click on the "alarms" tab Verify alarm messages appear within the "Alarms" window Verify all of the messages within the columns are parsed and are correctly filed Click on the "events" tab Verify alarm messages appear within the "Events" window Verify all of the messages within the columns are parsed and are correctly filed Using I/NET, Verify AMT receives the event message, Exit Alarms - renter - verify that all windows are returned to the same position per operator. Verify that all alarms and events are time-stamped to the nearest second. Verify add, remove and re-organize columns using (Add/Remove columns) Click on the "alarms" or "Events" tab Right Click on a column Verify the "Add/Remove columns editor appear Select a checkbox to add or Select to remove an attribute Click the Ok Button Verify columns are added and removed. To reorganize a column, select and drag the column either right or left Verify the column is re-organized Verify that an operator may acknowledge alarms Using I/NET, select Summary=> Controller => from the main menu. Verify AMT is running Verify a "controller summary" window appears. Select your Discrete Alarm (DA) point type object. (video alarm) Verify the Point Object is "off" Using StruxureWare, Select your Discrete Alarm (DA) point type object. (video alarm) Right-click on the point type object and select Properties (Value) Change the control state of the point to "on" or 1 Click on the "alarms" tab Verify alarm messages appear within the "Alarms" window Select the active alarm message and Click the Acknowledge icon Verify the message is acknowledged Verify that the operator may hide and unhide alarms from each alarm type window Using I/NET, select Summary=> Controller => from the main menu. Verify AMT is running Verify a "controller summary" window appears. Select your Discrete Alarm (DA) point type object. (video alarm) Verify the Point Object is "off" Using StruxureWare, Select your Discrete Alarm (DA) point type object. (video alarm) Right click on the point type object and select Properties (Value) Change the control state of the point to "on" or 1 Click on the "alarms" tab Verify alarm messages appear within the "Alarms" window Select the active alarm message and Click the Hide alarm icon Verify the message is hidden Click the show hidden alarm icon Verify the message is appears Select the message and click the unhide alarm icon Verify the message is appears Create a A Sample and/or D Sample in I/NET ***Verify that the time zone is updated to reflect your zone*** Using INET, select Edit => Controller => Point Extensions => Trend Sampling (TR) Verify the TR extension is set up. Set up Trend Definitions in INET for either (ASample or D Sample) Verify Trend Results in INET Using StruxureWare, Right click on INET Interface and select "New => Value" Verify "Create Object" window appears Verify "value appears in the name field. ie (Value PP.BB AI) Change the name "value" to "A Sample Trend log Value" Click the "Create" button Verify Newly created INET Trend Object (A Sample Trend log Value) appears in StruxureWare. Select Trend log Value Go to the "basic" tab or Right click on the Trend object and select "properties" Locate the "point to trend" Click on the "…" and select an point object to trend Click select button Verify the correct path appear Click "ok" button Verify the Trend Log Value Object appears within the INET Interface Tree Locate and right click on the newly Created Trend Log Value Object (LL.SS.PP.BB AI). Go to the "Actions=> view in" from the main menu or right click on the Trend object and select "view in" Select "Trend Log List"=>"New Trend Log List" Verify Trend entries appears in the Log info in StruxureWare click the save icon Verify the Save Object editor appears Point to Server 1 Name the Trend object "A Sample Trend log List and "save" Verify the newly created Trend log object appears and Trend log entries appears StruxureWare Verify that you can Add an A Sample and/or D Sample Trend chart Locate and select the newly Created INET Trend object (LL.SS.PP.BB AI). Go to the "Actions=> view in" from the main menu or right click on the Trend object and select "view in" Select "Trend Charts"=>"New Trend Chart" Verify Trend Chart and Chart Lines appears in the in StruxureWare click the save icon Verify the Save Object editor appears Point to Server 1 Name the Trend object "A Sample Trend Chart and "save" Verify the newly created Trend Chart object appears and Chart Lines are being plotted. Configuration and Log into Webstation Locate the StruxureWare machines IP address by typing (IPConfig) at the command prompt Make note of the IP Address (example: 10.159.XXX.XXX) log into the remote machine and run the browser (IE) On the remote machine enter the target StruxureWare machines IP address at the browser address line and click enter….(example: http://10.159.XXX.XXX) Verify "Welcome To StruxureWare" editor appears enter user name: admin, password admin and click "log on" Verify Webstation system tree view appear. DCU Tests (controlling Points) Select "INET Interface" select the List view tab Verify all of the Points objects for the DCU controller appears Select and Right click (Discrete Alarm (DA) point) =>properties Scroll down to Values Change the Value of the point to "on" by clicking the drop down and selecting "1". (Value will vary upon Setup) click ok Verify the state changes on the (Discrete Alarm (DA) point) object. Right click Analog Input (AI) point type object =>properties Scroll down to Values Change the control value by entering a numeric value. click ok Verify the value changes on the Analog Input (AI) point type object. Graphics Click on the Graphic object Verify the Graphic object/s appears in Webstation. Double click on the graphic page Verify page editor appear Update the control state or value from the page editor Verify the Graphic updates in both StruxureWare and INET Alarm and Messages Change view to engineering Click on the "alarms" tab Verify alarm messages appear within the "Alarms" window Select the active alarm message and Click the Acknowledge icon Verify the message is acknowledged Verify all of the messages within the columns are parsed and are correctly filed Click on the "events" tab Verify alarm messages appear within the "Events" window Verify all of the messages within the columns are parsed and are correctly filed Install StruxureWare/ES/I/NET up to 10 workstations (Windows 7 or Windows XP sp3). Connect multiple Stations to one ES Install only the StruxureWare Workstation Log into the Workstation is running by selecting Start=>All programs=>Schneider Electric=>StruxureWare 1.3=> StruxureWare Workstation Verify "Welcome To StruxureWare" editor appears Enter user name: admin, password admin Enter the IP address of the with the main ES, server: IP (XXX.XXX.XXX.XXX) Click log on" Select either the Administration or Engineering view Verify the Workstation System tree screen info from the main ES machine appears. Repeat steps 1-6 on multiple machines. Connect No ES StruxureWare client (w/o I/O server) to a ES StruxureWare client (with I/O server) Locate a machine that has StruxureWare Workstation/ES and I/NET (I/O server) installed and make note of the IP address Install only the StruxureWare Workstation on another machine Log into the Workstation is running by selecting Start=>All programs=>Schneider Electric=>StruxureWare 1.3=> StruxureWare Workstation Verify "Welcome To StruxureWare" editor appears Enter user name: admin, password admin Enter the IP address of the with the machine above Click "log on" Select either the Administration or Engineering view Verify the Workstation System tree screen info from the main ES and I/NET (I/O server) machine appears. Click on "INET Interface" and Actions=>"Launch INET" or right click=>"Launch INET" Verify the INET does not launch. Convert and Launch Customer Graphics Connect to a Host LAN tap Configuration (1200 and 9600 baud rate) Select Server 1 Select "Device Discovery" tab Click drop down using the "Select device type" Select "Inet devices" Verify the Host LAN Configuration appears in the list of Links in list view Connect to a 731 Device Select Server ES or AS Select "Device Discovery" tab Click drop down using the "Select device type" Select "Inet devices" Verify the 731 Device appears in the list of Links in list view

Issue How to turn on and release a specific command priority on a BACnet point? Product Line EcoStruxure Building Operation Environment ES AS Bacnet interface Script programming Cause Wants an example script program to turn on/ off specific BACnet command priorities in a BACnet device. Resolution To control a specific Digital or Analog Output in a BACnet device, from a script program you would use a Numeric Output in the program that has its value set as required by the program. This Output from the program is then bound to the specific command priority attribute of the point to be controlled. To release control from that Command Priority the "Relinquish" keyword is used in the program to Null that specific command priority and allow lower commands to take control of the output.   Here is an example AS test program that turns on a Digital Output for 4 seconds and then releases it for 4 seconds. The Numeric Output DOControl should be bound to the required Output Command Priority 2, it is written as a fallthru program. Notice; the Relinquish command is releasing the output from Command Priority 2 as used in this example.   Numeric Output DOControl DOOnLine: DOControl = Active Wait4: If TS > 4 Then goto DOOffline Else goto Wait4 DOOffline: Relinquish(DOControl,2) Wait4More: If TS > 4 Then goto DOOnline Else goto Wait4More   This type of script program can be located in the Application of the BACnet interface and control outputs on 3rd party BACnet products or b3 controllers. Note: For control of b3 outputs it is often better to put an appropriate control program (Not the above code) within the b3 controller itself, making it more robust in case of comms failure and also reducing communications traffic. Also check out the Convert Continuum Plain English into SBO Script Quick-Help video on the Exchange.

Issue How to set the IP address of a Xenta 5/7/9xx through serial communication. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause If the IP address of a Xenta 5/7/9xx is not known initially, then no configuration can be done through the IP interface. The IP address must be set through serial communication. Resolution IP setup for a Xenta server (Xenta 5/7/9xx) through serial communication for step-by-step instructions for this process.

Issue What is enabled on a Continuum Security Key? Product Line Andover Continuum Environment Continuum Security Key Cause There's a need to know what version of Continuum is enabled on the key. Resolution Note: The Excel method for viewing enabled key features mentioned below no longer works with Windows10 or greater and because of CyberSecurity issues ActiveX controls have been deprecated by Microsoft in favor of more secure web technologies.  This feature will not be updated for Cyberstation.   The supported version of the keys and what options are available on the key can be verified by doing the following using Microsoft Excel on a Workstation with Continuum and the key installed: Open MS Excel Select Insert> Object Select SecurityKeyreader Control and then Ok You will see an object inserted into the spreadsheet with a list of products on the left and options on the right. Example: Serial Number 1016019 Options Number of Points -1 Adv.WebServerEnable Number of Personnel -1 EpiSuiteEnabled Platform Lan(Multi) OPTxtLoggingEnabled Type Prog.Intg. PESourceCntlEnabled Max Version 1.79 Global 1 0 Global 2 0 Global 3 0 Global 4 0 Windows 7 64 bit will not support the MMC.exe option (mentioned below)   Use the command       mmc.exe /32     This will allow the ActiveX snap-in to be added and will work on a 64 bit PC   ActiveX controls in Excel 32 bit are not exposed by default. Use the following Excel spreadsheet (zipped) to read the security key instead. (Excel must be installed and must be on a 32 bit PC(64 bit shows this as blank) Security Key Reader Excel File You may be prompted to enable the ActiveX control Excel 2003 - The application is about to initialize ActiveX controls that might be unsafe. If you trust this document, select Yes and the control will be initialized. Excel 2007/2010 - Notice the Security Warning below the Toolbar                                   Click options                                   Select Enable this content Upgrading a key requires a call to repair (978-975-9464) for a cookie to update the key. In order to install the cookie, you must use the program, CyberKeyWriter2.exe to enter the new key which is on every Cyber CD in the Continuum\bin folder.    Note: Also see Accessing Continuum Security Key information using MMC instead of Excel that describes another method to see this information using MMC. This feature does not work with newer versions of Windows 10

Issue How to add Web Service and create SOAP Web Service with Graphic Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with release 1.2 or later Cause What are Web Services and how to add to my existing StruxureWare Building Operation site. How to add SOAP Web Service files and how to add to a project or site How to create values from SOAP Web Service Files How to add values to graphic that uses the values from SOAP Web Service Resolution Wikipedia: A Web Service is a method of communication between two electronic devices over the web (internet). W3C: A "Web Service" as "a software system designed to support interoperable machine-to-machine interaction over a network." Web Services: are hardware, programming language, and operating system independent Applications written in different programming languages and running on different platforms can seamlessly exchange data over intranet or the internet using Web Services Web Service interfaces are supported in both the AS and ES(does not support connection over a ProxyServer) Like BACnet, Lon, and Modbus, you can create a Web Service interface. EWS Interface - EcoStruxure Web Services Script Web Service - Generic Consume via Script (Web Service addition Script Web Service) Simple XML Web Service - Rest Generic Consume via Binding Tool (Web Service addition Simple XML Web Service) SOAP Web Service - SOAP Generic Consume via Binding Tool This article explains adding Sunrise and Sunset for a particular location data using SOAP Web Service: Select New > Interface > Web Service > SOAP Web Service Next Paste the URL which has the SOAP Web Service feature ((to find sunset/sunrise for your area, Google WSDL data) and location coordinates Get Operations button pulls in the data. Select Next  which shows the values and times and then select Create Create values by highlighting SOAP Web Service then File > New > Value Choose Next and highlight the specific for the values then select Create Here are the SOAP Web Service sunrise/sunset values If desired, Bind those values to a graphic Lastly for SOAP Web Service a graphic is created and the values which come from the SOAP Web Service are place on the page

Issue Sometimes just looking at the error message you get from e.g. TAC Vista or SmartStruxure when you try to send an email and it fails can lack information. Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista SmartStruxure WireShark Cause It is not necessarily all SMTP error messages and their explanation that are implemented in the software. Resolution For general information on WireShark usage read Using WireShark to analyse communications on an Ethernet network. If McAfee antivirus with HIPS is installed on the PC, use RawCap to capture the communication, as you will not see traffic originating from your PC online in WireShark. Additional reference for this article: Enhanced SMTP status codes   First of all when working with WireShark logs, it's a good idea to filter and focus the communication type you want to look at. In this case it's SMTP, so simply type smtp in the display filter and hit enter.   The easiest way to isolate a single smtp "conversation" between client and server, is to find one of the packets in the conversation, and in the "Analyze" menu click on "Follow TCP Stream".   This will give you the complete conversation in a separate window.   When you have used "Follow TCP Stream" be sure to set the display filter to "smtp" again when closing the window.   This is what happens if authentication is needed by the SMTP server but the client is not using authentication.   Here is the same attempt to send an email, but this time the client has enabled authentication   A little trick when using authentication is that WireShark can actually decrypt the Base64 encoded username and password. Simply right click on any SMTP packet, click "Protocol Preferences" and click "Decrypt AUTH parameters".   He are the packets decrypted   An error not easily detected by e.g. TAC Vista is error 535 "Incorrect authentication data". As stated in the enhanced status code table linked above, it simply means that either username, password or both is incorrect.   Though the product used may not have support for SSL and TLS, you can encounter SMTP server requiring it. Here is an example of a SMTP requesting SSL     For further info on troubleshooting sending emails from TAC Vista, please read Troubleshooting Sending Emails from a Vista Server.

Issue Device ID / Device Instance of SE8000 series BACnet controllers Duplicate BACnet Network Address alarms How to have 254 SSL Room Controllers on an Automation Server (AS) as shown in the SBO Automation Server and SE7000 and SE8000 - Architectural Guidelines Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment Automation Server Enterprise Server SE8000 Room Controller BACnet Cause There can be confusion from the difference in naming between SmartStruxure Lite(SSL) Room Controller(RC), SmartStruxure Building Operation and even Niagara(JACE). Bacnet Instance number in SSL = Object ID in SmartStruxure Building Operation COM Address in SSL = MAC Address in SmartStruxure Building Operation Resolution On the AS, considered is the Object ID of the two Comm Ports (as with all object IDs) they need to be unique across the system. A common ID is 1001 for CommA and 1002 for CommB of the first AS, then on the second AS CommA 2001, CommB 2002 etc. The key thing with BACnet is that every object (point, device, program, port etc) must have a unique Object ID. The SE8000 uses the Com Address referred to as the BACnet MAC Address in the AS. This, as detailed in BACnet COM Address of Room Controller SE7000 and SE8000, is the address range on just that one MS/TP bus. 1 – 127 are valid addresses, the AS (or bus master) will be address 0. If a second AS is on the same system this could use 83001 – 83127 for CommA, 84001 – 84127 CommB etc. Also SE8000 uses the BACnet Instance number which is called the BACnet Object ID in the AS. (This is the ID which must be unique across the whole system) So if you have the 2 ports used on one AS all 254 devices must have unique ID’s. When changing the Comm address in the SSL SE8000 to any value between 1 and 127, the Instance number will change as well. For example Comm address 9 would result in an Instance number of 83009. These will cover 127 stats that will go on CommA, and result in Instance numbers between 83001 and 83127. Any value above 127 will keep the Instance number unchanged. For CommB however, a site would need to change the Instance number manually. For example the first RC connected to CommB would be the 128th and would default to address 83127. So it is required to manually change the Instance number to 1083001 (up to 1083127). This defines unique Comm Addresses for ComB on the remaining 127 RC. When using an Automation Server (AS) you can find the Object ID and MAC address for devices on MSTP by using WorkStation and going to AS > System > Hardware > BACnet devices > Network_xxxx. A screen shot is below with the added columns Status, System Status, Object ID, and MAC address. In this first example, b3 controllers use the Object ID or Device ID of their serial numbers so each b3 is unique across the network. B3 controllers with serial numbers greater than 4194302 (the maximum allowed Object ID in BACnet) will be assigned a Device Object ID using a hashing algorithm to ensure it is unique. From an SE8000 series RC, BACnet network set-up screen shows when BACnet is detected in models. Select desired parameter and use up or down arrow to set parameter to desired value. The default BACnet instance number is generated by the model number and COM address of the controller. For example, The instance number of a SE8300A5B00 with a COM address of 57 is generated as "83057." The default instance number appears first. To change the instance number, use number pad and press Accept and Save. Below is a screenshot of the WorkStation logged into an AS, with the BACnet Interface and the MSTP network. The added columns show the Object ID and MAC address. Below is a screen shot of the WorkStation logged into the AS, with the System > Hardware Devices > Network_xxxx. The added columns show the Object ID and MAC address.  The screen shot below is the AS > BACnet Interface > MSTP Network > Configuration Settings.

Issue Cannot bring controller online in Continuum even though all settings are correct. Unable to browse to that controllers configuration webpage but can ping the controller. CPU LED blinking approximately two times a second (2 Hz at 50% duty). Product Line Andover Continuum Environment bCX40xx bCX96xx b3xxx i2xxx Cause The controller is in bootloader mode and has lost its application program. Resolution If the bCX is in bootloader mode, with the CPU LED blinking approximately two times a second (2 Hz at 50% duty), then there are a couple things you can try to do to get the controller back online before sending it back for repair. Basically it has lost its application program and dropped into bootloader mode. Try to uprev the controller with its application firmware to see if that will bring it back online. Attempt to uprev (Update OS) the controller from its device object in Continuum even though it may not show as online. Alternatively uprev the controller using the RoamIO to send the application firmware to the controller. If neither of these options work the controller must be returned to be repaired through your normal RA procedure for your region. (this option may no longer be available, due to the age of the controller) Note: An error code including 6818(hex) (c2026818 has been seen) or 26648(dec) during an attempted download or on a graphic. Example1: Example 2: See a Quick time movie to indicate CPU light modes for controllers that shows the various stages of the CPU LED blink rate.

Issue "Communication Failed" Alarm occurs when Adding an AS. Source: /Server 1/Servers/ASL/System/Server Communications/Models/2deef04c-05d1-41ae-9c3f-f84a9f7e0b41 Alarm "cannot verify lead object" appears even though AS is online. Product Line EcoStruxure Building Operation Environment StruxureWare Alarm Queue Cause The AS is unable to communicate with the ES. The ES may be able to communicate with the AS allowing the user to view and control the AS, but Value Binds will not work. This type of error can also occur as a result of multiple networks being accessed by the same PC.  It is important that if you are using multiple networks that the ES be configured with the IP address for the correct network. Resolution Ensure that no Firewalls are blocking configured ES and AS ports Ensure all devices are on the same Windows Domain In workstation, select the Enterprise server's Communication Tab and verify that the IP address listed for the ES matches the ES PC IP address. Right click on the ES and select Advanced > Repair Server Communication For more information see Creating Windows Firewall rules to allow StruxureWare Building Operation to communicate on the TCP port

Issue Send an SMS text message when an alarm occurs. Product Line EcoStruxure Building Operation Environment Alarming SMS Text Cause Sending an SMS Text message in response to an alarm condition will allow the responsible personnel to react immediately, even if they are not currently at the workstation. Resolution EcoStruxure Building Operation does not support direct SMS texting. One workaround is to use an Email to SMS Test service provider that handles conversion of emails to SMS, as emails are easily created in EcoStruxure Building Operation.   If direct SMS functionality is required there are work arounds with 3rd party programs such as SysManSMS via file output options (see Using Sysman alert server with StruxureWare Building Operation). Note that this third party products such as this are not supported or tested by Schneider Electric.

Issue [Invalid Address] Product Line TAC Vista Environment Vista Workstation Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Invalidate Resolved Addresses Cause If you view a controller in Vista Workstation and point values read [Invalid Address] instead of showing values, there are a number of troubleshooting techniques to rectify this. Unfortunately, [Invalid Address] is a bit of a "catch-all" error code. Since it can be difficult to determine the cause of the error, these troubleshooting suggestions will have varying degrees of success. 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 Check the label for N/P Designation If a programmable controller has read [Invalid Address] on every point since it was installed (it has never worked properly) then there is a chance that this is not a Network Presentation controller. These are referred to as stand-alone controllers and each of the 280 and 300 series have a non-network presentation variety. Check the label on the controller to make sure it says "302/N/P" or "282/N/P." If it just says "302" or "282" then this controller cannot communicate on a network and will never report values to a front end. Also see Xenta 280 or 300 Controllers without /N/P (networking and presentation) designation cannot communicate in a Network. In the Vista Workstation Right-click on the controller and choose Advanced Operations > Invalidate Resolved Addresses Proceed? Select Yes. Right-click on the controller and choose Advanced Operations > Read Address Proceed? Select Yes. Wait up to about 30 seconds for the values to populate. Download the Controller In the System Plug-in, Download Applications and Parameters to the controller Recommission the controller In the System Plug-in, TAC Network > Commence Communication (skip to this step for LON controllers) You may want to follow this action with another attempt at the steps outlined in the section above "In the Vista Workstation" Repair or recommission the Routers in the NL220 or Lonmaker database repair or recommission the Routers. Re-Do Group Bindings & Commence Communication: In the System Plug-in, LNS network > Create Group Bindings In the System Pug-In right click on the TAC Network and commence communication Re-doing group bindings ensures that the LNS network interface, and LON to IP routers receive message can 0 for the main xenta address broadcast in the network. Monitor Sets If your monitor sets have become corrupted, then every controller you download from that point on will say [Invalid Address] on every point. Monitor sets are actually stored on the hard drive of the PC, not in the LNS database. If you have made backups and passed them back and forth between PCs, as you often do during the commissioning phase, this invites corruption of monitor sets. There were some known issues with monitor sets in LNS version 3.24 that have since been corrected in LNS version 3.26. This can be downloaded from Echelon's website in LNS Server/Turbo Edition Service Pack 7. Go to http://www.echelon.com Navigate to Support > Support Resources > Downloads Log in with a user name and password. If this is the first time logging in, register for a free user name and password. Search for software in the Recommended Downloads category Find LNS Server/Turbo Edition Service Pack 7 (this is the latest at the time of this article, a newer one may exist and should be downloaded) Prior to restoring a backup, you may want to resynchronize the drawing making sure to check the option for "Sync monitor sets between drawing and database." Usually restoring the last good backup will fix up the monitor sets. If you do not have a recent backup, there are a couple of procedures that may help resolve the corrupted monitor sets issue.   Note: Viewing and altering monitor sets is only available in Echelon LonMaker. There is no analogous menu item in Newron's NL220. Do not download any more controllers. Check your monitor sets in LonMaker by navigating to LonMaker > Network Service Devices Click on the NSS which should have the same name as the network Select the Monitor Sets button If you get "Monitor set cannot be found. (Subsystem: NS, #160)" then your monitor sets are corrupt. Close down Vista Server & LonMaker (if you don't you will get an error when you try to validate that says "The Network Interface, database directory, or NSS type, conflicts with the already active network. (Subsystem: NS, #149)") Navigate to Start > Programs > Echelon LNS Utilities > LNS Database Validator Navigate to the LNS Network to Validate Check the Repair Database checkbox Hit the Validate button If that does not find and repair the monitor sets, the following steps may help. Make backup of the LNS database. Start LonMaker. Do not start Vista Server. Go to the monitor sets (LonMaker > Network Service Devices > NSS > Monitor Sets) and right-click and delete the monitor sets Run the System Plug-in and create a brand new Vista database in a different location than your current database. Stop the Vista Server and start it again Check the monitor sets again, they should be right now Stop the server again and change back to your original Vista database Non-Latin Characters If you use a signal name or description in the XBuilder Device Editor with non-Latin characters (like Swedish åäöÅÄÖ) you will get [Invalid Address] when you view the signal in Vista. Value pages are displayed correctly. Do not use non-Latin characters for signal name or description. This issue has been confirmed in versions 5.1.2 - 5.1.4, and will be fixed in a future release. Classic Networks View the Address Tab under the controller's properties in Vista Workstation Check Address Table slots 0 and 1. If the "Domain Index" and "Member or Node" have been manually altered, set them back to 0. An applicationless controller will display [Invalid Address] in a classic network, whereas in an LNS network, it would simply fail to commission due to its applicationless state.  Direct download the controller through the Menta serial cable to see if it resolves the error. Xenta 700 Menta values See Xenta 700 Menta Object Values report [Invalid Address] in Workstation, Read operation failed. Delete, Destroy, Redo This is your last resort. If you have tried everything else possible, it is time to remove this controller from the database and start from scratch. The exact steps and methodologies may change based on your network and controllers, but basically you need to remove any mention of this controller and add it back in as though it were a brand new device. Decommission the controller Delete the device Delete the device template In the System Plug-in, remove the device from the TAC Network Update the Vista Database Create a new controller Browse in a Menta file Update Vista and download

Issue Unable to send out emails using Gmail SMTP server (smtp.gmail.com) with the following error messages in the station's standard output. "javax.mail.MessagingException: 530 5.7.0 Must issue a STARTTLS command first." Authentication has been enabled in the system.properties file as per Mail Service in a Niagara R2 UNC station configured correctly but e-mails not being sent to the SMTP server. Product Line TAC IA Series Environment I/A Series R2 Cause As with most public SMTP servers, like Gmail, the outgoing mail SMTP server requires TLS (Transport Layer Security) or SSL (Secure Sockets Layer) which I/A Series R2 does not support. Resolution Use an SMTP server that does not require TLS or SSL.

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. Issue Failed to read events from the event log database. Product Line TAC Vista Environment TAC Vista Workstation Cause This error is sometimes displayed upon login to the TAC Vista Workstation. It indicates there is a problem with the connection between the Vista Server and the SQL database that stores event data. Resolution Before making any further tests, make sure you have MSXML 4.0 SP3 installed and then check if it works. It can be downloaded here: https://www.microsoft.com/en-us/download/confirmation.aspx?id=15697 The first thing to check is the SQL connection. Open the TAC Vista Server Setup In version 5.1.3 and prior: Start > Programs > TAC > TAC Vista Server X.X.X > Server Setup In version 5.1.4 and later: Start > Programs > Schneider Electric > TAC Vista Server X.X.X > Server Setup Go to the SQL Server tab In the lower right-hand corner of the tab, press the Test Connection button. If it pops up a window that says "Connection test succeeded!" then your SQL connection is okay. If it fails the connection test, check the instance name. If you are using default settings it should be: SQL Server name: PCname\TACVISTA or (local)\TACVISTA Log database name: taclogdata If these are set correctly and the connection still fails, one method for reestablishing the connection is to uninstall/reinstall the Vista software. Make sure SQL Server Agent is running. Right-click on My Computer and select Manage Navigate to Computer Management (Local) > Services and Applications > Services Find SQL Server (TACVISTA) -- assuming the default SQL instance is being used. Make sure the service status is running.  Start the service if needed. If there is no problem with the SQL connection, check the Server object's Network Master. In Vista Workstation, right-click on the Vista Server object and select Properties On the General tab, in the Network pane, check the Master: name In a one-server network, the Network Master must be set to the Server object name. Check for queued files in the $queues folder Navigate in a Windows Explorer window to the Vista Database. (If you are unsure of the location, you can verify it in the TAC Vista Server Setup Vista Database tab). Go to the $queues folder Look inside the insertevents and insertlogvalues folders. Are they empty or are they consistently growing with files? This is where data is stored temporarily before it is written to the SQL database. Having queued files is not necessarily a sign of a problem. However, if there is a connection problem, these folders will continually grow in size without older queued files being written from the folder. In the case of the error "Failed to read events from the event log database", it is possible that a queued file is causing the error prompt and that deleting it will fix it. If the data is not of dire importance, delete all the files inside both of the $queues folder. For more information see An efficient method for deleting all queued files in the $queues folder. Reconfigure the log database Open the TAC Vista Server Setup In version 5.1.3 and prior: Start > Programs > TAC > TAC Vista Server X.X.X > Server Setup In version 5.1.4 and later: Start > Programs > Schneider Electric > TAC Vista Server X.X.X > Server Setup Go to the SQL Server tab Change SQL configuration from Typical to Custom Change the Log database name Hit Apply. It will warn you: "TAC Vista integrated SQL backup/restore function will not be available in custom configuration." Hit OK. It will then warn you: "No log database was found on SQL Server. Create and configure a log database?" Hit Yes.   At this point, if no backup features are necessary, and the error has cleared, this is a viable solution. It is not, however, recommended to maintain a site without any log backups. The next step would be to switch the Vista Server Setup SQL configuration back to Typical. Hit Apply. You will be warned: "Log database was found but needs to be reconfigured. Reconfigure log database?" Hit Yes.   After reverting to typical SQL settings, the error should clear. If it has not, it may be time for some database management. Performing Database Maintenance Follow the steps in the article Performing database maintenance with Vista 4.5.0  to set up a log and event backup and to clean up old data. Schedule a backup to occur (now or soon after) The next time you log into Vista Workstation, the error should be cleared. If the error is sporadic, it could be the event viewer has too many events If the error only occurs when logging in to Vista Workstation, and doesn't happen every time, it could be that too many events are being brought into the Event Viewer on login. All events specified in the filter for the event viewer are uploaded to the Workstation. If too many events are specified, problems occur. In Workstation, go to the root TAC Vista folder Right-click $Eventview and select properties Go to the Date and Time tab Set the Time period to Last 1 Hour(2) instead of Last 1 Week(s), which is default Check the Windows Event Log If all else fails, check the Windows Event log for more information about the error. Checking this may provide you with the answers you need, or at least give you more information to provide to Product Support if you need further assistance. Instructions available in Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes. Right-click on My Computer and select Manage Browse to Computer Management (local) > System Tools > Event Viewer > Application Look for Type Error events with Source Vista. This may help you determine the source of the error.

Issue “IP_ADD_MEMBERSHIP failed” appears in the Application Director output during reboot of the Jace and in the Station Discovery on the Niagara Network after a failed discovery attempt Product Line TAC IA Series Environment ENC 520, 410, Jace 6E, 645, 700, 8000 controllers using G3/AX. The second Ethernet interface only applies to the Jace 6E, 700, 645 and 8000 Cause Incorrect or no default gateway assigned in the TCP/IP Configuration or Interface 2 is enabled and set for DCHP with no DHCP server available to that interface. See the notes on the illustration for possible configuration faults. Resolution Make certain you have a valid IPV4 or IPV6 (schema dependent) Gateway entered for the Interface 1 IP configurations. If set to DHCP, ensure there is a DCHP server available on the interface. Disable all unused interfaces and IPV6 if not applicable. If there are problems accessing or configuring the interfaces, you may need to use the System Shell of the ENC/Jace and correct the configurations there. Need to correct invalid IP address or subnet mask entered into an ENC or JACE