\n

AI Pedestrian Detection + PLC Integration for Forklifts

Quick answer: an AI pedestrian-detection camera can send a hazard status to a PLC, but the PLC should combine that signal with vehicle state before deciding whether to warn, request slow-down or request a controlled stop. The camera is a sensing layer; the complete safety behaviour depends on the approved control architecture, vehicle interface, fault handling and site validation.

Forklift AI pedestrian detection camera integrated with industrial control logic
Conceptual architecture: AI detection should be integrated with vehicle and control logic rather than treated as a stand-alone braking device.

Google Search Console is already showing Xenors for practical queries around AI pedestrian detection and forklift AI cameras. A common next question is not “can the camera see a person?” but “how do I connect that detection to a PLC so the forklift warns, slows or stops correctly?” This guide focuses on that implementation layer.

1. Start with the control objective, not the camera

Before wiring anything, define exactly what the system must do in each operating state. A useful requirement table separates three actions:

ConditionTypical responseWhy
Person detected, forklift parkedWarning only or event loggingA stop request may be unnecessary if the vehicle is already stationary.
Person detected, forklift moving slowlyWarning + speed reduction requestCreates more reaction margin while avoiding abrupt behaviour.
Person detected in critical zone while movingWarning + validated stop requestHighest-risk state; only use if the vehicle interface and risk assessment support it.
Camera or AI health faultFault indication + approved fallbackA failed sensor must not look like “no person detected.”

This distinction matters because a raw PERSON_DETECTED = 1 bit is not enough to understand risk. A pedestrian behind a parked vehicle and a pedestrian entering the path of a moving truck are different control situations.

2. Recommended signal architecture

A robust system normally has four information groups:

  1. AI hazard outputs: person in warning zone, person in critical zone, camera blocked, stream offline, AI heartbeat.
  2. Vehicle state: forward/reverse direction, moving/not moving, drive-enable, speed or a speed band where available.
  3. PLC decision logic: combines hazard and vehicle state, applies timers and fault logic, then generates warning/slow/stop requests.
  4. Vehicle interface: approved relay, digital I/O, CAN, OEM input or other authorised interface that actually changes vehicle behaviour.

The cleanest separation is: AI detects → PLC decides → vehicle interface acts. That makes troubleshooting easier because the technician can identify whether a bad event came from vision, logic or the actuator interface.

3. Example I/O map

The actual addresses depend on the PLC and vehicle, but a simple conceptual map can look like this:

SignalDirectionMeaning
AI_WARN_ZONEAI → PLCPedestrian present in outer warning zone
AI_CRITICAL_ZONEAI → PLCPedestrian present in inner critical zone
AI_HEALTHYAI → PLCCamera, stream and inference heartbeat valid
GEAR_FORWARDForklift → PLCForward selected
GEAR_REVERSEForklift → PLCReverse selected
VEHICLE_MOVINGForklift → PLCTruck is moving
ALARM_OUTPLC → alarmVisual or audible warning
SLOW_REQUESTPLC → approved interfaceRequest reduced speed
STOP_REQUESTPLC → approved interfaceRequest controlled stop
AI_FAULTPLC → HMI/alarmLoss of camera/AI protection

If the AI application runs on an industrial PC, Ethernet-based communication can be used for non-safety information. Where a safety function is claimed, do not assume that ordinary Ethernet or an ordinary PLC bit automatically becomes a safety-rated function. The required architecture depends on the machine, risk assessment and applicable safety design.

4. Example warning, slow and stop logic

A practical sequence is easier to validate when it is explicit:

IF NOT AI_HEALTHY:
    AI_FAULT = ON
    FOLLOW_APPROVED_FALLBACK()

ELSE IF VEHICLE_MOVING AND AI_CRITICAL_ZONE:
    ALARM_OUT = ON
    STOP_REQUEST = ON

ELSE IF VEHICLE_MOVING AND AI_WARN_ZONE:
    ALARM_OUT = ON
    SLOW_REQUEST = ON

ELSE IF AI_WARN_ZONE OR AI_CRITICAL_ZONE:
    ALARM_OUT = ON
    SLOW_REQUEST = OFF
    STOP_REQUEST = OFF

ELSE:
    NORMAL_OPERATION()

This is only conceptual logic. A production implementation should also handle direction, camera assignment, debounce/confirmation timers, latching rules, reset conditions, vehicle-specific stopping behaviour and diagnostic faults.

5. Direction-aware camera logic reduces false actions

On a three-camera forklift, a common layout is two front-facing cameras and one rear camera. It is usually wasteful to treat all cameras as equally critical in every direction. If the truck is moving forward, front detection deserves higher priority; if reversing, the rear camera becomes the primary path sensor.

A direction-aware rule can be:

This avoids a common commissioning problem where people standing beside a stationary forklift repeatedly trigger aggressive vehicle responses.

6. Use confirmation timers carefully

Computer-vision detections can flicker for one or two frames because of occlusion, glare, vibration or motion blur. A short confirmation timer can reduce nuisance events, but too much delay increases response time.

For each zone, measure the complete chain:

  1. camera exposure and frame interval,
  2. AI inference time,
  3. tracking or confirmation delay,
  4. network/PLC scan delay,
  5. output/interface delay,
  6. vehicle mechanical response.

The correct setting is not “2 seconds because it looks stable.” It must be checked against actual vehicle speed and stopping distance. A timer that is fine at walking speed may be unacceptable at a higher speed.

7. Heartbeat and stale-frame detection are mandatory engineering checks

One of the most dangerous software failure modes is a frozen frame that still looks valid to the application. The PLC should not receive “no pedestrian” forever just because the last inference result was clear.

The AI layer should expose at least:

The PLC can then require a changing heartbeat or a fresh timestamp. If that health condition disappears, the system enters a documented fault state.

8. Do not confuse detection confidence with safety integrity

A model confidence such as 0.82 or 0.95 only describes the model's score for a particular detection. It does not certify the entire system. Real failures can come from:

That is why a factory acceptance test must validate the complete chain, not just draw bounding boxes on a monitor.

9. Commissioning checklist

Use a controlled test area and document every result. At minimum, test:

Record video and PLC states together where possible. When a test fails, that combined evidence makes it much easier to decide whether to change the camera, model, zone, timer or vehicle logic.

10. PLC communication choices

For prototypes, simple digital I/O or relay outputs are easy to understand and isolate. For richer systems, industrial Ethernet can expose multiple zone states, camera health and diagnostics. The choice depends on the required reliability, the PLC family, available interfaces and whether the function is safety-related.

For example, PROFINET is widely used for industrial communications, but ordinary PROFINET data exchange and a safety-rated PROFIsafe function are not the same thing. Do not label a stop path “fail-safe” just because it uses an industrial network.

11. Where this fits with forklift safety controls

AI pedestrian detection should sit inside a broader traffic-safety strategy. OSHA guidance for powered industrial truck workplaces recommends separating pedestrians and lift trucks where practical, using walkways or barriers, posting traffic controls and speed limits, and warning pedestrians of forklift approach. Camera AI can add awareness, but it does not replace those controls.

Useful reference: OSHA forklift pedestrian traffic guidance.

For driverless industrial trucks, ISO 3691-4:2023 covers safety requirements and verification; ISO is also developing a newer revision. That standard is specifically for driverless industrial trucks and should not be misapplied as proof that a manually driven forklift AI retrofit is compliant.

Reference: ISO 3691-4:2023 overview.

12. Recommended implementation workflow

  1. Site survey: map travel paths, blind spots, speeds and pedestrian exposure.
  2. Define response matrix: decide what warning, slow and stop mean in each vehicle state.
  3. Choose camera positions: optimise visibility before tuning AI thresholds.
  4. Build AI health monitoring: stale frames and offline cameras must be visible to the PLC/HMI.
  5. Map PLC I/O: use named signals for zones, direction, motion and diagnostics.
  6. Integrate the vehicle interface: only through an approved method.
  7. Commission in stages: warning-only first, then any speed/stop function after validation.
  8. Measure actual response: record latency and stopping behaviour instead of relying on assumptions.
  9. Document fallback: define operation when AI protection is unavailable.
  10. Re-test after changes: model, camera, speed, tyre, floor or braking changes can affect the result.

13. Related Xenors guides

Frequently asked questions

Can an AI camera directly stop a forklift?

It should not be treated as a direct safety stop device by default. A stop function needs a vehicle-approved, risk-assessed control architecture with defined failure behaviour and validation.

Should the PLC receive only a pedestrian detected bit?

No. A stronger design also uses direction, motion or speed where available, plus AI health information. That allows the PLC to distinguish warning-only situations from higher-risk movement states.

What happens if the AI PC or camera goes offline?

The system should indicate loss of protection and follow the site's approved fallback behaviour. A fault must not silently become a clear/no-person state.

Can warning, slow-down and stop use different zones?

Yes. Separate zones are practical, but their distances must be derived from the real vehicle, speed, floor condition, response time and stopping behaviour.

Final takeaway

The most useful architecture is not “camera sees person, relay stops forklift.” It is a layered design in which AI provides hazard information, the PLC combines it with vehicle state, and an approved vehicle interface performs the response. Add heartbeat monitoring, stale-frame detection, direction-aware logic and a documented commissioning test, and the system becomes much easier to validate and maintain.

Safety note: this article is an engineering guide, not a certification. Any braking or motion-control modification should be reviewed against the specific truck manufacturer's requirements, the site's risk assessment and applicable safety standards.

Product: For a ready industrial solution with camera, control-box integration and ₹50,000 listed system price, see the Hesham AI Human Detection Safety Camera System.