Adept Windows PDF
Adept Windows PDF
Adept Windows PDF
This is a printed version of the AdeptWindows User's Guide online documentation. A Table of
Contents is provided so that you can locate the desired topics. Because this document is
designed for online viewing, cross−references will not have page numbers. For easier navigation
use the online version of this document, which can be accessed from the Knowledge Express
Library.
Table of Contents
Welcome To AdeptWindows........................................................................................................................................1
What is AdeptWindows?..............................................................................................................................................3
What's New?.....................................................................................................................................................4
System Requirements.......................................................................................................................................4
PC Requirements.......................................................................................................................................5
Adept Controller Requirements.................................................................................................................5
Network Requirements..............................................................................................................................6
How Do I Begin?..............................................................................................................................................6
Which Connection Method Should I Use?................................................................................................6
How Can I Get Help?.......................................................................................................................................6
Installing the Software......................................................................................................................................6
To install AdeptWindows:.........................................................................................................................7
To install the Omni−NFS Server Software...............................................................................................7
Installing the AdeptWindows License..............................................................................................................7
Setting up a Serial Connection.........................................................................................................................8
Required Cabling.......................................................................................................................................8
Hardware Connection................................................................................................................................8
Configuring the Serial Protocol.................................................................................................................8
Working With Ethernet.....................................................................................................................................9
A Note on IP Addresses............................................................................................................................9
Required Interface Hardware..................................................................................................................10
Using PING to Test the Ethernet Setup...................................................................................................11
Configuring Your System...............................................................................................................................12
Using the Controller Network Configuration Utility..............................................................................12
Configuring One PC, Controller, and NFS Server..................................................................................14
Configuring One PC, Multiple Controllers, and One NFS Server..........................................................15
Configuring Multiple PCs, Multiple Controllers, and One NFS Server.................................................16
Configuring Multiple PCs, Controllers, and NFS Servers......................................................................17
Configuring Multiple PCs, Controllers, NFS Servers, and Networks.....................................................18
Installing TCP/IP............................................................................................................................................19
Installing TCP/IP on a PC Running Windows 95/98..............................................................................20
Installing TCP/IP on a PC Running Windows 2000...............................................................................22
Installing TCP/IP on a PC Running Windows NT..................................................................................26
Installing NFS.................................................................................................................................................29
Configuring the Omni−NFS Server.........................................................................................................29
Mounting an NFS Drive from the Adept Controller...............................................................................34
Referring to Mounted Drives...................................................................................................................35
Testing the NFS Mounted Drives............................................................................................................35
Setting the DIP Switches on the Controller....................................................................................................37
Changing Software Switches and Network Settings......................................................................................38
Loading and Running the CONFIG_C Utility........................................................................................38
Changing the Software Switch Settings..................................................................................................39
Changing the User−Defined IP Address in NVRAM.............................................................................39
Changing the Names and Paths for NFS Mounted Drives......................................................................39
Installing DDE With AIM..............................................................................................................................40
Table of Contents
Using AdeptWindows PC...........................................................................................................................................43
Starting AdeptWindows PC............................................................................................................................43
Connecting Through Ethernet.................................................................................................................43
Scanning Ethernet for Available IP Addresses.......................................................................................44
Connecting Through a Serial Port...........................................................................................................44
The AdeptWindows PC Main Window..........................................................................................................45
The AdeptWindows PC Menus......................................................................................................................46
The File Menu.........................................................................................................................................46
The Adept Menu......................................................................................................................................46
Disconnecting From the Controller................................................................................................................46
Closing AdeptWindows PC............................................................................................................................47
Table of Contents
Troubleshooting..........................................................................................................................................................95
DDE Errors.....................................................................................................................................................95
Connecting to Host..................................................................................................................................95
Using Microsoft Excel.............................................................................................................................95
Energy Star Compliant Systems.....................................................................................................................96
Ethernet Communications..............................................................................................................................96
Connecting to an Adept Controller Through TCP/IP..............................................................................96
NetManage's TCP/IP...............................................................................................................................96
Other Ethernet Problems.........................................................................................................................96
PC or Adept Controller Problems...................................................................................................................97
PC or Windows Program Problems.........................................................................................................97
Adept Controller Problems......................................................................................................................97
TIFF Image Export.........................................................................................................................................97
V+ License......................................................................................................................................................98
AdeptWindows represents the first step toward drawing the PC closer to the Adept controller. In keeping with the
tradition of providing a safe and predictable development environment, Adept will continue this evolution of
software tools in a phased approach.
♦ AdeptWindows PC
♦ AdeptWindows DDE
♦ AdeptWindows Offline Editor
♦ AdeptWindows TFTP Server
♦ Controller Network Configuration Utility
♦ AdeptWindows Online Help
Your AdeptWindows kit (PN 00494−001) includes the following items:
AdeptWindows PC enables a PC to display the real−time Graphical User Interface (GUI) for an
Adept controller. The AdeptWindows PC solution allows a PC connected to the controller, using
either Ethernet or a COM (serial) port, to replace a dedicated display monitor, keyboard, and
mouse.
Note: Except for images in the Vision window, AdeptWindows PC does not support the AIM
screen capture utility. However, you can capture AdeptWindows screens using any
Windows−compatible screen capture utility program (e.g., HiJaak ). See TIFF Image Export for
more details.
AdeptWindows DDE
AdeptWindows DDE provides a standard Dynamic Data Exchange (DDE) server application to
allow communication with other DDE−capable applications running under Microsoft Windows on
a PC (e.g., WonderWarefi, Excelfi).
The DDE functionality is embedded in the interface between the PC and the controller. This
provides the first open link between the Adept controller and standard applications running on the
PC. Extending this concept further, custom applications developed in C, C++, or Visual Basic on
the PC can use the DDE protocol to communicate with the Adept controller through the DDE
interface. More...
AdeptWindows Offline Editor is an upgrade to our popular offline editor that provides the system
administrator/customizer with the capability to edit and manage disk files on the PC. More...
AdeptWindows TFTP Server allows the Adept controller to boot over Ethernet. It contains a
user−enabled diagnostics capability that displays the IP node address, file names, and error
messages during the booting process. More...
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. More...
The AdeptWindows Offline Editor features an online help system. The help system provides quick
access to proper keyword syntax, detailed keyword descriptions, and online versions of the V+
Language Reference Guide and the AdeptWindows User's Guide (the help system you are in
currently). More...
What's New?
Version 3.0 contains the following new features:
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. More...
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. More...
• 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
AdeptWindows runs on both Windows 95/98 and Windows NT 4.0/2000/XP. Unless noted, the term “Windows”
refers to these operating systems.
The AdeptVision image is not supported by the serial option. However, vision graphics are displayed on the PC.
• PC Requirements
• Adept Controller Requirements
• Network Requirements
PC Requirements
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.
NOTE: The following V+ system versions (or later) are required if the PC has Windows 2000 SP3 or Windows XP:
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.
• 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.
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.
How Do I Begin?
Before you can use AdeptWindows, you must complete the following steps:
Which method is best for you? Choose one of the following PC setups and follow the recommended procedure.
Recommended
Recommended
Your PC Setup User Interface and Notes
Procedure
Connection
Configuring One
AdeptWindows PC through
PC has an Ethernet card PC and Controller
Ethernet connection using Preferred and most common
and already has an With
user−assigned IP address in setup.
assigned IP address. User−Assigned
SmartController
IP Address
AdeptWindows PC through A common setup for Configuring One
PC has an Ethernet card
Ethernet connection using SmartControllers with PC and Controller
but doesn’t have an IP
default IP address in standalone PC’s (i.e., not on a Using Default IP
address configured.
SmartController corporate network). Address
PC does not have an
Useful for troubleshooting. See the
Ethernet card, or you’re
HyperTerminal through an Not useful for development − SmartController
having difficulty
RS−232 Serial connection does not allow Vision User's Guide,
connecting through
windows. section 3.6
Ethernet.
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.
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 Configure 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. See Installing the Omni−NFS Server on the PC for details on installing the Omni−NFS server software.
To install the license on the Adept controller, type the following at the Monitor prompt:
INSTALL password
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
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. More...
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 28 for details). Otherwise, the connection will succeed
but all other installed license options on the controller will be unavailable.
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.
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.
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.
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.
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
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 Installing TCP/IP for details on setting the
IP address and subnet mask in Windows 95/NT.
To simplify the process of referencing controllers, the names of your controllers can be mapped to the controller IP
addresses. Use Windows Explorer to select WINNT => SYSTEM32 => DRIVERS => ETC => HOSTS. Then
you can use WordPad or NotePad to edit the file. (see the example below).
127.0.0.1 localhost
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 (Adept PN 90963−00210).
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.
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 PC
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:
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.
PING 172.16.113.170
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
.Success
The basic configurations using Adept default settings and the NFS server component are:
There are also other network configurations that use more complex installations with multiple PCs, multiple
controllers, and multiple NFS servers, these include:
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.
Before performing the steps below, you must have your PC and Adept controller connected through a network
crossover cable or through a network hub. More...
1. Select Start => Programs => Adept => Controller Network Configuration Utility from the Windows
taskbar. The following window is displayed:
2. Click on Next. The Controller Network Configuration Utility prompts you to make sure the Adept
controller is turned off.
3. Turn off the Adept controller.
4. Click on Next. The Controller Network Configuration Utility prompts you to turn the Adept controller back on
and wait until it boots completely.
5. Turn the Adept controller on. Once the controller is detected, the following window is displayed.
Change the IP address shown Enter the new IP address and subnet mask.
Click on Update.
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+. Additionally, the controller has mounted NFS drives exported by the PC node
ASERVER.
1. Connect the Adept controller and your PC to a network hub, or use a crossover cable in place of the hub
and its connecting cables.
2. Install the AdeptWindows software on the PC. More...
3. Install TCP/IP on the PC using the IP address and subnet mask. More...
4. Start the Adept controller and test the Ethernet connection. More...
5. If the Omni−NFS software was not installed on the PC during the installation of the AdeptWindows
software, install the Omni−NFS software on the PC. After installing the Omni−NFS software, verify that
the Omni−NFS server is running. More...
6. If required, install the AdeptWindows license on the controller. More...
7. Restart the Adept controller to automatically mount the default NFS directories exported by the PC.
8. Start AdeptWindows on the PC and connect to the controller. Since you are starting AdeptWindows for the
first time, you will have to enter the controller’s IP address. More...
9. Test the NFS mounted drives. More...
In this example, there is one PC networked to multiple Adept controllers. Each controller is using the default IP
address assigned by V+ . Additionally, all the controllers have mounted the same NFS drives exported by the PC
node named ASERVER.
Note: You can connect to multiple controllers from one PC by simply starting additional AdeptWindows sessions
and entering the appropriate IP addresses in the Ethernet connection dialog boxes.
In this example, there are multiple PCs networked to multiple Adept controllers. Each controller is using the default
IP address assigned by V+. Additionally, all the controllers have mounted the same NFS drives exported by the PC
node named ASERVER.
Note: You can connect to multiple controllers from one PC by simply starting additional AdeptWindows sessions
and entering the appropriate IP addresses in the Ethernet connection dialog boxes. However, only one PC can be
connected through Ethernet to each controller.
In this example, there are multiple PCs networked to multiple Adept controllers. Each controller is using the default
IP address assigned by V+. Additionally, Controller 1 has mounted two NFS drives exported by the PC node
ASERVER; Controller 2 has mounted two NFS drives exported by the PC node BSERVER.
Note: You can connect to multiple controllers from one PC by simply starting additional AdeptWindows sessions
and entering the appropriate IP addresses in the Ethernet connection dialog boxes. However, only one PC can be
connected through Ethernet to each controller.
In this example, there are multiple PCs networked to multiple Adept controllers. This network is attached to another
network by a hub/gateway. In this situation, all PC node names, IP addresses, and subnet masks are assigned by the
network administrator.
1. Connect the Adept controllers and PCs to one or more network hubs.
2. Install AdeptWindows software on the PCs. More...
3. Install TCP/IP on each PC using the IP addresses and subnet mask assigned by your system administrator.
More...
4. Start the Adept controllers and test the Ethernet connections. More...
5. If the Omni−NFS software was not installed on the PC during the installation of the AdeptWindows
software, install the Omni−NFS software on the PC. After installing the Omni−NFS software, verify that
the Omni−NFS server is running. More...
6. Install the AdeptWindows license on each controller. More...
7. Set the IP address of the Adept controller using the Controller Network Configuration Utility. More...
8. Using the CONFIG_C utility on each Adept controller, modify the NETWORK section of the V+ System
Configuration data for each controller. The node names, IP addresses, mount names, etc., must be assigned
by your system administrator. More...
9. Restart the Adept controllers to automatically mount the default NFS directories exported by the NFS
server PC(s).
10. Start AdeptWindows on each PC and connect to the desired controller. Since you are starting
AdeptWindows for the first time, you will have to enter the available IP addresses. More...
Note: You can connect to multiple controllers from one PC by simply starting additional AdeptWindows sessions
and entering the appropriate IP addresses in the Ethernet connection dialog boxes. However, only one PC can be
connected through Ethernet to each controller.
Installing TCP/IP
TCP/IP is a networking protocol that is used to establish Ethernet communications between a PC and an Adept
controller. The setups for Microsoft Windows 95/98 and NT 4.0 are slightly different.
1. Choose Start => Settings => Control Panel => Network from the START menu in Windows 95/98. The
following dialog box is displayed:
2. If TCP/IP is on the list of installed components, go to Step 3. If TCP/IP is not on the list of installed
components, choose Add to add a new protocol. The Select Network Component Type window is
displayed as shown below.
2. Choose Add to display the Network Protocol selection. The Select Network Protocol window is displayed
as shown below.
5. Choose the IP Address tab and type in the correct IP Address and Subnet Mask. If you are using the
default IP address (in NVRAM) for the Adept controller, then you must use the following IP address and
subnet mask for the PC:
IP Address: 172.16.2aa.bb
where “aa” and "bb" in the IP address define a unique node address for each PC in the network. Adept recommends
using 1 for the first PC, 2 for the second PC, 3 for the third PC, etc. If you are not using the default IP address for the
Adept controller, see your network system administrator for the IP address and subnet mask to use.
6. Choose OK on the TCP/IP Properties dialog box and on the Network dialog box.
7. Reboot your PC.
1. Choose Start => Settings => Control Panel from the Windows taskbar.
2. Select Network and Dial−up Connections from the Control Panel.
3. Choose one of the following:
4. Select Internet Protocol [TCP/IP] from the Local Area Connection Properties window if it is not already
highlighted.
5. Click on Properties to assign an IP address. The Internet Protocol (TCP/IP) Properties window is
displayed as shown below.
After clicking on Add Network Components from the column on the left in the Network and Dial−up Connections
window, the Windows Optional Networking Components Wizard starts.
a. Check Networking Services from the Windows Optional Networking Components Wizard window as
shown below.
After you have selected Local Area Connection from the Network and Dial−up Connections window, the Local
Area Connection Status window is displayed as shown below.
1. Click on Properties. The Local Area Connection Properties window is displayed as shown below.
2. Select Internet Protocol [TCP/IP] as the component you want associated with the connection.
3. Click on Install. The Select Network Component Type window is displayed as shown below.
1. Choose Start => Settings => Control Panel => Network from the START menu in Windows NT 4.0.
The following dialog box is displayed:
2. If TCP/IP is on the list of installed components, go to Step 3. If TCP/IP is not on the list of installed
components, choose Add to add a new protocol. The Select Network Protocol dialog box is displayed as
shown below.
c. Choose OK from the Select Network Protocols dialog box to save these selections and return to
the Network dialog box.
3. Select Protocols from the Network dialog box.
4. Choose the Properties button to display the TCP/IP Properties dialog box shown below.
5. Choose the IP Address tab and type in the correct IP Address and Subnet Mask. If you are using the
default IP address (in NVRAM) for the Adept controller, then you must use the following IP address and
subnet mask for the PC:
IP Address: 172.16.2aa.bb
where “aa” and "bb" in the IP address define a unique node address for each PC in the network. Adept recommends
using 1 for the first PC, 2 for the second PC, 3 for the third PC, etc. If you are not using the default IP address for the
Adept controller, see your network system administrator for the IP address and subnet mask to use.
6. Choose OK on the TCP/IP Properties dialog box and on the Network dialog box.
7. Reboot your PC.
Installing NFS
Network Files System (NFS) capability requires two parts: an NFS client and an NFS server. AdeptNet, included
with the AWC board or SmartController, provides the NFS client portion on the Adept controller side. To complete
the package, you must also install NFS server software on the PC.
Once both parts have been installed on their respective systems, the client system can “mount” additional
drives/directories exported by any “server”. After mounting the drives, the client can access files on these drives in
the same manner as any local drive. This allows the Adept controller to:
Your AdeptWindows software includes an NFS software package for the PC named “Omni−NFS”, manufactured by
XLink Technology, Inc.
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
Map group and user ids. Then, specify autostart settings for the NFS Server
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
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.
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.
1. Click the New button. The NFS Server Export window is displayed as shown below.
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.
Step 3 depends on the operating system you are using. Choose either Windows 95/98 or Windows NT/2000/XP.
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.
To complete the NFS configuration for Windows NT/2000, 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
b. 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.
c. Click the Default Group button. The Default Group Mapping window is displayed as shown below.
Installation is complete. You can now access the Omni−NFS Server from a V+ system and mount an NFS drive.
More...
At startup, provided that the NFS server software is already running, the Adept controller performs the necessary
network initialization and mounting procedure to mount the external drive(s) defined by the MOUNT statement(s)
contained in the V+ configuration data. More...
If the NFS server does not respond, the mounts fail. A failure occurs, for example, if the server software is not
running or if the server is disconnected from the network. Use the NET monitor command after startup to determine
which mounts were successful. More...
You cannot initialize the network after the V+ system has completed its initialization. You can use the PING
monitor command to verify network connectivity. If a problem exists with the network connection, correct it and
You can also mount additional NFS drives using the FSET monitor command or the FSET program instruction, or
add additional statements to the V+ configuration data (using CONFIG_C) to automatically mount the additional
drives. See the AdeptNet User's Guide for details.
The following syntax is used to fully specify any file in the V+ environment:
device>disk_unit:directory_path\filename
For example, the full specification of a file called MY_FILE.DAT, residing in the directory NEW_DATA on an
Adept controller’s local D drive, is:
DISK>D:\NEW_DATA\MY_FILE.DAT
With the NFS functionality, the device name NFS has been added to V+. If the same file is in a directory with the
same name but on a remote disk mount called DISK1, the full description is:
NFS>DISK1:\NEW_DATA\MY_FILE.DAT
In the case of the “default” NETWORK configuration statements, the mounted drives are designated “XC” and
“XA”. So, the specification for the same file (MY_FILE.DAT) on the XC mounted drive would look like:
NFS>XC:MY_FILE.DAT
You can use the CD monitor command to specify the default device, unit, and directory to access if those elements
are omitted from a file specification.
The NET command can be used to display the status of any mounted drives. At the dot prompt, type
NET
Once you have verified that the correct drives are mounted, you can list the files on any of the mounted drives by
typing:
fdir NFS>[MOUNT]:\
where [MOUNT] is the mount name assigned to the drive. For example, in Figure 2−39 the mount name XC is
assigned to the directory C:\ADEPT\DISKS\DISK_C. So, to display a list of the files in that directory, simply type:
dir NFS>XC:\
With the factory DIP switch setting, the system will read the configuration data from the NVRAM chip. This allows
you to set all the configuration options in software without changing the physical DIP switches. See the description
of the CONFIG_C program in the Instructions for Adept Utility Programs for details.
Note: When the hardware or software switches on the Adept controller are set to use the AdeptWindows interface,
the AdeptWindows option must be enabled (see Installing the AdeptWindows License). Otherwise, the connection
will succeed but the other installed license options on the Adept controller will not be available.
If you decide to use the hardware DIP switch settings, rather than the software switches in NVRAM, you must first
decide which interface you want to use—serial or Ethernet—and then use the appropriate DIP switch settings shown
in the Adept MV Controller User's Guide or SmartController User's Guide for details.
CD UTIL
LOAD CONFIG_C
EXECUTE A.CONFIG_C
The Adept controller is equipped with hardware and software switches. The software switches that are stored in an
NVRAM, can be viewed and changed using the CONFIG_C utility.
If you are connecting your Adept controller to an existing network, you will need to set the user−defined IP address
to match your existing network. In this situation, your network system administrator will need to specify the correct
IP address (and subnet mask) for the Adept controller.
0.0.0.0
when the Adept controller is shipped from the Adept factory. That setting causes the default IP address to be used.
More...
The user−defined IP address can be viewed and changed using the CONFIG_C utility.
In certain situations, it may be necessary to change the node names, IP addresses, or paths for NFS
mounted drives. This information is stored in the NETWORK section of the V+ system
configuration data. It can be viewed and changed using the CONFIG_C utility.
Before editing the NETWORK section of the V+ system configuration data, you need the
following information:
♦ The IP address of each PC that contains the drives/directories you wish to mount
♦ The path/name of each directory you wish to mount
♦ A node “name” that you wish to assign to each PC
♦ A mount “name” that you wish to assign to each mounted drive.
For example, the following NETWORK configuration statements define two mounted drives: XC
and XA, and associate the PC node name ASERVER with the IP address 172.16.200.1:
.network
For more information on viewing and editing the configuration data, see the Instructions for Adept
Utility Programs for details.
Shut down the AIM system and then restart it. The DDE server is automatically enabled.
Note: If you are using the Ethernet option, it is possible to connect to multiple Adept controllers at the same time
(each connection requires a separate AdeptWindows PC session running on the PC). The maximum number of open
AdeptWindows PC sessions is limited only by the amount of memory (RAM) installed on your PC.
Starting AdeptWindows PC
Closing AdeptWindows PC
Starting AdeptWindows PC
To start AdeptWindows PC from the Windows toolbar, select:
If this is the first time that AdeptWindows PC has been started on the system, the AdeptWindows PC introductory
screen is displayed followed by the Connection type dialog box. For other AdeptWindows PC startup options, click
here.
Select the connection type: either Ethernet or a COM port (for serial communication). Choose OK to save the
selection.
The system “remembers” your connection preference. It prompts you appropriately the next time you try to connect.
In the IP field, type the IP address (or host name) for the Adept controller (if you do not know the IP address, see
Scanning Ethernet for Available IP Addresses). This should be the same address used when you PINGed the
controller during installation (see Using PING to Test the Ethernet Setup for details).
If you do not know what IP addresses are available, you can select File => Scan Ethernet to display a list of the IP
addresses for Adept controllers on your network that support AdeptWindows PC. The following window is
displayed:
Simply select the desired IP address from the list and click Connect to connect to that system.
NOTE: This item works only with Adept MV controllers that are equipped with an AWC board. It will not work
with the Adept SmartController.
Use the scrolling COM Port list to select the COM port your PC uses to connect to the Adept controller.
NOTE: If autoboot is not enabled and the Adept controller is on when you try to connect, the DDT window (black
window with yellow text) will be displayed when the connection is made. You will then see the “Load from local
disk...” prompt and DDT will wait for your input before proceeding. See Booting the Adept Controller Over
Ethernet for details.
You can reduce the window size by double−clicking on the AdeptWindows PC menu bar or clicking:
Once the Monitor window is opened, you can execute Monitor commands, use the SEE editor, start up AIM, etc.
If the AdeptFTP or AdeptNFS license is installed on your Adept controller and the appropriate software is installed
on your PC, then you can perform file transfers between the Adept controller and your PC. This allows you, for
instance, to write and edit programs on the PC (for example, using the AdeptWindows Offline Editor) and then
transfer them to the Adept controller using AdeptFTP or AdeptNFS. See the Instructions for Adept Utility Programs
for details on the Adept FTP client/server utility. See the AdeptNet User's Guide for details on Adept NFS software.
NOTE: File transfers require either the AdeptFTP or AdeptNFS license and File Transfer Protocol (FTP) or
Network File System (NFS) software running on your PC. Windows contains an FTP program that can be accessed
by typing “FTP” (no quotes) at the MS−DOS prompt (or type “FTP ?” for a list of commands). NFS software is
included with the AdeptWindows software.
• File
• Adept
1. Choose File => Disconnect. The AdeptWindows PC dialog box is displayed as shown below.
2. Choose Yes to disconnect. You can now reconnect to a different Adept controller by following the
procedure described in Connecting Through Ethernet or Connecting Through a Serial Port.
Closing AdeptWindows PC
To close AdeptWindows PC, choose:
1. Choose File => Exit. The AdeptWindows PC dialog box is displayed as shown below.
NOTE: If you are still connected to the Adept controller, the message shown above is displayed.
Or, to manually start AdeptWindows TFTP Server from the Windows Program Manager:
Once the TFTP Server is initialized, the window is minimized on the Windows Taskbar. To view the TFTP Server
window, simply double−click the Adept TFTP Server task on the Taskbar.
• File
• Help
NOTE: All screen messages shown in this section are displayed in the DDT window (black window with yellow
text).
1. Set the hardware DIP or software switches on the Adept controller so that auto boot is disabled. See for
details on setting the hardware DIP switches. See the Instructions for Adept Utility Programs for details on
setting the NVRAM software switches using the CONFIG_C utility.
2. Start the PC.
3. Start AdeptWindows PC and check that the TFTP Server window is displayed (it will appear as a
minimized task on the Windows Taskbar). See Starting the AdeptWindows TFTP Server for details.
If you are using the Adept VGB/monitor/keyboard interface in place of AdeptWindows PC, you can
manually start the TFTP Server without starting AdeptWindows.
4. Start the Adept controller. See the Adept MV Controller User's Guide for details. After the controller
completes the self tests, the following prompt is displayed:
If an SIO board is present, the list of local disks is A, B, C, or D, and the default disk is A.
5. Type "X" to choose the network disk and press the ENTER key. The following prompt is displayed:
NOTE: A separator (slash or backslash) must be included at the end of the path if a directory is specified.
The boot process continues and the following messages are displayed:
Reading C:\Adept\Disks\Disk_C\ADEPTSYS.ADM
Reading C:\Adept\Disks\Disk_C\ADEPTSYS.CFG
Reading C:\Adept\Disks\Disk_C\ADEPTSYS.SYS
You can abort the Ethernet boot process by pressing the ENTER key one time. The system returns to the "Load from
local disk..." prompt.
To enable diagnostics:
After the Settings window appears, select the Display diagnostics checkbox. Close the Settings window by choosing
OK .
Once the diagnostics are enabled, the AdeptWindows program will display all connect messages when booting over
Ethernet such as the IP address of the node that is requesting files, the names of files being sent, and error messages.
When the AdeptWindows TFTP Server diagnostics are enabled, the diagnostic messages will continue to
accumulate in the server window until they are manually cleared or until the server window is closed. To manually
clear the messages:
All messages are cleared from the AdeptWindows TFTP Server window.
To close AdeptWindows TFTP Server, from the TFTP Server menu bar select:
Note: AdeptWindows DDE works only with an Ethernet TCP/IP link between the PC and Adept controller.
• PC An application that runs on your PC and acts as a DDE Server to DDE client programs on the same PC.
This application forwards messages to the Adept controller using a TCP/IP link over Ethernet.
• V+ A driver task that runs on the Adept controller under AIM 3.1 or later. This task receives messages
from the DDE Server and accesses V+ and AIM variables to provide data items as requested.
The DDE driver runs in task 9 on the Adept controller. Therefore, the V+ Extensions license on the Adept
controller is required in order to exchange DDE variables with your PC.
To start the AdeptWindows DDE Server from the Windows Program Manager, choose:
To display the Adept DDE Server window, double−click the DDE Server icon on the Windows taskbar. The
following window is displayed:
• Display displays a list of active hosts, the number of variables for each host, and the current value of each
variable. See Getting DDE Status Information for details.
• Terminate stops the DDE Server and closes the program.
• Ok minimizes the Adept DDE Server window as an icon on the Windows taskbar (see AdeptWindows
DDE Taskbar Icon ).
To start AdeptWindows DDE Server from the MS−DOS prompt, use the following command:
<path>adept
where <path> is the full path name to the directory where the file ADEPT.EXE is located, and adept executes the
program file ADEPT.EXE.
Note: Since the DDE Server now uses the Windows system hosts, you no longer specify the node name when
starting DDE Server from the MS−DOS propt.
c:\adept\adeptwindows\program\adept
Command line execution can be used to manually start the server by typing the commands at the MS−DOS prompt,
or these commands can be embedded in your AUTOEXEC.BAT or WIN.INI file to automatically start the server
each time your PC is booted.
Once a host is defined, the DDE Server automatically senses if a host is requesting information and then sends it to
the defined address. The connection to and disconnection from the host is handled automatically through the
software.
The Windows HOSTS file is used to define, modify, or delete a V+ host. You can edit the Windows HOSTS file
using Notepad, Wordpad, or any other text editor that can output an ASCII text file.
C:\WINDOWS\HOSTS.SAM
Note: After you are done editing HOSTS.SAM, you must save it as HOSTS (without the .SAM extension) so that
Windows 95 will recognize the defined host names.
C:\WINDOWS\SYSTEM32\DRIVERS\ETC\HOSTS
Note: If the Windows HOSTS file does not exist, you must create it.
3. Define, modify, or delete hosts in the Windows HOSTS file. An example file is shown below.
Enter the IP address followed by the corresponding host name and an optional comment (all comments
must start with the # character). You must enter the IP address in decimal format (e.g., 172.16.144.1).
4. Save the edited file into the same directory from which it was opened. The file must be saved as HOSTS
(without any extension) so that Windows will recognize the host names defined in the file.
Once it is enabled, the DDE driver loads automatically when AIM is started. It executes as a separate program task
in V+ task 9 and uses negligible CPU time until it is accessed by the AdeptWindows DDE Server through the
network.
Caution: The V+ Extensions license must be installed on the Adept controller in order to run AIM and the DDE
driver.
The item name identifies a V+ system item or an AIM variable. It consists of a number of names or numbers
delimited by “\” (backslash without quotes) characters. Currently, all item names must begin with one of the
following:
For example, the item name “sys\controller_serial_number” returns the serial number of the Adept controller.
The system names are defined in the DDE initialization database, DDEINI.DB, which you may modify as desired.
The system names refer to V+ expressions with optional arguments. You can use up to three different arguments in
each expression. The values of the three optional fields following the argument name are substituted into the V+
expression in place of dummy parameters “#1”, “#2”, and “#3”.
switch(#1[#2])
In this example, “robot” is the first argument, and “1” is the second argument.
AIM variables are specified as: “aim\module\variable” where “module” is the name of a loaded (but not necessarily
selected) resource module, and “variable” is the name of a Variable database record in that module. If “module” is
omitted (as in “aim\\variable”), the global Variable database is accessed.
In the current implementation, all "sys\" items may have their polling time set in the BASEINI.DB record. All
"aim\" items in the Variable database allow you to set the polling time and control read−write access for all AIM
variables. To minimize system overhead, static data items (such as "controller_serial_number") should have the
polling time set to zero (do not poll).
Note: Even if the polling interval is set to zero, AIM variable values are always sent to the client whenever they are
changed by an AIM SET or SETS statement or by an AIM menu page. Therefore, to improve efficiency, always use
a polling interval of zero for AIM variables unless they are being changed by some other method.
Database record fields that are linked to an AIM variable are not automatically polled when the field value changes.
The window lists the names of all connected hosts and the number of variables for each host. Once the window is
opened, the information is dynamically updated as connections and links are established or terminated. This feature
is helpful for status information during operation of a DDE connection and for debugging a new DDE application.
To obtain details about a specific host, click the corresponding Expand button. The following window is displayed:
Like the DDE Status Window, once the Host Information window is opened, the information is dynamically updated
as connections and links are established or terminated.
Caution: The DDE initialization records control the interaction between the Adept DDE driver and other DDE
applications. Therefore, it is recommended that you have a good understanding of DDE, AIM customizing, and your
application before attempting to create or modify DDE initialization records.
Once the record is opened, you can change the values on the record page. AIM automatically saves the changes
when closing the record page.
You can now create records that outline specific V + functions and/or V + variables that you want to write to the
AdeptWindows DDE Server task on the PC. There are nine predefined DDE records included in AIM. The function
of each record is fully described in the record's Description field. You can copy and edit one of the existing records
or create a new record from scratch. (The steps below use the copy and edit method.)
To edit the fields on the new record page, select the desired field and enter the information. See the section titled
"Customizing Initialization Databases" in the AIM Customizer's Reference Guide for details. The following
information must be entered:
1. Enter the name in item 1 that will be used by the DDE client to refer to this record. The name must contain
only alphanumeric characters and underscores.
2. Verify the information in item 2. The Page Name field must contain "DDE_SYS". The File Name field
must contain "ini.mnu".
3. Enter a description for the record page in item 3.
4. Verify that the Command Line field (item 4) contains the information shown in the diagram above.
5. Set the #A field in item 5 to zero or blank. All other fields in this group should be blank.
6. Set all fields in item 6 to blank.
After the record is created, you must also create a definition as shown in the following section.
Note: Once the record is saved, you can edit the values on the record. See Modifying DDE Records in AIM for
details.
Once the DDE record is created you must define the V+ expression that will be associated with that record.
Seek => Index => double−click the record name created in the previous section
1. Enter the name in item 1 that will be used by the DDE client to refer to this record. The name must contain
only alphanumeric characters and underscores.
When this expression is evaluated, any arguments of the form #1, #2, or #3 are replaced by additional "\"
arguments found in the request from the DDE client.
4. The field in item 4 is optional. If blank, this DDE item cannot be written. If nonblank, it must be a V+
global variable name of the same type as the expression in item 3. This variable occurs on the left side of an
equal (=) sign in an assignment operation. Array variables are permitted and may contain #1−type
arguments.
When this expression is evaluated, any arguments of the form #1, #2, or #3 are replaced by additional "\"
arguments found in the request from the DDE client.
5. Set the optional polling time by entering a value in the Polling time field (item 5). For example, if you
You also can create variables in the Variables database in AIM 3.1 or later that can be accessed (read/write) through
the DDE link. These variables may be of any type available to the Variables database records. See the section titled
"Variable Database" in the MotionWare User's Guide for details on creating Variable records.
Once a Variables database record is created, you can control DDE access to the record using the DDE Access
options:
• Select Read to set up the Variable record for read access from a PC application using DDE.
• Select Write to set up the Variable record for write access from a PC application using DDE.
The Write check box is available only when the Read check box is selected.
• Set the polling time for the variable by entering a value in the Polling time field. For example, if you enter
5, the information is updated every five seconds.
A polling time of zero means that the information is updated only when it changes (see the note in See Hot
and Cold Links). This is useful for items that never change, such as constants, ID numbers, number of
robots, etc.
Microsoft Excel provides a good example of using DDE to read static and dynamic data.
The following examples assume that you have defined the V+ host as "User1". If not, simply substitute your host
name where "User1" appears.
The "|" and "!" characters are delimiters for the application name, topic name, and item name. "User1" represents a
V+ host name that you defined in the AdeptWindows DDE Server. See Links\xd2 ying DDE Item Names" on page *
for details on the item name format.
=Adept|User1!sys\controller_serial_number
Press the Enter key. The cell displays the serial number of the Adept controller.
=Adept|User1!sys\time_since_boot
Press the Enter key. The cell displays the time that has elapsed since the controller was booted.
Continue watching the screen to see the time update automatically.
Here is an example of a link to an AIM variable named status in an AIM resource module named assembly_cell. The
V+ host name for the Adept controller that is running AIM is mtr_cell.
=Adept|mtr_cell!aim\assembly_cell\status
You do not have to be connected to the Adept controller to use the AdeptWindows Offline Editor.
Restrictions
• Although indentation is performed, V+ control structures are not validated
• GOTO labels are not validated
• Some V+ and MicroV+ commands are not currently supported
Get Around
The editor window expands to the maximum size of the PC monitor screen. You can adjust the size of the window
using the icons located at the upper right−hand corner of the window.
The Editing Toolbar icons provide a shortcut for common program editing operations (cut, copy, paste, etc.)
The Loop/Branch Toolbar icons provide a shortcut for inserting looping and branching structures into your
programs.
Inserts an IF structure into the program on the line below the cursor position
Inserts a CASE structure into the program on the line below the cursor position
Inserts a FOR structure into the program on the line below the cursor position
Inserts a WHILE structure into the program on the line below the cursor position
Inserts a DO structure into the program on the line below the cursor position
The Motion Toolbar icons provide a shortcut for inserting motion program instructions into your program.
• File
• Edit
• Search
• Project
• Insert
• Tools
• Window
• Help
The online help system should address most of your AdeptWindows usage and V+ programming questions.
However, if you require further assistance, Adept provides an applications questions hotline along with several other
services for applications and software support. See How Can I Get Help? for details.
The AdeptWindows Offline Editor provides immediate access to proper keyword syntax. To display the syntax of
any V+ keyword:
3. Choose Show abbreviated syntax . The correct syntax for the keyword is displayed.
4. Choose OK to close the syntax display.
Details on Keywords
Note: This feature requires that Adobe Acrobat Reader is installed on the system and that Adept's Manuals on CD
ROM is available in the CD−ROM drive or copied onto the system's hard drive.
You can access the online version of the V+ Language Reference Guide at any time by pressing the F1 key. The V+
Language Reference Guide is displayed in an Acrobat Reader window.
Note: This feature requires that Adobe Acrobat Reader is installed on the system and that Adept's Manuals on
CD−ROM is available in the CD−ROM drive or copied onto the system's hard drive.
Choose from the Acrobat Reader toolbar to return to the Offline Editor window.
Getting Around
When a program file is opened, the first program in the file is displayed. There are several options for moving from
one program in the file to another.
Navigate
The Find option allows you to quickly locate a specified text string. To use the Find option:
• Use the Find What field to specify the text to search for. You can match the specified case by selecting
Match Case.
• Choose Find Prev. to individually find each occurrence of the specified text.
• Choose Find Next to individually find each occurrence of the specified text.
• Choose Cancel to clear all entries and close the dialog box.
The Replace option allows you to quickly locate a specified text string and then replace it with a different
(specified) text string. To use the Replace option:
• Use the Find What field to specify the text to search for. You can match the specified case by selecting
Match Case.
• Use the Replace With field to specify the new (replacement) text.
• Choose Find Next followed by Replace. Then Find to individually find and replace each occurrence of the
specified text.
• Choose Replace All to find and replace every occurrence of the specified text.
• Choose Done to close the dialog box.
When the cursor is on a line with a CALL instruction, choose the Goto Prgm option (or press Ctrl+G) to open a
new window and display the called program. If the cursor is not on a line with a CALL instruction, the editor
displays a dialog box that asks you for the program name. The following restrictions apply:
After using the Goto Prgm option, you can use the Prev. Prgm option (or press Ctrl+P) to display the previous
program.
Note: The editor window displays only the previously viewed programs that are contained in the current file. It
cannot switch from the current file window back to the previously displayed file window.
Choose the List All Pgms option (or press Ctrl+A) to display an alphabetical pick list of all the programs in the file.
Double−click one of the programs on the pick list to open that program for editing.
Choose the List Bad Pgms option (or press Ctrl+B) to display a pick list of the programs that have syntax errors.
Once a program is opened (by double−clicking on the program name) use the Next Error menu option (or press
Ctrl+E) to locate each error.
Navigate
It is often useful to see the call/caller relationship among different programs in a program file. This is particularly
true in a large file containing many programs, or when you are trying to understand a V+ application written by
someone else.
Choose
This option provides an interactive display of the CALL hierarchy of programs in a file. Navigate works only for
program files that are open. The CALL relationship is displayed with file icons next to the program names. These
icons can be interpreted as follows:
• An open file icon indicates that the branch of the call tree has been expanded.
• A closed file icon indicates that this program is the end of a branch (it calls no other programs).
• A closed file icon with a “+” indicates that this branch is not fully expanded and the program contains calls
to other programs that are not displayed.
• A closed file icon with an “x” indicates that this program is not in the current file.
Note: Do not use the Navigate option to return to the original call tree. This option creates a call tree for the current
program. It does not take you back to the original call tree.
• Enter the new program name in the New Program Name field. (The disk file and the program use this
name.) The program name must conform to V+ file name restrictions.
To open an existing program file, choose the open folder icon or:
Use the Look in field to locate the drive/directory where the file is stored.
Double−click the desired file name. You also can enter the desired file name in the File name: field.
Use the Files of type field to control the file type(s) displayed in window.
Choose Open to display the file. Choose Cancel to clear all entries and close the dialog box.
The editor window is displayed after you create a new program file or open an existing program file:
At this point, you can begin typing V+ code just as you would if you were using the SEE editor on the Adept
controller. See the V+ Language User's Guide for information on using the SEE editor. See the V+ Language User's
Guide for information on V+ commands.
The AdeptWindows Offline Editor has several “automated” features to assist you:
• It checks the program instructions for the proper syntax as they are entered. If you type an unknown
command or use a command incorrectly, the line is flagged with a question mark (?).
• It formats each line with the proper indentation for all logic loops (FOR, WHILE, etc.).
• It color codes variable names, instructions, and comments for easy identification. You can select the color
used for each item (see page 124 for details).
You can use the Loop/Branch and Motion toolbars to access icons that automatically insert For, While, Do, etc.,
structures and motion program instructions into your programs.
Additionally, the Edit menu and Editing toolbar include a list of options, such as Undo, Cut, Copy, Paste, etc., that
simplify program editing.
The AdeptWindows Offline Editor includes several useful tools for working with program variables.
3. Choose Display variable properties. The variable’s properties are displayed in a window.
4. Choose 	OK to close the window.
Replacing a Variable
The AdeptWindows Offline Editor allows you to easily replace a variable with another variable in the current
program or in the module. To replace any variable in your V+ program:
3. Choose Replace with another variable from current program or Replace with another variable from
current module. A listing of available program or module variables is displayed.
4. Choose the new variable from the variable list.
5. Choose OK to close the list and insert the new variable into the program.
When you build a project, the AdeptWindows Offline Editor locates the source files and transfers them from the
source directories to the target directories.
Building a Project
• Enter the directory and path where the project will be stored. You can type the information or choose
Browse to scroll through a list of available drives/directories.
• Enter the project name. The name must conform to filename specifications defined in Windows 95 and
Windows NT 4.0. The file name can contain up to 255 characters (including spaces) except for the
following:
Note: V+ versions 8.4 and 10.5 apply to all releases of version 8.x and version 10.x, respectively.
• Choose OK to save all entries and close the dialog box, or choose Cancel to clear all entries and close the
dialog box.
At this point, you must create the V+ program files for the project and place these files on the project file list.
The Project Information dialog box displays information about the project (name, description, date created, date
modified, etc.). You also have the option to edit the following items:
• You can edit the project description directly in the Description field.
• You can edit the Major and Minor Project Version numbers.
• You can change the V+ version by typing the new version number or by choosing Browse to scroll through
a list of available versions.
• After you have finished viewing/editing the dialog box, choose Done to close the dialog box.
The Project Files dialog box is used to modify the files within the current (loaded) project. To display the Project
Files dialog box:
The File Attributes dialog box allows you to change the attributes (Source/Destination File Type and Target
Directory) for the file selected on the Project File dialog box. To display the File Attributes dialog box:
• The File Name field displays the name of the selected file.
• The Read Only option is not enabled in this release.
• Use the Source File Type group to set the file type for the source file.
• V+ Source Code: a V+ file that can be edited with the AdeptWindows Offline Editor.
• Data File: any source file on the PC.
• Documentation: a text file created by a text editing program.
• Project File: a file with a .PRO extension. This file is used as a directory to other files in the project.
• Select Squeezed if you want all comments and blank lines removed from the destination file. The .SQU
extension is automatically added to the destination file name.
Note: The Destination File Name is enabled only for V+ Source Code files.
• Enter the destination directory and file name. This is the location that the file is copied to when you build
the project. You can type the information or choose Browse to scroll through a list of available directories.
• Choose OK to save all entries and close the dialog box. Choose Cancel to clear all entries and close the
dialog box.
Building a Project
Once your project is completed (you have created a project and written all of the V+ programs for the project), you
are ready to “build” the project. The Build menu option, located on the Project menu, copies all of the V+ program
files for the project to the specified target directories.
The target directory can be a floppy disk (for transfer to the Adept controller, creation of a utility disk, etc.) or any
directory on the hard disk drive of your PC. If the Ethernet NFS option is installed on your PC and on the Adept
controller, you can directly access the hard disk drive on the controller and use any directory on that drive as a
“target” directory. See the AdeptNet User's Guide for details on installing the NFS option.
If you select the Squeezed option (on the File Attributes dialog box), all header information, comments, and blank
lines are removed from the specified file(s) as they are being copied to the target directories.
The program name is removed from the list and the program is deleted from the file.
• Choose New to create a new program in the file.
• Choose Rename to rename the selected program.
• Choose Copy to make a copy of the selected program and insert it in the current file.
• Choose Done to close the Program List dialog box.
Highlighting Colors
The AdeptWindows Offline Editor can insert a standard header template at the top of every program. This is an
option that is selected on the New File/Program Name dialog box.
The editor includes a dialog box that allows you to customize the header template information. This is useful for
adding header information that is used in every program (this eliminates retyping it each time). For example, you
could have a standard template that includes your company name and address; your name as the program author;
and categories for typing program−specific information (abstract, input/output parameters, side effects, etc.).
The template has six predefined categories: ABSTRACT, INPUT PARAM, OUTPUT PARAM, SIDE EFFECTS,
DATA STRUCT, and MISC. You can edit the template as follows:
The AdeptWindows Offline Editor allows you to customize the colors used to identify variables, comments, and
other parts of a program.
• Select the category that you want to change in the scroll window.
• Foreground Color sets the color of the text.
• Background Color sets the color of the area behind the text.
Note: Always use different (contrasting) colors for the foreground and background. Otherwise, the
corresponding text line(s) will not be legible.
• Choose Change to save the new settings.
• Choose Cancel to clear the new settings and close the dialog box. This must be done instead of selecting
Change.
The AdeptWindows Offline Editor allows you to display or hide the toolbars in the Offline Editor window.
or
or
Each of these menu items works like a toggle switch—each time you select it, the display mode changes. A check
mark next to the menu item indicates that the toolbar is displayed.
The window displays a text file with the call tree listing. The file is displayed using Windows Notepad. It can be
viewed, edited, and saved with Notepad or any text editor.
Keyword Listing
The keyword listing menu item searches the program file for all occurrences of a keyword and outputs this to a text
file.
• Enter the Input File to process. This automatically defaults to the path and file name of the file currently
being edited. However, you can enter the path and file name of any program file.
• Enter the Output File name (this is the text file that contains the search results). The default file name is
LISTING.OUT.
• Check the Program Attributes box to insert the input file header information at the beginning of the
listing.
• Check Keyword Listing box to search for a specific keyword. Enter the keyword(s) in the corresponding
field. If you wish to search for multiple keywords, enter all keywords separated by a comma.
• Choose OK to save all entries and close the dialog box. Choose Cancel to clear all entries and close the
dialog box. If you choose OK, a window displays the search results:
The window displays a text file with the keyword listing. The file is displayed using Windows Notepad. It can be
viewed, edited, and saved with Notepad or any text editor.
Note: The Print and Print Preview options use the standard Windows printer interface.
The ID keyword
MENU events
Window Size
Example V+ Program
The /BUFFERED keyword may appear in the FOPEN instruction when used for creating new icons. It causes the
subsequent WRITEs to the icon to be buffered to 512−byte blocks. The syntax for WRITE remains unchanged.
The new /EVENT CONNECT keyword enables connect and disconnect event notification.
The ID Keyword
ID(11,1)
In V+ version 14.x, the above code returns a bit mask value. The first bit and the last bit apply to AdeptWindows
applications.
For example, if the above command returns a value of ^H1B on a system that is running AdeptWindows, this hex
value translates to the binary value:
In V+ version 14.x and later, the /MENU keyword may appear only in the FSET instruction. (In version 11.x, the
/MENU keyword was also allowed in the FOPEN instruction.)
Menu Events
Menu events may arrive at any time (if they are enabled) rather than just when the user clicks on the menu bar.
These apparently random events always have menu ID (event[1]) equal to zero. For example, when you enter the
following command:
<event[1] = 0, event[2] = 1;
followed by:
followed by:
These events are intended to elicit the FSET /PULLDOWN instructions from V+ to set the contents of all possible
pulldown menus.
Window Size
In V+ version 11.x, the minimum window size (for windows containing a title bar) is 64 x 64. (This means that
windows with a dimension of less than 64 x 64 are automatically increased to 64 x 64.)
In V+ version 12.x or later, the minimum window size is 8 x 8 (this is the same as the minimum size for windows
without title bars).
If your program specifies a window dimension less than 64 x 64, the window displayed in V+ version 14.x will be
smaller than it was in V+ version 11.x.
Example V+ Program
The following V+ program illustrates the correct use of the items discussed in this appendix.
.PROGRAM example()
; ABSTRACT: The following example program shows how to use an event loop
; to make selections in a menu program.
;
; INPUT PARM: None
;
; OUTPUT PARM: None
;
; SIDE EFFECTS: None
;
;* Copyright (c) 1997 by Adept Technology Inc.
;−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−
wn.e.menu = 14
wn.e.connect = 20
wn.e.disconnect = 21
quit = FALSE
DO
GETEVENT (glun) event[]
CASE event[0] OF
VALUE wn.e.menu: ;Menu selection
IF event[1] == 0 THEN
ELSE
menu = event[1]
item = event[2]
CASE menu OF
VALUE 1: ;Menu 1
CASE item OF
VALUE 1: ;Selection 1
TYPE "Code for Item 1−1"
VALUE 2: ;Selection 2
TYPE "Code for Item 1−2"
END
VALUE 2: ;Menu 2
CASE item OF
VALUE 1: ;Selection 1
TYPE "Code for Item 2−1"
VALUE 3: ;Selection 3
TYPE "Code for Item 2−3"
END
VALUE 3: ;Menu 3
CASE item OF
VALUE 1:
quit = TRUE ;Request to quit
END
END ;CASE menu OF
END ;IF event[1]
; When the window is no longer needed, delete it and detach from the
; logical unit.
RETURN
.END
DDE Errors
Ethernet TCP/IP
V+ License
DDE Errors
You may receive DDE errors in the following situations:
• Connecting to a host
• Using DDE in Microsoft Excel
Connecting to Host
When connecting to a host, the connection is typically made within several seconds. If the Connect to Host dialog
box and hourglass symbol continue to remain on the screen, check the following:
1. The host must be correctly defined. You can display the host information by double−clicking the host name
in the Connect to Host dialog box. See Defining, Modifying, or Deleting a V+ Host for details.
2. AIM must be running on the Adept controller. See Specifying DDE Item Names for details.
3. The AIM DDE Enabled option must be initialized. If it is not, you must turn it on and then restart AIM. See
Installing DDE With AIM for details.
Choose No and start up the AdeptWindows DDE server. If the AdeptWindows DDE server is running,
check that the host name is correct in the Excel formula and that the named host is connected (see Defining,
Modifying, or Deleting a V+ Host).
• If the cell shows "#NAME?", it means the AdeptWindows DDE server does not support the item (variable)
name. Check the spelling of the item name. Once Excel has established a connection with the
AdeptWindows DDE server, and cells have been defined with links to the server, you can check all the
linked connections by selecting the Links option from the Excel Edit menu.
Ethernet Communications
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 the
topic Changing Software Switches and Network Settings 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.
• 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 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.
For more information about troubleshooting your Ethernet connection, please see “Troubleshooting Ethernet
Problems” in Knowledge Express on Adept’s web site at:
http://www1.adept.com/main/ke/data/Procedures/EtherTrouble/EtherTroubleTOC.html
For more information about IP addresses, please see “Understanding IP Addresses” in Knowledge Express on
Adept’s web site at: http://www1.adept.com/main/ke/data/Procedures/EtherTrouble/ethernet_trouble_IP.html
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.
In most cases, this reestablishes the connection. However, if you receive a timeout error (10060), simply reconnect
AdeptWindows PC.
If the Adept controller locks up or crashes while AdeptWindows PC is running, you can reestablish the connection
as follows:
If the controller crashes repeatedly, report the problem to customer service. More...
To export any other window, you can use any PC−based screen capture program (such as HiJaak by Quarterdeck
Corporation). Once the window is captured, it can be saved to a file on the PC.
You can also use the Windows screen copy command to capture the screen contents.
1. Press ALT + PRINT SCREEN to copy the active window to the Windows clipboard.
2. Press PRINT SCREEN to copy the entire screen to the Windows clipboard.
The clipboard contents can be pasted into a program or saved to a file. See the Windows online help for details.
V+ License
When upgrading a system from V+ version 11 to 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).