# Reading Installation Variable Values to URCap **URL:** \ **Category:** URCap Development\ **Created:** [March 27, 2019, 3:17pm UTC](https://forum.universal-robots.com/t/reading-installation-variable-values-to-urcap/3961 "2019-03-27T15:17:03Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![chris.briedenhann](https://avatars.discourse-cdn.com/v4/letter/c/9de053/32.png) [@chris.briedenhann](https://forum.universal-robots.com/u/chris.briedenhann)\ **Post date:** [March 27, 2019, 3:17pm UTC](https://forum.universal-robots.com/t/reading-installation-variable-values-to-urcap/3961/1 "2019-03-27T15:17:03Z")
Hi I need to read the installation Variable values into the URCap, is there any way of doing this. My project involves using a SENSOPART camera with its URCap. I had a issue where I get the offsets from the camera, my program uses the offsets and the path os offset, but as soon as I step to the point or use the Move\_Here function, the robot references references the point to the original plane and not the offset plane, same when I do a set waypoint, it then adds the offset to the waypoint coordinates. See post [Defining points with respect to plane - #20 by chris.briedenhann](https://forum.universal-robots.com/t/defining-points-with-respect-to-plane/934/20) for my setails on the problem. I wrote a URCap to overcome this, see attached, where I input the offsets manually and the Move\_Here and TouchUp function works correctly. I now need to find a way to get the offset values from the SENSOPART URCap into my URCap. ![URCap](https://us1.discourse-cdn.com/flex020/uploads/universal_robots/original/2X/7/79b2d0008f831325a13518edc28305ae66b07d48.jpeg) Thanks Chris [URCap Node.pdf](https://us1.discourse-cdn.com/flex020/uploads/universal_robots/original/2X/f/f8ef97fb850de6d666149ff4ae7a03a67191331c.pdf) (11.8 KB) ---
**Author:** ![jbm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/jbm/32/614_2.png) [@jbm](https://forum.universal-robots.com/u/jbm)\ **Post date:** [March 27, 2019, 3:29pm UTC](https://forum.universal-robots.com/t/reading-installation-variable-values-to-urcap/3961/2 "2019-03-27T15:29:34Z")
I wouls recommend reaching out to Sensopart, to query if they have any interfaces in their URCap to pull these values - probably in URScript or via a Script Function. ---
**Author:** ![chris.briedenhann](https://avatars.discourse-cdn.com/v4/letter/c/9de053/32.png) [@chris.briedenhann](https://forum.universal-robots.com/u/chris.briedenhann)\ **Post date:** [March 27, 2019, 3:37pm UTC](https://forum.universal-robots.com/t/reading-installation-variable-values-to-urcap/3961/3 "2019-03-27T15:37:18Z")
I will do that. Is there a way to get the Values of Installation Variables in a URCap as this would be the easiest way of doing it, writing the offset to the Variable and reading it into the URCap. Thanks ---
**Author:** ![jbm](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.universal-robots.com/jbm/32/614_2.png) [@jbm](https://forum.universal-robots.com/u/jbm)\ **Post date:** [March 27, 2019, 3:56pm UTC](https://forum.universal-robots.com/t/reading-installation-variable-values-to-urcap/3961/4 "2019-03-27T15:56:31Z")
Only the existence of the variable is known in the PolyScope/URCap domain. The variables value is only certain to be known in URScript, when the program is running. ---
**Author:** ![chris.briedenhann](https://avatars.discourse-cdn.com/v4/letter/c/9de053/32.png) [@chris.briedenhann](https://forum.universal-robots.com/u/chris.briedenhann)\ **Post date:** [March 27, 2019, 8:02pm UTC](https://forum.universal-robots.com/t/reading-installation-variable-values-to-urcap/3961/5 "2019-03-27T20:02:28Z")
Would you say that what I am trying to do is possible or not, don’'t really want to waste any more time on this if it will not work. Its a pity as most of the project we are looking at need this functionality. Will you be adding the functionality on future updates? The fact that the variable is only available when the program is running is something you will have to look at fixing as well, as this causes problem when referencing a Installation variable in script and using the step function. Eg. movel(pose\_trans(CameraOffset, Position), a = 1.2, v=0.3, r = 0.0)