ROBOGUIDE Remark

- ROBOGUIDE might not work correctly with graphic driver bundled in Windows.
- Virtual iPendant and Vision PC controls may not work correctly
by Internet Explorer settings and security software settings.
Internet Explorer11 recommended.
- Some functions do not support Windows Vista or later.
Please refer vision manual for vision PC control system requirements.
- On 32Bit Windows, lack of memory or resource might make ROBOGUIDE unstable.
Windows 64-bit is recommended.
- 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 continuously with soft panel screen
and so on, ROBOGUIDE may not work correctly.
- 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 might not be 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 the simulator plug in is used to monitor actual robots, ROBOGUIDE cannot
display DCS settings of
actual robots 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 workcell
that has Japanese object name may not work on English environment.)
If you need to share workcells between multiple language 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.
 H787 CR-15iA
H768 CR-35iA
H777 M-10iAe
H865 M-430iA/2F
H864 M-430iA/2FH
H699 M-430iA/4FH
H843 M-430iA/2PH
P-XXXiA
H707 R-1000iA/120F-7B
H745 SR-3iA
H746 SR-6iA
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.
When you changed from virtual iPendant to legacy pendant, the drawing is also
impossible.
- Virtual robot V5.30 does not work on Windows 7 or later.
- You cannot make new PaintPRO, PickPRO, iRPickPRO workcell from ROBOGUIDE core
workcell create wizard.
Please execute PaintPRO, PickPRO or iRPickPRO directly from task bar
Start/Program/FANUC Robotics in order to
create new workcell.
- Motion optimization 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, V7 and V8.
- 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 because
ROBOGUIDE will 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 an actual robot to a virtual robot that is older than the
actual robot,
the virtual robot might not work correctly.
In this case, you might 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 virtual TP and try again.
- Multiple parts picking/dropping 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
Internet Explorer.
- You cannot use the same CAD file name for different CAD files.
- You can use substitute a virtual robot for older virtual robots that do not
exist.
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.
- 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 instruction 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.
- 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 manually in this case.
- If your PC does not have graphic system that can process OpenGL fast, some
functions that
require advanced graphic function might not work. (For example, vision laser
function,
4D edit function might not work on CPU integrated graphic.)
- If your PC does not have the latest graphic driver from graphic chip vendor,
ROBOGUIDE may
not work correctly.
- Data monitor option of virtual robot V6.30 and V6.33 is not supported.
- If a robot has no shift operation option (J591), the FWD key of virtual TP may
not work.
- Robot neighborhood operation on Explorer is not supported on Windows 64-bit.
- Loaded models from CALLADA, OBJ, VRML, RWX and 3DS format are optimized models.
- When ROBOGUIDE is uninstalled, it may need to install vision PC controls again.
- Virtual robot V6.30 and V6.33 might not work correctly when start mode is changed
from controlled
start to cold start. Please restart the robot in this case.
- Virtual robot V6.30 might not work correctly.
 Virtual robot V6.33 may work as substitution.
- When a virtual robot has Chinese dictionary with multi dictionaries, alarm
messages of the robot
might not be displayed correctly.
- ROBOGUIDE does not display alarm messages correctly when the messages are in
other language
except English.
- When you set an object transparent, then the object is not highlighted at
collision.
- When override is very low, the robot might not move by jogging with virtual TP
jog keys.
- If multiple users log in a PC, ROBOGUIDE might not work correctly.
- Taught points that have different user frame number are not connected on node
map.
Joint representation taught points that have none zero user frame number are not
connected
on node map.
- Node map might not be drawn correctly during program editing. In this case,
please click
[Redraw node map] of cell browser right-click menu of the program in order to
redraw node map.
- When tool frame comment or user frame comment is changed with virtual TP,
ROBOGUIDE
might not get the change correctly. Please restart the robot in this case.
- Virtual robot might not work correctly after PC sleeping.
- When program name is specified by string register for call instruction, profiler
and simulation
program may not work correctly.
- Virtual robots do not support power consumption monitor function.
- When a virtual robot is created again, you may need to input robot setting
parameters.
Then you need to do controlled start the robot and F3 AUTO setting in robot
maintenance
screen with virtual TP.
- Some functions do not support perspective view mode.
- When you update ROBOGUIDE, old setting might be reset.
- Virtual robot devices have size limitation.
- Data collection span is more than refresh rate setting.
- When you make a robot to load a large LS file, ROBOGUIDE might raise
time out message even if the loading is completed.
Please do cold start to reset the robot.
You could load the LS file with virtual teach pendant.
- Collecting one of reducer, power, or duty information and recording simulation
AVI, may make ROBOGUIDE unstable.
Please disable collecting reducer, power duty information to avoid that.
- If robot backup files contain no relationship file, creating a new virtual
robot from the backup files may fail.
- Hot start after enabling continuous turn function may cause the robot to crash.
- When Windows shutdown process starts, ROBOGUIDE does not work correctly
even if the process is interrupted. Please close your workcell before Windows
shutdown.
- Large or small scale (like 0.01) may cause object clicking failure.
- For complicated robots or left hand robots, some functions like simulation may
not work correctly.
- When you select another robot, key pad of virtual TP might be not correct.
Please close and re-open it.
- ROBOGUIDE may not display alarm messages correctly. Please use virtual TP to get
correct messages.
- You may need to remove some robot options by manual.
- Please do not install ROBOGUIDE and RCS to a PC.
- Clip panes are ignored during simulation recording.
- When you add a motion group in serialize wizard, you may need to reopen the
workcell.
- When you make a virtual robot from a backup files, some macro settings might be
loaded.
Please load SYSMACRO.SV for the case.
- When you make a virtual robot from a backup files, some settings might be loaded.
Please load necessary file such as SYSMACRO.SV for the case.
- When you make a virtual robot from a backup files and make new workcell such as
renaming workcell, the settings of virtual robot might be lost.
- Please refer online help for other limitations.