Jump to content

All Activity

This stream auto-updates

  1. Today
  2. ---

    using Pcm to see if subsequent evaluation is running

    getRunMode("subsequentEvaluation")
  3. ---

    CAA probe calibration magic

    If you're seeing .03" difference, even using CAA, you have another problem. The difference between using CAA compared to individual probe angles not using CAA is nowhere near that amount of difference. This sounds like a calibration issue. Do you use more than 1 reference sphere? What is your calibration procedure?
  4. I have several PCM codes that run in the beginning of programs, but when i run a subsequent evaluation, it will error because that run was not run in the normal order. I believe it is not calculating or reading probe data (getProbe().variables) when it is in subsequent evaluation mode. looking for something i can put in the "inspection_start_pcm" like this.... if program == SE then not do something else do something endif
  5. ---

    CAA probe calibration magic

    I ran into this recently when tracking down an error and spent along time trying to wrap my head around it. I'll leave it to more experienced RDS users (former Vast exclusive guy) to confirm but yes. When I ran my verification program from standard calibration styli against RDS-CAA Styli I saw a major move but in general the CAA calibrations were just not as good because of how it's making a mathematical model essentially to try and cover all of the positions. I'm looking at transferring what I can to a list calibration as everything here previously was set up to CAA except for 1 stylus. Still figuring that out
  6. ---

    setCF for dynamic selection of Characteristics

    Here the format of the txt file to use in the addME. I was experimenting with order, redundancy ... and all models were OK, but try when possible, to use in FEATURE LIST.
  7. ---

    ZEISS INSPECT 2027 Released

    Hi @TIM MCKAY, The bundled Python interpreter in ZEISS INSPECT 2027 is Python 3.14. You can now set the required Python version in the App's settings. If you don't specify anything, Python 3.9 is assumed, which would have to be installed additionally. Or you set the App's Python version to 3.14.x to allow using the bundled version. You find the details in Adding and using specific Python versions. Best regards, Matthias
  8. Hello Raul, I think with one surface curve on the "base" surface (curve 1) and a Curve from touch points (edge) on the burr (curve 3) can be used for this. Then a continuous curve distance: ZEISS Quality Tech Guide with max. label. If it is tricky to construct the curves I recommend reaching out to your local support with the project. Nanno
  9. ---

    setCF for dynamic selection of Characteristics

    //============> SOLVED SOLVED SOLVED <======================== When you want to AUTOMATE at-hot or on the fly a PLAN!!! 1. Create a text file but not in the same format as a handwritten "addME("ME0001",...,"ME000n") but in the format: ME0001 ME0002 ... ME000n That is, with the newline or return at the end of each line 2. Then, you can with ===> readListFile() obtain the new LIST of ME: addME(readListFile(PathFile)) That is because the internal format of addME is not the same defined or showed in the sentence addME("ME0001",...,"ME000n"). This was my ERROR. Well community, I try to hold the FEATURE LIST order, but I have experimented and any way, not order, redundancy....order...alll was functional and OK
  10. No. If a new run has been initialized use the new data. No new run has been initialized. "If you need to analyze measurements independently of the CALYPSO CNC workflow, PiWeb Reporting Plus would be the appropriate solution. With Reporting Plus, you can open a separate PiWeb Monitor instance that is not controlled or closed by CALYPSO. You can then open the report and select previous measurements for further analysis while CALYPSO continues running measurements." This answered my most of my question, the only option I wouldn't want is a new run is running. I would want to analyze the current data only. From your reply (In green), I could open a PiWeb report based on the current data and edits and continue editing the program as needed including manually re-running features affected by characteristic changes?
  11. ---

    setCF for dynamic selection of Characteristics

    I got an issue in the Zeiss Calypso system: I have experimented with the external software to automate the Characteristics to measure (Like a MINIPLAN but "on the fly"). 1. I have created the specific instructions addME for the correspondent Characteristics. They aapears in order of excecution of FEATURES. (regardless of redundancy) and the same experiment with / without redundancy, in order and out of features order (EVER RUN FROM FEATURE LIST) addME("IntCone","IntCone","2D Curve1","2D Curve2","2D Curve3","2D Curve4","BottConePlane") //===> (redundancy "IntCone" and in FEATURES order) addME("2D Curve2","2D Curve3","IntCone","2D Curve1","2D Curve4","IntCone","BottConePlane") //===> (redundancy "IntCone" and out of FEAT. order) addME("IntCone","2D Curve1","2D Curve2","2D Curve3","2D Curve4","BottConePlane") //===> (no redundancy in FEATURES order) addME("2D Curve2","2D Curve3","IntCone","2D Curve1","2D Curve4","BottConePlane") //===> (no redundancy and out of FEAT. order) [ in ALL CASES the program RUN without problems and in order of FEATURE LIST ] no issues ONLY WHEN I WRITE EXPLICITY THE CODE on PCM ] 2. When I try to write the code using external txt file automatically, here the PCM addME(readListFile(FOLDER_BASE + "SelectorDim-" + PLANVERSION + "\addMEList.txt")) //===> addMEList is created on the fly THEN I GET THIS ISSUE OR MESSAGE: SOME IDEAS PLEASE TO MAKE A REAL AUTOMATION WITHOUT THESE MESSAGES
  12. Hi, If I understand your workflow correctly, you would like to continue analyzing a previously generated measurement even after the PiWeb report has been closed or a new CNC run has been completed. Is that correct? With the standard PiWeb Reporting workflow in CALYPSO, the behavior you describe is generally expected. At the end of a CNC run, CALYPSO closes the PiWeb Monitor instance associated with the previous run and opens a new instance to display the result of the newly completed measurement. While the current PiWeb Monitor instance is still open, it should be possible to use the measurement selection to select a previous measurement and continue analyzing it. However, this Monitor instance is controlled by the CALYPSO CNC workflow and will be closed again when the next measurement is completed. If you need to analyze measurements independently of the CALYPSO CNC workflow, PiWeb Reporting Plus would be the appropriate solution. With Reporting Plus, you can open a separate PiWeb Monitor instance that is not controlled or closed by CALYPSO. You can then open the report and select previous measurements for further analysis while CALYPSO continues running measurements. For a more centralized setup and access to measurement data from multiple systems, a PiWeb network solution could also be considered. Could you confirm whether this matches your workflow and whether the main requirement is to keep the analysis of a previous measurement open independently of subsequent CALYPSO CNC runs?
  13. ---

    Bild zu einem Prüfmerkmal verknüpfen

    Das geht ganz einfach: Man kann jedes belibige Bild in PiWeb einfügen, so z.B.: Man zieht aus den Vorlagen das "Bild" in das Protokoll: Dort wählt man mit einem Rechtsklick, Bild--> Bild laden..., und wählt sein Bild im jpg Format aus. Und so kann man mit vielen Elementen arbeiten. Man kann sich so auch Koordinatensystem einbauen und die Frei anpassen. Gruß, Matthias
  14. ---

    saveToMiba: failed !

    Ich kann es reproduzieren, CAD-Auswertung -> gesperrter Computer -> Fehlermeldung
  15. Thanks for the input. I've checked all paths works and the funny thing is if use Zeiss "adjustment and check" program this error doesn't pop up. We've created our own PiWeb template, only thing changed is the header everything else is untouched. and on our other CMM's this template works without this error popping up. If i create a new program from scratch with the standard template this error also pops up and that leads back to what your writing that it have something to with the paths, but we can't located the bug?
  16. ---

    saveToMiba: failed !

    Ich glaube die Meldung hat nicht unbedingt etwas mit dem Sperren zu tun. Ich bekomme diese Meldung auch bei CAD-Auswertungen. Sporadisch und nicht immer bei der gleichen Auswertung. Daher bin ich ratlos woran dies liegen könnte. Wäre aber gut eine Lösung zu finden. Ich kann es auch nicht reproduzieren. Wenn ich CNC-Nachträgliches Auswerten machen, kann es sein es läuft durch oder bleibt bei einer anderen Auswertung stecken.
  17. ---

    Contura 6206 Granite Flatness

    Basically correct, but at least in the zone of the air bearings flatness matters, as any deviation directly affects the geometry of one or more axes. That's what CAA is for.
  18. ---

    Calypso 2027

    Hey Marcel, Dieser Fehler tritt auf, wenn die Ampel [Anzeige] verschwindet – zum Beispiel wenn ich AutoRun schließe und Calypso öffne. Danach kann ich die Ampel [Blinker] nicht mehr öffnen, ohne diesen Fehler auszulösen.
  19. Yesterday
  20. ---

    Contura 6206 Granite Flatness

    I was wondering if the flatness of the granite is actually required for CMMs. After all, unless you are probing granite, it takes no part in measurements. If I need to measure something off of granite, I place a qualified plate on the CMM and use that. It's not checked during calibration too. Is this correct or do I misunderstand something?
  21. ---

    gage r&r

    It's been 20 some years, but I believe Gauge R&R on new programs should be emphasized in basic and then even more in advance training. Not only is Zeiss’s reputation hindered when a bad part inspects good or a good part inspects bad and then checks different the 2nd time it’s checked, the CMM and its programmers reputations precedes it. Literally thousands of hours and money are lost over time. I spent a lot of time at IMTS this year talking with several measuring machine company sales representatives and guess what? Programming is easy and damn near bullet proof, anybody can do it, if it doesn't do it itself.
  22. ---

    First Zeiss CMM Purchase Wishlist

    I was considering the rotary for larger parts due to size constraints when that comes up.
  23. ---

    First Zeiss CMM Purchase Wishlist

    It's all about budget. I would push for curve and free form. Having RDS is really a plus - you can reach almost anywhere without special probe config. I can not compare an active head to a passive head, but i believe with a slowdown compared to active head you can do the same. I think you won't need anything else than RDS - machined faces are shiny, so i would not try linescan or optics ( if they are available ). Perhaps rotary table or if you are dealing with gears, then GEAR pro option
  24. Hello everyone, My company is planning to purchase their first Zeiss CMM (Contura 9,12,6). Aside from the necessary things, what would say you couldn't live without? I plan to have a decent selection of probes and extensions as we are more of a job shop so things can vary. I plan to have like 6-9 preset probes for most things but having options is always good. We are considering using the option to switch between rds and other sensors. I know some things are subjective and will vary by use cases. We don't do much with castings mostly machined from bar stock or pre-cut blanks. We do make some die parts so some of the things will be verifying them. Most is steel but we do also do some aluminum and other materials like g10. All suggestions are appreciated. Thanks in advance, Nathaniel
  25. ---

    Qualification Program with RDS-CAA probe

    I have 2 reference spheres. The correct one for that probe is active.
  26. ---

    gage r&r

    I do R&Rs on selective features only. I use close tolerance features and locations. If you base your loose tolerance features on the same parameters as your close tolerance features you should have no issues testing only close tolerance features. We have parts that run upwards of 4 hours per program, in some cases a single part will collect over 2,400 dims, and total run time is around 7 hours. I can do a Gage R&R in about 40 minutes for one program. This will save you a lot of time, and management loves to save time.
  27. ---

    Qualification Program with RDS-CAA probe

    Check your "Reference Sphere Management", what reference sphere is active, do you have an alternate sphere setup?
  1. Load more activity
×
×
  • Create New...