hexagon logo
Register Sign in
  • Replies 15 replies
  • Subscribers 222 subscribers
  • Views 296 views
  • Users 0 members are here
Options
Related

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

r.ntibu
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?
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?
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement