Opened the same program in 2016 and was able to manipulate the components independently, as normal. Made the necessary changes and reopened in 2017. I would call this a pretty major bug, as it renders the quick fixturing completely unusable.
Report it. I don't know if we're allowed to "do it" through the forum, but it is soo easy as the problem description already is here. I usually ping
Don Ruggieri for these tasks and hope that he is kind enough to file it for us. Would be good to have an official "sure, you guys can continue do that" though I know
cvelisetty and
Josh Carpenter are also solid for bug report filing.
I figured that Josh would eventually come through and see it. I guess that I'll file a report as well though.
*edit: Report not yet filed. Was typing at the same time as Don.
Hey
Josh Carpenter or
Don Ruggieri, when using the new SIZE feature, there are options for Any Cross Section or Specific Fixed Cross Section. How can I specify the fixed cross section location of a cylinder? Or I am interpreting this incorrectly?
Hey Josh Carpenter or Don Ruggieri, when using the new SIZE feature, there are options for Any Cross Section or Specific Fixed Cross Section. How can I specify the fixed cross section location of a cylinder? Or I am interpreting this incorrectly?
I think the key may be figuring out how to get PC-DMIS to display the rings of your cylinder instead of simply the cylinder. I have been wondering about this for some time.
has anyone tried running routines in 2017r1 with blank moves? ( MOVE/POINT,NORMAL,<,-0.6704,> ) Just had several cmm crashes where these move types seem to be driving to 'zero' instead of 'blank'.
So awhile back I learned this trick of leaving some of the fields blank in a MOVE/POINT, NORMAL.
I immediately did not trust it, even after my coworkers showed me that it worked (this was using 2013 MR1).
My gut feeling was that this trick was probably exploiting a loophole where Wilcox forgot to disallow blank fields like they do
everyotherfield.
And now it looks like they closed that loophole.
Best Practice = do not leave any fields blank.
The only time I have this issue is when there are Move Points in the program containing variables. Then PC-DMIS will sometimes fill in the blank axis in the Move Point with a number or another variable. I am using 2017 R1 with a program that has a Move point with the X,Y Axis blank with no issues on line during testing. But those blank axis Move Points are only used for collision testing in offline mode. I use these Blank Axis Move Points when I disable the Increment moves in my template. As Josh stated "Best Practice = do not leave any fields blank".
