Some problems with 2019 R2 SP3

[JEFMAN]

I noticed some problems / bugs on V2019 R2 SP3 :

• After a basic scan / plane, the move to clear plane is not perp to the clear plane (if the clear plane is Z, the probe moves on xy of some mm, maybe the tip radius ?)
• The paste / pattern mirror Z worksas a ponctual symetry, not a plane symetry.
• the mirroring doesn't up dte the features contained in a feature set
• feature sets containing hits loose the bracket informations when close the prog (for example, a feature set with CIRC1.HIT[1..CIRC1.NUMHITS] become CIRC1)
• In a loop DO/UNTIL with a alignment inside, I usually assign the alignment name, and save the alignment at the end of the loop and recaal it at the start. In this version, it doesn't work, I have to recall directly the external alignment.

I will try the same on 2020 asap...

[Aaron Baldauf]

Regarding your first point. I don't think this is a new bug. I think this bug exists in nearly every version i used so far.
Mostly its not a problem but if you scan close to an obstacle in can crash. In these cases i just use move points before the clear plane.

[Cumofo]

I got off of 2019 R2 SP3 as fast as I could.
2020 R1 loads faster, and responds a lot better to scanning parameters. but i did get a crash to desktop this morning on my offline 2020 seat. I was copy/paste to notepad while the best fit alignment dialog box was open. Who knows? Im just glad to be out 2019, what a nightmare.

[zbailey]

My company is still using 2014, so ill gladly take these bugs over the crap we deal with on 2014 lol.

[zbailey]

Thanks for this, I am in process of trying to convert my facility over to 2019 from 2014. Medical stuff so validation is really slow, but 2014 is an absolute nightmare. Honestly not sure how an upgrade wasn't forced through long before I came here considering. All the bugs found helps me out a lot. From what I have seen we are still coming out ahead all things considered VS 2014 lol.

[vpt.se]

Don't miss the megathreads of reported issues (bugs and user-related) for 2018 and 2019. A lot in them can help you make an informed decision.

[zbailey]

Well at present we are on 2014 and its still got a lot of bugs. Even with the bugs 2019r2 has we will still ultimately be better off than we are with 2014 from all I can see. 2014 is such a dumpster fire of intermittent bugs and crap that you cant really plan for until they kick you right in the throat.

[JEFMAN]

I noticed some problems / bugs on V2019 R2 SP3 :

• After a basic scan / plane, the move to clear plane is not perp to the clear plane (if the clear plane is Z, the probe moves on xy of some mm, maybe the tip radius ?)
• The paste / pattern mirror Z worksas a ponctual symetry, not a plane symetry.
• the mirroring doesn't up dte the features contained in a feature set
• feature sets containing hits loose the bracket informations when close the prog (for example, a feature set with CIRC1.HIT[1..CIRC1.NUMHITS] become CIRC1)
• In a loop DO/UNTIL with a alignment inside, I usually assign the alignment name, and save the alignment at the end of the loop and recaal it at the start. In this version, it doesn't work, I have to recall directly the external alignment.

I will try the same on 2020 asap...

This (in red) re-appears in 2020 R1 SP12 (and maybe in some others ?)
Don Ruggieri
neil.challinor Peter Fuller


Maybe implementing davehocum 's code ?

https://www.pcdmisforum.com/forum/pc-dmis-enterprise-metrology-software/tips-tricks/496613-more-generic-function-example

[Don Ruggieri]

Did this problems all work prior to 2019 R2 SP3?

Unfortunately, "red" did not come through. Which problems persist in 2020 R1 SP12?

Do they also fail in 2021.2 Technical Preview?

I am especially interested in that last one, saving and recalling alignments. I do that frequently in loops. Can you share code to show the way you do it?

[JEFMAN]

Don Ruggieri :

• feature sets containing hits loose the bracket informations when close the prog (for example, a feature set with CIRC1.HIT[1..CIRC1.NUMHITS] become CIRC1)

sorry, I didn't check the color...

[DAN_M]

Don Ruggieri :

• feature sets containing hits loose the bracket informations when close the prog (for example, a feature set with CIRC1.HIT[1..CIRC1.NUMHITS] become CIRC1)

sorry, I didn't check the color...

this sounds like a nice enhancement

[neil.challinor]

I tested using the most recent service packs of 2019 r2, 2020 R1, 2020 R2, 2021.1 and 2021.2 and I do not see this problem.

[Don Ruggieri]

I tested again, created my own loop with saving and recalling an alignment and it works fine in 2021.2, as with previous versions. Can you share some specifics?