# Status words/bits plc pfc200

**URL:** <https://www.wago.community/t/status-words-bits-plc-pfc200/2175>\
**Category:** CODESYS\
**Tags:** pfc200, codesys\
**Created:** [August 4, 2025, 11:14pm UTC](https://www.wago.community/t/status-words-bits-plc-pfc200/2175 "2025-08-04T23:14:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![pabloud92](https://avatars.discourse-cdn.com/v4/letter/p/ba8739/32.png) [@pabloud92](https://www.wago.community/u/pabloud92)\
**Post date:** [August 4, 2025, 11:14pm UTC](https://www.wago.community/t/status-words-bits-plc-pfc200/2175/1 "2025-08-04T23:14:37Z")

</div>

Hello everyone,  
We currently have several PFC200 PLCs within a control architecture that communicates via Modbus with a SCADA system. We need to monitor the CPU’s RUN and STOP status.

Does WAGO have reserved registers for this?  
Is there a library available that allows us to detect or monitor this status?

Thank you for your response.

---

<div class="post-metadata">

**Author:** ![TomasD](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/tomasd/32/2042_2.png) [@TomasD](https://www.wago.community/u/TomasD)\
**Post date:** [August 5, 2025, 7:16am UTC](https://www.wago.community/t/status-words-bits-plc-pfc200/2175/2 "2025-08-05T07:16:04Z")

</div>

Good afternoon, but this can be tracked inside the program.  
Tell me you use Codesys or eCockpit ?

---

<div class="post-metadata">

**Author:** ![Alexander\_Landfried](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/alexander_landfried/32/306_2.png) [@Alexander\_Landfried](https://www.wago.community/u/Alexander_Landfried)\
**Post date:** [August 5, 2025, 10:48am UTC](https://www.wago.community/t/status-words-bits-plc-pfc200/2175/3 "2025-08-05T10:48:14Z")

</div>

Look here, you can use the REST API of the Device.

[WAGO Device REST-API WDx/WDA - Hardware and Linux - WAGO Open Source Community](https://www.wago.community/t/wago-device-rest-api-wdx-wda/1406)

it provides nearly everything which is available inside the Web Based Management.  
try it out.

Provide Diagnostic from the Program will only work the Codesys Runtime is in RUN.  
so i recommend to use the REST API to get all relevant Diagnostic Information of the Linux OS, including PLC Data.

But the REST API will only work for Devices PFC100 Generation 2, CC100, PFC200 Generation 2, Edge Controller and TP600 with a FW \>= Index 28.

---

<div class="post-metadata">

**Author:** ![WagoDamRud](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/wagodamrud/32/258_2.png) [@WagoDamRud](https://www.wago.community/u/WagoDamRud)\
**Post date:** [August 7, 2025, 10:50am UTC](https://www.wago.community/t/status-words-bits-plc-pfc200/2175/4 "2025-08-07T10:50:29Z")

</div>

In Codesys 2.3 runtime there are special registers, which work without running PLC program:

```plaintext
register 4160 - PLC Status 0-run, 1-stop
register 8208 - firmware version
register 8209-8210 - PLC model

```

 ![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/0/087c569a08661953c63dee4945cf911efd0d1513.png)

In e!COCKPIT runtime:

 ![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/8/8d80aac51317c94d0fc4df395a639f5f8f3914f5.png)

```plaintext
register 64013 - PLC Status 2-run, 1-stop

```

In Codesys 3.5 runtime (FW\>22) special registers are not available, so when program is stopped, you will receive modbus timeout response (unfortunately this is a feature of this version of codesys), but:

- FW\>=28, following @Alexander_Landfried you can use REST API
- I can find some workarounds:
  1. if you can ping, but there is no response from modbus - program stopped
  2. for PFC200 G2/TP600/EDGE you can run some Docker container which cyclically runs _ **/etc/config-tools/get\_run\_stop\_switch\_value** _ (script return value “run” or “stop”) and show this info in modbus TCP server on different port

Let us know which version of controller (750-8202 (PFC200 G1) or 750-8212 (PFC200 G2)) and which runtime (codesys 2.3/e!COCKPIT/Codesys 3.5) are you working with

---

<div class="post-metadata">

**Author:** ![bmarco](https://avatars.discourse-cdn.com/v4/letter/b/96bed5/32.png) [@bmarco](https://www.wago.community/u/bmarco)\
**Post date:** [August 8, 2025, 1:22pm UTC](https://www.wago.community/t/status-words-bits-plc-pfc200/2175/5 "2025-08-08T13:22:57Z")

</div>

> **[Support WAGO AUTOMATION](https://www.supportwago.fr/index.php)**
>
> Support WAGO AUTOMATION

Retrieving Controller Information - WagoAppPLCInfos\_FR

CODESYS 3

WagoAppPLCInfos\_FR is a CODESYS 3 library that allows retrieving general information about a controller, as well as a controller equipped with an integrated GSM interface.

The following function blocks are available