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.

Hi Ian, The lack of the template id element would lead me to believe that the property template is not required. Correct. The data history will be the same as the point to which it is linked; the logging type of "All Data" will ensure this. It's not that simple. If the publisher is sending realtime values with update / change as its update event, the data source is saving real time values, but the point on the publisher is logging on an interval then the updates within an interval would have been published and saved, while on the publisher side only the interval logging would be recorded longer term. So the settings that go into it are: Publisher update event. All publishers have this setting, and it determines when you send a value from a point (or update the publishers' data image in the case of the Modbus or BACnet publisher). The logging type of the data point being sent. For a data point logging all data, for instance, the 'update' and 'logged' events are synonymous. If the publisher transmits real time data. If not, then only historical syncs will bring about data on the receiver. If the data source saves real time data. If not, then the points will appear to update in time, but their histories will only be filled in once a history sync is run.

Hi Phil, Thanks for the quick reply. I now have the Mango login screen displaying on the cloud server. I resolved this by creating a firewall rule to allow traffic through to port 8080 (so effectively port forward). I may need to change to port 80 to lose the port from the URL in the future- thanks for that tip! The echo $JAVA_HOME. I did log out of ssh session so I think it should work. I need to look into this further but the issue right now may be my lack of linux use. I may need to add JAVA_HOME to the profile file instead. The java.net.UnknownHostException message at the stack trace- I got this message prior to creating the firewall rule so I need to check for this message when I restart Mango (I can only do this next week so I will keep you posted) Great software and great support- much appreciated Paul

Hello Jarrod, Thank you, I will enter it manually. Cheers Brian

Hi fishfacs, Its also worth noting that I can add the Amps from multiple motors on different series, so I'm guessing it is a conflict with the units of Hz and A being on the same Y axis. I wouldn't think so, series with different units can share an axis. It could be: The chart is displaying with no height. I saw this using your code snippet, but solved it by putting all those directives into a <div style="height: 300px"></div> One of the series is much more dense than the other and you've hit the limit of point values on a chart (5001 by default) and the less dense series isn't getting to return much data before that limit gets hit. Perhaps try a rollup like "Start" ? Have you tried clicking on the series in the chart legend to see if you can see the other series simply by disabling the display of one of them? Also, while I'm on the topic, I've noticed that when I mess up the syntax in any way, the preview in the page editor just shows up blank. Is there any log or debugger I can use to determine what is causing it not to render? You can open your browser's developer tools. Sometimes you'll see a related error for certain sorts of mistakes in the markup, but not always.

Did all points stop or only the COV points?

Disregard. It started working as intended following a server reboot. Thanks.

DEBUG 2019-03-26T10:52:40,708 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.:62) - Creating Jssc Serial Port Input Stream for: /dev/ttyUSB11 INFO 2019-03-26T10:52:40,714 (com.serotonin.m2m2.rt.RuntimeManagerImpl.initializeDataSourceStartup:380) - Data source 'Keepalive Connection' initialized INFO 2019-03-26T10:52:40,716 (com.serotonin.m2m2.rt.RuntimeManagerImpl.initializeDataSourceStartup:385) - Data source 'Keepalive Connection' took 24.55144ms to start INFO 2019-03-26T10:54:30,269 (com.serotonin.m2m2.rt.RuntimeManagerImpl.initializeDataSourceStartup:380) - Data source 'Keepalive Message' initialized INFO 2019-03-26T10:54:30,270 (com.serotonin.m2m2.rt.RuntimeManagerImpl.initializeDataSourceStartup:385) - Data source 'Keepalive Message' took 80.276995ms to start INFO 2019-03-26T10:57:34,036 (com.serotonin.m2m2.rt.RuntimeManagerImpl.stopDataSourceShutdown:423) - Data source 'Keepalive Connection' stopped DEBUG 2019-03-26T10:58:39,274 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.:62) - Creating Jssc Serial Port Input Stream for: /dev/ttyUSB11 INFO 2019-03-26T10:58:39,280 (com.serotonin.m2m2.rt.RuntimeManagerImpl.initializeDataSourceStartup:380) - Data source 'Keepalive Connection' initialized INFO 2019-03-26T10:58:39,281 (com.serotonin.m2m2.rt.RuntimeManagerImpl.initializeDataSourceStartup:385) - Data source 'Keepalive Connection' took 13.000694ms to start INFO 2019-03-26T10:59:36,361 (com.serotonin.m2m2.rt.RuntimeManagerImpl.stopDataSourceShutdown:423) - Data source 'Keepalive Connection' stopped DEBUG 2019-03-26T10:59:36,929 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.:62) - Creating Jssc Serial Port Input Stream for: /dev/ttyUSB11 INFO 2019-03-26T10:59:36,934 (com.serotonin.m2m2.rt.RuntimeManagerImpl.initializeDataSourceStartup:380) - Data source 'Keepalive Connection' initialized INFO 2019-03-26T10:59:36,936 (com.serotonin.m2m2.rt.RuntimeManagerImpl.initializeDataSourceStartup:385) - Data source 'Keepalive Connection' took 12.735079ms to start DEBUG 2019-03-26T11:14:00,003 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:121) - Serial Receive Event fired. DEBUG 2019-03-26T11:14:00,003 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:130) - Recieved: ERROR 2019-03-26T11:14:00,005 (com.infiniteautomation.serial.rt.SerialDataSourceRT.serialEvent:476) - null java.lang.NullPointerException: null DEBUG 2019-03-26T11:16:00,003 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:121) - Serial Receive Event fired. DEBUG 2019-03-26T11:16:00,004 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:130) - Recieved: ERROR 2019-03-26T11:16:00,005 (com.infiniteautomation.serial.rt.SerialDataSourceRT.serialEvent:476) - null java.lang.NullPointerException: null DEBUG 2019-03-26T11:17:00,003 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:121) - Serial Receive Event fired. DEBUG 2019-03-26T11:17:00,003 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:130) - Recieved: ERROR 2019-03-26T11:17:00,005 (com.infiniteautomation.serial.rt.SerialDataSourceRT.serialEvent:476) - null java.lang.NullPointerException: null DEBUG 2019-03-26T11:18:00,003 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:121) - Serial Receive Event fired. DEBUG 2019-03-26T11:18:00,004 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:130) - Recieved: ERROR 2019-03-26T11:18:00,005 (com.infiniteautomation.serial.rt.SerialDataSourceRT.serialEvent:476) - null java.lang.NullPointerException: null DEBUG 2019-03-26T11:21:00,003 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:121) - Serial Receive Event fired. DEBUG 2019-03-26T11:21:00,004 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:130) - Recieved: ERROR 2019-03-26T11:21:00,005 (com.infiniteautomation.serial.rt.SerialDataSourceRT.serialEvent:476) - null java.lang.NullPointerException: null DEBUG 2019-03-26T11:24:00,004 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:121) - Serial Receive Event fired. DEBUG 2019-03-26T11:24:00,004 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:130) - Recieved: fe DEBUG 2019-03-26T11:25:00,004 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:121) - Serial Receive Event fired. DEBUG 2019-03-26T11:25:00,005 (com.infiniteautomation.mango.io.serial.JsscSerialPortInputStream.serialEvent:130) - Recieved: ff I'll have to monitor...

This has come up in the forums before. Your best bet at this point in time is to utilise the script written by Phil and firing that to generate the format you want. https://forum.infiniteautomation.com/topic/4037/changing-the-excel-report-name

Thanks Matt, Phil... I will check out the swagger API interface. I will dive into the SQL queries too as I haven't looked at how the data is organized/stored yet.

Did you close the console that was running the H2 web console batch file? You say PC, do you mean Windows? You should be able to connect to your own machine regardless of firewalls. If you had set up your SMTP server, you could have tried using the password reset provided through Mango. On Windows both IPv4 and IPv6 address work with the H2 web console.... If you have a JSON backup in your Mango/backup you could throw away the existing data and database and reimport it into a fresh installation by moving the Mango/databases directory while Mango is not running. If you have an SQL backup in your Mango/backup from before your changed the password you could move the databases directory while Mango is not running and then restore this backup into a fresh installation.

Thanks Phil for clearing that up for me. That all makes sense now. I was wanting to capture more warnings on the Mango 3 server than I had on the Mango 2. Cheers Brian

Sure! { "xid":"EH_964391", "alias":"", "handlerType":"EMAIL", "eventTypes":[ { "sourceType":"DATA_POINT", "dataPointXID":"siteName_Error_Log", "detectorXID":null } ], "activeRecipients":[ { "recipientType":"MAILING_LIST", "mailingList":"ML_277765" } ], "sendEscalation":false "escalationRecipients":[], "sendInactive":false, "includeSystemInformation":false, "includePointValueCount":10, "includeLogfile":false, "customTemplate":null, "additionalContext":[ ], "script":null, "scriptPermissions":{ "scriptDataPointReadPermission":"", "scriptDataPointSetPermission":"", "scriptDataSourcePermission":"" }, "disabled":false } I did already blow them out of the system, I just happen to have a bad tab habit so it was still in Np++.

Yes. We also fixed it for that, and the active recipients array too (in the eventual 3.6 release).

@phildunlap said in History Data Import Doenst Work: o, if you had an H2 backup of the Mango where the data was recorded, you could restore that to have the necessary informa Thanks for the help! I will try these solutions!!

Certainly, thanks for solving it here on the forum so people may search for it!

@pikey4 Hey! Sorry I didn't reply sooner but your info helped me out. Thx. R

Sorry yes I forgot to add the column name to the arguments. Glad you sorted it out.

Ok I did that and will recheck to see where I missed the documentation. I will have a look also at the user module. That seems like a good candidate. Thanks for the pointer Jim.

It will be possible in 3.6 via //add ExcelReportVO available under 'report' variable name for post processing script for(var k = 0; k < report.getTimeSeries().length; k+=1) { //epoch time of time series beginning and end, for actual run var startTimestamp = report.getTimeSeries()[k].getStartTimestamp(); var finishTimestamp = report.getTimeSeries()[k].getFinishTimestamp(); }