What's the most amount of features you've reported in one PC-DMIS program?

[rangerboat72]

50+
100+
200+
300+
400+
500+
750+
1000+
1500+
2000+


Just curious. In MMIV the most I reported was around 500 features. Since we've had PC-DMIS (a lil' over two years now) I think the most I've reported has been about 450...


One thing I've noticed though is that the MMIV programs that were that large took over a week to create versus a day or so in PC-DMIS

[ag162]

100+. I've been in small to medium size stampings thru my career.

A.Gore

[MJBolster]

So, if you are reporting on a lot os 32 parts, with 15 dims each, your total would be 480. Is this what you're asking?

[JamesMannes]

2000 on a subaru part.

[dfiola66]

2000 on a subaru part.

one individual part??? Not an assembly??? GAWD!!!

[Andrew Gardner]

1000 - 1500, then I split the programs up. Too many points really slows things down.

[uber user]

~1500

[rangerboat72]

So, if you are reporting on a lot os 32 parts, with 15 dims each, your total would be 480. Is this what you're asking?

No, I'm actually referring to the total length of one program (1 part sample).

[jmgreen]

1874 on a Windshield we had to check at specific points in a grid pattern. Scan would not work due to the shape. What I learned to do in MM4 and now in PCDMIS is to read in the points and use a loop to run the program. Took about half a day to write in MM4 a little longer in PCDMIS (due to learning curve) and almost 35 minutes (if I remember correctly) to run each part. If you have a great many points to run of the same type, 100 to 2000 surface points for example, let me know and I would be happy to send you the part of the program that will read them in and report them. I can now even report just the actuals and and deviation (T value) in a text format that is great to open in excel and graph.
I'm slowly but surely getting the hang of how to use the flow controls and I/O commands. For a while there, I'd get frustrated and go back to MM4 but now I'm determined to use PCDMIS, although I find it is not near as stable and editing is harder. I wish they had better help for this type of stuff. what I've seen so far is poor at best. Thanks to Jim Jewell and Scott for their company's help in giving me a boost along the learning curve. In house training is great if you can get the powers that be to go for it. I'm extremely lucky in that respect.

[rangerboat72]

1000 - 1500, then I split the programs up. Too many points really slows things down.

That's kind of what I was getting at. I've noticed that on some of the larger programs I've created. I've started creating 3 seperate programs for the majority of the plastic housings I measure. One is for the main alignment, one for the holding fixture verification and one for the actual part verification. Once you get used to it, it seems much more efficient...

[why me]

1500+ this took awhile to program and I could take my lunch while it was running.

[rangerboat72]

1500+ this took awhile to program and I could take my lunch while it was running.

I don't know about you, but I kind of like those types of programs...

The one I created the other day was 450 reported features and took about 20 minutes to run. That give me plenty of EXTRA time to study for the CQE exam (not really: too many interuptions)...

[DaddyBluto]

Around 6500 on an intake manifold. Took over a week to program and 2½ hours to run. Mostly profile points.

[bw_bob]

Over 100

[Axel45]

300+

Rack and pinion housing