AML Management Unit Release Notes Version 3.
Copyright Notice © 2003 ADIC The information contained in this document is subject to change without notice. This document contains proprietary information which is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced, or translated to another language without prior written consent of ADIC.
AMU Version 3.12 AMU Release Notes This release notes cover the release of the AML Management Software (AMU) Version 3.12. For more information, call the ADIC Technical Assistance Center at: • 1.800.827.3822 (outside of Europe and Japan) • 00.800.9999.3822 (Europe and Japan) For Your Safety WARNING: AMU SENDS TIME CONTROLLED COMMANDS TO ITS ROBOTS. WHEN STARTING AMU, MAKE SURE THAT NO PERSON, NO ARMS OR HANDS, ARE PLACED INSIDE THE STORAGE DEVICE.
AMU System Hardware and Software Hardware/software Requirements Processor min. Intel Pentium 350 MHz Memory min. 64 MB RAM (128 MB recommended, required for systems with 2 or more hosts) Hard disk min. one hard disk with 850 MB free space (2 hard disks recommended) Operating system OS/2 4.0 with fixpack 15, MPTS 6.0, and TCP/IP 4.31 Database manager IBM DATABASE 7.01 Communication TCP/IP 4.
AMU Table 2 Gripper Dependencies, AML/J Systems Gripper Robot SW V0 (201000060) Eprom AMU >= 2.4D V 1.2 od. V 1-3 >= 2.4i >= 3.0 V 2.2, V 3-3 od. V 3-4 >= 4.01 V 4-4 V1 (201001140) V2 (201001300) V2 (201001980) V2 (201002869) V2 (201003500) Table 3 V 5-5 Gripper Dependencies, AML/2 and AML/E Systems Gripper 3480 Robot SW V1 (401000700) AMU 2.2 or 3.0 >= 2.4i V2 (401002100) V3 (401004840) MM D2 V1 (401001220) V1 (401003090) V2 (401004050) PS V1 (401004930) 2.3 or 3.
AMU Table 4 Special cases for drive and media integration LTO Ultrium1 Gripper (with Eprom) Drive a Medium /J IBM 3580 LTO LP Robot Software /2 + /E /J /2 + /E V5 (with V5-5) PW V2 >= 4.11 (401003600) AMU DCI >= 2.30H > 3.10D >V3 a. Drive type see in list of supported drives Table 5 Medium Drive-to-AMU and DCI compatibility Drive a Firmware DCI AMU AIT-1 SDX-300 04E5 4 3.11 AIT-2 SDX-500 0200.cy10 4 3.11 AIT-3 SDX-700 0103.cy10 4 3.11 DLT IV DLT 7000 LP 107 4 3.
AMU AMU Installation Program This AMU 3.12 Release can be used to upgrade existing AMU systems, to fix current bugs, or to enable you to use the latest supported hardware/drives. To install or upgrade please use Install.cmd script. Installation To install the AMU version 3.12, perform the following steps: Step 1 Check the correct level of your system software with the command syslevel (MPTS, DB/2). AMU version 3.12 requires Database Manager 7.01 and MPTS Fixpack 6.
AMU Changes and Updates This section contains information about changes performed in various versions of AMU system. AMU 3.12 AMU 3.12 is required for DAS 3.12 and vice versa. NOTE: Fixed Bugs Table 6 Bugs fixed in AMU 3.12 Related Ticket PR105 PR108 PR114 PR122 PR123 PR124 PR125 PR127 6 Explanation of Changes Error in menus and help files. Some lexical errors in dialogs and on-line help Fix for "AMU looping".
AMU Table 6 Bugs fixed in AMU 3.12 Related Ticket PR128 Explanation of Changes 'Frozen' command queue. There can be a situation (not often) when the AMU command queue hangs. In this state AMU accepts the commands (from host or DAS) but does't issue any command for robot. This state can be as long as 15 minutes. Fixed in AMU3.11H2 HOC tcp/ip sockets leak. Under some customer configurations Trap in BUD module. When there is no available socket (see PR129), BUD can trap on allocating the new connection.
AMU Table 7 Improvements in AMU 3.11 Related Ticket PR152 Explanation of Changes Media Identifier settings should be changeable from AMU GUI Configuration changes Support of LTO-2 FibreChannel drives (as DCI-connected) added in AMU 3.12. AMU 3.11 AMU 3.11 is required for DAS 3.11 and vice versa. NOTE: Table 8 Changes in version 3.11 Related Ticket PR205 PR206 PR207 PR208 Explanation of Changes Drive Control Interface extension AMU 3.11 supports new drives as DCI-connected.
AMU Version 3.10E Table 9 Changes in version 3.10E Related Ticket ET90532 ET36851 ET43402 ET44142 ET44151 ET65747} Explanation of Changes New Function: AMU version will be shown in the AMU log New Function: The AMU checks for configurations with wrong load modules (only functional working combinations will be allowed and started) New Function: Drive serial number. Assign serial numbers for the drives. ACI applications can access this information.
AMU Version 3.10D Table 10 Changes in the named modules for version 3.10D Module Explanation of Changes New Feature: Support of new Media Types: • IBM LTO (C3) • DVC-Pro Large (VB) • DVC-Pro Medium (VC) New Feature: Support of New Drives: • IBM LTO Ultrium (only with Drive Control Interface - DCI) (D1) • DVC (DD) Version 3.10C Table 11 Module amuconst.rc amuconst.ini ArcSQLe.dll Art.exe Bud.exe Cfg.dll Cfg.dll, HocPmac.dll Clm.exe ConClean.exe ConCont.dll ConLog.
AMU Table 11 Changes in the modules for version 3.10C Module DBconv.exe filetr.exe hoc3964.dll, hocaml2.dll HocAml2.dll HocEhll.exe HocScan.dll HocTcpIp.dll install.cmd KrnLStep.dll KrnLUtil.dll KrnPhys.dll Explanation of Changes When started with option '-d' (restore existing DBconv.dat file) the existance of the DBconv.dat file was not checked before the database was dropped. So it was possible to loose the ABBA database by a simple user mistake.
AMU Table 11 Changes in the modules for version 3.10C Module KrnPmac.dll Log.dll LogView.exe Rte.exe Explanation of Changes fixed problem with PMAC register dump Build answer for correct command with correct return code. Avoid blocking of KrnP when first command is to a DG drive and it fails. Remember PIDDATA for command if there is an error in KrnReadAMUPQueue called from KrnSendContMsg. Build answer for failed command if KrnSendContMsg fails, not for command that triggered this function.
AMU Module Description KrnPhys.DLL access to the request table now with a semaphore. cfg.dll CAN address for DCI changed to 2 digits, additional PROC KRNLOAD Version 3.10A Module Description KrnUtil.DLL Krn Trap after a negative answer for a no longer necessary KEEP (rc=1094 or N203) changes of the logwrites for **kernel** state mismatch ConTrc.DLL Write/Formate trace produced an error message KrnPMAC.DLL Teach with option 1P has produced a trap, because of a too small buffer HocEHLL.
AMU • Determine time for drive dismount by the robot Backup Demon AMU 3.10 will be distributed with a new BUD for increased safety control of the database on the Dual-AMU. The new features are: • No more updates are possible from a passive to an active AMU • In the case of a missing coordinate, the BUD will now send futher updates to the other coordinates. Configuration For the DCI, create the new Interface type ID (DCI-SOTEC) to configure CAN address and the DCI port.
AMU Detailed AMU process changes The detailed process cnanges are described here. ARC • no changes ART, LOG, TRC • fixed trap in ART in some conditions at midnight BUD • fixed trap in BUD module if no sockets available.
AMU • Fix for "AMU looping" • Fix for 'Hanged' KEEPs • Fix for 'Frozen' command queue KRN-P • Error when accessing DCI drives on systems with more then 1 DCI unit. Fixed in AMU3.11H1 • Support of LTO-2 FibreChannel drives (as DCI-connected). • Bug in CanLib can corrupt the preceding commands. Fixed in AMU3.
AMU Addressed Tickets The addressed tickets and issues are described in this section. AMU 3.11 Ticket number ET31428 CR12218 Problem Eject to 'unknown' position (not scanned by Auto-Invt). This ticket was announced as fixed in AMU 3.10E but was actually fixed in AMU 3.11. The problem was related with eject commands to EIF unit with Auto-Inventory command running. Under this condition (not all I/O slots were scanned) AMU can produce the error “Source position is unknown.
AMU Ticket number Problem ET81763 Dual-AMU problem with ACOM command There was a problem with the ACOM command during switch -- AMU generated wrong response on these conditions. This problem has not been resolved. ET65185 DB update for drive failed in the case of a move to the problem box -- Trap with IBM RICC Adapter. Enhancement -- LTO no longer requires DCI. Version 3.10D Ticket number Problem GR000004295 Solved pass-through problem (AML/2).
AMU Ticket number Problem ET0000036288 3270 communication problems without RTE ET0000037043 Insert Cleaning cartridges to a predefined position in the AML ET0000037074 TCP/IP Communication to ROBAR ET0000040136 Installation of AMU with BUD ET0000040136 Installation of AMU with BUD ET0000041574 Online Log is hanging up ET0000044344 SYS 3170 bei HOC EHLL Communication ET0000045397 Display of Online Log, if moved to the outside of monitor ET0000046169 Cleaning DLT7000 endless loop Version
AMU Version 3.10 Ticket number Problem ET0000030906 Enhancement of Logwrite for the FLIP command ET0000033088 Kernel State mismatch produced a stop of the system ET0000030878 sort files in the View Log files dialog ET0000031062 Prevent the system failure SYS3170 ET0000015086 Move to the second problembox in a AML/J GR000002985 Problems with the file transfer of the AMUCONF.
AMU Known Bugs and Work Arounds Ticket number Problem Workaround ET0000050741 Rho File Manager starts KRN without any options (Problem with DAS or Dual-AMU) After using RFM, restarts the AMU (shutdown AMU, call AmuStart.cmd) GR000002878 AMU-Manual Mode also for AML/J Configure the robot type R0 (AML/2) PR213 Router between active and passive AMU doesn't work for ROBAR commands use only the active AMU when sending commands from ROBAR. This problem will be fixed in the first hotfix to AMU 3.
AMU Example of Start Scripts Examples of start scripts are shown here. Startup.cmd startcm cd amu call AmuStart.cmd AmuStart.cmd @REM ----------------------------------------------------------@REM Filename: AmuStart.cmd @REM Description: Start Script for the AMU modules @REM @REM [cd can @REM DL Download binaries to CAN-controller @REM cd ..
