Store PLCnext CommunityPLCnext on LinkedInPLCnext on Instagram  PLCnext on YouTube Github PLCnext CommunityStore PLCnext Community

  1. johnyeu
  2. PLCnext Technology & PLCnext Controls
  3. Wednesday, 07 April 2021
Hello, I have a testrack and I want to get online to my CPU. After scanning the Network, PLCnext finds the station and the Status is OK. I can add the station to my project, but then I'm not able to connect. I always get the message "connection failed, no response from the controller:" Can someone help me?
Martin PLCnext Team Accepted Answer Pending Moderation
1
Votes
Undo
Hi johnyeu,
Which PLC are you using?
What firmware version is on the PLC?
What version of PLCnext Engineer are you using?
What is the IP address of the PLC that is discovered by PLCnext Engineer?
What is the IP address of the Ethernet adapter on your PC that you are using to connect to the PLC?
Phoenix Contact Electronics Headquarters - PLCnext Runtime Product Management and Support
johnyeu Accepted Answer Pending Moderation
0
Votes
Undo
Hello,
hereby the answers:
Which PLC are you using? = AXCF2152
What firmware version is on the PLC? = I can't go online (even not with google chroome, but ping-ing is possible), so I can't see it
What version of PLCnext Engineer are you using? = 2021.0.2 build 4.7.1183.0
What is the IP address of the PLC that is discovered by PLCnext Engineer? = 192.168.1.10
What is the IP address of the Ethernet adapter on your PC that you are using to connect to the PLC? = 192.168.1.114
Martin PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo
Thanks for the extra information.
If the PLC is discoverable, then it is quite strange that a browser on the same PC cannot connect to the Web Based Management page on the PLC. What do you see when you browse to the ip address of the PLC (192.168.1.10) in Chrome?
Phoenix Contact Electronics Headquarters - PLCnext Runtime Product Management and Support
johnyeu Accepted Answer Pending Moderation
0
Votes
Undo
I get the following answer from Chroome: "This site can't be reached. 192.168.1.10 refused to connect. Try: checking the connection or checking the proxy and the firewall. ERR_CONNECTION_REFUSED"
Martin PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo
And can you connect to the PLC using ssh, either using PuTTY or in a Windows command prompt:

ssh admin@192.168.1.10
Phoenix Contact Electronics Headquarters - PLCnext Runtime Product Management and Support
johnyeu Accepted Answer Pending Moderation
0
Votes
Undo
I get the following message over WIndows command prompt: "ssh: connect to host 192.168.1.10 port 22: connection refused"
Martin PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo
Can you please post the result of the ipconfig command in Windows, and the result of the network scan in PLCnext Engineer, showing the ip address details of the Online PLC?
I have attached examples of both. I don't have a PLC directly connected at the moment, but the area where the address details will appear is outlined in red.
What LEDs are on and/or flashing on the PLC?
Attachments (2)
Phoenix Contact Electronics Headquarters - PLCnext Runtime Product Management and Support
johnyeu Accepted Answer Pending Moderation
0
Votes
Undo
Hereby the requested printscreens and LED BF-d is flashing red and Led's Run and D are lighting green.
Attachments (2)
Martin PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo
There seems to be two Ethernet adapters on the same network. This might cause a problem because ip messages may be routed through the WiFi adapter instead of the Ethernet adapter. In general it is a good idea to have different Ethernet adapters on different networks or subnets. You could try changing the IP address of the Ethernet adapter and the PLC to be on a different network to the WiFi adapter. If you want the PLC to be able to access the internet, then you could try setting up routing between the two adapters on the PC, or else plug the PLC into a LAN port in the back of your WiFi adapter (if available), in which case the PLC will be accessible over WiFi. This latter arrangement works for me at home.

It is possible that there is a device on the WiFi network that has already been assigned the ip address 192.168.1.10 by the WiFi router. This can be checked by removing the LAN cable from the PLC, and checking if you still get a response from the "ping" command. If so, then there is another device with that address.

You should be able to check the IP addresses of all the devices on the network on the management page of the WiFi router. The router probably also allows you to set a range of IP addresses that will be automatically assigned to devices via DHCP. The static IP address that you assign to the PLC should be outside this range, otherwise the PLCs ip address may also be automatially assigned to another device.

If you think this might be the problem, then please assign a new static IP address to the PLC from the Online Controllers window in PLCnext Engineer, and see if this helps.
Phoenix Contact Electronics Headquarters - PLCnext Runtime Product Management and Support
johnyeu Accepted Answer Pending Moderation
0
Votes
Undo
That was the problem, my WiFi adapter was in the same network. After switching it off and changing the IP-address to another IP-range, I could reach my CPU and switch on my WiFi adapter again.
Thanks for your help!!!
  • Page :
  • 1


There are no replies made for this post yet.
However, you are not allowed to reply to this post.