How-to
Programming a Fatek PLC Through a Weintek HMI Ethernet Link
Short answer
Yes — the FBs-20 can be programmed from a PC through the panel with only the console's one Ethernet cable. Bridge the panel's RS232 line over Ethernet with the panel's pass-through feature or an Ethernet-to-serial converter, present it to the PC as a virtual COM port, then open that port in WinProladder with the PLC's own baud, parity and station number and a raised timeout, because the panel's polling shares the line.
On this page
- What the link has to carry
- Get the panel-to-PLC link healthy first
- Pick the route the console can live with
- Put the PC on the panel's network
- Bring the tunnel up as a COM port in WinProladder
- Sizing the timeout for an 8070ie to FBs-20 link at 115200 baud
- What each failure points to
- Prove the whole chain before you need it
- Questions asked
Yes. A Fatek FBs-20 wired to a Weintek 8070ie panel over RS232 can be programmed from WinProladder with only the console's single Ethernet cable, by tunnelling the panel's serial line over Ethernet. The PC gets a virtual COM port that bridges TCP to the panel's COM port, and WinProladder opens that COM port with the PLC's own baud, parity, data bits, stop bits and station number. Two routes do the bridging: the panel's pass-through feature, or a small Ethernet-to-serial converter at the PLC. Either way the communication timeout goes up, because the panel's own polling shares the same line. This walkthrough records the settings first, brings each route up, and sizes that timeout with real arithmetic.
What the link has to carry #
The panel's Ethernet port carries panel traffic: project download from EasyBuilder Pro, remote access, and whatever Ethernet protocols the project enables. The RS232 port carries the Fatek protocol between the panel's device driver and the PLC. The FBs manual puts both roles on one protocol: the PLC port answers Fatek's internal communication protocol whether the peer is WinProladder or a man-machine interface. That fact is what makes a tunnel possible at all.
The tunnel has to do three things:
- Accept a TCP connection from the PC.
- Relay the bytes to the panel's COM port unchanged.
- Present a virtual COM port on the PC, because WinProladder opens a COM port, not a socket.
The consequence applies to every route: with the tunnel open, the panel and the PC are two masters on one line to the FBs-20. Only one master transmits at a time and everyone else waits, which is the same delay mechanism behind why Modbus RTU drive polling on one serial port runs slow. The sharing discipline is the one used when multiple HMIs share one PLC over 200 ft of serial, minus the multidrop hardware.
Get the panel-to-PLC link healthy first #
A tunnel built on a broken panel-to-PLC link wastes the day, because tag faults and tunnel faults look identical from the PC seat. Run the project against live PLC data before adding anything.
| Setting | Where it lives | Fault it causes |
|---|---|---|
| Fatek device driver on the RS232 COM port | EasyBuilder Pro system parameter device list | every tag in a communication error |
| Baud, parity, data bits, stop bits | device entry; must equal the PLC port settings | timeouts; no tag ever updates |
| PLC station number | device entry; must equal the PLC | no reply from the PLC |
| RS232 wiring, TX/RX/GND | cable between panel COM port and PLC port | silent line |
A silent line is a pinout fault before it is anything else — the same class of wrong-pair mistake as uploading an HMI program without the right cable pinout, so check both hardware manuals before rewiring. If tags sit in error with no PC attached, treat it as an HMI PLC communication timeout over serial and fix it now; the tunnel adds nothing until that link is clean.
Record these before going further, reading each one from the PLC port settings in WinProladder rather than from memory:
- The PLC port in use.
- Baud rate.
- Parity.
- Data bits and stop bits.
- Station number.
Every later step — the virtual COM port, WinProladder's communication screen, the timeout decision — takes its values from this list. The check that closes the section: a numeric object bound to a PLC register shows a live value on the panel.
Pick the route the console can live with #
| Route | What it needs | What it gives | What it costs |
|---|---|---|---|
| Panel pass-through | EasyBuilder Pro version and firmware that support pass-through for the Fatek driver; virtual COM driver on the PC | programming over the single existing cable, no added hardware | PLC access dies with the panel |
| Ethernet-to-serial converter at the PLC | a spare PLC serial port or a shared bus, the converter inside the console, a small switch so one exit cable serves both, the converter's virtual COM driver | programming access that survives a panel fault | one more part in the box |
| Easy Access 2.0 | a paid license code, the panel connected to the internet, user accounts on the panel | panel and PLC reachable from anywhere, no port forwarding | pointless on a bench cable with no internet |
The manufacturer's support answers restrict pass-through to specific listed uses, so confirm in your EasyBuilder Pro documentation that the Fatek driver on the COM port is covered. For the sealed bench console in this question — one Ethernet cable, no internet — commit to pass-through when the installed EasyBuilder Pro lists the Fatek driver for it: zero extra hardware. If the driver is not on the list, or the machine cannot lose PLC access when the panel dies, fit the converter. Easy Access 2.0 earns its license code only when the console later sits behind a network nobody will forward ports on.
Writing your own Ethernet-to-serial relay on the panel is the worst of the three: custom code to maintain, and PLC access still tied to panel health, which is exactly what the converter avoids.
Put the PC on the panel's network #
- Set a static IP on the panel, in the EasyBuilder Pro network settings or the panel's own settings page, and write it down.
- Give the PC a static address in the same subnet with the same mask.
- Connect PC to panel directly, or through the console's switch, on one NIC; turn Wi-Fi off so Windows does not route out the wrong adapter.
- Allow the panel tools through the Windows firewall when prompted.
- Verify both ways: the panel answers ping, and a project download from EasyBuilder Pro completes. If the download works, the Ethernet side is proven and every later fault is serial-side.
Bring the tunnel up as a COM port in WinProladder #
- Install the virtual COM driver for the chosen route — the panel pass-through tooling, or the converter vendor's driver — and point it at the panel's (or converter's) IP address and the TCP port named in its documentation.
- Note the COM number it creates in Device Manager, and close any program already holding that port.
- Start the tunnel on the panel side: in the HMI list, the pass-through control appears with the connected panel's entry, below its IP address once the connection is active. Run it for the Fatek device on the COM port.
- In WinProladder's communication settings, select that COM port and enter the recorded baud, parity, data bits, stop bits and station number.
- Raise the communication timeout to the value sized in the next section before the first connect.
- Connect and read the PLC.
Take the machine to a safe state before any download: a half-written program in a running FBs-20 is a machine acting on code you cannot see. A read proves addressing; a completed download of one small change proves long frames survive the tunnel — save the full project download for after that.
Sizing the timeout for an 8070ie to FBs-20 link at 115200 baud #
Inputs, each with its source:
- Line speed 115200 baud, characters of 10 bits (1 start, 8 data, 1 stop, no parity) — recorded from the PLC port settings in WinProladder on this console; substitute your own recorded values.
- One programming frame modeled at 256 characters — an illustrative input, representative rather than measured; the real frame length belongs to the programming software.
- The panel's polling and the PLC's turnaround are not calculable from the settings; they are only measured on the live link, so they must sit inside the margin.
Rule in words: the timeout must clear the round-trip line time of the longest frame with a wide margin, because everything that is not line time — the polling queue, PLC processing, tunnel latency — only adds delay. Use ten times the calculated floor.
Arithmetic:
- Bits per character: 1 start + 8 data + 1 stop = 10 bits.
- Time per character: 10 bits ÷ 115200 bits per second = 86.8 microseconds.
- One 256-character frame, one way: 256 × 86.8 µs = 22.2 ms.
- Round trip: 2 × 22.2 ms = 44.4 ms of pure line time.
- Margin: 10 × 44.4 ms = 444 ms.
Result: any timeout at or below about 44 ms fails on line time alone, even on an idle line. A 1000 ms setting carries the 444 ms requirement with room for the panel's polling and the PLC's turnaround.
Decision: set 1000 ms on this link and commit to it. If WinProladder still drops mid-download, raise the timeout before touching any other setting; if it fails again, cut the panel's poll load — fewer tags or a slower cycle. For scale, every kilobyte occupies this line for 1024 × 86.8 µs ≈ 88.9 ms, so a full project costs seconds of line time at best — plan the maintenance window accordingly.
What each failure points to #
| What you see | Layer | Likely cause |
|---|---|---|
| Panel tags in comm error, no PC attached | panel-to-PLC link | wrong driver, serial parameters, station number or cable — fix before any tunnel |
| Ping to the panel fails | network | subnet mismatch, wrong NIC, bad cable |
| Virtual COM port missing or reported in use | PC driver | driver not bound to the panel IP, or another program holds the port |
| WinProladder times out, panel tags keep updating | tunnel | pass-through not running for that device or COM port, or serial parameters differ from the PLC port |
| Connects, drops during download | contention | timeout below the round-trip need; raise it, then reduce panel poll load |
| Works on the bench, fails across a router | routing | port forwarding missing at the panel's router, or move to Easy Access 2.0 |
Prove the whole chain before you need it #
- Power the console with only the single Ethernet cable connected to the PC.
- Confirm the panel shows live PLC values.
- Open the virtual COM port in WinProladder and read the PLC type and program.
- Watch one non-critical register from the PC while the panel displays it — a change at one end must appear at the other.
- Download one small, safe change and watch it land.
Once the chain is proven, the same tunnel carries any FBs-20 work from the PC — logic, registers, and motion projects built on pulse-train output for stepper control on the FBs-20.
Questions asked
Do the panel's screens keep updating while WinProladder is connected through it?
Expect them to lag. The tunnel does not add a second port to the FBs-20 — the panel's polling and the PC's programming traffic share one RS232 line, and only one master can hold it at a time. Screen refresh recovers as soon as the PC disconnects. If operators need live values during the session, schedule the download for a stoppage or reduce the panel's poll load first.
Can I program a different PLC brand through the same panel?
Only if the panel tooling supports pass-through for that exact device driver. Support is per driver and per EasyBuilder Pro version, and the manufacturer's support answers restrict pass-through to listed uses, so a Fatek driver on the COM port carries Fatek frames only. Check the supported-device list in the EasyBuilder Pro documentation before promising the job, and fall back to an Ethernet-to-serial converter when the driver is not listed.
What happens to PLC access when the panel fails?
With pass-through it disappears with the panel, which is that route's real cost. An Ethernet-to-serial converter wired to a spare PLC port keeps programming access independent of the HMI, and a small switch inside the console lets the single exit cable serve both. If the machine cannot wait for a panel repair, choose the converter even though pass-through needs no extra hardware.
Is Easy Access 2.0 needed for this?
No. Easy Access 2.0 is the remote-service route: a paid license code, the panel connected to the internet, and user accounts configured on it, after which you reach the panel and the PLC through it without router port forwarding. A bench cable between PC and panel needs none of that — pass-through or a converter works with no internet at all. Move to it only when the console later sits behind a network you do not control.
Why does WinProladder connect and then drop during a download?
Because the longest frame exceeds the timeout while the panel's polling queues ahead of it. At 115200 baud with 10-bit characters, one kilobyte occupies the line for about 88.9 ms before any turnaround, and contention multiplies that. Raise the communication timeout rather than retrying, then cut the panel's poll load — fewer tags or a slower cycle — if transfers still fail.