Skip to content
Piyush Verma
DEFIANZ / ENGINEERING NOTES / 04

Communication. Timing & packet loss.

A measurement is useful only if it arrives in time. Turn up delay or packet loss and watch the control computer’s view of the car fall behind.

0.0 / 30 S · 20 HZ PER NODE
Wheel speedWaitingNO PACKETSteeringWaitingNO PACKETBrake pressureWaitingNO PACKETIMU yaw rateWaitingNO PACKETAccumulatorWaitingNO PACKETControl stateWaitingNO PACKETCONTROL COMPUTER0 RXTIMESTAMP + SEQUENCE CHECKSIMULATED MEASUREMENTS / NO HARDWARE CONNECTION
CAN ID / SEQUENCEARRIVAL AGE

Start the network to inspect packets.

Packets sent0
Packets received0
Observed packet loss0%
Stale / missing nodes6 / 6
UNDER THE HOOD

What you’re seeing.

My work: socket-based CAN over TCP/IP communication across six nodes and HC-12 telemetry. The six signal names here are an illustrative allocation, not a recovered E16 network database.

This experiment: a seeded, discrete-event network with timestamps, sequence numbers, configurable latency, jitter and loss. It illustrates freshness, not CAN electrical arbitration, bus load or TCP retransmission. The packet-loss setting represents end-to-end missing updates; it is not a physical-layer error model.

Watch the distinction: receive rate and data freshness are different. A network can deliver every packet and still give the controller old information.

Educational reconstructions of ideas from my work. Demo results are computed here; they are not team test results.