Building Automation Knowledge Base

Issue How to read the Modbus device's register and, via Menta in a Xenta 700, convert the value in to the 4 bytes required to bind these values to the SNVT_preset member Value. Environment Vista 5.1.X Communication with a Modbus device. Xenta 700 5.1.X (Menta) Cause SNVT_preset includes a member value[4] which is an unsigned long containing 4 bytes. Modbus contains only 16 bit registers. The SNVT member Value is shown as 4 separate bytes in Vista. Resolution Click here to download an Xbuilder project containing the correct Menta file to convert from a Modbus register to the 4 bytes that the member Value contains. Instructions: Download the zip file and extract the Xbuilder project. Open the Xbuilder project and change the IP address to your device's IP address. Download the project to the Xenta server and save to Vista.

Issue Satchwell VZF 2-Port Flanged Valve Body requires replacement. Environment Satchwell 2-Port Plug and Seat Flanged Valve Body VZF1727                                VZF 1727 VZF1777                                VZF 1777 VZF1852                                VZF 1852 VZF1902                                VZF 1902 VZF1954                                VZF 1954 Cause Obsolescence of Satchwell VZF 2-Port Flanged Valve Body Resolution A number of alternative S-E 2-Port Flanged Valve Bodies are available to replace existing Satchwell VZF 2-Port Flanged Valve Bodies. Suggestion 1 Replace Satchwell VZF 2-Port Flanged Valve Body with S-E VG221F 2-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on VZF 2-Port Flanged Valve Body may be retained for installation on replacement S-E 2-Port Flanged Valve Body.  In such instances a S-E L9TVG Linkage Kit will additionally be required.  Alternatively an Actuator from the S-E range of Actuators may be installed on the VG221F 2-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. Suggestion 2 Replace Satchwell VZF 2-Port Flanged Valve Body with S-E V222 2-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on VZF 2-Port Flanged Valve Body may be retained for installation on replacement S-E 2-Port Flanged Valve Body.  In such instances a S-E L8TV Linkage Kit will additionally be required.  Alternatively an Actuator from the S-E range of Actuators may be installed on the V222 2-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. IMPORTANT NOTE It should also be noted that the face to face dimensions both of the S-E VG221F and V222 2-Port Flanged Valve Bodies differ to that of the Satchwell VZF 2-port Flanged Valve Body  Similarly, the centre line to bottom of third port dimensions both of the S-E VG221F and V222 2-Port Flanged Valve Bodies differ to that of the Satchwell VZF 2port Flanged Valve Body  As a result alterations to the pipework connected to the VZF 2-port Flanged Valve Body will be required. Details of the Satchwell VZF 2-port Flanged Valve Body may be viewed here. Details of the S-E VG221F 2 port Flanged Valve Body may be viewed here. Details of the S-E V222 2-port Flanged Valve Body may be viewed here. Details of the S-E L9TVG Linkage Kit may be viewed here. Details of the S-E L8TV Linkage Kit may be viewed here.

Issue RM / XRM series Light Duty Rotary Actuator installed on MB Valve Body requires removal / replacement. Environment RM          RM3601 XRM        XRM3201 Light Duty Rotary Actuator MB Valve Body Cause RM / XRM series Light Duty Rotary Actuator installed on MB Valve Body requires removal / replacement. Resolution RM / XRM series Light Duty Actuator removal / replacement may be achieved as follows :- Removal :- 1.    Beware!        RM Actuator is connected to a Mains Voltage power supply.        XRM Actuator is connected to a 24 Volt power supply. 2.    Isolate Actuator power supply. 3.    Locate Terminal Chamber - This may be found on top of the Actuator. 4.    Remove Terminal Chamber Cover. 5.    Locate Locking Plate Tab – This may be found inside the Terminal Chamber on the face nearest the Window housing the 0-10 Position Indicator Wheel. 6.    Pull Locking Plate Tab up to disengage the Actuator from the Valve Body. 7.    Separate Tongue of Actuator from Groove in Valve Body Spindle. 8.    Actuator may now be removed by joggling Keyhole Slots in Actuator Base plate over Allen Bolts protruding from MB Valve Body. N.B. It is not necessary to remove the Allen Bolts from the MB Valve Body in order to remove the Actuator. Replacement :- 1.    Joggle Keyhole Slots in Actuator Base plate over Allen Bolts protruding from MB Valve Body. 2.    Insert Tongue of Actuator in Groove of Valve Body Spindle 3.    Push Locking Plate Tab down to lock the Actuator to the Valve Body 4.    Replace Terminal Chamber Cover securely. 5.    Restore power supply. Details of the RM and XRM Actuators may be viewed here.

Issue Satchwell MJF 3-Port Flanged Valve Body requires replacement. Environment Satchwell 3-Port Plug and Seat Flanged Valve Body MJF3426    MJF 3426 MJF3427    MJF 3427 MJF3476    MJF 3476 MJF3526    MJF 3526 MJF3576    MJF 3576 MJF3626    MJF 3626 MJF3676    MJF 3676 Cause Obsolescence of Satchwell MJF 3-Port Flanged Valve Body Resolution Replace Satchwell MJF 3-Port Flanged Valve Body with S-E V311 3-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on MJF 3-Port Flanged Valve Body may be retained for installation on replacement   S-E 3-Port Flanged Valve Body.  In such instances a S-E L8TV Linkage Kit will additionally be required.  Alternatively an Actuator from the S-E range of Actuators may be installed on the V311 3-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. IMPORTANT NOTE It should also be noted that the face to face dimension of the S-E V311 3-Port Flanged Valve Body differs to that of the Satchwell MJF 3-Port Flanged Valve Body  Similarly, the centre line to bottom of third port dimension of the S-E V311 3-Port Flanged Valve Body differs to that of the Satchwell MJF 3-Port Flanged Valve Body  As a result alterations to the pipework connected to the MJF 3-Port Flanged Valve Body will be required. Details of the Satchwell MJF 3-Port Flanged Valve Body may be viewed here. Details of the S-E V311 3-Port Flanged Valve Body may be viewed here. Details of the S-E L8TV Linkage Kit may be viewed here.

Issue Cannot find any installation instructions documentation for the WorkPlace Tech Tool software, versions 5.8 or 5.8.1. Product Line TAC IA Series Environment WorkPlace Tech Tool software version 5.8 & 5.8.1 Cause An updated version of the document "WorkPlace Tech Tool Version 5.7 Installation Instructions" has not yet been released by our publications group. Resolution The existing "I/A Series WorkPlace Tech Tool Version 5.7 Installation Instructions", F-27367 can be used for installing the release 5.8 or release 5.8.1 of the WorkPlace Tech Tool software. There are two items applicable to the newer versions of the WorkPlace Tech Tool software that are not covered in the published installation instructions. The WorkPlace Tech Tool software, releases 5.7.7, 5.8 and 5.8.1 will run on the 32 bit versions of Windows-XP, Windows Vista or Windows-7.  These releases of the software will also run in XP-Mode under the 64-bit version of Windows-7.  See I/A Series (Niagara) R2 Windows Compatibility Matrix and the linked PA-00163 product announcement for more information on Windows 7 compatibility.  Make sure that the computer meets or exceeds the recommended requirements, not the minimum requirements, for the operating system being used. Beginning with release 5.8.5 of the WorkPlace Tech Tool software, Windows 7 64-bit Professional and Microsoft Visio 2010 is supported (32-bit version only), in addition to the documented Microsoft Visio 2003 and Microsoft Visio 2007 (32-bit versions). The use of Visio 2010 and its ribbon bar menu system are described in the WorkPlace Tech Tool release 5.8 release notes.  This same version of the release notes (5.8) is applicable to the use of Visio 2010 with the WorkPlace Tech Tool software release 5.8.1.

Issue Wiring a MD10B-24 / MD20B-24 actuator to a Climatronic CXT / CXR / CSC Actuator Environment MD10B-24 MD20B-24 Actuator Climatronic CXT CXR CSC Cause The Climatronic controller switches the O volt side of the 24 volt supply, but the actuators shows that it requires 24 volts to open and close. Resolution The Satchwell range of Climatronic controllers have always switched the 0 volt side of the 24 volt supply to control the actuator position. CXT Controller - Terminals 13 and 14 provide 0 volts to close or open the actuator. A permanent 24 volts is provided by terminal 37. For the complete datasheet, please click HERE. CXR Controller - Terminals 23 and 24 provide 0 volts to close or open the actuator. A permanent 24 volts is provided by terminal 37. For the complete datasheet, please click HERE. CSC Controller - Terminals 33 and 32 provide 0 volts to close or open the actuator. A permanent 24 volts is provided by terminal 37. For the complete datasheet, please click HERE. The MD10B-24 / MD20B-24 datasheet shows the wiring as follows; For the complete MD10B datasheet, please click HERE. For the complete MD20B datasheet, please click HERE. The above actuator wiring shows a 0 volt connection to the common connection (1) and a switched 24 volt connection (2 or 3). To connect the MD10B-24 / MD20B-24 actuator to any of the above controllers it will be necessary to connect the actuator as follows. Controller 24 volt  (37) to connection wire (1). Controller Open signal (14, 24 and 32) to connection wire (2). Controller Close signal (13, 23 and 33) to connection wire (3). Please note that the actuator direction can be changed by repositioning the switch on the front of the actuator.

Issue What are the differences between the IAC 400 and the IAC 420 controllers? Product Line Field Devices, Other, Satchwell MicroNet, Satchwell Sigma   Environment IAC 400 IAC 420 Cause The IAC 400 controller is obsolete and its replacement is the IAC420. Resolution Hardware differences; The IAC 400 has 3 Temperature, 2 Analogue and 1 Digital input, where as the IAC 420 has 6 Universal inputs. Communications differences; The IAC 400 controller uses terminal 3 to earth the communications cable screening, on the IAC 420 the screening must be connected to a good earth and not terminal 3. Tables and offsets; Because the IAC 420 has different inputs that tables and offsets are changed, please review IAC Controllers - Tables and Offsets. IAC 400 Wiring details. For the full data sheet please click HERE.   IAC 420 Wiring details. For the full data sheet please click HERE.

Issue TAC 200 OTP User Guide TAC 239W DHW User Guide Environment TAC 200 OTP TAC200 OTP TAC239W TAC 239 W Cause Information required regarding the TAC200 OTP Optimiser/Compensator Controller. Information required regarding the TAC239 W DHW Controller. Resolution Download here the TAC200 OTP guide. Product Part Number: 200-1005-000 Download here the TAC239 W guide. Product Part Number: 239-1010-800

Issue "Relock upon Door Closure" option is greyed out and feature is not available.  Environment Continuum Access Control Cause The "Relock upon Door Closure" feature is not implemented at this time.  Resolution For this "Relock upon Door Closure" functionality you will need to use Plain English code. The code located here is a sample of how this can be accomplished.

Issue The EGWW sensor is obsolete and needs to be replaced. Environment  EGWW: EGWW 120 Cu 5122720000 EGWW 120 St 5122720010 STP100: 5123102010 5123104010 5123106010 5123108010 5123110010 5123112010 5123114010 Cause Obsolete sensor needs to be replaced. Resolution There is no direct replacement, as the old EGWW had 2 sensor elements and was designed to be used with controllers like TA 219WB (Data sheet here). Also, the EGWW was designed to be mounted directly into the pipe work using a well, and not using a pocket as with the STP100. If only one sensor element is required by the application, the STP100 series sensor is recommended. However, please note that the EGWW well was 120mm or 220mm (see data sheet here), while the STP100 sensor probe and pockets are available in 50, 100, 150, 200, 250, 300 and 400 mm lengths. For more information and details on the STP100 and its different configurations, please see data sheet here. If the 2 sensor configuration is required, you will have to install 2 parallel sensors.  

Issue In Niagara G3, the SNMP driver reference manual refers to three MIB files required so that the SNMP Point Manager can "discover" and "add" SNMP points as needed.  The filenames are: TridiumR3-MIB.my RFC1155-SMI.mib RFC1213-MIB.mib Where can they be found? Environment Niagara G3 Cause The three files are not easily located. Resolution The TridiumR3-MIB.my file is installed with the version of Niagara G3 installed on the host computer. The other two files (RFC1155-SMI.mib & RFC1213-MIB.mib) can be found on the World Wide Web by searching using their specific filenames. All three files are available here:  SNMP_Files_for_G3

Issue There is a need to be able to calculate and estimate the amount of power being consumed by IOU modules and their readers Environment 99xx 9680 IOUs Cause Power supplies have a wattage limit and adding to many modules can cause the bus to become unstable Resolution To estimate the amount of wattage being consumed by IOU modules, please download the following Excel Spreadsheet. Continuum I/O Module Power

Issue Replacing a DC3000 controller. Environment Drayton DC3000 Cause The DC3000 is now obsolete. Resolution The DC3000 controller is obsolete, and there is no direct replacement available. Our current range of discrete controllers cannot provide the same functionality as the DC3000, assuming that functionality has been used. To provide the same controller functionality a programmable controller such as the Micronet or Xenta ranges will be required To upload an overview of the Micronet range, please click HERE. The Xenta controller range is listed as part of the TAC Vista Product Catalogue which can be downloaded from Schneider Electric but a table of the controllers and their I/O are shown below.

Issue The documentation on The Exchange differs from the documentation included in the packaging. Neither document shows the full capabilities or wiring options of the transmitter. Environment STO300 Cause The supplier recently changed the PCB and as a result, all of the 300 model plantroom type sensors now offer dual outputs (current and voltage). Since the part number designation is for current only the documentation included in the packaging only shows this configuration. To further complicate matters the specification and installation materials on The Exchange have not been updated to reflect the changes at this time Resolution The installation instructions included in the product packaging should always be referred to when installing these transmitters. The latest installation instructions can be downloaded here. If the new 0-10VDC output feature is required please follow the diagram below for wiring and DIP switch configuration.

Issue How do points map from a i2 controller and the xP expansion modules to Infinity SX8000? Environment Using Continuum i2 controllers and xP modules on SX8000 Infinity systems. Cause The I/O channels on expansion modules are different from Infinity to Continuum. Resolution You can add an i2 controller to your Infinet networks on Infinity and it will co-exist with the other Infinity controllers. The controller will be seen as a equivalent infinity controller i.e. a i2850 will be seen as a TCX850. Also you will not be able to use any of the additional features that a i2 controller has like the flash memory or the smart sensor connection. For Expansion modules you could however use the xP modules (not including the xP display) the attached spreadsheet that shows how the i2 controllers I/O channels will be seen by the Infinity Controller. Download the spreadsheet here.  

Issue The alarms in the UNCs stop archiving to the Enterprise Server database. The process was working before and nothing was changed. Product Line TAC IA Series Environment I/A Series R2 using the Cloudscape database Cause The size of the Cloudscape database has grown too large. This may cause issues with the system. Resolution Reduce the size of the Cloudscape database by deleting older alarms and logs. Refer to this document for details on how you can delete old alarms and logs. For details on the CloudscapeAdmin utility mentioned in the document, refer to How to remove data for all logs prior to a specific date in a Niagara R2 Enterprise Server.   Switch to using a SQL database instead of the default Cloudscape database if there is a requirement to keep old alarms and logs for a longer period.   There isn't a known limit where the size of the Cloudscape database can grow before the possibility of problems starting to occur. It is different for each site. As a guideline, it is recommended that SQL database be used if the size of the Cloudscape database has to be greater than 2GB.

Issue The new release note for the IC3-SNP does not give the object mapping information for the IAC 420 controllers Environment Sigma IAC Controllers Integration Controllers Cause The release note for the latest IC3-SNP controllers does not give the table and offset information for the object mapping used in the gateway.txt file Resolution Please click here for a document giving the details of the tables and offset used. It is from an old release note but the details have not changed.

Issue Object level security using SecurityLevel Environment CyberStation Cause Documentation Resolution Click -> Continuum Security Levels explained.

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 Can the xPBD4 be used with an i2 or b3. Environment xp Expansion Module Cause Is the xPBD4 compatible with an i2 or b3. Resolution No. The following note is from the xP Expansion Datasheet: The xPBA4 and xPBD4 Expansion Modules can only be connected to the bCX1 Controller/Routers and ACX Series Access Controllers. The other xP expansion modules do work with the i2/b3 controllers. See the attached data sheet for more info.