Chapter 01 · Meet the robot, then build its mathematical language
Today in the field story
One problem, then the next
The station manager marks the two parcel lanes on a desk grid, but a bare ‘5’ cannot tell the Parcel-Sorting Desk Robot where to place anything. Choose an origin, positive directions, and one unit, then predict and measure moves that cross zero. This gives yesterday’s hinge records and tool traces an honest numerical language instead of unexplained symbols.
- Why now
Every position, limit, error, and later transform depends on signed coordinates and compatible units.
- Ignore today
Ignore sensor uncertainty models beyond recording ruler resolution and an honest discrepancy.
- Unlocks next
Measured vectors, framed positions, and unit-safe robot messages.
Understand
Build the physical picture first
A bare number is an unfinished measurement; it becomes useful only after you say what it describes, its unit, and where zero and positive direction are.
A scalar is one number used to describe a quantity such as temperature, battery voltage, or link length. A variable is a name that can hold a value; it is not a mystery symbol. If x means rover position along a taped line, writing x = 30 cm says much more than writing 30. The equals sign says both sides describe the same quantity, not “now calculate an answer.”
A number line needs an origin, a positive direction, and a scale. Negative does not mean bad or physically impossible; it means the point lies opposite the chosen positive direction. On an x-y grid, an ordered pair (x, y) gives two signed coordinates relative to one origin and axis convention. The order matters: (−2, 3) and (3, −2) are different points.
Units are part of engineering meaning. The metre (m) is the SI base unit of length. A centimetre is one hundredth of a metre, so 30 cm = 0.30 m. Conversion must preserve the physical length even though the number changes. Add or compare quantities only after their units are compatible. Five centimetres plus two seconds is not a length because the quantities are different.
Measurements also have resolution and uncertainty, even if today you record only a simple estimate. A ruler marked every millimetre cannot honestly prove micrometre accuracy. A robot log should retain the original unit or convert at a clear boundary, name the frame, and avoid silent assumptions. These habits prevent errors that can look numerically reasonable while being physically wrong by a factor of 100 or 1,000.
Words you need
Name each idea precisely
- Scalar
A quantity represented by one number.
Physical example:Battery voltage = 12 V.
- Variable
A name assigned to a value or quantity that may change.
Physical example:x holds the rover's signed position on a line.
- Coordinate
A signed number locating a point along a named axis from a chosen origin.
Physical example:x = −20 cm means 20 cm opposite the declared +x direction.
- Origin
The location chosen as zero for a coordinate system.
Physical example:The lower-left tape mark on a work surface is defined as (0, 0).
- Physical unit
A standard that says what scale and kind of quantity a number uses.
Physical example:m for length, s for time, and V for electric potential difference.
Math, one line at a time
Work through today’s relationship
Prerequisite rescue · optionalStart at zero: counting, units, and coordinates
No maths is assumed. First give every robot number a physical meaning, a unit, a zero point, and a positive direction.
- N
- a count, such as number of jointsUnit: no unit
- x
- one position measured from a chosen zeroUnit: centimetres (cm) or metres (m)
- Δx
- change in x; Δ means changeUnit: same unit as x
Draw a number line. Put the origin at 0 cm, choose right as positive, and place the robot at x = 20 cm.
Move 30 cm right, so Δx = +30 cm. Predict x_new = 20 cm + 30 cm = 50 cm.
Measure to check, then convert with 100 cm = 1 m: 50 cm = 0.50 m. Never add centimetres directly to metres.
A variable is like a named field in code, but a robot field must also say its physical unit and what zero means.
A robot starts at x = 40 cm and moves 15 cm left. What is its new x coordinate?
Left is negative, so Δx = -15 cm and x_new = 40 - 15 = 25 cm.
A conversion multiplies by a value equal to one:
The centimetre labels cancel. In , is horizontal and is vertical relative to a chosen origin.
Predict and convert a rover position
A rover starts at x_start = −20 cm and moves Δx = +35 cm along the same axis.
Check that both values use the same origin, axis, and centimetre unit.
Write the relationship x_new = x_start + Δx.
Substitute the signed values: x_new = −20 cm + 35 cm.
Calculate x_new = +15 cm.
Convert by dividing centimetres by 100: 15 cm = 0.15 m.
Verify on a ruler that the point is 15 cm on the positive side of zero.
The predicted position is x_new = +15 cm = +0.15 m in the declared line frame.
Signs, units, origin, and axis are part of the answer, not decoration around the number.
Physical examples
Where this appears in real life
Shelf coordinate
A rail's centre is x = 0; a sensor sits at −25 cm and a stop block at +40 cm.
The signs describe opposite sides of the same origin while all three values remain lengths.
Motor-shaft drawing
A technician receives a 5 mm shaft dimension while software interprets the bare value 5 as centimetres.
The number matches but the physical size differs by a factor of ten, demonstrating why API fields need units.
Hands-on exercise
Make the idea observable
Use masking tape or squared paper, a ruler, five small objects, and a pen.
Mark an origin and label the positive x direction.
Place objects on both sides and record each signed coordinate in centimetres.
Predict five signed moves before sliding one object.
Measure each final position and compare it with x_new = x_start + Δx.
Convert every result to metres and keep the sign.
Record the smallest ruler marking so you do not claim finer precision.
The physical location stays unchanged during unit conversion while its numerical representation changes.
All five predictions include variable name, sign, unit, origin description, measured result, and any discrepancy.
Build today
Build a paper two-link robot and a browser notebook that shows its parts, allowed motion, coordinates, vectors, frames, and matrices.
Evidence to save
DONE when the integrated “Number lines, coordinates, scalars, variables, and physical units” path is observable, cancelable, and leaves the prior baseline reproducible.
Common mistakes
Catch the wrong mental model
Writing a position as the bare number 5.
Add the quantity name, unit, axis, origin, and frame needed to interpret it.
Dropping a minus sign during conversion.
Convert only the scale; the direction relative to the origin does not change.
Adding values with unlike dimensions or units.
Confirm the same physical quantity and convert to compatible units before arithmetic.
Reporting more precision than the measuring tool supports.
Record resolution and round the result to an honest level.
Job connection
How this becomes employable evidence
Define telemetry and mission fields with explicit metres, seconds, timestamps, and coordinate-frame names; reject incompatible or implausible values at the boundary.
Relevant target roles
- Robot HMI / Control & Monitoring Engineer
- Robot Fleet Backend / Platform Engineer
- Robotics Deployment, Integration & Validation Engineer
Chapter 01 interview drill
Interview questions: Number lines, coordinates, scalars, variables, and physical units
Practise a 60–90 second answer: define the idea, connect it to a physical robot, state assumptions, frames, and units when relevant, then finish with the failure signal or evidence you would inspect.
Primary interview scenario
A map UI shows a robot 100 times farther from the dock than reality. Describe how you would test unit, scale, origin, sign, and frame assumptions.
Answer shape: clarify the situation → trace the physical and software path → test the most likely boundaries → name the evidence that would confirm the result.
Technical follow-up questions
Q1Does −30 cm describe a negative distance?
It describes a signed coordinate 30 cm in the direction opposite +x; its distance from the origin is 30 cm.
Q2Why do 30 cm and 0.30 m represent the same length?
The metre is 100 centimetres, so dividing the number by 100 while changing the unit preserves the physical quantity.
Q3What information is missing from the coordinate pair (2, 3)?
At least the unit, named frame or origin, axis directions, and what physical point is being located.