Problem communicating Mobile UI

Find and share HowTos to various installations / configurations!
6 posts • Page 1 of 1
jeissonsierrac
Posts:62
Joined: Wed Jun 03, 2015 9:37 pm

Problem communicating Mobile UI

Post by jeissonsierrac »

Hi good day,

We are trying to implement a mobile application, but we are presenting inconveniences of communication when making the project configuration on the phone the application will be registered but not start; And sends the following error message.

Connection to (SYS: 0 Data -num 0 CONN: 1) @XXXX: 4897 failed, new attempt in 1 secs



Thank you very much in advance

mkoller
Posts:741
Joined: Fri Sep 17, 2010 9:03 am

Re: Problem communicating Mobile UI

Post by mkoller »

That simply means the UI could not establish a TCP connection to your data manager on port 4897.
Usually you'll go through the proxy manager (WCCILproxy) but you always need to make sure that the IP address you have set in the config file is reachable
from the mobile, the port you're using is not blocked by a firewall and if you have defined hosts by name that these are resolvable to IP addresses by the DNS server your mobile is using.

jeissonsierrac
Posts:62
Joined: Wed Jun 03, 2015 9:37 pm

Re: Problem communicating Mobile UI

Post by jeissonsierrac »

Hi good day

I was reviewing comments:

And check some things and;

Yes, I have access from the phone to the established IP address.
The communication port 443 - 80 is already enabled.

When I make the configuration, it registers the project but it indicates the same error.

Run a test with WinCC OA Desktop UI 3.15 x64 with the same configuration that I'm placing on the mobile UI and it does not start.

Image

I have done step by step as indicated in the help.

I do not know if I need to add configurations in the project configuration file.

I appreciate if I could collaborate.
Attachments
Error.jpg

schneebergera
Posts:89
Joined: Sun Apr 03, 2016 5:52 pm

Re: Problem communicating Mobile UI

Post by schneebergera »

Hello,
please clear the webclient cache dir [.wincc_oa-cache] on the client machine and give it a try once more.
If "WinCC OA Desktop UI 3.15 x64" connection is also not working, I will not expect an mobile-UI issue.
Try to reach the demo project [http://demo.etm.at:80] - is it working? [actual app-version (3.15.3)].
As already mentioned, WinCC_OA relies on a working name resolution. As I have no detailed logs I assume the machine name cannot be resolved by webclient.
It is necessary to make the connection to DATA and EVENT manager (Firewall: Port Forwarding).
Is there a config.webclient existing?
Please check again the config file:
e.g.
--------
data = ""
event = "

jeissonsierrac
Posts:62
Joined: Wed Jun 03, 2015 9:37 pm

Re: Problem communicating Mobile UI

Post by jeissonsierrac »

I appreciate your prompt response

Access to the demo project of the app can be done correctly.

WE HAVE NOT A "config.webclient"

We have an internal network where it is managed by an internet-free access point; To this network we have connected 4 teams which are: 2 Portable and 2 Cell phones.

The team where the project is:
Server: 172.16.5.101
Customer Team: 172.16.5.102
IOS Phone: 172.16.5.103
Android phone: 172.16.5.104

-------------------------------------------------- -------------------------------------------------- ---------

We managed to solve the problem by adding these settings in the config file.

[general]
Pvss_path = "C: /Siemens/Automation/WinCC_OA/3.15"
Proj_path = "C: /Siemens/Automation/WinCC_OA/3.15/MobileAppServer_3.15"
Proj_path = "C: /WinCC_OA_Proj_3.15/Mobile_Test"
Proj_version = "3.15"
Langs = "en_US.utf8"

Data = "172.16.5.101"
Event = "172.16.5.101"
NoReverseLookup = 1
# - if mxproxy is not used -
MxProxy = "none"

[WebClient]
MobileRootPanel = "MainMobile.pnl"


We remain attentive to your comments and thank you very much for your help.

:laugh: :laugh: :laugh:

leoknipp
Posts:2928
Joined: Tue Aug 24, 2010 7:28 pm

Re: Problem communicating Mobile UI

Post by leoknipp »

Just one remark to your configuration.
The sub project MobileAppServer_3.15 needs to be defined as proj_path if the Operator / Mobile App is used.
The Operator / Mobile App is NOT the Mobile UI.
For detailed information concerning the Operator / Mobile App please have a look at the WinCC OA documentation: WinCC OA UI --> Operator / Mobile App Server

Best Regards
Leopold Knipp
Senior Support Specialist

6 posts • Page 1 of 1