cliu 98035366a7 R1.05 V5 and V6: graphics files and history checks on the test server

V5 (read-only): Layouts.readme and components identical; JCEF browser
component now loaded from tls\exe\lib\jcef; connectrdp.cmd present;
jwuiutl help identical; AOG_UAC_MethodArg_Call2 added, AOG_OPCUA_Methods
not installed; web trend DataSource.js re-enables the pen checks behind
ISS-041 (probably fixed, not tested).
V6 (read-only): hisdbg 1/20/6 as on R1.03; history and item start/stop
scripts differ only by the extension hooks.
ISS-092, 097, 100, 101 closed; notes on ISS-094, 096.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-09 11:20:38 +11:00

5.3 KiB

Raw Blame History

task: Deploy, remove, export, validate and search displays; open them in the browser version: R1.05 (first written for R1.03) source: IM 36K10C50-01EN §1.5 (R1.05 5th ed. Feb. 2026); IM 36K10R30-01EN §1.1, §4 (R1.05 4th ed. Feb. 2026); practiced on CI-Eng-Sample 2026-10-01; sample operator HMI (8 displays) and validate test 2026-10-06 status: verified on R1.03. R1.05: manuals re-checked 2026-10-08 (jwuiutl options and HTML export unchanged except the search output wording); not re-tested on the R1.05 test server (shared server: no deploy, validate or export allowed); `jwuiutl --help` and the deploy folder structure there awaiting user verification

Deploy and check displays

On R1.03 no admin rights were needed (C:\Users\Public\Yokogawa\tls\wap). On the R1.05 test server the data root is C:\Yokogawa\CIServer\tls: use %TLS_WAP_PATH% and check write access before deploying. jwuiutl.cmd is in tls\com (on PATH); call it through cmd (cmd /c "jwuiutl.cmd …"). jwuiutl.cmd --help prints the option list (read-only; R1.03 help text matches the C50 summary §2, but says -o defaults to the current directory, whereas the export without -o wrote into mobileoperator\operatorInterfaces\<deployment> — verified R1.03).

1. Deploy / remove (sample scripts)

examples/CI-Eng-Sample/displays/deploy_displays.cmd: copies the 8 sample displays (CIENG_Header, CIENG_Overview, … CIENG_TankFaceplate) to %TLS_WAP_PATH%\cfg\operatorInterfaces\DEPLOY\displays\ and runs jwuiutl.cmd -e HTML -i -f DEPLOY <name> for each (HTML into %TLS_WAP_PATH%\mobileoperator\operatorInterfaces\DEPLOY\displays\). remove_displays.cmd deletes both files of each (close the displays in the Edit Module first). Deploy after load.cmd so the items exist. Verified 2026-10-06: remove → 0 sample files left, deploy → exactly the 8 XML + 8 HTML files.

For another display: copy <name>.xml into DEPLOY\displays and export it the same way. Displays with symbols also need the symbol files in DEPLOY\symbols.

2. Validate (re-saves the validated files)

cmd /c "jwuiutl.cmd -d -v -i -l <scratch>\validate.txt"

Per display: Validating <name> then Info: No problems found, or *** Validation failed for display <name>: with Problem: <component>: Connected item is not found (<item>). Skipped: *** Display locked <name> (open in the Edit Module or a stale .lck; -u unlocks — with approval), displays saved by a newer version. -vf re-saves all displays — only with approval.

-v also re-saves (tested 2026-10-06: jwuiutl -d -v -i -l … CIENG_Test reported No problems found and rewrote the file, 9 618 → 11 191 bytes: default values dropped, positions moved into attributes - same content). Run it on copies, or redeploy the source files afterwards. On 2026-10-02 a validation of eight displays once hung on one of them and left <name>.lck and <name>.xml.tmp (stop the java process, delete both files); not reproduced on 2026-10-06 (ISS-075).

3. Search

cmd /c "jwuiutl.cmd -d -m <term> > <scratch>\match.txt 2>&1"

CSV Type, File, Component per match (R1.03; the R1.05 manual describes the output as space-separated, not checked, ISS-094); -M adds actions and properties. Use it before deleting or renaming items to find the displays that use them.

4. Open in the browser (HTML display)

http://localhost:8080/mobileoperator/?d=<display> (&l=<layout>). The user logs in with a CI Server user. The page shows the operator frame (menu, navigation buttons, alarm banner, status line). To switch displays type the name in the display box and press Enter. To refresh, use the display menu View > Reload (keeps the session) — reloading the browser page ends the session and needs a new login. Check live values by writing a test value (itmval -p, test items only).

R1.05 manual (IM 36K10R30-01EN §4.10, from docs): the restrictions "no automatic reconnect after a disconnect" (reliable socket) and "no HTML export from CI View (Edit Module over Remote Connect)" are no longer listed; enterprise displays and enterprise user-profile settings are no longer excluded; new: HIS-TSE connections are not supported in the HTML display. Not tested on R1.05 (ISS-093).

Verified (2026-10-01)

Remove → deploy recreated both files; -e HTML output identical to the Edit Module's HTML; validation of CIENG_Tank No problems found (also after a sample reload with new item ids — but a stale <itemId> then shows 0 at run time, ISS-052); search worked; browser showed live values. HTML trend without line: ISS-041 (cause and workaround in trend.md §6).

R1.05 test server: installed files (V5, 2026-10-09, read-only)

jwuiutl --help prints the same text as on R1.03 (so the help still says -o defaults to the current directory, ISS-094). The -m / -M output format was not checked (a search is not run on the shared server).
jwuiutl.cmd and jwuiged.cmd now load the new web browser component based on JCEF (change e12737) from %TLS_ROOT_PATH%\tls\exe\lib\jcef (R1.03: %TLS_WAP_PATH%\webapps\jcef) and add tls\exe\lib\* to the class path. connectrdp.cmd (RDP Connect) is installed in tls\com.
DEPLOY has the same sub-folders as R1.03 (components, displays, layouts, locales, symbols, thresholds); the factory component list is identical.

5.3 KiB Raw Blame History