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.

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

Hi Ian, Why are you trying to do such a thing? No, a named range can only be associated with one time period or series in one time range. The reason being is that the ranges expand and you would never want one series to overwrite another (which I believe you could still achieve by having two named ranges grow over one another, one down and one over). If they are distinct time periods, why not put them on their own sheets? I would think Excel has the capacity to generate a column by appending columns on other sheets together. I would expect you want 80+ named ranges for the columns in the report. You could have all the points in the same time period in the excel report setup, but you would probably want to separate each sheet into its own time period so that each sheet has timestamps that you could append together to create something like the example excel cells you posted.

Old thread I know, but I've been having this same issue on a RPi installation. I hard set the memory and I think it might have fixed the issue. Cheers Dan

I would say the closest we are to having a fail-over system right now would involve some development work to revive some of the NoSQL database integrations we've done in the past, which would generally lead to increased costs in either licensing the database engine or the increase in disk and processing power some of those database engines require. It also means we're not necessarily in control of solving every encountered issue (which we still aren't, but this was a large reason of why we kept improving out own NoSQL database). It's completely possible for authenticated users to crash Mango by making too many and/or too large of requests. Give someone data source permission and there's even more potential for trouble. That said, a single, well managed instance can achieve the metrics specified in your post of requirement 5. Thinking of your own deployments, do they already meet that standard?

Hi Jenny, I have sent you an email about this. For license and accounts issues, we prefer to conduct those via email.

Hi James, welcome to the forum! You could use the Mango/bin/h2-web-console script to launch the H2 web console, then after logging in with the credentials from the H2 section of your Mango/overrides/properties/env.properties file (or Mango/classes/env.properties) to login and DELETE FROM dataPoints WHERE id=(SELECT MAX(id) FROM dataPoints); You can find more about the web console here: https://help.infiniteautomation.com/about-the-h2-database Or you could move your Mango/databases/ directory, then start with a clean database and restore a backup. That should give you a little time to poke around before it shuts down due to too many points.

@sbaik said in filter points being used in graphics: Is there a way to sort all points being used in the custom page graphics? There's no easy way unfortunately. The only suggestion I could give you would be to open your dev tools and look at the network requests your dashboards are making. You will see requests to /rest/v2/point-values/time-period/{xid} for example when its fetching point values for a particular point. You can also find the websocket for live point value updates and see what XIDs it is listening to - [image: ZgGXsiG.png]

@andrew-oxner said in 3D Models of a building or space.: But I'm looking for more of a 3D environment is this possible in Mango? Are you actually wanting to display the 3D model in the dashboard so you can click and drag and rotate etc? Craig is talking about displaying a 2D projection of the model in the dashboard. If you did want a 3D model it would be possible using a WebGL library but you would have to implement that all yourself. If you do want a 2D projection you could follow Craig's advise and export the drawing as a JPEG then manually draw SVG layers over it and bind these to the Mango data points. Or you could export the projection as a PDF, convert to SVG then manipulate that. There may be an easier way to export to SVG, thats just what I found when I googled exporting SVG from Sketchup.

Hi @JoelHaggar Ahh, Excel my nemesis, we meet again :P Thanks for the suggestion. I added 2 rows to the report template and the export is now working as I would expect. [image: TEIONvl.png] Ian

Technically the free / unlicensed core in 3.x is only to be used for personal, educational, and other non-commercial uses, so I hope that limitation is being honored along with the 300 point limit. There are other ways to do it that would not use a data point, and then not get you closer to the limit. Still operating under the assumption this is Modbus, the Modbus4J code is open source and you could create the right requests from a script and submit them to the Modbus master. A script solution is also completely possible (where you read the registers as a different data type and then do bitmasking in a script as you suggest. You would just have to encode what to do to the Modbus point into the point that updates the script's context, and do something like, //untested var data = input.value.split("-"); var mask = 1 << parseInt(data[1]); if( data[0] === "0" ) modbusPoint.set( modbusPoint.value & ~mask ); else modbusPoint.set( modbusPoint.value | mask ); Or for that matter scripts can use the JsonEmport tool to modify points during script runtime.

Thanks @phildunlap with your fast support once again.

C:/Users/DCU/test outside C:/Mango The webserver cannot try to open a database URL outside its Mango directory. You're probably looking for a URL of jdbc:h2:C:/Mango/databases/mah2

Thanks. It worked.

@phildunlap I guess the thought was to have the function built in within Mango to not rely on the browser. In the case that the user needs to switch browser, clear cookies, or something to that aspect. But I did not consider the vulnerability of network information. Will talk it over with our tech director some more.