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.

Yes I suppose concurrent points would be an issue.. I have had this working now for a few days and it seems to be functioning correct although the virtual point seems like a clean way to mitigate the concurrency so I will probably try that, Thanks Guys.

Looks like a load of missing menu items to me. If you can edit the JSON, Amend it to this: { "menuItems": [{ "name": "ui.dataPointDetails", "permission": "superadmin" }, { "name": "ui.events", "permission": "edit-ui-pages" }, { "name": "ui.watchList", "permission": "edit-ui-pages" }, { "name": "ui.settings", "permission": "superadmin" }, { "name": "ui.help", "permission": "superadmin" }, { "name": "ui.docs", "menuHidden": false, "permission": "superadmin" }, { "name": "ui.plantaDeTratamiento", "url": "/planta-de-tratamiento", "linkToPage": true, "permission": "user", "menuText": "Planta de Tratamiento", "pageXid": "cd3b879e-125a-4544-9df4-7b7479b6c017", "menuHidden": false, "weight": 1000, "abstract": false, "menuTr": "Planta Tratamiento" }, { "name": "ui.estacionbomb.acueducto", "url": "/acueducto", "linkToPage": true, "permission": "user", "menuText": "Estacion Bombeo", "menuTr": "", "pageXid": "3efbd854-5e20-4fc7-8e78-a7a1d4ce15f1", "menuHidden": false, "weight": 1000, "menuIcon": "E", "abstract": true }, { "name": "ui.estacionbomb.acueducto.estacionbomb", "url": "/estacionbomb", "linkToPage": true, "permission": "user", "menuText": "Estacion de Bombeo", "pageXid": "3efbd854-5e20-4fc7-8e78-a7a1d4ce15f1", "menuHidden": false, "weight": 1000, "abstract": true, "menuIcon": "E" } ] }

Hi Pikey4, We typically encourage use of Mango in a mainly supervisory role to the controller. In my mind, it would primarily matter about how the timing and response needs to be. Should you require a response time that is always necessarily predictable and minuscule, you could encounter complications with things like Java garbage collection and whatnot. Having a webserver would provide an opportunity to spontaneously increase the memory load of the unit, and if it paused control when millisecond timing was important, that would be a problem. I would not let Mango time my engine's firing. But, I wouldn't hesitate to let it toggle my vehicle between driving modes (if I had such modes). Beyond timing as a concern (because it will respond within seconds almost always), one could question the reliability of the endeavor. Mango is crashable. You can crash it still by doing things like running massive reports or kicking off an infinite loop in a script validation. What's more, Mango has a webserver, so you need to either lock down access or your control system could get hit with a denial of service attack. Bad news. Then there are the issues that the user of Mango could build into their solution (in haste or innocence) because Mango is complex. If Mango is logging data and the disk fills up, you wouldn't want the process control to suffer. Then there are issues [a] developer[s] create[d], because Mango is complex. I'm not familiar with cascading pumps for demand, so I can't comment on the specific problems you may face there. But I certainly think you can have Mango making determinations in your distributed system and submitting controls, for sure. Most situations are different, so there is just cause for much thought on the redundancies required and the ways Mango could fail in a given system, and how the system can fail. We always encourage publishing the data to a cloud Mango instance if you are doing controls with Mango, and then visualizing your data in the cloud instance. We are a SCADA platform, we do SCADA applications.

Anytime, always here to assist.

OK got it thanks

Yes, the NoSQL backup is just a zip of the entire Mango/databases/mangoTSDB directory, while the increment is just a zip including the files that changed from last backup. So, as long as the points existed in the configuration you are restoring, you will have no issue restoring a NoSQL backup later than the SQL backup in question.

Hi Phillip, Thanks for bringing that to our attention! It looks like when I made the sync tracking more efficient I didn't fix that column to use the new logic. The sync tracking turned out to be one of the culprits in H2 databases getting gigantic. Anyway, I have fixed the table for the upcoming 3.5 release to display the "Consider sync'ed unto time" showing up in that column again, even if the publisher is disabled (which is an enhancement of the old functionality).

The BACnet4J 4.1.6 Release was only to update the build system and did not effect the performance of the library. We are currently in development of 4.1.7-SNAPSHOT which should be released as 4.1.7 by the end of August. So basically you aren't missing out on any features that have been released by using version 4.1.5 As for your problem, it looks like the new device is sending a message that BACnet4J doesn't understand. This is causing the Transport layer to reject it when it tries to process it. I suggest that you start by getting a Wireshark capture of the messages the new device is sending to Mango, specifically the Unconfirmed COV Notification Requests as they look to be malformed.

@phildunlap Hello, yes I received your email, I will reply to the email.

@psysak It looks like you are using an older version of the BACnet4J library, I would suggest using the latest version 4.1.6 and see if you still have the problem. If you do then re-post the new stack trace so I can see how it fits in the latest code. I'm working on the library this week so if you can get the me the info before I move on then I'll make a fix if something is broken.

@phildunlap said in Excel Report: the top section of /system_settings.shtm I just checked the top section of /system_settings.shtm and I actually saw that you are using H2. I think it was something of the update, because I made an update and since then it did not work anymore, but before that it was like MYSQL. I will pass the database to MYSQL and check if the error will continue.

Good to know thanks Jared.

You could manually download the Data in CSV format, manipulate it and then upload it again. If you need to have it automated I have a feeling you could write a metadata point script that would determine if data is being lost by looking at the last time data was logged and then average the spiked reading over the time the data was lost. What are the logging settings you are using on the Data Point?

@joelhaggar Thanks for that the link to the manual upgrade. The upgrade worked, but there are still problems. The upgrade from 3.3.4 to 3.4.4 broke numerous metadata scripts (a problem someone else posted in https://forum.infiniteautomation.com/topic/3627/not-a-function). Also, the internal upgrade is still not working. I just tried to upgrade the two modules listed on /ui/administration/modules/upgrade: mangoNoSqlDatabase Time Series Data Store 3.4.0 3.4.1 MangoUI Provides an AngularJS user interface, 3.4.6 3.4.7 However, the automated download failed once again: WARN 2018-07-11T20:40:26,229 (com.serotonin.m2m2.web.dwr.ModulesDwr$UpgradeDownloader.run:503) - Upgrade download error java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:210) ~[?:1.8.0_131] at java.net.SocketInputStream.read(SocketInputStream.java:141) ~[?:1.8.0_131] at org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:137) ~[httpcore-4.4.9.jar:4.4.9] at org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:153) ~[httpcore-4.4.9.jar:4.4.9] at org.apache.http.impl.io.SessionInputBufferImpl.read(SessionInputBufferImpl.java:206) ~[httpcore-4.4.9.jar:4.4.9] at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:176) ~[httpcore-4.4.9.jar:4.4.9] at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:135) ~[httpclient-4.5.5.jar:4.5.5] at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:148) ~[httpclient-4.5.5.jar:4.5.5] at com.serotonin.io.StreamUtils.transfer(StreamUtils.java:34) ~[mango-3.4.4.jar:?] at com.serotonin.io.StreamUtils.transfer(StreamUtils.java:27) ~[mango-3.4.4.jar:?] at com.serotonin.web.http.HttpUtils4.execute(HttpUtils4.java:105) ~[mango-3.4.4.jar:?] at com.serotonin.m2m2.web.dwr.ModulesDwr$UpgradeDownloader.run(ModulesDwr.java:499) [mango-3.4.4.jar:?] at com.serotonin.timer.Task.runTask(Task.java:179) [mango-3.4.4.jar:?] at com.serotonin.timer.TaskWrapper.run(TaskWrapper.java:23) [mango-3.4.4.jar:?] at com.serotonin.timer.OrderedThreadPoolExecutor$OrderedTaskCollection.run(OrderedThreadPoolExecutor.java:336) [mango-3.4.4.jar:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_131] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_131] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131] The ping time from my Mango server to infiniteautomation.com is close to 700ms. Perhaps there is a timeout in the Mango download function that is too strict to meet that loop time?

Thanks Jared. For now we set web.security.iFrameAccess=ANY as a test and it works great. We might restrict it further in the future.

Thanks @phildunlap Yes it was from a MPTCP Data source. I have altered and will see how it goes. Thanks

Works great on LibreOffice and numbers! Excel just cant get it right I have tried all the delimiters.

@phildunlap said in Create event detector that applies to all/specific datapoints: You'd have a bunch of options to hack it up. You had me at hack I've got a status dashboard doing something similar already. Although I can likely extend what you've done here and implement an email with a template listing all iffy datapoints. It's not an alarm per se but it sure is a darn good start. I'll put it in the wishlist. I think it'd be good to datasource/point template wide alarm settings that individual points have. Inidividual point alarms override template -> template override datasource. That's my idea. Thanks again Phil! Fox

https://forum.infiniteautomation.com/topic/3635/release-notes-for-mangoui-3-4-7