ISSUE 1 v2011

[DeWain Hodge]

I have a program that I have been using for a while in v2009. This program has three parts in a fixture that loops from part 1-3 moving Y 3.25" in every loop. I just upgraded to v2011 this weekend and now all the move points are messed up. Instead of moving to avoid the fixture it keeps moving and hitting the fixture. I stepped thru the program and all the move point are showing the correct coord. I went back to v2009 and used my back up and everything seems to be running fine. Anyone know whats up with move points in v2011?

[cmccullough]

What type of move command are you using MOVE/POINT or /INCREMENT??

[Ironhoe]

Ive seen the move/increment go completely to H3LL in the 2010/2011 versions after migration. No explanation. There is something evil lurking in 2010/2011 and I suspect it's partially in the tool kit, but I can't prove it out since my issues have been quite random.

[cmccullough]

They had added more parameters to the move command. Thats why some users may have some migration issues.

[DeWain Hodge]

All I ever use are either move point or clearplanes.

[corelex]

<sigh> Oh, man... <sigh>

Sorry, DeWain Hodge I am just sad I can not understand this at all. Programs from old versions should work, but not in PCDMIS. There is always something.
Just now I have some other problems getting my program to work in 2009ver. Program ran and worked in 4.3 and not just offline like I think (this is just MO ) the Wilcox is doing the tests for PCDMIS.


<sigh>

[cmccullough]

ClearPlanes you should be okay, but move point might be your issue. They have added a third parameter to move/point. It use to be MOVE/POINT,NORMAL,<XX.XXX,YY.YYY,ZZ.ZZZ> now its MOVE/POINT,NORMAL,[COORDSYS],<XX.XXX,YY.YYY,ZZ.ZZZ>

[COORDSYS] can be PART or MACHINE.

I mostly use ClearPlanes and MOVE/INCREMENT.

[JEFMAN]

Nice enhancement, thanks to had find it, cmccullough !
Maybe there's a new parameter in the setting editor that give you a default choice between CMM and part ?

[Chally72]

When I encounter movepoints or features that do not move where they say they do- I export the program in Basic and look at all of the code/numbers there. You'll be able to pick out corrupt movepoints and other things.

[LOBBS]

Nice enhancement, thanks to had find it, cmccullough !
Maybe there's a new parameter in the setting editor that give you a default choice between CMM and part ?

Has anyone confirmed if there is a parameter that controls this in the settings editor? I use Move To.. commands almost exclusively. If it doesn't default to PART in the [COORDSYS] when the programs are migrated into 2011 I cannot see how we'd be able to move to 2011. We'd have way too many programs to fix to make it worth our while.