Why is Inline Target (*) creation restricted on OmniCore FlexPendant compared to IRC5?

General
1

Hi everyone,

I have a question regarding target creation behavior on the new OmniCore FlexPendant.

On the IRC5 controllers, we were able to create inline/nameless targets represented as * (e.g., MoveL *, v1000, z50, tool0;) directly from the FlexPendant. When adding a move instruction without explicitly specifying a target name, it would default to an inline target (*).

However, on OmniCore, it seems impossible to create an unnamed/inline target directly from the FlexPendant once named targets exist or when generating new movement instructions. The GUI enforces assigning/selecting a named target (robtarget) for every new movement command.

  1. Is there any specific architectural/programming rule reason why ABB changed this target program behavior on OmniCore?

  2. Is creating an inline target (*) completely blocked on the OmniCore FlexPendant UI, or is there a specific setting/workaround to re-enable it without using RobotStudio text editor?

Working on-site without RobotStudio makes quick teaching quite inconvenient when forced to manage named target data every time. Any insights or workarounds would be greatly appreciated!

Thanks!