Skip to main content

Robot Program Configuration and Saving Interface

What You See​

In the "Save Location" section, you have inputs for defining the "File Name" as LayupProgram1 and the directory path where the file will be stored, with accompanying "Open" buttons likely for accessing the file or path directly. The "Post Processor" segment details settings for selecting a "Type" and indicates a specific "Post File" is loaded (AFP-XS Rev E KUKA), complete with options to load, unload, refresh, or edit, and it confirms the file is valid for use. Under "Program Settings," there are options to override default TCP and base settings, and a choice to ignore simulation errors, suggesting readiness for different operational scenarios. Buttons for "Generate" and "Abort" provide controls for initiating or stopping the program generation process.

What It Means​

This is a critical part of the robotic programming suite, providing tools for precise program setup and control before deployment to the robot's control system.

Save Location​

"Save Location": Ensures organized storage and quick retrieval of robot program files, enhancing operational workflow.

  • File Name: User-defined program name
  • Directory Path: Storage location on system
  • Open Buttons: Quick access to files or directories

Post Processor Configuration​

The post-processor translates generic robot commands into controller-specific code.

Type Selection​

"Type": A dropdown menu for specifying the post-processor to ensure compatibility with various robot controllers.

Common types include:

  • KUKA KRL
  • ABB RAPID
  • Fanuc LS
  • Universal Robots
  • Custom processors

Post File Management​

"Post File": This specifies the actual file used for post-processing.

Control options:

  1. "Load": Brings the file into active use
  2. "Unload": Deactivates it from the current session
  3. "Refresh": Revalidates or updates connection to the post-processor file
  4. "Edit": Allows for changes to the file's parameters or content

"Valid": This status reassures the user that the post-processor is correctly configured and ready for operation.

Robot Information​

"Name": Indicates the robot's model number, ensuring the correct kinematic model is used.

Program Settings​

Advanced options for program generation:

  1. "Override TCP": Allows temporary changes to the tool center point

    • Use when TCP differs from simulation
    • Testing with different tools
    • Compensating for tool wear

  2. "Override Base": Permits base coordinate modifications

    • Different fixture setups
    • Multiple workstations
    • Coordinate system changes

  3. "Ignore Simulation Errors": Permits program compilation despite issues

    • Use with caution
    • Only for known, non-critical errors
    • Testing purposes
    • Expert users only

Generation Controls​

  1. "Generate" Button:

    • Initiates program creation
    • Applies all settings
    • Creates output file

  2. "Abort" Button:

    • Stops generation process
    • Use if errors detected
    • Cancels without saving

Program Generation Workflow​

Pre-Generation Checklist​

  1. Simulation Verification

    • All checks passed
    • No collision detected
    • Paths validated
    • Timing confirmed

  2. Post-Processor Setup

    • Correct type selected
    • Valid file loaded
    • Robot model matches
    • Version compatibility

  3. Settings Review

    • File name appropriate
    • Save location accessible
    • Overrides necessary?
    • Error handling decided

Generation Process​

  1. Click Generate

    • Progress indicator shows
    • Processing messages appear
    • File creation begins

  2. Monitor Progress

    • Watch for warnings
    • Note any conversions
    • Verify completion

  3. Output Verification

    • Check file created
    • Review file size
    • Open in text editor
    • Verify structure

Post-Generation Actions​

  1. File Review

    • Check header information
    • Verify coordinate systems
    • Review motion commands
    • Confirm process parameters

  2. Transfer to Robot

    • Use appropriate method (USB, network, etc.)
    • Verify file integrity
    • Load into controller
    • Test in T1 mode first

  3. Documentation

    • Record generation parameters
    • Note any overrides used
    • Document post-processor version
    • Archive simulation files

Common Issues and Solutions​

Generation Failures​

Post-processor not found

  • Verify file path
  • Check file permissions
  • Reload post-processor

Invalid robot configuration

  • Confirm robot model
  • Check kinematic parameters
  • Verify work envelope

Path conversion errors

  • Review simulation for issues
  • Check for singularities
  • Verify reach limitations

Output Problems​

Incomplete programs

  • Check disk space
  • Verify write permissions
  • Review error logs

Format issues

  • Confirm post-processor version
  • Check controller compatibility
  • Verify syntax requirements

Best Practices​

  1. Always simulate first: Never generate without successful simulation
  2. Use descriptive names: Include date, part, version in filename
  3. Maintain backups: Archive both simulation and generated files
  4. Version control: Track changes and iterations
  5. Test incrementally: Run programs in stages on actual hardware
  6. Document changes: Note any manual edits to generated code