11.10.3 Eliminating Codesys Web Visualization Errors; Table 57: Errors And Its Solution - WAGO -I/O-IPC-C6 Manual

Wago-i/o-system 750
Hide thumbs Also See for WAGO-I/O-IPC-C6:
Table of Contents

Advertisement

132
CoDeSys 2.3 Runtime Environment

11.10.3 Eliminating CoDeSys Web Visualization Errors

If problems occur when using CoDeSys Web visualization, please try to find a
solution in the following table first. If you cannot eliminate the problems, please
contact WAGO support.

Table 57: Errors and its solution

Error
Internet Explorer
reports the error
"APPLET NOT
INITIATED"
Web visualization is not
displayed
Web visualization
"freezes".
Web visualization stops
after a longer period of
time.
Web visualization
cannot be loaded into
the I/O-IPC
Bitmap is not displayed If the name of an image file contains umlauts, the Web server cannot
Java console reports:
"Class not found"
Web visualization is
static, all process values
are "0"
Solution
Close all Internet Explorer windows and restart it. If the error continues
to occur, this indicates a missing or damaged file.
Check whether the Java archive "webvisu.jar" is completely available in
the folder "/PLC" of the I/O-IPC using FTP. The original file can be
found in the installation path of CoDeSys (usually under
C:\Programme\WAGO Software\CoDeSys V2.3\Visu\webvisu.jar).
If necessary, replace the damaged file using FTP or force the download
of all files in CoDeSys with Purge All > Compile All > Log In.
Have you installed the JRE? Check the firewall settings, e.g. if port 8080
is open.
The call-up intervals selected in the task configuration are too small. As a
result, the I/O-IPC Web server, which is executed with a low priority,
receives insufficient or no computing time.
If no (explicit) task configuration has been provided, the PLC_PRG is
(implicitly) executed as a free running task with Priority 1. This allows
the Webserver too little computing time. Always provide a task
configuration when using Web visualization. In doing so, the call-up
interval should not exceed three times the average execution time. When
determining the execution time, ensure that the PLC program is not
"steady state."
It may be that not all files fit into the file system of the I/O-IPC. Do not
delete necessary data (e.g., via FTP).
interpret these image names.
The JRE does not find the entry point for the class "webvisu.class" in the
Java archive "WebVisu.jar. The Java archive is probably incomplete.
Delete "WebVisu.jar" from the Java cache and/or deactivate the cache. In
this case, the I/O-IPC requests the archive (applet) again.
If the problem continues to exist, upload the project onto the I/O-IPC
again.
The cause is that the process data communication has failed.
If web visualization is operated over a proxy server, then a SOCKS
proxy is also necessary for process data exchange in addition to the
actual HTTP proxy.
WAGO-I/O-SYSTEM 750
758-874/000-131 WAGO-I/O-IPC-C6
Manual
Version 1.0.0

Advertisement

Table of Contents
loading

This manual is also suitable for:

I/o-system 750758-874/000-111

Table of Contents