Skip to content

Close-Range Proximity and Safety Sensors for Low-Speed AVs

Last updated: 2026-05-09

Low-speed autonomy still needs a safety-rated near-field layer. Long-range LiDAR, cameras, radar, occupancy grids, and learned perception help the vehicle understand the scene, but they are not a substitute for a certified protective field around people, pallets, aircraft, docks, forklifts, trailers, and building edges. The near-field layer should be simple, monitored, and hard for the main autonomy stack to bypass.

The core architecture is a safety controller that receives safety-rated scanner, bumper, edge, and proximity inputs; selects protective fields based on vehicle speed and direction; and directly commands safe stop or speed limitation. The autonomy stack can consume this state for planning, but it should not be able to mask a protective stop.


AV, Indoor, Outdoor, and Airside Relevance

DomainClose-range hazardDesign implication
Generic AVPeople or objects can enter blind spots below perception sensor height or inside braking distance.Use independent near-field protective sensing tied to the safety controller.
Indoor warehousePallets, racks, glass, dock plates, forklift tines, and pedestrians are close to the vehicle path.Combine safety laser scanners with ultrasonic, edge, and bumper coverage for blind zones.
Outdoor campus and yardRain, fog, sunlight, dust, trailers, curbs, and mixed manual traffic affect detection.Use outdoor-capable scanners or sensor fusion; validate fields in weather and contamination.
AirsideGround crew, aircraft fuselage, tow bars, belt loaders, fuel trucks, cones, and jet blast debris are near the vehicle.Add field sets for docking, stand maneuvering, wing/fuselage clearance, and apron transit.

Architecture

Safety laser scanners / safety radar / ultrasonic / tactile bumpers
        |
        v
Safety I/O or safety network (OSSD, safety relay, PROFIsafe, FSoE, CAN safety)
        |
        v
Safety PLC / safety MCU
        |
        +--> Field-set selector from speed, direction, steering mode, load state
        +--> Safe-speed and safe-stop logic
        +--> Diagnostics and muting/service-mode policy
        |
        +--> Brake / drive enable / safe torque off / E-stop chain
        |
        +--> Non-safety status to autonomy planner and fleet logs

The protective layer is not the same as the perception layer. A safety scanner can also provide measurement data for navigation, but its safety output must remain validated as a safety function with documented response time, diagnostic coverage, and field configuration.


Sensor Modalities

ModalityStrengthLimitationBest use
Safety laser scannerConfigurable 2D protective and warning fields, mature PL/SIL products, good for mobile bases.Can be affected by mounting height, reflectivity, weather, contamination, and occlusion.Primary personnel protection around AMRs, AGVs, tugs, and low-speed AVs.
Outdoor safety laser scannerDesigned for sunlight, rain, snow, fog, and outdoor industrial use.Higher cost; still needs cleaning and field validation.Outdoor campus, yard, mining, agriculture, and airside apron routes.
Safety radarMore tolerant of dust, fog, rain, steam, and airborne particles.Lower spatial resolution than laser; object discrimination and field shape can be coarser.Outdoor zones where optical scanners nuisance-trip or lose availability.
Safety-rated ultrasonicDetects transparent or low-reflectivity objects and short-range geometry; useful in dirty or wet zones.Acoustic reflections, air turbulence, temperature gradients, and narrow beams require careful placement.Docking, aircraft clearance, pallet pocket detection, glass or shrink-wrap detection.
Tactile bumper / safety edgeLast-resort contact detection; simple, visible, and easy to reason about.Contact has already occurred; must operate at very low residual energy.Low-speed final protection on bumpers, doors, carts, and docking faces.
Non-safety proximity sensorsCheap coverage for blind spots and service aids.Not a safety function by itself.Advisory planning inputs and diagnostic context.

Design Details

Protective Field Design

Field Sets

Protective fields should change with motion state. A single static field either creates nuisance stops or leaves unsafe gaps.

Motion stateField policy
StationaryClose protective field around the vehicle; restart interlock if a person is inside.
Forward cruiseLong forward field sized by speed, response time, braking distance, slope, load, and uncertainty.
ReverseRear field with lower speed limit unless rear coverage equals forward coverage.
TurningSwept-path field on the outside of the turn and side field for tail swing.
Crab or lateral motionSide protective fields become primary; front/rear fields remain warning zones.
DockingVery short protective field, low speed, tactile/ultrasonic close-in confirmation.
Trailer/tow/load presentField expands to include load envelope and hitch articulation.
Manual service modeReduced speed, hold-to-run, local enable device, explicit field-set indicator.

Separation Distance

For non-contact protective devices, field size must account for:

  • Sensor response time.
  • Safety controller and output response time.
  • Drive/brake reaction time.
  • Vehicle stopping distance under worst validated load, slope, surface, and tire condition.
  • Object approach speed and possible body-part access into the field.
  • Sensor resolution, mounting height, blanking/muting, and measurement uncertainty.

The safety case should store the calculation inputs with the scanner field configuration. A field drawing without a response-time budget is not reviewable.

Minimum Near-Field Coverage

ZoneTypical riskSensor design
Front low zoneFeet, cones, tow bars, pallet corners below long-range sensor line of sightLow-mounted scanner plus bumper/edge coverage.
Rear low zoneReverse into pedestrians, dock edge, aircraft equipmentRear scanner or dual-corner scanners; low-speed reverse policy.
Side sweepTail swing, crab motion, articulated loadSide fields linked to steering mode and yaw rate.
Docking faceContact with aircraft, dock, rack, charging targetUltrasonic/proximity plus tactile bumper and hard speed cap.
UnderbodyLow obstacles, fallen FOD, chocks, cablesShort-range proximity or mechanical guard; treat as advisory unless safety-rated.
Sensor blind regionsMounting brackets, payload, lift mast, tow loadRedundant fields or speed/geofence constraints.

Safety Controller Design

Safety Function Examples

Safety functionInputsOutputNotes
Protective stopScanner protective field, bumper, edge, safety radarBrake request, drive inhibit, safe torque offMust not depend on autonomy planner approval.
Warning speed reductionScanner warning field, ultrasonic proximitySpeed limit to DBW/safety controllerUseful before protective stop; still log as near-field event.
Restart interlockField occupied while stoppedHold inhibited statePrevents restart into a person or object.
Dynamic field switchingSpeed, direction, steering mode, load stateScanner field-set selectionField selection must be monitored for plausibility.
Service modeKey switch, enable device, low speed, local operatorReduced protective behavior with explicit limitsMuting is not free; it is a safety mode with evidence.

Interface Rules

  • Safety outputs go directly to the safety controller or safety network.
  • The autonomy stack receives a read-only mirror of field state, trip cause, speed limit, and reset eligibility.
  • Safety field configuration is release-controlled and tied to vehicle geometry, load geometry, brake performance, and scanner firmware.
  • Remote reset is blocked unless the vehicle is stopped, the field is clear, and a local or approved remote procedure permits it.
  • Muting and blanking require time, location, and state constraints. They should be rare, logged, and visible to the operator.

Deployment Notes

  1. Validate braking distance with the heaviest load, lowest traction surface, battery low-voltage condition, and cold/hot brake behavior expected in the ODD.
  2. Commission scanner fields from surveyed vehicle geometry, not from CAD alone. Verify with physical test targets at ground level and body-part heights.
  3. Test field switching while turning, reversing, crab steering, docking, lifting, towing, and driving over slopes or dock plates.
  4. Include contamination tests: dust, rain, de-icing mist, mud splash, plastic wrap, glass, reflective clothing, and low-dark objects.
  5. Log every protective stop with active field set, object range/bearing, vehicle speed, brake command, stopping distance, and reset actor.
  6. Treat nuisance stops as safety evidence, not just productivity issues. Frequent nuisance stops often indicate field sizing, cleaning, mounting, or environment problems.
  7. Revalidate fields after sensor replacement, bracket adjustment, tire size change, brake service, payload geometry change, or software release changing speed limits.

Failure Modes

Failure modeDetectionSafe response
Scanner contamination or blocked windowScanner diagnostic, reduced signal strength, health monitor, cleaning failureDegrade speed, trigger cleaning, stop if protective coverage is insufficient.
Field-set mismatchCommanded field does not match speed/direction/load stateStop or enforce lowest speed field; raise configuration DTC.
Blind zone from payload or tow loadCommissioning test, payload state mismatch, sensor occlusionExpand fields, add sensors, or restrict motion mode.
Nuisance trips from dust, rain, snow, or sunlightHigh trip rate with no object confirmed; environmental correlationUse outdoor scanner/radar, cleaning, field tuning, or ODD restriction.
Ultrasonic false negative on angled/soft objectDocking test miss, cross-sensor disagreementRedundant sensor angle, speed cap, tactile backup.
Bumper or edge disconnectedSafety input fault, channel discrepancy, test pulse failureInhibit motion or limit to service mode.
Safety controller network lossMissing OSSD/safety network heartbeatSafe stop; planner cannot override.
Remote reset into occupied fieldReset request while field occupied or cause unknownDeny reset; require local inspection if repeated.
Protective field too short after brake wearStopping test drift, brake DTC, maintenance dataLower speed limit or require brake service and field recalculation.


Sources

Public research notes collected from public sources.