Hi all, I was taking another look at Mango after playing with it a while back. An upcoming project calls for some historian/SCADA work with thick/thinclient HMI's and a supervisory "booth" so a cost effective web-based server solution is being investigated. Tag count won't be over 350 but 2 of the pieces of equipment need certain sensors to be logged 1/s with and charted up live. So I threw a little something together with the VM I'm working on as my data source to populate some garbage data.

Here's my issue. Using the watchlist function I made a few windows to sort of simulate thin clients and then played with the chart update functions. Going under 5/s caused a "connectivity lost, restoring connection" warning. This would eventually spread to the other open windows and then "resolve" itself. But, while I'm getting this warning and the data points are XXXX'd out, I'm still seeing data updating and the charts updating... Is this a bug? It eventually resolves if I refresh the screen.

Upping the virtual machine to 3 cores and memory to 6GB got my windows to "resolve" faster, but the dropping error continues even though my CPU isn't maxed out and I have plenty of memory overhead (I see folks are running this on a pi, I can't see how with my test). I see this as a problem unless I'm somehow pulling and/or charting these points wrong (data source polled at 1/s, points logged as "when point value changes", . The logs show no record of a datasource losing connection, I have zero warnings or errors in the logs for the time of this test.

My typical use may see as many as 3 of these charts per screen on 2-3 screens when . user is looking closely at a sensor. Now this is with the watchlist, not a custom page, so maybe there is something more intensive about using the watchlist? I've read folks doing ms logging on here so maybe I'm missing something?

Anyway, I'd like to know before I go further into developing a project on this.

Thanks.

Ok, I'll take a look at those options. Making a meta data point seems like I'm just going to be doubling my points and since this is a point-based license, well...

Basically if I have input value coming in at .1 but I want to convert this to display as a % (ie: 10%) I don't see a way to do that without making a meta data point and then generating a new value? I crawled the forums but it seems that a simple way to change the way that text is displayed was never implemented. An example is pulling in data from things like the internal mango data, It's not like I can just scale that on my device, and honestly, not sure why I'd want to.

for display I could do something like

<ma-get-point-value point-xid="loadAverage" point="loadAverage"></ma-get-point-value>
{{loadAverage.value*100}}

But that seems cumbersome and doesn't change the fact that now I have to get it back to my charts.

There has to be an easy way to do this that doesn't involve me writing a script for each point. I see that modbus already has something like this.

Sounds good. I downloaded and installed the free version. I'm guessing I should download and replace the free version with the enterprise version?

Dedicated 50% of the ram but honestly seeing the same problems. Only one window, roll up of like 3 seconds on a display period of 5 minutes with a 1 second interval update. So what you're saying is that the only way I'm going to see 1/s is with the noSQL database?

Hey thanks for the quick response. I am running the free mode so yes, only the H2 database. If getting the rates I need requires the nosql database I guess I should try that trial. I'll try changing the memory allocation in start-options too. Thanks.

Hi all, I was taking another look at Mango after playing with it a while back. An upcoming project calls for some historian/SCADA work with thick/thinclient HMI's and a supervisory "booth" so a cost effective web-based server solution is being investigated. Tag count won't be over 350 but 2 of the pieces of equipment need certain sensors to be logged 1/s with and charted up live. So I threw a little something together with the VM I'm working on as my data source to populate some garbage data.

Here's my issue. Using the watchlist function I made a few windows to sort of simulate thin clients and then played with the chart update functions. Going under 5/s caused a "connectivity lost, restoring connection" warning. This would eventually spread to the other open windows and then "resolve" itself. But, while I'm getting this warning and the data points are XXXX'd out, I'm still seeing data updating and the charts updating... Is this a bug? It eventually resolves if I refresh the screen.

Upping the virtual machine to 3 cores and memory to 6GB got my windows to "resolve" faster, but the dropping error continues even though my CPU isn't maxed out and I have plenty of memory overhead (I see folks are running this on a pi, I can't see how with my test). I see this as a problem unless I'm somehow pulling and/or charting these points wrong (data source polled at 1/s, points logged as "when point value changes", . The logs show no record of a datasource losing connection, I have zero warnings or errors in the logs for the time of this test.

My typical use may see as many as 3 of these charts per screen on 2-3 screens when . user is looking closely at a sensor. Now this is with the watchlist, not a custom page, so maybe there is something more intensive about using the watchlist? I've read folks doing ms logging on here so maybe I'm missing something?

Anyway, I'd like to know before I go further into developing a project on this.

Thanks.