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

  1. flume
  2. PLCnext Engineer
  3. Monday, 09 November 2020

Hello out there.

I'm new to PLCnext (I'm familiar with Siemens STEP7 and TIA) and directly ran into the first problem with PLCnext Engineer.

I've got an AXC 2152 controller.

  1. At first I thought I could just give my network card a second IP in the correct subnet and modify the IP on the WBM, but it's just a read out. One of the most logical ways to change the IP settings does not seem to be implemented.
  2. Next i tried to find online devices in PLCnext Engineer but that function doesn't find anything. I changed the project controller settings so the controller has the default IP and I could connect to it. But still it won't show up under online devices.
  3. I even downloaded netnames and let it search for devices but that program hangs up all the time.
  4. I used a USB to Ethernet adapter to get a second network card and set up a direct connection to my controller. Same outcome, i can ping and connect while my project has the settings of the default IP but it doesn't show as online device. Also netnames still doesn't find anything, seems to hang up with full search bar at the bottom of the window.
  5. Newest firmware has been installed via WBM, still no success.

What am I missing here? What is the common way to change IP address of the controller and how do I get around it if it doesn't show up as online device?

 

Thanks in advance 

 

Martin PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo

Hello,

Firstly, please check that you have selected the correct Ethernet adapter in the PLCnext Engineer "Online Devices" window (or in Netnames):

2020 11 09 21 19 55

If this doesn't help - I have had problems when searching for PLCnext Engineer from a Virtual Machine. LLDP is not routable, and something about the way VmWare routes Ethernet traffic on my machine means layer 2 comms just doesn't work on some of my VMs (but it's ok on some others ... go figure!).

If all else fails - so long as you can ssh to the PLC (e.g. using PuTTY), you can always change the IP address by editing the file /etc/network/interfaces directly on the PLC (using, for example, WinSCP).

Please let us know if any of this helps, or not.

Martin.

 

Phoenix Contact Electronics Headquarters - PLCnext Runtime Product Management and Support
  1. more than a month ago
  2. PLCnext Engineer
  3. # 1
flume Accepted Answer Pending Moderation
0
Votes
Undo

Thanks for the reply.

I didn't mention it but I had the correct Ethernet adapter selected but without success.

Thankfully SSH is no problem and I could edit the interface file like you described it.

For the future I would wish myself an edit function on the WBM and a manual function in PLCnext engineer where I can type in the IP address of the PLC when it doesn't match my project settings (delivery settings) and can't be found with a saerch function. If the target IP is known and i can ping it i want to be able to overrule the project settings for a first time download. 

  1. more than a month ago
  2. PLCnext Engineer
  3. # 2
dcrispino@phoenixcontact.com Accepted Answer Pending Moderation
1
Votes
Undo

I had the same problem and found out that was related to installation of last version of Wireshark; it looks like NPCAP is used from both software, but PLCNext engineering need the version self installed during the first installation (meanwhile Wireshark always try to update it).

Take a look here: https://www.plcnext-community.net/en/discussions-2-offcanvas/communication-problem-between-pcwe-and-axc-f-2152-and-few-questions-about-possibility-of-wireless-communication.html#reply-1547

Try uninstall the NCAP service installed on your NIC, uninstall PLCNext Engineering and install again..you'll be asked if install NPCAP included.

It worked for me, bye!

  1. more than a month ago
  2. PLCnext Engineer
  3. # 3
joris Accepted Answer Pending Moderation
0
Votes
Undo
Had the same issue, solved by removing wireshark, NCAP and installing NCAP during the PLCnext engineer installation. Thanks @dcrispino@phoenixcontact.com# !
  1. more than a month ago
  2. PLCnext Engineer
  3. # 4
anonymous_user_pgOfqi9rba Accepted Answer Pending Moderation
0
Votes
Undo
Any update or solution available yet for running PLCNext Engineer in a VM ?
(I'm not having any luck discovering or connecting to the PLC from the VM)
Martin PLCnext Team Accepted Answer Pending Moderation
0
Votes
Undo
DCP is not, and never will be, a routable protocol, so if routing is required (as I suspect it is with my VM) then the device discovery feature in PLCnext Engineer - which uses DCP - will never work.
As described above, you can edit the interfaces file directly on the PLC to assign the IP address.
Once the correct IP address is assigned - which can be confirmed with a ping from the VM - then connecting from PLCnext Engineer should be no problem.
Phoenix Contact Electronics Headquarters - PLCnext Runtime Product Management and Support
Dzmitry Ivaniuk Accepted Answer Pending Moderation
0
Votes
Undo
Hello,
I also have faced problems with NetNames+ (1.50.1922) on Windows (20H2 19042.631), but I solved it running NetNames+ as administrator.
  • Page :
  • 1


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