Resulting Element Creation

[[Aj...]]

Hello everyone,

I am trying to automate a measurement process on a prismatic part. I have a curve which runs around the circumference of the whole part. I want to first cut this curve with a plane. With the resulting intersection points I want to construct a circle. I have carried out this process and recorded it, and the script works. The problem that I have is that the points (probably around 200) appear in the measurement plan, in the explorer. Is it possible that the process of intersection points takes place in the background, without creation of the elements, so that only the circle gets created as an element and is available in the explorer? Every time I create a resulting element I have to go through a number of construction steps. The idea is that the construction steps take place in the background (in the code), so that only the resulting element which is used for further measurement is available to be measured.

Thanks,

Ajay

[[Ma...]]

Hi Ajay,

I just aked a colleague who mentioned that a "Collective Section Curve" (Operations->Section->Collective Section->Collective Section Curve) might help to create a single element instead of a large number of elements.

Best regards,

Matthias 

[[Aj...]]

Hi Matthias,

Thanks for your reply. I was unaware of this method. I am actually also looking for a way to create other elements, such as points and lines in the background. Lets say I have a plane and I intersect it with eight other elements resulting in eight intersection points. Then I create a circle by selecting the eight points. In the program I would then have a plane, 8 points and a circle. The number of elements keeps increasing exponentially, as many elements that I have. To solve this, I want all this to be done in the background using the code, such that only the circle is created as an element in the end.

Thanks,

Ajay

[[Ma...]]

Hi Ajay,

It is not possible to create any elements without adding them to the explorer, but you can

• Hide elements from the 3D view
• Collapse/expand parts of the Element Explorer
• Delete elements which are no longer needed
• Create Element Group might help to order your elements

Maybe you find some useful hints in Selecting elements in scripts — App Development Documentation.

Best regards,

Matthias

 

[[Na...]]

Hi,

maybe a point cloud from Section-Element Intersection Points (https://techguide.zeiss.com/en/zeiss-inspect-2025/article/cmd_pointcloud_create_by_intersecting_section_element.html) works for you? The intersection points result in one element and can be used as the selection for fitting elements.

Nanno

[[Aj...]]

Thanks Matthias and Nanno,

 

Please sign in to view this username.

: I think I have come to the same conclusion. I dont think it is possible to evaluate elements that have not yet been created

Please sign in to view this username.

: Thanks for the suggestion. I am familiar with the point cloud concept. My hope was that I am able to "create" elements in the code which are solely used for evaluation, or further construction. For example in the concept of Measuring principle - Touch Sphere (Tastkugel), with two contacting points as the setting, the software creates an internal plane and a line along which the nominal sphere is guided, until it contacts the actual mesh at two points. So in this procedure, there is a plane, a line (a direction) and two points involved. These elements are not actually created rather mathematically exist for the creation of the actual sphere. I hoped that something like this would also be possible using scripting. The concept with the points in my original question was just an example.