Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website

Overriding point update frequency on Mango/Angular page

User help
Log in to reply
  • AldoRamos

    I have a data source which polls every second. I am displaying data points on an Angular page, and it's attempting to update them every second, but due to bandwidth, etc. the browser is unable to keep up.

    How can I override so that it updates less frequently? 5 or 15 seconds? Even every minute?

    I want the logging to be that detailed, but for display purposes I don't need them refreshing as often.

    Apologies if this has already been addressed, but all my keywords matched other topics instead.

    0
  • MattFox

    You use an ma-now component tied with a ma-point-values and tell it to update at the rate you like:

    <ma-now update-interval="15 SECONDS" output="NOW"></ma-now>

<ma-point-values  point="point"  values="vals" from="NOW | maMoment:'subtract':'15':'seconds'" to="NOW" ></ma-point-values>
    0
  • AldoRamos

    Thanks, that does the trick!

    Interestingly, however, I copied it exactly as you posted but watching the network tab (Chrome developer tools) confirms that the update is happening every 10 seconds even though 15 is specified. This is close enough for now, but I am always curious to be correct and understand how things work, so I'll be reading up on ma-now; but I thought you should know.

    0
  • MattFox

    Np, maybe increase the duration.
    What version of mango are you using? Might be handy for Jared to know.

    Fox

    0
  • AldoRamos

    Yes, that's what I'd figured I would do if needed, but this is good enough for now to solve my issue, move forward and be productive.

    This instance is running Mango 3.5.6; will be upgraded soon.

    0