Scan to construct circle

Good morning all,

I’m struggling to get a circle produced from two half circles. I get a “measure maths failed” error come up. This is on 2017 CAD R1. Any ideas!

Hopefully I’ve attached a screenshot of the program segment.

NinjaBadger over 1 year ago

2d circle - check you have the correct workplane.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Henniger123 over 1 year ago

I typed in your values, there are no issues on my end

probably incorrect workplane as NinjaBadger sayed
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
vpt.se over 1 year ago

GC3_DAT_CIR_E only have two features, constructed circle needs three indata features.

CIR_15A.HIT[1], CIR_15A.HIT[2..CIR_15A.NUMHITS], CIR_16A.HIT[1..CIR_16A.NUMHITS] could work. Or just use CIR_17 which is the exact same construction...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Varthog over 1 year ago

My best guess would be workplane is not the right one
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
BKulpa over 1 year ago

Try making a point cloud feature from your partial circles and construct the final one from the point cloud.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Lost again over 1 year ago

Thank you folks. Must admit it worked originally. Made it into a subroutine and then didn’t like it.

Cir 17 & the GC3 DAT CIR E are just me trying two ways to get it work. I’ll check my work plane on Monday.

Have a great weekend.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Lost again over 1 year ago

So I’ve faffed again this morning. My workplane is fine. Restated it a couple of times to make sure but still doesn’t like it.

I produced a little program to test what I had and the scan and Cir 17 worked fine.

Pasted it back into my subroutine and it stops working. I’ve added a workplane directly above the scan just to be sure.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

vpt.se over 1 year ago

Are you passing the featurename to your subroutine?

CS1 =CALLSUB/CHANGE_THEO_X,:{PNT1},,
C1 =COMMENT/INPUT,NO,FULL SCREEN=NO,
Passed feature:
FEAT1
The current theo X is:
FEAT1.TX
Type a new theo X value:
ASSIGN/FEAT1.TX=C1.INPUT
COMMENT/OPER,NO,FULL SCREEN=NO,AUTO-CONTINUE=NO,OVC=NO,
"Feature updated to " + FEAT1.TX

From:
https://docs.hexagonmi.com/pcdmis/2022.2/en/helpcenter/mergedProjects/core/22_flow_topics/Passing_Arguments_into_a_Subroutine.htm

Lost again over 1 year ago

I’m not, but do I need to?
I’m asking this through ignorance.
I have a main program with an alignment. Main program opens my subroutine/sub program. Recalls the alignment then measure and reports all the features in the subroutine/sub program. Once it’s run it returns to the main program.

I thought I only needed to worry about the arguments if I’m taking variables from the main program into the subroutine and vice versa.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
vpt.se over 1 year ago

No, that sounds about right...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel