CONFIG_C, Installation
| File Name | Program Name | File Type | Description |
|---|---|---|---|
|
CONFIG_C.V2 |
a.config_c |
B |
Controller configuration utility |
The options under this menu item are used when upgrading a V+ system. The purpose of these operations is to carry forward all the custom configuration information from the old system to the new system. See Upgrading Your V+ System for details on installing a new V+ system.
SAVE current ROBOT DATA
NOTE: This menu item followed by an asterisk(*) indicates that the operation cannot be performed because of an incompatibility between the edition of CONFIG_C being used and the current V+ system. Use the edition of CONFIG_C that was supplied with your old V+ system.
This option creates configuration data files for the robots and external encoders that the current V+ system is configured to control. These data files can be stored on any disk, and can be used later to restore robot and encoder configuration data to the V+ system.
You are asked which disk drive should receive the data files. If an optional floppy drive is indicated, you are asked to insert a diskette. All the data files are created automatically. Each file name is displayed for reference. For example, if an error occurs, the file name should help you to understand the problem. If the files were written to a diskette, you are advised to write-protect and label the diskette.
|
CAUTION: Any existing files with the same names are overwritten without warning! |
INSTALL a NEW V+ SYSTEM
This option copies the new V+ system to the desired output disk drive and then duplicates the system configuration from the old V+ system on the new V+ system disk.
CONFIG_C automates most of the installation process. As noted above, however, the robot and encoder configuration data must have been saved in disk files before the installation process is initiated. After completing this installation step, you must complete the installation process by selecting step #3 (APPLY saved ROBOT DATA).
The entire installation process can take up to 45 minutes. Most of that time is spent making backup copies of your old and new V+ systems; you can stop the process at any time while making these copies. However, after the process of configuring your new V+ system has begun, do not interrupt the installation process. The system informs you when the uninterruptible portion of the process has been reached, and you can stop at that point.
NOTE: Use the edition of CONFIG_C that you received with the new
V+ system.
Make sure you clearly identify the diskettes used during the installation process. There is no way for the program to tell if you have inserted the wrong diskette in response to a request. Carefully read the program messages before you respond to each prompt.
During installation, answer the program questions about the system disks.
In various situations, the program recommends that you make a backup copy of the old and/or new V+ systems. If you agree, DISKCOPY is invoked to make the copy. You should be familiar with the use of the DISKCOPY program to copy a V+ system and to copy a diskette image.
NOTE: In most situations Adept strongly recommends that you make a backup, and you are asked a second time if you want to make the backup.
After the appropriate backup disks are made, the program asks you to put one or the other of the system disks in the floppy drive so that configuration information can be read and confirmation can be made that needed files are present on the new system disk.
Next, the actual installation process begins, and it should not be interrupted. The following steps are performed:
-
The new system is copied to the specified output drive.
-
The appropriate device modules are installed in the V+ system file on the output disk.
NOTE: If the installer cannot find the necessary device-module file(s), you are asked for the disk to be accessed.
-
The configuration information from the old system is written to the output disk.
NOTE: No check is made to ensure that the robot selections defined in the configuration data match the device modules that are present on the disk. That is, if the old system is incorrectly configured, the new system is also.
Finally, you are told what steps must be performed to load the robot data from the disk files created in step #1 of the three-step installation process.
APPLY saved ROBOT DATA
|
CAUTION: For Cobra s600 or s800 systems (purchased before 2005), when using a customized SPEC file, you must manually re-enter any customized SPEC data when upgrading the V+ operating system software. Details... |
This option applies the saved robot and encoder data from the old V+ system to the new V+ system disk.
The system must have been booted from the disk created with step #2 above.
-
After the purpose of the menu item is displayed, you are given an opportunity to cancel the menu selection.
-
Next, the robot and external encoder configuration of the current system is displayed, and you are given another chance to cancel the process.
-
You are asked which disk drive contains the configuration data files. If an optional floppy drive is indicated, you are asked to insert the diskette. The program looks for the configuration data files on the specified disk in the subdirectory \CONFIG_C\ with the names that were displayed during step #1.
-
After confirming that the required files are present, you are given one more chance to cancel the process. (If any required file is not found, its file specification is displayed, and the process cannot be continued.)
-
If you agree to continue, all the data files are read automatically. Each file name is displayed for reference. For example, if an error occurs, the file name should help you to understand the problem.
NOTE: As the files are read, several lines of output may be displayed. You are advised by the program to use CTRL+S/CTRL+Q to control the output. Some of those lines may appear to be error messages. (Refer to the documentation for the SPEC utility in the Adept SmartMotion Developer's Guide for an explanation of the messages displayed while a configuration data file is being read.) In general, such messages result from changes that have been made to the V+ system or the CONFIG_C program and do not indicate a real problem.
- After all the data files are read, you are asked if that data should be written to a V+ system disk. If so, you are told that the system disk must be the one from which the current V+ system was booted. If you indicate that the data should not be written to a V+ system disk, the ramifications are explained and you are asked to confirm your choice.
