Building Automation Knowledge Base

Issue Unable to gain access to Building Expert Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi Purpose Manager MPM-GW MPM-UN MPM-VA Cause The admin password has been changed and the user has lost the password Resolution For MPM with firmware 2.14 and earlier: Send the MPM 'default.db' file to Product Support.  From a web browser, you can save the default.db file to the local drive by typing the address http://[ip_address]/root/default.db (replace [ip_address] with the actual IP address of the MPM, or 10.50.80.2 if bootloader is used) For MPM with firmware 2.15 and later: Send the MPM Node ID or MAC Address to Product Support. Refer to the document StruxureWare Building Expert Password Recovery When Accessing MPM - Reference Guide for the procedure to obtain the MPM Node ID or MAC Address.

Issue Looking in the controller error log, what does this error indicate and how do I troubleshoot it? 0x00006c0e 0x00002600 0x020a8536 0x00000000 0x00000000 error transmitting (LAN_ERR_TRANSMIT_ERROR) Product Line Andover Continuum Environment Continuum Controllers ControllerErrorLogTool error log report Cause This error can be the result of comms buffers being too full to transmit data to the LAN. Resolution Check the following: Check the scan rate of the controller to see if it is high. If high (above 1.0 scans/sec), stop programs to see which may be causing problems. Are there a lot of remote points being read or written from/to this controller? Try minimizing this traffic by limiting the number of points per program line, set COV Increment values, etc... If writing to 3rd party controllers, check how often your programs are doing this. Are they being sent each scan or only once when the value is required? Many BACnet writes per second can saturate the communications buffers and cause communications bottlenecks. Run a Wireshark capture by mirroring the controller's NIC card. This will show the traffic that is making it to the controller's NIC. See if there is traffic from 1 or more IP addresses that could be affecting the system and eliminate or reduce that traffic.

Issue Unable to upload the same Lua script to multiple Room Controllers at the same time Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Automation Server Premium SSL SE8000 (all) Cause The alternative method of uploading the script to each of the room controllers using a USB cable Resolution To upload a script to multiple Room Controllers, follow the below steps: (This procedure assumes the BACnet MSTP network is already setup) 1 - Log in to Building Operation Workstation 2 - Right-click on MSTP network and click "Search" 3 - Search for "Lua program 1" or any other Lua program object 4 - Highlight all the Room Controllers that the script will be transferred to then click on the "show/hide property grid" button. 5 - Expand the "Basic" tab and copy the Lua script in the "Description" field then click Save. 6 - The script will be uploaded to each of the Room Controllers one at a time and will be played automatically. Recommendations & Limitations: - Each Lua Program can take up to 460 bytes of text (per script). (Total of 10 Lua programs) - Script must be placed on a single line. Use semicolons ( ; ) as carriage return - Use multiple Lua programs if the 460 bytes limit is exceeded - Encapsulate logic inside the following if statement if the logic is intended to run once: if not init then    ---Script logic here    init = true end For general information about Lua programming for SE8000 Room Controllers, refer to the following guide: Custom Programming Guide for SE8000 Series Room Controllers - Application Guide

Issue Modbus TCP Device (Slave) address greater than 247 Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (AS, AS-P, AS-B)  Modbus TCP Network Modbus TCP Gateway Cause Modbus TCP Device (Slave) address 248 is reserved and cannot be used. (Modbus TCP Network or Gateway) SmartStruxure supports up to address 247, as per StruxureWare Building Operation - Technical Reference Guide (up to v1.6.1). There was a defect within v1.5.0 and earlier that caused address 250 to be used if the Device address is set to "Invalid." This defect was corrected in v1.6.1. Resolution From v1.9 this is corrected, so it is possible to define addresses for Modbus TCP devices from 1-247 and 249-254 Device addresses 0 and 248 are reserved. Device address 255 is used as the Default address.   For Modbus RTU RS485 master/slave networks, slave device addressing is different, see KB article Modbus RTU slave address.   Further information about Modbus can be found in the KB article Modbus basics.

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 reset an NC2 9680 model controller Environment CX 9680, NCII, NC2 Cause While upgrading/downgrading the controller firmware, communications was lost and the controller was not able to communicate afterwards.   Resolution Reset controller and re-commission. Please click here for document on how to reset the CX9680 controller.

Issue How to get answers for project specification responses or how to get a product enhancement implemented. Product Line Security Expert, EcoStruxure Building Operation Environment Security Expert EcoStruxure Building Operation Cause Unsure who to go to for help with specification replies or how to get a potential product enhancement added to the offer. Resolution Create an idea on The Exchange Community for your specific Offer. The more Likes an idea floated on the Community receives, the more attention it is given by offer management for that associated product line. Even if you do not yourself have an Enhancement Request, help raise the profile of others by Liking theirs Contact your local solution category manager for the Offer as they will be able to point you in the right direction for answers to specification questions and can help escalate enhancement requests to Product Management. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific & India: AsiaPac.EcoStruxureBuilding@schneider-electric.com When providing your feature request make sure to include as much detail as possible about the feature as well as any specifics that might help justify the need for the new feature.

Issue Not all 3rd party manufacturers use the same Modbus addressing. Product Line Andover Continuum, EcoStruxure Building Operation Environment Modbus RTU X Driver bCX1, CX controllers, NC2 Building Operation Enterprise Server Building Operation Automation Server Cause Not all manufacturers use the same Modbus addressing. Resolution Many manufacturers have put their own slant on the "Modbus Standard" for addressing and number formats. The standard only defines 16 bit integer and binary data, but many manufacturers needed to use long integers (or swapped) and floating point numbers. They will transmit them as 2 integers over the protocol, then the receiving system needs to interpret them accordingly. To cope with this, special function codes were added which cover most formats. There are various interpretations by different 3rd party systems on addressing. Some number from 0 and others starting at 1. Some require a 30000 or 40000 offset including in the address, depending on I/O type. What is implemented in the X Driver is that whatever decimal address you enter in the X Driver point is what is sent down the bus. If the other system supplier is asked exactly what address they want sent down the bus, that is what is required in the X Driver point. Sometimes this is not the address that is on their datasheets. Sometimes there may be a need to add or subtract a value of 1, 30000 or 40000. This article was written for Continuum, but is still relevant to EBO Also see Helpful Modbus register Information for further information on Modbus registers.  

Issue SpaceLogic IP device is located in a remote subnet and EcoStruxure BMS server can't discover it. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room Controller (RPC) Building Operation IP-IO Cause BACnet broadcast messages, such as Who is/I am that are used for device discovery, will not be forwarded between the two IP subnets. BACnet Broadcast Management Device (BBMD) is required to allow BACnet to operate through IP routers. Resolution Scenario 1: SpaceLogic BACnet/IP device is located in remote subnet with no EcoStruxure BMS server or BBMD located in same subnet. EcoStruxure BMS server will be configured as BBMD, and SpaceLogic BACnet/IP device will be configured as foreign device and register itself with BBMD (which is the AS-P in our example).    The following video will illustrate how to: Configure SpaceLogic BACnet/IP device located in foreign IP subnet as a foreign device. Configure an EcoStruxure BMS server as BBMD. View foreign device registration on the EcoStruxure BMS Server. Discover and host the SpaceLogic BACnet/IP device.   Scenario 2: SpaceLogic BACnet/IP device is located in remote subnet with a 3rd party device that can be configured as BBMD. In the other subnet, EcoStruxure BMS server will also be configure as BBMD. SpaceLogic IP device will not be configured as foreign device as there is BBMD device in the same subnet. This BBMD will redistribute the essential broadcast messages to it. Once configured, EcoStruxure BMS server will be able to discover and host the SpaceLogic BACnet/IP device and other BACnet deviced located in the remote subnet.   The following video will illustrate how to: Configure SpaceLogic BACnet/IP device located in a remote IP subnet. Configure an EcoStruxure BMS server as BBMD. Configure Broadcast distribution table (BDT) in EBO. Use BACnet browser to check and verify the BDT configuration of a 3rd party BACnet device. Discover and host the SpaceLogic BACnet/IP device and 3rd party BACnet devices located on remote subnet.

Issue Controller is unresponsive and does not respond to a hard reset or power cycle with the battery disconnected..  CPU light remains on constantly. Product Line Andover Continuum Environment InfinityController, b3 Controller NetController II, CX9680 ACX57 bCX Cause Controller stopped functioning after power cycled. Resolution Test controller with a known working PS power supply and/or test the supply voltage is correct If the controller still does not respond to a hard reset then return for repair. See the appropriate manual for reset instructions

Issue The ETL job configuration tool freezes when running the load sources task under the mappings tab. Product Line EcoStruxure Building Operation Environment Extract Transform Load Administration Tool (ETL) Power Manager for SmartStruxure EcoStruxure Web Services (EWS) Enterprise Server Automation Server Cause The ETL default HTTP query size is set to 10 which in some cases can impact the performance of the tool. Resolution Make sure that you read through Energy Expert (Power Manager for SmartStruxure): Best Practices. This article will provide a lot of tips to avoid issues or improve system performance. ETL locks up while loading sources Adjust the HTTP query size to a higher value. This will reduce the number of queries between ETL and the SBO Server. Close ETL. Go to the location where ETL is installed. The default path is C:\Program Files\Schneider Electric\ETL X.X (SBO to PME). Under the Jobs folder there is a project file named "JOB_ETLProjectName.xml". Open this XML file with a text editor. Search for the setting called "ContainerQueryBatchSize". It is set to 10 by default, change it to 100 and save the job. Open the ETL user interface again and try running the Load Sources task. The folder count at the bottom of the screen will increase slower then before because each call is gathering ten times as much data. Note: If the ETL tool locks up again with the query size set to 100, try other values until it is able to complete the task such as 50, 25, etc. ETL takes a very long time to load sources When dealing with very large systems it can take hours for ETL to search through the entire database for all trends. To help reduce the searching time filters can be created to restrict what is exposed to EWS. Go to the System folder EcoStruxure Web Services > EWS Server Configuration. Click on the Filter Hardware Folder tab. Under the "Filter Hardware Folder by Path" section, click on the green addition symbol. In the pop up window, name the path filter and click create. Select the newly created filter path and click on the edit symbol. Enter the path of the folder or item in the database that you want to exclude from EWS. Click Okay. Note: All filter paths created here will NOT be searched by the ETL tool. Save changes. Once the ETL tool has loaded sources and the project has been created, the EWS filters may be removed.

Issue Troubleshooting sending email alarms from a Vista Server Mail error 1 – MAIL client needs to be configured first Mail error 2 – Couldn’t connect to server. Error:0  Mail error 2 – Couldn’t connect to server. Error:10022 Mail error 2 – Couldn’t connect to server. Error:10061 Mail error 3 – Couldn’t send message. Response:550 Mail error 3 – Couldn’t send message. Response:503 Unable to relay Product Line TAC Vista Environment SMTP Server Vista Server Workstation Cause There are many reasons why an emailed alarm from a Vista Server wouldn't reach the desired destination inbox.  This document walks through the most common settings and networking issues and how to overcome them. Resolution Vista can be configured to send out alarms via email.  Typically, following the instructions found in the TAC Vista Technical Manual will result in successful delivery of email alarms.  However, there are some factors that can hinder these email messages.  This document is intended to address a few of the most common troubleshooting techniques to resolve these problems. The Basics The first step to getting Vista alarms to email out is to configure the Server Setup.  Reference Chapter 3.3 Setting Up TAC Vista Server in the TAC Vista Technical Manual.  Enter the address of the Simple Mail Transfer Protocol (SMTP) server as well as the authentication information (if any).  If no SMTP server or login information has been provided, contact an IT professional at the customer’s site to obtain this information. Once Vista Server Setup is correctly configured you must restart the Vista Server. After the Server has been stopped and restarted, set up an Alarm Control Object and an Alarm Receiver – Email.  The steps for this can be found in Chapter 18 Alarm Processing in the TAC Vista Technical Manual. Consider configuring the Alarm Receiver to email a distribution list as opposed to individual email addresses.  Then the distribution list can be edited and maintained by the IT staff without ever having to access Vista. If everything is set up correctly, test the email alarm receiver by forcing an alarm condition.  The alarm should show up in the Vista Alarm Queue as well as at the alarm receiver’s designated inbox.  If the email does not arrive as expected, proceed to the next section of this document titled “Check Vista for Alarms/Errors.” Check Vista for Alarms/Errors If emails are not showing up when expected, the first place to begin the investigation is in Vista Workstation’s Alarm Queue.  There are helpful messages that may appear based on some criteria.  The Alarms will all come from $EE_Mess object under the Vista Server.  Sort the Alarm Queue by Last Change if the alarm just happened, or by Object ID to find the $EE_Mess alarms. Server-$EE_Mess Mail error 1 – MAIL client needs to be configured first Server-$EE_Mess Mail error 2 – Couldn t connect to server. Error:10022 Server-$EE_Mess Mail error 2 – Couldn t connect to server. Error:10061 Figure 1.  Vista Alarm Queue Mail Errors There are three possible errors that can be seen in the Vista Alarm Queue.  They should occur within a few seconds of the alarm if there is an error connecting to the SMTP server.  If the alarms are acknowledged or disabled, they may not show up in the Vista Alarm Queue.  The other place to look for them is under the Vista database folder on the hard drive.  Inside the database structure there is a folder called $log.  Inside this folder should be a file called b0warlog.txt.  Open this file and scroll to the time/date where the alarm occurred.  If an error occurred, the same text that appears in the Alarm Queue will appear in the error log in a slightly different format.  An example: Mon Aug 17 08:16:26 2009 alrdisp >> Error from SMTPSendMail: Mail error 1 – Mail client needs to be configured first Three possible alarm conditions are discussed here: Mail error 1 – MAIL client needs to be configured first This error refers to the TAC Vista Server Setup.  Refer back to Chapter 3.3 Setting Up TAC Vista Server in the TAC Vista Technical Manual.  If the server is setup correctly, be sure that the server has been restarted since the last change.  Changes in Server Setup will not take effect until the next time server is run. Mail error 2 – Couldn’t connect to server.  Error:0 Unknown cause. Mail error 2 – Couldn’t connect to server.  Error:10022 This error means that the SMTP server is unreachable.  If using a DNS name for the SMTP server, double check the spelling.  If everything looks correct, move to section of this document titled “Check SMTP Server Connectivity” and follow the steps described there. Mail error 2 – Couldn’t connect to server.  Error:10061 This error means that the SMTP server has been reached, but Vista was not allowed access to the server.  Double check the authentication username and password.  Re-enter the password to ensure it is correct (only dots are shown for privacy).  There are three different authentication modes to choose from: CRAM MD5 – (Safest) Password is coded with Message Digest 5. AUTH LOGIN – (Standard) Password coded with base64 method. LOGIN PLAIN – Password is sent uncoded. If the correct authentication mode has not been provided, it may require trying all three until the mail error clears.  If all three result in an error, contact an IT professional to be provided with a valid username and password.  Use the section of this document titled “Contacting an IT Professional” for a template to request this information. Mail error 3 – Couldn’t send message.  Response:550 Unknown user Unknown cause. Mail error 3 – Couldn’t send message.  Response:503 Must have sender and recipient first. Unknown cause.  If no errors occur in the Vista Alarm Queue or in the Vista alarm log text document, refer to the section of this document titled “Vista Indicates No Errors” for more troubleshooting techniques. For troubleshooting unknown errors, read Troubleshooting sending emails using WireShark. Unable to relay If an error "Unable to relay" is returned, this is most likely because authentication is not sent to the SMTP server. Go to Vista Server settings At the email tab set proper authentication (Vista Technical Manual Chapter 3.3 explain this more in detail) You may need to consult with the IT department on site Check SMTP Server Connectivity In order to use an SMTP server, a connection must be established.  In this example, the provided SMTP server is “smtp.ACME.com.”  Pinging is the lowest level of internet communication.  A successful ping will not guarantee communication with an IP device, but a failed ping will guarantee no communication.  Open a new DOS command prompt (Start > Programs > Accessories > Command Prompt).  Ping the SMTP server. C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Figure 2.  Failed Ping Example In Figure 2, a request to ping the SMTP server has failed.  Check that the computer where Vista Server resides has internet connectivity (Start > Settings > Network Connections).  Make sure the connection status is Connected, navigate to an internet website, or ping a known IP address.  If those fail, check the computer’s IP settings.  Figure 3.  TCP/IP Properties - Obtain IP Automatically If the computer is set to obtain an IP address automatically make sure that an IP address has been assigned.  Figure 4.  Local Area Connection Status If no IP address has been defined, then the DHCP server is not available and the computer is not connected a network.  Check the physical connections and contact an IT professional to determine why the DHCP server is not assigning the PC an IP address. If the TCP/IP properties are configured to use a static IP address (which is common in applications where WebStation or ScreenMate are employed), then the DNS server address must also be defined if a DNS SMTP server is used.  Figure 5.  TCP/IP Properties - Static IP If DNS is causing problems, it is possible to bypass this by using the IP address for the SMTP server as opposed to the DNS name. Look back to Figure 2 to obtain the SMTP server’s resolved IP address.  In this example, the IP is 10.10.10.10.  Figure 6.  Using IP Address of SMTP Server When everything is set correctly, try to ping the SMTP server again.  This time, it should go through successfully, which is an indication that most of the basic settings are correct – but should not be viewed as indication that email messages will successfully be delivered by the SMTP server. C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms Figure 7.  Successful Ping Example In Figure 7, the ping has returned four successful results.  This will confirm that cables are connected properly, IP addresses are set, and any necessary gateway routers are communicating.  It does not indicate ultimate success in connecting to the SMTP server. To check connectivity with the SMTP server, use a simple telnet command on port 25 (or the specified port) from a command prompt. C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com... Figure 8.  Telnet command. If there is an error connecting, you will see this: C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com...Could not open connection to the host, on port 25: Connect failed Figure 9.  Failed Telnet Command. If the connection succeeds, the command prompt will clear and show a new line beginning with 220.  Type the word “helo” and press enter.  The SMTP server should again respond but this time with a line starting with 250.  Exit the telnet session by typing “quit” and pressing enter. 220 smtp.ACME.com ESMTP helo 250 smtp.ACME.com quit 221 smtp.ACME.com Connection to the host lost. C:\> Figure 10.  Successful Telnet Session. If a connection can successfully be established through telnet, then the ports are open and SMTP messages should be successfully received from the Vista Server.  That does not guarantee they will be relayed by the SMTP server, so if emails are still not being delivered, continue troubleshooting with the next section titled “Vista Indicates No Errors.” Command not found If a telnet attempt results in the command prompt error "command not found" it is most likely because telnet is not enabled. In newer operating systems (Windows Vista/Windows 7) this feature is not enabled by default. To enable telnet: Go to Start > Control Panel > Programs and Features On the left side, select Turn Windows features on or off Scroll down to Telnet Client and check the box (see Figure 8 below) Figure 11. Enable Telnet Client. Vista Indicates No Errors If no errors show up in either the Vista Alarm Queue or the $log folder, then Vista has successfully contacted a valid SMTP server.  Review Chapter 18 Alarm Processing in the TAC Vista Technical Manual.  Make sure that the alarm is using the correct Alarm Handler that is assigned the correct Alarm Receiver that has the correct valid email addresses defined. If the alarms are set up correctly, the focus should now shift to troubleshooting the SMTP server itself.  Assistance from an IT professional will be helpful at this stage.  Things to check include: Check the incoming/outgoing messages from the SMTP server.  See if the messages from Vista are arriving but not being sent out.  Many companies will set up an “allowed” list that will only pass emails from recognized IP addresses, and all else is filtered as spam.  Make sure the Vista Server’s IP address is listed on the acceptable list. Ask what port the SMTP communication is using.  Port 25 is typically used for SMTP communication, but some companies will change this for security purposes.  Request that port 25 be opened for SMTP communication from the Vista Server.  If this is not an option, the port can be changed manually using registry settings.  See the section of this document titled “Changing the default SMTP Port” for instructions. Look at the selected Text encoding in the Vista Server Setup.  Unicode (UTF-8) is the most common in America and Europe.  If encoding is set to UTF-7, some SMTP servers will filter the messages out as spam. Some companies will block all POP messages on the network.  This will disable the ability to use external SMTP servers.  Make sure POP messages are allowed or that the SMTP server is internal to the network. If you are trying to use an SMTP server of a different ISP than the one Vista Server is connected to, this will most likely be blocked by the SMTP server. This is known as mail relaying – something spammers can and will abuse. Changing the Default SMTP Port Vista defaults to using Port 25 for all SMTP communication.  This is the standard port for SMTP and is typically used by SMTP servers.  However, because it is so well known as the SMTP port, some companies prefer to change this as a security measure.  Request that port 25 be made available to the Vista Server.  Unfortunately, sometimes this is just not possible because of security procedures.  If a different port is required, it is possible to manually change the port by navigating through registry keys. Open up the Registry Editor on the Vista Server PC (Start > Run… > regedit).  Navigate to: My Computer > HKEY_LOCAL_MACHINE > SOFTWARE > TAC AB > TAC Vista > 5.1.2 > SMTP Depending on the version of Vista, the path may change slightly.  If a 64-bit operating system is being used, the path will be: My Computer > HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node > TAC AB > TAC Vista > 5.1.5 > SMTP Navigate until the SMTP folder is located.  Inside the SMTP folder, the SMTP settings that were set with Vista Server Setup can be viewed.  There is also an additional registry key defining the port.  Figure 12.  SMTP Registry Settings If there is no registry key for Port, create one.  Right click in the key view window, but not on an existing key.  Select New > DWORD Value.  Name the new value “Port.” Double-click the Port registry key to edit.  Radio buttons convert the value from hexadecimal to decimal.  Ports are typically described in decimal values.  Switch to decimal, enter the required port number, and click OK. Figure 13.  Editing Port Registry Key Verify that the value had changed in the registry.  Vista should now be sending out SMTP communication on the required port. Contacting an IT Professional If you need help contacting the customer’s IT department to gather and share the correct data, use the document attached in Appendix A:  IT Request for Information.  A completed example is shown in Appendix B:  Sample IT Request for Information. Disclaimer The information contained in this document is subject to change without notice.  It is also subject to change with versions of TAC Vista.  If further assistance is required, please Call or email Schneider Electric Product Support Appendix A: IT Request for Information The TAC Vista building automation system installed on your site has the capability to email facilities personnel in certain situations.  Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system.   TAC Vista uses standard Simple Mail Transfer Protocol (SMTP) for these messages.  An SMTP server must be provided in order for these messages to be delivered.  The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP):   Authentication method (choose one): None CRAM MD5 AUTH LOGIN LOGIN PLAIN Username (if applicable):   Password (if applicable):   Text encoding (if filtered):   To distribution list (if any):   Required TCP Port:   Information for IT from the Installation Contractor SMTP messages will be sent with the following details: (This can be found in TAC Vista Server Setup): To distribution list (or email addresses):   From name:   From email address:   From IP address:   Desired TCP port: 25 Appendix B:  Sample IT Request for Information The TAC Vista building automation system installed on your site has the capability to email facilities personnel in certain situations.  Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system.   TAC Vista uses standard Simple Mail Transfer Protocol (SMTP) for these messages.  An SMTP server must be provided in order for these messages to be delivered.  The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP): smtp.ACME.com Authentication method (choose one): None CRAM MD5 AUTH LOGIN LOGIN PLAIN Username (if applicable): emailuser Password (if applicable): password123 Text encoding (if filtered): UTF-8 To distribution list (if any): facilities_staff@thebuilding.com Required TCP Port: 25 Information for IT from the Installation Contractor SMTP messages will be sent with the following details: (This can be found in TAC Vista Server Setup): To distribution list (or email addresses): facilities_staff@thebuilding.com From name: Vista Server From email address: vista @server.com From IP address: 10.10.10.20 Desired TCP port: 25

Issue A combined keypad reader works with a valid card swipe, but the keypad does not work. The keypad does not allow a valid pin to be entered to engage the door output even though the door, area and personnel objects are setup correctly. This issue could also happen with a keypad only, without the combination reader. Product Line Andover Continuum Environment Keypad Keypad/Reader Combination Cause A keypad or keypad/reader combination can be ordered with the keypad output set to work in a number of different modes.  Continuum requires the output mode to be ordered as follows: Buffer one key add compliment 8 bit message (Dorado) This is also known as 8 bit burst A keypad that has a different configuration than this will not work with Continuum   Resolution 1. Order a keypad or keypad/reader combination with the 8 bit burst output mode set 2. Contact the keypad manufacturer's technical support (Eg. HID), to see if they will send a Configuration Card that allows the output mode to be changed retrospectively in the field.

Issue When swiping / presenting a card to a Wiegand card reader in Continuum it does not open the door..  When opening a Listview of Events the log shows "Card Bad Parity" or it reads an incorrect card number using Custom Wiegand. Product Line Andover Continuum Environment CyberStation all versions, with any of the Access Controllers - ACX700, ACX780, ACX57xx, NetControllers with any of the AC1 module range. Cause This fault is caused by incorrect wiring to the reader or choice of a 3rd party reader that is not compatible with Continuum. Resolution When wiring between a controller and a Wiegand card reader, all wires must be connected straight through to the corresponding terminal. Data1 to Data1 Data0 to Data0, Gnd to Gnd ..............etc. See relevant controller installation guide for further details on reader wiring and cable types. On HID readers be sure to wire between the two Data 1 terminals and the two Data 0 terminals. Do not refer to the Clock and Data legend that is also on the controllers and many readers, as this is only used for ABA data connections. When using a separate Power supply for the reader, the 0V (Ground) terminal must still be connected back to the controller GND terminal to ensure both devices are working from a common ground potential. When testing out cards and readers always use a Listview showing a relevant Event log, as this will provide more information than the event view from the Door editor itself. To assist with troubleshooting data reads by the controller especially when using Custom Wiegand for non standard Continuum formats: Select only Custom Wiegand in the Door configuration. Rename the "AccessFormat" array if one has been created. Present a card to the reader. Check the Listview for Events as this will show the raw binary data string the controller is receiving. Compare raw binary data against the expected data from the reader used.

Issue Installation and configuration for SE8600 heat pump application Product Line EcoStruxure Building Expert Environment  SE8600 Cause Installation and configuration errors for heat pump application Resolution SE8600 terminal identification In typical HP application, you shall connect to following terminals below: Y2 = Compressor 2 | Y1 = Compressor 1 | G = Fan | RC = 24 Vac positive | C = Common << 24Vac common >> W1 = Auxiliary Heating stage | W2 = O/B = First stage heating | UI22 = Supply temperature sensor | UI23 = Outdoor temperature sensor Depend on specification document, the application may require addition controls and connections. Application shall be set to: HP for heat pump From winter to summer season, high BP is the outdoor temperature value ABOVE which the system transfer from auxiliary heat <> and maintain heating setpoint with the heat pump << default 32°C >>. Temperature shall be set per system geographical localization. From summer to winter season, low BP is the outdoor temperature value BELOW which the system transfer from heat pump <> and maintain heating setpoint with the auxiliary heat << default -24.5°C >>. Temperature shall be set per system geographical localization. * Outdoor temperature sensor shall be installed   Heat pump reversing valve operation O: energize valve in cooling operation << default position >> B: energize valve in heating operation Heat pump system

Issue Drayton Theta ll ES4 Optimiser Controller requires replacement. Product Line Field Devices, Satchwell Sigma Environment Stand alone discreet Drayton Optimiser Controller Theta ll ES4 Cause Obsolescence of Drayton Theta ll ES4 Optimiser Controller. Resolution Please note that the Satchwell SVT controller is no longer available, and that the only possible replacement is the DC1400. Please refer to What is the replacement for the SVT controller range? for more details.  Replace Drayton Theta ll ES4 Optimiser Controller with Satchwell SVT Optimiser Controller.  N.B.  Two models of the Satchwell SVT Optimiser Controller are available :-  SVT 4201 with Analogue Timeswitch  SVT 4251 with Digital Timeswitch, Details of the Satchwell SVT Optimiser Controllers may be viewed here. It should also be noted that the associated Drayton Theta ll ES4 Optimiser Controller Sensors are obsolete.  These Sensors are not compatible with the Satchwell SVT Optimiser Controllers and must therefore be replaced.  Unlike the Drayton Theta ll ES4 Optimiser Controller, which requires the installation of both an Outside Air Temperature Sensor and an Inside Air Temperature Sensor, the Satchwell SVT Optimiser Controllers require the installation of a Inside Air Temperature Sensor only.  A STR 614 Inside Air Temperature Sensor is packed with the Satchwell SVT Optimiser Controller when supplied new :-   Details of the STR 614 Room Temperature Sensor may be viewed here.

Issue Security Expert database size increasing rapidly and getting large. SecurityExpert Database size From the screen capture below, it can be seen that the Security Expert transaction log file SecurityExpert.ldf has increased to a large size. SecurityExpert database log file Product Line EcoStruxure Security Expert Environment Security Expert Microsoft SQL Server Cause The Recovery model of the Security Expert database is set to FULL and the database has not been maintained. When using the Full recovery model, regular backups of the transaction log should be performed to prevent the transaction log file size from growing out of proportion to the database size.   New user databases are created with the same recovery model as the model database. The default recovery model for the model database depends on the edition of SQL Server you have installed. Editions targeted at test and development environments (SQL Server Express) set the recovery model of the model database to SIMPLE. Other editions set the recovery model of the model database to FULL. Resolution For Security Expert, it is recommended that the Recovery model be set to the default of SIMPLE.   You can reduce the size of the logs and also prevent them from getting too large again by changing the recovery model of the database from FULL to SIMPLE. The databases are then shrunk to free up drive space.   Refer to the following steps: Take a backup of both the SecurityExpert and SecurityExpertEvents databases and store them in a safe location Change the Recovery Model of the SecurityExpert database from Full to Simple in SQL Server Management Studio. To do this, right click on the SecurityExpert database and go to its properties. Select 'Options'. Change the Recovery Model setting to Simple. Recovery Model Simple Right click on the SecurityExpert database and select Tasks > Shrink > Files Shrink In the Shrink File - Security Expert window, change the File type to Log. Shrink File Type Log Click OK Repeat steps 2-5 for the SecurityExpertEvents database   It is recommended that regular scheduled backups be configured when using the SIMPLE recovery model. In SIMPLE recovery mode, changes since the most recent backup are unprotected.

Issue Installing Echelon Network Interfaces on Windows 7 Operating Systems Environment Microsoft Operating Systems: Microsoft Windows 7 (64-bit and 32-bit) Windows Server 2008 R2 (64-bit), Windows Vista (32-bit) Windows XP (32-bit) Windows Server 2003 (32-bit) Echelon Network Interfaces: i.LON 10 Ethernet Adapter i.LON 100 Internet Server i.LON 600 Internet Server PCLTA-21 PCI Network Interfaces PCLTA-20 PCI Network Interfaces PCLTA-10 ISA LonTalk Adapter PCC-10 PC Card Network Interface SLTA-10 Serial Network Interface (requires separate driver) SmartServer and SmartServer 2.0 U10 USB Network Interfaces U20 USB Network Interfaces Cause Installing Echelon Network Interfaces on computers with newer Windows Operating Systems. OpenLDV 4.0 Resolution Install and use Echelon OpenLDV network interface driver version 4.0 and above. You can download OpenLDV 4.0 from the Echelon website here Echelon Network Interface(s) manuals can be found here. Echelon has released OpenLDV 5.0. It can be downloaded from here. 

Issue Unable to successfully use Gmail SMTP server to send out alarms via email from I/A Series G3.  Various errors can be seen in the console output. Some of the errors are indicated below but they may not be limited to these. Error: BOutgoingAccount could not dequeue persistent email: 550 The address is not valid java.lang.Exception: Valid CryptoService not found Environment Enterprise Network Server / Enterprise Network Controller I/A Series G3 version 3.5 and above I/A Series G3 maintenance builds version 3.4.55 and above Cause Improper configuration of the EmailService's OutgoingAccount and missing CryptoService in the station. Resolution Procedure and properties settings required when using the Gmail SMTP Server: Add the EmailService and CryptoService to the station's Services folder. If emails are to be sent from an ENC, ensure that the email and crypto modules (and their dependencies) are installed into the ENC. Add the OutgoingAccount to the EmailService. In the OutgoingAccount properties, configure the properties indicated below. Leave other properties as their default settings. Hostname: smtp.gmail.com Port: 465 (this is the TCP port SMTP over SSL uses) Account: example@gmail.com Password: Your Gmail account password Enabled: true Use Ssl: true (Gmail requires SSL) Transport: SMTP Use Authentication: true (Gmail requires authentication when sending out emails) You can test the functionality by right-clicking on the EmailService and selecting 'Actions' > 'Send' to send out an email. If you are still having an issue with authentication, it may need to allow less secure apps to access your Gmail account. Refer to https://support.google.com/accounts/answer/6010255?hl=en for details.  Notes: CryptoService enables the SSL feature in the G3 station. The crypto module is included in the installation of I/A Series G3 version 3.6 but it was not included in earlier versions. You can download the crypto modules for earlier versions of G3 (crypto 3.4.64 / crypto 3.5.34) from The Exchange Download Center. Ensure that the station is licensed for crypto. You can look into your license file to check. Below is an example taken from a demo license. feature expiration="2012-03-31" name="crypto" parts="ENS-DEMO" ssl="true"

Issue What is the part number for a flying lead temp sensor for Continuum? Environment Measuring air temperature in fan coil applications or exhaust ducts Cause On site or inability to find the HVAC Sensor Catalogue Resolution STD550 The 550 is intended for measuring air temperature in fan coil applications or exhaust ducts. The sensor, which are made of stainless steel, is delivered with a 2m (6.5 ft.) cable, PVC sheathed overall. Mounting details such as screw and clamp are included with the product. Description Duct Temperature Sensor STD550 Order Code 5123058400 Part Number STD550 For Continuum Systems   HVAC Sensor Catalog in pdf format