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.

Hay that's awesome. do you also know any other way to push data from mango to excel? Thank you PD

Generally true Hussam, but not always. If a datasource fails polling some points but not others, it will only update the times of those it successfully polled. Or, if the entire poll fails, no timestamps will be updated. The timestamp displayed for a point on the data point details page does reflect the cache's perspective, meaning what the value of a point is and when that value was reported last. Other ways of accessing data can get you timestamps that reflect those which will ultimately be logged in the database. For example, compare two meta scripts being run on a point receiving 1 second updates, but not always changing (I used a virtual binary point on random): It is set to log on change. return new Date(p1.time); //returns the date of the last update return new Date(p1.lastValue(0).time); //returns the date of the last logging

@djmolloyjr22 The REST api has a feature that allows bulk updating of data points via a PUT of a JSON array, but this has not been rigorously tested and is still in Beta. Use at your own risk since not every type of data point has been verified to work. I would suggest making a backup of your database prior to testing your specific updates. Here is the basic idea: Make a GET request to {YourMangoHost}/rest/v1/data-points to get all your data points as an Array in JSON format Edit your JSON Do a PUT request with the edited array of data points as the payload to {YourMangoHost}/rest/v1/data-points Note that since the JSON structure for a Data Point in the REST API is different than the Mango JSON Export you cannot use one with the other.

I also need basic authentication, has something been implemented? I tried using http://username:password@someserver.com but this returns an error.

Hi Ralf, That's an easy fix - you just have to create a navigation file. You might want to show different menus to different users and nav files are how you do that. To make one, just click the 'person' icon in the top right of DGLux then click the 'Edit Navigation' link. In the centre pane, navigate to the .dgml dashboard file you made (you might need to look under the 'files' tab) and then drag it to the left-most pane to add it to your menu. You can now edit the properties of your menu object including name, icon, and whether to have it load automatically. Then, hit the save and save your navfile as 'default.nav'. When prompted, associate it to the current user and now this is the menu that shows up when you log back in. Hope this helps!

Nothing comes to mind for this and would probably need to be a bit of java code written to do this.

One quick note: In the latest nightly build of 2.6.0 we are removing the ability to add the .json to the end of the URLS for the REST api. This was done because we found we could not easily interpret dots in other areas of the URL. So for example: /rest/v1/users/admin.json must now be: /ret/v1/users/admin This better allows us to do things like: /rest/v1/users/firstname.lastname The other feature this effects is the ability to define the content type using a file extension on the URL. So for example previously one could request a csv file: /rest/v1/data-points/data-source/DS_XID.csv Or a JSON file: /rest/v1/data-points/data-source/DS_XID.json One must now use: /rest/v1/data-points/data-source/DS_XID?format=csv OR /rest/v1/data-points/data-source/DS_XID?format=son OR Set the accept header in the request to the desired file type (CSV or JSON support only for now)

@jeremyh I'm swamped at work right but but will be happy to write up when I get a break, probably around 1July. Short story, we are a datacenter company and using the product as a backend data acquisition tool to provide energy and environmental (Critical and Essential) such as room temperature/humidity/air handler information. We have a various set of protocols ranging from ModBus, BacNet, SNMP, SQL, and custom SOAP calls and needed a one stop package that Mango provides. We have a front-end website that makes API calls to the Mango for data point retrieval.

Hi Dominic, I've been running Mango in a VPS myself for a week now, it's great and I haven't run into any issues. I haven't migrated all our data sources and history though, so it will be interesting to see how it compares once I do that.

@Andoni-Abedul It happens to me too, it's because this forum software is new I guess, there may be some tweaking needed. What's weird is that if I open the link in a new window/tab it works, but if I click the link and it opens in the current window/tab it doesn't!

Great it did work !! much appreciate the advise. I think, I started using Mango M2M (the great Scada product) around 2010. My gratitude goes to the developers. When I installed Mango on Windows it did work like a charm, but every time I tried installing on Ubuntu gave me a headache. finally I did manged to install on a Ubuntu server (I don't want to allocate more resources just for running a server) The reason I want to install Mango on Ubuntu desktop version is the Gambas3 is another opensource SDK. when I did some google research I found that ScadaBR which is a derivative from Mango M2M, but easy to install, and I can install it on Ubuntu desktop. What soever I still love Mango M2M. much appreciate that if you can direct me to sort out the Mango Ubuntu installtion issue. I know this Forum is not for discussing installation issues. Anyway thank you once again for helping me Have a great day !!

@JoelHaggar said: We will be developing a new reports module soon which will use an Excel file as a template. Really interested here too.

@djmolloyjr22 I realized the "script" datasource would be sufficient. It would be cool to do some native SOAP calls, but this will get me through.

Hey Guys, Sorry for the delay on this. We do have a TCPIP data source but it's in Beta. I'm pretty sure it works but it hasn't been touched in a while. Here it is, will require core 2.5 to test. Please let me know if you get it to work. Thanks, Joel. Attachment: download link

The formatting of this post got really messed up during the forum move, so here's a link to this content on my personal blog instead: http://jeremyhall.com.au/reading-snmp-values-from-mikrotik-routeros-into-mango-automation

Email alerts can be a critical component of a Mango setup. Here are three ways to configure email sending. [size=18]Option 1 - Google's restricted SMTP[/size] This is the simplest method and the most flexible, as long as you are sending to a gmail address. Advantages: You don't need to set up any accounts, and you don't need to provide any authentication, works with dynamic IPs. Disadvantages: You can only receive mail if you are a gmail or google apps user, and some ISPs block port 25 to prevent spam. To use, simply enter aspmx.l.google.com as the STMP server in Mango's settings, and select port 25. Leave authorisation and TLS unchecked/blank. More info here: https://support.google.com/a/answer/176600?hl=en [size=18]Option 2 - Google's open SMTP server[/size] This is a better option if you have a gmail account yourself, but want to send to recipients who may not, or if your ISP blocks port 25. Advantages: Can send to any recipient, don't have to use port 25, works with dynamic IPs. Disadvantages: Requires entering your gmail/google apps details into the Mango system To use, enter the SMTP server as smtp.gmail.com, select port 587, enable TLS and Authorisation, and use your full gmail/google apps account username and password for authentication. More info here: https://support.google.com/a/answer/176600?hl=en [size=18]**Option 3 - Sendgrid Email **[/size] This is the most time consuming to set up, but offers the most reliable delivery. You will need to sign up for a free account at sendgrid.com, which means entering some personal/company information. The free account allows 400 emails per month, with a limit of 100 emails per SMTP connection (Mango should only make one connection per email event so unless you are sending to 200+ users this should be fine). Advantages: Can send to any recipient, don't have to use port 25, works with dynamic IPs. Disadvantages: Have to sign up for (free) account, sending limits of 400 emails/month To use, first sign up at sendgrid.com, then once the account is established, enter smtp.sendgrid.com as the SMTP server, port 587, with TLS and Authorisation checked. Use your sendgrid account username and password. More info: https://sendgrid.com/docs/Integrate/index.html Remember to test your configurations, and set your email reply-to address to something appropriate.

For Solar PV systems that utilise a SMA Power Reducer Box (for control over active output power limitation setpoints by the grid operator), access using Modbus to read the active power limitation setpoint value is not possible. Nor can the value be read from the inverters or other plant devices using Modbus. Instead, you can use a HTTP retriever and regex to scrape the value from the Power Reducer Box's internal web server (in this case, at IP address 1.2.3.4). { "dataSources":[ { "xid":"DS_158029", "name":"Power Reducer Box", "enabled":true, "type":"HTTP_RETRIEVER", "alarmLevels":{ "PARSE_EXCEPTION":"NONE", "DATA_RETRIEVAL_FAILURE":"INFORMATION", "SET_POINT_FAILURE":"NONE" }, "purgeType":"YEARS", "updatePeriodType":"MINUTES", "quantize":true, "retries":2, "setPointUrl":"", "timeoutSeconds":30, "updatePeriods":5, "url":"http:\/\/1.2.3.4\/index.php?module=PlantStatus&action=index", "purgeOverride":true, "purgePeriod":1 } ], "dataPoints":[ { "xid":"DP_172704", "name":"Active Power Limitation Setpoint", "enabled":true, "loggingType":"ON_CHANGE", "intervalLoggingPeriodType":"MINUTES", "intervalLoggingType":"INSTANT", "purgeType":"YEARS", "pointLocator":{ "dataType":"NUMERIC", "ignoreIfMissing":false, "setPointName":"", "settable":false, "timeFormat":"", "timeRegex":"", "valueFormat":"###.#", "valueRegex":"(?<=L3: )(.*)(?=%)" }, "eventDetectors":[ { "xid":"PED_028817", "type":"LOW_LIMIT", "alarmLevel":"INFORMATION", "limit":99.0, "durationType":"SECONDS", "duration":60, "alias":"" } ], "plotType":"STEP", "unit":"%", "chartColour":"", "chartRenderer":{ "type":"TABLE", "limit":10 }, "dataSourceXid":"DS_158029", "defaultCacheSize":1, "deviceName":"Power Reducer Box", "discardExtremeValues":false, "discardHighLimit":0.0, "discardLowLimit":0.0, "intervalLoggingPeriod":15, "intervalLoggingSampleWindowSize":0, "overrideIntervalLoggingSamples":false, "purgeOverride":true, "purgePeriod":1, "textRenderer":{ "type":"PLAIN", "useUnitAsSuffix":true, "unit":"%", "renderedUnit":"%", "suffix":"" }, "tolerance":0.0 } ] }

Thanks your share, and For the 7.Chapter,I think if need add the device tier for query,interface ,in fact,mango datapoint use Two-Tier Architecture for store value,datasource--points,and when read value,three-Tier is better,datasource--device--point,datasource is face to developer, device and datapoint is face to end user.

This export was from Mango 2.5.0 Beta which has an added alarm. You should be able to just remove the: "POLL_ABORTED":"URGENT", and then the import would work. I'm not the Regex guys so someone else will have to answer that or you can use the other example to figure out the forecast.