ci-server-engineer/knowledge/manuals/IM36K10R30-01EN.md
cliu 83af63ab53 R1.05 re-check batch 2: graphics, history, portal, system-management, items
Full manual diffs (C50, R30, C60, L20, C40, L35, R10, R20, J10, L30, L50,
P30, G10, C10) and read-only checks on the shared R1.05 test server where
the permission system allowed them. Skills and summaries moved to R1.05.
Issues ISS-092..129 (gaps 104-107, 114-115, 130-131 unused); ISS-074
closed (manual and software agree), ISS-091 corrected by ISS-119.
version-differences: unlisted manual changes and installed-only changes.
r105-verification: V5-V9 and new not-tested rows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 19:29:15 +11:00

122 lines
9 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
manual: IM 36K10R30-01EN
title: Graphic Display Setup
edition: 4th Edition, Feb. 2026 (R1.05); first summarised from the 3rd Edition, Sep. 2023 (R1.03)
version: R1.05 (first written for R1.03)
status: R1.05 re-check 2026-10-08 - full text diff reviewed (§5 below), from docs; installed R1.05 files (Layouts.readme, web client) awaiting user verification. R1.03 results - HTML display (Mobile Operator) and a project layout (CIENG_Operator) verified in the Operator Interface (desktop) and the HTML display 2026-10-01; sample operator HMI with tab set, popup layout and per-user layout verified on both clients 2026-10-06; dataset forms, form language and dual screen from docs
---
# Graphic Display Setup (R1.05)
How the operator interface is framed (layouts), how custom dataset forms are added, and how
displays run in a web browser (HTML display, "Mobile Operator"). Section numbers refer to the
manual. Building displays: `IM36K10C50-01EN.md`; AOG library: `IM36K10C60-01EN.md`.
## 1. Files and folders (installed)
| What | Where (`%TLS_WAP_PATH%` = `C:\Users\Public\Yokogawa\tls\wap` on the R1.03 machine; the R1.05 test server has its data root under `C:\Yokogawa\CIServer\tls` - read `set TLS`) |
|---|---|
| Displays (operator interface) | `cfg\operatorInterfaces\DEPLOY\displays\<name>.xml` (plus `.lck` while open in the Edit Module, `.autosave`) |
| Symbols | `cfg\operatorInterfaces\DEPLOY\symbols\` (≈ 3100 files incl. the AOG library) |
| Layouts | `cfg\operatorInterfaces\DEPLOY\layouts\Layouts.xml` (+ `Layouts.readme`, `Layouts-original.xml`) |
| Components, locales, thresholds | `cfg\operatorInterfaces\DEPLOY\components\`, `locales\`, `thresholds\` |
| HTML displays | `mobileoperator\operatorInterfaces\DEPLOY\displays\<name>.html` |
| Dataset forms | `cfg\dialog\dialogs\<name>Dia.xml` (components `<name>Com.xml`, definitions `JToolsGlobalDef.xml`); texts in `cfg\properties\` |
`DEPLOY` is the deployment name (a user's *Operator Interface Deployment* field selects another;
empty = `deploy`).
## 2. Layouts (§1)
- `Layouts.xml` holds several `<layout>` elements under `<layouts>` (common options such as
`debugActivationKey="CONTROL SHIFT F6"` for the graphics debugger, Java only). A layout =
menu, toolbar, **frame set (required)**, status line.
- Layout options: `name`, `icon`, `title` (`$<frame>` = title of the display in that frame),
`drawBorder`, `sizingAllowed`, `minimizingAllowed`, `closingAllowed`, `alwaysOnTop`, `modal`,
`lookAndFeel`, `initialPosition` (… `fitFrames`), `initialPositionX/Y`, `initialSize`,
`initialSizeWidth/Height`, `maximumOpen`, print orientation and margins (Java only).
- Menu items (§1.5, e.g. `menu.file.login`, `menu.view.reload`), toolbar (§1.6), status line
items (§1.7, e.g. graphics queue level), frames and tabs (§1.8), translations (§1.9).
- Which layout opens: *In layout* of an *Open display* action (Edit Module), or the user's
*Layout* field (Engineering Module, Authorization > Users); empty = `default`. Verified
2026-10-06 with the sample user `CIENG` on the desktop and in the HTML display.
- Dual screen (§1.10): copy the layout and the banner display as `<name>_1` / `<name>_2` and let
each banner open its main display in its own layout.
- **Verified (2026-10-01, former sample layout)**: sample layout `CIENG_Operator` (skill `graphics`, task `layouts.md`):
second window from an *Open display* action, own menu/toolbar/frames, `$default` title, popup
layout, F11; the Operator Interface reads `Layouts.xml` only at start. The installed
`Layouts.readme` is the full reference for options and commands. Since 2026-10-06
`CIENG_Operator` is the sample operator HMI (header frame, tab set, banner) with the popup
layout `CIENG_Popup`; web and desktop findings for tab sets in `layouts.md` §6.6.
- **Installed layouts**: `mobile`, `default`, `sxga1f/r`, `uxga1f/r`, `wxga1f/r`, `wsxga1f/r`,
`wsxgap1f/r`, `wuxga1f/r`, `ResizablePopup`, `FixedPopup`, `popup`, `Splash`, `tuningpanel`,
`faceplate`, `SelectMode`, `Setpoint`, `mapviewer` (`f` fixed / `r` resizable per screen
size). The test system's `Layouts.xml` also has a custom layout added by the author; keep a copy
of the original before editing.
## 3. Dataset forms (§2, §3)
Engineering-Module-style forms for operators: write `<name>Dia.xml` in `cfg\dialog\dialogs`
(never change the existing forms there), optionally a property file per language, then place a
*Dataset form* component on a display. Objects: `label`, `textField`, `checkBox`, `comboBox`,
`panel`, `component` (`JhmiRecordNameCom`, `JhmiTreeComboBoxCom`, `JhmiSelectAvailableCom`,
`JhmiTimeSelectorCom`); `meta` links an object to a dataset field: `field=`, `mixedValue=`,
`choices=<dataset>[,<field>[,<filter>]]`, `none=`, `available=`/`selected=`, `label=`,
`dateVisible=`, `visibility=`. Layout by `column`, `top="+"`, `right="*"`. Localisation via
property files and language codes (§3.5).
## 4. HTML display / Mobile Operator (§4)
- Export: Edit Module saves the HTML version automatically when the display has **HTML
display** ticked; or `jwuiutl -e HTML -i [-o <path>] [-f <deployment>] [<display>]` (without
`-o` it writes into `mobileoperator\operatorInterfaces\<deployment>`). **Verified**: both give
identical HTML (except a time stamp).
- Open: `http(s)://<host>:8080|8443/mobileoperator?d=<display>&l=<layout>&u=<user>` or *Open* of
*Mobile Operator* on the Remote Connect page. Login with a CI Server user (manual, or SSO via
`https://<host>:8443/auth/mbl`); user profile fields used: password, authorization group, ASA,
shelving group, process areas, logoff timeout, deployment, **layout**, initial display,
locale; not supported: destinations, playback, and (R1.03 only) enterprise - R1.05 marks the
*Enterprise* settings as supported (§4.4). The earlier note "layout not" was a misreading of
a garbled text extraction: the table marks *Layout* as supported in R1.03 and R1.05, as the
installed software showed (a logon as `CIENG` without `?l=` opened `CIENG_Operator`,
2026-10-06; ISS-074, ISS-095). Login control: `dssana.sup` interface *mobile operator* (the
R1.03 manual misspelt the file as `dssna.sup` in §4.5; fixed in R1.05).
- **Verified (2026-10-01)**: `http://localhost:8080/mobileoperator/?d=CIENG_Tank` showed the operator
frame (menu, navigation buttons, alarm banner, status line) and the display; the number field
updated live; the alarm overview listed the sample's alarms. **Reloading the browser page ends
the session** (login again); use the display's own menu *View > Reload* instead (keeps the
session, confirmed by the user), and the display box to open other displays.
- Differences from the Java operator interface (§4.7): layout windows live inside the browser
window (no resizing of embedded layouts); displays need explicit width/height; names are
case-sensitive; zoom and pan not supported; some mouse/keyboard events and actions missing;
no enterprise displays in R1.03 (§4.7.15 *Enterprise Solution*, removed in R1.05, §5).
Components supported (§4.8): alarm overview, display, group, symbol, trend, visibility
group/layer, parameters, web browser (with listed properties).
- Full screen F11, Chrome shortcuts or `chrome.exe --app=http://<host>:<port>`.
- **Test system**: the HTML trend of `CIENG_Tank` (removed from the sample 2026-10-06) drew no line although history existed; browser
console `Mismatch between number of labels … and number of columns in array (51)` (ISS-041).
Cause (2026-10-02): the web trend code always builds 50 data columns, so a trend draws only
with 50 visible pens; workaround `add_trend_spares.ps1`, details and web/desktop differences in
skill `graphics`, `tasks/trend.md` §6. R1.05 web client not checked yet (ISS-096).
## 5. Changes in R1.05 (from docs, full text diff 2026-10-08)
The revision table lists only R1.05 §4.8 (Enterprise Operation properties) and §4.10
(restrictions); there is no R1.04 edition entry. The diff shows:
- **Enterprise operation on the HTML display**: §4.7.15 *Enterprise Solution* ("not supported
on the HTML display") removed; general restriction "Enterprise Operation features not
supported" removed; §4.4 user profile *Enterprise (all)* now supported; §4.8 now marks as
supported: display primary/secondary data location and *Enterprise* flag (§4.8.3), symbol
definition *Enterprise* (§4.8.5), trend *Enterprise* (§4.8.7); alarm overview no longer lists
*Enterprise mode* as unsupported (§4.8.1). *(§4.4, §4.7 and the alarm overview are not named
in the table)*
- §4.10 restrictions: removed "Reliable Socket (automatic reconnect) not supported - log in
again after a disconnect" and "export to HTML from CI View (Edit Module over Remote Connect)
not supported"; added "HIS-TSE connection not supported by the HTML display".
- §1 layouts: `shell <where>` description reworded only; no option or command change.
- §4.5: setup file name corrected to `dssana.sup` (R1.03 text had a typo).
- Chapters 2–3 (dataset forms) unchanged.
None of this is tested: the R1.05 test server is shared and no enterprise configuration exists
there (ISS-093).