About ROBOGUIDE - Support OS Windows 7 English version(32bit, 64bit) Windows 7 Japanese version(32bit, 64bit) Windows Vista Service Pack2 or later English version(32bit, 64bit) Windows Vista Service Pack2 or later Japanese version(32bit, 64bit) Windows XP Service Pack2 or later English version(32bit, 64bit) Windows XP Service Pack2 or later Japanese version(32bit, 64bit) (*) Windows 7 64bit is recommended. Internet Explorer6 or later .NET Framework3.5 Service Pack1 or later (*) Some functions do not support Windows Vista or later. Virtual robot V5.30 does not work on Windows 7. Some versions of vision PC control do not work on Windows Vista or later. System monitoring option does not work on Windows Vista or later. (*) Windows is a registered trademark of Microsoft Cooperation in the United States and other contries. - CPU PC to run Windows normally. However, low power CPU might not treat heavy workcells correctly. Core2 Quad or higher are recommended. - Graphic system supports OpenGL. Graphic system that can process OpenGL fast is recommended. For example, NVIDIA QUADRO. - 1024x768dot, 65000 colors. 1280x1024dot, True color is recommended. - Normal font size. (96DPI) - Hard disk space 2G bytes. - Memory 500M bytes. 4G bytes memory is recommended. - Mouse for Windows operation. - DVD drive - Ethernet to communicate with robot controllers. (*) Windows 3.1, Windows 95, Windows 98, Windows Me, Windows NT and Windows 2000 are not supported. (*) Virtual PC, VMWare and similar software are not supported (*) Windows XP Mode of Windows 7 is not supported. (*) Remote desktop is not supported. (*) Port 3002 should not be used for other purpose. (*) Computer name must be A-Z, a-z, 0-9 or '-'. (*) Comma decimal separator is not supported. (*) Screen should be 96DPI. (*) You need administrator privilege to execute ROBOGUIDE in some cases. (*) You cannot use Guest acount for ROBOGUIDE. (*) Virtual iPendant may not work correctly by Internet Explorer settings and security software settings. Limitations - If you open copied workcell, virtual robots on it may not work. Please close and open the workcell. - For DispenseTool, you are not supposed to perform Maximum Analog Out (Meter)/Maximum Meter Speed Calibration. - For DispenseTool, you are not supposed to perform Channel 2 Control Calibration. - When you close, open, close ... iPendant continously with soft panel screen and so on, ROBOGUIDE may not work correctly. - When you open another workcell without terminating ROBOGUIDE, ROBOGUIDE may not display correctly. Updating graphic driver may fix this phenomenon. - If installed .NET Framework is old, ROBOGUIDE may not work correctly. For example, when you open online help, you may fail to make new workcell. Please install .NET Framework 3.5 SP1 or later to update .NET Framework. - Lack of memory causes ROBOGUIDE unstable. - It is not possible to take WeldPRO arc spark animation to AVI. - When you open old PickPRO workcell, robot programs in it may be overwritten by PickPRO. - TP programs that are generated by PickPRO may not have wait instruction after pick, drop. Please insert wait instruction manually. - If you disable brake for a virtual robot, ROBOGUIDE may not get brake release time correctly. - Just after adding comment line to a simulation program, the comment line is not displayed correctly. - When simulator plug in is used to monitor actual robot, ROBOGUIDE cannot display DCS settings of actual robot correctly. - Robot link is available on virtual robot V7.40 or later. However, robot link approach deterrence is not available. - A workcell that includes data of another language may not work correctly. (For example, a workcaell that has Japanese object name may not work on English environment.) If you need to share workcells between multiple langauage environments, please use alphabet and digit for object name, program name and so on. - ROBOGUIDE may raise an error after you terminate ROBOGUIDE. Please ignore the error message. - Program shift function can create shifted TP program. Program sub type of shifted TP program may be different from sub type of original TP program. Please modify the sub type manually in the case. - Some robot models do not support to display robot work envelope. - Open a workcell that is created with older version of ROBOGUIDE, virtual camera connection might fail. Please close and open the workcell. - Open a workcell that is created with older version of ROBOGUIDE, virtual camera connection port settings might reset. Please set virtual camera port in General tab of iRVision property page. - The following robots do not support extended axes. H865 M-430iA/2F H864 M-430iA/2FH H699 M-430iA/4FH H843 M-430iA/2PH H798 M-2000iA/900L H799 M-2000iA/1200 - Operation Panel is not supported. - It is not possible to draw current selected position register to graphic screen with virtual iPendant. - Virtual robot V5.30 does not work on Windows 7. - Some versions of vision PC control do not work on Windows Vista or later. - You cannot make new PaintPRO, PickPRO workcell from ROBOGUIDE core workcell create wizard. Please execute PaintPRO or PickPRO directly from task bar Start/Program/FANUC Robotics in order to create new workcell. - Motion optimiztion function of MotionPRO might not work. Please close MotionPRO and try again. - When F-100iA is placed on the workcell, the robot configurations and the graphic model on the screen may not be matched. In this case, please restart the virtual controller with controlled start mode and reconfigure the robot. - The location of EOAT at current TP point may be wrong, if the program is called parent program. - It is not possible to transfer license between ROBOGUIDE V6 and V7. - If disk free space is not enough, ROBOGUIDE may not work correctly. Please keep enough disk free space. Please care to make big AVI files. - You must make workcells on local drive. You cannot use network drive since ROBOGUIDE may be unstable on network drive. - You must not load virtual robot system files (.SV, .VR and so on except numreg.vr, posreg.vr and diocfgsv.io) to real robots. (*) If you load diocfgsv.io, you may need to reconfigure the I/O. - You must not load robot simulator system files (.SV, .VR and so on except numreg.vr and posreg.vr) to real robots. - If you load files from actual robot to virtual robot that is older than the actual robot, the virtual robot might not work correctly. In this case, you need to update ROBOGUIDE to use new virtual robots. - Password (including DCS password) may be reset when you create a virtual robot from a backup files. - If batteryless gun change is selected, it will work as battery gun change. Servo gun reference point detecting and gun mastering do not work. - Virtual TP might not work correctly. Please close vitual TP and try again. - Mutli parts picking/droping target might be wrong if the robot is fast. Enabling TCP trace, increase refresh rate or disabling simulation sync mode may fix it. - External force is not simulated. - Mastering operation with virtual TP might not work correctly. - Gravity compensation is ignored on virtual robots. - Vision PC controls and robot tools may not work on integrated browser. Please use default browser. - You cannot use the same CAD file name for different CAD files. - You can use subsituite a virtual robot for older non existence virtual robots. However, the substitution might not work correctly. For example, virtual iPendant might not work in the case. - If you change selected dictionary of a virtual robot, you need to execute cold start for the robot. - You need vision PC option in order to execute simuation in sample workcells that use virtual camera. - If your workcell folder has very long path name, ROBOGUIDE might not work correctly. Please use shorter path name in the case. - If you need to change configuration of robot, extended axis and so on, please use maintenance screen in controlled start. Please do not change the settings by system variable directly. - Auto back up with virtual TP is not supported. - If too many logic instructions are executed in short time, ROBOGUIDE might not work correctly. For example, the following instructions may be executed many times in short time. LBL[1] IF DI[1]=OFF, JMP LBL[1] Please reduce such execution. For example, use WAIT instuction instead of IF JMP LBL. - If group IO has same configuration of other IO, group IO does not work correctly. - Work envelope function for user tool base does not support special kinematics robot models like M-1iA. - LR HandlingTool robots might cause errors with joint jog tool when virtual teach pendant is enabled. - If there is many I/O connections in a workcell, ROBOGUIDE performance might be down. Please remove unnecessary I/O connections in such cases. - EthernetIP is not supported. - When RUN statement is used to execute another task, ROBOGUIDE may fail to detect program termination. Please stop the simulation manually in this case. - Consumed memory size is different in virtual robots and actual robots. Thus, free memory size will be different. - When you create new virtual robot from a backup files, ROBOGUIDE might not be able to load some robot settings. Please input the parameters manuall in this case. - if your PC does not have graphic system that can process OpenGL fast, some functions that require advanced graphic funciton might not work. (For example, vision laser function) - Data monitor option of virtual robot V...
kmex