All Activity

@Matthew D If the correct nominal angle does not appear when you select the Tangent1 and the CenterLine 3dLine, this could mean the nominal values of the features used to build Tangent1 and CenterLine 3dLine are not correct or are not at the same Z height or not perpendicular to the Z axis. If nominal features are correct but they are at different Z's or not perpendicular to Z, you can project the 2 lines to the top plane and do an Angle between Features of the 2 projections.

Hallo Matthias, aktuell liegt dazu ein BUG bei der Entwicklung vor, weil die "default" Ausgabe nicht funktioniert. Trage bitte in deiner qdasconv.con (befindet sich im Hauptordner von CALYPSO) folgenden Befehl ein: UTF_8_BOM=1 <- für Ausgabe UTF8 mit BOM oder UTF_8_BOM=0 <- für Ausgabe mit UTF8 (ohne BOM) Mit dem kommenden Patch wird der default als UTF8 mit BOM ausgegeben und kann auf wunsch über die qdasconv.con auf UTF_8_BOM=0 gesetzt werden um eine Ausgabe ohne BOM zu erhalten. Gruß Marcel

.010 is the most difficult measurement to make (imperial measurement, just to be specific).

We have success. Unchecking 'Export diagrams with scale paper' did the trick. This means it was for sure a timing issue where Ghostscript was timing out or something. It formatted to my pdf just fine with no scaling issues. Good call Roman

Hello, Is it possible to connect two separate programs? basically, i need to consolidate reports from 2 different programs.

Thanks.

Hi, please stick to the available articles in the techguide, youtube etc. or contact your local support. A good starting point is this video for example: It is highly recommended to take part in the basic training if you are new to the software. Please do not share content of paid training. Nanno

I can not find any downloadable material for basic training. I have it, but its 16MB

Either double click on text or on right side panel is somewhere a button "Text" where you can edit that. Those values are from keywords - on left is "description(KEYWORD)" and on right is just "user_KEYWORD". Content for report is then in "key" icon. Editing keywords are also in same button like content, but you can edit that and also to be stored in your APP

Wir arbeiten mit einer Vorlage von einem Externen Dienstleister . Daraus erstellen wir eine Vorlage für uns. Bei der ersten Fahrt /Scanen bekomme ich eine Berechnung . so bald ich den Vorgang wiederhole . Kommt der Fehler MCADTool 0030 .Best Fit fehler wird angezeigt

Hallo Andreas, wenn du uns dein Problem und vor allem die Umstände etwas detaillierter beschreibst, kann dir vermutlich jemand helfen.

Guten Morgen ich habe ein Problem mit Best Fit Ausrichtung MCADTool 0030 hat jemand eine Idee wie ich das lösen kann

fehler MCADTool 0030

Thank you Martin, one more thing: is there an explanation of how to change the wording from the title page report ?

Hi, I use an ATOS Q mounted to a FOBA, and in our workflow we frequently need to switch between different lenses for different measurement tasks. Since our company is mainly R&D oriented at the moment, we currently operate the system manually rather than through a VMR cell. I would like to suggest a possible workflow improvement for the calibration process: adding audio guidance that indicates whether the scanner needs to be raised or lowered, and when the correct calibration height or position has been reached. As many users know, manual calibration requires the operator to physically monitor the scanner and calibration board while also looking at the software screen to confirm the scanner’s position and alignment. This can be somewhat inefficient. In my opinion, directional audio feedback could make this process much easier and more efficient. For example, the software could provide different sounds or tones to indicate: Decrease/increase distance Correct height reached Centering needed This would allow the operator to focus directly on the physical setup while receiving real-time guidance from the software, without constantly shifting attention between the scanner and the screen. I would be very interested to know whether this type of feature has ever been considered, suggested, or implemented in any form. I would also be happy to hear if other users working with manual setups have experienced a similar need. Thank you very much.

In short guide is that you right click on style you want to modify and click modify style. After changes you should click icon for apps, click your modified style and save it to your app. All needed info should be on helpguide https://techguide.zeiss.com/en/zeiss-inspect-2023/article/cmd_report_create_report_style.html

This will be by evaluation of datum C/ C' By norms is datum in this case evaluated as tangential element ( circumscribed ). Circularity will tell you more and is the reason why it differs.

Hallo zusammen, mir ist bei der Messung eines Teils ein Problem aufgefallen. An einem Bolzen messe ich zwei Kreise die 1,4mm voneinander entfernt sind. Beim Auswerten der Konzentrizität ist mir aufgefallen, dass die Werte deutlich voneinander abweichen. Bei beiden Messungen habe ich jeweils den anderen Kreis als Bezug verwendet. Ich frage mich nun ob das sein kann und wenn ja warum das so ist. Ich freue mich auf Eure Kommentare

Hello, is there a tutorial that explains how to add or modify report style ?

Hallo, Wir mussten wegen eines anderen Fehlers das Patch für 8.0.1203 installieren. Seit dem scheint der Qdas Export nicht mehr zu funktionieren. Die DFQ wird nicht erzeugt, die Qdas-Log zeigt nur ein "qdas: starting conversion at....." So wie es aussieht scheint die qdasconv.exe kaputt zu sein. Wenn ich die durch eine ältere Version ersetze geht der Export wie gehabt. Ist jemanden das auch schon aufgefallen? Gruß, Matthias

That's what I was looking for. Thank you.

Are you evaluating the slots as individual symmetry planes or one combined symmetry plane?

Thank you, as this is what I was searching for. I will see if this helps in our reports. Thanks again!

That did it!! Thank you Richard for all your help, it's greatly appreciated.

Decided to give it another try after the latest patch, and yea, still avoiding 8.0. I tried an uninstall and reinstall with latest SP and patch, and I think it is actually worse than it was before.