How to make a feature request for a new Operation type? (WCS Translation/Offset)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi, can someone point me to how I can make a feature request proposal to the Fusion 360 manufacturing team?
The proposal is a feature to translate WCS coordinates. This is fairly similar in UI (but quite different in outcome) to using probing where you click the "Override deriving WCS"
The purpose of the request is that many manufacturing shops will use a fixed reference point as their WCS origin to increase setup speed for many manufacturing jobs, for example the zero point location, point on a vice, corner of a jaw, etc. For example, in my case I use the top-left/bottom-right of the bed of each vice as a fixed reference point
However, this is inconvenient at the machine in as much as I much prefer the g-code coordinates to be relative to some point on the part itself, for example an underside face is generally my preferred reference. This has benefits in that I can quickly observe (at least in 3 axis machining) that Z axis references are all than xx millimeters above the zero plane, meaning I won't hit the jaws or whatever. Basically WCS relative to some distant point is hard to sanity check on the machine itself
On first inspection, the "Override deriving WCS" looks to do what is needed. However, it leaves the WCS based on the original WCS, so whilst it can correct for deviations between the CAD model and actual machine setup, it can't easily handle doing something like swapping out for a different set of vice jaws or moving the setup to a different vice altogether.
I can of course do what I need through a manual NC operation, but this is error prone if I change the CAD/CAM, then the changes don't flow through to the manual NC operation
The proposal is for an operation, which will need machine specific post support. It will assume that the user has created their setup with their desired on machine WCS, for example centred on the part. The operation will take a source point on the model and the source WCS that defines that point. This will work very similarly to how the probe UI looks today, except only points or planes would be selectable. The post will be responsible for setting the destination WCS to be equal to the source WCS, except shifted by the offset as measured from CAD.
The flow through the post would look very similar to the current probing code path
Opinions?
Fusion