Skip to main content
EVCore Studio is the desktop companion for the CS Harness EV Diagnostic Brick (EVCore). It runs tests on the device, keeps every result with its work order, vehicle, and customer, and produces the service report for the customer. The device owns test execution and safety; Studio only requests actions and records evidence.

Feature areas

Connection modes

Studio supports three ways to connect, selectable from the connection panel:
  1. In-app demo — synthetic signals and results for UI exploration and training. No device or firmware is involved. Simulated data is labeled on every screen and report.
  2. Firmware simulator — the real EVCore firmware running on this computer with simulated hardware, bridged via desktop/firmware-sim.cjs. This is the closest you can get to real device behavior without hardware.
  3. USB device — Web Serial with Studio’s own port picker. The firmware has no USB CDC stack yet, so this path has not been used with physical hardware, but the port picker and permissions are in place.

Guided job workflow

The guided job is a single screen that walks a technician through a complete service visit:
  1. Connect — choose a connection mode and confirm the device is ready.
  2. Identify the vehicle — select or create a customer and vehicle.
  3. Verify safe conditions — a checklist confirmed before every test.
  4. Test — select a test, confirm setup, run, and stop.
  5. Review — findings for the customer, with measurements against limits.
  6. Service report — generate a PDF with shop details, results, and a signature line.

Data storage and limits

Records are stored as files in the Studio user-data folder, written atomically with the previous version kept. A backup snapshot is taken automatically once a day. You can also trigger Back up now or Restore from Device & settings. Current limits:
  • 5,000 reports
  • 5,000 work orders
  • 5,000 customers
  • 10,000 vehicles

Current limitations

The plan to 1.0.0 is tracked in the 1.0 roadmap.
  • USB: the firmware has no USB CDC stack yet, so the USB path has not been used with physical hardware. The port picker and permissions are in place.
  • Live data: continuous telemetry and bus streaming exist only in the in-app demo, until the device protocol provides them.
  • Reports: test limits are illustrative fixture values until approved profiles exist.
  • Safety: the device must enforce every interlock itself. Closing Studio or losing the connection never confirms that outputs are off.