Hello, there is nothing wrong with your code. Currently there is a feature missing to get the command option PolyTrans working how it is supposed to do. When you switch on PolyTrans and it gets added to the following movement commands it searches in the preparation for the same entry in the following command. Since the first command gets prepared too fast for you to command the next command it never finds the next command to blend over. This will get solved in the future with a replaning feature. For now i can give you a workaround (in python): …
…
# signal_Id : free choice from 00 – 99
# auto_reset = True -> Signal gets reseted to false automatically
motion.kin_cmd_wait_for_signal(kin, signal_id = 99, auto_reset=True)
motion.kin_cmd_wait_prepare( kin,buffered=True)
motion.kin_cmd_opt_poly_trans_p( kin, eps=100.0)
…
…
#Kin-commands
motion.kin_cmd_move_lin_abs( kin, ( 227.2658 ,88.2926 ,Zdown))
…
…
# url to set the signal over the Data Layer perhaps possible via set_signal
uri = 'motion/state/functions/somo/signals/99'
datalayer.write(uri, True)
…
… This stops the preparation of the motion commands and thus can correctly plan the PolyTrans. The above logic also works with the PLC. The function blocks should be in the misc folder. Hint: In most cases, the "PolyTrans" function should be used in combination with the "ContMotion" command option so that a continuous velocity profile is generated without braking to a standstill at command transitions. Best regards
... View more