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.

@jared-wiltshire
Hi jared,
Didn't realise i needed to add ".value" at the end i have now added it and the button now works as i wanted :) Thanks for you help
Regards
Billy

@Phillip-Weeks not exactly. It seems that yes maybe something did change (either in our serial chart component or in the amCharts library) which affects how it draws the graph. As far as I can see though it is charting the values correctly in v3.2 as the JSON does indeed contain negative values.

If this is not what you desire I suggest that you try playing with the amCharts options for the valueaxis, try setting minimum: 0, strictMinMax: true.

So

<ma-serial-chart ... options="{valueAxes: [{minimum: 0, strictMinMax: true}]}"></ma-serial-chart>

For anyone reading this thread, if you use Mango v3.3 you can now generate JWT authentication tokens from the users page on the new UI and use these to authenticate instead of logging in from your script.

You do not need to use any CSRF/XSRF protection cookies/headers when using JWT authentication.

Just set the one header on every request -
Authorization: Bearer <token>

Hi dovydas,

Can you provide an example input and output for the uppercasing you're talking about? Have you checked out the angular "uppercase" filter? It will easily allow you to uppercase the whole date, like,

<ma-now update-interval="1 SECONDS" output="time"></ma-now> <div >{{time|maMoment: 'format':'MMMM Do, dddd' | uppercase}}</div> // sausio 12-oji, penktadienis <div >{{time|maMoment: 'format':'dddd' | uppercase}}</div> // penktadienis

Thanks Jared,

Option 1 worked a treat.

Cheers!

@sean sorry I didn't see your question earlier. That is just a warning from the Ace editor that we use, it obviously doesn't recognize the grid CSS properties as they are a very new spec.

Hi David,

You can use the query attribute of the ma-point-list element and some RQL to filter down the results. What you're looking for is probably,

query="'like(name,*Temp*)'"

@chio This shows you how to add a user module. You might also want to search the forum for "user module" to find some examples of how it is used.
https://help.infiniteautomation.com/getting-started-with-a-user-module/

For reference, our directives are open source and located here - https://github.com/infiniteautomation/ma-dashboards/tree/main/UI/web/ngMango/directives
You might want to look at serialChart.js or stateChart.js for example.

I would recommend that you have a reasonable knowledge of AngularJS to attempt this.

@bhanner You can use a point value inside the point-xid attribute

<ma-get-point-value point-xid="source-point-xid" point="sourcePoint"></ma-get-point-value> <ma-point-value point-xid="point-{{sourcePoint.value}}"></ma-point-value>

@sean I'll just show you how to use the ng-knob module instead of customising our gauge since it seems that is what you really want to use.

Use this for your usermodule file. This loads the ng-knob and d3 libraries (you dont need to load angular as our app already loads it) and tells the user module it needs to include the ui.knob module.

define(['angular', 'require', 'https://cdnjs.cloudflare.com/ajax/libs/ng-knob/0.1.3/ng-knob.js', 'https://cdnjs.cloudflare.com/ajax/libs/d3/3.5.10/d3.min.js'], function(angular, require) { 'use strict'; var userModule = angular.module('userModule', ['maUiApp', 'ui.knob']); return userModule; }); // define

You don't really need to define and use a controller as you can just use the <ui-knob> directive in your pages.

e.g. Put a point value on the gauge and set some options -

<div class="ma-designer-root" id="8167524e-1ad3-414d-9b65-d872f1317b4d" style="width: 1366px; height: 768px; position: relative;"> <ui-knob id="2666c64f-0a4f-4041-82ee-1f132d82728e" value="myPoint.value" options="{size:300}" style="position: absolute; left: 220px; top: 80px;"></ui-knob> <ma-get-point-value id="82a89bb2-cf03-49d2-a001-f9abf219c5fb" style="position: absolute; left: 28px; top: 159px;" point-xid="voltage" point="myPoint"></ma-get-point-value> </div>

@Bhanner Thats a bug on our end, the input should resize when you resize the <ma-set-point-value> component. For the time being add this to your page -

<style> ma-set-point-value md-input-container { width: 1000px; } </style>

would need more of your html to see what you are doing, but do note you can use
<ma-point-query query="'like(deviceName,'+dn.name+'*)&sort(deviceName,name)&limit(200)'"></ma-point-query>

the * will enable you to use a wildcard surrounding your search term in a like() query.
Hope this is a start

Fox

Thanks, Jared I am beginning to figure it out. Thank goodness. :)

@ralf Yeah like I said I'll make it use the user's locale. I wont make it possible to define number formats in the user settings however if this is what you meant.

Thanks for the advice on clearing the cache and sorry for the freezing up alarm.

Jared; Should this code also work in v3.0 I tried it in both play areas and only 2.8.8 works? Is there a different format in 3? Thanks.

maMoment is the change