The INI file ships with no timeout entry, so a search finds nothing: you add PanelTimeout = 5000 yourself, under an existing heading, in milliseconds. On a cellular port forward on port 9999, size the entry above your measured transfer time, and keep a connection that never opens separate from a transfer that expires mid-copy.
The INI file has no timeout entry to find. It ships without one, and the documented fix is to add the line yourself, under an existing heading in the file the programming software reads:
PanelTimeout = 5000
The value is in milliseconds, so the documented example sets a 5 second wait. On a cellular port forward on port 9999, that wait is what expires when a remote project transfer stops mid-copy, and the fix from there is arithmetic: measure what the link delivers, then set the entry above it. This page gives the edit, the checks that separate a timeout from a router path failure, and the number to use on a slow link.
Why the file has no timeout entry
The INI file for this panel family, EA_.ini on the computer that runs the programming software, ships with no timeout entry at all. The vendor's support answer for file transfer over the internet documents adding it by hand: one line placed under a heading, with the value in milliseconds. The heading is not named in that answer, so the entry goes under an existing heading in the same file.
Two details decide whether the edit works. The entry name is PanelTimeout, spelled exactly. The unit is milliseconds, so the number you type is the number of milliseconds the software waits; typing it while thinking seconds is the classic error on this transfer, and HMI project transfer timeout: seconds, not milliseconds covers what that mistake does to a wait.
What each symptom points to
- The software never opens the connection. The failure is the path: the forward rule for port 9999, the panel address behind the router, or a firewall between them. A timeout entry changes nothing until a connection exists.
- The connection opens, progress starts, then the transfer stops with a timeout message. The wait is shorter than the transfer. This is the case the INI entry fixes.
- The same project loads in seconds on the plant LAN but expires over cellular. The wait suits LAN speed, and cellular throughput is a small fraction of it. This split is the subject of HMI remote access that works on Wi-Fi but not cellular.
- The transfer stops at about the same point every run. A fixed wait on a steady link always expires after the same amount of data. Stops landing at random points point at the link dropping, so check the router and its signal before editing anything.
Check the port forward before the wait
Confirm the rule sends external port 9999 to the panel address on the private network. The port the software speaks stays what it is no matter which external number the router forwards, the trap explained in why a port forward does not change the HMI programming TCP port. Where the path also crosses a controller firewall, the NAT rule has to rewrite source and destination both, the pattern shown in forwarding SSH through a controller firewall with DNAT and SNAT.
A forwarded port on a cellular router publishes a control panel to the public internet. Lock the rule to the one remote address it serves, or drop the forward and set up a VPN router for remote PLC and HMI access instead.
Add the entry
- Find the INI file the programming software reads, EA_.ini in this family. Installs and updates leave old copies behind, so confirm from the software's documentation or support which copy is live before you edit.
- Copy that file aside as a backup and note where you kept it.
- Open it in a plain text editor.
- Under an existing heading, add one line:
PanelTimeout = 5000 - Save, reopen the file, and read the line back: the name spelled PanelTimeout, the value 5000.
- Retry the same transfer from the same computer over the same path with the same project. One change, one retry.
Worked example: 30 MB over a 1.5 Mbit/s cellular link
A 30 MB project has to reach a panel through a cellular router forwarding port 9999. A file copy over that link measures 1.5 Mbit/s of sustained upload. The plant LAN runs 100 Mbit/s.
Convert the project to bits: 30 MB × 8 = 240 Mbit.
On the LAN, 240 Mbit ÷ 100 Mbit/s = 2.4 s. The documented 5000 ms entry is a 5 s wait, and 2.4 s fits inside it.
On cellular, 240 Mbit ÷ 1.5 Mbit/s = 160 s. In 5 s the link moves 1.5 Mbit/s × 5 s = 7.5 Mbit, which is 0.9 MB, about 3 percent of the project. The wait ends with nearly the whole transfer still to go.
Size the entry above the transfer time: 160 s × 1.25 = 200 s, which is 200000 ms. The line becomes PanelTimeout = 200000. If the remote console repaints slowly even before a transfer starts, why an HMI remote console runs slow over a cell modem explains where that time goes; the throughput number feeds the same arithmetic.
What the retry tells you
- The transfer completes. Keep the entry, file the backup and the edit with the maintenance record, and write down the throughput you measured so the next resize starts from data.
- It still expires at about the same point. Re-measure the throughput at the hour you transfer; cellular capacity changes through the day, and an entry sized from a quiet evening can be short at a busy midday. If the fresh number still says the transfer fits inside the wait, the link is dropping the connection and the router is the next check, not the INI file.
- The connection never opens. Path again: forward rule, address, firewall. The entry cannot help.
What to set
Recommendation: Add PanelTimeout = 5000 to the INI file the programming software reads as soon as a remote transfer reaches the panel and expires, then replace the number with your own: milliseconds at least a quarter above the worst measured transfer time, 200000 on the example link. Keep 5000 for LAN-speed paths. If the connection never opens, leave the file alone and fix the forward on port 9999 first, locked to one source address or moved behind a VPN.
Questions
Why is there no PanelTimeout line in my INI file?
The file ships without the entry. You write it in yourself, under an existing heading, exactly as PanelTimeout = 5000. Searching the file again will not produce a line that was never there.
Is the PanelTimeout value in seconds or milliseconds?
Milliseconds. The documented example, 5000, is a 5 second wait. To allow a 3 minute transfer you write 180000, and the example link in this article calls for 200000.
The software cannot even connect to the panel. Will the timeout entry fix that?
No. A connection that never opens is a path problem: the port forward on 9999, the panel address behind the router, or a firewall between them. The entry only lengthens a wait that has already started.
How do I keep the panel off the public internet while transferring remotely?
Restrict the forward rule to the single remote address that needs it, or drop the forward and run the remote link through a VPN router. The transfer then works the same way, with the same INI entry sized from your measured throughput.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.