Oxford Industrial Automation
Programming and controls

Robot, PLC and machine controls designed as one system.

A production robot must coordinate with tooling, conveyors, sensors, safety devices and surrounding machinery. We engineer the software and interfaces so the complete cell starts, stops, changes product and recovers from faults predictably.

Sequence control

The cell needs a clear operating state, not isolated pieces of code.

Reliable cells coordinate machine readiness, product presence, guarding, tool status and downstream availability before each motion. The control architecture should make those conditions visible to operators and maintenance teams.

We define automatic, manual, setup and recovery sequences together with clear permissives, interlocks, alarms and restart behaviour.

  • Robot motion and process programs
  • PLC sequence and interlocking
  • HMI status, recipes and diagnostics
  • Safety PLC or safety relay integration
  • Fieldbus, industrial Ethernet and discrete I/O
  • Machine and line handshakes
Usability

Operators need useful information when production changes or stops.

A good HMI presents the information needed to run the cell, change product and resolve normal faults without exposing unnecessary engineering complexity. Alarm messages should identify the failed condition and the safe recovery action.

Recipe management can coordinate robot positions, gripper settings, conveyor parameters, inspection thresholds and pallet patterns for multiple products.

  • Production overview and cell state
  • Actionable alarm messages
  • Guided changeover
  • User access levels
  • Manual controls and maintenance screens
  • Counts, reject reasons and basic production data
Handover

Software is tested with the real interfaces and documented for support.

The control sequence is tested during build and factory acceptance testing, then verified again after connection to the customer’s equipment. Interface responsibilities and signal definitions are agreed early to avoid commissioning delays.

Handover can include program backups, network information, I/O schedules, functional descriptions, operator training and maintenance guidance appropriate to the project.

  • Interface control document
  • I/O and network schedules
  • Software backups and version records
  • Factory and site acceptance tests
  • Operator and engineering training
  • Remote-support readiness where agreed
Practical answers

Frequently asked questions

These answers provide an initial planning framework. Final requirements are confirmed against the product, process, site and applicable safety obligations.

Can a robot communicate with an existing PLC?

Usually, provided compatible I/O or industrial communication is available and the required handshakes can be implemented. The existing control system and documentation should be reviewed early.

What signals are needed for machine tending?

Typical signals include machine ready, cycle complete, door or chuck status, robot load complete, robot clear, cycle start, fault and safety status. Exact signals depend on the machine and process.

Can one cell run several products?

Yes. Recipes can coordinate robot paths, gripper settings, inspection parameters and surrounding equipment. Product presentation and tooling must also support the required changeovers.

Do you provide robot program backups?

Project handover should define the software, backups, version information and access supplied to the customer. The exact package depends on the equipment and support agreement.

Project review

Discuss the production task with an automation engineer.

Send the product details, required output, available space and a photo or short video of the current process. We will review the application and identify the next engineering step.

Send your project details →
☎ 01865 416830Project brief →