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.

@pierjsap said in How to managed data on DB and query by ma-point-query: What's wrong? I specified "from a dashboard", you are trying to use the function in a server side script. These are two different environments. @pierjsap said in How to managed data on DB and query by ma-point-query: Would you give me an example of how to recall classes and methods for working with datasoruce and datapoint and extracting the fields? I was not suggesting to tag data points from within a script, in fact I would advise against this. I was suggesting to setup all your data sources for the sensors and possibly meta data sources as required then tagging these through the bulk data point editor in the UI. You can these use these tags from your dashboards to locate the applicable data points for the machine you are viewing.

Hi Phildunlap, I have an update. The mission time is being received through serial communication and is saved as a data point. How can I use that to configure the axis?

@phildunlap SHOW !!!! Thank you, Thank you, Thank you.

Hi Gordoe, Good question! Alas, I'm not too sure. i can tell you that the OPC module is using the org.openscada OPC version 0.9 library to actually do the OPC protocol. I have very limited experience with OPC devices. It looks like you could modify a Mango/bin/ext-available script to set the log level for the logger in the library to a lower level by change its JAVA_OPTS to -Dorg.slf4j.simpleLogger.defaultLogLevel=debug or put a config file someplace: https://stackoverflow.com/questions/14544991/how-to-configure-slf4j-simple I'm not sure I found the ideal place to explore v0.9 of the source code for the library on the web.

JAVA_HOME would be defined as an environment variable in the OS, so that's Control Panel --> System --> Advanced System Settings --> Environment Variables as C:\path\to\jdk1.8.0_x You could also modify your Path environment variable to ensure jdk/bin/ is sooner on the path than jre/bin/ (or remove the jre path entry entirely) Are you sure you downloaded a JDK when you installed Java?

Great thanks! I will try that out.

The Import / Export tool tries to not delete things. You could delete them surgically from the database if you trust your SQL or you can. delete from eventDetectors where sourceTypeName='DATA_POINT'; Then import your configuration backup of the data points again.

@phildunlap said in system drops: You would need a license or Mango would shut down on a timer. But yeah, you could install it and migrate your data from your existing H2 database on the /mango_no_sql.shtm page. I told you that you would need a license to use NoSQL. This is all in the context of the memory issue. If that is not occurring any longer, great! It's possible you either increased the available memory as discussed, or that your point values table was large.

Hi guys, Series are limited to millisecond resolution for storing values and if using the NoSQL database will not have more than one value at one millisecond. The charting limit is indeed 5001 by default and can be changed. https://forum.infiniteautomation.com/topic/2983/increase-the-5001-limit-on-values-in-the-new-dashboards-ui TLDR Administration --> UI Settings

OK, got the device set up correctly and the node scan finds it now! On to the next step..

Hi Phil, updating the receiver worked a charm, thanks heaps.

Nginx might also do what you want and may be simpler depending on how you set it up. You can also pretty easily adjust headers on Nginx (if needed) R

Hi Phil, Thanks for pointing me to the right direction. By changing logging type mango started logging backdated values nicely. Many thanks! Thomas

@matwolff said in Mango RestApi Login V3.3.1: thanks for this as well. This would be an awesome option but would need something longer than a 3 month expiry as we wouldn't be able to trust our end users to update this regularly. You should be able to select a period longer than 3 months. You can also manually set the expiration date to anything you want. Just click the date input. [image: inHvnx4.png] @matwolff said in Mango RestApi Login V3.3.1: Also, I just tried to create a token to check it out and received an error with no token generated. Cannot deserialize value of type java.util.Date from String "2018-06-04T21:55:32.087Z": not a valid representation (error: Failed to parse Date value '2018-06-04T21:55:32.087Z': Unparseable date: "2018-06-04T21:55:32.087Z") I think you must have rest.customDateInputFormat set to something in your ${MA_HOME}/overrides/properties/env.properties file. Delete that line and also rest.customDateOutputFormat. They now have defaults for parsing/formatting dates as ISO 8601.

Hi Pedro, Which System Setting changes can eliminate this error? You could slow down the point data mover and status provider by increasing the "Batch process manager period (ms)" and the "Status update period (ms) " in the NoSQL section of the system settings. Also, if you are fully up to date, these messages have been removed entirely since they're mostly clutter. What symptoms would this error lead to? None. This would be more indicative that a garbage collection lasted longer than the intervals specified for the two tasks in part 1 of this response. We are sometimes not receiving emails of critical events. Could this be the cause? No. You should have an error in your log file about being unable to send an email if the error was known before the actual relay of the mail was handed on to the SMTP server. If you do not have an error about sending a test email when you try to send a test email, then either your SMTP provider isn't forwarding it or it's being filtered out of your inbox.

Hi Phil, Thanks for that. I tested some more and it seems related to the port I was using. The Mango is being a second DNP3 master and I used port 20002 (the other Master is using 20001). I'll investigate what ports both masters can use - unfortunately the slave device needs separate ports...

Hello. Thanks for all the feedback. Sorry for the slow reply as I was forced to get sidetracked for a bit. I did open the web console and loaded a pie chart. It spat out a JS error, which I didn't record. I think its moot now anyway, as it sounds like this was an known issue that was corrected in the last update. I checked for updates as advised above. There was one for mangoUI (6.4.0 to 6.4.2). This corrected the pie chart rendering, along with a few other issues. Cheers

Alex called us an I assured him there is enough depth in the permissions system to compartmentalize users, which seemed to be the crux of the question when we spoke.

var pvd = this.pvd; if(!pvd) { pvd = this.pvd = com.serotonin.m2m2.Common.databaseProxy.newPointValueDao(); } print( p.value ); print( p.time ); var loggedValue = pvd.getPointValueBefore( p.getDataPointWrapper().getId(), p.time + 1 ); print( loggedValue.doubleValue ); //if numeric point print( loggedValue.time ); While this could perhaps be more straightforward, I am having a tough time figuring out why one would be polling a virtual data source to get an interval logging rollup and then compute something off the interval values. It would seem to me to make more sense to record all data from the edge data source, and use the statistics functions in the scripting environment to compute the interval value you wish to use in the script body. That way if you have some anomalies you can still view the original data.

Hi @luigi here's a report of the licenses for the Java libraries that are used by Mango - https://cdn.rawgit.com/infiniteautomation/misc-files/master/third-party-report.html The libraries that start with com.infiniteautomation are covered by the Mango license. https://raw.githubusercontent.com/infiniteautomation/ma-core-public/main/Core/LICENSE