Export Waveform to Spreadsheet File bug

[BillMe]

With LV2012:

When using the Export Waveforms to Spreadsheet using an 1D array of waveforms, the resulting file has an extra line with delimiters but no text. This is for the case where you choose NOT to write a header, otherwise it appears to work correctly.For example, for single element 1D waveform with one Y data element, I get the following in the csv file (comma delimited):

1/19/2013 18:45:34.961600,1.229937E+1
,

Note the comma on the second line.

Culprit looks to be an "Increment" on the output of the for loop which determines max numbr of rows needed. That works as long as you are writing a header along with the data. If not writing a header, the increment causes an extra blank string at the end of the line which becomes a delimiter as shown above.

Perhaps this is a CAR that just hasn't been fixed yet. Hard to believe no one else has reported this but I found nothing in the forum.

[IanW]

I found the same behaviour in my version 10, so it’s been like this for some time. I agree with your explanation of where the problem is in the vi’s code.

Not sure how you can raise this issue, bug reporting procedures seem to be hidden away quite well ( I guess can understand why) !!

[billko]

---

@IanW wrote:

I found the same behaviour in my version 10, so it’s been like this for some time. I agree with your explanation of where the problem is in the vi’s code.

Not sure how you can raise this issue, bug reporting procedures seem to be hidden away quite well ( I guess can understand why) !!

---

Actually, reporting it to the forum is an excellent way of "raising the issue."  Just about every post that I've read that claims to be reporting a bug has been looked at by an NI rep and acted upon, whether it be to acknowledge an old bug, request more information to create a new CAR, and even to update on the progress of the CAR.  I've seen threads updated weeks after the original post to update the OP on the progress of the CAR.

[IanW]

I didn’t mean to imply that that this wouldn’t get looked at by NI. I know that there are many NI people active on the forums providing valuable help and support.

I’m sure this issue will get looked at here, which is why I replied adding my little bit of additional evidence.

Ian

[chaka1234]

Hi BillMe,

Actually we have a CAR #44310 to track this same issue and currently our R&D department is working to find a fix for this.

Best,

Carmen C.

[johnsold]

I notice that this VI has been re-written in LV2013. It does not appear to exhibit this behavior (extra lines) in this version.

However, there is no reference to CAR #44310 in the fixed items list.  Did this get fixed and not reported? Or fixed unintentionally as a result of some other change and not linked to the CAR?  Or are there still unresolved issues which my quick tests did not uncover?

Lynn

[JÞB]

---

@johnsold wrote:

I notice that this VI has been re-written in LV2013. It does not appear to exhibit this behavior (extra lines) in this version.

However, there is no reference to CAR #44310 in the fixed items list.  Did this get fixed and not reported? Or fixed unintentionally as a result of some other change and not linked to the CAR?  Or are there still unresolved issues which my quick tests did not uncover?

Lynn

---

Thanks Lynn,  I'll do some hand waving and see if we can't get a definitive answer

Hey NI Guys /\/\/\/\/

[Jeff-P]

CAR 44310 is still an open CAR but may have been fixed as a byproduct of another fix put into LabVIEW 2013. I will test and see if the CAR is still reproducible in 2013. Thanks for bringing this up.

Jeff Peacock 

Product Support Engineer | LabVIEW R&D | National Instruments 

[Jeff-P]

I was able to reproduce this in 2013, the behavior is still present. The key to reproducing it is to make sure you aren't writing a header: i forgot that and tested 2013, 2012, 2009 and 8.5 before realizing I was doing something wrong. The following snippet reproduces this.

Thanks

Jeff Peacock 

Product Support Engineer | LabVIEW R&D | National Instruments 

[johnsold]

Jeff,

Thanks for digging into this. I see it now also.

I worked out a limited fix for this (in LV 2012) for a project that I worked on recently. Would NI be interested in looking at what I did?

Lynn