IMPORTANT: <\/strong>TM Component is not designed for confidential encapsulation. Do not use TM Component in confidential usage.<\/p><\/blockquote>\n A component can consist of a variety of features to make the flow structure simple as well as reusable in other projects. TM Component Editor provides developers with a complete mechanism to create components. Among the nodes, the Start node<\/strong> can configure the component\u2019s basic parameters such as display icon, usage, global variables, and its instruments. Moreover, developers are able to provide users to modify the parameters on demand. To help users to understand the usage scenarios of the developer\u2019s component quickly, TM Component Editor manages a naming rule.<\/p>\n Developers can click on the Start node for basic settings. In the basic settings, Provider is the name of the developer, Name, and Type stand for the name and the type of the node respectively, and Icon is the image to represent the component. In addition, TM Component Editor can pack available Global Variables and instruments together into the component, and show the results in the branches of the Gateway<\/strong> node.<\/p>\n Step #1: Create a new project and tick ‘Component Editor’, project name naming rule is introduced below.<\/p>\n Component Naming:\u00a0<\/strong>The naming rule of TM Component Editor goes by\u00a0Application_Provider_Model_Version_Function<\/strong><\/em>. IMPORTANT: <\/strong>Do not use reserved words such as var in naming.<\/p><\/blockquote>\n Step #2: The component is created successfully, fill the settings on the right Component Edit panel. Details are listed below.<\/p>\n IMPORTANT: The component\u2019s icon supports PNG image files only, and the suggested maximum resolution is 73 x 73 pixels to avoid distortion or blur.<\/p><\/blockquote>\n Global Variables Naming This item sets the branches of the component. Developers have to select a Gateway node as the exit of the component and the possible results branch over the Gateway node exits according to the logic. Users can process the flow with the respective programs provided by the developers. Click ‘Save…’ and click ‘OK’. The component can be imported\/export to other devices.<\/p>\n In TM Component Editor, you can edit the devices in advance, such as F\/T Sensor devices, Modbus devices, Network devices, and embed the devices in the Component. The supported devices of TM Robot will be covered one by one below.<\/p>\n Users can set the parameters of the Modbus TCP\/RTU devices and have the devices embedded in the Component. By dragging the Component in TMflow to have a Modbus device added, users can configure the Modbus device in the list at the right of the screen.<\/p>\n Users can add a new network device newly added by the Network node embedded to the Component. Dragging the Component in TMflow will add a Network device.<\/p>\n Users can have the parameters of communication and physics in the force-sensing devices embedded in the Component. By dragging the component in TMflow, users can merely configure the serial port address to match the actually connected address for making use of the Component established with the device in the flow. If DeviceReadOnly is checked, users of the component will be limited to use the developer set devices.<\/p>\n Once you have completed the Component programming, you can export the Component to various projects or make the Component available to others. The following goes through how to open the Component and use it in the Project Page as well as how to make it available to others.<\/p>\n Navigate to NOTE: <\/strong>Components created in newer versions of TMflow are not applicable to older versions of TMflow.<\/p><\/blockquote>\n When selecting the Gateway node as the exit in TM Component Editor and clicking save, TMflow will create a component with the project. In the meantime, users can activate the created Component in the Component List by navigating to The Component should come out as a node on the left node panel. Below is an example of successful imported components.<\/p>\nStart creating your first component<\/h1>\n
TM Component Editor settings<\/h2>\n
Start node<\/h3>\n
\nName\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 Description & Examples
\nApplication <—>\u00a0 \u00a0GRIPPER
\nProvider\u00a0 \u00a0 \u00a0 <—>\u00a0 \u00a0TechmanRobot
\nModel\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 <—>\u00a0 \u00a0Adaptive
\nVersion\u00a0 \u00a0 \u00a0 \u00a0<—>\u00a0 \u00a0V001
\nFunction\u00a0 \u00a0 \u00a0<—>\u00a0 \u00a0GRIP<\/p>\n![\"\"](\"https:\/\/www.tm-robot.com\/wp-content\/uploads\/2021\/05\/component-1-e1622014543762-1024x562.png\")
<\/p>\n![\"\"](\"https:\/\/www.tm-robot.com\/wp-content\/uploads\/2021\/05\/component-2.png\")
<\/a><\/p>\n\n
\n
\nThe prefix of a Global Variable has to be the first two names (Application_Provider_) of the project name in TM Component Editor. Inappropriate naming of Global Variables may result in existing Global Variables being overwritten.<\/p><\/blockquote>\nSelect Exit From Gateway nodes<\/h3>\n
<\/a><\/p>\nNode Setting<\/h3>\n
\n
<\/a><\/p>\n\n
<\/a><\/p>\nSave Component<\/h3>\n
<\/a><\/p>\nDevices<\/h2>\n
Modbus Devices<\/h3>\n
Network Devices<\/h3>\n
Force Sensing Devices<\/h3>\n
Using Your Component<\/h1>\n
Import\/Export Components<\/h2>\n
<\/a>–> System –> Import\/Export to export the component to the USB driver labeled with TMROBOT and import the component onto the users\u2019 TM control box and make it available to users.\u00a0 Procedures can be found here<\/a>.<\/p>\nOpen the component<\/h2>\n
<\/a>–> Setting –> Component, choose imported components and click ‘Save’. <\/a><\/p>\n