Skip to end of banner
Go to start of banner

Import from gripper.json

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Choose this option only if you have a special gripper with one or more vacuum channels and a file in the robot home folder called "gripper.json" that contains the geometry and the corresponding IO settings for the gripper.

In order to have this functionality working, the position and the dimensions of the bounding rectangle should be defined for each vacuum zone as well as the digital output channels that control the vacuum valves and optionally the compressed air used at release.

See example further down

The file has the following structure:

name: name of the gripper

description: a short description of the gripper

picture: an optional picture in PNG format, encoded as a base64 string

dimensions:

  • width, length, height: total dimensions of the entire gripper

  • weight: weight of the gripper including mounting bracket and screws

  • foamHeight: the height of the foam / suction cups that can be pressed down

properties:

  • edgeAlignment: if true, the box edges will be aligned to the gripper zone edges, otherwise the gripper zone(s) will be centered above the box center

    • coveragePercent: defines how many percents of the vacuum zone (bounding rectangle) area must be covered in order to use a specific zone

tcp: the tool center point (TCP) of the gripper as [x, y, z, rx, ry, rz]

cog: the center of gravity (COG) of the empty gripper as [x, y, z]

zones: definition of each individually controllable vacuum area

  • id: unique identifier (number) of the vacuum area, starting from 1

    • x, y: center point of the bounding rectangle relative to the gripper center

    • width, length: size of the bounding rectangle

    • grip: digital IO signal that controls the vacuum

      • type: standard, configurable, tool (robot IO type)

      • channel: the digital output channel (0-1 for tool 0-7 otherwise)

      • inverse: true if high level signal means no vacuum

    • release: digital signal that controls the compressed air (optional)

configurations: list of valid combinations of vacuum areas that can be used together 

(Lengths are specified in millimeters, weight in kilograms.)

Name the greated json file “gripper.json“

Example

The following diagram is an example of a 4-channel suction-cup gripper with its corresponding gripper.json file. The different colors indicate different groups of suction cups that can be controlled together.

 

{
  "name": "4-channel gripper",
  "description": "test gripper for multiple product sizes"
  "dimensions": {
    "width": 400,
    "length": 200,
    "height": 150,
    "weight": 1.9,
    "foamHeight": 15
  },
  "properties": {
    "coveragePercent": 51,
    "edgeAlignment": false
  },
  "tcp": [0, 0, 150, 0, 0, 0],
  "cog": [0, 0, 0],
  "zones": [
    {
      "id": 1,
      "x": 0,
      "y": 0,
      "width": 134,
      "length": 201,
      "grip": {
        "type": "standard",
        "channel": 0,
        "inverse": false
      },
      "release": {
        "type": "standard",
        "channel": 4
      }
    },
    {
      "id": 2,
      "x": -163,
      "y": 0,
      "width": 67,
      "length": 201,
      "grip": {
        "type": "standard",
        "channel": 1
      },
      "release": {
        "type": "standard",
        "channel": 5
      }
    },
    {
      "id": 3,
      "x": 163,
      "y": 0,
      "width": 67,
      "length": 201,
      "grip": {
        "type": "standard",
        "channel": 2
      },
      "release": {
        "type": "standard",
        "channel": 6
      }
    },
    {
      "id": 4,
      "x": 0,
      "y": 0,
      "width": 527,
      "length": 67,
      "grip": {
        "type": "standard",
        "channel": 3
      },
      "release": {
        "type": "standard",
        "channel": 7
      }
    }
  ],
  "configurations": [ 
    [1,2,3,4], [4], [1,2,3], [1,2], [2,3], [1], [2], [3] 
  ]
}

Copy the above code and use as a template. Name the created file “gripper.json“

Note: TCP settings are optional and may not be included in older gripper.json files. If your gripper is mounted with a position/rotation offset, make sure that the offset is properly set according to the specification in 5.1.3 - Attach the gripper properly


  • No labels