Appearance
Y305 PLC I/O Modules Wiring and Applications
Select compatible field circuits for Y305-4400, Y305-4421, Y305-8800, or Y305-8821, then turn their signals into a defined operating sequence. Relay outputs are standard; NPN transistor outputs are an order option, with no separate model suffix. The analog-level filling example uses Y305-4421 or Y305-8821.
The tank-filling sequence is a design example, not executable ladder logic or a safety function. Test it on the intended hardware and firmware. Keep field equipment disconnected until the load circuit meets its electrical limits and the sequence passes its bench tests.
- Hardware options and electrical limits
- Installation and initial electrical checks
- Analog feedback scaling
Contents
- Define the circuit and signal schedule
- Connect the documented input topology
- Separate relay and transistor circuits
- Assign control ownership
- Design a hysteresis and delay sequence
- Define trips and recovery
- Test the application
1. Define the circuit and signal schedule
Y305-4400/4421 provide 4 DI + 4 DO; Y305-8800/8821 provide 8 DI + 8 DO. Copy X/Y labels and common groups from the unit drawing. These labels use octal-style numbering; an eight-input unit uses X0–X7.
For the filling example, assign the first four inputs and one output as follows. Use free addresses and adapt the terminal schedule if the project already assigns them.
| Signal | Terminal/device | Application meaning |
|---|---|---|
| Start pushbutton, normally open | X0 | A fresh start action arms the sequence when conditions permit |
| Normal-stop contact, closed to permit operation | X1 | OFF disarms the sequence; restoring ON does not restart it |
| Process permissive contact | X2 | ON permits filling; loss removes the output request |
| Actuator auxiliary contact | X3 | ON indicates operation; compare with the output request within the equipment's allowed response time |
| 0–10 V level signal | AD0 / D8030 | Scaled and validated 0–100% level on Y305-4421/8821 |
| Fill actuator request | Y0 | Drives a compatible interposing circuit through one program output path |
Record each signal's supply, normal state, fault interpretation, and destination. RS485 and RTC are separate options; this local sequence does not require either. Mounting, supply protection, and initial continuity checks follow the User Manual.
2. Connect the documented input topology
The manufacturer's drawing connects S/S to +24 V and switches Xn to 0 V. Closing the switch completes the input circuit. A sinking sensor output can serve the same role if its electrical characteristics match the input.
| Field signal | Circuit with S/S at +24 V | Selection check |
|---|---|---|
| Dry contact, such as X0 start | Xn through the contact to the associated 0 V return | The closed contact must meet the input's voltage/current conditions |
| Normally closed contact, such as X1 stop | The closed contact joins Xn to 0 V; opening it removes the input signal | Assign OFF to stop in the program; test an open wire as well as button operation |
| Powered sinking sensor | Sensor output pulls Xn toward the compatible 0 V reference when active | Match output topology, residual ON voltage, OFF leakage, and references |
Identify a powered sensor's wires from its documentation and compare its limits with the fitted DI hardware. A “24 V sensor” label alone does not establish compatibility.
Keep S/S at +24 V for this circuit. Use a sourcing sensor only with a manufacturer-specified Y305 connection for that sensor topology; do not reverse S/S to 0 V on the assumption that the input supports it. Do not apply AC to input terminals.
Test wiring separately from logic: close one contact, observe its online X state, reopen it, and check that no other input changes. Then assign the application's meaning to ON and OFF. A normally closed permissive contact can make an open wire remove permission, but does not by itself establish diagnostic coverage or a safety rating.
3. Separate relay and transistor circuits
3.1 Relay hardware
For a DC interposing-coil example, the circuit path is protected load-supply positive, the relevant COM/Y0 contact, the coil, then load-supply return. The relay contact switches the separate load supply; it does not supply voltage itself. Follow the unit's common-terminal grouping; do not assume separate isolated commons or changeover contacts. Isolate each load supply before rewiring, even when the PLC supply is off.
The stated relay figures are AC 220 V or DC 30 V and a 5 A current ceiling. They do not establish a per-channel continuous or common-group rating. Before connecting a load, obtain the applicable motor rating, DC inductive breaking capacity, common-group current, simultaneous-loading limit, inrush limit, and switching life. The voltage and current figures alone do not establish suitability for a motor or inductive load. Where direct switching is unsuitable, use a rated interposing device and include its coil in the load calculation.
3.2 NPN transistor hardware
For the same DC interposing-coil example on optional NPN hardware, the circuit path is protected load-supply positive, the coil, Y0, then the output common at load-supply negative. The transistor sinks the coil current. Match the connection to the ordered unit's drawing and reference requirements.
The stated transistor current ceiling is 3 A; it does not establish a per-channel continuous rating. Obtain the permitted output voltage and shared-common capacity for the fitted hardware before selecting a load supply or combining channels. The module's 24 V supply marking does not establish the permitted load voltage. Do not connect AC loads. Relay and transistor outputs use different hardware; software cannot switch between them.
Select inductive suppression with the load manufacturer. Suppression can change release time, so measure its effect on the response. Relay contacts are unsuitable for high-speed pulse generation. Transistor pulse capability needs separate specifications for the delivered unit.
4. Assign control ownership
Command each physical output through one program path. Other logic supplies requests and permissives. Keep the output command, measured actuator feedback, operating state, and fault state distinct.
A host or HMI sends requests through an agreed application interface. PLC logic checks each request against local conditions before changing outputs. Define command expiry and the priority of local stop controls in that logic; these are not automatic Y305 functions.
Separate normal regulation from protective stopping. Ordinary PLC permissives can support the operating sequence. Emergency stopping and other required safety functions need independent provisions.
5. Design a hysteresis and delay sequence
In the tank-filling example, Y305-4421 or Y305-8821 reads a valid AD0 level signal scaled to 0–100%. The X0 start action arms automatic operation only with X1 normal stop released, X2 permissive present, and no active trip. Y0 requests the interposing device. X3 provides actuator feedback. The initial state is Inhibited, with no output request.
The example starts filling at or below 35%, stops at or above 65%, qualifies a start for 2 seconds, and delays a routine high-level stop for 1 second. These values illustrate the sequence. Set production thresholds and delays from process response and overshoot limits. Use zero routine stop delay unless the process has a specific reason for a delay.
5.1 Two-threshold demand
While armed with valid feedback, set fill demand at or below 35% and clear it at or above 65%. Between the thresholds, retain the previous demand. This avoids repeated switching around a single boundary. Reject settings where the lower threshold is not below the upper threshold.
5.2 State transitions
| State | Output request | Transition |
|---|---|---|
| Inhibited | OFF | A fresh start with valid conditions enters Ready |
| Ready | OFF | Fill demand starts the start-delay interval |
| Start pending | OFF | Demand and permissives held for 2 seconds enter Running; loss cancels the timer |
| Running | ON | Demand clearing begins the routine stop-delay interval |
| Stop pending | ON | After 1 second, turn OFF and return to Ready |
| Tripped | OFF for this example | Use the recovery sequence in Section 6 |
Once the routine stop interval begins, complete it rather than extending it as the measurement fluctuates. Any later start must qualify again.
Normal stop, invalid feedback, and lost permissives take precedence over timer completion and other normal transitions in every active state. They bypass both delays and remove the output request without an intentional software delay.
A normal stop disarms automatic operation, clears fill demand, resets both timers, and enters Inhibited. Releasing stop does not restart the output; a fresh start is required. At power-up or program restart, initialize armed and demand OFF and reset both timers.
Measure total stopping time, including input filtering, scan execution, output switching, and actuator release. The example assumes that stopping the fill output is the appropriate response. Check that assumption against the real process.
6. Define trips and recovery
Specify which conditions inhibit starting, which latch a trip, and which need independent protective action. Examples include invalid feedback, missing actuator confirmation within the equipment's allowed response time, and a separate high-level limit. Do not delay protective stopping to complete a normal timing sequence.
In the tank-filling example, a trip clears demand and both timers, removes the output request, and records the cause. Recovery requires the cause to clear, valid feedback, and an operator acknowledgment. Acknowledgment returns to Inhibited; a fresh start is still required.
Require a fresh start after power restoration and program restart. Measure actual output behavior during STOP, power loss, and startup on the delivered hardware. Do not rely on software initialization to control an output while the program is not executing; provide independent protection where an uncontrolled transition could create a hazard.
7. Test the application
Use isolated actuators or a limited-energy simulator. Record expected and observed behavior for:
- Each physical input and output, including OFF states and common grouping
- Slow level sweeps through both thresholds and noise inside the hysteresis band
- Interrupted start qualification and routine stop timing
- Stop, lost permissives, and trips in each sequence state, including a stop in the same scan as timer completion
- Fault acknowledgment before and after the cause clears
- Power loss, STOP/RUN changes, and stale remote commands
Record sequence response times against the commissioning acceptance stages. Use the Analog and PID Guide to establish level validity and the Programming Guide to organize the state logic and final output path.
