Dwell before each hit taken?

I noticed that sometimes when taking points along the contour of a part, I can see the readout showing good vector numbers while I scan, but after I make a point group and then try to make a profile dimension for the report, shows the numbers all over the place.

I pondered this a bit and tryed a few things before noticing that if I come to a complete stop, and dwelled for just a second before each hit, everything reads fine. When I take points while the ball probe is still moving, the points are thrown out seemingly at random.

Now I know that if the probe is gliding along the surface too fast, the romer will make an unpleasant sound letting you know to slow down, but I'm refferring to times that it's not making that sound, but still throwing the points out

Is there a dwell setting of some sort that can adjust how long you must sit before each hit?
Our old romer, (that still uses Supra Stuff,) can take acurate points while the probe is moving with no issue, so I got a bit spoiled using that old dinosaur

Parents

Colin Simithraaratchy over 12 years ago

It doesn't. It's just that the Pulled Point functionality is being activated, whereas the Supra s/w didn't have it.

<you might not care about this>
Here's how the (standard) button operation works:

You can click a button. (takes a hit)
You can hold a button for less than 1 sec. (takes a pulled hit)
You can hold a button for greater than 1 sec. (takes a scan)

What I think is happening: you're not striking the button fast enough, and you're inadvertently activating the second function. Now, I know that we can go into the Settings Editor and change the timing that controls the temporal functionality of these button presses, but it's more easily solved by simply striking the button faster.
</you might not care about this>

Maybe the new software you're using has made your old technique more difficult to use correctly. Maybe a new technique might work better with the new software?

Seems to me that if you're clicking fast enough, that shouldn't be consistently happening....and it also seems to me that a scan/body axis scan might be getting you more/better information. Let me know if you need more information on the subject. Unfortunately, I don't know where in the Settings Editor to go to effectively change the button timing -- that might be one for tech support...

ps

i also wonder if your current laptop is underpowered and that's contributing to the timing issues....
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

Colin Simithraaratchy over 12 years ago

It doesn't. It's just that the Pulled Point functionality is being activated, whereas the Supra s/w didn't have it.

<you might not care about this>
Here's how the (standard) button operation works:

You can click a button. (takes a hit)
You can hold a button for less than 1 sec. (takes a pulled hit)
You can hold a button for greater than 1 sec. (takes a scan)

What I think is happening: you're not striking the button fast enough, and you're inadvertently activating the second function. Now, I know that we can go into the Settings Editor and change the timing that controls the temporal functionality of these button presses, but it's more easily solved by simply striking the button faster.
</you might not care about this>

Maybe the new software you're using has made your old technique more difficult to use correctly. Maybe a new technique might work better with the new software?

Seems to me that if you're clicking fast enough, that shouldn't be consistently happening....and it also seems to me that a scan/body axis scan might be getting you more/better information. Let me know if you need more information on the subject. Unfortunately, I don't know where in the Settings Editor to go to effectively change the button timing -- that might be one for tech support...

ps

i also wonder if your current laptop is underpowered and that's contributing to the timing issues....
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

No Data