hexagon logo

PC-DMIS 2017 (interop.pcdlrn.dll) issue on profile of a surface measurements

Hi,

i am software programer so i dont really know about inspection and CMM.

i am having issue using the library interop.pcdlrn.dll for the command "perimeter scan" for a "profile of surface".


when i'm using the librairy it shows a measurement value of 0 like if the machine is offline. but when i use the software PC-DMIS, i have the good results.


but when i do a "constructed set" for a "profile of surface" i have good results either if im using the library or the software.

i dont't understand how the library can act differently from the software. this strange behavior prevents us to use the custom software on the prod environnment.

because im a software programmer i dont really know how to express myself in this forum so i'm sorry if i dont give enough details

Parents
  • I don't see anywhere in the code where you are trying to get a profile dimension. I am a little confused about your question. Are you only trying to execute it through C# and produce a report from the PC-DMIS application?

    I am not sure which temporary files you are referring to. There are files for probe calibrations, toolchanger calibrations, rotary table calibrations, statistics, and more. Can you gie me an example of which temporary files you are asking about?

    There does not need to be a 1:1 correlation between the interop and PC-DMIS version. The only time a problem would arise if you were accessing some new commands which might not have been in an older interop, but that is not the case here.

    Let's start over. What are you trying to accomplish with this C# utility?


    Hey Don,

    Yes exactly, the only thing i am trying to do is to execute it through c#.

    When I execute PC-DMIS trough c#, the generated PDF report is different at a specific command result. This command is a "perimeter scan" for a "profile of surface". It shows 0.0000 with an online machine (i don't know if it's linked, but when i execute it through c# with an offline machine, it shows a value on DEV like in this post, but i have absolutly no technical skill on inspection stuff and it is sometimes hard for a programmer to convince non programmer that bug is not only from code.).

    - PC-DMIS trough c# :



    - PC-DMIS trough PC-DMIS:





    I mentioned temporary file because all the cmm programs are stored on a network folder. As seen on the c# sample code, Each time a program is needed for inspection, the custom software do a local copy of the .prg file and the .cad file on
    c:\\TEMPCMM\\ so the network cannot cause issue on the inspection process. all executed programs are executed from c:\\TEMPCMM\\ . i noticed temporary hidden files like

Reply
  • I don't see anywhere in the code where you are trying to get a profile dimension. I am a little confused about your question. Are you only trying to execute it through C# and produce a report from the PC-DMIS application?

    I am not sure which temporary files you are referring to. There are files for probe calibrations, toolchanger calibrations, rotary table calibrations, statistics, and more. Can you gie me an example of which temporary files you are asking about?

    There does not need to be a 1:1 correlation between the interop and PC-DMIS version. The only time a problem would arise if you were accessing some new commands which might not have been in an older interop, but that is not the case here.

    Let's start over. What are you trying to accomplish with this C# utility?


    Hey Don,

    Yes exactly, the only thing i am trying to do is to execute it through c#.

    When I execute PC-DMIS trough c#, the generated PDF report is different at a specific command result. This command is a "perimeter scan" for a "profile of surface". It shows 0.0000 with an online machine (i don't know if it's linked, but when i execute it through c# with an offline machine, it shows a value on DEV like in this post, but i have absolutly no technical skill on inspection stuff and it is sometimes hard for a programmer to convince non programmer that bug is not only from code.).

    - PC-DMIS trough c# :



    - PC-DMIS trough PC-DMIS:





    I mentioned temporary file because all the cmm programs are stored on a network folder. As seen on the c# sample code, Each time a program is needed for inspection, the custom software do a local copy of the .prg file and the .cad file on
    c:\\TEMPCMM\\ so the network cannot cause issue on the inspection process. all executed programs are executed from c:\\TEMPCMM\\ . i noticed temporary hidden files like

Children
No Data