hexagon logo

Single Hit Circle - behavioral change

I am having issues with Single Hit Circles. Long story short: new employer, new absolute arm, fresh round of training. I had been through training in the past and have worked with Romers for over three years but the training at this new company was intended more to benefit others in my department. Anyways, only since the training, my Single Hit Circles have been mis-behaving. The parts I check have many perforations and small holes that I don't need to check form on, just many different distance checks, hence Single Hit is very quick and easy for this need.

Quick Start Method: I measure a PLN then select CIR with one hit and specify the feature as PLN1 rather than Workplane. When I take a hit, I get "HIT 1 OUT OF RANGE".

Auto Circle Method: I set the Sample Hits to "3" and the Circle Hits to "1". When I take the initial points, everything works out fine. I hit "Create", a circle is made, and shows in Graphics. The diameter of the probed Circle is exactly the Nominal I keyed in at the Auto Circle window, not an Actual result. Now, when I go back and Execute Program or Execute Feature, all goes well throughout the Sample Hits. The moment I trigger the Single Hit for the Circle, it disappears from the Graphics window. When I confirm the Hit and review my results in Command Mode, the Diameter shows as "0". The Graphics window still shows the CIR1 ID Tag but it points to open space. The Distance measurements from this invisible circle are also out of whack.

I couldn't find this exact problem in any other Thread. One came close but never got fully answered. I already checked my preferences...."Any order execute tolerance" is set to "0". Ruled that out. Also, the Ruby is definitely passing through the feature PLN established. I am wondering if some simple toggle command or setting has been changed during the normal course of training and I simply need to change it back? I am awaiting contact from Tech Support of the company we bought the machine from. I have not yet tried Hexagon.

Machine Info: Absolute with PC DMIS portable CAD 2013 MR1
Parents
  • If you F9 your LoadProbe statement, you can use the Edit button and check to see if PCDMIS has changed the calculated size of your tip. This is a known 2013 bug. The graphic of the probe isn't impacted by this value, it's defined somewhere else. So, you can have a normal-looking probe that has had the calibrated size changed.

    Recommend update to 2014 asap.
Reply
  • If you F9 your LoadProbe statement, you can use the Edit button and check to see if PCDMIS has changed the calculated size of your tip. This is a known 2013 bug. The graphic of the probe isn't impacted by this value, it's defined somewhere else. So, you can have a normal-looking probe that has had the calibrated size changed.

    Recommend update to 2014 asap.
Children
No Data