LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Auto index only shows partial data

Solved!
Go to solution

I guess it doesn't really matter how many times you transpose a 2D array to get the expected result.  Personally I'm partial to 0 or 1 but its a really cheap operation.

Capture.PNG


"Should be" isn't "Is" -Jay
0 Kudos
Message 31 of 53
(1,489 Views)

I added a new column to the data file: timestamp.  Is there a way I can get data from the Excel based on a range that I input?  In my file, the first timestamp is 12:15:42.406 and the last one is 12:15:44.282.  How can I enter a range e.g. 12:15:42.406 - 12:15:43.544 and only display that data?  Could someone point me in the right direction?

 

Also, how can I choose an answer as the solution?

 

Thanks. 

Download All
0 Kudos
Message 32 of 53
(1,452 Views)

If you have the two timestamps you want to be between and an array of the timestamps, use Threashold 1D Array to find the index range that you should be using.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 33 of 53
(1,446 Views)

@crossrulz wrote:

If you have the two timestamps you want to be between and an array of the timestamps, use Threashold 1D Array to find the index range that you should be using.


Time to XL can be downloaded from here https://decibel.ni.com/content/docs/DOC-19689

 

Excel won't treat strings as dates

 


"Should be" isn't "Is" -Jay
0 Kudos
Message 34 of 53
(1,421 Views)

Is it possible to simply click on the time during run-time and change it?  

 

Also, how can I reduce the range?  The time axis currently has a range of 17 seconds.  I'm not sure where that number is coming form.  I tried going to properties and changing the scaling factors but I can't change it.

0 Kudos
Message 35 of 53
(1,391 Views)
You need to change the chart history length. The total available length depends on dt and the history size. Autoscale the x axis to see all available points.
0 Kudos
Message 36 of 53
(1,381 Views)

If I change the chart history length, doesn't it affect what's stored in the chart data buffer?

0 Kudos
Message 37 of 53
(1,375 Views)

@rhupd wrote:

If I change the chart history length, doesn't it affect what's stored in the chart data buffer?


Yes, of course! Isn't that the point?

 

I don't know what you tried when you say that "... I tried going to properties and changing the scaling factors but I can't change it....".

You need to define dt so the chart knows the time increment per point. You can change the visible range by turning off autoscaling and defining the axis end points.

0 Kudos
Message 38 of 53
(1,360 Views)

So just to clarify, the chart data buffer is where data is stored, right?  Let's say I change it to 100 points instead of 1024; does that mean only 100 points will be saved in the buffer at any given time?

 

Also, I tried what you said.  I turned off autoscale and tried to define the axis end points (minimum and maxium on the scales tab in chart properties) but I can't save the changes I make.  When I clicked ok and went back to properties, it has automatically changed back to what it was before.  Please see the attached file.  For the first graph, the difference isn't even one second which is too small but for the second one, it's almost 17 seconds which is too big.  That's what I'm trying to fix.

 

Download All
0 Kudos
Message 39 of 53
(1,331 Views)

Never ever attach a modified VI with the same name as the original VI. This makes debugging difficult. Always create a new unique name.

 

  • The multiplier needs to be set only once and since you graph 4 points every 250ms dt should be 1/16 of a second, right? (you have a problem that 4 points arrive at the same time every 250ms, but maybe you can ignore that... I cannot make that decision)
  • Since the X scale format never changes, you don't need to write that property, ever.
  • The X offset is the time of the first point of the chart. It needs to be written only once at the start of the program. None of your property nodes belong inside the loop.
  • Why do you get the time 4 times in parallel? Do you expect four different results? Once is enough! You can branch the wire, right?

 


@rhupd wrote:

So just to clarify, the chart data buffer is where data is stored, right?  Let's say I change it to 100 points instead of 1024; does that mean only 100 points will be saved in the buffer at any given time?


A chart keeps a buffer of the given size. These are points per plot, so if a chart has 4 plots, each keeps 100 points if the history lenght is 100. If new data arrives and the buffer is full, the oldest data gets discarded.

0 Kudos
Message 40 of 53
(1,323 Views)