Parse a DEX/UCS (EVA-DTS) audit file to extract machine identification, product, and sales records from a vending machine controller.

domain: vending-europe.eu · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Retrieve the raw DEX/UCS audit file from the machine (via handheld, DEX cable, or telemetry-delivered EVA-DTS/DDCMP file).
  2. Split the file into newline-delimited data segments, each starting with a 2-4 character block identifier (e.g., ID1, PA1, CA1) followed by asterisk-delimited data elements.
  3. Parse the ID1 segment for machine identification (serial number, model, build standard, asset number).
  4. Parse repeated PA1 segments (with associated PA5/PA7 detail lines) for per-selection product identifier, price, and vend counts since initialization/reset.
  5. Parse CA-series segments (CA1, CA2, CA9, CA10, CA16, etc.) for cash-in, cash-to-box, cash-to-tubes, overpay, and fill values.
  6. Validate each transaction set's CRC-16 integrity check before trusting the parsed values.

Known gotchas

Related routes

Map EVA-DTS audit-file fields (CA/PA/DA records) to a sales reconciliation report for a vending route.
vending-europe.eu · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans