Got a problem? Post it!

Need help troubleshooting a PDMS problems? Post it and our members will help.

In 11.6.sp2  in Draft, when dimensioning steel, I try to tag element, and instead of it snapping to the TOS and start, or whatever the steel is justified by, it seems to only want to tag the NA at the midpoint of the sctn. And I cannot pick plines in draft either, I have to go back and dimension before and after the elements to get the right dims?  Whats up?

In Draft, the dimension point will usually default to the midpoint. To change it, change your PKEY and PKDIST attributes.

PKEY is the justification by default, the PKEY is set to NA.
PKDIST is the PROP.
[COLOR="Red"]PKDIST 0[/COLOR]  Dimension set to Start
[COLOR="Red"]PKDIST .5[/COLOR]  Dimension set to Midpoint
[COLOR="Red"]PKDIST 1[/COLOR]  Dimension set to End

Hope this is what you where looking for.

I thought that the plines would highlight, like ppoints do when dimensioning to them, there is no graphic response.  I'll try that tomorrow though.   I'm new to structural, but I thought the dim point would go to the origin of the member, depending on the justification, guess not...  I've been assumin' again...

Check your styf, if your plnpen is turned off you cannot pick plines in draft.  That will fix your problem

THE GURU HAS SPOKEN:cool:

Need help troubleshooting a PDMS problems? Post it and our members will help.

When inputing parameters into a variable in a method how do you make the variable output in the units in which you are working?  For instance if I set !x = para[1] on a member then output that variable it will be in mm.  If my units are inches and the output is 25.4, it interperts this as inches...not one inch.

Just saw your post JDRHOUSTON,  quick answer 'cause I'm outta here today..

The way I do it is throw a "mm" after calling the variable

example

!e = para[1]
by n $!e mm

I'm looking into creating a method applied to the real object, since the distance method doesn't work quite right, and I'll get back to you on that.

THE GURU HAS SPOKEN:cool:

OK. heres one. I dont seem to be able to get the TUBI OD?
the Pseudo attribute is AOD and LOD but this returns 0
LODIA is used for Components and doesn't work for TUBI.
This is required for a stress program.
Any idea's or does this require some code to get it to work?

OD of pipe is published as standard - up to 12" (ie 12"-12.75, 10"-10.75, 8"-8.625 etc etc). And after 14", the OD is same as the pipe size.

You can almost hard code this in your stress calculation problem and not worry about getting it from PDMS (unless it is API pipe, then you should go to API for standard OD of pipe).  

Of course the OD is available in Paragon, Para2 of the scom etc (depends on how the catalog is built), but why not go to the real source?

yes. thank you. must of been having a senior moment.
I came to me after wards getting for the catalogue so long as they are consistant with the catalogue. PARA 2 OF SCOM OF CATREF as you explain above. sometimes you can get so wrapped in in the trees you cant see the wood...so as to speak.