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.

Have you had a look at the <ma-json-store> component? Adding this component to the html markup of your code provides a way of storing and retrieving data in realtime across pages, clients and web browsers. Unlike local storage data is stored in Mango's database and is synced in realtime across all screens.

More info here:
http://localhost:8080/dashboards/examples/utilities/json-store

http://localhost:8080/dashboards/docs/ma-dashboards/ma-json-store

Hi Pikey,

The answer is probably, "that isn't really possible right now," but it's a good idea!

This may seem close (and maybe close enough):

<ma-serial-chart style="height: 300px; width: 100%" series-1-values="hwinletPressureValues" series-1-point="hwInletPressure" series-1-type="line" series-1-color="#ffaa00" legend="true" export="true" options="{ valueAxes:[{logarithmic: true, dashLength: 6}], guides: [{dashLength:5, inside: true, label: 'average', lineAlpha: 1, value: statsObj.average.value}]}" ng-if="statsObj.average.value"> </ma-serial-chart>

But the problem comes in where the serial chart will be aware of updates in the set of point values, but it will not adjust the options to match. So, this will draw the line for the average on the first page load. Perhaps one could hack up a solution to redraw the whole component, but that's not ideal. There may be a way to adjust this value more directly in the amChart but I am unsure of an easy way to do that.

This could be useful. I'll ask one of our developers to take a look later today.

Thanks.

@atkins-chrisw I think it is due to you using rendered point values on the AmCharts, the client side is interpreting the string as a number formatted with a comma as the decimal point. We will fix this in an upcoming release, for now either dont use rendered point values with a chart or dont use a comma in the rendered point value.

Thanks guys!

As always, appreciate your help!

Cheers!

@Balistar
There is also a line near the top of index.html that needs adminTemplate renamed, <base href="/user-dashboards/adminTemplate/">
Sorry for the inconvenience, somehow that didn't make its way into the new documentation page.

Alternatively, create a file called i18n_en.properties (for English locale) in overrides/properties and put a line in there with the new text i.e. common.set=Set the point
This will update the text everywhere in the application.

Hi @DieselD try the following syntax

<md-input-container> <label>Filtered point list using RQL</label> <ma-point-list ng-model="myPoint3" query="'in(name,' + nameFilter.join(',') + ')'"></ma-point-list> </md-input-container>

There is a setting in your developer tools that can disable caching while you have the developer tools open. I would encourage you to check that and keep your developer tools open during development, both for the cache and seeing anything that is being printed to the console.

Set a numeric point and to display it rendered.

@atkins.chrisw
You can always create a page and set the permissions on it so your users dont see it.

You are going to have to elaborate more about the errors you are getting for us to help you. For starters when and where it happens and your console output. The login issue in particular is strange, as a 403 means that you are not logged in, perhaps record your screen as this occurs with the console open so I can see exactly what is happening here, you could post it to YouTube.

Hi Radu,

It's probably easier for you to do this by using the GET /v1/events endpoint, since you can includes a URL parameter to do that filtering quite easily:

/v1/events?alarmLevel=CRITICAL&sort(-activeTimestamp)&limit(50)

Everything seems to be working perfectly now, so there are no errors.

So I'm going to rule out anything on the Mango side, but I'll look into the MTU settings as soon as I figure out where they are.

Thanks for the help.

In my option it would be best practice to set the Slave ID of a replacement Modbus device the same as the one it's replacing.

Also, it's really easy to change the slave ID of a set of points be either exporting all the points as JSON or csv. Making the change with a find and replace or in Excel and then importing them on the Configuration Import / Export page.

Thanks @Jared-Wiltshire, I will try it.

@Jared-Wiltshire
Thanks, it works!