Building Automation Knowledge Base

Issue Extended Logs have stopped updating on the Enterprise Server. Product Line EcoStruxure Building Operation Environment Extended Trend Logs Cause Extended Trend logs have been set up on the site for some time and have operated correctly. Now some of them have stopped updating.  Resolution This issue can be caused by a Server backup being restored. Trend logs and Extended Trend logs are allocated sequence numbers, and if the sequence numbers do not follow the correct sequence, the Extended Trend log may not update. To confirm that this is the issue; Trend Log. Navigate to the Trend log and open it in a "Trend Log List" view. Add an additional column to show the Sequence number. Note the highest sequence number used. Extended Trend Log. Navigate to the Extended Trend log that is referencing the above Trend Log. Open it in a Extended Trend Log properties. Press and hold down the "ALT" key and click where the dot is indicated on the screen shot below, (just below the Basic tab).       This will show some more properties for the Extended Trend Log, the one you are interested in is “Last transferred sequence number”.   If the last transferred sequence number on the Extended Trend Log is higher than the Trend log’s highest sequence number, then that is why the Extended Trend Log has stopped. How can this issue be resolved? Increase the sample interval of the Trend log until it has caught up. The Extended Trend Log will only fetch new records that has a sequence number higher than the last transferred sequence number. So until the sequence has caught up, you will not see any new records in the Extended Trend Log, and only records created after you have caught up in sequence numbers will be fetched. Re-create the Extended Trend Log. The new Extended Trend Log will fetch every record the log has and continue from there, but you will lose the records the old Extended Trend Log had that the log does not have anymore. Backup / restore on the AS. The Trend log will be cleared but the Extended Trend Log will start fetching new records.    

Issue How do I format a Comma Separated Variable file (CSV) to create personnel objects via import that will include area assignments and photos. Product Line Andover Continuum Environment CyberStation Cause Need way to mass create personnel objects. Resolution Typically personnel information is provided from Human Resources in a MS Excel file, the data can be saved as a CSV file and easily formatted for import into the Continuum system which will automatically create one personnel object per row using the information (LastName, FirstName etc) included in the file. Assigning areas during import is accomplished by specifying a personnel template (previously created using Continuum). Different areas can be assigned to different personnel objects as a template can be specified per row. When the personnel object is created via the CSV import, it will be assigned all the areas found in the specified template. Importing a photo for the personnel object is accomplished by specifying an image file in the PhotoFile column. Click Here for a sample CSV file.

Issue Default IP address of a SmartStruxure Lite MPM Product Line EcoStruxure Building Expert Environment MPM Cause What is the default IP address of a SmartStruxure MPM? Resolution Out of the box, the default IP is 10.50.80.3 subnet mask 255.0.0.0 This should be changed to suit the project requirement. Log into the controller using the default IP address. Edit the Ethernet setting, changing the IP address, Subnet Mask and Default Gateway. Click save.

Issue Separate a 7792 or 7793 into two 7798C Split SAV files  Product Line TAC INET Environment I/NET Seven 779x Controllers Cause Need to replace a 7792 or 7793 which has two station addresses and replace with two 7798C Controllers which have one station address Resolution To split the required SAV Files: Download and Extract the attached SAV_Split_EXE.zip Make a backup of the I/NET Seven system using DBCreate. Perform Station Save to all the required controllers Copy the SAV files that need to be split to the same location where the ZIP file was extracted too in step 1. Run the SAV_Splt.exe The commands are showing the Sav_Splt.txt file contained within the ZIP file and shown below Purpose: Use this tool to create two 7798 SAV files from a dual-station 7793 SAV file. Syntax: Sav_Split.exe (with no parameters will check all save files in the current directory and split 2 station 7793s.) Sav_Split.exe LLSS (where LL = Link and SS = Station) Result: The resulting files will be named DCULLSS-0.SAV and DCULLSS-1.SAV. Rename these files appropriately to match the link and station of the 7798 into which each will be loaded. Example: SavSplit.exe 0906 Results: DCU0906-0.SAV and DCU0906-1.SAV     Finally check the split files using the "Work Offline" mode within I/NET Workstation. Any issues or additional questions please raise a case with your local support   For SAV file upgrade information see How to upgrade bin and SAV files in I/NET controllers.

Issue Is a certain version of Technician Tool Mobile Application compatible with all versions of StruxureWare Building Operation? Product Line EcoStruxure Building Operation Environment Building Operation Technician Tool Automation Server Enterprise Server Cause The Technician Tool will always be backwards compatible, meaning that the latest version of the tool will work with any version of SBO. Older versions of the Technician Tool may not work with a newer version of SBO. Resolution Please note: Mobile experience to be replaced with EcoStruxure™ Building Operation v2.0 WebStation. For further information, please refer to Notice of Withdrawal of the Building Operation Technician Tool Always use the latest version of Technician Tool Mobile Application when possible, as that will work with all SBO versions.

Issue Is it currently supported in EcoStruxure Building Operation to make EWS requests with users managed by Active Directory (Windows user)? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause The EcoStruxure Building Operation software provides two methods to log on to the system, as a Windows user or as an EcoStruxure Building Operation user. Windows User A Windows user account is mapped to a Windows Active Directory user account group. Log On as an EcoStruxure Building Operation User When logging on as an EcoStruxure Building Operation user, you authenticate yourself with an EcoStruxure Building Operation account user name and password Resolution EWS only supports login to SBO domains (with Challenge Response, RFC7616) and NOT Windows domains added into SBO. It is not possible for an EWS request to authenticate using a Windows user only an EcoStruxure Building Operation user.

Issue An AS has failed and there is no backup. Can the SD card from the broken AS be used in a new AS Product Line EcoStruxure Building Operation Environment Automation Server Cause AS has failed without any backup and there is a need to get the information to the new AS Resolution The SD card in each AS is encoded for that specific AS. The information on the SD card can only be read by that AS. AS's are now replaced by the AS-P, however if an AS can be obtained, then a backup can be recovered as follows:   It is possible to put the SD card from the damaged AS into a non damaged AS and do a backup. Then the backup can be restored into a new AS-P. The AS-P does not use a SD card. Important note: The version of the bad AS / SD card needs to match the donor AS used to make the backup. To remove the memory card push the metal retainer in towards the centre of the PCB The metal retainer will disengage its locking catches The metal retainer is hinged and can then be opened The memory card can then be lifted out for replacement Replacement is the reverse of the removal process.

Issue Xenta group bindings are used for group communication between Xenta group masters and members.  They also transmit TAC Network Variables between two programmable controllers.  Redoing group bindings is a common troubleshooting technique to address issues with these functions.  However, it can often be time consuming, especially if using LonMaker which requires the Visio drawing to be resynchronized.  Verifying that the Xenta group bindings in the device's address table are correct prior to redoing them can save time on an unnecessary troubleshooting step. Product Line TAC Vista Environment Vista programmable controllers LonMaker, NL220 Cause Checking to see if the group bindings need to be redone instead of always using it as a standard troubleshooting technique can save time. Resolution To access the Device Address Table of an application device in LonMaker: Right-click on the controller in LonMaker and go to Properties. Go to the Address table tab. Look at the first two entries (0 and 1) and note the value in the ID column. Go to another controller in the same group and compare the values in the ID column. Every controller on a network should share the same ID in row 0. Every controller in a group should share the same ID in row 1. If the group bindings are correct, there is no need to redo group bindings.   To access the Device Address Table of an application device in NL220: Select the application device in the tree Press Ctrl+A keys or right click on it and select the option Network\Network tables ... in its context menu Select the tab Addresses    The grid contains one line for each entry in the address table. Index = The index of the address entry MT = Yes if the entry is reserved for message tags connection Type = Type of the entry, Unbound (Not used or "free"), Turnaround, Subnet/Node, Broadcast, Group Size = Size of the group (zero for a large group) and Used only if Type is Group Domain = Domain index (0/1) Mb/Node = Member if Type is Group (not used for a huge group), Node id if Type is Subnet/Node or Unused Repeat timer = Value of the repeat timer  Retries = Retries count Rcv timer = Value of the receive timer  Tx timer = Value of the transmit timer  Gp/Subnet  = Group id if Type is Group, Subnet id if Type is Subnet/Node or Unused   Refresh will refresh the table.

Issue EBO system was in sync with Building Advisor Portal and is now not. Product Line EcoStruxure Building Operation, EcoStruxure Building Advisor Environment Building Operation Building Advisor Portal Building Operation Enterprise Server Building Operation Automation Server Cause System ID changed and no longer matches in Building Advisor Portal. Resolution Check EBO Server Trace Log for nsp.pin.Cloud records and there should be one that shows "SystemId". Here is an example: 2023-11-19 12:37:30.437 [320] nsp.pin.Cloud.DspInterface Sending notification {"ProtocolVersion": "1.0", "NotificationType": "TimeSeries", "IotDeviceId": "urn:dev:ops:sebms-sbo-es-fb6b2834ba4749d89cdad333c12704a3", "SystemId": "4ba3db45-0235-7146-981a-c81dc08e39bf", "GeneratedAt": "2023-11-19T12:37:30.0437Z", "GeneratedBy": "SBO 3.2.4.22","Operation": "Update","TimeSeries": [{"TimeSeriesId": "d8e6b6fc-a472-4285-a56d-2d3e4a6915e1","Samples": [{"Timestamp": "2023-11-19T12:37:30.0437Z","Value": "Unknown [null]","Unit": "0x10001","Status": 20}]}]} 2023-11-19 12:37:30.437 [320] nsp.pin.Cloud.DspInterfaceReal edgeAgent_sendMessage: {"ProtocolVersion": "1.0", "NotificationType": "TimeSeries", "IotDeviceId": "urn:dev:ops:sebms-sbo-es-fb6b2834ba4749d89cdad333c12704a3", "SystemId": "4ba3db45-0235-7146-981a-c81dc08e39bf", "GeneratedAt": "2023-11-19T12:37:30.0437Z", "GeneratedBy": "SBO 3.2.4.22","Operation": "Update","TimeSeries": [{"TimeSeriesId": "d8e6b6fc-a472-4285-a56d-2d3e4a6915e1","Samples": [{"Timestamp": "2023-11-19T12:37:30.0437Z","Value": "Unknown [null]","Unit": "0x10001","Status": 20}]}]} (retCode = 0) In Building Advisor Portal, check the BMS System Identifier to ensure it is the same and update as needed. In this case, d057cfba-9fc0-11e4-a62a-3417ebbed129 needed to be updated to 4ba3db45-0235-7146-981a-c81dc08e39bf

Issue Animations, gifs, updating values, hover overs or mouse event scripts work in Workstation but do not work in Webstation. Product Line TAC Vista Environment Vista Webstation TGML graphics   Dynamic values       Cause Various reasons can cause TGML graphics to not function the same in TAC Vista Webstation as in Workstation. Typical reasons can be: Using "Static TGML viewer" vs. "Dynamic TGML viewer". Under Static view, all animations are prohibited. Using unsupported script functions can cause animation to not work in Webstation. Sizes and the number of animated .GIF images used on a single TGML graphic page. Resolution Check if the Webstation is running under Dynamics view. Go to Start->All Programs->Schneider Electric->TAC Vista Web Applications -> Vista Web Setting. (For Vista 5.1.3 or prior, go to Start->All Programs->TAC->TAC Vista Web Applications -> Vista Web Setting instead.) Click on "Graphics/TGML Views" in the left panel. Make sure the TGML View is either “AutoDetect” or “Dynamics” in the right panel.  If it is “Static”, click on the drop down manual and choose a different display viewer.   Check if using any unsupported Java script. Please reference Vista Webstation unsupported TGML functions for more information.   If a TGML graphic page contains many animated GIF images, it can cause the animation on that graphic page to run slow, discontinuously, or not run at all.  The amount of animated GIF images that can be put on one single TGML graphic page various case by case. Therefore, the best way to test it is deleting all animated GIF images and add them back on one by one.

Issue Getting error message when reloading a Continuum controller: "Unable to reload attributes for \ \ . Reload Object's Type mismatches with object's in WCU Controller. Please Reload WCU Controller." Environment All Continuum controllers Cause The most common cause of this error message is duplicate alias names. For example, a controller object named "W Lobby" and a door object in the controller named "WLobby" (without the space) will have the same alias (WLobby). Resolution Rename one of the duplicate objects so that the alias is unique to the system.

Issue Right clicking the controller and selecting "Distribute Personnel" results in NO distribution There is no error Product Line Andover Continuum Environment CyberStation Cause Corrupted Personnel Distribution table in SQL ContinuumDB Resolution Truncate table PersonnelDistribution and re-populate it, then distribute personnel once again. WARNING: Unless knowing exactly what you are doing, deleting entries from your database can cause irreversible harm to your database and can potential cause corruption. Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and if not already installed, where to get Management Studio from) Make a backup of the Continuum database as a precaution. Close ALL CyberStation workstations. In SQL Management Studio execute the following query. truncate table PersonnelDistribution Once the table is truncated it must be re-populated by one of the following methods... If the total number of personnel objects is reasonably small (in the hundreds) launch Continuum and bring a list view of all the personnel objects, select all then right click and perform a 'Send to controller' OR In SQL Management Studio Invoke the stored SQL procedure that initializes the PersonnelDistribution table using the query dt_DIST_Init_Personnel_Dist_Table IMPORTANT: Truncating the PersonnelDistribution table will remove all pending personnel distribution including personnel deletions; controllers could potentially continue to allow access to doors for the deleted personnel until reloaded. Conversely, removing a pending personnel distribution could potentially cause a person to be denied access at a door until a distribution is performed to the controller.

Issue After downloading application and parameters to a TAC Xenta from TAC Vista, get an error message "OUT OF MEMORY (RAM)" When trying to edit a Xenta trend in TAC Vista Workstation get an error message "Could not save the object: OUT OF MEMORY (RAM)" Product Line TAC Vista Environment TAC Vista Workstation TAC Menta Cause The error message means that a trend log definition exceeds the capacity on the TAC Xenta unit. Resolution In Menta: Select the "Option" menu, and click on "Trend Logs". In the Select Trend Log dialog box, double click on the trend log that need to be edited. In the "Trend Log Definition" window, under "Signal" section: Increase the "Log Interval" time Decrease the "Log Space" time In TAC Vista Workstation: Right click on the Xenta log that needs to be edited. Select "Properties". Under the "Signal" Tab: Increase the "Log interval" time. Decrease the "Log space" time.

Issue Extended Elevator control (Step by step instructions) Product Line TAC INET Environment I/NET Seven DPU Firmware 3.20 or above. (DPU7920 with 48k MIP or SCU1284) Cause Extended elevator control allows support up to 79 floors and easier programming methodology than the traditional method.  This has been added to I/NET Seven software and DPUs as detailed in the environment.  Resolution To use any of these features requires that the DPU be a 7920 w/ MIP board or the new SCU1284. 7910 and 7920 w/o MIP board will still work with the I/Net system but they cannot use these functions. The host prevents the download of these features to any DPU revision prior to 3.10.   Extended Elevator Control Setup Example This is based impart on basic prior knowledge of InetSeven Host software setup and configuration to include but not limited to Controller Station Parameters, Resident I/O, Point Extensions, Operations of Network Configuration, and Access Configurations (Doors, Tenants, Groups, Individuals and Personnel Schedules). Hardware required: DPU 7920 48k (The following control will only apply to the 7920 48k) Please follow these steps to configure extended elevator control. Resident I/O Editor Edit / Controller / Resident I/O – Add the following Internal DO Door Reader point Internal DI point for each Floor DO External DO point for each Floor button DI Note – Save Door in the Network Configuration editor. Controller Door Editor Edit / Controller / Door Editor Select Door to add Elevator Control Modify – check Elevator Control box Select “Message type” Alarm / Transaction Note – Ensure a Schedule (s) has been assigned to the Door reader point. Controller Elevator Parameter Edit / Controller / Elevator Add Elevator Extension to reader point. Add Floor parameters. Complete the following; Floor Index Selection Floor designation Button Enable (DO) Button Selection (DI) Note – When finished “STOP” Do not select floors, Select OK and Close. Network Configuration  Edit / Host Computer / Network Configuration. Penetrate down to the DPU (Door Read Point) with Elevator Control Penetrate one more level and SAVE all your floor extensions. Tenants Access / Tenants Select Tenant Locate Door Reader point – Remove “X” (Unselect). Place an “X” next to all floors that tenant will have access to – Select Ok At this time I would suggest performing a save function followed by an SLI and DPU restore. Individual Editor You are now ready to add individuals or assign individuals access to floors.

Issue When connecting the RoamIO-2 service tool directly to a standalone BACnet b3 controller which is not connected to the MSTP network yet, the RoamIO-2 does not show the b3 controller on the screen. Environment RoamIO-2 Continuum SmartStruxure BACnet b3 controller Cause By default, the View option of the ROAMIO2 Bacnet Service Tool is set to view "By Network".  Resolution Connect the RoamIO2 service tool directly to the b3's service port. Launch the BACnet Service Tool and in the 'View' menu de-select 'By Networks' and 'BACnet Only' menu entries. Click the green icon to connect. Now, it will show the b3 controller in the service tool.

Issue Continuum Add-On Software products and support contacts Environment Continuum Continuum Reports Suite Continuum Archiver/Archivers Continuum Elevator Control Continuum Bioscrypt Integration Video Monitor For Third Party Video Systems Continuum Guard Tour Center of Excellence (COE) Cause Continuum Add-On Software products and support contacts information. Resolution Please forward Continuum Add-on Software support requests to COE.Support@buildings.schneider-electric.com The Reports Suite software can be downloaded here: https://ecobuilding.schneider-electric.com/search?documentUUID=e040ce9b-7114-4cbc-b9cc-bcde73a6d64e&title=Continuum%20Reports%20for%20CyberStation%20v1.81%20and%20v1.82%20Add-on%20Software Internal note: In bFO the Care Team to which PSS will De-Escalate case is the NAM_BLD_COE_ADV Care Team.

Issue Standard Applications for I/A Series Micronet BACnet (MNB) controllers Product Line I/A Series Environment I/A Series WorkPlace Tech 5.x and above I/A Series MNB controllers Cause A library of standard pre-engineered applications for MNB controllers is available. These can be modified and used as a reference for creating MNB applications. Resolution The library of standard applications can be downloaded from Exchange Extranet. Below is a list of the applications available for downloads.  DUI Application Stencil Operation Guide Application Objects Visio Stencil (Includes DUI_App) Applications - BACnet Zone, VAV, and Unitary Applications using SP and SPP Momentary Start/Stop Object Application Operation Guide Application - BACnet Zone Controller Applications Application - BACnet VAV Box Applications Application - BACnet Unitary Applications Stencil - Application Stencils Application - VAV_Staged_Heat.vst Application - FC_1DX_1EH.vst Application - FC_1PropCL_1PropHT.vst Application - FC_2Pipe_2PosHC_wCO.vst Application - All BACnet Unitary Applications.zip Application - All BACnet VAV Box Applications.zip Application - VAV_Cooling_Only.vst Application - VAV_Floating_Heat.vst Application - AHU_HeatPump.vst Application - VAV_Parallel_Fan_Staged_Heat.vst Application - VAV_Parallel_Fan_Floating_Heat.vst

Issue How to use RoamIO to set the Infinet ID of Infinet device to zero before re-deploying the device. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum Service Tool Cause Need a way to set the Infinet ID of Infinet device to zero before re-deploying the device. Resolution  This video demonstrates… Tell if the i2 device has an Infinet ID assigned by observing the TD/RD LEDs on the device. Use the RoamIO to connect directly to the i2 device and reset its Infinet ID to zero. Confirm by visual observation of the device's TD/RD LEDs that the ID has been successfully set to zero.

Issue In Menta simulation mode, when changing the RI block (using the button on the left hand side), the TSCHI will get the same value When changing the TSCHI block, nothing will happen at all  Environment TAC Menta Xenta 701, 711, 721, 731 Cause This happens due to a bug in TAC Menta. Resolution Create the TSCHI block before the RI block (this issue will only occur when the RI block is created first). Please note the this issue only affects simulation mode of Menta, you won't notice it  when the project is downloaded to the device.

Issue Do I need an X Driver to send simple ASCII strings to a third party system? Environment Plain English Drivers PE Driver, Raw Mode CX Controllers Netcontroller II bCX ACX Cause Require the limitations of Plain English drivers Resolution It is possible to create a Plain English driver to print ASCII data out of a Comm port. Use the Open, Close and Print keywords to develop your program in a CX or bCX controller, if you go to the "Help, Contents" on Cyberstation Explorer you can enter these keywords and get full details on their use including example programs. You can also read responses from the 3rd party system with the "Read" keyword. The Plain English program would be able to print out any information that can be put into an InfinityString. The characters that a PE Driver cannot handle are the FFh (255) and 0H (null) characters, to use these would require the use of an X Driver or another form of gateway to an open protocol. If you have a first generation controller (CX9900, CX9400 etc) there is a Generic ASCII "X Driver Filter" that can be used to print/ read an ASCII string with no character limitations. If the port is X Driver enabled then download software X-Driver Filter The CHR keyword can be used to send "Non printable characters". The other thing is that a Plain English Driver will be dependent on the controller scan time so it would not be suitable for any protocols that are timing critical and the controller scan time must be kept low. As a general rule of thumb, if you can send the required characters out using Hyperterminal and the system accepts it, then a PE program should be able to send them too.  The attached document is an example of a Plain English driver that was written a while ago to communicate with a Video Recorder over an RS232 link, the principles and techniques used in this example show the use of the above keywords as well as some of the string manipulation keywords. Download it here. This also applies to the ACX57xx controllers but they only have a single half duplex RS485 port which may not be suitable for all applications.