Building Automation Knowledge Base

Issue Graphics appear fine when viewed from WorkStation, but when a web browser (WebStation) is used to view the AS, dark lines appear across portions of the graphic. Some objects with transparent backgrounds (fill set to "None") may appear with a grey background when viewed through a web browser. Product Line EcoStruxure Building Operation Environment AS TGML Graphics WebStation Cause WebStation is less forgiving of some improper configuration settings than WorkStation. Objects attributes must follow proper syntax for Fill, Stroke, or Visibility. Resolution Open the graphic page in the TGML viewer Change lines, borders, and fills to some other value (black, for example) Change the attribute back to the desired setting (Visibility = Hidden or Fill = None) Save the graphic The improperly formatted attributes should be overwritten with the correct syntax and the graphic appears as desired in both environments.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue When EBO servers (ES & AS) no more need to keep the unnecessary TrendLog objects, the obsolete objects need to be deleted from EBO servers, and their log data need to be removed from the Extended Log Storage (PostgreSQL/TimescaleDB) server as well.  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server External Log Storage PostgreSQL (pgAdmin 4) TimescaleDB  Cause Deleting the obsolete TrendLog objects from EBO servers does not remove the old log data of the obsolete TrendLogs left in the PostgreSQL/TimescaleDB database. Resolution Once the obsolete TrendLog objects are deleted from EBO servers, their log data are no longer saved in the PostgreSQL/TimescaleDB. The next task is removing the old log data left in the PostgreSQL/TimescaleDB database.   1. As always, backup current EB & AS’s databases from EBO workstation.   2. As always, backup the current PostgreSQL/TimescaleDB database and save to a safe location. Backup the “ebo_db” from the PostgreSQL/TimescaleDB server using the pgAdmin 4 (refer to https://www.pgadmin.org/docs/pgadmin4/development/backup_dialog.html , or refer to page 8 “Backup” section of the “EBO External Log Storage Installer.pdf” document for detail).  3.Remove the obsolete TrendLog from the PostgreSQL/TimescaleDB database (the “ebo_db”). Method_1: Delete the EBO TrendLog object from ES & AS’s & TimescaleDB using EBO workstation. (1) From the EBO workstation, expand the folder (location) of the TrendLog object, and delete the TrendLog object. (2) From the EBO workstation, go to the TimescaleDB folder (/Server 1/System/External Log Storage/TimescaleDB/Trend /Logs/Tree View), and delete the Trendlog object from PostgreSQL/TimescaleDB database. (3) Verify the TrendLog disappears from both the EBO and the PostgreSQL/Timescale DB.   Method_2: If the above Method1 takes a long time to complete, you can delete the TrendLog objects from PostgreSQL/TimescaleDB database directly.  (1) From the EBO workstation, expand the folder (location) of the TrendLog object, and delete the TrendLog object. (Same as item (1) of the above Method_1) (2) From the PostgreSQL/TimescaleDB server, run the pgAdmin 4, select the “ebo_db”, open the “Query Tool”, and execute the below scripts: Find the ID of the obsolete TrendLog from the trend_meta table. Select Externallogid, source from trend_meta where sources like '%TrendLog Name or Path%' Remove the TrendLog from the 2 tables using the above found Externallogid as below. Delete from trend_data where externallogid = 1234567890 Delete from trend_meta where externallogid = 1234567890 (3) Verify the TrendLog disappears from both the EBO and the PostgreSQL/Timescale DB.  

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue After deleting unnecessary TrendLog objects from EBO and their logged data from the Extended Log Storage (PostgreSQL/TimescaleDB) by selecting the “Clear log” from the System folder (i.e.: Server1/System/Extended Log Storage/TimescaleDB/Trend/Tree View/…”), the Windows still shows the same free disk space size as it was before the deletion. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server External Log Storage PostgreSQL (pgAdmin 4) TimescaleDB  Cause PostgreSQL databases require periodic maintenance known as vacuuming for Windows to recover or reuse the freed-up disk space occupied by PostgreSQL/TimescaleDB. Resolution There are two variants of VACUUM: standard VACUUM and VACUUM FULL.  VACUUM FULL can reclaim more disk space but runs much more slowly.  VACUUM FULL requires an exclusive lock on the table it is working on, and therefore cannot be done in parallel with other use of the table. Refer to the documentation mentioned at  https://www.postgresql.org/docs/9.5/routine-vacuuming.html  before performing the VACUUM command.   Below is an example of the procedure to get the freed-up disk space occupied by PostgreSQL/TimescaleDB back to Windows.   1. Back up the current PostgreSQL/TimescaleDB database and save to a safe location. Backup the “ebo_db” from the PostgreSQL/TimescaleDB server using the pgAdmin 4 (refer to https://www.pgadmin.org/docs/pgadmin4/development/backup_dialog.html , or refer to page 8 “Backup” section of the “EBO External Log Storage Installer.pdf” document for detail).   2. Stop the External Log Storage from EBO. Open the Properties of the TimescaleDB object (/Server/System/External Log Storage/).\ Remember (take a note) the current value settings of the “Host Address” & the “Database Name” attributes. Change them to the wrong value (or clear them) so that EBO fails to connect to the PostgreSQL/TimescaleDB server. Repeat the above operation for all the other servers (AS’s) that are enabled/connected to the PostgreSQL/TimescaleDB server.   3.Delete the old logs from the PostgreSQL/TimescaleDB database (the “ebo_db”). Run the pgAdmin 4, select the “ebo_db”, open the “Query Tool”, and execute the below scripts:   Delete from trend_data where DATE_PART('day', now() - timestamp) > 365   Delete from event_data where DATE_PART('day', now() - timestamp) > 365   4. Vacuum the Database with Full option. From the same Query Tool on the “ebo_db”, run the below command: Vacuum Full Wait until it completes (this may take a while depending on the number of old logs that have been deleted from the tables).   5. Start the External Log Storage from EBO. Open the Properties of the TimescaleDB object (/Server/System/External Log Storage/). Set the value of the “Host Address” & the “Database Name” back to the correct value, so that the EBO server successfully connects to the PostgreSQL/TimescaleDB server. Verify the EBO server is connected to the PostgreSQL/TimescaleDB server, and it works normally.    Repeat the above operations for all the other EBO servers (AS’s) that were disabled/disconnected from the PostgreSQL/TimescaleDB server.  

Issue What resources are available to get more information on the Modbus protocol? Product Line Andover Continuum,EcoStruxure Building Operation,Field Devices,Satchwell BAS & Sigma,Satchwell MicroNet,TAC IA Series,TAC INET,TAC Vista Environment Modbus ASCII/RTU Modbus TCP/IP Cause The Modbus protocol information is available on www.modbus.org Use the menu on the left and select Technical Resources. Select the Modbus Specifications. Resolution Found on www.modbus.org are the protocol specifications: Modbus ASCII/RTU Modbus TCP

Issue VTRA Valve Body requires replacement due to obsolescence. Product Line Field Devices Environment VTRA 3-port Mixing Valve Body Cause Obsolescence of VTRA Valve Body Resolution VTRA Valve Bodies are obsolete and have been for many years. VTRA Valve Bodies were available with either Flanged or Screwed connections.  Details of the various size / connection combinations available appear VTRA Specification Sheet. REPLACEMENT OF VTRA FLANGED CONNECTION VALVE BODY A replacement for the VTRA Flanged Valve Body (32-80mm) may be selected from the VTRE range of Flanged Valve Bodies, see VTRE S-E Specification Sheet for more datails. N.B. It should be noted that the VTRE Valve Body is rated PN6 whereas the VTRA was rated PN10. The VTRE Flanged Valve Body may be operated by the EM9 Actuator, see Alternatively the VTRE Flanged Valve Body may be operated by the M9B Actuator, See EM 9 Specification Sheet for more details. No Linkage Kit is required to mount the EM9 or M9B Actuator on the VTRE Valve Body. Alternatively a replacement for the VTRA Flanged Valve Body (65-80mm only) may be selected from the the S-E VG311F and V321 3-Port Flanged Valve Bodies, more details can be found in the Venta VG311F 65-150C Specification Sheet and the Venta V321 Specification Sheet N.B. It should be noted that the S-EVG311F and V321 Valve Body are rated PN16 whereas the VTRA was rated PN10.   REPLACEMENT OF VTRA SCREWED CONNECTION VALVE BODY A replacement for the VTRA Screwed Valve Body (15-50mm) may be selected from the MB range of Screwed Valve Bodies, see the MB/MBF data sheet for more details. The MB Screwed Valve Body may be operated by the MD10B series Actuator, see the MD10B specification sheet for more details. Alternatively the MB Screwed Valve Body may be operated by the MD10A Actuator, see the MD10A specification sheet for more details.  

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 How to define the number decimal places displayed for a point? Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The default resolution for displaying points is 2, there is no setting to change this in individual points on the Workstation. Resolution The number of displayed decimal places is read from the Workstation PC Windows Region Options, change or customize the Windows Options to set the "No of digits after decimal" value as required. This setting applies to all displayed values except for graphics where the number of digits displayed can be defined in the graphic editor. Control panel\Region\ Select Additional Settings opens Customize Format. Adjust "No. of digits after decimal to your requirements".   The Workstation will need to be restarted for this setting to be changed. The screenshot below shows a setting of 2 decimal places, Windows allows the value to be changed from 0 through 9:

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