hexagon logo
Register Sign in
  • Replies 8 replies
  • Subscribers 32 subscribers
  • Views 197 views
  • Users 0 members are here
Options
Related

Dwell before each hit taken?

BlueRay
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
  • Here's some code that I do just what you are asking. 

    COMMENT/DOC,******************************
            COMMENT/DOC,CMM will pause at this point, this is to simulate longer prehit / retract.
            COMMENT/DOC,******************************
            ASSIGN/STARTTIME1 = SYSTEMTIME("mm'.'ss")
            ASSIGN/STARTTIME2 = STARTTIME1
TIMECHECK  =LABEL/
            ASSIGN/STARTTIME3 = SYSTEMTIME("mm'.'ss")
            ASSIGN/TIMEDELAY = STARTTIME2+.02
            IF_GOTO/TIMEDELAY>STARTTIME3,GOTO = TIMECHECK
PNT3       =FEAT/POINT,RECT
            THEO/-0.0501,1.32,-0.02,1,0,0
            ACTL/-0.0513,1.32,-0.0201,1,0,0
            MEAS/POINT,1
            HIT/BASIC,-0.0501,1.32,-0.02,1,0,0,-0.0513,1.32,-0.0201
            ENDMEAS/
            MOVE/POINT,0,1.43,-0.02
            COMMENT/DOC,******************************
            COMMENT/DOC,CMM will pause at this point.
            COMMENT/DOC,******************************
            ASSIGN/STARTTIME1A = SYSTEMTIME("mm'.'ss")
            ASSIGN/STARTTIME2A = STARTTIME1A
TIMECHECKA =LABEL/
            ASSIGN/STARTTIME3A = SYSTEMTIME("mm'.'ss")
            ASSIGN/TIMEDELAYA = STARTTIME2A+.02
            IF_GOTO/TIMEDELAYA>STARTTIME3A,GOTO = TIMECHECKA
PNT4       =FEAT/POINT,RECT
            THEO/-0.0501,1.43,-0.02,1,0,0
            ACTL/-0.0513,1.4302,-0.0202,1,0,0
            MEAS/POINT,1
            HIT/BASIC,-0.0501,1.43,-0.02,1,0,0,-0.0513,1.4302,-0.0202
            ENDMEAS/
            MOVE/POINT,0,1.315,-0.02
            COMMENT/DOC,******************************
            COMMENT/DOC,CMM will pause at this point.
            COMMENT/DOC,******************************
            ASSIGN/STARTTIME1B = SYSTEMTIME("mm'.'ss")
            ASSIGN/STARTTIME2B = STARTTIME1B
TIMECHECKB =LABEL/
            ASSIGN/STARTTIME3B = SYSTEMTIME("mm'.'ss")
            ASSIGN/TIMEDELAYB = STARTTIME2B+.02
            IF_GOTO/TIMEDELAYB>STARTTIME3B,GOTO = TIMECHECKB
PNT5       =FEAT/POINT,RECT
            THEO/0.0499,1.32,-0.02,-1,0,0
            ACTL/0.0431,1.3193,-0.0201,-1,0,0
            MEAS/POINT,1
            HIT/BASIC,0.0499,1.32,-0.02,-1,0,0,0.0431,1.3193,-0.0201
            ENDMEAS/
            MOVE/POINT,0,1.43,-0.02
            COMMENT/DOC,******************************
            COMMENT/DOC,CMM will pause at this point.
            COMMENT/DOC,******************************
            ASSIGN/STARTTIME1C = SYSTEMTIME("mm'.'ss")
            ASSIGN/STARTTIME2C = STARTTIME1C
TIMECHECKC =LABEL/
            ASSIGN/STARTTIME3C = SYSTEMTIME("mm'.'ss")
            ASSIGN/TIMEDELAYC = STARTTIME2C+.02
            IF_GOTO/TIMEDELAYC>STARTTIME3C,GOTO = TIMECHECKC
PNT6       =FEAT/POINT,RECT
            THEO/0.0499,1.43,-0.02,-1,0,0
            ACTL/0.0423,1.4301,-0.0201,-1,0,0
            MEAS/POINT,1
            HIT/BASIC,0.0499,1.43,-0.02,-1,0,0,0.0423,1.4301,-0.0201
            ENDMEAS/
  • Ummm, not sure what to do with this??

    Just to be clear this is a portable CMM and I am taking the points manually
  • Ahh.. Not sure what you are after then.
    This is for a DCC CMM and the code causes the machine to pause before taking the next hit.

    Can't you just do that manually?
    I mean... just don't take the next point until you feel you are ready.
  • Oh, sorry I meant to post in the PC-DMIS Portable

    haha my issue is that I seem to be ready before the CMM is... Whats happening is I'm being forced to stop and pause at each location before taking the hit, or else the reported info shows wrong numbers.
    What I'd like to be able to do is slide my probe along the surface of a part taking random hits either without stopping my probe, or at least a very minimal stop. Right now I'm being slowed down by having to wait for a sec before each hit I take

    I'm looking to do something similar to "plane auto trigger," except I'd like to click the points manually, instead of holding the button down taking a ridiculous amount of points
  • Oh, sorry I meant to post in the PC-DMIS Portable

    haha my issue is that I seem to be ready before the CMM is... Whats happening is I'm being forced to stop and pause at each location before taking the hit, or else the reported info shows wrong numbers.
    What I'd like to be able to do is slide my probe along the surface of a part taking random hits either without stopping my probe, or at least a very minimal stop. Right now I'm being slowed down by having to wait for a sec before each hit I take

    I'm looking to do something similar to "plane auto trigger," except I'd like to click the points manually, instead of holding the button down taking a ridiculous amount of points

    BR:

    What's happening when you "hear a weird noise"? You are inadvertently creating Pulled Hits. check the Help Menu for "Pulled Hits Method" for the full explanation. Cliff's Notes: The IJK of your hits is being replaced with the direction of your dragging.

    Possible solutions:

    1) slow down, so the Pulled Hits are not being activated
    2) create Vector Points at the location you want them, and then Auto Trigger them. Group and Profile as needed.
    3) create a Manual Scan by holding down button 2 and dragging. Profile as needed
    4) create a Body Axis Scan. Profile as needed.

    All of these methods will work if you're trying to find the profile of a contoured surface. Scans sound the easiest to me, but your application might be wildly different than what I'm thinking.
  • Yeah I understand why it faults and I've established how to make hits work properly, that's not an issue. No problems with getting good points. The issue is with how slow I'm required to go to make good points happen. I'd like to know how I can make this software read faster so I don't have to slow down so much.

    I got used to using our old Romer where I could glide the probe across a surface hitting the button whenever I want and Supra Stuff knew exactly where I was at each moment. I find it hard to belive that our brand new version of PC-DMIS requires so much more time to think than our ancient MS DOS software, but maybe it does afterall?
  • 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....

  • Yes the timing controls editor for button presses is exactly what I'm looking for. Any info on this would be greatly appreciated
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement