qual. tool locations not updating (v3.7 MR3)

I'm using v3.7 mr3. I qualify on a 1" sphere, "yes" to has it moved. This updates that spheres XYZ definition.
I switch probe configurations, select the same sphere, "no" it hasn't moved. The spheres' definition is not the same as after the first qualify, so the probe heads for an old location. This is a new trick, hasn't given me any trouble before. I tried adding a new "tool". This fixes the problem, but only once. For now,
I have to add a new tool (deleting some old ones) each time I start. What up?

Parents

probetip over 12 years ago

Thanks to everyone for your answers. Here I go into "shoulda" land. When you say that a given tool has moved, the system uses the current
probe offset lengths as is, and updates the tool.xyz in the stored file. When you switch probes, and try to qualify on the "just established"
tool, that tools location SHOULD BE being read from the file and used to update the probe offsets of the new probe.
It SHOULDNT matter how many tools you have, or what you named them, they are all stored in tool.dat to be accessed or updated
depending on whether you select YES tool has moved or NO tool has not moved.
Or am I getting signals thru my tin foil hat?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

probetip over 12 years ago

Thanks to everyone for your answers. Here I go into "shoulda" land. When you say that a given tool has moved, the system uses the current
probe offset lengths as is, and updates the tool.xyz in the stored file. When you switch probes, and try to qualify on the "just established"
tool, that tools location SHOULD BE being read from the file and used to update the probe offsets of the new probe.
It SHOULDNT matter how many tools you have, or what you named them, they are all stored in tool.dat to be accessed or updated
depending on whether you select YES tool has moved or NO tool has not moved.
Or am I getting signals thru my tin foil hat?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

No Data