LabVIEW
VISA Write error: -1073807360
Upload the code if you want help. We can not even guess what you have done. I hope you already googled but if not, my guess is that the answer is in this article: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P6USSA0&l=sv-SE.
.
@A.S.H wrote:
Thank you so much for your reply,
I read that article and tried those presented solutions also, but it did not work. Later I put a time delay VI in an Output subVI (LV driver of the Instrument) which rectified the error.
As of now the problem had been solved so I guess I can work ahead with it.
I wouldn't call it solved. Quite likely this is just a band aid that for some more or less esoteric reasons seems to work for you. Delays in communication drivers to devices are NEVER a proper fix but at best a workable hack.
But without seeing your code and some documentation about the device you try to talk to, we can not do anything more for you.
@A.S.H wrote:
Sorry to bother,
I have put a time delay in between VISA WRite and its one of the Data Input for 3s. It is working fine now.
Could there had been another solution or approach which I should be taking care of?
Repeat after me: "If you need to put hard coded waits to get your communications to work, you probably don't understand how to communicate with the instrument." Manufacturers (almost) always provide a way to communicate with your instrument in as efficiently as possible.
Think of it this way. So you keep increasing the wait time until you find a wait time that enables communication without error. Usually it happens in less than one second but occasionally it can take up to five seconds. So you decide you need to wait for six seconds to make sure you've waited long enough. Now you're usually waiting five extra seconds with each communications. Manufacturers (usually) have a way of telling you when the data is ready so you wait exactly as long as is needed to retrieve the data; no more, no less.
What you have described is likely a workaround not a solution. I would unmark it as the solution until we can look at the code to determine whether or not this is good code. It smells. A lot.
