I received some continuous paths modeled as solids and imported them in PS in the past, but never exported something like this.
I'm not sure if is possible, but You can try to select the path/curves, go to File menu, Import / Export and Export to JT.
If it works, You will probably need to convert the .jt formato to another one, depending on the application You want to open it.
I didn't touched KUKA.Sim in a while, and I know newer versions can create WorkVisual projects, but I don't know if they also can read WoV projects
Anyway, in the worst case, You can open Your project in WoV, export all programs and relevant config files, like $config.dat, and import them in KUKA.Sim.
One time a colleague put my name on the UALM of a FANUC robot, we make a test program, and of course we forget to delete it after.
Some YEARS after, a maintenance guy from this customer sent me a message like: did You ever heard about FANUC viruses? And me: what?
So he sent me a photo from my name being displayed on teach pendant. 
You can play Tetris on a KRC4 if You are really committed to do so.
(First time the pick wasn't uploaded properly. Now there is)
Yes.
Based on your report, this is probably a problem related with virtual robots.
I had a problem like this in the past, with an older PS version and with non VW robots.
For me, the solution was:
1- Make a backup of Your cell (a PSZX or so)
2 - Close PS
3 - Through Windows, delete the RobotMachineDataFile specific folder from the problematic robot
4 - Open PS and change the controller type from FANUC to Default
5 - Save the project/PSZ and close PS again
6 - Open PS and attach the virtual controller to the robot again
7 - Sometimes You will need bring back some files from the old RobotMachineDataFile folder, so pay attention to the step 1
If I understood correct, the OP wants to use KRC as a KMC. Robot controller will command another kinematics that isn't the original KR.
And now I saw that KMC was mentioned a lot of times before. Sorry, hehe.
This RCS version is specific for VW group. Are You sure it will work with PS 16.0 instead PS 16.0.1 or even PS 16.1, for example?
Some years ago we had a problems with FANUC memory.
In our specific scenario, we really have more (huge) programs than robot memory could carry, so in our case, the solution was order an option from FANUC called DRAM File Storage (R798), that enabled an additional memory section called Shadow Memory.
Depends.
The 3D component of Robosim is a ripped of version of Blender, and put anything besides the robot inside the virtual environment is possible, but no so intuitive as in other softwares in the same category. And I don't remember if its possible to make knematics, but I'm almost sure its not.
Anyway, COMAU has a newer simulation tool called Roboshop, that uses a different 3D engine, and maybe things got better with it
As far I can tell, there is no documentation describing this procedure in detail, but for ABB, you first need to load all user data in (tooldata, loaddata, Wodobj and so on) in robot setup or robot properties, and after this You can upload program modules.
Nunca trabalhei com essa placa, mas recentemente tive que fazer um trabalho de enviar strings via EthernetKRL, e uma coisa que jogou a gente no buraco foi o fato do nosso programa estar enviando os caracteres de final de linha duas vezes. Só conseguimos ver isso após habilitar um outro modo de visualização de mensagens no Hércules.
Not a full wiring diagram, but maybe it can help You.
Display MoreAll are windows ce because filesystem is FAT16 on system
EOL in all text files is CRLF (this means windows not linux-unix).
Drive names are with letters (not mount paths) and file path with inverse slash (\).
Also controller has full tcp/ip stack and functions that only full operating systems offer
like windows-linux-unix (NOT dos).
Windows CE has realtime versions (with realtime kernel).
All evidence seems that all are windows embedded arm architecture (pendant and controller) .
Advertisement say not PC based (means not x86/x64 based) doesn't say not windows based.
I will investigate more but am almost sure that OS is windows embedded (realtime).
I think all these factors (EOL, inverse slashs) are because controller need to communicate with iPendant, that runs on Windows, and we know Windows isn't so happy to read information that not come formatted as its expect.
Even KUKA - the poster boys of PC Based industrial robots - doesn't use Windows as its realtime operation system. They use VxWin, that is a tailored version of VxWorks. I don think FANUC would go a different route.
I believe Windows runs on iPendant, not on controller CPU.
If You simply try to upload an VKRC2 program on a VKRC4, robot will refuse it.
And if You try to use Manual Upgrade function (and specific VKRC feature), VKRC4 will upload it, but will delete everything inside the programs.
TLDR: there is no easy way. But is possible.
If You simply try to upload an VKRC2 program on a VKRC4, robot will refuse it.
VKRC4 has more parameters than VKRC2, and VKRC robots have more hidden instructions than a regular KRC robot. But since VKRC modules are plain text files, You can try to do some sort of search and replace operation by hand.
Other option would be try some specific third party program, like Dramat, Tekrob or Steineke editors, that are designed to work with files from VW robots and can perform these changes in a way or another. Tekrob has an specific VRKC2 to VKRC4 import feature, and with some workarounds, Dramat and Steineke can understand this situation and convert files properly. But all these programs need paid licenses.
And, finally, If you have access to Process Simulate and the proper licenses, You could try to upload the VKRC2 program inside Process Simulate, change software version and download it in VKRC4 format.
I had a problem like this before, but it was triggered because I installed a newer version of MotoSim EG (the simpler simulator) in a machine with an older version of MotoSim EG-VRC (the complete simulator). Updating EG-VRC and reinstalling EG solved the problem at that time.
Anyway, MotoSim 2022SP1 manual has a mention on this type of problem on its troubleshooting section (14.1 Start of MosoSim EG-VRC), but the solution isn't really helpful. Basically, it says to uninstall older versions of MotoSim and try again, and I believe You did it already a couple of times. But I would investigate some sort of remaining system file or registry entry after the uninstall process.
Normalmente os códigos de erro da Kawasaki são maiores, compostos por uma letra e quatro dígitos. D1018, por exemplo. Qual o código que aparece no robô que está dando erro?
And, of course, You must populate Your xml with the keywords that You want suggested.
Hi Massula,
What do you mean by "To have autocomplete, you must create an .xml file, and put it at C:\Program Files\Notepad++\plugins\APIs\ (on Windows XP)."?
Would that work the way you start typing and get sugestions like in ABB RobotStudio?
Hi, sby.
Yep, exactly.
But, please note that I was referring to a N++ version from 2013, and since them, a lot of stuff changed in the program.
If I recall correctly, the autocomplete files now must be put inside a folder called autocomplete (not API anymore). But is good to check the documentation.
