Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. ---

    Fitting Position on MasterProbe

    Thanks Lucas. I don't use an RDS so that explains why I haven't heard of it.
  3. ---

    Fitting Position on MasterProbe

    Thank you for your feedback. This would be why I am considering a Fitting Position.
  4. Today
  5. ---

    Prüfmerkmale auf zwei PiWeb Protokolle aufteilen

    Then i'm affraid only option would be separate application which would take out information from files ( .hdr, .chr, .fet ) or excel and make own protocol.
  6. ---

    Prüfmerkmale auf zwei PiWeb Protokolle aufteilen

    Hi Martin, Thanks a lot for your answer. I had already suspected as much, but there are so many hidden paths in CALYPSO. MyVoice isn't an option! If you just look at Zeiss's response to it (years of dithering...), MyVoice comes very close to being a black hole.
  7. ---

    Prüfmerkmale auf zwei PiWeb Protokolle aufteilen

    As far as i know this is not doable in Calypso - perhaps in PiWeb app, but that would not be automatical. I would suggest to place this in MyVoice - it should be easily implemented, since it wouldn't alter inner structure of a measuring program much.
  8. ---

    GearPro results with PiWeb

    Please get in touch with the ZEISS support team if the mentioned steps don´t work.
  9. Moin, Ich habe einen Prüfplan mit 42 Prüfmerkmalen.😁 Davon möchte ich zwei getrennte PiWeb Protokolle erstellen und anzeigen lassen. Einmal mit 15 Prüfmerkmalen und einmal mit den übrigen 27 Prüfmerkmalen. Bisher haben wir dafür entweder Merkmalsgruppen genutzt was aber dazu führt, das wir zwei mal messen müssten. Oder die nicht benötigten Prüfmerkmale markieren und einmal mit und einmal ohne "Ausblenden der markierten Prüfmerkmale" ausgeben. Das führt aber dazu das ich einmal ein Protokoll mit 15 Prüfmerkmalen habe und das andere mit allen, also 42 Prüfmerkmalen. ( Hier muss ich auch noch das PiWeb Template kopieren und zwei Namen vergeben weil ansonsten nur das erste definierte Protokoll auf dem Bildschirm angezeigt wird 😞 ) Wie kann ich also (elegant) diese zwei PiWeb Protokolle mit unterschiedlichen Prüfmerkmalen ausgeben?
  10. ---

    Loop - Recall Feature Points from Pattern of Curves

    Hello Richard, I didn't fully understand what you're trying to achieve. Could you post a few pictures of your current setup and what you're aiming for?
  11. In my opinion, the idea of evaluating a surface profile in only one direction is contradictory in itself. It's like if you say "I want to calculate a line, but I have only one point" If you recall the definition of a surface profile, the tolerance zone is derived from placing an infinite number of virtual spheres with their center point on the nominal surface and their diameter being the tolerance width. The actual zone are two tangential surfaces touching the spheres from both sides. How could this be calculated in only one direction? The only way would be to use a line profile instead.
  12. ---

    Removing shadows that cause issues.

    Here is cutout from "Function-descriptions_ZEISS-INSPECT-Optical-3D-2025_EN.pdf" which i could find on the internet. There is a way to remove artifacts due fixture shadows ATOS_shadows_artifacts.pdf
  13. ---

    Annoying Elements in the CAD Window

    in my case after uncheck all the boxes teh elements still remaining.
  14. Yesterday
  15. Does anyone know of an efficient way to Recall Feature Points from a Curve that has a Pattern on it? In my example, I have a group of (4) curves that has a 116x pattern on them. I need to then create a FreeForm Surface for each 4x group of curves - so essentially I need to create 116x FFS that pulls from the correct set of (4) curves. Any and all help is greatly appreciated.
  16. ---

    error: A primitive has failed

    Isagani, Thank you for the update. Glad to hear that you were able to pinpoint and resolve the issue!
  17. ---

    Fitting Position on MasterProbe

    Hello Richard, Typically, no, performing a fitting position of the masterprobe shouldn't require you to re-qualify all of your stylus systems. Really, a fitting position only needs to be performed once to enable RC-CAA for other stylus systems. If the fitting position was done as part of routine maintenance, you probably don't need to requalify. However, if the fitting position was repeated because of a crash, hardware change, or for another issue that could affect accuracy, then I would recommend requalifying the other stylus systems. Here is all I could really find on the topic in the CALYPSO manual
  18. ---

    error: A primitive has failed

    UPDATE: Background: IT department modified the network printer path/location without us knowing, this caused the error to occur after the program finished running and about to create PDF files and send to print automatically. In the Calypso Environment - the printer was still set-up to the old network printer which was selected initially before. The Fix: changed it to calypso default printer, which is the newly set-up network printer or you can select the printer manually in define printer.
  19. ---

    Fitting Position on MasterProbe

    I've never heard of a fitting position before. What is it?
  20. ---

    Annoying Elements in the CAD Window

    Unchecking this box makes them go away, but the box gets re-checked automatically for me in one particular program. I wish i could figure out how to fix this one annoying program
  21. ---

    Fitting Position on MasterProbe

    If I perform a fitting position on the MasterProbe will that affect all of my qualified styli? I have always re-qualified all styli in the past. Just looking for a short cut since I just qualified recently. FYI I had a stylus pass RC-CAA and qualification with a sigma of .00061 while the limit is set at .00015. It clearly shows as passed in the Probing System Qualification dialog box.
  22. ---

    VMR Path Opetemization

    Is here any way to turn off the VMR optemization? I had to adjust some moves on our new scanbox (assembled with Inspect 2026 only) and the program I was going to edit was previously migrated to Inspect 2025, both 5x scanbox systems. The VMR scan positions were re-created on the new 5X, why would the new cell auto optemize moves on a program with identical VMR's? For clarity, I used the same VMR elements in both projects. All I did was open the inspect 2025 project in Inspect 2026 at the scanbox.
  23. ---

    A Helpful Tool - ZEISS Knowledge Base

    "Nothing has changed".
  24. ZEISS offers several multi-sphere calibration artifacts, here are 2 examples. https://shop.metrology.zeiss.com/INTERSHOP/web/WFS/IMT-US-Site/en_US/-/USD/ViewProduct-Start?SKU=626106-9013-000&CategoryName=460120&CatalogID=400000&ExtendedNavigation=true https://shop.metrology.zeiss.com/INTERSHOP/web/WFS/IMT-US-Site/en_US/-/USD/ViewProduct-Start?SKU=626106-9120-100&CategoryName=460120&CatalogID=400000&ExtendedNavigation=true Here is a thread on one method for adding a second orientation to a calibration program
  25. Yep , its killstrike from designer. I think that the designer confused position with surface profile. Thanks for the feedback.
  26. I saw evaluation in one axis, but that was in Calypso and only for curves - not for FF. I ended up with equidistant points and reporting their deviation in on axis. But i can not figure out what meaning will that number have for me.
  1. Load more activity
×
×
  • Create New...