Should i leave automatic recognition in the bios or to detect them and to use the exact model?
Sent from my GT-N7100 using Tapatalk
Posts by vvelikov
-
-
They are recognized in ths bios correctly
The robot is with KRC2 cabinet made in 2003.Sent from my GT-N7100 using Tapatalk
-
Hi guys,
i am trying to make a copy of the KRC2 cabinet HDD - the system disk - C: in case something happen with the original HDD.
I did it with Norton Ghost - copying both C: and D: (logical drives) to the new HDD.
When i tried to start the robot with the new HDD it wasn't starting - staying at "Verifying DMI pool data.........."
I tried with two HDD's - 80GB and 40GB ones. The original one is 20GB - is this a problem?As i am not sure where i am mistaken, can someone advise how to do it properly, what software to use for cloning, which options to check etc?
Cheers,
V -
To translate the programmed path from a CAM system to the robot you will need:
1. CAM software to import the detail and to make the cutting/milling paths
2. Postprocessor for your CAM - to export the code
3. Visualisation software to check out the code, singularities, collisions etcYou can check Sprutcam - it is all in one
There is also Robotmaster (needs Mastercam), Powermill robot interface (needs Powermill), Eureka (independent), IRBcam etc but they are much more expensive... -
Hey guys,
received today this error while milling and the brakes switched on because of too fast rotating of the axis A5
So the error is: ACKN. WATCHDOG POWER MODULE 1After the reboot there was more errors saying that all the servos are not connected right... the servo drives are glowing green and red.
After another reboot it is all fine and working.
What would that mean and should i be worried about this? It looks like kind of power module overloading, but still not sure what can i do to prevent it...
Any help appreciated!
-
hehe, now is the time some top notch milling stuff
-
-
-
Yes, love the software
-
does SprutCAM manage joint limits, configurations, singularities, workspace and collisions? if not you are severely limiting your options with programming. That is the drawback of just using a simple post-processor for a CAM system.
Yes, all of this is covered -
That's really good topic, i would like to join - the last video is what the robot can use i think.
Anyone with idea how is the extruder working?
The other part is the software, but i suppose that it is possible to be used any 3d printing software with custom made postprocessor? -
I can send you some code as well... can you try to make a square cut not by jogging, but with a simple code with coordinates on X, Y?
-
Hi
i can see that you are going in circles
ok, i will explain about the toolpath: the toolpath defines the movement of the physical end of your tool and it doesn't matter how long you will make it in Sprutcam - the code is still about the movement of end of your tool bit. As long you are doing proper tool calibration on the robot it will follow the same path with different (in the CAM) tool lengths.
This is not an issue in any way, that is normal. And you don't need to have super ultra precise robot model - the software is not writing the rotations/angles of the axes etc - it using the kinematics just to check the collisions, reachability and singularities. The end result is the toolpath which will be fine as long you have well calibrated tool, base and mastered robot
About the tool definition: the X is pointing to the tool orientation vector - in your case down. And your Z should point forward - just as it is in the picture you provided from the Kuka documentation. I think you mixed them up... You can easily check you directions on the robot by moving it XYZABC
The problem is if you have rectangle instead of square
for me that means that your robot needs remastering.
It is not difficult and you can do it by yourself even with smaller precision, but is a must if you want to do milling.
Do you have instructions how to master your axes? Send me a PM if you need info about that. -
don't forget the concrete floor - you will need a proper base for the robot - at least 150mm, depends of the size of the floor - as you won't want any vibration when milling...
-
Why dont you try a circle without external software - just krl core with two arcs?
Or even few arcs with known radius? -
If you decide to go for a Christmass beer in London, i am available
-
It is not that simple - you can't execute G-code directly in a robot.
You will need to "translate" the G-code via postprocessor in your CAM software to get the right language and commands for the particular robot.
It is all depend of what are you using for CAM programming and are you ready to learn new software if needed.
You will also need to have proper simulation and collision/singularities checking and code editing software - to check the created code before you start it on the robot.
So basically it is structured like that:CAM software -> Postprocessor -> Simulation&Verification -> Execution on the robot
-
Th axis optimizer is giving you the possibility to avoid collisions ans singularities - it is VERY useful
just don't forget to recalculate the toolpath after making your optimisation. -
And an example how i did the side cut
-
Do you have the axis optimizer in your version???
Advertising from our partners
