All UP and Folge programs contain many parameters that have to be equal for the motion command in the SRC file and the corresponding data structure in the DAT file.
Any difference in the values of the corresponding parameters can be difficult to predict during the operation of the robot.
In the picture below we can see some motion point instruction.
This text is shown on KCP when we run the program.
But this is only a user-friendly text and has no effect on the movement of the robot itself.
However it's important that this text corresponds to the KRL code parameters interpreted by the robot during motion.
For our example the visible VB value is 5.
The real motion parameters are hidden in the KRL source code that we can display in the DReS editor when we remove the VKRC viewer.
Now we can see that the value of VB stored in the third parameter is 50.
This means that somebody could change this manually in any plain text editor without checking the syntax.
Now, if we take a look into the DAT file where parameters for this motion are declared we can see another inconsistency.
In the P1_D structure the VB parameter has the value 20.
To validate the integrity of data we can use the VKRC Data Integrity plugin.
The plugin can validate all current SRC files opened in the editor or search for SRC files in the given location.
After processing, a report with all found data incompatibilities will be generated.
In the picture below we can see a message generated for our example data.
The following parameters will be checked for the specified motion type.
| Tool | Base VW VSOFT >= 8.1 |
VB | ACC | VE / Genau | SPSTrig | |
| PTP | x | x | x | x | x | x |
| LIN | x | x | x | x | x | x |
| CIR | x | x | x | x | x | x |
| KPTP | x | x | x | x | x | x |
| KLIN | x | x | x | x | x | x |
| KCIR | x | x | x | x | x | x |
| SPTP | x | x | x | x | x | x |
| SLIN | x | x | x | x | x | x |
| SCIR | x | x | x | x | x | x |
| LIN SUCHEN | x | x | x |