usb raw 2.0 writing text file error

[dudhar]

hi everybody,
 when i am writing the data in text file from usb raw 2.0 then i am getting this error

"Possible reason(s):

LabVIEW:  An input parameter is invalid.
---
NI-488:  Command requires GPIB Controller to be Controller in Charge."

does anybody knows y i m getting dis error?

thanks.
robin.

[Dennis_Knutson]

Since it sounds like you are doing file I/O, then it is probably the first reason. Check to see how you are creating the path. Post your VI if you wish.

[dudhar]

hi dennis,

here i am sending my vi .n thanks for reply.n have checked on ni site for that code i got this description for that error.
"
Command requires GPIB Controller to be Controller-In-Charge. This error occurs when the board is not the Controller-In-Charge and any board-level function requiring controller capability is called or when any device-level function that affects the GPIB is called and the driver cannot make the board the Controller-In-Charge."

kind regards.
robin.

[Dennis_Knutson]

Don't know why you posted the information about the error code. There are two possible reasons for the error as you already posted and since you are not using GPIB, the second reason does not apply. Since you only posted an image and not the actual VI, my guess is that you are getting the error because you are closing the file inside the loop. You should close it only when you are done. Otherwise, you will have to open it each time inside the loop.

[dudhar]

hello dennis,

i kept that file closing vi outside of loop but still giving it's error.ok here is that vi. in dis open case "26 " n in that stacked sequence stracture 2.

thanks.
robin.

[Dennis_Knutson]

You moved it outside the for loop. You still have it inside the while loop. You are still closing it and then not opening it the next time you do a write.

p.s. It's a real good idea to keep your block diagram small. A rule of thumb is to keep it about the size of your screen.

[dudhar]

hello dennis,

yaa i did wt u said n now it's working fine .

thanks
robin.

[dudhar]

hi dennis,

the text file which i am writing from my motherboard fifo after stop operation in that at the end it's giving me data with zero's .i have findout one reason n thats timeout problem.but when i am increasing the time out it reduces the zero.but still enough zero's are their.can you tell me wt i have to do? i am attaching text file with timeout duration.

the firsrt file gpxdata.text with timeout 1sec.
n the second one is gpxdata1.text with 1 milisec.

so plz can tell me wt i have to do?

kind regards
robin.