{"id":589,"date":"2016-12-11T02:11:18","date_gmt":"2016-12-11T10:11:18","guid":{"rendered":"https:\/\/blogs.plm.automation.siemens.com\/t5\/Tecnomatix-News\/Modeling-Kinematic-Devices-in-Simcenter-Motion-for-use-in\/ba-p\/379752"},"modified":"2026-03-26T06:55:54","modified_gmt":"2026-03-26T10:55:54","slug":"modeling-kinematic-devices-in-simcenter-motion-for-use-in-process-simulate-kinematics","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/tecnomatix\/modeling-kinematic-devices-in-simcenter-motion-for-use-in-process-simulate-kinematics\/","title":{"rendered":"Modeling Kinematic Devices in Simcenter Motion for use in Process Simulate Kinematics"},"content":{"rendered":"

This article was authored by Hans Kopp<\/STRONG><\/P>
\n

(please scroll to the bottom of the article for instructions on using the Process Simulate on Teamcenter Solve NX Kinematics<\/EM> command)<\/P>
\n

 Guidelines and best practices<\/FONT><\/H3>
\n

For this purpose, a kinematic device in Simcenter Motion must follow some rules, because Process Simulate can handle only a subset of the kinematic devices that you can create in Motion.<\/P>
\n

Note: \u201cSimcenter Motion\u201d is the motion application name, starting NX11. In older versions, the name is \u201cNX Motion Simulation\u201d.<\/P>
\n

 Supported types of simulations (Motion dialog box Environment<\/EM>)<\/H4>
\n

When you create a new simulation:<\/P>
\n

\"NewSim_button.png\"<\/span><\/P>
\n

  <\/P>
\n


    \n
  • Analysis Type<\/STRONG> must be Kinematics<\/STRONG>.<\/LI>
    \n
  • Component-based Simulation<\/STRONG> check box must be selected.<\/LI>
    \n<\/UL>
    \n

    \"EnvironOptions.png\"<\/span> <\/P><\/p>\n

    Process Simulate supports only a single kinematic definition per component.<\/P>
    \n

    Mechanism definition requirements<\/H4>
    \n

    There are no restrictions on the creation of links. Because the simulation is component-based, you can use only assembly components as link geometry.<\/P>
    \n


      \n
    • If an assembly component has its own kinematic definition, you can still use it as a link geometry of a parent kinematic.<\/LI>
      \n
    • You cannot use the child components of the component in the parent component.<\/LI>
      \n
    • Joints must be Revolute<\/STRONG> or Slider<\/STRONG> joints. Both types of joints must have both the Action Link<\/STRONG> and the Base Link<\/STRONG> defined. For Process Simulate, it does not matter which link is action and which is base.<\/LI>
      \n
    • The names of the joints must be alphanumeric, with the first character only alphabetical. Other characters are not supported by Process Simulate and will be replaced by the kinematic solver.<\/LI>
      \n
    • There must be one Fixed<\/STRONG> type of joint that connects one of the links to ground. This joint should define only the action link but no base link. The link that is marked this way will become the root link in Process Simulate \u2013 that is, the link that is fixed to ground.<\/LI>
      \n<\/UL>
      \n

      \"FixedJoint-cutdown.png\"<\/span><\/P><\/p>\n

      \"FixedJoint2-cutdown.png\"<\/span><\/P><\/p>\n

      Note<\/STRONG>: You can also connect a link to ground using a Revolute or Slider joint, but this is not the recommended workflow.<\/P>
      \n

      In general, the kinematic graph must be tree-like. The allowed exceptions to this \u2013 the cranks, are listed in section 4 below.<\/P>
      \n

      Exporting kinematic model to Process Simulate <\/FONT><\/H4>
      \n

        \n
      1. In the Simcenter Motion Navigator<\/STRONG>, select the Simulation<\/STRONG> node and select Export\/Process Simulate Kinematics<\/STRONG>. You must repeat this step for each device that you want to export. This creates a data set of type kinematics<\/STRONG> on the item revision of the device in Teamcenter.<\/LI>
        \n
      2. You must export the JT files for all the sub components of the device.<\/LI>
        \n<\/OL>
        \n

        To load the device in Process Simulate, assign the item revision of the device to a process and open this process in Process Simulate. For tree-like kinematics, no further steps are needed; the kinematics will be immediately usable (for example, in the joint jog).<\/P>
        \n

        The joint limits of the joints will be transferred.<\/P>
        \n

         \"JointLimits_transferred2-cutdown.png\"<\/span><\/P><\/p>\n

        Exporting cranks <\/FONT><\/H4>
        \n

        Process Simulate supports the import of the most frequently used crank types.<\/P>
        \n

        When creating a kinematics with cranks in Simcenter Motion, you must verify that the crank types are supported by Process Simulate (see Supported types of cranks<\/EM> below). Otherwise, it will not be possible to move the kinematics in Process Simulate.<\/P>
        \n

        In addition, you must define the driving<\/EM> joint for each crank to be exported. The driving joint is the joint that should be jogged in Process Simulate. The other joints of the crank will be dependent on the driving joint.<\/P>
        \n

        To define the driving joint in Simcenter Motion, create a joint Driver for a single joint of the crank. The type of driver and the parameters of the driver are not used by Process Simulate.<\/P>
        \n

        \"CreateJointDriver.png\"<\/span><\/P>
        \n

        Note:<\/STRONG> The export of the driver is available only since NX11. If the kinematic should be created with NX 9 or NX 10 then Process Simulate will use that joint as driving joint the joint name of which comes first in the alphabet. Upper case letters are considered to be before lower case letters here. Thus if there are e.g. the joints with names \u2018a1\u2019, \u2018C1\u2019, \u2018b1\u2019, \u2018D1\u2019 in a crankthen the joint C1 will be used as driving joint. If a wrong driving joint is selected the crank might not be solvable as the crank type is not supported.<\/P>
        \n

        Apart from the information listed above, the creation and the export in Simcenter Motion is the same as for tree-like kinematics.<\/P>
        \n

        Importing cranks in Process Simulate<\/FONT><\/H4>
        \n

        The import of a kinematics with cranks requires an additional manual step in the import to Process Simulate. After loading the kinematic device to Process Simulate, you must run a solve for the cranks.<\/P>
        \n

        To do this, customize the command Solve NX Kinematics<\/STRONG> in a ribbon, select the imported device, and run the command. The command (described in detail below) will analyze the kinematic and solve all cranks of the kinematic. If the kinematic cannot be solved, an error message is displayed.<\/P>
        \n

        When solving the kinematic, the kinematic graph is transformed into a tree. You cannot export this transformed tree back to Simcenter Motion.<\/P>
        \n

        Supported types of cranks<\/FONT><\/H4>
        \n

        The following crank types are supported by the kinematic solver in Process Simulate. Both the driving joint and the fixed link must correspond to one of the pictures below. In each picture, the arrow indicates the driving joint and the dashed link represents the fixed link.<\/P>
        \n

        RRRR<\/EM><\/P>
        \n

        \"RRRR-crank.png\"<\/span><\/P><\/p>\n

        This is a crank with four rotational joints, all of which have the same joint direction. The driving joint is connected to the fixed link. <\/P><\/p>\n

        RPRR<\/EM><\/P>
        \n

        \"RPRR-crank.png\"<\/span><\/P><\/p>\n

         This is a crank with a single prismatic joint and three rotational joints. The prismatic joint is the driving joint. The fixed link is not connected to the prismatic joint.<\/P>
        \n

        PRRR<\/EM><\/P>
        \n

        \"PRRR-crank.png\"<\/span> <\/P><\/p>\n

        This is a crank with a single prismatic joint and three rotational joints. The prismatic joint is the driving joint. The fixed link is connected to the prismatic joint.<\/P><\/p>\n

        RRRP<\/EM><\/P>
        \n

        \"RRRP-crank.png\"<\/span><\/P><\/p>\n

        This is a crank with a single prismatic joint and three rotational joints. A rotational joint is the driving joint. The fixed link is connected to both the prismatic joint and the driving joint.<\/P><\/p>\n

        Compound cranks<\/H4>
        \n

        You can combine the crank types above into compound cranks. With compound cranks, you can create kinematic structures with two or more kinematic cycles that share a single joint and two links. Only one crank of a compound crank can have a driving joint. For the other cranks, the shared joint will become the driving joint.<\/P>
        \n

        Here an example of a combined RPRR and RRRR crank \u2013 a three-point crank.<\/P>
        \n

        \"Combined-crank.png\"<\/span><\/P><\/p>\n

        A kinematics can have multiple cranks that do not share a common joint, but share only a link or do not share any elements.<\/P><\/p>\n

          <\/P>
        \n

        The Solve NX Kinematics command in Process Simulate on Teamcenter:<\/H3>
        \n

        You can import the kinematics of an equipment from NX Motion to Process Simulate on Teamcenter. First it is necessary to export the assembly’s NX Motion kinematics and JT files to Teamcenter and them import them with Process Simulate.<\/P>
        \n

        After loading to Process Simulate, the application automatically reads this equipment – if the kinematics did not contain any cranks (kinematic cycles), the device can be used right away.<\/P>
        \n

        If it does contain cranks, you can try and solve the device by selecting the node and using the Solve NX Kinematics \"SolveFromNX-icon.png\"<\/span> <\/STRONG>command. This is necessary in order to enable using Joint Jog and other commands for the device. To see if a device contains cranks, you can open the Kinematics Editor for it \u2013 cycles in the graph indicate that you need to solve the kinematics:\"Crank_from_NX.png\"<\/span><\/P><\/p>\n

        Notes:<\/P>
        \n


          \n
        • Make sure that devices are not in modeling mode when using the Solve NX Kinematics <\/EM>command.<\/LI>
          \n
        • After fixing the device’s kinematics in the Kinematics Editor, use the End Modeling<\/EM> command and then perform Teamcenter Update<\/EM>.<\/LI>
          \n
        • The command supports multi-selection or selecting a compound node to solve all devices under it. An informative message displays in the event that the command did not solve the device or If problems occurred.<\/LI>
          \n
        • You can customize the command as needed.<\/LI>
          \n<\/UL><\/p>\n","protected":false},"excerpt":{"rendered":"

          This article was authored by Hans Kopp
          \n (please scroll to the bottom of the article for instructions on using the Process Simulate on Teamcenter Solve NX Kinematics command)
          \nGuidelines and b…<\/p>\n","protected":false},"author":56405,"featured_media":629,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[1],"tags":[],"industry":[],"product":[],"coauthors":[],"class_list":["post-589","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news"],"featured_image_url":"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/7\/2019\/09\/Crank_from_NX-1.png","_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/tecnomatix\/wp-json\/wp\/v2\/posts\/589","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/tecnomatix\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/tecnomatix\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/tecnomatix\/wp-json\/wp\/v2\/users\/56405"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/tecnomatix\/wp-json\/wp\/v2\/comments?post=589"}],"version-history":[{"count":14,"href":"https:\/\/blogs.sw.siemens.com\/tecnomatix\/wp-json\/wp\/v2\/posts\/589\/revisions"}],"predecessor-version":[{"id":630,"href":"https:\/\/blogs.sw.siemens.com\/tecnomatix\/wp-json\/wp\/v2\/posts\/589\/revisions\/630"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/tecnomatix\/wp-json\/wp\/v2\/media\/629"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/tecnomatix\/wp-json\/wp\/v2\/media?parent=589"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/tecnomatix\/wp-json\/wp\/v2\/categories?post=589"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/tecnomatix\/wp-json\/wp\/v2\/tags?post=589"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/tecnomatix\/wp-json\/wp\/v2\/industry?post=589"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/tecnomatix\/wp-json\/wp\/v2\/product?post=589"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/tecnomatix\/wp-json\/wp\/v2\/coauthors?post=589"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}