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.

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(); }

@psysak This will be a lot easier in Mango 3.6, stay tuned.

Yes. The only thing to add to be fully correct is that start times are inclusive, end times are exclusive (at the millisecond level).

Whew! Glad that you were able to reproduce it. heh

Edit: I see that having the space after the "<" prevents the chopping. Very odd... As I mentioned above, I have only seen this behaviour in the scripting data source editor.

After today's reboot (for OS and module updates) everything is working well. It could also have been the previous time the modules were updated, as we only reboot these for updates.

Hi,
Thanks for your prompt reply.
I restored the database , and all good now. The times on the logs were out, as I just "grep ERROR *ma.log" and cut/paste the interesting ones.

Thanks again - Its the fastest SCADA support I have seen.

to your third point, actually on GMT-08:00, which does explain that!

Wait, there aren't 22 hours in a day? Whoops :P

The offsets are right - still trying to sort why the epoch value is off by a couple of days +/-. Will keep mucking about here.

How did you know the value in the register before reading it? Perhaps it's not sync'ed to the right time. The bit banging to decode registers into data types can be found here, but it's quite unlikely there's an issue there: https://github.com/infiniteautomation/modbus4j/blob/master/src/com/serotonin/modbus4j/locator/NumericLocator.java

Phil! thanks for show me the light at the tunnel end hehe, with the virtual serial server i was able to get the data from the gateway, i think the magic is in the regex both in the datasource and datapoint. Now i can listen the raw data and digest it through an Scripting DS.

Regards!.