Sprutcam 11.5 Crack
Mariam Obregon
We're trying to get started with a KR60-L30-3-KS with KRC2 and KSS 5.4.14 as a CNC milling machine with an external 7th axis kinematic system. Our spindle is not currently setup to be run through KRC2; we switch it on and off independently. I'm currently trying to evaluate SprutCAM as a possible solution, but am running into problems with the post processing. The code that sprutcam produces throws many compilation errors and will obviously require quite a lot of post-processor work.
I need to know whether I should abandon sprutcam for mastercam/robodk or try another cam/processor package altogether. To do this I need to know if anyone out there is willing to lay out some successful routes to getting error free code out of sprutcam for our Kuka setup? The guy at sprutcamamerica doesn't seem to be very useful in this regard. At this point, I'll settle for the easiest possible anything at all. I just need to know if sprutcam is capable of producing anything useful out of the box.
I've been trying to get the people at sprutcam to produce a good robot model for us using the datasheet for our model as well as our rotary table. But it's clear I need to be able to get data from the robot about the TCP as well as the xyzabc location of the table. I haven't yet seen how to do this. Is anyone willing to share their experiences with this? What else am I missing?
At this point, I've produced a little square path program using a calibrated tool and base in the KCP. I then produced a similar 2D Contour path in sprutcam using roughly the same dimensions as the square path I made in the KCP. The problem is that I don't know how to get sprutcam to use our robot's calibrated tool and base inside the robot model. My goal here was to simply compare src and dat files to see what the differences were. It turns out the sprutcam files won't compile as you can see in the pic.
I can't tell at this point if my problem is that I need to learn how to write a post processor or if there are far superior packages than this out there that I won't have spend so much time effectively earning a phd in robotics to use.
I can post the code if anyone cares to see it. The code I created in the KCP is short, but the one from sprutcam is significantly longer. I really don't know what to do at this point. I'm ready to abandon sprutcam, but don't have a great place to turn to after that.
If you only intend to respond with RTFM, please don't. I have read the manuals. I'm looking for specific parts of the manuals that I've missed. If you know what those parts are, please specify manual and page number. If you know of a useful tutorial, please show it to me. If there's a post somewhere that I've missed, please direct me to it.
Obviously all the new parts are unknown and unused in you older version. If its is simple in SPRUTCAM to leave this bits out while generating KRL code or choosing generate for KRC2 vs KRC4 you are probably done.
[size=1em]1. google SPRUTCAM[/size]
[size=1em]2. click on first result ( )[/size]
[size=1em]3. click on SUPPORT/TUTORIALS[/size]
[size=1em]4. click on ROBOT PROGRAMMING tutorial[/size]
[size=1em]5. click on FIRST link ("working with SprutCAM")[/size]
[size=1em]6. second slide is tool calibration or entering tool data...[/size]
[size=1em]next i looked at your screenshot.... what a waste.[/size]
[size=1em]hint: we are trying to not waste space here, many good topics have been deleted to make room for some un-necessarily large attachments that may only benefit one member instead of community. [/size]
[size=1em]content of the screenshot confirms that you are using KRC2 but compilation errors show that declared structures are using KRC4 format. should be simple to just use search and replace and get rid of not supported elements like jerk. in the long term (to avoid constant search and replace) one could play with settings (edit postprocessor)[/size]
[size=1em]about the program size... cant tell without seeing the program. in general programs created manually will be orders of magnitude shorter than anything made with some CAD-to-path conversion process. this depends on granularity you have selected...[/size]
Hello jkinst,
I am using Sprutcam everyday and can confirm that it is easy to use and configure BUT you need to educate yourself a bit.
I will try to make it short as panicmode already had good point for a solution - in the Sprutcam website there is a really good section with tutorials how to configure your software.
Hope that helps, Sprutcam is one of the best packages available and is really easy to use - but you need to put some efforts in the beginning
BTW i wrote earlier to different users here about how to configure Sprutcam - use the search in the forum to find this info.