The figure that was 4-16 in the 2009 is now 7-22 in the 2018.

Thinking more on the RFS version - the datum feature simulator for D will be perfectly centered at the 29mm distance from datum feature simulator for B. When it starts to contract around datum feature D, it may only contact one point that is on a plane through the axis of the datum feature B simulator and the axis of the datum feature D simulator, but since that limit is on an RFS basis, it could be that this large diameter of the simulator will contact the that single point at the lowest diameter of the feature. Determining exactly where that one point is won't be easy and small errors in measurement will allow large movement of the part relative to the datum reference frame.

Had they used the translation modifier then the position tolerance would no longer apply and the feature would better control clocking. This case is what the translation modifier was created for.

pmarc - good catch. I should have known that they would add additional cases. So many parallel construction paragraphs that bulk up the document. Serves me right for skimming.

Now there are two of them that are certainly not correctly describing the situation.

I'm not sure, having not worked though it, but I expect 7-23 also is flawed for the same reason. I expect that the LMB situation leaves a thicker wall tangentially relative to [A|B(L)|D(L)] than the calculation would suggest.

3DDave,

I am glad that you finally saw the reason for introducing the translation modifier to the standard

I don't see a reason for introducing it, but if it's in there might as well use it. I prefer controls to be explicit rather than forcing the drawing reader to have to figure out what degrees of freedom might be left unconstrained. Using parallel extensions on the width of the feature shows the exact direction the control is to be applied. They could have used the customized datum reference frame instead of creating the translation modifier as well; that would also make the direction of the control explicit.

<off topic> One concept that seems to be skipped is that datum feature references are best used as idealized versions of the mating features on the mating part(s.) If a planar mating surface is identified as a datum feature, the pretend version of the mating feature on the mating part is a planar datum feature simulator - a stand in for the planar imperfect mating surface of the actual part.

With that in mind, when there is a case that something like a protruding pin on a mating surface is going to mate with a slot, then the depiction of how that slot is oriented is important. It isn't always the case that the slot will intersect with a locating feature/axis of rotation to simply control rotation. It's possible the slot will not intersect. The problem with the translation modifier is that there is only one sort of slot that can be represented and it takes anyone else depending on the drawing time to figure out what can be explicit - in the case of the customized datum reference frame that direction is easily machine readable without having to depend on some AI to sort through the options that are unclear from the translation modifier. With extension lines, it is discernible at a glance.

Done graphically with extension lines and more, one could have a datum feature defined to account for a curved slot in the mating part.
</off topic>

Regarding the RMB case:
Contrary to what you allude to,
The maximum external boundary of datum feature D at case (c) is an 8.6 diameter. This results from the combination of size+form error plus the position tolerance creating an outer boundary of datum feature D, and it would be so even if the position tolerance applied to it was referencing only A and B rather than A, B, C. It is true that for the position control of case (c) datum feature D is free to rotate about datum axis B before being constrained to its simulator, but it doesn't alter the boundary dimensions in any direction because in that stage the pin feature is still potentially able to contact any point on an 8.6 diameter boundary perpendicular to datum A and centered to any point located at exactly 29 mm from datum B. This is true with or without the perpendicularity within 0.3 control applied to datum feature D.

Edited: the bolded portion for clearer description.

Datum feature D is allowed to rotate 360 degrees about [A|B] so the width is a 360 ring. It can contact some point(s) on the inner and/or outer surface of that ring. When D is added as a constraint it is only the tangential tilt that sets the width. The width due to that tangential tilt is less than the radial width of the ring.

3DDave,

Customized DRF concept and the translation modifier are two different animals.

In the scenario that you described in the off topic reply, customization of DOFs constrained by the tertiary slot would make no sense because there would be no DOF to customize (as there would be only 1 rotational DOF left to constrain by the tertiary simulator). It would makes sense, however, to specify that the location of the tertiary simulator with respect to the secondary simulator does not need to be basic.

The problem at hand was the origin of the translation modifier suggestion - that is: while there is one remaining degree of freedom the tertiary feature controls two degrees of freedom and, in a practical application it may be the feature that forces the part into a particular X location that secondary one does limit. Example: if the tertiary is a tighter fit than the secondary.

By specifying a customized datum reference frame it becomes explicit that only one degree of freedom from that feature can be used, so force-fit away.

If it was interpreted the other way then there would never be a push for the translation modifier.

edit:

Another alternate is to specify something like [A|B|B-D]

For the customized datum reference frame the modifiers could be [A[z,u,v)|B(x,y)|D(x,y)]** for the non-translation mode and then the translation mode is the default and requires no symbol.

** Yeah - they should be in square brackets, but I'm already using square brackets for the feature control frame delimiting and this editor doesn't have text size control to make them little like they did in the standard.

As I indicated, there should be a way to define the direction that the datum feature (or any feature) is allowed to move tangentially when there is a radial change.

I don't think the true origin of the translation modifier was to prevent the tertiary from constraining more degrees of freedom than it normally should, although I agree that it could be a potential application.

The origin is relatively decently explained in fig. 4-32 in Y14.5-2009. Notice that both Means this illustrations don't differ when it comes to which and how many DOFs are constrained by B secondary.

The competition in 4-32 is whether the slot location and slot width are both used to set the orientation or whether only the slot width is used - the translation is eliminating an over-constraint by allowing the centerplane of the slot to be at a different radius from the axis. Removing that constraint allows a wider range of parts to be acceptable, (whether or not that wider range is also useful is another task beyond Y14.5)

AFAIK the first area was in 4-9 vs the added 4-19 example where the desire was to use RFS callouts for the holes used as datum features and the complaint was this might require a mallet to get the part onto the gauge. I don't recall if it was this forum in the Yahoo! Y14.5 group but that distance between pins problem was the first I came across it and that was before the '2009 was a twinkle in anyone's eye.

4-9 was kind of like figure 4-8 from '1994, but they removed all the maximum material references in the '1994 version so it could use the fictional uniform expanding pin and then 4-19 that still requires the fictional uniform expanding pin plus a precision made gauge if real gauges are to be used as was once the case for mass production in-process inspection. I guess they felt they covered the maximum material case in other figures to not double onto it in '2009.

Quote (3DDave)

Datum feature D is allowed to rotate 360 degrees about [A|B] so the width is a 360 ring. It can contact some point(s) on the inner and/or outer surface of that ring. When D is added as a constraint it is only the tangential tilt that sets the width. The width due to that tangential tilt is less than the radial width of the ring

In the RMB case option (b), had the datum references been |B|D|, would you say the OB (Outer Boundary) for datum feature D is a 360° ring?

D has a datum reference directly to A. That's where the perpendicularity fits in.

Another analogy since the Monte Hall problem didn't work.

You are standing beside a highway. Cars go by at 100kph. If you reach out to touch one you'll be injured.
You then get into a car and you travel with the stream of cars at 100 kph. You can reach out and touch another car next to you. You aren't injured.

Changing the frame of reference changes the outcome.

The tangential component for the location of the feature used as datum feature D is only fixed by the initial reference to datum feature C. Once that is gone all that remains in the tangential direction is the orientation limitation and that is refined to a smaller value by the perpendicularity tolerance. The radial variation remains only as long as there is a reference to datum feature B. With that gone, the orientation component of the position tolerance remains, and the position tolerance control of orientation is again refined away by the perpendicularity tolerance when the only reference is datum feature A.

The explanation in 7.11.9.1 (b) is dissatisfying for not telling why the position tolerance isn't part of the calculation.
"to ensure that datum precedence is not violated" doesn't say how it could be violated and why this selection avoids violating it. I think too much discussion happens at the meetings until everyone is familiar with the supporting analysis and then they forget they only got to that understanding by seeing that supporting analysis which they don't put in the document.

The cynic suggests that's held back to sell training, but the group-thought experience says the more likely explanation is they are so used to it they don't notice. Like the use of UAME in some posts - an abbreviation that isn't in the standard.

Since you posted your reply at the same time I edited my post (very short time after posting it), let me ask you one more time:

In the RMB case option (b), had the datum references been |B|D|, would you say the OB (Outer Boundary) for datum feature D is a 360° ring?

It would not be 360 because D is what gets you going 100 kph to align with D. If it is [A|B] only then datum feature D is not constrained and the part is free to rotate resulting in that ring.

If it is B only then it's too complicated as predicting the orientation of D relative to B is not trivial, but the pin feature will be able to occupy anywhere in some ring shape. A fixture to accept all locations/orientations of the pin will require a circular trough for that side of the part.

Quote (3DDave)

It would not be 360 because D is what gets you going 100 kph to align with D.

Then what would be the shape of the OB, and what would be the shape of the datum feature simulator/true geometric counterpart for datum feature D, in a control referencing B primary D secondary?

3DDave,

In my mind, figs. 4-9 vs. 4-19 and 4-32(a) vs. 4-32(b) are about the same thing - the translation modifier allows the simulator to fully engage with the feature designed to constrain the rotational DOF.

My main message still remains - in principle, the translation modifier does not work the same way as the customization of DRF, as one might conclude by reading your previous comments in this thread; in 4-19 and 4-32(b) no DRF customization really takes place.

Side note: Although the gage pins B and C in fig. 4-8 in '94 would indeed be of fixed size, according to para. 4.5 3(d) the distance between them should be variable, and so the whole gage would not be that trivial anyway.

Side note 2: A mallet might be needed to install the part from fig. 4-9 in '09 onto the gage, because generally in the gage design (assuming someone would even like to design a gage to simulate B and C at RMB), the sequence of DOF constraint, as defined by the datum portion of the FCF, is ignored for obvious economical reasons. Even Y14.43 standard for gages doesn't pay too much attention to the topic - there is just one figure, as far as I remember, that talks about it in greater detail.

4.5.3(d) in '94 was about RFS gages, so for 4-8 would not apply and a moveable pin would not ever be required.

All that the translation modifier does is relieve the constraining feature of one degree of freedom, which is explicit in a customized datum reference frame. How do you suppose a customized datum reference frame is able to shift constraints from a feature they ordinarily control to one later in the sequence?

As I related earlier - indicating the width of a hole or pin in the direction of desired restriction on the datum feature handles these cases.

As for the orientation by the slot - I haven't seen any real mechanism that both required a fixed offset to define the location of such a feature that then said - doesn't matter where it is. However - on an RFS basis the slot competes for control of the Y location and excluding that control explicitly would indicate that the datum simulator could move.

For '2009, "in 4-19 and 4-32(b) no DRF customization really takes place." That's true - both are MMC/MMB cases.

Quote (3DDave)

4.5.3(d) in '94 was about RFS gages, so for 4-8 would not apply and a moveable pin would not ever be required.

The only difference between MMC and RFS gage pins in '94 was in the size of the pins (fixed vs. adjustable), not in their mutual distance relationship (basic vs. variable). Take a closer look at fig. 4-9 in '94 to see that the basic distance between the simulators/TGCs B and C is not fixed. Also, if you have access to Y14.43-2003 (that supports Y14.5M-1994) you may want to take a look at fig. B10(c) to see how the lack of the requirement for basic distance between pins B and C is realized. This changed with the release of Y14.5-2009, where para. 4.5.2(c) explicitly stated that the distance between the two simulators must be basic, unless translation modifier or movable datum target symbol was specified. Both cases are illustrated by figs. B10(c) and B11(c) in Y14.43-2011 (that supports Y14.5-2009).

Quote (3DDave)

How do you suppose a customized datum reference frame is able to shift constraints from a feature they ordinarily control to one later in the sequence?

As far as hard gaging is considered, you may want to take a look at fig. B24 in Y14.43-2011 for an example of how this can be achieved. This figure corresponds to fig. 4-46 in Y14.5-2009, except that the MMB modifiers were added in B24.

Quote (3DDave)

For '2009, "in 4-19 and 4-32(b) no DRF customization really takes place." That's true - both are MMC/MMB cases.

I am not sure why you are saying that these are MMC/MMB cases. Taking fig. 4-32 as an example, I am imagining the slot B produced at the LMC width and perfectly perpendicular to A. When mounted onto a gage simulating the |A|B⊳| DRF, the part will look the same as in fig. 4-32(b). But when mounted onto a gage simulating the |A|B(M)| DRF, the part will be allowed to look more like in fig. 4-32(a), except that the width of the simulator B will be fixed at 4.7 and the slot will be contacting the simulator B at only one wall as a result of rotational datum feature B shift.

FYI... My intention was not to sidetrack the thread. I just felt a comment was needed after you had suggested that the translation modifier could be simply replaced with the customized DRF concept. Can we now agree that we went too far down the rabbit hole?

It's fine - otherwise it's just been comments saying that rules are rules and that's all there is to it.

Did I misunderstand "Side note: Although the gage pins B and C in fig. 4-8 in '94 would indeed be of fixed size, according to para. 4.5 3(d) the distance between them should be variable, and so the whole gage would not be that trivial anyway?"

That seemed to indicate the the MMC callout didn't require the distance to be fixed and therefore the gauge, as suggested, would not be trivial. Perhaps it was a short cut and was meant to be about the RFS version and that then 4.5.3(d) would apply - but that paragraph says nothing about translation.

Which is what was the division in opinion in the standard's participants that drove the translation modifier; however at the same time the customized datum reference frame was also being worked in, no doubt by a different committee and they all agreed "Why not both?"

Is there any case of a customized datum reference frame that can properly be gauged without translating and/or rotating gauge elements? If they can translate they could be doing the same thing as the translation modifier.

I don't have 14.43; Did they put a fixed round pin into the square hole and call it good? Because the customized datum reference frame callouts implies that there should be square pin that fits with a cylindrical base into a hole so it can turn to allow motion to let datum feature C participate. If they moved it to all MMC/MMB references that avoids putting the datum feature C simulator on a slide to vary the center distance. It becomes a much easier gage with one rotating part.

re: 4-32 - i'm dumb and got looking at the wrong figure instead of 4-32.

For 4-19 - similar problem as for the offset slot - why are they defined at MMC and then referred to at RMB? Why give bonus orientation/location to them based on the size and then say - naw, we're going to build the mating assembly to have expanding pins, and one of the pins is on a slide mechanism? I don't see an application that demands this - it seems contrived to support the translation modifier because the CMM guys hated looking for the center of the "expanding pin" because it requires generating geometry to see where it contacts and that just finding the center of the hole wherever it was was so much easier.

Quote (3DDave)

Is there any case of a customized datum reference frame that can properly be gauged without translating and/or rotating gauge elements? If they can translate they could be doing the same thing as the translation modifier

Yes, there is one in the standard, the one with the conical primary datum feature giving away the axial translation constraint to the secondary.

And what if the gage element needs to only rotate, like in another example, the one with the square hole? Would you then ask for addition of a rotation modifier?

On the other hand for cases with the translation modifier, often the explicitly stated degrees of freedom for a customized datum reference frame attempting to replace the modifier, would be the same as the ones implied by the types of datum references and the datum precedence order anyway, as the modifier is not intended to change the way how the constraints should take place in an ideal scenario like the costomized DRF does, but only to prevent a problem.

I take that you are still thinking through my last question from 8 May 22 05:04, or maybe you lost interest in the original topic of your thread? In that case you may as well want to change the title again.

I thought I had already given an answer for that before you asked, but if you need it again - here it is:

Quote:

If it is B only then it's too complicated as predicting the orientation of D relative to B is not trivial, but the pin feature will be able to occupy anywhere in some ring shape. A fixture to accept all locations/orientations of the pin will require a circular trough for that side of the part.

Oh - I realize you don't consider context - the context is that Only B preceding datum feature D, not that B is the only reference, which would make no sense due to the fact these all concern using D as part of the development of the datum reference frame. So, here, if you want it spelled out for you [B(m}||D(m)] is what I was referring to.

Why would I ask for a rotation modifier? There is already a customized datum reference frame control for rotation.

Quote (B)

Yes, there is one in the standard, the one with the conical primary datum feature giving away the axial translation constraint to the secondary.

That requires the fixture to move to engage the cone relative to the pin and flat face and to control the orientation of the entire part. It cannot be a single rigid gauge.

I asked you earlier:

"In the RMB case option (b), had the datum references been |B|D|, would you say the OB (Outer Boundary) for datum feature D is a 360° ring?"

To which your answer was:

"It would not be 360 because D is what gets you going 100 kph to align with D."

That's why I thought that for the "B only" option, you were referring to something else. Now you say that the "B only" option addresses what I asked about (which is by the way not "[B(m}||D(m)]" but never mind that). And if so, you do consider the OB or MMB of datum feature D to be a ring shaped boundary, according to: "but the pin feature will be able to occupy anywhere in some ring shape. A fixture to accept all locations/orientations of the pin will require a circular trough for that side of the part", and your initial "not be 360" statement is to be disregarded. Am I interpreting you correct this time?

Quote (3DDave)

That requires the fixture to move to engage the cone relative to the pin and flat face and to control the orientation of the entire part. It cannot be a single rigid gauge.

The same applies to certain applications without customization of the DRF, such as the case in fig. 4-30 (a) in the '09 version. Thus, you see that the customization does something different from what the translation modifier is intended for.

If the frame of reference is [A|B] for the part then any feature using [A|B] will need a fixture that has 360 degree clearance for the pin to be located anywhere about the B-perpendicular-to-A axis.

If the frame of reference is [A|B|D] then any feature using [A|B|D] will have an oblong slot the for pin used as the D datum feature to fit into located from the B-perpendicular-to-A axis and not be 360.

The difference is that in the second case one has caught up with [D] and that has no dependency on the [C] feature - by which reference you caught up with C and saw the tangential movement allowed by the position tolerance. Catching up D means there is no longer tangential movement allowed - only the orientation remains. Since it is located from B, the radial position component remains - so it's a slot, but, because of the way they combine it's not a simple full rounded end slot.

In the example 4-30 the customized datum reference frame would be:
for RFS: [A[x,y,z,u,v]| B [w] ]
for MMC, since nothing moves there is no customize datum reference frame required.

Quote (3DDave)

If the frame of reference is [A|B|D] then any feature using [A|B|D] will have an oblong slot the for pin used as the D datum feature to fit into located from the B-perpendicular-to-A axis and not be 360.

I see that you avoid using the specific terms like I did in my question, but I conclude that you suggest that for an |A|B|D| referencing control, the outer boundary calculated in fig. 7-24 of the '18 standard, and likewise the RMB datum feature simulator for the external cylinder designated as datum feature D, should be an internal oblong. This so that the tangential direction of the outer boundary accounts only for the variation in size, form, and orientation of datum feature D relative to datum A, while the radial direction accounts for the position relative to A and B (and also includes the other variations).

If you are consistent with that approach, then if you were requested to consult a manufacturer designing a gage for a part he produces which is similar to the one from fig. 7-24 in the '18 standard (an RMB case), you would instruct him to build a custom datum feature simulator for datum feature D, that would be a contracting device with an oblong slot of adjustable size.

Correspondingly for the MMB case, it would be the fixed size oblong slot as you already showed in your calculation back on the day. By that you would ensure that the measurement method doesn't provide as much datum shift as allowed by the cylindrical datum feature simulator for a cylindrical feature as described in the standard.

Is that so?
If it is then I'm sorry, but I'm afraid you could get fired for such consultation, the way you suggested firing that vendor in a recent discussion.

Quote (3DDave)

In the example 4-30 the customized datum reference frame would be:
for RFS: [A[x,y,z,u,v]| B [w] ]

I don't know how you imagine that the cylindrical datum feature A can constrain 3 translational degrees of freedom, at least as long as everything applies in free state and the diameter is not chucked with force. Is that "z" addition the reason for the customized DRF? If not, what is the purpose of customization when everything else works exactly as it would by default?
The point with this example was that the customized datum reference frame from fig. 4-45, the one with the conical primary datum feature, does not work by implying translation of the datum feature simulators relative to each other in any way that differs from the behavior imposed by the default datum simulation rules for comparable cases. Yet, default degrees of freedom constraints are overridden.

This is significantly different from what is achieved by the translation modifier, which works by imposing an exception to the datum simulation rules that would otherwise apply, and doesn't necessarily override any default constraints. On the contrary, in the examples it is shown ensuring them.

Oh, you caught me. I was tired and added the z. Redo your analysis ignoring "z"

Quote (3DDave)

Is there any case of a customized datum reference frame that can properly be gauged without translating and/or rotating gauge elements? If they can translate they could be doing the same thing as the translation modifier

Quote (B)

Yes, there is one in the standard, the one with the conical primary datum feature giving away the axial translation constraint to the secondary.

Quote (B)

The point with this example was that the customized datum reference frame from fig. 4-45, the one with the conical primary datum feature, does not work by implying translation of the datum feature simulators relative to each other in any way that differs from the behavior imposed by the default datum simulation rules for comparable cases.

First, how honestly amazing you think that they created an example of a customized datum reference that had an identical interpretation as if they had not done anything at all.

Second, the "default" is for orientation and not location. There is a basic dimension required (not shown) to place that flat surface relative to the location where the apex of the cone should be and another from there to the hole. The hole true position axis is not parallel to the flat surface - it is perpendicular to the axis of the cone. The figure 4-30 rule doesn't apply.

---

How does the fixture feature for the pin affect the fixture feature for the hole for the MMB case - it wasn't part of the 4-16(b) calculation; why would it be added?

Quote (B)

By that you would ensure that the measurement method doesn't provide as much datum shift as allowed by the cylindrical datum feature simulator for a cylindrical feature as described in the standard.

Yes - that's the point - what is shown in the standard doesn't reflect what the restrictions placed on the features produces. I worry more about those who see a set of rules and then don't see an obvious problem with a propose interpretation that gives the wrong answer.

Still haven't asked a CAD guy to model it up for you have you?

Quote (3DDave)

Did I misunderstand "Side note: Although the gage pins B and C in fig. 4-8 in '94 would indeed be of fixed size, according to para. 4.5 3(d) the distance between them should be variable, and so the whole gage would not be that trivial anyway?"

That seemed to indicate the the MMC callout didn't require the distance to be fixed and therefore the gauge, as suggested, would not be trivial. Perhaps it was a short cut and was meant to be about the RFS version and that then 4.5.3(d) would apply - but that paragraph says nothing about translation.

The paragraph says that the TGC cylinders must only be oriented to each other, not oriented and located. This applies to both cases, RMB and MMB (RFS and MMC using the '94 terminology) and fig. 4-9 shows that.

Quote (3DDave)

I don't have 14.43; Did they put a fixed round pin into the square hole and call it good? Because the customized datum reference frame callouts implies that there should be square pin that fits with a cylindrical base into a hole so it can turn to allow motion to let datum feature C participate. If they moved it to all MMC/MMB references that avoids putting the datum feature C simulator on a slide to vary the center distance. It becomes a much easier gage with one rotating part.

The simulator B pin is indeed a square pin with a cylindrical pilot sticked into a hole in the base so that the pin can rotate around the axis of the pilot/hole. The simulator pin C is at fixed distance from the pilot/hole axis. However, the distance is fixed not because C has been referenced at MMB, but because in Y14.5-2009 they changed the default rule for the distance between the secondary and tertiary simulator from variable to basic. In other words, if C was referenced RMB (not MMB) and in absence of the translation modifier, the distance between B and C would also be fixed.

What I find interesting is that in the diagram in '1994 Figure 4-8 (b) is the indication of how the datum feature could be depicted to make clear that only the tangential control is being applied.

The interpretation that the distance isn't fixed I think was added in 1994, but I don't have access to the 1982 or 1973 versions to confirm. My recollection is that since requiring a fixed-boundary gauge to have moving parts is not what is reasonable except to CMM software sellers that this resulted in the 2009 reversal of that change and the adoption of the translation modifier. The customize datum reference construction is a superset of what translation does - there doesn't need to be both, though the translation modifier is a convenient short-hand.

If you write software you'll recognize that

i=i+1 gets tedious to write a few thousand times vs.
i++ or ++i, which also allow in-stream incrementing.

The translation modifier is a shortcut that does the same thing as i=i+1, but as i++. Yeah it's even more convenient, but, unlike i++, it isn't explicit as to what the effect is and then the reader has to go digging through the rest of the references to see what might be the case unless it's a trivial example.

And still, I'm left with the question - what designs demand rigid separation of features and have flexible/mobile mating parts that won't contact anything but the width (for example)?

It all seems a gift to CMM operators/software developers to not have to search for the optimum solution that fits the constraints and instead just removes the real problems of force-fits and interference.

Quote (3D)

I was tired and added the z. Redo your analysis ignoring "z"

What is there to redo? As I mentioned apart from the "z" your suggestion for customization of fig 4-30 (a), :"[A[x,y,z,u,v]| B [w] ]" didn't customize anything. The degrees of freedom are constrained by the primary and secondary datum references, exactly like in the original figure.

Quote (3D)

First, how honestly amazing you think that they created an example of a customized datum reference that had an identical interpretation as if they had not done anything at all

How is that an identical interpretation?
Unlike your customization of fig 4-30 (a) the customized DRF of 4-45 overrides the default constraints. If the DRF wasn't customized, A would constrain the z translation.

You are incorrect that the same rules that apply to fig. 4-30 (a) datum feature B do not apply to 4-45 datum feature B:

Quote (ASME Y14.5-2009 4.11.4)

(g) Secondary and Tertiary Surface RMB. Where the datum feature (secondary or tertiary) is a surface, RMB applied to the datum feature requires the datum feature simulator to expand, contract, or progress normal to the true profile of the feature from its MMB to its LMB until the datum
feature simulator makes maximum possible contact with the extremities of the datum feature while respecting the
higher precedence datum(s).

This is not a rule for rotation constraining datum references only.

Quote (3D)

How does the fixture feature for the pin affect the fixture feature for the hole for the MMB case - it wasn't part of the 4-16(b) calculation; why would it be added?

Please clarify. I was addressing your explanation of the (c) case (" If the frame of reference is [A|B|D]...") first RMB (2018 7-24) then MMB (2009 4-16, 2018 7-22), what effect of pin fixture to hole fixture did I suggest adding?

Quote (3DDave)

I worry more about those who see a set of rules and then don't see an obvious problem with a propose interpretation that gives the wrong answer

I worry more about those that reference a standard in a drawing and then expect that the rules are ignored at interpretation. Do you reference Y14.5 in your drawings? Are you aware of what shape a true geometric counterpart of a datum feature is supposed to have? The math in the standard is not wrong as long as it follows its own rules. You could suggest that the rules are wrong, but then good luck promoting your own "workable solutions" of making users derive oblongs from cylinders.

Should "allowed to have" be the same as "will be able to have"?

You ignored the geometry and have reverted to "the rules are the rules are the rules" again. That's not what the mathematics shows; you'll continue to be disappointed until you get your CAD guy to show you what is happening.

In 4-45 there is no boundary given that can move - more to the point, if that boundary were allowed to change, the location of the hole would not be constrained to the surface itself. One could say that anywhere along the shaft the hole was drilled that the surface could expand to reach that 24 mm dimension.

Anyway, "what size/shape is it" questions need to have a nice diagram - your CAD guy can help. I don't care to spend more time trying to figure out what you mean. I've shown you what I mean for this case; that's done.

Quote (B)

Specifically, Correspondingly for the MMB case, it would be the fixed size oblong slot as you already showed in your calculation back on the day. By that you would ensure that the measurement method doesn't provide as much datum shift as allowed by the cylindrical datum feature simulator for a cylindrical feature as described in the standard.

There would only be one cylindrical feature on the fixture - at the hole. So, make a nice diagram that shows the feature in some acceptable orientation and location that complies with the limitations allowed for that feature and how that diameter you like so much is appropriate in meeting the requirements in a different datum reference frame.

Quote (3D)

You ignored the geometry and have reverted to "the rules are the rules are the rules" again

You reverted to "the math is the math is the math" again, but ignored what any math is based on: definitions.
And the math shown in the figures is based on different definitions than you base your calculations on. You miss the context of the shown calculations and that is setting the sizes related to the datum feature simulator, which is defined by certain rules. It's not intended as a math exercise to describe some virtual limit of vector-directed translation variations, the way you seem to think.

If the analysis had to be such that it accounts for specific vector-directed constraints like radial and tangential, as opposed to the standard's consistent equal treatment of displacement at any direction on the XY plane as long as there are a YZ and XZ planes established in the DRF, then if there was a position control applied to the pin located at 29 basic from B axis referencing only the planar datum feature A as primary and hole B as secondary, then the diameter symbol for the tolerance of position would be inappropriate. The tolerance zone would need to be ring shaped, with the width of the ring as the tolerance value. But the tolerance zone is generally cylindrical for a pin, regardless of the constraints that apply, with some very specific exception cases described separately.

Quote (3D)

"what size/shape is it"
questions need to have a nice diagram - your CAD guy can help

Or, it could be covered by the definitions that you haven't learned. Your copy of the standard can help. But until you get to that, the word "counterpart" in the term "true geometric counterpart" may give you a clue. By the way, I am my own "CAD guy". I hope that not your entire understanding of tolerancing comes from making CAD simulations, as useful as they are.

Your approach seems to be just as practical as that custom-made datum feature simulator for the pin to be made with the uniformly contracting oblong slot to contain the cylindrical pin in the RMB case.
And If you were that consultant hired to aid the gage design for the MMB case, you would cause the part manufacturer to build a fixture rejecting parts which are acceptable by the designer's intent, and could be approved by the inspection team of any other vendor that may get the same job.

Quote (3D)

In 4-45 there is no boundary given that can move - more to the point, if that boundary were allowed to change, the location of the hole would not be constrained to the surface itself. One could say that anywhere along the shaft the hole was drilled that the surface could expand to reach that 24 mm dimension.

I don't know why you say all that. The "boundary" can't move, but the datum feature simulator is allowed some limited level of adjustment around the basic location from the apex, per the profile tolerance. And as you could have seen in the "means this" portion, the datum reference frame contains two planes derived from the primary cone and one plane from the planar shoulder face. The datum simulator B needs to engage with the actual face, and it does that according to the requirement to progress from MMB as described in the text which I quoted for you to learn from in my previous post. Simulated datum B can't travel away from the actual face to offset the hole's tolerance zone that is basically located from it.

Anyway, "what size/shape is it" questions need to have a nice diagram. I didn't see a diagram and you didn't ask the CAD guy. If you are a CAD guy who cannot make a diagram you need to take some classes. Why do you feel a wall of text is an answer to a geometry problem?

The diagram in the standard also didn't show a diagram of how they determined that number - same failure.

Finally - the boundary cannot move in the fixture without parts that translate. So the customized datum reference frame supports translation.

3D,
I agree that a CAD diagram with a bit of explanation is a good idea. I will soon post it in a separate dedicated thread.

Quote (3DDave)

Finally - the boundary cannot move in the fixture without parts that translate. So the customized datum reference frame supports translation.

That's the opposite conclusion to the one you should have made.
You've been clearly shown that the translation in the needed range for a secondary or tertiary planar datum feature simulator that has a location relationship to preceding datums, is perfectly within the default requirements, and not necessarily related to a customized datum reference OR the translation modifier.

And since the translation modifier is not intended to override default constraints of degrees of freedom, it would make no sense to try and replace it by using the customized datum reference frame for its applications.

Oh, not intended. Well, that settles it.

The translation modifier explicitly applies extra constraint(s) a datum feature simulator places on the motion of the part. The translation modifier is a special case of a customized datum reference frame and a customized datum reference frame makes explicit what a "default" requirement does by implication.

If you wanted to specify the datum feature simulator behavior shown in fig. 4-19 in the '09 standard by the customized datum reference frame, what would the customized datum reference frame tell the user that the regular and unmodified one doesn't?

Were I to write a computer program that read customized datum reference frames I could immediately parse the exact control required and would not depend on having to do an analysis of the relationship between portions of the part surfaces to figure out which directions might be allowed to control the motion.

You do understand the difference between "explicit" and "implied"?

Implied was the point of my question.
Having it explicit may help you get it:

The communicated requirement by a customized datum reference frame explicitly stating the constraints of degrees of freedom as shown in figure 4-19, would be exactly the same as the implied constraints of degrees of freedom by the datum references shown without any modification or customization in the related figure, 4-9. Therefore, It would impose the exact same datum simulation method shown in the "means this" portion of fig 4-9, with the basic spacing of 57.4 mm between the B and C datum feature simulators. It would in no way be equivalent to what is shown in the "means this" portion of figure 4-19, covering the special datum simulation method allowed by the use of the translation modifier; the adjustable spacing between the datum feature simulators.

You shift the argument from the one you lose to the one I didn't make. I understand why you do that.

Years ago I played against a chess program. When it got to the point where the only moves it could make would be forced moves, it claimed that those moves I would make to do that were not allowed. However, when I told the software to play from my position it immediately performed the move(s) it claimed were not allowed.

I've seen what your tactic is already.

I think you could benefit from being less focused on argument tactics, and more on the topic.

You've been saying all along that the translation modifier is redundant and everything it does could be achieved by the customized datum reference frame.
You've been just shown again that the translation modifier is not "a special case of a customized datum reference frame" but here we are again with you not willing to learn.

You haven't shown that.

I have.
But I guess "explicit" doesn't always work, either.

So apparently the explicit explanation (11 May 22 17:06) didn't work, although by saying "you haven't shown that" you don't point out what exactly you disagree with.
Nevertheless, you could try to look at it from another angle; the translation modifier is like the movable datum target symbol applied to datum features identified by only a datum feature symbol and not the datum target symbol. Is the movable datum target symbol redundant too?