This site uses cookies for functional purposes. To continue please read and agree to our Data Privacy.

By closing this message, you consent to our use of cookies on this device.

PLCnext on Instagram  PLCnext on YouTube Github PLCnext CommunityStore PLCnext Community

  1. persifal
  2. PLCnext Engineer
  3. Tuesday, 05 February 2019

Hello, I hope i chose right category.

I'm working on a project that involves communication between AXC F 2152 controller and Raspberry Pi 3 (only one at the moment, but in future i would like to communicate with few Raspberry Pi 3). I have FL WLAN EPA - WLAN Ethernet Port Adapter, which i have to use in this project, to able communication between the controller and raspberry Pi (so both devices can communicate wirelessly). I have a problem at the stage of communication between PCWE and PLC.  I have PLC and my computer connected with Ethernet cable. When I create a blank project and try to find the PLC using 'Scan the network' button in Online devices tab, the PCWE doesn't find it (I'm sure i set IP Range in Settings tab correctly). When I use AXC F 2152 template in PCWE i can't find the device either, but when i go to the Settings tab of AXC F 2152 and change IP address assignment mode to Manual and write the PLC default IP Adress below (192.168.1.10) i can connect to the controller from the Cockpit tab (using 'Connect to the controller...' option, and after logging in as admin with default password). Has anyone got a clue what might be the case? I can find the device using Advanced IP Scanner, i can access the WBM, and i managed to install new firmware using WinSCP, but somehow PCWE doesn't see the PLC. I tried all the solutions i could find on this forum and nothing helped

 

And as I mentioned in the beginning, I want to establish a wireless connection between PLC and Raspberry PI using FL WLAN EPA adapter. Is this possible using this adapter? I couldn't find any info on this adapter or examples of usage apart from the manual so I would be grateful for any advices.

Martin PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo

Hello,

Some things that may stop the PLC from being found by the Scan function:

1. In the "Project" window, please make sure that the correct Ethernet adapter has been selected (the screen shot below is from my machine - you need to pick the network adapter that is attached to your PLC).

06 02 2019 07 06 28

2. If you have a firewall installed on the network or on your PC, then this may block discovery messages.

3. If the PLC is located on a different network, discovery messages might not get through the router. If you have a direct cable connection to the PLC, then this should not be a problem.

4. The discovery service uses a Profinet protocol - this is enabled by default, but it is possible to disable it. (this is usually done to stop the BF-C and/or BF-D LEDs from flashing when there is no Profinet network required). But I'm guessing you haven't changed this setting in your PLC.

Please let us know if any of this helps.

- Martin.

Phoenix Contact Electronics Headquarters - PLCnext Runtime Product Management and Support

  1. more than a month ago
  2. PLCnext Engineer
  3. # 1
Martin PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo

On the question about the FL WLAN EPA:

Yes, it is possible to use this Ethernet Port Adapter to connect the AXC F 2152 to a WiFi network. The information in the EPA user manual should be enough to set up the adapter, but if not then additional support for this device can be provided through the Phoenix Contact subsidiary in your country.

- Martin.

Phoenix Contact Electronics Headquarters - PLCnext Runtime Product Management and Support

  1. more than a month ago
  2. PLCnext Engineer
  3. # 2
Konrad Accepted Answer Pending Moderation
0
Votes
Undo

I've got the same problem with communication between PLCNE and AXC F 2152.

AXC F 2152 with firmware 2019.3.
PLCNE 2019.3 installed on laptop with pure (not PxC corporate) Windows 7. No external firewall, windows firewall disabled.

PLC can't be discovered by PLCNE.
How can I change IP settings without Linux console?
How can I fix this?

This problem does not apply to all PLCs. I have another AXC F 2152 with the same firmware and using the same laptop everything works correctly and PLC can be discovered.

  1. more than a month ago
  2. PLCnext Engineer
  3. # 3
Martin PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo

Hi Konrad,

I guess you don't know the IP address of the PLC, otherwise you would be able to open a Linux console using PuTTY ...

I am wondering if the PLCnext process is running. Can you tell me what LEDs you have on the unresponsive PLC?

- Martin.

Phoenix Contact Electronics Headquarters - PLCnext Runtime Product Management and Support

  1. more than a month ago
  2. PLCnext Engineer
  3. # 4
Konrad Accepted Answer Pending Moderation
0
Votes
Undo

Hello Martin,

In this case the IP address is known, because I've made PLC's factory reset.
PLC is reachable by PuTTY and web, but the problem is only with "Online Devices" feature in the PLCNE.

  1. more than a month ago
  2. PLCnext Engineer
  3. # 5
Martin PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo

Hi Konrad,

Are you sure the PLCnext process is running? What LEDs are you seeing?

If you can reach the PLC with PuTTY, then to answer your question - "How can I change IP settings" - you can edit the file /etc/Network/interfaces to change the IP address.

- Martin.

Phoenix Contact Electronics Headquarters - PLCnext Runtime Product Management and Support

  1. more than a month ago
  2. PLCnext Engineer
  3. # 6
Konrad Accepted Answer Pending Moderation
0
Votes
Undo

I think that PLC is running normally. After factory reset BF-C and BF-D are blinking red, RUN is green and D is yellow.

If you can reach the PLC with PuTTY, then to answer your question - "How can I change IP settings" - you can edit the file /etc/Network/interfaces to change the IP address.

My question was: "How can I change IP settings without Linux console?"
I know the way that you described and it of course works. Furthermore after this interface setting from the linux level, the problem described by me disappears and the controller can be detected by PLCNE.

  1. more than a month ago
  2. PLCnext Engineer
  3. # 7
Martin PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo

Hi Konrad, sorry for my misunderstanding, it has been a busy week at the Hannover Fair.    :-)

Profilnet discovery should always be possible when the Profinet system component is running, which in turn relies on the PLCnext process running. In cases where Profinet discovery is not possible, AND the PLC can’t be reached any other way by Ethernet (WBM, SSH, etc), then a complete factory reset is probably the best choice.

I understand that at some future point the USB port may be available for situations like this.

 

Phoenix Contact Electronics Headquarters - PLCnext Runtime Product Management and Support

  1. more than a month ago
  2. PLCnext Engineer
  3. # 8
Dan Møller Accepted Answer Pending Moderation
0
Votes
Undo

Same problem here. I can´t see the PLC in online devices when searching. The right network adapter is choosen. I can connect to WBM and download to the controller. But the scan is not working. I have tried it on two different controllers. My network cable it connected directly to the controller in port X1 or X2  

LED og the controller. 
BF-C and BF-D flashing red
RUN Green
D Orange

PCWE version 2019.3
Controller Firmware 2019.3

Windows 10 pro 1809

Dan Møller
Automation support DK
  1. more than a month ago
  2. PLCnext Engineer
  3. # 9
Martin PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo

Hi Dan,

Can you please send me a copy of the Output.log file from a PLC that you can't scan? (send by email if you want)

Martin.

Phoenix Contact Electronics Headquarters - PLCnext Runtime Product Management and Support

  1. more than a month ago
  2. PLCnext Engineer
  3. # 10
peterdallmann Accepted Answer Pending Moderation
0
Votes
Undo

PLC Next Engineer trends to be a bit slog to reaktion to the chance of network adapter.

Even if the CPU is shows in the online devices, it May tale a moment to register in the cockpit so you can connect.

i have now complete lur frist client project with the AXC F 2152 and have seen some smaller issues when connecting to the CPU. But after a restart of PLC Next Engineer it always worked.

for the question on how to change the IP address of the controller:

  1. set your project controllers IP address, Subnet mask and gateway
  2. set the project IP addresses, Subnet mask and gateway (you can start with this and take the controller next)
  3. in online devices scan for the connected controller
  4. when found, assigned the found controller to the project controller
  5. PLC Next Engineer will adopt the online controller with the settings of the project controller.

This worked for me. I post some pictures tomorrow - no controller at hand.

Peter

  1. more than a month ago
  2. PLCnext Engineer
  3. # 11
tristen Accepted Answer Pending Moderation
2
Votes
Undo

Hello,

I also had a problem with the Online devices in PLCnext engineer. I found out that the WinPcap or Npcap was the problem.

Go to your network adapter settings and see if the driver are there. In my case I had two drivers installed. I removed all driver and then selected the following:

NPCAPDriver1

 When I removed the old ones and installed the Npcap Packet Driver (NPF) version it worked again for me!

This is on Windows 10. I believe windows 7 has the Winpcap drivers. 

Maybe this can work for you!

Tristen

  1. more than a month ago
  2. PLCnext Engineer
  3. # 12
  • Page :
  • 1


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