Hi panicmode ,first of all thanks alot,i have a robot kr 15-2 krc2 , kss4.1,windows 95, that it has 5 technology packages(P00,A10,A20,A50,..) now i have upgraded from win 95 to win xp,when i want to restore my programs from backup diskette in new os ,an error occured,for example it says wrong krc v4.1 to krc 5.1 ?is there any solution?
OS upgrade
-
aqapour -
August 14, 2022 at 4:23 PM -
Thread is Unresolved
-
-
as mentioned in READ FIRST, you should check key manuals for your KSS. you can get it from KUKA documentation portal called Xpert.
in this case check programming manuals for system integrators for KSS5.5 (KSS_55_SI_en.pdf)
tool and base setup is covered under startup and recommissioning > calibration
for example if you already have data, you can use numeric data entry:
Hi panicmode ,first of all thanks alot,i have a robot kr 15-2 krc2 , kss4.1,windows 95, that it has 5 technology packages(P00,A10,A20,A50,..) now i have upgraded from win 95 to win xp,when i want to restore my programs from backup diskette in new os ,an error occured,for example it says wrong krc v4.1 to krc 5.1 ?is there any solution?
-
please do not hijack unrelated posts. check topic READ FIRST and post details on your system and problem experienced.
software upgrade can be complex and... it certainly is when changing major KSS version and underlying OS. things like this need some checks and planning, including checking any dependencies like tech options, creating backups etc.
one simple solution is to not upgrade. things that used to work can continue to work if nothing is changed. in this case you may revert to previous installation.
another option is to make an upgrade, then manually import individual programs and settings. your posts suggest that you are trying to restore entire archive into new (and different) environment. that does not work. restore only works for environment that did not change (same KRC, same robot, same KSS, same tech options...).
so you need to manually transfer individually relevant programs and settings (tools, bases, fieldbus and network configuration....)
there may be further problems and compilation errors. those too will need to be dealt with one at a time.
-
please do not hijack unrelated posts. check topic READ FIRST and post details on your system and problem experienced.
software upgrade can be complex and... it certainly is when changing major KSS version and underlying OS. things like this need some checks and planning, including checking any dependencies like tech options, creating backups etc.
one simple solution is to not upgrade. things that used to work can continue to work if nothing is changed. in this case you may revert to previous installation.
another option is to make an upgrade, then manually import individual programs and settings. your posts suggest that you are trying to restore entire archive into new (and different) environment. that does not work. restore only works for environment that did not change (same KRC, same robot, same KSS, same tech options...).
so you need to manually transfer individually relevant programs and settings (tools, bases, fieldbus and network configuration....)
there may be further problems and compilation errors. those too will need to be dealt with one at a time.
I'm so sorry, I didn't mean to be bold, I searched a lot on the site and couldn't find the desired post... I have different questions, one is whether the technology packages from an old system like Windows 95 can be transferred and used to Windows XP or not... the second. Which files should be transferred from the archive to the new os and software?
-
now i have upgraded from win 95 to win xp,
...how, exactly? On KRCs, the Windows version and KSS version are tied together intimately. If you used a regular Microsoft desktop-type Windows installation, you've probably bricked the KRC entirely.
The only safe way to do an OS upgrade on a KRC is to determine the highest compatible OS from KUKA -- this includes both Windows and VxWorks/KSS -- and get the applicable installation media set from KUKA. Then install Windows, followed by KSS, in the correct sequence.
As for Tech Packages... P00 is not a TP, it comes with every KRC by default. TP compatibility is a complex question. Some old TPs work well in newer KSS versions, others definitely do not. Aside from asking KUKA for a compatibility list, the simplest approach is to try installing each TP from the D:/KUKA_OPT copy and see which ones work and which ones don't.
-
...how, exactly? On KRCs, the Windows version and KSS version are tied together intimately. If you used a regular Microsoft desktop-type Windows installation, you've probably bricked the KRC entirely.
The only safe way to do an OS upgrade on a KRC is to determine the highest compatible OS from KUKA -- this includes both Windows and VxWorks/KSS -- and get the applicable installation media set from KUKA. Then install Windows, followed by KSS, in the correct sequence.
As for Tech Packages... P00 is not a TP, it comes with every KRC by default. TP compatibility is a complex question. Some old TPs work well in newer KSS versions, others definitely do not. Aside from asking KUKA for a compatibility list, the simplest approach is to try installing each TP from the D:/KUKA_OPT copy and see which ones work and which ones don't.
I installed Windows XP, then I installed Kuka Cross version 5.1 and now I want to transfer my existing programs from Windows 95 to the new Windows xp, and for this purpose I want to use the archive, but I get an error, I don't know if the transfer steps are possible And if it is possible, how should I do this? By the way, the robot works perfectly after installing Windows XP, but I want my previous programs to be transferred to the new system and work there as well.
-
I installed Windows XP, then I installed Kuka Cross version 5.1
How? Unless you used the specific KUKA version of Windows, you've probably wrecked the KRC.
What steps did you take to ensure this Windows XP installer would work correctly with the KRC, and had all the correct drivers?
Is the robot working at all after doing this OS change?
now I want to transfer my existing programs from Windows 95 to the new Windows xp, and for this purpose I want to use the archive, but I get an error
What error(s), exactly? Details matter.
If the only errors are related to missing TPs, then you can try to re-install the TPs from the disk image you made of the hard drive before you tried installing a new version of Windows. You did make a proper backup image first, correct?
-
How? Unless you used the specific KUKA version of Windows, you've probably wrecked the KRC.
What steps did you take to ensure this Windows XP installer would work correctly with the KRC, and had all the correct drivers?
Is the robot working at all after doing this OS change?
What error(s), exactly? Details matter.
If the only errors are related to missing TPs, then you can try to re-install the TPs from the disk image you made of the hard drive before you tried installing a new version of Windows. You did make a proper backup image first, correct?
Hi Skyefire, look, I have my Windows 95 backup, now I want to transfer my programs to Windows XP, but after transferring the technology package to the folder TP, as well as my programs, a red X mark appears on all of them. How can I solve the problem? Did you solve it?
-
a lot is left out and you are not successful in conveying important details. so rather than going though million questions, lets forget about importing old programs for a moment - you installed new OS and KSS. is the robot operational now? if that is not the case, importing programs and settings is pointless. so can you use robot normally? that means jog, create new text program from a default template....
if your robot is operational. then you can think about importing programs from the old archive.
if not, you are just wasting time...
so suppose robot is operational and you transferred some of your programs... important thing here is to no overwrite any files, just add files that do not already exist on new KSS. failure to do that will corrupt the installation and you will need to start fresh. any files that exist in new KSS need to be retained. the only change would be to insert user declared variables from old $CONFIG.DAT to new one. that is it.
red X on program files indicates compilation error. usual causes are not declared variables or missing dependencies. this can be resolved but it is time consuming. for example of $CONFIG.DAT has red X, pretty much everything else will have it too since pretty much all programs (including submit interpreter) use $CONFIG.DAT.
as mentioned $COFIG.DAT is not the same among different KSS versions. this means you cannot just overwrite it. well you can but it is a bad idea. same goes for machine data, and other key files (BAS.SRC, P00.SRC etc.)
once the key files are error free, insert into $CONFIG.DAT user declared variables as well as tool load and base data.
then you can focus on user programs. i would usually recommend simply commenting out any line that fails to compile.
once you get each program to compile (no more red X) you got the skeletons... this allows you to see if all dependencies are there. then you can test them. if something is not right, look at what was commented out and fix or recreate that functionality.
-
a lot is left out and you are not successful in conveying important details. so rather than going though million questions, lets forget about importing old programs for a moment - you installed new OS and KSS. is the robot operational now? if that is not the case, importing programs and settings is pointless. so can you use robot normally? that means jog, create new text program from a default template....
if your robot is operational. then you can think about importing programs from the old archive.
if not, you are just wasting time...
so suppose robot is operational and you transferred some of your programs... important thing here is to no overwrite any files, just add files that do not already exist on new KSS. failure to do that will corrupt the installation and you will need to start fresh. any files that exist in new KSS need to be retained. the only change would be to insert user declared variables from old $CONFIG.DAT to new one. that is it.
red X on program files indicates compilation error. usual causes are not declared variables or missing dependencies. this can be resolved but it is time consuming. for example of $CONFIG.DAT has red X, pretty much everything else will have it too since pretty much all programs (including submit interpreter) use $CONFIG.DAT.
as mentioned $COFIG.DAT is not the same among different KSS versions. this means you cannot just overwrite it. well you can but it is a bad idea. same goes for machine data, and other key files (BAS.SRC, P00.SRC etc.)
once the key files are error free, insert into $CONFIG.DAT user declared variables as well as tool load and base data.
then you can focus on user programs. i would usually recommend simply commenting out any line that fails to compile.
once you get each program to compile (no more red X) you got the skeletons... this allows you to see if all dependencies are there. then you can test them. if something is not right, look at what was commented out and fix or recreate that functionality.
First of all, thank you for taking the time to answer my question... After installing Windows XP and KSS 5.2.12, my robot is fully operational and working. There are only two P00 files in the folder. I transferred A10, 20, 50, and H50 files from the previous Windows archive (Windows 95) from the TP folder (file package technology) and a series of other files to TP, and when in my program (for example, the car body), the relevant lines I comment on the mentioned files, the work done in Windows 95 works perfectly on the robot, but when I remove this technology package from the comment, I get about 20-30 errors.
-
again, your communication is lacking. tip - please read pinned topic READ FIRST. it tells how to post properly including how to take screenshots. your screenshots do not cover entire screen, you still did not list all messages etc.
your last image shows that some of the declarations are missing. in the past KUKA included bunch of libraries (Axx, Hxx). later on those were removed and replaced by paid tech packages (if i recall Axx became ArcTech while H50 became GripperTech etc). P00 remained the same.
if you are trying to make the old style libraries work on newer KSS, you will need to import missing global declarations. on older KSS, there was bunch of those in $CONFIG.DAT and new $CONFIG.DAT no longer has them. You would need to bring those in if you hope to continue using same libraries:
-
Hi Skyefire, look, I have my Windows 95 backup, now I want to transfer my programs to Windows XP, but after transferring the technology package to the folder TP, as well as my programs, a red X mark appears on all of them. How can I solve the problem? Did you solve it?
You still didn't answer any of the critical questions.
1. You cannot simply copy the contents of the TP directory from one robot to another. TPs must be installed using the actual KUKA installation program. These programs normally come on the CDs from KUKA, but when installed a copy of the installer is normally placed under the D:\KUKA_OPT directory inside the robot.
2. If you did not make a complete hard drive image before doing the Windows upgrade, then your only way to get the TPs back is to get the install CDs from KUKA. Because doing the Windows upgrade probably deleted the original D: partition.
3. You mention "red Xs", but you have said anything about the error messages. Each line of a program that fails compilation and linking will produce a detailed error message specifying which line failed, and why. You're going to need to try to load one file at a time, and examine the resulting errors in detail, to determine what still works and what is broken.
-
You still didn't answer any of the critical questions.
1. You cannot simply copy the contents of the TP directory from one robot to another. TPs must be installed using the actual KUKA installation program. These programs normally come on the CDs from KUKA, but when installed a copy of the installer is normally placed under the D:\KUKA_OPT directory inside the robot.
2. If you did not make a complete hard drive image before doing the Windows upgrade, then your only way to get the TPs back is to get the install CDs from KUKA. Because doing the Windows upgrade probably deleted the original D: partition.
3. You mention "red Xs", but you have said anything about the error messages. Each line of a program that fails compilation and linking will produce a detailed error message specifying which line failed, and why. You're going to need to try to load one file at a time, and examine the resulting errors in detail, to determine what still works and what is broken.
Thanks SkyeFire,all things done and working properly,first i edited the $Config.dat file in winxp side with declaration Tech packs then unfold $Config.dat in win95 side then select all contenets and copy them afte that paste it to the win xp $Config.dat then i replace bas.src from win 95 to win xp all x crossed files have been corrected now every things working well but i have a small error that says DSE writing I/O Errors but It does not cause a problem Thank you and thanks alot Panic mode
-
Hi Dear Friends
After I changed the operating system of the robot from Windows 95 to Windows XP, everything was fine until today. Today, I wanted to open a new module. I encountered the following error message.
"Name invalid for this type of constant
BAS (#PTP_PARAMS,100)
Can you advise what the problem could be and fix it?
-
With this little information nobody can help. Read and follow:
ThreadREAD FIRST...
how to post correctly:
1. be a good citizen and follow common sense. this includes no sharing or asking for copyrighted material. such posts will get you banned (because we don't want Kuka legal team stepping in and request ban on all manuals). an example of something that will get you in trouble is any material from Kuka College.
1.5 make SURE to post in the right forum section (manuals in manuals section, IIWA and Sunrise topics in IIWA section). see attached example for IIWA... sigh..
Please…panic modeJune 5, 2016 at 4:30 PM -
Please read the above posts carefully. I have already discussed the whole story with Panic Mod and Skyfire
-
I have read the whole thread, and even there you never told the complete whole story.
But now you have another problem. So try to post more informations about the actual problem. As you told, that before everything worked fine. Something must have been happened.
-
perhaps you should heed your own advice:
Please read the above posts carefully.
several people have already told you the same:
a lot is left out and you are not successful in conveying important details.
again, your communication is lacking. tip - please read pinned topic READ FIRST.
You still didn't answer any of the critical questions.
With this little information nobody can help. Read and follow:
ThreadREAD FIRST...
how to post correctly:
1. be a good citizen and follow common sense. this includes no sharing or asking for copyrighted material. such posts will get you banned (because we don't want Kuka legal team stepping in and request ban on all manuals). an example of something that will get you in trouble is any material from Kuka College.
1.5 make SURE to post in the right forum section (manuals in manuals section, IIWA and Sunrise topics in IIWA section). see attached example for IIWA... sigh..
Please…panic modeJune 5, 2016 at 4:30 PM -
Thank you, Herman, as I wrote in the above posts, I have a Kuka robot krc2 ed 2004 that used to work with Windows 95. I upgraded it to Windows XP and replaced my previous programs in each of the system, program, and TP folders. And all the problems were solved and the robot was working until today when I wanted to open a new module or a new program, after opening a red cross mark fell on this new program and I practically cannot run the new program.is this infos enough?
-
It has below error :
"Name invalid for this type of constant
BAS (#PTP_PARAMS,100)
Compilation error
-