KR C4 WorkVisual 4.0 Deploy Error

it means your WorkVisual project is incomplete. creating complete project can be involved. it also requires (so far) manual steps though number of manual steps is getting smaller as WorkVisual gets smarter...

for user, correct thing is to get project from the controller and use it as starting point. you can modify it etc. but all essentials are there.

another way to complete project is to merge it with complete project and absorb missing parts. WorkVisual can try to do this on its own...

Another thing to keep in mind is that WorkVisual must be contfigured before use

Dear Panic Mode,
I have one question regarding deploy/downloading work visual project.

For this process, is it necessary to deselect submit interpreter or just stopiing submit interpreter is enough?

No

Only robot program need to be deselected

Hello everyone,

I have same problem with durmazonur.

I get backup from my KR20-3 (KRC4) and changed profinet device name.
Then I want to deploy same project. But didnt deploy.
I tried merge. And I've solved all the errors. But I didnt deploy again.

Please help me.

So why don't you deploy...?

I do not know. I got a backup from the robot. Then I wanted to install it without making any changes. It did not. The following image appeared on the Resolve conflict tab.

Can I be from Workvisual version? (I use wov 5.0)
My computer is in English.

[size=1em]well, no crystal ball here.. all i do is read... and you should too, screenshot you posted cannot be clearer:[/size]
[size=1em]

"project incomplete, and it cannot be automatically merged with base or active project on a controller".

"project incomplete" ... should be obvious that something is missing in the project
"automatic merging did not work" ... fine, when automatic does not work, consider manual merging
"merge with active or base project" ... tells with what exactly one should try merging this project. and if automatic merge fails, those projects maybe are also incomplete.

Btw, can you please try to be specific? in wrong hands anything can go wrong. so before asking for help:[/size]

[size=1em]1. read READ FIRST[/size]
[size=1em]2. is your WoV installed and configured correctly (integrated options and DTMs?)[/size]
[size=1em]3. what is the exact KSS version running on the controller? (at least major AND minor version of the KSS)[/size]
[size=1em]4. what are the exact names and versions of installed tech options? are they integrated into WoV?[/size]
[size=1em]5. what do you mean EXACTLY by "i got backup of the robot"? is that an image, an archive, KRCdiag, WoV project or something else? how did you collect it and how did you extract WoV project from it? Are you sure you are dealing with working project? Are you sure you are dealing with active project? [/size]

[size=1em]Read manuals:[/size]

[size=1em]* WORKING project is simply one that works [/size]
[size=1em]* ACTIVE project is the current project (and it may or may not work)[/size]
[size=1em]* INITIAL project is just an empty shell, avoid it.[/size]
[size=1em]* BASE project is the factory default[/size]

[size=1em]You can think of BASE project as the smallest working project that KUKA delivers as a template. But it has special role too. For example it is used as a donor to complete missing parts in partial projects when merge is performed. When your project is incomplete but merge is not performed, controller will try to limp by using missing parts from the base project - without updating your incomplete project. This can get people sometimes out of jam but in general this can be bad since user gets impression that things are ok when they are not. But if BASE project is not original or correct for the system (maybe it is from a different system or it is also missing some parts), then it may not be possible to use it to automatically complete your project (one you are trying to deploy). Same may be with presently activated project... or with project you are collected from "backup".[/size]

[size=1em]Workflow is:[/size]
[size=1em]1. get robot working (with a good project)[/size]
[size=1em]2. get compatible WoV installed correctly on your PC[/size]
[size=1em]3. get options from D:\KUKA_OPT and integrate them into WoV you just installed. WoV versions 5.x allow profiles so one can have more than one configuration)[/size]
[size=1em]4. connect WoV machine with robot controller and get copy of working active project[/size]
[size=1em]5. save that project as is (for backup purposes)[/size]
[size=1em]6. save that project as ANOTHER file name (this will be the one you will modify)[/size]
[size=1em]7. make changes as needed[/size]
[size=1em]8. on controller, select T1, deselect program and close any startup plugin or configuration window, and login[/size]
[size=1em]9. deploy and activate project. if hardware or safety was altered, checksum will change so in this case also you also need to activate safety configuration[/size]

[size=1em]ALSO: [/size]

[size=1em]1. every time you try to deploy project, it will get RECOMPILED. this means your project will get MODIFIED - every time. And if your WoV is not installed correctly or configured correctly: ooooops....[/size]

[size=1em]2. if you did not change name of the project in step 6, deploying will overwrite project already on the controller. And if the project on controller is the only fall back option, and there is trouble (started with incomplete or wrong project, changes are not compatible, you don't have WoV correctly installed and configured).... even bigger oooops. situation just got worse.[/size]

[size=1em]3. read messages. try to figure out what they mean and what alternatives are possible... if that does not help, try it word by word and ask what exactly each of them means. [/size]