Palette:sickEngine
Summary
A sickEngine component launches a SICK TOP in a separate process so that more than one SICK sensor can be used in the same project.
If multiple SICK TOPs are used in the same project, only the first node to cook will activate. Therefore, each SICK sensor must run on a separate CPU process. To accomplish this, the sickEngine component is built on top of the Engine COMP which will allow a SICK sensor to run on an isolated process. This prevents sensors from clashing with each other even when accessed in the same project.
To connect to your first sensor, you can use a SICK TOP. If you need to run two or more SICK devices within the same project, load each additional device in a sickEngine component.
Note: It can be beneficial to always run SICK sensors in a sickEngine component even if only one sensor is used in the project. SICK sensors are tied to the life of the process it's instantiated in, so they are designed to start and stop with the process. It isn't reliable to restart the sensor without killing the main TouchDesigner process and restarting it as well. If you need to restart your sensor without restarting TouchDesigner, we recommend using the sickEngine component to load the sensor. However, Engine COMPs don't produce console outputs, so running a SICK TOP on the main process instead of a sickEngine component could be better for debugging purposes.
Parameters - SICK Page
Active - Activate the connection to the sensor.
Launchfile - A path to the launch file to configure the sensor. A valid launch file is necessary to connect to the sensor and to set advanced configuration options. Sample launch files for each sensor can be downloaded from SICK's website. This file must match the SDK version and model of your sensor. The SDK version can be viewed in the SICK TOP's info box by middle-clicking on the node.
Address - The IP address for the sensor. If this parameter is blank, the default address in the launch file will be used.
Port - The port number for the sensor. If this parameter is blank, the default port number in the launch file will be used.
Customargs - Additional arguments that should be included when initializing the sensor. This can be used to customize parameters for individual sensors while still using the same launch file. Arguments should be in the format "name1:=value1 name2:=value2".
Red - ⊞ - The name of the data field that will be assigned to the red component of the output image e.g. 'x'. The available fields will vary depending on the sensor and can be selected from the flyout menu to the right of the parameter. 'one' or 'zero' can be used to assign a constant value.
- Zero
zero-
- One
one-
Green - ⊞ - The name of the data field that will be assigned to the green component of the output image e.g. 'g'. The available fields will vary depending on the sensor and can be selected from the flyout menu to the right of the parameter. 'one' or 'zero' can be used to assign a constant value.
- Zero
zero-
- One
one-
Blue - ⊞ - The name of the data field that will be assigned to the blue component of the output image e.g. 'z'. The available fields will vary depending on the sensor and can be selected from the flyout menu to the right of the parameter. 'one' or 'zero' can be used to assign a constant value.
- Zero
zero-
- One
one-
Alpha - ⊞ - The name of the data field that will be assigned to the alpha component of the output image e.g. 'one'. The available fields will vary depending on the sensor and can be selected from the flyout menu to the right of the parameter. 'one' or 'zero' can be used to assign a constant value.
- Zero
zero-
- One
one-
Parameters - About Page
Help - Click to open this help page.
Version - The version of this component.
Toxsavebuild - The version of TouchDesigner that this component was saved in.
TouchDesigner Build: