All Activity

Hey Austin, The iDIC "Image Scale" value is the same as "Local Resolution" in the ARAMIS App. To find it: ARAMIS App → Select your camera, lens, and measuring volume → Read the "Local Resolution" value (px/mm). That Local Resolution value is the image scale used in the iDIC Good Practices Guide.

subStr must interact differently with a list than a string. But I get the same error from your first post when trying to parse through a list with subStr. Maybe it has something to do with how the text file is encoded. 🤷‍♂️

Hello Abbas, Yes, I have tried flipping back and forth between those two settings, but it has no effect on the "bad" Calypso windows.

Hello Zak, Not that I have noticed but do suspect it is possibly a windows issue as everything looked fine for the first 6+ months of using the workstation, but then one Monday morning I loaded and launched everything like normal to find Calypso text/font not looking right.

Hello, Yes, several customers have successfully scanned bellows with both GOM Scan 1 and T-SCAN hawk 2. Capturing all the data depends on the depth and spacing of the folds. In general, T-SCAN hawk 2 tends to perform better on deep or hard-to-reach features due to its handheld laser scanning approach, while GOM Scan 1 may struggle with areas that are hidden from the cameras. Multiple scan angles and, if needed, scan spray can help improve coverage

Hey Alexis, Using a non-standard camera with TRITOP depends on whether the camera is supported and can be properly calibrated within the software. At this time, we have not found any published ZEISS documentation describing how to calculate the binarization threshold for a Sony A7 IV or recommending a calibration procedure for custom camera models

Hey Dustin, Great question! I don't believe there's a native way to create a line chart from an arbitrary selection of dN values and place it directly in a ZEISS INSPECT report. The closest built-in option is a Curve Deviation Diagram, which requires a curve/section rather than a manually selected set of points. For custom dN line charts, you'd likely need to export the values and generate the chart externally (Excel, PiWeb, Python, etc.) before inserting it into the report.

It's okay to overscan the paths and then limit the evaluation to only the portions inside the area of interest. Also, keep an eye out for whether Calypso extracts the Torus correctly as either an internal or external feature. It's been prone to invert the two on certain versions.

I respectfully disagree with you on this one, @DWC. We fixture and measure parts of that size and shape all day long. It's all a matter of scale. The helix geometry on that part lend itself to either tactile or DotScan non-contact. Vision may be helpful, but it could also introduce projection error.

Randawgg is correct. Here's a more in depth explanation on the topic - https://portal.zeiss.com/knowledge-base?id=1769596

i just ran it in two version to see what i get it seems in my version, it doesn't see the "A" as string and still sees it as a list and returns "D1" also as a list once i converted "A" to string it failed as you suggested

@Joe Kerman, we are prone to believe what we are taught / trained on.

Thanks, @Caitlin Chandler We appreciate the communication.

Were you able to extract the feature as a single Torus, from the CAD model? The CAD lines in the middle of the feature would lead me to believe that we are looking at two seperate Torus features and a thin Cylinder that seperates them. What type of measurements are you trying to take from it?

Hello You can go to Extras>Settings>Environment>Font and see if the font is system setting or Calypso standard. if its system setting you can change to Calypso standard and see if that would fix it

I must be missing something. When it's defined as: subStr(X,1,1), I'm under the impression it will only return the first character, not the first row/line. For example. Maybe someone smarter than me can explain why that works in your attached topic? However, don't fix what's not broken.

this is the portion of the code and in 6.8 worked flawlessly i guess i got lucky with a glitch or something 😁

This is my first time trying to probe a torus, and I agree it seems pretty straightforward...the only issue is that it is so small that no matter how small of paths I set, it the probe keeps going over the edges.

If "Clear existing results" isn't ticked, it will always be set to current alignment.

I have a program that has worked just fine in the past. However, today, I bring it up and when I go to start it, the base alignment is locked and greyed out to 'current alignment'. As I mentioned, I have used this program several times before with no issue. Other programs brought up today also seem to work as well. is there something that I can look at and change?

Glad I could help. I would be extremely cautious with the other programs using subStr though. If the context is similar to what you have shown above, I really can't fathom how they are working.

btw, using torus is a lot less scarier than it seems you can use a combination of vertical (small diameter) and horizontal circle (in your case in four segments) using your star probe specially when you have the cad model

honestly the closes i would get to be able to use two plane as datum would be symmetry but then the call-out should be change to |0.02|B-D|C| projection is a tricky thing, it could be projected using the cylinder axis or using plane vector. each could give you a different point

Please understand the difference between 'Actual Section' and 'Referenced construction' before you simply change the measuring principle: "Actual section" ensures that the nominal plane is used as cutting plane. For many evaluations you need this! "Referenced construction" would replace the nominal cutting plane with an associated actual plane (if you are using a nominal plane with a measuring plane to determine the actual plane). This could result in a nominal and actual section which have not the geometrical same plane which leads to "invalid" inspection evaluations or evaluations which gives you weird values. If you still want to use "Referenced Construction" and you need to have the same cutting plane use a nominal plane with no applied measuring principle ("No measuring principle").

Maybe baseSystem().machine.inspection.settings.actualCFName // name only baseSystem().machine.inspection.settings.actualCF // type and name, for example "Diameter Diameter1" could work.