WAGO Controller REST:API

Linux Based Wago Controllers offer an REST:API to read/write different settings of WBM. you’ll find the API description on your contoller at: http://IP/openapi/wda.openapi.html#section/REST-API-Overview

you will find two code snippets for Nodered and Python as exampels to interact with the API on the Git hub Repo:

6 Likes

This is very cool. Is there a way to R/W to the KBUS as well?

not yet, i’m also waiting for this feature.

Hello,

Is there a way to configure the IO on the 751-9402 (CC100) via WDx? (ex. set the DIO and AIO?)

Also is it possible to R/W to the IO?

2 Likes

Hello, yes I was able to do it using node-red.
do you need me to resume what I have done ?

2 Likes

Thanks! I see the device model information here: WAGO Device Model - 751-9402 | WAGO Download Center

I also found an example flow to do this with Node-RED. Once I have the hardware, I’ll try it out and share the flows

2 Likes

Hello Mike, Icard,

I also very interested to reach IO of 751-9402 via Node-RED. Could you please share your flows and experiences? I will use it with my customer in Turkey. Thx!

Yes, I did not create these flows, but found them helpful in understanding how to access the IO.

  • You will need to go into each HTTP node, and add your PLC’s login credentials.
  • To set outputs, you will need to set the access mode to “control mode”
  • There is also a nice UI.

Thanks to whoever made this example :slight_smile:

NodeREDflows.JSON (227.0 KB)

1 Like

I think I have the same demo. I think we should have something to make the HTTP part easier (Like only having one server declaration and using the same with an layer on top for each request.)

2 Likes

Thanks for all answers guys. I agree that we need to have easy configuration for http, https part in node-red and codesys 3.5 as well.

1 Like

Hello @WagoIcard and @Suleyman

I made some improvements and consolidated some of the http nodes in this flow. I also created a global context variable for the IP address. Still probably some places for improvement but its a start!

751_9402_08012025.json (54.0 KB)

2 Likes

@MikePsaltis The URL goes to a 404 not found.

Thanks for letting me know. I edited the post and it should work now.