In attachment an simple example.

I think that you are familiar with how to get parameters of blocks by parameter VM assignment in the VM memory of the LOGO!.

In the LWE, you then have to insert 2 analog values per switching time (on and/or off time), one for hours and one for minutes. The Display format for the values must be HEX.

Hello sumit_b,

you're welcome ...

Benjamon

Hello, I try to continue on this to control my boiler. You have made the kallender in LWE, but how do you connect this in the logo soft? I Can't connect a VM to a weekly Timer?

In attachment there is a exaple with the weekly timer, one cam.

In LSC take look at the Parameter-VM-Mapping.

Take a look at my post above from 5/3/2020 3:30 PM.

There's a example that you can download.

No, this is not a problem of settings.

Without your current LWE project and your current LOGO! program I can't say anymore.

AlanTrollip

Hallo

Please read my post again

I used YOUR  project with no changes.

The only change is that your example was made with LWE v 1.0

When I load it, it says that there must be a conversion to v1.1.0

Even with a new project it does the same.

I will log a support call, its not your problem

I have read your post again, but you wrote in your first post only, that the all 2-3 seconds changes in the web servers, the values in the LOGO! are be constant.
And when the values in the webserver changes all 2-3 seconds it's not a problem of the web server.

And my project is a older version created with LWE V1.0.1. At 2019/2020 there was no V1.1.0. If you load a older version with V1.1.0, then will LWE it convert to V1.1.0, that 's normal.

AlanTrollip

Here is one I tried after testing yours

you can see the data is there, its just got 16# in the box..

In your first post you haven't anything write about the hex sign "16#". This is a problem of the LWE.

For this I made a topic in July 2019:

How can remove the hex marking (16#) when displaying the switch times of a weekly timer in the extended web server?

But in LWE V1.1.0 you can make it in a better way. Use a other function, the Scaled Time. In LWE V1.1.0 has this function more entries.

In attachment in have this function integrated in your LWE project.