272 Run-time System CODESYS 2.3
WAGO-I/O-SYSTEM 750
750-8207 PFC200 CS 2ETH RS 3G
Manual
Draft version 1.2.1 from 2017-09-13, valid from FW Version 02.06.20(09)
8.12.3 FAQs about CODESYS Web Visualization
How can I optimize the applet for special screen resolutions?
In order to optimize the Web visualization for display on a device with a fixed
resolution, proceed as follows:
In the “Target system settings”, enter the pixel width and height in the tab
“Visualization”. When the visualization is created, the visible area is highlighted in
gray. However, the actual pixel width and height of the Web visualization is
defined by the attributes “Height” and “Width” of the HTML APPLET tag in the
“webvisu.htm” file. Do not forget to also adapt these parameters to the existing
resolution.
Which JRE should I use?
Java2 standard edition Version 1.5.0 (J2SE1.5.0_06) or higher is recommended.
This is available free of charge at www.oracle.com.
Microsoft's MSJVM3810 was also tested. For PDAs, there are runtime
environments available from other manufacturers (JamaicaVM, CrEme, etc.).
Please consider that for the Web visualization, these solutions can behave
differently within their scope of services (e.g., stability) than those mentioned
above.
Should the Java Cache be used?
This depends on the situation. After a standard installation, the cache is enabled.
If the cache is enabled, the JRE uses it to store applets and Java archives. If the
Web visualization is called up a second time, it requires considerably less time to
start because the applet (approx. 250 kb) does not need to be reloaded via the
network, but is already available in the cache. This is especially useful when
network connections are slow.
Note:
The Java archives may not be completely transferred into the cache due to
network failures. In this case, the cache must be cleared manually or disabled.