Building Automation Knowledge Base

Issue The stop watch object operates erratically when set to days. If you set the stop watch to issue a pulse once a day it can issue a pulse 2 or 3 times during the day. Environment VisiSat Bubbleland Stopwatch   Cause Software/firmware error. No fix planned. Resolution When programming a stop watch do not use days. Instead of 7 days  use 168 hours  Instead of 14 days  Use 336 hours  If there is a requirement to convert the value back to a day for MicroNet View graphical representation, A suggested method follows: -   In VisiSat find the stopwatch object.  Add the Stopwatch Rollover to the VisiSat points list. Under the menu topic Tools Export your points list to MicroNet View.   In the MicroNet View project manager and load the new points. To view the hour value received from the controller as weeks on the graphical interface. Open MicroNet View in Development mode (Window Maker) Open the window that the value will be added too. Add some text to the Windows you want to display the value. For example “###” To view the rollover value, add the tag for the stop watch rollover value. To show the value as weeks add /24 after the tagname. Below is an example of both showing the results. This can be achieved using a data change script. In MicroNet Window Maker (Development mode) add a tag and data change script. The tag could look something like this. The minimum and maximum values of the tag can be changed to provide limits. The data change script could look something like this.  To display and allow the user to change the value in weeks. Add some text to the Windows you want to display the value. For example “###” Inside the "###" should be set for "user inputs Analog" (Analogue)  Click on "user inputs Analog and select the data change tag created earlier.  Using the example from above, the window will now look like this  To set the rollover in days click the days set area.  Change to the required amount of days. Hit the return key to enter the value.  The Rollover is now set to 14 days. It is important to remember the rollover value in the controller its not 14 it is the hour value 336. It is just at the MicroNet View front end/user interface window where it is displayed as days.

Issue As a part of the drive to improve information regarding our products, this document has been created to assist and clarify methods of connecting Touchscreens to newer and older series MicroNet controllers, and the controllers on the sub LAN under the Touchscreen unit. Product Line Satchwell MicroNet Touchscreen Environment Touchscreen wiring Cause Connecting MicroNet Touchscreen to microNet controllers. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Remote Mounted Touchscreen (NCP) Connected to MN550/MN650 Controllers. Fig.1  Fig.2 If the system has a front-end, or local interrogation is required, connection to the Touchscreen and its sub LAN should be done via LAN A of the Touchscreen. The address of the Touchscreen should start at 1/2. (See fig 3)  Fig. 3                                                                             Fig. 4 The sub LAN number, under the Touchscreen, is dictated by the address of the Touchscreen. We do not recommend the use of address 1 for Touchscreens, as this creates a sub LAN 1 under main LAN 1. The Touchscreen is supplied with 2 jumpers across the top two auxiliary connector pins. (See fig. 4) A visual check should be carried out to insure the jumpers, are fitted to the auxiliary pins and they have a good physical connection. Connection to controllers on the sub LAN is done via LAN B of the Touchscreen to LAN B of the other controllers on the sub LAN. If the option of an isolated LAN for the 50 series controllers on the sub LAN is to be utilised, then a separate 24 Volt power supply should be used to supply the Touchscreen. Touchscreen (NCP) Directly Mounted on MN550/MN650 Controllers.   Fig.5  Fig.6 If the system has a front-end, or local interrogation is required, connection to the Touchscreen should be done through LAN A of the controller the Touchscreen is mounted on. The address of the Touchscreen should start at 1/2. (See fig 7)  Fig. 7                                                                           Fig. 8 The sub LAN number, under the Touchscreen, is dictated by the address of the Touchscreen. We do not recommend the use of address 1 for Touchscreens, as this creates a sub LAN 1 under main LAN 1. The Touchscreen is supplied with 2 jumpers across the top two auxiliary connector pins. (See fig. 😎 A visual check should be carried out to insure the jumpers, are fitted to the two auxiliary pins and they have a good physical connection. The MN50-TS-NCP specification of the Touchscreen differs from other variants and only has these 2 pairs of pins. This is to allow the Touchscreen to mount directly onto the controller; the other auxiliary pins are not fitted when manufactured. The controller that the Touchscreen is to be mounted on must not have the jumpers fitted to the auxiliary pins. These are fitted at the factory, and should be removed. Connection to other controllers on the sub LAN should be done via LAN B of the base controller to LAN A of the other controllers on the sub LAN.  If the option of an isolated sub LAN, using 50 series controllers, needs to be fully utilised, the Touchscreen would need to be mounted remotely with a separate 24 Volt power supply. If the Touchscreen must be mounted directly onto a controller, that controller and the Touchscreen would not be fully isolated, but provided the Touchscreen /controller has a separate supply to the rest of the sub LAN, other controls on that sub LAN could be isolated. Remote Mounted Touchscreen (NCP) Connected to MN500/MN620 Controllers. Fig.9 Fig.10 If the system has a front-end, or local interrogation is required, connection to the Touchscreen and its sub LAN should be done via LAN A of the Touchscreen. The address of the Touchscreen should start at 1/2. (See fig 11) Fig. 11                                                                                 Fig. 12 The sub LAN number, under the Touchscreen, is dictated by the address of the Touchscreen. We do not recommend the use of address 1 for Touchscreens, as this creates a sub LAN 1 under main LAN 1. The Touchscreen is supplied with 2 jumpers across the top two auxiliary connector pins. (See fig. 12) A visual check should be carried out to insure the jumpers, are fitted to the auxiliary pins and they have a good physical connection. The controller on the sub LAN needs to have the jumpers fitted to the auxiliary pins. Connection to controllers on the sub LAN is done via LAN B of the Touchscreen to LAN B of the other controllers on the sub LAN. Touchscreen (NCP) Directly Mounted on MN500/MN620 Controllers.    Fig.13 Fig.14 If the system has a front-end, or local interrogation is required, connection to the Touchscreen should be done through LAN A of the controller the Touchscreen is mounted on. The address of the Touchscreen should start at 1/2. (See fig 15)  Fig. 15                                                                           Fig. 16  The sub LAN number, under the Touchscreen, is dictated by the address of the Touchscreen. We do not recommend the use of address 1 for Touchscreens, as this creates a sub LAN 1 under main LAN 1. The Touchscreen is supplied with 2 jumpers across the top two auxiliary connector pins. (See fig. 16) A visual check should be carried out to insure the jumpers, on the Touchscreen, are fitted to the auxiliary pins and they have a good physical connection. The controller that the Touchscreen is to be mounted on must not have the jumpers fitted to the auxiliary pins. Connection to controllers on the sub LAN should be done via LAN B of the base controller to LAN B of the other controllers. Caution to be taken when replacing an MN500 or MN620 controller if a Touchscreen is directly mounted on the unit. When replacing an MN500 or an MN 620 controller that has a Touchscreen directly mounted with a 50 series MN550 or an MN650 controller. The Touchscreen auxiliary pins 6 and 7 foul components on the controllers back plate, and will need to be cut. Pins 6 and 7 are identified in figure 17 below, will need to be cut close to the isolation strip A Once this modification has been carried out to the Touchscreen, the unit will no longer be suitable to run ARCnet communications. Fig. 17 An option would be to replace the Touchscreen at the same time as replacing the controller, with specification number MN50-TS-NCP. The MN50-TS-NCP specification of the Touchscreen has been modified, in production, starting Q2 2007, to allow direct mounting onto the MN500, MN 620, MN 550 and MN 650 controllers. Note: The 50 series controllers can be on the same LAN as the old 100 series of controllers. The LAN connections previously described, for the particular controller should be observed. Further information regarding these controller can be found in the product data sheets. See MicroNet 100 series controller MLi's and Data sheets See MicroNet 50 series controller MLi's and Data sheets

Issue When doing Xenta server to Xenta server communication, via other projects network, a good troubleshooting technique is to determine if the two Xenta servers are truly communicating to one other over TCP-IP. This is possible via the online status of the imported Xenta server in the project tree. Environment Xenta 511, 527, 555, 701, 711, 721, 731, and 913 Cause Two Xenta servers are set up to communicate to one another, but they are not passing data properly. Troubleshooting step number one should be to determine if the two Xenta servers are online to each other on the TCP-IP Resolution To  check the online / offline status of a Xenta server follow these steps: Login to the web browser of the Xenta server that that is configured to receive data. Navigate to the project tree similar to the image below. 3.  Within the project tree, browse down to the Xenta servers and check the online status as shown here:

Issue If there is an online selection tool for all the HVAC sensors (room temperature sensors, duct pressure sensors, etc.) Environment All Schneider Electric Buildings product lines Cause Since Schneider Electric manufactures a huge amount of sensors for different product lines. Sometimes it takes a bit of time to search for the right sensor. Therefore, Schneider Electric developed an online selection tool to help customer pick the right sensors. Resolution Click here to go direct to the online HVAC sensors selection tool. Select the desired features of the sensor. All sensors match the requirements will be displayed on the right. Datasheets can be accessed by clicking on the image or the part number. NOTE: the listed sensors may not be available in some region. Please contact the local sales or Support team to confirm the information.

Issue When attempting to start the programme an error indicating that the communications port is already open, is generated. Environment BAS 2800+ BAS2800+ Sigma Visisat Comms port open Comm 1 Cause The communications port is already being used by another programme. Resolution One of the most common programmes to cause this issue is Microsoft Active Sync, if this is found to be installed, either disable it or remove it if the programme is no longer required. The screen shot below shows the Active Sync connection settings window.   Ether change the Serial port number or de-select it. If Active Sync is not the problem, then disabling communications port 1 in the system Bios, may cause the programme to generate an error when it starts up. Once the programme is identified it can be disabled. The System Bios is accessed during start-up by pressing the F2 function key. You should then follow the on-screen instructions.

Issue When using the Generate project command in XBuilder the Generate output screen will not show any errors even though it reports an error was encountered or the error is visible but the info message indicating what it was trying to build the caused the error is not visible. Using the Window-> Restore Default Settings does not correct this. Environment TAC XBuilder Cause A filter has been applied to the Output window. Resolution Right click in the Output window and ensure that each of the following options are selected: Show Info Messages Show Warning Messages Show Error Messages

Issue A controller with only 2 available outputs is being used to control a 3 stage device. Environment Three stage device control where lower stages must remain active. Cause Hardware or space limitations may prevent there from being enough outputs to control a three stage device. Resolution Two controller outputs in conjunction with a DPDT (dual pole, dual throw) relay can be configured to control a three stage device. This will allow you to activate stage 1, stages 1 and 2 or all three stages by activating either one or both of the controller outputs. An example of when this might be used is to control three stages of heat or a three stage fan. A standard "ice cube" type relay can be used (IDEC RH2B or similar) and should be wired as shown in the diagram below.   The controller should be programmed to activate only output 1 for stage 1, activate only output 2 for stages 1 and 2 and finally to activate both outputs for stages 1, 2 and 3. Note that certain application specific controllers may not allow the outputs to be configured in the way described above and thus cannot take advantage of this setup.

Issue Modbus slave device only supports function code 10 hex/16 dec for writing of holding registers. Environment Xenta 913 Xenta 701/711/721/731 Xenta 511/527 Cause In system program 5.1.4 a trigger was added to the Xenta Server software that enables the device to use only the Multi-Register function code. This command is executed from the console port or from the VXI web shell command webpage. VX M 1 = Enable Multi-Register write VX M 0 = Disable Multi-Register write VX M = Display current status of the trigger Note: This setting is persistent on the unit until the firmware has been reloaded. If the unit is upgraded the setting will need to be reapplied. Resolution Log In to the webpage of the Xenta Server Access the Utilities\Target System\VXI Web Shell Commands webpage. Issue a "VX M" command to display the current status. Issue a "VX M 1" to enable the multi register write command option. Some of the Xenta Servers with recent Modbus support do not have the VXI web shell commands web page and the console will need to be used instead. The VXI web shell commands web page should be available in firmware 5.1.6.

Issue GSM modem does not send text message when an alarm is generated. Environment Sigma BAS 2800+ Micronet Vista Cause Remote Alarm Manager configuration is incorrect. Resolution Check the recipient configuration to ensure that the selected interface is correct.

Issue The Remote Alarm Manager shuts down during use, or cannot be restarted. Environment Sigma BAS 2800+ Vista Micronet Remote Alarm Manager RAM Cause The Log.mdb file becomes too large, and uses excessive memory, this can cause the RAM Engine to shut down. Resolution The Log.mdb can record all system alarms, user actions and the actions that RAM is taking. This file will increase in size and has no restrictions on how big it can get. How fast it increases in size will depend on the logging requirements set in the configuration. This file needs to be managed, and this is achieved as follows: 1 - If the system is running without any problems, then this file should be deleted or renamed on a regular basis. To do this stop the RAM services and locate the Log.mdb record (For Sigma it is most likely located in Sigma\Data\Remote Alarm Manager), and delete / rename it. Restarting the RAM services will recreate a new file. 2 - Ensure that all logging is set to its most infrequent setting. The above screen shot shows the "Debugging" screen for the "GSM Modem" interface. In this instance, logging has been set to "Nothing", but there are four other options. 1 - Errors - Only errors are logged. 2 - Normal - Only low level information is recorded,. 3 - Detailed - More in depth information is stored. 4 - Verbose - All information is logged. If RAM is operating correctly, then choosing either Nothing or Errors, would be appropriate.

Issue What is the wiring for the RS-232 A, RS-232 B, RS-485 A, RS-485 C, and 10Base-T ports on a Xenta Server? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 BACnet/IP BACnet MS/TP M-Bus C-Bus Lon Modbus Cause The wiring and pin outs for the Xenta Server hardware is detailed in chapter 2.1.2 of the TAC Xenta 500/700/911/913 Product Manual . Resolution The ports and wiring is unique for each port. RS-232 A port For serial communication it is typical to only connect the RX, TX, and Ground pins. Pin 3 4 5 Serial Cable RX TX Ground  RS 232 B port   10 Base-T port (Web connection) Note: The Xenta 913 also supports BACnet/IP and Modbus TCP/IP on this port. RS 485 A port (Modbus) Note: The Xenta 913 also supports BACnet MS/TP on this port. If two wire communication is being used then only use pins 5 and 6. Pin 5 6   + - If four wire communication is being used then all four pins will be used. Pin 5 6 7 8   TX + TX - RX + RX - RS485 C port (I/NET) This port is used for I/NET communication. Pin 19 20   + -

Issue Making connections in Xbuilder for graphics, connection objects, alarms, Menta programs, or trends can be tedious due to the organization and tree structure of the System pane window. Do logical units in the system pane have to be used when making bindings? Environment Xbuilder 5.0.2 - 5.1.x Cause Both logical and physical objects can be linked (though some unit issues might cause one method to be preferable to another) to graphics, alarms, connection objects, Menta programs, and  trends. With the use of the Filter View the system and network pane can be presented in a single window filtered to only display objects which work together. Use of the Filter View will provide a user friendly connection process that avoids the need for users to scroll up and down the system pane to drag and drop signals. The filter view toolbar also provides the ability to fix the view and connect objects without having to drag and drop them into the system pane. The Filter View is only available in Xbuilder version 5.0.2 or higher. Resolution Highlight the object you want to make a connection with in the System Pane. Select the Filter View tab in the middle pane. Select the signal from the combined list of System and Network panes. Use the Connect button on the Filter View toolbar to finish the connection.

Issue  To convert a 0 - 20 mA signal into an acceptable form to be used into a variety of controller types. Environment Sigma BAS Micronet X96 controllers X32 controllers IAC controllers Micronet controllers Cause Some controllers will not accept a 0 - 20 mA signals and therefore the signal must be converted. Resolution To achieve this conversion, please follow the instructions below. Install a 500 ohm 0.1% resistor in series with the 0 - 20mA signal. From across the resistor, take the signal to the controller . The Universal Input or Analogue Input should be set as a standard voltage input.

Issue Configuration instructions for setting up a communications VX Log in the Xenta 5/7/9xx for communications troubleshooting. Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 VXI Cause Configuration instructions for setting up a communications log in the Xenta 5/7/9xx for communications troubleshooting. Obtaining the communications log for a Modbus or BACnet network is crucial in finding communications errors, or other unforeseen problems with integrating to third party devices. Resolution Step by step instructions for creating the communication log for troubleshooting or for data analysis: Log In to the Xenta 5/7/9xx controller and navigate to the Utilities Folder:   Click on the Target System Folder and choose VXI Web Shell Commands:   The command line should appear with VX populated in the command line:   Logging to file in the Xenta controller will first need to be enabled to by typing VX L 1 and press submit:   VXI Web Shell Commands should return a messing indicating logging has been enabled for 1 hour:   After logging has been enabled, the verbosity will need to be set in order to capture each layer of communications on the wire. In the command line type VX V 9 and press submit:   VXI Web Shell Commands should return a messing indicating the verbosity has been set to 9 and what messages you will see with this verbosity level :   Let the communications log run for 5-10 minutes. Create as many changes on the 3rd party wire as possible to get various data changes to and from the Xenta Server.   In the command line type VX O and press submit:   This command will output the communications log the Xenta Server has collected. Highlight this entire output log and copy, then paste it into notepad for archiving or emailing:   To set the communication logging back to default type "vx V 1" or power cycle the Xenta Controller. To stop the logging to file, type "vx L".   For TCP/IP logging you can only monitor one client at a time: Complete Steps 1- 8 above Enter "vx d" This will display a list of the TCP available devices Enter vx d # where # is the number corresponding to the deice you wish to monitor To view the log, follow steps 9 and 10 above

Issue After upgrading a site that contains MicroNet or IAC controllers from SBO to EBO the time Schedules no longer display time periods entered. Product Line EcoStruxure Building Operation Environment Building Operation Workstation (from v2.0.1) Building Operation WebStation (from v2.0.1) Building Operation Enterprise server (from version 2.0.1) Building Operation Automation Server (AS Classic from v2.0.1 to v3.1 and AS-P from v2.0.1) Cause From EBO 2.0.1 release includes support for MicroNet time and holiday schedules in WebStation, to achieve this the existing SBO schedules have been replaced by a TGML graphic for both WebStation and WorkStation. Resolution To enable the new schedules, run the Data Importer on each MicroNet interface, this will add new TGML schedule objects for all existing MicroNet and IAC Time and Holiday schedules. Before upgrading. After upgrading. Carry out a Data import. After the Data import, then the associated TGML graphics can be seen. Further information is available in the EBO 2.0.1 release note. The graphic creation is confirmed in the trace information presented when Data importing: The trace will be sent to: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation n.n\DataImport\Trace.DataImport.MicroNet Interface.txt and the following is seen: Source: C:\Satchwell\Projects Full URL: C:\Satchwell\Projects Processing XML... Committing to server... Creating object editor graphics (3) ... Object editor graphics created

Issue The Exchange Download Center contains all of the assets you once accessed through the Buildings Extranet are now available on a brand new platform. It's easy to search and fast to download. Stay tuned for more great features as we roll this into the all-new extranet solution for Buildings. We ask that you register for a new account on The Exchange.   Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Exchange Download Center Cause You can utilize the new Buildings web experience from The Exchange. Resolution Navigate to https://ecoxpert.se.com/ * Use a modern browser for the best experience: Google Chrome, Mozilla Firefox, Microsoft Edge, and Microsoft Internet Explorer version 8 or later. If you receive the following error in Internet Explorer despite using version 8 or later, the browser displays the page in Compatibility View. Click here for more information on Compatibility View and how to disable it. The Download Center will not function properly in Compatibility View.   On the header bar, you will see the option in the top right corner for “Login / Register.” Click it.   If you are already registered, enter your email address and password. If this is your first time registering, click the link for “New to the Download Center? Register here!”   Answer whether or not you are a Schneider Electric employee using the radio buttons. If you are a Schneider Electric employee, enter your SESA ID and your desired password for The Exchange. Click to accept Schneider Electric’s Terms and Conditions and hit “Create Account.” * The first time you register, you must be connected to the Schneider Electric network or connected via VPN. This is only required at registration. All future logins can be done externally. If you are not a Schneider Electric employee, enter your first name, last name, company name, location, business email address, and desired password for The Exchange. * It is important to use your business email address if you are a licensed partner. Your email address is used to automatically validate your Partner status and assign the correct permissions to your user profile.   An email is sent to your designated inbox with a link to click through and validate your email address. Once this is done, your login is created, and you are ready to start using the Download Center. * If an error is displayed when trying to validate your authentication code, please try to log in. This happens when an email address has already been verified and oftentimes does not indicate an error with the registration.   Once logged in, you can search and download assets available to your user profile. If you attempt to download a file that you do not have access to, you will be given a chance to report if this is in error. Your username, email, and the asset you are trying to access are recorded. Please enter a message if any further description is required and hit “Submit.” A member of our team will get back to you promptly with a resolution. Web Site Support For any issue regarding The Exchange Download Center, please contact us at exchangesupport@schneider-electric.com.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Using the ribbon cable provided with the Satchwell MicroNet Touchscreens & Satchwell MicroNet LCDs to supply power from a MicroNet 50 series controller that is powered with 24VDC. Product Line Satchwell MicroNet Environment Satchwell MicroNet Touchscreens Satchwell MicroNet LCDs Satchwell MicroNet 50 series controllers Cause The Satchwell MicroNet 50 series controllers were built on new hardware. MN350-ARC, MN350-NCP, MN350-LON MN450-ARC, MN450-NCP, MN450-LON MN550-ARC, MN550-NCP, MN550-XCOM, MN550-LON MN650-ARC, MN650-NCP, MN650-XCOM, MN650-LON This new 50 series hardware design added support to the controller to be powered by 24 VAC or 24 VDC The Satchwell MicroNet Touchscreens & Satchwell MicroNet LCDs displays used an adaption of the 100 series hardware, which does not support being powered by 24VDC. Resolution The MicroNet 50 series range MN350, 450, 550, 650 LCD, and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. When using a Satchwell MicroNet Touchscreens or Satchwell MicroNet LCDs on Satchwell MicroNet 50 series controllers that are being supplied with 24VDC, the ribbon cable cannot be used to supply the Satchwell MicroNet Touchscreens or Satchwell MicroNet LCDs with power. A separate 24VAC transformer should be used to power the Satchwell MicroNet Touchscreen or Satchwell MicroNet LCD. The MicroNet 50 series controller MLi's and Datasheets are available to download by searching for the article “MicroNet 50 series controller MLi's and Datasheets” The MicroNet 100 series controller MLi's and Datasheets are available to download by searching for the article “MicroNet 100 series controller MLi's and Datasheets”

Issue Faulty operation of BMS equipment due to electrical interference from other equipment can be difficult and costly to identify and fix.  Guidance is required for the best installation practices to minimize the source of the interference and to protect against it when it occurs. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment All electrical equipment Cause Poor installation can cause equipment to generate high and low-frequency electromagnetic interference that can disrupt the operation of other systems. Resolution Schneider Electric has produced a document Practical Installation Guidelines which discusses the theory and offers practical guidelines to protect against and minimize the generation of, electromagnetic interference.

Issue What utility in Windows XP can disable items in Startup? Environment Windows XP Cause Items that run on startup can sometimes make the boot up process for a PC very slow. Depending on which applications have been added to start automatically on startup, it can also cause problems if things load in the incorrect order. Resolution Click the Start button in Windows XP Select Run Type msconfig and click OK.

Issue How to find the IP address information on a PC? Environment Windows Operating Systems Cause Need to identify the IP address of the workstation (PC). Resolution For a Windows 95/98 PC, go to a DOS screen and run WINIPCFG. For a Windows NT / XP / Windows7 / Server 2008 PC, run a CMD window and run IPCONFIG.