I don’t remember if I wrote that part of the translator and what my reasoning was for it to work like that. But sure it could probably be better. If and when we revisit Yaskawa I’ll have another look at the source with this in mind. For a hotfix you could try to modify “Yaskawa_JBI.py” source file on line 595 like this:
EDIT: Fixed the picture and its source code so that it’s valid python now
-k
@keke Thank you very much. That was helpful.
Hi killuoz! Could you share with me the way you connect RT ToolBox 3 with Visual Components, please?
I think MELSOFT Gemini can connect to RT Toolbox along with other Mitsubishi Electric products. Gemini is based on Visual Components.
Hello! Is the post processor version available for Techman/omron robots? if so, can you attach the .zip file as a reply? Thank you in advance!
Unfortunately we don’t have Techman post-processor and there are no new brands being worked on for this add-on at the moment.
-k
Hmm, perhaps a tiny bit awkward to post this here now but Techman/Omron has been added (TMScript).
We do not expect new brands to being worked afterwards, perhaps some bug fixes at most.
br,
Lefa
Hello,
I’ve instaled addon and no “Post Process” button shows up on the Program ribbon tab.
I tried instalation (unpacking into directory) as written in readme, also tried install it with addon store, but all with same result.
I have VC premium 4.9 with floating license.
Thanks in advance
Most likely this issue that is in 4.9:
I edited this thread’s OP to mention that for new version’s add-on folder should be “My Commands\Python 2”.
-k
Thank you, the post-processor button is in its place.
I don’t know if there is a hidden setting, but it looks like there is an error in the position variable processing for Mitsu robots.
Even though the VC configuration is Righty, Above, Noflip, the processor export it as 3, which in the RT toolbox translates to Left, Above, Non Flip.
That may be error in the translator. You could also try adding one PTP motion at the start as PTPs will set the configuration for linear motions following it. And path statements are usually translated as linear motions.
-k
I made these changes in translator starting from line 156
if rconf == 0:
lf1 = 7
elif rconf == 1:
lf1 = 6
elif rconf == 2:
lf1 = 5
elif rconf == 3:
lf1 = 4
elif rconf == 4:
lf1 = 3
elif rconf == 5:
lf1 = 2
elif rconf == 6:
lf1 = 1
elif rconf == 7:
lf1 = 0
it solved the problem for me
Hi!
We have doosan robot.
can anyone recommend a post processor for it? i.e. it convert solidworks model into robot language and creates path
thanks
Can a post-processor be developed for DOBOT robots? If possible, I have the robot model and the required DOBOT format files available here.
Hi,
We no longer develop this post-processor add-on. All post-processor development is made for VC OLP products. So if you are using OLP products and would have need to use OLP for this brand please contact your sales representative. He can then then forward your case and see what would it take to add Dobot translators to OLP.
-k
