Siemens LOGO! V8 Fertigation Programming: 4x Daily 10-Min Cycles
Fertigation is the combined injection of fertilizer into an irrigation line. The canonical control requirement is "run the pump four times per day, each cycle for ten minutes", synchronized to local civil time. The Siemens LOGO! V8 (the 8th-generation 6ED1052 family, marketed as LOGO! 8.3 / FS4) is sized exactly for this class of machine: a built-in real-time clock with daylight-saving compensation, weekly and yearly timers, an astronomic option on the timer blocks, and (on FS4) NTP client support over Ethernet. This reference builds the program from primitives, validates it in simulation, and addresses the most common failure modes seen when commissioning a first-time LOGO! project.
1. Hardware Identification Before You Program
Confirm the exact order number (MLFB) printed on the front of the base module, because behavior differs across revisions:
| Family | Order Number (examples) | Feature Set | RTC Battery Backup | NTP Client | Ethernet |
|---|---|---|---|---|---|
| LOGO! 8.0 (BM) | 6ED1052-1MD08-0BA0 | FS02 | Yes | No | Yes |
| LOGO! 8.1 (BM) | 6ED1052-1MD08-0BA1 | FS03 | Yes | No | Yes |
| LOGO! 8.2 (BM) | 6ED1052-1MD08-0BA2 | FS03 | Yes | No | Yes |
| LOGO! 8.3 (BM) | 6ED1052-1MD08-0BA3 | FS04 | Yes | Yes (FS4+) | Yes |
| LOGO! 8.4 (BM) | 6ED1052-1MD08-0BA4 | FS05 | Yes | Yes | Yes |
Verify the feature set under LOGO!Soft Comfort > Tools > Select Device or by reading the device's Diagnostics > FW Version web page once it is on the network. NTP and astronomic timers are gated behind FS4+; if your base module is FS02/FS03, plan to use the weekly timer block driven by the local RTC and an external NTP-to-Modbus gateway, or accept manual time drift correction.
2. Fertigation System I/O Plan
Map the physical actuators to LOGO! digital outputs. A minimal fertigation skid has three outputs: main irrigation pump, fertilizer doser pump, and a master enable indicator. Reserve one input for a low-pressure safety interlock so a dry-run shuts the pump off without the LOGO! continuing to count cycle time.
| LOGO! Address | Signal | Device | Notes |
|---|---|---|---|
| I1 | Low-pressure switch (NC) | Pressure transmitter / PS | Open = fault |
| I2 | Manual RUN | Pushbutton, NO | One-shot test |
| I3 | Manual STOP | Pushbutton, NC | Hard interlock |
| Q1 | Irrigation pump contactor | 1-phase or 3-phase contactor | Coil 24 VDC from LOGO! RLY |
| Q2 | Fertilizer doser pump | Peristaltic or diaphragm pump | Drives only during last 30 s of cycle |
| Q3 | Run indicator lamp | 24 VDC LED | Mirror of Q1 |
The relay-version base module (R suffix in the order number, e.g. 6ED1052-1HB08-0BA0) is recommended for inductive contactor coils. The transistor (T) variant is for 24 V signals only.
3. LOGO!Soft Comfort Workspace Setup
- Open LOGO!Soft Comfort V8.x (matching the FW of your base module — V8.3 for FS4, V8.4 for FS5). Mismatched versions reject the LSC file with a dialog box; this is the most common reason a starter cannot open a downloaded program.
- Select File > New. In the Properties dialog set the device to the exact MLFB printed on the front of your LOGO!.
- Open Tools > Options > Simulation and confirm the simulator clock is unlocked. This is what lets you step time by one minute in five-second simulation ticks.
- Set the PC clock and timezone in Tools > Options > General. The simulation runs against the PC clock, not against a manual offset.
4. Time Base Selection: Why "Hours as Seconds" Hurts You
It is a common shortcut during simulation to set a "10-hour" timer and run the simulation for 10 seconds. The shortcut is fine for the on-delay block, but it is the wrong tool for a daily-schedule problem: a 10-hour on-delay is a one-shot, not a repeating daily trigger. The correct primitive is the Weekly Timer (block B13 in the LOGO! function-block list, Special Functions > Timers > Weekly Timer), which compares the LOGO! internal RTC against up to three on/off cam pairs per week.
5. Building the 4x Daily 10-Minute Schedule with Weekly Timers
Configure four independent Weekly Timer blocks, one per irrigation window. Each block has three on/off cams; you only need one cam per block. For a typical 06:00, 12:00, 18:00, 00:00 schedule:
| Block | Function | Cam 1 On | Cam 1 Off | Days | Pulse at end |
|---|---|---|---|---|---|
| B13a | Cycle 1 trigger | 06:00 | 06:00 | Mo Tu We Th Fr Sa Su | Yes, 1 s |
| B13b | Cycle 2 trigger | 12:00 | 12:00 | Mo Tu We Th Fr Sa Su | Yes, 1 s |
| B13c | Cycle 3 trigger | 18:00 | 18:00 | Mo Tu We Th Fr Sa Su | Yes, 1 s |
| B13d | Cycle 4 trigger | 00:00 | 00:00 | Mo Tu We Th Fr Sa Su | Yes, 1 s |
| B04 (On-delay) | Run-time | 10:00 min | — | — | — |
| B05 (Off-delay) | Run extension | — | 00:00 min | — | — |
The pulse output of each weekly timer becomes the trigger input of a shared 10-minute on-delay (B04). The on-delay's output drives the pump contactor Q1 via an AND with the low-pressure interlock I1 and the manual-stop I3. The off-delay (B05) is left at zero — its job is to keep the cycle on a hard 10-minute cap even if a subsequent 12:00 cam arrives early because of a network time correction.
5.1 Ladder-Logic Equivalent in FBD View
[ B13a ] -- ( B04 = 10:00 min ) -- ( AND I1 /\ ~I3 ) -- ( Q1 )
[ B13b ] ----/
[ B13c ] ----/
[ B13d ] ----/
[ Q1 ] -- ( AND ) -- ( B06 off-delay = 30 s ) -- ( Q2 doser )
5.2 Why OR the Four Timers
The four weekly timers are evaluated in parallel; their outputs are wire-OR'd into the trigger of the on-delay. Any one of the four rising edges starts the 10-minute run. If two cycles were configured at the same minute, the second rising edge is ignored because the on-delay is already timing out — this is the desired behavior and prevents overlapping irrigation windows.
6. Real-Time Clock and Timezone Configuration
The LOGO! internal RTC is set from one of three sources, in priority order:
-
NTP (FS4+ only): Configured in LOGO! > Settings > Time/Date > NTP on the LOGO! web interface. Point to up to two NTP servers (e.g.
0.pool.ntp.org,1.pool.ntp.org). Polling interval defaults to 60 s. - LOGO!Soft Comfort online clock: When connected via Ethernet/USB, the LSC toolbar Online > Set Time button writes the PC clock to the LOGO!.
- LOGO!Soft Comfort SD card auto-load: A project on a Siemens SITOP / SD card with the time offset written will set the RTC at boot.
Daylight saving time is handled automatically on FS4 and later via the Time/Date > DST checkbox. On FS02/FS03 the clock does not auto-advance, and a one-hour slip will occur twice per year. Compensate by adding a Yearly Timer (block B14) on the spring/fall DST boundaries that drives a hidden B04 with a 60-minute on-delay to nudge downstream calculations, or accept the slip and re-sync quarterly.
7. NTP Time Sync on FS4 (Step-by-Step)
- Connect the LOGO! Ethernet port to a routable network. Default IP is
192.168.0.10on the first power-up; change it via LSC Tools > Ethernet Connections or via the on-board web UI. - Open a browser to
http://<LOGO_IP>. Default credentials: userLOGO, passwordLOGO(change on first login). - Navigate to System > Time / Date. Enable NTP. Enter two NTP servers. Set timezone to your UTC offset.
- Click Apply. The LOGO! will synchronize within one poll cycle. Verify by reloading the page — the displayed time should match an internet reference clock to within ±1 s.
- Block diagram: the time-source flag is exposed to the program as a digital marker (M30 in the default symbol table) that can be used to blink a heartbeat LED when the clock is healthy.
8. Simulation Workflow
The Tools > Simulation (F3) toolbar in LOGO!Soft Comfort advances time against the PC clock by 1:1, so a 10-minute on-delay will take 10 minutes of wall time in simulation. To compress, do one of the following:
- Temporarily change the B04 setpoint to
00:00:10(10 seconds) for test only. The simulation is intended for logic verification, not for proving real-time behavior. After verification, restore the B04 setpoint to 10:00 min before downloading. - Use Simulation > Set Time of Day to set the PC clock near the next cam time, then step the simulator in 1-minute increments. The weekly timer will fire exactly on the cam minute.
- Use the Trigger Cam button on the simulation panel of the weekly timer to force a rising edge for logic-only testing.
Run the simulation for at least one full civil day (00:00:00 → 23:59:59) to confirm that all four cams fire and that overlapping cams do not start a second on-delay. The Diagram > Watch Window should show Q1 high for 10 minutes, four times.
9. Download Issues Specific to Starter LSC Files
The most common LSC download failure is a credentials prompt. Siemens Industry Online Support requires a registered Siemens account before any ZIP file will stream. The workarounds, in order of preference:
- Create a free Siemens Industry Online Support account at the support portal. The same credentials are used to download the LSC installation package and every Knowledge Base article sample.
- If you must access a project from a public forum, ask the original author to export via File > Export > LOGO! Project Archive, which produces a single
.lmafile. This file does not require an account to email and can be opened in any matching LSC version. - When the project opens with "file corrupted" or "unsupported block", the version mismatch is the cause. Update LSC from the support portal — it is freely downloadable after registration.
10. Verification & Commissioning Checklist
| Step | Action | Pass Criterion |
|---|---|---|
| 1 | Set LOGO! clock via NTP or LSC online | Web UI shows correct civil time ±1 s |
| 2 | Force Cam 1 (06:00) from simulation in online mode | Q1 closes, Q1 indicator LED on |
| 3 | Time 10:00 with a stopwatch | Q1 opens at 10:00 ±2 s |
| 4 | Trip low-pressure (open I1) at minute 5 | Q1 opens within 100 ms, fault latched |
| 5 | Re-arm by clearing I1 and pressing RUN (I2) | Q1 does not auto-restart — next cam only |
| 6 | Power-cycle the LOGO! | Program retained, RTC retained > 24 h |
| 7 | Re-check the 12:00 cam the next day | Trigger fires at 12:00:00 |
| 8 | Verify DST transition (FS4 only) | Local time jumps correctly at 02:00 |
11. Troubleshooting Matrix
| Symptom | Likely Cause | Fix |
|---|---|---|
| Pump never runs | Cam configured on the wrong day mask (e.g. Mo-Fr only) | Open the weekly timer block, tick all seven day boxes |
| Pump runs continuously | On-delay set to 0, off-delay missing | Set B04 to 10:00 min, B05 to 00:00 min (latch guard) |
| Pump fires at 06:00, 12:00, 18:00 but not 00:00 | 00:00 cam interpreted as "end of day" not "start of next day" | Use 23:59:59 → 00:00:01 split, or define the 00:00 cycle as a separate 00:00 → 00:00 pulse on the next day's mask |
| Time drifts 5-15 min/week | FS02/FS03 without NTP, RTC tolerance ±2 s/day | Upgrade to FS4, or use a Modbus master to write the time weekly |
| Download fails with "device not found" | USB driver missing on Windows 10/11 | Install the LOGO! USB driver from the support portal, or use Ethernet |
| Error LED on LOGO! | Program memory overflow (LOGO! 0BA0 base has 200 blocks; 0BA8 has 400) | Check block count in LSC; split into two LOGO!s or upgrade to 6ED1052-1MD08-0BA3 with 400-block program memory |
12. Extending the System
Once the four-cycle base system is stable, the same primitives scale to:
- Seasonal schedule — replace the four weekly timers with a single Yearly Timer (B14) and gate the 10-minute run by month. This is the typical summer/winter fertigation pattern.
- Dosing profile — add an analog input (LOGO! AM2 module) reading a flow meter on the main line, and multiply the 10-minute run by a scale factor to keep the fertilizer concentration constant as the irrigation flow changes.
- Remote start — on FS4, expose a webserver page on the LOGO! that lets an operator trigger an extra cycle on demand. The page is enabled under System > Webserver > User-defined page; binding Q1 to a VM (variable memory) address makes it visible to the page.
- Alarm SMS — a low-pressure fault can be written to a digital marker, polled by a Siemens LOGO! CMR (cellular router) and forwarded as an SMS or email alert.
13. Program-Block Map (Reference)
| Block # | Type | Function | Inputs | Output |
|---|---|---|---|---|
| B01 | OR (4-input) | Cam aggregator | B13a, B13b, B13c, B13d | — |
| B04 | On-delay | 10-min run timer | Trg = B01.out | Q1, Q2 (dosing) |
| B05 | Off-delay | Run extension guard | Trg = Q1 | — |
| B13a-d | Weekly timer | Daily cams 06/12/18/00 | — | 1 s pulse |
| B06 | On-delay | Doser pre-feed 9:30 | Trg = B04.out | Q2 |
| B07 | AND | Safety gate | Q1, I1, /I3 | — |
What is the difference between LOGO! V8 and LOGO! V8.3 (FS4)?
LOGO! V8 is the marketing family name; the trailing order-number digit (e.g. 6ED1052-1MD08-0BA0 vs -0BA3) defines the feature set. FS02/FS03 (early 0BA0/0BA1/0BA2) lack NTP and have a smaller program memory. FS04 (0BA3) and FS05 (0BA4) add the NTP client, astronomic timer, and 400-block program memory. Always check the MLFB on the device label, not the family brochure.
Can the LOGO! run 4 irrigation cycles per day without a weekly timer?
Yes, but it is not recommended. A self-resetting on-delay can be cascaded to give a 6-hour period with 10-min high time, but it is not synchronized to civil time and drifts whenever the LOGO! is power-cycled. The weekly timer (B13) is synchronized to the RTC and survives power-cycles; it is the documented primitive for daily-schedule tasks.
Why does my LOGO!Soft Comfort V8.3 not open a sample downloaded from the support portal?
The file was authored in a newer LSC version (typically V8.4 or V8.5). LSC is forward-incompatible in the same way Office is — older versions cannot parse newer block IDs. Install the latest LSC from the Siemens Industry Online Support portal, then re-open the project. A free Siemens account is required to download LSC installers.
How do I trigger a 00:00 cycle in the weekly timer?
Set the cam On time to 00:00 and the cam Off time to 00:00 of the next day's mask. A 00:00 → 00:00 cam on Sunday's mask is interpreted as a midnight trigger at the start of Monday. Alternatively, use a 23:59:59 → 00:00:01 split to make the boundary obvious in the block diagram. Both forms work on FS2 and later.
Does the LOGO! RTC keep time when power is removed?
Yes. The base module has a backup capacitor that holds the RTC for approximately 20 days, and the LOGO! 8 series also has a CR1632 coin cell that extends retention to roughly 2 years. The card slot on the front can hold an SD card that retains the program (not the time). Replace the coin cell every 4-5 years as preventive maintenance.