AI Software. Industrial Confidence.

[root@edge-01:~/dosing-skid]# ./target/release/oasis-agent

[pack] modbus capability pack registered (ModbusRead, ModbusWrite)

[pack] opc ua capability pack registered (OpcUaBrowse, OpcUaRead, OpcUaWrite)

[pack] ethercat capability pack registered (EtherCatScan, EtherCatIdentify, EtherCatSdoRead, EtherCatSdoWrite)

  ██████╗  █████╗ ███████╗██╗███████╗
 ██╔═══██╗██╔══██╗██╔════╝██║██╔════╝
 ██║   ██║███████║███████╗██║███████╗
 ██║   ██║██╔══██║╚════██║██║╚════██║
 ╚██████╔╝██║  ██║███████║██║███████║
  ╚═════╝ ╚═╝  ╚═╝╚══════╝╚═╝╚══════╝

        ❯ agent cli   // made by mutexer

oasis-agent v0.14.2+g8f21ac0 · model: magnum-1 · endpoint: http://10.8.0.23:8080 · cwd: /srv/dosing-skid

modules   [✓] PREEMPT_RT   [✓] Modbus   [✓] OPC UA   [✓] EtherCAT   [✓] IEC 61131-3

type /help for commands, /exit to quit · Tab completes · Shift+Tab switches permission mode · \ or Alt+Enter for a newline · Ctrl+C cancels

› the skid on eth0 is new. tell me what is on it, then start the master.

▾ EtherCatScan · {"interface":"eth0","subdevices":3,"not_in_op":3,… · 1 lines · 22ms

  ╰ {"interface":"eth0","subdevices":3,"not_in_op":3,"faulted":0,"latency_ms":3.368635,"positions":[{"position":0,"al_state":"init","al_error":false…

Three SubDevices, all in init. No master has claimed them yet, so nothing is energised.

▾ ModbusRead · {"unit":1,"point":"holding:4012","values":[1847,423]… · 1 lines · 12ms

  ╰ {"unit":1,"point":"holding:4012","count":2,"values":[1847,423],"latency_ms":12,"budget_ms":250,"map":"config/dosing.map.json"…

▾ OpcUaRead · {"node_id":"s=Skid.Interlock","value":false,"quality":"Good"… · 1 lines · 31ms

  ╰ {"node_id":"s=Skid.Interlock","value":false,"quality":"Good","source_timestamp":"2026-08-24T09:14:11Z","security_policy":"Basic256Sha256"…

Level 1847 mm, 42.3 °C, interlock clear. Now the master. The skill is explicit that these tools observe a segment and the application is the master, so I will read it before writing anything.

▸ Skill · # Building an EtherCAT control application · 255 lines · 0ms

  │ # Building an EtherCAT control application

  │ 

  │ The tools in this harness **observe** a segment. The application you are about

  ╰ … +252 more lines · /expand t-4

The skill puts one decision ahead of the rest: what the target image carries. This board has no ec_master module and never loads one at boot, so it is ethercrab, and the edition has to come down to match the toolchain that is actually on the device.

✎ /srv/dosing-skid/Cargo.toml +5 −1

@@ -1,7 +1,11 @@

 [package]

 name = "dosing-master"

 version = "0.1.0"

-edition = "2024"

+edition = "2021"

 [dependencies]

+ethercrab = "0.7"

+futures-lite = "0.3"

+tokio = { version = "1", features = ["rt-multi-thread", "macros"] }

+anyhow = "1"

That is the manifest. Cycle time is yours to set and I am not going to pick it for you: the sync manager watchdog window follows from it, and getting it wrong faults the segment rather than slowing it down.

← turn done · 31.6s · ctx 28.4k/228.6k 12% · 1.2k new + 0.6k out · 3 model calls