Posts by javaman

rdc must changed to identify as kr150 or not ?

Can a KR150L130 modified to be a KR150?

Is the extension of extra 200mm removable?

So the robot to have less envelop but more payload?

if you find answer please post it here

a nice article about preempt-rt

https://opensourceforu.com/2018/05/a-quan…ith-preempt_rt/

https://blog.icterra.com/real-time-linux-comparison/

wind river that makes vxworks have own a commercial version of preempt-rt

I have a similar question...

I want to integrate to a KRC2 robot a saf nertajet hp125 plasma.

What extra i/o options & software i need for krc2 ?

Also what cad-cam is suitable for plasma cutting & supports krl post processors ?

Hello.

Can someone with krc2 report the ram chips that use the memory modules of kpc2 ?

Not the code of whole ram module only the code of the 8 memory chips that has the module.

Iam interrested for 256mb & 512mb modules chip codes.

Thanks.

The bios has been modified in a manner that has functions disabled because specific

interrupts to cpu kill real time performance.

For example the custom bios has sound/usb/power managment functions disabled.

The custom bios does not have altered functionality only certain function & peripherals disabled.

"custom" has to do with configuration only.

In preempt-rt linux kernel with power managment/cpu throttling functions enabled in bios real time performance drops significantly so the best jitter is with these function/peripherals disabled.

Also when you isolate real time functions to specific cpu core (with configuration of kernel)

and all other general pc functions to other cores jitter is very low.

I have upgraded cpu and ram but how i know that this ram i have used works?

(The pc now with the ssd/p3 cpu/more ram is definitely more fast)

What are the symptoms of non working ram in robot ?

Also what is this info in KC - Tool Driver ?

I have a system with atom J4150 with linux preempt-rt kernel that has uptime more than 6 months without reboot without shutdown.

linux is far more reliable and stable and needs less resources than windows for this reason is the first choice in servers, supercomputers and embedded systems. For embedded systems there is special preempt-rt kernel that makes a typical general pc real time.

When kuka started producing robots before 20+ years ago preempt-rt does not exist but today many things have changed..

Iam sure if they started to develop a robot controller today first choice will be linux with preempt-rt kernel.

I have searched in kuka xpert web site for article no 69-225-463 but i can not find it.

Last is to contact kuka with mail..

OK i got it that makes sense.

But the cheap and easy way is linux preempt-rt kernel & linux.

With this kernel a motherboard that costs 100eur for example intel atom with some configuration can give servo thread jitter < 50uS .

So for only 200eur you can get a full generic pc that is real time with servo thread < 50uS.

I have found already the siemens product catalog 1FK6 i know the naming code of siemens (in the naming code are not all documented)

But I have not found specific datasheets for kuka motors neither in siemens or kuka web sites.

Application is to use kuka-siemens servomotors with generic servo drive and to setup this drive need all the characteristics of motor.
Maybe this data can obtained from some kuka robots configuration files (MADA files)?

Ok for the pinout but if i want all technical data of motor

for example number of poles/frequency/inertia/back emf

where can i find kuka servomotors datasheets?

Siemens manuals/datasheets have similar models but no models especially

produced for kuka robots.

For example if i search in google siemens 1FK6100-8AF91-1ZZ9-Z S09

i did not find something.

Hello.

Where can i found kuka 1FK6100 3.77kw servomotor resolver 12pin pinout ?

12ms servo thread i think is to big..

And the problem for this is that windows kernel jitter is big because is not a real time kernel.

For example other cnc controllers(linux preempt-rt kernel/embedded arm with some RTOS) have < 1ms servo thread.

The design of real time controller based on windows OS is a fail because windows is not real time.

i will update cpu & ram.If iam lucky this will work.

i have already updated hdd with an ssd and now boot time is 5''

PIII-1.4S has the same stages pipeline as celeron is more fast in clock and has more cache.

I don't see any reason to fail. Jitter can not increased by this change only can reduced so real time performance will be better.

I agree that if you put other mobo or enable features in bios like usb/sound or add another gpu jitter can increased dramatically and have serious impact in real time performance.

Kuka in SY-7VBA133U has upopulated the audio function chips and i think the reason is the real time performance.

The only case i see that PIII-1.4S will not work is if kuka software has checks inside that stop function if detect another cpu than celeron733mhz

I have the keyfiles in usb flash but the user group is programmer now not administrator.

programmer user group has full rights ?

Also i have plan to upgrade ram to 3x512mb and cpu to PIII 1.4-S tualatin for better performance.

I made this jumpers to my vkrc2 and activated T1

What about Windows Fundamentals For legacy Pcs instead of windows xp embedded ?

https://en.wikipedia.org/wiki/Windows_F…_for_Legacy_PCs

This is more lightweight version of windows xp embedded.