Build, run and understand every test

Connect your hardware and tools, set pass/fail rules that run on the machine, and review every run in the cloud.

1. Get started

   Install Computer, connect a first input, learn the words the docs use.

   • What is Phloem
   • Install
   • Your first input

   Connect a computer to your workspaceSign in from Phloem Computer and approve in your browser, or enrol a headless machine with phloem device enrol for an admin to approve.
2. Connect data

   Streams, recordings and your own code: every reading becomes a named channel.

   • Inputs
   • Live streams
   • Files & recordings
   • Send your own data
   • Name channels and units
   • Pipelines
   • Assets

   Verify that your data is arrivingConfirm an input is producing samples, see its channels on Live, and check whether its data has reached the cloud.Replay a recordingLoad an MCAP file or a ROS 2 bag, pick its topics, and scrub through it on Replay with the same channels a live run produces.Stream from a PLC over ModbusInstall the Modbus connector, point it at a PLC over TCP or RTU, and map its registers to named channels with units.Send readings from a Python scriptOpen a Push endpoint input and run a Python script that posts readings to this device, where they appear as live channels.Decode a CAN bus with your DBCRead a live CAN bus or a candump log and decode every frame into named signals with your own .dbc file.Scale a raw signal into engineering unitsCalibrate a channel with a line, a polynomial or a certificate table, check it against the live reading, and share it across channels.Add footage and line it up with your dataImport a recorded video clip as a camera channel, pinning one frame to the instant it shows on your data.
3. Run tests

   Trellis rules run on the machine: stop on a limit, drive outputs safe, alert someone.

   • Trellis
   • Declare reads and writes
   • Stop conditions
   • Interlocks
   • Alerts
   • Procedures
   • Acceptance recipes
   • User page
   • Notebooks
   • Run your own scripts
   • Peers

   Stop a test when a reading goes out of rangeAdd a limit to a channel so the test stops and every output goes to its safe value the moment a reading crosses it.Get a Slack message when a limit is crossedRoute a Trellis alert to a Slack channel, so crossing a limit posts a message without stopping the test.
4. Review results

   Replay any run, mark what happened, chart it onto a dashboard.

   • Live
   • Replay
   • Runs
   • Marks
   • Charts and dashboards
   • Export data

   Mark an event and find it laterTag a moment or a range in Replay with a name, then filter and jump back to it from the tags list.Chart a run and pin it to a dashboardHave Hamming chart a run, save the chart onto a new or existing dashboard, and open it in the console with fresh data.Open a run in Excel or pandasDownload a recorded run as CSV for Excel or Parquet for pandas, then open it. Files past one Excel sheet continue in parts.
5. AI

   Ask Hamming about a run, trace a change through your tools, and connect your coding tools.

   • AI
   • Hamming
   • Trace
   • MCP for coding tools

   Ask Hamming about a test runAsk Hamming why a run failed or how it compares to others, and get an answer built from the run's own measurements and data.

Workspace

• ProjectsA project holds your inputs, calibrations, pipelines, Trellis documents and layouts. Save versions, share them as profiles and load them on other devices.
• Devices and fleetsConnect a computer or a headless server to your workspace, stay within your plan's device limit, rename or revoke a device, and group devices into fleets.
• Members and plansInvite people, set who is an Admin or a Member, switch workspaces, create API keys for CI, and see what your plan allows.
• Cloud sync and working offlineWhat works with no network or no sign-in, how captures wait on disk and catch up, choosing what to send, and checking what reached the cloud.
• Where your data livesFind, browse and query what your devices send to the cloud. It all lands in Reservoir, in one of four tables chosen by what the channel is, not which input…
• RetentionChoose how long the cloud keeps recorded data, once for the whole organization, in Reservoir → Settings → Retention.
• AI providerWho serves Hamming's models — Phloem managed, or on Enterprise your own Vertex AI, Azure AI Foundry, Amazon Bedrock or API key.
• AI usage and limitsEach plan includes monthly AI credits for Hamming. What a credit is, what happens when they run out, and where your workspace's usage shows.