Jump to content

Stitching 3 measurement files together


---
 Share

Recommended Posts

This might be a beginner question, But I have 3 separate measurement measurement files I want to stitch together and I'm having problems.  I fully understand how to combine a top and bottom scans using common reference points.  But when I try to import the 3rd scan, it won't let me choose different reference points to stitch that 3rd scan to the two I've already combined.

I feel like its something obvious I'm missing here.  I can provide more details and screenshots if needed. 

 

Link to comment
Share on other sites

Please sign in to view this quote.

Hello Chad.

I think this is the method; if you are combining multiple curves into one curve select all of them then Right click and select: ADD RANGE LIMITS

Add range limit.jpg

Edited
Link to comment
Share on other sites

Close, but that's Calypso and I need this for my GOM scanner using Zeiss Inspect.  Actually, I'm using GOM ATOS Professional V8.  Which has pretty much the same interface as Zeiss Inspect.   

 

Random side note, soon I'll be getting a new computer for my GOM and latest version of software.  

Edited
  • Like! 1
Link to comment
Share on other sites

Hey Chad, 

It sounds like the issue may be related to how the reference point alignment was created. Are all three scans in the same project, and do the same reference points exist across all of them? If the third scan uses a different set of reference points than the first two, a slightly different workflow may be needed.

My first suspicion is that you're creating a single reference point alignment that contains only the points used for Scan 1 ↔ Scan 2. Once that alignment exists, INSPECT expects all measurement series participating in that alignment to use the same point set.
 
Link to comment
Share on other sites

Please sign in to view this quote.

I think updating the PC and the software will be a great advancement for your workflow. Please reach out if you need any help along the way with that as well.  

Link to comment
Share on other sites

Please sign in to view this quote.

This is zeroing in on my issue.  

 

Each measurement series is in a separate project.  You are correct in that I created the reference point alignment, and Inspect is expecting my 3rd scan to use the same reference point alignment, but it doesn't. 

It seems like this should be possible, but I can't figure it out.   I have an idea of combining two of them using reference points, then turning it into CAD, and then using geometric alignments to combine them, but it seems like I should be able to do this with reference points.  

Below is a breakdown of what I have:

 

image.png.2b606336dcb8182a174da6b60b80886e.png

Link to comment
Share on other sites

Based on your diagram, I think the issue is that the Bottom and Top scans don't share any common reference points. Once Bottom + Middle are aligned using one reference point constellation, the software expects additional datasets to use that same constellation.

My thought would be to use the Middle scan as the bridge:

  1. Align Bottom ↔ Middle using their common reference points.
  2. Keep the Middle scan in the project.
  3. Import the Top scan.
  4. Create a second reference point alignment between Middle ↔ Top using their shared reference points.

In theory, this should allow the transformation chain to propagate Bottom → Middle → Top without requiring Bottom and Top to share reference points. If that isn't possible in ATOS Professional V8, could you share a screenshot of the project tree after combining Bottom and Middle? That should help determine whether this is a workflow limitation or a project setup issue.

Link to comment
Share on other sites

Please sign in to view this quote.

Okay, this was my idea at first;  But I can't figure out how to create a second reference point alignment.  

Usually I can get these in two scans.  So I don't have much practice combining when I use 3 scans. 

 

image.thumb.png.fb2db6d2e8494da219ac2230c4bb2533.png

image.png.15dc5be6fb60514d9a87f49c3c60e02a.png

Link to comment
Share on other sites

 Share

×
×
  • Create New...