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

X3 Version2.4 failed to communicate using Codesys V3 label communication

X3 Version2.4 failed to communicate using Codesys V3 label communication

DeathScytheH
New Poster

Hello,

I have some trouble about X3 2.4 using Codesys V3 label communication to communicate with HMI. When I tried using this codesys function to establish communication between X3 and HMI, the TCP communication was established, however there were no data between X3 and HMI. My symbol configuration was shown below: 

2024-08-15_11h14_24.png2024-08-15_11h42_15.png

As I could not using X3 to communicate with HMI by V3 label communication, I tried another PLC called AM522 to make a comparation. However, AM522 could communicate with HMI through V3 label communication. So I tried using wireshark to catch TCP packages about X3 and AM522. Here's my data (left was AM522, right was X3):

1. The type of packets of X3 and AM522 is the same. In both cases, HMI first sends a confirmation frame and then sends a data frame with confirmation, and then the controller returns a data frame with confirmation

DeathScytheH_0-1723698346914.png

2. X3 The headers of these TCP packets are the same as those of AM522

DeathScytheH_1-1723698474126.png

3. The length of the data part of the TCP packet X3 is much lower than that of AM522, and the data is all 0. Currently, it is suspected that the label does not take effect when X3 establishes communication with HMI, and HMI does not send the label data

DeathScytheH_2-1723698521159.png

Since the same program AM522 can establish communication but X3 cannot, may I ask whether X3 does not support this communication method to modify the global variables in the plc program? If no, is there a problem with my method of operation?

Many thanks for you help

Qianxin.YANG

1 REPLY 1

CodeShepherd
Community Moderator
Community Moderator

Did you already check the topic "How to use ctrlX CORE to communicate to 3rd party HMI via Codesys V3 protocol?"? As similar question is discussed there.

Also topic "communicate to 3rd party HMI via Codesys V3 protocol in ctrX PLC >=1.20" could be interesting for you.

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