All Activity

SSDs mostly die for sure. I think dead controller. I had no luck with "shorted cap" on any SSD

@Tom Oakes Can you give a little more description about not being able to access files? Can you see it detected in BIOS? Does the SSD appear in Disk Management but shows RAW or Unallocated? Or it it not detectable at all?

You can edit most of the icons or replace them with the ones from older versions.

The SSD on my Zeiss computer has crashed. I need to install windows10 IoT ENt2016 LTSB High End on a new SSD. I'm very comfortable with other versions of Windows installs. Has anyone ever done this ? Can anyone give me specific info on which version I need to download? I have tested the old SSD in another computer and cannot access files.

I am using own dialog form in python to fill header, store measured data, make pdf ( ask to store and continue if it's with errors - not calculated and so on ), export qdas. I have in queue a program for 3 parts in one scan - using built-in function for that is not good - seems like you have to copy whole program for every part, which seems bad for changes of a program - so i'll do that with python to separate each scanned part from mesh and make stages. So i'll be doing almost same thing as you 🙂

Please note the following.

in this specific situation I want to use the content of the keyword to create a file name for PDF export of the report. Thanks for your help.

Awesome! Thanks Mike

I believe you can see if is this stage enabled, but i'll try to look at it tomorrow at work. So your intent is what? Only reading of enabled stage keyword from report header?

There is a difference between gom.app.project.in_stage and gom.app.project.stages The first one only takes the enabled stages into account, while the second has all stages. I have to create an index list for the enabled stages and find the index in this list for further usage. Or is there another method available? Johnny

Great for beginners who are overwhelmed and need a foundation, but advanced to experts most likely will not use it.

On some topics, but not on dynamic profile. https://www.amazon.com/Geometric-Dimensioning-Tolerancing-Applications-Measurement-Y14-5-2009/dp/0971440166

I true chef does not concern themselves with the opinions of cookbooks.

THE COOKBOOK IS OVERRATED! ...There, I said it 😂

Die Berechnungsart „Geometrie“ sollte nur dann verwendet werden, wenn eine normgerechte Auswertung nach ISO oder ASME aufgrund der Geometrie des Bauteils nicht möglich ist. Ein typisches Beispiel ist eine Positionstoleranz auf einem Halbzylinder. Es handelt sich also um eine Sonderlösung für spezielle Anwendungsfälle. In allen anderen Situationen sollte die Berechnung nach ISO beziehungsweise ASME bevorzugt werden, sowohl für tolerierte Elemente als auch für Bezugselemente. Dafür gibt es zwei wichtige Gründe: Sie können sicher sein, dass die Ergebnisse den Anforderungen der jeweiligen Norm entsprechen. Die Software unterstützt Sie dabei, die Auswertung korrekt durchzuführen. Die erforderlichen Einstellungen werden automatisch berücksichtigt, sodass Sie sich nicht selbst um die Wahl der richtigen Parameter kümmern müssen. Bitte beachten Sie außerdem, dass die Aussage „Zylinder werden nach ISO 1101 als Hüll- beziehungsweise Pferchelement berechnet“ nur für Bezugselemente gilt. Für tolerierte Elemente trifft dies nur zu, wenn die entsprechenden Modifikatoren ausdrücklich spezifiziert wurden. Im oben beschriebenen ISO-Fall erfolgt die Auswertung des tolerierten Elements wie folgt: Zunächst wird ein Gauß-Zylinder berechnet. Aus diesem Gauß-Zylinder wird eine Achse bestimmt. Diese Achse dient als Grundlage für die Erzeugung von Querschnitten rechtwinklig zur Achse. In jedem Querschnitt wird ein Gauß-Kreis berechnet. Die Mittelpunkte aller Gauß-Kreise zusammengenommen ergeben die extrahierte Achse Abschließend wird der kleinstmögliche Zylinder bestimmt, der sämtliche Punkte dieser extrahierten Achse einschließt. Der Durchmesser dieses umschließenden Zylinders entspricht der ausgegebenen Abweichung. Siehe auch ISO 1101 17.14.3

Hello Lacy, it is possible to edit the label templates in Zeiss Inspect and create custom checks with custom abbreviations. But I think the better solution is to edit it in Piweb/the Piweb report template. I will move the question to the Piweb subforum where the Piweb experts are 🙂 Nanno

@Chad Watton, I probably should have qualified by what I meant by "modern." I do not mean black, white and grey styling with minimal contrast. I agree that the legacy icons were significantly more effective than the current icon set, which I detest. By "modern," I mean that we should leverage effective GUI. My kids' Roblox games have more intuitive GUI than Calypso. Solidworks is one of the most effective examples of proper GUI. Zeiss should learn from other such software that helps the user be fast and effective based on color, organization, visual cues, and other design elements.

You can switch from MM to IN by going to Edit->Preferences->Default Units-> Length

Is there a way to switch from mm to in?

You may also want to try performing a manual alignment "in simulation" to make sure everything base alignment related is matching.

Who had a "style of didactic prose" for comments when reading these? I did not see that coming. 😅

I want to add more details to help eliminate any confusion. I renamed two of the CAD entities to Tab1 and Tab2, which correspond to tabs located on my CAD model. After I make changes to the measurement plan, all CAD entities occasionally disappear. When this happens, I can no longer toggle the associated features to show or hide them. Sometimes restarting the measurement plan resolves the issue, but in most cases it does not. Before: After:

The title doesn't match, but are you referring to the "Geometric Dimensioning and Tolerancing Handbook (per ASME Y14.5-2009)" by Meadows? If so, does Meadows provide his own take on the questions the committee specifically left unanswered for the sake of reaching the consensus required by the ANSI process (e.g., the question of whether position or profile FCF's referencing no datum features are all to be Simultaneous Requirement by default)?

I have to agree with @Dinko Sabo. Tom, you said that you marked up the drawing (I'm guessing for IP confidentiality reasons), but I'm also guessing you didn't add the 'Ⓤ0' to the 0.05 for the line with the Dynamic profile tolerance modifier. If I'm correct in that, and the original print said 0.05Ⓤ0△ on one line, the 'Ⓤ0' contradicts the '△', meaning the designer has not utilized the dynamic profile tolerance modifier correctly. If, on the other hand, the line is actually 0.05△, then this could be the same concept as the example in Figure 11-37 of the 2018 standard, in which a wider-tolerance-zone profile is used to control the size and location of the surface, and a narrower-tolerance-zone dynamic profile is used to control the form. (The example in the standard is explicit in the caption that it is a two-single-segment profile tolerance. I don't even see anywhere the standard addresses the possibility of performing refinements in a composite profile tolerance FCF, though I can see why one might want to do that.)