Tires

You will be able to describe the tire positions of an asset, fit and remove tires, record tread depth and pressure, and see what each tire costs per distance. The Fleet screens arrive with the web console; until then you work through the API calls below.

Before you start #

• The dispatch_fleet license flag is on (Business plan, an add-on for Starter and Pro, included in the 14-day trial).
• The asset exists. Tire layout is set once per asset.
• Tire costs are entered in minor units of a currency, such as cents.

Steps #

1. Set the layout with POST /fleet/assets/:id/tyre-layout. Send axles, a list of 1 to 12 entries, each with steer and dual set to true or false. The answer lists the position codes. An asset that already has a layout returns conflict.
2. Add each tire with POST /fleet/tyres: serial is required. You can add brand, model, size, dot_code, starting_tread_tenth_mm, cost_cents, currency, purchased_on and vendor_id. A serial that exists already returns conflict.
3. Fit a tire with POST /fleet/tyres/:id/fit and a position_id. Add fitted_on to back-date it. The tire status becomes fitted, and the fitment keeps the asset's distance at that moment.
4. Look at what sits where with GET /fleet/assets/:id/tyres.
5. Remove a tire with POST /fleet/tyres/:id/remove. Send a reason: rotation, worn, damaged, puncture, retread, sold or other. It defaults to rotation. The fitment closes with the distance at removal.
6. To rotate, remove each tire with reason rotation, then fit each one to its new position. A rotation is a removal plus a fitment.
7. Record a check with POST /fleet/tyres/:id/readings: any of tread_inner_tenth_mm, tread_mid_tenth_mm, tread_outer_tenth_mm and pressure_kpa.

Positions #

A single axle has two positions: 1L and 1R. A dual axle has four: 2LO, 2LI, 2RI, 2RO (left outer, left inner, right inner, right outer). The number is the axle, counted from the front.

Status after a removal #

Units and thresholds #

Tread depth is stored in tenths of a millimeter and pressure in kilopascals (kPa), whatever units the people on your team see. A reading of 85 tenths means 8.5 mm.

Pop Dispatch ships no legal tread or pressure limits, because they differ by country and vehicle class. Alert thresholds are values your business sets for itself. With none set, a reading raises no alert. When you set them, the lowest of the three tread readings is compared with the minimum tread, and the pressure with your minimum and maximum.

Cost per distance #

A tire's cost per distance is its purchase cost over the distance it covered across all its fitments. An open fitment counts up to the asset's current odometer. A fitment with no odometer reading at one end counts as zero distance. With no distance yet, there is no figure. The cost shows per kilometer or per mile, by your business setting.

If something goes wrong #

• feature_not_licensed (403) or licence_read_only (403): the flag or license state blocks writes.
• conflict (409): the tire is already fitted, the position already has a tire (remove the old one first), the layout exists, or the serial is taken.
• validation_failed (422): axles is empty or longer than 12, reason is unknown, removed_on falls before the fitting date, or a reading has no tread and no pressure.
• not_found (404): the tire, position or asset does not exist.