pylabrobot.formulatrix.mantis.driver.master.MantisDriver.__init__#

MantisDriver.__init__(*, device_id: str | None = None, io: FTDI | None = None, rfid_io: FTDI | None = None, name: str = 'Mantis', declared_configuration_json: str | None = None, oem_config_directory: str | None = None, ftdi_library: str | None = None, show_actions: bool = True)#
Parameters:
  • device_id (str | None) – the FTDI serial number. None uses the first Mantis found.

  • io (FTDI | None) – an already-built FTDI for interface B, used instead of building one.

  • rfid_io (FTDI | None) – an already-built FTDI for interface A, the RFID reader. None builds one for device_id, unless io is given: then there is no RFID reader.

  • name (str) – the device name, heading its log messages.

  • declared_configuration_json (str | None) – a file save_configuration wrote. Setup refuses a device that disagrees with its device block on what is fitted (FITTED_FIELDS).

  • oem_config_directory (str | None) – the unit’s vendor Data/Device/Configs folder, read at every setup.

  • ftdi_library (str | None) – “libftdi” or “d2xx”, for both links; None picks D2XX on Windows when FTDI’s D2XX library loads, else libftdi. Ignored for a link given as io or rfid_io.

  • show_actions (bool) – whether the v4’s LED bar shows each action’s colour, and the idle animation between actions; False shows the idle animation from setup on.

The unit’s own values (UNIT_BLOCKS) come from oem_config_directory and the declared file; where both have a block, they must agree. A unit block or non-fitted device field the declared file lacks comes from the folder, else the generation’s recording (another unit’s values, less accurate on this one), with one warning naming each and where it came from; a motion calibration (MOTION_CALIBRATION_BLOCKS) never comes from a recording.