Skip to content
A prototype wired onto a test board
  1. Conglomerado
  2. Calaa Lab
  3. Development
  4. Cal-1 Link

01.3

The software that lives inside the vehicle.

The software is on its own the moment the vehicle starts driving

The software inside the Cal-1 Link comes from this division. What sets this development apart from the other two is where it lives. A server sits in a room you can walk into; this software sits in a vehicle that is on a motorway today and has spent three weeks in a garage tomorrow.

01.3.1

The data is already collected, and it is collected in pieces

The diagnostic connector is effectively the same across every large market. Mandatory in the United States since 1996, in Europe since 2001 for petrol and 2004 for diesel, and elsewhere afterwards. A common set of parameters comes out of it, whatever the make and the country.

What comes out of it is collected today. The manufacturer collects it in its own connected vehicles, a fleet in its own through whatever device it fitted, an insurer in the ones it covers. Each keeps its piece, none follows the vehicle when it changes hands, and those on none of those lists are collected by nobody.

A vehicle's life, and who was watching it

Three collectors, and the gaps they leave between them

Any vehicle across its life. The stretches are illustrative and not to scale.

the manufacturer, in its connected vehicles
a fleet, through the device it fitted
an insurer, while it covers the vehicle
nobody is watching
registration
changes hands
changes hands
today

the vehicle's life

  • registration
  • changes hands
  • changes hands
  • today

A vehicle's life, and who was watching it

  • the manufacturer, in its connected vehicles
  • a fleet, through the device it fitted
  • an insurer, while it covers the vehicle

Select a collector to see which stretch it watches.

the vehicle's lifethe manufacturer, in its connected vehicleschanges hands

None of the three stretches survives a change of owner, and a vehicle on none of the three lists appears nowhere at all. The data that exists belongs to whoever was watching. What does not exist is a history that belongs to the vehicle and stays with it when it changes hands.

01.3.2

Four requirements that inside a vehicle are not taken for granted

None of the four is hard on a server. All four are hard inside a vehicle, and that is the brief.

  1. 01

    Reading the vehicle without interruption

    The same reading a workshop takes, and continuously

    A workshop reads the connector once, with the vehicle in front of it and the engine at its disposal. Reading it on the move, month after month and asking nothing of the driver, is a different job through the same port.

  2. 02

    Deciding on board what is transmitted

    With nobody on the other side to ask

    A moving vehicle emits far more readings than are needed. Which one travels is decided inside the device, because at the moment of deciding there may be no network to consult.

  3. 03

    Carrying on measuring without coverage

    A car park, a tunnel, a secondary road

    All three are ordinary places for a vehicle and poor places for a network. What cannot be sent is stored and leaves when coverage returns, without losing which moment each reading belonged to.

  4. 04

    Updating under regulation

    UNECE R155 and R156

    Both regulations require a cybersecurity management system and a software update management system across the vehicle's whole life. The European Union has required them of every new vehicle since July 2024. Outside the markets that require them, a product that already complies enters without being rebuilt.

A server and a vehicle

What a room takes for granted has to be built inside a vehicle

The four rows are the four above, seen through what each place guarantees.

What has to be doneA room takes for grantedInside a vehicle it demands
Reading from the vehicleThat the source answers when queriedReading while the vehicle is moving, asking nothing of the driver
Choosing what is transmittedThat there is someone to ask before decidingDeciding inside the device, with what it holds at that moment
Carrying on when the network failsThat the network returns within secondsStoring what cannot leave and sending it later, without losing when it was measured
Changing versionThat nobody regulates itTaking every change through R155 and R156, across the vehicle's whole life

None of the four is a feature added at the end. All four come from the same place, which is why none can be solved once the other three are built.

01.3.3

Both halves of the device belong to the same group

The object and the software come from two different places in the group, a company and a division. The split is put in writing exactly as if they were two unrelated suppliers, because each half has to answer for its own in front of a buyer. What changes is that both are designed knowing about each other from the start, instead of meeting once they are finished.

The boundary, in writing

What each half promises the other

The five commitments that cross between the two halves, with the arrow of who owes what to whom.

The object
The software
the joint between the two

The object · Calaa Robotics

  • That the port to read from exists
  • That there is power for as long as the vehicle supplies it
  • That the casing holds where it is mounted

The software · Calaa Lab

  • Not asking the object for more than it can give
  • Being able to change version without opening the casing

Select a commitment to see whose it is.

The softwareThe objectwhat crosses the joint

This list exists just the same between two suppliers who have never met. What changes is when it is written. Written at the end, any mismatch forces one of the two halves to be rebuilt. Written at the start, it is adjusted while both can still move.

01.3.4

The device reads and transmits, and does nothing else

It plays no part in driving and commands no vehicle system, and that line does not move to gain a feature. Which device is manufactured, and from which components, is decided by Calaa Robotics, who owns the object.

The port, in one direction only

The return lane has not been built

The two possible directions between a vehicle and a device connected to its port.

The vehicle
The device
readings from the standardised connector
nothing arrives in this direction
A command to the engine
A command to the brakes
Control over any other vehicle system

the lane that does exist

  • readings from the standardised connector

What would travel there if it existed

  • A command to the engine
  • A command to the brakes
  • Control over any other vehicle system

Select the lane to see what it carries.

readings from the standardised connectorThe vehicleWhat would travel there if it existed

A device that only reads can be verified by what it does not have. The return direction is not switched off by an option somebody could switch on. It does not exist, and that is what separates a promise from a property of the product.