LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why is exported time 1 hour ahead of hypertrend time in MAX?

Hi mdai,

 

I'm not sure if you mean in DIAdem or MAX. Neither applications appear to use the term "project".

 

In DIAdem, they are both "float64".

 

In MAX, they appear to be "double", a screen shot is below.

 

Cheers,

 

PorridgeMan.

 

New Picture.jpg

0 Kudos
Message 11 of 14
(871 Views)

Quote:

 

Yes, that was my first thought as well, but even though we are in summer here (southern hemisphere), daylight savings is not used and the PC clock has it turned off. Odd, maybe MAX uses a different clock.

 

I believe it's a time settings issue too.  Could you try to enable daylight saving in your Windows and try export to DIAdem again?

 

PS, the trace is logged as double type as the datatype is 7(analog) in your property dialog.

0 Kudos
Message 12 of 14
(853 Views)

Hmm, this gets complicated.

 

I did an experiment where I focussed on a 1 hour period of data. The data consisted of a single trend (i.e. time and measured property). First of all, I did a direct data transfer of that period from the Citadel database into DIAdem using the Remote DataStore feature. That worked correctly (for once). I then exported the same data from MAX to .csv and .dat and then loaded both formats into DIAdem. I then turned daylight savings time (DST) correction on in the PC clock and did exactly the same .csv and .dat exports/imports again. What I found is:

 

With DST off

1) .dat  - the measurement data was correct, but the time base was too large by 1 hour (i.e. needed to be offset by -1 hour).

2) .csv (text) - everything was correct.

 

With DST on

1) .dat  - the measurement data was exported from the previous hour and the time base was too large by 1 hour (i.e. needed to be offset by -1 hour).

2) .csv (text)  - the measurement data was exported from the previous hour and the time base was too large by 1 hour (i.e. needed to be offset by -1 hour).

 

Gosh, what a mess. I think there is just some silly bug at work here.

 

Anyway, if the Remote DataStore option is still the recommended route (see comments from Eric B.), this is all academic and we should concentrate on what is going wrong there. Does anyone have any ideas on why this sometimes only gives me portions of the requested period?

 

Cheers,

 

PorridgeMan.

0 Kudos
Message 13 of 14
(832 Views)

PorridgeMan,

 

 

Do you have a support contract with NI?  I think the best next step is to have to you create a Service Request with our Applications Engineering department.  This way I hope you can shared your database files with us so NI R&D can take a closer look at what might be going on.

 

 

Thanks, 

Mark
NI App Software R&D
0 Kudos
Message 14 of 14
(824 Views)