Jump to content

Aleš Vaupotič

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Aleš Vaupotič

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks, @Cara Bereck Levy, looking forward to the fix.
  2. Thanks, will do that, yes. I mean it is not breaking anything for me, it is just annoying making additional timers in ladder just for those cases, when I need to send my daily or hourly aggregations to the server.
  3. Hi, team! Just wondering what is the reasoning behind limiting the period to 100 units of 100ms here? What difference would it make if you allowed 10 or 100 times that or am I missing something here? Aleš
  4. Thanks, I am sure it works that way, but I was hoping for some kind of advanced functionality included with Unilogic, like observers or onChange events to not having to add those compare statements for every variable. What I would love to see is having a table of observed variables and set boundaries on them (either fixed or relative) and they would change a "state" of a variable (low-low, low, normal, high, over-the-moon or up-5-percent, down-5-percent) which you could also use for styling the display on HMI. Right now I am struggling with that too. Ok, now I am ranting, but thanks for
  5. Hello! I am tracking some values in my application thru MQTT and would like to trigger a publish event if for example a value changes for a fixed amount or percentage. What I am using right now is periodic transfer but would like to save some bandwidth if data isn't changing much. Also, I need some kind of general solution to implement it on 50 values. Let me give you an example: we are monitoring an outside temperature. The sensor is quite unstable and changes in tenths every few seconds. It's value table at 10am might look like this: 10:00:01 102 = 10,2 degrees C 10:00:02
  • Create New...