• Recent
    • Tags
    • Popular
    • Register
    • Login
    1. Home
    2. arvand.owji
    3. Topics

    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 Mango 5 Documentation Website
    A
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 67
    • Groups 0

    Topics

    • A

      DataPoints previous values

      Watching Ignoring Scheduled Pinned Locked Moved Scripting general Discussion
      2
      0 Votes
      2 Posts
      2k Views
      phildunlapP
      Hi arvand, The functions in "About Mango JavaScript" will work in Mango scripting contexts only, so Scripting data sources, meta data points, point links, etc. Judging from that snippet, is it part of a dashboard you're designing? If so, you could check out the existing getPointValue.js file in the UI module powering the ma-get-point-value directive, or check out the NodeJS style use of the REST API for point values, here: https://github.com/infiniteautomation/node-mango-client If it really is in the Mango JavaScript environments, you can print(p123); to see the available functions on the context point.
    • A

      V3 Dashboard Designer

      Watching Ignoring Scheduled Pinned Locked Moved Development general discussion
      6
      0 Votes
      6 Posts
      3k Views
      Jared WiltshireJ
      @arvand-owji I'm going to recommend a hybrid approach. Use a userModule.js file like this, you can add it from the UI settings page. We are going to add a parent state which you can then nest custom pages inside of. The myApp.home state etc will be nested inside the <div ui-view> element of the myApp state. The "page" that is linked to from the myApp state is the menu, define(['angular', 'require'], function(angular, require) { 'use strict'; var userModule = angular.module('userModule', ['maUiApp']); userModule.config(['maUiMenuProvider', (maUiMenuProvider) => { maUiMenuProvider.registerMenuItems([{ name: 'myApp', url: '/my-app', template: '<ma-ui-page-view xid="d012dd15-0b4e-4539-8e8a-e0235c08411d"></ma-ui-page-view><div ui-view></div>', menuText: 'My app base', //menuHidden: true, abstract: true }]); }]); return userModule; }); // define Menu "page": <div class="ma-designer-root" id="cd40a324-2725-42fa-9778-12255ebb5a62" style="width: 1024px; height: 48px; position: relative;"> <ma-button id="54f9db80-3064-4c61-8db4-59380f86df6e" style="position: absolute; left: 104px; top: 0px;" icon="android" label="Page 1" raised="true" palette="accent" ui-sref="myApp.page1"></ma-button> <ma-button id="7bd73a7c-6923-4e3d-93e2-85c2d4cf3f25" style="position: absolute; left: 0px; top: 0px;" icon="home" label="Home" raised="true" palette="primary" ui-sref="myApp.home"></ma-button> </div> Home page, page 1 etc.. Create pages as desired then add menu icons for them, making sure to choose "My app base" as their parent.
    • A

      MangoEs V3 Ip address Change

      Watching Ignoring Scheduled Pinned Locked Moved Development general discussion
      8
      0 Votes
      8 Posts
      4k Views
      JoelHaggarJ
      The easiest way is to click on Data Sources under Adminitration. This will open up the legacy UI and then you can select System Settings from the top menu.
    • A

      Import javascript library

      Watching Ignoring Scheduled Pinned Locked Moved Scripting general Discussion scipting javascript
      98
      0 Votes
      98 Posts
      113k Views
      phildunlapP
      Maybe you should try adding echo $PATH; to your CoolpropScript.sh Did you add a user? If you're editing using crontab -e, you may be running them as the mango user and may have various file permission issues to tackle. If you place them with a user specified in the /etc/cron.d directory you may have more luck.