Dear Community User! We will start the migration process in one hour.
The community will be then in READ ONLY mode.
Read more: Important information on the platform change.

cancel
Showing results for 
Search instead for 
Did you mean: 
SOLVED

PROFINET: Connect ctrlX CORE X3 to PLC S7-1200

PROFINET: Connect ctrlX CORE X3 to PLC S7-1200

Milo112
Member

Hi everyone, 

I am testing to connect the ctrlX CORE X3 (as PROFINET Controller) to the Siemens PLC S7-1200 (as PROFINET Device). A customer of mine wants to collect the data from the S7, then synchronize it to the datalayer on ctrlX.

I have completed the following steps:

1. Installed all the required add-ins on my ctrlX CORE (Ubuntu Core 22). 

2. Defined the IPs for both devices as the following: ctrlX CORE (XF10: 192.168.0.123) and S7-1200 (192.168.0.133). Both devices are wired through a switch with IP: 192.168.0.100.

3. Install the GSD file of the S7 into the ctrlX's device repository.

On the ctrlX CORE, I have setup the PROFINET Device through Codesys as the following. At this step, my ctrlX CORE has been able to scan the PLC S7-1200 and "Copy to the project" that device.

ctrlX Setup.png:

However, when I compiled the PLC program and login the ctrlX CORE, it could not make a connection with the S7 and kept showing the error "DB814006 - Connect Parameter Error". From the S7 side, the PLC blinked Red as it could not connect to the ctrlX yet.

I want to ask for support and suggestions what should I do/check/modify to be able to create a successful connection between the 2 devices. 

I am new to ctrlX CORE, so I deeply appreciate your support a lot. Please just let me know if I should provide any more information.

Thank you first!

5 REPLIES 5

CodeWasi
Occasional Contributor

Hello !
you mention the connection to the S7-device via a switch connected on XF10.
How to you run the engineering. Do you mind to shift it to XF51 for testing? Does the switch suits PN ?
Can you present the log-register-info of the codesys PNController site. IP Seting and Naming is already done?
I will leave you a note for the exchange in case not all info is supposed to be spread.

I will be able to setup a test connection with a S7 on monday. 
Please check your notes.

 

Hi CodeWasi,

Thank you for your responses. It took me the last few days to collect again all the steps that I have done for this project. Please have a look at the PDF attached, I have provided all the important info about my setup, devices, licenses, and software/firmware in the slide, so you can have a clearer context. I also conclude all my past testing/debugging on the last page.

I am testing it without any sensitive data, so if you need any more information, just let me know, ok? I am trying other ways, so it would be great if you test with a S7 on your side. Please let me know if there is any news.

Thank you!

 

CDSAddons
Established Member

Hello Milo112.

We have the suggestion, to set the priority of the PROFINET IO task to 1 or 0, otherwise it will most likely never get stable communication.

Also, the whole logger (Seen in the pdf) is full of “Check Firewall...” messages.
So, apparently the UDP communication is not getting through.

For a more detailed analysis we need a Wireshark capture (either locally on the Control X, or with TAP or switch with port mirroring enabled).

Hi CDSAddons, 

I provide the Wireshark capture file. You can have a look then. Seem like there are truly problems related to the UDP connection as you said. But I still don't know whether it is the ctrlX or the Siemens PLC.

Thank you so much!

Hi guys, 

It is great to receive news from you. I have just tested the setup a different way again and it works. I connect to the ctrlX through XF10 (192.168.1.133) for engineering and connect the ctrlX with S7 through XF51 (192.168.2.144), without any router or switch in between.  
 
I believe my Office Switch has some protocols that limit the connection since it is also a Wi-Fi router. One main thing is that I must set up different IP layers for the XF10 (192.168.1.133) and XF51 (192.168.2.144). I configure them as 192.168.2.XXX before, so there must be some conflicts.
 
However, it is strange since my colleague uses the same setup with the same model of the switch, and it works while the 2 devices are connected to it. I will check again whether which settings on the switch I should change or modify.
 
Thank you so much for your time and support. 
 
Best regards,
Thinh
Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist