Blogs

HOW TO PROPERLY DESIGN THE PLC LOGIC OF AN L-CNG STATION TO AUTOMATICALLY PRIORITIZE FUELING A TRANSIT BUS CONNECTING TO THE CNG DISPENSER OVER A TRUCK CONNECTING TO THE LNG DISPENSER?

Understanding the Fueling Priorities in L-CNG Stations

When managing an L-CNG station, one of the trickiest parts is designing the PLC logic to handle multiple vehicle types simultaneously. Specifically, giving priority to a transit bus fueling from the CNG dispenser over a truck using the LNG dispenser requires clear decision-making paths encoded in your control system.

Transit buses typically have tighter schedule constraints and might be more critical for timely operation compared to larger trucks, which often have longer fueling windows. This operational insight directly influences how you architect the PLC logic.

Breaking Down the Components: Dispensers and Timers

We generally have at least two key dispensers—one for CNG and one for LNG. The PLC must constantly monitor both dispensers’ status signals (ready, busy, fault) and the connection requests from vehicles.

  • CNG dispenser input: Indicates transit bus connection request and fuel status.
  • LNG dispenser input: Registered when a truck connects for fueling.
  • Priority flag or latch: A boolean variable reflecting if transit is currently being served or has priority demand.

Additionally, using timers to prevent indefinite waiting or starvation is essential; you never want a truck stuck endlessly simply because a bus hasn't connected yet.

Implementing Priority Logic Without Starvation

The core challenge here is handling what we call "priority inversion" — making sure the bus gets fueled first but without completely delaying the truck for too long. A simple approach is:

  • When a transit bus requests fueling (i.e., signals ready at the CNG dispenser), immediately set a priority bit inside the PLC.
  • If the truck is already fueling or queued, allow it to finish within a maximum timeout period.
  • Once time expires or the truck disconnects, switch dispenser control to the transit bus.
  • If no bus is waiting, freely allow truck fueling to proceed.

This sequence can be built using basic ladder logic elements—set/reset coils, timers, and interlocks. Remember to test edge cases, such as simultaneous disconnection or emergency stops.

State Machine Concept For Cleaner Control Flow

Instead of just juggling bits, consider implementing a state machine:

  1. IDLE: No vehicle connected.
  2. BUS_WAITING: Bus has engaged dispenser but not fueling yet.
  3. BUS_FUELING: Bus actively fueling.
  4. TRUCK_WAITING: Truck on site, awaiting clearance.
  5. TRUCK_FUELING: Truck fueling.

Transitions between these states must prioritize going to BUS_FUELING state whenever a bus request comes in—unless the truck is actively fueling and under timer protection.

This approach simplifies debugging and provides intuitive visibility into the station’s current activity.

Communication Challenges and Sensor Inputs

Reliable sensor feedback is the backbone. Using reliable, hardwired proximity sensors or inductive loops ensures that vehicle connection status is accurately relayed to PLC inputs.

Don't overlook the importance of health monitoring inputs on dispensers themselves—fault signals should force immediate aborts or safe stop routines, preventing priority switching races during unsafe conditions.

Incorporating CRYO-TECH Hardware Integration

If your setup uses equipment from CRYO-TECH or similar, verify their communication protocols and leverage any embedded status registers they provide. Many modern dispensers come with Modbus or CAN bus interfaces that can supplement hardwired IO signals. This detail can add robustness to your logic design and reduce false positives in vehicle detection.

Testing Tips From the Trenches

Field tests reveal many surprises! Here are some quick tips before final deployment:

  • Simulate concurrent bus and truck connections multiple times to validate priority trigger timing.
  • Check how the system handles unexpected disconnects—does it reset gracefully?
  • Ensure that timers do not inadvertently lock out either party by accidentally extending wait periods.
  • Log PLC state transitions during live runs to spot subtle timing conflicts.

Remember, a perfectly scripted PLC program can get tripped up by a loose wire or flaky sensor signal.

Why Not Give Both Equal Priority? (Spoiler: It’s About Operational Efficiency)

Giving the transit bus priority isn't merely a nice-to-have; it's about maximizing throughput and adhering to public transit schedules. An unattended truck can often wait longer without disrupting wider system operations.

So, while the logic design might seem complex, the payoff is visible in smoother station traffic flow and happier operators.