User Profile Macro Inconsistency

[Anonymous]

Hello, I have created a series of User Profiles. I have inserted them in the railing, ladder, truss, purling, bracing, portal, stair macros in AstorRules. However only for "ladders" and "bracing" these profiles do not appear in the sections list (the "All" selection does not appear), while in the remaining macros (railing, truss, etc.) they are there. They are the same profiles for all so no typing mistake or incorrect input. Can anybody help? Thanks.

[johnjmbennett]

Hi,

assumed you use the GUI allowed sections table in astorrules,  along with the correct macro name. SEpurlin. SEbracing etc.

also if you add you user profiles to you preferred listing , it may be easier to see them in general, not have to keep looking under the all.

cheers

[Anonymous]

Thanks. Yes I am using allowed sections table in GUI AstorRules with the correct macro names, and user profiles are all the same. However only the ladder and bracing macros are not showing the "All" selection and therefore cannot use the user profiles, while the other ones created are working correctly.

Any ideas?

[johnjmbennett · Accepted solution]

Have you tried added them to the preferred section list under management tools?

[Anonymous]

Great, adding them to preferred worked. Thanks. If I can take a little of your time again.

Hopefully last queries for this matter:

- for cagedladder (stringers worked) is there the possibility of adding the user profiles also for the rungs?

- in "Portal/Gabel Frame" user profiles are present, but for "Mono-Pitch Frame" I cannot find them

Is there a specific reference in the astorrules for these?

[johnjmbennett]

Hmm, 

so for ladder rung try this approach: 

• open the management Tools and then the table editor--open the databases
• have a look for the AstorProfiles and search your profile in the ProfileMasterTable and copy the name of the column: Subtypename.
• this should something like "USR---the name you define"
• after this you could add here:  RULE_CageLadder_LadderUserRung in the column DefaultProfile

I found this in thread over adding a user rung, so credit to @Sebastian_Eiche  for posting that there

https://forums.autodesk.com/t5/advance-steel-forum/hexagon-shaped-ladder-rung/td-p/8672388

for the mono pitch portal,  i don't think there is a way to add it via the GUI allowed sections, from this AKN i found.

https://knowledge.autodesk.com/support/advance-steel/troubleshooting/caas/sfdcarticles/sfdcarticles/...

Cheers

[Anonymous]

Thanks, rung user profile solved!

Pity for the mono pitch portal.

Cheers.

[mick-CNF]

Find the user profile in the MT profilemastertable and put I in the subtypename column.

As you it looks like you cannot alter the orientation of the column in the macro you may have to rotate it when creating it.

[SMPConsulting]

@johnjmbennett 

Hi John,

Hey I'm having a similar issue after setting up user profiles for Australian Aluminium profiles. The profiles I have created so far are working fine however when I use the stair macro the profiles are not appearing in the macro.

Any suggestions....

[johnjmbennett]

Have you tried to add that new section to the GUI allowed sections table in the database, you need to create a line for the stair stringer element and then use the type name text entry for the profile type.

[SMPConsulting]

Thanks for that @johnjmbennett 

I'm new to coding up new sections in the library so can you recommend any resources on how to add new sections into the GUI macro, I had a look at the GUI Astor rule but wasn't quite sure how to add the new sections.

[b15063368]

This happens because Ladder and Bracing macros use stricter section filters than other macros in AstorRules.

Even if the profiles are correct, they will not appear unless they are explicitly allowed for ladder and bracing use.

What to check quickly:

• Make sure the profiles are enabled for Ladder and Bracing in the section/profile settings

• Verify the section family/type (angles, pipes, flats, etc.) is supported by those macros

• Check macro parameters for restricted section filters

• Restart AstorRules or refresh the section database