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
  • Anders, I too was confused by some of the details, and lack thereof. r.nitubu, let me ask this a different way. Do you see the machine moving when you run it from the script. I suspect you are getting frustrated with these questions, but when we assume, well. . . . .

    Aside from that, we wrote a simple VBA automation project to execute a similar program using a perimeter scan and then a surface profile, executing online there was no problem.

    Can you attach ALL the files involved please? The PRG, the c# project with all subs and functions, and whatever else might be included and we will try it again here in a different way.

    and. . . let me ask you for one more file. In PC-DMIS, make sure debug is enabled. You'll find this under Edit - Preferences - Machine Interface Setup and then the Debug tab. Enable the debug log, then exit PC-DMIS. Now start PC-DMIS (without automation) and execute that same routine. Then exit PC-DMIS and send the debug file. It is usually called debug.text and found in the folder named C:\ProgramData\Hexagon\PC-DMIS\2017 R2 with that last folder based on whatever version you are using. Please send that file also
Reply
  • Anders, I too was confused by some of the details, and lack thereof. r.nitubu, let me ask this a different way. Do you see the machine moving when you run it from the script. I suspect you are getting frustrated with these questions, but when we assume, well. . . . .

    Aside from that, we wrote a simple VBA automation project to execute a similar program using a perimeter scan and then a surface profile, executing online there was no problem.

    Can you attach ALL the files involved please? The PRG, the c# project with all subs and functions, and whatever else might be included and we will try it again here in a different way.

    and. . . let me ask you for one more file. In PC-DMIS, make sure debug is enabled. You'll find this under Edit - Preferences - Machine Interface Setup and then the Debug tab. Enable the debug log, then exit PC-DMIS. Now start PC-DMIS (without automation) and execute that same routine. Then exit PC-DMIS and send the debug file. It is usually called debug.text and found in the folder named C:\ProgramData\Hexagon\PC-DMIS\2017 R2 with that last folder based on whatever version you are using. Please send that file also
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement