# PositionParameters / Wrong Pose using WaypointNodeFactory with specific TCP Rotation
**URL:** https://forum.universal-robots.com/t/positionparameters-wrong-pose-using-waypointnodefactory-with-specific-tcp-rotation/6982
**Category:** Technical Questions
**Tags:** bugs
**Created:** [April 16, 2020, 12:56pm UTC](https://forum.universal-robots.com/t/positionparameters-wrong-pose-using-waypointnodefactory-with-specific-tcp-rotation/6982 "2020-04-16T12:56:49Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@m.birkholz](https://forum.universal-robots.com/u/m.birkholz)
#### Post date: [April 16, 2020, 12:56pm UTC](https://forum.universal-robots.com/t/positionparameters-wrong-pose-using-waypointnodefactory-with-specific-tcp-rotation/6982/1 "2020-04-16T12:56:49Z")
Hi,
in the newest API Version 1.10 i noticed a change in the RobotPositionCallback Interface which now uses PositionParameters to save Waypoints rather than jointpositions and pose which is now flagged as deprecated.
My Question is: how do i create Waypoints with PositionParameters manually?? (e.g. if i get Pose and JointPositions through rti socket )
Is there any Factory Interface i missed or is it missing?? ☹
---
### Author:  [@Ebbe](https://forum.universal-robots.com/u/Ebbe)
#### Post date: [April 16, 2020, 9:04pm UTC](https://forum.universal-robots.com/t/positionparameters-wrong-pose-using-waypointnodefactory-with-specific-tcp-rotation/6982/2 "2020-04-16T21:04:53Z")
Hi @m.birkholz,
I do not think it is there. Where exactly do you need an instance that is not the one passed to your callback , do you have any specific use case in mind?
---
### Author:  [@m.birkholz](https://forum.universal-robots.com/u/m.birkholz)
#### Post date: [April 17, 2020, 3:58am UTC](https://forum.universal-robots.com/t/positionparameters-wrong-pose-using-waypointnodefactory-with-specific-tcp-rotation/6982/3 "2020-04-17T03:58:53Z")
Hi @Ebbe,
thanks for your reply. Our Use case is to save waypoints with a Tool IO which gets the waypoint data (pose and jointpositions) from the robot real time interface. There are also other urcap vendor products that work this way.
Therefore, a PositionParameters Facotory Interface is necessary to continue generating Waypoints this way.
---
### Author:  [@Ebbe](https://forum.universal-robots.com/u/Ebbe)
#### Post date: [April 17, 2020, 6:38am UTC](https://forum.universal-robots.com/t/positionparameters-wrong-pose-using-waypointnodefactory-with-specific-tcp-rotation/6982/4 "2020-04-17T06:38:33Z")
Hi @m.birkholz,
Maybe I have missed something. But is your method for creating the Waypoint deprecated?
---
### Author:  [@m.birkholz](https://forum.universal-robots.com/u/m.birkholz)
#### Post date: [April 17, 2020, 6:56am UTC](https://forum.universal-robots.com/t/positionparameters-wrong-pose-using-waypointnodefactory-with-specific-tcp-rotation/6982/5 "2020-04-17T06:56:28Z")
Hi @Ebbe,
no it’s not ( `createFixedPositionConfig` is now overloaded) but i guess the new MotionParameters (and the RobotPositionCallback2) finally fix an issue we have with false inverse kinematics when using API generated waypoints?
---
### Author:  [@Ebbe](https://forum.universal-robots.com/u/Ebbe)
#### Post date: [April 17, 2020, 9:05pm UTC](https://forum.universal-robots.com/t/positionparameters-wrong-pose-using-waypointnodefactory-with-specific-tcp-rotation/6982/6 "2020-04-17T21:05:13Z")
I have been in touch with the R&D team. And there is no factory for now. I am not sure if the new method will fix the inverse kinematics issue.
---
### Author:  [@m.birkholz](https://forum.universal-robots.com/u/m.birkholz)
#### Post date: [April 28, 2020, 5:50am UTC](https://forum.universal-robots.com/t/positionparameters-wrong-pose-using-waypointnodefactory-with-specific-tcp-rotation/6982/7 "2020-04-28T05:50:34Z")
The Issue with the Kinematics is a wrong Pose Result after using the API Interface WaypointNodeFactory. This can be reproduced on the Ellipse Example as well as the integrated Palletizing Node with the Pick/Place Waypoint Assistent.
You can try the following to reproduce the bug:
1. Setup a home pose with axis postions(deg) 0,-90,-90,-56.56,90,0 - the robot tool flange now points down to the base plane.
2. move the robot to the home position and set the tcp orientation with the asisstant with this pose relative to the base plane - the output should sth like 1.88,-1.88,0.5676:
3. set a tcp offset of about 300 mm to z
4. select the ellipse urcap and program the center point to the home pose
5. the the waypoint node should now display the wrong Pose: