I can't connect to the new PFC200 via Ethernet

CODESYS
1

Hello,

I can’t connect to the new PFC200 via Ethernet even though the ping is positive.

I need to load a Codesys software and therefore I need this tethered connection.

What can I do?

Thank you

2

Hello, First, what is your PC ip address ? (You can use the command “ipconfig” to check it).
Next what is the PFC200 IP config ?

Last is it a new device or one already setup ?

Can you access to the web based management ? (http://[IP Address] or https://[IP Address])

3

My IP adress is 192.168.1.1

My mask is 255.255.255.0

I’m going to test this afternoon.

4

The IP adress of the PFC200 is 192.168.1.17

5

And i have the web page with this URL : http//192.168.1.17

6

Here is the manual:
PFC200 Manual

There is possibility to setup temporary IP address

For each bridge used, the assigned interfaces are assigned their own address, whereby
bridge 1 receives the IP address “192.168.1.17”, bridge 2 the IP address “192.168.2.17” and
so on.
No reset is carried out.
To set temporary fixed IP addresses, proceed as follows:

  1. Set the mode selector switch to the STOP position.
  2. Press the reset button for more than 8 seconds.
    ⮕ Execution of the setting is signaled by the “SYS” LED flashing orange.
    If you make changes to the IP configuration of a bridge after enabling the temporary IP ad
    dresses, the new settings are permanently adopted and applied immediately. The configured
    bridge exits the temporary IP address mode. The other bridges keep the temporarily set IP
    address until restart / reset.
    To cancel the setting, proceed as follows:
    • Perform a software reset.
    or
    • Switch the product off and on again

You can find Web-based Management here: https://192.168.1.17/wbm

Here is also the WAGO Ethernet Settings program:

it uses port 6626 to setup the controller, so maybe you can access this way.

For codesys, check the firmware version on you controller (wbm first page or Ethernet Settings) and look at this table for compatibile Codesys version:

7

Thank you for your help.

I just found the problem, and it was the firmware version. My prototype, which connects fine, has version 26, while the one I was trying to connect unsuccessfully has version 22.

Updating the firmware fixed everything.

Have a good day.

8

Indeed FW22 was made for codesys 2.3 and e!Cockpit