LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Write data from 12 element cluster to excel

Hi XebeXUC,

 

Am I even near the solution?

Well, you get nearer 😄

 

What about using a case structure?

IF remainder == 0 THEN
   save data to file
ELSE
   do nothing
ENDIF
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 11 of 25
(1,352 Views)

What would I fill in the false case then? I can't have nothing in there

 

Edit:

 

Got it! I  don't have to go through the case 😄

 

Thanks for your help and patience 😄

0 Kudos
Message 12 of 25
(1,350 Views)

Hi XebeXUC,

 

do you really have big problems to implement a case structure to save data only when needed?

check.png

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 13 of 25
(1,347 Views)

It's monday for everyone :s

I just come back here too fast instead of thinking twice (or three times).

 

However I still failed with my time stamp, the string doesn't work with the array. And converting it to double like the rest of the data gives again a big number.

 

But that's not a big issue, I don't think it really needs a time stamp.

0 Kudos
Message 14 of 25
(1,343 Views)

Hi XebeXUC,

 

However I still failed with my time stamp, the string doesn't work with the array. And converting it to double like the rest of the data gives again a big number.

Hint: when converting the timestamp to a DBL number fails you  might convert your measurement values to strings and use an array of strings…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 15 of 25
(1,340 Views)

Oh yeah, that worked great, only negative side is that I seem to be losing digits, but the sensors are probably not even that sensitive so rough numbers should be good enough.

0 Kudos
Message 16 of 25
(1,344 Views)

Hi Xebe,

 

why do you lose digits? Use a better format string!

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 17 of 25
(1,337 Views)

@XebeXUC wrote:

It's monday for everyone :s

I just come back here too fast instead of thinking twice (or three times).

 

However I still failed with my time stamp, the string doesn't work with the array. And converting it to double like the rest of the data gives again a big number.

 

But that's not a big issue, I don't think it really needs a time stamp.


try Time to XL.vi

Excel an LabVIEW use different "Epochs"  

WARNING Time constants do not travel well adjust that constant for your timezone

Capture.png


"Should be" isn't "Is" -Jay
0 Kudos
Message 18 of 25
(1,335 Views)

Basically digits after the comma/point.
So 1,9 becomes 2...

 

But thanks for the tip, I found a better one indeed.

 

Edit: apperently it isn't that much better :S

0 Kudos
Message 19 of 25
(1,323 Views)

Hi Xebe,

 

Basically digits after the comma/point. So 1,9 becomes 2...

Using FormatIntoString with a format of %f will give you "1.9"…

 

But thanks for the tip, I found a better one indeed.

Which one?

Edit: apperently it isn't that much better

Well, which one isn't better?

 

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 20 of 25
(1,317 Views)