LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 43 in Write to Spreadsheet File (DBL)

Hi,

 

I want to save my 2D array data in text file using Write to Spreadsheet.vi. It is functional when i run it in normal VI. But when i deploy the vi into my chassis board, there is an error 43 occured.

 

Can help me solve the problem? Thank you.

 

Regards.

0 Kudos
Message 1 of 16
(4,315 Views)

I don't understand when you deploy it into the Chassis board. What is the hardware? You have any FPGA card and are you trying to put this VI into it? Please explain

-----

The best solution is the one you find it by yourself
0 Kudos
Message 2 of 16
(4,295 Views)

Hi Yapp,

 

you really want to do file access from within the FPGA?

 

That's surely NOT the recommended way…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 3 of 16
(4,285 Views)

sorry i m newbie. Let me explain once again.

 

when i run my vi file, there is no error. (Open vi-> run vi-> press stop-> "choose file to write" pop out-> save signal data in text file).

 

But when i run vi in lvproj (open lvproj -> open vi from lvproj -> run vi -> press stop -> error 43 occurred).

 

May i know why there is not functioning when i run the vi under lyproj? THank you.

 

 

 

0 Kudos
Message 4 of 16
(4,261 Views)

How is your project set up?  If this VI is actually supposed to run on an FPGA as the file name suggests, you should get errors.


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 5 of 16
(4,252 Views)

Sorry i not very understand it. Is it means the problem is my vi file name?

 

0 Kudos
Message 6 of 16
(4,250 Views)

No. The problem is in which target your VI resides. Can you show a screen shot of your project?

-----

The best solution is the one you find it by yourself
0 Kudos
Message 7 of 16
(4,228 Views)

@Yapp wrote:

Sorry i not very understand it. Is it means the problem is my vi file name?

 


No.  The name of your VI makes us suspect that you are trying to run this VI on an FPGA, which doesn't have any File I/O.  That is why we are asking for you to share your project so that we can see what context your are running this VI in.


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 8 of 16
(4,211 Views)

sorry, please forget the name. And plz refer following picture. thx.

0 Kudos
Message 9 of 16
(4,200 Views)

Hi Yapp,

 

so it's a RIO: a RIO (usually) has no user interface and so you cannot open a dialog to ask the user for some settings (like filenames)…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 10 of 16
(4,196 Views)