MAFC and Video replay

Bryan Carpio Felsher

MAFC and Video replay
There is a major problem I have been asking to have fixed for a long time now...

In MAFC, there are two parameters...
1) Max discretization step and
2) Max distance between steps

They do two completely different things, yet they are assigned the exact same variable name, so I can't use Equivalent dimensions and grab them all...I have to manually select each one from the list (the one I want to change is the second on the list for each MO even though it appears first on the MO page) which takes a very long time on the part I'm doing with about 500 different tool paths!

The video replay is not working correctly when the step is left large, so i have to make the step smaller (.100) so replay will be correct and then make it large again (400in) before posting!!!

It would be great if the replay just worked correctly, but I still need the variables fixed, because I often will change the value to a smaller number right before posting depending on what type of 5-axis machine the part will run on.

I noticed the replay error because I was making changes to a job I did a year ago in R17 which replayed fine. I bring it back up in R18 and the replay is JUNK!

COE Administrator

RE: MAFC and Video replay
(in response to Bryan Carpio Felsher)
Bryan,

Enter the string "Max Discretization Angle" to filter the right parameters in order to create Equivalent Dimensions.



Bryan Carpio Felsher

RE: MAFC and Video replay
(in response to Bryan Carpio Felsher)
Mark has submitted a request to Dassault to fix the double variable bug on max discretization step on MAFC'ing. Thanks Mark!!!

COE Administrator

RE: MAFC and Video replay
(in response to Bryan Carpio Felsher)
Bryan,

DS has acknowledged the problem and has opened an APAR (Authorized Problem Analysis Report) to most likely be corrected in R19.

I will notify you when the APAR closes.

COE Administrator

RE: MAFC and Video replay
(in response to Bryan Carpio Felsher)
Bryan,

DS has just notified me that this problem will be corrected in V5R19 SP2 and also V5R20 GA level.

======================================================

Patrick T........

PMR 08492,180,000
APAR HD77654 (closed PER)

Bryan Carpio Felsher

RE: MAFC and Video replay
(in response to Bryan Carpio Felsher)
That is Great! I am so pleased with the support we've been receiving lately from you guys. Mark and Patrick -you're great.

In fact, I've tried to think of enhancements I'd like and you have really covered a LOT of ground.

Here "was" my list of importance. Some of the items are in the works or already taken care of.

1) Repair the mass edit function (Is being fixed)
2) MAFC variable issue (will be fixed in next release)
3) Video replay (is fixed)
4) User representation for tools (Is being worked on)
5) Mass edit function macro problem (Is being worked on)
6) Toolpath editor ability to insert PPwords. (Will be fixed in next release!)
7) Clearance feedrate choices (Is fixed in next release)

I have gotten custom VB scripts to address many of my problems- so my workarounds have me satisfied for the most part with many other issues- mostly graphical and functionality stuff.

With these changes, Catia is really on it's way to becoming the BEST. I'm one of those guys that could give a crap about dog and pony show fluff. I ONLY care about functionality to make a good program and that is ALL THAT SHOULD MATTER in my opinion. Fluff is crap for me and I don't need any of it. If there's a workaround, I'm pretty much satisfied if it's an easy workaround.

Here's what we need now, and I might put this in another topic once I have a better grasp of how the repairs should be made.

We need improvements in roughing. It HAS to respect the boundary and start points. It needs an option to skip any paths where it cannot plunge outside the boundary. This is IMPORTANT. You cannot suddenly plunge straight down into hard materials. It is very difficult to catch the times where Catia's path plunges. It needs to just SKIP those paths if it cannot compute an entry outside the boundary or from the start points. Those "skipped" paths should be saved as geometry optionally.

We need HS arc's with the zig-zag roughing path. It really only uses HS machining arcs with helical/spiral type strategies. The rounding motion really makes the machines run smoother.

This shouldn't be too hard to code- just simply SKIPPING any path where the tool cannot be computed to plunge OUTSIDE the boundary and would improve confidence in the roughing paths EXPONENTIALLY!!! Adding HS arcs to zig-zag path just like as done with contouring or pocketing.