# Odd inputs for Positioner SmartComponent

**URL:** <https://tech-community.robotics.abb.com/t/odd-inputs-for-positioner-smartcomponent/11055>\
**Category:** UpFeed\
**Created:** [March 8, 2023, 6:47pm UTC](https://tech-community.robotics.abb.com/t/odd-inputs-for-positioner-smartcomponent/11055 "2023-03-08T18:47:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![BartSchumer](https://avatars.discourse-cdn.com/v4/letter/b/e480ec/32.png) [@BartSchumer](https://tech-community.robotics.abb.com/u/BartSchumer)\
**Post date:** [March 8, 2023, 6:47pm UTC](https://tech-community.robotics.abb.com/t/odd-inputs-for-positioner-smartcomponent/11055/1 "2023-03-08T18:47:24Z")

</div>

Hello all,

First of all, I am new to RobotStudio. Thus, there may be a very logical answer to what I am about to say but I couldn’t find it anywhere.

The problem is with the _Positioner_ smart component within the _Station Logic_ of the _Simulation_ tab. I am trying to make a simulation where I can input an x and y coordinate which will move an object to a location (simulating a vision kit providing the x and y coordinates, after processing). So I set the numbers for the analog input signals (intended as mm), the controller interprets these numbers as mm so thats great! However, when putting these numbers in a vector (using the _VectorConverter_ smart component) and providing this vector to the _Positioner_ block, the numbers are multiplied by a 1000. It seems as if the _Positioner_ block interprets the input vector in meters even though it requires vector values in milimeters.

This can of course be easily solved by dividing each of the signal values by a 1000 before vectorising. However, this seems like unnecessary work. I would assume that it is more logical that if you input a vector containing [100 ,100, 0] into the _Positioner_ that it would interpret it as [100, 100, 0], rather than [100000, 100000,0].

I have added a picture so you can see what I mean.

Again, I am new to RobotStudio and the forum, I have tried to search for a solution or question about this but could not find it.

Thankyou in advance!

---

<div class="post-metadata">

**Author:** ![Simmu](https://avatars.discourse-cdn.com/v4/letter/s/e0b2c6/32.png) [@Simmu](https://tech-community.robotics.abb.com/u/Simmu)\
**Post date:** [March 13, 2023, 6:16am UTC](https://tech-community.robotics.abb.com/t/odd-inputs-for-positioner-smartcomponent/11055/2 "2023-03-13T06:16:06Z")

</div>

I have noticed this behaviour in other SmartComponents aswell. When setting a SurfaceVelocity in the PhysicsControl SmartComponent this is also the case. The parameter is set in mm/s but when I connect it with a variable it seems to be in m/s.

I have no idea why this is though.

---

<div class="post-metadata">

**Author:** ![BartSchumer](https://avatars.discourse-cdn.com/v4/letter/b/e480ec/32.png) [@BartSchumer](https://tech-community.robotics.abb.com/u/BartSchumer)\
**Post date:** [March 13, 2023, 3:56pm UTC](https://tech-community.robotics.abb.com/t/odd-inputs-for-positioner-smartcomponent/11055/3 "2023-03-13T15:56:36Z")

</div>

After experimenting with it more I also noticed that orientation vectors get multiplied by 57.295. This seems even more strange and adds even more work when trying to design simulations.

---

<div class="post-metadata">

**Author:** ![nicolahinssen](https://avatars.discourse-cdn.com/v4/letter/n/e47774/32.png) [@nicolahinssen](https://tech-community.robotics.abb.com/u/nicolahinssen)\
**Post date:** [March 13, 2023, 5:39pm UTC](https://tech-community.robotics.abb.com/t/odd-inputs-for-positioner-smartcomponent/11055/4 "2023-03-13T17:39:18Z")

</div>

> [@BartSchumer](#):
>
> After experimenting with it more I also noticed that orientation vectors get multiplied by 57.295. This seems even more strange and adds even more work when trying to design simulations.

It seems like this happens because it expects radians as “input”, and shows degrees as “output”. (57.295 \* 2π ≈ 360)