PC-DMIS to LK-DMIS

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

  • PC-DMIS to LK-DMIS

    Anyone here know how difficult this is? I know someone whose company uses LK-DMIS. Their customer sent them a PC-DMIS program. Is it possible to use any of the program, or will they have to start new? From what I understand it is a very difficult part with days/weeks of programming.
    When in doubt, post code. A second set of eyes might see something you missed.
    sigpic

  • #2
    John,

    If it was Lk-Dmis to Pc-dmis, it would be easy. Pc-dmis has too many "macros" written that get used that are not DMIS compliant. I would say he could use some of it, depending on many factors, but he will re-write most of it.
    Jim Jewell

    Comment


    • #3
      Thanks, Jim. I had a feeling, and I also knew my Canadian buddy might have an answer!
      When in doubt, post code. A second set of eyes might see something you missed.
      sigpic

      Comment


      • #4
        Our sister company still uses LKDMIS and asks us for programs all the time. We give them the DMIS code out of the PCDMIS programs but, it's not much help to them as far as programming goes. They can program along and get an idea of how we may be checking a feature. They stayed with LKDMIS to use the Camio package but, when they ask me to troubleshoot a program for them, they are never using the solid model. Strange to spend that kind of money for a tool and never use it. I do know that the solid models exists because I do the initial setups and PPAPs on the parts before they take over. Can we say major loss in cost savings having us on two different softwares and them not using their's to its potential?
        sigpic

        Comment


        • #5
          djayne,

          That is a definite loss. We have several sister facilities, all running the same version of pcdmis.

          ZydecoPete
          sigpic

          Comment


          • #6
            Originally posted by jjewell View Post
            If it was Lk-Dmis to Pc-dmis, it would be easy. Pc-dmis has too many "macros" written that get used that are not DMIS compliant. I would say he could use some of it, depending on many factors, but he will re-write most of it.
            WJS

            I have the same experience. Going LK->PC: easy. The other way quickly runs into trouble, mostly because PC-DMIS has so many additional features. Quickly programs become all tangled up.

            I had some success with exporting to a DMI file and importing that into LK. But still, I think that in the end it would have been faster to re-program the whole part in LK.


            Jan.
            ***************************
            PC-DMIS/NC 2010MR3; 15 December 2010; running on 18 machine tools.
            Romer Infinite; PC-DMIS 2010 MR3; 15 December 2010.

            Comment


            • #7
              We do have two lab CMM's running LKDMIS 5.6 SP5 but, all new products have been going on the PCDMIS shop floor CMMs for the last 2 years. I think the plan is to fade out all quality techs and the quality lab all together. Maybe that's why our sister company chose to hang on the LKDMIS where only the QC techs are able to run the CMMs. Maybe I'm just working myself out of a job here with PCDMIS. I know that I get absolutely zero overtime.
              sigpic

              Comment

              Working...
              X