Robot-Vision Communication Protocol#

FlexiVision One communicates with the robot via TCP/IP protocol over an Ethernet network.

Protocol specifications#

Parameter

Value

Protocol

TCP/IP

Port

Configurable (default: FB1 → 4001 ; FB2 → 4002 ; FB3 → 4003)

Termination character

CHR(13) - Carriage Return

Data format

ASCII string

Timeout

Configurable (default: 5000 ms)

Encoding

UTF-8

Available commands#

The system supports the following commands via text strings sent over the TCP/IP connection.

Recipe management#

Command

Action

Return Value

set_recipe=<name>

Loads the specified recipe and starts synchronization of the connected FlexiBowl® units.

None

get_recipe

Returns the name of the currently loaded recipe.

<recipe_name>

Example:

set_recipe=MyRecipe

or:

get_recipe
→ MyRecipe

Locator commands#

Command

Action

Return Value

start_Locator

Starts the part-locating process. If no pickable parts are present, it automatically calls the FlexiBowl® movement routine. If the Locator is already active, the command is ignored and the process is not restarted.

Important

If no model is selected/enabled at the time the command is issued, the system returns an error message and the Locator does not start.

Pattern_n;x;y;r / Hopper;signalnumber;time

stop_Locator

Stops the locating process.

None

turn_Locator

If no part has been picked, it requests a new FlexiBowl® movement and restarts the search process.

Pattern_n;x;y;r

test_Locator

Starts the locating process without activating the FlexiBowl®; only image acquisition and search are performed.

Pattern_n;x;y;r / None

state_Locator

Returns the diagnostic status of the locating process.

Locator is Running / Locator is in Error / Locator is not Running

mix_Locator_<models>

Tip

For more information, see the section on mix commands

Dynamically selects one or more models and starts the Locator. Previously selected models are first disabled. Available numbers range from 1 to 8 (e.g. mix_Locator_12, mix_Locator_248, mix_Locator_12345678).

Note

If the Locator is already running, the command is ignored and the current selection is not changed.

Normal Locator result / #Error_mix_locator_not_valid (if no valid model is found)

Note

Other available string separators, besides ;, are: ,, |, :, &, $, @, #.

Note

For start_Locator and mix_Locator_<models>, when the Locator is already running, no response is sent to the robot.

How to correctly use the Start and Mix commands#

FlexiVision One supports two distinct application modes, depending on whether the FlexiBowl® is loaded with a single type of component or with several different components at the same time. The command to use depends on the application configuration: start_Locator and mix_Locator_<models> must never be used interchangeably within the same recipe.

Standard application – single component

In a standard application, only one type of component is loaded on the FlexiBowl®. The different models are used to recognize the different gripping faces of the same component, for example:

  • Model 1 = Component, gripping face 1

  • Model 2 = same Component, gripping face 2

  • Model 3 = same Component, gripping face 3

In this configuration, only start_Locator is used: the command automatically starts a sequential search across all the models created (first Model 1, then Model 2, Model 3, and so on). If no valid instance is found, the FlexiBowl® rotates and the search cycle restarts.

Important

In a standard application, mix commands (mix_Locator_<models>) must never be sent. The search across the different faces of the same component is already handled automatically by start_Locator.

Mix application – different components

In a mix application, several different components are loaded on the FlexiBowl® at the same time. Each model is associated with a specific component and/or one of its gripping faces, for example:

  • Model 1 = Component 1

  • Model 2 = Component 2

The corresponding commands are:

  • mix_Locator_1 → searches only for Component 1 (Model 1)

  • mix_Locator_2 → searches only for Component 2 (Model 2)

Unlike start_Locator, a mix command searches exclusively for the models indicated in the command number. To search for several models at the same time — whether they are different faces of the same component or different components — simply concatenate the relevant numbers, for example:

  • Model 1 = Component 1, gripping face 1

  • Model 2 = Component 1, gripping face 2

  • Model 3 = Component 2, gripping face 1

  • Model 4 = Component 2, gripping face 2

In this case:

  • mix_Locator_12 → searches for Models 1 and 2 at the same time (both faces of Component 1)

  • mix_Locator_34 → searches for Models 3 and 4 at the same time (both faces of Component 2)

Each mix command therefore searches only and exclusively for the models associated with that command, without extending the search to the other models in the recipe.

Summary

Application configuration

Command to use

Single component, with one or more gripping faces

start_Locator

Several different components loaded together

mix_Locator_<models>

Note

The two commands are not interchangeable: mix_Locator_12 does not behave like start_Locator and does not perform an automatic sequential search across all models — it only searches for models 1 and 2.

FlexiBowl® commands – Emptying#

Command

Action

Return Value

start_Empty

Starts the FlexiBowl® Quick-Emptying sequence. The command cannot be executed while the Locator is active.

Start_Empty Started / Locator is Running / #Error_flexibowl_not_connect

stop_Empty

Stops the FlexiBowl® emptying sequence.

Stop_Empty Command Sent / #Error_flexibowl_not_connect

state_Empty

Returns the current status of the emptying sequence.

Emptying Running / Emptying Stopped / #Error_flexibowl_not_connect / #Error_invalid_emptying_state

Control camera commands#

Command

Action

Return Value

start_control_<parameter>

Requests an inspection with the associated control camera. The <parameter> (text, optional) is forwarded to the VisionPro script, which decides which tools to run and which results to return. The trailing underscore of the prefix is mandatory.

Tip

For the command format, parameters and example exchanges, see start_control_ command.

String defined by the VisionPro script (e.g. X=125.450;Y=78.320;Rz=45.000 / Not_Found / #Error_Control_…)

Note

The start_control_ command is available from software version v0.24. The result is sent to the robot only if connected. For the #Error_Control_… and #Error_Camera… errors, see Troubleshooting – Control Cameras.

Optional hopper signals#

Note

If the hopper needs to be activated, the following string will be received: "Hopper;signalnumber;time"

General errors#

Note

FlexiVision license: if the software license is not active, robot commands are rejected and the following is returned: #Error_License_not_active


Advanced / Service Commands#

The following commands are reserved for technical personnel.

FlexiBowl® connection#

Command

Action

Return Value

connect_flb

Requests connection to the FlexiBowl®. If not connected, the related connection task is started.

#Flb1_connected / #Flb1_Not_connected


For detailed information on physical installation and electrical connections, proceed to the following sections: