Building Automation Knowledge Base

Issue First Day of Week is incorrect Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation  WebStation Cause Calender/Schedule has the week starting on Sunday/Monday and the first day of the week in my region is Monday/Sunday. Resolution WorkStation Exit the Building Operation WorkStation. In the Operating System for Windows, select Start - Control Panel - Clock Language and Region. In Region and Language on the Formats tab, find First day of week and adjust to your regions choice: Open up Building Operation WorkStation and see your calendar changes the first day of the week to match your choice: WebStation Navigate to web_root/localization folder under the ES and find the Local-en.US.js.gz file to edit Using WordPad++ below I find the "First_Day_Of_Week" as shown below and change from "1" to a "2" then save, and using my zip software, I save to format gzip. Notice in the above screenshot the renamed OLDlocal-en-US.js.gz and the new one is in place. Now you can see in WebStation the first day of the week is Monday rather than Sunday

Issue How to calculate wet bulb temperature from a temperature sensor and humidity sensor Product Line Satchwell BAS & Sigma Environment Satchwell BAS & Sigma Cause How to calculate wet bulb temperature from a temperature sensor and humidity sensor? Resolution For an exact answer, the dew point and barometric pressure are also required. However a reasonably accurate answer can be derived from a temperature sensor and humidity sensor, as follows: In the 1st example, the pressure can either be taken as an input, or a constant can be used. the constant will normally be derived locally or the 1006mBars can be used.  Example 1. tw = t * (0.45 + 0.006 * Rh * sqr(p/1060)) Where tw = wet bulb temperature (Celsius degree) t = dry bulb temperature (Celsius degree) Rh = relative humidity (%) The BAS or Sigma programmable object would be: 10 XFlo = 0.000000 20 YFlo = 0.000000 30 XFlo = XFlo + ( SQRT ( 1006.00 / 1060.00 ) ) 40 YFlo = YFlo + ( 0.00600000 * POINT 0|50 * XFlo ) 50 YFlo = 0.450000 + YFlo 60 YFlo = POINT 0|49 * YFlo 70 RETURN VIA TEXT 101 VALUE YFlo P0|49 is the temperature sensor (Celsius degree) P0|50 is the humidity sensor 1006 mbars sample pressure which is the standard used in the formula below. This can be substituted for either a sensor or another reading. Example 2. In the range Tdry bulb = 15..40[deg C] and rh = 10...90[%] the Twet bulb[degC] can be calculated at P=1006[mbar] with max relative error ~ 6% . For lower Tdry and rh the relative error will be higher. Twet bulb= (A * Tdry) + (B * rh) + (C * Tdry^2) + (D * rh^2) + (E * Tdry * rh) + F where A=5.391260E-01 B=1.047837E-01 C=-7.493556E-04 D=-1.077432E-03 E=6.414631E-03 F=-5.151526E+00 ^2=squared The BAS or Sigma programmable object would be: 10 XFlo = 0.000000 20 XFlo = XFlo + ( 0.539126 * POINT 0|49 ) 30 XFlo = XFlo + ( 0.104784 * POINT 0|50 ) 40 XFlo = XFlo + ( - 0.000749356 * POINT 0|49 * POINT 0|49 ) 50 XFlo = XFlo + ( - 0.00107743 * POINT 0|50 * POINT 0|50 ) 60 XFlo = XFlo + ( 0.00641463 * POINT 0|49 * POINT 0|50 ) 70 XFlo = XFlo + - 5.15153 80 RETURN VIA TEXT 101 VALUE XFlo P0|49 is the temperature sensor (Celsius degree) P0|50 is the humidity sensor

Issue Satchwell ALE series Linear Actuator requires replacement. Product Line Field Devices Environment Satchwell ALE series Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body.  Actuator type :- ALE series.  Cause Obsolescence of Satchwell ALE series Linear Actuator. Resolution Replace Satchwell ALE series Linear Actuator with Schneider Electric M800 Linear Actuator and Linkage Kit :-   Linkage kit to mount a M800 actuator to a Satchwell valve (MZ,MZF, VZ, VZF, VSF and MJF) = L2SV Replace ALE Actuator with M800 + L2SV combined part number 880-0650-000 Replace ALE with Auxilary Switch kit with M800-S2 + L2SV combined part number 880-0651-000 Just linkage kit = 880-0124-000 Just M800 = 880-0310-030 N.B.  Should the Satchwell ALE series Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the S-E M800 Actuator as appropriate :-  S2 - Two independent 24 volt 4amp AC-1 rated SPDT Auxiliary End Point Switches. (880-0104-000)   Particular care should be taken when selecting an Schneider Electric Forta M800 Actuator to replace an existing Satchwell ALE series Actuator. The Schneider Electric Forta M800 Actuator may be used to replace an existing Satchwell ALE series Actuator but it should be noted that where an existing Satchwell ALE series Actuator has been connected directly to a Satchwell Controller, an independent Transformer rated to provide the greater level of power required by a single Schneider Electric Forta M800 Actuator (50VA) will also be required. (e.g. Schneider Electric Transformer Type TR60)   Where an existing Satchwell ALE series Actuator has been connected via an independent Transformer, it is possible that the Transformer may have been rated to provide the level of power required by a single ALE series Actuator (9.5VA) only.   In such circumstances the existing independent Transformer may also require replacement by another independent Transformer, rated to provide the greater level of power required by a single Schneider Electric Forta M800 Actuator (50VA) (e.g. Schneider Electric Transformer Type TR60) Details of the Schneider Electric M800 Actuator may be viewed here Details of the Schneider Electric TR60 Transformer may be viewed here

Issue EcoStruxure Building Operation Automation Server, Enterprise Server and BACnet object names limitation Dragging converted I/NET TGML graphics into Workstation causes Workstation to crash with following message: Exception message: Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at SE.WorkStation.Base.Windows.Views.TgmlFileDropHandler.Drop(FileInfo, Path, IOperationContext, IProgressInfo) at SE.WorkStation.Base.Windows.Views.FileDropCoordinator.ExecuteDrop(Path, IList`1, IProgressInfo) at SE.WorkStation.Base.Windows.Views.<>c__DisplayClassd.b__9(IProgressInfo) at SE.WorkStation.Framework.Services.<>c__DisplayClass1.b__0(IProgressInfo) at SE.WorkStation.Framework.ProgressIndication.ProgressActionOperation`2.Run(IProgressOperationInternal, IProgressResult, IProgressOperationInfo) at SE.WorkStation.Framework.Services.ProgressItem`1.b__1a(Task) at System.Threading.Tasks.<>c__DisplayClasse`1.b__d() at System.Threading.Tasks.Task`1.InvokeFuture(Object) at System.Threading.Tasks.Task.InnerInvoke() at System.Threading.Tasks.Task.Execute()  Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The number of characters and the use of special characters in a EcoStruxure Building Operation object name and EcoStruxure Building Operation BACnet objects names Resolution Refer to the Webhelp Object Names topic for information on naming restrictions The statements in Webhelp also apply to EcoStruxure Building Operation BACnet objects unless is it a Continuum b3 object.  If you are creating a Continuum b3 object etc., the b3 object display name is limited to 16 characters consisting solely of letters, digits, and underscores (as per Continuum limitation). Basically, any objects you create for Continuum, for example, a 'BACnet Analog Input (Continuum)' will be subjected to the Continuum limitation. If you add a standard 'BACnet Analog Input' into an Automation Server or an Enterprise Server, then it is not limited by the Continuum limitation of 16 characters. The most common issue when bringing I/NET TGML converted graphics into Workstation is not checking for spaces at either the beginning or end of the converted file name.  Make sure there are no spaces (white space) before or after any characters of the file name before copying into Workstation.

Issue Displaying Automation Server status on a graphic page Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation Automation Server Cause The online / offline status of an Automation Server can be viewed in the Workstation System Tree (Servers folder). However, there is currently no 'built in' method of displaying the Automation Server status on a graphic page.  Resolution There are two possible ways to workaround this   Within TGML Bind any Automation Server attribute that is shown only when the Automation Server is online (such as DateTime) and convert the status either by TGML script or a ConvertStatus element. See the attached example.   Using a script program We can create a point in the Automation Server and use another server to monitor this point. Below is an example of using the Enterprise Server to monitor an Automation Server.  Create a value point in the Automation Server. In this example, I have created an Analog Value point and set it to a value of 88.8. This value does not really matter but I have set to this value for easier recognition. Create a value point in the Automation Server. In this example, I have created an Analog Value point and set it to a value of 88.8. This value does not really matter but I have set to this value for easier recognition 1. Create a value point in the Automation Server. In this example, an Analog Value point (named 'Status')is created and set to a value of 88.8. The value set does not matter. It has been set to 88.8 for easy recognition.    2. In the Enterprise Server, create a new Program point (named 'Monitor AS' in this example) with the following codes.  Numeric Input In1 String Output Out1 Numeric Output Out2 Out2 = In1 If In1.Offline = true then Out1 = "Offline" else Out1 = "Online"   3. Edit the binding of the Script program and bind 'In1' to the Value Point that was created in the Automation Server.    4. When the Automation Server loses connectivity to the Enterprise Server, the Out1 output of the Script program will show 'Offline'. You can then bind this to a graphic page.

Issue What is throttling range? Product Line TAC I/A Series Environment I/A Series controllers Cause Setting a proper throttling range will allow for more accurate control of external actuators and devices. Resolution Throttling range is the amount of change in the process variable that is necessary to cause the controller output to change from 0 to 100%. The controller output may be 4-20mA, a voltage range, or pressure range.

Issue Satchwell MZF 3-Port Flanged Valve Body requires replacement. Product Line Field Devices Environment Satchwell 3-Port Plug and Seat Flanged Valve Body MZF MZF3729 MZF3779 MZF3854 MZF3904 MZF3958 Cause Obsolescence of Satchwell MZF 3-Port Flanged Valve Body Resolution A number of alternative Schneider Electric 3-Port Flanged Valve Bodies are available to replace existing Satchwell MZF 3-Port Flanged Valve Bodies. Suggestion 1 Replace Satchwell MZF 3-Port Flanged Valve Body with S-E VG311F 3-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on MZF 3-Port Flanged Valve Body may be retained for installation on replacement Schneider Electric 3-Port Flanged Valve Body. In such instances a Schneider Electric L9TVG Linkage Kit will additionally be required. Alternatively an Actuator from the Schneider Electric range of Actuators may be installed on the VG311F 3-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. Suggestion 2 Replace Satchwell MZF 3-Port Flanged Valve Body with S-E V321 3-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on MZF 3-Port Flanged Valve Body may be retained for installation on replacement Schneider Electric 3-Port Flanged Valve Body. In such instances a Schneider Electric L8TV Linkage Kit will additionally be required. Alternatively an Actuator from the Schneider Electric range of Actuators may be installed on the V321 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 dimensions both of the Schneider Electric VG311F and V321 3-Port Flanged Valve Bodies differ to that of the Satchwell MZF 3-Port Flanged Valve Body Similarly, the centre line to bottom of third port dimensions both of the Schneider Electric VG311F and V321 3-Port Flanged Valve Bodies differ to that of the Satchwell MZF 3-Port Flanged Valve Body As a result alterations to the pipework connected to the MZF 3-Port Flanged Valve Body will be required. Details of the Satchwell MZF 3-Port Flanged Valve Body may be viewed here. Details of the Schneider Electric VG311F 3-Port Flanged Valve Body may be viewed here. Details of the Schneider Electric V321 3-Port Flanged Valve Body may be viewed here. Details of the Schneider Electric L9TVG Linkage Kit may be viewed here. Details of the Schneider Electric L8TV Linkage Kit may be viewed here. 

Issue Receive “Timeout while waiting for server to get ready” error when starting PCT Product Line EcoStruxure Building Operation, Project Configuration Tool Environment Project Configuration Tool, PCT Cause PCT can't reach DHCP-server from the virtual machine. Resolution To configure a port group or virtual switch to allow promiscuous mode: 1.Log into the ESXi/ESX host or vCenter Server using the vSphere Client. 2.Select the ESXi/ESX host in the inventory. 3.Click the Configuration tab. 4.In the Hardware section, click Networking. 5.Click Properties of the virtual switch for which you want to enable promiscuous mode. 6.Select the virtual switch or port group you wish to modify and click Edit. 7.Click the Security tab. 8.From the Promiscuous Mode drop  down menu, click Accept. Note: The setting on the port group overrides the virtual switch setting. For more information, see How promiscuous mode works at the virtual switch and portgroup levels (1002934).  

Issue Solid red light Blinking red light Blinking green light Product Line TAC Vista Environment Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause The indicator lights on the face of the Xenta controllers can help explain the state of the controller with different actions.  Resolution There are two LED indicators – one red and one green on the Xenta programmable controllers.   The red service diode is primarily an error indication. It also lights up if the Service pin is activated. A solid red light usually indicates that the hardware has failed.  Please see a few simple steps to deactivate the solid red light below. Use a reset dongle to wipe the controller then reinstall the firmware and menta program. If the controller is the group master you might try to assign a different controller to group master.  This method has not been proven but has worked before during internal testing. NOTE: The hardware may need to be replaced if the solid red light continues after these steps. If the red indicator light is blinking once per second this will indicate a non-configured node. If the controller has been commissioned you might try to decommission the controller and try again. If the red indicator light is off this would indicate that it has been commissioned and added properly to the network.  You should not see the red indicator light if the controller is working properly. The green status diode blinks once per second to indicate that the program is running properly.

Issue A newly installed program does not run and could be using a port on the host computer that's already assigned to another running program or service.  How can current port usage on the host computer be determined quickly? Product Line EcoStruxure Building Operation, EcoStruxure Building Expert, Satchwell MicroNet, Satchwell BAS & Sigma, TAC INET, TAC I/A Series, TAC Vista, Andover Continuum, CCTV, Field Devices Environment Microsoft Windows Cause A port conflict is suspected. Resolution Open a command prompt and type: netstat -a -n -p tcp -b This command will display all services running, protocol used, local and foreign address, state, and program name.   netstat -p tcp -ano This command will display all services running, protocol used, local and foreign address, state and PID (process identifier). Use Task Manager to match the PID to the program using the port. netstat -p tcp -ano | findstr :80 If a specific port number is necessary, this command will interrogate the system for the program currently using that port number:

Issue What is the difference between the three stretch behavior buttons in the TAC Vista graphic viewer.   Product Line TAC Vista Environment Vista Workstation Cause The explanation of what these buttons do has never been explained well. Resolution TAC Vista Workstation   There are five types of stretch&zoom buttons in TAC Vista Workstation (see figure below).   The three stretch behavior buttons are: Reset the strech behavior to what is defined in the TGML document. Set image to uniform size, which means that the image is stretch out to show it as large as possible and still show the whole image and with correct aspect ratio. Fill the entire client area/window, which means that the image is strechted out as large as possible to fill the whole area without maintaining the correct aspevct ratio.   The two zoom buttons are used for zooming in and out. To use them, one selects one of the buttons and then click on the TGML image to do the actual zooming. Or one can use the plus (+) or minus (-) keys to do the zooming when the TGML windo has the focus.     TAC Vista Graphics Editor TGML In the graphics editor there are two ways of looking at the TGML image; Design or Preview mode. The second view should simulate what is shown in the Workstation.   Design mode: When starting the editor, the TGML image is shown in its actual size -100% (i.e., no stretching or zooming is done).   By clicking on the Zoom button one can get to the rest of the sub-buttons for stretching/zooming. When this sub-toolbar is shown (and only then) the shortcut keys for the strecth/zoom button works (Ctrl-Asterisk, Ctrl-Plus and Ctrl-Minus). The restore stretch button (Ctrl-Asterisk) resets the strech behavior 100%.   The two zoom buttons are used for zooming in and out. To use them, one selects one of the buttons and then click on the TGML image to do the actual zooming. Or one can use the plus (+) or minus (-) keys to do the zooming when the TGML windo has the focus. By using the shortcuts Ctrl-Plus or Ctrl-Minus, selects the correct button (and the cursor changes to the spyglass when moved) and then one can click in the image to zoom.       Preview mode: When the preview mode is entered, the strech behavior will follow what is defined in teh TGML document.  By changing the behavior in the TGML document, the stretch mode changes in the preview window (unless zoomimg has been performed - se below).   In preview mode there are no strech/zoom buttons to use in Vista (the zoom buttons are present in Struxureware). However the shortcut keys plus (+) and minus (-) can be used for zooming if the TGML image has the focus.   In Struxureware's version of the graphics editor one can use Ctrl-Asterisk to reset the strech behavior to what is defined in the TGML document if the zooming has been used. However, in Vista's version the Ctrl-asterisk does not work in preview mode. But it seems that most shortcut keys for the toolbar buttons does not work in Vista.   Note: The stretch button has different meaning in the two views.          

Issue The bandwidth utilization in the Lon network is high, it is possible to see what Lon device and what objects in the Lon device that is causing the high load on the Lon network. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Cause When the load on the Lon network is too high (above 50%) you need to analyze the Lon communication to understand what Lon devices and objects in the Lon device that is causing the high load on the network. Resolution Use a Lon Protocol Analyzer to measure the Lon bandwidth utilization on the Lon network if the load on the network is too high (above 50%) analyze the communication. When doing that it is possible to use the trace log in the ES or AS-P, please see attached video of how that is done.    Configure Trace Log to capture Lon Communications Open Workstation and navigate to [AS/ES name]/System/Modules/Trace/Loggers/nsp/nsp.pin/nsp.pin.lon Right-click "nsp.pin.lon.comm" and choose Properties Under Level, change from "Information" to "Trace", then click ok Let it run for a few minutes. If there is some user input needed to recreate the lon issue, then perform these steps now Retrieve the log by right-clicking [AS/ES name]/System/Modules/Trace/TraceSettings and choose Trace settings->Get trace log Save the log file

Issue In order to troubleshoot random network issues, it is sometimes necessary to set up Wireshark to capture network traffic for an extended period of time. As Wireshark runs it decodes packets and its data structures grow. This causes performance issues and eventually, Wireshark may simply run out of virtual memory and stop capturing or crash. Product Line Andover Continuum, EcoStruxure Building Operation Environment Wireshark Cause Need to capture network traffic using Wireshark for an extended period of time. Resolution Open Wireshark and follow these instructions: From toolbar, select Capture -> Options On the Input tab, select input adapter. If necessary set capture filter. On the Output tab, perform the following: Browse capture file location and provide a filename. A timestamp will be added to the filename as a suffix. Ensure output format = pcapng Check Create a new file automatically Check After 1 and change seconds to hours Check when time is multiple of 1 and change seconds to hour Check use a ring buffer with X files. (Recommended settings are 96 hours (4 days) or 168 hours (1 week) so can retrieve files after long weekend or 1 week, respectively).  On the Options tab, perform the following Check last selection and change to 744 hours. (Recommended to capture for 31 days without stopping).  When an event happens, gather a capture with the timestamp before and after the event. One can ZIP the .pcapng files to save space when transferring.   NOTE: More recent versions of Wireshark ( 2.4.1.21317 ) make it very easy to set up a ring buffer from the Output tab of the Capture options. For older versions of Wireshark 1.x use the steps below When capturing data, Wireshark actually uses a capture utility called DumpCap to do the actual data capture. DumpCap does not decode packets as they come in and thus has a smaller memory footprint which remains constant. The only remaining concern is the size of the capture file or files which can be specified when starting the ring buffer to keep them from growing too big. DumpCap is found at the location where the Wireshark program resides which can be seen if you go to Help\About Whireshark\Folders Determine the index to the Ethernet adapter you need to capture on. In this example, the traffic seen by the Broadcom NetXtreme Gigabit Ethernet adapter will be captured. Index 1 is specified when starting DumpCap. Execute DumpCap with the following options dumpcap -i 1 -b files:3 -b filesize:10 -w C:]temp\abe.pcapng -i 1 specifies tp capture on the network adapter with an index of 1 -b file: 3 specifies to use a 4 file ring buffer. -b filesize:10 specifies to limit the file size to 10 KB (*** for a real life capture this number would be much bigger like say 100/200 MB) -w c:\temp\abe.pcapng specifies location and prefix for the three files In the screenshot below we can see the files in the ring buffer being used, once a file reaches the specified limit, the capture continues at the next file, files are names using the specified prefix as well as a date-time stamp that is updated each time utility dumps captured data in the file. Care should be taken to stop the capture as soon as possible once the issue under investigation takes place and before the ring buffer wraps around and overwrites the data.

Issue Script program Halts with error “Datetime calculation with overflow” resulting in the program not controlling Product Line EcoStruxure Building Operation Environment Observed in versions 4.0.1.86 and 4.0.3.176 Cause When a script program subtracts one datetime from another it can result in a negative value if the datetime being subtracted (subtrahend) is a later datetime than the one being subtracted from (minuend).  This causes the program to halt with error “Datetime calculation with overflow”.  The issue can also occur when a script program calls a function that involves a datetime subtraction resulting in a negative value, for example the standard PID function.   The image below illustrates the issue where DT1 is a later time than DT2.     The problem has typically been seen to occur when using the PID function and the ASP is set to obtain updates from an NTP server.  The PID function uses the current time and the last time the function was called to calculate the time passed, for example: -   TimePassed = CurrentDate – LastTime   Ignoring the date portion consider the scenario where the ASP time is currently 14:01:00 but is one minute ahead of the actual time of the NTP server.  If the function has just been called the LastTime variable will be 14:01:00.  However, in the meantime if the ASP time is updated by the NTP server it becomes 14:00:00 and hence when the function is called again the calculation is: -   TimePassed = 14:00:00 – 14:01:00    This results in a negative value halting the program on error “Datetime calculation with overflow”.   Resolution Either of the two workarounds below can be used but each will need to be considered based on their overall impact.    Use the DIFFTIME function If calling a function check the subtrahend is not a later datetime than the minuend before calling.   This is reported in defect #50263

Issue Satchwell FEU 4-port Unit Control Valve is obsolete. Product Line Field Devices Environment Satchwell FEU 4-port Unit Control Valve installations FEU4414 FEU4415 FEU4416 FEU4451 FEU4452 FEU4454 FEU4626 FEU4627 Cause Satchwell FEU 4-port Unit Control Valve requires replacement due to failure. Resolution Satchwell FEU 4-port Unit Control Valve may be replaced by Schneider Electric VZ419 series Unit Control Valve, although dimensional differences may apply.. It should be noted that VZ419 series Unit Control Valves are available in both Flat Face and Compression fitting specifications. The latest issue of the Schneider Electric Valves and Actuators Catalogue should therefore be consulted in order to determine the availability of the particular size / kv / fitting combination required.   It should also be noted that any Actuator installed on the Satchwell FEU 4-port Unit Control Valve will not be compatible with the replacement Schneider Electric VZ419 4-port Unit Control Valve and that a Schneider Electric MZ20 series Actuator of the appropriate operating voltage / signal type will also be required. 

Issue Error: 8000401a Retrieving the COM class factory for component with CLSID {2B768E20-89F2-11D2-99FD-00104B6D2299} failed due to the following error: 8000401a.Server process could not start because the configured identity is incorrect. Check username and password. (Exception from HRESULT: 0x8000401A).Code: -2147467238 When starting Vista Server, a fatal error happens: TACOS: COM Initializing failed, error code: -2147417831 Product Line TAC Vista Environment Remote desktop TAC Vista Windows 2008 Server or Windows 7 Cause When using Remote Desktop with a Windows 2008 Server and disconnecting, the TACOS process may end up in a "sandbox" and can not be reached by other people trying to log in remotely. Or, the Vista Server can't be started. Resolution The attached Tacos RDP Disconnect contains scripts that will disconnect a Remote Desktop session back to the physical session if tacos.exe is running. If tacos.exe is already running on the physical session or is not running at all, nothing happens.

Issue How can I add a SmartStruxure Automation Server to TAC Vista using BACnet/IP and what is needed Product Line TAC Vista, EcoStruxure Building Operation Environment TAC Vista Xenta 913 Automation Server Cause Building Operation versions earlier than 3.2 are not FDA 21 Part 11 approved, In instances where the version is lower than 3.2 it can be achieved by using  TAC Vista as a front end, and having Automation Servers as field controllers. In Building Operation version 3.2 and later an optional Regulated Industries Compliance Pack is available that can be used without the need for  TAC Vista as a front end. Resolution 1. Create a BACnet interface in Automation Server. 2. Create BACnet points in the "Application" folder 3. Browse the Automation Server with a BACnet browser (Here is a free tool) 4. Note the instance id's of the points 5. In TAC Vista, create a Xenta 913 6. Edit the Xenta 913 7. Create a "BACnet IP Client" interface and give it the IP address of the Automation Server 8. Create a BACnet device template containing the points you need - refer to the id's previously discovered 9. Add the device template to the "BACnet IP Client" interface in XBuilder 10. Save and download the project 11. Now you get the live values from the Automation Server in TAC Vista

Issue Needs to know how often Vista (or Xenta Servers) do online/offline polls for Modbus and MBus devices Product Line TAC Vista Environment Xenta Server Modbus Mbus Cause The devices may go offline for several different reasons. It's not possible to give a precise answer to this question, since it depends on your setup and the number of devices. Resolution In general, if a Modbus device has been detected as offline by the Xenta Server, it will wait 60 seconds until it tries polling that device again. That doesn't mean that a device will come online after 60 seconds if it has been offline because as described below, other factors comes into play, such as the number of devices and registers, and invalid registers. Mbus: The Mbus protocol is designed so that all information in the device will be received at every poll, regardless of what is defined in the device template. If the Xenta Server doesn't receive any information it will retry twice and if still no reply it will set the device to offline. All offline devices will be transferred to an offline queue in the Xenta Server, and at every new poll one device (the oldest) will be moved to the poll queue again. The reason for not retrying all is that if you have lots of devices that are offline at the same time, each poll would take very long time to complete and if using a short poll interval it may not be finished in time before the next poll. That will also mean that if you have many offline devices and have set a long poll interval in Xbuilder (default 1 min) it may take quite a while until all devices are online again. Note: In Xbuilder 5.1.9 and later it's possible to set the number of offline devices to poll each cycle. In some cases, for example when there are few meters and/or long poll times you may want to increase this number. Modbus/TCP: You will have a Server address for the TCP Client and if that server's ip address can't be reached all the Modbus devices below it will go offline. However as soon it can be reached again (will be tried constantly), it will scan all devices below it, and if they reply they will be set to online. If there's no response from a single device, it will retry twice before it's set to offline. The time it will take depends on the slave timeout setting in Xbuilder (default 3 seconds). As for Mbus, you have an offline queue where 1 device will be moved to the poll queue every poll cycle. The total poll time also depends on how many devices and registers you have defined (many devices/registers = longer poll time = longer time to detect if a device is offline/online). Modbus/RTU: It works similar to Modbus IP, except for the server part (which is not present). Besides that, you also have the "transmit delay" setting in Xbuilder (default 0 ms, max 1000 ms) which may effect the time it takes for a device to be reported as online/offline

Issue How to set the neuron ID of an I/O Module in a Vista classic network. Product Line TAC Vista Environment Vista Classic Network Xenta I/O modules Cause Xenta I/O modules beneath a base unit (300 or 400 series) do not show up in the Folder view tree structure.  You cannot right-click and set a neuron ID the same way you do for a base unit. Resolution Click on the Xenta base unit (300 or 400 series controller) in the tree structure. This brings up a list of modules inside the Menta file as well as two option modules that cannot be seen from the tree structure-- $IO and $LOGS. Double click the $IO module. All of the I/O modules defined in the Menta file are listed here.  Right-click, properties, to set the neuron ID.

Issue Downloading a license update, such as after adding features to a site license or extending the evaluation period on an evaluation license, and this fails with the below error being shown.   License not found Product Line EcoStruxure Security Expert Environment Security Expert Server Cause This error generally occurs when trying to license Security Expert from a Client and not on the Server. Resolution Go to the Security Expert Server and license/update the license from there.