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.

I added the component with the + and now User Components is visible and i can drag them from the menu

You can also use another search engine if you prefer. You can add the term site://forum.infiniteautomation.com while googling, for instance.

Thanks Craig, That looks like the problem, Didn't even see that there .

Cheers!

Update on a really old thread. There was just no option for me to change anything on the PLC side as mentioned before but figured out a workaround.

The problem was that the pump could not be started if the stop bit held the 1 (or stopped if the start bit held the 1) You can visibly see a stuck button if the bit held the 1. The same button could be pressed again to attempt to write a 0 at release.

But instead of explaining that process, I am having the momentary of the start write a 0 to the stop and the stop will write a 0 to the start. This ensures the end user uses the buttons as intended without having to worry about stuck button or held bits. Seems to work fine.

@jared-wiltshire said in Change Step in ma-point-value:

it should be released in the next couple of weeks

Ok thanks

@Jared-Wiltshire
@CraigWeb

Thank you for your help it works perfectly

Thanks for the suggestions, I ultimately went a different route with this, and bound a slider to the variable that was previously at the top of the page (which was 30 in the first instance) and allowed the user to select how many days worth of data they wanted to see:

The text box is also editable, so they can manually type a number in, if they wish (the '500' example at the end). I did use some of the styles suggested to modify the axes to a different grey to lessen it's impact upon the page, but it also meant that the X-axes date was relevant again, so the requirement to remove it changed (let's just call it 'agile development :). The slider modifies about 10 graphs across the page and works quite fast.

Cheers

Richard

Put the ng-repeat inside it's element, but make sure that is surrounded by the div with a class of:

class="ma-designer-root"

I've also found it handy to give this div a sensible ID (ie not a UUID generated one) on which you can start doing some styling.

EG:

<style> #main { width: 100%; height: 100%; padding: 0; margin: 0; } </style> <div class="ma-designer-root" style="width: 1366px; height: 768px; position: relative;" id="main"> <p ng-repeat="(name, age) in {'adam':20, 'amalie':22}">{{name}} is {{age}}</p> </div>

HTH

Richard

Oh, I see, Jared. Thank you! ;)

@jared-wiltshire

Thanks, works well!

Hi JoHn-Beer,

It does seem like those functions should exist for completeness. Currently there would be two ways to do this,

Use the JsonEmport tool. You could export the publishers JSON, find the publisher you wished to toggle, change the 'enabled' property appropriately and reimport. Go through the actual runtime manager, like function enablePublisher(xid, enabled) { var publisher = com.serotonin.m2m2.db.dao.PublisherDao.getByXid(xid); publisher.enabled = enabled; com.serotonin.m2m2.Common.runtimeManager.savePublisher(publisher); }

And then call it as needed. I'll create a git issue about putting such a function into the script environments' RuntimeManager utility.

@jared-wiltshire said in Excel report:

@psysak said in Excel report:

Is it still the case that the <ma-excel-report-run> does not support multiple ranges?

There are three ways of running it, by default it only sets the date range for one time series. You can however get it to set the dates for all the time series by setting all-time-series="true" or only certain time series by passing time-series-names="['Time series 1', 'Time series 3']"

I suspected you might say that, I was curious what the option was for. That's perfect Jared!

Works like a charm, just user has to be User, picky little thing :)

Hi JoHn-Beer,

It sounds like a time to use the PointValueQuery.

var endDate = CONTEXT.getTimestamp(); var startDate = endDate - CONTEXT.millisInPast(DAY, 30); //handles DST shenanigans var results = []; var callback = function(idValueTime) { results.push(idValueTime); }; var pointsToQuery = [ p1.getDataPointWrapper().getId() ]; PointValueQuery.rollupQuery( pointsToQuery, startDate, endDate, callback, LAST, 1, DAY); print(results); //Do want you want now with the results, or in the callback function

Run on cron 0 0 8 * * ?

https://forum.infiniteautomation.com/topic/4004/menu-folders

Hi Christoff

If you don't come right you can paste your code here and explain what you trying to do. It is hard to help you when we don't know exactly what you want to do.

@vlasta said in Custom model for Mango 2.8:

For some reason I thought that device name = data source name...

Well it does default to that, so I can see where you went wrong. Just a heads up in Mango >= 3.3.0 you can add any number of arbitrary data point tags to help differentiate and locate your data points, e.g. site = xyz, boiler = 1 etc Just something to keep in mind if your system becomes more complicated.

@vlasta said in Custom model for Mango 2.8:

Your example works just fine too, even with my over complicated configuration.
Thanks heaps!

No worries.

Hi Sean

1.On your original point you must make then event detector with your 2 minute duration.
2. Then create a new binary virtual point.
3. go to event handler page and make a event handler like the picture. use the meta point that you created.

4. Now use <ma-get-point-value> on the new meta point and use that for your dashboard logic.

great. thanks. Sorry for the plethora of noob questions...