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.

@pascal are you talking about Excel reports?

The cron expression should be evaluated against the server timezone AFAIK (it uses the timezone from the OS/JVM by default, you can override this in your env.properties file).
Are you sure you don't have your server timezone set to UTC?

@pascal said in Use of CRON to schedule reports.:

What is the behavior of the CRON expression when DST (daylight saving time) adjustments apply

Good question. Our cron code is based on the Quartz scheduling library v2.1.0, so this should help -
http://www.quartz-scheduler.org/documentation/faq.html#FAQ-daylightSavings

Of course if its actually evaluating the expressions as UTC time then there is no DST.

Hi arvand,

The functions in "About Mango JavaScript" will work in Mango scripting contexts only, so Scripting data sources, meta data points, point links, etc.

Judging from that snippet, is it part of a dashboard you're designing? If so, you could check out the existing getPointValue.js file in the UI module powering the ma-get-point-value directive, or check out the NodeJS style use of the REST API for point values, here: https://github.com/infiniteautomation/node-mango-client

If it really is in the Mango JavaScript environments, you can print(p123); to see the available functions on the context point.

Thanks for sharing the resolution!

Yes I tried to stop and start Mango again but it didn't help at all.

Finally I resolved it by editing script in ma-start.bat -

"%EXECJAVA%" %JPDA% %JAVAOPTS% -server -Xmx2500m -Xms1000m -Dma.home="%MA_HOME%" -cp "%MA_CP%" com.serotonin.m2m2.Main

Maybe it's not elegant but now I see change in memory usage after starting Mango.

Thanks for help.
Greetings

Hi Dan,

Perhaps your Mango is quite old? The sleep function was added sometime ago as a wrapper for Thread.sleep. You may still be able to do java.lang.Thread.sleep(XXXX); if you are using Java 8.

something screwy about this new history purge feature. I made a mistake entering the end date when I ran the first time and it created records back to 1969.

0_1516390980443_bbdbd51f-58e3-4567-86d7-fbdba57debbb-image.png

TL;DR If you make an excel template, limit your named ranges to as small as possible

Alrighty, so after a few more days of troubleshooting, @phildunlap took a look at my excel template. He determined that the named range I designated in Excel was too long (only by a million cells!) for EACH named range, of which there are about 50. So, the theory was that the POI Apache plugin that allows Mango to interact with Excel was loading these empty cells into memory somehow, and was sporadically causing a memory leak or memory usage at least until the point where it would cripple the amount of available memory to the JVM to VERY VERY low, and render the garbage collection useless. Thats a mouthful.

And so, the problem only reared its ugly head once in awhile, it was hard to track down, but I've been operating for about a week now with no "crippling" memory issue, and I've launched thousands of reports without issue. For anyone who wants to know, the final template filled in is 82kb, has charts and 5 sheets of data, the time range spans 14 months and there are multiple different time ranges used and approximately 10-15 data points queried.

Hi Terry,

I've emailed you a log file separately regarding this issue. Thanks for the help!

Sure, you would do the same thing to get pvd, then do

var values = pvd.getLatestPointValues(dataPointId, 2);

It is expected. Ideal or not, who can say. But, originally there was 'no change' to facilitate this kind of point, and it would do what you described. But, it also generated a 'point updated' event every poll period. So, in comes the non-polling virtual data source, which never schedules itself to do any work, it just sits there.

I could understand using the start value even still in this situation: it does seem implied. But, it's just as easy to initialize them elsewhere.

@te36051 said in How to make Data source page?:

Sory for my English language. I want to build my page. May be include graphic, gauges or anything for my design. And one I want include datasource table and chart function same example below picture into my page too. Can you recommend me?😅

No worries. I would use the word "watchlist" for what you posted, and the chart would then be a "watchlist chart". That's what it will be called in the API docs

Nice! Glad you got it working!

Glad to hear it! It should work in any script set point event handler, but you may need to give the handler sufficient script permissions (add 'superadmin' to the script permissions fields on the event handler) and ensure the event is raised.

Thank you for your advice. I got this working last week, but as you indicate, it requires tree structures in Mango 2.8.8:

one metadata point used for creating a context change from user input one metadata point to detect the context change then execute the script one scripting datasource to set multiple points each time the context of the first point changes

I'm glad to hear this has been simplified in Mango 3.x.

If the inserts are generated faster than they are processed, they would certainly not finish the queue. The SQL point values table hasn't been performance tested in quite some time. The NoSQL backend is so much faster it isn't really worth it. Our licensing in version 3 is such that only free licenses don't have an unrestricted NoSQL license. If using SQL you really need to keep that table small.

I've not had issues with Aurora. I'm not sure that was the AWS RDS I've used by name but I've not had issues with the Amazon RDS in general.

Using NoSQL would have behaved fine in the situation you describe to store data sufficient to charting it that way. Rollups should chart even if the value was log on change.

Certainly! Glad to hear you got it working!

Certainly! I did just edit it though... needed to be more caring with system resources than I was.