Terry,

Thanks for the tip on:

runtime.realTimeTimer.defaultTaskQueueSize

The setting was adjusted to a max of 2. The FATAL message still occurs. Periodicity is around a minute between occurrences. It seems better than it was but still nagging away.

If you're not seeing the same thing on your end there must be a configuration difference on my end. Dealing with configuration problems is tiresome for all involved. With that in mind, I highly recommend Docker. If Mango were available on the Docker hub I'd definitely use it.

@phildunlap Thank you! You fixed the problem for me.

All I had to do was to remove: mango/classes/org/jfree/data/Range.class

Hi sjobbe,

These functions are implemented in apache-poi, and it looks like by version 3.10-FINAL (the one we package with Mango at the moment) these are not implemented.

The good news for you, however, is that that function is implemented in the current stable version, 3.13! I will make an issue for us to consider packaging that version of the apache poi library into the next Mango release, but in the meantime you can download version 3.13 from https://poi.apache.org/ and swap the Mango/lib/poi-3.10-FINAL.jar and two poi-ooxml jar files with the versions in the poi 3.13 release (such that you only have jars for one version in your lib folder). Hope this helps!

Meanwhile, you could type kW*h into the unit field. It is then displayed as kW·h. I use it all the time in the integral field since it is more useful than the default kW·s.

However, if Mango considers kW/h to be an alias for kWh, that should definitely be corrected, as it could cause undetected incorrect numerical conversion issues. In fact, just today I was thinking of writing a function that used kW/s, so the possibility that someone may use kW/h is not out of the question.

Hello

I have upgraded our Mango today and this issue is resolved :) Thank you very much.

Today I started creating reports and noticed that it fails if some cell contains for example:
=PROPER(SLA!G9)&" Environmental Averages"

Message in the log is: Error evaluating cell 'HEL01 - Environmental Averages'!A1

What's up?

I may be wrong, but from memory, the chart colours only apply to reports.

The charting stuff looks to have been completely overhauled in the newest beta anyway:
http://infiniteautomation.com/forum/topic/1872/new-features-coming-soon

The image is created prior to generating the HTML via the FTL template. The images all have preset sizes and are generated at this size when the report is created.

A future feature could be allowing sizes to be set in the report configuration.

However there is a way to generate different size charts via the Chart Servlet. This is the servlet that generates the charts on the Data Point Details page. The help for this can be accessed via the help icon in the System Settings --> Chart API Settings. These charts are different than the report charts but it should be possible to use this chart instead if you can create the URL properly in the template.

That is a self referencing variable. so my.value would give you the value of the meta data point. This is useful if you want to add a value to it's self or use the current or past values of the meta data point within the calculation. It prevents you from needing to add the meta data point into the script context which ultimately allows you to import self referencing meta data points through the JSON import without getting errors.

Thank you! Solved by removing report usin SQL

I have a PHP script that creates JSON for adding data points. Could i run the JSON from command line (in linux)? I could then trigger it from the PHP script.

Currenlty PHP creates the JSON file to the templates folder and I then need to run it from "Templates" by selecting it from the drop down list. Not very convenient...

@sjobbe said:

Also the Unit in "Unit properties" does not recognize Wh (kWh) or VA (kVA). I find that odd since both are regularly used when measuring electricity.

You can enter kW/h (with a slash). For kVA I usually leave the unit blank then set the unit suffix manually in the text renderer properties.