Beckhoff Embedded PC driver setup issues

Beckhoff Embedded PC driver setup issues https://forum.weintekusa.com/uploads/db0776/original/2X/2/2ef96f10c9a4120115641624b2ec0c98df297438.png
none 0.0 0
  • HMI Model: cMT3072XH
  • EasyBuilder Pro Version: 6.10.01.259 build 2025.02.12

Hey there. I am having some issues getting this Beckhoff device and the Weintek HMI talking together. Specifically it seams, getting the tags imported from the IPC

the Beckhoff device is a CX-5020 controller, the recommended driver for this controller is: the Beckhoff Embedded PC driver.

Beckhoff driver SS

The guide itself is a bit dated and it seems that the TwinCAT interfaced has changed much since writing, but many of the instructions were also unclear.

for instance: does this section imply that any tags that I want to share with the HMI MUST be setup as a custom struct, or just that this is supported?

My understanding is that the tags that I want to share need to be addressed manually in memory. Here is the addressing scheme that I have tried both in a TwinCAT GVL and the MAIN POU with the goal of getting the en_outputcurrent BOOL tag connected to the HMI

VAR
	adsread1 : ADSREAD;
	GF100NETID    : T_AmsNetId := '169.254.0.1.3.1';
	status1 : UINT;
	adswrite1 : ADSWRITE ; //adswrite 1 is for output current
	adswrite2 : ADSWRITE ; //adswrite 2 is for ouput voltage
	adswrite3 : ADSWRITE ; //adswrite 3 is for input length
	//adswrite1 : ADSWRITE ;
	en_outputcurrent AT %MX0.0 : BOOL; //enable to write for Output Current
	en_outputvoltage: BOOL; //enable to write for Output Voltage
	en_inputlength: BOOL; //enable to write for increase in input length
	inputlength: UINT := 4; // 4 in decimal for input length to 4 words
	outputvoltage: UINT := 8454; // 8454 in DEC from 2106H in modbus protocol for Output voltage
	outputcurrent: UINT := 8732; // 8732 in DEC from 221CH in modbus protocol for Output current(modified from EL series VFD)
	//(PLC PROGRAM MUST BE DOWNLOADED ONTO MS300 FOR OUTPUT CURRENT TO BE READ PROPERLY)
	
END_VAR

The issue that I am running into is that when I try to import the TYP file as instructed, the import is successful, but there are no tags in the file to be read, according to EBPro.

is this an instance in which I should download MSXML 4.0 and see if that works?
Any insight is appreciated. Thanks.

Hi @Cstarr,

Can you please try this driver instead and advise the result?

1 Like

I have similar issues using this driver, in that when importing the tag file it indicates success but none of the tags are included.

Update: I instead created GVL and imported the .GVL file and that works. I am not sure why it wasn’t happy with the TPY file

1 Like

Hi @Cstarr,

Thank you for the update! Can you please let us know what version of the TwinCAT IDE you are using for our reference?

Build 4024.62

I am still having trouble getting the HMI to connect given the instructions in the driver description.
It seems that all I need to do is:

1.) add the HMI IP address and AMS netid to the route in TwinCAT i.e. 169.254.0.10 and 169.254.0.10.1.1
2.) add the PLC IP address and AMS netid to the driver settings in EBpro i.e. 169.254.0.1 and 169.254.0.1.1, set the port to 851 (default TC3)
2.) import the tags into EBPro, in this case I used the GVL from the TwinCAT directory and the tags come in fine.

This all works great but I still can’t connect to the PLC, any assistance would be awesome.

Are you using a physical cMT3072XH connecting to the Beckhoff PLC?
If so, I would recommend you chang the static IP addresses of both HMI and PLC.
The IP address range 169.254.0.1 to 169.254.255.254 is reserved for Automatic Private IP Addressing (APIPA). This range is used when a device cannot reach a DHCP server and needs a temporary IP address to communicate on the local network.
The LAN1 and LAN2 of the cMT3072XH must be set to separate subnets.

I have set the IPs on 192.168.12.- subnet and still get the same result. Although it appears that LAN1 is still set to 169.254.0.1

Perhaps you could attach some screenshots of what you configured in both PLC side and HMI side. I think most 3rd party HMI vendors that have their own Beckhoff TwinCAT ADS symbolic addressing driver implement similar configuration settings in their software due to the communication requirements.