Building Automation Knowledge Base

Issue The FlexNet console shows the following error Vendor daemon down: taclic No such feature or vendor does not exist: taclic Product Line EcoStruxure Building Operation Environment License Server FlexNet TACLIC Cause The taclic vendor daemon which serves the SmartStruxure licenses is down. This indicates that the vendor daemon either does not exist, or that another application using the same vendor daemon executable is present on the PC. You can run one or more FlexNet license servers with different vendor daemons, but a given vendor daemon can only be run once at a time on the PC. The SmartStruxure Building Operation vendor daemon is called taclic.exe. This can be seen as a process in the Windows Task Manager. Resolution 1. Make the SmartStruxure license server is properly installed 2. Follow SmartStruxure license and TAC Vista license on the same PC if both TAC Vista and SmartStruxure Building Operation is installed on the same PC.

Issue When a TGML graphic is opened from Webstation red crosses is shown on the whole graphic or sometimes over certain components. After a few seconds the red crosses disappear. Product Line EcoStruxure Building Operation Environment Building Operation Webstation version 2.x and 3.0.x Cause The red crosses only appear when values from field bus devices are displayed in in the TGML graphic, and only in Webstation version 2.x and 3.0.x. When the graphic is opened from Workstation no red crosses are shown in the graphic. Resolution This issue is fixed in EBO version 3.1.1

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 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 Does the Niagara R2 Modbus driver support a 6-digit address format? Product Line TAC IA Series Environment Niagara R2 Modbus driver Cause Modbus 6 digit addressing is not supported when using modbus format in the driver. Resolution The six-digit address format and the five-digit format are just two different notations for the same thing - there is no difference in the protocol. For example, the first one thousand holding registers are normally represented as: (modbus) 40001 to 49999 -or- (decimal) 0 to 9998 -or- (hex) 0 to 270E When using modbus format in the driver, the left most digit, '4' in this example, is part of a convention that indicates the 'type' of point and, when using that convention, the point type does not have to be specified.  For example, for modbus point 40001 the '4' indicates that it is a holding register. But there are actually 64000 holding registers available and, using the common 5-digit modbus notation, it is not possible to specify more than 9999 of them. The six digit convention just moves this 'type' digit one space to the left. In this six-digit notation, the first one thousand holding registers would be 400001 to 409999. This 6-digit convention for 'modbus' formatted addressing is not supported but it is still possible to use decimal or hex notation to specify these addresses with Niagara R2. When 'modbus' formatted addresses are used, the driver subtracts 1 from the entered address, since modbus uses base 1 formatting and decimal uses base 0.  When using decimal or hex, the leading digit is dropped and subtract one from the register value and optionally convert to hex and use that as the point address. For example, to read data from register address = 422202 Drop the leading character = 22202 Subtract 1 = Decimal address 22201 or hex address 56B9

Issue If the STR 350 plug-in is missing, then the STR 350/351 setup needs to be performed manually in NL220, LonMaker, TAC Vista Workstation, or TAC Menta. Product Line TAC Vista Environment TAC Vista 5.1.4, TAC Vista 5.1.5 Windows 7, Server 2008 Cause Not all plug-ins in the TAC ToolPack can run on Windows 7 or Windows 2008. Read details in TAC ToolPack plug-ins are not showing up. Resolution If the STR 350 plug-in is missing, then the STR 350/351 setup needs to be performed manually in NL220, LonMaker, TAC Vista Workstation, or TAC Menta. NL220 STR 350/351 setup steps are shown below: Use the STR 350 device template to create a new node on the channel. Note: the device template is located at C:\LonWorks\import\TAC\IO Modules (Default location) Double click on the STR 350/351 device and make necessary changes to any signal under “NVs” tab. TAC Workstation STR 350/351 setup steps are shown below: Expand the tree structure in the left panel. Select the desired signal to change in the right panel. If a STR 350/351 is connected to a programmable controller (Xenta 280/300/400), then the STR 350/351 can be added in the Menta file similar to an IO module. Setup steps are shown below: Under “Options/Device Specification” select “Add STR Module…" Under “Type” Select “STR350/351” and Under “Bit(s)”, choose the desired bit(s). Note: hover over each bit, there is a short description about the selected bit. If a STR 350/351 is connected to a Xenta Server (Xenta 7XX), then the STR 350/351 can be added in the Xbuilder project similar to an IO module. Setup steps are shown below: In Network panel,  under “LON", right click and select “Add IO Module->STR35X". Right click on the STR35X model just added, and select "Configure". A configuration pop up window will be displayed.  Make any desired changes. Note: Neuron ID can be manually typed in the Xbuilder or get from service pin in the Workstation. If choose to service pin, need to create and commission a LNS network in Workstation. Save and download the project. Below is a table of each bit in nciOption1 and nciOption2 and its brief description. nciOption1: Bit 0, 1: Fan type 00: No fan (Default) 10: On/Off fan 01: 2 speed fan 11: 3 speed fan Bit 2: Fan auto state 0: Not allowed (Default) 1: Allowed Bit 3: Fan off state 0: Not allowed (Default) 1: Allowed Bit 4: Fan speed 1 0: Not allowed (Default) 1: Allowed (On/Off fan type needs to be activated) Bit 5: Fan speed 2 0: Not allowed (Default) 1: Allowed (2 speed fan type needs to be activated) Bit 6: Fan speed 3 0: Not allowed (Default) 1: Allowed (3 speed fan type needs to be activated) Bit 7, 8 ,9: Not used   Bit 10: Temperature presentation 0: °C (Default) 1: °F Bit 11: Temp. normally displayed 0: Setpoint temperature (Default) 1: Room temperature Bit 12: Setpoint temp. presentation 0: Absolute temperature (Default) 1: Offset temperature Bit 13: Bypass button usage 0: Bypass (Default) 1: On/Off Bit 14: Not used   Bit 15: Supported protocols 0: Standard LonTalk protocol only 1: Standard LonTalk protocol and TAC proprietary protocol (Default) nciOption2: Bit 0, 1: Sunblind - Switch 1 00: On/Off (Default) 10: Up/Down 01: On/Off/Up/Down 11: Not used Bit 2, 3: Sunblind - Switch 2 00: On/Off (Default) 10: Up/Down 01: On/Off/Up/Down 11: Not used Bit 4: Light - Switch 1 0: Disable (Default) 1: Enable Bit 5: Light - Switch 2 0: Disable (Default) 1: Enable Bit 6, 7, 8: Local sensor 000: None (Default) 100: CO 2 010: RH 001: Occupancy Bit 9: CO 2 /RH value 0: Hidden (Default) 1: Display Bit 10-15: Not used  

Issue The ACCDataServices application is crashing on start up of CyberStation Product Line Andover Continuum Environment CyberStation Windows XP Cause Windows permissions issue Windows Firewall Configuration  Resolution Make sure when installing CyberStation the user has Local Admin rights to the computer Make sure Windows Firewall is turned off during the install Make sure all VirusScan software is turned off during the install. Check the event notifications and verify that none of them are set for the recipients to have pager, log, forward or any unused option which can create unnecessary traffic when using enhanced alarm delivery. To check if you are using enhanced alarm delivery Database Initialization > Server (or Stand Alone) > see check box for enhanced alarm delivery An example of possible unnecessary check box recipient options:  Check that each action in the event notification i.e. 'Display Graphic' has a corresponding object for the point alarming. If no object is selected it may cause accdataservices errors. Run acctrace and/or the Continuum error  log and wireshark to determine if there are errors. Cleaning up these issues can relieve the system and these errors. The Windows application/system logs and system.nfo/Belarc advisor can help gather info about the PC. See Top 10 Steps for Troubleshooting Cyberstation and webClient issues. If there is a 3rd party bacnet device, disable or unplug the device to see if the issue is related to the flooding of traffic into Continuum Liebert Sitelink- If you are on 1.93 and below, the Sitelink trendlogs could affect Continuum. Upgrade to 1.94 and disable trendlogs. Engineering is working on a hotfix for this issue. (Not released as of 11/29/12) Stand Alone Windows 7 system - A stand alone system can easily tax resources when extended logging, graphics, SQL Server, Cyber, etc. are all running on the same system. Eliminate any errors in the error log and disable certain functions to see if this helps. Consider a server class PC depending on what the system functions that are required by the site. Install Cyberstation 1.94 SP1 and related firmware updates as there are many fixes to address accdataservices.exe crashes (See Continuum 1.94 SP1 Service Pack to address accdataserices.exe crashes and other issues) Do not mix 1.94 and 1.94 SP1 Cyberstations on the same db, this could cause accdataservices crashes

Issue How to reset an ACX 57xx model controller Product Line Andover Continuum Environment ACX 57xx Cause While upgrading/downgrading the controller firmware, communications were lost and the controller is not communicating afterwards. Resolution Consult How to reset a ACX 57xx controller to reset the controller and then re-commission.

Issue Often data is required to be exported out from the Continuum system for record keeping or for further analysis, what keywords can be used to help with this? Environment Cyberstation Plain English programs - all versions. Microsoft Excel Product Line Andover Continuum Cause Specific help is available in the product for specific keywords but how can these be put together to export data to .CSV format. Resolution As we do not advocate 3rd party system trying to directly extract data from the Continuum database, you should create a Plain English program in a Workstation that can export logged data directly from the controllers out to a .CSV or .TXT file.   Keywords to use for this purpose are: OpenFile WriteFile CloseFile   Details of the above Keywords are available in the Cyberstation internal help pages.   The attached example dump file could be run on a daily basis to extract temperature logs from a controller and save them to files with a date stamped naming convention.   Click to download the example WriteFile dump file. 

Issue As of Continuum version 1.82 the standalone Database Engine is SQL Express, which offers inbuilt backup and restore functionality via Microsoft SQL Server Management Studio (SSMS). What is the process for backing up and restoring Databases prior to 1.82? Product Line Andover Continuum Environment Standalone CyberStation v1.81 and below. Backup/Restore  Cause As of Continuum version 1.82 the standalone Database Engine is SQL Express. Prior to that it was MSDE. What is the procedure to backup/restore an MSDE database? Resolution Visit the Download Center for MSDE Database Utilities:  MSDE Database Utilities Move SQL DB to a different hard drive

Issue Locating the IC3-Modbus documentation Environment Sigma IC3 Modbus Documentation Cause Unable to locate documentation. Resolution To download the IC3-Modbus Gateway.txt file click HERE. To download the IC3 configuration guide click HERE. To download the IC3 data sheet click HERE.

Issue CSC5252 and CSC5352 Climatronic Compensator Controller will not display Room Temperature.  Environment Satchwell CSC5252  CSC5352  Climatronic Compensator Controller  Room Temperature.  Cause CSC5252 and CSC5352 Climatronic Compensator Controller may not display Room Temperature for the following reasons :- 1.  No Room Temperature Sensor installed. 2.  Room Temperature Sensor installed but ROOM INFLUENCE MODE default value in CSC Controller has not been amended.. .  Resolution CSC5252 and CSC5352 Climatronic Compensator Controller may be set to display Room Temperature as follows:- 1.  Ensure Room Temperature Sensor is installed and connected to CSC Controller Room Temperature Sensor Input terminals. 2.  Ensure ROOM INFLUENCE MODE (INF) setting in CSC Controller Fine Tune Mode is set to value = 1 N.B. Sensor connection details and the means of entering and exiting the CSC Controller Fine Tune Mode both appear in the Climatronic CSC5352 and CSC5252 Compensator User Guide, a copy of which may be viewed here.

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

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 Under rare circumstances, resetting your Manager to its factory defaults may be necessary.  For example, if you have forgotten your Manager's IP address, or if you are experiencing login problems.  Environment SmartStruxure Lite Web Browser SmartStruxure Lite MPM Cause All SmartStruxure Lite™ Managers are equipped with a bootloader, accessible via a special IP address that lets you access several Manager firmware functions, among them, a factory reset.  Resolution WARNING: Restoring your Manager to factory settings should only be performed as a last resort; doing so will erase all its objects and devices, requiring you to reconfigure your Manager from scratch. Accessing the Bootloader As its name suggests, you access the bootloader at boot time, i.e., when you power up your Manager. To perform a factory reset: 1. Disconnect electrical power from your Manager by unplugging its power connector or unplugging its power supply from the AC outlet. 2. Ensure that your computer's TCP/IP settings are on the same subnet as the bootloader IP address:10.50.80.X.     IMPORTANT: Upon restarting your Manager, you will have only a brief interval–approximately 5 seconds–during which you will be able to access the bootloader. As such, we recommend that you perform the following steps 3.  Open your browser and type the following IP address into the address bar, but do not click the browser's Go icon or press any  key on your keyboard: 10.50.80.2 4. Reconnect your Manager's electrical power. 5. Within approximately 5 seconds, click your browser's Go icon or press the key to navigate to the  bootloader's IP address.  The bootloader screen displays.    6. In the Restore factory defaults area, click Submit. The Manager begins restoring its settings to the factory defaults. When completed, a success message displays.  7. Restart your Manager by clicking the Submit button in the Restart system area. 8. You may now log in to the Manager using its restored IP address: 10.50.80.3. If you cannot connect successfully to the bootloader using the above steps, chances are you are not navigating to the bootloader's URL within the defined 5-second window.       As an aid, some users may find it useful to do the following:      Open a command window and type the following: ping 10.50.80.2     As soon as you see a ping reply, return to your browser window and press the key to navigate to the address previously entered into the address bar.   Restoring your Manager to Factory Settings download as PDF.

Issue When a MicroNet 100 series LON controller is upgraded to a MicroNet 50 series LON controller, reference in/out objects and the bindings to the LON SNVT bindings are lost. Product Line Satchwell MicroNet Environment VisiSat Software version 2.1 Builds 137, 148, 148 SP1, 185 and 196. Cause The upgrade process removes various items/objects from the original scheme. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- The upgrade process removes various items/objects from the original bubbleland scheme. See MicroNet 100 to 50 series upgrade precautions.pdf to view more detailed information.

Issue Is there a way to specify the priority that the system should use by default when writing to the value of BACnet objects in EcoStruxure Building Operation (EBO)? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation WorkStation BACnet Cause It may be necessary, especially in a legacy b3 environment, or third party BACnet network integration, to write by default to a priority other than 16 in the Command Priority stack. Resolution The default Command Priorities within a system used when writing to BACnet objects are governed by the Interface Manager in the ES.  These settings are then inherited to all AS. Command Priority 16 is used by default writing to the Value Property of a BACnet Object Command Priority 8 (Manual Operator) is used by default when Forcing the Value BACnet Object in EBO. Both defaults can be changed but care should but be taken here as any changes will ripple through the entire system and may have unforeseen consequences. Script programs created in a b3 will still use Command Priority 10 by default. It is still possible to write at any other priority in EBO by Binding directly to the desired command priority.

Issue What actuators are available? Environment VG210R VG310R Actuators Cause Choice of available actuators. Resolution Suitable Actuators for the VG210R and VG310R ball valves ranges are; Direct fit. MG600C, MG600C SR   With AV-823 Long Stem adaptor. M400 M800 M1500 MG900 SR To view the following data sheets, please select the data sheet required. VG210R,  VG310R, MG600C,  MG600C Installation,  MG600C SR,  MG600C SR Installation and Manual Override instructions

Issue A BACnet devices can contain 1000's of objects, performing an upload on these devices can take upwards of 30 minutes to complete when only a few objects are required for integration. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Cause Uploading all objects in a controller can take a lot of time and is often not required. Resolution From version 2.0 Open the device discovery view / BACnet - then Discover All. Once the Device is hosted, click on the device (in the Device Discovery window) and open the right-hand Object pane. Drag/drop the required Object into the hosted BACnet device Application folder. Alternatively, the Hardware folder can be used, this was the best method for some earlier versions Perform the BACnet discovery, then view the Hardware folder at /ServerName/System/Hardware/BACnet devices. Navigate to the required Device/Object, then Drag and drop the Device and Object as above.

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 What image formats are supported in a TGML graphic? Product Line EcoStruxure Building Operation Environment EcoStruxure ES, AS Vista Graphic Editor Cause Clarification of supported graphic formats required. Resolution When inserting a picture in a TGML graphic you can select the image file from the following file types: Bitmap, GIF, ICO, JPEG, Metafiles, PNG, TIFF