MCIS RPC sl Installation instructions MCIS RPC V Build 2

Transcription

1 MCIS RPC sl Installation instructions Installation Package for MCIS RPC sl The installation package may be installed only on manufacturing host computers for solution line controllers. System requirements and supplementary conditions The installation may be performed only on a manufacturing host computer (PC) for a solution line controller. The software may be installed under Windows XP only. If the HMI sl has not yet been installed, this is installed as well. At least 1GB free hard disk memory is required. Either HMI sl Version must be installed on the PC or no HMI sl at all. Installation on a newer HMI sl as Version is not permissible. After installing the software, the system must be rebooted. The installation, during which the screens are not always displayed, can take up to 20 min. The end of the installation process is displayed by a PopUp window which prompts the user to reboot the system. Only maximally one host instance may be configured on the PC that is used as host computer The mmc.ini must be adapted after the Readme which is also installed on the target computer. Note: In order to prevent diverging time stamps between incoming and outgoing alarms, the command C_ORDER_M SFCT=100 must be called up regularly for time synchronization between the PCU and NCU. Installation of the software If the HMI has not yet been installed, it is installed automatically. Admin rights are required to perform the installation process. In service mode, copy the contents of the file RPCsl_V B2.zip into an arbitrary temporary folder of the manufacturing host computer. Start the file Setup_RPC_sl.exe with a double-click. Follow the onscreen instructions. Note: After performing the installation and rebooting the system, please read the Readme file (start menu... SINUMERIK MCIS RP SL -> readme) Siemens AG 2010 GER I IA&DT WSTN APC MT Page 1 of 5

2 Possible messages during the installation Text: No Admin rights! Setup for MCIS RPC sl will not be installed." Reason: The user is not logged in as an administrator. The installation will not continue. Log out and log in as an administrator. Verification of the successfully installation The installation finishes with a pop-up window which requests the user to reboot the system. After successfully installing the RPC software, the following files are created in the HMI sl installation directory C:\Programs\Siemens\Sinumerik\HMIsl\siemens\sinumerik\hmi\base. Contents of the base folder MCIS_RpcSl.exe MCIS_RPCSLCFG.exe MFC71.dll SCVarset.ini cp_param.ini After completing the installation process, restart the computer. BackUp files The file systemconfiguration.ini, if any, is renamed into systemconfiguration.ini.org. Starting from the base folder of MCIS RPC sl, a new directory rpcsl is created in which the date-stamped log file of the installation and the file version.txt are stored. Siemens AG 2010 GER I IA&DT WEST TSS 7C Page 2 of 5

3 Supplementary notes Reading out the TC_MOP parameters with single tool AP In the configuration program you can set that, when reading out a single tool, the cutting edge-related tool monitoring data are output as well. Afterwards, read out a single tool. According to the DocOnCD, the parameter TC_MOP11 includes the tool life setpoint and the parameter TC_MOP13 the quantity setpoint. When opening the file read out by RPC, these two setpoints, however, are included in the parameters TC_MOP5 and TC_MOP6. According to the DocOnCD, these two parameters are provided for the wear actual and setpoint values. Solution With the TC_MOP parameters, RPC always outputs a consecutive list including MOP1-9. The DocOnCD also comprises nine parameters which are, however, called MOP1-6, MOP11, MOP13 and MOP15. RPC MOP assignment Real data contents Contents acc. to DocOnCD Description MOP1 MOP1 MOP1 Tool life prewarning limit MOP2 MOP2 MOP2 Residual tool life MOP3 MOP3 MOP3 Quantity prewarning limit MOP4 MOP4 MOP4 Residual quantity MOP5 MOP5 MOP5 Wear prewarning limit MOP6 MOP6 MOP6 Residual wear MOP7 MOP11 MOP11 Tool life setpoint MOP8 MOP13 MOP13 Quantity setpoint MOP9 MOP15 MOP15 Wear setpoint Machine status from DB12.DBB14 AP When reading out the machine status from DB12.DBB14, the results cannot be interpreted unambiguously on the basis of the existing documentation. MCIS_RPC and MCIS_RPCsl show a correct behavior. The results are to be interpreted as follows: MCIS_RPC on Powerline and MCIS_RPCsl on solution line (machine version) Siemens AG 2010 GER I IA&DT WEST TSS 7C Page 3 of 5

4 DB12.DBX3.1 DB12.DBX14.0 DB12.DBX14.1 DB12.DBX14.2 Status Meaning 1 X X X 4 Components deactivated Active Faulty Restart Inactive MCIS_RPC on Powerline and MCIS_RPCsl on solution line (TPS version) DB12.DBX7.1 DB12.DBX5.0 DB12.DBX5.1 DB12.DBX5.2 Status Meaning 1 X X X 4 Components deactivated Active Faulty Restart Inactive Read out parameter designation with single tool AP The file returned when reading out a single tool includes the parameters TC_DP26-34 with the cutting edge parameters. According to the DocOnCD, these parameters do not exist. Solution In fact, these parameters include $TC_DPV, $TC_DPV3, $TC_DPV4, $TC_DPV5, $TC_DPVN3, $TC_DPVN4, $TC_DPVN5 and $TC_DPNT. However, the parameters are correctly designated in the complete list of all tools. 1.) When reading all tool data (T_DATA_M, SFct.20), the TO_INI.INI file from the NCK is transferred to the FLR. As this file is created by the NCK, the extended cutting edge data are correctly displayed. $TC_DPV, $TC_DPV3, etc. When reading resp. reporting a single tool (T_DATA_M, SFct.21-23), the extended cutting edge data are transferred as $TC_DP26 to $TC_DP<n> (depending on the configuration). The parameter number of the extended cutting edge data can vary depending on the cutting edge data configuration. The customer must determine for his machine which data have been set for the parameters TC_DP T_DATA_M ignores the paths resp. file names specified by the user AP With the subfunctions of T_DATA_M, the user can specify a name for the data returned by RPC. For example with the Sfct. 10 (output of a list of all programs in the NC), the user can specify a name and path under Name 2 under which the list shall be stored on the host computer. Siemens AG 2010 GER I IA&DT WEST TSS 7C Page 4 of 5

5 If the user enters a name, this is ignored. The list is always stored as NcPrList.001. Specified paths are not considered. Instead, the list is always stored in the Host Put directory. The same applies with Sfct 20 (output of a list of all tools). This also concerns Sfct 1 (transfer NC program to the host computer). The user can specify a name under which he wants to store the program on the FLR. This name, however, is not evaluated. The system always uses the name of the program in the NC. Conversely, a user-defined alternative name is entered with R_DATA_M (program transfer to the NC). The MCIS_RPC documentation does not unambiguously describe how paths and file names must be specified. In principle, the user cannot specify his own names for the T_DATA_M subfunctions. 1 Transfer NC program to the FLR Name1: \mpf.dir\nc1.mpf SL_M1 1 \mpf.dir\nc1.mpf C:\TMP\HOST\PUT\NC1.MPF Transfer list of existing NC programs to the Name1: \mpf.dir 10 FLR SL_M1 10 \mpf.dir C:\TMP\HOST\PUT\NCPRLIST Transfer list of existing tools to the FLR Name1: empty SL_M1 20 C:\TMP\HOST\PUT\TOOLDATA.001 Siemens AG 2010 GER I IA&DT WEST TSS 7C Page 5 of 5