Inheco ODTC
This page gets you from an unboxed ODTC to a first temperature reading from Python. Inheco's manual covers plate types, method parameters, and safety.
What you need
| Item | Detail |
|---|---|
| Instrument | An ODTC 96, 96XL, 384, or 384XL, powered on |
| Network | Ethernet, on the same subnet as the GroundControl machine. If commands time out, see known quirks |
| Device serial number | The node name (ODTC_ plus 6 character serial number) from the device label |
| Connector | Inheco ODTC from the UniteLabs registry |
| Vendor software | None |
| Machine | Windows, Linux, or macOS running GroundControl |
| Access | A tenant and the SDK installed. See Setup |
Install and configure the connector
- In GroundControl, add a connector and pick Inheco ODTC (how to add a connector).
- Fill in the configuration. The fields that matter:
Field Value node_nameThe node name from the device label, e.g. ODTC_04E964. Always set it; the default is only an exampleip_addressLeave empty. Set it to the ODTC's IP address only if the connector can't find the ODTC by name simulatedfalsefor the real device (trueruns the connector's built-in simulator) - Start the connector. It waits until the ODTC reports
idle, resetting it first if it's in an error state. GroundControl then shows the modulesDeviceService,DoorController,MethodService, andTemperatureProvider.
First successful test
Read the device identity, its state, a set of temperatures, and the methods stored on it. This test does not move or heat up the device.
from unitelabs.sdk import AsyncApiClient
client = AsyncApiClient()
odtc = await client.get_service_by_name(name="Inheco ODTC")
print(await odtc.device_service.get_identification())
status = await odtc.device_service.subscribe_status()
async with status:
print(await anext(status))
temperatures = await odtc.temperature_provider.subscribe_temperature()
async with temperatures:
print(await anext(temperatures))
print(await odtc.method_service.get_method_names())
Expected:
- The identification prints the device name, serial number, and firmware version.
- The status prints
{'State': 'idle', 'Locked': ...}. - The temperatures print in °C, keyed
Ambient,Heatsink,HeatsinkTEC,Lid,LidMonitor,Mount, andMountMonitor.Mountis the block. - The method names print as 2 lists,
PreMethodsandMethods.
The SDK returns these as plain dicts with PascalCase keys.
Known quirks and errors
| You see | It means | Do this |
|---|---|---|
Startup fails with No ODTC devices were found at all | No ODTC answered discovery: it's off, on another subnet, or the network drops broadcasts | Check power and cabling, and that both are on the same subnet. Then set ip_address |
The configuration is rejected on node_name | It must be ODTC_ plus 6 characters, 0 to 9 and A to F | Copy it from the label, in capitals |
Commands time out with Timed out waiting for ResponseEvent | The ODTC reports finished commands back to the connector, and a firewall on the GroundControl machine blocks it | Set event_listener_port to a fixed port, e.g. 8090, and allow inbound TCP on it. On Windows the connector adds this rule itself when it runs with admin rights |
returnCode=4 | The ODTC is busy with another command | Wait until the status is idle |
returnCode=9 | The command isn't allowed in the current state, usually after an error | Run device_service.reset() |
start fails and the message names StartBlockTemperature | A method's start block temperature has to match the last pre-method's target, or the last method's end | Run the matching pre-method first |
Method '…' not found | No pre-method or method on the device has that name | Check get_method_names(). Names are case-sensitive |
start reports progress and finishes, but the ODTC is still running, or it finished earlier | start times progress and its own end from the method's estimated duration | Wait for the status to return to idle before the next step |
| A temperature or status subscription stops sending values | A poll failed, for example when the ODTC finished a command with a warning (returnCode=12), and the connector stops polling after the first error | Close the subscription, then open a new one |
More snippets
Open and close the door:
await odtc.door_controller.open()
await odtc.door_controller.close()
Create a method: a method runs from a starting block and lid temperature, and a pre-method
brings the ODTC to exactly those temperatures first. Upload both in a single MethodSet in Inheco's
XML format. This one holds 20 °C for 90 seconds, then cools to 4 °C and holds for 60 seconds, with
the lid at 105 °C.
method_set = """<?xml version="1.0" encoding="utf-8"?>
<MethodSet>
<DeleteAllMethods>false</DeleteAllMethods>
<PreMethod methodName="Demo-Pre" creator="labuser" dateTime="2026-10-28T12:00:00">
<TargetBlockTemperature>20</TargetBlockTemperature>
<TargetLidTemp>105</TargetLidTemp>
</PreMethod>
<Method methodName="Demo-Method" creator="labuser" dateTime="2026-10-28T12:00:00">
<Variant>960000</Variant>
<PlateType>0</PlateType>
<FluidQuantity>2</FluidQuantity>
<PostHeating>true</PostHeating>
<StartBlockTemperature>20</StartBlockTemperature>
<StartLidTemperature>105</StartLidTemperature>
<Step>
<Number>1</Number>
<Slope>4.4</Slope>
<PlateauTemperature>20</PlateauTemperature>
<PlateauTime>90</PlateauTime>
<OverShootSlope1>0.1</OverShootSlope1>
<OverShootTemperature>0</OverShootTemperature>
<OverShootTime>0</OverShootTime>
<OverShootSlope2>0.1</OverShootSlope2>
<GotoNumber>0</GotoNumber>
<LoopNumber>0</LoopNumber>
<PIDNumber>1</PIDNumber>
<LidTemp>105</LidTemp>
</Step>
<Step>
<Number>2</Number>
<Slope>0.18</Slope>
<PlateauTemperature>4</PlateauTemperature>
<PlateauTime>60</PlateauTime>
<OverShootSlope1>0.1</OverShootSlope1>
<OverShootTemperature>0</OverShootTemperature>
<OverShootTime>0</OverShootTime>
<OverShootSlope2>0.1</OverShootSlope2>
<GotoNumber>0</GotoNumber>
<LoopNumber>0</LoopNumber>
<PIDNumber>1</PIDNumber>
<LidTemp>105</LidTemp>
</Step>
<PIDSet>
<PID number="1">
<PHeating>60</PHeating>
<PCooling>80</PCooling>
<IHeating>250</IHeating>
<ICooling>100</ICooling>
<DHeating>10</DHeating>
<DCooling>10</DCooling>
<PLid>100</PLid>
<ILid>70</ILid>
</PID>
</PIDSet>
</Method>
</MethodSet>"""
await odtc.method_service.set_parameters_as_xml(params_xml=method_set, delete_all=False)
print(await odtc.method_service.get_method_names()) # Demo-Pre and Demo-Method are listed
Remember:
- Give the pre-method the same block and lid temperatures as the method's
StartBlockTemperatureandStartLidTemperature. Otherwise methodstartfails. - Leave optional attributes such as
descriptionout of the XML, or give them a value. The ODTC rejects empty ones, such asdescription="".
delete_all=False keeps the methods already on the ODTC. It does not override a
<DeleteAllMethods>true</DeleteAllMethods> in the XML.
Repeat steps: to loop, as in a PCR cycle, set GotoNumber on the last step of the loop to the step it jumps back to, and LoopNumber to the number of extra passes.
Run a method and watch the block: run the pre-method with the door closed, load the plate, then
run the method. start blocks for the method's estimated duration, so run it as a task and read
temperatures alongside it. Then wait for idle, since the device can still be busy when start
returns.
import asyncio
async def run_and_watch(name):
run = asyncio.create_task(odtc.method_service.start(method=name, priority=1))
temperatures = await odtc.temperature_provider.subscribe_temperature()
async with temperatures:
while not run.done():
reading = await anext(temperatures)
print(f"{name}: block {reading['Mount']} °C, lid {reading['Lid']} °C")
await run
status = await odtc.device_service.subscribe_status()
async with status:
while (await anext(status))["State"].lower() != "idle":
pass
await odtc.door_controller.close()
await run_and_watch("Demo-Pre")
await odtc.door_controller.open()
input("Load the plate, then press Enter")
await odtc.door_controller.close()
await run_and_watch("Demo-Method")
Read the trace of the last run: await odtc.temperature_provider.get_last_data() returns a
sample per time point, with target, block, and lid temperatures.
Manage methods: get_parameters_as_xml() returns everything on the ODTC in the same XML format,
delete_method(name=...) removes one, and delete_all=True on upload replaces them all.
Connector reference
Browse the connected instrument's modules and actions in GroundControl, or list them in Python with
print(odtc.method_service.actions.keys()).
Vendor documentation
Plate types, method parameters (slopes, overshoot, PID sets), and safety are in Inheco's ODTC manual.
Last updated