MELFA-Works

What is MELFA-Works?

MELFA-Works is an add-in tool(*1) for SolidWorks(*2) that can be used to simulate Mitsubishi Electric industrial robots.
Using MELFA-Works, it becomes possible to verify robot program operations and creat processing path data.
*1) An add-in tool is a software program that adds certain functions to application software packages.
*2) SolidWorks® is a registered trademark of SolidWorks Corp, (USA).
*This product requires SolidWorks. Please note that SolidWorks needs to be provided by the customer.

Features of MELFA-Works

·         MELFA-Works is an add-in tool that runs under SolidWorks.

·         MELFA-Works can simulate production systems using robots on personal computers, and it is possible to make use of peripheral devices and parts such as hands created using SolidWorks as it is.

·         In the simulation it is possible to convert processing paths defined for workpieces to data and output this data.

·         Since MELFA-Works includes RT ToolBox2 (mini), it can create programs and change parameters.

Windows®-compatible

Robot model setting

·         This function allows selecting a model name from a displayed list and setting the robot model.

·         A robot can be placed using positions relative to the CAD origin or other parts. Layout setting via value entry is also possible.

·         A traveling axis can be installed to a robot to verify the operation of the system equipped with this.

·         (Please refer to the "MELFA-Works Instruction Manual" for robots supported by this software.)

Installation of hands, Handling of work

·         Hands designed/created in SolidWorks® can be installed on robots. An ATC (Auto Tool Changer) can also be specified for each hand.

·         Simulations of hand signal control can be created using a robot program to handle workpieces.

Loading of part data and rearrangement

·         Part data created in SolidWorks® can be loaded.

·         The positions of loaded parts can be rearranged relative to the CAD origin and other parts.

·         Part positions can also be changed via numerical input.

·         Please Check the SolidWorks® website and other published documents for the latest specifications.

Virtual Controller

·         MELFA-Works allows starting a virtual robot controller supporting a positioned robot.

·         Since this virtual controller simulates the actual robot controller almost exactly, it can be used just like an actual controller in almost all operations, such as program creation, parameter setting and monitoring, using RT ToolBox2.

Also, by connecting a virtual controller with the currently displayed robot, the movement of a robot program can be reproduced as it is.

Assignment of robot programs

·         Use the RT Toolbox2, to create an operable program in this software.

·         Robot programs can be used as is without any modifications.

·         A different robot program can also be specified for each task slot.

Robot program debugging functions

The following functions are provided to support the debug of robot programs.

·         Step operation : A specified program can be executed step by step.

·         Breakpoint : Breakpoints can be set in a specified program.

·         Direct execution : Desired robot commands can be executed.

Jog function

The robot shown in SolidWorks® can be jogged just like a real robot.

Offline teaching

·         The robot posture can be set up on the screen in advance.

Simulation of robot operations

Robot programs, including I/O signals, can be simulated.This means that movements of the actual system can be recreated directly and accurately.
The following two methods are provided to simulate I/O signals of your robot controller.

·         Create simple definitions of operations associated with I/O signals.

·         Link I/O signals with GX Simulator.

Interference checks

·         Interference between the robot and peripheral devices can be checked.

·         A target of interference check can be specified by a simple mouse click it on the screen.

·         Information explaining the condition of interference that occurred (such as the contacted part, program line that was being executed when the interference occured, and corresponding robot position) can be saved to a logfile.