hexagon logo
Register Sign in
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 39 views
  • Users 0 members are here
Options
Related

Parametric Programing in PCDMIS (general outline & tools?)

michelle
Hello,

I have unsuccessfully attempted to find any sort of solid documentation on 'parametric programming' in PCDMIS. I have searched and read related threads both on this forum and cmm guys, but I still have not really got the just of it.
Below is my best guess on how things may work when it comes to parametric programming in PCDMIS:

* The Forms Editor lets you code in Visual Basic, and can be used to create the GUI for the operator to interact with.

* The Basic Script Editor lets you code in Basic, and can be used to process the operators' input and perform calculations based on this input before storing resultant nominal values into globally accessible variables; which then can be later compared to measurements taken in DCC mode?
(1) Is my above train of thought on the right track? Or have I got it completely wrong?

I am assuming that all parametric programming is done within IN PCDMIS itself with no need for any external coding environment.
(2) Am I correct in making this assumption?

If I have got the above all wrong, could someone please list the tools and general approach they use to write parametric programs for PCDMIS? For example, lets say you needed to take typed input in from the operator, you needed to read a text file in (parameters specifying the part), you needed to do appropriate calculations to work out where all your points to measure are and values of your nominals etc. etc
(3)What list of tools would you need? Only the Script and Form editors, or something more?

Any suggestions or comments would be very much appreciated.

michelle
Parents
  • It would be enough with the script and form editors. However, some use Visual Basic to interact with (talk to) PC-DMIS, mostly because (I think) the syntax are very similar to the Cypress Enable scripting language.

    No matter what, it would take some extensive coding from your side if you would want to 'generate' PC-DMIS programs on-the-fly based on operator input. If there are very few differences between the programs, you could create a 'base' template program, containing all the probe moves/hits (using variables/loops) and then just feed the values to this template program from a textfile or similar.

    I have never used it, but I think 'marked sets' could help you out as well. Check with the more experienced programmers on the board how to use them (marked sets) best. If I understood the marked sets logic correctly, you could create one program for all your similar parts and then just 'tell' the program what to execute by using the marked sets (depending on the part to measure).
Reply
  • It would be enough with the script and form editors. However, some use Visual Basic to interact with (talk to) PC-DMIS, mostly because (I think) the syntax are very similar to the Cypress Enable scripting language.

    No matter what, it would take some extensive coding from your side if you would want to 'generate' PC-DMIS programs on-the-fly based on operator input. If there are very few differences between the programs, you could create a 'base' template program, containing all the probe moves/hits (using variables/loops) and then just feed the values to this template program from a textfile or similar.

    I have never used it, but I think 'marked sets' could help you out as well. Check with the more experienced programmers on the board how to use them (marked sets) best. If I understood the marked sets logic correctly, you could create one program for all your similar parts and then just 'tell' the program what to execute by using the marked sets (depending on the part to measure).
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement