All Activity

Thanks that's what i needed. How did you find the "gom.script" functions? the print(__doc_) just returns none for it

https://www.gdandtbasics.com/composite-position-vs-multiple-single-segment-tolerances/ I'm pretty sure ASME requires at least 1 datum for position. For example, a cylinder with a position to the bottim surface plane would essentially be an evaluation of perpendicularity.

To see which alignment corresponds to each index, simply type: print(gom.app.project.alignments[3]) (just change the index number). • Index 0 → always the original scan position • Index 1 → usually the pre-alignment • Index 2, 3, … → user-created alignments in the order they were created.

Hello Darci, for composite/Multiple Single Segment position, I recommend reviewing Faro.com's and GDandTbasics.com's material on this topic. I haven't seen them without datums however, so I can't help with that. Sorry!

Hi Justin! If I understood this simple script do exactly what you have to do. This is one way to do it. # -*- coding: utf-8 -*- import gom page_in_report=[] for page in gom.app.project.reports: print (page) page_in_report.append(page) gom.script.manage_alignment.set_alignment_active (cad_alignment=gom.app.project.alignments[2]) gom.script.report.update_report_page ( pages=page_in_report, used_alignments='current', used_digits='report', used_legends='report', used_stages='report', used_units='report')

Hi Nanno! My goal is to take the vector and the position in the 3dview of a dn label then create a normal deviation label in the same position of the dn label. Do you know the right way to do it?

I have a family of parts. The geometry is the same, but each P/N changes size in all axis. My base alignment uses (in-part) two angled planes to construct a symmetry plane for X Each of the parts, the two planes have a different angles and XZ coordinates. I have those variables in a para file for the first part. The problem is, I don't know the best way to move the points with PCM as the planes change. Do I have to have XYZ for each of the 4 points for each plane? Or is there a simpler way?

@DWC Since you are online at the moment, can I ask you another question? What does the composite tolerance mean? I am not very familiar with them either, and I am even more confused since there is no datum.

I posted here as well to get more eyes on it. I got my answer. Thanks.

@Darci Burch You are correct, this note is becoming much more common on engineered drawings. Usually it is something like, "Unless otherwise specified all features must have a surface profile within XXX". This is the author's catch-all note to control 100% of the part geometry. Unless you are using a CT (X-ray) or scanner based system, you cannot reasonably perform this measurement. Where I work, we do have a CT based system, and when I actually do select ALL of the surfaces and evaluate the profile (usually to itself), the results tend to surprise the customer because for the first time ever someone is checking this note in its entirety.

Hello Andrea Sacilotto, we are aware that the behavior you mentioned is occurring in SW2026. We are working on a solution that would be released with SW2026-SP1, which would enable you to again use all 64 logical processors of your machine.

Until recently, I have not seen many drawings with a profile callout. The ones that did have it were just one specific feature. Lately we have been getting a lot of new parts that have something like this as the only type of tolerance on the weldment or any of the components. I barely understand what this means, let alone how to check it. I only have Calypso...no curve or freeform or anything like that. All I can think is that I have to fully probe each individual surface and feature and make a profile dimension for each of them...but that isn't right either, is it? Because don't they have to all tie together somehow so it is the profile of the complete part? Also, CMM inspections on welded parts are not done during production. So the people welding want to know +/- target and I was told to just spit it in half (so +/- .060 in this case) but I don't know if that is actually correct.

I have 20 report pages that i need to change the active alignment from the align1 to align2using a script. Recording gave me the two lines below. Line 1 is activating the new updated alignment, Line 2 is editing the report page. gom.script.manage_alignment.set_alignment_active (cad_alignment=gom.app.project.alignments['Align2']) gom.script.sys.edit_creation_parameters (element=gom.app.project.reports['report 17']) I manually changed back to align 1 then trying to rerun this does nothing except staying open the edit creation parameters for the one page without changing the alignment. A second question is why in the recorded script does it identify my report page as 'report 17' when its actual page name is HOLES, i cannot find anywhere an identifier of report 17 Thanks for any assistance

How can i get it to display the cad model + stress and non stress area

Hi Jeffrey, are you sure about "positionCMM(z,-5)"? At least in Calypso 2024 that yields an "Parameter z is not defined" error

if you do that the value of "Plane_1" would be -0,095° because the rad() fuction expects an angle in degrees as an argument

if you want to define a variable, that gives your plane an angle: Plane_1 = rad(-5.51627)

Hi, fHbetaC (also fHalphaC) is defined in ISO 1328-1:2013-09. Sorry, I´m not allowed to share screenshots from standards, but if you have the ISO 1328-1:2013-09 have look into page 34 B.3.3. and formula B.2 A very good picture example is included in VDI/VDE 2612 Part 1:2024-12 on page 38. In the user manual of GEAR PRO you can search for "Nominal slope modification for profile and line". The topic is described very clearly there ...

Data is received and we are analyzing.

I was about to reply that im mistaken, gimme a minute :D

Many thanks!

Hey Clarke, you can declare an angle as "-5.5". You dont know in the moment of declaration if its in rad or degrees. If you take an angle from a feature you always get it in rad If you have a plane with an XY Angle of 180° degrees and you do: angle = getActual("Plane1").a1 The variable "angle" will have a value of 3,14rad. If you want that in degrees you need to do this angle1 = deg(getActual("Plane1").a1) In this case the value of "angle1" would be 180°

Hi Johnny, looks like I misunderstood. We are analysing this in a support ticket right now.

I'm forgetting the correct syntax for an angle. Here's what I have in my para file, but it's not working. I seem to remember that maybe "rad" belongs in there somewhere? Plane_1 = -5.51627

I'm forgetting the correct syntax for an angle. Here's what I have in my para file, but it's not working. I seem to remember that maybe "rad" belongs in there somewhere? Plane_1 = -5.51627