Will not save coordinates

[RoadKill95]

I'm running 4.2, I've got some programs written, but when I got to run them, they do not have the coordinates that I put in> Any ideas???????

[inspector212]

I'm running 4.2, I've got some programs written, but when I got to run them, they do not have the coordinates that I put in> Any ideas???????

You need to explain with more detail. What coordinates do you speak of grasshopper?

[JamesMannes]

I'm running 4.2, I've got some programs written, but when I got to run them, they do not have the coordinates that I put in> Any ideas???????

Post your code.

[RoadKill95]

When I wrote the program (offline and V4.1) whatever location of a feature or the moves to get there change. Here's an example;

FRSHRHI =FEAT/CONTACT/CIRCLE,CARTESIAN,IN,LEAST_SQR
THEO/<1599.4,585,-163.5>,<0,-1,0,18.2
This is what I programmed, and below is what it reads when I re-open the program and try to run it.

FRSHRHI =FEAT/CONTACT/CIRCLE,CARTESIAN,IN,LEAST_SQR
THEO/<1620.188,564.83,117.953>,<-0.3096724,0

[inspector212]

Is your alignment changing somehow? Is everything solid?

Did you execute between examples?

Is the first example from the offline station and the second an online station?

Is the scroll lock turned on?

[vpt.se]

I'm running 4.2, I've got some programs written, but when I got to run them, they do not have the coordinates that I put in> Any ideas???????

I have reported this error to the nordic office since two months back. Somehow they didn't believe that it was a PC-DMIS issue, but rather an operator error. They had to send to technicians in order to believe it, the tech's had to experience the bug 'live'. Some support, huh...

However, you must manually enter the nominal values each time you run this program in order to get a correct measurement. This bug are said to have been fixed in one of the later beta's. You can do a correct evaluation using the legacy method as it is not affected by this bug.
The bug appeared first in v4.2 and have been consistent in each and every release, beta or not, until later.

[Matthew D. Hoedeman]

I have reported this error to the nordic office since two months back. Somehow they didn't believe that it was a PC-DMIS issue, but rather an operator error. They had to send to technicians in order to believe it, the tech's had to experience the bug 'live'. Some support, huh...

However, you must manually enter the nominal values each time you run this program in order to get a correct measurement. This bug are said to have been fixed in one of the later beta's. You can do a correct evaluation using the legacy method as it is not affected by this bug.
The bug appeared first in v4.2 and have been consistent in each and every release, beta or not, until later.

An old method of 'fixing' this lovely enhancement (which has cropped up before, THANK YOU WILCOX!)-(but not for me!) is to make the nominals (THEO) into an equation. Type it in as 0+123.456 for your nominal and (in the older version that did this) it would no longer change those values.

[vpt.se]

Yeah, have tried that too, but it didn't help. It still messes with the nominals.

EDIT : I am dead tired of the 'fixes' that even tech support suggests - the software is meant to work - period. Apply the same 'fixing procedure' to your car or other stuff and it will get apparent how hilarous the entire thing is (which you all probably already knew).

[RoadKill95]

Thanks for the comments, I now have 3.7 loaded on my computer, we'll see if I have better luck with that.