Want to extract information from the build in webserver.

Hi guys,

I found this article on the internet

https://www.kb-controls.io/post/working-with-the-s7-1500s-new-web-api

It sounds interesting but is there like some kind of user manual to know what is possible to retrieve from the webserver. We are looking for a way to read out for example how many work code memory is used, how many data retain / data non-retain memory is being used from the PLC. 

A lot of things refer to the link below, but i don't want to create a webpage on the S7-1500. I want to extract information from the build in webserver.

https://support.industry.siemens.com/cs/document/68011496/creating-and-using-user-defined-web-pages-on-s7-1200-s7-1500?dti=0&lc=en-WW

------------------------------------------------------------------------------------------
Split from Web API and cycle time.

The original (non-api) web server provides that detail once you are logged in.  Are you trying to avoid web s-c-r-a-p-i-n-g?

AutoGen_1774684

Hi guys,

I found this article on the internet

https://www.kb-controls.io/post/working-with-the-s7-1500s-new-web-api

It sounds interesting but is there like some kind of user manual to know what is possible to retrieve from the webserver. We are looking for a way to read out for example how many work code memory is used, how many data retain / data non-retain memory is being used from the PLC. 

A lot of things refer to the link below, but i don't want to create a webpage on the S7-1500. I want to extract information from the build in webserver.

https://support.industry.siemens.com/cs/document/68011496/creating-and-using-user-defined-web-pages-on-s7-1200-s7-1500?dti=0&lc=en-WW

If you have your PLC, you can start with interrogating the PLC for the available and supported requests.  Read up on how that works in the webserver manual found here: https://support.industry.siemens.com/cs/document/59193560/

It shows how to request or browse for the json data showing what is supported by that PLC and firmware.

In this way, a single application can be written that can access current and future firmware and API methods making your web api applications more dynamic.

Yes we are trying to avoid web s-c-r-a-p-i-n-g. Thank you very much for the tip.