All Activity

use minimum or maximum coordinates

D wouldn't affect anything in this case anyways, as Datum-B is already covering all the same constrains C-D projection is basically wrong, as you are changing a 3d (cylinder) geometry to a 2d (circle). a point instead of an axis go talk to engineering team and get them either to fix the call-out or explain the design intent my 2 cent

that worked, thank you very much for the help i just checked few other programs that run the same/similar codes in 6.8 and below and substr seems to be working on those version i personally don't know much coding and use whatever gives me the results 😅 your solution just saved my day and i am thankful

are fonts incorrect anywhere else on your PC? other software, Microsoft windows, etc...?

Ive been tasked with adding and subtracting dN from one another and the sum of the two dN must fall within a tolerance. So my question is with an hour or two of research already, how do you add or subtract dN of 2 surface points? Also adding a tolerance to it for the requirements. TIA

The RT moves, when I select the circle, in the location I desire. I then get invalid axis. I click on Rotary Table, under the measurement tab, and it snaps back to where it was. Changing the dimensions in that file does nothing either. I ended up just ignoring it, and moving on with what I needed to get done.

Hello, We encountered an odd issue on one of our workstations that operates Calypso that is connected to a CMM. One morning out of nowhere some of the text/font in our windows does not look like it should or does not look like all of the other workstations that we run Calypso on (3 online, 3 offline.) The issue primarily impacts the initial start window, the automatic stylus window, and a handful of other windows. I have tried changing the default font settings within the Calypso 'system settings: Environment' but it has no impact on correcting the issue regardless of whether we have "Calypso Standard" or "From System Settings" selected. I have also played around with the screen resolution, and a handful of other windows settings, but have run out of ideas as to how to fix the problem. I have even tried to install a different version of Calypso and the issue transfers over. If anyone has encountered the issue or may have any ideas on a system setting to change please let me know. The first two images below are what "normal" or what it "should" look like is. The second two images are the same windows from the problem machine. As you can see it is a bit of an issue in the automatic stylus changer window as the stylus names are covered up by the changer positions so you can't really tell what stylus system is in what position unless the operator is highly familiar with the systems and positions... "BAD/INCORRECT FONT/TEXT BELOW"

I haven't used Calypso 6.8, but I'm surprised sub string ever worked in this case. instead of D1=subStr(A,1,1) Try: D1=getParameterNamed(A,1) That should give you the first row of the list.

Normal vector should be axis angles ( A1, A2 ) - it forces calculations with fixed nominal angles of feature axis.

i have this program that was running on 6.8 version and now that we have upgraded to 7.8, i have nothing but issues with PCM i have a file that contains point coordinates (file is attached) i read the list A = readListFile(MS_Curve_Points_Temp) // read NX output then i use subStr to seperate teh lines into individual string that i can easily phrase D1 = subStr(A,1,1) this was working up until we upgraded, now i am getting an error can someone please tell what has happened and what can i do to address this issue i tried to convert "A" to text, but it didn't help Greeley appreciate all the help 🙂 13382673_10_fof_zeiss_20_ms_x_Temp.para

Is the FCF correct? Datum D doesn't constrain any new degrees of freedom. Maybe B-D as a common datum would work. The new GD&T engine has a checkbox for common datums.

How about Normal Vector, I am measuring a cone and am wondering what normal vector does so I can properly evaluate this feature.

Assign it a VAR ? e.g. CHR1 = strElement(1," ",getActual().identifier) , CHR2 = strElement(1," ",getActual().identifier) Then call CHR1 CHR2 at end as needed. Also if you have Calypso 2024 or later perhaps excel functions can help with generateTableColumn() I no longer have PCM license or I would dig deeper.

You can do that too! it's back to the "90's style tinkering" but if you close out CALYPSO, then navigate to C:\Program Files\Zeiss\CALYPSO 8.0\bin\CALYPSOFileDialog (or whichever calypso version you're using) there will be a CALYPSOFileDialog.exe. if you rename that executable to "testCALYPSOFileDialog.exe" or something similar, the next time you launch CALYPSO and click on Open Measurement Plan, then the windows file explorer will open, rather than the file dialog box. if I'm not mistaken, any time you upgrade to a new service pack, these steps will need to be re-conducted.

Is it placing the RT in the location of the circle you are creating? If so, you may need to change the values for the circle to better match where you want it on the table (Step 8).

Hi Michael - Unfortunately, still no updates.

Yes it does. But as Richard pointed out, in this case it's using the origin for its' calculations from the center of the plane, not the best-fit center of the bolt circle. If you simply offset the starting pointing point, you're still using a pre-defined starting point rather than the best-fit center of the bolt circle. Consequently, the offset method will tell you if the bolt holes are good themselves, but the nominals/actuals won't be an accurate representation of the best-fit.

I want to add the first few characters of each characteristic name (up to the first space character) to a column of the chr table file. I know that generateTableColumn() iterates through all the characteristics and calls a user-defined function for each of them. But how can I access the name of the currently processed characteristic from within that function? From the post settings of a characteristic I can get the substring I want with the following command: strElement(1," ",getActual().identifier) But of course this doesn't work anywhere else as getActual().identifier then no longer returns a valid name. In the end my code needs to run from an external PCM file, so I need a different way to get that characteristic name. Any ideas?

Great tip, thank you! How do I recall the lowest -Z point?

You can identify features too small to probe by scanning over the area and recalling the lowest -Z point from the scan as the location of your dimple. This strategy is taught in the Zeiss expert class specifically as a way to locate a clocking feature with an unknown orientation

I am not sure if there are any differences in UI of Calypso, but for nonmeasurable features you select it as "Theoretical feature" or if there is an feature, then use from construction menu ( offset plane, ... )

On new GD&T i can not do that. I believe it's either intersection C-D or your projection

Whether this is actually a major functional breakthrough...?? The main problems were performance, 3D models of all CMMs, 100% detection of all collisions, measurement range overshoot with RDS XXT, memory leaks, and a whole host of other issues. From Release notes of 8.0.16: 795786 In the CAD simulation, collision detection is now set to very high accuracy by default. 803828/809372 Curve with a turntable. In the CAD simulation, the turntable is rotating in the wrong direction 817080 CAD simulation. Contura G2 does not work directly with XXT. 818704 The wrong stylus is displayed in the CAD simulation. If a stylus system is present, it will be displayed; otherwise, the (stored) reference stylus system is displayed. 823312 URDF files and the faceting of the button simulation have been revised. The display and performance of the CAD simulation have been improved. 862756 The CAD simulation does not work properly if file paths contain special characters, such as the sharp S (ß). 863099 An incorrect position in the CAD simulation during the calculation of the measurement range in the Z-direction has been corrected. 867088 The Prismo 16/24/10 was not displayed correctly in the CAD simulation

Thanks!

.