HMI web page shows only 10 of your screens: why and the fix

Why the menu stops at 10 screens

The menu you see in the browser is HTML, served from files stored in the panel's web-server folders. Those files are the factory default set, and the default set carries entries for screens 1 through 10 and none beyond. Switching the web server on serves exactly those files; it writes no new entries for your project. A 54-screen project and a 12-screen project get the same 10-entry menu.

The project is separate from the menu. The panel runs every screen of the project at its own touchscreen, and the web server hands a browser a fixed page set that references the first 10. A short menu is an index problem, so the fix lives in the address line or in the served HTML, never in the project.

Symptoms and what each one points to

• The menu ends at entry 10 on every computer and in every browser. That points to the default page set on the panel, not to the network, the PC or the browser.
• The project holds more than 10 screens in the development software. The screens exist; only the served index is short.
• A direct-screen address with a number above 10 opens the screen. The panel serves screens by number, and the index is the only fault.
• The menu shows fewer than 10 entries, or none. Check the project version on the panel and the web server's state before blaming the default pages.
• A page opens but the live values are zeros. That is a data-address fault, covered in why an HMI web server shows zeros for PLC tags.
• No page loads at all while the panel answers on the network. That is a server-level fault; a web server that stalls while FTP still works covers it.

Open any screen now with its direct address

One common touch-panel family documents this exact pattern:

http://your.ip.address/fancyScreen.html?screenNum=44

Replace your.ip.address with the panel's IP address and 44 with the number of the screen you need, exactly as the project's screen list shows it. Type the finished address into a browser on the same network as the panel and the screen opens on its own, no menu involved.

Panels from other makers that serve one page per screen use the same shape: an address that ends in the screen number. The web-server section of the panel's manual prints the pattern when the maker documents one; when no maker documents one, the HTML route in the next section is the path.

This is the same-shift fix. It puts one screen in front of one browser, and the menu still lists 10 entries afterward. Browser access reaches more than screens: the same web server can expose live controller values, which reading PLC tag values from an HMI panel web server covers.

One safety note: keep the panel's web server on the plant network, and reach it from outside the plant only through the VPN the site already runs, as in view a plant HMI web page from home over VPN.

Build a standing menu in the served HTML

For a menu operators can browse every shift, edit the HTML files and add the missing entries. The remedy needs ordinary HTML editing, and the panel family in question documents it as the standing fix.

1. Copy the original HTML files out of the web-server folders and keep them. With the backup in hand you can restore the original menu at any time.
2. Open the menu page and read how one working entry addresses its screen. Every new entry copies that shape with a different screen number.
3. Add one entry per screen the operators need, using the project's real screen numbers from the development software's screen list.
4. Load the edited files back to the web-server folders by the transfer path the panel's manual documents, and keep the direct address working as your fallback while you test.
5. Browse the new menu from a browser and open representative entries: several from screens 1 through 10 and several from the numbers above 10, before a shift depends on the menu.

Worked example: a 54-screen project whose menu lists 10

Inputs, each with its source:

• Project size: 54 screens, counted in the development software's screen list.
• Served menu: 10 entries, the panel's default page set, covering screens 1 through 10.
• Direct address: http://your.ip.address/fancyScreen.html?screenNum=44, the documented pattern above with screen 44 as the target.

Rule in words: a menu that stops at exactly 10 while the project holds more than 10 is the default-page limit. Every screen above 10 still exists and is reachable by its number.

Arithmetic:

• Screens with no menu entry: 54 - 10 = 44.
• First screen the menu leaves out: 10 + 1 = screen 11.
• Last screen to account for: screen 54.
• Address for one of them, screen 44: http://your.ip.address/fancyScreen.html?screenNum=44.

Result: the browser opens screen 44 straight away. The menu keeps its 10 entries until the HTML carries the missing links.

Decision: an exact stop at 10 in a larger project points to the default page set, so use the direct address for access today and the HTML entries for the standing menu. A menu that stops at another number, or a project with 10 screens or fewer, has a different cause; work down the symptoms list above.

Checks that settle it

• Count the screens in the project file. Ten served entries against a larger count is the default-page limit.
• Open screens 1 through 10 from the menu. If they open, the pages serve and the index is the fault.
• Request one screen above 10 by its direct address. If it opens, the index is short and the addressing works, which settles the case.
• If the direct address fails on every number, including 1, check the panel's IP address and the screen number first, then the web-server section of the manual. A menu edit comes last.

What to do, in order

Recommendation: When the served menu stops at exactly 10 and the project holds more screens, type the direct-screen address for same-shift access, then edit the served HTML for a standing menu and keep the original files backed up. When the direct address fails on every number, stop editing web files and settle the panel's IP address, the screen numbering and the manual's web-server section first.

Questions