PCDMIS Not Recording Hits

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • PCDMIS Not Recording Hits

    As the title says, the probe tip is hitting the part to be inspected, but the software isn't recording hits at all. The probe readout stays the same for all 3 axis's and the hit counter stays right at 0.

    I've tried to restart the program and machine, calibrate the probe tip... but no luck. I think it could be the software itself that's simply not recognizing the hits for whatever reason. Has this happened to you? If so, what was the cause?

    Edit: It works now, amazingly. I am still curious as to why PCDMIS stopped registering hits all of a sudden, though.

    For anyone curious as to what I did: I wanted to see if the "Emergency Error" message would come up if I snagged the styli away from the probe head by hand. It did. When given the option to go back to the program or Shut Down, I decided to shut down PCDMIS and opened it up again. Whaddya know, the software now recognizes hits from the probe tip. It might have something to do with the communication between the machine and software. Any ideas are accepted so I know what to do next time.
    Last edited by ALousyUser; 04-26-2019, 11:05 AM.

  • #2
    magnets?
    sigpic
    Originally posted by AndersI
    I've got one from September 2006 (bug ticket) which has finally been fixed in 2013.

    Comment


    • ALousyUser
      ALousyUser commented
      Editing a comment
      Can you elaborate? I have the part sitting on a magnetic grinding block. I took away the grinding block but the hits still aren't being recorded. As far as I know, there are no other magnetic forces as strong as the grinding block nearby....

    • NinjaBadger
      NinjaBadger commented
      Editing a comment
      Magnet (or even a magnetised part) can stop a touch probe (eg TP20) from registering hits. This is why I asked about if the machine stopped. As it is the signal is getting from probe to Controller.

    • ALousyUser
      ALousyUser commented
      Editing a comment
      I see. We place parts on the grinding block all the time and have had zero problems. This leads me to think that something else is at play here.

      For your knowledge, I'm using a
      - Leitz LSP-X1s probe head
      - A Browne & Sharpe CMM
      - 1BY20MM styli

      It might just be the connection between the machine and computer going awry.

      Edit: It works now, amazingly. I am still curious as to why PCDMIS stopped registering hits all of a sudden, though.

      ​​​​​​​For anyone curious as to what I did: I wanted to see if the "Emergency Error" message would come up if I snagged the styli away from the probe head by hand. It did. When given the option to go back to the program or Shut Down, I decided to shut down PCDMIS and opened it up again. Whaddya know, the software now recognizes hits from the probe tip. It might have something to do with the communication between the machine and software. Any ideas are accepted so I know what to do next time.
      Last edited by ALousyUser; 04-26-2019, 11:05 AM.

  • #3
    When you manually probe the part does the machine stop, or let you keep driving into/through the part?
    Applications Engineer
    Hexagon UK

    Comment


    • ALousyUser
      ALousyUser commented
      Editing a comment
      The machine stops when I attempt to drive through the part (in the YPLUS direction) and into the part (ZMINUS), but no error message comes up at all (like it should) and the jog box doesn't stop working (as a fail-safe), so I am able to keep using the machine as if nothing happened. This is odd.

      Edit: It works now, amazingly. I am still curious as to why PCDMIS stopped registering hits all of a sudden, though.

      ​​​​​​​For anyone curious as to what I did: I wanted to see if the "Emergency Error" message would come up if I snagged the styli away from the probe head by hand. It did. When given the option to go back to the program or Shut Down, I decided to shut down PCDMIS and opened it up again. Whaddya know, the software now recognizes hits from the probe tip. It might have something to do with the communication between the machine and software. Any ideas are accepted so I know what to do next time.
      Last edited by ALousyUser; 04-26-2019, 11:05 AM.

  • #4
    my guess:

    you had two programs open.
    Ex-Hex

    Comment


    • ALousyUser
      ALousyUser commented
      Editing a comment
      My long-distance mentor suggested the same thing. It's definitely something to keep in mind for next time (hopefully not!).

  • #5
    was the enable probe button pushed? Restarting PCDMIS i believe turns it back on.
    Time for the Trolls to leave.

    Comment


    • louisd
      louisd commented
      Editing a comment
      Yes, my machines are setup to not detect probe hits while manually orienting with jogbox, unless both the SLOW/Turtle and Probe Enable buttons are on.
      FYI, Probe enable on the Leitz LSP-X1s is a "Probe Balance" toggle, it must ALWAYS be on while probing in DCC or manual.

    • ALousyUser
      ALousyUser commented
      Editing a comment
      Yes it was.

  • #6
    I have a TP20 system, and sometimes, when I accidently take a manual hit in rapid (without the turtle), the machine will stop registering hits.

    I slap the stylus (move it til it almost stops in a sideways manner, not actually slap it) and it makes a beep.

    The issue is then cleared. Version 2009 and 2012.

    When taking a hit mannually, I'm always controlling the speed with the stick, so my hits aren't crashes, they are slow just like normal touch speed, I'm just barely touching/rotating the stick.

    Global performance, I know it has something to prevent false triggers, maybe the contact in rapid, even though not fast enough to do damage as a crash, counts as a "crash" to the software with the probe comp off and the machine is waiting for the crash to be cleared.

    Sounds somewhat like what you describe though, so long as you touched the part with the turtle off. For me this is usually my manual hit locating the sphere. If I'm aligning, I notice the machine move too fast to the following manual touch, erase all hits and start over with the turtle on.

    hth

    Comment


    • #7
      In the 70's and early 80's this was the button that you push to record all the hits, but that darn old DJ would always cut in right before the song ended.

      51tFKUog95L._SX466_.jpg

      No Problem Roberto just recycle them and use a door or curtain

      f677cd3f590179bce9fd20e6841b2d74.jpg ​​​​​​​
      Last edited by KIRBSTER269; 04-30-2019, 11:59 AM.
      (In Memory of my Loving wife, "Ronda" who I lost March 7, 2016. I love you baby.)
      They say "Nobody's Perfect." I must be Nobody.

      Comment


      • Roberto
        Roberto commented
        Editing a comment
        funny! then your tape got eaten by the cassette player.
        Last edited by Roberto; 04-30-2019, 12:34 PM.

      • ALousyUser
        ALousyUser commented
        Editing a comment
        As a 90's kid, the cassette tape curtain is a completely novel idea to me! Hilarious.

    • #8
      I see you got it working again. Maybe your module is going bad. Or, two programs were open at the same time like Anthony was saying.

      Comment


      • Jason_S
        Jason_S commented
        Editing a comment
        I can't count how many times this has been my issue with hits not counting.
        Self induced problems.

      • ALousyUser
        ALousyUser commented
        Editing a comment
        Funny, my mentor suggested the same thing (two programs open at the same time). I think my module is fine, but I'll keep that in mind. Thanks a ton.

    Related Topics

    Collapse

    Working...
    X