LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

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

Hello People,

 

I'm not sure which board to post this question in; if there was one for MAX, that's where it would go.

 

I have a problem when using MAX to export data from a Citadel 5 database. If I use the "Export to DIAdem..." function, the time base of the exported data is shifted +1 hour (compared to the live hypertrends in MAX). However, if I use the "Export to Text...", the time base is correct.

 

Does anyone know what causes this problem? It would be nice to be able to fix it, as the amount of data I'm exporting is impracticably large for text. I have also tried extracting the data via a "Remote Datastore" connection in DIAdem, but for some reason that only grabs clumps of the range I request, so am stuck with the "Export to DIAdem..." function.

 

We are using MAX v 4.5.0f0.

 

Any advice appreciated,

 

PorridgeMan.

0 Kudos
Message 1 of 14
(3,776 Views)
I had a similar problem in LabVIEW once and it turned out to be due to the day light saving settings
David
www.controlsoftwaresolutions.com
0 Kudos
Message 2 of 14
(3,770 Views)
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.
0 Kudos
Message 3 of 14
(3,744 Views)

You mentioned trying a remote DataStore, do you mean creating a Citadel 5 DataStore as detailed in this KnowledgeBase? http://digital.ni.com/public.nsf/allkb/B0DBF70DEB899B74862575A600523042

 

What sort of problems were you having when setting up that DataStore?

Eric B.
National Instruments
0 Kudos
Message 4 of 14
(3,720 Views)

Hi Eric,

 

Yes, this is exactly what I tried. The problem I've had is that the interval which (I believe) you have to specify in the DataStore properties (i.e. Start Time and End Time), are not correctly observed. The start time is always correct, but the end time is not. The online help on configuring DataStores is poor, so maybe I've missed something out.

 

Cheers,

 

PorridgeMan.

 

P.S. I'm using DIAdem 11.1.0f3806 TDM.

0 Kudos
Message 5 of 14
(3,713 Views)

PorridgeMan,

 

What are the exact Start Time and End Times you are configuring, and what data do you get into DIAdem?  Using a DataStore is the recommended way of getting that Citadel data into DIAdem, it'd be better to find out what is going on there rather than worrying about exporting the data directly from MAX.

Eric B.
National Instruments
0 Kudos
Message 6 of 14
(3,690 Views)

Hi Eric,

 

OK, here is an example. Below is a screen shot of the DataStore range I am requesting. When I drag the PST_002_FCE channels to the Data Portal, I get the range requested. When I do the same for PST_002_PRS, I get the following range:

 

11/12/2009 09:00:00.0140

14/12/2009 14:01:29.2020

 

However, there is continuous data in PST_002_PRS between 14/12/2009 14:01:29.2020 and 24/12/2009 09:00:00.0000, it is just not being acquired by DIAdem.

 

Trying other channels yields similar results, but with varying end times. There seems to be no consistent error.

 

Cheers,

 

PorridgeMan.

 

CETO DataStore.jpg

0 Kudos
Message 7 of 14
(3,680 Views)

Where you able to export that specific trace to a text file from MAX?

 

What is the data type of the failed trace?

 

--J.D. Robertson

Senior Software Engineer

National Instruments

0 Kudos
Message 8 of 14
(3,671 Views)

Hi J.D.,

 

I have never had a problem with text exports from MAX. I did export the failed trace as text, but could not load it into DIAdem as it was too large. This was the error message I got.

 

The data types of the channels in the failed trace are time and numeric.

 

Cheers,

 

PorridgeMan.

0 Kudos
Message 9 of 14
(3,652 Views)
What's the exact type for the time and numeric trace there?   if the data logging is from a shared variable, you can right click your variable in project window and choose property to it's data type.
0 Kudos
Message 10 of 14
(3,641 Views)