# FixedPositionDefinedWaypoint

**URL:** https://forum.universal-robots.com/t/fixedpositiondefinedwaypoint/7946
**Category:** Java
**Created:** [June 30, 2020, 1:23pm UTC](https://forum.universal-robots.com/t/fixedpositiondefinedwaypoint/7946 "2020-06-30T13:23:48Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![anon2596383](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@anon2596383](https://forum.universal-robots.com/u/anon2596383)
#### Post date: [June 30, 2020, 1:23pm UTC](https://forum.universal-robots.com/t/fixedpositiondefinedwaypoint/7946/1 "2020-06-30T13:23:48Z")

</div>

Hello!

I am trying to create a waypoint using a predefined pose and joint positions.  
The code works in the simulation.  
UR software 3.13.0

I found out that the TCP is the difference between simulation and the “real” robot. The simulation has none TCP offset while the robot has a TCP offset of.  
X: -0.45mm  
Y: 3.33mm  
Z: 442.78mm  
RX: 1.8598  
RY: -1.8526  
RZ:0.6056  
payload 2.50kg  
Center of gravity  
CX: 0  
CY: -100  
CZ: 100

My question is why does this not work on the robot?

Checklist:  
I use the correct solution to the pose obtained from a getUserDefinedRobotPosition(new RobotPositionCallback())  
The waypoint appears in the tree with the correct pose but not the desired joint position.  
I have tried to use the new way introduced in the urcap API 1.10.0, called  
createfixedPositionConfig(PositionParameters positionParameters, BlendParameters blendParameters, WaypointMotionParameters waypointMotionParameters); but I can’t make an instance of PositionParameters without a RobotPositionCallback2 that would be okay if I then could save it in the DataModel but the does not have a set method I can use.  
I have now tried with the positionParameters but get the same error.

 ![billede](https://us1.discourse-cdn.com/flex020/uploads/universal_robots/original/2X/d/daf27826f4c6bbbcb908fed51a4535a63ee7ca39.png)  
outside the picture, the homeWaypointNode is added to a move tree.  
I would really appreciate some help on this matter.

---

<div class="post-metadata">

### Author: ![anon73888028](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@anon73888028](https://forum.universal-robots.com/u/anon73888028)
#### Post date: [December 6, 2021, 5:28pm UTC](https://forum.universal-robots.com/t/fixedpositiondefinedwaypoint/7946/2 "2021-12-06T17:28:55Z")

</div>

> [@anon2596383](#):
>
> Hello!
> 
> I am trying to create a waypoint using a predefined pose and joint positions.  
> The code works in the simulation.  
> UR software 3.13.0
> 
> I found out that the TCP is the difference between simulation and the “real” robot. The simulation has none TCP offset while the robot has a TCP offset of.  
> X: -0.45mm  
> Y: 3.33mm  
> Z: 442.78mm  
> RX: 1.8598  
> RY: -1.8526  
> RZ:0.6056  
> payload 2.50kg  
> Center of gravity  
> CX: 0  
> CY: -100  
> CZ: 100
> 
> My question is why does this not work on the robot?
> 
> Checklist:  
> I use the correct solution to the pose obtained from a getUserDefinedRobotPosition(new RobotPositionCallback())  
> The waypoint appears in the tree with the correct pose but not the desired joint position.  
> I have tried to use the new way introduced in the urcap API 1.10.0, called  
> createfixedPositionConfig(PositionParameters positionParameters, BlendParameters blendParameters, WaypointMotionParameters waypointMotionParameters); but I can’t make an instance of PositionParameters without a RobotPositionCallback2 that would be okay if I then could save it in the DataModel but the does not have a set method I can use.  
> I have now tried with the positionParameters but get the same error [readmore](https://www.pikacoustics.com/13-bass-trap).
> 
> ![billede](https://us1.discourse-cdn.com/flex020/uploads/universal_robots/original/2X/d/daf27826f4c6bbbcb908fed51a4535a63ee7ca39.png)  
> outside the picture, the homeWaypointNode is added to a move tree.  
> I would really appreciate some help on this matter.

Hi mate this is your compiler issue, you have no need to worry about it. Just simply restart your browser and try it again and boom your problem is solved.
