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've tested it on the 1.1.1 module that is about to be released with Mango 2.7.0 this week and it works fine with that version. You may have to wait as I'm not 100% sure when that feature was added.

I mispoke in my last post, you should be able to use 1 web socket for all your data point values. If you review the web/js/mango-2.0/RealtimeDataProvider.js file in the Dashboards module you can see how this would work. Basically you just need 1 web socket and can then send additional registration requests for each data point you want.

The next version of the Dashboards module (1.1.1) will contain an example of how to use 1 web socket for all point values captured within Mango.

What you are trying to do is going to require a solid understanding of Javascript. I think you should start by just trying to plot one or 2 data points on a chart.

The example in the dashboards module in web/tutorials/dataPointChart.shtm will get you started. Once you have an understanding of how that works I can provide a slightly more advanced example that will show you how to manipulate the data.

Good Luck!

Mango security filters are based on the URL extension:

.shtm (Secure HTML behind Mango's login control)
.htm (Non secure HTML that anyone can access)

By making your extension .shtm you are asking Mango to restrict access to only its users.

There are a few things you need to know about using our REST api from a host other than Mango.

You will need to setup the CORS filter to allow cross site requests into Mango. You will need to allow all the various headers that you want to use. Checkout the classes/mangoApiHeaders.properties and the web/dox folder to see how the override-web.xml file should work. Be careful as the early releases of 2.6.0 beta have this filed named web-override.xml (which is wrong).

You will need to use the REST api to login to Mango via your remote server and then retain the session cookie to pass back to mango on any future requests.

Be sure to include the password header in the CORS configuration as you will most likely need to use this to login.

In the future we are planning to use OAUTH but this has not been a high priority for us yet.

All up and running,

Thanks for the input Joel!

P.S. How do I mark post as SOLVED?

Sorry I didn't understand.

OK I think this will help you.

In Mango click on Custom Dashboards on the main icon menu at top of the page. Here you will see many examples. Here's a video as well

By The Way - You can do a view source in your browser to see the html for these examples or goto <mango root dir>/web/modules/dashboards/web/private

-WoodyB

Thank you for the custom module. I have seen you have added XID to the paylod object exactly as I asked. Much appreciated.

Gary

Joel,

Well done to you and your team. This all really just looks fantastic and we are all very excited here.

Between this, functionality like the persistent TCP syncing, and of course the MangoES, Mango is really growing to be a product that we are using and depending on more and more, and it's great to see it moving in these directions.

see www.amcharts.com for more information