hexagon logo

PC-DMIS 2001 - Error when uploading a XYZ file

Hi everyone,

That's the first time i come on this forum. I have not a large experience in CMM.

I am trying to make measurements of a blade with the old PC-DMIS 2001. There are like 350 points per face... I'm doing this to compare a physical blade with a CAO model (surface model* : we can't know how the blade has been modeled)
So i would like to import a simple file (Text) as a .XYZ file.

I follow the syntax indicated in the manual :

XYZIJK METRIC
x,y,z,i,j,k

When i try to import the file i have an error message :
Le verouillage indique que l'entrée/sortie XYZ n'est pas disponible.
The lock indicates that the input / output XYZ is not available.

I have not find any posts about this error neither on the forum nor on Google.


An other solution would be to directly insert commands generated on Excel by copy/paste like this :
PNT13 =AUTO/POINT-VECT; AFFICH TOUS PARAM=OUI
THÉO/-45;45;-11;0;0;1
RÉEL/-45;45;-10.474;0;0;1
CIBLE/-45;45;-11;0;0;1
ÉPAISSEUR THÉO = 0; CART; ENCLENCH = OUI ;$
DÉPLACEMENT AUTO = NON; DISTANCE = 0


But PC DMIS does not like when i copy/paste from Exel or Notepad and say :
Erreur de ligne trop longue.
Error : line too long.


I am looking for your help Confused
Nobody here have used the CMM to do automatic control.

If you have any idea, you help is welcome.

Sorry if my English is not so good. As you can guess, this is not my native language.

Thanks !

Maxime
Parents
  • I don't see that they'd remove it tbh - it's not like it gives full CAD functionality or anything.

    The issue I see is that I've had to make extensive changes to scripts which run fine from anything 3.7 to current versions, in order for them to work on 3.2.


    That is because V3.5 was a complete re-coding of the software, basically.

    Biggest change that was put in V3.5 was the way alignments are handled.

    Bascially what it boils down to is that before V3.5, features measured after the alignment were tied to the alignment, and no further. With V3.5 (and all since), they don't stop there, but track all the way back to machine co-ordinates, if ya follow what I mean.

    Pre V3.5, when you move the part/fixture to a new place on the table and measured the alignment, all the post-alignment features "updated" to the new alignment position before they are measured. Now, they stick to where they were in machine co-ordinates where they were last measured until they are re-measured. Took a little to get used to this when the change was made as I was used to being able to see the features on the model where they belong after doing the alignment instead of being forced to wait for them to get measured again for them to be "on the model" where they belong.
Reply
  • I don't see that they'd remove it tbh - it's not like it gives full CAD functionality or anything.

    The issue I see is that I've had to make extensive changes to scripts which run fine from anything 3.7 to current versions, in order for them to work on 3.2.


    That is because V3.5 was a complete re-coding of the software, basically.

    Biggest change that was put in V3.5 was the way alignments are handled.

    Bascially what it boils down to is that before V3.5, features measured after the alignment were tied to the alignment, and no further. With V3.5 (and all since), they don't stop there, but track all the way back to machine co-ordinates, if ya follow what I mean.

    Pre V3.5, when you move the part/fixture to a new place on the table and measured the alignment, all the post-alignment features "updated" to the new alignment position before they are measured. Now, they stick to where they were in machine co-ordinates where they were last measured until they are re-measured. Took a little to get used to this when the change was made as I was used to being able to see the features on the model where they belong after doing the alignment instead of being forced to wait for them to get measured again for them to be "on the model" where they belong.
Children
No Data