HMI Advanced SW FC5253-6BX40-1AG_

Transcription

1 HMI Advanced SW FC5253-6BX40-1AG Prerequisite for the installation of this software is a PC with Windows NT 4.0, Service Pack 6 (not Windows 2000!), CD-ROM drive, min. 128MB RAM, 140MB free hard disk capacity and virtual main memory > 140MB. The HMI Advanced SW is functionally the same as MMC 103 SW , but contains extensions and error eliminations as well. HMI Advanced SW contains the five European standard languages. Help for setting and machine data is available in English and German only. Please note the documentation "Starting Up HMI Advanced (IM4)"! Please note the boundary conditions valid for HMI Advanced SW 6.1! General notes for installing HMI Advanced SW: Existing HMI software is detected and an update-installation is performed on it, the data management is unchanged. Please note that the HMI Advanced software contains the standard cycles (version ). All Siemens cycles in the "Standard cycles" directory should therefore be removed from the NC before installation and if necessary GUD7 and SMAC in the "Definitions" directory as well. All files in the directories F:\USER, F:\ADD_ON, F:\OEM remain unchanged. It is therefore important that all changes to.ini files be made in these directories and not in F:\MMC2 or F:\HMI_ADV. INSTALLATION INSTRUCTIONS FOR HMI Advanced SW on PC / PG: 1.) Installation from CD-ROM 2.) Changes from SW ) Compatibility 4.) Tips and Tricks 1.) Software installation from CD-ROM The installation is started by calling SETUP.EXE in the folder HMI Advanced SW on the supplied CD- ROM. You will then be guided through the installation by InstallShield. Any target directory can be selected. Three installation variants are available: Online with link to an NCU / CCU An MPI board must be available in the PC (for example CP5611). The necessary S7 drivers will be installed upon request with the HMI software. The operation of a control system 840D / 810D is the same as for a PCU50 and is possible in this mode. Local without link to an NCU / CCU Local without link to an NCU / CCU with a simulated NCK Note: Both local modes have not been released for use! General notes: The HMI Advanced SW 6.1 is entered in the windows registry during installation and can be deinstalled under System control / Software. The HMI Advanced SW is adapted as standard for a 640x480 screen and can be switched to full-frame display for the current screen resolution (max. 1024x768). The entry "RESOLUTION=1" must be set in the area [control] in file USER\MMC.INI.

2 2.) Changes from HMI Advanced 6.0 HMI Advanced 6.1 is functionally the same as MMC 103 SW 5.3. The main SW 6.1 specific changes are outlined below. Please refer also to the user documentation and to the SIEMENSD.rtf from MMC 103 SW 5.3 if necessary. System: PDF help based on Acrobat Reader 4.0. If an Acrobat Reader 4.0 is available on the PC it will be used. Machine area: The functions scratching and actual value presetting can be based on NCK functionality with NCU software 6.2. NC-MD MC_MM_SYSTEM_FRAME_MASK bit 0 = 1 must be set. Parameters area: Displaying system frames with NCU software 6.x The frames are displayed with the following designations: $P_SETFR system frame for actual value presetting and scratching $P_EXTFR system frame for external zero offset $P_PARTFR system frame for TCARR and PAROT $P_TOOLFR system frame for TOROT and TOFRAME A radius can be entered now for tool type "Drill". PDF help for setting data Tool management: 8VHRILQFKPHWULFVHWWLQJIRUWRROGDWDEDVHDQGFRGHFDUULHU With SW 5.3 and SW 6.0 a softkey interlock for the tool cabinet and code carrier functions for unit changeover (inch/metric changeover) has been incorporated. Automatic conversion of the data for tool cabinet/code carrier processing has now been introduced instead of these softkey interlocks. This means that the data for units in NC and HMI is now viewed and handled in a homogeneous way. This functionality is controlled via entries DATABASE_LENGTH_UNIT and CODECARRIER_LENGTH_UNIT in PARAMTM.INI in the area [TMMODES] introduced with SW 5.3/6.0. The meaning of the entries remains the same, however the actions triggered by the settings change from disabling the softkeys to converting the data. To activate this function entries DATABASE_LENGTH_UNIT and CODECARRIER_LENGTH_UNIT in paramtm.ini must be used to define which unit the cabinet/ code carrier data is available in; and the Inch/Metric changeover must be activated in the NC (general machine data $MN_CONVERT_SCALING_SYSTEM is set to 1). If these entries are not available and the inch/metric functionality in the NC has already been activated, the softkey interlock mechanism for the functions on the tool cabinet and code carrier continues to act as before. The inch/metric changeover functionality in the NC can be used in the HMI tool management in the following NCK version ranges: NCK version from (NCK.P5_20.7) to and from (NCK.P6_43) onwards. No conversions are made on HMI for tool database and code carrier for NCK releases not corresponding to the above versions or for configurations with $MN_CONVERT_SCALING_SYSTEM=0. All tool compensation parameters (TOA parameters) to which a unit has been assigned as well as OEM tool data and cutting edge data, when a unit has been assigned to it over the general machine data , are part of the automatic conversion. The following mechanism has been implemented for the automatic conversion of the tool cabinet data and the code carrier data: the unit for the data carrier LVspecified permanently by the user with entries DATABASE_INCH_MM and CODECARRIER_INCH_MM. This information is used from now on in the tool cabinet, and code carrier data are interpreted according to this definition. To display the tools from the cabinet, the data are converted according to the current setting in NCK if necessary (general MD 10240: MN_SCALING_SYSTEM_IS_METRIC), and for the

3 transmission of this data to the NC and from the NC to the tool cabinet. A detailed description is to be found in paramtm.ini: [TMMODES] ; Using the setting inch/metric for tool data record ;!! NOTICE: The settings described here are only relevant ; when the machine data $MN_CONVERT_SCALING_SYSTEM=1 ; is set in the NC. ; The entry for DATABASE_INCH_MM is only evaluated ; when no unit has yet been entered in the tool data record. ; Typically once! ; For an obsolete NC version ; without the conversion functionality inch/metric, ; or if $MN_CONVERT_SCALING_SYSTEM=0, the NC ; operates without inch/metric conversions. ; In this case, no conversions are made for the ; tool data record either!! ; -1 = No definition for inch/metric ; in the tool data record (default). ; The setting $MN_CONVERT_SCALING_SYSTEM=1 in the ; NC means that the conversion inch/metric ; should be used. The user ; must therefore define the unit for data in the ; tool database. ; As this is not carried out with the setting -1, ; all softkeys for database activities ; are disabled. ; 0 = mm. Defines ; that the data in the tool database ; are in mm when a tool database is opened for the first time ; by a tool management with differentiation inch/ mm. ; The database is expanded by one entry that defines ; that the tool data in the database are in the ; unit mm. ; This is taken into consideration with future data transfers ; between database and NC. ; 1 = inch. Defines ; that the data in the tool database ; are in inch when a tool database is opened for the first time ; by a tool management with differentiation inch/mm. ; The database is expanded by one entry that defines ; that the tool data in the database are in the ; unit inch. ; This is taken into consideration with future data transfers ; between database and NC. DATABASE_INCH_MM=-1 ; Using the setting inch/ metric for code carrier ;!! NOTICE: The settings described here are only relevant, ; when the machine data ; $MN_CONVERT_SCALING_SYSTEM=1 is set in the NC. ; For an obsolete NC ; without the conversion functionality inch/metric, ; or if $MN_CONVERT_SCALING_SYSTEM=0, the NC ; operates without inch/ metric conversions. ; No conversions are therefore made ; for the code carrier either!! ; -1 = No definition for ; inch/metric for code carrier (default). ; The setting $MN_CONVERT_SCALING_SYSTEM=1 in the ; NC means that the conversion inch/metric ; should be used. The user ; must therefore define the unit for data ; on the code carrier.

4 ; As this is not implemented with the setting -1, ; all softkeys for code carrier activities ; are disabled. ; 0 = mm. All effected data ; are written to the code carrier as mm value in future. ; This is taken into consideration for future ; data transfers between code carrier and NC. ; 1 = inch. All effected data are written ; to the code carrier as inch value in future. ; This is taken into consideration with future data transfers ; between code carrier and NC. CODECARRIER_INCH_MM=-1 (UURUHOLPLQDWLRQV,QFKPHWULF'LVSOD\LQJVSHFLDOXQLWVRIOHQJWKDFFRUGLQJWR1&VHWWLQJLQWRROGDWDDQG HGJH2(0GDWD Texts for the units are displayed in national languages in the tool detail screens and in the tool cabinet and catalog screens when special units are defined for the tool OEM data ($MN_CC_TDA_PARAM_UNIT ) and edge OEM data ($MN_CC_TDA_PARAM_UNIT ) in the NC. The texts are loaded from the national language resource file. All "inch" or "inches" strings in this resource file are replaced with the international abbreviation "in". The texts from paramtm.ini for units in this OEM data ("UserDataParamSize" in [ToolEdgeParams] and "[ToolParams]") are ignored in this case. 0DNHUDGLXVDFFHVVLEOHIRUWRROW\SHGULOO The tools of type drill are expanded with the geometrical value radius ($TC_DP6). 7RROUHORFDWLRQLQEXIIHUV The softkey "Searching for an empty location" is redundant in this situation and has been disabled. 7RROOLIHLQZKROHPLQXWHVRQO\ No decimal point could be entered in the tool life columns in the list screens. DUHQRZDOORZHGFKDUDFWHUVLQ7RRO,GHQW In addition to the characters "a" to "z", "A" to "Z", "0" to "9" and "_" (underscore), ".", ",", "-", "+" are allowed characters now when entering a tool designation. This check is also made now with tool details. Due to an error, any character could be entered up till now. 7RROFDELQHW7KHFRQWHQWVRIWKHGLVSOD\ILHOGIRU1DPHLVQRZGLVSOD\HGVRUWHG 7RROFDELQHWWRROFDWDORJVFUHHQVZLWKWDEOHV The entry fields in the tables cannot be exited any more in entry mode with the cursor keys. 7RROFDELQHWWRROFDWDORJFRUUHFWLRQV An incorrect edge number was sometimes displayed for tools with cutting gaps during reselection after an area switchover (edge number after the gap). 6RPHWLPHVPHVVDJHVZHUHRYHUZULWWHQDQGLPPHGLDWHO\GHOHWHGDJDLQLQWKHPDJD]LQHOLVW IRUH[DPSOHWKHWH[W7KHGLVSOD\LVVZLWFKHGWRQRWWUDQVIRUPHGIRU/2$' 7RROHGJHGLVSOD\LQFRPSOHWH All edges were not displayed for multiple-edge tools under the following circumstances: MultiLine display (1 line per cutting edge) of magazine list and minimum number of columns parameterized: only trivial cutting edge data (for example edge number or tool type), no columns for "Standard" cutting edge data, for example length, wear and tear, monitoring data, OEM data parameterized.

5 /RDGPDJD]LQHOLVW If the loading sequence was stopped due to error because the location type was incorrect for example, the incorrect message (UURUZKHQUHDGLQJIURP1&PDJD]LQHDSSHDUHGinstead of the message 0RYLQJWRROPDJD]LQHVWRSSHGZLWKHUURU. /RDGPDJD]LQHOLVW When the loading sequence was terminated due to an error, the softkeys were not enabled when one of the softkeys 7RROGHWDLOV, 1HZFXWWLQJHGJH or 6WDUW had already been pressed once for the tool being processed, before the failed loading sequence. /RDGPDJD]LQHOLVW If the softkey 1HZFXWWLQJHGJH was pressed before the softkey 6WDUW, the setting [DEFAULT_SETTINGS] DEFAULT_WITHOUT_CONFIRM in paramtm.ini was ignored for this loading sequence.,qfkphwulffkdqjhryhu5hvroxwlrqixqfwlrqdolw\iru6,1&20kdvehhqlpsohphqwhg,qwhudfwlrqehwzhhqlqfkphwulffkdqjhryhudqg5(6(7glgqrwdozd\vzrunfruuhfwo\ 7RROFDWDORJFDELQHWFXWWLQJHGJH2(0VFUHHQ7KH2(0XQLWVZHUHQRWGLVSOD\HG FRUUHFWO\LQWKHVFUHHQDIWHUUHVHOHFWLRQZLWKLQFKPHWULFFKDQJHRYHU 7RROFDWDORJFDELQHW,QFKPHWULFFKDQJHRYHU,QYDOLGYDOXHVLQWKHGLVSOD\ZKHQ '$7$%$6(B/(1*7+B81,7 7KHFRGHFDUULHUVHUYHUFRXOGQRWEHVWDUWHG (UURUHOLPLQDWLRQLQWKHUHODWLRQVKLSLQFKPHWULFDQG2(0GDWD An error occurred under the following boundary conditions: In tool catalog/cabinet, tool OEM and cutting edge OEM, during the reselection of tool management after an area switchover, after an NC changeover from mm->inch, when the database was set to inch: if OEM data with the unit 5 (m/s2) or 7 (m/s3) were changed in an area switchover before deselection and not yet written to the database (softkey "OK" or softkey to changeover to another data/cutting edge not yet pressed), the value of the entries were changed to this value after reselection. Program area: Editor: When using the contour editor or the cycle support, the automatic block number generation is not interrupted any more. Editor: The linefeed character ( ) can be removed from the display. New text font in the editor adapted to the resolution of the OP. Access to the network drives can be disabled with protection levels (display MD). Files of type TOP can now be created in the parts program directory (MPF.DIR). Simulation: The simulation is based on NCK SW 5.3 (20.09). A protection level can be assigned to the softkey simulation in DPDH.INI and AEDITOR.INI. The manufacturer cycles (CMA.DIR) are integrated in the simulation. Accessing sequence (search path) is CUS.DIR,CMA.DIR,CST.DIR. Cycles loaded in the simulation are logged under Match data/loaded data/manufacturer cycles. The programs are stored in the simulation in the original location, i.e. a subroutine is now stored in directory /_N_SPF_DIR and not in the current workpiece directory. These programs are deleted again from the simulation with workpiece changeover. 1RWH Cycles (from CUS.DIR, CMA.DIR, CST.DIR) are moved to /_N_SPF_DIR, when the cycles are not preloaded or the cycle interface is not automatically generated. These subroutines remain available after a workpiece changeover.

6 Zooming can be adjusted in the SIM screens with the following entry in the local tool DPWP.INI files and globally in the user directory in the DPMWP.INI and DPTWP.INI templates QRW DFFHVVLEOHYLDRSHUDWLQJSDQHO: [VIS] ;*** only SW6.1 / SW5.4 or later *** ;Zoom reference: ON => at window center or OFF => at coordinates origin ZOOM_AT_CENTER=ON ;*** As with all other SIM graphics elements, the background colour in the simulation screens can be defined for all new workpieces either local or global with the following entry: [VIS_COL] ;Colours code: 0-black, 1-white, 2-red, 3-green, 4-blue, 5-cyan, 6-yellow, 7-magenta, ;8-light gray, 9-dark gray, 10-dark red, 11-dark green, 12-dark blue, 13-dark yellow, ;14-dark cyan, 15-dark magenta, 16-transparent (0 to 15 => XOR with background) ;*** only SW6.1 / SW5.4 or later *** ;Background BG_COL=0 ;*** The settings are accessible to the operator: "Settings/Display and colours/general colours/background" Increasing main memory for simulation The RAM main memory for simulation is defined at present LQWKH6,0UHIHUHQFH ILOHV'+?'3',5?6,0',5?VLPLQLBPFRPPLOOLQJDQGVLPLQLBWFRPWXUQLQJLQWKH6,0SDUW WHPSODWHVLQ+0,B$'9DQG00&?GSPZSLQLPLOOLQJDQGGSWZSLQLWXUQLQJDQGILQDOO\LQWKH SDUWVORFDOGSZSLQLILOHVwith the following default INI entries DODUPWKUHVKROG!.%5$0 UHPDLQLQJPHPRU\WRWDO5$0PDLQPHPRU\IRUDFWLYH6,0VHVVLRQ!0%: [SIM] ;Reserved memory parameters DP_SIMMASCH_MEMORY_WARNING=4 DP_SIMMASCH_RAM_SIZE= The SIM main memory in the current software versions can be increased as follows by adapting these INI entries (globally effective for all new workpieces in the USER directory in an existing or new file GSPZSLQLor GSWZSLQL), these are also the current default settings: [SIM] ;Default memory parameters ;RAM-threshold(KBytes) for warning message DP_SIMMASCH_MEMORY_WARNING=32 ;RAM-size(Bytes): => 1 MB, => 2 MB, max => 4 MB DP_SIMMASCH_RAM_SIZE= With centric drill holes LQWKHWXUQLQJFHQWHU, the end face of the hole is also shown with depth colour information as well as the geometrical contours of the hole in the side views. Services area: The NC function "Cycles in DRAM or on NC Card" is supported. Note: Cycle saving in the FlashFileSystem on the NC Card is very slow. Reading an NC series IB can be very slow as these cycles are also contained in the NC series IB. The ZMODEN protocol for secure data transmission is now available for RS-232 data transmission. The software SINUCOM PCIN 1.3 is required on the external PC.

7 The archive name can now be 25 characters long for archiving to diskette. The structure of the "Upgrade archive" has been changed so that an upgrade archive created with HMI Advanced can also be read with HMI Embedded. Note: An upgrade archive created with SW 6.1 cannot be read with earlier software versions. 1RWH 7KHIXQFWLRQ8SJUDGHFDQQRWEHXVHGLQ6: Diagnostics area: Improved screen layout with 1024x768 resolution. The alarm help has been converted to PDF and corresponds to NCU SW 6. Startup area: The help for machine data has been converted to PDF. The file IB.INI is now situated in directory MMC2. Technology cycles: HMI Advanced SW contains the technology cycles (standard cycles) V Help system: The function "Go to" can now be used to search for any string in the current PDF help file. If the PDF help is called, without a search string (for example alarm no.) being specified by HMI- Advanced, the system jumps to the beginning of the alarm help file (PDF). The old Windows help (for example for PLC errors/operational messages) will continue to be supported. 3.) Compatibility HMI Advanced SW can be combined with the 840D NCU SW 5.x and 6.x, 810D SW 3.x and 4.x. The simulation is based on NCK 5.3 (20.09). Thus generally no simulation is possible when SW 6.x is installed in the NCU. The Help system is based on the documentation for SW 6 AUTOTURN 5.2 is operational. Step7 V5.0 (MLFB 6FC5252-5AY00-2AG_) can be installed and run under HMI Advanced. 4.) Tips and Tricks Tool management: "NewFormNames=0" must be entered from HMI SW 6.0 onwards in the [CONTROL] area of PARAMTM.INI. If the USER/ADD_ON/OEM directory contains old INI files with an old entry (value = 1), the parameters area does not startup however, a message box appears. The tool management SHOULD NOT be activated any more in Regie.ini with Task1=name := paramtm,! Tool management is automatically activated in HMI Advanced when it is activated in the NCU. Contour processor: The orientation of the coordinate system in the contour processor is always defined with the display MD 9650 CMM_POS_COORDINATE_SYSTEM, for example = 8 for technology turning. The MD 9610 CTM_POS is meaningless. Cycle support from SW 4.x: The "old" cycle support known in SW 4.x is available on the ETC bar in the editor when the user cycles directory contains the file COV.COM. It can be copied out of standard cycles if necessary.

8 Editing large files: The ASCII editor on the MMC can edit files with max. 16MB as standard. The max. file size can be increased to 56MB by changing the entry MemFactor= in the file AEDITOR.INI (from SW 4.4 onwards). Protection levels for softkeys in diagnostics and startup: The protection levels for functions in the areas diagnostics and startup accessible over softkeys can be defined in files DG.INI and IB.INI, section [AccessLevel], (from SW 5.1 onwards). Simulation: The technology default (turning/milling) for simulation can be changed with the display MD 9020 TECHNOLOGY= (1: turning, <>1: milling). If necessary, GUD7 in the directory interactive programming/ simulation data must also be adapted with GUD7 in the "Definitions" directory. Note: Delete DPWP.INI as well if changes are made! NC series startup: Skipping "NCK overall reset": From NCK 4.3 onwards file IBN.SYF contains an entry (a command) to generally reset the NCK before a series startup. It can happen with this entry that when machine data UPLOAD_MD_CHANGES_ONLY is set when the series startup archive is being created, the archive cannot be read in any more due to inconsistent archive contents: in which case the archive must be read repeatedly. Should this rare situation arise, the NCK must not be generally reset every time since this will not help. The following settings can be made in this case: New entry in the file DINO.INI: ; options for data in/out (archives), questions and priority of COM interfaces [Function] ; 1: ask before overwriting CFG_RESET.INI, 0: don t ask Ask_for_CFG_RESET.INI=0 With a series startup, the prompt: "The selected file already exists! Overwrite?" appears now with _NC_ACT\CFG_RESET.INI with INI entry Ask_for_CFG_RESET.INI=1. Thus this file and the NCK general reset can be skipped (with softkey NO).