Application and selection overview
Coordinate PLCs, HMIs and sensors by I/O, signals, protocols, revisions and environment.
Key parameters to confirm
| Item | Information to provide |
|---|---|
| PLC and I/O | CPU model, memory, digital and analog point count, output type and expansion modules. |
| HMI | Display size, resolution, supply, ports, engineering software and availability of the project file. |
| Sensors | Target, range, accuracy, output signal, connector, cable and mounting. |
| Communications | PROFINET, EtherNet/IP, Modbus, serial or other protocols and network topology. |
| Environment and safety | Temperature, vibration, enclosure, hazardous area, machine-safety level and redundancy. |
RFQ checklist
- Send the complete bill of materials, wiring diagram and system architecture.
- Record full order numbers, hardware revisions and firmware versions.
- State whether PLC code, HMI project and communication configuration are available.
- List spare capacity, future expansion and the permitted shutdown window.
Common mistakes and risks
- Providing only a family name and omitting CPU, I/O and connector suffixes.
- Mixing voltage levels, PNP/NPN signals or relay/transistor outputs.
- Ignoring firmware and engineering-software compatibility.
Frequently asked questions
Can PLC and HMI products from different brands communicate?
Often yes through a mutually supported open protocol, but tag mapping, data types, diagnostics and performance need engineering review.
Does replacing a CPU require reprogramming?
Even within a family, firmware, memory, I/O addressing or communications may differ. Back up and assess the program first.
What if a sensor model is unreadable?
Provide photographs, mounting dimensions, sensing distance, target material, supply voltage and output wiring.
Next step
Send the BOM, complete models, I/O list, protocol, engineering-software version, quantities and destination so a compatible component list can be prepared.
Related Products