vector odity with llSetLinkPrimitiveParams

This one eludes me..
I have a two obj linked Prim. The child moves from one pos to another -alt least it tells me that it moves -It actuallay does not move at all..

In a timer in root i have
{
pos=llGetPos();//tested llGetLocalPos() ..no...
pos=pos+<0,3,0>;
llSetLinkPrimitiveParams(id, [PRIM_POSITION, pos] );
}
and then shift back
:
pos=pos+<0,0,0>;

The debug shows
obj: pos: <87.88179, 189.40472, 297.58188>
obj: pos: <87.88179, 192.40472, 297.58188>
obj: pos: <87.88179, 189.40472, 297.58188>

But NO movement
If i on the other hand does this:
llSetLinkPrimitiveParams(id, [PRIM_POSITION, <0,0,0>] );
and the shift
llSetLinkPrimitiveParams(id, [PRIM_POSITION, <0,3,0>] );
..Then the child DO move..
Why does that act this way?
tyia.

First off, you DO want llGetLocalPos(), because the position you set with llSetPos() or llSetPrimitiveParams()/PRIM_POSITION is local (in the root prim's coordinate system) for a child prim. The code you show should move the prim once provided that pos+<0,3,0> is within 10m of the root prim's center. After that, it depends on whether you use llGetLocalPos() to set 'pos' again when you do the second move (in which case 'pos+<0,0,0>'--which is the same as just 'pos'--is not going to move it at all, and more than likely the next 'llGetLocalPos()+<0,3,0>' is going to be outside the 10m link distance and the move won't happen) or if 'pos' is a global variable whose value isn't changed until the next llSetPos()/llSetPrimitiveParams() (in which case the second move SHOULD be working).

Q
provided that pos+<0,3,0> is within 10m of the root prim's center.
q
...ofcause :/ -i was so confused -if only an error would popup when the limit is broken..
Thanks Hewee!

We would all be spammed to death if it did!

Do you have the object selected when the script is running? I find the viewer still doesn't always like to show prim movements all the time if an object is selected