# Plr & ot

**URL:** <https://discuss.pylabrobot.org/t/plr-ot/146>\
**Category:** General\
**Created:** [February 3, 2025, 2:01am UTC](https://discuss.pylabrobot.org/t/plr-ot/146 "2025-02-03T02:01:30Z")\
**Posts on this page:** 5\
**Page:** 4

<div class="post-metadata">

**Author:** ![koeng](https://discuss.pylabrobot.org/letter_avatar_proxy/v4/letter/k/4af34b/32.png) [@koeng](https://discuss.pylabrobot.org/u/koeng)\
**Post date:** [February 15, 2025, 8:55am UTC](https://discuss.pylabrobot.org/t/plr-ot/146/61 "2025-02-15T08:55:32Z")

</div>

> [@ben](#):
>
> seems like the best path, and could enable the OT-2 to be used in production long-term, even if you had the extra capital for STARs

Got it captain. I’ll try to do custom calibration.

btw, [this was the thing](https://x.com/koeng101/status/1890685582617047042) I was working on. It doesn’t take much of the imagination to see how PLR is important in realizing that dream!

---

<div class="post-metadata">

**Author:** ![rickwierenga](https://discuss.pylabrobot.org/user_avatar/discuss.pylabrobot.org/rickwierenga/32/963_2.png) [@rickwierenga](https://discuss.pylabrobot.org/u/rickwierenga)\
**Post date:** [February 25, 2025, 2:41am UTC](https://discuss.pylabrobot.org/t/plr-ot/146/62 "2025-02-25T02:41:39Z")

</div>

@koeng your server should work with the flex right? perhaps someone will need to pr some extra stuff eg for the arm

---

<div class="post-metadata">

**Author:** ![koeng](https://discuss.pylabrobot.org/letter_avatar_proxy/v4/letter/k/4af34b/32.png) [@koeng](https://discuss.pylabrobot.org/u/koeng)\
**Post date:** [February 25, 2025, 3:18am UTC](https://discuss.pylabrobot.org/t/plr-ot/146/63 "2025-02-25T03:18:49Z")

</div>

yeah it should work with the flex, but I have no way to check to verify.

Question on the coding side, just to confirm:

1. The API should just be locations (x,y,z in mm) with aspirate, dispense, pick\_up\_tip, drop\_tip, home
2. On the PLR side, where exactly do I define the deck layout?
3. The API should also have a calibrate function so we can make offsets for PLR to use. Offsets + deck layout + (internal PLR) labware == xyz positions, pass to API

---

<div class="post-metadata">

**Author:** ![rickwierenga](https://discuss.pylabrobot.org/user_avatar/discuss.pylabrobot.org/rickwierenga/32/963_2.png) [@rickwierenga](https://discuss.pylabrobot.org/u/rickwierenga)\
**Post date:** [February 25, 2025, 7:12am UTC](https://discuss.pylabrobot.org/t/plr-ot/146/64 "2025-02-25T07:12:28Z")

</div>

multiple people are interested in developing the Flex. Obviously not work for you to do, just wanted to double check that this approach works. I told them to use the forum when they get started.

> [@koeng](#):
>
> - The API should just be locations (x,y,z in mm) with aspirate, dispense, pick\_up\_tip, drop\_tip, home

yes (does home take a param at all?)

> [@koeng](#):
>
> - On the PLR side, where exactly do I define the deck layout?

Using the OTDeck class and the rest of the Resource model. Docs are here:

[https://docs.pylabrobot.org/resources/index.html](https://docs.pylabrobot.org/resources/index.html)

Unfortunately, I don’t think we really have a complete example for OT scripts. Briefly, you’d say

```auto
lh = LiquidHandler(backend=ot, deck=OTDeck())
plate = CellVis_96_wellplate_350uL_Fb(name="unique")
lh.deck.assign_child_resource(plate, slot=1)

```

> [@koeng](#):
>
> The API should also have a calibrate function so we can make offsets for PLR to use. Offsets + deck layout + (internal PLR) labware == xyz positions, pass to API

If we had some anchor on the deck (like the + sign on slot 1 iirc), we could use that for calibration of the OT itself. As long as that stays consistent (eg “ot move to +” doesn’t drift over time - it sounds like that’s the case), we should be able to manage the rest in the plr resource model.

---

<div class="post-metadata">

**Author:** ![rickwierenga](https://discuss.pylabrobot.org/user_avatar/discuss.pylabrobot.org/rickwierenga/32/963_2.png) [@rickwierenga](https://discuss.pylabrobot.org/u/rickwierenga)\
**Post date:** [October 3, 2025, 6:26pm UTC](https://discuss.pylabrobot.org/t/plr-ot/146/65 "2025-10-03T18:26:59Z")

</div>

for the record, I ended up implementing this in [fix Opentrons integration by rickwierenga · Pull Request #689 · PyLabRobot/pylabrobot · GitHub](https://github.com/PyLabRobot/pylabrobot/pull/689)

[Previous page](https://discuss.pylabrobot.org/t/plr-ot/146.md?page=3)
