[Borgis1]

Thanks. This looks like just what the doctor ordered. I'll try that! Quick fix for now has been to use rconf 1,0,0,0,0,0,0... but it is only that, a quick fix

[Borgis1]

Now that everything seems to work fine and dandy, how do I get robodk to post rconf 1,0,0,0,0,0,0,0 instead rconf 0,0,0,0,0,0,0,0?

[Albert]

I understand you should change the configuration of your targets. You can right click on the program and select Recalculate Targets to update the configuration based on the simulation result.

[Borgis1]

Recalculating tells me "no problems found for this path" it also  doesn't post as rconf 1,0... only as earlier stated rconf 0,0...
Well on the theme of postprocessing, I also have ... well the postprocessor for motoman is posting speed wrong. This is from a random program:

Code:

MOVJ C00000 VJ=100.0
MOVL C00001 V=150.0
CALL JOB:M101
MOVC C00002 V=36.00
MOVC C00003 V=36.00
MOVC C00004 V=36.00
MOVC C00005 V=36.00
MOVC C00006 V=36.00
CALL JOB:M110
MOVC C00007 V=150.0
MOVC C00008 V=150.0
MOVL C00009 V=150.0
MOVL C00010 V=150.0
CALL JOB:M101
MOVC C00011 V=36.00
MOVC C00012 V=36.00
MOVC C00013 V=36.00
MOVC C00014 V=36.00
MOVC C00015 V=36.00
CALL JOB:M110
MOVL C00016 V=150.0
CALL JOB:M101
MOVC C00017 V=42.60
MOVC C00018 V=42.60
MOVC C00019 V=42.60
MOVL C00020 V=42.60
MOVC C00021 V=42.60
MOVC C00022 V=42.60
MOVC C00023 V=42.60
CALL JOB:M110
MOVL C00024 V=150.0

Motoman (at least none of mine) cannot handle the movement with two decimals. so I have to replace 36.00 to 36.0 and 42.60 to 42.6. I cannot seem to find an option for this in the menus. But it should at least be in the postprocessor