WindLDR Installation, Setup, and First Connection to IDEC FC6A PLC

Overview

This guide walks through installing WindLDR (distributed as part of the IDEC Automation Organizer suite), creating a project, selecting the correct PLC family, and establishing first communications to an FC6A CPU over USB, serial, or Ethernet. Every step emphasizes repeatable, auditable procedures — driver verification, IP hygiene, and known-good PLC status checks — so the connection is trustworthy before any real program work begins.

Prerequisites

• A Windows PC meeting IDEC's current Automation Organizer requirements (Windows 11 or 10; Windows-only; IDEC states "no support for virtual environment").
• Access to IDEC's Software Download Center / Automation Organizer Suite package.
• Physical access to the FC6A CPU (or panel) and at least one supported maintenance-communication path:
  • USB — FC6A USB 2.0 Mini-B connector with the recommended USB maintenance cable.
  • Serial Port 1 — RS-232 maintenance cable (the communication manual provides example cable part numbers).
  • Ethernet Port 1 — Cat 5 STP LAN cable per the manual's specifications.
• An understanding that some Ethernet configuration (notably the "maintenance communication server" settings) is done in WindLDR's Function Area Settings and may require a download step before it becomes active on the PLC.
• Safety readiness: you must be able to place the machine in a safe state before downloading, forcing I/O, or monitoring/changing device values. The IDEC manuals repeatedly emphasize external failsafes and safe start/stop practices.

Step 1 — Installation and Environment Hardening

1. Download the Automation Organizer installer from IDEC's "Downloads and Updates" area and record the displayed suite version numbers for traceability.
2. Verify system requirements. Current requirements state Windows 11/10 and explicitly say the software is Windows-only. IDEC also states "no support for virtual environment." Include this prominently in your project documentation if your team commonly uses VMs.
3. Run the installer with appropriate privileges consistent with your organization's endpoint controls (IDEC requirements mention specific Windows user-account-control guidance).
4. After install, launch WindLDR and create a baseline environment note in your project readme: OS version, Automation Organizer suite version, WindLDR version, and date.

Step 2 — Project Creation and PLC Selection

5. Create a new project and select the PLC series and CPU model consistent with the deployed hardware. Because the target firmware/system-software version is unspecified at this stage, include a later verification step to confirm the model and system software version from the live PLC.
6. Write a minimal "smoke-test" ladder program — for example, a single rung that drives a non-critical internal relay (M device) based on an input (I device). This avoids touching outputs until you confirm safe conditions and I/O mapping.

Step 3 — Physical Connection and First Online Session

Choose your connection path and document the decision:

Option A — USB Maintenance Connection

1. Connect the PC and PLC using the USB maintenance cable. The FC6A communication manual depicts the USB 2.0 Mini-B connector and names the recommended cable.
2. Use WindLDR's online/transfer workflow to connect, then read PLC status (CPU type, system software version).

Option B — Serial Port 1 Maintenance Connection

1. Cable the PC to FC6A Serial Port 1. The manual includes an example communication cable and lists supported maintenance functions (download, upload, monitor/change devices, run-time download, and system software download depending on model/port).
2. Match serial parameters in WindLDR to the PLC port configuration (document the exact baud rate, parity, and stop bits).

Option C — Ethernet Port 1 Maintenance Connection

1. Configure the "maintenance communication server" settings in WindLDR and set parameters as shown in the manual's Ethernet maintenance procedure.
2. Use Online > Monitor > Batch and confirm the configured IP address is reflected in special data registers D8330–D8333. Treat this as your first-pass validation.
3. Open Online > PLC > Status and verify the module type and system software version display correctly.

Step 4 — Confirming Version and Identity

8. Record the PLC system software version using one of these authoritative paths:
   • WindLDR PLC status dialog (shown in the communication manual workflow).
   • Special data register D8029 ("System Software Version").
9. Capture an identity snapshot (screenshot or PDF export) including: CPU module type (D8002) and system software version (D8029).

Step 5 — First Download and Monitor Cycle

10. Download the minimal smoke-test program and immediately verify:
    • The PLC stays in the intended mode (RUN/STOP) and the machine remains safe.
    • You can monitor internal relays and (if safe) verify one non-critical output under controlled conditions.

Connection Workflow

flowchart TD
  A[Download Automation Organizer / WindLDR] --> B[Install + record versions]
  B --> C[Create project + select FC6A CPU]
  C --> D{Connection method?}
  D --> E[USB maintenance]
  D --> F[Serial Port 1 maintenance]
  D --> G[Ethernet Port 1 maintenance]
  G --> H[Configure maintenance server + IP params]
  H --> I[Batch monitor: verify IP in D8330-D8333]
  E --> J[Online > PLC Status]
  F --> J
  I --> J
  J --> K[Record CPU type + system SW version]
  K --> L[Download smoke-test program]
  L --> M[Monitor devices + validate safe behavior]

Minimal Smoke-Test Program

Goal: confirm scan execution without energizing real actuators.

// Rung 1: Mirror a physical input into an internal relay.
// Use a known safe input point (e.g., a panel test switch).
I0  ----[ ]--------------------( )----  M0000
// I0 address range depends on CPU type and wiring; verify with your I/O map.

Device addressing conventions (I for inputs, Q for outputs, M for internal relays) and valid ranges are defined in the FC6A user manual device tables.

Key Device Address Ranges

Quick Checklist

• Confirm PC meets IDEC requirements (Windows 11/10; no VM support).
• Record Automation Organizer suite + WindLDR version from IDEC's download center.
• Choose USB, serial, or Ethernet and document your decision.
• Verify identity: CPU type (D8002) and system software version (D8029) before writing version-specific documentation.
• Run a non-actuating smoke test first (internal relay only), then move to real outputs only after a safety review.