All Activity

Hi @Tom Prophet The solution to your issue is a setting in windows, not Calypso. To fix this: Go to the computer you mentioned that opens the image in Paint. Right click on any image file that has the same extension as the one you use for part setup instructions (usually this is either a .jpg or .png file). Then, click the "change" button to assign a different default app.

I agree.

Thank you much...

@Tom Prophet Go to the file location of your image. Right click the image, go down to properties. In the window that opens, you will see "Type of File:" and directly underneath that "Opens with:". Click the Change button, and select the preferred app (Microsoft Photos App?).

That file type is probably associated with Paint on that PC. Just set it back to the normal picture application.

Hi all, I'm new to Calypso software and I'm running 3 CMMs with 2025 software. On one of the CMMs, when I pull up my picture of the part set up, it pulls up in paint rather than jpeg. It only happens on 1 of the 3. I don't know why but that's what is happening. Is there a setting somewhere within calypso software that is not set? Thanks for any suggestions

So this is a funny situation. It's not wrong but could lead to trouble. Datum C provides only clocking. All of the other 5 DOF are constrained. Datum C remember is NOT the hole itself. Its DFS will be a best fit pin mutually parallel to B and perpendicular to A. Whatever size that best fit pin is when constrained for orientation, its CL is the clocking datum. You could start this hole perfectly on position but if the drill walks and the hole isn't perpendicular to A, I suspect an evaluation of TP with C tertiary would yield different results than the same evaluation with no tertiary. It is possible to have the C feature machined OOT for TP using C as tertiary because DFS's have perfect form and orientation while your feature will not.

Circle3 and Circle9 were not measured at the same Y position. Therefore, they cannot be compared.

Cleaning and Re-qualifying would be what I would start with. Are both scans being done with the same scanning settings?

Perhaps it's looking into new location ( new instalation ). Remember path from "Calypso x.x" and go back to "C:\Users\Public\Documents\Zeiss" and there should be more than one "Calypso" folder

I would start with calibration. If there is same problem even after calibration, then i don't know.

Dear Expertise, I need your support regarding an issue I am currently facing. There is a significant measurement variance between two different probes: Short probe – Ø3 length 85 mm Long probe – Ø5 length 125 mm The measurement differences are quite large even though the alignment remains the same. We are using an RDS with a VAST XXT rotating probe system. Could anyone please advise how to eliminate this error? As below measurement table for your referance. Feature Circle3 (short) Circle9 (long) Difference (short - long) X actual (mm) -0.02173 -0.01202 0.00971 Z actual (mm) -0.02633 -0.01052 0.01685

Recently installed Calypso 2025 with SMA and I'm trying to convert my .dfm piweb databases to .dfs. When I went to look for ConvertPiWebDatabases in the start menu, it was not there. Am I looking in the wrong place? That is where the user guide is saying to look.

I must admit - this is a confusing one. I think this is wrong. TP of datum A is not giving me much sense. Then TP of 4xø.405 is not giving me much sense in a way how both rows are same, just with different tolerance. Also datum A is small to have it as proper cylinder and control their location. For TP of 4xø.405 - .030 tolerance would be pattern and .015 would be individual ones, but i have no experience in composite TP. I would be glad if main datum would be plane (3.946) and then circle as datum B ( previously datum A )

I am SOO glad you posted this!! About 2 years ago, during calibration the tech broke the lock on our RDS head and told me that because of that, this error would pop up and it was just to flag me to verify that the lights were green on the RDS, and if they were, to go ahead and hit OK. So that is what I did, and there were no issues. We ended up getting the RDS replaced several months later and I thought the message would go away but it did not. I have since asked a couple of people from Zeiss about it and neither of them couple figure out where the error message was coming from or how to turn it off. I tried your solution and I found that I also had linescan selected even though we don't have one. Now the error is gone, and it seems it had absolutely nothing to do with what I was originally told it was for! So thank you!

I have several questions about the position callouts in the attached print. I have no idea how to tell the CMM what I need here. 1) The position callout on the .563 hole (item 3) does not have a datum. I assume it must be referring to the 1.009 and 2.880 locations from the sides, correct? So I should use those two edges as my datums when I set it up? 2) The composite tolerance on the bottom (items 10 and 11) only lists datum A, which is the hole from question 1. I don't have the CAD model, but I assume if I get it, it will pull in the correct nominals. Wouldn't it need to consider all 3 directions (X, Y, and Z)? I have never done position with more than 2 directions. Is that even possible? Would I have to do the holes as cylinders? Or would I scan the holes and project them to the faces? If projecting to the faces, would I use the inner or outer faces since the material thickness could vary? For the top line, I believe I would have a separate position characteristic for each hole within .030(M), as that is how I would do a regular position. For the bottom line, my understanding is that would control the position of each of the 4 holes to each other. I am confused because I thought the bottom line was supposed to have less datums, but both lines only have datum A. If the bottom line is controlling the holes to each other, what does datum A have to do with it? How do I make the characteristic(s) for the bottom line? Is there a singular characteristic that takes care of the whole pattern or would that need to be separate for each hole as well?

@Jason Barry Everyone can make a mistake - so was I when not considering base dimension from A as you did - thanks. And in your answer you are right - it would be 0.100 if any of a measured and filtered point would be 0.05 away from base dimension. @RPSmetrologyTech i think if that dimension is not as base then different distance from A should not make any difference in profile result. At least i hope 🙂

Having the same issue...any update on how to fix this?

@Krish Madhu Did you select the Characteristics.xlt when setting up your Excel output? If you want to compile many Calypso XLS files into one easy to copy and paste XLSX block, use the following PowerShell script to do that instead of trying to do anything with the Zeiss macro enabled template. It is important to note the naming convention of your files (with incremental part number) needs to be something like _001, _002, _003...._010, _011, _012 etc so when the script sorts by ascending, you don't get file names sorted like _1, _10, _2, _3, etc. This is a PowerShell script that once you give it the path to your folder containing the XLS files, it manipulates them with the final result being a file called "compiledExcel.xlsx" located in the same folder. Copy and paste the block of data into whatever official report you have, and that's it. Massive amounts of data compiled quickly and accurately. This script can be further refined, but the heavy lifting is here. <# .SYNOPSIS Converts .xls to .xlsx, trims specified ranges, and compiles data into a master Excel file. #> param( [Parameter(Mandatory = $false)] [string]$Directory = "C:\PATH TO YOUR FILES" ) # --- Helper: Logging function --- function Write-Log { param([string]$Message, [string]$Level = "INFO") $timestamp = (Get-Date).ToString("yyyy-MM-dd HH:mm:ss") Write-Host "[$timestamp][$Level] $Message" } # --- Verify directory --- if (-not (Test-Path $Directory)) { Write-Error "Directory not found: $Directory" exit 1 } Write-Log "Processing files in directory: $Directory" # --- Start Excel safely --- try { $excel = New-Object -ComObject Excel.Application $excel.Visible = $false $excel.DisplayAlerts = $false $excel.AutomationSecurity = 3 # Disable macros Write-Log "Excel instance started successfully." } catch { Write-Error "Failed to start Excel COM object. Ensure Excel is installed. $_" exit 1 } # --- Function: Safely close and release COM object --- function Release-ComObject { param($obj) if ($null -ne $obj) { [void][System.Runtime.InteropServices.Marshal]::ReleaseComObject($obj) Remove-Variable obj -ErrorAction SilentlyContinue } } # --- Convert .xls to .xlsx --- Write-Log "Converting .xls files to .xlsx..." Get-ChildItem -Path $Directory -Filter "*.xls" -ErrorAction SilentlyContinue | ForEach-Object { $xlsFile = $_.FullName $newFileName = [System.IO.Path]::ChangeExtension($xlsFile, ".xlsx") try { Write-Log "Converting $xlsFile..." $workbook = $excel.Workbooks.Open($xlsFile) $workbook.SaveAs($newFileName, [Microsoft.Office.Interop.Excel.XlFileFormat]::xlOpenXMLWorkbook) $workbook.Close($false) Write-Log "Converted: $xlsFile ? $newFileName" # Uncomment next line to delete original # Remove-Item $xlsFile -Force } catch { Write-Warning "Failed to convert $xlsFile $($_)" } finally { if ($null -ne $workbook) { Release-ComObject -obj $workbook } } } # --- Process .xlsx files (remove A1:H13) --- Write-Log "Trimming range A1:H13 from all .xlsx files..." Get-ChildItem -Path $Directory -Filter "*.xlsx" -ErrorAction SilentlyContinue | ForEach-Object { $xlsxFile = $_.FullName try { Write-Log "Processing $xlsxFile..." $workbook = $excel.Workbooks.Open($xlsxFile) $worksheet = $workbook.Sheets.Item(1) $worksheet.Range("A1:H13").Delete() $workbook.Save() Write-Log "Trimmed file: $xlsxFile" } catch { Write-Warning "Error processing file $xlsxFile $_" } finally { if ($null -ne $workbook) { $workbook.Close($false) Release-ComObject -obj $workbook } } } # --- Compile into one Excel file --- Write-Log "Compiling data into master file..." $destinationExcelFilePath = Join-Path $Directory "compiledExcel.xlsx" if (Test-Path $destinationExcelFilePath) { Remove-Item $destinationExcelFilePath -Force -ErrorAction SilentlyContinue Write-Log "Removed existing compiledExcel.xlsx" } try { $destinationWorkbook = $excel.Workbooks.Add() $destinationWorksheet = $destinationWorkbook.Sheets.Item(1) $columnIndex = 1 Get-ChildItem -Path $Directory -Filter "*.xlsx" | Sort-Object Name | ForEach-Object { $sourcePath = $_.FullName try { Write-Log "Copying data from $sourcePath" $sourceWorkbook = $excel.Workbooks.Open($sourcePath) $sourceWorksheet = $sourceWorkbook.Sheets.Item(1) $sourceValues = $sourceWorksheet.Range("B1:B1000").Value2 if ($sourceValues) { $destinationWorksheet.Cells.Item(1, $columnIndex).Resize(1000, 1).Value2 = $sourceValues Write-Log "Copied column $columnIndex from $sourcePath" $columnIndex++ } else { Write-Warning "No data found in B1:B1000 for $sourcePath" } } catch { Write-Warning "Error reading from $sourcePath $_" } finally { if ($null -ne $sourceWorkbook) { $sourceWorkbook.Close($false) Release-ComObject -obj $sourceWorkbook } } } $destinationWorkbook.SaveAs($destinationExcelFilePath) Write-Log "Compiled workbook saved to $destinationExcelFilePath" } catch { Write-Error "Error compiling Excel files: $_" } finally { if ($null -ne $destinationWorkbook) { $destinationWorkbook.Close($true) Release-ComObject -obj $destinationWorkbook } } # --- Cleanup Excel --- Write-Log "Cleaning up Excel COM objects..." try { $excel.Quit() Release-ComObject -obj $excel [System.GC]::Collect() [System.GC]::WaitForPendingFinalizers() Write-Log "Excel closed and resources released." } catch { Write-Warning "Error during Excel cleanup: $_" } Write-Log "Script completed successfully."

Would this be relatable? The profile measurement changes based on the width of the .075, which is not a basic dimension. I'm assuming the best fit compensates the width in the plane's vector?

All I can say is "because we're forced to use PiWeb." Good luck.

Think of the graphic as a cross-section of the hole along its axis. The green arrow dictates which direction the probe will move along the axis of the feature during initial centering moves. If you're starting very near the top of the hole, you want the initial force (this green arrow) to push toward the bottom. If you have this backward (again, only if you're very near the extreme ends), the probe could fall out of the hole while seeking center. Likewise if you're close to the bottom and want to be sure you don't hit the bottom of the hole, swap the arrow. I think, though am not certain, that the green arrow pointing away from the hole bottom indicates initial centering movement along the normal vector. If, like many of us, you keep your scans away from the edges of the hole, you won't notice a difference.

We have drawers full of various configurations of thread locators. I mean hundreds. I've stopped using them. They cost time at the machine. I have no trouble with direct scanning. The plugs are doing a nice job of keeping those drawers from floating away though.

Depending on your Calypso version, but basic PiWeb is free - or in other words included in your Calypso installation. You can choose PiWeb template with only plot so you can have CAD view or graphical evaluation of some characteristics.

hello all, can anybody tell if i want a graphical result without piweb licence, in genral PDF format.