Kawasaki Post Processor not working?- Printable Version +- RoboDK Forum (//www.sinclairbody.com/forum) +-- Forum: RoboDK (EN) (//www.sinclairbody.com/forum/Forum-RoboDK-EN) + - - -论坛:RoboDK错误(//www.sinclairbody.com/forum/Forum-RoboDK-bugs) +--- Thread: Kawasaki Post Processor not working? (/Thread-Kawasaki-Post-Processor-not-working) |
Kawasaki Post Processor not working?-ftoso91-05-30-2016 Dear RoboDK staff, I generated a program with RoboDK for a Kawasaki robot, but when I loaded it on the real robot it didn't work. At the beginning I thought to a connection problelm, but then I noticed that the final code generated by the Kawasaki post processor didn't match the "typical" Kawasaki AS language (commands like "MOVE TRANS" are unexpected). Is this a bug? In this case, can it be fixed somehow? (The Kawasaki Post Processor doesn't seem to be editable by the user) Thank you Federico RE: Kawasaki Post Processor not working?-RoboDK-06-26-2016 Dear Federico, 我们没有正式吃晚饭port Kawasaki robots yet as we do not have the post processor for these robots. We will soon have the Kawasaki post processor for offline programming with our default installer. If you own a RoboDK license we can add the post processor for you. Alternatively, you can add the post processor yourself. The following tutorial might be of help: //www.sinclairbody.com/help.php#PostProcessor RE: Kawasaki Post Processor not working?-RoboDK-10-28-2017 The Kawasaki post processor was updated and is working 3 months ago. If you want to customize your post processor there is more information about RoboDK post processors here: //www.sinclairbody.com/doc/en/Post-Processors.html RE: Kawasaki Post Processor not working?-pokerkerl-03-03-2021 Hey Guys, while programming a RS007N and setting some LMOVEs from cartesian to axis-specific the LMOVE Trans (x, x, x, x, x, x) changes to LMOVE [x, x, x, x, x, x] but there is a '#' missing. In the final code it should be LMOVE #[x, x, x, x, x, x]. Is there a reason for that or am I missing something? RE: Kawasaki Post Processor not working?-Albert-03-18-2021 We just fixed this issue with the latest version of RoboDK published yesterday. I recommend you to update RoboDK to the latest version: //www.sinclairbody.com/download I noticed the issue you mentioned happened when using joint targets with linear movements. |