Hi all,
Can someone please suggest why a "Code generation failed error" occurs when trying to active a project?
And my wvs version is 8.3.26 while the controller is 4.X.X.
How can I update the wvs on the controller?
Please advice
Thanks
Code Generation failed error in wvs?
-
n0909 -
February 25, 2018 at 11:11 PM -
Thread is marked as Resolved.
-
-
[size=1em]
Hi all,
Can someone please suggest why a "Code generation failed error" occurs when trying to active a project?
[/size][size=1em]not enough info... some possible reasons are:[/size]
[size=1em]a) options in WoV and on controller don't match or [/size]
[size=1em]b) that they are not integrated into WoV or [/size]
[size=1em]c) they are not really installed on controller or[/size]
[size=1em]d) you are using wrong project [/size]
[size=1em]etc.[/size][size=1em]And my wvs version is 8.3.26 while the controller is 4.X.X.How can I update the wvs on the controller?[/size]
[size=1em]that makes no sense, please try focusing and proofreading your own content before posting. [/size]
[size=1em]there is no WoV version 8.3.26. there is a KSS with that version (but KSS and WoV are two very different things).[/size]
[size=1em]What do you mean by "controller 4.x.x."? Controller in this case is clearly some sort of KRC4.[/size]
[size=1em]Software version 4.x.x may apply to WoV but ... that is NOT specific enough. i told you already to read READ FIRST....[/size][size=1em]For example WoV 4.x.x is some 30 different versions and ... they are quite different. Newer versions are generally better (more capable in comparison to previous versions) but this is not necessarily always a good thing for particular robot. WoV versions don't even use same file format for projects. They have different compatibility with tech packages etc. WoV included with your robot is not necessarily the newest but it sure will work with your robot. Upgrading WoV can brake that compatibility so you have to ask yourself: what do you stand to gain and also what to lose. i have seen quite few people calling in for help because they attempted upgrade and were not aware of potential issues. This always happens to types that don't read manuals or instructions (does this sound familiar?)[/size]
-
Hi panic mode,
Workvisual ver: 4.0.19_Build0098
KRC4 compact ver: 8.3.28So three problems discovered:
Problem 1: Getting an error when accessing the KRCDiag for sending it to Kuka support.
Problem 2: We have a Profinet package installed, but we cannot access (greyed out) any options in wov under PROFINET -> FUNCTIONS -> Device List and Profinet names. So is this normal? Having had the PROFINET package installed and as per the manual shouldn't this be enabled?
Problem 3: Has anyone had a similar experience with the Anybus X gateway? The wov displays an error stating error in DTM catalog?I have made a rough network map of our cell so kindly help me with some troubleshootingsteps. I could not find these errors in the Manuals/Forums.
Any suggestions/advices welcome
Regards
n -
[size=2]Problem 1.:
Screnshot shows that problem occurs when trying to save file to USB but drive letter is different...How exactly you are trying to generate KRCDIAG? Are you using network path for eample?[/size]
-
About the DTM part:
I've heard some people complaining about the same problem, when running WoV 4.x in Windows 10.
I've worked with WoV 3.0.10 under Win10 with no problems, but my applicatinos where simple, without any options.
Did You tried run WoV inside a Windows 7 virtual machine?
-
i have seen a lot of people complaining about WoV not working correctly. Turns out there is plenty of user errors trying to use WoV such as:
1. WoV (or one of several dependencies) not installed correctly. there could be several reasons for this, one fairly common is that installation folder has long name, other is that user does not have needed rights etc.
2. another common issue is DTM is not updated or correct
3. also common issue is that WoV is not configured correctly before use (plugins not installed or wrong versions)
4. also worth mention are incomplete or incorrect WoV project (users try creating new project from scratch and failing to merge for example etc.)
5. finally, one of the most common error is that users simply ... do not read... they don't read instructions, manuals, dialogs, messages... then it is no wonder that when they need help, they provide wrong info too. -
Also did you consider trying newer version of WoV?
I've been using WoV4.0.24 for ages. current one from http://www.kuka.com is WoV 4.0.27. -
Thanks panic mode, massula,
You guys are the best at solving stuff.
Okay I might request the kuka support for a different version of wvs.
[size=2]Problem 1.:
Screnshot shows that problem occurs when trying to save file to USB but drive letter is different...How exactly you are trying to generate KRCDIAG? Are you using network path for eample?[/size]
And I'm trying it this way,
Plugging it USB stick into the SmartPAD, then logging in as expert mode.
HMI File --> Archive --> USB Cabinet --> KRCDiag
Please correct me if I'm wrong.
Cheers
About the DTM part:I've heard some people complaining about the same problem, when running WoV 4.x in Windows 10.
I've worked with WoV 3.0.10 under Win10 with no problems, but my applicatinos where simple, without any options.
Did You tried run WoV inside a Windows 7 virtual machine?
I'm currently setting up the software tools required to try that VMware, wvs , etcWill test it and keep you guys updated about the progress.
i have seen a lot of people complaining about WoV not working correctly. Turns out there is plenty of user errors trying to use WoV such as:
1. WoV (or one of several dependencies) not installed correctly. there could be several reasons for this, one fairly common is that installation folder has long name, other is that user does not have needed rights etc.
2. another common issue is DTM is not updated or correct
3. also common issue is that WoV is not configured correctly before use (plugins not installed or wrong versions)
4. also worth mention are incomplete or incorrect WoV project (users try creating new project from scratch and failing to merge for example etc.)
5. finally, one of the most common error is that users simply ... do not read... they don't read instructions, manuals, dialogs, messages... then it is no wonder that when they need help, they provide wrong info too.
Also did you consider trying newer version of WoV?
I've been using WoV4.0.24 for ages. current one from http://www.kuka.com is WoV 4.0.27.Thanks panic mode will double check the points you have mentioned and see if it solves the problem,
We just installed the wvs that came in with the Robot. I have requested for support from Kuka Australia and see if they could offer any help.Will keep you guys updated of any progress.
Thanks
-
And I'm trying it this way,
Plugging it USB stick into the SmartPAD, then logging in as expert mode.
HMI File --> Archive --> USB Cabinet --> KRCDiag
Please correct me if I'm wrong.
Cheers
There is another way to make the KRCDiag.
I don't remember the menus path exaclty, but I think is in Diganosis > KRCDiag.
This way, when You start KRCDiag, it will be saved inside the robot HDD, at C:\KUKA\KRCDiag, not in the USB Stick.
Try this, please.
-
that is what system integrator manual is for - that is a KEY DOCUMENT for any integrator. (check topic READ FIRST...)
-
Okay, Guys sorted the issue out.
The error in DTM Profinet is because there was a clash in the assigned Anybus X Gateway and Auto-scan listed gateway so its resolved as below.
Add the module into the profinet field bus and then open dtm catalog and remove the unnecessary Anybus gateway devices from the list.
Only keep "Anybus X-Gateway RT Standard" and then connect the profinet and then click on profinet-functions-Device names and Profinet list.
Now if you see duplicated anybus modules then simply clear the whole row. And now just select the one defined with your IP address and click assign name button below. And after giving in the name, just hit send signal. Thats it, the module is now configured and you should see the gateway device with green leds over MS and CS.Hope this helps.
Cheers
-
And I'm trying it this way,Plugging it USB stick into the SmartPAD, then logging in as expert mode.
HMI File --> Archive --> USB Cabinet --> KRCDiag
Please correct me if I'm wrong.
....If You select "HMI File --> Archive --> USB Cabinet !!!!!!! --> KRCDiag"
You should plug the stick into the CABINET, not into the SmartPAD.