2019 R2 issues

[MikeF]

just had 2019 r2 installed and now my programs won't run and my command mode lines are gone, I get improper argument, any ideas?

[JaredHess]

What do you mean by "my command mode lines are gone"? Do you mean the Edit window won't open in Command mode for your measurement routines (.prg files)?

[vpt.se]

Make sure you run it as administrator at least once after installation.

[SABarber]

Do you have the latest v2019R2 SP2? Sounds like an issue that was resolved when the PRG has nested groups. (PCD-176574).

[brian.freeman]

Never have I seen this before:

CIR_C1       =FEAT/CONTACT/CIRCLE/DEFAULT,CARTESIAN,IN,MAX_INSC
              THEO/<nan,nan,nan>,<-nan(ind),-nan(ind),-nan(ind)>,0.205
              ACTL/<0.005852,-9.035757,-2.264297>,<-0.999873,0.0152751,0.0045493>,0.209071
              TARG/<nan,nan,nan>,<-nan(ind),-nan(ind),-nan(ind)>
              START ANG=nan,END ANG=nan
              ANGLE VEC=<-nan(ind),-nan(ind),-nan(ind)>
              DIRECTION=CCW
              SHOW FEATURE PARAMETERS=NO
              SHOW CONTACT PARAMETERS=NO
CIR_C2       =FEAT/CONTACT/CIRCLE/DEFAULT,CARTESIAN,IN,MAX_INSC
              THEO/<nan,nan,nan>,<-nan(ind),-nan(ind),-nan(ind)>,0.205
              ACTL/<0.004276,-9.03797,-0.000054>,<-0.9999219,0.0124762,0.000678>,0.208071
              TARG/<nan,nan,nan>,<-nan(ind),-nan(ind),-nan(ind)>
              START ANG=nan,END ANG=nan
              ANGLE VEC=<-nan(ind),-nan(ind),-nan(ind)>
              DIRECTION=CCW
              SHOW FEATURE PARAMETERS=NO
              SHOW CONTACT PARAMETERS=NO
CIR_C3       =FEAT/CONTACT/CIRCLE/DEFAULT,CARTESIAN,IN,MAX_INSC
              THEO/<nan,nan,nan>,<-nan(ind),-nan(ind),-nan(ind)>,0.205
              ACTL/<0.006363,-0.0021,-2.267173>,<-0.9999469,-0.0079294,0.006576>,0.208891
              TARG/<nan,nan,nan>,<-nan(ind),-nan(ind),-nan(ind)>
              START ANG=nan,END ANG=nan
              ANGLE VEC=<-nan(ind),-nan(ind),-nan(ind)>
              DIRECTION=CCW
              SHOW FEATURE PARAMETERS=NO
              SHOW CONTACT PARAMETERS=NO
CIR_C4       =FEAT/CONTACT/CIRCLE/DEFAULT,CARTESIAN,IN,MAX_INSC
              THEO/<nan,nan,nan>,<-nan(ind),-nan(ind),-nan(ind)>,0.205
              ACTL/<0.00724,-0.000144,-0.00018>,<-0.9998819,-0.0145965,0.0048062>,0.20864
              TARG/<nan,nan,nan>,<-nan(ind),-nan(ind),-nan(ind)>
              START ANG=nan,END ANG=nan
              ANGLE VEC=<-nan(ind),-nan(ind),-nan(ind)>
              DIRECTION=CCW
              SHOW FEATURE PARAMETERS=NO
              SHOW CONTACT PARAMETERS=NO
DAT_C        =FEAT/SET,CARTESIAN
              THEO/<nan,nan,nan>,<-nan(ind),-nan(ind),-nan(ind)>
              ACTL/<0.005933,-4.518993,-1.132926>,<-0.9999993,0.0003501,0.0011589>
              CONSTR/SET,BASIC,CIR_C1,CIR_C2,CIR_C3,CIR_C4,,

[Randy P]

this is an old program opened in R2?
Try starting a new program and see how it works!
missing command lines, make the parameter from no to YES. see below
.
FORMAT/TEXT,OPTIONS, ,HEADINGS,SYMBOLS, ;NOM,TOL,MEAS,DEV,OUTTOL, ,
.
PNT1 =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
THEO/<289.306,730.984,657.829>,<0,1,0>
ACTL/<284.067,370.648,-632.662>,<-0.0003536,0.0046052,0.9999893>
TARG/<289.306,730.984,657.829>,<0,1,0>
REPORT VEC=<0,1,0>,UPDATE VEC=<0,0,1>
SHOW FEATURE PARAMETERS=YES <<<<<<<<<<<<<<<<<<
SHOW CONTACT PARAMETERS=YES <<<<<<<<<<<<<<<<<<
AVOIDANCE MOVE=BOTH,DISTANCE=10
SHOW HITS=NO

[brian.freeman]

@Randy P This program was initially programmed in 2014.1, brought in to 2019R2, Ran in off-line mode for verification, Ran on-line 2 times with product. No noticeable deviations from 2014.1 and 2019R2.
Had to run a new product, brought up the program and whamo corrupt program--Thank goodness I have a backup.
This program will not let me update any of the features. The rest of the program, after Datum A scan is the same as you see in the code.

CIR_C1       =FEAT/CONTACT/CIRCLE/DEFAULT,CARTESIAN,IN,LEAST_SQR
              THEO/<nan,nan,nan>,<-nan(ind),-nan(ind),-nan(ind)>,0.205
              ACTL/<0.004025,-9.033427,-2.263889>,<-0.999943,0.0078474,0.0072463>,0.206041
              TARG/<nan,nan,nan>,<-nan(ind),-nan(ind),-nan(ind)>
              START ANG=nan,END ANG=nan
              ANGLE VEC=<-nan(ind),-nan(ind),-nan(ind)>
              DIRECTION=CCW
              SHOW FEATURE PARAMETERS=YES
                VOID DETECTION=NO
                REMEASURE=NO
                SURFACE=THICKNESS_NONE,0
                MEASURE MODE=NOMINALS
                RMEAS=NONE,NONE,NONE
                AUTO WRIST=NO
                CIRCULAR MOVES=STRAIGHT
                GRAPHICAL ANALYSIS=NO
                FEATURE LOCATOR=NO,NO,""
              SHOW CONTACT PARAMETERS=YES
                NUMHITS=3,DEPTH=0.02,PITCH=0
                SAMPLE METHOD=SAMPLE_HITS
                SAMPLE HITS=3,SPACER=0.1
                AVOIDANCE MOVE=BOTH,DISTANCE=0.3
                FIND HOLE=DISABLED,ONERROR=NO,READ POS=NO
              SHOW HITS=YES
                HIT/BASIC,<nan,nan,nan>,<-nan(ind),nan,1>,<0.025034,-9.033806,-2.161018>
                HIT/BASIC,<nan,nan,nan>,<-nan(ind),nan,1>,<0.024375,-8.944367,-2.315545>
                HIT/BASIC,<nan,nan,nan>,<-nan(ind),nan,1>,<0.022726,-9.122816,-2.315504>
              ENDMEAS/

[Randy P]

I had a couple of 2014 programs that didn't come in right using R1. I just created a new program and copied the code and pasted to the new one. they ran fine

[sealevel]

Is the issue similar to this?

https://www.pcdmisforum.com/forum/pc-dmis-enterprise-metrology-software/pc-dmis-for-cmms/448429-nan?pp=448669

[MikeF]

I have uninstalled R2 and installed R1 and now everything works

[brian.freeman]

Found this out by accident:
Created a program in 'inches' but the drawing is metric. So dimensioned it, originally, in english, now converting the dimensions to metric. So when I 'clicked' in UNITS= IN to Change to MM. Nothing happens.
So I decided to create the dimension in MM, it still posts it in "IN".

 DIM DIST1= 2D DISTANCE FROM PLANE PLN_5 TO PLANE PLN_6 PAR TO   YAXIS,NO_RADIUS  UNITS=[COLOR=#FF0000]IN[/COLOR],$
  GRAPH=OFF  TEXT=OFF  MULT=10.00  OUTPUT=BOTH
  AX    NOMINAL       MEAS       +TOL       -TOL        DEV     OUTTOL
  M        1.594      1.593      0.030      0.030     -0.001      0.000 ----#-----
  DIM DIST1= 2D DISTANCE FROM PLANE PLN_5 TO PLANE PLN_6 PAR TO   YAXIS,NO_RADIUS  UNITS=[COLOR=#FF0000]MM[/COLOR],$
  GRAPH=OFF  TEXT=OFF  MULT=10.00  OUTPUT=BOTH
  AX    NOMINAL       MEAS       +TOL       -TOL        DEV     OUTTOL
  M        1.594      1.593      0.030      0.030     -0.001      0.000 ----#-----

MM.PNG

[brian.freeman]

Anybody come across this lately?
Auto feature dialog box doesn't 'represent' what is simulated on the screen.
IE: Should be 3 hits per row--1 Row = 3 hits
IS: 4 hits per row -- 3 rows = 12 hits

[KIRBSTER269]

I have, on a couple of programs, except I had like 50 to a 100 hits, couldn't really pin point the problem, except 1 out 3 computers the problem exist. When I put the same program on 2 other seats, (computers) it didn't show the same problem. I just assumed the 1 computer was weak. Probably don't answer your question, but that's all I got.

[RIDER]

In your example, you have Void Detection turned on. It will make auto features act wonky.

[brian.freeman]

@KIRBSTER269
Yes I have found that it randomly occurs, even on the same computer.

[KIRBSTER269]

Reason I say that is because some motherboards come with a generic video card built in, and even though you add a kickazz video card. DMIS will default to the built in one.

[brian.freeman]

@KIRBSTER269

OPENGL is NVIDIA386.07

[KIRBSTER269]

how much Video Memory? also you might want to go to NVIDIA.COM and update your software. How often do you update?

[AndersI]

Anybody come across this lately?
Auto feature dialog box doesn't 'represent' what is simulated on the screen.
IE: Should be 3 hits per row--1 Row = 3 hits
IS: 4 hits per row -- 3 rows = 12 hits

You have the "Void detect" button pushed down (9:th button from the left). This button effectively says "spread enough hits over the full CAD surface, taking your spacing and border avoidance into consideration" - very powerful in some circumstances, a nuisance in others.

[KIRBSTER269]

I was going to say that, but I knew in my situation, the void detect, On or Off did not make a difference. That would be the only reason I went down the video card road. I myself have never had extra or lacking hits from that button. Maybe screwy hits, but not the other.

[brian.freeman]

So the VOID Detect over-rides the Rows and hits? That could become a real pain. Thanks.
Also Have you seen this:
In the middle of programming; every once in a while, I get " You do not have a License. PC-DMIS cannot continue."

[neil.challinor]

If you're using an old Hasp (dongle) check your power save settings on the PC are not disabling the USB ports after a certain length of time.

[brian.freeman]

@neil.challinor.
Will check, but seems weird that it is happening while in the middle of programming.
Our IT department is upgrading our servers, since this is a dongle, it shouldn't be happening.

[neil.challinor]

It's the USB selective suspend under advanced power options that you need to check. Even if you are using the PC at the time they can still kick in if IT haven't disabled them.

power_save.JPG