AdeptWindows Installation Guide - Adept · PDF fileAdeptWindows Installation Guide Version 3.0 ... Adept NanoStage L3, ... AdeptWindows Installation Guide 4 TROUBLESHOOTING

AdeptWindows Installation Guide Version 3.0

August 2006

Part Number: 00971-07401 Rev A

AdeptWindows Installation Guide

2

Adept Technology, Inc., Copyright Notice

The information contained herein is the property of Adept Technology, Inc., and shall not be reproduced in whole or in part without prior written approval of Adept Technology, Inc. The information herein is subject to change without notice and should not be construed as a commitment by Adept Technology, Inc. The documentation is periodically reviewed and revised.

Adept Technology, Inc., assumes no responsibility for any errors or omissions in the documentation. Critical evaluation of the documentation by the user is welcomed. Your comments assist us in preparation of future documentation. Please submit your comments to: [email protected].

Copyright © 1996 – 2003, 2006 by Adept Technology, Inc. All rights reserved.

The Adept logo, AdeptVision, AIM, HexSight, and HexaVision are registered trademarks of Adept Technology, Inc.

ActiveV, Adept, Adept 1060, Adept 1060+, Adept 1850, Adept 1850 XP, Adept 540, Adept 560, Adept C40, Adept C60, Adept CC, Adept Cobra 550, Adept Cobra 550 CleanRoom, Adept Cobra 600, Adept Cobra 800, Adept Cobra i600, Adept Cobra

i800, Adept Cobra s600, Adept Cobra s800, Adept DeskTop, Adept Digital Workcell, Adept FFE, Adept FlexFeeder 250, Adept IC, Adept Impulse Feeder, Adept LineVision,

Adept MC, Adept MV, Adept MV-10, Adept MV-19, Adept MV4, Adept MV-5, Adept MV-8, Adept NanoBonder EBS, Adept NanoBonder LWS, Adept NanoCell, Adept

NanoStage L1P2, Adept NanoStage L3, Adept NanoStage L3P2, Adept OC, Adept SmartAmp, Adept SmartAxis, Adept SmartController CS, Adept SmartController CX,

Adept SmartModule, Adept SmartMotion, Adept SmartServo, Adept sDIO, Adept Servo Kit, Adept sMI6, Adept SMIF-EZ, AdeptAlign 650, AdeptAtlas, AdeptCartesian, AdeptForce, AdeptFTP, AdeptGEM, AdeptModules, AdeptMotion, AdeptMotion Servo,

AdeptMotion VME, AdeptNet, AdeptNFS, AdeptOne, AdeptOne-MV, AdeptOne-XL, AdeptRAPID, AdeptSix 300, AdeptSix 300CL, AdeptSix 600, AdeptTCP/IP,

AdeptThree, AdeptThree-MV, AdeptThree-XL, AdeptTwo, AdeptVicron, AdeptVicron 300S, AdeptVicron 310D, AdeptVision AVI, AdeptVision AGS, AdeptVision GV,

AdeptVision I, AdeptVision II, AdeptVision VME, AdeptVision VXL, AdeptVision XGS, AdeptVision XGS II, AdeptWindows, AdeptWindows Controller, AdeptWindows DDE,

AdeptWindows Offline Editor, AdeptWindows PC, AIM Command Server, AIM Dispense, AIM PCB, AIM VisionWare, A-Series, AutoCal, AutoTune, AutoWidth, CCM, CCMII, CGM, FlexFeedWare, HyperDrive, Microenvironment, MicroV+, MotionWare, ObjectFinder, ObjectFinder 2000, PackOne, PalletWare, SMIF-C, SMIF-EZX, SMIF-Z,

SMIF-ZX, S-Series, UltraOne, V, V+, and VisionTeach are trademarks of Adept Technology, Inc.

Any trademarks from other companies used in this publication are the property of those respective companies.

Printed in the United States of America


3

Table of Contents

OVERVIEW................................................................................5

What's New? ......................................................................................5

System Requirements .........................................................................5

PC Requirements ........................................................................................5 Adept Controller Requirements .....................................................................6

Adept MV Controller Requirements......................................................................... 6 Adept SmartController Requirements ..................................................................... 6

Network Requirements ................................................................................6

How Do I Begin?.................................................................................7

Which Connection Method Should I Use?........................................................7

How Can I Get Help? ...........................................................................7

INSTALLING THE SOFTWARE ....................................................8

To install AdeptWindows:.....................................................................8

To install the Omni-NFS Server Software ...............................................8

Configuring the Omni-NFS Server .........................................................9 Step 1 ......................................................................................................... 9 Step 2 ......................................................................................................... 9 Step 3 - Windows 95/98 Users Only ......................................................... 11 Step 3 - Windows NT/2000/XP Users Only............................................... 11

Installing the AdeptWindows License ................................................... 14

SETTING UP A SERIAL CONNECTION.......................................15

Required Cabling .............................................................................. 15

Hardware Connection ........................................................................ 15

Configuring the Serial Protocol ........................................................... 15

WORKING WITH ETHERNET ....................................................16

A Note on IP Addresses ..................................................................... 16

The Default IP Address ..............................................................................16

Required Interface Hardware.............................................................. 17

CONFIGURING YOUR SYSTEM .................................................18

Using the Controller Network Configuration Utility................................. 18

Configuring One PC and Controller Using Default IP Address .................. 19

Configuring One PC and Controller With User-Assigned IP Address.......... 21


4

TROUBLESHOOTING................................................................24

General Startup Problems .................................................................. 24

Energy Star Compliant Systems.......................................................... 24

Serial Communications ...................................................................... 24

Ethernet Communications .................................................................. 24

Using PING to Test the Ethernet Setup ........................................................24 Pinging the Adept Controller................................................................................ 24 Pinging the PC................................................................................................... 25

Connecting to an Adept Controller Through TCP/IP........................................25 NetManage's TCP/IP........................................................................................... 25

Other Ethernet Problems ...........................................................................25 More Ethernet Troubleshooting Resources....................................................26

PC or Adept Controller Problems ......................................................... 26

PC or Windows Program Problems...............................................................26 Adept Controller Problems..........................................................................26

V+ License....................................................................................... 26


5

Overview The AdeptWindows quick installation guide is intended to get you up and running the AdeptWindows software as quickly as possible, making only the necessary connections and configurations. For detailed or more advanced setups, refer to the AdeptWindows online documentation.

What's New? Version 3.0 contains the following new features:

Connect button added to the Scan Ethernet window.

In previous versions of AdeptWindows, you were required to write down the desired IP address and then enter it in the V+ Cell Address dialog box. AdeptWindows version 3.0 allows you to simply select the desired IP address and press the new Connect button to connect to the selected system.

Controller Network Configuration Utility

The Controller Network Configuration Utility simplifies the process of bringing up a new Adept controller. It allows you to set the IP address (and subnet mask) of the Adept controller regardless of the current IP address of the controller and of the PC.

Vision improvements

Vision window appends the text "(LIVE)" to the title bar when live video is displayed.

For V+ 14.2 and later, V+ no longer transmits video when the Vision window is closed.

When V+ detects missing video data, it gradually reduces the video transmission rate until no video data is missing.

System Requirements The AdeptWindows software runs on Windows 95/98 and Windows NT 4.0/2000/XP. Unless noted, the term “Windows” refers to these operating systems.

Note: When installing the Omni-NFS Server product on a Windows XP system, you will need to perform additional configuration steps. See page 11 for details. Additionally, you will need to disable the Windows Firewall, to allow communication with the Adept controller. See your Windows documentation for details.

The AdeptVision image is not supported by the serial option. However, vision graphics are displayed on the PC.

PC Requirements

In order to use AdeptWindows, a PC should be configured as follows: IBM-compatible PC with a processor capable of running Windows® 95/98 or

Windows® NT/2000/XP. Windows 95/98 or Windows NT 4.0/2000/XP operating system. (Windows

95/98 requires the Microsoft Windows Installer 2.0 update for the MSI-based software installer, which is available from the Microsoft website.)

500 Mb hard disk (recommended minimum, more may be required for your version of Windows).

Minimum of 16 Mb RAM (more memory may be required to run Windows NT/2000/XP).

SVGA monitor.


6

CD-ROM drive. AdeptWindows Kit (includes AdeptWindows CD, Ethernet crossover cable,

Online Help, and the AdeptWindows Installation Guide). AdeptWindows version 3.0D2 or later is recommended for use with the SmartController.

For the Ethernet option, the PC requires an Ethernet card, and an Adept-supplied crossover cable or user-supplied networking hardware (cabling, hub, wireless node, etc.). CAUTION: If the Adept-supplied crossover cable is used, it must be directly connected between the PC's Ethernet card and the Adept controller. DO NOT mix the crossover cable with user-supplied hubs or cables.

For the serial option, a serial-interface cable is required. Adept Controller Requirements

In order to use AdeptWindows, an Adept controller should be configured as follows: NOTE: If the PC has Windows 2000 SP3 or Windows XP, the following V+ system versions (or later) are required: 13.0 edit G3, 13.1 edit K1, 13.2 edit E5, 13.3 edit A3, 14.0 edit K5, 14.1 edit B8, 14.2 edit C8, 15.0 edit E, 15.1 edit B5, 15.2 edit A, 16.x.

Adept MV Controller Requirements

V+ 13.0 or later (V+ 13.2 or later is required to run the Controller Network Configuration Utility).

An AWC-II board. An AdeptWindows license on the controller. For the Ethernet interface, the AdeptNet license must be enabled. For the serial option, a serial link between the PC and the Adept controller is

required. This link uses the serial RS-232/Term port, located on the AWC board.

Adept SmartController Requirements

CompactFlash supplied by Adept that is preloaded with the V+ OS. V+ 15.0 edit D or later. An AdeptWindows license on the controller. User-supplied 24VDC power supply. Refer to "Connecting Power" in Chapter 2

of the Adept SmartController User's Guide. For the Ethernet interface, the AdeptNet license must be enabled.

NOTE: The serial option is not supported on the Adept SmartController.

Network Requirements

AdeptWindows users should be aware that a fixed IP address is required for both the PC and the Controller. Typically, IP addresses are allocated by your IT department.


7

How Do I Begin? Before you can use AdeptWindows, you must complete the following steps:

1. Install the Adept controller. 2. Install AdeptWindows on your PC. 3. Install the AdeptWindows license on the Adept controller. 4. Set up a serial or Ethernet connection. 5. Start the AdeptWindows program(s).

Which Connection Method Should I Use?

Which method is best for you? Choose one of the following PC setups and follow the recommended procedure.

Your PC Setup Recommended

User Interface and Connection

Notes Recommended Procedure

PC has an Ethernet card and already has an assigned IP address.

AdeptWindows PC throughEthernet connection using user-assigned IP address in SmartController

Preferred and most common setup.

Page 21

PC has an Ethernet card but doesn’t have an IP address configured.

AdeptWindows PC throughEthernet connection using default IP address in SmartController

A common setup for SmartControllers with standalone PC’s (i.e., not on a corporate network).

Page 19

PC does not have an Ethernet card, or you’re having difficulty connecting through Ethernet.

HyperTerminal through an RS-232 Serial connection

Useful for troubleshooting. Not useful for development - does not allow Vision windows.

See the SmartController User's Guide, section 3.6

How Can I Get Help? Refer to the How to Get Help Resource Guide (Adept P/N 00961-00700) for details on getting assistance with your Adept software or hardware. Additionally, you can access the information sources on Adept's corporate web site: For Contact information: http://www.adept.com/contacts/ For Product Support information: http://www.adept.com/services/ For further information about Adept Technology, Inc.: http://www.adept.com


8

Installing the Software The AdeptWindows software for the PC is distributed on CD-ROM. The media contains an installation program to properly install the software on the PC. The following programs will be installed:

AdeptWindows PC AdeptWindows Offline Editor AdeptWindows DDE Server AdeptWindows TFTP Server Omni-NFS Server (optional) Controller Network Configuration Utility AdeptWindows Online Help AIM Online Help

After installation, each of these programs can be started from the Start menu bar in Windows.

To install AdeptWindows: 1. Insert the AdeptWindows software CD-ROM into the CD drive of your PC. 2. If AutoPlay is enabled, the Welcome to AdeptWindows menu is automatically

displayed. 3. If AutoPlay is disabled, you will need to manually start the CD-ROM. Use

Windows Explorer to browse to your CD-ROM drive, right-click on the drive, and select AutoPlay from the menu.

4. Click Read Important Information. The ReadMe file is displayed. 5. Verify that your system meets the minimum requirements described in the

System Requirements section. 6. After reviewing the information, click the close icon in the upper-right corner

of the information window to close it. 7. Click Install AdeptWindows. The AdeptWindows Setup Wizard opens.

Follow the on-screen instructions to complete the installation.

To install the Omni-NFS Server Software NOTE: The configuration of Omni-NFS server requires a different procedure on Windows NT/2000/XP systems versus Windows 95/98 systems. Please refer to the topic Configuring the Omni-NFS Server for details. If you do not have Omni-NFS server or another NFS server application installed on your PC, you should install the supplied Omni-NFS server software. This section describes the installation of the Omni-NFS Server on a PC with either the Microsoft Windows 95/98 or Windows NT 4.0/2000/XP operating system. To install Omni-NFS Server software:

1. On the Welcome to AdeptWindows CD-ROM menu, click Install Omni-NFS Server. Or, you can double-click the SETUP.EXE program in the CD-ROM's OmniNFS folder. The InstallShield Wizard Welcome window is displayed.

2. Follow the on-screen instructions to complete the installation.

3. Once you have completed the software installation, you must configure the Omni-NFS Server on your PC. Refer to the following section on Configuring the Omni-NFS Server.


9

Configuring the Omni-NFS Server NOTE: The configuration of Omni-NFS server requires a different procedure on Windows NT/2000/XP systems versus Windows 95/98 systems. Please see the following instructions for details.

After installing the Omni-NFS Server, you need to configure it to run on your PC. The Omni-NFS Server supports multiple operating systems including Windows 95/98 and Windows NT/2000/XP. The steps required to complete configuration are: Step 1 Set sharing properties for the 3.5 inch floppy drive

Step 2 Specify configuration parameters for the Omni-NFS server

Step 3 for Windows 95/98 Users:

Specify start-up options for NFS Server

Step 3 for Windows NT/2000/XP Users:

Map group and user ids. Then, specify autostart settings for the NFS Server

Note: When using the Omni-NFS server with Windows XP, you must disable the Windows Firewall to allow communication with the Adept controller.

Step 1

To set sharing properties for the 3.5 inch floppy drive (A:).

1. Double-click on the My Computer icon or select Start => Programs => Windows Explorer to access the A drive.

2. Highlight the A drive.

3. Click the right mouse button and select Properties from the pop-up menu. The 3.5" Floppy (A:) Properties window is displayed.

4. Click the NFS Sharing tab.

5. Select the Shared button.

6. Click the Exported to All Clients check box.

7. Select the Read/Write button in the Directory Access Rights section.

8. Click OK to close the 3.5 Floppy (A:) Properties window.

Step 2

To configure the NFS Server:

1. Select Start => Programs => Omni-NFS Server V4.1 => NFS Server to start the Omni-NFS Server configuration utility program. The Omni-NFS Server Configuration window is displayed.


10

Note: The A drive is shown in the configuration window as exported to all

clients.

2. Set sharing properties for the Adept folder located on the C drive.

a. Click the New button. The NFS Server Export window is displayed as shown below.

b. Select the C drive in the Drive field.

c. Double-click Adept in the Path selection box.

d. Double-click Disks in the Path selection box. Then, click Drive_C in the Path selection box.

e. Click the Exported to All Clients check box.

f. Select the Read/Write button in the Directory Access Rights section.

g. Click Ok to close the NFS Server Export window. Click Yes when asked to restart the server. The NFS Server icon appears in the Windows taskbar to indicate that the NFS Server is running. The new, exported path is displayed in the Omni-NFS server window.


11

Step 3 depends on the operating system you are using. Choose either Windows 95/98 or Windows NT/2000/XP.

Step 3 - Windows 95/98 Users Only

To set autostart options for the NFS Server.

1. Click on the NFS Server icon using the right mouse button.

2. Be sure the Run at Boot Time option is enabled (checked).

3. Click on the desktop to close the Omni-NFS Server menu. Then, click the Exit button in the Omni-NFS Server window.

Installation is complete. You can now access the Omni-NFS Server from a V+ system.

Step 3 - Windows NT/2000/XP Users Only

To complete the NFS configuration for Windows NT/2000/XP, you need to map group and user IDs and specify autostart settings.

1. Click the Mapping button on the Omni-NFS Server Configuration window. The UID & GID Mapping window is displayed as shown below.

a. Click on the Group Name to GID mapping tab.

b. Select the local computer name from the Windows NT domain pull down list.

c. Highlight Administrators in the Windows NT Groups scroll list.

d. Set the Group ID to zero.

e. Click the Add button. You should see Administrators displayed in the group column of the Mappings in Group File section.


12

2. Click on the User Name to UID tab at the top of the UID & GID Mapping window. The settings for mapping a user name to a UID are displayed as shown below.

a. Highlight Administrator in the Windows NT Accounts scroll list.

b. Set the User ID to zero.

c. Click the Add button.


13

3. Click the Default Group button. The Default Group Mapping window is displayed as shown below.

a. Select Local Administrator. Administrators should appear in the unmarked box.

b. Click Administrators.

c. Click the Assign button.

d. Click the Close button to dismiss the Default Group Mapping window. You should see administrators displayed in the Default Group column of the Mappings in Password File section.

4. Click OK to close the UID & GID Mapping window and finish mapping the user and group IDs.

5. Click Yes when asked to restart the server.

6. Verify the NFS server is running.

a. Choose Start => Settings => Control Panel to display the Control Panel window.

b. Double click on the Services icon. The Services window is displayed as in the next screen.

c. Scroll to and highlight the line for the Omni-NFS Server.

d. Click the Start button if it has not already started.

e. Double click the Omni-NFS Server entry if Automatic is not listed under the Startup column and select Automatic as the service type.


14

f. Click the Close button to close the Services window.

Note: When using the Omni-NFS server with Windows XP, you must disable the Windows Firewall to allow communication with the Adept controller.

Installation is complete. You can now access the Omni-NFS Server from a V+ system and mount an NFS drive.

Installing the AdeptWindows License To use AdeptWindows PC, the AdeptWindows license must be installed on the Adept controller. If your system was ordered from Adept with the AdeptWindows PC option, the license is already installed. If you are adding the AdeptWindows PC option to an existing system, the license must be installed. On a controller that does not have the license installed, the controller will allow a connection to an AdeptWindows PC interface. However, all the other license options on your Adept controller are disabled. This allows you to install the license and then restart the controller. After restarting, all controller options will initialize normally. To install the license on the Adept controller, type the following at the Monitor prompt:

INSTALL password where “password” is the password for AdeptWindows on your Adept controller.


15

Setting up a Serial Connection This section describes how to set up a serial communication link between your PC and the Adept controller. If you are using an Ethernet communication link, see Working With Ethernet on page 16. Note: The serial connection works only with the RS-232/TERM serial port on the AWC board being used as the Adept controller’s main system processor. It cannot be used with the controller’s global serial ports located on an SIO board or serial ports on an auxiliary processor board. Additionally, this item works only with Adept MV controllers that are equipped with an AWC board. It will not work with the Adept SmartController.

Required Cabling The serial interface cable is provided with the AdeptWindows Controller board. The controller end of the cable has a circular mini-DIN male connector. This connector plugs into the RS-232/TERM port (circular mini-DIN female connector) located on the AWC board. See the Adept MV Controller User's Guide or Adept SmartController User's Guide for pinout details. The PC end of the cable is terminated with a DB 25-pin serial connector. This plugs into a 25-pin serial port on your PC. A 25- to 9-pin adapter is included that can be used to connect the cable to a 9-pin serial port.

Hardware Connection To set up the serial connection:

1. Connect one end of the serial interface cable to a COM port in your PC. Make a note of the COM port you are using (this information is required during the software startup).

2. Connect the other end of the cable to the RS-232/TERM port on the AWC board or RS-232 port on the Adept SmartController.

3. Set the DIP switches on SW1 on the AWC board or Adept SmartController. Note: When the DIP switches on the AWC board are set for AdeptWindows, the AdeptWindows option must be enabled (see “Installing the AdeptWindows License” on page 11 for details). Otherwise, the connection will succeed but all other installed license options on the controller will be unavailable.

Configuring the Serial Protocol The serial ports are automatically configured by the AdeptWindows PC software and V+ 14.0 (or later) operating system. Therefore, you do not need to manually configure the serial protocol. The V+ version 14.0 (or later) operating system (running on the Adept controller) and the AdeptWindows PC application (running on the PC) are configured to operate at a predefined baud rate. This protocol automatically overrides any previously defined serial configuration for the serial port on the Adept controller and on the PC. You are now ready to start AdeptWindows PC.


16

Working With Ethernet You can set up a simple Ethernet communication link between one or more PCs and one or more Adept controllers as shown below.

A Note on IP Addresses The IP address is the logical means by which the higher-level Ethernet software identifies a specific node. The IP address must be unique for each node within a LAN.

The Default IP Address

For Adept MV controllers, when an AWC board is installed in the Adept MV controller, V + version 13.0 (or later) will automatically create a “default” IP address for the controller that is based on the AWC board’s serial number (not the controller’s serial number). The default IP address will take the form:

172.16.1xx.1yy where “xx” and “yy” are the right-most 4 decimal digits of the AWC board’s serial number as shown below.

Note: The AWC board serial number is located on a bar-code label attached to the backplane connectors at the rear of the board.

The default IP address will be used whenever:

the NVRAM has not been initialized

the IP address in the NVRAM has been set to 0

a hardware or software switch on the Adept controller forces use of the default IP address.

If you are using the default IP address for the Adept controller (either AWC-equipped MV controller, or Adept SmartController), then you must use the following IP address and subnet mask for the PC:

IP address: 172.16.aa.bb

subnet mask: 255.255.0.0


17

where "aa" and "bb" in the IP address define a unique node address for each PC in the system. Adept recommends using 1 for the first PC, 2 for the second PC, 3 for the third PC, etc. See the section “Installing TCP/IP” in the AdeptWindows online documentation for details.

Required Interface Hardware Each PC requires a user-supplied Ethernet interface card. These are available

at most PC supply outlets. A shielded cross-over Ethernet cable is provided with the AdeptWindows

Software Kit. This cable can be used in place of a network hub when one PC is connected to one Adept controller.

If more than one PC or Adept controller is being connected, you must use a user-supplied network hub and user-supplied Ethernet cables. These are available at most PC supply outlets.

CAUTION: If the Adept-supplied crossover cable is used, it must be directly connected between the PC's Ethernet card and the Adept controller. DO NOT mix the crossover cable with user-supplied hubs or cables.

The AWC board and Adept SmartController are equipped with an Ethernet interface connector. Therefore, no additional hardware is required for the Adept controller.


18

Configuring Your System There are many ways to configure your AdeptWindows system. You can setup a basic Ethernet installation between one or more PCs (with only one PC configured as an NFS server), a hub or crossover cable, and one or more Adept controllers. The basic configurations are:

One PC and controller using default IP address One PC and controller with user-assigned IP address

The basic configurations using Adept default settings and the NFS server component are:

One PC, controller, and NFS server One PC, multiple controllers, and one NFS server Multiple PCs, multiple controllers, and one NFS server

There are also other network configurations that use more complex installations with multiple PCs, multiple controllers, and multiple NFS servers, these include:

Multiple PCs, controllers, and NFS servers Multiple PCs, controllers, NFS servers, and networks

Using the Controller Network Configuration Utility The Controller Network Configuration Utility simplifies the process of bringing up a new Adept controller. With previous versions of AdeptWindows, this process involved configuring a PC to a specific IP address that was accessible from the Adept controller, running AdeptWindows PC to communicate with the Adept controller, running a V+ configuration utility to set the desired IP address (and subnet mask) for the Adept controller, and then finally reconfiguring the PC to be able to communicate with the specified IP address. The Controller Network Configuration Utility allows you to set the IP address (and subnet mask) of the Adept controller regardless of the current IP address of the controller and of the PC. You can also use the tool to set other Adept controller startup features such as use of AdeptWindows PC as the default system user interface, and enabling auto-start (i.e., use of the disk file AUTO.V2). You can record the IP address of the PC so it will be accessed as the default NFS server for the controller. Lastly, you can initiate a reboot of the Adept controller, so that the configuration changes will take effect.

Note: The Controller Network Configuration Utility depends on UDP broadcasts for its functioning. Therefore, the Adept controller and the PC running the configuration utility must exist on the same LAN segment, either through a Cat 5 shielded crossover cable (provided with the AdeptWindows product) or a simple network hub. Some network hubs, most network switches and bridges, and all network routers prevent the transmission of UDP broadcasts.

The section "Configuring One PC and Controller With User-Assigned IP Address", on page 21, describes a procedure for using the Controller Network Configuration Utility.


19

Configuring One PC and Controller Using Default IP Address As shown in the figure below, there is one PC networked to one Adept controller. The controller is using the default IP address assigned by V+. This is a simple configuration that is useful for troubleshooting.

NOTE: This configuration requires the Adept-supplied crossover cable and CompactFlash card that was supplied with the Adept controller.

To create the network shown above, complete the following steps:

1. Disconnect power from the controller. Install the Adept-supplied CompactFlash that was included with the controller.

2. Set the controller DIP switch SW1 to the following:

SW1 SW2 SW3 SW4 OFF ON OFF ON

3. Record the IP address of the controller. For the MV controller with an AWC board, the IP address is included in the serial number on the connector label of the AWC board (see A Note on IP Addresses, on page 16, for details). For the SmartController, the IP address is on a label on the bottom of the controller.

4. Connect the Adept controller and your PC using the Adept-supplied crossover cable. DO NOT connect a hub between the controller and PC or use any other network cable.

5. Install the AdeptWindows software on the PC. For Setup Type, choose "Typical" and accept the default installation directory. Although installation of the Omni-NFS software is not required for this setup, you may install it at this time for future use.

6. Install TCP/IP on the PC using the IP address and subnet mask shown in the illustration. NOTE: To establish an Ethernet connection, the PC and the controller must be

on the same network. 7. Reconnect the power to the controller. For the SmartController, make sure

the 24VDC power is connected with the correct polarity. See the section titled “Installing Power” in the SmartController User's Guide for details.


20

8. Start the Adept controller and test the Ethernet connection. 9. If required, install the AdeptWindows license on the controller. 10. Start AdeptWindows on the PC and connect to the controller. Because you are

starting AdeptWindows for the first time, you will have to enter the controller’s IP address.

11. The controller firmware boot screen (black window) will display in the AdeptWindows session window. When prompted, press “enter” to load from drive D: (the CompactFlash). The V+ operating system will load from the CompactFlash. AdeptWindows will establish a connection with V+ and the Adept system identification information will display followed by a flashing cursor at a dot prompt. The Adept controller is now ready for use.


21

Configuring One PC and Controller With User-Assigned IP Address As shown in the figure below, there is one PC networked to one Adept controller. This configuration assumes that the PC has already been assigned an IP address (for example, for use on a corporate network). Therefore, the controller must have a user-assigned IP address rather than the default IP address assigned by V+. This is a simple configuration that is useful for troubleshooting.

NOTE: This configuration requires the Adept-supplied crossover cable and CompactFlash card that was supplied with the Adept controller.

To create the network shown above, complete the following steps:

1. Disconnect power from the controller. Install the Adept-supplied CompactFlash that was included with the controller.

2. Set the controller DIP switch SW1 to the following:

SW1 SW2 SW3 SW4

OFF OFF OFF OFF

3. Connect the Adept controller and your PC using the Adept-supplied crossover cable. DO NOT connect a hub between the controller and PC or use any other network cable.

4. Install the AdeptWindows software on the PC. For Setup Type, choose "Typical" and accept the default installation directory. Although installation of the Omni-NFS software is not required for this setup, you may install it at this time for future use.

5. Determine the IP address and subnet mask of your PC by looking at the TCP/IP properties of Network Settings in the Windows Control Panel. See “Installing TCP/IP” in the AdeptWindows online documentation, for more details. Alternatively, you can determine the IP address of your PC by using the "winipcfg" command (Windows 95/98) or "ipconfig" command (Windows NT/2000/XP) in the Windows MS-DOS Prompt window. NOTE: To establish an Ethernet connection, the PC and the controller must be

on the same network. 6. Based on the PC’s IP address and subnet mask determined above, define a

controller IP address, which will be configured in the next step.


22

Example: If the PC’s IP address is 192.9.200.80 and the subnet mask is 255.255.255.0, then the common network number is 192.9.200.xxx. In this case, the controller’s IP address should be defined as 192.9.200.xxx, where xxx is a number between 0 and 255 that defines a unique IP address on the network. The subnet mask must be defined as 255.255.255.0.

NOTE: If your controller will be connected to your corporate network, then you may need to contact your network administrator to get a controller IP address.

7. Use the Controller Network Configuration Tool (automatically installed with AdeptWindows) to assign the controller IP address. Start the Controller Network Configuration Tool, by selecting: START > Programs > Adept > Controller Network Configuration Tool Follow the online instructions, and, when instructed, reconnect the power to the controller. For the SmartController, make sure the 24VDC power is connected with the correct polarity. See the section titled “Installing Power” in the SmartController User's Guide for details.

NOTE: It may take up to a minute for the controller to boot and for the screen shown in Controller Network Configuration Tool (below) to appear.

8. Enter the new controller IP address and subnet mask. Be sure that the “AdeptWindows PC as default interface” and “Re-start Adept controller” checkboxes are selected as shown in the figure below. Then click the “Update” button to update the new configuration.

Controller Network Configuration Tool


23

9. On the next window, select the checkbox to launch AdeptWindows PC and click “Finish”. This will start AdeptWindows PC and automatically connect to the controller using the new IP address.

10. Alternatively, the AdeptWindows PC program can be started from the Windows desktop by selecting START => Programs => Adept => AdeptWindows PC

11. Connect using Ethernet (if this is the first time you have used AdeptWindows, you will be prompted. Otherwise, select this option from the File pulldown on the top menu bar). Enter the controller IP address and click OK. The V+ operating system will be loaded from the CompactFlash. AdeptWindows will establish a connection with V+ and the Adept system identification information will be displayed followed by a flashing cursor at a dot prompt. The Adept controller is now ready for use.


24

Troubleshooting Use this section to help you resolve problems that you may encounter when using AdeptWindows.

General Startup Problems SW1 Dipswitches: Check that the dipswitches are set to the correct

positions (this is commonly overlooked). Check that the dipswitches are fully seated in the required positions. Exercise the four dipswitches by flipping them up and down several times and then set them to the required positions.

CompactFlash: Is the original CompactFlash shipped from Adept installed? Is it fully inserted?

NOTE: Do not substitute an off-the-shelf unit for the original CompactFlash that was supplied by Adept (it will not work).

24VDC Power: Does the fan in the rear of the controller work when power is applied? Do any LED’s come on when power is applied? Check the power supply output. Check the polarity of the wiring to the XDC1 or XDC2 connector (incorrect polarity will not damage the controller, but it will not work).

Energy Star Compliant Systems On some computers that use "Energy Star" compliant motherboards, any network connections may be disrupted when the BIOS power-save function activates. If your system exhibits this problem, you can correct it by disabling the power-save feature in the BIOS. See your PC user's guide or installation manual for details.

Serial Communications Serial Cable: Check that the data transfer cable is a null-modem (not

straight-through) type. Test and verify the cable for continuity and accurate wiring.

Serial Communications: When using HyperTerminal, check that the COM port settings are set correctly in the HyperTerminal session.

Ethernet Communications

Using PING to Test the Ethernet Setup

To test the Ethernet connection, it is useful to know how to “PING” between the PC and the controller. The PING command sends a quick message between the two devices to verify that the Ethernet connection is working.

Pinging the Adept Controller

To test the communication from the PC to the Adept controller, you can execute the PING command at the PC’s MS-DOS prompt. From the Windows taskbar, select:

Start => Programs => MS DOS Prompt

At the MS-DOS prompt, type the PING command followed by the IP address (or node name) for the Adept controller. If you do not know the IP address of the controller, you will have to scan for it using AdeptWindows. For example, to PING a controller with the IP address 172.16.113.170,type:

PING 172.16.113.170


25

If the PING is successful, a message similar to the following is displayed:

Pinging 172.16.113.170 with 32 bytes of data:

Reply from 172.16.113.170: bytes=32 time=39ms TTL=15



Pinging the PC

You can also use the PING command to test the communication from the Adept controller to your PC. At the Monitor prompt, type the PING command followed by the IP address (or node name) for the PC:

PING 172.16.200.1 If the PING is successful, the following message is displayed:

.Success

Connecting to an Adept Controller Through TCP/IP

The Adept controller and the PC must use the same IP network address and subnet mask to enable communications through TCP/IP. Note, in the table below, that the network section of the IP address must match exactly (the node number [marked with "x" below] consists of any legal values and must be different for each node on your network), and the entire subnet mask must match exactly.

PC Adept Controller

IP address 172.16.xxx.xxx 172.16.xxx.xxx Subnet Mask 255.255.0.0 255.255.0.0

Check the IP network address and subnet mask setting for the PC using the

Network option located on the Windows Control Panel. See the Windows online help for details.

Check the IP address and subnet mask setting for the Adept controller using the CONFIG_C utility. See "Changing Software Switches and Network Settings" in the AdeptWindows online documentation for details.

NetManage's TCP/IP

It is recommended that you not run NetManage's TCP/IP in conjunction with Microsoft's TCP/IP. Doing so can cause a one-second delay when displaying characters in the monitor window that are typed on the keyboard. To correct this problem, disable the NetManage TCP/IP connection. See the Windows online help system for details.

Other Ethernet Problems

Ethernet Cable: Check that the Ethernet cable is a crossover (not straight-through) type (for direct connection between PC and controller; no hubs). Are you using a shielded Ethernet cable? The crossover, shielded Ethernet cable supplied with the AdeptWindows Software Kit is for direct connections (no network hub).

Ethernet Communications: Do the PC and controller have common network numbers? Do they have identical subnet masks? Did you restart Windows after setting the IP address and subnet mask on your PC? If communicating


26

with the controller using the default IP address, check that your PC IP address is on the network number “172.16.xxx.xxx” and that the subnet mask is “255.255.0.0”.

PING Command: The “ping” command can be used in the PC MS-DOS Prompt window to check the Ethernet connection with the controller. For details, see the topic Using PING to Test the Ethernet Setup on page 24.

More Ethernet Troubleshooting Resources

For more information about troubleshooting your Ethernet connection, see “Troubleshooting Ethernet Problems” in the Adept Document Library at: http://www.adept.com/Main/KE/DATA/Procedures/EtherTrouble/EtherTroubleTOC.html For more information about IP addresses, see “Understanding IP Addresses” in the Adept Document Library at: http://www.adept.com/Main/KE/DATA/Procedures/EtherTrouble/ethernet_trouble_IP.html

PC or Adept Controller Problems

PC or Windows Program Problems

When any of your Windows programs cause your PC to lock up or crash while AdeptWindows PC is running, you may lose the AdeptWindows PC connection. This section describes how to reestablish your AdeptWindows PC connection.

If you see the error message "V+ not responding":

1. Disconnect from AdeptWindows PC.

2. Connect to AdeptWindows PC.

If your Windows operating system is locked up:

1. Reboot your PC.

2. Start AdeptWindows PC.

In most cases, this reestablishes the connection. However, if you receive a timeout error (10060), simply reconnect AdeptWindows PC.

Adept Controller Problems

If the Adept controller locks up or crashes while AdeptWindows PC is running, you can reestablish the connection as follows:

1. Exit AdeptWindows PC.

2. Reboot the Adept controller.

3. Start AdeptWindows PC.

If the controller crashes repeatedly, report the problem to customer service.

V+ License

When upgrading a system from V+ version 11 to, for example, V+ version 14 (version 12.2C or higher is required for AdeptWindows), the V+ Version 14 license must be installed on the controller. Otherwise, all other licenses (such as V+ Extensions, etc.) are deactivated until the V+ Version 14 license is installed (and the V+ system is rebooted from disk).


27


28

PN 00971-07401 Rev A

Documents

AdeptWindows Installation Guide - Adept · PDF fileAdeptWindows Installation Guide Version 3.0 ... Adept NanoStage L3, ... AdeptWindows Installation Guide 4 TROUBLESHOOTING