Jumping from 3.7 to 2019

[JEFMAN]

What do you guys think about it ? (that's not for me...).
I've been told that some functions of the old good release doesn't exist anymore in the new one ?

Is it necessary passing through 2010MR3 to avoid problems of PCDRLN.INI ?

Any advice would be welcome

[Matthew D. Hoedeman]

I have no problem going from V3.7 to 2016. I write in V3.7, do most of the executions in 2016. Only 'thing' is round/square slots change direction by 180 degrees, but then I pretty much only use VECTOR, SURFACE, EDGE, CIRCLE, SLOT features.

[bfire85]

Live dangerously! However...backup backup backup!

[Matthew D. Hoedeman]

Live dangerously! However...backup backup backup!

Don't try to scare him, works just fine......

[bfire85]

Don't try to scare him, works just fine......

I am sure most everything works fine. I think the biggest jump I have done was from 2011 to 2013.

[NinjaBadger]

No doubt there will be some issues, but (as much as I know 3.7 was good) I think there's enough enhancements in the later versions (as well as compatibility with newer OS and a more powerful PC etc to make it worth it.


I'd recreate probe files from scratch (had issues updating before from 4.2 to 2009) and things like angles will all need revising.

[AndersI]

"Angle between" has been changed during the years, but I believe PC-DMIS pops up a warning that you may have to edit those commands.

I believe there has been some changes in cylinders too, which could cause trouble for a program that wasn't correctly written, but worked anyway in the old version(s).

[KIRBSTER269]

Don't worry JEFMAN It's like jumping into a small puddle and getting your feet wet.

tenor[1].gif

Well, the PC-DMIS way, anyways

[Sora5]

The biggest upgrade for me was from 2012 to 2018. Ran across a major bug that I'm still trying to work around that forced me to downgrade to 2016 and put 2018 on hold. Basically any Xact diametric position made in a 2012 program will lose the diametric symbol and report wrongly when opened in 2018. I did a few test and found after I opened in 2018, I had to F9 all the diametric position dimensions and recreate them to get the ø back. I reported this bug a while back, but haven't tested any 2019 versions so I don't know if this is fixed or not. I'm working on a script to open and save as my 1000+ 2012 programs in PCDMIS 2016, then save as again as 2018.

[Ncogneto]

Don't try to scare him, works just fine......

https://www.pcdmisforum.com/forum/pc-dmis-enterprise-metrology-software/pc-dmis-for-cmms/448108-2019-r1-spx-issues