All Activity

@Kyle Johnson Ah I didn't even look at his picture, all I saw was "smallest‐enclosing" and immediately thought he wanted to enclose all of the outside points. Yes, max inscribed on the inside diameter is the the largest circle not containing any points, functioning like the largest pin gage fitting into a bore.

Nope just Segment,Segment,Segment. but they are grouped. so they say grouped segments or something. If I ungroup them it works fine which is the workaround.

I might be mistaken, but I don't think you can set an RDS angle for clearance data. Is your strategy set up as Clearance, segment, clearance, segment, clearance, segment in the strategy? Do you know if your clearance data has the "before, after, or before and after measurement" applied? Calypso may be confused on what RDS angle is applied to each specific clearance data, even though the segments have a specific angle.

@DWC Are you sure you don't mean maximum inscribed? https://portal.zeiss.com/knowledge-base?id=420544. "Maximum Inscribed" means it is the largest circle that does not contain any of the points. "Minimum circumscribed" means it is the smallest that contains all of the points.

For anyone that runs into this issue in the future, Shawn did create a ticket with our support team and I spoke with him. We found the issue was in the "inspset" file inside of the measurement plan folder. When we removed it, the issue did not occur again. Now, do not ask me what is wrong with that inspset file. If anyone runs into this and finds this thread, my recommendation is to use "save as" on the program, delete out the inspset from one of the programs and then go through the program (evaluation settings, formulas, etc) to make sure nothing changed. The inspset file doesn't control things like the strategy or the features themselves (that's in the inspection file), but it does have things like pre/post settings, names for output files and I think some evaluation settings in the features and characteristics.

Hello Marc, I'm glad to hear that you have a work around for now, but I would probably reach out to the hardware support team in your region. There might be something going on with the drives or something like that where it doesn't like going at full speed in that region. I highly doubt it is an issue inside of Calypso.

No the strategy is just 3 curve segments grouped together. No clearance distance, no extra moves. Should just retract and move to the clearance plane when its done. I copied the curve from another curve and modified it. I noticed it is going back to the angle from the previous curve so it must have something to do with that. I even completely deleted the strategies and remade them but it still does it.

Hi Štefan, in that case please reach out to your local support to check the parameters and the project. This kind of support for a concrete project is out of the scope of the forum I'm afraid. Nanno

Do you use a CMM position after the curve segment strategy? If you create a curve with the intended RDS angle, then later came back to add CMM position, I believe it uses the current RDS angle active on the CMM instead of feature's angle.

I have an issue with some grouped curve segments using the RDS/XXT sensor where at the end of the scan the RDS wants to change angles before it goes to the clearance plane. For the life of me I cannot see where the command to change angles is coming from. Has anyone ever encountered this?

@Marco Waibel Recall the points into a circle, and your evaluation of this recalled circle would be a minimum circumscribed element. This evaluation is the smallest circle that will encompass the three most extreme outside points. This is a functional diameter evaluation, like placing the smallest ring gauge over a shaft or outside diameter.

I am using helix path defined by thread with aid using self-centering option. Measuring threads were discussed many times with different strategies. Like line scan with many points and filtering and so on.

I would recall all of the points into a single (inside diameter) circle , and use the Outer Tangential evaluation

Hallo Marco, Du holst dir einen Kreis, und rufst die 6 Punkte in den Kreis zurück. Dies machst Du in dem du auf Sollwerteingabe gehst, dann Punkte-Rückruf. In dem darauf folgenden Fenster wählst du deine 6 Punkte aus deinen Gemessenen Kreisen aus. Bei deinen gemessenen Kreisen gehst du auf Pfad öffnen und wählst dort die Punkte aus die du benötigst. Hoffe du verstehst was ich meine. Gruß Jörg

That's why it's better to use the Calypso backup function for config migration. In the first few releases that had the backup function, the migration of the SQL db didn't work because it tried exactly that: copying the db files without stopping the SQL server first. And Calypso didn't even warn you about the failure. But in later releases they implemented a workaround: now all data gets exported to an external file which can be copied, and gets reimported when the backup is restored.

Hello everyone, i am depeloving a scanning path on external thread to extract axis by external tangential element. Making many measures I found that locking vectors on normal gave me more stable results. In which occasions do you use that ? Is it a good idea using that on a thread scanning path ? Thank you.

Hi Nanno, I don't know how to manually construct the point. I don't have any experience with this yet. Where do I then choose for the measuring principle to take into account the manually constructed point and curve? Thank you very much in advance for your help. Štefan

Just installed calypso 2025 on my offline seat. Set everything up... machine tabs, rotary table, etc... Lots of problems... 1) when opening program, work piece looks to be 6-7" into the machine. 2) Cannot probe the machine "plate surface" 3) trying to establish RT... if I open the base alignment and do a manual alignment, it flips the part about 105 degrees towards the back of the machine... if i just open then close and let the machine do it, it will flip the part 180 degrees (upside down). I have been doing the planner since 4.0 and never had this before. I contacted Zeiss but thought maybe someone has had this happen... Note all my machines are on 2020 with a RT01 and not an AB... I don't know if this is what causing the issues (can't see why because its virtual on planner)

Hi everyone, I’m using CALYPSO 2024 (7.8) and I have six circular scan paths. From each path I want to use one representative point, and from these six points I need CALYPSO to calculate the smallest possible circle that fits them. What’s the correct way to generate this smallest‐enclosing circle from just these 6 points in CALYPSO? Thanks for any help!

Hi, please check also if the flush prevents the second side to be found automatically. Adapt the flush (nominal) parameter to look for the side at the proper height Look for Flush (nominal) at ZEISS Quality Tech Guide for more information Cheers, Sergio

With your gom versione don't you have this problem?

Hallo Markus, ein direkter PCM-Befehl existiert dafür nicht. Du kannst z.B. die Datei "inspection_pre_start_dialog_pcm.txt" oder "inspection_post_load_pcm.txt" in den Prüfplanordner oder den Standardpfad für die Prüfpläne packen und den Code unten einfügen (auf eigene Gefahr!). protPath und ProtName musst du gegebenenfalls anpassen. Achtung: Die Zeilen mit removeAll löschen die bisher aktivierten Protokollkopfvariablen. Wenn dies nicht gewünscht ist, einfach auskommentieren. protPath="C:\Users\Public\Documents\Zeiss\CALYPSO\data\protocol header\" // Pfad zur Protokollkopfdatei protName="ProtocolHeader.xml" // Name der Protokollkopfdatei codeProt = "(t1 := '" + protPath + protName + "') readStream. " codeProt = codeProt + "t2:=Zeiss.Calypso.OMInspection active protocol protDefObj. " codeProt = codeProt + "t2 settings at: #multiProtOn put: true. " codeProt = codeProt + "t3:=#phParaFor_E. " codeProt = codeProt + "t4:=#phParaFor_R. " codeProt = codeProt + "(t2 settings at: t3) removeAll. " codeProt = codeProt + "(t2 settings at: t4) removeAll. " codeProt = codeProt + "([(XML.XMLParser on: t1 asFilename) " codeProt = codeProt + " validate: false; scanDocument] " codeProt = codeProt + " on: XML.MalformedSignal , OsInaccessibleError do: [:t10 | ^Zeiss.Calypso.OMProtHeadParameterSelection new parameterListNotReadable: t1]) root realElements " codeProt = codeProt + "do: [:t5 | | t6 | t5 tag type = 'Edit' " codeProt = codeProt + "ifTrue: [t6:=t3] " codeProt = codeProt + "ifFalse: [t5 tag type = 'CNC' " codeProt = codeProt + "ifTrue: [t6:=t4] " codeProt = codeProt + "ifFalse: [ ^Zeiss.Calypso.OMProtHeadParameterSelection new parameterListNotReadable: t1]]. " codeProt = codeProt + "(t2 settings at: t6) addAll: (t5 realElements collect: [:t7 | t7 elements first text asSymbol]) asOrderedCollection. ]. " codeProt = codeProt + "^0 " executeCode(codeProt) clearParameter("codeProt", "protPath", "protName")

Hi Štefan, please make sure to have side 1 and side 2 in separate parts in the project and try to use the measuring principle again. There are some rare cases, when the automatic creation of the base point on side 2 does not work. In this case please construct a base point manually on the same plane as the point you are using the measuring principle at and define it in the dialog. Easiest way is to use an edge point at side 1 and click the base point on a section, which is defined by the plane of the edge point side 1. When the measuring principle is applied to a curve, a manually constructed curve on side 2 may help analogous to the manual constructed point. If this workaround is necessary, it would be nice to have the sample data available for analysis. So please contact your local support and refer to this thread Get in touch with our team | ZEISS Industrial Quality Solutions Nanno

Hi, that is not possible. We can only group the measurement tables according to part or measurement attributes. This would be a new requirement, which you are welcome to publish on the ZEISS Portal

Hello Kyle, but this is the ZEISS Inspect area of the forum. Maybe somebody who have knowledge from Calypso and ZEISS Inspect read this question, too, but to my understanding you would increase the chance to get a good answer if you repost your question inside the Calypso->General forum. Best regards Christoph Schult