Skip to content

Can't connect 2152 and 1152... profinet error 0x0023

doublec4doublec4
edited July 2021 in PLCnext Technology & PLCnext Controls
Hello,

I have my 2152 set up as the master and my 1152 set up as profinet device slave.

I followed this here to establish the in / out arrays and ports: https://www.plcnext-community.net/en/discussions-2-offcanvas/i-need-some-help-to-communicate-plc-in-profinet.html

I made sure I brought in the right device into the profinet tree on my master project. It is an 1152 with firmware 2021.0.3 LTS so I brought in the 1152 controller 2021.0

Within the 2152 project, I double clicked the 1152 device and I changed the name of station and dns host name to match the 1152 along with a manual IP assignment... made sure the IP here matched what the 1152 project has. So name and IP should match...

However, my master controller (2152) has both BF-C and BF-D flashing red. The webmanager shows error 0x0023 and says:

Bit 0: lost connection
Bit 1: invalid data
Bit 5: neighborhood information is not available

Is there something else I should be looking for?

Comments

  • Oliver PLCnext TeamOliver PLCnext Team
    Hello Doublec4,
    not realy ... all that realy matters should be the Online Profinet Nam AXC-1152 == AXC-1152Project PN Device name
    At the Project node you can you can scan for Devices.
    That is where you can make sure that the Online PN Name of the AXC 1152 fits the name you have defined in the AXC f 2152 Project.



    Also make sure that no other device in your network has the IP of the AXC F1152!
  • patopato
    Hello,

    I have my 2152 set up as the master and my 1152 set up as profinet device slave.

    I followed this here to establish the in / out arrays and ports: https://www.plcnext-community.net/en/discussions-2-offcanvas/i-need-some-help-to-communicate-plc-in-profinet.html

    I made sure I brought in the right device into the profinet tree on my master project. It is an 1152 with firmware 2021.0.3 LTS so I brought in the 1152 controller 2021.0

    Within the 2152 project, I double clicked the 1152 device and I changed the name of station and dns host name to match the 1152 along with a manual IP assignment... made sure the IP here matched what the 1152 project has. So name and IP should match...

    However, my master controller (2152) has both BF-C and BF-D flashing red. The webmanager shows error 0x0023 and says:

    Bit 0: lost connection
    Bit 1: invalid data
    Bit 5: neighborhood information is not available

    Is there something else I should be looking for?
    as far as I know the 2152 is a profinet device unless you insert a profinet card at the left side so then it becomes a profinet controller
  • Oliver PLCnext TeamOliver PLCnext Team
    Hello pato,
    the AXC F 2152 is a PN Controller and a PN Device.
    You can also use both functionalities simultaneously without any addons.

    If you add the ETH EX module you are able to physically seperate the PN Device from them PN Controller network.
  • doublec4doublec4
    Hi Oliver,

    Since I have never been able to use the "scan the network" function I have not been able to use that method. Scanning my network never finds any PLC within PLCnext Engineer. However, using the IP addresses I have been able to connect to the PLCs manually and upload my projects and make changes to the PLCs.

    My network for testing is its own dedicated router so the only devices on the network are the two PLCs and my laptop, and I have confirmed that there are no IP conflicts. The controllers are online as I can access the eHMI pages and I can access both web manager pages. The slave device has ACTIVE / ACTIVE in the profinet tab on its own web manager.

    I'm lost at this point as to why it will not connect...
  • Martin [PLCnext Technology Team]Martin [PLCnext Technology Team]
    It's only a guess, but perhaps the causes are linked - Profinet, like the DCP protocol, is not routable, so if there is a layer 3 device (physical or virtual) between the devices then that could cause both problems.
    Is it possible to connect the Profinet controller and device directly using an Ethernet cable, at least temporarily, and see if that works?
  • doublec4doublec4
    Hi Martin,

    I am far from a network expert, so the concept of a layer 3 device is not something I am familiar with. However, I tried your suggestion.

    I connected the master and slave directly using the Ethernet cable. Each PLC also has an HMI connected by ethernet cable. Using this configuration nothing works at all. The eHMI pages are not even accessible on the HMIs. I then unplugged the ethernet cable connecting the two PLCs and I still couldn't establish a connection between the HMIs directly plugged into their respective PLCs.

    I then tried rebooting the PLCs. No ethernet cable connecting the two PLCs. Each PLC only connected to its own HMI through ethernet cable. Still could not connect to the eHMI pages.

    Then I went back to my original configuration whereby the master and slave PLC is connected to my router. Also, each PLC still has an HMI connected to it directly. The eHMI pages are now accessible again, but still no success on profinet (basically my original problem that prompted this topic). So nothing has changed here. However, when I disconnect either PLC from the router the connection between the HMI connected directly to the PLC is maintained.

    A bit of an aside from the original topic, but why is this the case? Why can the HMI access the PLC it is directly connected to only after the PLC was initially connected to my router? If I power up the PLC and HMI directly connected to one another with no initial connection to the router, the HMI cannot access the eHMI page.
  • Oliver PLCnext TeamOliver PLCnext Team
    Hello,
    about the side Question:
    Either one device is setup to get the IP via DHCP or it probly has something to do with the order of starting up the devices and the handshaking of Connection Speeds.

    If you have trouble with the Scan for device
    -> please check your network adaptersettings it should look like similar to this..


    If this is activated and you are still having issues try reinstalling the Engineer or npcap drivers.

    You can check or change the PN name manually by logging into the PLC via SSH:
    /opt/plcnext/config/Io/PnS/PnS.local.config
    name="StationName"
    No special characters allowed. No Capital letters allowed.
  • Arne SmetsArne Smets
    I have exactly the same problem. I'm in contact with the Dutch department of Phoenix and have had a look with them in wireshark files I created. There are a big amount of start-stops: see attachment...
    The problem is solved by simply connecting all profinet devices directly to eachother, as Martin is suggesting above.
    This will not be possible because the installation has 4 slaves and a master that are quite far from eachother in distance and all the ethernet cables are designed to go to the controlbox of the master.
    So from the master, the cable will run into a switch to connect everything.
  • doublec4doublec4
    Interesting, my settings are the same however I do not have the GW DEVICE SERVER NDIS Protocol. Not sure what that is, but it is not on my list.
  • Martin [PLCnext Technology Team]Martin [PLCnext Technology Team]
    The GW DEVICE SERVER NDIS Protocol is not required in this case (I know, that's not very clear from the image).
    Arne makes a good point - if you can get in touch with your local Phoenix Contact subsidiary, then their technical specialists may be able to help with your specific setup. They might even be able to visit your office (restrictions permitting) and spot something that we haven't thought of.
Sign In or Register to comment.