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.

https://forum.infiniteautomation.com/topic/3991/release-notes-for-scripting-3-5-1

@chio said in Stop data logging on date source exception:

when faulted it stops responding to Mango queries via Modbus TCP

How did you verify this?

@iperry It actually is possible, you just need to enable HSTS in the env.properties -

# Configure HSTS (HTTP Strict Transport Security) # Enabled by default when ssl.on=true # Sets the Strict-Transport-Security header, web browsers will always connect using HTTPS when they # see this header and they will cache the result for max-age seconds ssl.hsts.enabled=true ssl.hsts.maxAge=31536000 ssl.hsts.includeSubDomains=false

This will only affect browsers, as @Puckfist says HTTP is actually still enabled and you can make REST requests over HTTP using a script for example.

Just bear in mind that the browser will remember the HSTS setting and refuse to connect to HTTP for the specified amount of time after you configure this.

Glad to hear it!

Sorry I should have qualified that question. I meant if they were run exactly on the hour would they be equivalent?

Hi Psysak,

It's possible the devices are indeed dead. We'd prefer to address this over email if possible. Can you send in a link to this thread and the serial numbers for the MangoES units in question to support@infiniteautomation.com ? Thanks.

@phildunlap said in Implementing project tracking sheet:

Not yet. It would take something like a script shuffling it into a data point to make it available to an excel report, currently.

Would it be better, and feasible, to implement the same thing using alpha points?

Yes I have seen it before in my case Mango was not running on the server. What you are seeing is from your browser cache. Try doing a hard refresh and see what errors you get in your browsers console.

Hi Ian,

You could do this by modifying the Mango/web/modules/mangoUI/web/mangoUi.js file. The string Mango v3 only appears in the relevant place (you'll need to address the use of titleSuffix elsewhere in the file, probably).

The <title> element is in Mango/web/modules/mangoUI/web/ui/index.html

Modifying those will not persist through an upgrade. While you could put them into Mango/overrides/web/modules/mangoUI/web[/ui] I would not advise it, since that could break other things in the UI upon update.

Edit: See this thread for a better way to do it: https://forum.infiniteautomation.com/topic/4457/cutomizing-the-tab-name

Hi Phil,

Ohh good, thought we might be going crazy. heh

Thanks
Ian

Thanks Craig.

Thanks Phil. Looks like selecting the points to ignore if missing did the trick.

Hey Phil, thanks for that.
I'll give it a go on a clean installation.

Cheers
Dan

Ok. I'll give that a go. Thanks for the help Jared.

@chrapchp here's the commit where I added the bookend attribute for reference - https://github.com/infiniteautomation/ma-dashboards/commit/4180be9742aa02017e869c96a5b5c3d8097d3e92

Hi fishfacs,

The /ui/administration/excel-reports and /excel-reports.shtm#finished pages have a table of previously run reports and information about them.

As far as logging, the excel reports module has pretty sparing debug information (and the error level logs would already appear in the Mango/logs/ma.log file). One information about queuing reports, starting and finishing. That would be debug level logging on the com.infiniteautomation.mango.excelreports that you would be adding to Mango/classes/log4j2.xml (copy to Mango/overrides/classes/log4j2.xml for persistence on upgrade).

I am not aware of how much logging there is to be had in the Apache POI library. That would be the org.apache.poi package, and I would expect either debug or trace level logging.

An entry like what I'm referring to in the log4j2.xml file looks like:

<AsyncLogger includeLocation="true" name="org.apache.poi" level="trace"/>

In my experience, having some really large named ranges is a way to slow reports down. Defining a range only requires a starting cell and a second cell to specify the direction to expand. Some people are tempted to select entire rows or columns when selecting the cells to create the named range, but this is not necessary.

Also so far as Java slowing down, if you schedule a whole bunch of reports to run at the same time, such that they compete for memory, they may run significantly slower than if they were run in sequence.

If your report is taking minutes to run, you can download a few thread dumps from the /ui/administration/system-status/threads while it is running and send them to support@infiniteautomation.com and I will attempt to resolve what is taking the time.

Thanks Jared, found what you mean. I don't recall seeing that in the Documentation part of the site, and it never occurred to me that permissions were also in amongst system settings. Would prefer if they were all in one place personally. But that's just my opinion.

Fox