KUKA

KUKA KRC2/VKRC2 Industrial Robot Controller

The KRC2 and VKRC2 are two versions of the same hardware platform, but they are tailored for very different operational environments.

While the “K” stands for KUKA, the “V” in VKRC2 stands for Volkswagen, as this version was specifically developed for the VW Group and its subsidiaries (Audi, SEAT, Skoda).

Comparison at a Glance

Feature    KRC2 (Standard)    VKRC2 (VW Standard)

Primary User    General Industrial Market    VW Group / Automotive Tier 1

Software    KUKA System Software (KSS)    VW System Software (VSS)

Programming    KRL (KUKA Robot Language)    Inline forms / “Folge” & “Up”

Flexibility    High (Open programming)    Low (Locked to standards)

Ease of Use    Requires training in KRL    Designed for rapid deployment

Key Differences

1. Programming Philosophy

KRC2 (KRL): This is the “open” version. A programmer has full access to the KUKA Robot Language (KRL). You can create complex custom logic, use variables freely, and build highly specialized functions.

VKRC2 (Structured): This is “menu-driven.” To maintain consistency across thousands of robots in a VW factory, programming is restricted to a specific structure:

Folge (Sequence): The main program sequence.

Up (Subroutine): Smaller motion sub-programs.

Makro: Logic-only routines (no motion).

Note: In VKRC2. you generally cannot type free-form code unless you enter “Expert Mode” with a special key/password.

KRC2/VKRC2

2. User Interface

The KCP (KUKA Control Panel) looks identical for both, but the soft-keys and menus are different.

VKRC2 menus focus on automotive-specific tasks like “Spot Welding” or “Gripper Control” using standardized blocks.

KRC2 menus are more general, allowing you to configure various types of industrial fieldbuses and custom kinematic systems more easily.

3. Interbus & Hardware

Because of its automotive roots, the VKRC2 almost always includes the DSE-IBS (Interbus) card you asked about previously, as Interbus was the VW group standard for years. While standard KRC2 units often use it, they are more frequently found with DeviceNet, Profibus, or Ethernet/IP depending on the customer’s factory.

4. Safety & Interfacing

VKRC2 often uses a specific “VW Interface” (X11/X40 connectors) designed to plug directly into the standard VW cell safety PLC.

KRC2 uses the standard X11 interface which is more “universal” for integration into diverse factory environments.

Can you convert a VKRC2 to a KRC2?

Yes, it is a common practice in the used robot market. Since the hardware (PC, drives, motors) is nearly identical, you can “reflash” a VKRC2 to run standard KSS software.

Requirement: You need a standard KSS software installation (e.g., V5.x) and potentially a change in some wiring jumpers on the MFC/ESC safety cards.

Leave a Reply

Your email address will not be published. Required fields are marked *