local app export data - time stamp translation needed

Started by mtdoc, December 15, 2012, 01:24:56 AM

Previous topic - Next topic

mtdoc

Ok - I had an arc fault on one of my Classics today. I'm trying to pin down when it happened. Unfortunately there is no logging of the time when a fault occurs - at least not that I can see.

I can determine the time by looking to see when the output of the Classic went to zero - but after exporting the data I'm having a hard time figuring out how to translate the time stamp in the A column of the export csv file.

I've tried the formula that is listed but the result I get does not make any sense:

Per the csv file:

QuoteThe timestamp format is in UTC milliseconds since 1/1/1970 00:00:00. To convert to a time compatible with Microsoft Excel or Sun OpenOffice.org you can use the following formula: =(A1/1000 + <timezone Offset>*60*60)/86400 + 25569.  Where 'A1' is the cell with the timestamp Replace '<timezone Offset>' with your GMT offset (e.g. US PST time is GMT-7 so use -7; Brisbane Australia is GMT+10 so use 10)

So for example, using that formula with my PST time zone offset for the first cell (A9) that has data - which should correspond to just after midnight, using the A9 time stamp value of 1355472009500 I get a result of 41257.04178 ???? :o

What am I doing wrong? Help!



Array 1: Sanyo HIT225 X 8 on Wattsun tracker. Array 2: Evergreen ES-E-225 X 12 on shed roof. Midnite e-panel with Outback GVFX3648, FNDC and Classic 150 X 2. 436 AH AGMs. Honda eu2000i X 2.

boB


I think that to find the time of the arc fault you will have to go to the Classic MNGP itself to check the recent history (minutely as opposed to daily) logs and see when it went to resting.

The local app does not yet download that minutely/hourly history.

The time stamp on the daily ~should~ happen at midnight (23:59) if the clock is set correctly.

I agree, we should be logging faults.

boB
K7IQ 🌛  He/She/Me

TomW

Just FYI, that epoch date (135547200950) converts to GMT: Sat, 15 Dec 2012 12:56:08 GMT.

I find this converter much easier than math. In case you need to convert another epoch date to human readable:

http://www.epochconverter.com/
Do NOT mistake me for any kind of "expert".

( ͡° ͜ʖ ͡°)


24 Trina 310 watt modules, SMA SunnyBoy 7.7 KW Grid Tie inverter.

I thought that they were angels, but much to my surprise, We climbed aboard their starship and headed for the skies

mtdoc

Thanks guys.  Yes - logging of alerts and faults would be great.


Quote from: TomW on December 15, 2012, 08:05:24 AM
Just FYI, that epoch date (135547200950) converts to GMT: Sat, 15 Dec 2012 12:56:08 GMT.

I find this converter much easier than math. In case you need to convert another epoch date to human readable:

http://www.epochconverter.com/

Ah  I see, it's a Unix thing. No wonder I was lost  ::)

Still not sure why the formula given in the CSV isn't working for me - but I'm too lazy to work out the math - especially when there are on line conversion calculators.

The link is great.  Thanks Tom.
Array 1: Sanyo HIT225 X 8 on Wattsun tracker. Array 2: Evergreen ES-E-225 X 12 on shed roof. Midnite e-panel with Outback GVFX3648, FNDC and Classic 150 X 2. 436 AH AGMs. Honda eu2000i X 2.

dRdoS7

#4
Hi,

Did you format the cell for date time?

dRdoS7

PS. I get: 18:00 Friday, 14, December 2012. I'm in Australia (+11 AEDST)