HMI Screen Blank After Program Transfer – "Unable to Connect to Socket" Error

[Progics005 (ABIN MV)]

I’m using the 4PPC50.101E.10A module for a project. When I reset the HMI, it starts in RUN mode. However, after I transfer the program to the HMI, the screen goes blank.

I can still see the visualization through a VNC Viewer, but the HMI itself displays the message “Unable to connect to socket.”

Why is this happening, and how can I resolve the issue?

[kovarj (Jaroslav Kovar)]

So you have VC4 visualization? how many clients connection are configured? Something in the logger?

[chris.hairston]

Hello Abin,
I would expect this to most likely be an issue with how either AR or the terminal side of the C50 has its network settings configured properly. Could you provide the settings from your ETH configuration as well as the Terminal configuration (found in PLC configuration).

Also have you taken a look at the logger with all relevant modules enabled? Is there anything of interest in there?

Thanks,
Chris Hairston

[Progics005 (ABIN MV)]

• Panel: 4PPC50.101E-10A
• Hardware module version: 1.2.3.0
• Automation Runtime: 4.93U for PPC5X
• Linux Image: AS4_LX_PPC_50_V1.1.2
• Linux image uploaded through USB port IF4
• Subsystem changed to Terminal
• The corresponding configuration for IF3 was also changed
• Visualization mode: VNC
• Application URL: localhost
• Local Window Scaling: OFF IP Address: *192.168.0.20
• Subnet Mask: 255.255.255.0 .VNC port/node number: *5900
• MX connections: 2

[chris.hairston]

Hello Abin,
Apologies as I don’t think I was specific enough. I would like to see the following.

• Screenshot of ETH Configuration
  

  

• Screenshot of Terminal Configuration
  

  

• Screenshot of VNC Server Configuration for PLC
  

  

Thanks

[Progics005 (ABIN MV)]

[Progics005 (ABIN MV)]

[chris.hairston]

Hello @Progics005,
Could you please send a screenshot of the terminal configuration as shown below.

Thanks

[Progics005 (ABIN MV)]

[Progics005 (ABIN MV)]

snmp is deactivated in my configuration i changed it and activated but there is no change

[Progics005 (ABIN MV)]

[kovarj (Jaroslav Kovar)]

I can see that terminal is set to get IP address from DHCP server, are you sure that terminal has valid IP address?

[Progics005 (ABIN MV)]

[kovarj (Jaroslav Kovar)]

Great. Please, if you provide a picture, it is always good to also describe what you have done and the status of your progress. Btw, you set the IP address of your terminal to 192.168.0.20, but this IP address is already used for the Ethernet interface IF2, so if you have not changed that, then now you have an IP address conflict. So set different IP address for yoor terminal e.g. xx.xx.xx.21. For VNC if localhost will not work, try to set same url you are using from external PC. e.g. 192.168.0.20:5900, format is IPADDRESS: PORT OF VNC server

[Progics005 (ABIN MV)]

Thank you very much for the help! You were right: the terminal had the same IP address (192.168.0.20) as the Ethernet interface IF2, which caused the conflict. I changed only the terminal IP to a different address (192.168.0.21), and the problem is solved. I’ll also include a short description of my progress together with any screenshots I post in the future.

Thanks again!

[kovarj (Jaroslav Kovar)]

Happy to help you can also activate dhcp server on plc side and use get ip address from dhcp on terminal side. Princip is the same.