That's a very good point trunkcnc. It is actually RDW2 v1.20.
Posts by KonstantinosP
-
-
If I didn't make it clear my apologies. The old PC is not ed05. We would have tested then the old MFC card if it works inside the new PC but it's not even a PCI card
Thank you. -
Thank you RS,
Yes, you are right to think of that scenario, we did too but putting the old PC back in the cabinet, the system works perfectly fine. Also, putting in the old PC the hard drive with the image of the one that came from KUKA, gets us passed the Start 10% mark. It doesn't in the end complete the startup of the HMI due to the obvious reasons but doesn't that rule out cabinet and software issues?
-
Actually, even after installing Windows and KSS from scratch, still it doesn't want to go passed the Start 10% mark. This is a brand new PC configured to my system and shipped directly from KUKA. I can hardly believe that something is damaged in it.
Could it be a conflict with something else inside the controller? I will certainly contact KUKA tomorrow but it is just puzzling this situation to me.
Thank you. -
Thank you Panic Mode and RS.
I checked on VXWorks network settings and Firewall, everything looks normal. Also the MFC card is fitted properly in the PCI slot.
I was thinking about do a complete installation (windows, security, KSS)on a different hard drive and see if that would help. -
Hello all,
We are trying to update our older KRC2 controller.(edited: not an ed05)
We just acquired a new ed05 PC from KUKA(KSS 5.6.12). The archives where sent for proper configuration for our system. KUKA prepared the hard drive and installed windows and KSS for us.
We swapped the old PC for the new one and when we started it, the booting process hangs up at the "Start 10%" mark. We tried a number of things. We cloned the hard drive that came with the PC for safety and on the cloned we did a clean installation of the KSS and started the controller. That didn't fix it. We also tried installing an earlier version KSS (v.5.4.14) which is the one that we ran the system previously on, that didn't work either. It just doesn't go past the start 10% mark.Any suggestions would be greatly appreciated.
Thank you.
-
No CAMRob KRC is not a CAM generator.
Apparently you didn't read the manuals that I attached.CAMRob comes in two flavors. CAMRob PC and CAMRob KRC.
CAMRob PC is built on top of KUKA.Applications PC and in conjunction with KUKA.Sim pro or tech can read in CAM files generated from your own CAM package, run a simulation, check for collisions singularities etc and generate src Files. It also generates a .job file and a .bin file that contains all the XYZABC values of all the targets in the program. This is the PC side of the package that if you have your own simulator you don't need it.
CAMRob KRC is the part that gets installed in your controller. This is the part I was talking about. One of the main functionalities that offers is that of drip-feeding chunks of targets in memory so you can ultimately run in one shot a program as big theoretically as you D:\ drive can handle.
I will let you read the manual and see why this is your best option but briefly I will give you a small example of my workflow to better understand the idea.
I create a 3D model in my CAD app
I generate toolpath in my CAM package.
I generate the .src file in my simulator. In specific I use KUKA PRC, a plugin for Rhino. It generates a single src file that contains all the LIN commands, sometimes hundreds of thousands or more.
I copy all the LIN commands and paste them in a .txt file.
Then I delete them from the src. Now my src file is not more than 20 lines.
I read the .txt file in Excel.
I format it in the following pattern:
Line nr;X;Y;Z;A;B;C (you can actually add user-specific parameters per line but it's optional)
Export it as a semicolon separated .csv file
Then I copy the src file in R1\Program and the .csv file in D: (note that in D: the only file-size restrictions you have is the available room in that partition.)
I add the CamRob in-line commands in the src file. You can actually use regular KRL commands for IO etc but you need to add at least the Proccess CAMRob command that basically starts the drip-feeding process.
If you formatted correctly the CSV file you are done. -
Signum,
If you are going through all this trouble just because you want to satisfy your intellectual curiosity as to how far you can push the Physical Pages limits, then you don't need to read further...
But if you really trying all these tricks in order to be able one day to run large size programs (for example a milling program with hundreds of thousands of points or multiple of those) I can tell you right now that you have entered a process so painful that in the end the experience of going through it it will measure the density of hair in your chest... I went through the same exact mental-trip trying to upgrade memory cards then wasted days and days trying to find the right amount of Physical Pages just to crash the system, cold starts, hot starts, and quite honestly, I never became able to run REALLY large size files. I ended up feeling that I made a huge mistake investing in an older KR210 KRC2 and that for my application it was quite useless.. My advice... don't do it...
There is a better way....
It's called CAMRob KRCYou will need:
KSS 5.4.14 or later. If you have a DSE card installed in your KRC2 you can upgrade from v 5.2.19, make sure you also have the right Windows version for it.
The Package consists of:
Art.# 91B300-012 KUKA.CAMRob KRC V2.2 which you can get from KUKA Belgium. This version is newer than the V2.3 that they sell in the US. Buy it from them. KUKA USA will tell you that older KRC 2 controllers cannot support it, I am the living proof that this is a pile of poop.. It works perfectly fine.
Art.# 91B300-010 KUKA.Applications KRC V1.2 You need this because CAMRob works on top of this. The awesome part of this particular version of Applications is that via Job Creator you can take a number of .src files and turn them into a Job and batch-run them, a functionality very similar to that of DirLoader but for a fraction of the money and the headache.(See page 16 in the attached manual)
You will also need KUKA.UserTech V2.4.1 Build 2
I am attaching the manuals so you can read all the info that I just mentioned for your self.
Bottom line. With an investment of 2,400 Euro you can run programs of hundreds of thousands of lines or hundreds of subprograms of that size in one shot, I do it every day of my life.
In short, if you are not familiar with CAMRob KRC, this is what happens: You generate an src file that is not more than 20-30 lines and all it does is calling all the CAMRob functions. You also put separately in a .CSV file all the points(XYZABC E1 etc values). This file can be massively big(million points or more). You do not need a .dat file. The .src file as usual goes in R1\Program. The .CSV file goes into D:\Applications In the .src file you can set up your spindle feed and speed, start, stop it, set up ATC all with CAMRob commands. You also call the PROCESS command (or multiple PROCESS commands)which what it does is it reads-in chunks of points from the .CSV file one buffer after the other. Then buffers that their points have been processed get flushed out of memory and get populated again with new chunks of points for later execution. That way CAMRob basically drip-feeds points into memory and this is a process that can go on for ever.
A few key points. There is a myth that you need also the 12K CAMRob PC package to make this work. That's incorrect. Although the PC part generates the entire Job folder automatically (includes among others the .src and the .bin file) plus it looks like it is an excellent simulator, you can completely enjoy all the functionalities of CAMRob KRC without the PC part (see attached manual page 49) It is a bit of extra work to create manually the .CSV file but Excel is your best friend on that... You will also need to be very careful with how you configure CAMRob KRC because it will simply not work, or work unpredictably.
I encourage you if you decide so, to buy it from KUKA Belgium. They are extremely knowledgible and on contrary to the fellas from KUKA USA, are extremely polite. To give you an idea, I worked with the man who runs the R&D department and in order to walk me through the program, he called me from his house on his cel, on his own time in the middle of the night there, because we couldn't establish a good internet connection during his office hours. And I wasn't even trying to buy a robot...
I hope you found this useful.
-
Panic mode thank you for your reply.
You are right. Both memory sticks are 128Mb. I tested one at a time and the HMI didn't even go passed booting.
The most upsetting part is that the sticks are clearly labeled from the manufacturer(not from KUKA) as 256MBMany thanks again.
-
Hello everybody,
I am new in the forum, new in the KUKA world as well. I recently acquired a KR210 2000 series. I use it for foam carving and light milling.
My controller is a 2004 (V)KRC2 with 434Mhz processor, runs on Windows XP SP1 with DSE card installed. KSS v.5.4.14.Not very technically savvy, if I am omitting any important info that would help clarify the case please let me know.
I am trying to expand the existing RAM from 3x64MB to 3x256MB. KUKA USA sold me two cards that they had available last week for my controller(part number 39000082), I installed them in place of two of the 64MB ones and after booting with cold start I expected to see under Help/info a total of 576MB of RAM.
However, it appeared as if I only had 320MB RAM. I tried a number of different combinations to rule-out a damaged RAM, both installed separately with an additional 64MB card work fine. It almost looks like the system can only handle up to 320MB. Interestingly enough, any other attempted combination that would result to a total over 320MB drops the memory reading to 256MB or 320MB. For example, 2x256MB + 1x64MB shows as 320MB RAM and 2x256MB + 0x64MB shows as 256MB.
Not the end of the world of course if my upper bound is 320MB but if anybody here thinks that could share some knowledge, I would be greatly appreciative.Thank you.