Parameters

Parameters described here are additions or modifications to the standard Parameters. They can be used in production when working with a multi-feeding recipe.

Table 26 List of parameters

Parameter	Type [1]	Additional value	Valid value	Default value
multi_part_quantity	R/W	string	int	0
multi_n_parts_prepared	RO	string	int	0
multi_hopper_fill_ratio	RO	string	float	<none>

[1]

RO: Read Only; R/W: Read and Write

multi_n_parts_prepared

It returns the number of parts currently prepared for the given type (a, b, c or d).

This parameter takes a mandatory additional value corresponding to the part type (a, b, c or d).

get_parameter multi_n_parts_prepared a
200 1
get_parameter multi_n_parts_prepared b
200 2

multi_part_quantity

It is the number of parts of a specific type requested by prepare_part and get_part each time it takes an image. If this number of parts is not found during image acquisition, then the get_part or prepare_part will start again (vibration + image acquisition) until this number of parts is found.

This parameter takes a mandatory additional value corresponding to the part type (a, b, c or d).

Note

Refer to get_part to see how multi_part_quantity can be combined with different part types.

get_parameter multi_part_quantity a
200 0
set_parameter multi_part_quantity b 4
200
get_parameter multi_part_quantity b
200 4

multi_hopper_fill_ratio

This parameter returns whether a connected Asyfill smart hopper is empty (returns 0.0) or has some remaining parts in the container (returns 1.0) for a given part type (a, b, c or d). This parameter can only be requested during Production or Purge.

Tip

This parameter is particularly useful when used in Purge full scenario to check whether that your Asyfill smart hopper is empty before loading a new batch of parts, therefore preventing any mix-up of parts.

For this parameter to properly work, please note the following:

• An Asyfill smart hopper with firmware of at least version 1.2.0 is required.

• A hopper vibration of at least ~150 ms is needed. In case the Asyfill smart hopper did not complete a long enough vibration, an error 426 is returned instead.

Note

Depending on the part, this parameter might return a status of empty when the container still has some parts remaining. Usually, rigid parts and/or heavy parts are reasonably detected by the Asyfill smart hopper while soft parts and/or light parts can lead to an inferior detection.

# ... production scenario

stop production
start purge 123456

get_parameter hopper_fill_ratio a
200 1.0

purge full
200

# Depending on the response, you might want to perform a purge full again
get_parameter hopper_fill_ratio a
200 0.0