2019 R1 (SPx) issues

[vpt.se]

Starting a new thread listing issues found in PC-DMIS 2019 R1 (SPx).

Each issue will be listed per post, not several in one post.

I will not be hiding issues that is caused by user error either.


Idea is to revisit my 2018 thread and move through the issues reported there - if and when I can find the time:
https://www.pcdmisforum.com/forum/pc...18-r2-released

General thoughts on 2019 R1 SP1:

- Seems more volatile (prone to crashing) than 2019 R1
- Needs quite a bit more time to "think" when a scan has been completed

General thoughts on 2019 R1 SP2:

- More stable than SP1
- Laser workarea is never animated, does not update the position of the probe unless you change the probedensity/stripewidth.
- Laser workarea displays intermittently (not always)

General thoughts on 2019 R1 SP3:

- Much, much slower in general, particularly if you have pointclouds - worse than any previous 2019 version
- If you have the status window active, it affects speed negatively - worse than any previous 2019 version
- Almost every "thinking" or "processing" (hourglass) sets PC-DMIS into Not Responding mode almost immediately (first time I have seen this with PC-DMIS)


"Major" issues (calculation errors, etc.):

- Impossible to use UPR filter above 1000, also UPR filtering non-functional in autofeatures:
https://www.pcdmisforum.com/forum/pc...213#post449213

- Outlier removal filter in autofeatures does not work, filtering not performed:
https://www.pcdmisforum.com/forum/pc...318#post449318

[vpt.se]

PC-DMIS 2019 R1 SP1

Feature sets are not selectable in datum definition dialog PCD-163766

Feature sets does not display in the list of selectable features.

Workaround: Do a DATDEF directly in the command (text mode) window.

EDIT: Verified fixed as advertised in build 375 (SP2 release).

[Don Ruggieri]

This is fixed in 2019 R1 SP2 with build #375

[vpt.se]

PC-DMIS 2019 R1 SP1

Analysis view with grid=on shows wrong values and grid labels cannot be moved? PCD-157107

Just made an analysis view of a profile of any line (form) and enabled the grid:
analysis profileform.JPG

- I haven't been able to figure out how to move the axis labels, seems to me they cannot be positioned
- The left axis shows a max of 3.8 and a min of -3.6, but of what? My max and min are 0.0407 and -0.0328...
- Changing to manual axis values does not help, actually nothing changes at all...

[AndersI]

Did you have an arrow multiplier of 100? If so, the 3.8 and -3.6 seem [almost] consistent with the *displayed length* of the arrows (snapped to the grid?)...

[vpt.se]

Yes, the multiplier might have been set at 100, however the multiplier isn't displayed in the grid view or is hidden behind the other labels, so it would be an essential thing to display...

[Don Ruggieri]

This is fixed in 2019 R2

[vpt.se]

PC-DMIS 2019 R1 SP1

Point cloud selection does not show up in the feature selection list for Xact Measure profile

I have two scans and two point cloud selections. When doing an Xact Measure profile evaluation, the point cloud selections does not show up in the feature list:

Capture1.JPG

However, if I click on SCN3, the point cloud selections show up:

Capture2.JPG

And are selectable:

Capture3.JPG

- If this is by design, I'd really like to have a [+] sign next to the parent feature so I know that the feature contains subitems.

[vpt.se]

PC-DMIS 2019 R1 SP1

Deleting a defined datum marks the datum red in FCF's but cannot be removed through the XactMeasure FCF dialog

I defined three datums for this test (three machine coordinate system planes) and made sure I had some circles to do a TP on:

fcf1.JPG

Nothing strange here. Command shows the same datums as the FCF.
Click OK to close the dialog.
Now, remove the DATDEF for datum Z, PC-DMIS will complain that there are evaluations using this datum. I chose to remove the datum regardless.
The command should display Z in red.
F9 the FCF:

fcf2.JPG

The command lists Z in red, the FCF does not display datum Z. Even if I click OK here, datum Z will not be removed from the command.
I can even remove datum Y through the FCF dialog (not the actual DATDEF) and datum Z will still be in the command:

fcf3.JPG

Removed datum Y from the FCF through the dailog, but Z remains in the command.
There is no way to remove a deleted datum from FCF's that have already been created through the XactMeasure dialog.

Workaround: Simply delete the datum from the FCF command in text/command mode.

fcf4.JPG

[vpt.se]

PC-DMIS 2019 R1 SP1

Dimension colors does not display correctly when using "display lower tolerance as negative" is enabled PCD-162876

When using GRAPH=ON this can display deviation arrows that are within tolerance to actually display the color for out of tolerance and deviation arrows that are out of tolerance can be displayed as the color for within tolerance.

[vpt.se]

PC-DMIS 2019 R1 SP1

Graphics display window does not update immediately as it has in previous versions

Rightclick a label in the graphics display window and choose "hide". The label does not hide until you manually refreshes the graphics display window or zoom/pans it.

EDIT: Updating the graphics drivers fixed it.

EDIT2: Not quite fixed, however this occurs only on one of our installations so I will flag this as a local issue...

EDIT3: Updated to the newest Quadro drivers, did not fix the issue. Starting to think that it may have something to do with me running all three sensors (probe, vision, laser) and that these tabs does not play nice together.

[mbatten]

It still does this to me even after I updated the graphics drivers. I think it might have more to do with my 4k monitor, though.

[vpt.se]

Well, there is something peculiar going on with the graphics window for sure. Updating drivers did not help.

[vpt.se]

Updated again, no remedy.

[vpt.se]

PC-DMIS 2019 R1 SP1

Audio cues/sound cues for "feature complete/ended" plays when a wrist/angle change is placed directly after a feature PCD-164331

- Manual mode
- Measure a feature
- Make a wrist/angle change
- Measure a feature

When executing the program above, the execution is like below:

- Feature to measured
- Dialog for wrist change
- Confirm wrist/angle change
- Audio cue for "feature complete" is played (?)
- Wrist/angle changes
- Feature to measure

Tested a program that just had wrist/angle changes (no features) and the sound cue did not play after wrist change, so it seems connected to feature+wrist change.

[AndersI]

If you don't have any features, I doubt the wrist changes are executed - I believe they are postponed until that tip is actually needed (MOVE or MEAS).

[vpt.se]

Yes, that is correct, it just changed the previous (first) wrist change to whatever I chose, no new wrist change were added to the program. I mitigated that by putting MOVE points between each wrist change. I used this method to test the thesis above (in MAN mode).

[vpt.se]

PC-DMIS 2019 R1 SP1

CMM live execution does not match graphical indicators for start/stop angle in autofeatures PCD-164332

- Adaptive helix spiral scanning of internal diameter
- I adjust my start/stop angles until the graphical indicators (arrows) are placed as I want (see picture)
- Execute the scan

Capture.JPG

CMM should start at the purple arrow and scan clockwise up until the yellow arrow.
However, the CMM stops prematurely, at the grey circle (probe stem from above) not completing the full scan as indicated by the arrows.

[vpt.se]

PC-DMIS 2019 R1 SP1

Selected scanning strategy doesn't always display in the graphic window, instead the default strategy is shown (wrong)

- Autocircle/cylinder with any adaptive scanning strategy than the default
- Make sure you see the correct adaptive strategy is displayed in the graphics window
- Click OK to create the feature
- F9 it and the default strategy is displayed instead of the selected adaptive one

There may be a difference in how/when the default strategy is displayed. I tested with an autocylinder without measured data and the default strategy was shown on F9. After the feature was measured, I F9'd it again and the selected adaptive scanning strategy was displayed correctly in the graphics window.

[Don Ruggieri]

We are not able to reproduce this one: We've created measurement routines with all the strategies and followed the instructions, Please provide more details such as any specific measurement strategy

[vpt.se]

Tried to trigger it but it worked as expected.

Will add info next time it occurs.

[vpt.se]

PC-DMIS 2019 R1 SP1

When an autofeature dialog is opened, the graphic display does not show the probes true position neither does it update the position of the probe if you run the machine manually (positioning the probe) PCD-164330

Sometimes, I like to position the probe where I want the autofeature to be measured and then position the depth, offset etc. in the autofeature dialog to match the probe position. This no longer works and haven't done so since a couple of versions back. This is a real QoL setback.

[Orizon-STL]

My custom header won't work in 2019 r1. I have a custom "FILE_HEADER.LBL" that I copy into the Reporting folder and this has worked every time I update to a new version. But, this time, it did not work. Any suggestions?

[vpt.se]

I do this too, worked fine here. If you replace the FILE_HEADER.LBL while PC-DMIS is open, you will need to refresh the report or restart PC-DMIS.

[bfire85]

My custom header won't work in 2019 r1. I have a custom "FILE_HEADER.LBL" that I copy into the Reporting folder and this has worked every time I update to a new version. But, this time, it did not work. Any suggestions?

Try opening your file header label in 2019 and save over your original with 2019 schema.

[vpt.se]

PC-DMIS 2019 R1 SP2

Checking the checkbox for "RN" when evaluating position in XactMeasure does not display the "RN" on the report PCD-165692.

Created a TP with holes in an already existing program, checked the "RN" box in the "Nominals" tab and added tolerance. "RN" does not display in the report.

EDIT: Added screenshots.

Edit window (tried English language to see if that made any difference):

editwin.JPG

Report window:
reportwin.JPG

[Don Ruggieri]

I know this sounds simple but our first tests did not expose this issue. Can you prove a screen capture of the edit window and the report showing these areas please?

[vpt.se]

Uploaded screenshots.

[mbatten]

I've run 2019 R1 and 2018 R1 and the only time I've seen PC-DMIS do this correctly is when there was only one circle being reported.

[vpt.se]

PC-DMIS 2019 R1 SP2

Command missing a comma separating the options for TP FCF - possible future serialization errors when fixed? PCD-165335

- Running swedish language
- Noticed a comma was missing in the TP FCF separating the options

Capture.JPG

It should say

TOLERANSREKTANGEL/VISANOM=NEJ[COLOR=#FF0000][SIZE=14px][B],[/B][/SIZE] [/COLOR]VISA PARAMETRAR=JA

but says

TOLERANSREKTANGEL/VISANOM=NEJVISA PARAMETRAR=JA

[SABarber]

This should not be a serialization issue. This is a visual text for humans.
Just a note that I think this happens in all languages.

[Don Ruggieri]

checking on both of these. . . .

[vpt.se]

Thanks, guys!