We currently have a position open to fill our CMM Operator position (Traditional Bridge Style Brown and Sharp). We are also adding laser scanner operator (Romer/V5) and rapid prototype technitian to the jobs responsiblities so you will have a wide range of things to do here. If you are interested, please respond with an email and I can send you the details about the postion and about our company.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1 2
#2
IMAlign / Re: Importing 3D Digitized Datasets
January 28, 2010, 03:11:57 PM
So I just dragged and dropped the second IMAlign project into the 3D Scene of the first one and everything imported well. ???
#3
IMAlign / Re: Importing 3D Digitized Datasets
January 28, 2010, 01:56:15 PM
I was never able to put my finger on what was causing this... but it never was an issue, so I forgot about it.
NOW HERE IS MY ISSUE.
I was scanning something very large and I got the Out of Memory error after like 250 linescans.
I scanned the last 1/3 of the part in a new IMAlign project and finished it just fine. Now I have put them together for one large polygonal model. I can use a big 64-bit workhorse now, so the size thing is not an issue. The problem is that when I try to import the linescans from the workspace I get the spotty images like before. When I open the IMAlign second IMAlign project it works just fine and the linescans are complete, but when I try to import them into the first, only 20% of the surface shows up. So it appears the saving of the linescans is OK because I can open it via the second IMAlign project, but when I try to import them into the first to complete the model in IMAlign, it does not work. Could it be my import options?
NOW HERE IS MY ISSUE.
I was scanning something very large and I got the Out of Memory error after like 250 linescans.
I scanned the last 1/3 of the part in a new IMAlign project and finished it just fine. Now I have put them together for one large polygonal model. I can use a big 64-bit workhorse now, so the size thing is not an issue. The problem is that when I try to import the linescans from the workspace I get the spotty images like before. When I open the IMAlign second IMAlign project it works just fine and the linescans are complete, but when I try to import them into the first, only 20% of the surface shows up. So it appears the saving of the linescans is OK because I can open it via the second IMAlign project, but when I try to import them into the first to complete the model in IMAlign, it does not work. Could it be my import options?
#4
Inspector / Re: Probe Surfaces You Cannot Scan
November 25, 2009, 10:11:53 AMQuote from: prehistory on November 25, 2009, 09:51:28 AM
Hi,
I think this is pretty straightforward...
1. scan everything you can in IMAlign. Mesh it, or not.
2. Open IMInspect and import your CAD model
3. import your polygonal model or IMAlign project as the Data object
4. Probe the hidden surfaces as planes. You can probe a lot of points to get better coverage (like 50 if you want). Make sure to compensate correctly so that the data points are compensated.
5. Select all the elements from the probing session(s) and Edit > Data Reference Element > Ignore for Alignment
6. Do your Best-Fit alignment, which will drag all the Data objects (polygonal model, probed points) and their associated features (the plane primitives) along.
7. Run your Data to Reference comparison, and your probed points will act just like the vertices in your polygonal file, giving you a good surface analysis
8. If you want more coverage of the plane areas at this point, just resume probing- you should be "in position" at this point. Do Stationary, or Continuous Time or Distance probing to get good coverage, MAKING SURE THAT YOU HAVE "Compensation" checked in the probing dialog zone, and that you are compensating to the CAD object.
If you really want to compare the plane FEATURES with the CAD, you'll extract the nominal planes at this point, and use the Feature Controls to set up either GD&T like Flatness, or simple dimensions like XY angle or whatever.
Hope this helps!
The step that I am not confident in, is #4. My probing experience is limited and need a little more detail here. My assumption was that I needed to probe by selecting feature > create > plane and select the probe option. By doing this the plane is not associated to the data, so I do not think this is the method you are explaning. Can you please be more specific on this step... ? Thanks.
#5
Inspector / Probe Surfaces You Cannot Scan
November 25, 2009, 07:51:19 AM
Hi everyone... here is my situation:
I need to inspect a cast planar surface that I cannot scan because I cannot get enough of an angle given the geometry. I can howerver can get the probe (of the Romer Arm located above the V5 Scanner) in to probe the surface I need to inspect.
Here is what I am trying to do:
I typically scan in IMAlign, create a polygonal model, import it into IMInspect and then compare it to a CAD model. I would like to be able to incorporate the probed two planes into the scanned (polygonal model) inspection. I would like to use the scanned surfaces in the alignment rather than having to probe all alignment surfaces.
Here is my intial solution:
I wanted to scan in IMAlign, create a polygonal model, inport it into IMInspect (do not align yet), create the two plane features by probing, import the CAD, then align both the polygonal model and two plane features but only using the polygonal model for the alignment. Then I would like to do the comparison
Here is what I do not know how to do:
1. I do not know if I can move the two plane features along with the polygonal model on top of the CAD and use the Best-Fit align to control both polygonal model and then plane features.
2. I also do not know how easy it is going to be to get a comparison from the CAD model to the plane features created by probing - maybe I will have to then define nominal and use the feature controls to get a comparison.
Any advice or procedures would help a lot! Thanks.
I need to inspect a cast planar surface that I cannot scan because I cannot get enough of an angle given the geometry. I can howerver can get the probe (of the Romer Arm located above the V5 Scanner) in to probe the surface I need to inspect.
Here is what I am trying to do:
I typically scan in IMAlign, create a polygonal model, import it into IMInspect and then compare it to a CAD model. I would like to be able to incorporate the probed two planes into the scanned (polygonal model) inspection. I would like to use the scanned surfaces in the alignment rather than having to probe all alignment surfaces.
Here is my intial solution:
I wanted to scan in IMAlign, create a polygonal model, inport it into IMInspect (do not align yet), create the two plane features by probing, import the CAD, then align both the polygonal model and two plane features but only using the polygonal model for the alignment. Then I would like to do the comparison
Here is what I do not know how to do:
1. I do not know if I can move the two plane features along with the polygonal model on top of the CAD and use the Best-Fit align to control both polygonal model and then plane features.
2. I also do not know how easy it is going to be to get a comparison from the CAD model to the plane features created by probing - maybe I will have to then define nominal and use the feature controls to get a comparison.
Any advice or procedures would help a lot! Thanks.
#6
IMAlign / Re: Wavy Scans
April 14, 2009, 09:15:58 AMQuote from: spike3d on April 07, 2009, 01:40:00 PM
Can you post a screen shot of what it looks like at the lower frequency and %?
If all you changing is those 2 parameters then I would suspect that the scanning hardware and software combination is unable to process the higher scan rate data while still getting regular arm position updates.
It might also be interesting to see what the processor(s) usage is like at the two different scan settings by watching it in the Task Manager
With a lower frequency the entire scan looks like the front (yellow) that is nice and flat.
I have not run into this since, so I have not needed to play around with it. I'll let you know if it comes up again. Thanks for everyone's help.
#8
Inspector / Re: Quick slope measurment
April 09, 2009, 09:15:12 AMQuote from: Firefly on April 07, 2009, 11:09:56 PM
If you use nominal and measured ones I think you can only use the angle feature between the two planes.
For using only measured ones the quick way is to define nominal and measured inside one feature with pick&fit so you can use the 'normal' feature controls.
I never noticed the angular feature in the feature menu. I was always looking for something under the measure menu. Thanks for pointing it out for me.
For those who are unfamiliar with what this is, here are some screeshots:
#9
Inspector / Quick slope measurment
April 07, 2009, 09:40:34 AM
What is the quickest/easiest way to measure the slope of a planar surface compared to another adjacent planar surface?
I created two planes on the surface by using a pick than fit, but I dont now how to get the angle relative to each other.
I created two planes on the surface by using a pick than fit, but I dont now how to get the angle relative to each other.
#10
IMAlign / Scanning + Probed Points in Same Session
March 31, 2009, 09:12:19 AM
I very rarely use my hard probes of my Romer Arm and rely on my V5 Scanner. I have a case that I would like to use a combination of scanning and probed points but I do not know that best strategy. I am trying to scan a Briggs and Stratton engine to make sure it will fit in a go cart. I need the overall shape + the mounting holes all in one session. I would like to probe the holes so that I can use it in my alignment as well as to get dimensional data from the hole pattern. Can someone advise me on how I should proceed? Should I be scanning in IMInspect?
Here is a similar pic of the engine:
Here is a scanned pic of the first try when I realized I would not be able to get accurate info on the holes:
Thanks in advance.
Here is a similar pic of the engine:
Here is a scanned pic of the first try when I realized I would not be able to get accurate info on the holes:
Thanks in advance.
#11
General Discussion / Re: Network Connections
March 20, 2009, 10:36:41 AM
Well I think I solved my own problem. I connected both the controller and computer directly to the network switch via regular ethernet cables and it works like a dream. I have not tested if I can work on a workspace that is on a network drive yet, but I know it works in Scanworks so far.
#12
General Discussion / Network Connections
March 20, 2009, 08:57:30 AM
This topic is for you who use a controller box with a ethernet cross-over cable for a connection (ie. Perceptron v4 or v5).
Do any of you guys have it setup to connect to the controller and your network at the same time? If so, how do you guys have it setup?
I was able to connect the controler to the computer using a second network connection with a USB-> Network Adapter, but the connection did not provide fast enough data transfer when the scanner was at scanning at 100%. I would get an error mid scan (after 2-3 seconds) and the scan would stop by itself.
Do any of you guys have it setup to connect to the controller and your network at the same time? If so, how do you guys have it setup?
I was able to connect the controler to the computer using a second network connection with a USB-> Network Adapter, but the connection did not provide fast enough data transfer when the scanner was at scanning at 100%. I would get an error mid scan (after 2-3 seconds) and the scan would stop by itself.
#13
IMAlign / Importing 3D Digitized Datasets
March 18, 2009, 07:27:39 AM
My IMAlign session crashed and I tried to recover the scans by importing the 3D Digitized Datasets. When they imported into my new IMAlign project, it looked like this:
This is what it looked like before the crash:
Has anyone seen anything like this or know why this did not work properly?
This is what it looked like before the crash:
Has anyone seen anything like this or know why this did not work properly?
#14
Inspector / Re: Flatness around a hole
March 18, 2009, 07:01:36 AM
My first thought would be to create a plane using the pick, then fit option. This would snap the plan to the circular area. Then I would just use the flatness GD&T option in the Feature Controls window to determine the flattness.
Are you familiar with these procedures? Or was the question a bit more complicated than this?
Are you familiar with these procedures? Or was the question a bit more complicated than this?
#15
Inspector / View > Origin ?
March 17, 2009, 08:12:27 AM
Has anyone found how to display the origin in V11?
Pages1 2