# TCP selection in Move Nodes **URL:** \ **Category:** Product Wishlist\ **Created:** [June 26, 2018, 12:56pm UTC](https://forum.universal-robots.com/t/tcp-selection-in-move-nodes/2185 "2018-06-26T12:56:05Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![anon83001199](https://avatars.discourse-cdn.com/v4/letter/a/e0b2c6/32.png) [@anon83001199](https://forum.universal-robots.com/u/anon83001199)\ **Post date:** [June 26, 2018, 12:56pm UTC](https://forum.universal-robots.com/t/tcp-selection-in-move-nodes/2185/1 "2018-06-26T12:56:05Z")
Hey! In our use case the robot has a welding torch mounted on the UR Tool Flange. Through an UR Cap some MoveNodes are added to the Robot Program without any User Interaction. But the TCP has to be selected afterwards manually in each MoveNode otherwise the flange TCP is used automatically and the robot moves to completely wrong positons. A possibility for choosing one of the TCPs in the Java Programming code of the UR Cap would be very good. Just the same like the Feature can be choosen (Base/Tool). Thank you 🙂 ---
**Author:** ![m.birkholz](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/m.birkholz/32/7084_2.png) [@m.birkholz](https://forum.universal-robots.com/u/m.birkholz)\ **Post date:** [June 27, 2018, 5:56am UTC](https://forum.universal-robots.com/t/tcp-selection-in-move-nodes/2185/2 "2018-06-27T05:56:07Z")
i posted a feature request about this problem some months ago and it seems UR solved this by selecting “use active TCP” as default action when creating URCaps Waypoint nodes. All you need to do is using the newest SDK 1.3.55 and PolyScope 3.6 + 🙂 ---
**Author:** ![anon83001199](https://avatars.discourse-cdn.com/v4/letter/a/e0b2c6/32.png) [@anon83001199](https://forum.universal-robots.com/u/anon83001199)\ **Post date:** [June 27, 2018, 7:40am UTC](https://forum.universal-robots.com/t/tcp-selection-in-move-nodes/2185/3 "2018-06-27T07:40:12Z")
Thank yo for your help! I will try that. 🙂