• Skip to main content
  • Skip to header right navigation
  • Skip to site footer
CDP Studio logo

CDP Studio

The no-code and full-code software development tool for distributed control systems and HMI

  • Doc
  • Why CDP
    • Software developers
    • Automation engineers
    • Managers
  • Products
    • Automation Designer
    • HMI Designer
    • Maritime HMIs
  • Services
  • Use cases
  • Pricing
  • Try CDP

CDP Studio Documentation

  • Hardware - Wago I/O Modules
  • WAGO 750-652 Serial Interface
  • 5.0.4

WAGO 750-652 Serial Interface

Overview

The 750-652 Module implements the byte-level handshake required to communicate with a WAGO 750-652 Serial Interface module through its process image. It supports continuous transmit and event-driven receive using the module’s control (C0/C1) and status (S0/S1) bytes.

Use WAGO tools such as Wago-I/O-Check to configure module parameters (communication type RS-232/422/485, process image size, baud rate, etc.). Refer to the WAGO 750-652 datasheet for wiring and bus coupler setup.

Note: By default, the 750-652 process image is 24 bytes on both input and output: S0 + S1 + 22 * RX_DATA on the input side, and C0 + C1 + 22 * TX_DATA on the output side. If you change the process image size, update the BinaryEncodedLength of both RX_DATA and TX_DATA accordingly. The length is always process-image-size – 2.

Usage

  • Add a 750-652 module to a supported IOServer.
  • If the module is configured in Wago-I/O-Check with a non-default process image size, un-hide the Signals in the module and adjust BinaryEncodedLength for both RX_DATA and TX_DATA to the same value.
  • Connect the module events:
    • Write
    • WriteSuccess
    • Read

    In addition, Init, Inited and Error can be connected if needed.

    Note: Another IOServer set up with a CDPTransport can connect to this block. Connecting the CDPTransport causes that IOServer to communicate its data with the 750-652 module.

Performance

There is a limited amount of data (RX_DATA/TX_DATA size) that can be pushed through this module at any time. In addition, there is a limit to the cycle-time (fs) that the Wago buscoupler scans the bus and 'runs' the module. Some protocols do not play well with data that is segmented into several chunks separated by 1/fs time intervals. These issues may influence the usability of the module, and care should be taken to verify that the module is suited for the type of communication used.

Events

The 750-652 Module defines the following events:

NameDirectionDescription
InitInputCauses the module to (re) initialize, and also forwards out the message to Inited.
InitedOutputEmitted as a result of receiving an Init message.
WriteInputAccepts a CM_MESSAGE_RAW message containing the payload. Triggers a continuous send session that streams the payload to the module in chunks of TX_DATA size.
ReadOutputEmitted whenever bytes are received from the module. The received data is provided in the CM_MESSAGE_RAW payload.
WriteSuccessOutputEmitted when the module has transmitted the entire payload. The transmitted text is provided in the CM_MESSAGE_RAW payload.
ErrorOutputEmitted on UART errors. A combination of the following characters will be sent as CM_TEXTCOMMAND on error:
  • P - corresponding to S1_ERR_PARITY.
  • F - corresponding to S1_ERR_FRAMING (check communication parameters).
  • O - corresponding to S1_ERR_OVERRUN (check fs and baudrate).

The block performs a soft re-initialization when errors are detected, which may disrupt ongoing operations.

The definition for CM_MESSAGE_RAW can be found in CDPTransport.

Signals

The following hidden signals map directly into the 750-652 process image. They are provided for reference only; manipulating them externally may interfere with normal operation. To show the signals, make sure to un-check "Hide Internal Items" in the node filter.

NameDescription
C0Control byte 0.
C1Control byte 1.
TX_DATATransmit buffer (default 22 bytes)
S0Status byte 0.
S1Status byte 1.
RX_DATAReceive buffer (default 22 bytes)

The content of this document is confidential information not to be published without the consent of CDP Technologies AS.

CDP Technologies AS, www.cdpstudio.com

Get started with CDP Studio today

Let us help you take your great ideas and turn them into the products your customer will love.

Try CDP Studio for free
Why CDP Studio?

CDP Technologies AS
Hundsværgata 8,
P.O. Box 144
6001 Ålesund, Norway

Tel: +47 990 80 900
E-mail: info@cdptech.com

Company

About CDP

Contact us

Services

Partners

Blog

Developers

Get started

User manuals

Support

Document download

Release notes

My account

Follow CDP

  • LinkedIn
  • YouTube
  • GitHub

© Copyright 2025 CDP Technologies. Privacy and cookie policy.

Return to top