All Activity

This might not be relevant, but Zeiss Inspect can use AMD Ryzen just fine. My Zeiss supplied computer for Inspect has an AMD Threadripper.

Alternative to 3D PDFs https://github.com/Devon-Kile/Colormap_Visualizer_addon.git https://github.com/Devon-Kile/Colormap_Visualizer.git

I created a colormap visualizer that exports colormaps as standalone HTML files. It currently supports Surface Comparisons on CAD, Surface Comparisons on Actual (mesh and point-based*), Surface Components*, and Vector Fields. For projects with multiple stages or displacement data, the viewer includes a timeline so you can switch between stages. I tried to match the look and feel of ZEISS INSPECT. In short; the exporter reads the colormap np.arrays (.data.coordinate | .normals | .scalar_values | .triangles[when available]), compresses them, and embeds them in the HTML. The exported .html opens in most of the browsers i've tested so far, and in Microsoft teams chats. the user doesnt need to install anything. = ) to install: Download .addon: https://github.com/Devon-Kile/Colormap_Visualizer_addon.git or https://github.com/Devon-Kile/Colormap_Visualizer.git code->download zip->extract the "Colormap_Visualizer" folder--> Then in Zeiss APP Editor -->Connect external folder. test it, break it, fix it, & i've also included a "prompt_for_ai.md" if you want to improve it. *known limitations documented in the README.md

Thanks, I try to be through in my testing 🙂 Yes, it has been powered down and left to sit for ~15 mins first by the control box power button, then for ~45 mins by the control box power button then unplugging it from the wall. I'm in the process of submitting a helpdesk ticket, hopefully they'll have some ideas. The PC has been restarted as well.

You've done some good testing. Looks like you've ruled out limit switches and a faulty E-Stop on the control box. Dumb question, but have you completely powered the machine down and restarted it. I don't know of a way inside Calypso to say which sensor is causing the error. The Zeiss technicians have a software that will tell you, but its not publicly available of course.

Do you have filters and outliers?

If you perform a few automatic probe-tip changes and the probe head makes a humming sound or takes longer than usual to calibrate, the head is likely faulty. You might also want to try probing the reference sphere a few times to check for any variance in the probing results.

@Richard Stanich I’ve also used cervical plates like those; I handled the alignment via the drill hole (using a ball-shaped component).

It "should" be the curve corrected points. I've had issues when the two curves were setup differently, so typically I just define one of them, copy, and offset the 2nd one, so that they match. Usually the start/stop isn't much of an issue, it's typically the point numbers being drastically different, so there isn't a directly opposing point for calculation.

I don't use RE, but what I can say is that on the portal the most recent version is 2023/3.0 and that Zeiss' Software Product Discontinuation list currently has neither an "end of sale" nor an "end of support" date for this version.

Does the "Curve Distance" evaluation(s) use actual points or the calculated feature for results (for instance, if 4000 points was used on one curve and 5000 points was used on the other)? Also, what if the Curves were scanned in opposite directions, or with different start/stop points (in a 360 degree scan)

Agreed @Joe Kerman. That's exactly what this metrology community is for. We help each other and learn together.

Hello all, There is a basic dimension that is required for the next step in the process on our reports (perpendicularity callout), with a 0.005" tolerance. The problem is that every dimension on the report is usually in except the perpendicularity callout. It shows that there is one dimension out when in reality it is ok. I've asked about increasing the tolerance for it, but that was shot down. Is there any way that I can keep the tolerancing, but still show that it passed on the report? (have no red out of tolerance "number values:red")

A little AI information:

Huh, interesting, I've always assumed that CPU's brand doesn't matter as long as they support the same instruction set. I knew GPUs are different because of CUDA cores etc.

Hi, everyone We have been using ZEISS REVERSE ENGINEERING for about three years. During that time, we have never received a software update.We have now heard that the software is no longer being developed and is being phased out. Does anyone know the current status? Thanks in advance

Hallo Matthias, stell dein Profil vorübergehend auf US, dann sollte der Link funktionieren

At the bottom on the portal, Additional Files -> https://portal.zeiss.com/download-center/softwares/imt/software/9533

@Matthias Suchanek I cannot believe the Knowledge Base problem is still not solved. Dear Carl (@admin), when is the release date planned?

where is it

A gauge "uses all points, no filter and the hull principle" so to say. Measurement uncertainty on partial radii is real. You can use a form tolerance or make the tolerances appropriate for the situation? If you are afraid existing spikes in the radius area ruiining the result, but being acceptable, you can also go the "radius existing" text- route.

Hello all, sadly when I try to open this link, I get the message: "This page does not exist". If somebody has the time to share what was discribed in this article, I would be really grateful. Matthias

Calypso Simulation Mini-Games sound like an interesting way to explore interactive gameplay and enjoy short gaming sessions. Mini-games can be a great choice for players who want something entertaining without a long time commitment. Mobile gamers who enjoy customizing controls and sensitivity can also explore for Free Fire settings and gameplay customization information.

Zeiss publishes a "PTB Report" where they have an external company validate the math for every calypso release. Doc is published along with release notes.

Got a bit of a head scratcher on my hands. My Zeiss Micura was working fine on Friday and refuses to operate today after being left on all weekend. The status log does not have any enlightening information. On the control box, the only relevant symbol is an inverted triangle with an exclamation point in it. The drives on the device refuse to engage. I press the "M" button on the control box, I hear the button click followed by a rapid click-click of a relay inside the control box. The drives do not engage, and the light above the "M" does not flash or come on. It's got 5.1 bar of Nitrogen being delivered to the machine, so it's not air pressure. I can also hear the air system power up when I unlock the joysticks, and power down 15 minutes later. The head and bridge are not on the limit switches and are sitting about the middle of the machine. The PC connects with the CMM, as I can see the XY coordinates change as the bridge is gently pushed in the XY directions. I swapped the control box with another Micura we have, and the issue persists on the original machine. What should I check next? Is there a way to find out which sensor is stopping the drive?