2018 Frame Generator Issue/Bug

[SBix26]

I've discovered what I assume to be a bug in Inventor 2018.  If I try to create a Frame Generator frame in an assembly with the dimension display precision set to more than five decimal places, it fails:

Setting either or both of the linear or angular dimension display precision to more than five results in this error message.  Five or less for both allows normal FG creation.

I submitted a support case (13232084) for this on Thursday afternoon, got immediate response from EE "first responder", who turned it back over to Autodesk on Friday morning-- no response through the present moment.  I've stopped my regular work to track this down since then.  Maybe I should have started with the forum instead of tech support...

Sam B

Inventor Professional 2018.1
Vault Workgroup 2018.0
Windows 7 Enterprise 64-bit, SP1
Inventor Certified Professional

[salariua]

What is the length precision for that family in Content Center?

have you tried to copy it over to your library and change increment for the Length to 5 digit precision?

there's also this. but I don't find it helpful.

[salariua]

I am sure that's not the case but can you check if the Frame subassembly is "adaptive"? seem to remember a similar case had this issue.

[Mark.Lancaster]

@SBix26

I can reproduce this issue..  However I also got an odd response

When I changed the unit precision of the frame generator assembly that Inventor creates to 6 to 8 decimal places and leave the unit precision of the assembly hosting the frame generator model at 5 places.

And I'm using the same frame member that works when you leave the precision to 5 or less decimal places.

Update #2:  So the issue is related to the precision of the frame generator assembly that Inventor maintains.    When that sub-assembly is created by Inventor it carries over the precision of the top assembly.  If you open that sub-assembly and change its precision back to 5 or less, Frame Generator will create the frame members.

Paging @johnsonshiue

[SBix26]

@Mark.Lancaster, I'm seeing the same thing, and only for original placement from Content Center.  Editing placed members and re-using placed members is not affected, only placing new members.

@salariua, these structural members have no increment specified, so they are essentially infinitely variable within the given range.  And the frame subassembly is not adaptive.

Thanks for your verification and assistance.

Sam B

Inventor Professional 2018.1
Vault Workgroup 2018.0
Windows 7 Enterprise 64-bit, SP1
Inventor Certified Professional

[salariua]

Seems to be working on 2017... 

It's not related to which part in insert first. I have created a new simulation where I insert a "100mm" member then add one of "100.00001mm" and it still works

[SBix26]

2017 doesn't allow dimension display precision (Document Settings > Units > Linear Dim Display Precision) to be set more than five decimal places.  The problem occurs only in 2018, which allows that setting up to eight places.

Sam B

Inventor Professional 2018.1
Vault Workgroup 2018.0
Windows 7 Enterprise 64-bit, SP1
Inventor Certified Professional

[salariua]

I was wondering what @Mark.Lancaster was talking about! I could only see 5 digits max.

Issue found. so let's add @ChrisMitchell01 

[mercerc · Accepted solution]

Hi,

There is an issue in the Frame Generator when the precision of the assembly file is over 5 decimal places. It is only the assembly file or sub-assemblies created off that assembly.

If you need the assembly file precision to be over 5 decimal places one work around till it is addressed is to place just one frame member in the assembly with the file precision at 5 decimal places or lower. Once one member is placed you can increase the precision of the assembly file to what value about 5 decimal places you need.

This is presently being looked at thanks for bringing this to our attention. 

[Anonymous]

Cuál es la solución para este problema?

[johnsonshiue]

Hi! Please share an example (iam and ipt files) here so forum experts can help take a look.

Many thanks!