×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Changing properties standard shape reference point location by API function .pval(51) in v10.3.1

Changing properties standard shape reference point location by API function .pval(51) in v10.3.1

Changing properties standard shape reference point location by API function .pval(51) in v10.3.1

(OP)
The default location of reference point for a standard shape in FEMAP is "1". I want to change it to other location by using the API function .pval(51) e.g. to point 7. I have tried using the command pr.pval(51) = 7 then, .ComputeStdShape, then pr.Put(ID) to update the properties. There is no error nor warning messages after running the script. But the reference point was not updated, still at location "1".

If the reference point was changed manually throught tge "Properties" dialogue box and then read the new value by using the function Msgbox "xxx: " & pr.pval(51), the new reference point location "7' was displayed.

If the command .ComputeStdShape was removed or .pval(51) was moved to a location after the .ComputeStdShape command, the reference point location was updated as expected.

Is it true that the command .pval(51) CANNOT be used before the command .ComputeStdShape?

RE: Changing properties standard shape reference point location by API function .pval(51) in v10.3.1

faremusai,

For future inquiries, please use the regularly monitored FEMAP forum found here:
https://community.plm.automation.siemens.com/t5/CA...

You are close - the issue is that you need to use "pr.Put( pr.ID )" BEFORE "pr.ComputeStdShape(...)". Otherwise, you have not updated the property with your new reference point and you will always be computing on the original, unchanged, property.

RE: Changing properties standard shape reference point location by API function .pval(51) in v10.3.1

(OP)
Thanks for the explanation.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources

eBook - Mastering Tolerances for Machined Parts
When making CNC machined parts, mastering tolerances can be challenging. Are general tolerances good enough? When does it make sense to call out for tighter tolerances? Do you need a better understanding of fits, datums, or GD&T? Learn about these topics and more in Xometry's new e-book. Download Now
eBook – How to Choose the Correct Corrosion Testing Method
When designing a metal component, engineers have to consider how susceptible certain alloys are to corrosion in the final product’s operating environment. In a recent study by NACE (National Association of Corrosion Engineers), it was estimated that the direct and indirect costs of corrosion in the United States is approximately 6.2% of the GDP. In 2016, that cost exceeded $1 trillion dollars for the first time. Download Now

Close Box

Join Eng-Tips® Today!

Join your peers on the Internet's largest technical engineering professional community.
It's easy to join and it's free.

Here's Why Members Love Eng-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close