LK Camio import to PC-DMIS

[oleksandr]

Hello!

I am running PC-DMIS 2014.1 and I have Hexagon 7.10.7SF CMM.
As well I have a program written in Nikon Camio software. And I have issues with importing this program to my PC-DMIS.
In the begining I`ve received program as a simple .txt file. When I`ve tried to import it I`ve received this error:

1.jpg

Then I`ve changed .txt file extension to .dmi. Tried to import it, but my PC-DMIS crashes all the time:

2.jpg

Then I`ve tried to export sample program from PC-DMIS to DMIS code, copy/paste text from DMIS program and import it back. But here I have next problems:
1. Circle feature can not be exported from PC-DMIS to DMIS code, part of error log:
* Alignment used during export: STARTUP
* Total number of errors: 0
* Total number of warnings: 1
* Warning! For feature 'CIR1', unexpected feature type parsed from locator text&
* ''. Forcing feature type 40.
START_PT 4 0.0000 0.0000 0.0000
A15R15O00 3 15.0000 15.0000 0.0000
A0000B0000 2 0.0000 0.0000
TIPCTR 1 0.0000 0.0000 0.0000
CIR1 40 0.0000 0.0000 14.1410 -0.00000 -0.00000 -1.00000 56.8500 U 0.0000 &
0.00000 0.00000 1.00000
2. When I copy/paste to .dms file DMIS code and try to import it back I receive next

2634.jpg

Any ideas why this happens?
I already know that it is not the best way to import DMIS code to PC-DMIS, rather it is easier to rewrite program, but I am going to have several programs in DMIS code and if I could import them it would save me some time

[DAN_M]

Message means that there are bits of code in the native software that PC DMIS does not have an equivalent for.

My advise would be to re-write the program.

Its job security, it will be done "right" (assuming you know your stuff), and it will be way less annoying.

[oleksandr]

Yes, I understand that from one side it is better to rewrite the program, but on another side I will have plenty of them, which could have saved me time (just to check and adjust if necessary).
I am wondering why even native pc-dmis program cannot be converted to dmis and back, despite there is such kind of option...

[Peter Fuller]

My gut check tells me the hyphen in the Text/Oper code is the issue "Pre-Alignment" is probably failing thinking it's a math function of some kind. Alternately the DMIS code should be in plain text, just delete the offending code.

[Peter Fuller]

Alternately can you post the first few lines of code in the dmis file? I'd like to see if the format is correct. I notice it's unable to set the units from line #1? it would be interesting to see what else is in there.

[oleksandr]

This is sample of the DMIS code I have from Camio, measurement of 3 points and 2 circles. It seems like pure DMIS:

TEXT/OPER,'Pre-alignment in MANUAL mode'

MODE/MAN

F(P-a_Z_01)=FEAT/POINT,CART,-34.649,45.381,30.48,0,0,1
MEAS/POINT,F(P-a_Z_01),1
ENDMES

F(P-a_Z_02)=FEAT/POINT,CART,-31.4,-47.829,30.48,0,0,1
MEAS/POINT,F(P-a_Z_02),1
ENDMES

F(P-a_Z_03)=FEAT/POINT,CART,56.97,-0.147,30.48,0,0,1
MEAS/POINT,F(P-a_Z_03),1
ENDMES

F(P-a_Z)=FEAT/PLANE,CART,-3.026,-0.865,30.48,0,0,1
CONST/PLANE,F(P-a_Z),BF,FA(P-a_Z_01),FA(P-a_Z_02),FA(P-a_Z_03)

F(P-a_Y)=FEAT/CIRCLE,INNER,CART,65.903,0,29.21,0,0,1,6.096
RMEAS/CIRCLE,F(P-a_Y),4,FA(P-a_Z)
ENDMES

F(P-a_XY)=FEAT/CIRCLE,OUTER,CART,-65.903,0,42.31,0,0,1,6.096
RMEAS/CIRCLE,F(P-a_XY),4,FA(P-a_Z)
ENDMES

The error about the "Pre-alignment" was when I`ve tried to import from .txt file, but after I`ve copy/pasted to .dms exported from PC-DMIS it was unable to convert back simple point declaration:

F(P-a_Z_01)=FEAT/POINT,CART,-34.649,45.381,30.48,0,0,1

[bfire85]

Might fall down to the naming convention of the features. If you named your features in Camio as "F(P-a_Z_01)" PC-DMIS might be having an issue with that thinking it is a function rather than a name. The rule of thumb with PC-DMIS is to use only letters, numbers, and underscores when naming features.

[vpt.se]

So... You're saying PC-DMIS cannot import its own DMIS-converted programs?

[AndersI]

It probably can, but there are at least three flavors of .dmi export (menu choices + code in a Basic file), and at least four of import (menu choices + Settings Editor), so matching them might be a problem...

[vpt.se]

That can explain the troubles then - thanks AndersI

[Peter Fuller]

This code is missing critical information. Primarily the units of the program but probably a few other things required to convert a program. PC-DMIS can't create a program if it doesn't know the units the program is measured in.

[Matthew D. Hoedeman]

Pcdmis is NOT (never has been, never will be) DMIS code. Pcdmis has functions and so forth that are NOT DIMS code, not handled by DMIS code, and no way to translate them into DMIS code.

[Peter Fuller]

I created a PC-DMIS program that was blank, exported it to DMIS to get the proper header information, wrapped your code in to that DMIS file with the proper end statement and was able to import your code. It appears that your issue is your DMIS code is incomplete and requires more information for it to be possible to be imported properly. Below is the sample code modified on my part to correct the import.

DMISMN/'autogen.dms'
V(1) = VFORM/ALL
DISPLY/TERM,V(1),PRINT,V(1),STOR,DMIS,V(1)
UNITS/MM,ANGDEC
D(STARTUP)=DATSET/MCS
MODE/MAN
    SNSET/APPRCH,6
    SNSET/RETRCT,6
FEDRAT/POSVEL,MPM,3000
TEXT/OPER,'Pre-alignment in MANUAL mode'

F(P-a_Z_01)=FEAT/POINT,CART,-34.649,45.381,30.48,0,0,1
MEAS/POINT,F(P-a_Z_01),1
ENDMES

F(P-a_Z_02)=FEAT/POINT,CART,-31.4,-47.829,30.48,0,0,1
MEAS/POINT,F(P-a_Z_02),1
ENDMES

F(P-a_Z_03)=FEAT/POINT,CART,56.97,-0.147,30.48,0,0,1
MEAS/POINT,F(P-a_Z_03),1
ENDMES

F(P-a_Z)=FEAT/PLANE,CART,-3.026,-0.865,30.48,0,0,1
CONST/PLANE,F(P-a_Z),BF,FA(P-a_Z_01),FA(P-a_Z_02),FA(P-a_Z_03)

F(P-a_Y)=FEAT/CIRCLE,INNER,CART,65.903,0,29.21,0,0,1,6.096
RMEAS/CIRCLE,F(P-a_Y),4,FA(P-a_Z)
ENDMES

F(P-a_XY)=FEAT/CIRCLE,OUTER,CART,-65.903,0,42.31,0,0,1,6.096
RMEAS/CIRCLE,F(P-a_XY),4,FA(P-a_Z)
ENDMES
ENDFIL

I then posted the same code back out of PC-DMIS and had no issues generating the post out.

$$ PC-DMIS Generated DMIS File
DMISMN/'autogen.dms'
V(1) = VFORM/ALL
DISPLY/TERM,V(1),PRINT,V(1),STOR,DMIS,V(1)
FILNAM/'autogen.dms'
UNITS/MM,ANGDEC
D(STARTUP)=DATSET/MCS
MODE/MAN
    SNSET/APPRCH,6
    SNSET/RETRCT,6
FEDRAT/POSVEL,MPM,3000
D(STARTUP)=DATSET/MCS
MODE/MAN
    SNSET/APPRCH,6
    SNSET/RETRCT,6
FEDRAT/POSVEL,MPM,3000000
$$ Pre-alignment in MANUAL mode
F(P-A_Z_01)=FEAT/POINT,CART,-34.65,45.38,30.48,0,0,1
MEAS/POINT,F(P-A_Z_01),1
    PTMEAS/CART,-34.65,45.38,30.48,0,0,1
ENDMES
F(P-A_Z_02)=FEAT/POINT,CART,-31.4,-47.83,30.48,0,0,1
MEAS/POINT,F(P-A_Z_02),1
    PTMEAS/CART,-31.4,-47.83,30.48,0,0,1
ENDMES
F(P-A_Z_03)=FEAT/POINT,CART,56.97,-0.15,30.48,0,0,1
MEAS/POINT,F(P-A_Z_03),1
    PTMEAS/CART,56.97,-0.15,30.48,0,0,1
ENDMES
F(P-A_Z)=FEAT/PLANE,CART,-3.03,-0.86,30.48,0,0,1
CONST/PLANE,F(P-A_Z),BF,FA(P-A_Z_01),FA(P-A_Z_02),FA(P-A_Z_03)
SNSET/DEPTH,0.000000
F(P-A_Y)=FEAT/CIRCLE,INNER,CART,65.9,0,29.21,0,0,1,6.1
RMEAS/CIRCLE,F(P-A_Y),0,FA(P-A_Z)
ENDMES
SNSET/DEPTH,0.000000
F(P-A_XY)=FEAT/CIRCLE,OUTER,CART,-65.9,0,42.31,0,0,1,6.1
RMEAS/CIRCLE,F(P-A_XY),0,FA(P-A_Z)
ENDMES
ENDFIL

[oleksandr]

I`ve added header and footer from program exported from PC-DMIS and stii soft crashes during the conveting process each time I try to import it. Is there any solution for this?

[Roberto]

We run both LK Camio and Hexagon Pc-dmis CMM. Always re-write the programs.
I'd strongly suggest you send an e-mail to the powers that be (your boss and the people who thought this was possible).