|
| 1 | +--- |
| 2 | +nosearch: true |
| 3 | +--- |
| 4 | + |
| 5 | +# Camera calibration for PDS |
| 6 | + |
| 7 | +The PDS application always returns the position of an object with respect to the calibrated coordinate system. Typically, the calibrated coordinate system corresponds to the fork tines, so that the coordinate system will go up and down with the forks and the pallet position will always be provided with reference to the current position of the forks. |
| 8 | + |
| 9 | +## Concepts |
| 10 | +### PDS coordinate system |
| 11 | +PDS expects the orientation of the coordinate system to be as follows: |
| 12 | +- X is pointing in direction of the forks, |
| 13 | +- Y is pointing to the left of the forks, |
| 14 | +- Z is pointing up. |
| 15 | + |
| 16 | +When uncalibrated, the camera coordinate system is such that Z is pointing away from the camera, and X is pointing away from the cables. This is represented in the image below: |
| 17 | + |
| 18 | + |
| 19 | + |
| 20 | +The uncalibrated coordinate system does not correspond to what PDS expects. Consequently, if no calibration is set, PDS will raise an error. |
| 21 | + |
| 22 | +To fit the expected coordinate system of PDS, the coordinate system has to be rotated. An example of a correctly calibrated coordinate system would be as shown in the image below, where the origin of the coordinate system is placed at the center of the base of the forks: |
| 23 | + |
| 24 | + |
| 25 | + |
| 26 | +Note that the user can decide where to place the origin of the coordinate system. We show a couple of examples [below](#examples). |
| 27 | + |
| 28 | +PDS will look for a pallet within a defined volume of interest. By default, it expects the camera to be placed at approximately the same level as the bottom plane of the pallet. |
| 29 | +For more details about the volume of interest for the different PDS commands, refer to their respective documentation. |
| 30 | + |
| 31 | +Note that errors in the camera calibration will lead to errors in the position of the targeted object. If CAD data is known to be precise enough, it can be used to extract calibration values for the camera. Otherwise, any of [the calibration methods](../../CalibrationRoutines/index_calibrations.md) provided by ifm can be used. |
| 32 | + |
| 33 | +### Robot Coordinate System |
| 34 | +PDS' coordinate system will most often be different from the Robot Coordinate System (RCS): |
| 35 | +- The RCS is usually in a fixed position on the robot's chassis, whereas PDS' coordinate systems moves with the forks. The transformation between the RCS and the PDS coordinate system will depend on the position of the forks and has to be implemented by the user. |
| 36 | +- The RCS is typically in the middle of the steering axis, whereas PDS' coordinate system is located around the forks base or tip. |
| 37 | +- In general, the axis of the RCS and the PDS coordinate systems will be parallel. The X axis of the RCS usually points in the direction of travel, and PDS' coordinate system X axis points in the direction of the forks, which would typically be towards the back of the vehicle. The Z axis will point upwards in both coordinate system. |
| 38 | + |
| 39 | +:::{note} |
| 40 | +Note that these comments represent most typical use cases, but your coordinate system might be different. The coordinate system can be adjusted to fit your specific setup. |
| 41 | +::: |
| 42 | + |
| 43 | +## Examples |
| 44 | + |
| 45 | +### Tip of fork coordinate system |
| 46 | +Let's take for example a camera mounted horizontally, looking straight ahead, directly between the two forks. |
| 47 | +Let's assume the fork tines coordinate system's origin is at the tip of the right fork, like shown in the image below: |
| 48 | + |
| 49 | + |
| 50 | +Let's also assume the following measurements: |
| 51 | + |
| 52 | + |
| 53 | + |
| 54 | +Then, the values for the rotation and translations are as follows, shown in the Vision Assistant calibration wizard: |
| 55 | + |
| 56 | + |
| 57 | + |
| 58 | +This is equivalent to setting the following parameters in the relevant port's JSON configuration: |
| 59 | +```json |
| 60 | +{ |
| 61 | + "ports":{ |
| 62 | + "portX":{ |
| 63 | + "processing":{ |
| 64 | + "extrinsicHeadToUser":{ |
| 65 | + { |
| 66 | + "rotX": 0.00, |
| 67 | + "rotY": 1.57, |
| 68 | + "rotZ": -1.57, |
| 69 | + "transX": 1.00, |
| 70 | + "transY": 0.25, |
| 71 | + "transZ": 0.05 |
| 72 | + } |
| 73 | + } |
| 74 | + } |
| 75 | + } |
| 76 | + } |
| 77 | +} |
| 78 | +``` |
| 79 | + |
| 80 | +### Base of forks coordinate system |
| 81 | + |
| 82 | +Let's take another example and assume the camera is mounted horizontally pointing forward, directly between the two forks, and the origin of the coordinate system is at the base of forks, right between the two forks, as shown in the image below: |
| 83 | + |
| 84 | + |
| 85 | +Let's assume that the center of the coordinate system is 5 cm below the camera, and on the same (YZ) plane: |
| 86 | + |
| 87 | + |
| 88 | +With these measurements, we would have the following calibration values: |
| 89 | + |
| 90 | +This is equivalent to setting the following parameters in the relevant port's JSON configuration: |
| 91 | +```json |
| 92 | +{ |
| 93 | + "ports":{ |
| 94 | + "portX":{ |
| 95 | + "processing":{ |
| 96 | + "extrinsicHeadToUser":{ |
| 97 | + { |
| 98 | + "rotX": 0.00, |
| 99 | + "rotY": 1.57, |
| 100 | + "rotZ": -1.57, |
| 101 | + "transX": 0.00, |
| 102 | + "transY": 0.00, |
| 103 | + "transZ": 0.05 |
| 104 | + } |
| 105 | + } |
| 106 | + } |
| 107 | + } |
| 108 | + } |
| 109 | +} |
| 110 | +``` |
0 commit comments