# CODESYS Solution for Serial Comms via EtherCAT

**URL:** <https://www.wago.community/t/codesys-solution-for-serial-comms-via-ethercat/1684>\
**Category:** CODESYS\
**Created:** [March 20, 2025, 3:03pm UTC](https://www.wago.community/t/codesys-solution-for-serial-comms-via-ethercat/1684 "2025-03-20T15:03:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![WagoMark](https://avatars.discourse-cdn.com/v4/letter/w/d07c76/32.png) [@WagoMark](https://www.wago.community/u/WagoMark)\
**Post date:** [March 20, 2025, 3:03pm UTC](https://www.wago.community/t/codesys-solution-for-serial-comms-via-ethercat/1684/1 "2025-03-20T15:03:53Z")

</div>

I recently needed to demonstrate for a customer how to do serial communications via a 750-652 module located in a remote EtherCAT node of IO, using a WAGO controller (PFC200) as the EtherCAT master. It was important to the customer that they be able to configure the 750-652 comms parameters via the CODESYS project, rather than using WAGO-IO-Check. Using WAGO libraries and making use of the I\_Port interface, it was relative easy to provide a solution for what would otherwise be a very complex application. See attached.  
[PFC200 ECAT 652 Serial Comms.project](https://www.wago.community/uploads/short-url/39w19Q5oL7TyGr2OnnbwWbc0OQ9.project) (504.8 KB)
