LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 1059 - unable to get 11 channels of data written to spreadsheet file

Solved!
Go to solution

Hello Everyone

 

It's Luke again. I got the error 7 fixed, it was just missing a specific filepath to save the data too.

 

I have now hit another snag along the way. When I input the data into the write to a spreadsheet box, an error comes up saying "Error 1059: Unexpected file type"

 

Does anyone have any clue why its doing this?

 

The only things I'm putting into the function box is some specific data from the 2 GPS units I'm using, with a voltage obtained from my DAQ and strain gauge setup. All the information is working on my front panel, and the information is coming through, but the data will not save to a spreadsheet file, and writing to an .lvm file will not work either.

 

I will enclose a printscreen of the setup for the block diagram:

 

spreadsheet problem

0 Kudos
Message 1 of 8
(4,564 Views)

'Unexpected File Type' makes me think that there is a problem with the file path.

What are you using as the extention to your file? ie .txt, .xls, etc

Cory K
0 Kudos
Message 2 of 8
(4,556 Views)

Who are the Skier and the boat? Sounds interesting 🙂

 

0 Kudos
Message 3 of 8
(4,548 Views)

I'm unsure of the exact file extension

 

How do you set it?

0 Kudos
Message 4 of 8
(4,538 Views)
Try this VI
Balaji PK (CLA)
Ever tried. Ever failed. No matter. Try again. Fail again. Fail better

Don't forget Kudos for Good Answers, and Mark a solution if your problem is solved.
0 Kudos
Message 5 of 8
(4,534 Views)
Solution
Accepted by topic author Ohm Man

Ohm Man wrote:

I'm unsure of the exact file extension

 

How do you set it?


 

You set by whatever file name you put into your filepath control.

 

I just don't think it makes sense to get an error that says that for trying to write to a text file.

 

Any chance you are trying to write the file to a path that you don't have full access rights to?  I'm thinking the error may be 1059, but it is actually be caused by some windows file error.  How about some odd characters in the filename control that are not valid in Windows?

0 Kudos
Message 6 of 8
(4,533 Views)

Error 7 was due to the file path not being found. We fixed that and made a similar filepath with full access rights to it.

 

The thing is now, whenever I go to run the program, it tells me "Unexpected file type" so I don't think its the actual filepath that its trying to write to.

 

I'll give the .vi a shot 🙂

0 Kudos
Message 7 of 8
(4,507 Views)
I'm an idiot and didnt specify an actual file name, just a file path. Thanks to everyone! 🙂
0 Kudos
Message 8 of 8
(4,502 Views)