HMI remote file list shows only 8 logs: expand the page

Why does the remote file list stop at 8 files?

The page you open at the panel's address builds a list of 8 links, and that count lives in the supplied web page, not in the panel: the web server still serves every file on the card when you request its complete address. The panel is doing two jobs. The web server serves any file whose address you request. The page draws the list of links you click. Those jobs are separate, and the list is the short one. The example page was built with 8 entries, and every file past the eighth is served without being listed.

The count is a property of the page, in the same family as a shipped page that shows only 10 of your screens. Nothing about the card, the logging setup, or the remote access service changes it. File 9 and everything after it open the moment you type their addresses, which is the proof the serving side works.

Is there a setting that raises the file count?

No panel setting raises it, and none is documented: the count of 8 entries sits in the HTML example that ships with the remote access feature, and that HTML is a reference for building your own pages, so the page is the part you extend. The setup side of remote access is about enabling the service and admitting clients. None of those screens holds a file count. Searching them for one costs production time and returns nothing, because the number lives in the page source.

The page ships as a working example, meant to be extended into something of your own. Its list takes as many entries as you build into it, and the same server already hands you file 9 and beyond whenever you type the address.

How do you check that the other files are still there?

Type the complete address of one file the list leaves out, and it should open: that single test, about 2 minutes per file, separates a display limit in the page from a logging or card fault that no page edit will fix. Work through it in order.

1. Write down the file names the list does show, all 8 of them.
2. Pick one file you know exists that is missing. The name comes from an earlier download or from the file naming in the logging setup.
3. In the browser's address bar, type the panel's address, a slash, the folder, and the file name, for example http://192.168.1.50/logs/TEST0527.CSV.
4. Repeat with two more omitted files, so one typo cannot point the search at the card.

If the files open, the card and the logging setup are doing their jobs, and the fault is confined to the list the page draws. If a file fails to open, check the spelling and the path first, because a misspelled address looks exactly like a missing file. Then look at the card and the logging setup before touching any page.

Do not reformat the card or delete old logs to treat a list that runs short. That is the one way to turn a display fault into lost data.

What else hides files from a remote list?

Each hidden file has one of five causes, and the page limit is only the first: a fixed list in the page, a wrong name or path, a stalled web server, rollover deleting the oldest files, and an FTP view that scrambles records. Match your symptom to the line below before you edit anything.

• The list holds at 8 entries, and omitted files open by complete address. The page limits the list. Edit the page as described below.
• Omitted files fail by address with a not-found answer. The name or path is wrong, or the logging stopped writing. Check the file naming in the logging setup, then the card.
• The list page itself will not load while an FTP session to the same panel still works. The web server is the fault; start with a panel whose web server stalls while FTP answers.
• Files that were on the card last month are gone this month. The log rollover is deleting the oldest files as the drive fills; confirm the deletion order before you count on history, as confirming oldest-file rollover on a full log drive shows.
• A file looks scrambled viewed over FTP but reads clean once saved locally. That is the transfer view, covered in a log that looks mixed over FTP but fine saved locally.

How do you expand the list in the web page?

Edit the page, in a copy, after one backup of the project and the current page files: the list grows by adding entries to the section of the page that builds it, and the original page stays on hand for rollback. Take the steps in this order.

1. Back up two things: the project, and the page files as deployed today.
2. Find the page source. It sits in the project or in the installed example set for your panel and software version; the remote access setup section of the panel's help file documents this material.
3. Open the page and find the part that writes the file list. Count the entries. You will find 8.
4. Read how the entries are built. Hand-written entries each name one file, so you add one line per file. Entries filled from a bounded set of names take a bound instead, so you raise the bound.
5. Edit the copy, using the syntax already in the page. Generic web code the panel's server never supported is the fastest way to break the page.
6. Deploy with the workflow the documentation gives for your panel, and keep the original page file aside.

Example: how does a station with 31 log files get its full list?

A station logging one CSV file per day holds 31 files after a month, the page lists 8, and the arithmetic says 23 files are reachable only by address: 31 minus 8 leaves 23, about 74 percent of the month invisible. Walk the whole job with those numbers.

The station writes one CSV file per day to the card. On day 31 the card holds 31 files, and the remote list shows 8.

The check: three omitted files opened by complete address, about 2 minutes each, 6 minutes total. The card and the logging setup are fine.

The edit: the page held 8 hand-written entries, so the fix is 23 new lines, each naming one file, for 31 entries in total. One sitting covers the work.

The result: 31 of 31 files open from the list. On day 32 a new file appears on the card, and a hand-built list needs one more line. That upkeep is the price of a fixed list, and it is the reason to check whether the page fills its entries from a bounded set before you type 23 lines: a raised bound covers file 32 and the days after it.

How do you verify the new page and keep a rollback?

Reload the page from the panel's address, click every entry you added, and open one omitted file by its complete address again: all of those must pass, and the saved original page is the rollback if the edited one misbehaves. Count the entries first: 31 where there were 8. Click every entry you added; each must open the file it names. Open one omitted file by address once more, to confirm the edit left direct access alone. Repeat after the next log file is written, because a list that breaks on file 32 is a list that is not finished.

If the edited page fails to load or an entry opens nothing, put the original page back. You return to the working 8-entry list, and you retry the edit offline with the failed copy in front of you.

Recommendation: spend the first 6 minutes proving three omitted files open by complete address, then edit the page when the list is the tool your team uses at the panel address every day. When the station writes a file daily and no one owns the page, skip the list for archives and collect the log files over FTP on a schedule, leaving the shipped list for the newest files.

Questions