Embedded validation hardware

Electron eins

Demonstration unit
Readiness: Available for demonstration
Production unit
Readiness: In production development

Two units, two states. The demonstration unit is what we can connect and show you now. The production unit is still in development.

A desktop test unit that connects to an electronic control unit (ECU) on your bench, so an engineer can run tests at their own desk.

Testing a control unit usually means booking time on a shared test rack. Work queues behind whoever has the rack, and a test that takes an hour can wait a week for a slot.

Electron eins is small enough to sit on a desk. It connects to your PC on one side and to the control unit under test on the other, and it runs the test suites your team writes in Validative Software Studio.

Starting fromNeedsstarting price and currency (EUR, INR or both) — from Gok

What the hardware enables

Bench testing without a full test rack

A desk unit does not replace a large hardware-in-the-loop (HIL) rig. It removes the wait for one.

  • Testing at your own desk

    The unit sits beside the PC an engineer already works on. Nothing to book, no bench time to negotiate with another team.

  • Work stops queueing

    A shared rack is one point of contention for a whole team. With a unit each, two engineers can test the same afternoon.

  • The same suites, unattended

    Automated tests written in Validative Software Studio run against this unit, so a check can run while the engineer does something else.

Hardware configurations

What exists, what is in development, what is planned

Three things are described on this page and they are not at the same stage. Each one is labelled, so nothing here has to be taken on trust.

  • Readiness: Available for demonstration

    Demonstration unit

    The unit we can connect to a control unit and show working — online, or at our engineering lab in India. Its connectors are the ones described below.

    • Two CAN connections, on D-Sub 9 connectors
    • Two D-Sub 15 input and output connectors
    • USB and Ethernet to the PC
    • 12 V supply in, 12 V supply out to the unit under test
  • Readiness: In production development

    Production unit

    The unit intended for series supply. It is where fault injection and current measurement live, on the production circuit board. It is in development and cannot be ordered yet.

    • Fault injection and current measurement on the production board
    • In development — not available to order

    Needsconfirmation of public dates for the production unit — from Gok

  • Readiness: Planned

    Input and output expansion cards

    Cards that add input and output channels to a unit, for an application that needs more signals than a unit carries on its own.

    • Planned — not available today
    • Not part of either unit above
Electron eins test unitUSBEthernet2 × CAN on D-Sub 92 × D-Sub 15 input/output12 V supply outYour PCValidative Software StudioElectronic control unit(ECU) under test12 V supply inCAN = controller area networkYour PCValidative Software StudioElectron eins test unitUSB and Ethernet to the PC2 × CAN on D-Sub 92 × D-Sub 15 input/output12 V supply in12 V supply out to the ECUElectronic control unit(ECU) under testCAN = controller area network
DiagramWhat connects to what: the test unit sits between your PC and the control unit under test. The drawing labels the connectors only — channel counts are not shown, because they are not verified.

Vehicle bus

Two CAN connections to the control unit

CAN, the controller area network, is the bus most vehicle electronics communicate on. Electron eins provides two CAN connections, each on a D-Sub 9 connector.

That is the connection a test uses: send a message to the control unit, then read what the unit sends back.

  • 2 × CAN
  • D-Sub 9 connectors
  • Available on the demonstration unit

CAN FD

Readiness: Planned

CAN FD, the faster version of the same bus, is planned for the next-generation unit. It is not available on the unit described here, and we are not quoting it as though it were.

Input and output

Two input and output connectors

Beside the bus connections, the unit has two D-Sub 15 connectors for input and output (I/O) — the individual signals around a control unit, rather than the messages carried on the bus.

We have deliberately not published a channel count or a list of signal types for these connectors, and we have not stated that analogue input or output is present. Those figures are not verified yet, and a number on a web page is read as a specification.

  • 2 × D-Sub 15 connectors
  • Available on the demonstration unit

Send us the signals you need to drive and measure, and we will tell you what the unit covers.

Needsverified input/output count and types behind the two D-Sub 15 connectors, and whether analogue input/output is present — from HW lead

Fault injection and current measurement

Faults that cannot safely be created in a vehicle

Readiness: In production development

A control unit has to behave safely when a wire breaks, a signal line shorts or the supply drops away. On a bench those conditions can be created on purpose and repeated exactly. In a vehicle most of them cannot be created safely at all.

Fault injection and current measurement belong to the production circuit board (PCB), not to the demonstration unit. The board is in development. We will describe what it does — which faults, on which lines, over which ranges — once its function test has passed, and not before.

Needsconfirmation that the fault-injection and current-measurement function test on the production circuit board has passed, and what it covers — from HW lead

Connectivity

USB and Ethernet to the PC

The unit connects to the PC that runs Validative Software Studio over USB and Ethernet. That is the path the test and its results travel on.

The device under test (DUT) — your control unit — is wired to the connectors on the other side, and takes its 12 V supply from the unit so a test can control when it is powered.

  • USB to the PC
  • Ethernet to the PC

Supported applications

What teams use a desk unit for

Three kinds of work, all of which otherwise wait for a shared bench to come free.

  • ECU bench testing

    Connect a control unit, send messages on the bus, check the responses. The everyday work of validating a control unit, done at a desk.

  • Early software validation

    A new software build can be tested the day it is produced, instead of waiting for a slot on a rack. A fault found early is the cheapest one to fix.

  • Demonstrations and training

    A desk unit with a control unit connected is the simplest way to show how a test runs, whether in a review or when a new engineer is learning the bench.

For engineers

Technical specifications

Only verified values appear in this table. A row without one is a figure we have asked for internally and not yet had confirmed — it is not an omission for brevity.

The interfaces above are the ones we are willing to put in writing today. Channel counts, electrical ratings and dimensions follow the verified specification sheet.

Unit

Model tag
RVU-01

Power

Supply input
12 V
Supply to the unit under test
12 V

Interfaces

Vehicle bus
2 × CAN, on D-Sub 9
Input and output
2 × D-Sub 15 connectors
To the PC
USB, Ethernet

Dimensions

Needsdimensions values — from Gok
Needsverified Electron eins specification sheet — dimensions, electrical ratings, and input/output count and types — from HW leadNeedsElectron eins datasheet PDF — the download is hidden until it exists — from Gok

Next step

Tell us what you need to test.

Send the control unit, the bus and the signals involved. We will tell you what a desk unit covers today, what the production unit adds, and where a custom test rig is the better answer.

Send your requirements