Difference in format of native SRC and DAT files between KRC1 and KRC2?

[efsever]

Dear Community,

Please keep in mind that;
"we are first time users of Robots who are trying to communicate KUKA KR125 with KR C1 controller with DELCAM PowerMILL Robot Interface".
For this reason please accept our excuses for any funny or stupid questions.

We are preparing *.SRC and *.DAT files from our package.

Our problem;
=========
As far as stated by local KUKA support team in our country;

The *.SRC and *.DAT files prepared for KR C2 controller
is not compatible with KR C1 controller
due to common incompatible backward version problem.

But they are not helping us to describe;
differences between native NC codes of  KR C1 and KR C2
presenting some guide or anything else.

Our question;
==========
Please help/direct/guide/inform us by presenting some information about differences of native NC codes of old and latest KUKA controllers.

By this help we could able to tune our postprocessor and configuration files.
Thank you form know on.

[SkyeFire]

What are "native NC codes"?

KUKA Robot Language (KRL) has not changed appreciably between the KRC1 and KRC2 controllers.  Some features have been added, but things like major variable types and commands have not changed.

Now, certain bits of information in the header have probably changed, but this information is generally non-critical and easily reproducible.  This is the type of code I'm referring to:

Code:

&ACCESS RV1
&REL 335
&COMMENT Search Rack 1
&PARAM TEMPLATE = C:\KRC\Roboter\Template\NonProcessVorgabe
&PARAM EDITMASK = *

Note the & prefix on each line. 

Still, it's simple enough to get the correct header -- simply generate a program on the KCP using the menus, but leave it empty of any program code, and use the blank SRC and DAT file generated as your templates.

Other than this, there should be no difference.  KRL ignores case, whitespace, leading spacing, and other typographical fiddly bits. 

[efsever]

Hi,
Let me thank you first for your interest shown to begineers like us.
We will discuss your valuable thoughts with local KUKA support team, the we will try without prejudice.

Let me explain meaning of "native NC codes"; since we are CAD/CAM people, we use this words for any piece of programs to drive any CNC machine and robots. We are preparing NC codes from our CAM package PowerMILL package with Robot Interface, we are not using KUKA Control Panel as you expect.

Thanks once more.

[SkyeFire]

However, you are generating KRL SRC and DAT files to load into the robot, correct?  As long as your SRC and DAT files consist of standard KRL commands and variables, the issues should be minimal.

Perhaps you could post some examples of your actual working code, the SRC and DAT files you have already produced successfully for use in KUKA robots?

[optimus_prime]

Ultimately Compile the src or dat file.
So can be compiler version change.