Developer Settings

The Developer Settings subpage allows for the configuration of advanced options for the palletizer application. In order to navigate to the Developer Settings subpage, click on “Developer Settings” at the bottom of the Settings page.


Ensure you restart the snap package after changing any developer setting. Do so by running sudo snap restart jacobi-palletizer.

System Name

The system name uniquely identifies your Jacobi Palletizer configuration. It is used primarily for internal processes and logging purposes, so there is no need for user intervention or concern.


In this section, you can:

  • Choose between ‘Simulated’ or ‘Real’ for the robot driver and controller, defining how the system will operate in either a testing or real-life environment.

  • Specify the robot cell.

  • Set the robot host IP Address to establish the network connection.

  • Define pallet names. Misdefining these is a common source of bugs.


In this section, you can configure the following settings:

  • Automatic Clear Pallet: Whether to clear the pallet if it’s not present for a specified number of seconds. When this option is checked, you can configure the duration using Clear Pallet Duration.

  • Check Pressure Sensor: Whether to check the pressure sensor and trigger a fault if necessary.

  • Conveyor Control by PLC: Whether the conveyor is controlled using a PLC or robot controller

  • Fault on Area Scanner Triggered: Whether to trigger a fault if the area scanner is activated.

  • Gripper has Blowoff: Whether to enable blowoff for the gripper to allow for faster release.

  • Require Heartbeat Ping: Whether to require a heartbeat ping to ensure the system is responsive.

  • Sleep after Vacuum Change: The time to sleep after switching the vacuum on or off.

I/Os (Signals)

The I/Os section allows configuration of various input and output signals for the system. These include sensors, motors, and safety devices. Each I/O has a description, an alias field, and a toggle to activate it on a rising edge (1) or falling edge (0). The alias field for each signal must be configured according to the signals in the robot manufacturer’s programming software, such as ABB RobotStudio.


Signal aliases must match exactly the ones found in robot manufacturer programming software.