Hi, Alireza.
What is exactly the software version or Your VKRC? 3.3.x? 5.4.x?
You can write a simple background logic using makrosps.
But if You need more advanced stuff, You will need to play with VW_User as well.
Hi, Alireza.
What is exactly the software version or Your VKRC? 3.3.x? 5.4.x?
You can write a simple background logic using makrosps.
But if You need more advanced stuff, You will need to play with VW_User as well.
The level of quarantine is varying from state to stare here in Brazil, and where I live there isn't any lockdown (yet), but there is a scene happening with a certain frequency that get me a little bit scared: fireman and policeman vehicles with megaphones, saying to people stay at home. I'm feeling inside some kind of dystopian movie.
Kids are out of school since last Monday, and I'm working from home since Thursday.
Automakers are shutdown their factories, and lots of manufacturing shops are closing down as well.
The predicted peak for the outbreak here is mid April, so it is important that people stay home now.
Hope this go away as fast as possible.
Hi, sirmant15.
I don't think so. If.the WinC4G library and robot software version are matching, the problem must be another thing.
Probably syntax errors.
Try to open these programs with WinC4G, make small edits, and save them again.
It there are some syntax errors, WinC4G will war You about them.
Some time ago I sent some of these reports to customerservice@kuka.com and they answered very fast.
But the bug is still there, at least on WoV 6.0.6. Need to check 6.0.7.
Update: since I coudn't handle my own curiosity in this regard, I did the downgrade from VMware Player 15.5 to 14.0 now and this solved the problem. OL up and running. I will try 15.0 later.
Which version of VMWare are you using? I have discovered the hard way that my OLs didn't work on versions 16 and up, so I am sticking to the latest 15.
Interesting comment, dexterv
i've noticed some problems here after upgrading VMware Player to 15.5.
In the next days I'm planning downgrade to 14.0 and see what happens.
This controller is GM Global 4? Or VW VASS?
If Yes, You need to ask GM/VW for this particular FRVRC.
But You need a corporate email.
Email addresses from free services as Google or Yahoo aren't permitted anymore.
And even generic corporate emails, like robotics@mycompany.com are being blocked.
So You will need something as name.surname@mycompany.com
markopo , by the device name shown on video (kaclav110010r01sk-1k), I suppose it is a VKRC robot.
This is a regular Bosch controller, or a Kombi steurung?
Volkswagen has a very detailed document explaining how to configure ProfiNet bus according to their standards.
So, If You followed those steps, I would recommend to take a look tha the GSDML version, and also in the I/O mapping.
I remember some colleagues having problems because they mapped the signals as bits, and not as bytes.
Video isn't playing here.
Gazebo can work in parallel with ROS (Robot Operating System) stack, and I think You should use it to achieve Your objectives.
There are lots of good ROS resources around, but I think You can start with these two.
ROS courses page
And You can also take a look at this company page
https://www.theconstructsim.com/
They used to have some nice (and free) ROS tutorials
I don't know what it's real purpose, but is PARAM EDITMASK is used on VKRC robots, and I suppose it is a way to inform VSS what a user can or can't do on that specific program.
VKRC has a strict program naming convention.
So regular users can only create/manipulate programs named Folge(n), UPs or Makros, where the first is like a main program, the middle is a subprogram, and the later is somewhat a function (doesn't return values, but You can't put movement instructions inside).
These names can be only appended by a number suffix, like Folge1, UP99 and Makro0. On a VKRC, if You put a module named, lets say, Prog01, compiler will complain and give You a red cross.
There are some special makros, like MakroTrigger, MakroSPS and MakroSAW.
VKRC robots also have VW_User, a meta thecnology package containing VW (not so) secret sauce. You can be more creative naming programs inside VW_USer area, but integrators shouldn't touch these programs, unless under very special circumstances.
So, a header from a VKRC4 folge is like this
&ACCESS RVO1
&REL 39
&COMMENT VWxxx
&PARAM DISKPATH = KRC:\R1\Folgen
&PARAM TEMPLATE = C:\KRC\Roboter\Template\vorgabe
&PARAM TPVW_VERSION = 8.1.8
&PARAM EDITMASK = Folge999[1-999]
A header from a UP
&ACCESS RVO1
&REL 46
&COMMENT VWxxx
&PARAM DISKPATH = KRC:\R1\UPs
&PARAM TEMPLATE = C:\KRC\Roboter\Template\upvorgabe
&PARAM TPVW_VERSION = 8.1.8
&PARAM EDITMASK = Up999[1-999]
The header fom a regular Makro (Makro50)
&ACCESS RVP2
&REL 1
&COMMENT INICIALIZACAO MARCAS
&PARAM TEMPLATE = C:\KRC\Roboter\Template\makrovorgabe.src
&PARAM TPVW_VERSION = 8.1.8
&PARAM EDITMASK = Makro999[0-999]
The header from MakroSPS, a special cyclic makro (acts like a .sub)
&ACCESS RVO1
&REL 18
&COMMENT MAKRO_SPS_LASER
&PARAM TEMPLATE = C:\KRC\Roboter\Template\makrospsvorgabe.src
&PARAM TPVW_VERSION = 8.1.8
&PARAM EDITMASK = MakroSPS
And, finally, the header fom a VW_USER file (vw_usr_r.src)
Thanks for the tips, kwakisaki!
I will try to talk with KHI people.
But if someone who read this thread has this material and can share it, please drop me a line.
Is it just for this reason ? Because I installed it on W7 before and it worked. It also has a simple setup, what could I have done wrong, do you have any ideas about that ?
Do You really need WoV 5.0.4? If isn't a a client demmand, You can try 5.0.10, that can be downloaded from KUKA site.
Hey, kwakisaki .
I would like to know, for example, if Ford Kawasaki differ from standard Kawasaki in any significative ammount, like Toyota ones. Does it have custom menus, instructions and so on? Or the standard is only a convention for program and signal naming?
Hi, people.
I know a huge spreadsheet with lots of tabs containing signal tables and all sorts of information, but I'm wondering if other supplementary material does exist.
I would appreciate If someone have docs/backups/ or anything else related to Kawasaki Ford standard that could be shared with me.
Let's say I'm investigating a situation, so I cannot ask Ford directly for this material, yet.
Thanks!
Yes!
I used RoboShop once and it really has this improvements.
I will give it a try again.
Thanks, Vladarius.
Features I would like to sea on future versions of COMAU WinCRC.
WinCRC is the newest generation of Windows interface programs. Previously we had WinC5G/WinR1C, WinC4G and Win PCint (for C3G+ controllers), if I recall correclty.
Althought WinCRC is a very handy tool, I would like to see some minor changes/improvements on it.
- Syntax Highlighting: nothing fancy, but I would like to see at least the comments, and most inportant, commented instructions, on a diferrente color.
- Less instances, more tabs: Every time I click on a WinCRC associated file from Windows Explorer, it opens on a differente instance of WinCRC, and, depending of the workflow, these instances tend to swarm the desktop. I see many cases where is better open differente files on different instances, but I also see some situations where is better maintain all files opened on the same instance. So would be great to see a setup option, or a context menu option, for example, that permit user to decide what is the best way to work.
- Remembering paths: WinCRC has a built-in file explorer, but every time we need to open it, we need to browse our way to desired files again and again. Would be very helpful if the file explorer remember the last session.