Hello Guys,
I have trouble establishing a working connection between an AXC F 2152 controller and an AXL F BK PN TPS**** bus coupler.
My setup is as follows:
Station 1: AXC F 2152 controller with AXC F XT ETH 1TX**-** PLC extension module and AXL F BP SE4**-** Module carrier. The module carrier has a AXL SE IOL4**-** Communication module, AXL SE DI16/1**-** Digital module and two covers.
LEDs:
BF-D → red
BF-D → red flashing
Run → green
D → green
EXT → green
Station 2: AXL F BK PN TPS Bus coupler with AXL F BP SE4**-** Module carrier. The modul carrier has a AXL SE IOL4**-** Communication module, AXL SE DI16/1**-** Digital module and two covers.
BF → red flashing
RDY → green
D → green flashing
I can ping the controller as well as the bus coupler from my PC.
I can find both modules in PLCnext Engineer via the online search.
I can load a program, no problem.
I can even use the “read profinet modules” button and it shows the right modules.
So there seems to be a connection. However it does not work.
Interestingly the LEDs D1-D4 on the module carrier that is connected to the controller keep flashing green. I don’t know if it is connected to the other problem or just a coincidence.
In the WBM the controllers shows under Device List the error “No connection (0x0023)”
I hope you can help me.
If you need more information i am happy to provide it.
Best wishes,
Malte
Hello!
First of all you should be noted that, when you use ethernet extention module AXC F XT ETH 1TX with axcf2152, profinet connection will be established via that module , not thought plc lan ports. WBM shows that profinet controller ip address not in the AXL F BK PN TPS network.
So, kindly check your topology and lan ports addresses binding.
BR
Hello!
I didn’t know that the communication runs via the extension module.
And I have changed the addresses.
Now everything works.
Thank you!
All the best,
Malte
For reference, in case others are looking for this information:
How to set up AXC F XT ETH 1TX 
… and on page 15 of the AXC F XT ETH 1TX Data Sheet:
Hello again,
I still have issues with the connection.
Everything seems to be working. The AXC 2152 is working, and two bus couplers with sensors attached are working fine too.
In the WBM everything is green, and all components show up.
However, I can’t find the bus couplers via the PLCnext Engineer „Online Devices“ button.
image.pngimage.pngimage.pngimage.png
As per your comments, I changed the Profinet Controller IP and topology. And again, WBM says everything is fine.
image.png
Now the IPs are as follows:
PC - 10.75.44.9
AXL2152 - 10.75.44.10
Extension module - 10.75.45.10
Bus coupler 1 - 10.75.45.11
Bus coupler 2 - 10.75.45.12
Maybe you can help me once again.
Best Wishes!
Hello!
Do you have a route to reach your 10.75.45.0 network from the PC?
As I can see now there is two separate subnets configured on the plc, and there is no routing from the 10.75.44.0 via PLC to 10.75.45.0. So PLCNext Engineer can`t reach bus couplers.
Can you describe your current network topology?
BR.
(Edit: Oleksandr beat me to it. 
The „Online Devices“ window looks for Profinet devices from PLCnext Engineer, not from the PLCnext Control device.
It looks like the PC that’s running PLCnext Engineer is on a different network from the Profinet network, so it won’t be able to see the Profinet devices on that other network. It looks like you have the Profinet Device feature enabled in the PLCnext Control device, which is why you can see that on the 10.75.44.0/24 network.
If the Profinet network is working correctly - and it looks like it is - then there’s no real need to see the devices in the Online Devices window in PLCnext Engineer.
Hello,
ok, I somehow thought that the search would also include the network connected to the extension module. That’s on me.
image.png
However, that leaves me with my (hopefully) last question:
The BF-D LED on the AXC F 2152 controller is still flashing red.
While my PC is connected, the LED flashes. When I disconnect, the LED shines the whole time.
My understanding is that the red LED is a sign that the AXC F searches for its Profinet Controller.
However, the AXC F is the topmost entity. So there is no entity that controls the AXC F.
Is there a way to tell the AXC F that he is no Profinet Device? And because of that, he does not need to search for a Profinet Controller/ that there is no Controller missing.
Or do I have to live with the red flashing LED?
I tried disabling the Profinet Controller in the WBM under System Services. But it leads to the AXC F not being able to run.
(Edit: Oleksandr beat me to it. :)</p>The „Online Devices“ window looks for Profinet devices from PLCnext Engineer, not from the PLCnext Control device.</p>It looks like the PC that’s running PLCnext Engineer is on a different network from the Profinet network, so it won’t be able to see the Profinet devices on that other network. It looks like you have the Profinet Device feature enabled in the PLCnext Control device, which is why you can see that on the 10.75.44.0/24 network.</p>If the Profinet network is working correctly - and it looks like it is - then there’s no real need to see the devices in the Online Devices window in PLCnext Engineer.</p>
You mention that I have the Profinet Device feature enabled. How would I go about disabling it? Or do you mean the above described way in the WBM?
I hope you can help me once again.
Best Wishes!
„BF-D“ is short for „Bus Fault - [Profinet] Device“
The Profinet Device feature can be disabled in WBM.
Configuration - System Services Note:\n Before disabling a system service that is enabled by default make sure to know exactly what a service is for in the context of the PLCnext Runtime System. Otherwise, leave it enabled to avoid unwanted side effects.\n image.png
Hello Martin,
first and foremost thank you for your help so far and sorry for asking these basic questions.
After disabling the Profinet Device feature and restarting the controller all LEDs are off except D – which is yellow.
I can’t load a program via PLCnext engineer and can’t connect to the WBM.
However, I can ping the controller.
I mean, It makes sense I just disabled the communication.
So here goes my question:
Is there a way to load a program on the controller while the Profinet Device feature is disabled?
Because so far I solved the problem with the red flashing LED by basically making the controller unusable
All the best.
„I mean, It makes sense I just disabled the communication.“
No this doesn’t make sense. The PN device feature has nothing to do with the communication between PLC and PC.
I assume you did not wait long enough for PLCnext to be ready on the PLC after the mandatory reboot.
image.pngThere is a time frame where the Linux has finished booting and is reachable via Ping but the PLCnext services are not available yet.
BR
DivisionByZero
I mean, It makes sense I just disabled the communication.No, disabling the Profinet device feature does not affect WBM or PLCnext Engineer - they do not use Profinet to communicate with the controller (apart from the Online Devices window in PLCnext Engineer).
In this case it looks like the PLCnext Runtime has not started.
You could try logging in to the device using WinSCP and retrieving the file /opt/plcnext/logs/Output.log. That file contains messages that will probably show the reason why the PLCnext Runtime was not able to start. If that doesn’t help, then you could try a Type 1 reset, which deletes all user configuration settings (including changes to the IP address) and you can start again. On its own, disabling the Profinet Device feature should not cause a problem.
I can also recommend contacting the support team in the Phoenix Contact office in your country, who will be able to help with any technical support issues.
Thanks for your input, you two.
For anyone interested:
I contacted the local support.
There is an error in the Firmware 2024.6. It shows itself in combination with the AXC XT ETH.
The Profinet Device Feature must not be disabled, or else the error will lead to the above described behavior.
Support says it should be fixed in the upcoming Firmware update in early May.
Thanks for the information.
This should have been listed as a Known Issue some time ago, and now it is - in the Profinet section of this page in the Info Center:
Known issues This topic covers issues of the firmware releases from 2020.0 LTS to the current. For all known issues in firmware release 2019.9 and earlier, see the Change Notes for your devices.
… and on page 15 of the AXC F XT ETH 1TX Data Sheet:
