3 programmers, 1 machine

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

  • 3 programmers, 1 machine

    We have 3 cmm programmers, 1 on first shift and 2 on second shift. one of the 2nd shift programmers cannot log into PCDMIS and take hits with our Global advantage machine. the other 2 programmers do not have any issues with pcdmis (that they have noticed). We have recently upgraded to a tp200 touch probing system and this seems to be when problem started. I cannot find any difference in machine parameters or settings. What am I missing?

  • #2
    So I presume each programmer has their own windows login? If two can use the machine and one cannot, I'd be looking more closely at windows admin rights of user who cannot use the machine.... over TP200 vs old probe system differences...

    Comment


    • gnichols73
      gnichols73 commented
      Editing a comment
      windows admin rights are over my head lol I will see what I can find out about this. thanks for the suggestion

  • #3
    Do the 3 programmers all user the same windows user account or do they each have their own? If they have separate accounts, make sure they close PC-Dmis and log out before switching users or the machine connection could be held onto by the first account that connected.

    Also, whenever you install a new version of PC-Dmis, all 3 users would have to launch PC-Dmis with full admin rights the first time they start up the new version - not just the guy that installed it (this information is in the readme file).
    Neil Challinor
    PC-DMIS Product Owner

    T: +44 870 446 2667 (Hexagon UK office)
    E: [email protected]

    Comment


    • gnichols73
      gnichols73 commented
      Editing a comment
      Yes we all have our own windows user accounts. I personally logged into and out of each user this morning to see who can and cannot take hits. I have checked for all the same version of PC-Dmis and made sure each one was using full admin rights. we have had issues with other software we using not being closed out before switching users. I will double and triple check these suggestions to be sure. thanks for the help

  • #4
    Also, check your anti-virus and firewall settings for each user. We have seen issues where the machine connection doesn't close when you exit PC-Dmis because the anti-virus / firewall is holding onto it.
    Neil Challinor
    PC-DMIS Product Owner

    T: +44 870 446 2667 (Hexagon UK office)
    E: [email protected]

    Comment


    • gnichols73
      gnichols73 commented
      Editing a comment
      this I never even thought of. thanks again

  • #5
    Windows user account permissions. Good luck . . .

    Comment


    • #6
      Capture.JPG



      (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


      • louisd
        louisd commented
        Editing a comment
        YES! was thinking the same thing... 3 programmers sounds like a recipe for disaster, lol.

    • #7
      Have you tried "reset user" in settings editor? This should wipe out user specific settings. Alternately his icon for PC-DMIS is an offline icon and he doesn't realize it.
      Systems Integrator
      Hexagon Manufacturing Intelligence

      Comment


      • #8
        For this reason, we have always been setup where the CMM computer was just for the CMM and had it's own profile. There is an extra computer for each programmer/operator to log into his personal profile to send/receive emails and use our ERP system.
        PC-DMIS 2016.0 SP8

        Jeff

        Comment


        • gnichols73
          gnichols73 commented
          Editing a comment
          I have made this suggestions several times to no avail. we keep getting told the computer/software will work just fine with multiple users. we also have 4 separate CMMS that each programmer can log into with their own username

      • #9
        I appreciate everyones help and suggestions. The problem progressed to the point that the machine would not take readings or register hits under any of the users not just the one. Hexagon IT worked on this off and on for a couple of days. Today a field Tech came on site to work on issue and discovered that all of our probe files had become corrupted and had defaulted to a scanning head (which we did have scanning probe build ups but they were named specifically for scanning). Also 3 of the tips stack ups we use a lot were not even in the file anymore. we did finally fine one file that had changed from a .prb to a .prg. Having rebuilt all of our probe stack ups all 3 programmers are up and running at full capability.

        Comment

        Related Topics

        Collapse

        Working...
        X