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.

Hi Joe,

Sorry this took so long to respond to. Is that toggle function working for you? You could tie your button to call a function that calls the toggle function several times,

function toggleStuff() { togglePoint("F6_B01_R01"); ... togglePoint("F6_B01_R08"); }

but perhaps your question is more complex? There are also endpoints for updating several data points at once, if you wished to make fewer API round trips, the /rest/v1/data-points endpoint (not data point xid, must be supplied in each point in the list in the PUT content.

This was released in 3.2

Hi przemom,

Meta point scripts don't have the .set() function like a scripting data source does. So, your options are either to use a point link from your meta point to your modbus point, or to configure a scripting data source to set the value using varName.set( 12.34 );

Certainly! Welcome to our forum!

Hi gourav,

It sounds like you want a numeric Meta point something like this...

//valve is the boolean point controlling the valve, updating ontext, logging on change //total is the numeric point measuring the weight in the vessel if(valve.value || my.time > valve.lastValue().time) return "no value"; //we'll not be logging here... set data type exception to ignore! //Okay, valve just closed var values = valve.last(2); var difference = total.value - total.pointValueBefore(values[1].time).value; return my.vaiue + difference;

Glad to hear it!

Certainly! Glad you got it working!

Hi Phil,

Thanks for the advice, and also the script help. I will give this a try.

Kindest Regards,
Ray

Hi Phil,

The lowest I've seen the delta go is -1.1 or so. I like the Idea of < -50, I think that will work. I will give this a shot.

Thanks Again.

Awesome, Thanks.

Your the best Phil,

ago(SECOND, 86399)

The above took care of my issue. My Generated history looks more accurate now. Thanks so much!

I got this to work:

return point.past(MINUTE, 1440).get(true).starts;

Thanks.

Replacing data.count == 0 with data.length == 0 now works.

Thanks for your help Phil.

Thanks I worked it out POINT LINKS..thank you

Thank you so much it works like a treat. :-)

You could try the Discard Extreme values option on the logging setting and return a high value when you don't want to log any data. So rather than throw no value through 999999 and have the data point set to discard any value over 1000.

There is the help (?) within Mango for the Point Links and there are a couple examples around the forum: http://infiniteautomation.com/forum/search/"point link"?in=titlesposts&sortBy=timestamp&sortDirection=desc&showAs=posts

Ah you're right I didn't catch that. The day was off +1. Thanks!

Ah, gotcha. You'll probably want to switch the sign in my return statement, then.

The reset is that now.getMinutes() and now.getHours() will return 0 at midnight, and any past(PERIOD, 0) call will have an empty data set (I should confirm this, it could have a single data point if there's a value at that millisecond), and the sum of an empty data set is 0, so it'll be 0 - 0 = 0

Thanks Phil,

I will be doing the totalization within the controller as your correct in stating the accuracy will be better and the load on the mangoES will stay normal.

Thanks