My logo is connected to a MQTT broker, and sending datas properly.

However, I'd lilke to prevent the logo from sending "$logotime" every 10 seconds, as this consumes unnecessary ressources. 

Is it possible?

Thanks.

ixo65

No.

You have no access of time and date of your LOGO!.

Access to time and and date of the LOGO! have only remote devices, e.g. a other LOGO!, a S7, a HMI etc.

 To be sure that I express myself properly, I am not looking to have access to time and date, but more simply to inhibit the sending of this data systematically every 10 seconds by the logo once MQTT is enabled.
But as so far, I haven't found the option anywhere..

Hi,

The only way you may be able to improve this is in the MQTT data table where you configure when data should be tranfered.

The table looks like this:

Maybe if you change when you transfere data it may also influence how often LOGO! sends $logotime.

Hope this helps

Hello everyone,

I've been working with a Siemens LOGO! and I’m facing a similar issue where the LOGO! automatically sends time and date data every 10 seconds once MQTT is enabled. I understand that there's no direct access to the time and date from the LOGO!, but my goal is to simply prevent or inhibit this data from being sent automatically every 10 seconds.

So far, I haven’t found any option or setting to control or disable this behavior. Has anyone here managed to resolve this issue or found a workaround? Any help or suggestions would be greatly appreciated!

Thanks in advance!

Hi mate.

I hope you are doing great. Did you get any solution for this issue? I wanna stop that payload every 10 seconds as well.

I understand you are using LOGO 8.4 to communicate to MQTT. Other approach could be to communicate with Node-Red with raspberry pi and filter the data. Send it directly to MQTT from Node-Red.

If LOGO 8.4 couldn't dp it directly we need something else to do it for us.

Were you guys able to resolve this?

What I don't understand is why the $logottime does not appear in the Clod Data tab, why there are no elements to use for the diagram to trigger mqtt message publish/subs, or why this hello ping criteria and its timing does not appear in the MQTT setup. This is not a default for MQTT clients.

I have this same problem! I have cloud data set to 'On Change' but it sends out information every 10 secs. Also the timestamp is wrong. I am in Australia and its always 10hrs ahead of time. I have the correct time zone set within the logo so it doesn't make sense to me.

I was expecting to only receive data when the state of the bits I'm watching change. It is annoying as I will have to write something at the other end to filter it out of the log, as well as add in the correct timestamp.

If anyone has solved this I would very much appreciate the solution!

Cheers, Simon.

Did anyone find out any information on this (or maybe a solution)?  I have the exact same problem.  Setting the Period to 5 minutes in the cloud data transfer settings jut results in 29 empty JSON packets (just timestamp) being sent every 10s, followed by 1 packet with data in it.  The empty JSON packets are a nuisance.

Some time ago I asked the support the same question. The answer was more or less the timestamp message send all 10s, is a LOGO! feature which can’t be changed.

In LOGO! manual the feature is documented:

„BM publishes LOGO! time data value every 10 seconds.“