Hi, I'm loving Mango, and it seems a great piece of software, very well written and works great.

I love open-source, and this is great software, so well done to the developers. I'm only trying to point out some ideas I've had while looking at this for my project.

Here's my feedback on it's not-so-great aspects.

1. The name Mango, get's swamped in google searches, making it hard to connect with other users or to get a feel for the installed base. Try searching mango on google or youtube, of course you just get millions of links about mangoes. Maybe make the name MangoSCADA, or MangoM2M.

2. Support is hit-n-miss. Not to denigrate any help that is provided, which is great. The active user or developer community seems to be so small, that getting help from the forums is slow. Which makes it hard to justify a business case for its implementation. It also does not bode well for any commercial support arrangements if non-commercial support is so limited.

3. The development status and direction is unclear. Its relation to SCADABR is unclear. I'm not saying that these aspects are unknown, but its not clear from looking at the website. I can sort of work it out, like Mango was open-source, someone forked scadaBR, and mango has become closed-source again? But what is the history?

4. Little independent feedback. I can't find anything useful on Youtube, no mentions on Twitter. No case studies or in-depth reviews or comparisons.

These are some ideas. I hope the developers and user community do not take offence. It's a great piece of work and I'd like to see it really take off.

Hi, I'm loving Mango, and it seems a great piece of software, very well written and works great.

I love open-source, and this is great software, so well done to the developers. I'm only trying to point out some ideas I've had while looking at this for my project.

Here's my feedback on it's not-so-great aspects.

1. The name Mango, get's swamped in google searches, making it hard to connect with other users or to get a feel for the installed base. Try searching mango on google or youtube, of course you just get millions of links about mangoes. Maybe make the name MangoSCADA, or MangoM2M.

2. Support is hit-n-miss. Not to denigrate any help that is provided, which is great. The active user or developer community seems to be so small, that getting help from the forums is slow. Which makes it hard to justify a business case for its implementation. It also does not bode well for any commercial support arrangements if non-commercial support is so limited.

3. The development status and direction is unclear. Its relation to SCADABR is unclear. I'm not saying that these aspects are unknown, but its not clear from looking at the website. I can sort of work it out, like Mango was open-source, someone forked scadaBR, and mango has become closed-source again? But what is the history?

4. Little independent feedback. I can't find anything useful on Youtube, no mentions on Twitter. No case studies or in-depth reviews or comparisons.

These are some ideas. I hope the developers and user community do not take offence. It's a great piece of work and I'd like to see it really take off.

Hi, I'm having problems getting http retrievers to work behind a corporate firewall.

I can see the proxy settings under System Settings, but I'm not getting the http retrievers to work. They just fail with 407 errors (proxy authentication required).

Is there a log file I can see for detailed error info?

Any ideas?

Hi, I'm having problems getting http retrievers to work behind a corporate firewall.

I can see the proxy settings under System Settings, but I'm not getting the http retrievers to work. They just fail with 407 errors (proxy authentication required).

Is there a log file I can see for detailed error info?

Any ideas?

Any ideas on this?

That works now, thanks!

I guess you need to be logged in to Pachube. Have a look at:

http://pachube.com/feeds/47944?page=13

If I do a http request on https://api.pachube.com/v2/feeds/47944/datastreams/YAMBUKWF

I get returned:

{"at":"2012-05-04T06:45:09.734405Z","max_value":"31.9","min_value":"-0.6","unit":{"symbol":"W","type":"derivedSI","label":"Watt"},"id":"YAMBUKWF","version":"1.0.0","current_value":"6.3"}

The datapoint I'm interested in is current_value

Do we have the option to mark the datapoint with latitude/longitude ?

That would make it easy to present the datapoints on a map, either of a factory, or of a large distributed network such as telecoms, electricity, or water.

Do we have the option to mark the datapoint with latitude/longitude ?

That would make it easy to present the datapoints on a map, either of a factory, or of a large distributed network such as telecoms, electricity, or water.

So for an example, here is the URL:

https://api.pachube.com/v2/feeds/47944/datastreams/YAMBUKWF

The feed ID is: 47944
Data type: Numeric
StreamID is: current_value
Settable: No

Is that correct?

BTW. I'm not actually getting a connection to external data sources at the office, but at home its OK. We have a proxy set up at work under IE-Connection Settings-Lan-Proxy I have to enable. Would that cause a problem for Tomcat or Java and connectivity to the external net?