Skip to content

(General) Troubleshooting

Stephan Stricker edited this page May 5, 2020 · 8 revisions

Diagnostic page

The diagnostic page shows information about the connected clients, active bindings and more. It has to enabled in the mappviewcfg file. Click on advanced parameters (1) and then activate the diagnostic page (2). The diagnostic page is accessed from the browser which is connected to the mapp View server with the following URL: Ip-address:81/server/info. A login is only possible for users that correspond to the role configured for accessing the diagnostic page. After logging in, the start page is displayed.


OPC Variable

When an OPC variable does not show up as expected try the following steps to troubleshot the issue.

  1. Make sure the variable is visible in the OPC configuration (Connectivity)
  2. Make sure the variable is activated in the OPC server configuration (Connectivity)
  3. Make sure access rights are correct, add at least one user role in the OPC configuration (Connectivity) and give this user permission to read the variable

Logger

When the points listed above do not solve the issue open the logger and activate Visualization, check if an error is reported for the missing variable

Error ID: -2134832869 This can be caused if the local OPC server is configured to information model 2.0. In this case a "OPC UA remote Server configuraqtion" must be added to the mappView under the configuration view. Change the namespace to "http://br-automation.com/OpcUa/PLC/PV/" (Help File 4e9b500a-c34b-4753-923e-075b8a85ed57)

Languages do not show up in the language selector

Also multiple languages are configured only a few show up in the selector in mappVIEW. Languages must be defined in *.language file in the logical view but also in the *textconfig file in the configuration view. All languages must at least have one entry in any of the text files. If a language is only defined but has no text in any text file it will not show up in the language selector.

Scrolling no longer works in Chrome browser

If it is not possible in a Mapp View Visu to perform any touch actions on the touch display (e.g. scrolling a table widget), it could be due to the deactivated "touch events". The setting for this has migrated in the last chrome versions. To turn touch events back on call Chrome with the parameter "–touch-events".

Clone this wiki locally