Explainer
Why EasyBuilder Pro PC simulation stops after 15 minutes
Short answer
Yes, up to a point you cannot log on. EasyBuilder Pro online simulation polls an RS-485 meter from the PC through a USB converter, but Weintek documents a 10-minute limit when the target device is connected directly to the PC, so the session ends and needs a manual restart. Prove the link in simulation; run the hourly log on an operator panel or a dedicated logger.
On this page
Yes, the PC can read the meter — and no, it cannot keep the log. EasyBuilder Pro online simulation runs the whole project on the PC, drivers included, so through a USB-to-RS-485 converter it polls the meter over Modbus and shows live values. But Weintek documents a 10-minute limit for online simulation when the target device is connected directly to the PC; field reports land between ten and fifteen minutes, then the session stops and needs a manual restart. That makes the PC the right place to prove the communication path in an afternoon and the wrong place for unattended hourly logging. The same project, downloaded to an operator panel, logs around the clock, and a dedicated logging controller does the same job with no display at all.
The documented limit, and the fifteen minutes people report #
Weintek's project guide states the condition exactly: when using On-line Simulation on the PC, if the target device is the PLC connected directly to the PC, there is a 10-minute simulation limit. That limit is a property of the development environment, not a fault in your PC, your converter, or your project.
Plan on ten minutes. Reports of "about fifteen" fit the same behavior on a different release or a slower clock, and nothing you configure in the project moves it — the cap sits on the session, not on your driver settings, polling rate, or PC hardware. The stop is also clean: the session ends and you reopen it by hand, which is how you tell it apart from a communication timeout, where the session keeps running with dead objects.
Why the RS-485 reads still work #
The simulation emulates the project completely, communication included. EasyBuilder Pro devices speak Modbus over Ethernet or RS-232/RS-485, so with a USB-to-RS-485 converter installed, the PC becomes a Modbus master on the meter's two-wire bus. Be clear about what the converter does: RS-485 (TIA-485) is the electrical standard, a differential pair, while the meter's application protocol — usually Modbus RTU — is something the selected driver has to match. Read the meter's communication manual before choosing a driver; a healthy converter proves nothing about protocol compatibility.
To prove the link:
- Confirm the converter in Device Manager (run
devmgmt.msc) and note the COM port it took. - Wire the pair to the meter's terminals per both manuals, watching polarity and the meter's signal-reference requirement — a converter referenced to PC earth can create a ground path the meter never asked for.
- Select the driver that matches the meter's documented protocol and set the PC serial port to the meter's baud rate, parity, data bits, and stop bits.
- For the Modbus device types (3x, 4x, 6x and their double-word variants), set the data format under System Parameter Settings > Device Properties > Conversion so returned words decode correctly.
- Put one known register in a numeric object, start online simulation — the mode that talks to equipment, not the disconnected demonstration — and compare the value against the meter's own display. Prove one address before building the full list; a plausible number can still come from the wrong register.
When you poll several registers, the Modbus RTU driver's adjustable settings include the maximum read command size in words, which sets how many registers ride in one request. If another master already polls that bus, settle its access rules before attaching a second polling application — competing masters corrupt each other's transactions. The procedure for testing HMI simulation against a live PLC covers the connection setup and the checks around it in detail.
The arithmetic that rules the PC out #
Worked example — documented limit, illustrative schedule:
- Required log: one reading per hour, so 24 readings per day.
- Documented session limit: 10 minutes.
- Time between samples: 60 min ÷ 10 min per session = 6 restarts needed to keep a session alive from one sample to the next.
- Per day: 24 h × 60 min/h = 1440 min; 1440 min ÷ 10 min = 144 manual restarts to cover 24 samples.
- Even at the fifteen minutes some sessions give you: 1440 ÷ 15 = 96 restarts per day.
Nobody staffs that, and every restart you forget is a missing record. Storage, by contrast, is trivial. Take an illustrative record — 2025-03-14 06:00:00,1234.5,kWh,OK plus a line ending — at about 35 bytes: 35 B × 24 records/day = 840 B/day, and 840 B/day × 365 days = 306,600 B each year, about 0.3 MB annually. A few megabytes of panel flash hold a decade of hourly readings. The constraint is session lifetime, not capacity.
Where the hourly log belongs #
| Platform | How the log runs | What it asks of you |
|---|---|---|
| Operator panel running this project | The same project is downloaded to the panel; the StringToLogFile function block writes each timestamped record and FTPClient transfers the saved files on a schedule | Panel hardware suited to the mounting and environment |
| Dedicated logging controller | A controller application reads the meter over its serial port and writes files with its own logging function blocks, with no display | A unit whose documented serial interfaces and logging functions match the meter |
| PC with continuous-runtime software | A SCADA or logging package licensed for unattended operation does the polling and storage | A real runtime license and a computer built to stay in the cabinet |
The panel row is the short path: the documented limit belongs to PC simulation, and a downloaded project is not a simulation session. You keep the driver and register list you already proved. If nobody needs a screen at the meter, the trade-offs in headless HMI server versus operator panel selection apply directly. When the log must stay on a PC, settle whether you need SCADA software for a Modbus HMI project first, then host that runtime on an industrial mini PC that lives in the cabinet as the gateway and historian.
When the session will not come back #
After a stop, three things commonly block the restart, and none of them is the reason the session ended:
- An earlier simulation process that did not exit can still hold the COM port, so the new session cannot open the device — terminate the leftover process in Task Manager before relaunching.
- The PC firewall can block the simulation's device traffic, particularly on TCP connections; allow the engineering software through rather than disabling the firewall wholesale.
- If the simulated window draws at the wrong scale after a restart, set Windows display scaling to 100 percent and reload.
The decision #
- Commissioning this week: use online simulation, ten good minutes at a time, restarting as needed. It proves the converter, wiring, driver, addressing, and decoding.
- Unattended hourly logging with operators present: download the project to the operator panel — StringToLogFile writes the record, FTPClient moves it.
- Logging with no display: a dedicated logging controller chosen by documented interface support, or a headless server platform.
- Logging that must live on a PC: continuous-runtime SCADA or logging software on an industrial computer. The simulation stays what it is: a commissioning tool.
Questions asked
How do I tell the simulation limit from a real communication fault?
The limit stops the session on a schedule: ten minutes documented, up to about fifteen reported, then the window closes and you reopen it by hand. A communication fault runs the other way — the session stays up while objects show no data or error states. If it always dies near the same elapsed time with the link healthy, it is the limit.
Does the 10-minute limit also apply over Ethernet instead of RS-485?
The documented condition is the medium-independent one: online simulation on the PC with the target device connected directly to the PC. A USB-to-RS-485 converter and a TCP connection to the device both count as direct connections, so the session limit applies either way. Moving the meter link from serial to Ethernet buys a cleaner cable, not a longer simulation.
Can I schedule an automatic restart of the simulation every ten minutes?
That is an attempt to work around the vendor's runtime restriction, and it is unreliable anyway: a timer-relaunched session is not guaranteed to be up at the top of each hour, and each restart risks losing the serial port to a process that never exited. The supported route is a downloaded project on a panel or software licensed for continuous runtime.
Will the same project log around the clock once it is on an operator panel?
Yes. The documented limit applies to On-line Simulation on the PC, not to a project downloaded to the panel; the panel runs it as its application, not as a session. You keep the screens, driver, and register list as built, and the StringToLogFile and FTPClient function blocks write and transfer records with no session clock running.
Is the Idle Timeout setting what is stopping my simulation?
No. Idle Timeout, configured in the range 1 to 43200, starts an Action Trigger after the screen sits untouched for the set period. It is a screen-behavior feature, not a session limiter, so adjusting it will not extend an online simulation session.